Operations and Maintenance Using CLI

(1)

Alcatel-Lucent 7302

INTELLIGENT SERVICES ACCESS MANAGER

Alcatel-Lucent 7330

INTELLIGENT SERVICES ACCESS MANAGER FIBER TO THE NODE

Alcatel-Lucent 7356

INTELLIGENT SERVICES ACCESS MANAGER FIBER TO THE BUILDING

O P E R A T I O N S A N D M A I N T E N A N C E U S I N G C L I F O R F D 2 4 G B P S N T

(2)

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

Alcatel-Lucent assumes no responsibility for the accuracy of the information presented, which is

subject to change without notice.

Alcatel, Lucent and the Alcatel-Lucent logo are registered trademarks of Alcatel-Lucent. All other

trademarks are the property of their respective owners.

Copyright 2011 Alcatel-Lucent.

All rights reserved.

Disclaimers

Alcatel-Lucent products are intended for commercial uses. Without the appropriate network design

engineering, they must not be sold, licensed or otherwise distributed for use in any hazardous

environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft

navigation or communication systems, air traffic control, direct life-support machines, or weapons

systems, in which the failure of products could lead directly to death, personal injury, or severe physical

or environmental damage. The customer hereby agrees that the use, sale, license or other distribution

of the products for any such application without the prior written consent of Alcatel-Lucent, shall be at

the customer's sole risk. The customer hereby agrees to defend and hold Alcatel-Lucent harmless from

any claims for loss, cost, damage, expense or liability that may arise out of or in connection with the

use, sale, license or other distribution of the products in such applications.

This document may contain information regarding the use and installation of non-Alcatel-Lucent

products. Please note that this information is provided as a courtesy to assist you. While Alcatel-Lucent

tries to ensure that this information accurately reflects information provided by the supplier, please refer

to the materials provided with any non-Alcatel-Lucent product and contact the supplier for

confirmation. Alcatel-Lucent assumes no responsibility or liability for incorrect or incomplete

information provided about non-Alcatel-Lucent products.

However, this does not constitute a representation or warranty. The warranties provided for

Alcatel-Lucent products, if any, are set forth in contractual documentation entered into by

Alcatel-Lucent and its customers.

This document was originally written in English. If there is any conflict or inconsistency between the

English version and any other version of a document, the English version shall prevail.

(3)

Preface

This preface provides general information about the documentation set for the

7302 Intelligent Services Access Manager (7302 ISAM), the 7330 Intelligent

Services Access Manager Fiber to the Node (7330 ISAM FTTN) and the 7356

Intelligent Services Access Manager Fiber to the Building (7356 ISAM FTTB).

Scope

This documentation set provides information about safety, features and

functionality, ordering, hardware installation and maintenance, CLI and TL1

commands, and software upgrade and migration procedures for the current release.

Audience

This documentation set is intended for planners, administrators, operators, and

maintenance personnel involved in installing, upgrading, or maintaining the 7302

ISAM, the 7330 ISAM FTTN or the 7356 ISAM FTTB.

Required knowledge

Readers must be familiar with general telecommunications principles.

Product naming

When the term “ISAM” is used alone, the 7302 ISAM, the 7330 ISAM FTTN and

the 7356 ISAM FTTB are meant. If a feature is valid for only one of the products,

the applicability will be explicitly stated.

(4)

Preface

iv December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02

Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA

Documents

Refer to the Product Information document for your product to see a list of all

relevant customer documents and their part numbers.

Acronymns and initialisms

The expansions and optional descriptions of most acronyms and initialisms appear

in the glossary which is included in the System Description for FD 24Gbps NT

document.

Assistance and ordering phone numbers

Alcatel-Lucent provides global technical support through regional call centers.

Phone numbers for the regional call centers are available at the following URL:

http://www.alcatel-lucent.com/myaccess.

For ordering information, contact your Alcatel-Lucent sales representative.

Safety information

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

Special information

The following are examples of how special information is presented in this

document.

Danger — Danger indicates that the described activity or situation

may result in serious personal injury or death; for example, high

voltage or electric shock hazards.

Warning — Warning indicates that the described activity or situation

may, or will, cause equipment damage or serious performance

problems.

Caution — Caution indicates that the described activity or situation

may, or will, cause service interruption.

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

interest.

(5)

Preface

Release notes

Be sure to refer to the release notes (such as the Customer Release Notes or

Emergency Fix Release Note) issued for software loads of your product before you

install or use the product. The release notes provide important information about the

software load.

(6)

Preface

vi December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02

(7)

Preface

iii

Scope ... iii

Audience ... iii

Required knowledge ...iii

Product naming ... iii

Documents ... iv

Acronymns and initialisms ... iv

Assistance and ordering phone numbers ... iv

Safety information... iv

Special information... iv

Release notes... v

1 —

Introduction

1-1

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

Index List (IXL)

(8)

Contents

viii December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02

Non-Trouble Procedures (NTP)

NTP 1101 — Execute script files

NTP 1101-1

NTP 1114 — Perform equipment repairs

NTP 1114-1

NTP 1118 — Monitor performance and view

configuration

NTP 1118-1

NTP 1119 — Modify DSL services

NTP 1119-1

NTP 1124 — Maintain the system

NTP 1124-1

NTP 1126 — Manage system logging

NTP 1126-1

NTP 1127 — Configure SHDSL

NTP 1127-1

NTP 1130 — Configure Link Related Ethernet OAM

NTP 1130-1

NTP 1132 — Configure Connectivity Fault Management NTP 1132-1

NTP 2100 — Initial system configuration

NTP 2100-1

NTP 2103 — Configure equipment

NTP 2103-1

NTP 2104 — Configure a VLAN cross-connect

NTP 2104-1

NTP 2105 — Configure an iBridge VLAN

NTP 2105-1

NTP 2106 — Configure an IP-aware bridge

NTP 2106-1

NTP 2107 — Configure an IP router

NTP 2107-1

(9)

Contents

NTP 2115 — Monitor alarms

NTP 2115-1

NTP 2116 — Perform software management

NTP 2116-1

NTP 2117 — Modify system parameters

NTP 2117-1

NTP 2120 — Troubleshooting the network

NTP 2120-1

NTP 2121 — Manage an SNMP proxy CPE

NTP 2121-1

NTP 2122 — Cluster management

NTP 2122-1

NTP 2129 — Configure a loopback interface on the

SHub

NTP 2129-1

NTP 2133 — Configure an enhanced IP router

NTP 2133-1

Detailed Level Procedures (DLP)

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

session

DLP 1100-1

DLP 1112 — Lock and unlock equipment

DLP 1112-1

DLP 1113 — Configure the equipment

DLP 1113-1

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

cross-connect

DLP 1117-1

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

(10)

Contents

x December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02

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

cross-connect

DLP 1119-1

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

DLP 1120-1

DLP 1124 — Create an xDSL/native Ethernet user and

add this user to a VLAN on the LT

DLP 1124-1

DLP 1129 — Create xDSL profiles

DLP 1129-1

DLP 1130 — Configure xDSL bonding

DLP 1130-1

DLP 1134 — Configure QoS

DLP 1134-1

DLP 1145 — Configure 802.1x

DLP 1145-1

DLP 1146 — Configure PPPoE relay on LT

DLP 1146-1

DLP 1147 — Configure PPPoX cross-connect

DLP 1147-1

DLP 1151 — Shut down and restart the NT

DLP 1151-1

DLP 1152 — Reboot the system

DLP 1152-1

DLP 1153 — Shut down and restart individual

equipment

DLP 1153-1

DLP 1159 — Manage OSWP

DLP 1159-1

DLP 1163 — Modifying xDSL profiles

DLP 1163-1

DLP 1170 — Configure SSH and SFTP

DLP 1170-1

(11)

Contents

DLP 1174 — Create an xDSL IPoA user and add this user

to a VLAN on the LT for C-VLAN

cross-connect

DLP 1174-1

DLP 1182 — Configure SHDSL

DLP 1182-1

DLP 1183 — Configure IMA on SHDSL spans

DLP 1183-1

DLP 1187 — Configure global VLAN parameters on the

LT

DLP 1187-1

DLP 1188 — Configure custom PSD points

DLP 1188-1

DLP 1189 — Configure VDSL2 virtual noise values

DLP 1189-1

DLP 1190 — Configure threshold crossing alerts

DLP 1190-1

DLP 1197 — View port configuration and operational

data on LT

DLP 1197-1

DLP 1201 — Configure protocol tracing

DLP 1201-1

DLP 1202 — Configure QoS threshold crossing alerts

DLP 1202-1

DLP 1203 — Configure general security settings

DLP 1203-1

DLP 1205 — Configure Link Related Ethernet OAM

DLP 1205-1

DLP 1206 — Configure an xDSL DPBO profile

DLP 1206-1

DLP 1207 — Modify an xDSL DPBO profile

DLP 1207-1

(12)

Contents

xii December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02

DLP 1215 — Configure the impulse noise sensor on an

xDSL line

DLP 1215-1

DLP 1217 — Configure the xDSL overrule data

DLP 1217-1

DLP 1219 — Forced NT switchover

DLP 1219-1

DLP 1220 — Manage the CDE profile

DLP 1220-1

DLP 1221 — Manage troubleshooting counters on LT

DLP 1221-1

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

port

DLP 1225-1

DLP 1232 — Create an xDSL IPoA user and add this user

to a VLAN on the LT for iBridge

DLP 1232-1

DLP 1253 — Configure the third-party equipment

management port on the 7356 FD REM

DLP 1253-1

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

DLP 1255-1

DLP 1257 — Configure a line with an xDSL RTX profile

DLP 1257-1

DLP 1258 — Modify an xDSL RTX profile

DLP 1258-1

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

DLP 1271 — Configure link aggregation on the NELT-B

LT

DLP 1271-1

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

(13)

Contents

DLP 1283 — Troubleshooting congestion on the NELT-B

LT

DLP 1283-1

DLP 1291 — Configure a Vectoring Control Entity

profile and associate it to a board

DLP 1291-1

DLP 1292 — Modify a Vectoring Control Entity profile

DLP 1292-1

DLP 1293 — Delete a Vectoring Control Entity profile

DLP 1293-1

DLP 1294 — Configure or modify the mapping between

the VP board and the SLV LT boards

DLP 1294-1

DLP 1295 — Configure a line with an xDSL vectoring

profile

DLP 1295-1

DLP 1296 — Modify an xDSL vectoring profile

DLP 1296-1

DLP 1297 — Delete an xDSL vectoring profile

DLP 1297-1

DLP 1298 — Monitor xDSL vectoring lines

DLP 1298-1

DLP 2101 — Create operator profiles and instances

DLP 2101-1

DLP 2103 — Configure system parameters

DLP 2103-1

DLP 2105 — Configure link aggregation usage

DLP 2105-1

DLP 2107 — Manage OSPF

DLP 2107-1

DLP 2108 — Configure RIP

DLP 2108-1

(14)

Contents

xiv December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02

DLP 2111 — Plan, replan, and unplan equipment

DLP 2111-1

DLP 2114 — Configure NT redundancy

DLP 2114-1

DLP 2115 — Create a L2-terminated forwarder VLAN

DLP 2115-1

DLP 2116 — Create a L2-terminated router VLAN

DLP 2116-1

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

SHub

DLP 2121-1

DLP 2122 — Create a forwarding VRF

DLP 2122-1

DLP 2123 — Create a router VRF

DLP 2123-1

DLP 2125 — Create an IPoA user

DLP 2125-1

DLP 2126 — Create an IPoE user

DLP 2126-1

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

DLP 2128-1

DLP 2132 — Configure filtering on the NT

DLP 2132-1

DLP 2136 — Configure the multicast service in the

system

DLP 2136-1

DLP 2137 — Configure a multicast VLAN

DLP 2137-1

DLP 2138 — Configure a multicast channel

DLP 2138-1

DLP 2139 — Configure DHCP relay agent in iBridge

mode

DLP 2139-1

DLP 2140 — Configure DHCP relay agent in router

(15)

Contents

DLP 2141 — Configure DHCP relay agent in forwarder

mode

DLP 2141-1

DLP 2142 — Configure the system security domain

DLP 2142-1

DLP 2144 — Configure RADIUS

DLP 2144-1

DLP 2150 — Configure ARP table entry

DLP 2150-1

DLP 2154 — Create a snapshot alarm table

DLP 2154-1

DLP 2155 — Monitor alarms

DLP 2155-1

DLP 2157 — Manage the SHub database

DLP 2157-1

DLP 2160 — View version of the SHub software

DLP 2160-1

DLP 2162 — Modify the external management VLAN

DLP 2162-1

DLP 2164 — Ping another host

DLP 2164-1

DLP 2165 — Perform a traceroute action

DLP 2165-1

DLP 2166 — Configure SNMP proxy CPE management

DLP 2166-1

DLP 2167 — Script files

DLP 2167-1

DLP 2168 — Modify the system management IP

parameters

DLP 2168-1

DLP 2169 — Configure cluster management

DLP 2169-1

(16)

Contents

xvi December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02

DLP 2175 — Configure system management IP

parameters

DLP 2175-1

DLP 2176 — Performance monitoring commands

DLP 2176-1

DLP 2177 — Configure SFP downlink ports

DLP 2177-1

DLP 2179 — Configure system logging

DLP 2179-1

DLP 2180 — Configure static MAC addresses

DLP 2180-1

DLP 2181 — Configure operator authentication via

RADIUS

DLP 2181-1

DLP 2185 — Configure DHCP MAC concentration in

forwarder mode

DLP 2185-1

DLP 2186 — Configure ANCP session

DLP 2186-1

DLP 2191 — Enable dual tagging in the SHub

DLP 2191-1

DLP 2195 — Configure general bridge parameters on

the LT

DLP 2195-1

DLP 2196 — Configure Voice SIP

DLP 2196-1

DLP 2198 — Configure the multicast service on a user

port

DLP 2198-1

DLP 2199 — Configure QoS on the SHub

DLP 2199-1

DLP 2200 — Configure Spanning Tree on the SHub

DLP 2200-1

DLP 2204 — Configure an unnumbered IP interface on

(17)

Contents

DLP 2209 — Configure vMAC

DLP 2209-1

DLP 2210 — View the status of various system

parameters

DLP 2210-1

DLP 2211 — Configure SFP uplink ports

DLP 2211-1

DLP 2213 — Enable OAM counters

DLP 2213-1

DLP 2214 — Configure connectivity fault management DLP 2214-1

DLP 2216 — Configure Voice MEGACO

DLP 2216-1

DLP 2222 — Create the PCCP group

DLP 2222-1

DLP 2223 — Configure SHub port mirroring

DLP 2223-1

DLP 2224 — Change shelf mode

DLP 2224-1

DLP 2230 — Configure a VLAN on the SHub

DLP 2230-1

DLP 2231 — Manage the ports on the NT

DLP 2231-1

DLP 2236 — Configure the enhanced system clock

synchronization

DLP 2236-1

DLP 2273 — External Packet Forwarding

DLP 2273-1

Routine Task Procedure (RTP)

(18)

Contents

xviii December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02

RTP 2100 — Backup the configuration

RTP 2100-1

RTP 2101 — Restore the configuration

RTP 2101-1

Trouble Analysis Procedure (TAP)

TAP 1100 — Metallic test access

TAP 1100-1

TAP 1101 — F5 loopback test

TAP 1101-1

TAP 1102 — Equipment repair

TAP 1102-1

TAP 1103 — Single ended line testing

TAP 1103-1

TAP 1105 — Dual-ended line testing

TAP 1105-1

TAP 1106 — ITSC

TAP 1106-1

TAP 1107 — MELT

TAP 1107-1

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

TAP 1109 — Integrated NBLT for SIP Termination

TAP 1109-1

TAP 2104 — Fault isolation and troubleshooting

TAP 2104-1

Training (TNG)

TNG 1104 — DHCP relay agent configuration

TNG 1104-1

(19)

Contents

TNG 1107 — xDSL parameters

TNG 1107-1

TNG 1108 — SHDSL parameters

TNG 1108-1

TNG 1115 — Slot numbering schemes

TNG 1115-1

TNG 1116 — Link Related Ethernet OAM (EFM OAM)

TNG 1116-1

TNG 1119 — vMAC

TNG 1119-1

TNG 1120 — VLAN translation

TNG 1120-1

TNG 1121 — xDSL bonding

TNG 1121-1

TNG 2100 — Service installation

TNG 2100-1

TNG 2101 — QoS configuration

TNG 2101-1

TNG 2102 — IGMP and multicast configuration

TNG 2102-1

TNG 2106 — Specifying 7330 ISAM FTTN expansion

units using the CLI

TNG 2106-1

TNG 2109 — Performance management counters

TNG 2109-1

TNG 2110 — Configuration examples

TNG 2110-1

TNG 2112 — 7330 ISAM FTTN configuration for

subtending

TNG 2112-1

TNG 2117 — Enhanced iBridge

TNG 2117-1

(20)

Contents

xx December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02

Appendix (A)

A. Configuration example values for FD 24Gbps NT

A-1

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

(21)

1 —

Introduction

1.1 Introduction

1-2

1.2 How to use this document

1-2

(22)

1 — Introduction

1-2 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02

1.1 Introduction

This document provides instructions on CLI operation and maintenance tasks and

procedures for the Alcatel-Lucent 7302 ISAM, the 7330 ISAM FTTN and the 7356

ISAM FTTB.

These tasks and procedures are identical for the 7302 ISAM, the 7330 ISAM FTTN

and the 7356 ISAM FTTB, unless specified otherwise.

Throughout the document, the 7302 ISAM, the 7330 ISAM FTTN and the 7356

ISAM FTTB will be referred to as the Network Element (NE).

See the CLI Commands for FD 24Gbps NT document for more detailed information

about the CLI command syntax.

1.2 How to use this document

This document follows the task-oriented practice (TOP). The TOP method is a

documentation system that uses different types of layers, or documents, to describe

the installation, operations, and maintenance of telecommunications equipment and

software. Most layers in the TOP system provide step-by-step instructions for the

completion of a specific task or procedure.

A TOP document is structured so that experienced and less experienced users can

effectively use the material to perform work assignments. Less experienced users can

refer to detailed procedures to complete a task. Experienced users can bypass

detailed procedures and use only the level of information that they need.

TOP layers

to any point within the task description. This guide may contain any of the following

layers:

• Index List (IXL)

• Non-Trouble Procedure (NTP)

• Detailed Level Procedure (DLP)

• Routine Task Procedure (RTP)

• Trouble Analysis Procedure (TAP)

• Training (TNG)

(23)

Figure 1-1 TOP layers and major paths

Task index list (IXL)

An IXL lists the available tasks in the TOP document. An IXL is used to find a task

category and the applicable procedures to perform a task.

Non-trouble procedure (NTP)

An NTP describes how to perform a task, such as how to save a system after it has

been installed, turn up a system for service, or maintain a system according to a

maintenance plan. NTPs are made up of steps that often refer to DLPs or TNGs. Less

experienced users, or experienced users who need more information, can go to the

DLPs for detailed procedural and safety information, and TNGs for supporting

information. If users go to the referenced DLP or TNG, they must return to the NTP

to continue the procedure.

Detailed level procedure (DLP)

A DLP contains detailed steps that describe how to perform a task. In addition to

step-by-step information, a DLP contains any tables or illustrations that may be

required to perform the task.

DLPs are typically referenced from an NTP, always referenced from the IXL, and

sometimes referenced from other DLPs. When a DLP is referenced from another

layer, users must return to the layer at which the DLP was referenced to continue the

procedure.

Routine task procedure (RTP)

An RTP describes how to perform a routine maintenance task.

RTPs are typically referenced from the IXL.

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

(24)

Trouble analysis procedure (TAP)

A TAP describes how to identify and clear trouble in the system. TAPs are made up

of step-by-step instructions. For less experienced users, or experienced users who

need more information, some tasks provide a reference to a DLP or TNG. If users go

to the referenced DLP or TNG, they must return to the TAP to continue the

procedure.

Training (TNG)

A TNG contains supplementary information about a task or procedure. A TNG might

refer to a DLP or other document. If users go to the referenced document, they need

to return to the TNG to read the remaining information.

Step details

NTPs, DLPs, RTPs and TAPs use procedural steps and decision steps. Procedural

steps provide instructions, and decision steps provide a go-to choice.

Procedural steps may contain notations that refer to additional information such as

tables, figures, examples and other TOP layers. For example, a step in an NTP might

refer to a DLP.

Key information required to complete a step is shown at the beginning of the step.

More detailed information, which can be accessed according to experience level, is

provided at the end of the step, as shown in the example below:

“Reconnect the power feeds; see DLP 106.”

The completion of a specific task or procedure is indicated as follows:

“STOP. This procedure is complete.”

Procedures with options or substeps

When there are options in a procedure, they are identified by letters. When there are

required substeps in a procedure, they are identified by Roman numerals.

Procedure 1-1 Example of options in a procedure

At step 1, you can choose option a or b. At step 2, you must do what the step indicates. 1 This step offers two options. You must choose one of the following:

a This is one option. b This is another option. 2 You must perform this step.

(25)

Procedure 1-2 Example of required substeps in a procedure

At step 1, you must perform a series of substeps within a step. At step 2, you must do what the step indicates.

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

i This is the first substep. ii This is the second substep. iii This is the third substep. 2 You must perform this step.

1.3 Configuration examples

Configuration examples are provided in the DLPs.

Different rack configurations are used in the examples. These are indicated with

Config#1, Config#2 and Config#3.

Appendix

A

“Configuration example values for FD 24Gbps NT”

gives an overview

of the different configurations and values used in the DLP configuration examples.

(26)

(27)

Index List (IXL)

(28)

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

(29)

IXL 100 — Master Task Index List

Table IXL 100-1: Non-Trouble Procedures (NTPs)

Title NTP number

Execute script files NTP 1101

Perform equipment repairs NTP 1114

Monitor performance and view configuration NTP 1118

Modify DSL services NTP 1119

Maintain the system NTP 1124

Manage system logging NTP 1126

Configure SHDSL NTP 1127

Configure Link Related Ethernet OAM NTP 1130

Configure Connectivity Fault Management NTP 1132

Initial system configuration NTP 2100

Configure equipment NTP 2103

Configure a VLAN cross-connect NTP 2104

Configure an iBridge VLAN NTP 2105

Configure an IP-aware bridge NTP 2106

Configure an IP router NTP 2107

Configure services NTP 2108

Monitor alarms NTP 2115

Perform software management NTP 2116

Modify system parameters NTP 2117

Troubleshooting the network NTP 2120

(30)

IXL 100 — Master Task Index List

IXL 100-2 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02

Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA Table IXL 100-2: Detailed Level Procedures (DLP)

Cluster management NTP 2122

Configure a loopback interface on the SHub NTP 2129

Configure an enhanced IP router NTP 2133

Title DLP number

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

Lock and unlock equipment DLP 1112

Configure the equipment DLP 1113

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

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

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

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

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

Create xDSL profiles DLP 1129

Configure xDSL bonding DLP 1130

Configure QoS DLP 1134

Configure 802.1x DLP 1145

Configure PPPoE relay on LT DLP 1146

Configure PPPoX cross-connect DLP 1147

Shut down and restart the NT DLP 1151

Reboot the system DLP 1152

Shut down and restart individual equipment DLP 1153

Manage OSWP DLP 1159

Modifying xDSL profiles DLP 1163

Configure SSH and SFTP DLP 1170

Switch a user from ADSL to VDSL DLP 1173

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

cross-connect DLP 1174

Configure SHDSL DLP 1182

Configure IMA on SHDSL spans DLP 1183

Configure global VLAN parameters on the LT DLP 1187

Configure custom PSD points DLP 1188

Configure VDSL2 virtual noise values DLP 1189

Configure threshold crossing alerts DLP 1190

View port configuration and operational data on LT DLP 1197

(1 of 4)

Title NTP number

(31)

Configure protocol tracing DLP 1201

Configure QoS threshold crossing alerts DLP 1202

Configure general security settings DLP 1203

Configure Link Related Ethernet OAM DLP 1205

Configure an xDSL DPBO profile DLP 1206

Modify an xDSL DPBO profile DLP 1207

Configure xDSL power back off DLP 1208

Create an IP user/subnet DLP 1212

Configure the impulse noise sensor on an xDSL line DLP 1215

Configure the xDSL overrule data DLP 1217

Forced NT switchover DLP 1219

Manage the CDE profile DLP 1220

Manage troubleshooting counters on LT DLP 1221

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

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

Configure a port on the NELT-B LT DLP 1255

Configure a line with an xDSL RTX profile DLP 1257

Modify an xDSL RTX profile DLP 1258

Configure spanning tree on the NELT-B LT DLP 1270

Configure link aggregation on the NELT-B LT DLP 1271

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

Troubleshooting congestion on the NELT-B LT DLP 1283

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

Modify a Vectoring Control Entity profile DLP 1292

Delete a Vectoring Control Entity profile DLP 1293

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

Configure a line with an xDSL vectoring profile DLP 1295

Modify an xDSL vectoring profile DLP 1296

Delete an xDSL vectoring profile DLP 1297

Monitor xDSL vectoring lines DLP 1298

Create operator profiles and instances DLP 2101

Configure system parameters DLP 2103

Configure link aggregation usage DLP 2105

Manage OSPF DLP 2107

Configure RIP DLP 2108

(32)

Manage alarms DLP 2110

Plan, replan, and unplan equipment DLP 2111

Configure NT redundancy DLP 2114

Create a L2-terminated forwarder VLAN DLP 2115

Create a L2-terminated router VLAN DLP 2116

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

Create a forwarding VRF DLP 2122

Create a router VRF DLP 2123

Create an IPoA user DLP 2125

Create an IPoE user DLP 2126

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

Configure filtering on the NT DLP 2132

Configure the multicast service in the system DLP 2136

Configure a multicast VLAN DLP 2137

Configure a multicast channel DLP 2138

Configure DHCP relay agent in iBridge mode DLP 2139

Configure DHCP relay agent in router mode DLP 2140

Configure DHCP relay agent in forwarder mode DLP 2141

Configure the system security domain DLP 2142

Configure RADIUS DLP 2144

Configure ARP table entry DLP 2150

Create a snapshot alarm table DLP 2154

Monitor alarms DLP 2155

Manage the SHub database DLP 2157

View version of the SHub software DLP 2160

Modify the external management VLAN DLP 2162

Ping another host DLP 2164

Perform a traceroute action DLP 2165

Configure SNMP proxy CPE management DLP 2166

Script files DLP 2167

Modify the system management IP parameters DLP 2168

Configure cluster management DLP 2169

Enable EMS management DLP 2171

Create a default operator profile DLP 2172

Configure system management IP parameters DLP 2175

Performance monitoring commands DLP 2176

Configure SFP downlink ports DLP 2177

(33)

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

Configure system logging DLP 2179

Configure static MAC addresses DLP 2180

Configure operator authentication via RADIUS DLP 2181

Configure DHCP MAC concentration in forwarder mode DLP 2185

Configure ANCP session DLP 2186

Enable dual tagging in the SHub DLP 2191

Configure general bridge parameters on the LT DLP 2195

Configure Voice SIP DLP 2196

Configure the multicast service on a user port DLP 2198

Configure QoS on the SHub DLP 2199

Configure Spanning Tree on the SHub DLP 2200

Configure an unnumbered IP interface on the SHub DLP 2204

Configure vMAC DLP 2209

View the status of various system parameters DLP 2210

Configure SFP uplink ports DLP 2211

Enable OAM counters DLP 2213

Configure connectivity fault management DLP 2214

Configure Voice MEGACO DLP 2216

Create the PCCP group DLP 2222

Configure SHub port mirroring DLP 2223

Change shelf mode DLP 2224

Configure a VLAN on the SHub DLP 2230

Configure the enhanced system clock synchronization DLP 2236

External Packet Forwarding DLP 2273

Title RTP number

Retrieve remote inventory RTP 1102

Retrieve board temperature RTP 1103

Backup the configuration RTP 2100

Restore the configuration RTP 2101

(34)

Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA Table IXL 100-4: Trouble Analysis Procedure (TAP)

Table IXL 100-5: Training (TNG)

Title TAP number

Metallic test access TAP 1100

F5 loopback test TAP 1101

Equipment repair TAP 1102

Single ended line testing TAP 1103

Dual-ended line testing TAP 1105

ITSC TAP 1106

MELT TAP 1107

Integrated NBLT for MEGACO Termination TAP 1108

Integrated NBLT for SIP Termination TAP 1109

Fault isolation and troubleshooting TAP 2104

Title TNG number

DHCP relay agent configuration TNG 1104

Overall software packages TNG 1105

xDSL parameters TNG 1107

SHDSL parameters TNG 1108

Link Related Ethernet OAM (EFM OAM) TNG 1116

vMAC TNG 1119

VLAN translation TNG 1120

xDSL bonding TNG 1121

Service installation TNG 2100

QoS configuration TNG 2101

IGMP and multicast configuration TNG 2102

Specifying 7330 ISAM FTTN expansion units using the CLI TNG 2106

Performance management counters TNG 2109

Configuration examples TNG 2110

7330 ISAM FTTN configuration for subtending TNG 2112

Slot numbering schemes TNG 1115

Enhanced iBridge TNG 2117

(35)

Non-Trouble Procedures (NTP)

NTP 1101 — Execute script files

NTP 1114 — Perform equipment repairs

NTP 1118 — Monitor performance and view configuration

NTP 1119 — Modify DSL services

NTP 1124 — Maintain the system

NTP 1126 — Manage system logging

NTP 1127 — Configure SHDSL

NTP 1130 — Configure Link Related Ethernet OAM

NTP 1132 — Configure Connectivity Fault Management

NTP 2100 — Initial system configuration

NTP 2103 — Configure equipment

NTP 2104 — Configure a VLAN cross-connect

NTP 2105 — Configure an iBridge VLAN

NTP 2106 — Configure an IP-aware bridge

NTP 2107 — Configure an IP router

(36)

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

NTP 2115 — Monitor alarms

NTP 2116 — Perform software management

NTP 2117 — Modify system parameters

NTP 2120 — Troubleshooting the network

NTP 2121 — Manage an SNMP proxy CPE

NTP 2122 — Cluster management

NTP 2129 — Configure a loopback interface on the SHub

NTP 2133 — Configure an enhanced IP router

(37)

NTP 1101 — Execute script files

Purpose

A script file is a file containing CLI commands.

A script file must follow the same syntax rules as commands entered interactively. Only the tab and the question mark lose their special meaning in a script, so command expansion and single-line help are not available.

The script will be aborted if one of the commands in the script fails. A command may be preceded by a minus '-' to prevent the script from being aborted in case of a semantic error; for example, when you try to delete a node instance that does not exist. By default, a command script does not interact with the user. The execution of the script will be aborted if a command or filter requires interaction with the user. Interactivity can be enabled by specifying the interactive option with the exec command.

Command scripts may not be nested.

Procedure

In order to use script files, you need to perform the following tasks: 1 Create and execute script files; see DLP 2167.

Caution — When an NT switchover takes place during execution of the script, the possibility exists that CLI commands will fail.

To recover from this situation the operator should delete the objects which were created before.

(38)

NTP 1101 — Execute script files

NTP 1101-2 December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02

(39)

NTP 1114 — Perform equipment repairs

Purpose

This procedure provides the steps to perform equipment repair on the NE.

Procedure

Proceed as follows to perform equipment repair tasks:

1 Plan, unplan, and replan equipment (for example, plug-in units); see DLP2111. 2 Pull out and plug in equipment. For the procedures, see the hardware installation

manual for your equipment.

3 Lock and unlock equipment (mostly plug-in units); see DLP 1112. 4 Start up or shut down the system, select one of:

a Shut down or restart the NT; see DLP 1151. b Reboot the entire system; see DLP 1152. c Shut down individual equipment; see DLP 1153. 5 STOP. This procedure is complete.

(40)

NTP 1114 — Perform equipment repairs

(41)

NTP 1118 — Monitor performance and

view configuration

Purpose

This procedure list the procedures that can be used for:

•

Performance Monitoring (PM)

•

viewing the configuration and operational data of a port

Procedure

The following tasks can be performed:

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

2 Enable the Operations and Maintenance (OAM) counters; see DLP 2213. 3 Manage the troubleshooting counters on the LT; see DLP 1221.

4 Viewing the PM counters; see DLP2176.

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

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

(42)

NTP 1118 — Monitor performance and view configuration

(43)

NTP 1119 — Modify DSL services

Purpose

This procedure provides the steps to adapt the following services on the NE:

•

xDSL profiles

•

switching a user from ADSL to VDSL

Procedure

You can perform the following tasks: 1 Modify an xDSL profile; see DLP 1163. 2 Modify a DPBO profile; see DLP 1207. 3 Modify an RTX profile; see DLP 1258.

4 Modify an xDSL vectoring profile; see DLP 1296.

5 Modify an Vectoring Control Entity profile; see DLP 1292. 6 Switch a user from ADSL to VDSL; see DLP 1173.

(44)

NTP 1119 — Modify DSL services

(45)

NTP 1124 — Maintain the system

Purpose

This NTP provides the steps for system maintenance of the NE.

Procedure

Perform this procedure to maintain the system: 1 Back up the system configuration; see RTP 2100. 2 Restore the system configuration; see RTP 2101. 3 Retrieve the remote inventory; see RTP 1102. 4 STOP. This procedure is complete.

(46)

NTP 1124 — Maintain the system

(47)

NTP 1126 — Manage system logging

Purpose

This NTP provides the steps to manage system logging (SYSLOG) for the NE.

General

System statistics logs are user configurable and you can create up to 64 system logs. System logs can be saved locally to a remote server, or all active CLI terminals, or all active TL1 terminals.

You can perform the following three main tasks using CLI:

•

enable and disable logging for all system logs

•

create and configure up to 64 system logs

•

monitor system logs

Using filters, you can determine which messages are sent to the system log file, as well as set the severity level of the system log.

The following applies when using SYSLOG in an operational (E2E) environment:

•

The NE supports SYSLOG according to RFC3164 (aka BSD SYSLOG)

•

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

(48)

NTP 1126 — Manage system logging

•

The severity of the various application messages is predefined. It is reported as

follows:

•

CLI operator commands: INFO

•

Service Affecting alarm messages: EMERGENCY

•

Authentication messages: ALERT

•

Other CLI/TL1 messages (non-service affecting): INFO

•

protocol tracing: DEBUG

•

videoCDR reporting: NOTICE

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

See the System Description for FD 24Gbps NT document for more information about system and security statistics logging.

Procedure

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

1 Enable and disable logging for all system logs; see DLP2179. 2 Create, configure, and monitor system logs; see DLP 2179. 3 STOP. This procedure is complete.

(49)

NTP 1127 — Configure SHDSL

Purpose

Single-pair High-speed Digital Subscriber Line (SHDSL) is a physical layer standard based on the ITU-T Recommendation G.991.2. It describes a versatile transmission method for data transport in the telecommunication access networks, capable of supporting whichever network protocol is currently deployed while enabling higher bandwidth and reach (for example, TDM, ATM, Frame Relay and so on).

SHDSL transceivers are designed primarily for duplex operation over mixed gauges of two wire twisted metallic pairs. Four-wire and m-pair operations are included as options for extended reach. The use of signal regenerators for both the two-wire and the multi-wire operations is optional.

Inverse Multiplexing for ATM (IMA) permits a broadband cell stream to be transported on a number of lower-rate physical links (for example, several SHDSL span lines) by grouping these physical links into a single logical channel. The specification includes a means to maintain cell order and a method to allow in-service loss and restore of individual physical links.

Procedure

Proceed as follows to configure SHDSL: 1 To configure SHDSL; see DLP 1182.

2 To configure IMA on SHDSL spans; see DLP 1183. 3 STOP. This procedure is complete.

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

(50)

NTP 1127 — Configure SHDSL

(51)

NTP 1130 — Configure Link Related

Ethernet OAM

Purpose

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

Procedure

Proceed as follows to configure EFM OAM: 1 Configuration of EFM OAM; see DLP 1205.

2 After configuration, the following actions can be performed: a Viewing of Local and Remote (CPE) information; see DLP 1205. b Viewing of EFM OAM statistics; see DLP 1205.

c Retrieve MAC counters; see DLP 1205. d Retrieve PME counters; see DLP 1205. 3 STOP. This procedure is complete.

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

(52)

NTP 1130 — Configure Link Related Ethernet OAM

(53)

NTP 1132 — Configure Connectivity Fault

Management

Purpose

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

General

CFM (802.1ag) is an Ethernet OAM capability providing end to end fault detection and isolation on Ethernet networks. CFM requires that bridge ports throughout the network be configured with software entities, called “maintenance points” (MP). MPs process and respond to CFM messages sent on the dataplane. By looking at the replies from these MPs, a network operator can isolate a fault to a specific link or node. MPs are organized by maintenance domain (MD) and maintenance association (MA). See the System Description for FD 24Gbps NT document for more information about CFM. You can configure MPs on the NE to process and respond to CFM messages sent from the edge router or BNG. You cannot initiate CFM tests from the NE. To configure CFM, you must configure an MD, an MA, and you must configure an MEP or you must configure the MA to auto-create MIPs.

The ISAM supports MIPs and network facing MEPs at user ports. Within these MPs the ISAM responds to LBMs and to LTMs coming from the network. The ISAM responds to LBM coming from the user (see DSLF TR-101).

The ISAM supports network facing MEPs on the LT board at its GE interface towards the NT board. Within these MEPs the ISAM responds to LBMs and to LTMs.

See DLP 2214 for more information on configuration restrictions and prerequisites. You can also view CFM configuration data on the NE.

(54)

NTP 1132 — Configure Connectivity Fault Management

Prerequisites

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

•

You must have network management access or craft port access to the NE you want to configure and be familiar with the CLI.

•

CFM must be supported on the access aggregation network.

•

A VLAN must be configured.

Procedure

Use this procedure to configure CFM or view CFM configuration. 1 Configure CFM:

i Configure a maintenance domain; see DLP 2214

ii Configure (create) a maintenance association; see DLP 2214

iii Configure a maintenance end point; see DLP 2214

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

2 View CFM configuration; see DLP 2214

(55)

NTP 2100 — Initial system configuration

Purpose

This document describes the procedure to be used to perform the initial system configuration.

General

Figure NTP 2100-1 shows the management topology of the NE system. Figure NTP 2100-1: Management Topology

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

ISAM CLI agent TL1 agent SNMP agent RS232 RS232 SSH Telnet UDP SNMPv2 or SNMPv3 Debug agent SSH UDP EMS (e.g. AMS 5520) TL1

Gateway TerminalCLI TL1 CT CLI CT TL1 Terminal Debug Terminal Telnet

(56)

NTP 2100 — Initial system configuration

Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA Table NTP 2100-1: System Managers

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

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

Security Considerations

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

•

It is advised to close the remote debug acess. By default, the accesss is not disabled.

•

It is advised to use secure management channels (CLI/SSH, TL1/SSH, SNMPv3,

SFTP). This implies closing the unsecured management channels.

•

It is NOT advised to use unsecured remote management channels: CLI/Telnet, TL1/UDP, SNMPv1/2, or TFTP.

•

If SNMPv1/2 is used anyway, it is advised not to use community string = public.

•

It is advised to change the administrator password of TL1 and CLI (even if TL1 or CLI

is not used by the operator).

•

It is advised to deactivate the remote TL1 management interface when no remote TL1 is used. It is not possible to deactivate the local Craft Terminal TL1 access.

•

SHub ACLs can be configured to restrict the traffic from the Element Management

Systems (and other management plane services) to be routed to the NT OBC.

Procedure

Proceed as follows to perform an initial system configuration: 1 Set up a CLI session; see DLP 1100.

2 Create and configure an Operator Profile; see DLP 2101. 3 Create a default Operator Profile; see DLP 2172.

4 Configure the management IP parameters and network interfaces; see DLP 2175. 5 Configure SSH; see DLP 1170.

6 Configure the general security settings; see DLP 1203. 7 Configure the system parameters; see DLP 2103.

Manager type Description

EMS Remotely connected Element Management System based on SNMP TL1 CT Local Craft Terminal using TL1 commands

CLI CT Local Craft Terminal using Command Line Interface (CLI) commands CLI terminal Remotely connected terminal using CLI commands based over telnet or ssh TL1 gateway Remotely connected gateways using TL1 commands over UDP

(57)

8 Configure the enhanced system clock synchronization; see DLP 2236.

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

10 Enable the management of EMS; see DLP 2171. 11 Configure the alarm management; see DLP 2110. 12 Save the SHub database; see DLP2157.

(58)

(59)

NTP 2103 — Configure equipment

Purpose

This procedure provides the steps to:

•

plan, unplan, or replan the equipment

•

lock or unlock the equipment

•

configure the SFP uplink ports and the SFP downlink ports

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

General

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

Table NTP 2103-1: Configure plug-in units

Action Description

Planning equipment Planning a piece of equipment is possible before and after the equipment is physically present and detected by the system (at startup). The system verifies the configuration parameters and checks if the required equipment is available.

Note: As long as equipment is not planned, it is impossible to offer service. Units and other equipment are only available from an operation and maintenance point of view.

Unplanning

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

(60)

NTP 2103 — Configure equipment

Change the shelf mode

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

Procedure

Proceed as follows to configure or modify the system equipment: 1 Plan, replan, or unplan equipment; see DLP 2111.

2 Lock or unlock the equipment; see DLP 1112.

3 Modify the configuration of the system equipment; see DLP 1113. 4 If required, change the shelf mode; see DLP 2224.

5 Configure SFP downlink ports; see DLP 2177. 6 Configure SFP uplink ports; see DLP 2211. 7 STOP. This procedure is complete.

Locking and unlocking

equipment When necessary, you can lock any equipment, most often a unit, to put it out of service. Locking a unit renders it inactive. No traffic is generated or received by the units. All alarms related to the unit are filtered except for the “board-missing”, “board installation missing” and “board-type mismatch” alarms. However, the unit is not removed from the

configuration, and as soon as you unlock the unit, it becomes active again. It goes back to operational mode without restart or initialization, and traffic can resume immediately.

Similarly, you can power down the unit and restart it at a later time. In this case, however, the unit will go through a complete startup cycle before traffic is possible.

Action Description

(2 of 2)

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

(61)

NTP 2104 — Configure a VLAN

cross-connect

Purpose

The NE supports several VLAN cross-connect models:

•

Customer VLAN cross-connect or C-VLAN CC

•

Service provider VLAN cross-connect or S-VLAN CC

•

VLAN stacking or S+C-VLAN CC

Purpose of C-VLAN CC

This is the most straightforward VLAN cross-connect model where a single VLAN ID at the EMAN side is associated with a given PVC at the user side. Any kind of traffic issued by the subscriber is passed transparently towards the network using the selected VLAN ID.

Cross-connect VLANs can be enabled to be protocol aware for IGMP and 802.1x and to support the configuration of DHCP Option 82 and PPPoE relay.

Purpose of S-VLAN CC

In this mode, the Service Provider VLAN (S-VLAN) ID at the EMAN side is associated with a single subscriber interface at the user side. The C-VLANs carried within the S-VLAN are passed transparently to the end user. This allows the end user to specify its own end-to-end connectivity, while remaining transparent for the EMAN.

The NE acts as an S-VLAN aware bridge, with the restriction that only one subscriber interface can be attached. Forwarding is only done based on the S-VLAN forwarding context. The forwarding is transparent for the C-VLANs. Frames on the subscriber interface may or may not have an S-VLAN tag. In case of an absent S-VLAN tag (that is for C-VLAN tagged and untagged/priority tagged frames), the subscriber interface’s

(62)

NTP 2104 — Configure a VLAN cross-connect

Purpose of S+C-VLAN CC

The basic VLAN cross-connect mode suffers from the fact the that number of VLAN identifiers is limited to 4K. Since the VLAN is a EMAN wide identifier, one ends up with a scalability issue: there cannot be more than 4K end users connected to the whole EMAN. To solve this issue, two VLANs are stacked and the cross-connection is then performed on the combination (S-VLAN, C-VLAN) allowing to theoretically reach up to 16M end users.

The NE acts as a C-VLAN aware bridge, with the restriction that only one subscriber interface can be attached. Frames on the subscriber interface may be C-VLAN tagged or untagged/priority tagged. In case of C-VLAN tagged frames, a check will be performed on the received C-VLAN ID, while the subscriber interface‘s preconfigured S-VLAN will be assigned. In case of untagged/priority tagged frames, the subscriber interface’s pre-configured C-VLAN and S-VLAN will be assigned.

Prerequisite

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

•

The board must have been planned; see DLP 2111.

•

xDSL profiles must have been created; see DLP 1129.

Procedure

(63)

Figure NTP 2104-1: Configure a VLAN Cross-connect on an SHub-based ISAM

1 Configure a VLAN on the LT for VLAN cross-connect. Do one of the following: a For C-VLAN cross-connect; see DLP 1117.

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

2 Create a user and add him to a VLAN created in step 1. Do one of the following: a create an xDSL/native Ethernet user and add him to a VLAN on the LT; see

DLP 1124.

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

3 Configure network interface and LT interface on the SHub; see DLP 2231. 4 Optionally, configure LAG on the SHub; see DLP 2105.

5 Configure a VLAN on the SHub; see DLP 2230.

•

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

•

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

•

In case of S+C-VLAN cross-connect, the mode of the VLAN must be

NT_SHUB ISAM_SHUB LT LT C-VLAN CC Phy Phy LAG Phy DLP 2230 DLP 2121 DLP 2231 DLP 2231 DLP 2105 DLP 1124 DLP 1174 DLP 1117 (DLP 1118) (DLP 1119) VLAN 19 (=Bridge) LT port Network Ports VLAN 13 (=Bridge) VLAN 17 (=Bridge) VLAN 11 (=Bridge) C₁₁ VLAN CC VLAN CC S +C₁₇ ₂₃ VLAN CC S +C₁₇ ₂₉ S₁₃ VLAN CC S+C-VLAN CC S-VLAN CC S+C-VLAN CC C-, S+C- or S-VLAN CC (No VLAN translation shown on user side) SHub

VLAN LT VLAN for_{C-VLAN CC} DLP 2128

(64)

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

(65)

NTP 2105 — Configure an iBridge VLAN

Purpose

The concept of a VLAN in intelligent bridging (iBridge) mode is that multiple NSPs are each connected to the NE with a VLAN. The user ports are connected to the VLAN of their corresponding Network Service Provider (NSP).

This procedure provides the steps to create an iBridge VLAN.

Prerequisite

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