Operations and Maintenance Using CLI

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

Release name

ETSI

Release 3.4

ANSI

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

Description

Part number

CD containing all the documents in the 7302 ISAM documentation set

3HH-05883-AAAA

Product Information

Provides general system information for the 7302 ISAM

3HH-05221-AAAA-TCZZA

System Description

Provides conceptual information for the 7302 ISAM and the 7330 ISAM FTTN

3HH-05217-AAAA-TQZZA

Safety Manual

Provides general safety guidelines when handling, installing, or operating the 7302 ISAM equipment


Operations and Maintenance Using CLI

Provides task-oriented procedures for operating and maintaining the 7302 ISAM and 7330 ISAM FTTN using the CLI


Migration User Guide

Provides information for installing or upgrading the 7302 ISAM


Describes the hardware installation for the 7302 ISAM XD Modular equipment

3FE-21578-AAAA-RJZZA

Documentation CD 7302 ISAM CD General documentation

Hardware documentation XD Modular Hardware Installation Guide (1 of 2)

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

Description

Part number

FD Hardware Installation Guide

Describes the hardware installation for the 7302 ISAM FD equipment

3HH-03591-AAAA-RJZZA

UD Hardware Installation Guide

Describes the hardware installation for the 7302 ISAM UD equipment

3FE-21575-AAAA-RJZZA

CLI Commands

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

3HH-04416-CEAA-TCZZA

TL1 Commands and Messages

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


Software Installation Guide

Describes the software management of the 7302 ISAM equipment

3HH-03390-AAAA-RJZZA

Software Upgrade and Migration Application Procedures

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


CLI and TL1 documentation

Software documentation

(2 of 2) Note (1)

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

Description

Part number

CD containing all the documents in the 7330 ISAM FTTN documentation set (2)

3HH-05679-AAAA

Product Information

Provides general system information, features and functionality, and hardware unit data sheets for the 7330 ISAM FTTN


System Description

Provides conceptual information for the 7302 ISAM and the 7330 ISAM FTTN


Planning and Ordering

Provides information for planning and ordering the 7330 ISAM FTTN


Hardware Installation and Maintenance Practices

Provides task-oriented procedures for installing and maintaining the 7330 ISAM FTTN hardware


Operations and Maintenance Using CLI

Provides task-oriented procedures for operating and maintaining the 7302 ISAM and 7330 ISAM FTTN using the CLI


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

3HH-04416-CEAA-TCZZA

Documentation CD 7330 ISAM FTTN CD General documentation

CLI and TL1 documentation CLI Commands

(1 of 2)


v

Preface

Title

Description

Part number

TL1 Commands and Messages

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


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


Software documentation (2) Software Upgrade and Migration Application Procedures (2 of 2) Note (2)

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

vi

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

This is one option.

b

This is another option.


Preface

2

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

2

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

This is the first substep.

ii

This is the second substep.

iii

This is the third substep.

You must perform this step.

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 Système international d’unités (SI) standard for abbreviation of metric units.


vii

Preface

viii


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

1—

Introduction 1.1 1.2 1.3

1-1

Introduction ........................................................................................................ 1-2 How to Use this Document ................................................................................ 1-2 Configuration examples ..................................................................................... 1-5

Index List (IXL) IXL 100 —

Master Task Index List


IXL 100-1

ix

Contents

Non-Trouble Procedures (NTP) NTP 100 — Set up a CLI session and configure users

NTP 100-1

NTP 101 — Execute script files

NTP 101-1

NTP 102 — Configure the system

NTP 102-1

NTP 103 — Configure equipment

NTP 103-1

NTP 104 — Configure a cross-connect VLAN

NTP 104-1

NTP 105 — Configure an iBridge VLAN

NTP 105-1

NTP 106 — Configure an IP-aware bridge

NTP 106-1

NTP 107 — Configure an IP router

NTP 107-1

NTP 108 — Configure services

NTP 108-1

NTP 109 — Configure PPPoE termination

NTP 109-1

NTP 110 — Add an iBridge user

NTP 110-1

NTP 111 — Add an IPoA user

NTP 111-1

NTP 112 — Add an IPoE user

NTP 112-1

NTP 113 — Add a PPPoE user

NTP 113-1

NTP 114 — Perform equipment repairs

NTP 114-1

NTP 115 — Monitor alarms

NTP 115-1

x


Contents

NTP 116 — Perform software management

NTP 116-1

NTP 117 — Modify system parameters

NTP 117-1

NTP 118 — Monitor performance and view configuration NTP 118-1 NTP 119 — Modify configured services

NTP 119-1

NTP 120 — Troubleshooting

NTP 120-1

NTP 121 — Manage an SNMP proxy CPE

NTP 121-1

NTP 122 — Cluster management

NTP 122-1

NTP 123 — Secure shell

NTP 123-1

NTP 124 — Maintain the system

NTP 124-1

NTP 125 — Add an IPoA cross-connect user

NTP 125-1

NTP 126 — Manage system logging

NTP 126-1

NTP 127 — Configure SHDSL

NTP 127-1

NTP 128 — Manage an IPProxy CPE

NTP 128-1

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


NTP 130-1

xi

Contents

Detailed Level Procedures (DLP) DLP 100 — Set up a CLI session

DLP 100-1

DLP 101 — Create operator profiles and instances

DLP 101-1

DLP 102 — Configure dual IP address

DLP 102-1

DLP 103 — Configure system parameters

DLP 103-1

DLP 104 — Configure network interfaces

DLP 104-1

DLP 105 — Configure link aggregation usage

DLP 105-1

DLP 106 — Configure RSTP

DLP 106-1

DLP 107 — Configure OSPF

DLP 107-1

DLP 108 — Configure RIP

DLP 108-1

DLP 109 — Configure SNMP and trap management

DLP 109-1

DLP 110 — Manage alarms

DLP 110-1

DLP 111 — Plan, replan, and unplan equipment

DLP 111-1

DLP 112 — Lock and unlock equipment

DLP 112-1

DLP 113 — Configure the equipment

DLP 113-1

DLP 114 — Configure NT redundancy

DLP 114-1

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

xii


Contents

DLP 116 — Create a layer2-terminated router VLAN

DLP 116-1

DLP 117 — Create a C-VLAN

DLP 117-1

DLP 118 — Create an S-VLAN

DLP 118-1

DLP 119 — Create an SC-VLAN

DLP 119-1

DLP 120 — Create an iBridge VLAN

DLP 120-1

DLP 121 — Add network interfaces to a VLAN

DLP 121-1

DLP 122 — Create a forwarding VRF

DLP 122-1

DLP 123 — Create a router VRF

DLP 123-1

DLP 124 — Create an xDSL user

DLP 124-1

DLP 125 — Create an IPoA user

DLP 125-1

DLP 126 — Create an IPoE user

DLP 126-1

DLP 127 — Create a PPPoE user

DLP 127-1

DLP 128 — Add an LT port to a VLAN

DLP 128-1

DLP 129 — Create xDSL profiles

DLP 129-1

DLP 130 — Configure xDSL bonding

DLP 130-1

DLP 131 — Create an xDSL bonding group

DLP 131-1

DLP 132 — Configure filtering on SHub

DLP 132-1

DLP 133 — Configure QoS on layer 2

DLP 133-1


xiii

Contents

DLP 134 — Configure QoS

DLP 134-1

DLP 135 — Configure a QoS-aware VLAN

DLP 135-1

DLP 136 — Configure multicast on the LT

DLP 136-1

DLP 137 — Configure IGMP proxy

DLP 137-1

DLP 138 — Configure IGMP snooping

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

DLP 145 — Configure 802.1x

DLP 145-1

DLP 146 — Configure PPPoE relay

DLP 146-1

DLP 147 — Configure PPPoX relay

DLP 147-1

DLP 148 — Enable the PPPoE server

DLP 148-1

DLP 149 — Configure PPPoE profiles

DLP 149-1

xiv


Contents

DLP 150 — Configure ARP table entry

DLP 150-1

DLP 151 — Shut down and restart the NT

DLP 151-1

DLP 152 — Reboot the system

DLP 152-1

DLP 153 — Shut down and restart individual equipment DLP 153-1 DLP 154 — Create a snapshot alarm table

DLP 154-1

DLP 155 — Monitor alarms

DLP 155-1

DLP 156 — Management of the SHub database

DLP 156-1

DLP 157 — Manage the SHub database

DLP 157-1

DLP 158 — Manage the system database

DLP 158-1

DLP 159 — Manage OSWP

DLP 159-1

DLP 160 — View version of the SHub software

DLP 160-1

DLP 161 — View software licenses counters

DLP 161-1

DLP 162 — Modify the external management VLAN

DLP 162-1

DLP 163 — Modifying xDSL profiles

DLP 163-1

DLP 164 — Ping another host

DLP 164-1

DLP 165 — Perform a traceroute action

DLP 165-1

DLP 166 — Configure SNMP proxy CPE management

DLP 166-1

DLP 167 — Script files

DLP 167-1


xv

Contents

DLP 168 — Modify the system management IP parameters DLP 168-1 DLP 169 — Configure cluster management

DLP 169-1

DLP 170 — Configure SSH

DLP 170-1

DLP 171 — Enable EMS management

DLP 171-1

DLP 172 — Create a default operator profile

DLP 172-1

DLP 173 — Switching a user from ADSL to VDSL

DLP 173-1

DLP 174 — Create an IPoA cross-connect user

DLP 174-1

DLP 175 — Configure single IP address

DLP 175-1

DLP 176 — Performance monitoring commands

DLP 176-1

DLP 177 — Configure SFP downlink ports

DLP 177-1

DLP 178 — Configure the default security domain

DLP 178-1

DLP 179 — Configure system logging

DLP 179-1

DLP 180 — Configure static MAC addresses

DLP 180-1

DLP 181 — Configure operator authentication via RADIUS DLP 181-1 DLP 182 — Configure SHDSL links

DLP 182-1

DLP 183 — Configure IMA on SHDSL links

DLP 183-1

DLP 184 — Convert the NE IP address

DLP 184-1

xvi


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

DLP 188 — Configure custom PSD points

DLP 188-1

DLP 189 — Configure VDSL2 virtual noise values

DLP 189-1

DLP 190 — Configure threshold crossing alerts

DLP 190-1

DLP 191 — Enable dual tagging in the SHub

DLP 191-1

DLP 192 — Configure IPProxy CPE management

DLP 192-1

DLP 193 — Enable IPProxy CPE management

DLP 193-1

DLP 194 — Configure IPProxy CPE management session DLP 194-1 DLP 195 — Configure general bridge parameters

DLP 195-1

DLP 196 — Configure Voice SIP

DLP 196-1

DLP 197 — View port configuration and operational data DLP 197-1 DLP 198 — Configure multicast on the SHub

DLP 198-1

DLP 199 — Configure QoS on the SHub

DLP 199-1

DLP 200 — Configure MSTP

DLP 200-1


xvii

Contents

DLP 201 — Configure protocol tracing

DLP 201-1

DLP 202 — Configure QoS threshold crossing alerts

DLP 202-1

DLP 203 — Configure general security settings

DLP 203-1

DLP 204 — Configure an unnumbered IP interface on the SHub DLP 204-1 DLP 205 — Configure Link Related Ethernet OAM

DLP 205-1

DLP 206 — Configure a DPBO profile

DLP 206-1

DLP 207 — Modify a DPBO profile

DLP 207-1

DLP 208 — Configure power back off

DLP 208-1

DLP 209 — Configure vMAC

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

RTP 101 — Restore the configuration

RTP 101-1

RTP 102 — Retrieve remote inventory

RTP 102-1

xviii


Contents

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

TAP 100-1

TAP 101 — F5 loopback test

TAP 101-1

TAP 102 — Equipment repair

TAP 102-1

TAP 103 — Single ended line testing

TAP 103-1

TAP 104 — Fault isolation and troubleshooting

TAP 104-1

Training (TNG) TNG 100 — Service installation

TNG 100-1

TNG 101 — QoS configuration

TNG 101-1

TNG 102 — IGMP and multicast configuration

TNG 102-1

TNG 103 — VBAS

TNG 103-1

TNG 104 — DHCP relay agent configuration

TNG 104-1

TNG 105 — Overall software packages

TNG 105-1

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

TNG 107-1

TNG 108 — SHDSL parameters

TNG 108-1


xix

Contents

TNG 109 — Performance management counters

TNG 109-1

TNG 110 — Configuration examples

TNG 110-1

TNG 111 — 7330 ISAM FTTN ES configuration

TNG 111-1

TNG 112 — 7330 ISAM FTTN configuration for subtending TNG 112-1 TNG 113 — Multi-ADSL parameters

TNG 113-1

TNG 114 — DLP configuration examples

TNG 114-1

TNG 115 —

Slot numbering schemes

TNG 115-1

TNG 116 —

Link Related Ethernet OAM (EFM OAM)

TNG 116-1

Glossary

Index

xx


1 — Introduction

1.1 Introduction

1-2

1.2 How to Use this Document 1.3 Configuration examples

1-2 1-5


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


1 — Introduction

Figure 1-1 TOP Layers and Documentation Path Task index List (IXL) or Overview Flowchart

Non-Trouble Clearing Procedure (NTP)

User Training Package (TNG)

Routine Task List (RTL)

Trouble Analysis Procedure (TAP) 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.


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


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.


1-5

1 — Introduction

1-6


Index List (IXL)

IXL 100 — Master Task Index List



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

NTP number

Add a PPPoE user

NTP 113

Add an iBridge user

NTP 110

Add an IPoA cross-connect user

NTP 125

Add an IPoA user

NTP 111

Add an IPoE user

NTP 112

Cluster management

NTP 122

Configure a cross-connect VLAN

NTP 104

Configure a loopback interface on the SHub

NTP 129

Configure an iBridge VLAN

NTP 105

Configure an IP router

NTP 107

Configure an IP-aware bridge

NTP 106

Configure equipment

NTP 103

Link Related Ethernet OAM

NTP 130

Configure PPPoE termination

NTP 109

Configure services

NTP 108

Configure SHDSL

NTP 127

Configure the system

NTP 102

Execute script files

NTP 101

Maintain the system

NTP 124

Manage an IPProxy CPE

NTP 128

Manage an SNMP proxy CPE

NTP 121

(1 of 2)


IXL 100-1


Title

NTP number

Manage system logging

NTP 126

Modify configured services

NTP 119

Modify system parameters

NTP 117

Monitor alarms

NTP 115

Monitor performance and view configuration

NTP 118

Perform equipment repairs

NTP 114

Perform software management

NTP 116

Secure shell

NTP 123

Set up a CLI session and configure users

NTP 100

Troubleshooting

NTP 120

(2 of 2)

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

DLP number

Add an LT port to a VLAN

DLP 128

Add network interfaces to a VLAN

DLP 121

Configure 802.1x

DLP 145

Configure a DPBO profile

DLP 206

Configure a QoS-aware VLAN

DLP 135

Configure an unnumbered IP interface on the SHub

DLP 204

Configure ANCP session

DLP 185

Configure ARP table entry

DLP 150

Configure cluster management

DLP 169

Configure custom PSD points

DLP 188

Configure DHCP MAC concentration in forwarder mode

DLP 186

Configure DHCP relay agent in forwarder mode

DLP 141

Configure DHCP relay agent in iBridge mode

DLP 139

Configure DHCP relay agent in router mode

DLP 140

Configure dual IP address

DLP 102

Configure filtering on SHub

DLP 132

Configure general bridge parameters

DLP 195

Configure general security settings

DLP 203

Configure global VLAN parameters

DLP 187

Configure IGMP proxy

DLP 137

Configure IGMP snooping

DLP 138

Configure IMA on SHDSL links

DLP 183

(1 of 4)

IXL 100-2



Title

DLP number

Configure IPProxy CPE management

DLP 192

Configure IPProxy CPE management session

DLP 194

Configure link aggregation usage

DLP 105

Configure Link Related Ethernet OAM

DLP 205

Configure a PPP connection for local RADIUS authentication

DLP 143

Configure MSTP

DLP 200

Configure multicast on the LT

DLP 136

Configure multicast on the SHub

DLP 198

Configure NT redundancy

DLP 114

Configure operator authentication via RADIUS

DLP 181

Configure OSPF

DLP 107

Configure power back off

DLP 208

Configure PPPoE profiles

DLP 149

Configure PPPoE relay

DLP 146

Configure PPPoX relay

DLP 147

Configure protocol tracing

DLP 201

Configure QoS

DLP 134

Configure QoS on layer 2

DLP 133

Configure QoS on the SHub

DLP 199

Configure QoS threshold crossing alerts

DLP 202

Configure RADIUS

DLP 144

Configure RIP

DLP 108

Configure SFP downlink ports

DLP 177

Configure SFP uplink ports

DLP 211

Configure SHDSL links

DLP 182

Configure single IP address

DLP 175

Configure SNMP and trap management

DLP 109

Configure SNMP proxy CPE management

DLP 166

Configure SSH

DLP 170

Configure static MAC addresses

DLP 180

Configure system logging

DLP 179

Configure system parameters

DLP 103

Configure the default security domain

DLP 178

Configure the equipment

DLP 113

Configure the security domain

DLP 142

Configure threshold crossing alerts

DLP 190

Configure VDSL2 virtual noise values

DLP 189

(2 of 4)


IXL 100-3


Title

DLP number

Configure vMAC

DLP 209

Configure Voice SIP

DLP 196

Configure xDSL bonding

DLP 130

Convert the NE IP address

DLP 184

Create a C-VLAN

DLP 117

Create a default operator profile

DLP 172

Create a forwarding VRF

DLP 122

Create a layer2-terminated forwarder VLAN

DLP 115

Create a layer2-terminated router VLAN

DLP 116

Create a PPPoE user

DLP 127

Create a router VRF

DLP 123

Create a snapshot alarm table

DLP 154

Create an iBridge VLAN

DLP 120

Create an IPoA cross-connect user

DLP 174

Create an IPoA user

DLP 125

Create an IPoE user

DLP 126

Create an SC-VLAN

DLP 119

Create an S-VLAN

DLP 118

Create an xDSL user

DLP 124

Create operator profiles and instances

DLP 101

Create xDSL profiles

DLP 129

Enable dual tagging in the SHub

DLP 191

Enable EMS management

DLP 171

Enable IPProxy CPE management

DLP 193

Enable the PPPoE server

DLP 148

Lock and unlock equipment

DLP 112

Manage alarms

DLP 110

Manage OSWP

DLP 159

Manage the SHub database

DLP 157

Modify a DPBO profile

DLP 207

Modify the external management VLAN

DLP 162

Modify the system management IP parameters

DLP 168

Modifying xDSL profiles

DLP 163

Monitor alarms

DLP 155

Perform a traceroute action

DLP 165

Performance monitoring commands

DLP 176

Ping another host

DLP 164

(3 of 4)

IXL 100-4



Title

DLP number

Plan, replan, and unplan equipment

DLP 111

Reboot the system

DLP 152

Script files

DLP 167

Set up a CLI session

DLP 100

Shut down and restart individual equipment

DLP 153

Shut down and restart the NT

DLP 151

Switching a user from ADSL to VDSL

DLP 173

View port configuration and operational data

DLP 197

View software licenses counters

DLP 161

View the status of various system parameters

DLP 210

View version of the SHub software

DLP 160

(4 of 4)

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

RTP number

Backup the configuration

RTP 100

Restore the configuration

RTP 101

Retrieve remote inventory

RTP 102

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

TAP number

Equipment repair

TAP 102

F5 loopback test

TAP 101

Fault isolation and troubleshooting

TAP 104

Metallic test access

TAP 100

Single ended line testing

TAP 103

Table IXL 100-5: Training (TNG) Title

TNG number

7330 ISAM FTTN configuration for subtending

TNG 112

7330 ISAM FTTN ES configuration

TNG 111

Configuration examples

TNG 110

DHCP relay agent configuration

TNG 104

(1 of 2)


IXL 100-5


Title

TNG number

DLP configuration examples

TNG 114

IGMP and multicast configuration

TNG 102

Link Related Ethernet OAM (EFM OAM)

TNG 116

Multi-ADSL parameters

TNG 113

Overall software packages

TNG 105

Performance management counters

TNG 109

QoS configuration

TNG 101

Service installation

TNG 100

SHDSL parameters

TNG 108

Slot numbering schemes

TNG 115

Specifying 7330 ISAM FTTN remote expansion units using the CLI

TNG 106

VBAS

TNG 103

VDSLx parameters

TNG 107

(2 of 2)

IXL 100-6


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


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.


NTP 100-1

NTP 100 — Set up a CLI session and configure users

Figure NTP 100-1: Management Topology EMS (e.g. AWS 5523)

SNMP UDP161/ 162

CLI Terminal

TL1 Terminal

Telnet TCP1023

SSH TCP1022

Telnet TCP23

TL1 Craft Terminal

TL1 TL1 Gateway

TL1 UDP13001

SSH TCP22

CLI Craft Terminal

RS232

RS232

ISAM TL1 agent CLI agent

SNMP agent

IACM subsystem SNMP agent

MIB NT Controller / LIMs

SHub subsystem

MIB SHub

Active DB

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

Description

EMS

Element Management System based on SNMP

TL1 CT

Craft Terminal using TL1 commands

CLI CT

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.



2

Create and configure an Operator Profile; see DLP 101.

3

Create a default Operator Profile; see DLP 172.

4

STOP. This procedure is complete.


NTP 100-3


NTP 100-4


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

Create and execute script files; see DLP 167.

2



NTP 101-1

NTP 101 — Execute script files

NTP 101-2


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.


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.

NTP 102-2

2

Configure the system parameters; see DLP 103.

3

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

4

Enable the management of EMS; see DLP 171.

5

Configure the alarm management; see DLP 110.

6

Save the SHub database; see DLP 157.

7



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

Description

Planning equipment

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

Unplanning equipment

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

(1 of 2)


NTP 103-1

NTP 103 — Configure equipment

Action

Description

Replanning equipment

Replanning is done when changing the current equipment.

Locking and unlocking equipment

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

NTP 103-2

1

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

2

Lock or unlock the equipment; see DLP 112.

3

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

4

Configure NT redundancy; see DLP 114.

5

Configure SFP downlink ports; see DLP 177.

6

Configure SFP uplink ports; see DLP 211.

7



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.


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:

NTP 104-2

1

For the configuration of global VLAN parameters: see DLP 187.

2

For the creation of a C-VLAN; see DLP 117.

3

For the creation of an S-VLAN; see DLP 118.

4

For the creation of an SC-VLAN; see DLP 119.

5

For the creation of an Qos aware VLAN; see DLP 135.

6



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


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:

NTP 105-2

1

For the configuration of global VLAN parameters: see DLP 187.

2

For the creation of an iBridge VLAN; see DLP 120.

3

Add the network interface to the iBridge VLAN; see DLP 121.

4



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


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:

NTP 106-2

1

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

2

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

3

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

4



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


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:

NTP 107-2

1

Create a router VRF; see DLP 123.

2

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

3

Add users; see DLP 125 for adding IPoA user or DLP 126 for adding IPoE user.

4



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

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

ii

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

iii

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

2

Configure xDSL bonding; see DLP 130.

3

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


NTP 108-1


4

5

6

7

8

9

NTP 108-2

Configure QoS: i

For the configuration of a QoS-aware VLAN; see DLP 135.

ii

For the configuration of QoS on L2; see DLP 133.

iii

For the configuration of QoS on L3; see DLP 134.

iv

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

v

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

Configure IGMP and multicast: i

For the configuration of multicast on the LT; see DLP 136.

ii

For the configuration of multicast on the SHub; see DLP 198.

iii

For the configuration of IGMP proxy on the LT; see DLP 137.

iv

For the configuration of IGMP snooping on the SHub; see DLP 138.

Configure DHCP Relay: i

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

ii

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

iii

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

iv

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

Configure the authentication settings: i

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

ii

For the configuration of local authentication; see DLP 143.

iii

For the configuration of RADIUS; see DLP 144.

iv

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

v

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

vi

For the configuration of the default security domain; see DLP 178.

Configure the PPP relay settings: i

For the configuration of PPPoE relay; see DLP 146.

ii

For the configuration of PPPoA-PPPoE relay; see DLP 147.

Configure NT redundancy; see DLP 114.



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.

11

If necessary, configure Multiple Spanning Tree Protocol (MSTP); see DLP 200.

12

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

For the configuration of Open Shortest Path First (OSPF) management; see DLP 107.

ii

For the configuration of Routing Information Protocol (RIP) management; see DLP 108.

13

Configure Voice SIP; see DLP 196.

14

Configure an ANCP session; see DLP 185.

15



NTP 108-3


NTP 108-4


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

For the configuration of the PPPoE server; see DLP 148.

2

For the configuration of PPPoE profiles; see DLP 149.

3



NTP 109-1

NTP 109 — Configure PPPoE termination

NTP 109-2


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

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

2

Create an iBridge user; see DLP 124.

3



NTP 110-1

NTP 110 — Add an iBridge user

NTP 110-2


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

If the first IPoA user to be created on a VLAN needs DHCP, configure the VRF for DHCP; see DLP 140.

2

Create an IPoA user; see DLP 125.


NTP 111-1

NTP 111 — Add an IPoA user

3

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

NTP 111-2



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:

• • •


Procedure Proceed as follows to add an IPoE user: 1

If the first IPoE user to be created on a VLAN needs DHCP, configure the VRF for DHCP; see DLP 140.

2

Create an IPoE user; see DLP 126.

3

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


NTP 112-1

NTP 112 — Add an IPoE user

4

NTP 112-2



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

Create a PPPoE user; see DLP 127.

2

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


NTP 113-1

NTP 113 — Add a PPPoE user

3

NTP 113-2



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

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

2

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.

3

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

4

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

5

a

Shut down or restart the SHub; see DLP 151.

b

Reboot the entire system; see DLP 152.

c

Shut down individual equipment; see DLP 153.



NTP 114-1

NTP 114 — Perform equipment repairs

NTP 114-2


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

Create an alarm snapshot table; see DLP 154.

2

Monitor the alarms; see DLP 155.

3



NTP 115-1

NTP 115 — Monitor alarms

NTP 115-2


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

Management of the NT and SHub database; see RTP 100.

2

Management of the Overall Software Packages; see DLP 159.

3

View the version of the SHub software; see DLP 160.

4

Management of the software licenses; see DLP 161.

5



NTP 116-1

NTP 116 — Perform software management

NTP 116-2


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

Modify the management IP parameters; see DLP 168.

2

Change the external management VLAN; see DLP 162.

3

Configure an ARP table entry; see DLP 150.

4

Configure filtering on the SHub; see DLP 132.

5

Configure static MAC addresses; see DLP 180.

6



NTP 117-1

NTP 117 — Modify system parameters

NTP 117-2


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

Configure the Treshold Crossing Alert (TCA); see DLP 190

2

Viewing the PM counters; see DLP 176

3

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

4



NTP 118-1

NTP 118 — Monitor performance and view configuration

NTP 118-2


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

Modify an xDSL profile; see DLP 163.

2

Switching a user from ADSL to VDSL; see DLP 173.

3



NTP 119-1

NTP 119 — Modify configured services

NTP 119-2


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

Ping command; see DLP 164.

2

Traceroute command; see DLP 165.

3



NTP 120-1

NTP 120 — Troubleshooting

NTP 120-2


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 carrier’s 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


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:

NTP 121-2

1

Configure SNMP proxy CPE management; see DLP 166.

2



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.


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

Cluster No. 2 (A logical DSLAM)

Management Command to Cluster 2

EMS (AWS)

Management Command to Cluster 1

Single Logical Management Path DSLAM No. 7

Cluster No.1 (A logical DSLAM)

DSLAM No. 8 DSLAM No. 2

DSLAM No. 1 DSLAM No. 9

DSLAM No. 10

DSLAM No. 11

DSLAM No. 3

DSLAM No. 4

DSLAM No. 5

DSLAM No. 6

Procedure To configure cluster management, you need to perform the following tasks:

NTP 122-2

1

Configure the cluster; see DLP 169.

2



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

Configure the SSH functionality; see DLP 170.

2



NTP 123-1

NTP 123 — Secure shell

NTP 123-2


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

Back up the system configuration; see RTP 100.

2

Restore the system configuration; see RTP 101.

3

Retrieve the remote inventory; see RTP 102.

4



NTP 124-1

NTP 124 — Maintain the system

NTP 124-2


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

Create a C-VLAN or SC-VLAN; see DLP 117 or DLP 119.

2

Create an IPoA cross- connect user; see DLP 174.

3



NTP 125-1

NTP 125 — Add an IPoA cross-connect user

NTP 125-2


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


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.

NTP 126-2

1

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

2

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

3



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

To configure SHDSL links; see DLP 182.

2

To configure IMA on SHDSL links; see DLP 183.

3



NTP 127-1

NTP 127 — Configure SHDSL

NTP 127-2


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 CPE-MM

EMS

IP@/UDP IP@/TCP

IP@/UDP IP@/TCP

RMI

RMI

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

User Management Entity NE xDSL CPE

Relay LMI

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


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:

NTP 128-2

1

If not already done, enable the dual tagging mode in the SHub; see DLP 191

2

Configure the S-VLAN to be used for IPProxy CPE Management; see DLP 192

3

Enable the IPProxy CPE Management function; see DLP 193

4

Configure one or more IPProxy CPE Management sessions; see DLP 194

5

On the session configured, use Telnet or TFTP to the modem(s) to communicate using the connection () port allocated for the session.

6



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

Configure a host IP address on the NT using a mask 32.

2

Configure an unnumbered interface on the Shub (that is, a VLAN which has the network IP address as numbered interface); see DLP 204.

3

Configure VRF routes on the SHub:

• •

a route via the management VLAN 4093 directly attached. a default route via IP address out of address range of 2.

4

Configure a default route on the NT via the IP address of the numbered VLAN interface on the SHub.

5



NTP 129-1

NTP 129 — Configure a loopback interface on the SHub

NTP 129-2


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

Configuration of EFM OAM; see DLP 205.

2

After configuration, the following actions can be performed:

3

a

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

b

Viewing of EFM OAM statistics; see DLP 205.

c

Retrieve MAC counters; see DLP 205.

d

Retrieve PME counters; see DLP 205.



NTP 130-1

NTP 130 — Link Related Ethernet OAM

NTP 130-2


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


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


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


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


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



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

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.

3

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



DLP 100-1

DLP 100 — Set up a CLI session

DLP 100-2


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


DLP 101-1


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 (no) password-timeout (no) terminal-timeout (no) slot-numbering (no) description (no) aaa (no) atm (no) alarm (no) dhcp (no) equipment (no) igmp (no) ip (no) pppoe (no) qos (no) software-mngt (no) transport (no) vlan (no) xdsl (no) security

Note — No capitals may be used in the profile name.

2

Create an operator instance with the following command: configure system security operator (name) profile password prompt | plain: | encrypted: (no) prompt (no) description (no) more

Note — No capitals and blanks may be used in the operator name/profile name.

DLP 101-2



3


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”


DLP 101-3


DLP 101-4


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 no single-public-ip

2

The system can receive an IP address either statically by manual configuration or dynamically via BOOTP. Configure the host IP address of the system with the following command: configure system management host-ip-address bootp | manual:/


DLP 102-1


Note 1 — In case of manual configuration of the IP address: If the system IP address is not configured (default 0.0.0.0), the user’s session setup requests are refused. Note 2 — In case of dynamic configuration via BOOTP: you can view the IP address that you received from the server with the following command: show transport ip-address

3

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



show interface shub port ================================================================ port table ================================================================ port admin-status oper-status speed type duplex ---------------------------------------------------------------1 down down one-gb unused full 2

up

up

one-gb

outband

full

3

up

down

one-gb

user

full

4

up

down

one-gb

subtending

full

5

up

down

one-gb

network

full

6

up

up

hundred-mbps

network

full

7

up

up

hundred-mbps

network

half

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

4

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

Note — Set the parameter to:

• • 5

Do one of the following:

• • 6

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

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)

7

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 /


DLP 102-3


iii

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

8

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 vlan-id 4093

9

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


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



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


DLP 102-5


DLP 102-6


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 name location contact-person (no) en-snmp-auth-trap (no) ether-shape-rate mgnt-vlan-id system-mac // (no) single-public-ip (no) port-num-in-proto


DLP 103-1


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 location

3

If necessary, configure the system loop ID syntax with the following command: configure system loop-id-syntax (no) atm-based-dsl (no) efm-based-dsl

Note — For the loop ID syntax:

• •

4

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

b

Configure SNTP on the LT shelf with the following command: configure system sntp server-ip-addr (no) server-port (no) polling-rate enable (no) timezone-offset

5

Configure the system clock source and the clock source priority scheme with the following command: configure system clock-mgmt (no) priority-scheme (no) ext-source

Note — The last parameter is not available on 7330 ISAM FTTN systems.

DLP 103-2



6

Configure the error log handling with the following command: configure error (no) log-full-action

7

View information about the SNTP and its related parameters with the following command: show sntp

8


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


DLP 103-3


DLP 103-4


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.


DLP 104-1

DLP 104 — Configure network interfaces

DLP 104-2


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.


DLP 105-1


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

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 (no) link-up-down-trap (no) actor-sys-prio selection-policy actor-key (no) actor-port-prio (no) active-lacp (no) short-timeout (no) aggregatable lacp-mode

2

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



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

3

If necessary, use the following command to disable Link Aggregation: configure la disable-lacp

4

View information for a Link Aggregation Group configured on the Service Hub with the following command: show la aggregator-info (port)

5

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)

6


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]


DLP 105-3


DLP 105-4


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


DLP 106-1

DLP 106 — Configure RSTP

DLP 106-2


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.


DLP 107-1


Procedure Proceed as follows to configure OSPF management: 1

Configure the OSPF parameters and attributes with the following command: configure ospf enable router-id (no) as-border-router (no) enable-opaque-lsa (no) overflow-state-it (no) dis-rfc1583-comp (no) abr-type (no) passive-interface

2

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 (no) passive (no) itf-type (no) authentication

iii

Configure the OSPF interface timers with the following command: configure ospf area (area-id) interface (ip-addr) timers (no) transit-delay (no) retransmit-itvl (no) hello-interval (no) dead-interval (no) poll-interval

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: | encrypted: (no) accept-starts (no) generate-starts

v

Confirm the MD5 authentication with the following command: configure ospf area (area-id) interface (ip-addr) authentication md5

DLP 107-2



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

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

3

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 (no) metric (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 (no) passive (no) itf-type (no) authentication

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 (no) retransmit-itvl (no) hello-interval (no) dead-interval


DLP 107-3


(no) poll-interval

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 (no) accept-starts (no) generate-starts

v



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

vii

Configure an OSPF stub aggregate with the following command: configure ospf stub-area (area-id) aggregate-addr (dest-ip) (no) omit-advertise

4

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 (no) trans-itvl (no) asbr-rtr-trans (no) metric-type ]

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 (no) passive (no) itf-type (no) authentication

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

DLP 107-4



(no) hello-interval (no) dead-interval (no) poll-interval

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 (no) accept-starts (no) generate-starts

v



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

vii

Configure an OSPF NSSA aggregate with the following command: configure ospf nssa-area (area-id) aggregate-addr (dest-ip) lsa-type (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

5

Configure the redistribution of the OSPF with the following command: configure ospf redistribution (no) enable (no) local (no) static (no) rip

6

Configure the redistribution of the OSPF route parameters with the following command: configure ospf redistribution route-destination (dest-ip) (no) metric-type (no) metric


DLP 107-5


7

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

8


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



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


DLP 107-7


DLP 107-8


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

2

Configure RIP distribution with the following command: configure rip redistribution (no) enable (no) default-metric (no) local (no) static (no) ospf


DLP 108-1


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 default-metric (no) send (no) receive (no) split-horizon

4

Configure the RIP interface timers with the following command: configure rip interface (ip-addr) timers (no) update-timer (no) route-age-out (no) junk-collection

5

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 starts expires

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



6

An MD5 key for a RIP interface can be managed with the following command: admin rip interface (ip-addr) md5-key expires

7

Add or delete a route aggregation with the following command: configure rip (no) aggregation (ip-addr)

8

Define a route map with the following command: configure rip route-map (vlan-id) sub-index ip-addr / (no) direction (no) deny

9

View the information for RIP with the following command: show rip statistics show rip peer show rip routing-table show rip global

10


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


DLP 108-3


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

DLP 108-4


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.


DLP 109-1


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 type

2

Configure the SNMP community name with the following command: configure system security snmp community (name) host-address / (no) context (no) privilege (no) read-view (no) write-view (no) notify-view

3

DLP 109-2

Do one of the following: a

If SNMPv1 or SNMPv2 is used, continue with step 7.

b

If SNMPv3 is used, continue with step 4.



4

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

5

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

6

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

7

Configure an SNMP notification profile with the following command: configure system security snmp notify-profile (name) snmp-version v1 : | v2 : | v3 : : none | authentication | privacy-and-auth

8

Configure a filter for a notification profile with the following command: configure system security snmp notify-profile (name) filter notify-view

9

Configure an SNMP element manager with the following command: configure system security snmp manager (name) destination : notify-profile (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 (no) privilege (no) ip-addr

11

Configure the SNMP trap manager with the following command: configure trap manager : (no) priority (no) cold-start-trap (no) link-down-trap


DLP 109-3


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

12

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 window-size max-queue-size min-interval min-severity

Configure an SNMP manager of the SHub with the following command: configure trap shub manager : (no) cold-start-trap (no) auth-fail-trap (no) change-trap (no) community-string (no) snmp-version (no) min-severity

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

14

If necessary, reset the trap table with the following command: admin trap manager : reset-trap-buffer

15

DLP 109-4




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


DLP 109-5


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


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.


DLP 110-1


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 log-full-action non-itf-rep-sev-level

ii

Modify the alarm severity and actions on individual alarms with the following command: configure alarm entry (index) severity (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 warn-log-full-action minor-log-full-action major-log-full-action crit-log-full-act 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 (no) severity

v

Configure the default severity for an alarm on a type of interface with the following command: configure interface alarm (index) (no) default-severity

vi

Configure the alarm SHub parameters with the following command: configure alarm shub entry (index) severity (no) service-affecting (no) reporting

DLP 110-2



2

Configure an alarm profile for remote LT boards with the following command: configure alarm custom-profile (name) (no) mnemonic1 (no) description1 (no) visible1 (no) audible1 (no) polarity1 (no) severity1 (no) mnemonic2 (no) description2 (no) visible2 (no) audible2 (no) polarity2 (no) severity2 (no) mnemonic3 (no) description3 (no) visible3 (no) audible3 (no) polarity3 (no) severity3 (no) mnemonic4 (no) description4 (no) visible4 (no) audible4 (no) polarity4 (no) severity4 (no) mnemonic5 (no) description5 (no) visible5 (no) audible5 (no) polarity5 (no) severity5

3


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


DLP 110-3


DLP 110-4


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.


DLP 111-1


Procedure Proceed as follows to plan, replan, and unplan equipment: 1

Plan units in main subracks as follows: i

Plan a subrack with the following command: configure equipment shelf (index) class planned-type unlock (no) lock (no) extended-lt-slots (no) description

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 (no) power-down (no) unlock (no) alarm-profile capab-profile

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

2

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



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.

3

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:/ planned-type

ii

Plan the remote subrack with the following command: configure equipment shelf / planned-type

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

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 // planned-type

4

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:/ planned-type not-planned

iii

Unplan the remote subrack with the following command: configure equipment shelf / planned-type not-planned


DLP 111-3


5

View the slot status with the following command: show equipment slot

6


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



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


DLP 111-5


DLP 111-6


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

2

Unlock a plug-in unit with the following command: configure equipment slot (index) unlock

3


Configuration example: configure equipment slot 1/1/5 no unlock configure equipment slot 1/1/5 unlock


DLP 112-1

DLP 112 — Lock and unlock equipment

DLP 112-2


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

2

Configure the rack with the following command: configure equipment rack (no) description

3

Configure the subrack or shelf with the following command: configure equipment shelf (index) class (no) planned-type (no) unlock (no) extended-lt-slots (no) description

4

Enable or disable environment monitoring with the following command: configure equipment envbox (no) enable-supervise


DLP 113-1

DLP 113 — Configure the equipment

5

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

b

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

c

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

d

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

e

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

f

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

6


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


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.


DLP 114-1


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

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:

• •

2

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

3

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



4

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

v

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

5

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

6

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

7



DLP 114-3


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


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.


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

ISP

VRF DHCP Relay

ARP Proxy

P-VLAN

VB P-VLAN

LT IPoE/A Session ARP Proxy

IPoE/A Interface

DHCP Relay

VRF

P-VLAN

ISP

ARP Proxy

PPPoE/PPPoA, IPoE/IPoA always untagged

IPoE (P-VLAN)

IPoE (P-VLAN)

This procedure provides the steps to configure a 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 (no) name mode layer2-terminated (no) priority (no) broadcast-frames (no) protocol-filter (no) pppoe-relay (no) pppoe-relay-tag (no) dhcp-opt-82 (no) no circuit-id (no) circuit-id-dhcp (no) remote-id (no) remote-id-dhcp (no) dhcp-linerate (no) pppoe-linerate (no) circuit-id-pppoe (no) remote-id-pppoe (no) secure-forwarding

DLP 115-2



(no) aging-time

2

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

3

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

4

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

5

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

6

Create and configure an SHub network port: i

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

ii

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


DLP 115-3


7

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

8


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


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.


DLP 116-1


Figure DLP 116-1: Layer2-terminated Router VLAN LT PPPoE/A Session

VRF

PPPoE/A Interface

ARP Proxy

SHub V-VLAN

P-VLAN

IPoE/A Interface

ARP Proxy

DHCP Relay

ARP

VRF

ISP

VRF

LT IPoE/A Session

Routing Protocols (OSPF, RIPv2)

V-VLAN

DHCP Relay

ARP Proxy

PPPoE/PPPoA, IPoE/IPoA always untagged

IPoE (V-VLAN per VR)

IPoE (P-VLAN)

This procedure provides the steps to configure a 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



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 (no) name mode layer2-terminated (no) priority (no) broadcast-frames (no) protocol-filter (no) pppoe-relay (no) pppoe-relay-tag (no) dhcp-opt-82 (no) no circuit-id (no) circuit-id-dhcp (no) remote-id (no) remote-id-dhcp (no) dhcp-linerate (no) pppoe-linerate (no) circuit-id-pppoe (no) remote-id-pppoe (no) secure-forwarding (no) aging-time

2

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

3

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://

4

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

5

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

6

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

7

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

8

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


DLP 116-3


(no) name mode layer2-term-nwport (no) mac-move-allow

9

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:

12

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

13

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

14

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

15

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

16

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

17

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

18

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

DLP 116-4



19

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

20

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

21


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


DLP 116-5


DLP 116-6


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 (no) name mode cross-connect (no) priority (no) broadcast-frames (no) protocol-filter (no) pppoe-relay


DLP 117-1


(no) pppoe-relay-tag

ii

If required, configure the C-VLAN on the LT with the following command: configure vlan id (no) name mode (no) priority (no) vmac-translation (no) vmac-dnstr-filter (no) broadcast-frames (no) protocol-filter (no) pppoe-relay (no) pppoe-relay-tag (no) dhcp-opt-82 (no) no circuit-id (no) circuit-id-dhcp (no) remote-id (no) remote-id-dhcp (no) dhcp-linerate (no) pppoe-linerate (no) circuit-id-pppoe (no) remote-id-pppoe (no) secure-forwarding (no) aging-time

iii

Create a C-VLAN on the SHub with the following command: configure vlan shub id name mode cross-connect

2


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


iii


3

DLP 117-2




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


DLP 117-3


DLP 117-4


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 interface’s 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:

• •


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:: name mode cross-connect


DLP 118-1


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

ii

priority broadcast-frames protocol-filter pppoe-relay pppoe-relay-tag

If required, configure the S-VLAN on the LT with the following command: configure vlan id (no) name mode (no) priority (no) vmac-translation (no) vmac-dnstr-filter (no) broadcast-frames (no) protocol-filter (no) pppoe-relay (no) pppoe-relay-tag (no) dhcp-opt-82 (no) no circuit-id (no) circuit-id-dhcp (no) remote-id (no) remote-id-dhcp (no) dhcp-linerate (no) pppoe-linerate (no) circuit-id-pppoe (no) remote-id-pppoe (no) secure-forwarding (no) aging-time

iii

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

2


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


iii


DLP 118-2



3


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


DLP 118-3


DLP 118-4


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 interface‘s preconfigured S-VLAN will be assigned. In case of untagged/priority tagged frames, the subscriber interface’s pre-configured C-VLAN and S-VLAN will be assigned. 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:

• •



DLP 119-1


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:: name mode layer2-terminated (no) priority (no) broadcast-frames (no) protocol-filter (no) pppoe-relay (no) pppoe-relay-tag

ii

If required, configure the S-VLAN on the LT with the following command: configure vlan id stacked:: (no) priority (no) vmac-translation (no) vmac-dnstr-filter (no) broadcast-frames (no) protocol-filter (no) pppoe-relay (no) pppoe-relay-tag (no) dhcp-opt-82 (no) no circuit-id (no) circuit-id-dhcp (no) remote-id (no) remote-id-dhcp (no) dhcp-linerate (no) pppoe-linerate (no) circuit-id-pppoe (no) remote-id-pppoe (no) secure-forwarding (no) aging-time

iii

Create a stacked SC-VLAN on the LT with the following command: configure vlan id stacked:: name mode cross-connect (no) priority (no) broadcast-frames (no) protocol-filter

iv

Create an cross-connect VLAN on the SHub with the following command: configure vlan shub id name mode cross-connect

DLP 119-2



2


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


iii


3


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


DLP 119-3


DLP 119-4


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 (no) name mode residential-bridge (no) priority (no) broadcast-frames (no) protocol-filter (no) pppoe-relay (no) pppoe-relay-tag


DLP 120-1

DLP 120 — Create an iBridge VLAN

2

If required, configure the iBridge VLAN with the following command: configure vlan id (no) priority (no) broadcast-frames (no) protocol-filter (no) pppoe-relay (no) pppoe-relay-tag (no) dhcp-opt-82 (no) no circuit-id (no) circuit-id-dhcp (no) remote-id (no) remote-id-dhcp (no) dhcp-linerate (no) pppoe-linerate (no) circuit-id-pppoe (no) remote-id-pppoe (no) secure-forwarding (no) aging-time

3

Create an iBridge VLAN on the SHub with the following command: configure vlan shub id name mode residential-bridge

4


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


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

2

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

3

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


DLP 121-1

DLP 121 — Add network interfaces to a VLAN

4

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

5

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

6


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


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 (no) desc (no) contact (no) my-ipaddress (no) default-ttl (no) reassem-timeout mode forwarder

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


DLP 122-1

DLP 122 — Create a forwarding VRF

2


Configuration example: configure ip vrf 16 name forwardingvrf16 mode forwarder

DLP 122-2


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 (no) desc (no) contact (no) my-ipaddress (no) default-ttl (no) reassem-timeout mode router


DLP 123-1

DLP 123 — Create a router VRF

2

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

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

3


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


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.


DLP 124-1


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 | | name: spectrum-profile none | | name: (no) dpbo-profile (no) ansi-t1413 (no) etsi-dts (no) g992-1-a (no) g992-1-b (no) g992-2-a (no) g992-3-a (no) g992-3-b (no) g992-3-l1 (no) g992-3-l2 (no) g992-3-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 (no) admin-up bonding-mode (no) transfer-mode

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

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

DLP 124-2



3

4


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

b

For a user on a VDSL or VDSL 2 line, continue with step 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

5

For each of the created PVCs, create a bridge port with the following command: configure bridge port (port) (no) default-priority (no) accept-frame-type (no) qos-profile (no) prio-regen-prof

6

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 (no) network-vlan (no) vlan-scope (no) qos (no) qos-profile (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

7

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::4097


DLP 124-3


8


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


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 | | name: spectrum-profile none | | name: (no) dpbo-profile (no) ansi-t1413 (no) etsi-dts (no) g992-1-a (no) g992-1-b (no) g992-2-a (no) g992-3-a (no) g992-3-b (no) g992-3-l1 (no) g992-3-l2 (no) g992-3-am


DLP 125-1


(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 (no) admin-up bonding-mode (no) transfer-mode

2

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

3

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

4

5


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

b

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

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

6

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

7

DLP 125-2

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



8

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

Note — This command must be repeated for each IP address assigned to that particular user.

9


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


DLP 125-3


DLP 125-4


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:

• • •


Procedure Proceed as follows to create an IPoE user: 1

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


DLP 126-1


(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 (no) admin-up bonding-mode (no) transfer-mode


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

3

4



b


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

5

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

6

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

7

DLP 126-2

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



8

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

9


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


DLP 126-3


DLP 126-4


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 | | name: spectrum-profile none | | name: (no) dpbo-profile (no) ansi-t1413 (no) etsi-dts (no) g992-1-a (no) g992-1-b (no) g992-2-a (no) g992-3-a (no) g992-3-b


DLP 127-1


(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 (no) admin-up bonding-mode (no) transfer-mode


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

3

4



b


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

5

Create a bridge port with the following command: configure bridge port (port) max-unicast-mac

6

Create a user PPPoX interface with the following command: configure pppoe pppox-interface (port) (no) max-num-session (no) ppp-profile-name

7

DLP 127-2




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


DLP 127-3


DLP 127-4


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://

2


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


DLP 128-1

DLP 128 — Add an LT port to a VLAN

DLP 128-2


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

Description

Service Profile

Groups a number of parameters related to the xDSL service

Spectrum Profile

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:

• • • •

2

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.


DLP 129-1


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 (scope) version (no) ra-mode-down (no) ra-mode-up (no) min-bitrate-down (no) min-bitrate-up (no) plan-bitrate-down (no) plan-bitrate-up (no) max-bitrate-down (no) max-bitrate-up (no) max-delay-down (no) max-delay-up (no) imp-noise-prot-dn (no) imp-noise-prot-up (no) inp-wo-erasure-dn (no) inp-wo-erasure-up (no) min-l2-br-down

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

2

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



3

Create an xDSL spectrum profile and configure the parameters common to all the DSL flavors with the following command: configure xdsl spectrum-profile (index) name local-profile version (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 (no) min-noise-up (no) trgt-noise-down (no) trgt-noise-up (no) max-noise-down (no) max-noise-up (no) carrier-mask-down (no) carrier-mask-up (no) rf-band-list (no) power_mgnt_mode (no) l0-time (no) l2-time (no) l2-agpow-red-tx (no) modification (no) rau-noise-down (no) rau-noise-up (no) rau-time-down (no) rau-time-up (no) rad-noise-down (no) rad-noise-up (no) rad-time-down (no) rad-time-up (no) l2-agpw-to-red-tx


DLP 129-3


4

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

5

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 (no) max-agpowlev-up (no) max-psd-down (no) max-psd-up (no) pbo-mode-up (no) max-recv-power-up

6

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 (no) max-agpowlev-up (no) max-psd-down (no) max-psd-up (no) pbo-mode-up (no) max-recv-power-up (no) psd-shape-down

7

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 (no) max-agpowlev-up (no) max-psd-down (no) max-psd-up (no) pbo-mode-up (no) max-recv-power-up

DLP 129-4



8

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 (no) optional-band (no) optional-endfreq (no) adsl-band (no) max-agpowlev-down (no) max-agpowlev-up (no) psd-shape-down (no) psd-shape-up (no) pbo-mode-down (no) rx-psd-shape-up (no) ghstones-pwr-mode (no) max-band (no) max-freq (no) m-psd-level-down (no) m-psd-level-up (no) psd-pbo-par-a-up (no) psd-pbo-par-b-up (no) cust-psd-sc-down (no) cust-psd-ty-down (no) cust-rx-psd-sc-up (no) cust-rx-psd-ty-up

9

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: (no) b43 standard | auto | manual: (no) a43c standard | auto | manual: (no) v43 standard | auto | manual:

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 (no) max-agpowlev-up (no) psd-shape-down cs-psd-shape-dn cs-psd-shape-up (no) psd-shape-up (no) rx-psd-shape-up (no) psd-pbo-e-len-up (no) m-psd-level-down (no) m-psd-level-up (no) psd-pbo-par-a-up (no) psd-pbo-par-b-up (no) v-noise-snr-down (no) v-noise-snr-up (no) v-noise-psd-down (no) v-noise-psd-up


DLP 129-5


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

11

cust-psd-sc-down cust-psd-ty-down cust-psd-sc-up cust-psd-ty-up cust-rx-psd-sc-up cust-rx-psd-ty-up

Activate an xDSL spectrum profile with the following command: configure xdsl spectrum-profile (index) active

12


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


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)


DLP 130-1


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

b

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

•

2

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 local-profile | network-profile version (no) min-bitrate-up (no) min-bitrate-down (no) plan-bitrate-up (no) plan-bitrate-down (no) max-bitrate-up (no) max-bitrate-down (no) max-delay-down (no) max-delay-up (no) imp-noise-prot-dn (no) imp-noise-prot-up (no) active

DLP 130-2



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 | | name: (no) admin-up

4

5


In case of odd-even adjacent line bonding; go to step 7.

b

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)

6

Activate the xDSL bonding group with the following command: configure xdsl-bonding group (if-index) admin-up

7

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

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

8


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


DLP 130-3


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


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.


DLP 131-1

DLP 131 — Create an xDSL bonding group

DLP 131-2


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

Create filters on the SHub that let certain streams with specific MAC addresses pass through

2

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.


DLP 132-1


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.

2

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 (no) protocol-type filter vlan-id (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 action-drop

3

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

4

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

DLP 132-2



5

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

6

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

7

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

8

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

9

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

10

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



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 (no) action-drop (no) dst-ip-addr / (no) src-ip-addr / (no) direction (no) vlan-id

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 (no) protocol (no) action-drop (no) dst-ip-addr (no) src-ip-addr (no) vlan-id

Note — The IP filter takes into account source and/or destination IP addresses; either or both must be specified. The physical ports where the filters have to be applied are configured subsequently, by means of dedicated configuration commands. 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 (no) protocol (no) action-drop (no) dst-ip-addr (no) src-ip-addr (no) vlan-id

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

DLP 132-4




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


DLP 132-5


DLP 132-6


DLP 133 — Configure QoS on layer 2 Note This procedure is no longer valid. Refer to DLP 134 for the configuration procedure.


DLP 133-1

DLP 133 — Configure QoS on layer 2

DLP 133-2


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 (no) eth-efm-fact (no) enable-alignment (no) cac-mode

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

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


DLP 134-1


2

Configure the QoS policer profiles with the following command: configure qos profiles policer (name) committed-info-rate committed-burst-size

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

ii

Configure a marker for single DSCP with the following command: configure qos profiles marker dscp (name) default-dscp (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

v

Configure a marker for Dot1P and the DSCP contract table with the following command: configure qos profiles marker d1p-dscp-contract (name) dot1p-value (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

vii

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

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

DLP 134-2



4

Configure a scheduler profile with the following command: configure qos profiles scheduler (name) wfq-q1-weight

5

Configure a CAC profile with the following command: configure qos profiles cac (name) res-voice-bandwidth max-mcast-bandwidth res-data-bandwidth

6

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: | red:::

7

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 (no) src-mac-addr (no) ethertype (no) dot1p-priority (no) canonical-format (no) vlan-id

b

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 (no) src-ip-addr (no) min-dst-port (no) max-dst-port (no) min-src-port (no) max-src-port (no) dscp-value (no) protocol

8

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 (no) dot1p-value (no) discard-packet (no) shared-policer (no) policer-profile

9

Configure QoS policy profiles with a set of associated actions.


DLP 134-3


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 (no) precedence (no) policy-action

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 (no) up-policer none | name: (no) down-policer none | name: (no) up-marker none | 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 (no) qos-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 cac-profile

b

an SHDSL interface with the following command: configure qos shdsl-port (index) scheduler-profile cac-profile

c

an Ethernet link with the following command: configure qos interface eth-itf (index) scheduler-profile cac-profile

DLP 134-4



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

b

an SHDSL interface with the following command: configure qos shdsl-port (index) queue (queue) queue-profile

c

an Ethernet link with the following command: configure qos interface eth-itf (index) queue (queue) queue-profile

14


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


DLP 134-5


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

DLP 134-6


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


DLP 135-1


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 name mode qos-aware (no) priority

ii

Create a C-VLAN on the SHub with the following command: configure vlan shub id name mode cross-connect

2


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:

iv


DLP 135-2

3

Create an xDSL user; see DLP 124.

4




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


DLP 135-3


DLP 135-4


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 (no) fast-change (no) pkg-memb-bitmap (no) max-bitrate (no) mean-bit-rate

Note 1 — The minimum bitrate available for multicast is configured with the command configure xdsl service-profile; see DLP 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 (no) max-num-uncfg (no) cfg-res-time (no) uncfg-res-time


DLP 136-1

DLP 136 — Configure multicast on the LT

3

Configure the multicast source with the following command: configure mcast src (class-d-addr) (no) dis-fast-change (no) pkg-mem-bitmap (no) name (no) guaranteed-serv (no) atm-peak-bit-rate (no) eth-peak-bit-rate (no) atm-sus-bit-rate (no) eth-sus-bit-rate vlan-id (no) service-name (no) preview-duration (no) preview-number (no) preview-blackout

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)

5


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


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 (no) max-num-group cac-disable | cac ip-anti-spoof-dis | ip-anti-spoof (no) igmp-version

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

2

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

3

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


DLP 137-1


4

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 (no) template-name template-version

5

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

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

6

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

DLP 137-2



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 (no) attempt-max-pview (no) attempt-blackout (no) attempt-no-perm

8


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


DLP 137-3


DLP 137-4


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 trace-selection (no) router-purge-intv (no) host-purge-intv (no) max-mcast-learn (no) glb-leave (no) reduced-resp-int (no) remove-root-int

2

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

3

Configure the router port with the following command: configure igmp shub vlan-router-port (vlan-id) network-port

4

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


DLP 138-1


5

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

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

6

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

7

DLP 138-2




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


DLP 138-3


DLP 138-4


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.


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 slow-path-mode

2

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

3

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

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

ii

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

iii

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

iv

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

4

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

5

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

DLP 139-2



6

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 (no) hops-threshold (no) context-lifetime (no) agent-ip-addr

7


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


DLP 139-3


DLP 139-4


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.


DLP 140-1

DLP 140 — Configure DHCP relay agent in router mode


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

2


3

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

4

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 (no) hops-threshold (no) context-lifetime agent-ip-addr

5


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


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.


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


DLP 141-1

DLP 141 — Configure DHCP relay agent in forwarder mode

2

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

3

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

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

ii

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

iii

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

iv

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

4


5

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

6

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 (no) hops-threshold (no) context-lifetime agent-ip-addr

7

DLP 141-2




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


DLP 141-3


DLP 141-4


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 (no) vlan-id (no) primary-dns (no) second-dns (no) primary-nbns (no) second-nbns (no) sess-timeout (no) qos-policy none | name: authenticator local | radius: (no) admin-down

2

Define the security domain IP pool with the following command: configure system security ip-addr-pool (name) vrf-index start-addr / (no) size (no) admin-down


DLP 142-1

DLP 142 — Configure the security domain

3

Assign the security domain IP pool with the following command: configure system security domain (name) ip-pool (name) vrf-index priority

4


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


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.


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 authenticator local

2

Define the domain users with the following command: configure system security domain (name) user (name) password

3

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

4

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

5


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


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 ip-address (no) port secret (no) retry-limit (no) timeout-limit (no) admin-down (no) dead-interval

2

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


DLP 144-1

DLP 144 — Configure RADIUS

3

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

4

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

5

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

6

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

7

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

8

DLP 144-2




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


DLP 144-3


DLP 144-4


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

2

Configure the 802.1x parameters with the following command: configure system security pae authenticator (port) (no) controlled-port (no) quiet-period (no) tx-period (no) supp-timeout (no) server-timeout (no) max-req

3

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

4

Enable initialization control for a port with the following command: configure system security pae port (port) (no) initialize


DLP 145-1

DLP 145 — Configure 802.1x

5


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


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


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:

•


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 (no) pppoe-linerate (no) circuit-id-pppoe (no) remote-id-pppoe

2

Disable PPPoE relay with the following command: configure vlan id (vlanid) no pppoe-relay-tag

3


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


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 (no) pads-timeout (no) max-pad-attempts (no) trans-max-age (no) cc-max-age

2

Configure the PPPoX CC engine with the following command: configure pppox-relay cross-connect engine (vlan-id) (no) max-payload-tag (no) name (no) lock (no) service-name

3

Enable monitoring of the PPPoX CC engine with the following command: configure pppox-relay cross-connect engine (vlan-id) monitor


DLP 147-1

DLP 147 — Configure PPPoX relay

4

Configure PPPoX CC client port with the following command: configure pppox-relay cross-connect client-port (port) vlan-id | stacked:: default-priority (no) max-cc (no) qos-profile none | name:

5

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

6


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


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 enable-server

2


Configuration example: configure pppoe server-name PPPoEServer1 enable-server


DLP 148-1

DLP 148 — Enable the PPPoE server

DLP 148-2


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 (no) keep-alive-intvl

2


Configuration example: configure pppoe ppp-profile PPPProf1 auth-type chap-pap


DLP 149-1

DLP 149 — Configure PPPoE profiles

DLP 149-2


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:

•


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 (no) cache-pending (no) cache-refresh (no) cache-retry-time (no) max-retry-itvl (no) max-retries

2

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

3



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


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.


DLP 151-1


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



Procedure Proceed as follows to restart the NT: 1

Prepare the system for shutdown with the following command: admin equipment prepare-sys-shutdown

2

Pull out the NT board.

3

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

4

Insert the new NT board in the NE.

5

Observe that the NT is loaded properly.

6

Verify that the previously activated features are working again.

7

Send the old NT board back to Alcatel-Lucent.

8


Configuration example: admin equipment prepare-sys-shutdown


DLP 151-3


DLP 151-4


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

2


Configuration example: admin equipment reboot-isam with-self-test


DLP 152-1

DLP 152 — Reboot the system

DLP 152-2


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 // power-down

2

Restore power to a plug-in unit with the following command: configure equipment slot // no power-down


DLP 153-1

DLP 153 — Shut down and restart individual equipment

3


Configuration example: configure equipment slot 1/1/5 power-down configure equipment slot 1/1/5 no power-down

DLP 153-2


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


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: | start:warning: | start:minor: | start:major: | start:critical: | start::

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

2

The alarm snapshot table can be viewed with the following command: show alarm snap-shot table | equipment | eqpt-holder | 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:

• • 3

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: | start:warning: | start:minor: | start:major: | start:critical: | start::

4

The SHub alarm snapshot table can be viewed with the following command: show alarm shub snap-shot table (index)

DLP 154-2



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

• • 5

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

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

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

6

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

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

7


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


DLP 154-3


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


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)


DLP 155-1


2

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

3

Use the following commands to view the current alarms: i

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

4

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

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

b

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

c

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

d

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

e

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

DLP 155-2



f

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

5


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


DLP 155-3


DLP 155-4


DLP 156 — Management of the SHub database Note This procedure is no longer valid. The correct procedure is described in RTP 100.


DLP 156-1

DLP 156 — Management of the SHub database

DLP 156-2


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

2

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

3


Configuration example: show software-mngt shub config-file show system shub entry status


DLP 157-1

DLP 157 — Manage the SHub database

DLP 157-2


DLP 158 — Manage the system database Note This procedure is no longer valid. The correct procedure is described in RTP 100.


DLP 158-1

DLP 158 — Manage the system database

DLP 158-2


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 second-file-server-id download-set autofetch activate manually | after-download

Note — The parameters “download-set” and “autofetch” are obsolete parameters whose settings will be ignored by the system.

2

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


DLP 159-1

DLP 159 — Manage OSWP

3

Start the actual OSWP download with the following command: admin software-mngt oswp (index) download

4

Abort an OSWP download with the following command: admin software-mngt oswp (index) abort-download

5

Activate an OSWP with the following command: admin software-mngt oswp (index) activate manually | after-download

6

Commit an OSWP with the following command: admin software-mngt oswp (index) commit

7


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


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

2


Configuration example: show system shub entry version


DLP 160-1

DLP 160 — View version of the SHub software

DLP 160-2


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)


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

2


Configuration example: show system license

DLP 161-2


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

2

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


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.

3

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

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

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

5

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:

ii

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

6


7


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


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

2

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


DLP 163-1


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

3

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 min-noise-up trgt-noise-down trgt-noise-up max-noise-down max-noise-up carrier-mask-down carrier-mask-up rf-band-list power_mgnt_mode l0-time l2-time l2-agpow-red-tx rau-noise-down rau-noise-up rau-time-down rau-time-up rad-noise-down rad-noise-up rad-time-down rad-time-up l2-agpw-to-red-tx

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

b

When the modifications must be cancelled: configure xdsl spectrum-profile (index) modification cancel

DLP 163-2



4


Configuration example: configure xdsl spectrum-profile 22 modification start configure xdsl spectrum-profile 22 name test_profile configure xdsl spectrum-profile 22 modification complete


DLP 163-3


DLP 163-4


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)

2

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

3

(ip-addr) timeout tries mtu-size

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


Configuration example: ping 10.176.5.5 tries 3 ping 192.168.116.1 vrf 15 tries 3


DLP 164-1

DLP 164 — Ping another host

DLP 164-2


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 last-hop (no) timeout (no) mtu-size

ii

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


DLP 165-1

DLP 165 — Perform a traceroute action

2

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

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

ii

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

3


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


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


Configure the CPE remote management function with the following command: configure cpe-management proxy-mode snmp

2

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

3

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


DLP 166-1

DLP 166 — Configure SNMP proxy CPE management

4

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

5

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

6


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


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


DLP 167-1


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

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 flat | tee | discard info configure flat | tee append | discard

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

2

You can do one of the following: a

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

DLP 167-2



b

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

c

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

3


Configuration example: info configure | tee config info configure alarm flat | tee alaflat.cli exec /var/cmd/alaflat.cli


DLP 167-3


DLP 167-4


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

2

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

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

b

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

3

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

4


If the system is a single IP address system; go to step 12

b

If the system is a dual IP address system; go to step 5.


DLP 168-1

DLP 168 — Modify the system management IP parameters

5

Change the administrative status of the management vlan on the SHub to “down” with the following command: configure interface shub vlan-id admin-status down

6

Optionally, remove the IP address connected to the management vlan on the SHub via the following command: configure interface shub ip no ip-addr /

7

Configure the new IP address to the management vlan on the SHub via the following command: configure interface shub ip ip-addr /

8

Change the administrative status of the management vlan on the SHub to “up” with the following command: configure interface shub vlan-id admin-status up

9


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


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



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


DLP 168-3


DLP 168-4


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


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 node’s MAC address. With the information received in the topology response messages, the command and backup nodes are able to construct tables giving the complete topology of a cluster (including the MAC and IP address of each node).

This procedure provides the steps to configure cluster management.

Procedure Proceed as follows to configure cluster management: 1

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

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

2

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

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

3

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

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

DLP 169-2



4

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.

5

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

6


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


DLP 169-3


DLP 169-4


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.


DLP 170-1


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

2

3


If public key authentication is used, go to step 3

b

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

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 server’s public key can be regenerated with the following command: configure system security ssh key-regen

4

Configure the access channels (for example, disable the non-secure channels) with the following command: configure system security ssh access (no) ftp (no) protocol (no) cli (no) tl1

DLP 170-2



Note — The parameter ftp is obsolete and is replaced by the parameter protocol.

5

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:

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


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


DLP 170-3


DLP 170-4


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

2

3

Determine the task to perform and go to the appropriate step a

To enable the management of EMS in single IP address mode, go to step 2.

b

To enable the management of EMS in dual IP address mode, go to step 7.


To enable EMS management via SNMPv3, go to step 3

b

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: | [md5|sha1]:encrypted: (no) privacy none | des:prompt |


DLP 171-1


des:plain: | des : encrypted : (no) public

b

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

c

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

4

Go to step 10.

5

Enable EMS management via SNMPv1 as follows: a

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

b

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

6

Go to step 10.

7

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

8

Configure the SHub management VLAN filter IP address with the following command: configure system shub filter shub-manager (index) src-ip-addr where is the IP address of the EMS

9

Configure the SHub security SNMP community with the following command: configure system security snmp shub community (index) name privilege read-write no ip-addr

10

DLP 171-2




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


DLP 171-3


DLP 171-4


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 (no) password-timeout (no) terminal-timeout (no) slot-numbering (no) description (no) aaa (no) atm (no) alarm (no) dhcp (no) equipment (no) igmp (no) ip (no) ppoe (no) qos (no) software-mngt (no) transport (no) vlan (no) xdsl (no) security


DLP 172-1

DLP 172 — Create a default operator profile

2


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


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

At the creation of the service and spectrum profiles, fill in the correct values both for the ADSL and VDSL profiles; see DLP 129.

2

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 | | name: spectrum-profile none | | name: (no) dpbo-profile transfer-mode ptm admin-up

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

3

Create the new forwarding model. Refer to DLP 115 to DLP 127 for the correct procedure for the different modes.


DLP 173-1

DLP 173 — Switching a user from ADSL to VDSL

4


Configuration example: configure xdsl line 1/1/4/1 service-profile 7 spectrum-profile 5 transfer-mode ptm admin-up

DLP 173-2


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 mode cross-connect

2

Create a cross-connect VLAN on the SHub with the following command: configure vlan shub id (vlanid) name mode cross-connect


DLP 174-1


3

Create an xDSL line with the following command: configure xdsl line (if-index) service-profile none | | name: spectrum-profile none | | name: (no) dpbo-profile (no) ansi-t1413 (no) etsi-dts (no) g992-1-a (no) g992-1-b (no) g992-2-a (no) g992-3-a (no) g992-3-b (no) g992-3-l1 (no) g992-3-l2 (no) g992-3-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 (no) admin-up bonding-mode (no) transfer-mode

4

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

5

Create an ATM PVC with the following command: configure atm pvc (port-index) admin-up aal5-encap-type llc-snap-routed

6

Create an IWL with the following command: configure atm ip-cross-connect (interworking-port) cpe next-hop

DLP 174-2



7

Create a bridge port with the following command: configure bridge port (port) mac-learn-off

8

Assign a VLAN to the bridge port with the following command: configure bridge port (port) vlan-id (index)

9

Set the PVID with the following command: configure bridge port (port) pvid (vlan-id)

10


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


DLP 174-3


DLP 174-4


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 single-public-ip

2

The system can receive an IP address either statically by manual configuration or dynamically via BOOTP. Configure the host IP address of the system with the following command: configure system management host-ip-address bootp | manual:/


DLP 175-1


Note 1 — In case of manual configuration of the IP address: If the system IP address is not configured (default 0.0.0.0), the user’s session setup requests are refused. Note 2 — In case of dynamic configuration via BOOTP: you can view the IP address that you received from the server with the following command: show transport ip-address

3

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

4

Configure the network port management (inband or outband) with the following command: configure interface shub port (network-port) (no) mode automatic | 10mbps:full | 10mbps:half | 100mbps:full | 100mbps:half | 1gbps:full | 1gbps:half (no) port-type (no) admin-status (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



show interface shub port ================================================================ port table ================================================================ port admin-status oper-status speed type duplex ---------------------------------------------------------------1 down down one-gb unused full 2

up

up

one-gb

outband

full

3

up

down

one-gb

user

full

4

up

down

one-gb

subtending

full

5

up

down

one-gb

network

full

6

up

up

hundred-mbps

network

full

7

up

up

hundred-mbps

network

half

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

5

Specify the set of ports which are statically allocated as egress ports for the SHub management VLAN with the following command: configure vlan shub id 4093 egress-port (port)

6

Specify the egress ports which should transmit packets for the SHub management VLAN as untagged with the following command: configure vlan shub id 4093 untag-port (network-port)

7

Configure the bridge port with the following command: configure bridge shub port (network-port) pvid 4093

8



DLP 175-3


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


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


DLP 176-1


Note — The previous-1day counters are not available until 96 15-min intervals (that is, 24 hours) have passed.

2

Use the following commands to show the ATM counters: show atm tc-current-int one-day (port) show atm tc-current-int fifteen-min (port)

3

Use the following command to show the bridge port counters: show interface port bridge-port (port) detail

4

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

5

Use the following command to show the MSTP counters: show mstp bridge show mstp instance show mstp network-port show mstp port-instance

6

Use the following command to show the SHub port statistics: show bridge network-port (port)

7

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



8

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)

9

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 ]

12

Use the following command to show the IP SHub ARP Statistics per VRF forwarding statistics: show ip shub arp-stats (vrf-id)


DLP 176-3


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

b

For user ports configured for Tagged frames, view the ARP counters with the following command: show ip arp-proxy-stats (port-interface) vlan (subscr-vlan)

Note — By default, only ARP summary error counters are shown for each of the user ports. If detailed counters are required for monitoring or trouble shooting purposes, they need to be explicitly enabled by the operator for the particular user port, see TNG 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

b

For user ports configured for Tagged frames, view the DHCP counters with the following command: show dhcp-relay port-stats (port-interface) vlan (subscr-vlan)

Note — By default, only DHCP summary error counters are shown for each of the user ports. If detailed counters are required for monitoring or trouble shooting purposes, they need to be explicitly enabled by the operator for the particular user port, see TNG 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



show security radius acc-server acc-stats (name) vrf-index

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

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 show ima group counters far-end current-interval (if-index) show ima group counters far-end previous-interval (if-index) interval-no show ima link state (if-index) show ima link counters near-end current-interval (if-index) show ima link counters near-end previous-interval (if-index) interval-no show ima link counters far-end current-interval (if-index) show ima link counters far-end previous-interval (if-index) interval-no

23

Use the following commands to show the SHDSL information: show shdsl inventory (if-index) unit-id show shdsl span-status (if-index) show shdsl unit-status (if-index) unit-id show shdsl segment-status (if-index) unit-id side wire-pair show shdsl segment-counters current-interval (if-index) unit-id


DLP 176-5


side wire-pair show shdsl segment-counters current-1day (if-index) unit-id side wire-pair show shdsl segment-counters previous-interval (if-index) unit-id side wire-pair int-no show shdsl segment-counters previous-1day (if-index) unit-id side wire-pair int-no show shdsl span-counters current-15min (if-index) show shdsl span-counters current-1day (if-index) show shdsl span-counters previous-15min (if-index) interval-number show shdsl span-counters previous-1day (if-index) interval-number

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 show vlan port-prev-day-stats (port) interval-number show vlan current-15min-stats (vlanid)

DLP 176-6



port ] show vlan current-day-stats (vlanid) port show vlan previous-15min-stats (vlanid) port interval-number show vlan vlan-day-stats (vlanid) port interval-number

27


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


DLP 176-7


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



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


DLP 176-9


DLP 176-10


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


DLP 177-1


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



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


• • 2

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

3

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

4

View the traffic direction of the configurable ports with the following command: info configure equipment external-link-host (SFP index 6 or 7)

5

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

6

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

Go to step 14.

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


DLP 177-3


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

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

b

in a non-redundant system: admin equipment slot nt-a reboot

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:

• • •

14

DLP 177-4

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.




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


DLP 177-5


DLP 177-6


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 (no) vlan-id (no) primary-dns (no) second-dns (no) primary-nbns (no) second-nbns (no) sess-timeout (no) qos-policy authenticator


DLP 178-1

DLP 178 — Configure the default security domain

2

Configure the connection profile parameters with the following command: configure system security conn-profile (name) version (no) reject-no-domain (no) reject-inv-domain domain-name

3

Configure the security connection policy with the following command: configure system security conn-policy conn-profile-name

4


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


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.


DLP 179-1


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

Description

Parameter

Message type

Authentication actions

authentication

CLI configuration changes

cli-config-chgs

TL1 configuration changes

tl1-config-chgs

CLI messages

cli-msgs

TL1 messages

tl1-msgs

Protocol tracing messages

tracing1 tracing2 tracing3

Video CDR messages

video-cdr

All message types

all

(1 of 2)

DLP 179-2



Item

Description

Parameter

Log severity

Emergency

EM

Alert

AL

Critical

CR

Error

ER

Warning

WN

Notice

NO

Information

IN

Debug

DBG

(2 of 2)

When activating or deactivating system logs, you must specify the following information:

• • •

index number of the system log file (1 to 64) message type, or types if grouped, being sent to that system log file severity level set for that particular system log file

The index number is an integer from 1 to 64. Use the information command to view the settings of a system log file before entering the message type and log severity of the system log file to activate or deactivate. To monitor remote system logs dynamically, set the destination server type to all active CLI or all active TL1 terminals for a particular system log. This sends all messages to the active terminals that have a management session with the NE. When you are done monitoring, deactivate system logging for that server. You can view the static contents of a system log file that is saved to a remote server location using any text-based editor. You can also configure system and security logging using TL1 or SNMP. See the 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.

2

Create the system log and set the system log filename and configure the destination server type with the following command: configure system syslog destination (name) type no disable


DLP 179-3


3

Delete a system log server with the following command: configure system syslog destination (name) disable

4

Configure which messages must be sent to a given system log destination and assign the appropriate system log parameters to them with the following command: configure system syslog route (name) msg-type facility (no) emergency (no) alert (no) critical (no) error (no) warning (no) notice (no) information (no) debug

5

Configure the system transaction parameters with the following command: configure system transaction (no) time-out-value (no) log-full-action

6

Retrieve the configuration of a specific system log with the following command: info configure system syslog destination (name) type detail

7

Retrieve the configuration for all configured system logs with the following command: info configure system syslog destination detail

8

Force the system log file to rotate with this command: admin system syslog destination (name) rotate

9


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


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 | : forward-port // /::


DLP 180-1

DLP 180 — Configure static MAC addresses

2

Configure a static MAC address on the SHub with the following command: configure vlan shub unicast-mac (unicast-mac) vlan-id forward-port lt:// | network: | nt

3


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


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 (no) port secret (no) retry-limit (no) timeout-limit (no) admin-down (no) dead-interval where vrf-index is the index of the management VRF, that is 0.


DLP 181-1

DLP 181 — Configure operator authentication via RADIUS

2

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

3

Configure the RADIUS server set with the following command: configure system security radius policy (name) servers (index) auth-server none | name: vrf-index-auth (no) acc-server none | name: (no) vrf-index-acc priority where vrf-index-auth is the index of the management VRF, that is 0.

4

Enable the operator policy with the following command: configure system security radius (no) relay (no) auth-super-user oper-policy-name

5

Enable the RADIUS for the superuser with the following command: configure system security radius (no) relay auth-super-user

6


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


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.


Manage the SHDSL span profile with the following command: configure shdsl span (if-index) (no) active (admin-up | admin-down) (no) repeaters (no) op-mode (no) spectral-profile (no) wire-mode (no) mgmt-by-stu-r (no) regi-set (no) min-line-rate (no) max-line-rate (no) margin-down-worst (no) margin-down-curr (no) margin-up-worst (no) margin-up-curr (no) probe (no) tc-pam-sele


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.

2

Manage the SHDSL unit profile in one SHDSL span with the following command: configure shdsl unit (if-index) unit-id (no) loop-attenuation (no) snr-margin (no) loopback-timeout

3

Configure the SHDSL segment points on either side of an SHDSL unit with the following command: configure shdsl segment (if-index) unit-id side (no) loopback pbo-mode

4

Manage an SHDSL segment points with the following command: admin shdsl-seg (if-index) unit-id side (no) soft-restart

5

Activate the SHDSL line with one of the following commands: configure shdsl span (if-index) admin-up

6

DLP 182-2




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


DLP 182-3


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


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.


Manage the IMA group profile with the following command: configure ima group (if-index) (no) activate (admin-up | admin-down) (no) min-tx-links (no) min-rx-links near-end-ima-id

2

Manage the IMA link profile with the following command: configure ima link (link-if-index) grp-index


DLP 183-1

DLP 183 — Configure IMA on SHDSL links

3

Activate the IMA line interface with one of the following commands: configure ima group (if-index) admin-up configure interface port ima-line:/// admin-up

4


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


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


DLP 184-1


Procedure Proceed as follows to convert the IP address mode on the NE: 1

Establish a CLI session; see DLP 100.

2

Determine the task to perform and go to the appropriate step.

3

a

To convert the NE from dual to single IP address mode, go to step 3.

b

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

Go to step 10.

5

Remove the single IP address mode configuration with the following command: configure system no single-public-ip

6

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 /

iii

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

7


8

Configure the SHub filter (access list) with the following command: configure system shub filter shub-manager src-ip-addr where is the IP address of the EMS

DLP 184-2



9

Configure the SNMP SHub community string with the following command: configure system security snmp shub community name privilege read-write no ip-addr

Note — The name of the SNMP community can be 1 to 32 characters.

10


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


DLP 184-3


DLP 184-4


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.


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 (no) gsmp-version (no) gsmp-sub-version (no) encap-type (no) topo-discovery (no) layer2-oam (no) alive-timer (no) port-reprt-shaper (no) aggr-reprt-shaper (no) tcp-retry-time (no) gsmp-retry-time (no) dslam-name (no) window-size (no) tcp-port (no) vrf-id

2

Stop the ANCP session with the following command: configure l2cp no session (index)

3


Configuration example: configure l2cp session 1 bras-ip-address 192.168.200.100 configure l2cp no session 1

DLP 185-2


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


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 option-82 circuit-id remote-id (no) dhcp-linerate

2

Enable DHCP MAC concentration with the following command: configure dhcp-relay agent (vrfid) client-hw-address copysourcemac

3


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


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

2


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


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.


DLP 188-1


Procedure Proceed as follows to configure custom PSD points: 1

For the configuration of:

• • • • • • 2

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 version

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 psd

iv 3

Go to step 8

Configure the custom downstream PSD points for VDSL as follows: i


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



iv

Configure the downstream PSD values with the following command: configure xdsl spectrum-profile (index) vdsl cust-psd-pt-down (psdpt) frequency psd

v 4

Go to step 8

Configure the custom upstream PSD points for VDSL as follows: i


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 psd

v 5

Go to step 8

Configure the custom downstream PSD points for VDSL2 as follows: i


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


DLP 188-3


iv

Configure the downstream PSD values with the following command: configure xdsl spectrum-profile (index) vdsl2 cust-psd-pt-down (psdpt) frequency psd

v 6

Go to step 8

Configure the upstream Rx PSD points for VDSL2 as follows: i


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 psd

v 7

Go to step 8

Configure the upstream PSD points for VDSL2 as follows: i


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



iv

Configure the upstream PSD values with the following command: configure xdsl spectrum-profile (index) vdsl2 cust-psd-pt-up (psdpt) frequency psd

8

Activate the xDSL spectrum profile with the following command: configure xdsl spectrum-profile (index) active

9


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


DLP 188-5


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



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


DLP 188-7


DLP 188-8


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.


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 psd

2

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 psd

3

Activate an xDSL spectrum profile with the following command: configure xdsl spectrum-profile (index) active

4


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


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.


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 (no) ses-nearend (no) uas-nearend (no) es-day-nearend (no) ses-day-nearend (no) uas-day-nearend (no) es-farend (no) ses-farend (no) uas-farend (no) es-day-farend (no) ses-day-farend (no) uas-day-farend

2

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 (no) fcs (no) los-day (no) fcs-day

3


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


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

2

Disable the dual tag mode in the SHub with the following command: configure vlan shub no dual-tag-mode

3


Configuration example: configure vlan shub dual-tag-mode


DLP 191-1

DLP 191 — Enable dual tagging in the SHub

DLP 191-2


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::0 name mode layer2-terminated

2

Associate the S-VLAN created with the IPProxy CPE management function with the following command: configure cpe-management vlan-id

3

Create the S-VLAN in the SHub with the following command: configure vlan shub id mode layer2-terminated


DLP 192-1

DLP 192 — Configure IPProxy CPE management

4

Associate the S-VLAN created in the SHub with the IPProxy CPE management function with the following command: configure cpe-management shub vlan-id

5


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


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

2


Configuration example: configure cpe-management proxy-mode ip


DLP 193-1

DLP 193 — Enable IPProxy CPE management

DLP 193-2


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 /// service-profile spectrum-profile (no) dpbo-profile admin-up


DLP 194-1

DLP 194 — Configure IPProxy CPE management session

2

Configure xDSL line interface port with the following command: configure interface port xdsl-line:/// (no) link-updown-trap (no) user (no) severity

3

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 egress-port lt://

4

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 egress-port nt

5

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:: name mode cross-connect

6

Configure the PVC for this session with the following command: configure atm pvc // /::Eqpt::VciId> aal5-encap-type llc-snap-routed

7

Configure an IPoA cross-connect for this session with the following command: configure atm ip-cross-connect // /::: cpe next-hop

8

Configure a bridge port for this session with the following command: configure bridge port // /:: mac-learn-off

9

Configure the SC-VLAN on the bridge port with the following command: configure bridge port // /:: vlan-id stacked::

DLP 194-2



10

Configure a PVID on the bridge port as the SC-VLAN with the following command: configure bridge port // /:: pvid stacked::

11

Create the session with the following command: configure cpe-management session / // [connection ] 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


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


DLP 194-3


DLP 194-4


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

Note — The setting is applicable to the entire bridge.

2

Configure specify the aging time for dynamically learned MAC addresses in the filtering database of the SHub with the following command: configure bridge shub ageing-time

Note — The setting is applicable to the entire SHub bridge.


DLP 195-1

DLP 195 — Configure general bridge parameters

3

Configure specify the MAC learning states with the following command: configure bridge shub mac-learning (no) disable-nw-port

Note — The setting is applicable to the entire SHub bridge.

4


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


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 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: (no) port (no) server_type

b

Manage the Voice SIP server profile by DNS with the following command: configure voice sip server (name) admin-status up address dns: (no) port (no) server_type


DLP 196-1


2

Manage the Voice SIP dial plan profile with the following command: configure voice sip dialplan (name) (no) pre-activated (no) static-prefix (no) static-suffix

3

Manage the Voice SIP dial plan digitmap profile with the following command: configure voice sip digitmap (name) type rule (no) access-type

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 associated-proxyserver none | name: associated-regserver none | name: associated-dialplan none | name: (no) user-agent-domain admin-status up | down (no) port vlan-id (no) signal-dscp (no) signal-pbits (no) rtp-dscp (no) rtp-pbits

b

Configure the Voice SIP user agent profile mangement manually with the following command: configure voice sip user-agent-manual (name) associated-slot associated-proxyserver none | name: associated-regserver none | name: associated-dialplan none | name: (no) user-agent-domain admin-status up | down ip-address prefix-length gateway-ip domain-server (no) port vlan-id (no) signal-dscp

DLP 196-2



(no) signal-pbits (no) rtp-dscp (no) rtp-pbits

5

Manage the Voice SIP termination profile with the following command: configure voice sip termination (termination) user-agent (no) directory-number (no) user-name (no) uri (no) direct-uri (no) line-feed (no) md5-realm (no) md5-password (no) admin-status

6

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.

7


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


DLP 196-3


DLP 196-4


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

2

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

3

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)


DLP 197-1

DLP 197 — View port configuration and operational data

4

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

5


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


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 (no) max-bw (no) max-no-rate-based

2

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


DLP 198-1

DLP 198 — Configure multicast on the SHub

3

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

4

Configure the CAC Multicast Source with the following command: configure mcast shub src (src) vlan-id ip-addr (no) eth-sus-bit-rate (no) guaranteed-serv (no) bundle name

5


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


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 (no) queue1-weight (no) rx-pause (no) egress-rate (no) dscp2p-enable

2

Configure the traffic classes on the SHub with the following command: configure qos shub tc-map-dot1p (port) traffic-class


DLP 199-1

DLP 199 — Configure QoS on the SHub

3

Configure the mapping of the DSCP value to the 802.1p value with the following command: configure qos shub dscp-map-dot1p (dscp-index) dot1p-value

4

Configure the ingress policing parameters on SHub port with the following command: configure qos shub meter (index) (no) name max-ingress-rate burst-size

5

Configure the various flows to be policed with the following command: configure qos shub flow (index) (no) name (no) (type)

6

Configure the policing association with the following command: configure qos shub policer (port-id) flow meter

7


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


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


DLP 200-1


Procedure Proceed as follows to configure MSTP: 1

Configure the general MSTP parameters with the following command: configure mstp general (no) disable-stp (no) priority (no) max-age (no) hello-time (no) forward-delay (no) version stp-compatible | rstp | mstp (no) tx-hold-count (no) path-cost-type 16-bit | 32-bit (no) max-hop-count region-name (no) region-version (no) config-id-sel

Note 1 — The configuration of the parameters applies for the whole bridge.

Note 2 — This configuration applies to the SHub. Note 3 — When configuring RSTP, this command has to be split. Refer to the configuration example for RSTP at the end of this procedure. 2

Configure the MSTP parameters for a specific MSTP instance with the following command: configure mstp instance (instance) (no) priority

3

Map/unmap the VLAN on the MSTP instance with the following command: configure mstp instance (instance) (no) associate-vlan (vlan)

Note 1 — The VLAN can be associated with the MSTP instance without being configured first. Note 2 — One or more VLANs can be associated to an instance, but one VLAN can not be assigned to different instances. 4

Configure the port parameters for the Common Instance with the following command: configure mstp port (no) priority (no) disable-stp path-cost (no) edge-port (no) admin-p2p (no) hello-time

DLP 200-2



Note — By default MSTP is enabled on the network and outband ports.

5

Configure the MSTP parameters for a specific port-instance configuration with the following command: configure mstp port-instance (network-port) instance (no) priority (no) disable-stp path-cost

6

Manage MSTP related to a port (that is, clear the list of detected protocols) with the following command: admin mstp port (network-port) clear-protocols

7

View the MSTP operational information: a

View all the common spanning tree instances for the whole bridge with the following command: show mstp bridge

b

View the parameters of a multiple spanning tree instance with the following command: show mstp instance (instance)

c

View the MSTP network port information with the following command: show mstp network-port (port)

d

View all the MSTP port instances with the following command: show mstp port-instance (network-port) instance (instance)

8



DLP 200-3


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


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 (no) events (no) packet-summary

2


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


DLP 201-1

DLP 201 — Configure protocol tracing

DLP 201-2


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 (no) queue-stats (no) dsload-tca (no) dsload-thresh (no) buffer-tca (no) up-buf-thresh (no) up-obc-thresh (no) dn-obc-thresh (no) dn-buf-thresh (no) part-buf-thresh


DLP 202-1

DLP 202 — Configure QoS threshold crossing alerts

2

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 (no) tca-enable (no) load-thresh (no) dis-frame-th

3


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


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 min-num-numeric-char min-num-special-char (no) mixed-case

2

Configure file transfer states and attributes with the following command: configure system security filetransfer (no) protocol

3

Configure the file transfer server attributes with the following command: configure system security filetransfer server (serverid) user-name password


DLP 203-1

DLP 203 — Configure general security settings

4


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


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

2

Configure a VLAN on the SHub with the following command: configure interface shub vlan-id (vlan-id)

3

Configure an IP interface on the VLAN with the following command: configure interface shub ip (vlan-id)


DLP 204-1

DLP 204 — Configure an unnumbered IP interface on the SHub

4

Configure a VLAN on the SHub with as egress port the SHub port configured in: configure interface shub ip (vlan-id) ip-addr /

5

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

6

Configure a management VLAN on the SHub with the following command: configure interface shub vlan-id 4093

7

Configure an unnumbered interface on the management VLAN with the following command: configure interface shub ip 4093

8

Associate the numbered interface with the management VLAN with the following command: configure interface shub ip 4093 unnumbered-as (vlan-id) where vlan-id is the VLAN created in step 2.

9


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


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


DLP 205-1

DLP 205 — Configure Link Related Ethernet OAM

keep-alive-intvl response-intvl

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

3

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

b

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

5

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.

6

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.

a

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



b

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


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


DLP 205-3


DLP 205-4


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


DLP 206-1


2

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

3

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

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

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 active

6

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 /// dpbo-profile (index)

b

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

DLP 206-2



dpbo-profile (index)

7


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


DLP 206-3


DLP 206-4


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

2

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

3

Use one of the following commands to complete the modification of the DPBO profile:


DLP 207-1

DLP 207 — Modify a DPBO profile

a

When the modifications must be kept: configure xdsl dpbo-profile (index) modification complete

b

When the modifications must be cancelled: configure xdsl dpbo-profile (index) modification cancel

4


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


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


• •

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


DLP 208-1

DLP 208 — Configure power back off

2

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

3

Go to step 5.

4

Configure the PBO parameters for VDSL2 with the following command: configure xdsl spectrum-profile (index) vdsl2 pbo (band) (no) equal-fext (no) param-a (no) param-b

5


Configuration example: configure xdsl spectrum-profile 4 vdsl pbo 1 param-a 6000

DLP 208-2


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.


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

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

3

Enable/disable vMAC translation on a VLAN and configure the vMAC address downstream blocking option with the following command: configure vlan id (vlanid) (no) vmac-translation (no) vmac-dnstr-filter

4

You can view the vMAC translation fdb table to see vMAC/user MAC translation with the following command: show vlan vmac-bridge-port-fdb (port) [vlan-id ] [mac ]

5


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


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

2

View the memory usage on the NT (size of total memory, size of memory actually in use, percentage of memory in use) with the following command: show system memory-usage (slot)

3

View the CPU load on the NT (start time of monitoring, average load, current condition of monitoring activity) with the following command: show system cpu-load (slot)


DLP 210-1

DLP 210 — View the status of various system parameters

4


Configuration example: show system clock-mgmt show system memory-usage nt-a show system cpu-load nt-b

DLP 210-2


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


• • 2

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

3

View the traffic direction of the configurable ports with the following command: info configure equipment external-link-host (SFP index 6 or 7)

4

Go to step 8.

5

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


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

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

b

in a non-redundant system: admin equipment slot nt-a reboot

8


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


Routine Task Procedure (RTP)

RTP 100 — Backup the configuration RTP 101 — Restore the configuration RTP 102 — Retrieve remote inventory



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.


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:

• •

dm_complete.tar dm.tar: This is the dm_complete.tar without the management data

Prerequisite An empty file dm_complete.tar must exist in the specified path on the TFTP server before the upload is started. Otherwise, the upload will fail (error “upload-error:file-not-found”).

Note — The superuser must create this file.

Create the dm_complete.tar file on the TFTP server with the following commands ($ prompt is regular user, # prompt is superuser): $ su # 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 —

RTP 100-2

(*)

For AMS, the command is cd /opt/ALAams/systemdata



Procedure Proceed as follows to back up the NT database: 1


2

Back up the NT database (and SHub database) with the following command: admin software-mngt database upload actual-active:: where is the IP address of the AMS or AWS server.

3

View the status of the database upload process and, in case of an upload failure, the reason, with the following command: show software-mngt upload-download

4


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


RTP 100-3


RTP 100-4


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 : where is the IP address of the AMS or AWS server.

2

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

3

Activate the downloaded database with the following command: admin software-mngt oswp (index current oswp) activate with-linked-db

4



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


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

Description

manufacturer

An identification of the board manufacturer

inventory-pba

The Alcatel-Lucent Printed Board Assembly code of the code

inventory-fpba

The Alcatel-Lucent Printed Board Assembly code of the board, which also identifies the boot software

inventory-ics

The Item Change Status iteration code of the board

inventory-clie

The (USA) Common Language Equipment Identification code of the board

serial-no

The serial number of the board

Procedure Proceed as follows to retrieve and show remote inventory information: 1

View the RI information with the following command: show equipment slot // detail show equipment applique // detail


RTP 102-1

RTP 102 — Retrieve remote inventory

2


Configuration example: show equipment slot detail show equipment applique detail

RTP 102-2


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

To PSTN

Shelf

Test

TAU

SPLITTER

NTIO TL1 gateway installed Computer/WS (Median Device software installed)

Power -48v

Test Head NT

LT

Lab Network SHub

Computer (test head Software installed)


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



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:;


TAP 100-3


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



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::;


TAP 100-5


TAP 100-6


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

2

View the result of the test with the following command: info admin atm port (port)

3


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


TAP 101-1

TAP 101 — F5 loopback test

TAP 101-2


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

Lock equipment (mostly plug-in units); see DLP 112.

2

Shut down individual equipment; see DLP 153.

3

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

Replan equipment (for example, plug-in units); see DLP 111.

5

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.

6

Power up individual equipment; see DLP 153.

7

Unlock equipment (mostly plug-in units); see DLP 112.

8

Start up or shut down the system. Do one of the following:

9

a

Shut down or restart the SHub; see DLP 151.

b

Reboot the entire system; see DLP 152.



TAP 102-1

TAP 102 — Equipment repair

TAP 102-2


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.


TAP 103-1

TAP 103 — Single ended line testing

TAP 103-2


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.


TAP 104-1


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

2

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.

b

To access the alarms using the 5523 AWS, see the AWS administration overview chapter in the 5523 AWS ADMIN User Guide.

c

To access the alarms using CLI, see the NTP for monitoring alarms in the 7330 ISAM FTTN Operations and Maintenance Using CLI guide.

Select the alarm you want to view. An associated message appears at the bottom of the window.

TAP 104-2



Note — If multiple alarms are present, resolve the alarms in the following order:

• • • 3

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 NE type

Alarm (grouped by alarm type) No.

Alarm name (CLI)

Class

Sev.

Description

Troubleshooting recommendations

SA

Alarm type = Equip (1); Index1 = eqptHolderld (index in equipment holder Table), Index2 = not used 0

—

—

—

—

—

No defects

—

1

Persistent data loss

Equip

Crit

SA

7302

The system has lost all persistent data after a restart. The system is not configured.

Reconfigure the system.

The SNTP server does not respond to the requested messages.

Check the SNTP server.

7330 7302

The NT disk is 90% full.

Clean up the disk space on the NT.

The system is configured to synchronize to an external source and a source other than the configured highest priority source is being used to derive synchronization.

Check that the external source signals at the BITS inputs to the system are within specification.

(persist-data-loss)

2

SNTP server not responding

7330

Equip

Maj

NSA

7302

(sntp-comm-lost) 4

NT disk 90% full

Equip

Maj

NSA

(nt-disk-90%full) 5

System clock not using preferred timing mode (preferred-mode)

7330 Com

Maj

SA

7302 7330

(1 of 34)


TAP 104-3



Alarm name (CLI)

Class

Sev.

SA

6

System clock in holdover mode or in free-run mode

Com

Crit

SA

NE type

Description


7302

The system is configured to synchronize to an external source, and the system is deriving synchronization using the internal source due to a failure on the external source signal.

Check that the external source signals at the BITS inputs to the system are within specification.

The NT cannot communicate with the SHub.

Wait until the SHub has finished rebooting.

7330

(timing-reference)

8

Communication lost with SHub

Equip

Crit

SA

7302 7330

(shub-loc) 25

Back panel type invalid

Equip

Maj

NSA

7302

The NEP back panel type read from SMAS case is an unknown type.

The system will start up with the default back panel. Check the back panel type configuration when the system is running.

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.

Compare the SHub configuration with the database (last database changes may be lost).

(back-pnl-inv)

28

SHub configuration loss (shub-conf-loss)

Alarm type = EquipHolder (2); Index1 = eqptHolderId (index in equipment holder table), Index2 = not used 0

No defects

—

—

—

—

No defects

—

1

Rack power alarm

Equip

Min

NSA

7302

The power fuse is broken.

Check the power supplies.

Equip

Maj

NSA

7302

Fan unit 1 in the rack is failing.

Check the fan.

Equip

Maj

NSA

7302

Fan unit 2 in the rack is failing.

Check the fan.

Equip

Min

NSA

7302

A shelf detected, but the actual shelf type is unknown or it differs from the planned shelf type.

Check the equipment.

A consistency problem has been detected with the installation of the extension chain or multiple chains.

Check the cabling of the extension cable.

(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

7330

(shelf-mismatch) 8

Extension chain installation alarm (ext-chain-instl)

Equip

Crit

SA

7302 7330

Check the configuration.

(2 of 34)

TAP 104-4




Alarm name (CLI)

Class

Sev.

SA

9

Shelf missing alarm

Equip

Maj

SA

NE type

Description


7330

A shelf is planned, but no shelf is detected. A shelf has been detected at least once since the shelf was planned.

Check for a GENC-E or GENC-F card on the host shelf.

(shelf-missing)

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.

10

Shelf installation missing alarm

Equip

Min

NSA

7330

(shelf-install-missing)

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

No defects

—

—

—

—

No defects

—

15

Door alarm

Envir

Min

NSA

7302

Open NEP cabinet door

Close the door.

Equip

Crit

NSA

7302

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.

Check the fuse.

(door) 17

Fuse alarm (fuse)

18

Single fan failure

7330

Equip

Maj

NSA

7330

One or more of the shelf’s fans has failed.

Check the fan tray (the tray LED of the faulty fan is lit red).

Equip

Crit

SA

7330

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)

Check the fan tray of the shelf that raised the alarm. The shelf will power off within 3 minutes of the alarm.

(single-fan-fail) 19

Double fan failure (double-fan-fail)

Check the power feed.

The shelf can be a standalone, a host, or an expansion shelf. (3 of 34)


TAP 104-5



Alarm name (CLI)

Class

Sev.

SA

20

System ac power failure

Envir

Crit

SA

NE type

Description


7330

The shelf will shut down in 15 min.

Check the power installation.

(ac-power-fail) 21

This alarm is externally provided.

Test chain not configured

Equip

Min

NSA

7330

The test chain configuration does not support the test requested.

Configure the test chain to support the test requested.

Equip

Min

NSA

7330

The test cannot be completed because the GENC-F does not have a TAU (required for ITSC) or has failed.

If the GENC-F card does not support MTA, replace it with a GENC-F card that supports MTA.

The test cannot be completed because the GENC-F card does not support ITSC or has failed.

If the GENC-F card does not support ITSC, replace it with a GENC-F card that supports ITSC.

(test-chain-config) 22

TAU not present or failed (tau-problem)

23

ITSC not present or failed

Equip

Min

NSA

7330

(itsc-problem)

24

No test resources

Hardware failed

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

Verify the test equipment.

Equip

Min

NSA

7330

The test equipment has failed during a test.

Force a cold reset of the card. If the card fails again, send the card for repair.

(hw-fail)

Other equipment reported a hardware failure. 26

Test blocked during software download

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

Equip

Maj

NSA

7330

Test requests are blocked when the software download to a GENC-F card has failed.

Reset the GENC-F card (test requests are blocked when a software download has failed).

(test-blk-swdownload)

27

Test blocked because software download failed

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.

Equip

(test-resources)

25

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.

(test-blk-faildownload)

Alarm type = PlugInUnit (3); Index1 = eqptSlotId (index in equipment card table), Index2 = not used 0

No defects

—

—

—

—

No defects

—

(4 of 34)

TAP 104-6




Alarm name (CLI)

Class

Sev.

SA

3

Card-type mismatch alarm

Equip

Min

NSA

NE type

Description


7392

An LT unit is detected, but the actual unit type is unknown or differs from the planned unit type.


7330

(board-mismatch)

This alarm applies to all unit types: NT, LT, and ACU units. 4

Waiting for software

Equip

Maj

NSA

(waiting-for-sw)

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

Equip

Maj

NSA

7302 7330

(temp-exceeded)

12

Temperature shutdown alarm

Equip

Maj

SA

7302 7330

(temp-shutdown)

13

Defense alarm

Equip

Crit

SA

(defense)

14

Card missing alarm (board-missing)

7302 7330

Equip

Maj

SA

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.

Check the fans and restart the unit.

The unit has powered off as a result of temperatures that are too high. This alarm applies only to LT units.

Check the ambient temperature.

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.

Replace the unit.

Unit is planned, no unit is detected, but a unit has been detected at least once since it was planned.

Verify that the unit is present.

For remote units, check for a dirty fan dust filter.

Check the operation of the fans. Check the unit.

This alarm applies to all unit types: NT, EDSE-A, SATU-A, LT, and ACU units. (5 of 34)


TAP 104-7



Alarm name (CLI)

Class

Sev.

SA

15

Card installation missing alarm

Equip

Min

NSA

NE type

Description


7302

Unit is planned, no unit is detected, and no unit has ever been detected since it was planned.

Insert the unit.

7330

(board-instl-missing)

This alarm applies to all unit types: NT, LT, and ACU units. 16

Card initialization alarm

Equip

Maj

SA

7302 7330

(board-init) 17

Card reset protection

Equip

Maj

SA

(board-reset-prot)

28

SEM external power failure

7302 7330

SEM external power supply failure

Card reset or communication failure

SHub uplink breakdown

Force a cold reset of the unit. If this fails, repair the unit.

SA

7330

Power to the external power supply failed. SEM is running on battery power.

Check the power to the external power supply.

Equip

Crit

SA

7330

External SEM power supply or the batteries failed. The external ac power supply can still provide power, but needs to be checked to ensure uninterruptible power service.

Check the external power supply.

Equip

Maj

SA

7302

The LT unit has reset (alarm ON followed by alarm OFF), or there is a communication failure (alarm ON).

Check cabling if alarm is persistent.

The SHub uplink is broken. The alarm is forwarded to the NT, then to the ACU.

Check the SHub uplink cable for loose contacts or missing connections.

7330

(board-reset-cf)

31

The number of unit resets within a certain timeframe exceeded the threshold. This alarm applies only to LT units.

Crit

(sem-ups-fail)

30

Force a cold reset of the unit. If this fails, repair the unit.

Equip

(sem-power-fail) 29

A unit initialization failure has been detected. This alarm applies only to LT units and GENC-F cards.

Equip

Crit

SA

7302 7330

(shub-uplink)

If alarm toggles frequently, the card will go in Card Reset Protection mode (alarm 3, 17) and power down.

Alarm type = ATM (8); Index1 = ifIndex of ATM physical port, Index2 = see specific alarm number 0

No defects

—

—

—

—

No defects

—

1

Connection alarm

Equip

Maj

SA

—

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

No local repair action. Sender must lower shaping rate.

Report mode = disabled Logging mode = disabled (6 of 34)

TAP 104-8




Alarm name (CLI)

Class

Sev.

SA

3

Cell discarded in the downstream direction

QoS

Min

SA

NE type

Description


7302

ATM cell discarded in the downstream direction.

No local repair action. Sender must lower shaping rate.

7330

(cell-discard-down)

Index2 = VPI/VCI Report mode = disabled Logging mode = disabled

6

Duplicate MAC address from this pvc

Com

Min

SA

—

(mac-conflict)

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

No defects

—

—

—

—

No defects

—

1

Customizable alarm 1

Envir

Ind

NSA

7302

Customizable alarm 1 alarm

—

Envir

Ind

NSA

7302


—

Envir

Ind

NSA

7302


—

Envir

Ind

NSA

7302


—

Envir

Ind

NSA

7302


—

(custom1) 2

Customizable alarm 2 (custom2)

3


4


5


Alarm type = CustomizableAlarm (10); Index1 = eqptHolderID (shelf index in equipment holder table), Index2 = not used 0

No defects

—

—

—

—

No defects

—

11

HE customizable alarm 1

Envir

Ind

NSA

7330

Host/expansion customizable alarm 1 alarm

—

Envir

Ind

NSA

7330


—

Envir

Ind

NSA

7330


—

(he-custom1) 12

HE customizable alarm 2 (he-custom2)

13


(7 of 34)


TAP 104-9


Alarm (grouped by alarm type)

NE type

Description


No.

Alarm name (CLI)

Class

Sev.

SA

14

HE customizable alarm 4

Envir

Ind

NSA

7330


—

Envir

Ind

NSA

7330


—

Envir

Ind

NSA

7330


—

(he-custom4) 15


16


Alarm type = IMA-group (13); Index1 = IfIndex of IMA-group, Index2 = not used 0

No defects

—

—

—

1

Far-end starting up

Com

Min

SA

(ima-grp-fe-su) 2

Far-end failed configuration

—

No defects

—

7302

The far-end is starting up.

Check the IMA group configuration at the far-end.

The far-end is not configured properly.

Check which configurations are supported at the near-end and the far-end.

The near-end is not configured properly.

Check which configurations are supported at the near-end and the far-end.

There is an insufficient number of links at the far-end.

Check the status of the links at the far-end.

7330

There is an insufficient number of links at the near-end.

Check the status of the links at the near-end.

7302

The far-end is blocked.

Check the status of the IMA group at the far-end.

7330 Com

Min

SA

7302 7330

(ima-grp-fe-cfg) 3

Near-end failed configuration

Com

Min

SA

7302 7330

(ima-grp-ne-cfg) 4

Insufficient number of links at far-end

Com

Min

SA

7302 7330

(ima-grp-fe-nl) 5

Insufficient number of links at near-end

Com

Min

SA

7302

(ima-grp-ne-nl) 6

Far-end is blocked

Com

Min

SA

(ima-grp-fe-blk)

7330

Alarm type = IMA-link (14); Index1 = IfIndex of IMA-link, Index2 = not used 0

No defects

—

—

—

—

No defects

—

1

Failure in link facility

Com

Min

SA

—

There is a failure in the link facility.

—

This alarm is not currently supported on the system. 2

Loss of IMA frame

Com

Min

SA

(ima-lnk-lif) 3

7302 7330

Link out of delay synchronization

Com

Min

SA

7302 7330

One or more IMA frames are lost.

Check the clock associated with this link.

The link is out of delay synchronization.

Check the clock configuration for the associated group.

There is a connection problem in the link.

Check the link configuration at the far-end.

(ima-lnk-lods) 4

Link misconnect (ima-lnk-misc)

Com

Min

SA

7302 7330

(8 of 34)

TAP 104-10




Alarm name (CLI)

Class

Sev.

SA

5

Link remote failure indication

Com

Min

SA

NE type

Description


7302

There is a remote link failure.

Check the state of the associated facility.

There is a fault in the link facility.

Check for problems with the associated 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.


7330

(ima-lnk-rfi) 6

Fault in link facility

Com

Min

SA

(ima-lnk-fault) 7

Transmission blocked at far-end

7302 7330

Com

Min

SA

7302 7330

(ima-lnk-txblk) 8

Reception blocked at far-end

Com

Min

SA

7302 7330

(ima-lnk-rxblk)

Alarm type = Redundancy (20); Index1 = not used, Index2 = not used 0

No defects

—

—

1

Switchover capability lost

Equip

Maj

—

—

No defects

—

7302 7330

The switchover capability in a redundant system has been lost.

Check link on standby NT.

(loss-over-cap)

Check standby cards. Wait for Quench timeout.

Alarm type = SHDSL (23); Index1 = ifIndex of SHDSL physical port, Index2 = device ID 0

No defects

—

—

—

—

No defects

—

1

Loss of signal on network side on first pair

Com

Min

SA

—

Loss of signal on the network side on the first pair.

—

(shdsl-n-los-1) 2

Loss of signal on customer side on first pair

This alarm is not currently supported on the system. Com

Min

SA

—

(shdsl-c-los-1) 3

Loss of synchronization on network side on first pair

Loss of synchronization on customer side on first pair

Com

Min

SA

—

Loop attenuation alarm on network side on first pair (shdsl-n-aten-1)

Loss of the synchronization word on the network side on the first pair.

—


Min

SA

—

(shdsl-c-losw-1) 5

—

This alarm is not currently supported on the system.

(shdsl-n-losw-1) 4

Loss of signal on the customer side on the first pair.

Loss of the synchronization word on the customer side on the first pair.

—


Min

SA

—

Loop attenuation alarm on the network side on the first pair.

—


(9 of 34)


TAP 104-11



Alarm name (CLI)

Class

Sev.

SA

6

Loop attenuation alarm on customer side on first pair

Com

Min

SA

NE type

Description


—

Loop attenuation alarm on the customer side on the first pair.

—

(shdsl-c-aten-1) 7

SNR margin alarm on network side on first pair


Min

SA

—

(shdsl-n-snr-1) 8

SNR margin alarm on customer side on first pair

Com

Min

SA

—

DC continuity fault on network side on first pair

Com

Min

SA

—

—

DC continuity fault on customer side on first pair

Loopback active on network side

There is a DC continuity fault on the network side on the first pair.

—


Min

SA

—

(shdsl-c-dccont-1) 11

Signal-to-noise margin alarm on the customer side on the first pair. This alarm is not currently supported on the system.

(shdsl-n-dccont-1) 10

—


(shdsl-c-snr-1) 9

Signal-to-noise margin alarm on the network side on the first pair.

There is a DC continuity fault on the customer side on the first pair.

—


Min

SA

7302

Loopback is active on the network side.

Testing is in progress.

Com

Min

SA

7302

Loopback is active on the customer side.

Testing is in progress.

(shdsl-n-loopback) 12

Loopback active on customer side (shdsl-c-loopback)

Report mode = disabled Logging mode = disabled

13

Configuration error

Com

Min

SA

7302

There is a configuration error.

Check the configuration parameters supported by the device.

Com

Min

SA

7302

Loss of ATM cell delineation

Check the clock subsystem or the ATM configuration.

Com

Min

SA

7302

Loss of power at STU-R

Check the power supply at the STU-R.

Com

Min

SA

7302

Unable to disable STU-R access

Check for devices that do not support disabling the STU-R access.

Equip

Min

SA

7302

Device fault


Com

Min

SA

7302

No ATM cell delineation

Check the clock subsystem or the ATM configuration.

(shdsl-conferr) 14

Loss of ATM cell delineation (shdsl-atm-lcd)

15

Loss of power at STU-R (shdsl-lpr)

16

Unable to disable STU-R access (shdsl-secu-err)

17

Device fault (shdsl-dev-fault)

18

No ATM cell delineation (shdsl-atm-ncd)

(10 of 34)

TAP 104-12




Alarm name (CLI)

Class

Sev.

SA

19

Loss of signal on network side on second pair

Com

Min

SA

NE type

Description


—

Loss of signal on the network side on the second pair.

—

(shdsl-n-los-2) 20

Loss of signal on customer side on second pair


Min

SA

—

(shdsl-c-los-2) 21

Loss of synchronization on network side on second pair

Loss of synchronization on customer side on second pair

Com

Min

SA

—

Loop attenuation alarm on network side on second pair

Com

Min

SA

—

Loop attenuation alarm on customer side on second pair

Com

Min

SA

—

SNR margin alarm on network side on second pair

Com

Min

SA

—

SNR margin alarm on customer side on second pair

Com

Min

SA

—

DC continuity fault on network side on second pair

Com

Min

SA

—

DC continuity fault on customer side on second pair (shdsl-c-dccont-2)

—

Loop attenuation alarm on the customer side on the second pair.

—

Signal-to-noise margin alarm on the network side on the second pair.

—

Signal-to-noise margin alarm on the customer side on the second pair.

—


Min

SA

—

(shdsl-n-dccont-2) 28

Loop attenuation alarm on the network side on the second pair.


(shdsl-c-snr-2) 27

—


(shdsl-n-snr-2) 26

Loss of the synchronization word on the customer side on the second pair.


(shdsl-c-aten-2) 25

—


(shdsl-n-aten-2) 24

Loss of the synchronization word on the network side on the second pair. This alarm is not currently supported on the system.

(shdsl-c-losw-2) 23

—


(shdsl-n-losw-2) 22

Loss of signal on the customer side on the second pair.

There is a DC continuity fault on the network side on the second pair.

—


Min

SA

—

There is a DC continuity fault on the customer side on the second pair.

—


(11 of 34)


TAP 104-13


NE type


Alarm name (CLI)

Class

Sev.

Description


SA

Alarm type = EthItf (24); Index1 = ifIndex of Ethernet port, Index2 = see specific alarm number 0

No defects

—

—

—

—

No defects

—

1

IP address conflict on Ethernet port

Com

Crit

NSA

—

IP address conflict on Ethernet port.

—

(eth-itf-ip-addr-cnflct)


Alarm type = SwMgnt (29); Index1 = eqptSlotId (index in equipment card table for the NT), Index2 = not used 0

No defects

—

—

—

—

No defects

—

1

Implicit software rollback

Proc

Maj

SA

7302

The system cannot make the NotActive OSWP and linked database operational (although no error in the database is detected). The system performs an implicit rollback to the previous active OSWP (and linked database).

Remove the corrupted OSWP (abort operation).

The system cannot make the selected OSWP and linked database operational (an error is detected in the linked database). The system comes up with the selected OSWP and the previous linked database (if possible).

Download the desired database again.

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.

—

7330

(sw-rollback)

2

Implicit database rollback

Proc

Maj

SA

7302 7330

(db-rollback)

3

Autofetch failure

Proc

Min

NSA

—

Download the desired OSWP again. Activate the downloaded OSWP.

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

No defects

—

—

—

—

No defects

—

1

Derived alarm for temporal filter

Com

Ind

NSA

7302

Derived alarm for temporal filter.

Check the cause of the related basic alarm.


Check the setting of the related temporal filter.







Report mode = disabled


7330

(der-temp1)

2


Com

Ind

NSA

7302 7330

(der-temp2)

3

Derived alarm for temporal filter (der-temp3)

Com

Ind

NSA

7302 7330

Logging mode = disabled (12 of 34)

TAP 104-14




Alarm name (CLI)

Class

Sev.

SA

4


Com

Ind

NSA

NE type

Description


7302













































7330

(der-temp4)

5


Com

Ind

NSA

7302 7330

(der-temp5)

6


Com

Ind

NSA

7302 7330

(der-temp6)

7


Com

Ind

NSA

7302 7330

(der-temp7)

8


Com

Ind

NSA

7302 7330

(der-temp8)

9


Com

Ind

NSA

7302 7330

(der-temp9)

10


Com

Ind

NSA

7302 7330

(der-temp10)

11


Com

Ind

NSA

7302 7330

(der-temp11)

12


Com

Ind

NSA

7302 7330

(der-temp12)

13


Com

Ind

NSA

7302 7330

(der-temp13)

14


Com

Ind

NSA

7302 7330



TAP 104-15



Alarm name (CLI)

Class

Sev.

SA

15


Com

Ind

NSA

NE type

Description


7302













































7330

(der-temp15)

16


Com

Ind

NSA

7302 7330

(der-temp16)

17


Com

Ind

NSA

7302 7330

(der-temp17)

18


Com

Ind

NSA

7302 7330

(der-temp18)

19


Com

Ind

NSA

7302 7330

(der-temp19)

20


Com

Ind

NSA

7302 7330

(der-temp20)

21


Com

Ind

NSA

7302 7330

(der-temp21)

22


Com

Ind

NSA

7302 7330

(der-temp22)

23


Com

Ind

NSA

7302 7330

(der-temp23)

24


Com

Ind

NSA

7302 7330

(der-temp24)

25


Com

Ind

NSA

7302 7330


TAP 104-16




Alarm name (CLI)

Class

Sev.

SA

26


Com

Ind

NSA

NE type

Description


7302

























7330

(der-temp26)

27


Com

Ind

NSA

7302 7330

(der-temp27)

28


Com

Ind

NSA

7302 7330

(der-temp28)

29


Com

Ind

NSA

7302 7330

(der-temp29)

30


Com

Ind

NSA

7302 7330

(der-temp30)

31


Com

Ind

NSA

7302 7330

(der-temp31)

Alarm type = SpaFilter (35); Index1 = 1, Index2 = not used 0

No defects

—

—

—

—

No defects

—

1

Derived alarm for spatial filter

Com

Ind

NSA

7302

Derived alarm for spatial filter.



Check the setting of the related spatial filter.

















7330

(der-spa1)

2


Com

Ind

NSA

7302 7330

(der-spa2)

3


Com

Ind

NSA

7302 7330

(der-spa3)

4


Com

Ind

NSA

7302 7330

(der-spa4)

5

Derived alarm for spatial filter (der-spa5)

Com

Ind

NSA

7302 7330



TAP 104-17



Alarm name (CLI)

Class

Sev.

SA

6


Com

Ind

NSA

NE type

Description


7302













































7330

(der-spa6)

7


Com

Ind

NSA

7302 7330

(der-spa7)

8


Com

Ind

NSA

7302 7330

(der-spa8)

9


Com

Ind

NSA

7302 7330

(der-spa9)

10


Com

Ind

NSA

7302 7330

(der-spa10)

11


Com

Ind

NSA

7302 7330

(der-spa11)

12


Com

Ind

NSA

7302 7330

(der-spa12)

13


Com

Ind

NSA

7302 7330

(der-spa13)

14


Com

Ind

NSA

7302 7330

(der-spa14)

15


Com

Ind

NSA

7302 7330

(der-spa15)

16


Com

Ind

NSA

7302 7330


TAP 104-18




Alarm name (CLI)

Class

Sev.

SA

17


Com

Ind

NSA

NE type

Description


7302













































7330

(der-spa17)

18


Com

Ind

NSA

7302 7330

(der-spa18)

19


Com

Ind

NSA

7302 7330

(der-spa19)

20


Com

Ind

NSA

7302 7330

(der-spa20)

21


Com

Ind

NSA

7302 7330

(der-spa21)

22


Com

Ind

NSA

7302 7330

(der-spa22)

23


Com

Ind

NSA

7302 7330

(der-spa23)

24


Com

Ind

NSA

7302 7330

(der-spa24)

25


Com

Ind

NSA

7302 7330

(der-spa25)

26


Com

Ind

NSA

7302 7330

(der-spa26)

27


Com

Ind

NSA

7302 7330



TAP 104-19



Alarm name (CLI)

Class

Sev.

SA

28


Com

Ind

NSA

NE type

Description


7302

















7330

(der-spa28)

29


Com

Ind

NSA

7302 7330

(der-spa29)

30


Com

Ind

NSA

7302 7330

(der-spa30)

31


Com

Ind

NSA

7302 7330

(der-spa31)

Logging mode = disabled Alarm type = xDSL (38); Index1 = ifIndex of xDSL physical port, Index2 = not used 0

No defects

—

—

—

1

Near-end loss of signal

Com

Min

SA

—

No defects

—

7302

A near-end loss of signal has occurred.

Check the physical line.

A near-end loss of frame has occurred.

Check modem equipment.

A near-end loss of margin has occurred.

Check the physical line (new distributors).

Near-end excessive server errors have occurred.

Check the physical communication medium.

The line configuration data cannot be used.

Update the profile parameters.

7330

(xdsl-ne-los) 2

Near-end loss of frame

Com

Min

SA

7302 7330

(xdsl-ne-lof) 3

Near-end loss of margin

Com

Min

SA

7302 7330

(xdsl-ne-lom) 4

Near-end excessive server errors

Com

Min

SA

7302 7330

(xdsl-ne-ese) 5

Activation failure — configuration error

Com

Crit

SA

7302 7330

(xdsl-act-cfg-error)

Ensure that the pilot tones are not marked. If Glite is used, ensure that the bit rates fit within the standard.

6

Activation failure — configuration not feasible

Com

Maj

SA

7302 7330

The line capacity is not high enough to set up the requested profile.

Check the configuration data.

The upstream planned bit rate was not reached after initialization.

Lower planned upstream bit rate.

A near-end cell delineation has occurred.

Check the quality of the line.

(xdsl-act-not-feas) 7

Near-end bit rate threshold alarm

Com

Min

SA

7302 7330

(xdsl-up-br-reach) 8

Near-end no cell delineation

Com

Min

SA

7302 7330

Check the physical line (length and noise).

(xdsl-ne-ncd) (18 of 34)

TAP 104-20




Alarm name (CLI)

Class

Sev.

SA

9

Near-end loss of cell delineation

Com

Min

SA

NE type

Description


7302

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.

Check modem equipment.

A far-end loss of power was detected.

There is no repair required because this is the normal power-down of CPE.

A far-end loss of link was detected.


A far-end loss of margin has occurred.

Check the physical line (new distributors).

Far-end excessive server errors have occurred.


Unsuccessful initialization as a result of communication problems

Check the peer modem type.

Peer modem not detected

Wait until the modem is connected.

7330

(xdsl-ne-lcd) 10

Far-end loss of signal

Com

Min

SA

(xdsl-fe-los) 11

Far-end loss of frame

Com

Min

SA

(xdsl-fe-lof) 12

Far-end loss of power

Far-end loss of link

Com

Min

SA

Far-end loss of margin

7302 7330

Com

Min

SA

(xdsl-fe-lol) 14

7302 7330

(xdsl-fe-lpr) 13

7302 7330

7302 7330

Com

Min

SA

7302 7330

(xdsl-fe-lom) 15

Far-end - excessive severe errors

Com

Min

SA

7302 7330

(xdsl-fe-ese) 16

Activation failure — communication problem

Com

Maj

SA

7302 7330


(xdsl-act-comm) 17

Activation failure — No peer modem detected

Com

Min

SA

7302 7330


(xdsl-act-modem) 18

Far-end bit rate threshold

Com

Min

SA

7302 7330

(xdsl-do-br-reach) 19

Far-end no cell delineation

Com

Min

SA

7302 7330

The downstream planned bit rate was not reached after initialization.

Lower the planned downstream bit rate.

A far-end cell delineation has occurred.


A far-end loss of cell delineation has occurred.


A far-end UPBO violation has occurred.


There was an activation failure due to CPE policing.


(xdsl-fe-ncd) 20

Far-end loss of cell delineation

Com

Min

SA

7302 7330

(xdsl-fe-lcd) 23

Far-end UPBO violation

Com

Min

SA

7302 7330

(xdsl-fe-upbo-vio) 24

Activation failure — CPE policing

Com

Maj

SA

7302 7330

(xdsl-fe-cpe-pol)

Alarm type = xDSLTca (39); Index1 = ifIndex of xDSL physical port, Index2 = not used 0

No defects

—

—

—

—

No defects

—

(19 of 34)


TAP 104-21



Alarm name (CLI)

Class

Sev.

SA

1

Near-end TCA alarm errored seconds in 15 min

QoS

Min

NSA

NE type

Description


7302

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.


7330

(xtca-ne-es)

2

Near-end TCA alarm severely errored seconds in 15 min

QoS

Min

NSA

7302 7330

(xtca-ne-ses)

3

Near-end TCA alarm unavailable seconds

QoS

Min

NSA

7302 7330

(xtca-ne-uas)

4

Near-end TCA alarm errored seconds in 1 day

QoS

Min

NSA

7302 7330

(xtca-ne-day-es)

5

Near-end TCA alarm severely errored seconds in 1 day

QoS

Min

NSA

7302 7330

(xtca-ne-day-ses)

6

Near-end TCA alarm unavailable seconds in 1 day

QoS

Min

NSA

7302 7330

(xtca-ne-day-uas)

7

Far-end TCA alarm errored seconds in 15 min

QoS

Min

NSA

7302 7330

(xtca-fe-es)

8

Far-end TCA alarm severely errored seconds in 15 min (xtca-fe-ses)

QoS

Min

NSA

7302 7330

Check the modem equipment.








(20 of 34)

TAP 104-22




Alarm name (CLI)

Class

Sev.

SA

9

Far-end TCA alarm unavailable seconds

QoS

Min

NSA

NE type

Description


7302

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.


7330

(xtca-fe-uas)

10

Far-end TCA alarm errored seconds in 1 day

QoS

Min

NSA

7302 7330

(xtca-fe-day-es)

11

Far-end TCA alarm severely errored seconds in 1 day

QoS

Min

NSA

7302 7330

(xtca-fe-day-ses)

12

Far-end TCA alarm unavailable seconds in 1 day

QoS

Min

NSA

7302 7330

(xtca-fe-day-uas)





Alarm type = bonding (54); Index1 = IfIndex of bonding group, Index2 = not used 0

No defects

—

—

—

1

Bonding group upstream planned bit rate threshold

Com

Min

SA

—

No defects

—

7302

Group upstream actual bit rate is above group upstream minimum bit rate but below group upstream planned bit rate.

Lower group upstream planned bit rate.

Group upstream actual bit rate dropped below group upstream minimum bit rate.

Check physical line.

Group upstream actual bit rate is not high enough to set up the configured group upstream minimum bit rate.

Check configuration data.

Group downstream actual bit rate is above group downstream minimum bit rate but below group downstream planned bit rate.

Lower group downstream planned bit rate.

Group downstream actual bit rate dropped below group downstream minimum bit rate.


7330

(up-plan-bitrate) 2

Bonding group upstream minimum bit rate threshold

Com

Min

SA

7302 7330

(up-min-bitrate) 3

Bonding group upstream configuration not feasible

Com

Maj

SA

7302 7330

(up-config-not-feas) 4

Bonding group downstream planned bit rate threshold

Com

Min

SA

7302 7330

(down-plan-bitrate)

5

Bonding group downstream minimum bit rate threshold (down-min-bitrate)

Com

Min

SA

7302 7330

Check line state.


Check line state.

(21 of 34)


TAP 104-23



Alarm name (CLI)

Class

Sev.

SA

6

Bonding group downstream configuration not feasible

Com

Maj

SA

NE type

Description


7302

Group downstream actual bit rate is not high enough to set up the configured group downstream minimum bit rate.

Check configuration data.

CPE modem is not connected to the group lines.

Check the modem.

7330

(down-config-notfeas) 7

Bonding group no peer modem detected

Com

Min

SA

7302 7330

(no-peer-cpe)


Check the physical lines.

This alarm is not currently supported on the system. 8

Bonding group non-bonding CPE connected

Com

Min

SA

7302 7330

The CPE connected does not support bonding.

Check the modem.

The lines of the bonding group are connected to more than one CPE.

Check the xDSL wiring configuration.

A discovery or aggregation register failure is detected.

Check the CPE.

Not all configured lines of the bonding group are actually part of the bonding group.

Check the xDSL wiring configuration.

Check the physical lines.

(non-bonding-cpe) 9

Bonding group connected to multiple CPEs

Com

Maj

SA

7302 7330

Check the CPE.

(multiple-cpes) 10

Bonding group CPE register failure

Com

Maj

SA

7302 7330

(register) 11

Bonding group Incomplete

Com

Min

NSA

7302 7330

(group-incomplete)

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

No defects

—

—

—

—

No defects

—

1

VRF assignment failure

Proc

Maj

SA

7302

Failure to assign a VRF for a user session:

Check the system configuration.

•

Check the RADIUS server configuration.

(vrf-assign-fail)

7330

•

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




Alarm name (CLI)

Class

Sev.

SA

2

VLAN assignment failure

Proc

Maj

SA

NE type

Description


7302

Failure to assign a VLAN for a user session:


•


7330

(vlan-assign-fail)

•

3

IP address pool assignment failure (ip-pool-assign-fail)

Proc

Maj

SA

7302 7330

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.

Failure to assign an IP address pool:


•


•

•

•

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)


TAP 104-25



Alarm name (CLI)

Class

Sev.

SA

4

QoS parameters assignment failure

Proc

Maj

SA

NE type

Description


7302

Failure to assign QoS parameters for a user session:


7330

(qos-assign-fail)

•

•

5

IP address assignment failure

Proc

Maj

SA

7302 7330

(ip-addr-assign-fail)

Failure to assign IP address for a user session:

•

•

6

Missing attributes

Proc

Maj

SA

(missing-attributes)

7302 7330

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

RADIUS server should always specify a pool-id when it returns a VRF.


Check the system configuration. Check the RADIUS server configuration.

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

No defects

—

—

—

1

IP address preempt

Com

Maj

SA

(ip-addr-preempt)

—

No defects

—

7302

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.

7330

Check local IP address pool.

Alarm type = SFP (76); Index1 = ifIndex of IPoX interface on which the session takes place, Index2 = not used 0

No defects

—

—

—

—

No defects

—

1

Host SFP LOS

Com

Crit

SA

7330

Host shelf downlink SFP loss of signal.


(host-sfp-los)

This alarm applies only to a host ARAM-D shelf. (24 of 34)

TAP 104-26




Alarm name (CLI)

Class

Sev.

SA

2

Host SFP transmit fail

Com

Crit

SA

NE type

Description


7330

Host shelf downlink SFP transmission failure.

Check the host shelf SFP module.

(host-sfp-tx-fail)

This alarm applies only to a host ARAM-D shelf. 3

Host SFP not present

Com

Crit

SA

7330

(host-sfp-not-prst)

Host SFP missing. Host shelf downlink SFP detected but later removed.

Check the host shelf SFP presence.


Host SFP invalid Alcatel-Lucent ID

Com

Crit

SA

7330

(host-sfp-inv-id)

Host shelf downlink SFP does not have a valid Alcatel-Lucent ID.

Check the host shelf SFP module ID.


Host SFP control fail

Com

Crit

SA

7330

(host-sfp-ctrl-fail)

6

Host SFP unexpected remote LT

Equip

Min

NSA

7330

(host-sfp-rmtlt)

7

Host SFP assignment mismatch

Equip

Maj

SA

7330

(host-sfp-mismatch)

8

Host SFP incompatible shelf

Equip

Min

NSA

7330

(host-sfp-incompt)

Host shelf downlink SFP control failure.

Check the host shelf SFP module or I2C bus.

This alarm applies only to a host ARAM-D shelf.

If control of all host shelf SFPs fails, check the GENC-E or GENC-F.

The host SFP is not assigned to any remote LT units but a connection to a remote LT unit is detected.

Check for missing host SFP assignment configuration.

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.

Check for cabling error.

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.

Check for cabling error.

Check if the remote LT unit is cabled to the wrong host SFP.

Check for host SFP assignment configuration 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

Com

Crit

SA

7330

(exp-sfp-los) 12

ES SFP transmit fail (exp-sfp-tx-fail)

No defects

—

ES SFP loss of signal.


This alarm applies only to the ES. Com

Crit

SA

7330

ES SFP transmission failure.

Check the ES SFP module.

This alarm applies only to the ES. (25 of 34)


TAP 104-27


Alarm (grouped by alarm type) No. 13

Alarm name (CLI)

Class

Sev.

SA

ES SFP not present

Com

Crit

SA

NE type

Description


7330

ES SFP missing. ES SFP detected but later removed.

Check the ES SFP presence.

(exp-sfp-not-prst)

This alarm applies only to the ES. 14

ES SFP invalid Alcatel-Lucent ID

Com

Crit

SA

7330

(exp-sfp-inv-id) 15

ES SFP control fail

ES SFP does not have a valid Alcatel-Lucent ID.

Check the ES SFP module ID.

This alarm applies only to the ES. Com

Crit

SA

7330

(exp-sfp-ctrl-fail)

The SFP alarm for the ES downlink SFP control failure.

Check the ES SFP module or I2C bus.

This alarm applies only to the ES. Alarm type = LLURelay (78); Index1 = eqptSlotId (index in equipment card table), Index2 = not used 0

No defects

—

—

—

—

No defects

—

1

Wrong applique for LLU

Com

Maj

SA

7302

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.

(llu-relay-status)

Alarm type = SHDSL_ISAM (82); Index1 = IfIndex of SHDSL physical port, Index2 = linkID (higher 16 bits) + device ID (lower 16 bits) 0

No defects

—

—

—

—

No defects

—

1

Loss of signal on network side on each pair

Com

Min

SA

—

Loss of signal on the network side on each pair.

—


(shdsl-n-los) 2

Loss of signal on customer side on each pair

Com

Min

SA

—

(shdsl-c-los) 3

Loss of signal on the customer side on each pair.

—


Loss of synchronization on network side on each pair

Com

Min

SA

7302

Loss of synchronization word 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

Loop attenuation alarm on the network side on each pair


Com

Min

SA

7302

Loop attenuation alarm on the customer 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)

TAP 104-28




NE type

Description


No.

Alarm name (CLI)

Class

Sev.

SA

7

SNR margin alarm on network side on each pair

Com

Min

SA

7302

Signal-to-noise ratio alarm on the network side on each pair


Com

Min

SA

7302

Signal-to-noise ratio alarm on the customer side on each pair


Com

Min

SA

7302

DC continuity fault on the network side on each pair

Check the equipment and wiring on the network side.

Com

Min

SA

7302

DC continuity fault on the customer side on each pair

Check the equipment and wiring on the customer side.

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

Alarm type = CustomExternalAlarms (83); Index1 = eqptSlodId (index in equipment card table), Index2 = not used 0

No defects

—

—

—

—

No defects

—

1

Customizable external alarm 1

Equip

Maj

NSA

7330

REM customizable external alarm 1

—

Equip

Maj

NSA

7330


—

Equip

Maj

NSA

7330


—

Equip

Maj

NSA

7330


—

Equip

Maj

NSA

7330


—

(custextalarm1) 2

Customizable external alarm 2 (custextalarm2)

3


4


5


Alarm type = PlugInUnit2 (84); Index1 = eqptSlotId (index in equipment card table), Index2 = not used 0

No defects

—

—

—

—

No defects

—

1

Fan

Equip

Maj

NSA

7330

REM fan power alarm

Check the REM fan.

Equip

Maj

NSA

7330

REM DC A voltage low. DC B takes over.

Check the fuse.

REM DC B voltage low. DC A takes over.

Check the fuse.

(pluginfan) 2

DC A (plugin-dc-a)

3

DC B (plugin-dc-b)

Equip

Maj

NSA

7330

Check the cabling.

Check the cabling.

(27 of 34)


TAP 104-29



NE type

Description


No.

Alarm name (CLI)

Class

Sev.

SA

4

Dying gasp

Equip

Crit

SA

7330

REM dying gasp alarm. REM going out of service due to power shutdown. Possible causes: power failure, mains switch off, excessive over temperature, an so on.

Check the following at the REM and the cabinet: cabling, fuse, temperature, on and off switch.

Equip

Crit

SA

7302

Applique power supply malfunction. The relays are no longer configurable and are switched to the hardware default position.

Check applique power supply.

Equip

Maj

SA

7302

The LT unit reports an NTR loss event when the NTR signal is not available. An NTR-A loss is reported even when there is no NT unit in the NT-A slot.

Check the status of the NT-A NTR.

The LT unit reports an NTR loss event when the NTR signal is not available. An NTR-B loss is reported even when there is no NT unit in the NT-B slot.

Check the status of the NT-B NTR.

The test cannot be completed because of missing test equipment. The LT unit is not present or has failed.

Verify compatibility with ITSC tests.

The test cannot be completed because of missing test equipment. The applique is not present, not compatible or failed, or the LT unit is not compatible with the applique.

Check the applique. Verify compatibility with LT unit for test.

(plugin-dg)

5

Applique power supply failure (apsf-alarm)

6

NTR-A loss (ntr-a-loss)

7

7330

NTR-B loss

Equip

Maj

SA

(ntr-b-loss)

8

7302 7330

ITSC LT unit not present or failed

Equip

Min

NSA

7330

(lt-problem)

9

ITSC applique not present, not compatible, or failed

Equip

Min

NSA

7330

(applique-problem)



Alarm type = IntTestSealCur (85); Index1 = ifIndex of xDSL line being sealed, Index2 = not used 0

No defects

—

—

—

—

No defects

—

1

Test exceeded maximum time

Proc

Min

NSA

7330

The test duration exceeded the maximum allowed duration.

Try the test again.

Equip

Min

NSA

7330

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.

(test-exceeded-maxtime) 2

No DC termination on line (dc-termination)

Verify the connections of the test chain.

(28 of 34)

TAP 104-30




Alarm name (CLI)

Class

Sev.

SA

3

Sealing current cycle missed

Proc

Min

NSA

NE type

Description


7330

The line assigned to a sealing current interval could not be completed for two consecutive intervals. Possible reasons are:


(sc-cycle-missed)

• • • 4

Hazardous voltage detected on the line

Equip

Maj

NSA

7330

(hazardous-potential)

5

FEMF detected on the line

ITSC card protection detected on the line

Reduce or stop the number of manual ITSC tests to increase the time available for line sealing.

A hazardous voltage is detected on the line under test.

Verify the line at the customer side. WARNING: Ensure all proper precautions are taken to prevent injury.

Equip

Min

NSA

7330

A foreign electromotive force is detected on the line under test.

Verify the line on the customer side.

Equip

Min

NSA

7330

The ITSC card protection is activated for the line under test.

Verify the line on the customer side.

(femf) 6

ON duration too long too many lines per interval too many lines being tested by operator


(device-protection)

Alarm type = SIP User Agent (98); Index1 = sipUaId (index in SIP user agent table), Index2 = not used 0

No defects

—

—

—

—

No defects

—

1

DHCP server unreachable

Com

Crit

SA

7302

The DHCP server is unreachable for the SIP user agent.

Check the link between the system and the DHCP server.

The SIP proxy server is unreachable for the SIP user agent.

Check the link between the system and the SIP proxy server.

The SIP registrar server is unreachable for the SIP user agent.

Check the link between the system and the SIP registrar server.

7330

(dhcp-unreach) 2

SIP proxy server unreachable

Com

Crit

SA

7302 7330

(proxy-srv-unreach) 3

SIP registrar server unreachable

Com

Crit

SA

7302 7330

(reg-srv-unreach)

Alarm type = SIP PlugInUnit (99); Index1 = eqpSlotId (index in equipment card table), Index2 = not used 0

No defects

—

—

—

—

No defects

—

1

Invalid CDE file

Proc

Crit

SA

7302

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.

(inval-cdefile)

7330

• •

The CDE file does not exist. The CDE file is of invalid format.

(29 of 34)


TAP 104-31



Alarm name (CLI)

Class

Sev.

SA

2

Short of resource (short-res)

Proc

Crit

SA

NE type

Description


7302

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.

Wait until one of the busy calls is terminated.

7330

Alarm type = SIP Termination (100); Index1 = ifIndex of PSTN physical port, Index2 = not used 0

No defects

—

—

—

1

Unknown SIP subscriber

Com

Maj

SA

—

No defects

—

7302

The SIP subscriber information configured in the SIP termination does not exist on the SIP application server.

Verify if the directory number, the user name, or the URI of the SIP termination is valid.

The current threshold of the physical line of the port is exceeded. The usual root causes are:

Check the cabling of the port.

7330

(unknown-sub)

2

Ground key

Equip

Maj

SA

(ground-key)

7302 7330

• • • 3

Port high temperature

Equip

Maj

SA

(port-hightemp)

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.

The temperature threshold on the physical PSTN port is exceeded. The port is automatically shut down.

Check the ambient temperature. Check the operation of the fans. Check the port.

Alarm type = NonAlcateldev (104); Index1 = not used, Index2 = not used 0

No defects

—

—

—

—

No defects

—

1

No environment box

Equip

Crit

NSA

7302

The environment box does not exist or is not alive.

Verify if there is an environment box.

(loss-env-mon)

7330

Alarm type = FileTransfer (105); Index1 = file server ID (IP address), Index2 = not used 0

No defects

—

—

—

—

No defects

—

1

File server unavailable

Com

Maj

NSA

7302

The system is not able to connect to the file server for a file transfer.

Check if the file transfer server is correctly configured.

7330

(fileserv-unavailable)

Check the network-to-file transfer server. Alarm type = TrafficOverflow (106); Index1 = eqptSlotId (index in NT equipment card table), Index2 = not used 0

No defects

—

—

—

—

No defects

—

1

LT load overflow

QoS

Min

SA

7302

LT load overflow

Check the LT load.

(fanout)

7330

(30 of 34)

TAP 104-32




Alarm name (CLI)

Class

Sev.

SA

2

Upstream load overflow

QoS

Min

SA

NE type

Description


7302

Upstream load overflow

Check the LT load in upstream.

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.

7330

(up-overflow) 3

Upstream load to OBC overflow

QoS

Min

SA

7302 7330

(upobc-overflow) 4

Downstream load to OBC overflow

QoS

Min

SA

7302 7330

(dwobc-overflow) 5

Downstream load overflow

QoS

Min

SA

7302 7330

(dw-overflow) 6

BE and CF packets dropped exceeds threshold

QoS

Min

SA

7302 7330

(lwpri-overflow) Alarm type = EthTca (107); Index1 = ifIndex of Ethernet interface, Index2 = not used 0

No defects

—

—

—

—

No defects

—

1

LOS errors encountered in current 15-min interval has reached threshold value

QoS

Min

NSA

7302

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.


7330

(etca-los) 2

FCS errors encountered in current 15-min interval has reached threshold value

QoS

Min

NSA

7302 7330

(etca-fcs) 3

LOS errors encountered in current 1-day interval has reached threshold value

QoS

Min

NSA

7302 7330

(etca-day-los) 4

FCS errors encountered in current 1-day interval has reached threshold value

QoS

Min

NSA

7302 7330

(etca-day-fcs)





Alarm type = EthSFP (108); Index1 = ifIndex of Ethernet interface, Index2 = not used 0

No defects

—

—

—

1

Ethernet SFP LOS

Com

Min

SA

(user-sfp-los) 2

Ethernet SFP transmit fail (user-sfp-tx-fail)

—

No defects

—

7302

User SFP loss of signal


User SFP transmission failure

Check the SFP module.

7330 Com

Min

SA

7302 7330

(31 of 34)


TAP 104-33



Alarm name (CLI)

Class

Sev.

SA

3

Ethernet SFP not present (user-sfp-not-prst)

Com

Min

SA

Ethernet SFP invalid Alcatel-Lucent ID

Com

4

NE type

Description


7302

User SFP is not detected.

Check if the SFP is present.

User SFP does not have a valid Alcatel-Lucent ID.

Check the module ID of the SFP.

7330 Min

SA

7302 7330

(user-sfp-inv-id) Alarm type = L2Forward (109); Index1 = ifIndex of bridge port, Index2 = see specific alarm number 0

No defects

—

—

—

1

Duplicate MAC address

Com

Min

SA

—

No defects

—

7302

Duplicate MAC address on the bridge port indicated by Index1. The bridge port with the next MAC address is causing the conflict.

No special repair action required. Open or close the conflicted port manually if needed.

7330

(dupadr)

Index2 = Layer 2 forwarder ID (VLAN ID) Alarm type = QueueCounter (112); Index1 = ifIndex of physical line, Index2 = queue index 0

No defects

—

—

—

—

No defects

—

1

Packets dropped by queue exceed threshold

QoS

Min

SA

7302

The number of packets dropped by the queue exceeds the threshold.

Check the corresponding queue load.

The queue load exceeds the threshold.

Check the corresponding queue load.

7330

(queue-drop) 2

Queue load exceeds threshold

QoS

Min

SA

7302 7330

(queue-load) Alarm type = MEGACOMediaGateway (113); Index1 = slot ID of voice package server unit, Index2 = mediaGatewayId (identifier of the affected media gateway) 0

No defects

—

—

—

—

No defects

—

1

Media gateway controller unreachable (2)

Com

Crit

SA

7302

Contact is lost with the media gateway controller.

Check the network connections.

7330

Alarm type = MEGACOSignalingGateway (114); Index1 = slot ID of voice package server unit, Index2 = signallingGatewayId (identifier of the affected signalling gateway) 0

No defects

—

—

—

—

No defects

—

1

Signalling gateway controller unreachable (2)

Com

Crit

SA

7302

Contact is lost with the signalling gateway controller.

Check the network connections.

7330

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

No defects

—

—

—

—

No defects

—

1

LT unit unreachable from server card (2)

Com

Crit

SA

7302

The LT unit cannot be reached.

Check the interface between the voice package server unit and the VoIP units.

LT unit already associated (2)

Com

The LT unit is associated with another voice package server unit.

No action required.

2

7330

War

SA

7302 7330

(32 of 34)

TAP 104-34




Alarm name (CLI)

Class

Sev.

SA

3

Invalid LT unit CDE file (2)

Proc

Maj

SA

NE type

Description


7302

The CDE file in the card is invalid. This alarm is raised in the following situations:

Download the correct card CDE again.

7330

• • 4

5

CDE download to LT unit failure (2)

LT unit type mismatch

Proc

Maj

SA

7302 7330

Equip

Maj

SA

(2)

7302 7330

The CDE file does not exist. The CDE file is of invalid format.

The download of the card software to an LT unit did not succeed.

Lock or unlock the VoIP unit.

An LT unit is detected, but the actual unit type is unknown or differs from the planned unit type.

Check the configuration of the provisioned card against the configuration of the equipped card.

Reset the VoIP unit. The card software is automatically downloaded to the LT unit.

Alarm type = MEGACOTermination (116); Index1 = slot or equipment ID of voice package server unit (3), Index2 = accTerminationUserPortId (identifier of the user port) 0

No defects

—

—

—

—

No defects

—

1

Unknown media gateway controller subscriber (2)

Com

Crit

SA

7302

A subscriber profile is defined in the voice package server unit but not in the media gateway controller.

Check the user port identification.

Voice port ground key

Equip

The current threshold for the physical line of the port was exceeded. The usual causes are:

Perform a line test.

2

7330

Crit

SA

(2)

7302 7330

• • • 3

4

Voice port high temperature (2)

Equip

L1 activation failure (2)

Equip

Crit

SA

7302 7330

Crit

SA

7302 7330

5

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

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.


(33 of 34)


TAP 104-35



Alarm name (CLI)

Class

Sev.

SA

6

Line showering (2)

Com

Crit

SA

NE type

Description


7302

One of the lines assigned to a subscriber is connected to another subscriber.

Check the subscriber line connections.

7330

Alarm type = MEGACOSignalingLt (117); Index1 = slot ID of voice package server unit, Index2 = not used 0

No defects

—

—

—

—

No defects

—

1

Invalid gateway CDE file (2)

Proc

Crit

SA

7302

The card software file does not exist or is in an invalid format.

Download the correct CDE file for the voice package server unit again.

Voice signaling card — persistent data loss

Equip

The voice package server unit has lost all persistent data after restart. The card is not configured.

Reconfigure the system.

The voice package server unit has reached a 90% full level.

Delete the unused data on the voice package server unit.

The voice package server unit is not able to activate the last downloaded database.

Download the database again.

2

7330 Crit

SA

7330

(2)

3

4

7302

Voice signaling card — disk 90% full (2)

Equip

Voice signaling card — implicit database rollback (2)

Proc

Maj

SA

7302 7330

Maj

SA

7302 7330

Download the correct database.

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

This alarm cannot be viewed using CLI.

(3)

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 NE type

Alarm (grouped by alarm type) (1) No.

Name (CLI)

Class

Sev.

Description


SA

Alarm type = LANX (51); Index1 = not used, Index2 = not used 0 1

—

—

—

—

—

No defects

—

SHub fan failure

Eqp

Maj

NSA

—

SHub fan failure.

—

(fan) 2


SHub power fan failure

Eqp

Maj

NSA

—

SHub database restore (db-restore)

—


(power-fan) 3

SHub power fan failure.

Eqp

Maj

SA

7302 7330

The SHub database restore has failed.

Check local flash. Check remote file system. Check availability of MIB database.

(1 of 4)

TAP 104-36




Name (CLI)

Class

Sev.

SA

4

Emergency reboot

Eqp

Maj

NSA

(reboot)

5

SHub SNTP Communication Lost

NE type

Description


7302

The SHub has rebooted from the emergency boot package.

Check local flash.

SHub SNTP communication lost. The SNTP server does not respond to the requested messages from the SHub.

Check SNTP server.

An ARP request has been sent for a statistically configured next hop, but no ARP reply has been received in the specified time interval.

Check existence of configured Nexthop.

7330

Eqp

Maj

NSA

7302 7330

(sntp-comm)

6

No ARP reply received for next IP hop

Com

Maj

SA

7302 7330

(no-arp-reply)

Check remote file system. Check availability of software package.

Check connection with configured Nexthop.

Index1 = VRF ID Index2 = IP address of next hop Report mode = disabled Alarm type = ethLanx (52); Index1 = port identification of SHub Ethernet port, Index2 = see specific alarm number 0

—

—

—

—

—

No defects

—

1

Ethernet link down

Com

Crit

SA

7302

The Ethernet link is down.

Check the Ethernet link.

7330

Index2 = not used.

—

The Ethernet frame has been discarded due to buffer overflow.

(ether-link-down) 2

Ethernet frame discarded

QoS

Min

SA

—

Index2 = not used This alarm is not currently supported by the system. 3

SHub MAC conflict

COM

Min

SA

(mac-conflict)

7302 7330

Duplicate MAC address from Ethernet port of LAN switch. Index1 = port with the later coming MAC address that causes conflict.

No special repair action required. The conflict MAC address can be manually prohibited or permitted if needed.

Index2 = VLAN ID of domain on which the conflict happened. 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)


TAP 104-37


NE type


Name (CLI)

Class

Sev.

Description


SA

Alarm type = OSPF (69); Index1 = VRF-ID (VRF unique ID), Index2 = see specific alarm number 0

—

—

—

—

—

No defects

—

1

OSPF interface configuration error

Com

Min

NSA

7302

Received a packet with:

7330

•

Check the configuration of the OSPF and OSPF interface.

(ospf-itf-err)

• • • • •

OSPF version mismatch area mismatch (area ID or subnet ID not matching) netmask mismatch hello interval mismatch dead interval mismatch options mismatch

Check the configuration on the IP interface. Check the OSPF hello packets received on the OSPF interface.

Index2 = interface index 2

OSPF interface authentication error

Com

Min

NSA

7302


7330

•

(ospf-auth-err)

•

3

OSPF interface received bad packet

Com

Crit

SA

7302 7330

(ospf-rx-bad-err) 4

OSPF LSDB approaching overflow

Com

Maj

NSA

7302 7330

(ospf-lsdb-oflow-90)

5

OSPF LSDB overflow

Com

Maj

NSA

(ospf-lsdb-oflow)

7302 7330

authentication type mismatch authentication failure

Check the authentication type and password configured on the OSPF area and the OSPF interface.

Index2 = interface index

Check the authentication time range.

Received a packet that cannot be parsed. Index2 = interface index

Check the connection between the RIP interface and the cable.

The external LSA database has reached 90% of the external LSA limit.

Do not input external routes anymore, except for major external network routes.

Index2 = LSDB limit (percentage utilized)

Configure the OSPF area as a stub area if possible.

The external LSA count has reached the external LSA overflow limit.

Remove some external routes in the OSPF domain.

Index2 = LSDB limit (percentage used)

Configure the OSPF area as a stub area if possible. Only input major external network routes.

6

OSPF neighbor state change (ospf-nhbr-statchg)

Com

Min

SA

7302 7330

An OSPF neighbor connection is newly established or dismantled.

Check the OSPF neighbor table.

•

Index2 = interface index (interface on which the neighbor was learned)

•

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




Name (CLI)

Class

Sev.

SA

7

OSPF interface state change

Com

Min

SA

NE type

Description


7302

The OSPF interface status has changed (the DR or BDR may have been changed according to this OSPF interface).

No special repair action required. Check and modify the OSPF interface parameters if desired to change the OSPF interface status.

7330

(ospf-itf-statchg)

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

Com

Min

SA

—

No defects

—

7302


7330

• •

Check the configuration of the RIP send and receive version.

(rip-config-err)

RIP version mismatch netmask mismatch

Check the configuration of the IP interface. Check the RIP request and update packets received on the interface.

2

RIP interface authentication error

Com

Min

SA

7302


7330

•

(rip-auth-fail)

• 3

RIP interface received bad packet (rip-rcv-bad-pkt)

Com

Min

SA

7302 7330

authentication type mismatch authentication failure

Received a packet that cannot be parsed

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.

Alarm type = LANXuplinkgroup (75); Index1 = uplink group number, Index2 = not used 0

—

—

—

—

—

No defects

—

1

SHub uplink group down

Equip

Maj

NSA

7302

The SHub uplink group is down.

Check the SHub uplink group.

7330

(uplink-down) (4 of 4) Notes (1) The report mode is not supported on the SHub alarms.

4



TAP 104-39


TAP 104-40


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


TNG 116 — Link Related Ethernet OAM (EFM OAM)


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


TNG 100-1

TNG 100 — Service installation

Forwarding Modes The system has the following forwarding modes:

•

•

• • •

•

TNG 100-2

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



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


TNG 100-3


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:

TNG 100-4

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.

2

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.



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

LT board (LIM)

MAC learning cannot be disabled

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 SHub is 16384. Once the maximum limit is reached new addresses are not learned and the packets are discarded.

Maximum number of MAC addresses that can be learned on a LIM is 1024.

Secure MAC learning rules are applicable to different port types

NA

Static MAC address can be configured. There is a limit of 25 static MAC entries.

Static MAC address can be configured

Default aging time: 300 s

Default aging time: 300 s

Aging time range: 10 to 1000000 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.


TNG 100-5


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


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


TNG 101-1


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

a logical flow type

2

two policer profiles (upstream, downstream)

3

one marker profile (for upstream)

4

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



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

Supported Markers

Supported Filters

Remarks

Generic

all

L2, L3

May be used for all logical flow types, mainly for test purposes. The system will silently ignore unsupported contents from this profile.

PVC

all

(L2, L3)

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.

802.1x session

all

-

Designates all frames on a bridge port that was opened via 802.1x authentication

PVC.VLAN

all

L2, L3

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.

(for cross-connect mode only)

PPP

all

L3

ISAM terminated PPP sessions can use this flow type

IP

all

L3

Designates frames on an IP interface. This can be used for both IPoE and IPoA IP-aware bridges.

(1 of 2)


TNG 101-3


Logical Flow Type

Supported Markers

Supported Filters

Remarks

IPoE VLAN CC

all

L2, L3

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.

PPPoE VLAN CC

single dot1p

L2

A cross-connect mode that transports PPP encapsulated frames.

PPPoA CC

single dot1p

-

All frames on a PVC where PPPoATM encapsulation is used and is cross-connected to a VLAN.

IPoE IBridge

all

L2, L3

All frames on a subscriber-side IBridge port, where encapsulation mode is IPoE.

PPPoE IBridge

single dot1p

L2

All frames on a subscriber-side IBridge port, where encapsulation mode is PPPoE.

PPPoA relay

single dot1p

-

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.

IPoE IP-aware Bridge

all

L3

All frames on an IP-aware bridge subscriber interface, using IPoE encapsulation

IPoA IP-aware Bridge

all

L3

All frames on an IP-aware bridge subscriber interface, using IP encapsulation directly over ATM.

(2 of 2)

To create a QoS Session profile via CLI, use the following command: > configure qos profile session log-flow-type

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



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

CBS

Result

CIR in HW

Description

10K

1600

16K

16K

Big tolerance due to SW conversion

100K

1600

104K

102K

300K

1600

305K

297K

500K

1600

506K

492K

800K

1600

690K

781K

Rate limited by modem in upstream

1000K

1600

690K

977K


1500K

1600

690K

1469K



TNG 101-5


Table TNG 101-3: Illustration Policer Error Packet length

DS

US

no policer

policer

no policer

policer

64

435

345

544

323

128

409

314

512

314

256

409

309

614

309

512

409

306

819

306

1024

819

305

491

305

1280

1023

304

614

303

1518

1214

304

729

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 committed-info-rate committedburst-size

TNG 101-6



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

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.


TNG 101-7


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

• • •

• •

TNG 101-8

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.



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

Y

-

-

-

Sets a single P-bit for upstream frames on the SAP. Recommended marker type for bridged mono-QoS SAPs.

singleDscp

-

Y

-

Y

Sets a single DSCP value for upstream frames. Alignment is optional.

dscpContract

-

-

Y

Y

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.

dot1PandDscp

Y

Y

-

-

Sets a single DSCP and P-bit for all upstream frames of a SAP. Recommended marker for mono-QoS routed SAPs or IPoE CC.

dot1PandDscp

Y

-

Y

-

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.

-

-

-

Y

Accepts incoming DSCP values and set P-bits accordingly, to be used in the L2-part of the access network.

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.


TNG 101-9


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

L3 Filter

MAC Destination Address

Address Type

MAC DA Prefix

IP Destination Address

MAC Source Address

IP DA Prefix

MAC SA Prefix

IP Source Address

Ethertype

IP SA Prefix

P-bits

DSCP

CFI bit

Protocol Type

VLAN ID

Destination Port Range Source Port Range

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



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 don’t 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.


TNG 101-11


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



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

Global Table

DSCP to P-bits alignment

QoS Marker profile

Set P and DSCP for Yes subflow if specified

QoS Marker profile

Port default DSCP Yes

Alignment enabled?

Filter match?

(4)

(3)

QoS Marker profile

QoS Session profile Policy List

Yes, port default

May come from: 1. Bridge port default 2. VLAN default 3. QoS Session Profile Marker Port default P-bits No Yes, (1) trusted Tagged?

No, (2) trusted DSCP set? DSCP contract table

Yes, contract

QoS Marker profile

P-bit contract table

Yes, untrusted

Choose from factory defaults No QoS Marker involvement

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

untagged frames from user, where a port default P-bit is always applied

2

tagged or priority tagged frames, where subscriber marking is trusted

3

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


TNG 101-13


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



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

1..4 Qos Policy Table

QoS Marker Profiles

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


TNG 101-15


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, let’s 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



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.

2

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.


TNG 101-17


TNG 101-18


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


TNG 102-1


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



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

Description

Range

Default

max-num-group

Maximum number of groups supported by the system in enough bandwidth

0..4096

4096

max-num-uncfg

Maximum number of unconfigured groups supported by the system in enough bandwidth

0..128

64

cfg-res-time

Time to reserve the unused configured groups

0..2147483647

125

uncfg-res-time

Time to reserve the unused unconfigured groups

0..2147483647

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.


TNG 102-3


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



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

Description

show igmp system

Show all the IGMP system-related parameters

show igmp channel counter (port)

Show the IGMP channel counter details

show igmp channel miscellaneous (port)

Show the IGMP channel source details

show igmp channel protocol (port)

Show the IGMP protocol statistics for an IGMP channel

show igmp package-to-src (package-id)

Show the IGMP package to multicast source parameters

show igmp grp-to-package (mcast-addr)

Show the IGMP group to package parameters

show igmp module-mcast-src (slot) mcast-addr

Show the distribution of statistic information maintained by IGMP channels

show igmp module counter (slot-index)

Show the IGMP Module counters

show igmp module time (slot-index)

Show the time-related parameters of the IGMP module

show igmp module miscellaneous (slot-index)

Show miscellaneous parameters of the IGMP module

show igmp shub vlan-router-port (vlan-id) network-port

Show the status of the IGMP VLAN router ports

show igmp shub igs-stats (vlan-id)

Show the IGMP protocol statistics for the SHub

show igmp shub system-stats

Show the CAC system-related parameters and statistics

show igmp shub mcast-stats (src) vlan-id ip-addr

Show the CAC multicast-related channel statistics

show igmp shub bundle-stats (bundle-name)

Show the CAC multicast-related bundle statistics

show igmp shub bundle-to-src (bundle-name) class-d-addr vlan-id

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.


TNG 102-5


TNG 102-6


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 subscriber’s 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.


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: DA: 02.00.40.00.00.80 VL AN: 100 User: 00.b0.d0.bc. d5.d3

VBAS Resp User: MAC: 00.b0.d0.bc. d5.d3 Slot: 2 Port: 23 VLAN: 100

TNG 103-2


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


TNG 104-1


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

TNG 104-2

Parameter

Description

Relaying

When enabled, the relay agent is active

Server

When enabled, the relay agent forwards the packets to a specific DHCP server

Server IP

Address of the DHCP server to which the packets are to be forwarded

secs-threshold/hops-threshold

Thresholds for DHCP realy agent



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.


TNG 104-3


TNG 104-4


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.


TNG 105-1


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

TNG 105-2

The system selects the database that is compatible with and linked to the Enabled/NotActive OSWP among the available databases.



2

The system starts the activation procedure of the NotActive OSWP.

3

When the activation of the NotActive OSWP is successful, the system has two OSWPs.

The previously NotActive OSWP is now active together with the selected compatible database. The previously Active OSWP is still available but its status is now Enabled/NotActive.

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.

2

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.


TNG 105-3


TNG 105-4


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.


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



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

Available links

SFP number on faceplate

SFP to be cabled to

GENC

14 links:

4...17

rack/shelf/slot

• • • NCNC-B

6 links:

• NCNC-C

NCNC-E

2...7

SPFs 2 to 7 are configurable (up/down)

12 links:

• •

2...13

SPFs 2 to 7 are configurable (up/down) SFPs 8 to 13 are downlinks

6 links:

•

2...7

SPFs 2 to 7 are configurable (up/down)

12 links:

• • NCNC-D

SPFs 4 and 5 are uplinks SPFs 6 and 7 are configurable (up/down) SFPs 8 to 17 are downlinks

2...13

SPFs 2 to 7 are configurable (up/down) SFPs 8 to 13 are downlinks


TNG 106-3


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



Table TNG 106-2: ES slot designations for CLI Slot type

ES slot content

Slot identifier to enter using CLI

GFC

PWIO-B card

—

ATI

SATU-A card

1

NT slot B (NTB)

Filler plate

—

NT slot A (NTA)

EDSE-A card

2

LT slot 4 (LT4)

Any supported LT unit

7

LT slot 3 (LT3)


6

LT slot 2 (LT2)


5

LT slot 1 (LT1)


4

LP slot 4 (LP4)

Matching applique for LT unit installed in LT4

—

LP slot 3 (LP3)


—

LP slot 2 (LP2)


—

LP slot 1 (LP1)


—

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


TNG 106-5


3

Configure the association between a host shelf SFP and a remote LT: configure equipment external-link-assign 10 remote 3/1/4

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


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


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

Far-End

(f)los

5 ± 1 sec

6 ± 1 sec

sef/rdi

5 ± 1 sec

6 ± 1 sec

(f)lom

60 ± 1 sec

60 ± 1 sec

(f)se

10 ± 1 sec

10 ± 1 sec

(f)ncd

15 ± 1 sec

17 ± 1 sec

(f)lcd

15 ± 1 sec

17 ± 1 sec

(f)npd/(f)lpd

15 ± 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



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


TNG 107-3


•

• •

• • • • • •

TNG 107-4

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



Table TNG 107-2: Operating modes Name

Operating Modes

Description

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.

Instances

Line

Values

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

-

Table TNG 107-3: Rate adaptation mode Name

Rate Adaptation Mode

Description

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

Line DS, US

Values

raModeManual raModeAtInit

Granularity & Unit

-


TNG 107-5


Table TNG 107-4: Target noise margin Name

Target Noise Margin

Description

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.

Instances

DS, US

Values

0..31

Granularity & Unit

0.1 dB

Table TNG 107-5: Minimum noise margin Name

Minimum Noise Margin

Description

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.

TNG 107-6

Instances

DS, US

Values

0..31

Granularity & Unit

0.1 dB



Table TNG 107-6: Maximum noise margin Name

Maximum Noise Margin

Description

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

DS, US

Values

0..51 and “NoMaximumNoiseMargin”

Granularity & Unit

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

Increase Output Power at peer modem

Minimum Noise Margin 0 dB Margin

Modem restarts if persistent in this region


TNG 107-7


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

RF Band Data

Description

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]

• • •

•

Granularity & Unit

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

-

Table TNG 107-9: Minimum bitrate Name

Minimum Bitrate

Description

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.

TNG 107-8

Instances

Bearer DS, US

Values

0..262143

Granularity & Unit

1 kbit/s



Table TNG 107-10: Maximum bitrate Name

Maximum Bitrate

Description

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

Bearer DS, US

Values

0..262143

Granularity & Unit

1 kbit/s

Table TNG 107-11: Rate adaptation ratio Name

Rate Adaptation Ratio

Description

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

Bearer DS, US

Values

0..100

Granularity & Unit

1%


TNG 107-9


Table TNG 107-12: Maximum interleaving delay Name

Maximum Interleaving Delay

Description

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

Minimum Impulse Noise Protection

Description

Specifies the minimum required impulse noise protection as a number of protected DMT symbols at PMD output (de-interleaver input).

Instances

Bearer DS, US

Values

0..16 DMT Symbols

Granularity & Unit

0.1 DMT symbol

Table TNG 107-14: Bonding mode Name

Bonding mode

Description

This parameter indicates if the line is part of a bonding group or not.

Instances

Line

Values

Enumeration

• •

Granularity & Unit

TNG 107-10

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.

-



Table TNG 107-15: DPBO shaping mode Name

DPBO shaping mode

Description

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

Line DS

Values

psdDpboOff psdDpboOn

Default

Off

Granularity & Unit

-

Table TNG 107-16: DPBO electrical length Name

DPBO electrical length

Description

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

Instances

Line DS

Values

0..255.9 dB

Default

0 dB

Granularity & Unit

0.1 dB

Table TNG 107-17: DPBO assumed exchange PSD mask Name

DPBO assumed exchange PSD mask

Description

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

Line DS

(1 of 2)


TNG 107-11


Values

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.

Default

0 dB

Granularity & Unit

Frequency: 1 kHz PSD: 0.1 dBm/Hz

(2 of 2)

Table TNG 107-18: Default PSD breakpoints Frequency (kHz)

PSD level (dBm/Hz)

0

-95

4

-95

4

-92.5

80

-72.5

138

-44.2

138

-36.5

1104

-36.5

1622

-46.5

2208

-47.8

2500

-59.4

3002

-80

3132

-95

30000

-95

Table TNG 107-19: DPBO cable model parameters “ABC” Name

DPBO cable model parameters “ABC”

Description

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.

Instances

Line DS

Values

-1..1.5 for all three DPBO Cable Model Parameters.

Default

[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

TNG 107-12



Table TNG 107-20: DPBO minimum and maximum frequency Name

DPBO minimum frequency, DPBO maximum frequency

Description

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

Line DS

Values

0..30000 kHz

Default

DPBO Minimum Frequency = 0 kHz DPBO Maximum Frequency = 30000 kHz

Granularity & Unit

1 kHz

Table TNG 107-21: DPBO minimum usable signal level Name

DPBO minimum usable signal level

Description

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

Line DS

Values

-140..0 dBm/Hz

Default

-127.5 dBm/Hz

Granularity & Unit

0.1 dBm/Hz

Table TNG 107-22: Mode independent custom PSD mask downstream Name

Mode independent custom PSD mask downstream

Description

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

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

(1 of 2)


TNG 107-13


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

Extra DPBO maximum usable frequency control (xDPBOMUFCTRL)

Description

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

Line DS

Values

0..255.9 dB Special value: “fromDPBOESEL”

Default

“fromDPBOESEL”

Granularity & Unit

0.1 dB

Table TNG 107-24: Extra DPBO remote side electrical length Name

Extra DPBO remote side electrical length (xDPBORSEL)

Description

If this xDPBORSEL configuration parameter is set different from 0dB it modifies the standard DPBO algorithm by adding an extra term, function of xDPBORSEL.

Instances

Line DS

Values

0..255.99 dB

Default

0 dB

Granularity & Unit

0.01 dB

Table TNG 107-25: Extra DPBO offset Name

Extra DPBO offset (xDPBOOffset)

Description

This xDPBOOffset configuration parameter modifies the standard DPBO algorithm by adding an offset of magnitude xDPBOOffset.

Instances

Line DS

(1 of 2)

TNG 107-14



Values

-256..255.9 dB

Default

0 dB

Granularity & Unit

0.01 dB

(2 of 2)

Table TNG 107-26: Maximum deviation from maximum interleaving delay Name

Maximum deviation from maximum interleaving delay

Description

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

unconstrained

Granularity & Unit

1 byte

Table TNG 107-27: Custom band plan Name

Custom Band Plan

Description

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

Instances

Line

Values

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)


TNG 107-15


Table TNG 107-28: Predefined band plan Name

Predefined Band Plan

Description

Specifies the type of Band Plan.

Instances

Line

Values

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

Maximum Number of Bands

Description

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.

TNG 107-16

Instances

Line

Values

“unlimited”, 2..8

Unit

Bands



Table TNG 107-30: Maximum usable frequency Name

Maximum Usable Frequency

Description

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

Line

Values

“unlimited”, 1104..30000 kHz

Unit

kHz

Table TNG 107-31: ADSL band mode Name

ADSL Band Mode

Description

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

ADSL Band Mode End Frequency

Description

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

Line

Values

0 kHz, 276..2208kHz

Granularity & Unit

1 kHz


TNG 107-17


Table TNG 107-33: Optional band mode Name

Optional Band Mode

Description

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

Line

Values

Off, Up or Down

Granularity & Unit

-

Table TNG 107-34: Optional band mode end frequency Name

Optional Band Mode End Frequency

Description

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.

TNG 107-18

Instances

Line

Values

0 kHz, 138..276 kHz

Granularity & Unit

1 kHz



Table TNG 107-35: US power backoff mode Name

US Power Backoff Mode

Description

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

Line US

Values

psdPboOff psdPboOn psdPboOnPolicingPassive psdPboOnPolicingShutdown psdPboOnPolicingUS0Only

Granularity & Unit

-


TNG 107-19


Table TNG 107-36: DS G.hs tones power mode Name

DS G.hs tones power mode

Description

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

Line

Values

{default; automatic; manual}

Granularity & Unit

-

Table TNG 107-37: Minimum PSD Floor Tone set “i”

Si

Si in conservative mode(1)

A43

TBD dBm/Hz

-65 dBm/Hz

B43

TBD dBm/Hz

-70 dBm/Hz

A43c

TBD dBm/Hz

-70 dBm/Hz

V43

TBD dBm/Hz

-70 dBm/Hz

Note (1)

TNG 107-20

Alcatel-Lucent will determine if the conservative mode will be used or not. This has to be hardcoded in the chipset implementation.



Table TNG 107-38: DS G.hs tones power manual level Name

DS G.hs tones power manual level

Description

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

Line

Values

-99..-40 dBm/Hz

Granularity & Unit

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

Modem Features

Description

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

Line

Values

Bitmap

Granularity & Unit

-


TNG 107-21


Table TNG 107-40: Maximum aggregate transmit power Name

Maximum Aggregate Transmit Power

Description

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:

•

•

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.

Instances

Line DS, US

Values

-31..25.5 dBm

Granularity & Unit

0.1 dBm

Table TNG 107-41: PSD ceiling Name

Maximum PSD (1)

Description

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

Line DS, US

Values

0..-95.5 dBm/Hz or “no_constraint”

Granularity & Unit

0.1 dBm/Hz

Note (1)

TNG 107-22

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.



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

Custom MIB PSD Mask

Description

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


TNG 107-23


Table TNG 107-44: US power backOff PSD mask selection Name

US Power BackOff PSD

Description

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:

• •

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:

• • • • Granularity & Unit

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)

TNG 107-24

This psdMask is outphasing



Table TNG 107-45: US power backOff PSD AB parameters Name

US Power BackOff PSD AB Parameters

Description

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

US Power BackOff (per upstream Bands)

Values

[40..80.95 dBm/Hz; 0..40.95 dBm/Hz]

Default

[For US0: 40 dBm/Hz; 0 dBm/Hz]

Granularity & Unit

0.01 dBm/Hz; 0.01 dBm/Hz

Table TNG 107-46: US power backoff PSD full custom parameters Name

US Power BackOff PSD Full Custom Parameters

Description

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

Limit Tx PSD Mask

Description

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)


TNG 107-25


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

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.

-

(2 of 2)

Table TNG 107-48: Fx band plan frequency

TNG 107-26

Name

Fx Band Plan Frequency

Description

Specifies Fx frequency in case of bandPlanC band plan, ignored otherwise.

Instances

Line

Values

3750..12000 kHz

Granularity & Unit

1 kHz



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

Limit Tx PSD Mask

Description

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

Line DS, US

Values

• •

•

•

Granularity & Unit

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 shouldn’t be misinterpreted as the G993.1 [4] AnnexC. It is also associated to the BandPlanAext band plan (see Band plan).

-


TNG 107-27


Table TNG 107-50: US Power Back-off electrical length override Name

US Power Back-off electrical length override

Description

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

Virtual Noise PSD

Description

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

Virtual Noise SNRM_MODE

Description

Selects the reference noise PSD that shall be considered when evaluating the noise margin.

Instances

US, DS

(1 of 2)

TNG 107-28



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

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.

-

(2 of 2)

Table TNG 107-53: Erasure detection in INP Name

Erasure detection in INP

Description

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.

Instances

Bearer US, DS

Values

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)


TNG 107-29


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:

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

TNG 107-30

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



Table TNG 107-54: Current operational mode Name

Current Operational Mode

Description

The operational mode used for the current operation of the VDSLx modem subsystem (see Operating modes).

Instances

Line

Values

See Operating modes. Only 1 bit can be set to 1 at a time.

Granularity & Unit

-

Initialization value

Defined during configuration and G.hs.

Update frequency

NA

Table TNG 107-55: Operational mode capabilities Name

Operational mode Capabilities

Description

The total set of operational modes supported by the VTU-O and the VTU-R respectively.

Instances

Near-end/Far-end

Values

See Operating modes.

Granularity & Unit

-

Update frequency

NA

Table TNG 107-56: SNR margin Name

SNR Margin

Description

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

Global DS/US for VDSLx, and per band for VDSL2 on top (including US0 band).

Values

-64..+63 dB

Granularity & Unit

0.1 dB

Update frequency

DS: each = 10 seconds via EOC @ VTU-O US: each < 10 seconds @ VTU-O


TNG 107-31


Table TNG 107-57: Loop attenuation Name

Loop Attenuation

Description

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

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

0.1 dB

Accuracy

0.5 dB

Update frequency

NA

Table TNG 107-58: Signal attenuation Name

Signal Attenuation

Description

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


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

Aggregate Output Power

Description

Actual aggregate output power (that is, the total output power for the carriers of the corresponding direction) when the modem is in showtime.

Instances

DS/US

Values

-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

0.1 dBm

(1 of 2)

TNG 107-32



Accuracy

1 dB (maximum admissible deviation with actual measured value)

Update frequency

DS: each bit swap US: each bit swap

(2 of 2)

Table TNG 107-60: Actual average PSD Name

Aggregate average PSD

Description

Actual Average (in dB) Transmit power spectrum density over the loaded subcarriers.

Instances

DS/US

Values

-95..0 dBm/Hz. A special value “Out of Range” indicates the parameter is out of range to be represented.

Granularity & Unit

0.1 dBm/Hz

Accuracy

0.1 dBm/Hz

Update frequency

DS/US: each bit swap

Table TNG 107-61: Last state transmitted Name

Last state transmitted

Description

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

DS (VTU-O)/US (VTU-R)

Values

0x0 -> 0xFF

Granularity & Unit

1

Update frequency

Not Applicable

Table TNG 107-62: Attainable line bitrate Name

Attainable Line Bitrate

Description

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

DS/US

(1 of 2)


TNG 107-33


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

Actual Line Bitrate

Description

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

DS/US

Values

0..262143

Granularity & Unit

1 kbps

Update frequency

NA

Table TNG 107-64: Line relative capacity occupation Name

Line Relative Capacity Occupation

Description

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

DS/US

Values

0..100%

Granularity & Unit

1%

Update frequency

DS: derived from Actual and Attainable Line Bitrate US: derived from Actual and Attainable Line Bitrate

TNG 107-34



Table TNG 107-65: Attainable transport bitrate (per bearer channel) Name

Attainable transport Bitrate

Description

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

Per bearer channel

Values

0..262143

Granularity & Unit

1 kbps

Update frequency

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

Actual transport Bitrate

Description

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

Per bearer channel

Values

0..262143

Granularity & Unit

1 kbps

Update frequency

NA

Table TNG 107-67: Actual interleaving delay (per bearer channel) Name

Actual Interleaving Delay

Description

Actual delay caused by the interleaving and coding functionality.

Instances

Per bearer channel

Values

0..63

Granularity & Unit

1 ms

Update frequency

NA


TNG 107-35


Table TNG 107-68: Actual impulse noise protection (per bearer channel) Name

Actual Impulse Noise Protection

Description

Actual value of the impulse noise protection offered by the interleaving and coding functionality.

Instances

Per bearer channel

Values

0..16 DMT symbols Note: Care should be taken to the Carrier Spacing (see also Actual tone spacing)

Granularity & Unit

0.1 DMT symbols

Update frequency

NA

Table TNG 107-69: Actual TPS-TC mode Name

Current TPS-TC Mode

Description

The TPS-TC layer mode used for the current operation of the VDSLx modem subsystem.

Instances

Per line

Values

Same bitmap as TPS-TC mode capabilities. Only 1 bit can be set to 1 at a time.

Granularity & Unit

-

Update frequency

NA

Table TNG 107-70: TPS-TC mode capabilities Name

TPS-TC Mode Capabilities

Description

The total set of TPS-TC modes supported by the VTU-O and the VTU-R respectively.

Instances

Line Near-end/Far-end

Values

Bitmap: TPSTCModesATMBit TPSTCModesPTM_64_65Bit TPSTCModesPTM_HDLCBit

TNG 107-36

Granularity & Unit

-

Update frequency

NA



Table TNG 107-71: Actual tone spacing Name

Current Tone Spacing

Description

DMT tone spacing currently used by the PMD layer.

Instances

DS/US

Values

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

0..127.5

Granularity & Unit

0.1 dB @ 1 MHz

Table TNG 107-73: Actual VTU-R timing advance Name

Actual VTU-R Timing Advance

Description

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

-250..+250

Granularity & Unit

10 ns

Accuracy

+/- 25 ns


TNG 107-37


Table TNG 107-74: Actual highest frequency used Name

Actual Highest Frequency used

Description

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

US/DS

Values

0..30000

Granularity & Unit

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

US/DS

Values

1, 2, 4, or 8.

Unit

Number of carriers

Table TNG 107-76: Actual maximum PSD Name

Actual Maximum PSD

Description

Actual Maximum Transmit power spectrum density over the loaded subcarriers.

Instances

US/DS

Values

-95..0 dBm/Hz A special value “Out of Range” indicates the parameter is out of range to be represented.

TNG 107-38

Granularity & Unit

0.1 dBm/Hz

Accuracy

0.1 dBm/Hz

Update frequency




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

VTU-O/VTU-R

Values

Three times 32 bits word: [W2, W1, W0], according to parameter description above.

Granularity & Unit

-

Table TNG 107-78: VDSL2 actual standard limit PSD Name

VDSL2 Actual Standard Limit PSD

Description

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

Line

Values

Three times 32 bits word: [W2, W1, W0], according to parameter description above.

Granularity & Unit

-

Table TNG 107-79: VDSL2 limit PSD mapping Annex

PSD

-

Invalid

-

Unknown

(1 of 2)


TNG 107-39


Annex

PSD

-

Other Annex

A

Unknown in Annex A

A

Other in Annex A

A

PSD mask for operation over POTS

A

PSD mask for all-digital mode operation

B

Unknown in Annex B

B

Other in Annex B

B

997-M1c-A-7

B

997-M1x-M-8

B

997-M1x-M

B

997-M2x-M-8

B

997-M2x-A

B

997-M2x-M

B

HPE17-M1-NUS0

B

HPE30-M1-NUS0

B

997E17-M2x-NUS0

B

997E30-M2x-NUS0

B

998-M1x-A

B

998-M1x-B

B

998-M1x-NUS0

B

998-M2x-A

B

998-M2x-M

B

998-M2x-B

B

998-M2x-NUS0

B

998E17-M2x-NUS0

B

998E17-M2x-NUS0-M

B

998ADE17-M2x-NUS0-M

B

998ADE17-M2x-A

B

998ADE17-M2x-B

B

998E30-M2x-NUS0

B

998E30-M2x-NUS0-M

B

998ADE30-M2x-NUS0-M

B

998ADE30-M2x-NUS0-A

C

Unknown in Annex C

C

Other in Annex C

C

PSD mask for operation above POTS

C

PSD mask for operation above TCMISDN

(2 of 2)

TNG 107-40



Table TNG 107-80: Actual DS virtual noise SNRM_MODE Name

Actual DS Virtual Noise SNRM_MODE

Description

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

DS

Values

SNRM_MODE1, SNRM_MODE2

Granularity & Unit

-

Table TNG 107-81: Actual use of Trellis Coding Name

Actual Use of Trellis Coding

Description

Indicates the actual use of Trellis coding.

Instances

DS/US

Values

0: Not used 1: Used

Granularity & Unit

Boolean.

Table TNG 107-82: Actual used cyclic extension Name

Actual Used Cyclic Extension

Description

Indicates the actual cyclic extension used on the line (in showtime).

Instances

Line

Values

2, 3, 4, 5, …, 16.

Granularity & Unit

Unit of N/32 samples, where 2*N is the IFFT size.


TNG 107-41


Table TNG 107-83: Actual framing parameters Name

Actual Framing Parameters

Description

Indicates the following actual used framing parameters, per bearer. and linked to the latency path that carries that bearer:

• • • • •

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

Instances

Per bearer channel

Values

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

TNG 107-42

See “Values”.




TNG 107-43


TNG 107-44


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


TNG 108-1


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


Far-End

(f)los

5 ± 1 sec

6 ± 1 sec

sef/rdi

5 ± 1 sec

6 ± 1 sec

(f)lom

60 ± 1 sec

60 ± 1 sec

(f)se

10 ± 1 sec

10 ± 1 sec

(f)ncd

15 ± 1 sec

17 ± 1 sec

(f)lcd

15 ± 1 sec

17 ± 1 sec

(f)npd/(f)lpd

15 ± 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



Supported span operation configuration parameters The SHDSL Modem Subsystem accepts the configuration parameters listed hereunder. Based on the required levels, the required modem reaction on each parameter is:

• •

•

•

In case a parameter is indicated as “optional”, the input value is don’t care, and any value is accepted without having impact on the modem subsystem behavior. In case a parameter is indicated to be required to a certain level (for example, only limited set of defined number of input values), only input values corresponding to the required level are accepted. If the input parameter is not accepted, the modem subsystem raises a failure indication to the xDSL Manager indicating “Configuration Error” In case extra consistency checks need to be performed on a parameter or between parameters and the configuration should be rejected, 'rejection' always means that the modem subsystem raises a failure indication to the SHDSL Manager indicating “Configuration Error”, rather that a returned error of the considered SHDSL API call. An SHDSL API configuration request is replied with an error only when the call is done in a wrong administrative state.

The SHDSLx Modem Subsystem allows that the configuration can be independently set on individual line basis. M-pair (1 < M < 4) stands for a multiple-pair operation over SHDSL span for some applications having higher data rate requirements for end users.


TNG 108-3


Four-wire mode is identical to M-pair mode with M = 2, except for the method of assigning ordinal numbers to the wire pairs.

•

•

• • •

• •

TNG 108-4

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.



Operating Modes Table TNG 108-1 describes the operating modes parameter. Table TNG 108-2: Operating Modes Name

Operating Modes

Description

Specifies which operational protocol/standard are applicable for a span:

• • • •

(1) ATM-Native (2) ATM-IMA (ATM Forum) (3) PTM-64/65B (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 line’s operational mode are independent to the other lines, with exception of M-pair mode which requires all lines belong to a M-pair configuration in the same operational mode. Operational modes are not exchanged by G.hs. 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

Span

Values

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

Number of Repeaters

Description

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.

Instances

Span

(1 of 2)


TNG 108-5


Values

0-8

Granularity & Unit

1

(2 of 2)

Spectral Profile Table TNG 108-3 describes the spectral profile parameter. Table TNG 108-4: Spectral Profile Name

SHDSL Spectral Profile

Description

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

Span

Values

symmetricProfile asymmetricProfile

Granularity & Unit

-

Wire Mode Table TNG 108-4 describes the wire mode parameter. Table TNG 108-5: Wire Mode Name

Wire Mode

Description

Specifies whether 2-Wire or 4-Wire or 6-Wire or 8-Wire operation is in place. The supported wire mode depend on the actual lines of modem ASIC. IMA is not supported over M-pair links. The modem rejects the configuration and raise the “Configuration error” activation failure in the following scenarios:

• • Instances

No wire mode is selected (or no STU-C supported mode is selected) IMA operational mode is selected for multi-wire operation

Span

(1 of 2)

TNG 108-6



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

Managed from STU-R

Description

Specifies whether the STU-R initiated management flow is enabled/disabled by the STU-C.

Instances

Span

Values

disabled enabled

Granularity & Unit

-

Regional Setting Table TNG 108-6 describes the regional setting parameter. Table TNG 108-7: Regional Setting Name

Regional Setting

Description

Specifies the regional setting for the SHDSL line per the ITU-T G.992.1 Annexes (Annex A/F and Annex B/G).

• •

Region 1 - G.991.2 Annex A/F Region 2 - G.991.2 Annex B/G

Only a single setting (region 1 or region 2) can be provisioned. In Asymmetric Spectral Profile Mode, the regional setting cannot be modified. The modem rejects the configuration and raises the “Configuration error” activation failure in the following scenarios:

• •

No region is selected (or no STU-C supported region is selected) Region 1 and region 2 are selected together

Instances

Span

Values

BitMap: Bit

Granularity & Unit

Setting

---

---------

0

Region 1

1

Region 2

-


TNG 108-7


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

Minimum Requested Data Rate

Description

Defines the minimum requested transport payload bitrate which shall be set up and which shall be maintained during showtime by the STU. When line probe is enabled, the SHDSL line is probed for levels between this rate and the maximum requested data rate. The Line will not be activated at a lower rate. Only ATM/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

TNG 108-8

64 kbit/s * M (pair number)



Table TNG 108-9: Maximum Bitrate Name

Maximum Bitrate

Description

Specifies the maximum requested SHDSL data rate which can range from 192 to 5696 kb/s in Two Wire mode, plus the rate of 2312; and from 384 to 11.392 kb/s in FourWire mode; from 576 to 17,088 kb/s in SixWire mode; from 768 to 22.784 kb/s in EightWire mode The SHDSL line is probed for levels between this rate and the minimum requested data rate. The Line will not be activated at a higher rate. Only the ATM/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)


TNG 108-9


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

Worst Case Downstream Target Noise Margin

Description

Specifies the Target Margin in the Downstream direction, relative to the reference Worst Case, to be used during handshake and line-probe procedure in gauging a Bit Error Rate (BER) better than 1E-7. Target margin is used by the receiver to determine if a data rate can be supported with this margin under current noise measured during line probe and/or reference worst-case noise specified in Annexes A and B. A data rate may be included in the capabilities list resulting from line probe only if the estimated Signal-to-Noise Ratio (SNR) associated with that data rate minus the SNR required for BER = 1E-7 is greater than or equal to the target margin in dB. If both worst-case target margin and current-condition target margin are specified, then the capabilities exchanged shall be the intersection of data rates calculated using each noise condition separately. The use of negative target margins with respect to reference worst-case noise corresponds to reference noise with fewer disturbers. This may be applicable when the number of disturbers is known to be substantially fewer than specified by the reference worst-case noise. Use of negative target margins with respect to current conditions is not advised. Use of the current-condition target margin mode may result in retrains if the noise environment changes significantly. The negotiation of the target margins is done as follows: The target margins to be used by both the STU-C and the STU-R for determining the supported data rates are under the control of the STU-C. In the PMMS parameter exchange, the STU-C shall set the upstream and downstream PMMS target margins to identical values. This does not imply that the worst-case and current-conditions target margins are the same. To determine which data rates the STU-C can support, the STU-C can choose to use the upstream PMMS target margin transmitted by the STU-R in the PMMS parameter exchange, or the STU-C may choose to use an alternative internal value for the PMMS target margins. The STU-R shall use the downstream PMMS target margin parameters sent by the STU-C for determining which data rates the STU-R can support. This procedure is applicable to both the current-condition and the worst-case target margins. In M-pair operation, the same Downstream Target Noise Margin is used on all pairs. A value of -11 indicates not to use the Worst Case method in the downstream direction.

TNG 108-10

Instances

Span

Values

-11to 10

Granularity & Unit

1 dB



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

Current Case Downstream Target Noise Margin

Description

Specifies the Target Margin in the Downstream direction, relative to the Current noise conditions, to be used during handshake and line-probe procedure in gauging a BER better than 1E-7. Target margin is used by the receiver to determine if a data rate can be supported with this margin under current noise measured during line probe and/or reference worst-case noise specified in Annexes A and B. A data rate may be included in the capabilities list resulting from line probe only if the estimated SNR associated with that data rate minus the SNR required for BER = 1E-7 is greater than or equal to the target margin in dB. If both worst-case target margin and current-condition target margin are specified, then the capabilities exchanged shall be the intersection of data rates calculated using each noise condition separately. The use of negative target margins with respect to reference worst-case noise corresponds to reference noise with fewer disturbers. This may be applicable when the number of disturbers is known to be substantially fewer than specified by the reference worst-case noise. Use of negative target margins with respect to current conditions is not advised. Use of the current-condition target margin mode may result in retrains if the noise environment changes significantly. The negotiation of the target margins is done as follows: The target margins to be used by both the STU-C and the STU-R for determining the supported data rates are under the control of the STU-C. In the PMMS parameter exchange, the STU-C shall set the upstream and downstream PMMS target margins to identical values. This does not imply that the worst-case and current-conditions target margins are the same. To determine which data rates the STU-C can support, the STU-C can choose to use the upstream PMMS target margin transmitted by the STU-R in the PMMS parameter exchange, or the STU-C may choose to use an alternative internal value for the PMMS target margins. The STU-R shall use the downstream PMMS target margin parameters sent by the STU-C for determining which data rates the STU-R can support. This procedure is applicable to both the current-condition and the worst-case target margins. In M-pair operation, the same Downstream Target Noise Margin is used on all pairs. A value of -11 indicates not to use the Worst Case method in the downstream direction.

Instances

Span

Values

-11to 10

Granularity & Unit

1 dB


TNG 108-11


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

Worst Case Upstream Target Noise Margin

Description

Specifies the Target Margin in the Upstream direction, relative to the reference Worst Case, to be used during handshake and line-probe procedure in gauging a BER better than 1E-7. Target margin is used by the receiver to determine if a data rate can be supported with this margin under current noise measured during line probe and/or reference worst-case noise specified in Annexes A and B. A data rate may be included in the capabilities list resulting from line probe only if the estimated SNR associated with that data rate minus the SNR required for BER = 1E-7 is greater than or equal to the target margin in dB. If both worst-case target margin and current-condition target margin are specified, then the capabilities exchanged shall be the intersection of data rates calculated using each noise condition separately. The use of negative target margins with respect to reference worst-case noise corresponds to reference noise with fewer disturbers. This may be applicable when the number of disturbers is known to be substantially fewer than specified by the reference worst-case noise. Use of negative target margins with respect to current conditions is not advised. Use of the current-condition target margin mode may result in retrains if the noise environment changes significantly. The negotiation of the target margins is done as follows: The target margins to be used by both the STU-C and the STU-R for determining the supported data rates are under the control of the STU-C. In the PMMS parameter exchange, the STU-C shall set the upstream and downstream PMMS target margins to identical values. This does not imply that the worst-case and current-conditions target margins are the same. To determine which data rates the STU-C can support, the STU-C can choose to use the upstream PMMS target margin transmitted by the STU-R in the PMMS parameter exchange, or the STU-C may choose to use an alternative internal value for the PMMS target margins. The STU-R shall use the downstream PMMS target margin parameters sent by the STU-C for determining which data rates the STU-R can support. This procedure is applicable to both the current-condition and the worst-case target margins. In M-pair operation, the same Downstream Target Noise Margin is used on all pairs. A value of -11 indicates not to use the Worst Case method in the downstream direction.

TNG 108-12

Instances

Span

Values

-11to 10

Granularity & Unit

1 dB



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

Current Case Upstream Target Noise Margin

Description

Specifies the Target Margin in the Upstream direction, relative to the Current noise conditions, to be used during handshake and line-probe procedure in gauging a BER better than 1E-7. Target margin is used by the receiver to determine if a data rate can be supported with this margin under current noise measured during line probe and/or reference worst-case noise specified in Annexes A and B. A data rate may be included in the capabilities list resulting from line probe only if the estimated SNR associated with that data rate minus the SNR required for BER = 1E-7 is greater than or equal to the target margin in dB. If both worst-case target margin and current-condition target margin are specified, then the capabilities exchanged shall be the intersection of data rates calculated using each noise condition separately. The use of negative target margins with respect to reference worst-case noise corresponds to reference noise with fewer disturbers. This may be applicable when the number of disturbers is known to be substantially fewer than specified by the reference worst-case noise. Use of negative target margins with respect to current conditions is not advised. Use of the current-condition target margin mode may result in retrains if the noise environment changes significantly. The negotiation of the target margins is done as follows: The target margins to be used by both the STU-C and the STU-R for determining the supported data rates are under the control of the STU-C. In the PMMS parameter exchange, the STU-C shall set the upstream and downstream PMMS target margins to identical values. This does not imply that the worst-case and current-conditions target margins are the same. To determine which data rates the STU-C can support, the STU-C can choose to use the upstream PMMS target margin transmitted by the STU-R in the PMMS parameter exchange, or the STU-C may choose to use an alternative internal value for the PMMS target margins. The STU-R shall use the downstream PMMS target margin parameters sent by the STU-C for determining which data rates the STU-R can support. This procedure is applicable to both the current-condition and the worst-case target margins. In M-pair operation, the same Downstream Target Noise Margin is used on all pairs. A value of -11 indicates not to use the Worst Case method in the downstream direction.

Instances

Span

Values

-11to 10

Granularity & Unit

1 dB


TNG 108-13


Line Probe Enable Table TNG 108-14 describes the line probe enable parameter. Table TNG 108-14: Line Probe Enable Name

Line Probe Enable

Description

Specifies support for Line Probe (rate adaptation) of the units in a SHDSL line. When Line Probe is enabled, the system performs Line Probing to find the best possible rate. If Line probe is disabled, the rate adaptation phase is skipped to shorten set up time.

Instances

Span

Values

disabled enabled

Granularity & Unit

TNG 108-14



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

Loop Attenuation Threshold

Description

Specifies the Loop Attenuation Threshold Value in dBs, for generated associated alarms. A value of 0 disables alarm generation.

Instances

Unit

Values

0-127

Granularity & Unit

1 dB

SNR Margin Threshold Table TNG 108-16 describes the SNR margin threshold parameter. Table TNG 108-16: SNR Margin Threshold Name

SNR Margin Threshold

Description

Specifies the SNR Margin Threshold Value in dBs, for generated associated alarms. A value of 0 disables alarm generation.

Instances

Unit

Values

0-15

Granularity & Unit

1 dB

Loopback Timeout Table TNG 108-17 describes the loopback timeout parameter. Table TNG 108-17: Loopback Timeout Name

Loopback Timeout

Description

Specifies the Loopback Timeout duration in minutes. A value of 0 disables timeout.

Instances

Unit

(1 of 2)


TNG 108-15


Values

0-4095

Granularity & Unit

1minute

(2 of 2)

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

Segment Termination

Values

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

Power Backoff Mode

Description

Specifies the Power Backoff rule at the associated Segment Termination.

Instances

Segment Termination

Values

Default Selected

Granularity & Unit

TNG 108-16

-



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

Span State

Description

Indicates the overall state of this SHDSL span

Instances

Span

Values

unknown unequipped faulty idle startup active

Granularity & Unit

-

(1 of 2)


TNG 108-17



“Idle”

Showtime value:

“Active”

Update frequency

NA

(2 of 2)

TNG 108-18



Detected Units Table TNG 108-22 describes the detected units parameter. Table TNG 108-22: Detected Units Name

Detected Units

Description

Indicates the units that have been detected on this SHDSL span, bits are set(1) for detected units.

Instances

Span

Values

Bitmap: Bit

Unit

---

------

0

STU-C

1

STU-R

2

SRU-1

3

SRU-2

4

SRU-3

5

SRU-4

6

SRU-5

7

SRU-6

8

SRU-7

9

SRU-8

Granularity & Unit

-


NA

Showtime value:

Derived from EOC

Update frequency

NA

Configured Units Table TNG 108-23 describes the configured units parameter. Table TNG 108-23: Configured Units Name

Configured Units

Description

Indicates the units in the SHDSL span which have been successfully configured, bits are set (1) for units which have been successfully configured.

Instances

Span

Values

Bitmap: Bit

Unit

---

------

0

STU-C

1

STU-R

Granularity & Unit

-


NA

(1 of 2)


TNG 108-19


Showtime value:

Derived from EOC

Update frequency

NA

(2 of 2)

Span Status Table TNG 108-24 describes the span status parameter. Table TNG 108-24: Span Status Name

Span Status

Description

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.

TNG 108-20

Instances

Span

Values

Bitmap: Bit

Condition

---

---------

0

No Error

1

LOSW

2

Loop Attenuation Alarm

3

SNR Margin Alarm

4

DC Continuity Fault

5

Device Fault

6

Configuration Error

7

Loopback(s) Active

8

Non-Conform to STU-C Enable/Disable of STU-R Initiated Management Flow

9

ATM LCD/PTM LPD

10

Loss of Power

11

ATM NCD/PTM NPD

Granularity & Unit

-


NA

Showtime value:

Derived from EOC

Update frequency

NA



Wire Pair Assignment Table TNG 108-25 describes the wire pair assignment parameter. Table TNG 108-25: Wire Pair Assignment Name

Wire Pair Assignment

Description

Provides the correlation between the actual ports and their dynamic designation as fistPair and secondPair and thirdPair and fourthPair (if M>2 is supported) as a result of the pre-activation sequence in a modem ASIC. (firstPair is defined as the pair on which the final G.994.1 transaction is conducted) For 4-wire mode:

• •

00000100b: if the first port is the first pair, second port is the second pair 00000001b: if the second port is the first pair

6-wire mode examples:

• • •

00100100b: if the first port is the first pair, second port is the second pair, third port is the third pair 00010010b: if the second port is the first pair, third port is the second pair 00001001b: if the third port is the first pair, first port is the second pair

8-wire mode examples:

• • • •

11100100b: if the first port is the first pair, second port is the second pair, third port is the third pair, fourth port is the fourth pair 10010011b: if the second port is the first pair 01001110b: if the third port is the first pair 00111001b: if the fourth port is the first pair

Instances

Span

Values

Bitmap: Bit

Condition

---

---------

1,0 wirePair of the 1st modem ASIC port for 6/8-wire, 1st/3rd numbered port for 4-wire 3,2 wirePair of the 2nd modem ASIC port for 6/8-wire, 2nd/4th numbered port for 4-wire 5,4

wirePair of the 3rd modem ASIC port for 6/8-wire, set to 0 for 4-wire

7,6

wirePair of the 4th modem ASIC port for 8-wire, set to 0 for 4/6-wire

wirePair

value

----------

--------

1stPair

00

2ndPair

01

3rdPair

10

4thPair

11

Granularity & Unit

-


NA

Showtime value:

Derived from EOC

Update frequency

NA


TNG 108-21


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

Unit DC Powering

Description

Indicates whether this unit is powered locally, or derives power from the SHDSL span.

Instances

Unit

Values

LocalPowered spanPowered

TNG 108-22

Granularity & Unit

-


NA

Showtime value:

Derived from EOC

Update frequency

NA



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

Segment Termination Status

Description

Indicates any exception conditions active at this SHDSL segment termination

Instances

Segment Termination

Values

Bitmap: Bit

Condition

---

---------

0

No Error

1

LOSW

2

Loop Attenuation Alarm

3

SNR Margin Alarm

4

DC Continuity Fault

5

Device Fault

6

Configuration Error

7

Loopback(s) Active

8

Non-Conform to STU-C Enable/Disable of STU-R Initiated Management Flow

9

ATM LCD/PTM LPD

10

Loss of Power

11

ATM NCD/PTM NPD

Granularity & Unit

-


NA

Showtime value:

Derived from EOC

Update frequency

NA


TNG 108-23


Loopback State Table TNG 108-28 describes the loopback state parameter. Table TNG 108-28: Loopback State Name

Loopback State

Description

Indicates any loopback active at this SHDSL segment termination. In M-pair mode, the loopbacks can only be set-up and torn-down simultaneously on all pairs.

Instances

Segment Termination

Values

noLoopback normalLoopback specialLoopback

Granularity & Unit

-


noloopback

Showtime value:

Derived from EOC

Update frequency

NA

SNR Margin Table TNG 108-29 describes the SNR margin parameter. Table TNG 108-29: SNR Margin Name

SNR Margin

Description

Indicates the currently measured SNR Margin in dB at this SHDSL segment termination. A value of 127 indicates that this information is unavailable.

Instances

Segment Termination

Values

-128 to 127 dB

Granularity & Unit

1 dB

Accuracy

1 dB


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



Loop Attenuation Table TNG 108-30 describes the loop attenuation parameter. Table TNG 108-30: Loop Attenuation Name

Loop Attenuation

Description

Indicates the currently measured Loop Attenuation in dB at this SHDSL segment termination. A value of -128 indicates that this information is unavailable.

Instances

Segment Termination

Values

-128 to 127 dB

Granularity & Unit

1 dB

Accuracy

1 dB


US: Measured during initialization. DS: Not Available

Showtime value:

NA

Update frequency

NA

Power Backoff Level Table TNG 108-31 describes the power backoff level parameter. Table TNG 108-31: Power Backoff Level Name

Power Backoff Level

Description

Indicates the current Power Backoff value in dB at this SHDSL segment termination.

Instances

Segment Termination

Values

0 to 31 dB

Granularity & Unit

1 dB

Accuracy

1 dB



Showtime value:

NA

Update frequency

NA


TNG 108-25


Tip Ring Reversal Table TNG 108-32 describes the tip ring reversal parameter. Table TNG 108-32: Tip Ring Reversal Name

Tip Ring Reversal

Description

Indicates the current state of the Tip/Ring pair at this SHDSL segment termination.

Instances

Segment Termination

Values

normal reversed

Granularity & Unit

-

Accuracy

-



Showtime value:

NA

Update frequency

NA

Power Backoff Status Table TNG 108-33 describes the power backoff status parameter. Table TNG 108-33: Power Backoff Status Name

Power Backoff Status

Description

Indicates the Power Backoff status at this SHDSL segment termination. This value indicates the mode that will be selected at the next reset.

Instances

Segment Termination

Values

default selected

Granularity & Unit

-

Accuracy

-



TNG 108-26

Showtime value:

NA

Update frequency

NA


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.


TNG 109-1


Table TNG 109-1: Near-end line: related CLI commands Command

Description

show xdsl counters near-end line current-interval [ (if-index) ]

Displays xDSL counters of the near end line for the current 15 min interval

show xdsl counters near-end line current-1day [ (if-index) ]

Displays the xDSL counters of the near end line for the current day interval

show xdsl counters near-end line previous-interval [ (if-index) [ interval-no ] ]

Displays the xDSL counters of the near end line for a previous 15 min interval

show xdsl counters near-end line previous-1day [ (if-index) [ interval-no ] ]

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

Description

es

Errored Second count (ES) for upstream as per G.997.1 § 7.2.1.1.2

ses

Severely Errored Second count (SES) for upstream as per G.997.1 § 7.2.1.1.3

uas

Unavailable Second count (UAS) for upstream as per G.997.1 § 7.2.1.1.5

los

Loss Of Signal failure count (LOS) for upstream, counts the number of los failures as per DSL standard

lof

Loss Of Frame failure count (LOF) for upstream, counts the number of lof failures as per DSL standard

lom

Loss Of Margin failure count (LOM) for upstream, counts the number of lom failures as per DSL standard

ese

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

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

Failed-init count, as per G.997.1 § 7.2.1.3.2

ra-upshift

Rate Adaptation Upshift (RAU) for upstream, counts the number of rau anomalies as per DSL standard

ra-downshift

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



Table TNG 109-3: Far-end line: related CLI commands Command

Description

show xdsl counters far-end line current-interval [ (if-index) ]

Displays xDSL counters of the far end line for the current 15 min interval

show xdsl counters far-end line current-1day [ (if-index) ]

Displays the xDSL counters of the far end line for the current day interval

show xdsl counters far-end line previous-interval [ (if-index) [ interval-no ] ]

Displays the xDSL counters of the far end line for a previous 15 min interval

show xdsl counters far-end line previous-1day [ (if-index) [ interval-no ] ]

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

Description

es

Errored Second count (ES) for upstream as per G.997.1 § 7.2.1.1.2

ses

Severely Errored Second count (SES) for upstream as per G.997.1 § 7.2.1.1.3

uas

Unavailable Second count (UAS) for upstream as per G.997.1 § 7.2.1.1.5

los

Loss Of Signal failure count (LOS) for upstream, counts the number of los failures as per DSL standard

lof

Loss Of Frame failure count (LOF) for upstream, counts the number of lof failures as per DSL standard

lpr

Loss Of Power failure count (LPR), counts the number of far-end lpr failures as per DSL standard

lol

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

Loss Of Margin failure count (LOM) for upstream, counts the number of lom failures as per DSL standard

ese

Excessive Severe Error failure count (ESE) for upstream, counts the number of ese failures. An ese failure is raised after 10 contiguous SES.

ra-upshift

Rate Adaptation Upshift (RAU) for upstream, counts the number of rau anomalies as per DSL standard

ra-downshift

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.


TNG 109-3


Table TNG 109-5: Near-end channel: related CLI commands Command

Description

show xdsl counters near-end channel current-interval [ (if-index) ]

Displays xDSL counters of the near end channel for the current 15 min interval

show xdsl counters near-end channel current-1day [ (if-index) ]

Displays the xDSL counters of the near end channel for the current day interval

show xdsl counters near-end channel previous-interval [ (if-index) [ interval-no ] ]

Displays the xDSL counters of the near end channel for a previous 15 min interval

show xdsl counters near-end channel previous-1day [ (if-index) [ interval-no ] ]

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

Description

cv

Count of upstream Code Violations, i.e. incorrect CRC (CRC-8 anomalies) as per G.997.1 § 7.2.2.1.1

fecc

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

cec

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

Description

show xdsl counters far-end channel current-interval [ (if-index) ]

Displays xDSL counters of the far end channel for the current 15 min interval

show xdsl counters far-end channel current-1day [ (if-index) ]

Displays the xDSL counters of the far end channel for the current day interval

show xdsl counters far-end channel previous-interval [ (if-index) [ interval-no ] ]

Displays the xDSL counters of the far end channel for a previous 15 min interval

show xdsl counters far-end channel previous-1day [ (if-index) [ interval-no ] ]

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



Table TNG 109-8: PM counters for far-end channel Parameter Name

Description

cv

Count of downstream Code Violations, i.e. incorrect CRC (CRC-8 anomalies) as per G.997.1 § 7.2.2.1.1

fecc

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

cec

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

Description

admin ip shub arp-stats (vrf-id) (clear-statistics)

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

Description

Node level counters in-packets

Total number of ARP packets received on all interfaces. Includes packets that may have been discarded.

discard

Number of ARP packets that have been discarded because error checks have failed.

in-request

Number of incoming ARP requests that have been processed.

in-resp

Number of incoming ARP responses that have been processed.

out-request

Number of ARP requests that have been transmitted out.

out-resp

Number of ARP responses that have been transmitted out.

VRF level counters arp-discards


rx-arp-packets

Total number of ARP packets received on this vrf. Includes packets that may have been discarded.

(1 of 2)


TNG 109-5


Command

Description

rx-arp-req

Number of incoming ARP requests that have been processed.

rx-arp-rsp

Number of incoming ARP responses that have been processed.

tx-arp-req

Number of ARP requests that have been transmitted out.

tx-arp-rsp

Number of ARP responses that have been transmitted out.

invalid-op-code

Number of ARP packets discarded because the specified opcode is invalid.

unsupported-hw-type

Number of ARP packets discarded because the received ARP packet header specifies a HW type other than Ethernet.

unsupported-l3-proto

Number of ARP packets discarded because the received ARP packet specifies a L3 protocol type other than IP.

unsupported-addr-len

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.

invalid-src-mac

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.

invalid-user-mac

Number of ARP packets discarded because the specified source MAC addresses in the ARP packet header and Ethernet header are not in sync.

internal-ctxt-error

Number of ARP packets discarded because of internal software logic errors.

no-free-arp-entry

Number of ARP packets discarded because of ARP cache overflow.

(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

TNG 109-6

Command

Description

configure ip vrf (index) user-itf port (port-interface) [no] arp-proxy-stats

Allows the operator to enable or disable ARP detailed counters on a given user port.

admin ip arp-proxy-stats (user-port) (clear-statistics)

Allows the operator to clear the summary and detailed counters at any point in time.




Description

Summary counters error-summary


Detailed counters internal-ctxt-err

Number of ARP packets discarded because of internal software logic errors.

unsupported-hw-type

Number of ARP packets discarded because the received ARP packet header specifies a HW type other than Ethernet.

unsupported-l3-proto

Number of ARP packets discarded because the received ARP packet specifies a L3 protocol type other than IP.

unsupported-addr-len

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.

invalid-op-code

Number of ARP packets discarded because the specified packet opcode is invalid.

invalid-src-mac

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.

arp-cache-overflow

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.

unsupported-user-itf

Number of ARP packets discarded because the configured User interface is not supported. Only IPoE is supported.

invalid-target-ip

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.

invalid-src-ip

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.

unknown-user

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

identical-user-itf

Number of ARP packets discarded because of both sender and target IP addresses having been learnt on the same user interface.

unknown-target-ip

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:

• • •

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.

(1 of 2)


TNG 109-7


Command

Description

unsupported-probe-pkt

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.

req-rx-and-reply

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.

req-tx-and-reply

Number of all ARP Requests transmitted out on this user interface and responded by the User.

req-tx-no-reply

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.

req-tx-wait-reply

Number of all ARP Requests transmitted out on this user interface and for which the LT is currently in a pending state.

grat-rx-and-accept

Number of all ARP Gratuitous Requests that have been received by LT on this user interface and processed.

(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

Description

admin dhcp-relay shub vrf-agent-stats (vrf-id) (clear-statistics)

Allows the operator to clear the VRF counters at any point in time


Description

fwd-upstream

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.

fwd-downstream

Counter is incremented every time the DHCP relay agent transmits a DHCP message downstream towards the DHCP client (User).

rx-upstream

Number of DHCP messages received by the relay agent from LT/User.

rx-downstream

Number of DHCP messages received by the relay agent from network.

errors

Number of DHCP packets that were not forwarded by the relay agent and discarded.

(1 of 2)

TNG 109-8



Command

Description

internal-ctxt-err

Number of DHCP packets discarded because of internal software logic errors.

packet-expired

Number of DHCP request packets discarded because time stamp on the packet is less than the threshold time as configured on the relay agent.

malformed-packets

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.

too-many-hops

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.

dup-client-hw-addr

Number of DHCP packets discarded because the packet matches an existing context in the relay agent, but on a different port.

no-free-context

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.

upstr-invalid-giaddr

Number of DHCP request packets discarded because giaddr of incoming packet matches one of the interfaces' address in the VRF.

downstr-invalid-giaddr

Number of DHCP response packets discarded because DHCP reply does not contain SHub interface address as giaddr.

no-route-to-server

Number of DHCP packets discarded because route to the DHCP server could not be determined.

downstr-no-ctxt-found

Number of DHCP response packets discarded because the received DHCP reply could not be associated with any existing context.

invalid-packet-type

Number of DHCP packets discarded because the received packet does not contain a valid message type . The message type should be either BootRequest / BootReply.

invalid-hops

Number of DHCP request packets discarded because the giaddr in the received packt is zero while the hops count is non zero.

invalid-client-hw-addr

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.

(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


TNG 109-9


Table TNG 109-15: Related CLI commands Command

Description

configure dhcp-relay [no] port-stats (port-interface)

Allows the operator to enable or disable DHCP detailed counters on a given user port.

admin dhcp-relay port-stats (user-port) (clear-statistics)

Allows the operator to clear the summary and detailed counters at any point of time.


Description

Summary counters error-summary

Number of DHCP packets that have been discarded because error checks have failed.

Detailed counters internal-ctxt-err

Number of DHCP packets discarded because of internal software logic errors.

up-corrupt-pkt

Number of upstream DHCP packets dropped because of one of the following:

• • •

• •

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.

up-unsupp-l3-proto

Number of upstream DHCP packets dropped because the specified protocol version in the IP header is not IPv4.

up-large-pkt-discard

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.

up-frag-pkt-discard

Number of upstream DHCP packets discarded because the received DHCP packet is a fragmented IP packet. Fragmented packets are not handled.

(1 of 4)

TNG 109-10



Command

Description

up-malformed-option

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.

up-invalid-op-code

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.

up-not-allowed-pkt

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:

• •

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.

up-opt82-too-long

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.

up-not-trusted

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.

up-invalid-chaddr

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:

• • •

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.

up-invalid-giaddr

In case of DHCP session snooping, number of upstream DHCP packets discarded because of IP anti-spoofing failure for 'giaddr' field.

up-invalid-ciaddr

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

(2 of 4)


TNG 109-11


Command

Description

up-no-free-context

In case of DHCP session snooping, number of upstream DHCP packets discarded because no free context is available. Applicable constraints are as below:

• •

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.

up-no-assoc-context

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.

up-relay-agent-unsupp

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.

up-no-broadcast-vlan

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.

dn-not-trusted

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.

dn-invalid-yiaddr

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:

• • •

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.

dn-no-free-context

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.

option82-inserted

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.

(3 of 4)

TNG 109-12



Command

Description

option82-removed

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/VLan and the packet must have passed all the error checks.

active-snooped-session

Count of all the DHCP sessions that have been established on this port and are currently being snooped.

total-snooped-session

Count of all the DHCP sessions that have been established on this port and which are being or have been snooped.

(4 of 4)


TNG 109-13


TNG 109-14


TNG 110 — Configuration examples Introduction This TNG provides configuration examples for:

• • • • • •

Basic management connectivity Equipment planning DSL profile creation and assignment Basic data traffic Multicast 802.1x authentication

Both ADSL and VDSL port configuration examples are provided. Unless otherwise specified, the examples in this TNG apply to both the 7302 ISAM and 7330 ISAM FTTN.

Note — The examples in this TNG use the command repetition (also called ranging) feature of CLI. This feature can be used to execute a command over a group of ports. See the 7302 ISAM | 7330 ISAM FTTN CLI Commands document for more information about command repetition. Parameters for examples All of the examples in this TNG assume that the NE has the following settings.

• • • • • •

The name of the NE is ISAM-1. The NE has the following LT units: • two VDSL LT units, LT1 and LT2 • two multi-ADSL LT units, LT3 and LT4 The IP address of the NE is 192.168.1.1. The default gateway address (netmask) of the NE is 192.168.1.254. The management network is attached to port 1 of the NT unit. The management network is assigned to VLAN 4093.


TNG 110-1


Basic management connectivity This section shows an example of the steps required to configure the network connectivity of the NE for remote management using telnet. 1

Give the NE a name: configure system id ISAM-1

2

Enable single IP address mode. See the 7302 ISAM | 7330 ISAM FTTN System Description document for more information about single IP address mode. configure system single-public-ip

3

Set the IP address and default gateway address on the NE: configure system management host-ip-address manual:192.168.1.1/24 configure system management default-route 192.168.1.254

4

Configure the network management port on the NT unit: configure interface shub port 1 port-type network admin-status auto-up

5

Attach the management VLAN to the network management port on the NT unit: configure vlan shub id 4093 egress-port network:1

6

If the management network is untagged, configure the network management as untagged: configure vlan shub id 4093 untag-port network:1 configure bridge shub port 1 pvid 4093

7


You can now manage the NE remotely using telnet.

Equipment planning This section shows an example of the steps required to plan the equipment of an NE. This example assumes that the NE is a 7330 ISAM FTTN ARAM-D shelf with the following cards installed:

• • • •

GENC-E interface unit PWIO-B general facilities card two EVLT-A VDSL LT units (LT1 and LT2) with VPSC-D appliques two EBLT-C multi-ADSL LT units (LT3 and LT4) with HLPC-H appliques

The configuration procedure is as follows: 1

Plan the GENC-E: configure equipment slot 1/1/1 planned-type genc-e unlock

TNG 110-2



2

Plan the LT units:

Note — In CLI, LT1 is identified as 1/1/4, LT2 as 1/1/5, LT3 as 1/1/6, and LT4 as 1/1/7.

configure equipment slot 1/1/4 planned-type evlt-a unlock configure equipment slot 1/1/5 planned-type evlt-a unlock configure equipment slot 1/1/6 planned-type eblt-c unlock configure equipment slot 1/1/7 planned-type eblt-c unlock 3

Plan the PWIO-B and the appliques: configure equipment applique 1/1/2 planned-type pwio-b configure equipment applique 1/1/4 planned-type vpsc-d configure equipment applique 1/1/5 planned-type vpsc-d configure equipment applique 1/1/6 planned-type hlpc-h configure equipment applique 1/1/7 planned-type hlpc-h

4


The equipment is now planned and ready for further configuration.

DSL profile creation and assignment This section shows examples of the steps required to configure and assign profiles for multi-ADSL and VDSL service.

Configure and assign VDSL profiles: The configuration procedure is as follows: 1

Configure a VDSL spectrum profile. This profile is called g993_vdsl11 and supports only VDSL without upstream power backoff. configure xdsl spectrum-profile 1 name g9931_vdsl1 dis-etsi-dts dis-ansi-t1413 dis-g992-1-a dis-g992-1-b dis-g992-2-a dis-g992-3-a dis-g992-3-b dis-etsi-ts itu-g993-1

2

Configure the VDSL options for the profile, such as band plan and upstream power backoff mode: configure xdsl spectrum-profile 1 vdsl vdsl-band-plan band-plan-a4 optional-band up adsl-band allow-adsl max-agpowlev-down 145 max-agpowlev-up 145 psd-shape-down ansi-ftt-cab-m2 psd-shape-up ansi-ftt-cab-m2 pbo-mode-down rx-psd-shape-up ansi-a

3

Activate the spectrum profile: configure xdsl spectrum-profile 1 active


TNG 110-3


4

Configure a service profile for 25 Mb/s downstream and 3 Mb/s upstream service. The profile is called 25Mpbs_3Mbps. configure xdsl service-profile 1 name 25Mbs_3Mbps min-bitrate-down 32 min-bitrate-up 32 plan-bitrate-down 512 plan-bitrate-up 512 max-bitrate-down 25024 max-bitrate-up 3008 max-delay-down 8 max-delay-up 8 imp-noise-prot-dn 10 imp-noise-prot-up 10

5

Activate the service profile: configure xdsl service-profile 1 active

6

Assign the spectrum and service profiles to the VDSL ports and put the ports in service:

•

7

For a single port, use the following command: configure xdsl line 1/1/4/1 service-profile 1 spectrum-profile 1 admin-up • For a range of ports, use the following commands: configure xdsl line 1/1/4/[1...24] service-profile 1 spectrum-profile 1 admin-up configure xdsl line 1/1/5/[1...24] service-profile 1 spectrum-profile 1 admin-up STOP. This procedure is complete.

If all the physical connections are made, you can now train a VDSL modem on LT1 and LT2.

Configure and assign multi-ADSL profiles: The configuration procedure is as follows: 1

Configure a spectrum profile. The profile is called multi_adsl and supports ADSL, ADSL2, READSL, and ADSL2+. configure xdsl spectrum-profile 2 name multi_adsl g992-3-l1 g992-3-l2 g992-3-am g992-5-a

2

Activate the spectrum profile: configure xdsl spectrum-profile 2 active

3

Configure a service profile for 15 Mb/s downstream and 1 Mb/s upstream service. The profile is called 15Mpbs_1Mbps and has minimum delay and impulse noise protection configured. configure xdsl service-profile 2 name 15Mbps_1Mbps min-bitrate-down 32 min-bitrate-up 32 plan-bitrate-down 1024 plan-bitrate-up 256 max-bitrate-down 15360 max-bitrate-up 1024 max-delay-down 1 max-delay-up 1 imp-noise-prot-dn 0 imp-noise-prot-up 0

4

Activate the service profile: configure xdsl service-profile 2 active

TNG 110-4



5

Assign the spectrum and service profiles to the multi-ADSL ports and put the ports in service:

•

6

For a single port, use the following command: configure xdsl line 1/1/6/1 service-profile 2 spectrum-profile 2 admin-up • For a range of ports, use the following commands: configure xdsl line 1/1/6/[1...48] service-profile 2 spectrum-profile 2 admin-up configure xdsl line 1/1/7/[1...48] service-profile 2 spectrum-profile 2 admin-up STOP. This procedure is complete.

If all the physical connections are made, you can now train a multi-ADSL modem on LT3 and LT4.

Basic data traffic This section shows examples of the steps required to configure a basic data service using the iBridge and cross-connect VLAN models. To configure basic data traffic, you must:

• •

configure the VLANs assign bridge ports to the VLANs; this step assigns a VLAN ID and a PVID to each bridge port.

The following parameters must be defined for each port:

• • •

vlan-id; the vlan-id parameter makes the port a member of the VLAN so traffic can flow through the system pvid; the pvid parameter is used to place the untagged Ethernet frames from the xDSL port into the correct VLAN; by default, all traffic is sent toward the end user with no VLAN tag max-unicast-mac; the max-unicast-max parameter limits the number of devices that can be active on a bridge port

Configure basic data traffic for the iBridge VLAN model The iBridge model, also known as residential bridging mode, allows multiple DSL ports to belong to the same VLAN. iBridge VLANs also enforce some rules regarding user-to-user communication within the shelf and broadcast message control. See the 7302 ISAM / 7330 ISAM FTTN System Description document for more detailed information about iBridge VLANs. This example assumes that the NE has the following settings.

• • •

The data traffic is carried on network port 2. The VDSL ports, LT1 and LT2, are connected to VLAN 101. The multi-ADSL ports, LT3 and LT4, are connected to VLAN 102.


TNG 110-5


Note — Multi-ADSL and VDSL ports can be members of the same VLAN. In this example, they are part of separate VLANs for the sake of clarity. The configuration procedure is as follows: 1

Configure the data traffic network port: configure interface shub port 2 port-type network admin-status up

2

Create the VDSL and multi-ADSL VLANs on the SHub: configure vlan shub id 101 mode residential-bridge configure vlan shub id 102 mode residential-bridge

3

Assign the data traffic and VDSL ports to VLAN 101 on the SHub. This ensures the traffic is bridged from the network port to the appropriate VDSL LT unit. configure vlan shub id 101 egress-port network:2 configure vlan shub id 101 egress-port lt:1/1/4 configure vlan shub id 101 egress-port lt:1/1/5

4

Assign the data traffic and multi-ADSL ports to VLAN 102 on the SHub. This ensures the traffic is bridged from the network port to the appropriate multi-ADSL LT unit. configure vlan shub id 102 egress-port network:2 configure vlan shub id 102 egress-port lt:1/1/6 configure vlan shub id 102 egress-port lt:1/1/7

5

Create the VLANs on the NT subsystem: configure vlan id 101 mode residential-bridge configure vlan id 102 mode residential-bridge

6

For each multi-ADSL port, create an ATM PVC that matches the PVC configured on the multi-ADSL modem. This step is not required for VDSL ports.

•

7

For a single port on each LT unit, use the following command: configure atm pvc 1/1/6/1:8:35 configure atm pvc 1/1/7/1:8:35 • For a range of ports on each LT unit, use the following commands: configure atm pvc 1/1/6/[1…48]:8:35 configure atm pvc 1/1/7/[1…48]:8:35 Create the bridge port for each xDSL port. You must specify a vpi:vci identifier for each multi-ADSL port. This step is not required for VDSL ports. configure bridge port 1/1/4/[1...24] configure bridge port 1/1/5/[1...24] configure bridge port 1/1/6/[1...48]:8:35 configure bridge port 1/1/7/[1...48]:8:35

TNG 110-6



8

Assign all VDSL ports to VLAN 101: configure bridge port 1/1/4/[1...24] vlan-id 101 configure bridge port 1/1/4/[1...24] pvid 101 max-unicast-mac 4 configure bridge port 1/1/5/[1...24] vlan-id 101 configure bridge port 1/1/5/[1...24] pvid 101 max-unicast-mac 4

9

Assign all multi-ADSL ports to VLAN 102: configure bridge port 1/1/6/[1...48]:8:35 vlan-id 102 configure bridge port 1/1/6/[1...48]:8:35 pvid 102 max-unicast-mac 4 configure bridge port 1/1/7/[1...48]:8:35 vlan-id 102 configure bridge port 1/1/7/[1...48]:8:35 pvid 102 max-unicast-mac 4

10 STOP. This procedure is complete. The system can now pass data traffic. Data traffic from the VDSL ports is carried out of the system on VLAN 101 and traffic from the multi-ADSL ports is carried out of the system on VLAN 102. Figure TNG 110-1 shows an example of the traffic flow from the network to the VDSL ports on LT1 for the iBridge VLAN model. Figure TNG 110-1: Example of traffic flow for iBridge VLAN model SHub VLAN 101 with egress ports to network and LT1

Bridge port mapping VLAN to VDSL ports on LT1

NT LT1

SHub 3 VLAN 101

2

It:1/1/4

BP

1

BP

24

CPE

VLAN 101

1

CPE Backplane connection between NT and LT

All ports members of same VLAN 101

VLAN tagged Ethernet Frames 18725

Configure basic data traffic for the cross-connect VLAN model The cross-connect model enforces a one-to-one mapping of VLANs to VDSL ports or to ATM PVCs. See the chapter on layer 2 forwarding in the 7302 ISAM / 7330 ISAM FTTN System Description document for more detailed information about cross-connect VLANs.


TNG 110-7


This example assumes that the NE has the following settings.

• •

The data traffic is carried on network port 2. The ports are connected as follows: • ports on VDSL LT unit LT1 are connected to VLANs 101 to 124. • ports on VDSL LT unit LT2 are connected to VLANs 201 to 224. • ports on multi-ADSL LT unit LT3 are connected to VLANs 301 to 348. • ports on multi-ADSL LT unit LT4 are connected to VLANs 401 to 448.


Configure the data traffic network port: configure interface shub port 2 port-type network admin-status up

2

Create the VDSL and multi-ADSL VLANs on the SHub: configure vlan shub id [101…124] mode cross-connect configure vlan shub id [201…224] mode cross-connect configure vlan shub id [301…348] mode cross-connect configure vlan shub id [401…448] mode cross-connect

3

Assign the data traffic and xDSL ports to the appropriate VLANs on the SHub. This ensures the traffic is bridged from the network port to the appropriate LT unit:

•

4

assign the VDSL ports on LT1 to VLANs 101 to 124: configure vlan shub id [101…124] egress-port configure vlan shub id [101…124] egress-port • assign the VDSL ports on LT2 to VLANs 201 to 224: configure vlan shub id [201…224] egress-port configure vlan shub id [201…224] egress-port • assign the multi-ADSL ports on LT3 to VLANs 301 to 348: configure vlan shub id [301…348] egress-port configure vlan shub id [301…348] egress-port • assign the multi-ADSL ports on LT4 to VLANs 401 to 448: configure vlan shub id [401…448] egress-port configure vlan shub id [401…448] egress-port Create the VLANs on the NT subsystem:

network:2 lt:1/1/4 network:2 lt:1/1/5 network:2 lt:1/1/6 network:2 lt:1/1/7

configure vlan id [101…124] mode cross-connect configure vlan id [201…224] mode cross-connect configure vlan id [301…348] mode cross-connect configure vlan id [401…448] mode cross-connect

TNG 110-8



5

For each multi-ADSL port, create an ATM PVC that matches the PVC configured on the multi-ADSL modem. This step is not required for VDSL ports.

•

6

For a single port on each LT unit, use the following commands: configure atm pvc 1/1/6/1:8:35 configure atm pvc 1/1/7/1:8:35 • For a range of ports on each LT unit, use the following commands: configure atm pvc 1/1/6/[1…48]:8:35 configure atm pvc 1/1/7/[1…48]:8:35 Create the bridge port for each xDSL port. You must specify a vpi:vci identifier for each multi-ADSL port. This step is not required for VDSL ports. configure bridge port 1/1/4/[1...24] configure bridge port 1/1/5/[1...24] configure bridge port 1/1/6/[1...48]:8:35 configure bridge port 1/1/7/[1...48]:8:35

7

Assign each VDSL port on LT1 to the corresponding VLAN: configure bridge port 1/1/4/1 vlan-id 101 configure bridge port 1/1/4/1 pvid 101 max-unicast-mac 4 configure bridge port 1/1/4/2 vlan-id 102 configure bridge port 1/1/4/2 pvid 102 max-unicast-mac 4 ... configure bridge port 1/1/4/23 vlan-id 123 configure bridge port 1/1/4/23 pvid 123 max-unicast-mac 4 configure bridge port 1/1/4/24 vlan-id 124 configure bridge port 1/1/4/24 pvid 124 max-unicast-mac 4

8

Assign each VDSL port on LT2 to the corresponding VLAN: configure bridge port 1/1/5/1 vlan-id 201 configure bridge port 1/1/5/1 pvid 201 max-unicast-mac 4 configure bridge port 1/1/5/2 vlan-id 202 configure bridge port 1/1/5/2 pvid 202 max-unicast-mac 4 ... configure bridge port 1/1/5/23 vlan-id 223 configure bridge port 1/1/5/23 pvid 223 max-unicast-mac 4 configure bridge port 1/1/5/24 vlan-id 224 configure bridge port 1/1/5/24 pvid 224 max-unicast-mac 4


TNG 110-9


9

Assign each multi-ADSL port on LT3 to the corresponding VLAN: configure bridge port 1/1/6/1:8:35 vlan-id 301 configure bridge port 1/1/6/1:8:35 pvid 301 max-unicast-mac 4 configure bridge port 1/1/6/2:8:35 vlan-id 302 configure bridge port 1/1/6/2:8:35 pvid 302 max-unicast-mac 4 ... configure bridge port 1/1/6/47:8:35 vlan-id 347 configure bridge port 1/1/6/47:8:35 pvid 347 max-unicast-mac 4 configure bridge port 1/1/6/48:8:35 vlan-id 348 configure bridge port 1/1/6/48:8:35 pvid 348 max-unicast-mac 4

10 Assign each multi-ADSL port on LT4 to the corresponding VLAN: configure bridge port 1/1/7/1:8:35 vlan-id 401 configure bridge port 1/1/7/1:8:35 pvid 401 max-unicast-mac 4 configure bridge port 1/1/7/2:8:35 vlan-id 402 configure bridge port 1/1/7/2:8:35 pvid 402 max-unicast-mac 4 ... configure bridge port 1/1/7/47:8:35 vlan-id 447 configure bridge port 1/1/7/47:8:35 pvid 447 max-unicast-mac 4 configure bridge port 1/1/7/48:8:35 vlan-id 448 configure bridge port 1/1/7/48:8:35 pvid 448 max-unicast-mac 4 11 STOP. This procedure is complete. The system can now pass data traffic. Data traffic from each xDSL port is carried out of the system on a separate VLAN. Figure TNG 110-1 shows an example of the traffic flow from the network to the VDSL ports on LT1 for the cross-connect VLAN model. Figure TNG 110-2: Example of traffic flow for cross-connect VLAN model

Bridge port mapping VLANs to VDSL ports on LT1

SHub VLANs 101 to 124 with egress ports to network and LT1 NT VLAN 101

SHub

VLAN 124

VLAN 101

3 2

VLAN101

LT1 BP

It:1/1/4

1 CPE

VLAN 124 BP

1

24 CPE

Backplane connection between NT and LT

VLAN 124

VLAN tagged Ethernet Frames 18726

TNG 110-10



Multicast This example shows one of the ways you can configure multicast for a 7302 ISAM or 7330 ISAM FTTN. Multicast is the transmission from a single device (such as an IPTV host) to a group of recipients (such as xDSL subscribers). See the 7302 ISAM / 7330 ISAM FTTN System Description document for more detailed information on multicast. This example assumes that the NE has the following settings.

•

• • • • •

The system is configured for basic data traffic using the cross-connect VLAN model. This configuration allows for all multicast traffic to be delivered to the NE on a single VLAN separate from the VLAN configured on the subscriber bridge port. The system then connects the subscriber to a multicast group and forwards it to the subscriber VLAN when the subscriber requests the group using IGMP. See the 7302 ISAM / 7330 ISAM FTTN System Description document for more detailed information about multicast and IGMP. All multicast traffic is delivered on network port 2, with a VLAN ID of 10. The multicast sources available to subscribers are 224.1.1.1 to 224.1.1.100. There is an IGMP router connected to the NE on network port 2. The NE is not required to restrict multicast connections based on bandwidth. The IP addresses used by the NE for IGMP messaging are: • toward the subscribers: 192.168.1.1 • toward the network: 10.10.10.1


Configure VLAN 10 on the SHub so that multicast traffic can be delivered to all LT units: configure vlan shub id 10 mode residential-bridge configure vlan shub id 10 egress-port network:2 configure vlan shub id 10 egress-port lt:1/1/[4…7]

2

Configure VLAN 10 on the NT subsystem: configure vlan id 10 mode residential-bridge

3

Configure the multicast source table on the NE. This table contains the list of all multicast groups available to subscribers and the corresponding VLAN group for each multicast group. configure mcast src 224.1.1.[1…100] vlan-id 10 atm-peak-bit-rate 0 atm-sus-bit-rate 0

4

Configure the system to disallow the joining of unconfigured multicast groups for iBridge subscribers: configure mcast general no package-member [1...1024] configure mcast capacity max-num-uncfg 0

5

Set the maximum number of unique groups that can be active on a single LT unit: configure mcast capacity max-num-group 256


TNG 110-11


6

Start the IGMP system and configure the IP address used for IP messaging toward the subscribers and the SHub. This address is not used for messaging toward the router. configure igmp system src-ip-address 192.168.1.1 start

7

Configure the VLAN IP address used for IGMP messaging toward the upstream router: configure interface shub vlan-id 10 admin-status down configure interface shub ip 10 ip-addr 10.10.10.1/24 configure interface shub vlan-id 10 admin-status up

8

Enable snooping on the SHub: configure igmp shub igs-system enable-snooping

9

Configure the port and VLAN ID connection for the router upstream of the NE: configure igmp shub vlan-router-port 10 network-port 2 query-timer 125

10 Disable the snooping filter on the multicast VLAN. This step enables snooping on the VLAN. configure igmp shub vlan-filter 10 no snoop-filter 11 Enable the snooping filter on the subscriber VLANs. This disables snooping on the VLANs, since there should be no IGMP on these VLANs. configure igmp shub vlan-filter [101…124] snoop-filter configure igmp shub vlan-filter [201…224] snoop-filter configure igmp shub vlan-filter [301…348] snoop-filter configure igmp shub vlan-filter [401…448] snoop-filter 12 Enable IGMP on the subscriber interface and limit the maximum number of multicast groups to which a subscriber can belong at any one time: configure igmp channel 1/1/4/[1...24] max-num-group 10 configure igmp channel 1/1/5/[1...24] max-num-group 10 configure igmp channel 1/1/6/[1...48]:8:35 max-num-group 10 configure igmp channel 1/1/7/[1...48]:8:35 max-num-group 10 13 STOP. This procedure is complete. Subscribers can now join configured multicast groups from xDSL ports using IGMP.

TNG 110-12



802.1x authentication This example shows how to set up 802.1x authentication. See the 7302 ISAM / 7330 ISAM FTTN System Description document for more detailed information about 802.1x authentication on a 7302 ISAM or 7330 ISAM FTTN. This example assumes that the NE has the following settings.

• • •

The system is configured for basic data traffic using the iBridge or cross-connect VLAN model. A RADIUS server is available upstream of the NE. The RADIUS server is configured as follows: • accessible over management VLAN 4093 • authentication server IP address is 192.168.2.22 • accounting server IP address is 192.168.2.23 • default domain is ALCATEL • NAS-ID for the NE is ISAM-1 • NAS-IP for the NE is 192.168.1.1


Configure the server used for authentication. The shared RADIUS secret key is mysecret. configure system security radius auth-server sampleAuth vrf-index 0 ip-address 192.168.2.22 secret mysecret

2

Configure the server used for accounting. The shared RADIUS secret key is mysecret. configure system security radius acc-server sampleAcc vrf-index 0 ip-address 192.168.2.23 secret mysecret

3

Configure a RADIUS policy for the NE specifying the NAS-ID and the NAS-IP: configure system security radius policy sampleRadPol nas-id ISAM-1 nas-ip-address 192.168.1.1

4

Configure the policy to use the authentication and accounting servers. These servers were created in steps 1 and 2. configure system security radius policy sampleRadPol servers 1 auth-server name:sampleAuth vrf-index-auth 0 priority 40 acc-server name:sampleAcc vrf-index-acc 0

5

Configure the domain used by the RADIUS policy: configure system security domain ALCATEL vrf-index -1 authenticator radius:sampleRadPol

6

Create a connection profile for the ALCATEL domain and configure handling of requests without a domain: configure system security conn-profile sampleConnProf version 1 domain-name ALCATEL no reject-no-domain reject-inv-domain

7

Configure the connection profile for the connection policy defined in step 6: configure system security conn-policy conn-profile-name sampleConnProf


TNG 110-13


8

Enable 802.1x authentication at the system level: configure system security pae port-access

9

Enable 802.1x authentication on each xDSL port: configure system security pae ext-authenticator 1/1/4/[1...24] authentication configure system security pae ext-authenticator 1/1/5/[1...24] authentication configure system security pae ext-authenticator 1/1/6/[1...48]:8:35 authentication configure system security pae ext-authenticator 1/1/7/[1...48]:8:35 authentication

10 STOP. This procedure is complete. The system can now authenticate xDSL ports using 802.1x toward the subscribers and RADIUS as the backend authentication server.

TNG 110-14


TNG 111 — 7330 ISAM FTTN ES configuration Purpose This TNG provides the steps to configure the 7330 ISAM FTTN ES.

General The ES must have at least one LT unit installed so the ES can be detected by the host shelf when the expansion link connections are made and the ES configuration is complete.

Note — Beginning with the Release 3.3 (Feature Group 3.4), ES VLAN configuration commands support multishelf notation. In previous releases, users were required to use single shelf notation when configuring an ES VLAN. Single shelf notation is still supported for backwards compatibility; for more information about configuring an ES VLAN using single shelf notation, consult an earlier version of this document.

Procedure Use this procedure to configure the ES. 1

Perform the initial configuration of the ES: configure system id systemname configure system management host-ip-address manual:hostIP configure system management default-route defaultgwaddress configure interface shub port shubport# port-type shubporttype admin-status adminstatus configure vlan shub id shubvlanid egress-port


TNG 111-1


network:networkport# configure vlan shub id shubvlanid untag-port network:networkport# configure bridge shub port networkport# pvid shubvlanid where systemname is the name of the ES hostIP is the IP address and mask of the host shelf, in the format xxx.xxx.xxx.xxx/yy defaultgwaddress is the IP address of the default gateway shubport# is the port number for the SHub; you can enter a single port number or a range of port numbers shubporttype is the type of SHub port adminstatus is the administrative status of the SHub port shubvlanid is the number of the SHub VLAN networkport# is the port number for the network; the network port number must match the SHub port number

Example: configure system id 7330-ES1 configure system management host-ip-address manual:138.120.217.171/24 configure system management default-route 138.120.217.1 configure interface shub port [1...5] port-type network admin-status auto-up configure vlan shub id 4093 egress-port network:1 configure vlan shub id 4093 untag-port network:1 configure bridge shub port 1 pvid 4093

2

Plan the ECNT-A and GENC-E or GENC-F cards on the host shelf: configure equipment slot 1/1/1 planned-type genc-e|genc-f unlock configure equipment slot nt-b planned-type ecnt-a unlock Example: configure equipment slot 1/1/1 planned-type genc-e unlock configure equipment slot nt-b planned-type ecnt-a unlock

3

Plan the ES: configure equipment shelf rack/shelf planned-type aram-d where rack is the rack number of the ES shelf is the shelf number of the ES

Example: configure equipment shelf 1/2 planned-type aram-d

TNG 111-2



4

Plan the EDSE-A and SATU-A cards on the ES: configure equipment slot rack/shelf/2 planned-type edse-a unlock configure equipment applique rack/shelf/2 planned-type satu-a where rack is the rack number of the ES shelf is the shelf number of the ES

Example: configure equipment slot 1/2/2 planned-type edse-a unlock configure equipment applique 1/2/2 planned-type satu-a

5

Plan the installed LT cards and appliques on the ES: configure equipment slot rack/shelf/slot planned-type LT unlock configure equipment applique rack/shelf/slot planned-type applique where rack is the rack number of the ES shelf is the shelf number of the ES slot is the slot number of the unit LT is the designation of the LT card applique is the designation of the applique

Example: configure equipment slot 1/2/4 planned-type eblt-c unlock configure equipment applique 1/2/4 planned-type hlpc-h

6

Configure the modem service profile: configure xdsl service-profile servprofile# name servprofilename local-profile configure xdsl service-profile servprofile# version version# min-bitrate-down minbrdown min-bitrate-up minbrup plan-bitrate-down planbrdown plan-bitrate-up planbrup max-bitrate-down maxbrdown max-bitrate-up maxbrup max-delay-down


TNG 111-3


maxbrdelaydown max-delay-up maxbrdelayup configure xdsl service-profile servprofile# active where servprofile# is the number of the service profile servprofilename is the name of the service profile version# is the version number of the service profile minbrdown is the minimum downstream bit rate minbrup is the minimum upstream bit rate planbrdown is the planned downstream bit rate planbrup is the planned upstream bit rate maxbrdown is the maximum downstream bit rate maxbrup is the maximum upstream bit rate maxbrdelaydown is the maximum downstream bit rate delay maxbrdelayup is maximum upstream bit rate delay

Example: configure xdsl service-profile 1 name xsrvc1 local-profile configure xdsl service-profile 1 version 1 min-bitrate-down 22500 min-bitrate-up 384 plan-bitrate-down 22500 plan-bitrate-up 784 max-bitrate-down 25000 max-bitrate-up 1500 max-delay-down 1 max-delay-up 1 configure xdsl service-profile 1 active

7

Configure the spectrum profile: configure xdsl spectrum-profile specprofile# name specprofilename local-profile version version# dis-etsi-dts dis-g992-1-b dis-g992-3-b g992-3-l1 g992-3-l2 g992-5-a max-noise-down maxnoisedown max-noise-up maxnoiseup rf-band-list rfbandlist configure xdsl spectrum-profile specprofile# active where specprofile# is the number of the spectrum profile specprofilename is the name of the spectrum profile version# is the version number of the spectrum profile maxnoisedown is the maximum downstream noise maxnoiseup is the maximum upstream noise rfbandlist is the RF band list

Example: configure xdsl spectrum-profile 1 name xlne1 local-profile version 1 dis-etsi-dts dis-g992-1-b dis-g992-3-b g992-3-l1 g992-3-l2 g992-5-a max-noise-down 100 max-noise-up 100 rf-band-list 07:12:07:d0:16:0d:ac:0e:d8:19:1b:58:1b:bc:19:27:74:27:a6:19 configure xdsl spectrum-profile 1 active

8

Configure a downlink port on the host shelf where the remote LT is connected: configure equipment external-link-assign sfpindex

TNG 111-4



no remote|remote rack/shelf/slot Where sfpindex is the number of the downlink port on the GENC-E or GENC-F card on the host shelf rack is the rack number of the ES shelf is the shelf number of the ES slot is the slot number of the LT unit

Example: configure equipment external-link-assign 8 remote 1/2/4

9

Configure the VLANs: configure vlan id sysvlanid mode residential-bridge configure vlan shub id shubvlanid mode residential-bridge configure vlan shub id shubvlanid egress-port network:networkport configure vlan shub id shubvlanid egress-port lt:rack/shelf/slot where sysvlanid is the number of the ES VLAN shubvlanid is the number of the SHub VLAN networkport is the port number for the network; the network port number must match one of the SHub port numbers shelf is the shelf number of the SHub slot is the slot number of the SHub port is the port number of the SHub

Example: configure vlan id 101 mode residential-bridge configure vlan shub id 101 mode residential-bridge configure vlan shub id 101 egress-port network:3 configure vlan shub id 101 egress-port lt:1/2/4

10

If one or more dual-mode ports are used to connect the GENC-E to the EDSE-A on the ES, configure the dual-mode ports as downlink ports: configure equipment external-link-host dualport# direction remote-lt where dualport# is the number of the dual-mode (6 or 7); you can enter a single port number or a range of port numbers

Example: configure equipment external-link-host [6...7] direction remote-lt

11

Train the modems: configure xdsl line rack/shelf/slot/port service-profile


TNG 111-5


servprofile# spectrum-profile specprofile# admin-up configure atm pvc rack/shelf/slot/port:vpi:vci configure bridge port rack/shelf/slot/port:vpi:vci configure bridge port rack/shelf/slot/port:vpi:vci vlan-id sysvlanid configure bridge port rack/shelf/slot/port:vpi:vci pvid sysvlanid no mac-learn-off max-unicast-mac macaddress where rack is the rack number of the ES shelf is the shelf number of the ES slot is the slot number of the xDSL line port is the port number of the xDSL line servprofile# is the number of the service profile specprofile# is the number of the spectrum profile vpi is the VPI number of the ATM PVC and bridge port vci is the VCI number of the ATM PVC and bridge port sysvlanid is the number of the ES VLAN macaddress is the unicast MAC address; you can enter a single address or a range of addresses

Example: configure xdsl line 1/2/4/1 service-profile 1 spectrum-profile 1 admin-up configure atm pvc 1/2/4/1:8:35 configure bridge port 1/2/4/1:8:35 configure bridge port 1/2/4/1:8:35 vlan-id 101 configure bridge port 1/2/4/1:8:35 pvid 101 no mac-learn-off max-unicast-mac 4

12

TNG 111-6



TNG 112 — 7330 ISAM FTTN configuration for subtending Purpose This TNG provides information about configuring a 7330 ISAM FTTN system in a subtended configuration.

General Subtending allows several 7330 ISAM FTTN nodes to be connected to the network through a single node. For more information about subtending, see the 7330 ISAM FTTN Product Information. Figure TNG 112-1 shows an example of subtended 7330 ISAM FTTN nodes.


TNG 112-1

TNG 112 — 7330 ISAM FTTN configuration for subtending

Figure TNG 112-1: 7330 ISAM FTTN subtending example VLAN associations: 4093 400 VLAN associations: 4093 200 400

Node #2 Traffic on VLAN 200

Network

VLAN associations: 4093 100 200 300 400


Subtended NE (subtending host: Node #2)

Node #1 Traffic on VLAN 100 VLAN associations: 4093 300


Subtended NEs (subtending host: Node #1) 18850

In this example:

• • • •

Node 1 is a subtending node to Node 2 and Node 3 Node 2 is subtended to Node 1 and is a subtending node to Node 4 Node 3 is subtended to Node 1 Node 4 is subtended to Node 2

The master subtending node, Node 1 in Figure TNG 112-1, receives the management and customer traffic from the network and distributes it to the appropriate node. Management traffic is sent to all nodes. Customer traffic is sent only to the appropriate node, which is determined by the VLAN associated with the customer traffic. In the example in Figure TNG 112-1, the customer traffic is distributed as follows.

• • • •

TNG 112-2

Customer traffic on VLAN 100 is sent to the LT units of Node 1. Customer traffic on VLAN 200 is sent to Node 2 via the appropriate subtending port. Node 2 then sends the customer traffic to its LT units. Customer traffic on VLAN 300 is sent to Node 3 via the appropriate subtending port. Node 3 then sends the customer traffic to its LT units. Customer traffic on VLAN 400 is sent to Node 2 via the appropriate subtending port. Node 2, the subtending node for Node 4, sends the customer traffic to Node 4 via the appropriate subtending port. Node 4 then sends the customer traffic to its LT units.



Configuring VLANs for subtending and subtended nodes This section shows how to configure VLANs on subtending and subtended nodes, using the example in Figure TNG 112-1. 1

For each node (Node 1, Node 2, Node 3, and Node 4), configure the network port and the SHub management VLAN. configure interface shub port 1 port-type network configure vlan shub id 4093 egress-port network:1

2

For each subtending node (Node 1 and Node 2), configure the management VLAN ID: configure bridge shub port 1 pvid 4093

3

For each node (Node 1, Node 2, Node 3, and Node 4), configure the VLAN associated with the node: configure vlan id 100 mode residential-bridge configure vlan shub id 100 egress-port network:1 configure vlan id 200 mode residential-bridge configure vlan shub id 200 egress-port network:1 configure vlan id 300 mode residential-bridge configure vlan shub id 300 egress-port network:1 configure vlan id 400 mode residential-bridge configure vlan shub id 400 egress-port network:1

4

For each node (Node 1, Node 2, Node 3, and Node 4), configure the egress ports associated to each VLAN: configure vlan shub id 100 egress-port lt:1/1/4 configure vlan shub id 200 egress-port lt:1/1/4 configure vlan shub id 300 egress-port lt:1/1/4 configure vlan shub id 400 egress-port lt:1/1/4


TNG 112-3


5

For each subtending node (Node 1 and Node 2), create and configure the VLAN associated with the nodes subtended to it: i

Node 1: configure vlan shub id 200 mode residential-bridge configure vlan shub id 200 egress-port network:1 configure vlan shub id 300 mode residential-bridge configure vlan shub id 300 egress-port network:1

ii

Node 2: configure vlan shub id 400 mode residential-bridge configure vlan shub id 400 egress-port network:1

6

For each subtending node (Node 1 and Node 2), configure the subtending ports for each subtending node: i

Node 1: configure interface shub port 3 port-type subtending configure vlan shub id 4093 egress-port network:3 configure vlan shub id 200 egress-port network:3 configure vlan shub id 300 egress-port network:3

ii

Node 2: configure interface shub port 3 port-type subtending configure vlan shub id 4093 egress-port network:3 configure vlan shub id 400 egress-port network:3

7

TNG 112-4



TNG 113 — Multi-ADSL parameters Introduction This TNG provides more information about the parameters used by the Multi-ADSL modem:

• •

•

Re-initialization triggers Multi-ADSL configuration management • Line operation configuration • Multi-ADSL common configuration parameters • Flavor-dependent configuration parameters • ADSL2plus-specific configuration parameters Supported operational data parameters


TNG 113-1

TNG 113 — Multi-ADSL parameters

Re-initialization triggers During showtime (L0 line state), the Multi-ADSL Modem Subsystem performs persistency/severity checking and correlation on the defects/anomalies, in order to detect re-initialization triggers. Table TNG 113-1 lists them for the ATU-C and includes the required persistency time for each showtime error. Table TNG 113-1: Re-initialization triggers Related Defect/Anomaly


Far-End

(f)los

5 ± 1 sec

6 ± 1 sec

sef/rdi

5 ± 1 sec

6 ± 1 sec

(f)lom

60 ± 1 sec

60 ± 1 sec

(f)se

10 ± 1 sec

10 ± 1 sec

(f)ncd

15 ± 1 sec

17 ± 1 sec

(f)lcd

15 ± 1 sec

17 ± 1 sec

(f)npd/(f)lpd

15 ± 1 sec

15 ± 1 sec

Note — All the triggers, except los and sef based triggers, make up the “high-ber-hs” condition, specified in G.992.3 ([6]), annex D. The Multi-ADSL modem subsystem implements correct state behavior as specified in the different standards, according to the actual operation mode, The Multi-ADSL 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 113-1. All the far-end countdown timers are frozen when any near-end defect occurs. When all the near-end defects have disappeared, the far-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.

Note — For ADSL2x standards, fese cannot be derived through IB-bits, instead Management Counters are used. As soon as the UAS counter is different from 0 in the FE Management Counters, and the CPE did not restart the line, the ATU-C shall force re-initialization.

TNG 113-2



Multi-ADSL configuration management

Line operation configuration The Multi-ADSL 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 Multi-ADSL modem subsystem allows the configuration to be independently set on individual line basis.


TNG 113-3


Multi-ADSL 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.

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

TNG 113-4

Operating modes Auto-mode criterion 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 L3 Power State Permission L2 Power State Permission L0 Time L2 Time L2 ATPR L2 Bitrate Downstream L2 ATPRT Bonding Mode BondingGroupId Upshift Noise Margin Downshift Noise Margin Minimum Time Interval for Upshift Rate Adaptation Minimum Time Interval for Downshift Rate Adaptation Artificial Noise PSD Impulse Noise Monitor (INM): • INM Sensitivity Threshold • INM Pulse-Gap-Bridging Value Warm Re-Init Disable Programmable Resynch Triggers



Table TNG 113-2: Operating modes Name

Operating Modes

Description

This parameter defines which standards are allowed for the Modem Subsystem for line activation. Different DSL standards can be allowed by the XDSL Manager. The Modem Subsystem does the following:

• •

check if allowed modes are not conflicting (see MGMT_R12), and raise an error if there is a conflict. if allowed modes are accepted, try to initialize with peerend modem in one of the allowed operation modes. Selection of best-fit mode shall be done according to MGMT_R13.

Instances

Line

Values

Bitmap: ANSI.T1.413 (1998) Alcatel-Lucent-proprietary ETSI mode G.992.1 Annex A & B, each overlapped & non-overlapped G.992.2 Annex A (non-overlapped) & B (overlapped) G.992.3 Annex A, B, I, J & L, M each overlapped & nonoverlapped G.992.4 Annex A & I, each overlapped & non-overlapped G.992.5 Annex A, B & I, M each overlapped & non-overlapped

Granularity & Unit

-

Table TNG 113-3: Auto-mode criterion Name

Auto-Mode Criterion

Description

This parameter shall be used to set the policy to select optimal operation mode in case READSL2 operation mode has been enabled. If no READSL2 operation mode has been set by the xDSL Manager, this parameter shall be ignored. Currently, three policies are defined:

• • •

0x0 : chipset proprietary criterion (full freedom) 0x1 : optimize DS bitrate with US bitrate above Minimum Bitrate. 0x2 : optimize US bitrate with DS bitrate above Minimum Bitrate.

The use of this parameter shall be as described in MGMT_R13. Instances

Line

Values

Bitmap: ANSI.T1.413 (1998) Alcatel-Lucent-proprietary ETSI mode G.992.1 Annex A & B, each overlapped & non-overlapped G.992.2 Annex A (non-overlapped) & B (overlapped) G.992.3 Annex A, B, I, J & L, M each overlapped & nonoverlapped G.992.4 Annex A & I, each overlapped & non-overlapped G.992.5 Annex A, B & I, M each overlapped & non-overlapped

Granularity & Unit

-


TNG 113-5


Table TNG 113-4: Rate adaptation mode Name

Rate Adaptation Mode

Description

Specifies the Rate Adaptive mode of operation:

•

•

•

RA mode 1 (‘manual’): The ATU initializes at the specified Minimum Bitrate, rounded according to MGMT_R14, with a noise margin of at least the specified Target Noise Margin and a BER better than 10-7 at 0 dB noise margin. During showtime, the ATU tries to maintain that bitrate with at least the specified Minimum Noise Margin. RA mode 2 (‘atInit’): The ATU 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 (see MGMT_R14 for applicable bitrate rounding rules). During showtime, the ATU shall try to maintain that bitrate with at least the specified Minimum Noise Margin. The modem optimizes the maximum net bit rate while meeting the quality requirements as specified by the operator (in particular the burst error correction capability). But it does not increase the net bit rate at the expense of the link quality. Description of the list of priorities is defined by requirement MGMT_R15. RA mode 3 (‘dynamic’): same as RA mode 2 during initialisation. Once the line is in showtime however, the bit rate can vary between a configured minimum and maximum bit rate. The rate adaptations shall occur in the following 2 cases: Upshift: the noise margin is above the upshift noise margin during a time equal to ‘minimum time interval for upshift rate adaptation’ Downshift: the noise margin is below the downshift noise margin during a time equal to ‘minimum time interval for downshift rate adaptation’ In both cases, the new bit rate has to be selected such that the noise margin becomes equal to the target margin unless the upper or lower bitrate boundary is reached. It is guaranteed that the SRA (RA mode 3) requests do not violate the service requirements and framing parameters (See ADSL2_R24.1 and ADSL2_R24.2) except for the PER restriction. This PER restriction can be violated if the CRCs are normalized (see section 7.9.1 in G.992.3). The normalization shall be executed in the Modem Subsystem.

Remarks: In case the CPE does not support SRA or if a line initializes in an XDSL flavour (f.i. ADSL1) which does not support SRA, RA mode 3 behavior shall be identical to RA mode 2. In state L2, no Downstream SRA bit rate change is allowed. Instances Values

Line DS, US RaModeManual RaModeAtInit RaModeDynamic

Granularity & Unit

TNG 113-6

-



Table TNG 113-5: Target noise margin Name

Target Noise Margin

Description

Specifies the required noise margin, relative to a BER of 10-7 (= 0 dB noise margin), the modem will achieve in order to successfully complete the initialization. This parameter is not used in showtime. When the modem cannot initialize at this margin, it fails. For DS, the parameter is passed to the ATU-R, it is the responsibility of the ATU-R to use this parameter correctly. For ADSL2x standards, all values between 0.0 and 31.0 can be passed, while for ADSL1x standards, only values 0 to 31 with 1 dB granularity can be passed. In that case, non-integer values shall be rounded to the nearest value of the standard

Instances

DS, US

Values

0.0..31.0

Granularity & Unit

0.1 dB

Table TNG 113-6: Minimum noise margin Name

Minimum Noise Margin

Description

Specifies the minimum noise margin, relative to a BER of 10-7 (= 0 dB noise margin), the modem shall tolerate in order to maintain showtime. This parameter is only used in showtime. For DS, the ATU-C regularly polls the actual DS noise margin to the ATU-R, and compares this value with the minimum noise margin. For both US and DS, the Multi-ADSL modem subsystem raises the lom (loss of margin) defect whenever the actual noise margin is below the Minimum Noise Margin. The Modem Subsystem raises failure indication "Configuration Error" for configurations where Minimum Noise Margin > Target Noise Margin for one of the directions. For ADSL2x standards, all values between 0.0 and 31.0 can be passed, while for ADSL1x standards, only values 0 to 31 with 1 dB granularity can be passed. In that case, non-integer values shall be rounded to the nearest value of the standard

Instances

DS, US

Values

0.0..31.0

Granularity & Unit

0.1 dB


TNG 113-7


Table TNG 113-7: Maximum noise margin Name

Maximum Noise Margin

Description

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

The special value 51.1 is interpreted as meaning that no Maximum Noise Margin limit must be applied. Other values strictly bigger than 31.0 are converted to t51.1 as well. Note 1: for DS, the parameter has to be passed to the ATU-R during initialization (C-Msg-1 or C-Msg-RA). For ADSL2x standards, all values between 0.0 and 31.0 plus 51.1 can be passed, while for ADSL1x standards, only values 0 to 31 with 1 dB granularity can be passed. In that case, non-integer values shall be rounded to the nearest value of the standard, while the special value 51.1 is translated to 31. It is up to the CPE to interpret this value as infinity or 31. Note 2: In ADSL1x, the average PSD may not change too much due to SYNC symbols, which cannot change PSD in showtime. Therefore, the showtime behavior is different than stated above : far-end output power shall only be varied within a 1.5 dB range with regard to the initial (that is, before the first bit swap) showtime output power. Instances

DS, US

Values

0..51.1

Granularity & Unit

0.1 dB

For clarification, Figure TNG 113-1 gives an overview of the noise margin parameters, and the required actions from the modem.

TNG 113-8



Figure TNG 113-1: Noise margin parameters

Reduce Output Power at peer modem Maximum Noise Margin Maximum Additional Noise Margin Target Noise Margin

Increase Output Power at peer modem

Minimum Noise Margin 0 dB Margin

Modem restarts if persistent in this region

Table TNG 113-8: Carrier mask Name

Carrier mask

Description

The Carrier Mask specifies the sub-carriers that can be used for data transport by the Modem Subsystem. There is one mask for each direction. A sub-carrier shall be “masked”, i.e. not used for data transport (bi=gi=0), when the XDSL manager has set the bit for that sub-carrier to “1”. The total number of carriers for which the mask is specified: 512 (carrier #0 to carrier #511). The usage of this information depends on the actual used operation mode:

•

•

ADSL1x : US : modem subsystem shall request no bits and no power on masked sub-carriers in bit loading process. DS : modem subsystem shall not transmit masked sub-carriers during medley signal. ADSL2x : US & DS : “masked” sub-carriers shall be indicated as “not supported” in G.hs CL messages.

Note 1: Besides respecting the carrier mask, the modem subsystem must also respect the standard band plans and configured PSD masks. This means that the fact that a sub-carrier is not masked in one direction does not necessarily mean that it can be used for data transmission in that direction. Note 2 : In ADSL1x operation modes, when carrier masking is applied, and modem initialization continuously fails, the masking may be suspected as cause for these init problems. Therefore, when conditions for activation failures CMP or CNF are met, the modem subsystem replaces them by CE activation failure if masking is applied on carriers between tone 60 and 100, and the selected operational mode is ADSL1x mode. Instances

US, DS

Values

Bitmap, 1 bit per sub-carrier, “1”= masked, “0” = not masked

Granularity & Unit

-


TNG 113-9


Table TNG 113-9: RF band data Name

RF Band Data

Description

Specifies the list of RF bands (HAM band or AM band) for egress control and ingress canceling. Egress requirements shall be used in ADSL2plus operation mode, but with some minor modifications (see Figure TNG 113-2): the modem subsystem shall determine all PSD points based on the RF band Start and Stop frequency given by the operator. For this it will take into account the PSD shape or Custom PSD shape parameters. 1. PSD(i+1), PSD5,PSD6 and PSD(i+4) to be determined by the modem based on ALA MIB "Custom Shape" parameter (MGMT_R11.2) (and the PSD shape (MGMT_R11.1) ) 2. PSD(i+2) = PSD(i+3) = -80 dBm/Hz fixed in ALA TRS(MGMT_R9.8) 3. t(i+2)= RFI_f_start and t(i+3)= RFI_f_stop as specified in ALA MIB "RF band" parameter (MGMT_R9.0) 4. t(i+1) and t(i+4) to be determined by the modem based on MIB specified "Custom Shape" parameter (MGMT_R11.2) and the PSD shape (MGMT_R11.1)) In other operation modes, egress control is optional. Ingress parameter is for information of the Multi-ADSL modem subsystem, usage for RFI canceling purposes is vendor discretionary. Egress control of up to 2 different RF bands simultaneously shall be supported. Any RF bands configured shall affect the PSD shape even if DPBO (see XXXX) is active.

Instances Values

Line Maximum 8 RF bands can be specified: RF band = [Start frequency, Stop frequency, RF type, Egress control, Ingress level]

• • • •

Frequency: 0 – 12000 kHz RF type: HAM band (rfHam) or AM band (rfAm) Egress control: PSD level is reduced below -80 dBm/Hz (egressNotched) or PSD notching is not required (egressNoControl) Ingress level: expected ingress level can be negligeable (ingressLow), weak (ingressWeak = at -30dBm @ LT / - 20dBm@NT ) or strong (ingressStrong = at -10dBm @LT / 0dBm@NT ).

From these 8 specified RF bands, only 2 are relevant for the spectra used by the different ADSLx operation modes (and especially ADSL2plus). All other bands will be specified for higher frequencies, typically in VDSL bands. The Modem Subsystem scans the complete set of RF bands, checks the start frequency for each band, and only considers the bands, which are in-band for the current operation mode. All other RF bands are ignored. When the number of RF bands to be considered is higher than the supported number of RF bands (min 2 for the spectra used by the different ADSLx operation modes ), the Modem Subsystem generates a “configuration error” towards the XDSL Manager. Granularity & Unit

TNG 113-10

-



Figure TNG 113-2: Restrictions on breakpoints and PSD mask for RFI band specification PSD in dBm/Hz Limitmask(f) < 33.5 dB

PSD(i+1)

< 33.5 dB

PSD5 PSD6 PSD(i+4)

slope < 1.5 dB/tone

slope < 1.5 dB/tone

PSD(i+2) PSD(i+3)

t(i+1)

t(i+2)

t(i+3) t(i+4)

Tone index

ALA MIB Custom Shape PSD mask(f) ALA Requirement for RF band PSD mask


TNG 113-11


Table TNG 113-10: Minimum bitrate Name

Minimum Bitrate

Description

Defines the minimum requested bitrate which will be set up and which will be maintained during showtime by the ATU. Rounding of bitrate parameters is as follows:

•

•

•

•

For ADSL1x: The Minimum Bitrate is rounded up and the Maximum Bitrate is rounded down according to the bitrate granularity (32 kbps) when for the corresponding direction Maximum Bitrate Minimum Bitrate after rounding. Otherwise, both bitrates are rounded up and Minimum Bitrate = Maximum Bitrate after rounding. In case of the current showtime makes use of s=0.5 in dowstream, the downstream bitrate granularity is 64 kbps instead of 32 kbps. For ADSL2: The accuracy of the bit rates parameters "net_max" and "net_min" passed in G.Hs have a granularity of 4kb/s. G9923_net_max = rounddown_to_next_4k ( G9971_maximum_datarate) G9923_net_min = roundup_to_next_4k ( G9971_minimum_datarate) For ADSL2plus: The accuracy of the bit rates parameters "net_max" and "net_min" passed in G.Hs have a granularity of 8kb/s. G9925_net_max = rounddown_to_next_8k (G9971_maximum_datarate) G9925_net_min = roundup_to_next_8k ( G9971_minimum_datarate) General If G992x_net_max < G992x_net_min then new G992x_net_max = G992x_net_min = highest of both In other words: in case of ADSL2 fixed rate (i.e. G9923_net_max=G9923_net_min), the value exchanged during the handshake can be up to 4kb/s above the user specified value and the actual bitrate value in showtime can be 8kb/s above the value exchanged during the handshake which means in G992.3 the actual rate can be up to 4kb/s+8kb/s=12 kb/s above the user configured value. For G992.5, the actual bitrate can be up to 8kb/S+8kb/s=16 kb/s above the user configured value.

The minimum supported data rate is be 32 kbps. Lower configured rates may be rounded to 32 kbps. Instances

Path DS, US

Values

0..65535

Granularity & Unit

1 kbit/s

Note (1)

TNG 113-12

In G.lite operating mode, supported bitrates are only up to 512 kbps US and up to 1500 kbps DS. When the minimum bitrate is configured above this limitation, and selected operation mode is G.lite, the Multi-ADSL modem subsystem might still try to activate at this higher bitrate. If however initializations continuously fail due to this minimum setting, the modem subsystem raises the activation failure "Configuration not feasible on line". At the same time, the Relative Capacity Occupation for the direction causing the problem is set to 100%.



Table TNG 113-11: Maximum bitrate Name

Maximum Bitrate

Description

Defines the maximum allowed transport bitrate which is set up and which is maintained during showtime by the ATU. This parameter is relevant only in 'atInit' RA Mode. For the rounding of bitrate parameters: see Table TNG 113-10. The Multi-ADSL 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.When RA Mode is ‘manual’, the Maximum Bitrate parameter will be ignored.

Instances

Bearer DS, US

Values

0..65535

Granularity & Unit

1 kbit/s

Table TNG 113-12: Rate adaptation ratio Name

Rate Adaptation Ratio

Description

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

Bearer DS, US

Values

0..100

Granularity & Unit

1%


TNG 113-13


Table TNG 113-13: Maximum interleaving delay Name

Maximum Interleaving Delay

Description

Specifies the maximum allowed delay introduced by the interleaving and deinterleaving function in the corresponding direction. This parameter puts a constraint the parameter PMS-TC delay, but is extended towards all Multi-ADSL standards. The Modem Subsystem selects FEC parameters such that SpxDp/4 < ILVDbc for the latency path carrying the specified bearer channel bc. If multiple bearer channels are carried over the same latency path, obviously the minimum of all Interleaving Delay limits constrains this latency path.

Instances Values

Bearer DS, US 0 - 63. All integer values between these borders shall be supported.

•

•

Granularity & Unit

TNG 113-14

Special Value 0 is used as "No delay bound" The value 0 indicates that the system chooses the optimal delay value as follows: The method used by the receiver to select data rates, power, overhead and latency is implementation dependent. However, within the raw data rate provided by the local PMD, the selected values will meet all the constraints communicated by the operator : - (message based) overhead data rate: Minimum overhead data rate - Net data rate: Minimum net data rate - Impulse Noise Protection: Minimum impulse noise protection for all bearer channels. - Delay: Maximum delay for all bearer channels. Within those constraints, the receiver selects the values to optimize the modem behavior as listed in the following priority order: 1. Maximize net data rate (within MaximumBitrate constraint). 2. Maximize SNR margin (within MaximumNoiseMargin constraint). 3. Minimize Power consumption. If within the given constraints, the modem is unable to select a set of operation parameters for one or both directions, the Modem Subsystem raises failure indication to XDSL Manager (“configuration not feasible on line”). However, it keeps on trying to activate the line. Special Value 1 is used to specify that no interleaving must be used. The value 1 indicates that the Fast latency Path shall be used in the G.992.1 and ANSI operating mode and Sp and Dp shall be selected such that Sp<1 and Dp=1 in G.992.2, G.992.3 , G.992.4 and G.992.5 operating modes. When the ILVD=1 the INP should be set to zero. Note: due to the choice of 1 as special value, it is impossible to set the max interleaving delay to a value of 1ms • Exception1: In G992.1 and Ansi, the Interleaved path shall be selected If delay = 1 and max DS rate is too large to be possible to reach without S=0.5 (i.e. max DS rate >8128kbps) and If (CPE is able to do S=0.5 ) and (CO decides to apply S=0.5) • Exception 2 If one of the 2 directions (upstream or downstream) is configured in interleaved mode and other one in fast. It's allowed to use the interleaved path for both upstream and downstream direction in order to avoid possible showtime interoperability issues with some CPEs.

1 ms



Table TNG 113-14: Minimum impulse noise protection Name

Minimum Impulse Noise Protection

Description

Specifies the minimum required impulse noise protection as a number of DMT symbols. This parameter puts a constraint the parameter PMS-TC impulse noise protection but extends towards all Multi-ADSL standards. The Modem Subsystem selects FEC parameters such that 0.5 × SpxDp × (Rp / N_FECp) > INPbc for the latency path carrying the specified bearer channel bc. If multiple bearer channels are carried over the same latency path, obviously the maximum of all INP limits constrains this latency path (see also Table TNG 113-13

Instances Values

Bearer DS, US 0.0 to 8.0 DMT Symbols. INP_min = 0 is a special value indicating no impulse noise protection bound is being imposed If the CO modem subsystem is not able to follow the minimum INPrequirement, it raises the activation failure " configuration not feasible". The modem subsystem checks standard compliancy of the CPE, i.e. the CO checks whether the actual INP proposed by the CPE is > the CPE_INP_min. If the CPE doesn't follow the Minimum INP requirement, the modem subsystem raises the activation failure. The INP implementation is applicable both for ADSL2x and ADSL1x operating mode

Granularity & Unit

0.1 DMT symbol The multi ADSL modem system shall round up intermediate values to the nearest higher valid INP value that is supported.

Notes (1) Support of INP_min values 4 and 8: The ITU standards require mandatory support of the INP_min values 0.0, 0.5, 1.0 and 2.0 while support of the INP_min values 4 and 8 is optional. This MGMT-requirement requests support of INP_min values 4 and 8. (2)

Support of INP_min=2 up to the highest supported DS and US interleaved net data rates. The ATU-C shall support bitrates up to 2.6 Mbps upstream and 22.8 Mbps downstream for INP_min =2. This proprietary behaviour shall be coupled to the modem features bitmap. Note: This means support of higher interleaving depth D_ds > 64, D_us > 8. In case ATU-C or ATU-R is not supporting these bitrates the following behavior (as mentioned in ITU) is applicable: Configuration of Minimum Net Data rates such that the sum of all Minimum Net Data rates over all bearer channels results in values higher than the ITU standard tables with min INP and maxium delay related net data rates limits may lead to configuration errors by the ATU-C and/or initialization failures with “configuration error” failure cause by the ATU-R.

(3)

Standard Compliant extension of S and D The Multi-ADSL Modem Subsystem shall support all optional values for S and D as provisionally agreed in ITU. Negotiating capabilities with CPE through G.hs and implementation constraints shall be according to the same amendments.


TNG 113-15


Table TNG 113-15: L3 Power State Permission Name

L3 Power State Permission

Description

This bit controls allowed link state transitions to L3 power management state:

• •

If enabled (bit = 1), the Modem Subsystem is allowed to use orderly shutdown as a means to reduce power in both US and DS. It also accepts orderly shutdown requests initiated bythe ATU-R. In this case, the modem subsystem transitions from L0 to L3 state without failure event. If disabled (bit = 0), the Modem Subsystem is NOT allowed to use orderly shutdown. When orderly shutdown procedure is initiated by the ATU-R, the ATU-C refuses this procedure. This means that no transition to L3 should be done without failure notification.

This bit has the same interpretation for all ADSL1x and ADSL2x opmodes. Instances

Line

Values

Bit : L3-Enabled / L3-Disabled

Granularity & Unit

-

Table TNG 113-16: L2 Power State Permission Name

L2 Power State Permission

Description

This bit controls allowed link state transitions to L2 power management state:

• •

If enabled (bit = 1), the Modem Subsystem is allowed to use L2 as a means to reduce power in DS. Parameters described in Tables TNG 113-17 to TNG 113-20 will be used by Multi-ADSL modem subsystem to control the power management. If disabled (bit = 0), the Modem Subsystem is NOT allowed to enter L2 state. Parameters described in Tables TNG 113-17 to TNG 113-20 will be ignored.

This bit is ignored when the operation mode is ADSL1x. Instances

Line

Values

Bit : L2-Enabled / L2-Disabled

Granularity & Unit

-

Table TNG 113-17: L0 Time Name

L0-TIME

Description

Specifies the minimum time - after entering L0 - before transition to L2 Power State. Note: Any time lower than 10 s will be considered as 10 s.

TNG 113-16

Instances

Line

Values

0 to 1800 s

Unit

1s



Table TNG 113-18: L2 Time Name

L2-TIME

Description

Specifies the minimum time between L2 entry and first power trim or 2 consecutive power trims.

Instances

Line

Values

0 to 1800 s

Unit

1s

Table TNG 113-19: L2 ATPR Name

L2-ATPR (Aggregate Transmit Power Reduction Per Trim)

Description

This parameter specifies the maximum allowed aggregate transmit power reduction (in dB) that can be performed in the L2 Request (i.e. at transition of L0 to L2 state) or through a single Power Trim in the L2 state. It ranges from 0 dB to 31 dB. The maximum PCBds in a L2 request command is limited by following constraint : maximum_PCBds - PCBds (L0) < L2_ATPR where:

• •

maximum_PCBds is the maximum PCBds value in the L2 request PCBds(L0) is the PCBds value of the L0 state

The proposed value of PCBds (in dB) in any L2 trim command is limited by following constraint: PCBds(proposed) - PCBds(current) < L2_ATPR where

• •

PCBds(proposed) is PCBds value proposed in the L2 trim command PCBds(current) is the PCBds value currently used in the L2 state

Instances

Line

Values

0 to 31 dB

Granularity & Unit

1 dB


TNG 113-17


Table TNG 113-20: L2 Bitrate Downstream Name

L2 Bitrate Downstream

Description

Specifies the minimum bitrate that shall be set up during L2 state (up to eventual rounding within 8 kbps, see “Description” in Table TNG 113-10). The same value is used by the Modem Subsystem as maximum DS bitrate measured in fixed, consecutive 1 second intervals that may not be exceeded during a time interval MAXIMUM (10s, L0-TIME) - as trigger for transition to L2 state. In case of multiple used latency paths, the DS actual bitrate must be below the threshold for each path during MAXIMUM (10s, L0-TIME), before transition to L2 occurs. The total bitrate during L2 will then be at least the sum of all configured L2 bitrates. Note: In case L0min > L2min, additional restrictions are implemented such that there is no possibility to swap to L2 Mode in case this would lead to a bitrate increase. Note: if the actual DS bitrate in L2 state is lower than the configured L2 Bitrate Downstream (this is always the case if the configured L2 Bitrate Downstream force an Lp larger than 1024), the modem refuses the transition to L2 state.

Instances

Bearer Channel DS

Values

0 to 65535 kbps

Granularity & Unit

1 kbps

Table TNG 113-21: L2 ATPRT Name

L2-ATPRT (Total Maximum Aggregate Transmit Power reduction in L2)

Description

This parameter represents the total maximum aggregate transmit power reduction (in dB) that can be performed in an L2 state. This is the sum of all reductions of L2 Request (i.e. at transition of L0 to L2 state) and Power Trims. It ranges from 0 dB to 31 dB. All PCBds values in the L2 state (i.e. the maximum PCBds in a L2 request command, and the proposed value of PCBds (in dB) in any L2 trim command) shall be limited by following constraint : PCBds - PCBds(L0) < L2_ATPRT where:

• •

TNG 113-18

PCBds is any PCBds value in the L2 state PCBds(L0) is the PCBds value of the L0 state

Instances

Line

Values

0 to 31 dB

Granularity & Unit

1 dB



Figure TNG 113-3: Illustration of the Layer 2 power state control parameters PSD level NOMPSD

PCB(L0)

PCB1 PCB2

REFPSD

PCB(L0)

L2-ATPR>= L2-ATPRT>=

L2-ATPR>= L2-ATPR>= L2-ATPR>=

>= L0TIME

>= >= >= >= L2L2L2L2TIME TIME TIME TIME

>= L0TIME

Time Initialization

Initialization

Show-

Show-

Show-

Show-

Channel

(other parts)

time

time

time

time

L0

L2

L0

L2

Discovery

An L2 request message is sent from the CO towards the CPE asking for a transition to the L2 link state and indicating the maximum allowed first power cutback (smaller than or equal to L2_ATPR). The CPE will investigate this and respond with an L2 grant message, indicating the actual first power cutback (can be lower than what was requested by CO). When entering L2, the bit rate becomes equal to the L2 bit rate, but as a consequence of the (typical) small first power cutback it is possible that there is still a significant amount of excess margin (compared to the target margin). Therefore with intervals of L2_TIME power trim messages are sent from the CO to the CPE, indicating the maximum requested power cutback (smaller than or equal to L2_ATPR). The CPE will respond with a L2 trim grant message, indicating the actual allowed power trim (can be lower than what was requested by CO). With each new power trim the power is decreased with the maximum per trim limited to L2_ATPR until the excess margin has been eliminated. The total of all these power reductions should not exceed L2_ATPRT.

Table TNG 113-22: Bonding Mode Name

Bonding Mode

Description

This parameter indicates whether the bearer channel is used to carry one complete ATM stream (native mode) or used on a pair within a bonding group (atmBonding). In the latter case, ATM bonding is be set up according to all requirements. In case ATM bonding would not be supported by the chipset, a configuration error is raised upon startUpLine command if ATM bonding would have been configured.

Instances Values

Bearer Enumeration:


native : default, line shall not operate in bonding group atmBonding : line is used for ATM bonding.

-


TNG 113-19


Table TNG 113-23: BondingGroupId Name

BondingGroupId

Description

This parameter provides the group identification number of the bonding group the bearer channel belongs to in case the bondingMode (see previous) is set to atmBonding. The bonding group ID 0 is not used.

Instances

Bearer

Values

unsigned long

Granularity & Unit

-

Table TNG 113-24: Upshift Noise Margin Name Description

Upshift Noise Margin Only applicable in case of RA mode 3 (‘dynamic). If the noise margin is higher than the upshift noise margin during a time interval, which is equal to the ‘minimum time interval for upshift rate adaptation’, then an upshift action of the data rate is performed. The new data rate is such that the noise margin is equal to the target margin unless the upper bitrate boundary is reached.

Instances

DS, US

Values

0.0..31.0

Granularity & Unit

0.1 dB

Table TNG 113-25: Downshift Noise Margin Name Description

Downshift Noise Margin Only applicable in case of RA mode 3 (‘dynamic). If the noise margin is lower than the downshift noise margin during a time interval, which is equal to the ‘minimum time interval for downshift rate adaptation’, then a downshift action of the data rate is performed. The new data rate is such that the noise margin is equal to the target margin unless the lower bitrate boundary is reached.

TNG 113-20

Instances

DS, US

Values

0.0..31.0

Granularity & Unit

0.1 dB



Table TNG 113-26: Minimum Time Interval for Upshift Rate Adaptation Name

Minimum Time Interval for Upshift Rate Adaptation

Description

Only applicable in case of RA mode 3 (dynamic). This parameter defines the consecutive time interval during which the noise margin has to be higher than the upshift noise margin to perform an upshift action of the data rate. The new data rate is such that the noise margin is equal to the target margin unless the upper bitrate boundary is reached.

Instances

DS, US

Values

0..16383

Granularity & Unit

1s

Table TNG 113-27: Minimum Time Interval for Downshift Rate Adaptation Name Description

Minimum Time Interval for Downshift Rate Adaptation Only applicable in case of RA mode 3 (‘dynamic). This parameter defines the consecutive time interval during which the noise margin has to be smaller than the downshift noise margin to perform a downshift action of the data rate. The new data rate is such that the noise margin is equal to the target margin unless the lower bitrate boundary is reached.

Instances

DS, US

Values

0..16383

Granularity & Unit

1s

Table TNG 113-28: Artificial Noise PSD Name

Artificial Noise PSD

Description

TXREFANL defines the Transmitter Referred Artificial Noise Level to be used as additional noise source at the transmitter. It is defined as an array of 32 breakpoints for downstream. Points are given in frequency [kHz] and PSD [dBm/Hz] components, and are translated to an array of the following form: TXREFANL = [(t1, PSD1), (t2, PSD2), …, (tN, PSDN)], where t1 < ti < tN. For ADSL1 and ADSL2 only the frequencies upto 1104 kHz are taken into account.

Values

PSD component of breakpoint: -40 dBm/Hz..-140 dBm/Hz Special value (default): NoArtificialNoise Frequency component of breakpoint: 0..2208 khz

Granularity & Unit

1 kHz; 0,5 dBm/H


TNG 113-21


Table TNG 113-29: INM Sensitivity Threshold Name

INM Sensitivity Threshold

Description

The sensitivity threshold of x dB makes the impulse noise monitor x dB more sensitive. To make the impulse noise monitor less sensitive, one has to use negative “x” values. The expected behaviour is explained in PERF_R.A.1001.3. A change in the configuration of the sensitivity threshold will trigger a reset of the histograms at the CPE.

Instances Values

Line DS -40 dB.. 40 dB Default: 0 dB

Granularity & Unit

0.1 dB

Table TNG 113-30: INM Pulse-Gap-Bridging Value Name

INM Pulse-Gap-Bridging Value

Description

The pulse-gap-bridging mechanism defines that an impulse that is following a first impulse within a time interval (from end of impulse 1 to the start of impulse 2) smaller than the Pulse-Gap-Bridging value shall be counted as one long impulse. The Pulse-Gap-Bridging value is defined as an integer multiple of a DMT symbol.

Instances

Line DS

Values

1 - 10 Default: 0 (no Pulse-Gap-Bridging)

Granularity & Unit

1

Table TNG 113-31: Warm Re-Init Disable Name

Warm Re-Init Disable

Description

This bit controls the enabling/disabling of warm re-inits. Meaning: 0: disable warm re-inits, only full cold inits are allowed 1: enable warm re-inits

Instances

Line

Values

Bit: 0/1 Default: 0

Granularity & Unit

TNG 113-22

1



Table TNG 113-32: Programmable Resynch Triggers Name

Programmable Resynch Triggers

Description

This array of integers controls the values of the required resynch triggers at both the xTU-C and xTU-R. For each trigger, a special value is used for disabling. The parameters applicable to the far-end are communicated to the CPE. Meaning: Persistency in seconds of [los; sef; lom; se; ncd; lcd; flos; rdi; flom; fse; fncd; flcd]

Instances Values

Line [0¨255; c ; 0¨255] with a minimum of 3 seconds for (f)los Default: [5; 5; 60; 10; 15; 15; 6; 6; 60; 10; 17; 17] Special persistency value for each trigger: 0: disable trigger (except for (f)los)

Granularity & Unit

1 second

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 Maximum value of Maximum Aggregate Transmit Power for nonoverlapped operating modes Maximum PSD Maximum value of Maximum PSD Power backoff mode Maximum aggregate receive power Table TNG 113-33: Modem features Name

Modem Features

Description

Specifies modem features which can be allowed or not by the operator. Currently, only bit 0 (LSB) of this bitmap is interpreted by the Multi-ADSL 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 to use these features. The following examples are given to indicate which features shall be mapped to this bit:

• •

For all ADSLx flavors : transmission of NSIF messages in G.hs (see GEN_R13.4). For ADSL2x mode: Support of higher bitrates than allowed in ITU standards for certain INP values (= support of higher D) (see also Table TNG 113-13)

This bit shall be provided for ADSL/2, READSL2 and ADSL2plus. Instances

Line

(1 of 2)


TNG 113-23


Values

Bitmap

Granularity & Unit

-

(2 of 2)

Table TNG 113-34: Maximum aggregate transmit power Name

Maximum Aggregate Transmit Power

Description

Specifies the maximum total power level that is allowed to be transmitted in the corresponding direction. The maximum value (25.5 dBm) is used as special value to indicate that the value defined in the corresponding Multi-ADSL standard must be used. The usage of this parameter shall depend upon the used operation mode:

• •

ADSL1x : parameter shall be ignored, since Max. Aggregate Power levels are fixed within the relevant standards. ADSL2x : input shall correspond to parameter MAXNOMATP

When the configured value is above the maximum aggregate transmit power allowed by the relevant standard, the configured value is ignored. Instances

Line DS, US

Values

0 to 25.5 dBm

Granularity & Unit

0.1 dBm

The constraints imposed by the standards are summarized in Table TNG 113-35. Table TNG 113-35: Maximum value of Maximum Aggregate Transmit Power for nonoverlapped operating modes MaxATP US

MaxATP DS

ADSL1/ADSL2/ADSL2plus Annex A

12.5 dBm

19.9 dBm

ADSL1/ADSL2/ADSL2plus Annex B

13.3 dBm

19.3 dBm

ADSL2/ ADSL2+ annex M

12.5 dBm

19.3 dBm

READSL2

12.5 dBm

18.8 dBm

Note (1)

TNG 113-24

The aggregate transmit power across the whole passband and measured at the line terminals, must not exceed the values of Table TNG 113-35 by more than 0.5 dB, in order to accommodate implementation tolerances



Table TNG 113-36: Maximum PSD Name

Maximum PSD

Description

Maximum PSD parameter specifies the maximum nominal power spectral density allowed on the line at the transmitter output (upstream and downstream) for initialization and showtime signals. Lowering the maximum PSD results in reduction of power consumption, by paying the price of having a lower capacity. When the configured value of MAXPSD is above the maximum PSD allowed by the relevant standard, the configured value is ignored. If only ADSL1x is enabled in the profile, and the configured value MAXPSDds_ADSL is below -52 dBm/Hz, the modem subsystem generates a configuration error only in case it is not able to support this non-standard setting. Note: only one parameter exists for both READSL2 US masks. The same input value will thus be interpreted for both modes.

Instances

Line DS, US

Values

US : -60.0 to -32.9 dBm/Hz DS : -60.0 to -37.0 dBm/Hz

Granularity & Unit

0.1 dBm/Hz

Note (1)

The Maximum PSD parameter cannot be used to boost the PSD beyond the standard PSD, it can only be used to put additional constraints on top of the standard. The constraints imposed by the standards are summarized in Table 9.

Table TNG 113-37: Maximum value of Maximum PSD Maximum PSD US

Maximum PSD DS

ADSL1/ADSL2

-38 dBm/Hz

-40 dBm/Hz

READSL2 Mode 1

-36.4 dBm/Hz

-37 dBm/Hz

READSL2 Mode 2

-32.9 dBm/Hz

-37 dBm/Hz

ADSL2plus

-38 dBm/Hz

-40 dBm/Hz

ADSL2/ ADSL2plus annex M EU56 mask

-40.4 dBm/Hz

-40 dBm/Hz

Note — Support of MaxPSD down to -80dBm/Hz Support of extended MAXPSD range down to -80 dBm/Hz in ADSL1x and ADSL2x mode


TNG 113-25


Table TNG 113-38: Power backoff mode Name Description

Power Backoff Mode Specifies the Power BackOff Mode for ADSL2x: PBO Off: Upstream Power-Backoff mechanism is not used i.e. the parameter Maximum Aggregate Receive Power US (see Maximum aggregate receive power) is not interpreted by the Modem Subsystem. PBO On: The ATU-C requests the Upstream PBO to comply to parameter Maximum Aggregate Receive Power. This parameter shall be ignored for ADSL1x.

Instances Values

Line US PsdPboOff PsdPboOn

Granularity & Unit

-

Table TNG 113-39: Maximum aggregate receive power Name

Maximum Aggregate Receive Power (3 tones)

Description

Specifies the maximum allowed total receive power level allowed for ADSL2x . This parameter shall only be used when Psd PBO parameter (see Power backoff mode) is on. The input shall correspond to parameter MAXRXPWR This parameter shall be ignored for ADSL1x.

TNG 113-26

Instances

Line US

Values

-25.5 to 25.5 dBm

Granularity & Unit

0.1 dBm



ADSL2plus-specific configuration parameters The following configuration parameters will only be used when the selected operation mode is ADSL2+:

• •

PSD shape Custom PSD shape: • Custom DS PSD Shape • Custom US PSD Shape

In all other operation modes, they will be ignored. Table TNG 113-40: PSD shape Name

PSD Shape

Description

For DS and US: specifies a predefined (standard) PSD shape (mask or template) to be respected on the line in the corresponding direction. The different predefined shapes are specified through enumeration. Each PSD shape is characterized completely by the enumeration tag.

Instances Values

Line DS, US Enumeration. Next PSD Shapes Tags are defined for ADSL2plus: DOWNSTREAM:

• • •

PSD_SHAPE_CUSTOM : The “Custom PSD Shape” (see further) will specify the PSD shape. PSD_SHAPE_ADSL2PLUS_CO : Normal PSD Mask for CO deployment. PSD_SHAPE_ADSL2PLUS_CA_[X] : PSD Masks for Cabinet deployment. [X] designates the cut-off frequency for the passband. The possible values for [X] are 100 to 280 in steps of 10 tones.

Further details are given hereunder (Downstream PSD Shape Details) In case DPBO parameters are specified, the Downstream PSD Shape parameter is ignored. UPSTREAM:


PSD_SHAPE_CUSTOM : The “Custom PSD Shape” (see further) will specify the PSD shape. PSD_SHAPE_ADSL2PLUS_DEFAULT : Standard US PSD mask.

-

DOWNSTREAM PSD SHAPE DETAILS: In case the Central Office Mask is selected, there shall be no additional PSD shaping on top of the PSD Mask defined by G.992.5 Annex A, Annex B and Annex M. In case a Cabinet Mask is selected, the lower part of the spectrum shall be transmitted at lower PSD level (shaped). The set of Cabinet Masks only differ in the cut-off frequency for the stopband (see Figure 8).


TNG 113-27


Figure TNG 113-4: ADSL2+ PSD Masks for Cabinet deployment PSD in dBm/ Hz PSD2 = -36.5

PSD1 = -95 t1

t2

subca rrier index linea r sca le)

subca rrier index = frequency (kHz)/Df (Df = 4.3125 kHz) Each of the Cabinet PSD masks has 2 breakpoints: (t1,PSD1),(t2,PSD2) PSD1=-95 dBm/Hz PSD2=-36.5 dBm/Hz t2 varies from tone 100 to 280 in steps of 10 tones t1 = rounddown (t2 - (PSD2-PSD1)/2.2 dB/tone) = t2-27

This results in a total of 19 PSD Masks for Cabinet deployment, as illustrated in Table 10 Table TNG 113-41: ADSL2+ PSD masks for Cabinet deployment

TNG 113-28

PSD Mask

t1

t2

f1 (kHz)

f2 (kHz)

ADSL2Plus Ca 100

73

100

314.8125

431.25

ADSL2Plus Ca 110

83

110

357.9375

474.375

ADSL2Plus Ca 120

93

120

401.0625

517.5

ADSL2Plus Ca 130

103

130

444.1875

560.625

ADSL2Plus Ca 140

113

140

487.3125

603.75

ADSL2Plus Ca 150

123

150

530.4375

646.875

ADSL2Plus Ca 160

133

160

573.5

625 690

ADSL2Plus Ca 170

143

170

616.6875

733.125

ADSL2Plus Ca 180

153

180

659.8125

776.25

ADSL2Plus Ca 190

163

190

702.9375

819.375

ADSL2Plus Ca 200

173

200

746.0625

862.5

ADSL2Plus Ca 210

183

210

789.1875

905.625

ADSL2Plus Ca 220

193

220

832.3125

948.75

ADSL2Plus Ca 230

203

230

875.4375

991.875

ADSL2Plus Ca 240

213

240

918.5625

1035

ADSL2Plus Ca 250

223

250

961.6875

1078.125

ADSL2Plus Ca 260

233

260

1004.813

1121.25

ADSL2Plus Ca 270

243

270

1047.938

1164.375

ADSL2Plus Ca 280

253

280

1091.063

1207.5



Table TNG 113-42: Custom DS PSD Shape Name

Custom DS PSD Shape

Description

Specifies a US PSD shape (mask or template) to be respected on the physical line in the corresponding direction. The PSD Shape is specified through the following set of parameters:

• • •

PsdShapeFlag: indicates whether the shape is filled in or not by the XDSL Manager (if not, data are not trustable and should be ignored. In that case, only limit masks shall apply). PsdShapeType: indicates whether defined PSD points describe mask or template. Only “mask” is supported, “template” is rejected (*). PsdFreqScale : indicates whether PSD shape interpolation has to be done on linear or logarithmic scale. However, the modem subsystem ignores this parameter. The modem subsystem allows up to 20 specified PSD points. Note: 20 PSD points must be available even when the maximum number of RFI bands (two in ADSL2+) are defined (thise means that in ADSL2+ the total number of breakpoints to be supported by the modem is 20 for the custom DS PSD + 2x4 for the RFI bands which means a total of 28 breakpoints). The PSD shape implemented by the modem subsystem also needs to take RFI bands into account (see RF band data) Set of PSD Points: • PSD point = [frequency, max PSD] Frequency : 0 - 30000 kHz This range is defined for the VDSL passband. For Multi ADSL the applicable range is only the passband of ADSL2plus • max PSD : 0 to -95 dBm/Hz The valid PSD value = lowest value of (max PSD parameter and ITU standard limit mask PSD level)

The PSD shape is made by connecting the PSD points via linear or logarithmic interpolation (as in standard). Following rules apply:

•

• • • • (*)

The operator can specify a custom PSD shape with brick wall or with more strict requirements than specified in section 8.5.1 of G.992.5. It's the responsibility of the modem subsystem to translate these requirements according to the section 8.5.1 points 1-4 of G.992.5. As a minimum requirement the modem subsystem shall at least be able to implement a custom shape according to these standard requirements. The operator only gets guarantees on the standard PSD shape. However this doesn't prevent the modem subsystems to implement a PSD shape that approximates the operator custom PSD shape more closely. The RFI band specification is described in RF band data The successive PSD points must have increasing ( ) frequencies. It is allowed that for two successive PSD points, different PSD levels are defined at the same frequency f (brick wall): • point x: PSDx, f • point x+1: PSDx+1,f In case DPBO parameters are specified, the Downstream Custom PSD Shape parameter is ignored. Reject shall be done by raising the "Configuration Error" failure.

Instances

Line DS

Values

See details in “Description” field.

Granularity & Unit

0.5 dBm/Hz for PSD value 1 kHz for Frequency


TNG 113-29


Table TNG 113-43: Custom US PSD Shape Name

Custom US PSD Shape

Description

Specifies a US PSD shape (mask or template) to be respected on the physical line in the corresponding direction. The PSD Shape is specified through the following set of parameters:

• • •

PsdShapeFlag: indicates whether the shape is filled in or not by the XDSL Manager (if not, data are not trustable and should be ignored. In that case, only limit masks shall apply). PsdShapeType: indicates whether defined PSD points describe mask or template. Only “mask” is supported, “template” is rejected (*). PsdFreqScale : indicates whether PSD shape interpolation has to be done on linear or logarithmic scale. However, the modem subsystem ignores this parameter. The modem subsystem allows up to 20 specified PSD points. The PSD shape implemented by the modem subsystem also needs to take RFI bands into account (see RF band data) Set of PSD Points: • PSD point = [frequency, max PSD] Frequency : 0 - 30000 kHz This range is defined for the VDSL passband. For Multi ADSL the applicable range is only the passband of ADSL2plus • max PSD : 0 to -95 dBm/Hz The valid PSD value = lowest value of (max PSD parameter and ITU standard limit mask PSD level)

The PSD shape is made by connecting the PSD points via linear or logarithmic interpolation (as in standard). Following rules apply:

•

• •

(*)

The operator can specify a custom PSD shape with brick wall or with more strict requirements than specified in section 8.5.1 of G.992.5. It's the responsibility of the modem subsystem to translate these requirements according to the section 8.5.1 points 1-4 of G.992.5. As a minimum requirement the modem subsystem shall at least be able to implement a custom shape according to these standard requirements. The operator only gets guarantees on the standard PSD shape. However this doesn't prevent the modem subsystems to implement a PSD shape that approximates the operator custom PSD shape more closely. The successive PSD points must have increasing ( ) frequencies. It is allowed that for two successive PSD points, different PSD levels are defined at the same frequency f (brick wall): • point x: PSDx, f • point x+1: PSDx+1,f Reject shall be done by raising the "Configuration Error" failure.

Instances

Line US

Values

See details in “Description” field.

Granularity & Unit

0.5 dBm/Hz for PSD value 1 kHz for Frequency

TNG 113-30



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 Multi-ADSL 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 Tx PSD Last state transmitted Attainable line bitrate Actual line bitrate Line relative capacity occupation Attainable ATM bitrate (per bearer channel) Actual ATM bitrate (per bearer channel) Interleaving delay (per bearer channel) Actual impulse noise protection (per bearer channel) Actual L2 low power ATM Bitrate (per bearer channel) Actual Artificial Noise PSD Table TNG 113-44: Current operational mode Name

Current Operational Mode

Description

The operational mode used for the current operation of the Multi-ADSL modem subsystem (see Operating modes).

Instances

Line

Values

See Operating modes. Only 1 bit can be set to 1 at a time.

Granularity & Unit

-


Defined during configuration and G.hs.

Update frequency

NA


TNG 113-31


Table TNG 113-45: Operational mode capabilities Name

Operational mode Capabilities

Description

The total set of operational modes supported by the ATU-C and the ATU-R respectively.

Instances

ATU-C / ATU-R

Values

See Operating modes.

Granularity & Unit

-

Update frequency

NA


ATU-C: parameter reflects all the standards the modem chipset is able to support. ATU-R: parameter reflects the CPE supported standards indicated in G.hs. If ANSI or ETSI activation tones have been detected, also the operation mode bits for these mode are set.

Table TNG 113-46: SNR margin Name

SNR Margin

Description

Indicates the current noise margin relative to the noise power that the ATU can tolerate and still meet the target BER of 10-7 at 0 dB noise margin accounting for all coding gains included in the design. The SNR Margin given shall be the average of the margins (expressed in dB) of all loaded carriers. ADSL2: According to ADSL2 standard an SNRM value of -512 is a special value indicating that signal to noise ratio margin is out of range. For downstream this special value -512 is translated to 51.2 dB. For upstream the complete range -64 to 63 dB can be used

Instances

DS/US

Values

-64.0..+63.0 dB

Granularity & Unit

0.1 dB

Accuracy

0.5 dB

Update frequency

DS: at least every 10 seconds via overhead channel. US: at least every 10 seconds @ ATU-C.

Table TNG 113-47: Loop attenuation Name

Loop Attenuation

Description

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.

Instances

DS/US

(1 of 2)

TNG 113-32



Values


Granularity & Unit

0.1 dB

Accuracy

0.5 dB

Update frequency

NA

(2 of 2)

Table TNG 113-48: Signal attenuation Name

Signal Attenuation

Description

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 Values

DS/US 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

0.1 dB

Accuracy

0.5 dB

Update frequency

DS: at least every 10 seconds via overhead channel. US: at least every 10 seconds @ ATU-C.


TNG 113-33


Table TNG 113-49: Aggregate output power Name

Aggregate Output Power

Description

Actual aggregate output power (that is, the total output power for the carriers of the corresponding direction) when the modem is in showtime.

Instances

DS/US

Values

-31.0..+31.0 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

0.1 dBm

Accuracy

0.1 dB (maximum admissible deviation with actual measured value)

Update frequency

DS: each bit swap US: each bit swap

Table TNG 113-50: Actual Tx PSD Name

Actual Tx PSD

Description

Actual transmit power spectrum density over the subcarriers at the U interface, including artificial noise.

Instances

DS/US

Values

-127.0 to 0 dBm/Hz. A value indicated as “noPSD” is a special value. It indicates that no power is transmitted on that carrier.

Granularity & Unit

0.1 dBm/Hz

Accuracy

0.1 dBm/Hz

Update frequency


Table TNG 113-51: Last state transmitted Name

Last state transmitted

Description

This parameter represents the last successful transmitted initialization state in the relevant direction in the last full initialization performed on the line. Initialization states are defined in the individual ADSL Recommendations and are counted from 0 (if G.994.1 is used) or 1 (if G.994.1 is not used) up to Showtime (= 32). The DS parameter is stored in ADSL2x operation modes only and is provided during loop diagnostics mode. The index of the ATU-C state is represented by an 8-bit integer value from 0 (G.994.1 phase) and 1 (C-QUIET1) to 31 (C-SEGUE4) and 32 (CSHOWTIME). The US parameter is retrieved from the ATU-R and provided to the xDSL Manager only during loop diagnostics mode. The index of the ATU-R state is represented by an 8-bit integer value from 0 (G.994.1 phase) and 1 (R-QUIET1) to 30 (R-SEGUE4) and 31 (R-SHOWTIME).

Instances

DS/

(1 of 2)

TNG 113-34



Values

0 to 32

Granularity & Unit

1

Update frequency

Not Applicable

(2 of 2)

Table TNG 113-52: Attainable line bitrate Name

Attainable Line Bitrate

Description

Indicates the maximum bitrate the modem can sustain on the line (i.e. the ATM payload plus all overhead from the PMD, PMS-TC and TPS-TC layers) taking the current configuration (INP, delay, carriermask, coding …) into account (e.g. assuming same type of coding gain). If multiple bearer channels are active, the calculation assumes that all capacity would be allocated to the bearer channel with the highest coding gain. Note: the ATU-C takes the CPE capabilities into account (e.g. if the CPE does not support S=1/2, even if the CO supports S=1/2 the reported rate is the value without S=1/2 support) The accuracy of this attainable line bitrate is 10 %. This means that if the modem retrains - without change in loop or noise conditions - the actual line bitrate is within 10% of the reported attainable line bitrate before re-initialisation.

Instances Values

DS/US 0..65535 Remark: in case of no EOC, the initialization value for Attainable DS Line Bitrate is returned.

Granularity & Unit

1 kbps

Update frequency

DS: at least every 10 seconds via overhead channel. US: at least every 10 seconds @ ATU-C

Table TNG 113-53: Actual line bitrate Name

Actual Line Bitrate

Description

The total line rate currently set up by PMD layer (i.e. the actual ATM payload plus all overhead information from the PMD, PMS-TC and TPS-TC layers). The Line Bitrate is given by the number of bits per DMT symbol, multiplied with the number of DMT symbols per second, divided by 1000 (kbps).

Instances

DS/US

Values

0..65535

Granularity & Unit

1 kbps

Update frequency

ADSL2x : every time SRA is executed.


TNG 113-35


Table TNG 113-54: Line relative capacity occupation Name

Line Relative Capacity Occupation

Description

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. Note : L2 state transitions shall be transparent, i.e. DS Line Relative Capacity Occupation shall always be L0 line bitrate, even if line state is L2 !

Instances

DS/US

Values

0..100%

Granularity & Unit

1%

Update frequency

Every time Actual and/or Attainable Line Rate are updated.

Table TNG 113-55: Attainable ATM bitrate (per bearer channel) Name

Attainable ATM Bitrate

Description

Indicates the maximum ATM bitrate (i.e. ATM payload plus header bytes) the ATU can sustain on the line taking the current configuration (INP, delay, carriermask, coding …) into account, with margin not lower than Target Noise Margin. This parameter is provided for each activated bearer channel. The calculation estimates the attainable ATM Bitrate assuming that all available capacity is allocated to that bearer channel. Note: the ATU-C takes the CPE capabilities into account (e.g. if the CPE does not support S=1/2, even if the CO supports S=1/2 the reported rate is the value without S=1/2 support) The accuracy of this attainable ATM bitrate is 10 %. This means that if the modem retrains - without change in loop or noise conditions - the actual ATM bitrate is within 10% of the reported attainable ATM bitrate before re-initialisation.

Instances

Per bearer channel

Values

0..65535

Granularity & Unit

1 kbps

Update frequency

DS: each = 10 seconds via overhead channel. US: each < 10 seconds @ ATU-C

Table TNG 113-56: Actual ATM bitrate (per bearer channel)

TNG 113-36

Name

Actual ATM Bitrate

Description

The actual transport rate (that is, the transported payload plus header bytes) expressed in kbps in the L0 state.

Instances

DS/US per bearer channel

Values

0..65535

Granularity & Unit

1 kbps

Update frequency

ADSL2x : every time SRA or OLR is executed.



Table TNG 113-57: Interleaving delay (per bearer channel) Name

Actual Interleaving Delay

Description

Actual delay caused by the interleaving and de-interleaving functionality.

Instances


Values

0..63

Granularity & Unit

1 ms

Update frequency

ADSL2x : updated every time Sp and/or Dp changes (during Initialization or showtime)

Table TNG 113-58: Actual impulse noise protection (per bearer channel) Name

Actual Impulse Noise Protection

Description

Actual value of INP parameter, defined in Minimum impulse noise protection, in current session: The Modem Subsystem uses this formula to calculate actual INP Actual INP = 0.5 * SpxDp* (Rp / N_FECp) for each latency path p.

Instances


Values

0..8.0 DMT symbols. Actual INP values of 16 DMT symbols will be ceiled to actual INP of 8 DMT symbols.

Granularity & Unit

ADSL2x : updated every time Sp, Dp, Rp or N_FECp changes (during Initialization or showtime)

Update frequency

NA

Table TNG 113-59: Actual L2 low power ATM Bitrate (per bearer channel) Name

Actual L2 low power ATM Bitrate

Description

The actual ATM rate (i.e. the ATM payload plus header bytes) expressed in kbps in the L2 state.

Instances

DS for each bearer channel

Values

0 – 65535

Granularity & Unit

1 kbps

Update frequency

ADSL2x : every transition from L0 to L2 and during L2

Table TNG 113-60: TPS-TC mode capabilities Name

TPS-TC Mode Capabilities

Description

The total set of TPS-TC modes supported by the VTU-O and the VTU-R respectively.

(1 of 2)


TNG 113-37


Instances

Line Near-end/Far-end

Values

Bitmap: TPSTCModesATMBit TPSTCModesPTM_64_65Bit TPSTCModesPTM_HDLCBit

Granularity & Unit

-

Update frequency

NA

(2 of 2)

Table TNG 113-61: Actual Artificial Noise PSD Name

Actual Artificial Noise PSD

Description

Actual artificial noise power spectrum density per subcarrier at the constellation encoder.

Instances

For each carrier

Values

-140 to 0 dBm/Hz A value indicated as “noPSD” is a special value (default). It indicates that no artificial noise is transmitted on that carrier.

TNG 113-38

Granularity & Unit

0.1 dBm/Hz

Update frequency

DS: at the end of init


TNG 114 — DLP configuration examples Purpose This document gives a summary of the configuration used in the configuration examples in the DLP documents

Equipment Table TNG 114-1 lists the equipment. Table TNG 114-1: Equipment Equipment

Board Type

Subrack

XD

acu

aacu-c

nt-a, nt-b

ecnt-c

iont

ecnc-a

lt:1/1/4

evlt-c

lt:1/1/5

eblt-c

lt:1/1/6

polt-b

lt:1/1/7

eblt-k

lt:1/1/8

eblt-k

lt:1/1/9

smlt-k


TNG 114-1


xDSL profiles Table TNG 114-2 lists the configured xDSL profiles. Table TNG 114-2: xDSL profiles

Service profile

Spectrum profile

Bonding

ID

Name

7

ADSL_profile

8

VDSL_profile

10

XSRVC_0_0

4

vdsl_profile

5

adsl_profile

2

GroupProfile1

Note (1)

Other profiles are not used for actual lines

SHub ports Table TNG 114-3 lists the configured SHub ports. Table TNG 114-3: SHub ports

TNG 114-2

Port

Port Type

1

Subtending

2

Subtending

3

Network

4

Network

5

Network

6

Network

7

Network



VLANs Table TNG 114-4 lists the configured VLANs. Table TNG 114-4: VLANs VLAN LT mode

SHub mode

LT 1/1/x

Network Port

4 5 6 7 8 9 1 1 1 1 1 1 1 1 1 1 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 8 9 56

residential-bridge

70

layer2-term-netwport

80


T T

100

residential-bridge residential-bridge

x x x x

101

layer2-terminated residential-bridge

x x x x x x x x x x x x x x x x

T

200

residential-bridge residential-bridge

x x x x x x

T

300

cross-connect

cross-connect

301

cross-connect

cross-connect

350

qos-aware

cross-connect

x

T

cross-connect

x

T

400

U

x

T

x

T

400:0 cross-connect 401

cross-connect

x

T

401:0 cross-connect 500

cross-connect

x

T

500:0 layer2-terminated 500:6 cross-connect 00 501

cross-connect

x

T


layer2-terminated

x


residential-bridge

600


1450


2200

cross-connect

4090

layer2-terminated v-vlan

4093

T T

cross-connect x x x x x x

reserved


T

TNG 114-3


Note (1)

U: untagged - T: tagged

VRFs Table TNG 114-5 lists the VRFs on the LT. Table TNG 114-5: LT VRFs VRF

Mode

VLAN

1

Forwarder

5

Router

4090

16

Forwarder

101

Gateway

10.178. 14.97/27 192.168.116. 1/24

Table TNG 114-6 lists the VRFs on the SHub. Table TNG 114-6: SHub VRFs VRF

Mode

0

Slow-path

10 15

17

TNG 114-4

VLAN

IP Address

DHCP Relay to...

Slow-path

100

192.168.100.2/24

182.168.100.13

Fast-path

70

192.168.70.39/24

80

192.168.80.39/24

1450

10.178.14.85/27

4090

10.178.14.97/27

101

192.168.116. 2/24

Slow-path

10.178.14.97

192.168.116. 2



Lines

VDSL Table TNG 114-7 lists the VDSL lines. Table TNG 114-7: VDSL lines Line

Mode

VLAN

1/1/4/1

Cross-connect

301

1/1/4/2

Stacked

401:0

1/1/4/3

Stacked

501:601

1/1/4/12

Residential-bridge

200

1/1/4/14

IPoE

4090

1/1/4/15

PPPoE

101

VRF

CPE IP Address

16

ADSL Table TNG 114-8 lists the ADSL lines. Table TNG 114-8: ADSL lines Line

Mode

VLAN

VRF

CPE IP Address

1/1/5/1

Cross-connect

300

1/1/5/2

Stacked

400:0

1/1/5/3

Stacked

500:600

1/1/5/4

QoS-aware

350

1/1/5/7

IPoA cross-connect

2200

192.168.150.2

1/1/5/8

IPoA cross-connect

512:37

192.168.1.1

1/1/5/10

PPPoA-PPPoE relay

1/1/5/12

Residential-bridge

1/1/5/13

IPoA

16

1/1/5/14

IPoE

16

1/1/5/15

PPPoE

200


10.178.14.53

TNG 114-5


Bonding

• •

System level: 1/1/7/21, 1/1/8/25 Chipset level: 1/1/8/47, 1/1/8/48

SHDSL

• • •

TNG 114-6

4-wire: 1/1/9/1, 1/1/9/3 EFM: 1/1/9/5 IMA: 1/1/9/16, 1/1/9/18, 1/1/9/21, 1/1/9/24



IP bridge

Figure TNG 114-1: Configuration example IP Bridge

CPE

VLAN 100

LT-y

SHub

VLAN 100 RB

RB

Network VRF 10 DHCP relay

RB: Residential bridge VLAN

IP forwarder

Figure TNG 114-2: Configuration example IP forwarder

CPE

VLAN 101

LT-y VRF 16

SHub

VLAN 101 RB

L2-term

Network VRF 17 DHCP relay

L2-term: Layer2-terminated VLAN

RB: Residential bridge VLAN


TNG 114-7


IP router

Figure TNG 114-3: Configuration example IP router

CPE

VLAN 4090

LT-y VRF 5

L2-term

VLAN 1450

SHub

V-VLAN

VRF 15

L2-term-nwp

Network

router & DHCP relay

10.178.14.97/27

L2-term: Layer2-terminated VLAN

TNG 114-8

V-VLAN: Virtual VLAN

10.178.14.85/27

L2-term-nwp: Layer2-terminated VLAN on network port


TNG 115 — Slot numbering schemes Purpose This document describes the numbering schemes that are supported by the NE with regard to the slot positions in the subracks. To be able to align the different numbering schemes, an option is provided to the CLI operator to switch from one numbering scheme to the other; see DLP 103.

Terminology The different slot position schemes are:

• •

•

•

type-based: Type-based numbering (flat numbering per slot type from left to right starting with 1, TL1 format.) Position-based: This slot position scheme is a flat-numbering scheme from left to right (within the subrack when the boards are positioned vertically) or from bottom to top (within the subrack when the boards are placed horizontally) starting with 1. This is in fact equal to the physical position numbering from left to right or from bottom to top starting with 1. position-based legacy-num: This numbering is identical to position-based except for some very specific configurations (for example, ARAM-D and ALTS-M/Q, which are all characterized by the fact that the first LT position is not equal to the 4th slot position) where previously a kind of type-based numbering was used (that is, a fixed relation between CLI slot number and equipment log slot number). log-slot-num: Logical slot ID (that is, the numbering method defined for equipment identification in the MIB.)


TNG 115-1

TNG 115 — Slot numbering schemes

Translation table • • • •

lt x: line board x lp x: applique x Subrack: what is printed on the subrack itself Logical slot ID: ID that is used from and to equipment subsystem to identify a slot

XD equipment Table TNG 115-1 shows the translation table for the XD splitterless subrack XD-LT (ALTS-T). Table TNG 115-1: Translation table for XD-LT Silk

ac u

nt a

nt b

lt 1

lt 2

lt 3

lt 4

lt 5

lt 6

lt 7

lt 8

lt 9

lt1 0

lt1 1

lt1 2

lt1 3

lt1 4

lt1 5

lt1 6

Type based

ac u

nt a

nt b

lt 1

lt 2

lt 3

lt 4

lt 5

lt 6

lt 7

lt 8

lt 9

lt1 0

lt1 1

lt1 2

lt1 3

lt1 4

lt1 5

lt1 6

Legacy based

1

2

3

4

5

6

7

8

9

1 0

1 1

1 2

13

14

15

16

17

18

19

Position based

1

2

3

4

5

6

7

8

9

1 0

1 1

1 2

13

14

15

16

17

18

19

Logical slot ID

0

1

2

3

4

5

6

7

8

9

1 0

1 1

12

13

14

15

16

17

18

Table TNG 115-2 shows the translation table for the XD-Combo300 subrack (ALTS-U). Table TNG 115-2: Translation table for XD-Combo300 Silk

ac u

nt a

nt b

lt 1

lt 2

lt 3

lt 4

lt 5

lt 6

lt 7

lt 8

lt 9

lt1 0

lt1 1

lt1 2

lt1 3

lt1 4

lt1 5

lt1 6

Type based

ac u

nt a

nt b

lt 1

lt 2

lt 3

lt 4

lt 5

lt 6

lt 7

lt 8

lt 9

lt1 0

lt1 1

lt1 2

lt1 3

lt1 4

lt1 5

lt1 6

Legacy based

1

2

3

4

5

6

7

8

9

1 0

1 1

1 2

13

14

15

16

17

18

19

Position based

1

2

3

4

5

6

7

8

9

1 0

1 1

1 2

13

14

15

16

17

18

19

Logical slot ID

0

1

2

3

4

5

6

7

8

9

1 0

1 1

12

13

14

15

16

17

18

FD equipment For FD equipment, legacy-based numbering is equal to position-based numbering. Table TNG 115-3 shows the translation table for the 7302 FD subrack (NFXS-A).

TNG 115-2



Table TNG 115-3: Translation table for NFXS-A Silk

lt 1

lt 2

lt 3

lt 4

lt 5

lt 6

lt 7

lt 8

nt a

iont/lt 17

nbt/lt 18

lt 9

lt 1 0

lt 1 1

lt 1 2

lt 1 3

lt 1 4

lt 1 5

lt 1 6

Type based

lt 1

lt 2

lt 3

lt 4

lt 5

lt 6

lt 7

lt 8

nt a

iont/lt 17

nbt/lt 18

lt9

lt 1 0

lt 1 1

lt 1 2

lt 1 3

lt 1 4

lt 1 5

lt 1 6

Legacy based

1

2

3

4

5

6

7

8

9

10

11

1 2

1 3

1 4

1 5

1 6

1 7

1 8

1 9

Position based

1

2

3

4

5

6

7

8

9

10

11

1 2

1 3

1 4

1 5

1 6

1 7

1 8

1 9

Logical slot ID

3

4

5

6

7

8

9

1 0

1

0/19

2/20

1 1

1 2

1 3

1 4

1 5

1 6

1 7

1 8

Table TNG 115-3 shows the translation table for the 7330 FD subrack (NFXS-B). Table TNG 115-4: Translation table for NFXS-B Silk

nta

iont/lt9

nbt/lt 10

lt1

lt2

lt3

lt4

lt5

lt6

lt7

lt8

Type based

nta

iont/lt9

nbt/lt 10

lt1

lt2

lt3

lt4

lt5

lt6

lt7

lt8

Legacy based

1

2

3

4

5

6

7

8

9

10

11

Position based

1

2

3

4

5

6

7

8

9

10

11

Logical slot ID

0

1

2

3

4

5

6

7

8

9

10

ARAM-D equipment Table TNG 115-5 shows the translation table for the 4-LT shelf or ARAM-D shelf. Table TNG 115-5: Translation table for ARAM-D equipment Silk

lp1

lp2

lp3

lp4

lt1

lt2

lt3

lt4

nta

ntb

acu

Type based

lp1

lp2

lp3

lp4

lt1

lt2

lt3

lt4

nta

ntb

acu

Legacy based

(4)

(5)

(6)

(7)

4

5

6

7

2

3

3

Position based

1

2

3

4

5

6

7

8

9

10

11

Logical slot ID

131

132

133

134

3

4

5

6

1

2

-


TNG 115-3


TNG 115-4


TNG 116 — Link Related Ethernet OAM (EFM OAM) Introduction As Ethernet moves from being an enterprise-centric technology into a WAN and access technology, carrier-class capabilities need to be brought to Ethernet designs. One of the most important characteristics of a carrier-class technology is the implementation of operational, administration and maintenance (OAM) capabilities. Link Related Ethernet OAM (IEEE802.3 clause 57 standard) provides network operators with the ability to monitor the health of the network and quickly determine the location of failing links or fault conditions. It allows remote side information to be retrieved for a link connected with a node for which SNMP may not be available as default. EFM OAM does not include functions such as station management, bandwidth allocation or provisioning functions, which are considered outside the scope of this standard. Figure TNG 116-1 shows a typical Link Related Ethernet OAM configuration. Figure TNG 116-1: Typical Link Related Ethernet OAM Configuration 7302 ISAM or 7330 FTTN CPE IEEE802.3ah (Link Ethernet OAM)


TNG 116-1

TNG 116 — Link Related Ethernet OAM (EFM OAM)

General Description EFM OAM information is conveyed in Slow Protocol frames called OAM Protocol Data Units (PDUs). EFM OAM PDUs contain the appropriate control and status information used to monitor, test and troubleshoot OAM-enabled links. EFM OAM PDUs traverse a single link, being passed between peer OAM entities, and as such, are not forwarded by MAC clients (for example, bridges or switches). Link Related Ethernet OAM provides a mechanism to detect the presence of an OAM sub layer at the remote DTE called Discovery. During the Discovery process, the NE and the CPE exchange their respective configuration information and evaluate the remote information to determine compatibility. The decision for accepting remote configuration is based on the remote system's OAM mode, version, maximum PDU size, Parser Action, Multiplexer Action and functions supported information. If these parameters are accepted the discovery will complete and Link Related Ethernet OAM will be operational, else the remote configuration is rejected and requires operator intervention to rectify the conflicting parameters. Link Related Ethernet OAM has provision to retrieve one or more MIB variables, also referred as attributes, from the CPE. The operator can retrieve MAC layer counters and PME counters from the CPE after successful completion of discovery. Link Related Ethernet OAM is supported on most of the EFM, EFM Bonding and Native Ethernet LTs and some of the compatible CPEs.

Link Related Ethernet OAM Configuration Parameters Link Related Ethernet OAM is managed using the parameters described in Table TNG 116-1. These values are stored in the database persistently. Table TNG 116-1: Link Related Ethernet OAM parameter descriptions

TNG 116-2

Parameter

Description

Values

Default

admin-status

Parameter used to enable / disable Link Related Ethernet OAM on an interface

Enabled / Disabled

Disabled

oam-mode

Dot3 OAM mode value. (NE is always configured in Active mode)

Active / Passive

Active

alive-timer

Time interval between Alive PDUs sent to the CPE after completion of Discovery. (This parameter has impact on the alive timer of the CPE as this value should be same on both NE and CPE). In addition, internally the NE will use (alive-timer + 5 s) as the maximum interval to receive an OAM PDU from the CPE before declaring it down and restarting the discovery

1s - 300 s

300 s

var-response-timer

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

2 s - 10 s

5s


Glossary

10/100Base-T

10- to 100-Mb/s LAN An IEEE standard for 10/100 Mb/s twisted-pair Ethernet wiring.

10Base-T

An IEEE 802.3 LAN transmission standard for Ethernet. 10Base-T carries data at 10 Mb/s to a maximum distance of 328 ft (100 m) over unshielded twisted-pair wire.

100Base-FX

An IEEE 802.3 LAN transmission standard for 100 Mb/s Fast Ethernet using Long Wavelength (LX) laser transmitters over MMF for distances up to 1.25 mi (2 km). The 7302 ISAM and 7330 ISAM FTTN support an SMF implementation of 100Base-FX for distances up to 9.3 mi (15 km).

100Base-TX

An IEEE 802.3 LAN transmission standard for Fast Ethernet. 100Base-TX carries data at 100 Mb/s over two pairs of shielded twisted-pair or Category 5 unshielded twisted-pair wire.

1000Base-BX10

An IEEE 802.3 LAN transmission standard for bidirectional point-to-point 1000 Mb/s Gigabit Ethernet over SMF for distances of up to 6.2 mi (10 km). Always used in pairs, wavelength division multiplexing is performed in the SFP module to split the optical signal into two light paths. The 1000Base-BX10-D (downstream) SFP module transmits a 1490 nm signal and receives a 1310 nm signal. The 1000Base-BX10-U (upstream) SFP module transmits a 1310 nm signal and receives a 1490 nm signal.

1000Base-EX

A nonstandard implementation of the 1000Base-LX transmission standard with an extended reach up to 24.9 mi (40 km).

1000Base-LX

An IEEE 802.3 LAN transmission standard for 1000 Mb/s Gigabit Ethernet using Long Wavelength (LX) laser transmitters over fiber optic cable for distances up to 6.2 mi (10 km).

1000Base-SX

An IEEE 802.3 LAN transmission standard for 1000 Mb/s Gigabit Ethernet using Short Wavelength (SX) laser transmitters over fiber optic cable.


GL-1

Glossary

1000Base-ZX

A nonstandard implementation of the 1000Base-LX transmission standard operating at 1550 nm for distances up to 49.7 mi (80 km).

23 inch preconfigured rack

A 23 inch, 7 foot equipment rack with one or two ARAM-D shelves preinstalled. The rack can be extended to 9 ft or 11.5 ft in height.

3DES

Triple DES A mode of the DES encryption algorithm that encrypts data three times instead of once. Three 64-bit keys are used for an overall key length of 192 bits; the first encryption is encrypted with a second key, and the resulting cipher text is encrypted with a third key.

5523 AWS

The Alcatel-Lucent 5523 ADSL WorkStation

5526 AMS

The Alcatel-Lucent 5526 Access Management System A UNIX-based, client-server architecture controller for 7330 ISAM FTTN systems.

7300 ASAM

The Alcatel-Lucent 7300 Advanced Services Access Manager A DSLAM that delivers ATM-based services and provides an OC3c interface to the network side and ATM multiplexing and LT interfaces to the customer side. The ASAM also provides an OC3c interface to remote multiplexing equipment.

7302 ISAM

The Alcatel-Lucent 7302 Intelligent Services Access Manager A DSLAM that operates in a packet aggregation network. The 7302 ISAM enables deployment of triple-play services, such as video on demand, high-definition TV, and broadcast TV services for all subscribers simultaneously.

7330 ISAM FTTN

The Alcatel-Lucent 7330 Intelligent Services Access Manager Fiber to the Node A standalone DSLAM designed for the ease and rapid deployment of high-bandwidth IP services between high-bandwidth, optical fiber-based transmission media, and copper-based xDSL subscribers.

AAL

ATM Adaptation Layer A protocol used by ATM to segment and reassemble data for insertion into an ATM cell; also performs error checking and correction.

AAL1

ATM Adaptation Layer 1 Type 1 class of AAL service supporting constant bit rate, and time-dependent traffic such as voice and video.

AAL2

ATM Adaptation Layer 2 Type 2 class of AAL service characterized by voice and video transfer.

AAL5

ATM Adaptation Layer 5 Type 5 class of AAL service characterized by high-speed data transfer.

GL-2


Glossary

ACL

Access Control List

ACO

Alarm Cut Off A switch on the PWIO-B card that allows the audible alarms to be extinguished without affecting the visual alarms. The audible alarms can be toggled as enabled or disabled.

ACU

Alarm Control Unit A plug-in unit or built-in subsystem that collects shelf alarms and provides an alarm interface to the CO alarm system.

ADSL

Asymmetric DSL A variant of DSL with asymmetric upstream and downstream data rates. ADSL provides more bandwidth for downstream traffic (server to client) than for upstream (client to server). There are several types of ADSL including ADSL, ADSL2, READSL. All these types are collectively referred to as multi-ADSL.

AES

Advanced Encryption Standard A symmetric 128-bit block data encryption algorithm.

AIS

Alarm Indication Signal

ALP-248C cabinet

An Alcatel-Lucent Low Profile dual 48-inch remote terminal cabinet

ALP-248E cabinet

An Alcatel-Lucent Low Profile dual 48-inch remote terminal cabinet

AMP Champ

A common name for a 25-pair connector used on the 7330 ISAM FTTN to connect POTS CO lines and subscriber drop lines.

AMSL

Above Mean Sea Level

ANCP

Access Node Control Protocol

ANSI

American National Standards Institute A nonprofit, nongovernmental body supported by over 1000 trade organizations, professional societies, and companies; ANSI was established for the creation of voluntary industry standards.

APS

Automatic Protection Switching The capability of a transmission system to detect a failure on a working facility and switch to a protection facility to recover the traffic, thus increasing overall system reliability.

ARAM-D

ADSL Remote Access Multiplexer, version D

ARP

Address Resolution Protocol A protocol within TCP/IP that maps IP addresses to Ethernet MAC addresses. TCP/IP requires ARP for use with Ethernet.


GL-3

Glossary

ASCII

American Standard Code for Information Interchange A coding method used to convert letters, numbers, punctuation, and control codes into digital form.

ASEM-B

A 48-port multi-ADSL and POTS splitter remote expansion unit for the ARAM-D shelf. The ASEM-B features a flood resistant, environmentally hardened enclosure that is compliant with GR-950-CORE.

ASP

Access Service Provider

ATI

Alarms, Test Access, and Interfaces

ATM

Asynchronous Transfer Mode A multiplexed information transfer method in which the information is organized into fixed-length cells of 53 bytes and transmitted according to the needs of each user.

ATP

Aggregate Transmit Power

AWG

American Wire Gauge A standard measuring gauge for non-ferrous conductors.

BAC

Buffer Acceptance Control

BE

Best Effort

BER

Bit Error Rate A measure of transmission quality expressed as the percentage of received bits in error compared to the total number of bits received.

BITS

Building Integrated Timing Source A clock that supplies DS1 (1.554 Mb/s) or composite clock timing reference to all other clocks in a building.

blowfish

A freely available symmetric block cipher designed as a drop-in replacement for DES or IDEA. Blowfish allows variable-length keys of up to 448 bits.

BNC

Bayonet Neil-Concelman A locking connector for slim coaxial cables, such as those used for Ethernet.

BNG

Broadband Network Gateway

BOOTP

Bootstrap Protocol A member of the IP family of protocols that allows a diskless client machine to learn, among other information, its IP address. BOOTP starts a networked machine by reading boot information from a server. BOOTP is commonly used for desktop workstations and LAN hubs.

BRAS

GL-4

Broadband Remote Access Server


Glossary

BRI

Basic Rate Interface An ISDN interface consisting of two 64 kb/s B-channels and one 16 kb/s D-channel for a total of 144 kb/s.

CAC

Connection Admission Control An algorithm that evaluates whether or not a new connection can be added to the node. CAC examines QoS objectives defined by the PVC service category, as well as its configured traffic descriptor and traffic rates. CAC determines whether the system can satisfy these criteria for the PVC and whether the PVC will affect the guaranteed QoS that existing PVCs already have on the node.

CBR

Constant Bit Rate

CCSA

Checkpoint Certified Security Administrator or China Communications Standards Association

CDE

Customer Dependant Engineering The CDE file on a card contains country-specific information.

CEV

Controlled Environmental Vault A temperature- and humidity-controlled underground vault that houses the 7330 ISAM FTTN system at a remote location.

CFM

Cubic Feet per Minute

CHAP

Challenge Handshake Authentication Protocol A PPP authentication method for identifying a dial-in user. The user is given an unpredictable number and challenged to respond with an encrypted version. CHAP does not itself prevent unauthorized access; it only identifies the remote end.

CL

Controlled Load

CLEI

Common Language Equipment Identifier A 10-character code used to identify telecommunications equipment. The 10-character structure, outlined in the Telcordia specification, specifies the basic product type, features, source document, and associated drawings and versions. A CLEI code is unique to a specific piece of equipment.

CLI

Command Line Interface A workstation access method interface that uses CLI commands to communicate to any network element in the 7330 ISAM FTTN network.

CMOS

Complementary Metal Oxide Semiconductor

CMP

Communications Plenum Cable


GL-5

Glossary

CO

Central Office A telephone switching center that connects subscribers within a telephone network.

CODEC

Coder decoder

COLO

Collocation

CPCS

Common Part Convergence Sublayer The portion of the convergence sublayer of an AAL that remains the same regardless of traffic.

CPE

Customer Premises Equipment Customer-owned telecommunications equipment at customer premises used to terminate or process information from the public network.

CPE-MM

CPE Management Machine

CPR

Continuing Property Record A six-character code that can be used to classify equipment items into various property types. CPRs also provide property record unit identification that allows network service providers to create asset records for the purpose of equipment engineering, ordering, invoice processing, asset management, and auditing.

CPU

Central Processing Unit The part of a computer that performs the logic computational and decision-making functions.

CSMA/CD

Carrier Sense Multiple Access with Collision Detection A data communications mode in a shared medium in which access contention problems are solved by denying access to one of the contenders.

CT

Craft Terminal A workstation that has element management system software installed on it.

C-VLAN

Customer VLAN

CWDM

Coarse Wavelength Division Multiplexing

DA

Destination Address

DB-9

A 9-pin D-shell connector used for the craft port on the 7330 ISAM FTTN.

DES

Data Encryption Standard An ANSI symmetric-key encryption method that uses a 56-bit key and the block cipher method, which breaks text into 64-bit blocks and then encrypts them. DES was standardized by ANSI in 1981 as ANSI X.3.92.

DES-56 GL-6

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

Glossary

DHCP

Dynamic Host Configuration Protocol A client/server service that is an extension of the BOOTP protocol. DHCP simplifies the configuration of a client workstation since no IP addresses, subnet masks, default gateways, domain names, or DNSs must be programmed. With DHCP, this information is dynamically leased from the DHCP server for a predefined amount of time. Because the information is stored on a server, it centralizes IP address management, reduces the number of IP addresses to be used, and simplifies maintenance. RFC 2131 defines DHCP.

DLC

Data Link Connection A frame relay connection. or Digital Loop Carrier

DLP

Detailed Level Procedure

DMT

Discrete Multitone

DNS

Domain Name Server

DSCP

Differentiated Services Code Point A six-bit value encoded in the type-of-service field of an IP packet header. It identifies the CoS that the packet should receive.

DSL

Digital Subscriber Line A modem technology that enables high-speed data transmission between two modems, one at a service provider location and one at the subscriber premises, over a single twisted-pair copper telephone wire.

DSLAM

Digital Subscriber Line Access Multiplexer A network device that converts xDSL signals into ATM traffic. For a service management application, if the service user is connected to the ATM network through a DSLAM port, the network access is provisioned using a DSLAM attachment type.

DSP

Digital Service Provider

EAR

Ethernet Access Router

EAPOL

Extensible Authentication Protocol Over LAN

ECI

Equipment Catalog Item A six-digit numeric code that translates into the bar code on the bar code label. ECI codes are also used as internal processing codes.

ECMP

Equal Cost Multi-Path routing


GL-7

Glossary

EFM

Ethernet in the First Mile A set of copper and fiber-based access technologies that are based entirely on Ethernet packet transport.

eHCL

Electrical High Capacity Link

EIA

Electronic Industries Association A group that specifies electrical transmission standards. The EIA and TIA have developed numerous well-known communications standards, including EIA/TIA-232 and EIA/TIA-449.

EMAN

Ethernet Metropolitan Area Network

EMC

Electromagnetic Compatibility

EMI

Electromagnetic Immunity

EMS

Element Management System A system that manages the components of a network.

EOC

Embedded Operations Channel

EPS

Equipment Protection Switching The capability of physical equipment to detect a failure on a working facility and switch to a protection facility to recover the traffic, thus increasing overall system reliability.

ES

Expansion Shelf An expansion shelf using the same shelf as the 7330 ISAM FTTN host shelf (ARAM-D shelf), but with some different units installed to provide additional subscriber line connections for the host shelf.

ESD

Electrostatic Discharge

Ethernet

A data link layer protocol for interconnecting computer equipment into CSMA/CD LANs, jointly developed by Xerox, Digital Equipment Corporation, and Intel. This standard forms the basis for IEEE 802.3. The Ethernet protocol specifies how data is placed on, and retrieved from, a common transmission medium. It is used as the underlying transport vehicle by several upper-level protocols, including TCP/IP and UDP/IP.

ETR

Extended Temperature Range

ETSI

European Telecommunications Standards Institute The European counterpart to ANSI. Established to produce telecommunication standards integration in the European community for users, manufacturers, suppliers, and Post Telephone and Telegraph administration.

GL-8


Glossary

FDM

Frequency Division Multiplexing A form of multiplexing in which several independent signals are allocated separate frequency bands for transmission over a common channel.

FE

Fast Ethernet

FEMF

Foreign Electro-Motive Force

FENT

Fast Ethernet Network Termination

FEXT

Far-end XTalk (crosstalk)

FIB

Forwarding Information Base An internal table containing only the IP routes actually used by a router to forward IP traffic.

FIFO

First In, First Out

FPGA

Field Programmable Gate Array An integrated chip with functions that can be programmed by software.

FTP

File Transfer Protocol

FTTN

Fiber to the node See 7330 ISAM FTTN.

GE

Gigabit Ethernet Ethernet interface running at 1000 Mb/s.

GFC

General Facilities Card See PWIO-B.

GUI

Graphical User Interface A user screen that includes menus, tables, or icons to query or change data; usually distinguished from the command line interface.

HSI

High Speed Internet

IACM

Intelligent Access Termination, Control and Management

iBridge

Intelligent Bridging mode, also known as residential bridging mode

ICS

Item Change Status A code that identifies the change status of an Alcatel-Lucent unit or component.

IDEA

International Data Encryption Algorithm A symmetric-key encryption method that uses a 128-bit key and the block cipher method, which breaks text into 64-bit blocks and then encrypts them.


GL-9

Glossary

IEEE

Institute of Electrical and Electronics Engineers A worldwide engineering publishing and standards-making body. It is the organization responsible for defining many of the standards used in the computer, electrical, and electronics industries.

IETF

Internet Engineering Task Force An organization that provides the coordination of standards and specification development for TCP/IP networking.

IGFET

Insulated Gate Field Effect Transistor

IGMP

Internet Group Management Protocol A protocol used between hosts and multicast routers on a single physical network to establish hosts’ membership in particular multicast groups. Version 2 of IGMP is described in RFC 2236.

IGS

IGMP System on the SHub

IMA

Inverse Multiplexing for ATM

INP

Impulse Noise Protection The ability to protect equipment from excessive noise and vibrations, which cause signal degradation over xDSL lines.

IP

Internet Protocol A connectionless packet-switching protocol that works together with TCP.

IP@

Internet Protocol Address

IPCP

IP Control Protocol A protocol that configures, enables, and disables the IP protocol modules on both ends of a point-to-point link. IPCP is tied to PPP, and activated when PPP reaches the network layer-to-protocol phase. If IPCP packets are received prior to this phase, they are discarded.

IPoA

Internet Protocol over ATM

IPoE

Internet Protocol over Ethernet

IPTV

IP Video/Television The delivery of video services over an end-to-end IP infrastructure. IPTV can include various classes of video services including video on demand, broadcast TV, video conferencing, and mobile video.

ISAM

Intelligent Services Access Manager See 7302 ISAM or 7330 ISAM FTTN.

ISDN

Integrated Services Digital Network

ISP

Internet Service Provider

GL-10


Glossary

ITSC

Integrated Test and Sealing Current A feature that includes narrowband line testing functionality as well as sealing current for subscriber lines connected to the ARAM-D shelf.

ITU

International Telecommunications Union A standards organization that develops international telecommunications recommendations.

IXL

Index List

JFET

Junction Field Effect Transistor

L2

Layer 2

L3

Layer 3

LACP

Link Aggregation Control Protocol An IEEE specification (802.3ad) that allows you to bundle several physical ports together to form a single logical channel.

LAN

Local Area Network A type of network that sends and receives communications over a small area, such as within an office or group of buildings.

LANX

7330 ISAM FTTN Network Termination card Ethernet switch (also known as SHub)

LC

Lucent Connector A small optical fiber connector.

LCP

Link Control Protocol A protocol that LCP establishes, configures, and tests data-link connections for use by PPP.

LED

Light Emitting Diode A semiconductor diode that emits light when a current is passed through it.

LIM

Line Interface Module The EALT-A, EBLT-A, and EBLT-J cards are L2-based LIMs. The EBLT-C, EBLT-D, EVLT-A, EVLT-C, EVLT-D, and EVLT-E cards are L3-based LIMs.

LMI

Line Management Interface

LOS

Loss of Signal A condition at the receiver or a maintenance signal transmitted in the physical overhead, indicating that the receiving equipment has lost the received signal.


GL-11

Glossary

LPF

Low-pass Filter A single transmission band extending from zero frequency up to a specified cutoff frequency, not infinite.

LP slot

A slot in the 7330 ISAM FTTN shelf where an applique is installed.

LSA

Link State Advertisement A message of the OSPF routing protocol that informs about network topology changes.

LSDB

Link State Database A database used to compute network routes after each change of topology that has been reported by the routing protocol.

LSM

Line Server Module A generic term including xDSL line interface modules and any other server application-specific module.

LT

Line Termination

MAC

Media Access Control The IEEE sublayer in a LAN that controls access to the shared medium by LAN attached devices.

MAIP

Maintenance Access Interface Port or Multipurpose Alarm Interface Panel A panel, located in the electronics compartment of a 52-type cabinet that provides fused dc power to the 7330 ISAM FTTN shelf and cabinet fans, as well as cabinet and power alarm outputs.

MAU

Media Attachment Unit

MD5

Message Digest algorithm 5 A security algorithm that takes an input message of arbitrary length and produces as an output a 128-bit message digest of the input. MD5 is intended for digital signature applications, where a large file must be compressed securely before being encrypted.

MDF

Main Distribution Frame

MDI

Medium-Dependent Interface A type of Ethernet port for use with twisted-pair wiring.

GL-12


Glossary

MDIX

Medium-Dependent Interface Crossover The crossover version of MDI that enables the connection of like devices using straight-through twisted-pair for MDI port-to-MDIX port connections, and crossover twisted-pair for MDI-to-MDI or MDIX-to-MDIX connections.

Megaco

Media Gateway Controller

MIB

Management Information Base

MMF

Multimode Fiber An optical fiber with a core diameter of 50 to 100 μm most commonly used in short distance LANs. The larger core diameter allows broader light sources such as LEDs. Modal dispersion is a problem over longer distances.

MOS

Metal Oxide Semiconductor

M-pair

Multi-pair

MSTP

Multiple Spanning Tree Protocol An extension of RSTP that allows different spanning trees to co-exist on the same Ethernet switched network.

MTA

Metallic Test Access

MTAU

Metallic Test Access Unit

MTBF

Mean Time Between Failures

Multi-ADSL

A general term that refers to more than one type of ADSL (for example, ADSL, ADSL2, and READSL).

NACP

Network Access Control Protocol

NAT

Network Address Translation

NE

Network Element

NEBS

Network Equipment Building Standards Performance, quality, environmental, and safety standards set by Telcordia for telecommunications equipment.

NFS

Network File System A distributed file system protocol suite developed by Sun Microsystems that allows remote file access across a network. NFS is one protocol in the suite. The protocol suite includes NFS, RPC, and XDR. These protocols are part of a larger architecture that Sun refers to as ONC.

NSA

Non-Service Affecting

NSP

Network Service Provider


GL-13

Glossary

NT

Network Termination A plug-in unit that provides a link to a broadband network, such as ATM or IP. The 7330 ISAM FTTN uses the ECNT-A or ECNT-C card for network termination.

NTA slot

Network Termination slot A The slot on the 7330 ISAM FTTN shelf for an NT unit. There are two slots for NT units, marked as A and B.

NTB slot

Network Termination slot B The slot on the 7330 ISAM FTTN shelf for an NT unit. There are two slots for NT units, marked as A and B.

NTP

Non-Trouble Procedure

OAM

Operation, Administration, and Maintenance Broad categories of functions found in a communications network and/or the business processes found in network service provider companies.

OBC

On-Board Controller

ONC

Open Network Computing

OOS

Out-of-service The status of a primary rate link when it is out of service.

OS

Operations System A standalone software system that supports network-related operations functions.

OSP

Outside Plant

OSPF

Open Shortest Path First A dynamic routing protocol that responds quickly to network topology changes. As a successor to RIP, it uses an algorithm that builds and calculates the shortest path to all known destinations.

OSS

Operations Support System

OSWP

Overall Software Package

PADI

PPPoE Active Discovery Initiation

PDF

Power Distribution Frame

PDU

Protocol Data Unit

POTS

Plain Old Telephone Service A term for narrowband, voice-only telephone service.

PPP GL-14

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

Glossary

A protocol that allows a computer to use TCP/IP with a standard telephone line and a high-speed modem to establish a link between two terminal installations. PPPoA

Point-to-Point Protocol over ATM

PPPoE

Point-to-Point Protocol over Ethernet A specification for connecting multiple computer users on an Ethernet LAN to a remote site through common CPE. PPPoE allows users to share a common xDSL, cable modem, or wireless connection to the Internet. PPPoE combines the PPP protocol, commonly used in dial-up connections, with the Ethernet protocol, which supports multiple users in a LAN. The PPP protocol information is encapsulated within an Ethernet frame.

PSD

Power Spectral Density

PSTN

Public Switched Telephone Network A telephone network based on normal telephone signaling and ordinary switched long distance telephone circuits.

PTC

Positive Temperature Coefficient A type of thermal resistor used for current limiting in circuitry.

PTM

Packet Transfer Mode A DSL framing mode that allows DSL equipment to transport packet-based (for example, Ethernet or IP packets) rather than ATM-based data. PTM involves 64/65 byte block coding of variable size frames or frame fragments at the transmission convergence sublayer in the modem. PTM is defined in the G.992.3 (ADSL2) and G.992.5 (ADSL2+) standards.

PVC

Permanent Virtual Connection

PVID

Port VLAN Identifier

QoS

Quality of Service A measure of the quality of a data communications link provided to a subscriber.

RADIUS

Remote Authentication Dial-in User Service A standardized method of information exchange between a device that provides network access to users (RADIUS client) and a device that contains authentication and profile information for the users (RADIUS server).

RAL

Restricted Access Location

RAM

Remote Access Multiplexer

RARP

Reverse Address Resolution Protocol

RB VLAN

Residential Bridging VLAN

RDI

Remote Defect Indication


GL-15

Glossary

READSL2

Reach Extended ADSL2

RED

Random Early Detection

REN

Ringer Equivalence Number

RFC

Request for Comments The name of the result and the process for creating a standard on the Internet. New standards are proposed and published online, as a Request For Comments. The IETF is the consensus-building body that facilitates discussion, and eventually a new standard is established. RFC is the prefix for all published IETF documents for Internet environment standards; for example, the official standard for e-mail is RFC 822. RFC documents typically define IP, TCP, and related application layer protocols.

RFT

Remote Feeding Telecommunication

RIP

Routing Information Protocol An interior gateway protocol defined by the IETF (RIPv1 - RFC 1058 and RIPv2 - RFC 2453) that specifies how routers exchange routing table information. RIP is a routing protocol based on the distance vector algorithm. With RIP, routers periodically exchange entire tables.

RJ-45

A single-line jack for digital transmission over ordinary phone wire, either untwisted or twisted. It is the interface for Ethernet standards 10Base-T and 100Base-T.

RMI

Remote Management Interface

RNM

Residential Network Manager

RSTP

Rapid Spanning Tree Protocol A protocol specified in IEEE 802.1w. It replaces the spanning tree protocol specified by IEEE 802.1d. RSTP is targeted at switched networks with point-to-point interconnections, and allows for much quicker reconfiguration time (approximately 1 s) by allowing a rapid change in port roles.

RTL

Routine Task List

RTP

Real-time Transport Protocol

RTU

Remote Test Unit

RU

Rack Unit A unit of vertical space in a standard 19 inch or 23 inch equipment rack. One RU is 1.75 in. (4.45 cm).

Rx

receive To receive or carry signals or data to a device; any part of the equipment that converts or decodes signals or data entering the equipment into the desired form for use by the equipment.

GL-16


Glossary

SA

Service Affecting or Source Address

SAP

Service Access Point

SDU

Service Data Unit A unit of information from an upper-layer protocol that defines a service request to a lower-layer protocol.

SELT

Single-Ended Line Testing

SELV

Safety Extra Low Voltage

SEM

Sealed Expansion Module A remote expansion unit for the 7330 ISAM FTTN. The SEM is a single LT unit in a flood resistant, environmentally hardened enclosure designed for remote outside deployment in hard-to-reach or low-density locations. See also ASEM-B and VSEM-A.

SFP

Small Form-factor Pluggable A specification for a new generation of optical modular transceivers. The devices are designed for use with small form-factor connectors, and offer high speed and physical compactness. They are hot-swappable.

SFTP

Secured File Transfer Protocol

SHDSL

Symmetric High-speed Digital Subscriber Line

SHub

7330 ISAM FTTN and 7302 ISAM Network Termination card Ethernet switch (also known as LANX).

SI

Système international d’unités

SIP

Session Initiation Protocol

SLIC

Subscriber Line Interface Circuit

SMF

Single Mode Fiber An optical fiber with a core diameter of less than 10 μm that is used for high-bandwidth transmission over long distances.

SNMP

Simple Network Management Protocol A protocol used by network management to retrieve information about connection status, configuration, and performance.

SNTP

Simple Network Time Protocol A method of synchronizing network nodes. An SNTP server can be used by multiple nodes to synchronize themselves.


GL-17

Glossary

SONET

Synchronous Optical Network A transmission network that uses high-speed optical carriers.

SRA

Seamless Rate Adaptation

SSCS

Service-specific convergence sublayer

SSH

Secure Shell

STP

Spanning Tree Protocol A technique based on an IEEE 802.1d standard that detects and eliminates forwarding loops in a bridged network. When multiple paths exist, STP selects the most efficient path for the bridge to use. If that path fails, STP automatically reconfigures the network to activate another path. This protocol is used mostly by local bridges.

STU-C

SHDSL Transceiver Unit – Central Office

STU-R

SHDSL Transceiver Unit – Remote

S-VLAN

Stacked VLAN

SWDB

SoftWare DataBase

SWP

SoftWare Package

TAC

Test Access Control

TAP

Test Access Port or Trouble Analysis Procedure

TAU

Test Access Unit

TCA

Threshold Crossing Alarm

TCP

Transmission Control Protocol A protocol for establishing a duplex connection between end systems for the reliable delivery of data.

TCP/IP

Transmission Control Protocol/Internet Protocol A networking protocol that provides communication across interconnected networks, and between computers with different hardware architectures and various operating software.

TFTP

Trivial File Transfer Protocol

TIA

Telecommunications Industries Association The group responsible for setting telecommunications standards in the United States.

GL-18


Glossary

TL1

Transaction Language 1 Human-machine language standard for controlling network elements.

TNG

Training Document

TNV

Telecom Network Voltage

TOP

Task-Oriented Practice The TOP method is a documentation system that supports the installation, operation, and maintenance of telecommunications equipment and software through different layers of documentation.

Tx

transmit To send or carry signals or data from a device; any part of the equipment that converts or encodes signals or data exiting from the equipment into the desired form for transmission to other equipment.

UA

User Agent

UDP/IP

User Datagram Protocol/Internet Protocol A transport layer, connectionless mode protocol, providing a datagram mode of communication for delivery to a remote or local user. UDP is part of the TCP/IP suite.

UDS

Unit Data Sheet

UPBO

Upstream Power Back-Off

UPS

Uninterruptible Power Supply

URI

Universal Resource Identifier

USM

User-based Security Model

VACM

View-based Access Control Model

VBAS

Virtual Broadcast Access Server

VC

Virtual Channel A single communications connection identified by an office equipment number, VPI, and VCI.

VCC

Virtual Channel Connection

VCI

Virtual Channel Identifier An identifier in an ATM cell that distinguishes the data of one VC from the data of another VC.

VCL

Virtual Channel Link

VC/VP/VR

Virtual Channel/Virtual Path/Virtual Router


-19

Glossary

VDSL

Very High Bit Rate DSL A variant of DSL that provides very high speed asymmetric data transmission rates over a single twisted-pair copper telephone wire, but at shorter ranges than other xDSL types. There is more than one type of VDSL.

VLAN

Virtual LAN A VLAN divides a physical LAN into multiple virtual LANs whose members are not necessarily based on location. VLAN specifications are contained in IEEE 802.1q.

VoD

Voice on Demand

VoIP

Voice over IP

VP

Virtual Path A single communications connection identified by an office equipment number and a VPI.

VPI

Virtual Path Identifier An identifier in an ATM cell that distinguishes the data of one VP from the data of another VP.

VP/VC

Virtual Path/Virtual Channel

VRF

Virtual Routing Forwarder A logical or virtual routing function with associated routing table that can be instantiated in a router capable of supporting IP VPN services.

VTU-O

VDSL Transceiver Unit – Central Office

VTU-R

VDSL Transceiver Unit – Remote

WAN

Wide Area Network

WECO

Western Electric Company For WECO-spaced racks, 1 RU equals 2 in. (5.08 cm).

WFQ

Weighted Fair Queue

WRED

Weighted Random Early Detection

WRR

Weighted Round Robin

xDSL

A general term that is used to refer to more than one type of DSL (for example, ADSL, ADSL2, READSL, SHDSL, VDSL, VDSL2).

xTU-C

xDSL Transceiver Unit – Central Office

xTU-R

xDSL Transceiver Unit – Remote

XoA encapsulation

A general term used to refer to an unspecified type of encapsulation over ATM.

-20


Glossary


-21

Glossary

-22


Index

Numbers 7330 ISAM FTTN configuration for subtending, TNG 112-1 ES configuration, TNG 111-1 expansion unit management, TNG 106-4 maintaining, NTP 124-1 802.1x configure authentication, NTP 108-2 configuring, DLP 145-1 disabling, DLP 145-1 802.1x parameters configuring, DLP 145-1

A ADSL profile configuration example, TNG 110-3 alarms creating snapshots, DLP 154-2 fault isolation, TAP 104-1 managing, DLP 110-2 monitoring, NTP 115-1, DLP 155-1 SHub, TAP 104-1 system, TAP 104-1 troubleshooting, TAP 104-1 viewing alarm logs, DLP 110-2 viewing current alarms, DLP 110-2 viewing snapshots, DLP 154-2

ANCP configure session, DLP 185-2 ARP configure table entry, DLP 150-1

B basic data traffic configuration example, TNG 110-5 cross-connect VLAN configuration example, TNG 110-13 iBridge VLAN configuration example, TNG 110-11 basic management connectivity configuration example, TNG 110-2 bridge configure general parameters, DLP 195-1 configure IP-aware bridge, NTP 106-2

C C-VLAN create, DLP 117-1 CC-VLAN, NTP 104-2, TNG 100-2 configure QoS-aware VLAN, DLP 135-2 create C-VLAN, DLP 117-1 create S-VLAN, DLP 118-1 create SC-VLAN, DLP 119-2


IN-1

Index CLI session — iBridge

CLI session setting up, DLP 100-1 cluster management, NTP 122-2 configure, DLP 169-2 configuration 7330 ISAM FTTN ES, TNG 111-1 7330 ISAM FTTN subtending, TNG 112-1 backing up, RTP 100-3 CPE management, NTP 121-2 CPE remote management configure, DLP 166-1 cross-connect VLAN configuration example, TNG 110-13

D database restore, RTP 101-1 DHCP Option 82, TNG 104-2 DHCP relay configure, NTP 108-2 DHCP relay agent conditions, TNG 104-3 configuring forwarder mode, DLP 141-1 iBridge mode, DLP 139-2 MAC concentration, DLP 186-2 router mode, DLP 140-2 general description, TNG 104-1 parameters, TNG 104-2 restrictions, TNG 104-3 DPBO configure profile, DLP 206-1 modify profile, DLP 207-1 DSL profile configuration example, TNG 110-3

F F5 loopback test, TAP 101-1 fault isolation alarms, TAP 104-1 events, TAP 104-1 forwarding modes CC-VLAN, TNG 100-2 iBridge VLAN, TNG 100-2 layer 2 termination, TNG 100-2

G GENC-E expansion links, TNG 106-4

E EDSE-A expansion links, TNG 106-4 EFMOAM configuration parameters, TNG 116-2 general description, TNG 116-1 EMS management, DLP 171-1 IN-2

equipment configuring, DLP 113-1 configuring and modifying, NTP 103-2 planning, DLP 111-2 repairing, NTP 114-1, TAP 102-1 replanning, DLP 111-2 restarting, DLP 153-1 shutting down, DLP 153-1 unplanning, DLP 111-2 equipment planning configuration example, TNG 110-2 ES CLI commands, TNG 106-1 configuration, TNG 111-1 expansion link connections, TNG 106-4 identifying, TNG 106-1 MAC address, TNG 106-1, TNG 106-4 events fault isolation, TAP 104-1 troubleshooting, TAP 104-1 expansion links EDSE-A, TNG 106-4 GENC-E, TNG 106-4

I iBridge add user, NTP 110-1


Index iBridge VLAN — planning equipment

iBridge VLAN, TNG 100-2 configuration example, TNG 110-11 create, DLP 120-1 IGMP configure, NTP 108-2 configuring IGMP proxy, DLP 137-1 parameters, TNG 102-2 system parameters configuring, DLP 137-1 viewing configuration, TNG 102-5 IGMP snooping configure, DLP 138-1 IMA configure, DLP 183-1 IP address convert to dual IP address, DLP 184-1 convert to single IP address, DLP 184-1 IP address allocation, TNG 104-2 IP multicast configuration guidelines, TNG 102-5 IP router configure, NTP 107-2 IP-aware bridge configure, NTP 106-2 IPoA add cross-connect user, NTP 125-1 add user, NTP 111-1 create cross-connect user, DLP 174-1 create user, DLP 125-1 IPoE add user, NTP 112-1 create user, DLP 126-1 IPProxy CPE configure management, DLP 192-1 configure session, DLP 194-1 enable management, DLP 193-1 IPProxy CPE management, NTP 128-2

L layer 2 termination, TNG 100-2 link aggregation configuring, DLP 105-2 Link Related Ethernet OAM configure, DLP 205-1

local authentication configure, NTP 108-2 configuring, DLP 143-2 loopback interface on SHub, NTP 129-1

M MAC address, TNG 106-4 configure static MAC address, DLP 180-1 MAC concentration configuration, DLP 186-2 MAC learning, TNG 100-5 MSTP configuring, DLP 200-2 multicast configure, NTP 108-2 configure on LT, DLP 136-1 configure on the SHub, DLP 198-1 configuring, DLP 137-1

N NT redundancy configuring, DLP 114-2

O operator create default profile, DLP 172-1 OSFP configuring, DLP 107-2 OSWP management, DLP 159-1

P password rules, DLP 101-1 PBO configure, DLP 208-1 performance monitoring, NTP 118-1 commands, DLP 176-1 ping, DLP 164-1 planning equipment configuration example, TNG 110-2


IN-3

Index plug-in unit — SHub

plug-in unit locking, DLP 112-1 unlocking, DLP 112-1 plug-in units configuring, NTP 103-1 port view configuration, DLP 197-1 view operational data, DLP 197-1 PPPoA-PPPoE relay configure, NTP 108-2 disabling, DLP 147-1 enabling, DLP 147-1 PPPoE add user, NTP 113-1 create user, DLP 127-1 enable PPPoE server, DLP 148-1 profiles configure, DLP 149-1 PPPoE profile configure, DLP 149-1 PPPoE relay, NTP 108-2 disabling, DLP 146-2 enabling, DLP 146-2 PPPoE termination configure, NTP 109-1 protocol tracing configuration, DLP 201-1

Q QoS configure, NTP 108-2 configuring L3, DLP 134-1 QoS-aware VLAN, DLP 135-2 configuring on the SHub, DLP 199-1 configuring TCA, DLP 202-1

R RADIUS configure, NTP 108-2 configuring, DLP 144-1 operator authentication, DLP 181-1 remote expansion units, TNG 110-1

IN-4

remote inventory retrieving information, RTP 102-1 RIP configuring, DLP 108-1

S S-VLAN create, DLP 118-1 SC-VLAN create, DLP 119-2 script files, NTP 101-1 create, DLP 167-2 secure shell, NTP 123-1 security configuring general settings, DLP 203-1 security domain configure, NTP 108-2 creating, DLP 142-1 creating default domain, DLP 178-1 SELT, TAP 103-1 SEM CLI commands, TNG 106-1 expansion link connections, TNG 106-4 identifying, TNG 106-1 MAC address, TNG 106-1 planning, TNG 106-4 services adaptation, NTP 119-1 configuring, NTP 108-1 SHDSL configuration parameters segment, TNG 108-16 span, TNG 108-3 unit, TNG 108-15 configure links, DLP 182-1, DLP 182-1 operational parameters segment, TNG 108-23 span, TNG 108-17 unit, TNG 108-22 SHub configure filtering, DLP 132-2 dual tagging enable, DLP 191-1 loopback interface, NTP 129-1


Index SHub (continued) — vMAC

managing the database, DLP 157-1 MSTP management, DLP 200-2 restarting, DLP 151-3 shutting down, DLP 151-3 SW version, DLP 160-1 SHub alarm definitions, TAP 104-1 SHub MAC filters, TNG 100-6 SNMP configure, DLP 109-2 software management, NTP 116-1 SSH, NTP 123-1 configure, DLP 170-2 subtending configuration for 7330 ISAM FTTN, TNG 112-1 SW licences view counters, DLP 161-2 system configuring, NTP 102-2 forwarding modes, TNG 100-2 IP address configure single IP address, DLP 175-1 maintaining, NTP 124-1 modigy management IP parameters, DLP 168-1 reboot modes, DLP 152-1 rebooting, DLP 152-1 system alarm definitions, TAP 104-1 system clock, DLP 103-2 system IP address configure dual IP address, DLP 102-1, DLP 102-1 system logging, NTP 126-2 configure, DLP 179-1 system parameter modification, NTP 117-1 system time, DLP 103-2

T TCA configure, DLP 190-2 traceroute, DLP 165-1

traffic configuration example, TNG 110-5 trap configuring, DLP 109-2 reporting modes, DLP 109-2 troubleshooting alarms, TAP 104-1 events, TAP 104-1 troubleshooting commands, NTP 120-1

U unicast configuration, TNG 100-5 unnumbered IP interface configure, DLP 204-1 user create IPoA user, DLP 125-1 create IPoE user, DLP 126-1 create PPPoE user, DLP 127-1 create xDSL user, DLP 124-2 creating and configuring, DLP 101-2 switch from ADSL to VDSL, DLP 173-1

V VDSL profile configuration example, TNG 110-3 VLAN add an LT to a VLAN, DLP 128-1 add network interfaces, DLP 121-1 configure iBridge VLAN, NTP 105-2, NTP 127-1, NTP 130-1 configuring global parameters, DLP 187-1 cross-connect VLAN configuration example, TNG 110-13 iBridge VLAN configuration example, TNG 110-11 L2-terminated router VLAN create, DLP 115-2, DLP 116-3 modifying external management VLAN, DLP 162-1 subtending configuration for 7330 ISAM FTTN, TNG 112-1 vMAC configure, DLP 209-2, DLP 210-1


IN-5

Index Voice SIP — xDSL profiles

Voice SIP configure, DLP 196-1 VRF creating, DLP 121-1 forwarding VRF, DLP 122-1 router VRF, DLP 123-1

X xDSL create user, DLP 124-2 xDSL bonding group create, DLP 130-2 create profile, DLP 130-2 xDSL profile custom PSD points ADSL2+, DLP 188-2 VDSL, DLP 188-2 VDSL2, DLP 188-2 modify, DLP 163-1 types, DLP 129-1 VDSL2 virtual noise, DLP 189-2 xDSL profiles create, DLP 129-2

IN-6


Customer documentation and product support Customer documentation http://www.alcatel-lucent.com/osds Product manuals and documentation updates are available through the Alcatel-Lucent Support Documentation and Software Download service at alcatel-lucent.com. If you are a new user and require access to this service, please contact your Alcatel-Lucent sales representative.

Technical support http://www.alcatel-lucent.com/support

Customer documentation feedback [email protected]

© 2007 Alcatel-Lucent. All rights reserved. 3HH-05218-AAAA-TQZZA Edition 02 Released

Operations and Maintenance Using CLI

Recommend Documents