Alcatel-Lucent 7302
INTELLIGENT SERVICES ACCESS MANAGER
Alcatel-Lucent 7330
INTELLIGENT SERVICES ACCESS MANAGER FIBER TO THE NODE
Alcatel-Lucent 7356
INTELLIGENT SERVICES ACCESS MANAGER FIBER TO THE BUILDING OPERATIONS AND MAINTENANCE USING CLI FOR FD 24GBPS NT
R 4 . 3 . 02 3 H H - 1 0104- AAAA-T QZZA E ditio n 0 2 Re le ase d Alcatel-Lucent Proprietary This document contains proprietary information of Alcatel-Lucent and is not to be disclosed or used except in accordance with applicable agreements. Copyright 2011 © Alcatel-Lucent. All rights reserved.
Alcatel-Lucent assumes no responsibility for the accuracy of the information presented, which is subject to change without notice. Alcatel, Lucent and the Alcatel-Lucent logo are registered trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners. Copyright 2011 Alcatel-Lucent. All rights reserved. Disclaimers
Alcatel-Lucent products are intended for commercial uses. Without the appropriate network design engineering, they must not be sold, licensed or otherwise distributed for use in any hazardous environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, direct life-support machines, or weapons systems, in which the failure of products could lead directly to death, personal injury, or severe physical or environmental damage. The customer hereby agrees that the use, sale, license or other distribution of the products for any such application without the prior written consent of Alcatel-Lucent, shall be at the customer's sole risk. The customer hereby agrees to defend and hold Alcatel-Lucent harmless from any claims for loss, cost, damage, expense or liability that may arise out of or in connection with the use, sale, license or other distribution of the products in such applications. This document may contain information regarding the use and installation of non-Alcatel-Lucent products. Please note that this information is provided as a courtesy to assist you. While Alcatel-Lucent tries to ensure that this information accurately reflects information provided by the supplier, please refer to the materials provided with any non-Alcatel-Lucent product and contact the supplier for confirmation. Alcatel-Lucent assumes no responsibility or liability for incorrect or incomplete information provided about non-Alcatel-Lucent products. However, this does not constitute a representation or warranty. The warranties provided for Alcatel-Lucent products, if any, are set forth in contractual documentation entered into by Alcatel-Lucent and its customers. This document was originally written in English. If there is any conflict or inconsistency between the English version and any other version of a document, the English version shall prevail.
When printed by Alcatel-Lucent, this document is printed on recycled paper.
Preface
This preface provides general information about the documentation set for the 7302 Intelligent Services Access Manager (7302 ISAM), the 7330 Intelligent Services Access Manager Fiber to the Node (7330 ISAM FTTN) and the 7356 Intelligent Services Access Manager Fiber to the Building (7356 ISAM FTTB).
Scope This documentation set provides information about safety, features and functionality, ordering, hardware installation and maintenance, CLI and TL1 commands, and software upgrade and migration procedures for the current release.
Audience This documentation set is intended for planners, administrators, operators, and maintenance personnel involved in installing, upgrading, or maintaining the 7302 ISAM, the 7330 ISAM FTTN or the 7356 ISAM FTTB.
Required knowledge Readers must be familiar with general telecommunications principles.
Product naming When the term “ISAM” is used alone, the 7302 ISAM, the 7330 ISAM FTTN and the 7356 ISAM FTTB are meant. If a feature is valid for only one of the products, the applicability will be explicitly stated.
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
iii
Preface
Documents Refer to the Product Information document for your product to see a list of all relevant customer documents and their part numbers.
Acronymns and initialisms The expansions and optional descriptions of most acronyms and initialisms appear in the glossary which is included in the System Description for FD 24Gbps NT document.
Assistance and ordering phone numbers Alcatel-Lucent provides global technical support through regional call centers. Phone numbers for the regional call centers are available at the following URL: http://www.alcatel-lucent.com/myaccess. For ordering information, contact your Alcatel-Lucent sales representative.
Safety information For safety information, see the Safety Manual for your product.
Special information The following are examples of how special information is presented in this document. Danger — Danger indicates that the described activity or situation
may result in serious personal injury or death; for example, high voltage or electric shock hazards. Warning — Warning indicates that the described activity or situation
may, or will, cause equipment damage or serious performance problems. Caution — Caution indicates that the described activity or situation
may, or will, cause service interruption.
Note — A note provides information that is, or may be, of special
interest.
iv
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
Preface
Release notes Be sure to refer to the release notes (such as the Customer Release Notes or Emergency Fix Release Note) issued for software loads of your product before you install or use the product. The release notes provide important information about the software load.
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
v
Preface
vi
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
Contents
Preface
iii
Scope ............................................................................................... iii Audience ............................................................................................... iii Required knowledge ...................................................................................iii Product naming ........................................................................................ iii Documents .............................................................................................. iv Acronymns and initialisms ............................................................................ iv Assistance and ordering phone numbers ........................................................... iv Safety information ..................................................................................... iv Special information.................................................................................... iv Release notes............................................................................................ v
1—
Introduction 1.1 1.2 1.3
1-1
Introduction .............................................................................. 1-2 How to use this document ............................................................. 1-2 Configuration examples ................................................................ 1-5
Index List (IXL) IXL 100 —
Master Task Index List
IXL 100-1
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
vii
Contents
Non-Trouble Procedures (NTP) NTP 1101 — Execute script files
NTP 1101-1
NTP 1114 — Perform equipment repairs
NTP 1114-1
NTP 1118 — Monitor performance and view configuration
NTP 1118-1
NTP 1119 — Modify DSL services
NTP 1119-1
NTP 1124 — Maintain the system
NTP 1124-1
NTP 1126 — Manage system logging
NTP 1126-1
NTP 1127 — Configure SHDSL
NTP 1127-1
NTP 1130 — Configure Link Related Ethernet OAM
NTP 1130-1
NTP 1132 — Configure Connectivity Fault Management NTP 1132-1 NTP 2100 — Initial system configuration
NTP 2100-1
NTP 2103 — Configure equipment
NTP 2103-1
NTP 2104 — Configure a VLAN cross-connect
NTP 2104-1
NTP 2105 — Configure an iBridge VLAN
NTP 2105-1
NTP 2106 — Configure an IP-aware bridge
NTP 2106-1
NTP 2107 — Configure an IP router
NTP 2107-1
NTP 2108 — Configure services
NTP 2108-1
viii
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
Contents
NTP 2115 — Monitor alarms
NTP 2115-1
NTP 2116 — Perform software management
NTP 2116-1
NTP 2117 — Modify system parameters
NTP 2117-1
NTP 2120 — Troubleshooting the network
NTP 2120-1
NTP 2121 — Manage an SNMP proxy CPE
NTP 2121-1
NTP 2122 — Cluster management
NTP 2122-1
NTP 2129 — Configure a loopback interface on the SHub
NTP 2129-1
NTP 2133 — Configure an enhanced IP router
NTP 2133-1
Detailed Level Procedures (DLP) DLP 1100 — Set up a local CLI session or a local TL1 session
DLP 1100-1
DLP 1112 — Lock and unlock equipment
DLP 1112-1
DLP 1113 — Configure the equipment
DLP 1113-1
DLP 1117 — Configure a VLAN on the LT for C-VLAN cross-connect
DLP 1117-1
DLP 1118 — Configure a VLAN on the LT for S-VLAN cross-connect
DLP 1118-1
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
ix
Contents
DLP 1119 — Configure a VLAN on the LT for S+C-VLAN cross-connect
DLP 1119-1
DLP 1120 — Configure a VLAN on the LT for C-iBridge
DLP 1120-1
DLP 1124 — Create an xDSL/native Ethernet user and add this user to a VLAN on the LT
DLP 1124-1
DLP 1129 — Create xDSL profiles
DLP 1129-1
DLP 1130 — Configure xDSL bonding
DLP 1130-1
DLP 1134 — Configure QoS
DLP 1134-1
DLP 1145 — Configure 802.1x
DLP 1145-1
DLP 1146 — Configure PPPoE relay on LT
DLP 1146-1
DLP 1147 — Configure PPPoX cross-connect
DLP 1147-1
DLP 1151 — Shut down and restart the NT
DLP 1151-1
DLP 1152 — Reboot the system
DLP 1152-1
DLP 1153 — Shut down and restart individual equipment
DLP 1153-1
DLP 1159 — Manage OSWP
DLP 1159-1
DLP 1163 — Modifying xDSL profiles
DLP 1163-1
DLP 1170 — Configure SSH and SFTP
DLP 1170-1
DLP 1173 — Switch a user from ADSL to VDSL
DLP 1173-1
x
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
Contents
DLP 1174 — Create an xDSL IPoA user and add this user to a VLAN on the LT for C-VLAN cross-connect DLP 1174-1 DLP 1182 — Configure SHDSL
DLP 1182-1
DLP 1183 — Configure IMA on SHDSL spans
DLP 1183-1
DLP 1187 — Configure global VLAN parameters on the LT
DLP 1187-1
DLP 1188 — Configure custom PSD points
DLP 1188-1
DLP 1189 — Configure VDSL2 virtual noise values
DLP 1189-1
DLP 1190 — Configure threshold crossing alerts
DLP 1190-1
DLP 1197 — View port configuration and operational data on LT
DLP 1197-1
DLP 1201 — Configure protocol tracing
DLP 1201-1
DLP 1202 — Configure QoS threshold crossing alerts
DLP 1202-1
DLP 1203 — Configure general security settings
DLP 1203-1
DLP 1205 — Configure Link Related Ethernet OAM
DLP 1205-1
DLP 1206 — Configure an xDSL DPBO profile
DLP 1206-1
DLP 1207 — Modify an xDSL DPBO profile
DLP 1207-1
DLP 1208 — Configure xDSL power back off
DLP 1208-1
DLP 1212 — Create an IP user/subnet
DLP 1212-1
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
xi
Contents
DLP 1215 — Configure the impulse noise sensor on an xDSL line
DLP 1215-1
DLP 1217 — Configure the xDSL overrule data
DLP 1217-1
DLP 1219 — Forced NT switchover
DLP 1219-1
DLP 1220 — Manage the CDE profile
DLP 1220-1
DLP 1221 — Manage troubleshooting counters on LT
DLP 1221-1
DLP 1225 — Configure the p-bit counter on a VLAN port
DLP 1225-1
DLP 1232 — Create an xDSL IPoA user and add this user to a VLAN on the LT for iBridge DLP 1232-1 DLP 1253 — Configure the third-party equipment management port on the 7356 FD REM
DLP 1253-1
DLP 1255 — Configure a port on the NELT-B LT
DLP 1255-1
DLP 1257 — Configure a line with an xDSL RTX profile
DLP 1257-1
DLP 1258 — Modify an xDSL RTX profile
DLP 1258-1
DLP 1270 — Configure spanning tree on the NELT-B LT DLP 1270-1 DLP 1271 — Configure link aggregation on the NELT-B LT
DLP 1271-1
DLP 1282 — Configure the fairness SLA on the NELT-B LT
DLP 1282-1
xii
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
Contents
DLP 1283 — Troubleshooting congestion on the NELT-B LT DLP 1283-1 DLP 1291 — Configure a Vectoring Control Entity profile and associate it to a board
DLP 1291-1
DLP 1292 — Modify a Vectoring Control Entity profile
DLP 1292-1
DLP 1293 — Delete a Vectoring Control Entity profile
DLP 1293-1
DLP 1294 — Configure or modify the mapping between the VP board and the SLV LT boards DLP 1294-1 DLP 1295 — Configure a line with an xDSL vectoring profile
DLP 1295-1
DLP 1296 — Modify an xDSL vectoring profile
DLP 1296-1
DLP 1297 — Delete an xDSL vectoring profile
DLP 1297-1
DLP 1298 — Monitor xDSL vectoring lines
DLP 1298-1
DLP 2101 — Create operator profiles and instances
DLP 2101-1
DLP 2103 — Configure system parameters
DLP 2103-1
DLP 2105 — Configure link aggregation usage
DLP 2105-1
DLP 2107 — Manage OSPF
DLP 2107-1
DLP 2108 — Configure RIP
DLP 2108-1
DLP 2109 — Configure SNMP and trap management
DLP 2109-1
DLP 2110 — Manage alarms
DLP 2110-1
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
xiii
Contents
DLP 2111 — Plan, replan, and unplan equipment
DLP 2111-1
DLP 2114 — Configure NT redundancy
DLP 2114-1
DLP 2115 — Create a L2-terminated forwarder VLAN
DLP 2115-1
DLP 2116 — Create a L2-terminated router VLAN
DLP 2116-1
DLP 2121 — Add a network/LAG port to a VLAN in the SHub
DLP 2121-1
DLP 2122 — Create a forwarding VRF
DLP 2122-1
DLP 2123 — Create a router VRF
DLP 2123-1
DLP 2125 — Create an IPoA user
DLP 2125-1
DLP 2126 — Create an IPoE user
DLP 2126-1
DLP 2128 — Add an LT port to a VLAN on the SHub
DLP 2128-1
DLP 2132 — Configure filtering on the NT
DLP 2132-1
DLP 2136 — Configure the multicast service in the system
DLP 2136-1
DLP 2137 — Configure a multicast VLAN
DLP 2137-1
DLP 2138 — Configure a multicast channel
DLP 2138-1
DLP 2139 — Configure DHCP relay agent in iBridge mode
DLP 2139-1
DLP 2140 — Configure DHCP relay agent in router mode
DLP 2140-1
xiv
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
Contents
DLP 2141 — Configure DHCP relay agent in forwarder mode
DLP 2141-1
DLP 2142 — Configure the system security domain
DLP 2142-1
DLP 2144 — Configure RADIUS
DLP 2144-1
DLP 2150 — Configure ARP table entry
DLP 2150-1
DLP 2154 — Create a snapshot alarm table
DLP 2154-1
DLP 2155 — Monitor alarms
DLP 2155-1
DLP 2157 — Manage the SHub database
DLP 2157-1
DLP 2160 — View version of the SHub software
DLP 2160-1
DLP 2162 — Modify the external management VLAN
DLP 2162-1
DLP 2164 — Ping another host
DLP 2164-1
DLP 2165 — Perform a traceroute action
DLP 2165-1
DLP 2166 — Configure SNMP proxy CPE management
DLP 2166-1
DLP 2167 — Script files
DLP 2167-1
DLP 2168 — Modify the system management IP parameters
DLP 2168-1
DLP 2169 — Configure cluster management
DLP 2169-1
DLP 2171 — Enable EMS management
DLP 2171-1
DLP 2172 — Create a default operator profile
DLP 2172-1
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
xv
Contents
DLP 2175 — Configure system management IP parameters
DLP 2175-1
DLP 2176 — Performance monitoring commands
DLP 2176-1
DLP 2177 — Configure SFP downlink ports
DLP 2177-1
DLP 2179 — Configure system logging
DLP 2179-1
DLP 2180 — Configure static MAC addresses
DLP 2180-1
DLP 2181 — Configure operator authentication via RADIUS
DLP 2181-1
DLP 2185 — Configure DHCP MAC concentration in forwarder mode
DLP 2185-1
DLP 2186 — Configure ANCP session
DLP 2186-1
DLP 2191 — Enable dual tagging in the SHub
DLP 2191-1
DLP 2195 — Configure general bridge parameters on the LT
DLP 2195-1
DLP 2196 — Configure Voice SIP
DLP 2196-1
DLP 2198 — Configure the multicast service on a user port
DLP 2198-1
DLP 2199 — Configure QoS on the SHub
DLP 2199-1
DLP 2200 — Configure Spanning Tree on the SHub
DLP 2200-1
DLP 2204 — Configure an unnumbered IP interface on the SHub
DLP 2204-1
xvi
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
Contents
DLP 2209 — Configure vMAC
DLP 2209-1
DLP 2210 — View the status of various system parameters
DLP 2210-1
DLP 2211 — Configure SFP uplink ports
DLP 2211-1
DLP 2213 — Enable OAM counters
DLP 2213-1
DLP 2214 — Configure connectivity fault management
DLP 2214-1
DLP 2216 — Configure Voice MEGACO
DLP 2216-1
DLP 2222 — Create the PCCP group
DLP 2222-1
DLP 2223 — Configure SHub port mirroring
DLP 2223-1
DLP 2224 — Change shelf mode
DLP 2224-1
DLP 2230 — Configure a VLAN on the SHub
DLP 2230-1
DLP 2231 — Manage the ports on the NT
DLP 2231-1
DLP 2236 — Configure the enhanced system clock synchronization
DLP 2236-1
DLP 2273 — External Packet Forwarding
DLP 2273-1
Routine Task Procedure (RTP) RTP 1102 — Retrieve remote inventory
RTP 1102-1
RTP 1103 — Retrieve board temperature
RTP 1103-1
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
xvii
Contents
RTP 2100 — Backup the configuration
RTP 2100-1
RTP 2101 — Restore the configuration
RTP 2101-1
Trouble Analysis Procedure (TAP) TAP 1100 — Metallic test access
TAP 1100-1
TAP 1101 — F5 loopback test
TAP 1101-1
TAP 1102 — Equipment repair
TAP 1102-1
TAP 1103 — Single ended line testing
TAP 1103-1
TAP 1105 — Dual-ended line testing
TAP 1105-1
TAP 1106 — ITSC
TAP 1106-1
TAP 1107 — MELT
TAP 1107-1
TAP 1108 — Integrated NBLT for MEGACO Termination TAP 1108-1 TAP 1109 — Integrated NBLT for SIP Termination
TAP 1109-1
TAP 2104 — Fault isolation and troubleshooting
TAP 2104-1
Training (TNG) TNG 1104 — DHCP relay agent configuration
TNG 1104-1
TNG 1105 — Overall software packages
TNG 1105-1
xviii
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
Contents
TNG 1107 — xDSL parameters
TNG 1107-1
TNG 1108 — SHDSL parameters
TNG 1108-1
TNG 1115 — Slot numbering schemes
TNG 1115-1
TNG 1116 — Link Related Ethernet OAM (EFM OAM)
TNG 1116-1
TNG 1119 — vMAC
TNG 1119-1
TNG 1120 — VLAN translation
TNG 1120-1
TNG 1121 — xDSL bonding
TNG 1121-1
TNG 2100 — Service installation
TNG 2100-1
TNG 2101 — QoS configuration
TNG 2101-1
TNG 2102 — IGMP and multicast configuration
TNG 2102-1
TNG 2106 — Specifying 7330 ISAM FTTN expansion units using the CLI
TNG 2106-1
TNG 2109 — Performance management counters
TNG 2109-1
TNG 2110 — Configuration examples
TNG 2110-1
TNG 2112 — 7330 ISAM FTTN configuration for subtending
TNG 2112-1
TNG 2117 — Enhanced iBridge
TNG 2117-1
TNG 2118 — PPPoE with MAC address concentration
TNG 2118-1
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
xix
Contents
Appendix (A) A.
Configuration example values for FD 24Gbps NT A.1 A.2 A.3 A.4 A.5 A.6 A.7 A.8 A.9 A.10 A.11
A-1
Purpose ................................................................................... A-2 Equipment................................................................................ A-2 xDSL profiles ............................................................................. A-3 SHub ports................................................................................ A-3 VLANs ..................................................................................... A-4 VRFs ....................................................................................... A-5 Lines....................................................................................... A-6 IP bridge .................................................................................. A-7 IP forwarder.............................................................................. A-7 IP router .................................................................................. A-8 Enhanced IP router...................................................................... A-8
Index
xx
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
1—
Introduction
1.1 Introduction
1-2
1.2 How to use this document 1.3 Configuration examples
1-2 1-5
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
1-1
1 — Introduction
1.1
Introduction This document provides instructions on CLI operation and maintenance tasks and procedures for the Alcatel-Lucent 7302 ISAM, the 7330 ISAM FTTN and the 7356 ISAM FTTB. These tasks and procedures are identical for the 7302 ISAM, the 7330 ISAM FTTN and the 7356 ISAM FTTB, unless specified otherwise. Throughout the document, the 7302 ISAM, the 7330 ISAM FTTN and the 7356 ISAM FTTB will be referred to as the Network Element (NE). See the CLI Commands for FD 24Gbps NT document for more detailed information about the CLI command syntax.
1.2
How to use this document This document follows the task-oriented practice (TOP). The TOP method is a documentation system that uses different types of layers, or documents, to describe the installation, operations, and maintenance of telecommunications equipment and software. Most layers in the TOP system provide step-by-step instructions for the completion of a specific task or procedure. A TOP document is structured so that experienced and less experienced users can effectively use the material to perform work assignments. Less experienced users can refer to detailed procedures to complete a task. Experienced users can bypass detailed procedures and use only the level of information that they need.
TOP layers TOP documentation is constructed in layers, which provide the user with easy access to any point within the task description. This guide may contain any of the following layers:
• • • • • •
Index List (IXL) Non-Trouble Procedure (NTP) Detailed Level Procedure (DLP) Routine Task Procedure (RTP) Trouble Analysis Procedure (TAP) Training (TNG)
Figure 1-1 shows the major paths of TOP layers that may be used in this guide.
1-2
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
1 — Introduction Figure 1-1 TOP layers and major paths
Index List (IXL)
Non-Trouble Procedure (NTP)
Routine Task Procedure (RTP)
Trouble Analysis Procedure (TAP)
Training (TNG)
Detailed Level Procedure (DLP)
Task index list (IXL)
An IXL lists the available tasks in the TOP document. An IXL is used to find a task category and the applicable procedures to perform a task. Non-trouble procedure (NTP)
An NTP describes how to perform a task, such as how to save a system after it has been installed, turn up a system for service, or maintain a system according to a maintenance plan. NTPs are made up of steps that often refer to DLPs or TNGs. Less experienced users, or experienced users who need more information, can go to the DLPs for detailed procedural and safety information, and TNGs for supporting information. If users go to the referenced DLP or TNG, they must return to the NTP to continue the procedure. Detailed level procedure (DLP)
A DLP contains detailed steps that describe how to perform a task. In addition to step-by-step information, a DLP contains any tables or illustrations that may be required to perform the task. DLPs are typically referenced from an NTP, always referenced from the IXL, and sometimes referenced from other DLPs. When a DLP is referenced from another layer, users must return to the layer at which the DLP was referenced to continue the procedure. Routine task procedure (RTP)
An RTP describes how to perform a routine maintenance task. RTPs are typically referenced from the IXL.
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
1-3
1 — Introduction
Trouble analysis procedure (TAP)
A TAP describes how to identify and clear trouble in the system. TAPs are made up of step-by-step instructions. For less experienced users, or experienced users who need more information, some tasks provide a reference to a DLP or TNG. If users go to the referenced DLP or TNG, they must return to the TAP to continue the procedure. Training (TNG)
A TNG contains supplementary information about a task or procedure. A TNG might refer to a DLP or other document. If users go to the referenced document, they need to return to the TNG to read the remaining information.
Step details NTPs, DLPs, RTPs and TAPs use procedural steps and decision steps. Procedural steps provide instructions, and decision steps provide a go-to choice. Procedural steps may contain notations that refer to additional information such as tables, figures, examples and other TOP layers. For example, a step in an NTP might refer to a DLP. Key information required to complete a step is shown at the beginning of the step. More detailed information, which can be accessed according to experience level, is provided at the end of the step, as shown in the example below: “Reconnect the power feeds; see DLP 106.” The completion of a specific task or procedure is indicated as follows: “STOP. This procedure is complete.”
Procedures with options or substeps When there are options in a procedure, they are identified by letters. When there are required substeps in a procedure, they are identified by Roman numerals.
Procedure 1-1 Example of options in a procedure At step 1, you can choose option a or b. At step 2, you must do what the step indicates. 1
2
1-4
This step offers two options. You must choose one of the following: a
This is one option.
b
This is another option.
You must perform this step.
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
1 — Introduction
Procedure 1-2 Example of required substeps in a procedure At step 1, you must perform a series of substeps within a step. At step 2, you must do what the step indicates. 1
2
1.3
This step has a series of substeps that you must perform to complete the step. You must perform the following substeps: i
This is the first substep.
ii
This is the second substep.
iii
This is the third substep.
You must perform this step.
Configuration examples Configuration examples are provided in the DLPs. Different rack configurations are used in the examples. These are indicated with Config#1, Config#2 and Config#3. Appendix A “Configuration example values for FD 24Gbps NT” gives an overview of the different configurations and values used in the DLP configuration examples.
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
1-5
1 — Introduction
1-6
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
Index List (IXL)
IXL 100 — Master Task Index List
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
IXL 100 — Master Task Index List Table IXL 100-1: Non-Trouble Procedures (NTPs) Title
NTP number
Execute script files
NTP 1101
Perform equipment repairs
NTP 1114
Monitor performance and view configuration
NTP 1118
Modify DSL services
NTP 1119
Maintain the system
NTP 1124
Manage system logging
NTP 1126
Configure SHDSL
NTP 1127
Configure Link Related Ethernet OAM
NTP 1130
Configure Connectivity Fault Management
NTP 1132
Initial system configuration
NTP 2100
Configure equipment
NTP 2103
Configure a VLAN cross-connect
NTP 2104
Configure an iBridge VLAN
NTP 2105
Configure an IP-aware bridge
NTP 2106
Configure an IP router
NTP 2107
Configure services
NTP 2108
Monitor alarms
NTP 2115
Perform software management
NTP 2116
Modify system parameters
NTP 2117
Troubleshooting the network
NTP 2120
Manage an SNMP proxy CPE
NTP 2121
(1 of 2)
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
IXL 100-1
IXL 100 — Master Task Index List
Title
NTP number
Cluster management
NTP 2122
Configure a loopback interface on the SHub
NTP 2129
Configure an enhanced IP router
NTP 2133
(2 of 2)
Table IXL 100-2: Detailed Level Procedures (DLP) Title
DLP number
Set up a local CLI session or a local TL1 session
DLP 1100
Lock and unlock equipment
DLP 1112
Configure the equipment
DLP 1113
Configure a VLAN on the LT for C-VLAN cross-connect
DLP 1117
Configure a VLAN on the LT for S-VLAN cross-connect
DLP 1118
Configure a VLAN on the LT for S+C-VLAN cross-connect
DLP 1119
Configure a VLAN on the LT for C-iBridge
DLP 1120
Create an xDSL/native Ethernet user and add this user to a VLAN on the LT
DLP 1124
Create xDSL profiles
DLP 1129
Configure xDSL bonding
DLP 1130
Configure QoS
DLP 1134
Configure 802.1x
DLP 1145
Configure PPPoE relay on LT
DLP 1146
Configure PPPoX cross-connect
DLP 1147
Shut down and restart the NT
DLP 1151
Reboot the system
DLP 1152
Shut down and restart individual equipment
DLP 1153
Manage OSWP
DLP 1159
Modifying xDSL profiles
DLP 1163
Configure SSH and SFTP
DLP 1170
Switch a user from ADSL to VDSL
DLP 1173
Create an xDSL IPoA user and add this user to a VLAN on the LT for C-VLAN cross-connect
DLP 1174
Configure SHDSL
DLP 1182
Configure IMA on SHDSL spans
DLP 1183
Configure global VLAN parameters on the LT
DLP 1187
Configure custom PSD points
DLP 1188
Configure VDSL2 virtual noise values
DLP 1189
Configure threshold crossing alerts
DLP 1190
View port configuration and operational data on LT
DLP 1197
(1 of 4)
IXL 100-2
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
IXL 100 — Master Task Index List
Title
DLP number
Configure protocol tracing
DLP 1201
Configure QoS threshold crossing alerts
DLP 1202
Configure general security settings
DLP 1203
Configure Link Related Ethernet OAM
DLP 1205
Configure an xDSL DPBO profile
DLP 1206
Modify an xDSL DPBO profile
DLP 1207
Configure xDSL power back off
DLP 1208
Create an IP user/subnet
DLP 1212
Configure the impulse noise sensor on an xDSL line
DLP 1215
Configure the xDSL overrule data
DLP 1217
Forced NT switchover
DLP 1219
Manage the CDE profile
DLP 1220
Manage troubleshooting counters on LT
DLP 1221
Configure the p-bit counter on a VLAN port
DLP 1225
Create an xDSL IPoA user and add this user to a VLAN on the LT for iBridge
DLP 1232
Configure the third-party equipment management port on the 7356 FD REM
DLP 1253
Configure a port on the NELT-B LT
DLP 1255
Configure a line with an xDSL RTX profile
DLP 1257
Modify an xDSL RTX profile
DLP 1258
Configure spanning tree on the NELT-B LT
DLP 1270
Configure link aggregation on the NELT-B LT
DLP 1271
Configure the fairness SLA on the NELT-B LT
DLP 1282
Troubleshooting congestion on the NELT-B LT
DLP 1283
Configure a Vectoring Control Entity profile and associate it to a board
DLP 1291
Modify a Vectoring Control Entity profile
DLP 1292
Delete a Vectoring Control Entity profile
DLP 1293
Configure or modify the mapping between the VP board and the SLV LT boards
DLP 1294
Configure a line with an xDSL vectoring profile
DLP 1295
Modify an xDSL vectoring profile
DLP 1296
Delete an xDSL vectoring profile
DLP 1297
Monitor xDSL vectoring lines
DLP 1298
Create operator profiles and instances
DLP 2101
Configure system parameters
DLP 2103
Configure link aggregation usage
DLP 2105
Manage OSPF
DLP 2107
Configure RIP
DLP 2108
Configure SNMP and trap management
DLP 2109
(2 of 4)
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
IXL 100-3
IXL 100 — Master Task Index List
Title
DLP number
Manage alarms
DLP 2110
Plan, replan, and unplan equipment
DLP 2111
Configure NT redundancy
DLP 2114
Create a L2-terminated forwarder VLAN
DLP 2115
Create a L2-terminated router VLAN
DLP 2116
Add a network/LAG port to a VLAN in the SHub
DLP 2121
Create a forwarding VRF
DLP 2122
Create a router VRF
DLP 2123
Create an IPoA user
DLP 2125
Create an IPoE user
DLP 2126
Add an LT port to a VLAN on the SHub
DLP 2128
Configure filtering on the NT
DLP 2132
Configure the multicast service in the system
DLP 2136
Configure a multicast VLAN
DLP 2137
Configure a multicast channel
DLP 2138
Configure DHCP relay agent in iBridge mode
DLP 2139
Configure DHCP relay agent in router mode
DLP 2140
Configure DHCP relay agent in forwarder mode
DLP 2141
Configure the system security domain
DLP 2142
Configure RADIUS
DLP 2144
Configure ARP table entry
DLP 2150
Create a snapshot alarm table
DLP 2154
Monitor alarms
DLP 2155
Manage the SHub database
DLP 2157
View version of the SHub software
DLP 2160
Modify the external management VLAN
DLP 2162
Ping another host
DLP 2164
Perform a traceroute action
DLP 2165
Configure SNMP proxy CPE management
DLP 2166
Script files
DLP 2167
Modify the system management IP parameters
DLP 2168
Configure cluster management
DLP 2169
Enable EMS management
DLP 2171
Create a default operator profile
DLP 2172
Configure system management IP parameters
DLP 2175
Performance monitoring commands
DLP 2176
Configure SFP downlink ports
DLP 2177
(3 of 4)
IXL 100-4
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
IXL 100 — Master Task Index List
Title
DLP number
Configure system logging
DLP 2179
Configure static MAC addresses
DLP 2180
Configure operator authentication via RADIUS
DLP 2181
Configure DHCP MAC concentration in forwarder mode
DLP 2185
Configure ANCP session
DLP 2186
Enable dual tagging in the SHub
DLP 2191
Configure general bridge parameters on the LT
DLP 2195
Configure Voice SIP
DLP 2196
Configure the multicast service on a user port
DLP 2198
Configure QoS on the SHub
DLP 2199
Configure Spanning Tree on the SHub
DLP 2200
Configure an unnumbered IP interface on the SHub
DLP 2204
Configure vMAC
DLP 2209
View the status of various system parameters
DLP 2210
Configure SFP uplink ports
DLP 2211
Enable OAM counters
DLP 2213
Configure connectivity fault management
DLP 2214
Configure Voice MEGACO
DLP 2216
Create the PCCP group
DLP 2222
Configure SHub port mirroring
DLP 2223
Change shelf mode
DLP 2224
Configure a VLAN on the SHub
DLP 2230
Configure the enhanced system clock synchronization
DLP 2236
External Packet Forwarding
DLP 2273
(4 of 4)
Table IXL 100-3: Routine Task Procedure (RTP) Title
RTP number
Retrieve remote inventory
RTP 1102
Retrieve board temperature
RTP 1103
Backup the configuration
RTP 2100
Restore the configuration
RTP 2101
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
IXL 100-5
IXL 100 — Master Task Index List Table IXL 100-4: Trouble Analysis Procedure (TAP) Title
TAP number
Metallic test access
TAP 1100
F5 loopback test
TAP 1101
Equipment repair
TAP 1102
Single ended line testing
TAP 1103
Dual-ended line testing
TAP 1105
ITSC
TAP 1106
MELT
TAP 1107
Integrated NBLT for MEGACO Termination
TAP 1108
Integrated NBLT for SIP Termination
TAP 1109
Fault isolation and troubleshooting
TAP 2104
Table IXL 100-5: Training (TNG) Title
TNG number
DHCP relay agent configuration
TNG 1104
Overall software packages
TNG 1105
xDSL parameters
TNG 1107
SHDSL parameters
TNG 1108
Link Related Ethernet OAM (EFM OAM)
TNG 1116
vMAC
TNG 1119
VLAN translation
TNG 1120
xDSL bonding
TNG 1121
Service installation
TNG 2100
QoS configuration
TNG 2101
IGMP and multicast configuration
TNG 2102
Specifying 7330 ISAM FTTN expansion units using the CLI
TNG 2106
Performance management counters
TNG 2109
Configuration examples
TNG 2110
7330 ISAM FTTN configuration for subtending
TNG 2112
Slot numbering schemes
TNG 1115
Enhanced iBridge
TNG 2117
PPPoE with MAC address concentration
TNG 2118
IXL 100-6
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
Non-Trouble Procedures (NTP)
NTP 1101 — Execute script files NTP 1114 — Perform equipment repairs NTP 1118 — Monitor performance and view configuration NTP 1119 — Modify DSL services NTP 1124 — Maintain the system NTP 1126 — Manage system logging NTP 1127 — Configure SHDSL NTP 1130 — Configure Link Related Ethernet OAM NTP 1132 — Configure Connectivity Fault Management NTP 2100 — Initial system configuration NTP 2103 — Configure equipment NTP 2104 — Configure a VLAN cross-connect NTP 2105 — Configure an iBridge VLAN NTP 2106 — Configure an IP-aware bridge NTP 2107 — Configure an IP router NTP 2108 — Configure services
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
NTP 2115 — Monitor alarms NTP 2116 — Perform software management NTP 2117 — Modify system parameters NTP 2120 — Troubleshooting the network NTP 2121 — Manage an SNMP proxy CPE NTP 2122 — Cluster management NTP 2129 — Configure a loopback interface on the SHub NTP 2133 — Configure an enhanced IP router
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
NTP 1101 — Execute script files Purpose A script file is a file containing CLI commands. A script file must follow the same syntax rules as commands entered interactively. Only the tab and the question mark lose their special meaning in a script, so command expansion and single-line help are not available. The script will be aborted if one of the commands in the script fails. A command may be preceded by a minus '-' to prevent the script from being aborted in case of a semantic error; for example, when you try to delete a node instance that does not exist. By default, a command script does not interact with the user. The execution of the script will be aborted if a command or filter requires interaction with the user. Interactivity can be enabled by specifying the interactive option with the exec command. Command scripts may not be nested.
Caution — When an NT switchover takes place during execution of the script, the possibility exists that CLI commands will fail. To recover from this situation the operator should delete the objects which were created before. Then, the CLI command (or script) must be re-executed.
Procedure In order to use script files, you need to perform the following tasks: 1
Create and execute script files; see DLP 2167.
2
STOP. This procedure is complete.
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 1101-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
NTP 1101 — Execute script files
NTP 1101-2
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
NTP 1114 — Perform equipment repairs Purpose This procedure provides the steps to perform equipment repair on the NE.
Procedure Proceed as follows to perform equipment repair tasks: 1
Plan, unplan, and replan equipment (for example, plug-in units); see DLP 2111.
2
Pull out and plug in equipment. For the procedures, see the hardware installation manual for your equipment.
3
Lock and unlock equipment (mostly plug-in units); see DLP 1112.
4
Start up or shut down the system, select one of:
5
a
Shut down or restart the NT; see DLP 1151.
b
Reboot the entire system; see DLP 1152.
c
Shut down individual equipment; see DLP 1153.
STOP. This procedure is complete.
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 1114-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
NTP 1114 — Perform equipment repairs
NTP 1114-2
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
NTP 1118 — Monitor performance and view configuration Purpose This procedure list the procedures that can be used for:
• •
Performance Monitoring (PM) viewing the configuration and operational data of a port
Procedure The following tasks can be performed: 1
Configure the Threshold Crossing Alert (TCA); see DLP 1190.
2
Enable the Operations and Maintenance (OAM) counters; see DLP 2213.
3
Manage the troubleshooting counters on the LT; see DLP 1221.
4
Viewing the PM counters; see DLP 2176.
5
Viewing the configuration and operational data of a port (xDSL or Ethernet); see DLP 1197.
6
View the status of different system parameters (system clock, memory usage on the NT and CPU load on the NT); see DLP 2210.
7
STOP. This procedure is complete.
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 1118-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
NTP 1118 — Monitor performance and view configuration
NTP 1118-2
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
NTP 1119 — Modify DSL services Purpose This procedure provides the steps to adapt the following services on the NE:
• •
xDSL profiles switching a user from ADSL to VDSL
Procedure You can perform the following tasks: 1
Modify an xDSL profile; see DLP 1163.
2
Modify a DPBO profile; see DLP 1207.
3
Modify an RTX profile; see DLP 1258.
4
Modify an xDSL vectoring profile; see DLP 1296.
5
Modify an Vectoring Control Entity profile; see DLP 1292.
6
Switch a user from ADSL to VDSL; see DLP 1173.
7
STOP. This procedure is complete.
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 1119-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
NTP 1119 — Modify DSL services
NTP 1119-2
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
NTP 1124 — Maintain the system Purpose This NTP provides the steps for system maintenance of the NE.
Procedure Perform this procedure to maintain the system: 1
Back up the system configuration; see RTP 2100.
2
Restore the system configuration; see RTP 2101.
3
Retrieve the remote inventory; see RTP 1102.
4
STOP. This procedure is complete.
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 1124-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
NTP 1124 — Maintain the system
NTP 1124-2
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
NTP 1126 — Manage system logging Purpose This NTP provides the steps to manage system logging (SYSLOG) for the NE.
General System statistics logs are user configurable and you can create up to 64 system logs. System logs can be saved locally to a remote server, or all active CLI terminals, or all active TL1 terminals. You can perform the following three main tasks using CLI:
• • •
enable and disable logging for all system logs create and configure up to 64 system logs monitor system logs
Using filters, you can determine which messages are sent to the system log file, as well as set the severity level of the system log. The following applies when using SYSLOG in an operational (E2E) environment:
• •
The NE supports SYSLOG according to RFC3164 (aka BSD SYSLOG) The SYSLOG application on the external server has to listen to UDP port 514. Everything that comes in via this port should be considered as being a SYSLOG message. The NE sends out its SYSLOG messages on this port.
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 1126-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
NTP 1126 — Manage system logging
•
The severity of the various application messages is predefined. It is reported as follows: • CLI operator commands: INFO • Service Affecting alarm messages: EMERGENCY • Authentication messages: ALERT • Other CLI/TL1 messages (non-service affecting): INFO • protocol tracing: DEBUG • videoCDR reporting: NOTICE
Note — See DLP 1201 for the configuration of protocol tracing.
See the CLI Command Guide for FD 24Gbps NT document for more information about CLI commands used to configure system logging. See the System Description for FD 24Gbps NT document for more information about system and security statistics logging.
Procedure Use this procedure to manage system logging for the NE. See the references for detailed procedures and safety information.
NTP 1126-2
1
Enable and disable logging for all system logs; see DLP 2179.
2
Create, configure, and monitor system logs; see DLP 2179.
3
STOP. This procedure is complete.
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
NTP 1127 — Configure SHDSL Purpose Single-pair High-speed Digital Subscriber Line (SHDSL) is a physical layer standard based on the ITU-T Recommendation G.991.2. It describes a versatile transmission method for data transport in the telecommunication access networks, capable of supporting whichever network protocol is currently deployed while enabling higher bandwidth and reach (for example, TDM, ATM, Frame Relay and so on). SHDSL transceivers are designed primarily for duplex operation over mixed gauges of two wire twisted metallic pairs. Four-wire and m-pair operations are included as options for extended reach. The use of signal regenerators for both the two-wire and the multi-wire operations is optional. Inverse Multiplexing for ATM (IMA) permits a broadband cell stream to be transported on a number of lower-rate physical links (for example, several SHDSL span lines) by grouping these physical links into a single logical channel. The specification includes a means to maintain cell order and a method to allow in-service loss and restore of individual physical links.
Note — For a more detailed description of the different parameters for SHDSL span, unit and segment configuration, refer to TNG 1108.
Procedure Proceed as follows to configure SHDSL: 1
To configure SHDSL; see DLP 1182.
2
To configure IMA on SHDSL spans; see DLP 1183.
3
STOP. This procedure is complete.
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 1127-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
NTP 1127 — Configure SHDSL
NTP 1127-2
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
NTP 1130 — Configure Link Related Ethernet OAM Purpose This procedure provides the steps to configure Link Related Ethernet OAM (EFM OAM) on the NE and view local and remote (CPE) EFM OAM configuration, statistics, and counters.
Note — For more information on Link Related Ethernet OAM, see TNG 1116.
Procedure Proceed as follows to configure EFM OAM: 1
Configuration of EFM OAM; see DLP 1205.
2
After configuration, the following actions can be performed:
3
a
Viewing of Local and Remote (CPE) information; see DLP 1205.
b
Viewing of EFM OAM statistics; see DLP 1205.
c
Retrieve MAC counters; see DLP 1205.
d
Retrieve PME counters; see DLP 1205.
STOP. This procedure is complete.
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 1130-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
NTP 1130 — Configure Link Related Ethernet OAM
NTP 1130-2
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
NTP 1132 — Configure Connectivity Fault Management Purpose This NTP provides the steps for configuring Connectivity Fault Management (CFM) on the NE and for viewing CFM configuration.
General CFM (802.1ag) is an Ethernet OAM capability providing end to end fault detection and isolation on Ethernet networks. CFM requires that bridge ports throughout the network be configured with software entities, called “maintenance points” (MP). MPs process and respond to CFM messages sent on the dataplane. By looking at the replies from these MPs, a network operator can isolate a fault to a specific link or node. MPs are organized by maintenance domain (MD) and maintenance association (MA). See the System Description for FD 24Gbps NT document for more information about CFM. You can configure MPs on the NE to process and respond to CFM messages sent from the edge router or BNG. You cannot initiate CFM tests from the NE. To configure CFM, you must configure an MD, an MA, and you must configure an MEP or you must configure the MA to auto-create MIPs. The ISAM supports MIPs and network facing MEPs at user ports. Within these MPs the ISAM responds to LBMs and to LTMs coming from the network. The ISAM responds to LBM coming from the user (see DSLF TR-101). The ISAM supports network facing MEPs on the LT board at its GE interface towards the NT board. Within these MEPs the ISAM responds to LBMs and to LTMs. See DLP 2214 for more information on configuration restrictions and prerequisites. You can also view CFM configuration data on the NE.
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 1132-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
NTP 1132 — Configure Connectivity Fault Management
Prerequisites The following prerequisites must be fulfilled before CFM can be configured:
• • •
You must have network management access or craft port access to the NE you want to configure and be familiar with the CLI. CFM must be supported on the access aggregation network. A VLAN must be configured.
Procedure Use this procedure to configure CFM or view CFM configuration. 1
NTP 1132-2
Configure CFM: i
Configure a maintenance domain; see DLP 2214
ii
Configure (create) a maintenance association; see DLP 2214
iii
Configure a maintenance end point; see DLP 2214
iv
Optionally, configure (modify) the maintenance association and set the mhf-creation parameter to mhf-default; see DLP 2214
2
View CFM configuration; see DLP 2214
3
STOP. This procedure is complete.
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
NTP 2100 — Initial system configuration Purpose This document describes the procedure to be used to perform the initial system configuration.
General Figure NTP 2100-1 shows the management topology of the NE system. Figure NTP 2100-1: Management Topology EMS (e.g. AMS 5520)
SNMPv2 or SNMPv3
SNMP agent
TL1 Gateway
UDP
TL1 Terminal
SSH
TL1 agent
Telnet
TL1 CT
CLI Terminal
RS232
SSH
Telnet
CLI agent
CLI CT
Debug Terminal
RS232
UDP
Debug agent
ISAM Table NTP 2100-1 lists the different types of system managers.
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 2100-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
NTP 2100 — Initial system configuration Table NTP 2100-1: System Managers Manager type
Description
EMS
Remotely connected Element Management System based on SNMP
TL1 CT
Local Craft Terminal using TL1 commands
CLI CT
Local Craft Terminal using Command Line Interface (CLI) commands
CLI terminal
Remotely connected terminal using CLI commands based over telnet or ssh
TL1 gateway
Remotely connected gateways using TL1 commands over UDP
TL1 terminal
Remotely connected terminal using TL1 commands based on ssh
See the CLI Command Guide for FD 24Gbps NT document for detailed information about the CLI command syntax. See the TL1 Commands and Messages for FD 24Gbps NT document for detailed information about the TL1 command syntax.
Security Considerations The following must be taken into account with regard to system security:
• • • • • • •
It is advised to close the remote debug acess. By default, the accesss is not disabled. It is advised to use secure management channels (CLI/SSH, TL1/SSH, SNMPv3, SFTP). This implies closing the unsecured management channels. It is NOT advised to use unsecured remote management channels: CLI/Telnet, TL1/UDP, SNMPv1/2, or TFTP. If SNMPv1/2 is used anyway, it is advised not to use community string = public. It is advised to change the administrator password of TL1 and CLI (even if TL1 or CLI is not used by the operator). It is advised to deactivate the remote TL1 management interface when no remote TL1 is used. It is not possible to deactivate the local Craft Terminal TL1 access. SHub ACLs can be configured to restrict the traffic from the Element Management Systems (and other management plane services) to be routed to the NT OBC.
Procedure Proceed as follows to perform an initial system configuration:
NTP 2100-2
1
Set up a CLI session; see DLP 1100.
2
Create and configure an Operator Profile; see DLP 2101.
3
Create a default Operator Profile; see DLP 2172.
4
Configure the management IP parameters and network interfaces; see DLP 2175.
5
Configure SSH; see DLP 1170.
6
Configure the general security settings; see DLP 1203.
7
Configure the system parameters; see DLP 2103.
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
NTP 2100 — Initial system configuration
8
Configure the enhanced system clock synchronization; see DLP 2236.
9
Configure Simple Network Management Protocol (SNMP) and trap management; see DLP 2109.
10
Enable the management of EMS; see DLP 2171.
11
Configure the alarm management; see DLP 2110.
12
Save the SHub database; see DLP 2157.
13
STOP. This procedure is complete.
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 2100-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
NTP 2100 — Initial system configuration
NTP 2100-4
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
NTP 2103 — Configure equipment Purpose This procedure provides the steps to:
• • •
plan, unplan, or replan the equipment lock or unlock the equipment configure the SFP uplink ports and the SFP downlink ports
Some equipment-related items, such as the shelf, are auto-created at system startup and do not need to be created. However, they can be modified.
General The NE consists of a single shelf with plug-in units. You can perform the actions described in Table NTP 2103-1 to configure the equipment. Table NTP 2103-1: Configure plug-in units Action
Description
Planning equipment
Planning a piece of equipment is possible before and after the equipment is physically present and detected by the system (at startup). The system verifies the configuration parameters and checks if the required equipment is available. Note: As long as equipment is not planned, it is impossible to offer service. Units and other equipment are only available from an operation and maintenance point of view.
Unplanning equipment
If necessary, you can unplan any equipment. Unplanning, however, may be rejected in case of hierarchical dependencies. For example, it is impossible to unplan a shelf as long as one or more units in it are still planned.
Replanning equipment
Replanning is done when changing the current equipment.
(1 of 2)
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 2103-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
NTP 2103 — Configure equipment
Action
Description
Locking and unlocking equipment
When necessary, you can lock any equipment, most often a unit, to put it out of service. Locking a unit renders it inactive. No traffic is generated or received by the units. All alarms related to the unit are filtered except for the “board-missing”, “board installation missing” and “board-type mismatch” alarms. However, the unit is not removed from the configuration, and as soon as you unlock the unit, it becomes active again. It goes back to operational mode without restart or initialization, and traffic can resume immediately. Similarly, you can power down the unit and restart it at a later time. In this case, however, the unit will go through a complete startup cycle before traffic is possible.
(2 of 2)
Change the shelf mode When required, the shelf mode can be changed from NTIO_SUPPORTED (for shelves equipped with an NTIO board (and a second NT board) to NTIO_UNSUPPORTED (for shelves where an NTIO board is not required, in this case 2 extra LT slots are available) or vice versa.
Note — Changing the shelf mode results in an automatic restart of the system.
Procedure Proceed as follows to configure or modify the system equipment:
NTP 2103-2
1
Plan, replan, or unplan equipment; see DLP 2111.
2
Lock or unlock the equipment; see DLP 1112.
3
Modify the configuration of the system equipment; see DLP 1113.
4
If required, change the shelf mode; see DLP 2224.
5
Configure SFP downlink ports; see DLP 2177.
6
Configure SFP uplink ports; see DLP 2211.
7
STOP. This procedure is complete.
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
NTP 2104 — Configure a VLAN cross-connect Purpose The NE supports several VLAN cross-connect models:
• • •
Customer VLAN cross-connect or C-VLAN CC Service provider VLAN cross-connect or S-VLAN CC VLAN stacking or S+C-VLAN CC
Purpose of C-VLAN CC This is the most straightforward VLAN cross-connect model where a single VLAN ID at the EMAN side is associated with a given PVC at the user side. Any kind of traffic issued by the subscriber is passed transparently towards the network using the selected VLAN ID. Cross-connect VLANs can be enabled to be protocol aware for IGMP and 802.1x and to support the configuration of DHCP Option 82 and PPPoE relay.
Purpose of S-VLAN CC In this mode, the Service Provider VLAN (S-VLAN) ID at the EMAN side is associated with a single subscriber interface at the user side. The C-VLANs carried within the S-VLAN are passed transparently to the end user. This allows the end user to specify its own end-to-end connectivity, while remaining transparent for the EMAN. The NE acts as an S-VLAN aware bridge, with the restriction that only one subscriber interface can be attached. Forwarding is only done based on the S-VLAN forwarding context. The forwarding is transparent for the C-VLANs. Frames on the subscriber interface may or may not have an S-VLAN tag. In case of an absent S-VLAN tag (that is for C-VLAN tagged and untagged/priority tagged frames), the subscriber interface’s pre-configured S-VLAN ID will be assigned.
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 2104-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
NTP 2104 — Configure a VLAN cross-connect
Purpose of S+C-VLAN CC The basic VLAN cross-connect mode suffers from the fact the that number of VLAN identifiers is limited to 4K. Since the VLAN is a EMAN wide identifier, one ends up with a scalability issue: there cannot be more than 4K end users connected to the whole EMAN. To solve this issue, two VLANs are stacked and the cross-connection is then performed on the combination (S-VLAN, C-VLAN) allowing to theoretically reach up to 16M end users. The NE acts as a C-VLAN aware bridge, with the restriction that only one subscriber interface can be attached. Frames on the subscriber interface may be C-VLAN tagged or untagged/priority tagged. In case of C-VLAN tagged frames, a check will be performed on the received C-VLAN ID, while the subscriber interface‘s preconfigured S-VLAN will be assigned. In case of untagged/priority tagged frames, the subscriber interface’s pre-configured C-VLAN and S-VLAN will be assigned.
Prerequisite The following prerequisites must be fulfilled before a VLAN-CC of any type can be configured:
• •
The board must have been planned; see DLP 2111. xDSL profiles must have been created; see DLP 1129.
Procedure Proceed as follows (see also Figure NTP 2104-1):
NTP 2104-2
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
NTP 2104 — Configure a VLAN cross-connect Figure NTP 2104-1: Configure a VLAN Cross-connect on an SHub-based ISAM DLP 1117 (DLP 1118) (DLP 1119)
DLP 2230 DLP 2231
Network Ports
DLP 2121
SHub VLAN
DLP 2231 LT VLAN for
LT port C-VLAN CC
DLP 1124 DLP 1174
DLP 2128
C 11
VLAN 11 (=Bridge)
VLAN CC
VLAN 17 (=Bridge)
VLAN CC
Phy
S17 +C23
C-VLAN CC
S+C-VLAN CC
LT (No VLAN translation shown on user side)
VLAN 13 (=Bridge)
S17 +C29 VLAN CC
S+C-VLAN CC
Phy Phy
LAG
S 13
VLAN 19 (=Bridge) DLP 2105
VLAN CC
S-VLAN CC
LT
NT_SHUB ISAM_SHUB
1
2
C-, S+C- or S-VLAN CC
Configure a VLAN on the LT for VLAN cross-connect. Do one of the following: a
For C-VLAN cross-connect; see DLP 1117.
b
For S-VLAN cross-connect; see DLP 1118.
c
For S+C-VLAN cross-connect; see DLP 1119.
Create a user and add him to a VLAN created in step 1. Do one of the following: a
create an xDSL/native Ethernet user and add him to a VLAN on the LT; see DLP 1124.
b
create an xDSL IPoA user and add him to a VLAN on the LT (for C-VLAN cross-connect): see DLP 1174.
3
Configure network interface and LT interface on the SHub; see DLP 2231.
4
Optionally, configure LAG on the SHub; see DLP 2105.
5
Configure a VLAN on the SHub; see DLP 2230.
• • • 6
In case of C-VLAN cross-connect, the mode of the VLAN must be “cross-connect” and the VLAN ID is the ID of the C-VLAN In case of S-VLAN cross-connect, the mode of the VLAN must be “cross-connect” and the VLAN ID is the ID of the S-VLAN In case of S+C-VLAN cross-connect, the mode of the VLAN must be “cross-connect” and the VLAN ID is the ID of the S-VLAN
Add an LT port to the VLAN on the SHub; see DLP 2128.
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 2104-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
NTP 2104 — Configure a VLAN cross-connect
NTP 2104-4
7
Add a network/LAG port to the VLAN on the SHub; see DLP 2121.
8
STOP. This procedure is complete.
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
NTP 2105 — Configure an iBridge VLAN Purpose The concept of a VLAN in intelligent bridging (iBridge) mode is that multiple NSPs are each connected to the NE with a VLAN. The user ports are connected to the VLAN of their corresponding Network Service Provider (NSP). This procedure provides the steps to create an iBridge VLAN.
Prerequisite The following prerequisites must be fulfilled before an iBridge can be configured:
• •
The board must have been planned; see DLP 2111. xDSL profiles must have been created; see DLP 1129.
Procedure Proceed as follows to configure an iBridge (see also Figure NTP 2105-1):
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 2105-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
NTP 2105 — Configure an iBridge VLAN Figure NTP 2105-1: Configure an iBridge
DLP 1120 DLP 2230
DLP 2231
Network DLP 2121 Ports
SHub VLAN
DLP 2231
LT Ports
LT VLAN for iBridge
DLP 1124 DLP 1232
DLP 2128
iBridge VLAN 19
Phy LT
(No VLAN translation shown on user side)
iBridge VLAN 19
Phy LAG
Phy
iBridge VLAN 19
DLP 2105
NT_SHUB
LT
ISAM_SHUB
NTP 2105-2
1
Configure a VLAN on the LT for iBridge; see DLP 1120.
2
Create a user and add him to a VLAN created in step 1. Do one of the following: a
create an xDSL/native Ethernet user and add him to a VLAN on the LT; see DLP 1124.
b
create an xDSL IPoA user and add him to a VLAN on the LT (for iBridge): see DLP 1232.
3
Configure network interface and LT interface on the SHub; see DLP 2231.
4
Optionally, configure LAG on the SHub; see DLP 2105.
5
Configure a VLAN on the SHub; see DLP 2230.
6
Add an LT port to the VLAN on the SHub; see DLP 2128.
7
Add a network/LAG port to the VLAN on the SHub; see DLP 2121.
8
STOP. This procedure is complete.
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
NTP 2106 — Configure an IP-aware bridge Purpose In this mode, the NE can be seen as an IP-aware bridge without being seen as an IP next-hop. Users connected to the NE are seen as being directly attached to the edge router IP interfaces. The end-users use the IP address of the edge router as their default gateway, while the IP edge router sees the end-user subnets as directly attached networks. The NE sits in between and performs packet forwarding at L3. This procedure provides the steps to configure an IP-aware bridge on the NE. Figure NTP 2106-1: IP-aware Bridge VLAN X
NE
Video VLAN
Internet Video
Video VLAN is always in iBridge
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 2106-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
NTP 2106 — Configure an IP-aware bridge Figure NTP 2106-2: IP-aware Bridge: Traffic Flow Source MAC address = PC Destination MAC address = Network
NE
Source MAC address = NE Destination MAC address = Network
PC
Network
Source MAC address = Network Destination MAC address = NE Source MAC address = Network Destination MAC address = PC
Procedure Proceed as follows to configure an IP-aware bridge:
NTP 2106-2
1
Create a forwarder Virtual Routing Forwarding (VRF); see DLP 2122.
2
Create a L2-terminated forwarder VLAN for each of the Network Service Providers (NSP); see DLP 2115.
3
Add the network interfaces to the L2-terminated forwarder VLANs; see DLP 2121.
4
STOP. This procedure is complete.
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
NTP 2107 — Configure an IP router Purpose In this mode, the NE is seen as an IP next-hop by the edge routers to route the IP packets to the users connected to the NE. A single Virtual Router can be configured in this mode, which can co-exist in the same system with a number of VRs that are configured in IP-aware Bridge mode (see NTP 2106). At the user side of the system (xDSL line), unnumbered IP interfaces are used, while user subnets are configured on a user gateway interface. In order to achieve maximum efficiency in the allocation of IP addresses, several users (on different xDSL lines) can share a same subnet. Host routes toward the end-user devices are either dynamically created in the NE in case of dynamic DHCP sessions, or statically provisioned in case of static IP address assignment. Toward the network, IP interfaces are numbered (meaning that the NE IP addresses and subnets are configured).
Caution — The information in this procedure is kept for informational purposes only. The recommended way in which to configure an (enhanced) IP router is described in NTP 2133.
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 2107-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
NTP 2107 — Configure an IP router Figure NTP 2107-1: IP Router VLAN X
NE
Video VLAN
Internet Video
VLAN Y Video VLAN is always in iBridge
Virtual VLAN
Figure NTP 2107-2: IP Router: traffic flow Source MAC address = PC Destination MAC address = NE
NE
Source MAC address = NE Destination MAC address = Network
PC
Network
Source MAC address = Network Destination MAC address = NE Source MAC address = NE Destination MAC address = PC
Procedure Proceed as follows to configure an IP router:
NTP 2107-2
1
Create a router VRF; see DLP 2123.
2
Create a L2-terminated router VLAN; see DLP 2116.
3
Add users; see DLP 2125 for adding IPoA user or DLP 2126 for adding IPoE user.
4
STOP. This procedure is complete.
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
NTP 2108 — Configure services Purpose This procedure provides the steps to configure the following services on the NE:
• • • • • • • • • • • • • • •
xDSL profiles Quality of Service (QoS) Multicast Dynamic Host Configuration Protocol (DHCP) relay agent and Option 82 Authentication Point-to-Point Protocol (PPP) configuration NT redundancy Link aggregation Multiple Spanning Tree Protocol (MSTP) Routing protocols (optional) Integrated VoIP Service (MEGACO or SIP) Voice Session Initiation Protocol (SIP) Access Node Control Protocol (ANCP) session Path Connectivity Check Protection (optional) P-bit counter on a VLAN Port (optional)
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 2108-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
NTP 2108 — Configure services
Procedure To configure a service, you need to perform the following tasks: 1
Configure xDSL profiles: i
For the configuration of the service profiles and the spectrum profiles; see DLP 1129.
ii
For the configuration of custom PSD points; see DLP 1188.
iii
For the configuration of virtual noise values for VDSL2; see DLP 1189.
iv
For the configuration of a Downstream Power Back Off (DPBO) profile; see DLP 1206.
v
For the configuration of an RTX profile (standard ARQ provisioning); see DLP 1257
vi
For the configuration of a Vectoring Control Entity profile; see DLP 1291.
vii
For the configuration of an xDSL vectoring profile; see DLP 1295.
viii For System Level Vectoring (SLV), configuration of the mapping between the VP board and the SLV LT boards; see DLP 1294. For the configuration of power back-off; see DLP 1208.
x
For the configuration of xDSL overrule data; see DLP 1217.
xi
For the configuration of the impulse noise sensor on an xDSL line; see DLP 1215.
2
Configure xDSL bonding; see DLP 1130.
3
Configure general bridge parameters for LT and SHub; see DLP 2195.
4
If required, enable dual tagging on the SHub; see DLP 2191.
5
Configure QoS:
6
NTP 2108-2
ix
i
For the configuration of QoS; see DLP 1134.
ii
For the configuration of QoS on the SHub; see DLP 2199.
iii
For the configuration of QoS Threshold Crossing Alerts (TCA); see DLP 1202.
Configure multicast: i
For the configuration of the multicast service in the system; see DLP 2136.
ii
For the configuration of a multicast VLAN; see DLP 2137.
iii
For the configuration of a multicast channel; see DLP 2138.
iv
For the configuration of the multicast service on a user port; see DLP 2198.
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
NTP 2108 — Configure services
7
8
9
10
Configure DHCP Relay: i
For the configuration of the DHCP relay agent in iBridge mode; see DLP 2139.
ii
For the configuration of the DHCP relay agent in router mode; see DLP 2140.
iii
For the configuration of the DHCP relay agent in forwarder mode; see DLP 2141.
iv
For the configuration of DHCP MAC concentration in forwarder mode; see DLP 2185.
Configure the authentication settings: i
For the configuration of the security domain: see DLP 2142.
ii
For the configuration of RADIUS; see DLP 2144.
iii
For the configuration of 802.1x authentication; see DLP 1145.
iv
For the configuration of operator authentication via RADIUS; see DLP 2181.
Configure the PPP relay settings: i
For the configuration of PPPoE relay on the LT; see DLP 1146.
ii
For the configuration of PPPoX cross-connect; see DLP 1147.
If necessary, configure NT redundancy; see DLP 2114.
Note 1 — If NT redundancy is required, then this has to be specifically disabled enabled (this contrary to the earlier,
12
13
If necessary, configure link aggregation. Link aggregation is used to aggregate two or more physical links from one switch to another: i
For the configuration of link aggregation; see DLP 2105.
ii
For the configuration of link aggregation on the NELT-B; see DLP 1271
If necessary, configure Multiple Spanning Tree Protocol (MSTP): i
to configure MSTP on the SHub; see DLP 2200
ii
to configure MSPT on the NELT-B; see DLP 1270
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 2107.
ii
For the configuration of Routing Information Protocol (RIP) management; see DLP 2108.
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 2108-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
NTP 2108 — Configure services
14
Configure integrated VoIP service: i
For the configuration MEGACO-based VoIP service, see DLP 2216
ii
For the configuration of the SIP-based VoIP service, see DLP 2196
Note 1 — For POTS-only service: Either the MEGACO-based or the SIP-based VoIP service shall be configured. The system does not support both integrated VoIP services to run in parallel for the POTS only service.
Note 2 — For POTS + ISDN BRI service one of the following applies:
• •
only the MEGACO-based VoIP service is configured, supporting both the POTS and the ISDN BRI services simultaneously. the SIP-based VoIP Service is configured to support the POTS service and the MEGACO-based VoIP service is configured to support the ISDN BRI service. Only in this latter case does the system allow both integrated VoIP services to run in parallel.
15
Configure an ANCP session; see DLP 2186.
16
Configure the Path Connectivity Check Protection (PCCP) group; see DLP 2222.
Note — Only applicable when the MEGACO-based VoIP service is configured.
NTP 2108-4
17
Configure the p-bit counter on a VLAN port; see DLP 1225.
18
If required, configure fairness SLA on the NELT-B; see DLP 1282.
19
STOP. This procedure is complete.
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
NTP 2115 — Monitor alarms Purpose This procedure provides the steps to monitor the alarms on the NE.
Procedure Proceed as follows to monitor the alarms: 1
Create an alarm snapshot table; see DLP 2154.
2
Monitor the alarms; see DLP 2155.
3
STOP. This procedure is complete.
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 2115-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
NTP 2115 — Monitor alarms
NTP 2115-2
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
NTP 2116 — Perform software management Purpose This procedure provides the steps to perform software management on the NE.
Procedure The following steps can be used to perform software management: 1
Management of the NT and SHub database; see RTP 2100.
2
Management of the Overall Software Packages; see DLP 1159.
3
View the version of the SHub software; see DLP 2160.
4
Management of Customer Dependant Engineering (CDE) profiles; see DLP 1220.
5
STOP. This procedure is complete.
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 2116-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
NTP 2116 — Perform software management
NTP 2116-2
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
NTP 2117 — Modify system parameters Purpose This procedure lists the procedures for system parameter modification.
Procedure The steps below show the procedures for modifying different system parameters: 1
Modify the system management IP parameters; see DLP 2168.
2
Change the external management VLAN; see DLP 2162.
3
Configure an ARP table entry; see DLP 2150.
4
Configure filtering on the SHub; see DLP 2132.
5
Configure static MAC addresses; see DLP 2180.
6
STOP. This procedure is complete.
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 2117-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
NTP 2117 — Modify system parameters
NTP 2117-2
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
NTP 2120 — Troubleshooting the network Purpose The following troubleshooting commands can be used:
•
•
Ping: The ping command lets you verify that a particular IP address exists and can accept requests. Ping is used diagnostically to ensure that a host computer you are trying to reach is actually operating. Ping can also be used with a host that is operating to see how long it takes to get a response back. Traceroute: Traceroute is a utility that traces the route in the network for an IP address. It also calculates and displays the amount of time each hop took. The utility initiates the sending of a packet (using the Internet Control Message Protocol (ICMP)), including in the packet a Time To Live (TTL) value that is designed to be exceeded by the first router that receives it, which will return a Time Exceeded message. This enables traceroute to determine the time required for the hop to the first router. Increasing the time limit value, it sends the packet again so that it will reach the second router in the path to the destination, which returns another Time Exceeded message, and so forth. Traceroute determines when the packet has reached the destination by including a port number that is outside the normal range. When it's received, a Port Unreachable message is returned, enabling traceroute to measure the time length of the final hop. As the tracerouting progresses, the records are displayed for you hop by hop.
Procedure The following troubleshooting commands can be used: 1
Ping command; see DLP 2164.
2
Traceroute command; see DLP 2165.
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 2120-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
NTP 2120 — Troubleshooting the network
NTP 2120-2
3
Port mirroring; see DLP 2223.
4
STOP. This procedure is complete.
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
NTP 2121 — Manage an SNMP proxy CPE Purpose The Customer Premises Equipment (CPE) management functionality allows the operator to troubleshoot the CPE at all protocol layers when problems are experienced with either misconfiguration of the CPE or with the end-user's terminals. It allows to have a clear indication if a problem is situated before or after the demarcation point of a telecom carrier’s responsibility. Additionally, CPE management offers the possibility to control the SW upgrade of CPE by downloading from the network. The function of xDSL CPE remote management includes configuration, monitoring, maintenance and upgrade of an xDSL Remote Terminal. The network reference model is illustrated in Figure NTP 2121-1. Figure NTP 2121-1: Network Reference Model Network Management Entity
CPE-MM
RMI
User Management Entity
LMI NE
xDSL CPE
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 2121-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
NTP 2121 — Manage an SNMP proxy CPE
The CPE-MM is responsible for the management of CPE. The following interfaces are defined:
• •
LMI: interface between NE and CPE RMI: interface between CPE-MM and NE
Three channels are present on the LMI interface:
• • •
Service data channel: This channel is used to carry data traffic (for example, HSI traffic). Basic management channel: This channel is used to carry CPE remote management information. Auxiliary management channel: This channel is used to carry SW download, PPPoE testing, PING testing, bandwidth testing and so on.
The NE relays the SNMP messages between CPE-MM and CPE.
Note — This NTP is for CPE management using SNMP.
Procedure To configure SNMP proxy CPE management, you need to perform the following tasks:
NTP 2121-2
1
Configure SNMP proxy CPE management; see DLP 2166.
2
STOP. This procedure is complete.
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
NTP 2122 — Cluster management Purpose As a result of the massive deployment of xDSL, many more DSLAMs are provisioned in the network. They are mostly managed separately, which makes the management workload heavy and complicated. To simplify the management workload of the operator, cluster management groups multiple DSLAMs as one logical management domain. The logical management domain of a cluster is formed by a physically interconnected group of DSLAMs. The operator can organize its clusters according to, for example, physical location. Topology display will present the connectivity and status of DSLAMs in a connected environment, possibly over more than one cluster. Moreover, separately managed DSLAMs use more public IP addresses, which are limited. Figure NTP 2122-1 shows an example of the cluster management topology. Figure NTP 2122-1: Cluster Management Topology
Cluster No. 2 (A logical DSLAM)
Management Command to Cluster 2
EMS (AMS)
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
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 2122-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
NTP 2122 — Cluster management
Procedure To configure cluster management, you need to perform the following tasks:
NTP 2122-2
1
Configure the cluster; see DLP 2169.
2
STOP. This procedure is complete.
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
NTP 2129 — Configure a loopback interface on the SHub Purpose Configure a loopback interface on the SHub.
Prerequisites The following prerequisite must be fulfilled:
•
The system must run in single ip-address mode.
Procedure To configure a loopback interface on the Shub, you need to perform the following tasks: 1
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 2204.
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
STOP. This procedure is complete.
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 2129-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
NTP 2129 — Configure a loopback interface on the SHub
NTP 2129-2
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
NTP 2133 — Configure an enhanced IP router Purpose The enhanced IP router has the following adavantages as opposed to the IP router (see NTP 2107):
• • • •
Subnet and IP next hop support at subscriber side IP routing support for L3 and L2+ boards Easy migration from L2 to L3 model (that is, only the NT configuration needs to be changed to get IP routing without impacting the LT provisioning) IP option support for subscriber
Procedure Proceed as follows to configure an enhanced IP router: 1
Create a router VRF; see DLP 2123.
Note — Only step 2 of this DLP must be executed.
2
Create an xDSL Ethernet user and add this user to a VLAN on the LT; see DLP 1124.
3
STOP. This procedure is complete.
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 NTP 2133-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
NTP 2133 — Configure an enhanced IP router
NTP 2133-2
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
Detailed Level Procedures (DLP)
DLP 1100 — Set up a local CLI session or a local TL1 session DLP 1112 — Lock and unlock equipment DLP 1113 — Configure the equipment DLP 1117 — Configure a VLAN on the LT for C-VLAN cross-connect DLP 1118 — Configure a VLAN on the LT for S-VLAN cross-connect DLP 1119 — Configure a VLAN on the LT for S+C-VLAN cross-connect DLP 1120 — Configure a VLAN on the LT for C-iBridge DLP 1124 — Create an xDSL/native Ethernet user and add this user to a VLAN on the LT DLP 1129 — Create xDSL profiles DLP 1130 — Configure xDSL bonding DLP 1134 — Configure QoS DLP 1145 — Configure 802.1x DLP 1146 — Configure PPPoE relay on LT DLP 1147 — Configure PPPoX cross-connect DLP 1151 — Shut down and restart the NT DLP 1152 — Reboot the system
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
DLP 1153 — Shut down and restart individual equipment DLP 1159 — Manage OSWP DLP 1163 — Modifying xDSL profiles DLP 1170 — Configure SSH and SFTP DLP 1173 — Switch a user from ADSL to VDSL DLP 1174 — Create an xDSL IPoA user and add this user to a VLAN on the LT for C-VLAN cross-connect DLP 1182 — Configure SHDSL DLP 1183 — Configure IMA on SHDSL spans DLP 1187 — Configure global VLAN parameters on the LT DLP 1188 — Configure custom PSD points DLP 1189 — Configure VDSL2 virtual noise values DLP 1190 — Configure threshold crossing alerts DLP 1197 — View port configuration and operational data on LT DLP 1201 — Configure protocol tracing DLP 1202 — Configure QoS threshold crossing alerts DLP 1203 — Configure general security settings DLP 1205 — Configure Link Related Ethernet OAM DLP 1206 — Configure an xDSL DPBO profile DLP 1207 — Modify an xDSL DPBO profile DLP 1208 — Configure xDSL power back off DLP 1212 — Create an IP user/subnet DLP 1215 — Configure the impulse noise sensor on an xDSL line DLP 1217 — Configure the xDSL overrule data DLP 1219 — Forced NT switchover DLP 1220 — Manage the CDE profile DLP 1221 — Manage troubleshooting counters on LT DLP 1225 — Configure the p-bit counter on a VLAN port December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
DLP 1232 — Create an xDSL IPoA user and add this user to a VLAN on the LT for iBridge DLP 1253 — Configure the third-party equipment management port on the 7356 FD REM DLP 1255 — Configure a port on the NELT-B LT DLP 1257 — Configure a line with an xDSL RTX profile DLP 1258 — Modify an xDSL RTX profile DLP 1270 — Configure spanning tree on the NELT-B LT DLP 1271 — Configure link aggregation on the NELT-B LT DLP 1282 — Configure the fairness SLA on the NELT-B LT DLP 1283 — Troubleshooting congestion on the NELT-B LT DLP 1291 — Configure a Vectoring Control Entity profile and associate it to a board DLP 1292 — Modify a Vectoring Control Entity profile DLP 1293 — Delete a Vectoring Control Entity profile DLP 1294 — Configure or modify the mapping between the VP board and the SLV LT boards DLP 1295 — Configure a line with an xDSL vectoring profile DLP 1296 — Modify an xDSL vectoring profile DLP 1297 — Delete an xDSL vectoring profile DLP 1298 — Monitor xDSL vectoring lines DLP 2101 — Create operator profiles and instances DLP 2103 — Configure system parameters DLP 2105 — Configure link aggregation usage DLP 2107 — Manage OSPF DLP 2108 — Configure RIP DLP 2109 — Configure SNMP and trap management DLP 2110 — Manage alarms DLP 2111 — Plan, replan, and unplan equipment
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
DLP 2114 — Configure NT redundancy DLP 2115 — Create a L2-terminated forwarder VLAN DLP 2116 — Create a L2-terminated router VLAN DLP 2121 — Add a network/LAG port to a VLAN in the SHub DLP 2122 — Create a forwarding VRF DLP 2123 — Create a router VRF DLP 2125 — Create an IPoA user DLP 2126 — Create an IPoE user DLP 2128 — Add an LT port to a VLAN on the SHub DLP 2132 — Configure filtering on the NT DLP 2136 — Configure the multicast service in the system DLP 2137 — Configure a multicast VLAN DLP 2138 — Configure a multicast channel DLP 2139 — Configure DHCP relay agent in iBridge mode DLP 2140 — Configure DHCP relay agent in router mode DLP 2141 — Configure DHCP relay agent in forwarder mode DLP 2142 — Configure the system security domain DLP 2144 — Configure RADIUS DLP 2150 — Configure ARP table entry DLP 2154 — Create a snapshot alarm table DLP 2155 — Monitor alarms DLP 2157 — Manage the SHub database DLP 2160 — View version of the SHub software DLP 2162 — Modify the external management VLAN DLP 2164 — Ping another host DLP 2165 — Perform a traceroute action DLP 2166 — Configure SNMP proxy CPE management
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
DLP 2167 — Script files DLP 2168 — Modify the system management IP parameters DLP 2169 — Configure cluster management DLP 2171 — Enable EMS management DLP 2172 — Create a default operator profile DLP 2175 — Configure system management IP parameters DLP 2176 — Performance monitoring commands DLP 2177 — Configure SFP downlink ports DLP 2179 — Configure system logging DLP 2180 — Configure static MAC addresses DLP 2181 — Configure operator authentication via RADIUS DLP 2185 — Configure DHCP MAC concentration in forwarder mode DLP 2186 — Configure ANCP session DLP 2191 — Enable dual tagging in the SHub DLP 2195 — Configure general bridge parameters on the LT DLP 2196 — Configure Voice SIP DLP 2198 — Configure the multicast service on a user port DLP 2199 — Configure QoS on the SHub DLP 2200 — Configure Spanning Tree on the SHub DLP 2204 — Configure an unnumbered IP interface on the SHub DLP 2209 — Configure vMAC DLP 2210 — View the status of various system parameters DLP 2211 — Configure SFP uplink ports DLP 2213 — Enable OAM counters DLP 2214 — Configure connectivity fault management DLP 2216 — Configure Voice MEGACO DLP 2222 — Create the PCCP group
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
DLP 2223 — Configure SHub port mirroring DLP 2224 — Change shelf mode DLP 2236 — Configure the enhanced system clock synchronization DLP 2273 — External Packet Forwarding
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
Detailed Level Procedures (DLP)
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
-7
Detailed Level Procedures (DLP)
-8
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
Detailed Level Procedures (DLP)
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
-9
Detailed Level Procedures (DLP)
-10
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
DLP 1100 — Set up a local CLI session or a local TL1 session Purpose This procedure provides the steps to set up a local CLI session or a local TL1 session with the ISAM via the local craft connection.
Note — For security purposes, it is advised to change the default user name and password both for CLI sessions and for TL1 sessions when you log in for the first time.
Procedure Proceed as follows to set up a local CLI session or a local TL1 session: 1
Enter LOGIN to start up the command line interface. The logon prompt appears.
2
After the question “Would you like a CLI(C) or a TL1 login(T) or TL1 normal session(N)? [N]:”, type C and press Enter.
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 1100-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
DLP 1100 — Set up a local CLI session or a local TL1 session
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 — For remote CLI, after you set up the management channel, you can set up a remote CLI session using Telnet.
Warning — After three unsuccessful login attempts (that is, each consisting of three failed username/password prompts), the ISAM will block all login attempts from the IP address or from the craft port from which the three unsuccessful login attempts were initiated for a period of two minutes. If the user fails to successfully log in after this timeout has expired, the ISAM extends the blocking period with two minutes and will continue to extend this blocking period with two minutes for each failed login attempt. 4
Log out.
5
Enter LOGIN to start up the command line interface. The logon prompt appears.
DLP 1100-2
6
After the question “Would you like a CLI(C) or a TL1 login(T) or TL1 normal session(N)? [N]:”, type T or N and press Enter.
7
Enter the default user name (SUPERUSER) and password (ANS#150) that were provided to you with the system. If you do not have the default user name and password, contact Alcatel-Lucent technical support.
8
STOP. This procedure is complete.
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
DLP 1112 — Lock and unlock equipment Purpose This procedure provides the steps to lock and unlock plug-in units.
Procedure Proceed as follows to lock and unlock a plug-in unit: 1
Lock a plug-in unit with the following command: configure equipment slot (index) no unlock
2
Unlock a plug-in unit with the following command: configure equipment slot (index) unlock
3
STOP. This procedure is complete.
Configuration example (Config#1): configure equipment slot lt:1/1/5 no unlock configure equipment slot lt:1/1/5 unlock
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 1112-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
DLP 1112 — Lock and unlock equipment
DLP 1112-2
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
DLP 1113 — Configure the equipment Purpose The system will auto-configure a number of equipment items and detect the presence of the equipment at startup. It may therefore not be necessary to configure or reconfigure all equipment. The procedure in this section is a guideline only. Refer to the CLI Command Guide for FD 24Gbps NTdocument for a complete description of the commands used in this procedure.
Procedure Proceed as follows to configure the NE equipment: 1
Configure the description of the system with the following command: configure equipment isam (no) description
2
Configure the rack with the following command: configure equipment rack (index) (no) description
3
Configure the subrack or shelf with the following command: configure equipment shelf (index) class (no) planned-type (no) lock (no) mode (no) description
4
Enable or disable environment monitoring with the following command: configure equipment envbox (no) enable-supervise
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 1113-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
DLP 1113 — Configure the equipment
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
STOP. This procedure is complete.
Configuration example (Config#1): configure equipment isam description “Magabir Plant” configure equipment rack 1 description “***Main Rack***” configure equipment shelf 1/1 description Testshelf_Antwerp configure equipment envbox enable-supervise show equipment rack 1 detail show equipment shelf 1/1 detail show equipment slot lt:1/1/5 detail show equipment applique iont:1/1 detail
DLP 1113-2
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
DLP 1117 — Configure a VLAN on the LT for C-VLAN cross-connect Purpose This procedure provides the steps to configure a VLAN on the LT for C-VLAN cross-connect. This is the most straightforward VLAN cross-connect model where a single VLAN ID at the EMAN side is associated with a given PVC at the user side. Any kind of traffic issued by the subscriber is passed transparently towards the network using the selected VLAN ID.
Note — The operator does not have to identify any specific LT; the ISAM will find out the correct LT when the operator adds the (single) subscriber on the C-VLAN cross-connect.
Figure DLP 1117-1: Configure a VLAN on the LT for C-VLAN cross-connect DLP
C-VLAN CC LT
NT
ISAM
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 1117-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
DLP 1117 — Configure a VLAN on the LT for C-VLAN cross-connect
Procedure Proceed as follows to configure a VLAN on the LT for C-VLAN cross-connect: 1
Create a C-VLAN on the LT with the following command: configure vlan id (no) name mode cross-connect (no) priority (no) broadcast-frames (no) protocol-filter (no) pppoe-relay-tag (no) secure-forwarding (no) aging-time
2
If required, modify the C-VLAN on the LT with the following command: configure vlan id (vlanid) (no) name mode (no) priority (no) vmac-translation (no) vmac-dnstr-filter (no) vmac-not-in-opt61 (no) broadcast-frames (no) protocol-filter (no) pppoe-relay-tag (no) dhcp-opt-82 (no) circuit-id-dhcp (no) remote-id-dhcp (no) dhcp-linerate (no) pppoe-linerate (no) dhcpv6-linerate (no) circuit-id-pppoe (no) remote-id-pppoe (no) secure-forwarding (no) aging-time (no) l2cp-transparent (no) in-qos-prof-name (no) ipv4-mcast-ctrl (no) ipv6-mcast-ctrl (no) mac-mcast-ctrl (no) dis-proto-rip (no) proto-ntp (no) dhcpv6-itf-id (no) dhcpv6-remote-id (no) dhcpv6-trst-port (no) enterprise-number (no) icmpv6-sec-fltr (no) dis-ip-antispoof (no) unknown-unicast
3
DLP 1117-2
STOP. This procedure is complete.
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
DLP 1117 — Configure a VLAN on the LT for C-VLAN cross-connect
Configuration example (Config#1): configure vlan id 301 name "ISP_C_VLAN_301" mode cross-connect configure vlan id 301 dhcp-opt-82 circuit-id-dhcp physical-id remote-id-dhcp customer-id configure vlan id 300 name "ISP_C_VLAN_300" mode cross-connect configure vlan id 300 dhcp-opt-82 circuit-id-dhcp physical-id remote-id-dhcp customer-id configure vlan id 298 name "ISP_C_VLAN_298" mode cross-connect configure vlan id 298 dhcp-opt-82 circuit-id-dhcp physical-id remote-id-dhcp customer-id configure vlan id 299 name "ISP_C_VLAN_299" mode cross-connect configure vlan id 299 dhcp-opt-82 circuit-id-dhcp physical-id remote-id-dhcp customer-id
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 1117-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
DLP 1117 — Configure a VLAN on the LT for C-VLAN cross-connect
DLP 1117-4
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
DLP 1118 — Configure a VLAN on the LT for S-VLAN cross-connect Purpose This procedure provides the steps to configure a VLAN on the LT for S-VLAN cross-connect. In this mode, the Service Provider VLAN (S-VLAN) ID at the EMAN side is associated with a single subscriber interface at the user side. The C-VLANs carried within the S-VLAN are passed transparently to the end user. This allows the end user to specify its own end-to-end connectivity, while remaining transparent for the EMAN. Forwarding is only done based on the S-VLAN forwarding context. The forwarding is transparent for the C-VLANs. Frames on the subscriber interface may or may not have an S-VLAN tag. In case of an absent S-VLAN tag (that is for C-VLAN tagged and untagged/priority tagged frames), the subscriber interface’s pre-configured S-VLAN ID will be assigned.
Note — The operator does not have to identify any specific LT; the ISAM will find out the correct LT when the operator adds the (single) subscriber on the C-VLAN cross-connect.
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 1118-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
DLP 1118 — Configure a VLAN on the LT for S-VLAN cross-connect Figure DLP 1118-1: Configure a VLAN on the LT for S-VLAN cross-connect DLP
S-VLAN CC LT
NT
ISAM
Procedure Proceed as follows to configure a VLAN on the LT for S-VLAN cross-connect: 1
Create an S-VLAN on the LT with the following command: configure vlan id stacked:: name mode cross-connect (no) priority (no) broadcast-frames (no) protocol-filter (no) pppoe-relay-tag
2
If required, configure the S-VLAN on the LT with the following command: configure vlan id (vlanid) (no) name mode (no) priority (no) vmac-translation (no) vmac-dnstr-filter (no) vmac-not-in-opt61 (no) broadcast-frames (no) protocol-filter (no) pppoe-relay-tag (no) dhcp-opt-82 (no) circuit-id-dhcp (no) remote-id-dhcp (no) dhcp-linerate (no) pppoe-linerate (no) dhcpv6-linerate (no) circuit-id-pppoe (no) remote-id-pppoe (no) secure-forwarding (no) aging-time (no) l2cp-transparent (no) in-qos-prof-name (no) ipv4-mcast-ctrl
DLP 1118-2
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
DLP 1118 — Configure a VLAN on the LT for S-VLAN cross-connect
(no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no)
3
ipv6-mcast-ctrl mac-mcast-ctrl dis-proto-rip proto-ntp dhcpv6-itf-id dhcpv6-remote-id dhcpv6-trst-port enterprise-number icmpv6-sec-fltr dis-ip-antispoof unknown-unicast
STOP. This procedure is complete.
Configuration example (Config#1): configure vlan id stacked:400:0 name “IPS_S_VLAN-400” mode cross-connect
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 1118-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
DLP 1118 — Configure a VLAN on the LT for S-VLAN cross-connect
DLP 1118-4
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
DLP 1119 — Configure a VLAN on the LT for S+C-VLAN cross-connect Purpose This procedure provides the steps to configure a VLAN on the LT for S+C-VLAN crossconnect The basic VLAN cross-connect mode suffers from the fact the that number of VLAN identifiers is limited to 4K. Since the VLAN is a EMAN wide identifier, one ends up with a scalability issue: there cannot be more than 4K end users connected to the whole EMAN. To solve this issue, two VLANs are stacked and the cross-connection is then performed on the combination (S-VLAN, C-VLAN) allowing to theoretically reach up to 16M end users. Frames on the subscriber interface may be C-VLAN tagged or untagged/priority tagged. In case of C-VLAN tagged frames, a check will be performed on the received C-VLAN ID, while the subscriber 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.
Note — The operator does not have to identify any specific LT; the ISAM will find out the correct LT when the operator adds the (single) subscriber on the S+C-VLAN cross-connect
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 1119-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
DLP 1119 — Configure a VLAN on the LT for S+C-VLAN cross-connect Figure DLP 1119-1: Configure a VLAN on the LT for S+C-VLAN cross-connect DLP
S+C-VLAN CCs
LT NT
ISAM
Procedure Proceed as follows to configure a VLAN on the LT for S+C-VLAN cross-connect: 1
Create an S-VLAN on the LT with the following command: configure vlan id stacked:: name mode layer2-terminated (no) priority (no) broadcast-frames (no) protocol-filter (no) pppoe-relay-tag (no) secure-forwarding (no) aging-time (no) in-qos-prof-name (no) ipv4-mcast-ctrl (no) ipv6-mcast-ctrl (no) mac-mcast-ctrl (no) proto-ctrl-flags
2
Create a stacked S+C-VLAN on the LT with the following command: configure vlan id stacked:: name mode cross-connect (no) priority (no) broadcast-frames (no) protocol-filter
3
If required, configure the S+C-VLAN on the LT with the following command: configure vlan id (vlanid) (no) name mode (no) priority (no) vmac-translation
DLP 1119-2
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
DLP 1119 — Configure a VLAN on the LT for S+C-VLAN cross-connect
(no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no)
4
vmac-dnstr-filter vmac-not-in-opt61 broadcast-frames protocol-filter pppoe-relay-tag dhcp-opt-82 circuit-id-dhcp remote-id-dhcp dhcp-linerate pppoe-linerate dhcpv6-linerate circuit-id-pppoe remote-id-pppoe secure-forwarding aging-time l2cp-transparent in-qos-prof-name ipv4-mcast-ctrl ipv6-mcast-ctrl mac-mcast-ctrl dis-proto-rip proto-ntp dhcpv6-itf-id dhcpv6-remote-id dhcpv6-trst-port enterprise-number icmpv6-sec-fltr dis-ip-antispoof unknown-unicast
STOP. This procedure is complete.
Configuration example (Config#1): configure vlan id stacked:500:0 name “ISP_SC_VLAN-500” mode layer2-terminated configure vlan id stacked:500:600 name “ISP_SC_VLAN-500-600” mode cross-connect
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 1119-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
DLP 1119 — Configure a VLAN on the LT for S+C-VLAN cross-connect
DLP 1119-4
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
DLP 1120 — Configure a VLAN on the LT for C-iBridge Purpose This procedure provides the steps to configure a VLAN on the LT for C-iBridge. The concept of a VLAN in intelligent bridging (iBridge) mode is that multiple NSPs are each connected to the NE with a VLAN. The user ports are connected to the VLAN of their corresponding NSP.
Note — The operator does not have to identify any specific LT; the ISAM will automatically configure the iBridge VLAN on all LTs.
Figure DLP 1120-1: Configure a VLAN on the LT for C-iBridge DLP
C-VLAN iBridge LT
NT
ISAM
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 1120-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
DLP 1120 — Configure a VLAN on the LT for C-iBridge
Procedure Proceed as follows to create a C-VLAN iBridge on the LT: 1
Create an C-VLAN iBridge on the LT with the following command: configure vlan id (no) name mode residential-bridge (no) priority (no) broadcast-frames (no) protocol-filter (no) pppoe-relay-tag (no) secure-forwarding (no) aging-time
2
If required, configure the C-VLAN iBridge with the following command: configure vlan id (vlanid) (no) name mode (no) priority (no) vmac-translation (no) vmac-dnstr-filter (no) vmac-not-in-opt61 (no) broadcast-frames (no) protocol-filter (no) pppoe-relay-tag (no) dhcp-opt-82 (no) remote-id (no) remote-id-dhcp (no) dhcp-linerate (no) pppoe-linerate (no) dhcpv6-linerate (no) circuit-id-pppoe (no) remote-id-pppoe (no) secure-forwarding (no) aging-time (no) l2cp-transparent (no) dhcpv6-itf-id (no) dhcpv6-remote-id (no) dhcpv6-trst-port (no) enterprise-number (no) icmpv6-sec-fltr (no) (no) ipv4-mcast-ctrl (no) ipv6-mcast-ctrl (no) mac-mcast-ctrl (no) dis-proto-rip (no) proto-ntp (no) dis-ip-antispoof (no) unknown-unicast
3
DLP 1120-2
STOP. This procedure is complete.
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
DLP 1120 — Configure a VLAN on the LT for C-iBridge
Configuration examples (Config#1): configure vlan id 100 name “iBridge-vlan” mode residential-bridge configure vlan id 100 dhcp-opt-82 circuit-id-dhcp physical-id remote-id-dhcp customer-id secure-forwarding configure vlan id 200 name “Multicast-vlan” mode residential-bridge
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 1120-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
DLP 1120 — Configure a VLAN on the LT for C-iBridge
DLP 1120-4
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
DLP 1124 — Create an xDSL/native Ethernet user and add this user to a VLAN on the LT Purpose This procedure provides the steps to create an xDSL Ethernet user and add this user to a VLAN on the LT.
Note 1 — From R3.3 on, the user line interface stack (that is, ATM PVC and bridge ports) can be configured before the xDSL line is provisioned (that is, before an xDSL profile is assigned to an xDSL line). Also, when an xDSL line is unprovisioned (that is, when the association between the xDSL line and an xDSL profile is deleted), the user line interface stack (ATM PVCs and bridge ports) is preserved.
Note 2 — This entails that, when a clean up of the whole interface stack is required, all the ATM PVCs and bridge ports need to be deleted explicitly.
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 1124-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
DLP 1124 — Create an xDSL/native Ethernet user and add this user to a VLAN on the LT Figure DLP 1124-1: Create an xDSL/native Ethernet user and add this user to a VLAN on the LT VlanPort BridgePort ATM PVC xDSL
DLP
PVID VLAN LT NT
ISAM
Prerequisites The following prerequisites must be fulfilled before an xDSL Ethernet user can be created:
• • •
The LT must be planned; see DLP 2111. The xDSL profiles must have been created; see DLP 1129. A VLAN must have been created: • for creation of a C-VLAN cross-connect; see DLP 1117 • for creation of a S-VLAN cross-connect; see DLP 1118 • for creation of a S+C-VLAN cross-connect; see DLP 1119 • for creation of an iBridge; see DLP 1120.
Procedure Proceed as follows to create an xDSL Ethernet user: 1
2
Do one of the following: a
For a user on an ADSL line, VDSL2 line, go to step 2
b
For a native Ethernet user, continue with step 7.
Create an xDSL line with the following command: configure xdsl line (if-index) service-profile none | | name: spectrum-profile none | | name: (no) dpbo-profile (no) ansi-t1413 (no) etsi-dts
DLP 1124-2
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
DLP 1124 — Create an xDSL/native Ethernet user and add this user to a VLAN on the LT
(no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no)
3
g992-1-a g992-1-b g992-2-a g992-3-a g992-3-b g992-3-l1 g992-3-l2 g992-3-aj g992-3-am g992-5-a g992-5-b ansi-t1.424 etsi-ts itu-g993-1 ieee-802.3ah g992-5-aj g992-5-am g993-2-8a g993-2-8b g993-2-8c g993-2-8d g993-2-12a g993-2-12b g993-2-17a g993-2-30a carrier-data-mode admin-status transfer-mode
Configure the xDSL interface with the following command: configure interface port xdsl line:/// admin-up (no) link-state-trap (no) user (no) severity
4
5
Do one of the following: a
For a user on an ADSL line, continue with step 5
b
For a user on a VDSL or VDSL2 line, continue with step 8.
Create an ATM PVC (or the necessary ATM PVCs) with the following command: configure atm pvc (port-index) (no) admin-down (no) aal5-encap-type llc-snap | llc-snap-routed | llc-nlpid | vc-mux-bridged-8023 | vc-mux-routed | vc-mux-pppoa | automatic:ip | automatic:ppp | automatic:pppoa | automatic: ipoe-ppp
6
Go to step 8.
7
For configuration of a native Ethernet user, see DLP 1255.
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 1124-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
DLP 1124 — Create an xDSL/native Ethernet user and add this user to a VLAN on the LT
8
On top of the PVC / EFM / EthPhy, create a bridge port with the following command: configure bridge port (port) (no) default-priority (no) qos-profile (no) prio-regen-prof (no) max-committed-mac (no) mirror-mode (no) mirror-vlan
9
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
10
Set the PVID with the following command: configure bridge port (port) pvid (vlan-id)
Note — When it needs to be possible to receive single tagged frames at the user side (S-VLAN cross-connect), a specific C-VLAN ID must be used, namely 4097. The command is then: configure bridge port (port) pvid stacked::4097
11
STOP. This procedure is complete.
Configuration examples (Config#1):
DLP 1124-4
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
DLP 1124 — Create an xDSL/native Ethernet user and add this user to a VLAN on the LT
Configuration example for an ADSL user (Config#1): configure xdsl line 1/1/5/12 service-profile 7 spectrum-profile 5 transfer-mode atm admin-up configure atm pvc 1/1/5/12:8:35 aal5-encap-type vc-mux-bridged-8023 configure bridge port 1/1/5/12:8:35 no mac-learn-off configure bridge port 1/1/5/12:8:35 vlan-id 299 configure bridge port 1/1/5/12:8:35 pvid 299
Configuration example for a VDSL or VDSL2 user (Config#1): configure xdsl line 1/1/4/12 service-profile 8 spectrum-profile 4 admin-up configure bridge port 1/1/4/12 configure bridge port 1/1/4/12 vlan-id 300 configure bridge port 1/1/4/12 pvid 300 Configuration example Board Level Vectoring (Config#1): configure xdsl line 1/1/15/[1..48] service-profile 8 spectrum-profile 4 admin-up configure bridge port 1/1/15/1 configure bridge port 1/1/15/1 vlan-id 500 configure bridge port 1/1/15/1 pvid 500 Configuration example System Level Vectoring (Config#1): configure xdsl line 1/1/17/[1…48] spectrum-profile 4 service-profile 8 admin-up configure xdsl line 1/1/18/[1…48] spectrum-profile 4 service-profile 8 admin-up configure bridge port 1/1/17/1 configure bridge port 1/1/17/1 vlan-id 501 configure bridge port 1/1/17/1 pvid 501
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 1124-5 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
DLP 1124 — Create an xDSL/native Ethernet user and add this user to a VLAN on the LT
DLP 1124-6
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
DLP 1129 — Create xDSL profiles Purpose This procedure provides the steps to create xDSL profiles.
General Before you can create an xDSL line, you need to create the necessary profiles. Table DLP 1129-1 describes the two types of profiles. Table DLP 1129-1: xDSL profiles Profile
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 FD 24Gbps NT for more information on power management mode, SRA, and so on.
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 1129-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
DLP 1129 — Create xDSL profiles
See TNG 1107 for a full description of the multi-ADSL related parameters and the VDSL related parameters.
Procedure Proceed as follows to create an xDSL profile: 1
Create an xDSL service profile with the following command: configure xdsl service-profile (index) name 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 2136.
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 1163). 3
Create an xDSL spectrum profile and configure the parameters common to all the DSL flavors with the following command: configure xdsl spectrum-profile (index) name local-profile version (no) dis-ansi-t1413 (no) dis-etsi-dts (no) dis-g992-1-a
DLP 1129-2
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
DLP 1129 — Create xDSL profiles
(no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no)
4
dis-g992-1-b dis-g992-2-a dis-g992-3-a dis-g992-3-b g992-3-l1 g992-3-l2 g992-3-aj g992-3-am g992-5-a g992-5-b ansi-t1.424 dis-etsi-ts itu-g993-1 ieee-802.3ah g992-5-aj g992-5-am g993-2-8a g993-2-8b g993-2-8c g993-2-8d g993-2-12a g993-2-12b g993-2-17a g993-2-30a min-noise-down 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 modification 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
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
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 1129-3 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
DLP 1129 — Create xDSL profiles
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) propr-feat-value (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-mask-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) propr-feat-value (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 (no) psd-mask-up
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) propr-feat-value (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
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) propr-feat-value (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) pbo-mode
DLP 1129-4
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
DLP 1129 — Create xDSL profiles
(no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no) (no)
9
rx-psd-shape-up ghstones-pwr-mode max-band max-freq m-psd-level-down m-psd-level-up psd-pbo-par-a-up psd-pbo-par-b-up cust-psd-sc-down cust-psd-ty-down cust-rx-psd-sc-up cust-rx-psd-ty-up opt-startfreq
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) propr-feat-value (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 (no) cust-psd-sc-down (no) cust-psd-ty-down (no) cust-psd-sc-up (no) cust-psd-ty-up (no) cust-rx-psd-sc-up (no) cust-rx-psd-ty-up
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 1129-5 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
DLP 1129 — Create xDSL profiles
11
Activate an xDSL spectrum profile with the following command: configure xdsl spectrum-profile (index) active
12
STOP. This procedure is complete.
Configuration example (Config#1): configure xdsl service-profile 7 name ADSL_profile version 1 configure xdsl service-profile 7 active configure xdsl service-profile 8 name VDSL_profile version 1 min-bitrate-down 25000 min-bitrate-up 25000 plan-bitrate-down 40000 plan-bitrate-up 27000 max-bitrate-down 262143 max-bitrate-up 262143 configure xdsl service-profile 8 active configure xdsl service-profile 10 name XSRVC_0_0 version 1 min-l2-br-down 0 configure xdsl service-profile 10 ra-mode-up automatic min-bitrate-up 0 plan-bitrate-up 0 max-bitrate-up 0 max-delay-up 16 imp-noise-prot-up 0 no inp-wo-erasure-up configure xdsl service-profile 10 ra-mode-down automatic min-bitrate-down 0 plan-bitrate-down 0 max-bitrate-down 0 max-delay-down 16 imp-noise-prot-dn 0 no inp-wo-erasure-dn configure xdsl service-profile 10 active configure xdsl spectrum-profile 4 name vdsl_profile version 1 configure xdsl spectrum-profile 4 dis-ansi-t1413 dis-etsi-dts dis-g992-1-a dis-g992-1-b dis-g992-2-a dis-g992-3-a dis-g992-3-b dis-etsi-ts g993-2-8a g993-2-8b g993-2-8c g993-2-8d g993-2-12a g993-2-12b g993-2-17a g993-2-30a configure xdsl spectrum-profile 4 active configure xdsl spectrum-profile 5 name adsl_profile version 1 configure xdsl spectrum-profile 5 active configure xdsl spectrum-profile 22 name "approved-profile" configure xdsl spectrum-profile 22 active
DLP 1129-6
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
DLP 1130 — Configure xDSL bonding Purpose xDSL bonding allows traffic to be carried to and from a single logical subscriber interface over multiple physical xDSL lines.
Note — xDSL is ADSL or VDSL.
This procedure provides the steps to configure xDSL bonding.
Bonding services It offers the following services:
• • •
Extended reach of xDSL service Provisioning of standard xDSL services to subscribers that cannot receive these services over a single xDSL line Higher bit rate services
Bonding levels Different bonding levels can be configured, depending on the LT board capabilities and board type (ADSL or VDSL)
• •
Odd-even adjacent line bonding (for ATM/ADSL lines) Intra-LT line bonding (for ATM/ADSL lines and for PTM/VDSL lines)
Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 December 2011 DLP 1130-1 3HH-10104-AAAA-TQZZA Edition 02 Released Operations and Maintenance Using CLI for FD 24 NT
DLP 1130 — Configure xDSL bonding
Note 1 — The following applies to these xDSL lines in case of odd-even adjacent line bonding:
• • •
The two lines used for xDSL bonding must be subsequent lines The first line must be an odd line ATM PVC, … must be configured AFTER configuring the bonding group
Note 2 — The following applies to the first line (also known as bonding group index):
•
Configuration of parameters such as atm pvc, bridge port, and so on, must be done on that first line. Refer to DLP 1124 for the configuration procedure.
Prerequisites The following prerequisites must be fulfilled before xDSL bonding can be configured:
• • •
The The DLP The
• •
LT must be planned;see DLP 2111. xDSL profiles with the correct transfert mode must have been created; see 1129. transfert mode of the xDSL lines must be correct: If the default transfert mode of the lines is the required transfert mode, no configuration of the lines is necessary. If the default transfert mode of the lines is not the required transfert mode, the xDSL line/user must be configured; see DLP 1124.
Procedure Proceed as follows to manage an xDSL bonding group: 1
2
Do you want to: a
Create an xDSL bonding group, go to step 2
b
Delete an xDSL bonding group, go to step 4
Create a bonding group as follows: i
Configure an xDSL bonding group profile with the following command: configure xdsl-bonding group-profile (index) name 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
DLP 1130-2
December 2011 Alcatel-Lucent 7302 | 7330 | 7356 R4.3.02 Operations and Maintenance Using CLI for FD 24 NT Edition 02 Released 3HH-10104-AAAA-TQZZA
DLP 1130 — Configure xDSL bonding
(no) (no) (no) (no) (no)
max-delay-up imp-noise-prot-dn imp-noise-prot-up 
