Sad-Gebc Cli Operations View Z Aiwu

Alcatel 1540 Litespan Giga Ethernet Controller i
Edition 01 Proposal 3EC-41868-0001-TQZZA Operations and Maintenance Using CLI

Alcatel 1540 Litespan
Release 1.0
Operations and Maintenance Using CLI

ii Alcatel 1540 Litespan Giga Ethernet Controller
Alcatel assumes no responsibility for the accuracy of the information presented,
which is subject to change without notice.
Alcatel and the Alcatel logo are registered trademarks of Alcatel. All other
trademarks are the property of their respective owners.
Copyright 2006 Alcatel.
All rights reserved.
Disclaimers
Alcatel 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, licence or
other distribution of the products for any such application without the prior written
consent of Alcatel, shall be at the customer's sole risk. The customer hereby agrees
to defend and hold Alcatel harmless from any claims for loss, cost, damage, expense
or liability that may arise out of or in connection with the use, sale, licence or other
distribution of the products in such applications.
This document may contain information regarding the use and installation of
non-Alcatel products. Please note that this information is provided as a courtesy to
assist you. While Alcatel tries to ensure that this information accurately reflects
information provided by the supplier, please refer to the materials provided with any
non-Alcatel product and contact the supplier for confirmation. Alcatel assumes no
responsibility or liability for incorrect or incomplete information provided about
non-Alcatel products.
However, this does not constitute a representation or warranty. The warranties
provided for Alcatel products, if any, are set forth in contractual documentation
entered into by Alcatel 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.

Preface
This preface provides general information about the documentation set for
the Litespan-1540 Gigaethernet Controller.
Scope
This documentation set provides information about safety, features and
functionality, ordering, hardware installation and maintenance, CLI and TL1
commands, and software upgrade and migration procedures.
Audience
This documentation set is intended for planners, administrators, operators,
and maintenance personnel involved in installing, upgrading, or maintaining
the Litespan-1540 Gigaethernet Controller.
Prerequisite knowledge
The reader must be familiar with general telecommunications principles.

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.

Alcatel 1540 Litespan Giga Ethernet Controller iii
Procedures with options or substeps
When there are options in a procedure, they are identified by letters. When
there are required substeps in a procedure, they are identified by Roman
numerals.
Procedure 1 Example of options in a procedure
At step 1, you can choose option a or b. At step 2, you must do what the step indicates.
1 This step offers two options. You must choose one of the following:
a This is one option.
b This is another option.
2 You must perform this step.

iv Alcatel 1540 Litespan Giga Ethernet Controller
Procedure 2 Example of required substeps in a procedure
At step 1, you must perform a series of substeps within a step. At step 2, you must do
what the step indicates.
1 This step has a series of substeps that you must perform to complete the step. You
must perform the following substeps:
i This is the first substep.
ii This is the second substep.
iii This is the third substep.
2 You must perform this step.
Measurement conventions
Measurements in this document are expressed in imperial units. If metric
measurements are included, they appear in brackets following the imperial
measurement. The metric measurements follow the Systme international
dunits (SI) standard for abbreviation of metric units.
Contents
Contents
Preface 1
Scope .............................................................................................................................. 1
Audience .............................................................................................................................. 1
Prerequisite knowledge ......................................................................................................... 1
Safety information.................................................................................................................. 1
Documents ............................................................................................................................ 2
ETSI and ANSI release naming............................................................................................. 3
Special information................................................................................................................ 4
1 Introduction 1-1
1.1 Introduction........................................................................................................ 1-2
1.2 How to Use this Document ................................................................................ 1-2
Index List (IXL)
IXL 100 Master Task Index List IXL 100-1
Non-Trouble Procedures (NTP)
NTP 100 CLI Session Set up and User Configuration NTP 100-1
NTP 101 Script Files NTP 101-1
NTP 102 System Installation and Configuration NTP 102-1
NTP 103 Equipment Configuration NTP 103-1
NTP 104 Configuration of a Cross-Connect VLAN NTP 104-1
NTP 105 Configuration of an iBridge VLAN NTP 105-1
Contents
NTP 106 Configure an IP Aware Bridge NTP 106-1
NTP 107 Configure an IP Router NTP 107-1
NTP 108 Service Installation NTP 108-1
NTP 109 Configuration of PPPoE Termination NTP 109-1
NTP 110 Add an iBridge User NTP 110-1
NTP 111 Add an IPoA User NTP 111-1
NTP 112 Add an IPoE User NTP 112-1
NTP 113 Add a PPPoE User NTP 113-1
NTP 114 Equipment Repair NTP 114-1
NTP 115 Monitor Alarms NTP 115-1
NTP 116 Software Management NTP 116-1
NTP 117 System Parameter Modification NTP 117-1
NTP 118 Performance Monitoring NTP 118-1
NTP 119 Service Adaptation NTP 119-1
NTP 120 Troubleshooting Commands NTP 120-1
NTP 121 CPE Management NTP 121-1
NTP 122 Cluster Management NTP 122-1
NTP 123 Secure Shell NTP 123-1
Contents
NTP 124 Maintain the System NTP 124-1
NTP 125 Add an IPoA Cross-Connect User NTP 125-1
Detailed Level Procedures (DLP)
DLP 100 Set up a CLI Session DLP 100-1
DLP 101 Create Operator Profiles and Instances DLP 101-1
DLP 102 Configure Management IP Parameters DLP 102-1
DLP 103 Configure System Parameters DLP 103-1
DLP 104 Configure Network Interfaces DLP 104-1
DLP 105 Configure Link Aggregation Usage DLP 105-1
DLP 106 Configure RSTP DLP 106-1
DLP 107 Configure OSPF DLP 107-1
DLP 108 Configure RIP DLP 108-1
DLP 109 Configure SNMP and Trap Management DLP 109-1
DLP 110 Manage Alarms DLP 110-1
DLP 111 Plan, Replan, and Unplan Equipment DLP 111-1
DLP 112 Lock and Unlock Equipment DLP 112-1
DLP 113 Configure the Equipment DLP 113-1
Contents
DLP 114 NT Redundancy DLP 114-1
DLP 115 Create a L2 Terminated Forwarder VLAN DLP 115-1
DLP 116 Create a L2 Terminated Router VLAN DLP 116-1
DLP 117 Create a C-VLAN DLP 117-1
DLP 118 Create an S-VLAN DLP 118-1
DLP 119 Create an SC-VLAN DLP 119-1
DLP 120 Create an iBridge VLAN DLP 120-1
DLP 121 Add Network Interfaces to a VLAN DLP 121-1
DLP 122 Create a Forwarding VRF DLP 122-1
DLP 123 Create a Router VRF DLP 123-1
DLP 124 Create an iBridge User DLP 124-1
DLP 125 Create an IPoA User DLP 125-1
DLP 126 Create an IPoE User DLP 126-1
DLP 127 Create a PPPoE User DLP 127-1
DLP 128 Add an LT to a VLAN DLP 128-1
DLP 129 Create xDSL Profiles DLP 129-1
DLP 130 Configure xDSL Bonding DLP 130-1
DLP 131 Create an xDSL Bonding Group DLP 131-1
Contents
Alcatel 1540 Litespan Giga Ethernet Controller v
DLP 132 Configure Filtering on SHub DLP 132-1
DLP 133 Configure QoS on L2 DLP 133-1
DLP 134 Configure QoS on L3 DLP 134-1
DLP 135 Configure a QoS Aware VLAN DLP 135-1
DLP 136 Configure Multicast DLP 136-1
DLP 137 Configure IGMP Proxy DLP 137-1
DLP 138 Configure IGMP Snooping DLP 138-1
DLP 139 Configure DHCP Relay Agent in iBridge Mode DLP 139-1
DLP 140 Configure DHCP Relay Agent in Router Mode DLP 140-1
DLP 141 Configure DHCP Relay Agent in Forwarder Mode
DLP 141-1
DLP 142 Configure the Security Domain DLP 142-1
DLP 143 Configure Local Authentication DLP 143-1
DLP 144 Configure RADIUS DLP 144-1
DLP 145 Configure 802.1x DLP 145-1
DLP 146 Configure PPPoE Relay DLP 146-1
DLP 147 Configure PPPoA-PPPoE Relay DLP 147-1
DLP 148 Enable the PPPoE Server DLP 148-1
Contents
vi Alcatel 1540 Litespan Giga Ethernet Controller
DLP 149 Configure PPPoE Profiles DLP 149-1
DLP 150 Configure ARP Table Entry DLP 150-1
DLP 151 Shut down and Restart the SHub DLP 151-1
DLP 152 Reboot the System DLP 152-1
DLP 153 Shut down and Restart Individual Equipment DLP 153-1
DLP 154 Create a Snapshot Alarm Table DLP 154-1
DLP 155 Monitor Alarms DLP 155-1
DLP 156 Management of the SHub Database DLP 156-1
DLP 157 Manage the SHub Database DLP 157-1
DLP 158 Management of the System Database DLP 158-1
DLP 159 Management of OSWP DLP 159-1
DLP 160 View Version of the SHub Software DLP 160-1
DLP 161 Software Licenses Counters DLP 161-1
DLP 162 Modify the External Management VLAN DLP 162-1
DLP 163 Modifying xDSL Profiles DLP 163-1
DLP 164 Ping Command DLP 164-1
DLP 165 Traceroute Command DLP 165-1
DLP 166 Configure CPE Management DLP 166-1
Contents
Alcatel 1540 Litespan Giga Ethernet Controller vii
DLP 167 Script Files DLP 167-1
DLP 168 Modify the System Management IP Parameters
DLP 168-1
DLP 169 Configure Cluster Management DLP 169-1
DLP 170 Configure SSH DLP 170-1
DLP 171 EMS Management DLP 171-1
DLP 172 Create a Default Operator Profile DLP 172-1
DLP 174 Create an IPoA Cross-Connect User DLP 174-1
DLP 175 Configure Single IP Address DLP 175-1
DLP 176 Configure the Default Security Domain DLP 176-1
Routine Task Procedure (RTP)
RTP 100 Backup the Configuration RTP 100-1
RTP 101 Restore the Configuration RTP 101-1
RTP 102 Retrieve Remote Inventory RTP 102-1
Trouble Analysis Procedure (TAP)
TAP 101 F5 Loopback Test TAP 101-1
TAP 102 Equipment Repair TAP 102-1
Contents
viii Alcatel 1540 Litespan Giga Ethernet Controller
TAP 103 Single Ended Line Testing TAP 103-1
TAP 104 Fault isolation and troubleshooting TAP 104-1
Training (TNG)
TNG 100 Service Installation TNG 100-1
TNG 101 QoS Configuration TNG 101-1
TNG 102 IGMP and Multicast Configuration TNG 102-1
TNG 103 VBAS TNG 103-1
TNG 104 DHCP Relay Agent Configuration TNG 104-1
TNG 105 Overall Software Packages TNG 105-1
Glossary
Index
1 Introduction
1 Introduction
1ii
1ii
1 Introduction
1.1 Introduction
This document provides instructions on CLI operation and maintenance tasks and
procedures for the Litespan-1540 Gigaethernet Controller.
Throughout the document, the Litespan-1540 will be referred to as the Network
Element (NE).
See the CLI Commands document for more detailed information about the CLI
command syntax.
1.2 How to Use this Document
This document uses the task-oriented practice (TOP) method. The TOP method is a
documentation system that supports the installation, operation, and maintenance of
telecommunications equipment and software through different layers of
documentation. Most layers in the TOP system are programmed documents that
provide step-by-step instructions for the successful completion of a specific task or
procedure.
A task document is structured to provide information in such a way that both
experienced and inexperienced users can effectively use the material to perform
work assignments. Less-experienced users can refer to detailed step-by-step
procedure documents referred to by the task document to easily comprehend and
complete the task. Experienced users can bypass the procedure documents and use
only the level of information they need to do the task.
TOP layers
The TOP documentation method uses the following layers:
IXL Index List
NTP Non-Trouble Procedure
DLP Detailed Level Procedure
RTL Routine Task List
RTP Routine Task Procedure
TAP Trouble Analysis Procedure
TAD Trouble Analysis Data
TNG Training
Figure 1-1 shows the layers and logical path of the TOP documentation method.
1 Introduction
Figure 1-1 TOP Layers and Documentation Path
All layers do not apply to all documents. This document contains only contains the
layers needed to complete operation and maintenance tasks and procedures specific
to the NE through the EMS.
Index List (IXL)
The IXL lists each task and procedure (for example, Log on to the 5526 AMS), along
with related supporting information and the identification number of the
corresponding document (for example, DLP 500). This lets users know where to find
the appropriate documentation.
Non-Trouble Procedure (NTP)
NTPs are procedures that describe how to perform a task (what to do), such as how
to accept a system after it has been installed, turn up a system for service, or maintain
a system according to a maintenance plan. NTPs are made up of steps that refer to
detailed procedures (DLPs) or to supporting information (provided in TNGs). This
allows inexperienced users (or experienced users who want more information) to go
to the DLP or TNG for the additional information they need to complete the task. If
user go to the referenced DLP or TNG, they must return to the NTP to continue the
task.
NTPs are typically referenced from the IXL.
Detailed Level Procedure (DLP)
A DLP describes how to perform a procedure. In addition to step-by-step
information, DLPs contain any tables or illustrations that are required to perform the
procedure.
DLPs can be referenced from the IXL, an NTP, a lower-level TAP, another DLP, or
from a TNG. When a DLP is completed, the user returns to the point from which the
DLP was referenced.
Task index List (IXL) or
Overview Flowchart
Non-Trouble
Clearing Procedure
(NTP)
Trouble Analysis
Procedure
(TAP)
User Training
Package
(TNG)
Routine Task
Procedure
(RTP)
Routine Task List
(RTL)
Trouble Analysis
Data
(TAD)
Detailed Level Procedure
(DLP) or Chart
1 Introduction
Routine Task List (RTL)
An RTL provides a listing of routine maintenance procedures (what to do). The
detailed steps for each procedure listed in the RTL are provided in RTPs.
RTLs are typically referenced from the IXL.
An RTP describes how to perform a routine maintenance procedure.
RTPs are typically referenced from an RTL, but references can be made from the
IXL if there is no RTL.
TAPs are intended to help identify and clear trouble in the system. TAPs may be
organized in levels (what and how to do). A high-level TAP is designed to categorize
the trouble through a series of decisions and instructions. Once categorized, a
lower-level TAP is referenced. This lower-level TAP addresses only the isolated
topic and is structured to isolate and clear the trouble through a series of decisions
and instructions without returning to the higher-level TAP. For inexperienced users
(or experienced users who want more information), a TAP may provide a references
to a TAD, DLP, or TNG. If users go to the referenced TAD, DLP, or TNG, they need
to return to the TAP to continue the procedure.
TAPs are typically referenced from the IXL or other TAPs.
Trouble Analysis Data (TAD)
A TAD contains supporting information (other than procedural steps) to be used as
a trouble-clearing aid. It may be a functional schematic, text, or trouble-clearing
chart.
TADs are typically referenced from a TAP.
Training (TNG)
A TNG contains supplementary information about a task or procedure.
TNGs are typically referenced from an IXL, but references are also made from other
TOP layers such as NTPs and DLPs.
Step Procedure Details
NTPs, DLPs, RTPs, and TAPs use procedural steps and decision steps.
Procedural steps provide instructions, and decision steps provide a go-to choice.
Procedural steps may contain notations that refer to additional information such as
notes, tables, figures, examples, and other procedures.
1 Introduction
All mandatory information required to complete a step is shown at the beginning of
the step.
Optional information, which can be accessed according to experience level, is
enclosed in parentheses as shown in the example below:
Log on to the system (for details, see DLP-500).
The completion of a specific task or procedure is indicated as follows:
STOP. This procedure is complete.
1 Introduction

Index List (IXL)
IXL 100 Master Task Index List

Table 10000-1: Non-Trouble Procedures (NTPs)
Title NTP number
Add a PPPoE User NTP 113
Add an iBridge User NTP 110
Add an IPoA User NTP 111
Add an IPoA Cross-Connect User NTP 125
Add an IPoE User NTP 112
CLI Session Set up and User Configuration NTP 100
Cluster Management NTP 122
CPE Management NTP 121
Configure an IP Aware Bridge NTP 106
Configure an IP Router NTP 107
Configuration of a Cross-Connect VLAN NTP 104
Configuration of an iBridge VLAN NTP 105
Equipment Configuration NTP 103
Equipment Repair NTP 114
Monitor Alarms NTP 115
Performance Monitoring NTP 118
Configuration of PPPoE Termination NTP 109
Maintain the System NTP 124
Script Files NTP 101
Secure Shell NTP 123
Service Adaptation NTP 119
Service Installation NTP 108
Software Management NTP 116
System Installation and Configuration NTP 102
System Parameter Modification NTP 117
Troubleshooting Commands NTP 120
Table 10000-2: Detailed Level Procedures (DLP)
Title DLP number
Add an LT or the subatm to a VLAN DLP 128
Add Network Interfaces to a VLAN DLP 121
Configure 802.1x DLP 145
Configure a QoS Aware VLAN DLP 135
Configure ARP Table Entry DLP 150
Configure Cluster Management DLP 169
Configure CPE Management DLP 166
Configure DHCP Relay Agent in Forwarder Mode DLP 141
Configure DHCP Relay Agent in iBridge Mode DLP 139
Configure DHCP Relay Agent in Router Mode DLP 140
Configure Filtering on SHub and subatm DLP 132
Configure IGMP Proxy DLP 137
Configure IGMP Snooping DLP 138
Configure Link Aggregation Usage DLP 105
Configure Local Authentication DLP 143
Configure Management IP Parameters DLP 102
Configure Multicast DLP 136
Configure Network Interfaces DLP 104
Configure OSPF DLP 107
Configure PPPoA-PPPoE Relay DLP 147
Configure PPPoE Profiles DLP 149
Configure PPPoE Relay DLP 146
Configure QoS on L2 DLP 133
Configure QoS on L3 DLP 134
Configure RADIUS DLP 144
Configure RIP DLP 108
Configure RSTP DLP 106
Configure Single IP Address DLP 174
Configure SNMP and Trap Management DLP 109
Configure SSH DLP 170
Configure System Parameters DLP 103
Configure the Default Security Domain DLP 175
Configure the Equipment DLP 113
Configure the Security Domain DLP 142
Configure xDSL Bonding DLP 130
(1 of 3)
Create a C-VLAN DLP 117
Create a Default Operator Profile DLP 172
Create a Forwarding VRF DLP 122
Create a L2 Terminated Forwarder VLAN DLP 115
Create a L2 Terminated Router VLAN DLP 116
Create a PPPoE User DLP 127
Create a Router VRF DLP 123
Create a Snapshot Alarm Table DLP 154
Create an iBridge User DLP 124
Create an iBridge VLAN DLP 120
Create an IPoA Cross-Connect User DLP 173
Create an IPoA User DLP 125
Create an IPoE User DLP 126
Create an SC-VLAN DLP 119
Create an S-VLAN DLP 118
Create an xDSL Bonding Group DLP 131
Create Operator Profiles and Instances DLP 101
Create xDSL Profiles DLP 129
EMS Management DLP 171
Enable the PPPoE Server DLP 148
Lock and Unlock Equipment DLP 112
Manage Alarms DLP 110
Manage the SHub Database DLP 157
Management of OSWP DLP 159
Management of the SHub Database DLP 156
Management of the System Database DLP 158
Modify the External Management VLAN DLP 162
Modify the System Management IP Parameters DLP 168
Modifying xDSL Profiles DLP 163
Monitor Alarms DLP 155
NT Redundancy DLP 114
Ping Command DLP 164
Plan, Replan, and Unplan Equipment DLP 111
Reboot the System DLP 152
Script Files DLP 167
Set up a CLI Session DLP 100
Shut down and Restart Individual Equipment DLP 153
Title DLP number
(2 of 3)
Table 10000-3: Routine Task Procedure (RTP)
Table 10000-4: Trouble Analysis Procedure (TAP)
Table 10000-5: Training (TNG)
Shut down and Restart the SHub DLP 151
Software Licenses Counters DLP 161
Traceroute Command DLP 165
View Version of the SHub Software DLP 160
Title RTP number
Backup the Configuration RTP 100
Restore the Configuration RTP 101
Retrieve Remote Inventory RTP 102
Title TAP number
Equipment Repair TAP 102
F5 Loopback Test TAP 101
Fault isolation and troubleshooting TAP 103
Title TNG number
DHCP Relay Agent Configuration TNG 104
IGMP and Multicast Configuration TNG 102
Overall Software Packages TNG 105
QoS Configuration TNG 101
Service Installation TNG 100
VBAS TNG 103
Title DLP number
(3 of 3)

Non-Trouble Procedures (NTP)
NTP 100 CLI Session Set up and User Configuration
NTP 101 Script Files
NTP 102 System Installation and Configuration
NTP 103 Equipment Configuration
NTP 104 Configuration of a Cross-Connect VLAN
NTP 105 Configuration of an iBridge VLAN
NTP 106 Configure an IP Aware Bridge
NTP 107 Configure an IP Router
NTP 108 Service Installation
NTP 109 Configuration of PPPoE Termination
NTP 110 Add an iBridge User
NTP 111 Add an IPoA User
NTP 112 Add an IPoE User
NTP 113 Add a PPPoE User
NTP 115 Monitor Alarms
NTP 116 Software Management
NTP 118 Performance Monitoring
NTP 117 System Parameter Modification
NTP 119 Service Adaptation
NTP 120 Troubleshooting Commands
NTP 121 CPE Management
NTP 122 Cluster Management
NTP 123 Secure Shell
NTP 124 Maintain the System

NTP 125 Add an IPoA Cross-Connect User
NTP 100 CLI Session Set up and
User Configuration
Purpose
This procedure provides the steps to set up a CLI session with the NE and create a user
using the Alcatel-developed CLI.
General
Figure 10000-1 shows the management topology of the NE system.
Figure 10000-1: Management Topology
Table 10000-1 lists the three types of system managers.
Table 10000-1: System Managers
Manager type Description
EMS Element Management System based on SNMP
TL1 CT Craft Terminal using TL1 commands
CLI CT Craft Terminal using Command Line Interface (CLI) commands
SNMP based
manager
SNMP based
manager
TL1 craft
terminal
CLI craft
terminal
17706
SNMP
Mapper
Application code
LT shelf
CLI agent
TL1
Mapper
Application code
S Hub
SNMP
See the CLI Commands and Messages document for detailed information about the CLI
command syntax.
The use of TL1 commands is still supported.
Procedure
Proceed as follows to set up the CLI session and configure the CLI users:
1 Set up a CLI session; see DLP 100.
2 Create and configure an Operator Profile; see DLP 101.
3 Create a default Operator Profile; see DLP 172.
4 STOP. This procedure is complete.
Purpose
A script file is a file containing CLI commands, which can be used to restore a
configuration.
A script file must follow the same syntax rules as commands entered interactively. Only
the tab and the question mark lose their special meaning in a script, so command
expansion and single-line help are not available.
The script will be aborted if one of the commands in the script fails. A command may be
preceded by a minus '-' to prevent the script from being aborted in case of a semantic
error; for example, when you try to delete a node instance that does not exist.
By default, a command script does not interact with the user. The execution of the script
will be aborted if a command or filter requires interaction with the user. Interactivity can
be enabled by specifying the interactive option with the exec command.
Command scripts may not be nested.
Procedure
In order to use script files, you need to perform the following tasks:
1 Create and execute script files; see DLP 167.
NTP 102 System Installation and
Configuration
Purpose
There are two separate subsystems (the Line Termination (LT) shelf and the Service Hub
(SHub)) that must be configured via separate commands. This document describes the
procedure to be used to configure the system.
Prerequisite
A CLI session must have been set up; see DLP 100.
Security Considerations
Procedure
Proceed as follows to configure the system:
1 Configure the network interfaces; see DLP 104.
2 Configure the management IP parameters; see DLP 102.
Note: For the specific procedure on how to configure the system for single IP
address; see DLP 174.
3 Configure the system parameters; see DLP 103.
4 Configure Simple Network Management Protocol (SNMP) and trap management;
see DLP 109.
Note The following must be taken into account with regard to system
security:
It is NOT advised to use insecure management channels: CLI/Telnet,
TL1/UDP, SNMPv1/2, dual IP address mode (only SNMPv1/2 on
SHub), TFTP.
If SNMPv1/2 is used anyway, it is advised not to use community string
= public
It is advised to use secure management channels (CLI/SSH,
TL1/SSH, SNMPv3, single IP address mode, SFTP). This implies
closing the insecure management channels!
SHub ACLs must be configured to allow only AWS traffic to be routed
to the NT OBC.
Encryption via keys must be promoted compared to passwords
5 Enable the management of EMS; see DLP 171.
6 Configure alarm management; see DLP 110.
7 Configure the link aggregation link usage; see DLP 105.
8 Configure Rapid Spanning Tree Protocol (RSTP) management; see DLP 106.
9 Configure Open Shortest Path First (OSPF) management; see DLP 107.
10 Configure Routing Information Protocol (RIP) management; see DLP 108.
11 Configure the SHub database save location and the restore source file; see
DLP 157.
Purpose
This procedure provides the steps to plan, unplan, or replan the equipment and to lock or
unlock the equipment. Some equipment-related items, such as the shelf, are
auto-created at system startup and do not need to be created. However, they can be
midfield.
General
The NE consists of a single shelf with plug-in units. You can perform the actions
described in Table 10300-1 to configure the equipment.
Table 10300-1: Configure plug-in units
Procedure
Proceed as follows to configure or modify the system equipment:
1 Plan, replan, or unplan equipment; see DLP 111.
2 Lock or unlock the equipment; see DLP 112.
3 Modify the configuration of the system equipment; see DLP 113.
4 Configure NT redundancy; see DLP 114.
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.
Locking and unlocking
equipment
When necessary, you can lock any equipment, most often a unit, to put it out
of service. Locking a unit renders it inactive. No traffic is generated or
received by the units. However, the unit is not removed from the
configuration, and as soon as you unlock the unit, it becomes active again.
It goes back to operational mode without restart or initialization, and traffic
can resume immediately.
Similarly, you can power down the unit and restart it at a later time. In this
case, however, the unit will go through a complete startup cycle before
traffic is possible.
NTP 104 Configuration of a
Cross-Connect VLAN
Purpose
The NE supports several VLAN cross-connect models:
Customer VLAN (C-VLAN) cross-connect:
This is the most straightforward VLAN cross-connect model where a single VLAN ID
at the EMAN side is associated with a given PVC at the user side. Any kind of traffic
issued by the subscriber is passed transparently towards the network using the
selected VLAN ID.
Service provider VLAN (S-VLAN) cross-connect: VLAN stacking for business users
Two levels of VLAN tags are used, allowing to support a hierarchical addressing:
The customer VLAN: C-VLAN
The service provider VLAN: S-VLAN
In this mode, the S-VLAN ID at the EMAN side is associated with a single subscriber
interface at the user side. The C-VLANs carried within the S-VLAN are passed
transparently to the end user. This allows the end user to specify its own end-to-end
connectivity, while remaining transparent for the EMAN.
S-VLAN / C-VLAN cross-connect: VLAN stacking for residential users:
The basic VLAN cross-connect mode suffers from the fact the that number of VLAN
identifiers is limited to 4K. Since the VLAN is a EMAN wide identifier, one ends up with
a scalability issue: there cannot be more than 4K end users connected to the whole
EMAN. To solve this issue, two VLANs are stacked and the cross-connection is then
performed on the combination (S-VLAN, C-VLAN) allowing to theoretically reach up
to 16M end users.
Procedure
The procedures for creating a cross-connect VLAN are described in the following DLPs:
1 For the creation of a C-VLAN; see DLP 117.
2 For the creation of an S-VLAN; see DLP 118.
3 For the creation of an SC-VLAN; see DLP 119.
4 For the creation of an Qos aware VLAN; see DLP 135.
NTP 105 Configuration of an iBridge
VLAN
Purpose
The concept of a VLAN in intelligent bridging (iBridge) mode is that multiple NSPs are
each connected to the NE with a VLAN. The user ports are connected to the VLAN of
their corresponding NSP.
Note: The NE supports up to 128 iBridges.
Procedure
Proceed as follows to configure an iBridge VLAN:
1 For the creation of an iBridge VLAN; see DLP 120.
2 Add the network interface to the iBridge VLAN; see DLP 121.
Purpose
In this mode, the NE can be seen as an IP Aware Bridge without being seen as an IP
next-hop. Users connected to the NE are seen as being directly attached to the edge
router IP interfaces.
The end-users use the IP address of the edge router as their default gateway, while the
IP edge router sees the end-user subnets as directly attached networks. The NE sits in
between and perform packet forwarding at L3.
This procedure provides the steps to configure an IP aware bridge on the NE.
Procedure
Proceed as follows to configure an IP aware bridge:
1 Create a forwarder Virtual Routing Forwarding (VRF); see DLP 122.
2 For each of the n Network Service Providers (NSP), create a L2 terminated
forwarder VLAN; see DLP 115.
3 Add the network interfaces to the L2 terminated forwarder VLANs; see DLP 121.
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 Litespan. A single Virtual Router can be configured in this
mode, which can co-exist in the same system with a number of VRs that are configured
in IP Aware Bridge mode (see NTP 106).
At the user side of the system (xDSL line), unnumbered IP interfaces are used, while user
subnets are configured on a user gateway interface. In order to achieve max efficiency in
the allocation of IP addresses, several users (on different xDSL lines) can share a same
subnet.
Host routes towards the end-user devices are either dynamically created in the NE in
case of dynamic DHCP or PPPoE sessions, or statically provisioned in case of static IP
address assignment.
Towards the network, IP interfaces are numbered (meaning that the NE IP addresses
and subnets are configured).
This procedure provides the steps to configure an IP router on the NE.
Procedure
Proceed as follows to configure an IP router:
1 Create a router VRF; see DLP 123.
2 Create a L2 terminated router VLAN; see DLP 116.
3 Add the network interfaces to the bridged VLAN; see DLP 121.
Purpose
This procedure provides the steps to configure the following services on the NE:
Quality of Service (QoS)
Internet Group Management Protocol (IGMP) and multicast
Dynamic Host Configuration Protocol (DHCP) relay agent and Option 82
Authentication
Point-to-Point Protocol (PPP) configuration
Layer 2 Control Protocol (L2CP) session.
Procedure
To configure a service, you need to perform the following tasks:
1 Configure xDSL profiles; see DLP 129.
2 Configure QoS:
i For the configuration of a QoS aware VLAN; see DLP 135.
ii For the configuration of QoS on L2; see DLP 133.
iii For the configuration of QoS on L3; see DLP 134.
3 Configure IGMP and multicast:
i For the configuration of multicast; see DLP 136.
ii For the configuration of IGMP proxy on the LT; see DLP 137.
iii For the configuration of IGMP snooping on the SHub; see DLP 138.
4 Configure DHCP Relay:
i For the configuration of the DHCP relay agent in iBridge mode; see DLP 139.
ii For the configuration of the DHCP relay agent in router mode; see DLP 140.
iii For the configuration of the DHCP relay agent in forwarder mode; see
DLP 141.
5 Configure the authentication settings:
i For the configuration of the security domain: see DLP 142.
ii For the configuration of local authentication; see DLP 143.
iii For the configuration of RADIUS; see DLP 144.
iv For the configuration of 802.1x authentication; see DLP 145.
6 Configure the PPP relay settings:
i For the configuration of PPPoE relay; see DLP 146.
ii For the configuration of PPPoA-PPPoE relay; see DLP 147.
7 Configure an L2CP session; see DLP 177.
NTP 109 Configuration of PPPoE
Termination
Purpose
This procedure provides the steps to configure Point-to-Point Protocol (PPP) on the NE.
Procedure
To configure PPPoE termination, you need to perform the following tasks:
1 For the configuration of the PPPoE server; see DLP 148.
2 For the configuration of PPPoE profiles; see DLP 149.
Purpose
This procedure provides the steps to add an iBridge user on the NE.
Prerequisites
The following prerequisites must be fulfilled before an iBridge user can be created:
The LT must be planned; see DLP 111.
The xDSL profiles must have been created; see DLP 129.
An iBridge VLAN should be created; see DLP 120.
Procedure
Proceed as follows to add an iBridge user:
1 Add the LT to the VLAN, for the first user to be created on the LT for that VLAN; see
DLP 128.
2 Create an iBridge user; see DLP 124.
Purpose
An IPoA user interface is a L2 interface created on a PVC which is configured in
RFC2684 LLCSNAP routed or RFC2684 VC-MUX routed encapsulation modes.
An IPoA interface is attached to a Virtual Router (VR) by configuring an unnumbered IP
interface on top of it. The VR is always determined via configuration.
Multiple user sessions (or users) may exist on the same IPoA interface. A session
corresponds to all the traffic originating from or destined to a host whose IP address is
seen by the NE in the customer environment.
This procedure provides the steps to add an IPoA user on the NE.
Prerequisites
The following prerequisites must be fulfilled before an IPoA user can be created:
xDSL profiles must have been created; see DLP 129.
An IP aware bridge (see NTP 106) or an IP router (see NTP 107) must have been
created.
Procedure
Proceed as follows to add an IPoA user:
1 If the first IPoA user to be created on a VLAN needs DHCP, configure the VRF for
DHCP; see DLP 140.
2 Create an IPoA user; see DLP 125.
3 Add the LT to the virtual VLAN, for the first user to be created on the LT for that
VLAN; see DLP 128.
Purpose
An IPoE(oA) user interface is a L2 interface created on a PVC which is configured in
RFC2684 LLCSNAP bridged or RFC2684 VC-MUX bridged encapsulation modes.
An IPoE(oA) interface is attached to a VR by configuring an unnumbered IP interface on
top of it. The VR is always determined via configuration (802.1x authentication is not
supported in combination with IP forwarding).
Multiple user sessions (or users) may exist on the same IPoE(oA) interface. A session
corresponds to all traffic originated from or destined to a host whose IP addressis seen
by the NE in the customer environment.
Prerequisites
created.
Procedure
Proceed as follows to add an IPoE user:
1 If the first IPoE user to be created on a VLAN needs DHCP, configure the VRF for
DHCP; see DLP 140.
2 Create an IPoE user; see DLP 126.
3 Add the LT to the correct VLAN (service), for the first user to be created on the LT
for that VLAN; see DLP 128.
Purpose
A PPPoE(oA) user interface is a L2 interface created on a PVC which is configured in
RFC2684 LLCSNAP bridged or RFC2684 VC-MUX bridged encapsulation modes.
A PPPoE session is an unnumbered IP interface established by a user on a PPPoE(oA)
interface. IP interface is a notion to group traffic and treat as a single entity for different
purposes being authentication, accounting, service provisioning, and security.
Multiple PPPoE sessions can be established on the same PPPoE(oA) interface. The
system can also limit the max number of PPPoE session per PPPoE(oA) via
configuration.
Prerequisites
The following prerequisites must be fulfilled before an PPPoE user can be created:
created.
PPPoE termination (that is, enabling PPPoE server and configuration of PPPoE
profiles) must have been configured; see NTP 109.
Procedure
Proceed as follows to add a PPPoE user:
1 Create a PPPoE user; see DLP 127.
2 Add the LT to the correct VLAN (service), for the first user to be created on the LT
for that VLAN; see DLP 128.
Purpose
This procedure provides the steps to monitor the alarms on the NE.
Procedure
Proceed as follows to monitor the alarms:
1 Create an alarm snapshot table; see DLP 154.
2 Monitor the alarms; see DLP 155.
Purpose
This procedure provides the steps to perform software management on the NE.
Procedure
The following steps can be used to perform software management:
1 Management of the NT and SHub database; see RTP 100.
2 Management of the Overall Software Packages; see DLP 159.
3 Management of the SHub software; see DLP 160.
4 Management of the software licenses; see DLP 161.
NTP 117 System Parameter
Modification
Purpose
This procedure lists the procedures for system parameter modification.
Procedure
Proceed as follows to modify system parameters:
1 Modify the management IP parameters; see DLP 168.
2 Change the external management VLAN; see DLP 162.
Purpose
This procedure provides the commands for performance monitoring on the NE.
Note: For more information on the command syntax and the comand parameters, refer
to the CLI Commands and Messages.
Procedure
The following steps can be used for performance monitoring:
1 Use the following commands to show the xDSL counters:
show xdsl counters near-end line current-interval (if-index)
detail
show xdsl counters far-end line current-interval (if-index)
detail
show xdsl counters near-end line current-1day (if-index) detail
show xdsl counters far-end line current-1day (if-index) detail
show xdsl counters near-end line previous-interval (if-index)
detail
show xdsl counters far-end line previous-interval (if-index)
detail
show xdsl counters near-end line previous-1day (if-index) detail
show xdsl counters far-end line previous-1day (if-index) detail
Note: The previous-1day counters are not available until 96 15-min intervals (that is,
24 hours) have passed.
Example:
show xdsl counters near-end line current-interval 1/1/4/1 detail
show xdsl counters far-end line current-interval 1/1/4/1 detail
show xdsl counters near-end line current-1day 1/1/4/1 detail
show xdsl counters far-end line current-1day 1/1/4/1 detail
show xdsl counters near-end line previous-interval 1/1/4/1 detail
show xdsl counters far-end line previous-interval 1/1/4/1 detail
show xdsl counters near-end line previous-1day 1/1/4/1 detail
show xdsl counters far-end line previous-1day 1/1/4/1 detail
2 Use the following commands to show the ATM counters:
show atm tc-current-int one-day (port)
show atm tc-current-int fifteen-min (port)
Example:
show atm tc-current-int one-day 1/1/4/1
show atm tc-current-int fifteen-min 1/1/4/1
3 Use the following command to show the bridge port counters:
show interface port bridge-port (port) detail
Example:
show interface port bridge-port 1/1/4/1:8:35 detail
4 Use the following commands to show the link aggregation counters:
show la aggregator-info (port)
show la aggregator-list (port)
Example:
show la aggregator-info 4
show la aggregator-list 4
5 Use the following command to show the RSTP counters:
show rstp port-info (port)
Example:
show rstp port-info 4
6 Use the following command to show the SHub Ethernet port statistics:
show bridge shub-port (port)
Example:
show bridge shub-port 4
7 Use the following commands to show the PPPoE statistics:
show pppoe statistics-pppoe-itf tx-pkt (port)
show pppoe statistics-pppoe-itf rx-pkt (port)
show pppoe statistics-pppoe-itf stats (port)
show pppoe ppp-statistics (port)
Example:
show pppoe statistics-pppoe-itf tx-pkt 1/1/4/1:8:35
show pppoe statistics-pppoe-itf rx-pkt 1/1/4/1:8:35
show pppoe statistics-pppoe-itf stats 1/1/4/1:8:35
show pppoe ppp-statistics 1/1/4/1:8:35
8 Use the following command to show the QoS statistics:
show qos statistics buffer-overflow total 1/1/4
Example:
show qos statistics buffer-overflow total 1/1/4
9 Use the following command to show the IGMP statistics:
show igmp channel counter (port)
Example:
show igmp channel counter 1/1/4/1:8:35
10 Use the following command to show the IP forwarding statistics:
show ip vrf-statistics (vrf-id)
Example:
show ip vrf-statistics 17
11 Use the following command to show the IP SHub ARP Statistics per VRF forwarding
statistics:
show ip shub arp (vrf-id)
Example:
show ip shub arp 17
12 Use the following commands to show the DHCP relay port counters and the
statistics of DHCP relay agent per VRF:
show dhcp-relay port (port-interface)
show dhcp-relay shub vrf-agent-stats (vrf)
Example:
show dhcp-relay port 1/1/4/3:8:35
show dhcp-relay shub vrf-agent-stats 18
13 Use the following commands to show the PPoX relay statistics:
show pppox-relay cross-connect statistics engine (vlan-id)
show pppox-relay cross-connect statistics client-port
(client-port)
show pppox-relay cross-connect monitor-statistics engine
(vlan-id)
show pppox-relay cross-connect monitor-statistics client-port
(client-port)
Example:
show pppox-relay cross-connect statistics engine 600
show pppox-relay cross-connect statistics
client-port 1/1/4/3:8:35
show pppox-relay cross-connect monitor-statistics engine 600
show pppox-relay cross-connect monitor-statistics
client-port 1/1/4/3:8:35
14 Use the following commands to show the RADIUS statistics:
show security radius auth-server auth-stats (name) vrf-index
<Aaa::VrfIndex>
show security radius acc-server acc-stats (name) vrf-index
<Aaa::VrfIndex>
Example:
show security radius auth-server auth-stats AuthServ1
vrf-index 50
show security radius acc-server acc-stats AccServ1 vrf-index 50
15 Use the following command to show the EAPOL statistics:
show security pae eapol-stats (port)
Example:
show security pae eapol-stats 1/1/4/3:8:35
16 Use the following command to show the statistics related to the SNMP protocol:
show transport snmp protocol-stats
17 Use the following command to show the MAU statistics:
show transport ether-ifmau (if-index) index <Transport::Index>
Example:
show transport ether-ifmau 2 index 4
18 Use the following command to show the SHub L2 information:
show transport shub mac (index-num)
Example:
show transport shub mac 300
Purpose
This procedure provides the steps to adapt the following services on the NE:
xDSL profiles
Procedure
To configure a service, you need to perform the following tasks:
1 Modify an xDSL profile; see DLP 163.
Purpose
The following troubleshooting commands can be used:
Ping:
The ping command lets you verify that a particular IP address exists and can accept
requests. Ping is used diagnostically to ensure that a host computer you are trying to
reach is actually operating. Ping can also be used with a host that is operating to see
how long it takes to get a response back.
Traceroute:
Traceroute is a utility that traces the route in the network for an IP address. It also
calculates and displays the amount of time each hop took.
The utility initiates the sending of a packet (using the Internet Control Message
Protocol (ICMP)), including in the packet a Time To Live (TTL) value that is designed
to be exceeded by the first router that receives it, which will return a Time Exceeded
message. This enables traceroute to determine the time required for the hop to the
first router. Increasing the time limit value, it sends the packet again so that it will reach
the second router in the path to the destination, which returns another Time Exceeded
message, and so forth.
Traceroute determines when the packet has reached the destination by including a
port number that is outside the normal range. When it's received, a Port Unreachable
message is returned, enabling traceroute to measure the time length of the final hop.
As the tracerouting progresses, the records are displayed for you hop by hop.
Procedure
The following troubleshooting commands can be used:
1 Ping command; see DLP 164.
2 Traceroute command; see DLP 165.
Purpose
The Customer Premises Equipment (CPE) management functionality allows to
troubleshoot a CPE at all protocol layers when troubles are experienced with either
misconfiguration of the CPE or with the end-user's terminals. It allows to have a clear
indication if a problem is situated before or after the demarcation point of a telecom
carriers responsibility.
Additionally, CPE management offers the possibility to control the SW upgrade of CPEs
by downloading from the network.
The function of xDSL CPE remote management includes configuration, monitoring,
maintenance and upgrade of xDSL Remote Terminal. The network reference model is
illustrated in Figure 12100-1.
Figure 12100-1: Network Reference Model
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
Network Management Entity
User Management Entity
CPE-MM
RMI ISAM
LMI
xDSL CPE
Three channels ar 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.
Procedure
To configure CPE management, you need to perform the following tasks:
1 Configure CPE management; see DLP 166.
Support
Cluster management is supported on the Litespan.
Purpose
To simplify the management workload of the operator, cluster management groups
multiple Litespan as one logical management domain. The logical management domain
of a cluster is formed by a physically interconnected group of Litespan. The operator can
organize its clusters according to, for example, physical location.
Topology display will present the connectivity and status of Litespan in a connected
environment, possibly over more than one cluster. Moreover, separately managed
Litespan use more public IP addresses, which are limited.
Figure 12200-1 shows an example of the cluster management topology.
Figure 12200-1: Cluster Management Topology
Procedure
To configure cluster management, you need to perform the following tasks:
1 Configure the cluster; see DLP 169.
Purpose
Secure Shell (SSH) is a protocol that provides authentication, encryption, and data
integrity to secure network communications. On top of this protocol, Secure Shell
implementations offer secure replacements for rsh, rlogin, rcp, ftp, and telnet, all of which
transmit data over the network as clear text.
The Secure Shell protocol consists of several subprotocols:
SSH Transport Protocol
This subprotocol is responsible for setting up the secure channel that can be used by
the other SSH subprotocols. The SSH transport protocol handles secure key
exchange, server authentication, encryption, replay, and integrity protection. It runs
on top of any reliable transport protocol (for example, TCP).
SSH User Authentication Protocol
This subprotocol provides client-side user authentication. It runs on top of the SSH
Transport protocol.
SSH Connection Protocol
This subprotocol provides interactive login sessions and forwarded TCP connections.
Procedure
To configure the SSH functionality, you need to perform the following tasks:
1 Configure the SSH functionality; see DLP 170.
Purpose
This NTP provides the steps for system maintenance of the NE.
Procedure
Perform this procedure to maintain the system:
1 Back up the system configuration; see RTP 100.
2 Restore the system configuration; see RTP 101.
3 Retrieve the remote inventory; see RTP 102.
NTP 125 Add an IPoA Cross-Connect
User
Purpose
An Inter-Working Layer (IWL) is created on a PVC that is configured in RFC2684
LLC-SNAP routed or RFC 2684 VC-MUX routed encapsulation modes.
Only one C-VLAN or SC-VLAN is configured in cross-connect mode. This VLAN must
then be associated with a bridge port, which is created on the same PVC as the IWL.
This procedure provides the steps to add an IPoA Cross-Connect User on the NE.
Prerequisites
The following prerequisites must be fulfilled before an IPoA cross-connect user can be
created:
Procedure
Proceed as follows to add an IPoA cross-connect user:
1 Create an IPoA cross- connect user; see DLP 173.
2 Create a C-VLAN or SC-VLAN; see DLP 117 or DLP 119.
Note: Ignore the configuration of an xDSL line within DLP 117 or DLP 119: 3-i, 3-ii,
3-iii, and 3-iv.

Detailed Level Procedures (DLP)
DLP 100 Set up a CLI Session
DLP 101 Create Operator Profiles and Instances
DLP 102 Configure Management IP Parameters
DLP 103 Configure System Parameters
DLP 104 Configure Network Interfaces
DLP 105 Configure Link Aggregation Usage
DLP 106 Configure RSTP
DLP 107 Configure OSPF
DLP 108 Configure RIP
DLP 109 Configure SNMP and Trap Management
DLP 110 Manage Alarms
DLP 111 Plan, Replan, and Unplan Equipment
DLP 112 Lock and Unlock Equipment
DLP 113 Configure the Equipment
DLP 114 NT Redundancy
DLP 115 Create a L2 Terminated Forwarder VLAN
DLP 116 Create a L2 Terminated Router VLAN
DLP 117 Create a C-VLAN
DLP 118 Create an S-VLAN
DLP 119 Create an SC-VLAN
DLP 120 Create an iBridge VLAN
DLP 121 Add Network Interfaces to a VLAN
DLP 122 Create a Forwarding VRF
DLP 123 Create a Router VRF

DLP 124 Create an iBridge User
DLP 125 Create an IPoA User
DLP 126 Create an IPoE User
DLP 127 Create a PPPoE User
DLP 128 Add an LT or the subatm to a VLAN
DLP 129 Create xDSL Profiles
DLP 130 Configure xDSL Bonding
DLP 131 Create an xDSL Bonding Group
DLP 132 Configure Filtering on SHub and subatm
DLP 133 Configure QoS on L2
DLP 135 Configure a QoS Aware VLAN
DLP 136 Configure Multicast
DLP 137 Configure IGMP Proxy
DLP 138 Configure IGMP Snooping
DLP 139 Configure DHCP Relay Agent in iBridge Mode
DLP 140 Configure DHCP Relay Agent in Router Mode
DLP 142 Configure the Security Domain
DLP 143 Configure Local Authentication
DLP 144 Configure RADIUS
DLP 145 Configure 802.1x
DLP 146 Configure PPPoE Relay
DLP 147 Configure PPPoA-PPPoE Relay
DLP 148 Enable the PPPoE Server
DLP 149 Configure PPPoE Profiles
DLP 150 Configure ARP Table Entry

DLP 151 Shut down and Restart the SHub
DLP 152 Reboot the System
DLP 153 Shut down and Restart Individual Equipment
DLP 154 Create a Snapshot Alarm Table
DLP 155 Monitor Alarms
DLP 156 Management of the SHub Database
DLP 157 Manage the SHub Database
DLP 158 Management of the System Database
DLP 159 Management of OSWP
DLP 160 View Version of the SHub Software
DLP 161 Software Licenses Counters
DLP 162 Modify the External Management VLAN
DLP 163 Modifying xDSL Profiles
DLP 164 Ping Command
DLP 165 Traceroute Command
DLP 166 Configure CPE Management
DLP 167 Script Files
DLP 169 Configure Cluster Management
DLP 170 Configure SSH
DLP 171 EMS Management
DLP 172 Create a Default Operator Profile
DLP 173 Create an IPoA Cross-Connect User
DLP 174 Configure Single IP Address
DLP 175 Configure the Default Security Domain

Purpose
This procedure provides the steps to set up a CLI session with the NE.
Procedure
Proceed as follows to set up a CLI session:
1 Enter LOGIN to start up the command line interface.
The logon prompt appears.
2 After the question Would you like a CLI(C) or a TL1 login(T) or TL1 normal
session(N)? [N]:, type C and press Enter.
3 Enter the default user name and password that were provided to you with the
system. If you do not have the default user name and password, contact Alcatel
technical support.
Note 1: For security purposes, change the default user name and password. The
system will prompt you to do this when you log in for the first time.
Note 2: For remote CLI, after you set up the management channel, you can set up
a remote CLI session using Telnet.
DLP 101 Create Operator Profiles and
Instances
Purpose
Before an operator instance can be created, an operator profile must be created
An operator profile determines most of the properties of the operator. It is used to limit the
commands a group of operators can execute to those for which they have the necessary
skills and for which they are responsible.
This document describes the procedure to configure and create an operator profile and
to create an operator instance.
Operator Profile Rules
The following rules apply to an operator profile:
The permissions of an operator profile cannot be changed as long as one operator
belongs to the profile.
The operator profile is assigned at the moment the operator is created. It cannot be
changed afterwards. If an operator profile needs to be changed, then the operators
with this operator profile must first be deleted. Only then can the properties of the
profile be changed.
Password Rules
The following rules apply to a plain text password:
the password must consist of a minimum of 6 and a maximum of 20 characters
the password must contain a minimum of 1 non-alphanumeric character
a new password must be different from the last three passwords
Never specify a new password in an encrypted format, because you can enter any
hexadecimal string that is not necessarily linked to a password. It is almost impossible to
calculate a password from an encrypted string. This method of specifying passwords is
only intended to restore an existing configuration.
An operator will be requested to enter a new password after logging in for the first time
after a password change.
Procedure
Proceed as follows to create an operator instance:
1 Create and configure the operator profile to which the operator will belong with the
following command:
configure system security profile (name)
(no) prompt <Sec::Prompt>
(no) password-timeout <Sec::PasswordTimeout>
(no) terminal-timeout <Sec::InactivityTimeout>
(no) description <Sec::ProfileDesc>
(no) aaa <Sec::Aaa>
(no) atm <Sec::Atm>
(no) alarm <Sec::Alarm>
(no) dhcp <Sec::Dhcp>
(no) equipment <Sec::Equipment>
(no) igmp <Sec::Igmp>
(no) ip <Sec::Ip>
(no) pppoe <Sec::Pppoe>
(no) qos <Sec::Qos>
(no) software-mngt <Sec::Sw>
(no) transport <Sec::Transport>
(no) vlan <Sec::Vlan>
(no) xdsl <Sec::Xdsl>
(no) security <Sec::Security>
2 Create an operator instance with the following command:
configure system security operator (name)
profile <Sec::ProfileName>
password prompt | plain: <Sec::PlainPassword> |
encrypted: <Sec::EncryptedPassword>
(no) description <Sec::OperatorDesc>
(no) more
Configuration example:
configure system security profile (superuser)
no prompt
password-timeout 10
terminal-timeout 30
description superuser
aaa read
atm read
alarm write
no dhcp
equipment write
no igmp
cpeproxy write
ip write
pppoe write
qos write
software-mngt write
transport write
vlan write
xdsl write
security write
configure system security operator (Jim Phelps MI)
profile superuser
password plain: slfdestr&5secs
prompt:#
description:Operator for MI
DLP 102 Configure Management IP
Parameters
Purpose
This document describes the procedure to configure the system management IP
parameters.
Procedure
Proceed as follows to configure the system management IP parameters:
1 The system can receive an IP address either statically by manual configuration or
dynamically via BOOTP. Configure the host IP address of the system with the
following command:
configure system management host-ip-addr bootp |
manual:<Ip::V4Address>/<Ip::PrefixLengthHost>
Note 1: In case of manual configuration of the IP addres: If the system IP address is
not configured (default 0.0.0.0), the users session setup requests are refused.
Note 2: In case of dynamic configuration via BOOTP:
you can view the IP address that you recieved from the server with the following
command:
show transport ip-address
2 Configure the default route of the system with the following command:
configure system management default-route (default-route)
security:
It is NOT advised to use insecure management channels, such as
dual IP address mode.
It is advised to use secure management channels, such as single IP
address mode. This implies closing the insecure management
channels!
3 Configure the SHub IP address with the following command:
configure interface shub ip (vlan-id)
ip-addr <Ip::V4Address> / <Ip::PrefixLengthFull>
4 The default IP address, subnet mask and default gateway will only take only effect
when the configuration is stored and restored.
i Save the changes on the NT disk with the following command:
admin software-mngt shub database save
ii Restart the Shub with the following command:
admin equipment reboot-shub systemreset
Note 1: Restarting the Shub also assigns this IP address to the management VLAN.
Note 2: By default, the system will start up in dual IP address mode. You can set
the mode to single IP address; refer to DLP 103, step 1.
5 Specify the set of ports which are statically allocated as egress ports for the SHub
management VLAN with the following command:
configure vlan shub id 4093 egress-port (port)
6 Specify the egress ports which should transmit packets for the SHub management
VLAN as untagged with the following command:
configure vlan shub id 4093 untag-port (network-port)
7 Configure the bridge port with the following command:
configure bridge shub port (network-port) pvid 4093
8 Save the changes on the NT disk with the following command :
Configuration examples:
Configuration example for dynamic configuration via BOOTP:
configure system management host-ip-addr bootp
configure system management no default-route
configure system shub entry ip ip-cfg-mode dynamic
Configuration example for static configuration via manual configuration:
configure system management host-ip-addr
manual:192.168.203.189/24
configure system management default-route 192.168.203.1
configure interface shub ip 4093 ip-addr 192.168.203.190/24
DLP 103 Configure System
Parameters
Purpose
This document decribes the procedure to configure system parameters on the system
and on the SHub, such as:
System and SHub ID
SNTP
date and time
system clock management
error log handling.
Procedure
Proceed as follows to configure the system parameters:
1 Configure the system ID parameters with the following command:
configure system id <Sys::systemId>
name <PrintableString-0-255>
location <PrintableString-0-255>
contact-person <PrintableString-0-255>
(no) en-snmp-auth-traps <Transport::SnmpAuthTraps>
(no) ether-shape-rate <Sys::etherShapeRate>
mgnt-vlan-id <Vlan::VlanId>
system-mac <Sys::MacAddr> / <Sys::MacAddr> / <Sys::Range>
(no) single-public-ip
2 Configure the SHub ID with the following command:
configure system shub entry id
contact <PrintableString>
location <PrintableString>
3 Configure SNTP on the LT shelf with the following command:
configure system sntp
server-ip-addr <Ip::V4Address>
(no) server-port <Sys::portNumber>
(no) polling-rate <Sys::pollingRate>
(no) enable
4 If necessary, set the system time with the following command:
admin sntp system-time <Sys::Time>
5 Configure the clock source priority scheme and the external clock source (as E1 or
DS1, or 2048Khz) with the following command:
configure system clock-mgmt
(no) priority-scheme <Sys::SysClkSrcPriorityScheme>
(no) ext-source <Sys::SysClkExtSource>
6 Configure error log handling with the following command:
configure error (no) log-full-action <Error::errorLogFullAction>
configure system id 1207 name Test_Asam
location Magabir contact-person Ewan Tendunnit (Phone ext 345)
mgnt-vlan-id 100
system-mac 99:62:12:34:56:5B/98:45:43:6B:35:78/24
single-public-ip
configure system shub entry id
contact Hugh Shuckman (Phone ext 003) location Magabir
configure system sntp server-ip-addr 192.168.234.123
server-port 234 polling-rate 2400 enable
admin sntp system-time <2005-05-31:11:50:30>
configure system clock-mgmt priority-scheme external-local
ext-source khz2048
configure error log-full-action wrap
Purpose
At startup, the ports on the SHub are set to unused. In order to allow a management
connection, one of the ports (typically port 1) should be set to network port. This
procedure provides the steps to set the network ports.
Procedure
Proceed as follows to configure the network interfaces:
1 Set the network port with the following command:
configure interface shub port (network-port)
(no) mode automatic | 10mbps | 100mbps | 1gbps | full | half
(no) port-type <Sys::Type>
(no) mc-flooding
2 Once the port has been configured, the administrative status of the port must be set
to up with the following command:
admin-status <Shub::AdminStatus>
configure interface shub port 1 mode 100mbps:full
port-type network
configure interface shub port 1 admin-status auto-up
DLP 105 Configure Link Aggregation
Usage
Purpose
Link aggregation or trunking is a method of combining physical network links into a single
logical link for increased bandwidth.
The following link aggregation combinations can be used in the NE:
Network links:
For a GE type link, an aggregation can exist of maximum 7 component links.
For an FE type link, an aggregation can exist of maximum 7 component links.
Subtending links:
For a GE type link, an aggregation can exist of maximum 2 component links
For an FE type link, an aggregation can exist of maximum 3 component links.
Note: Link aggregation cannot be used for user links.
This document describes the procedure to configure the link aggregation usage.
General
This node allows to specify the Link Aggregation Group parameters.
A Link Aggregation Group is identified by means of the primary link, also referred to as
aggregator-port. The primary link for an Aggregation Group is the link with the lowest port
number within the group, provided the operational state of the link is UP.
The configuration should be performed for the primary link. The settings configured for
the primary link of the Aggregation Group apply to each and every link that is a member
of the Link Aggregation Group.
The link which is denoted as primary link may change during the lifetime of the
aggregation group. To cope with this phenomenon, the operator is advised to repeat the
configurations described in this procedure for each link of the Aggregation Group. Care
must be taken to configure identical settings for all links within the Aggregation Group.
Procedure
Proceed as follows to configure link aggregation link usage:
1 Specify the Link Aggregation Group parameters with the following command:
configure la aggregator-port (network-port)
name <Shub::AggName>
(no) link-up-down-trap
(no) actor-sys-prio <Shub::LaPortActorSysPriority>
selection-policy <Shub::AggSelectPolicy>
actor-key <Shub::LacpKey>
(no) actor-port-prio <Shub::LaPortActorPortPriority>
(no) active-lacp
(no) short-timeout
(no) aggregatable
lacp-mode <Shub::LacpMode>
Example:
configure la aggregator-port 1 name test_trunk actor-key 12345
actor-port-prio 101 active-lacp short-timeout aggregatable
lacp-mode enable-lacp
configure la aggregator-port 2 name test_trunk actor-key 12345
actor-port-prio 101 active-lacp short-timeout aggregatable
lacp-mode enable-lacp
2 Use the following command to configure Link Aggregation on the SHub. It merely
allows to enable or disable the Link Aggregation feature.:
configure la no disable-lacp
Note: this command is only necessary if the LA system was shut down manually. By
default , Link Aggregation is enabled.
3 If necessary, use the following command to disable Link Aggregation:
configure la disable-lacp
4 View information for a Link Aggregation Group configured on the Service Hub with
the following command:
show la aggregator-info (port)
Example:
show la aggregator-info l
5 View information for a member of a Link Aggregation Group configured on the
Service Hub with the following command:
show la network-port-info (port)
Example:
show la network-port-info l
Purpose
The NE can be configured with several network interfaces. They can be used to connect
the NE to multiple Ethernet switches.
The Rapid Spanning Tree Protocol (RSTP) is a link management protocol that provides
path redundancy while preventing undesirable loops in the network.
This procedure provides the steps to configure RSTP management on the NE.
Procedure
Proceed as follows to configure RSTP management:
1 Specify RSTP settings applicable to the SHub with the following command:
configure rstp
(no) disable-rstp
(no) priority <Shub::RstpPriority>
(no) max-age <Shub::RstpMaxAge>
(no) hello-time <Shub::RstpHello>
(no) forward-delay <Shub::RstpFwdDelay>
(no) version <Shub::RstpVersion>
(no) tx-hold-count <Shub::RstpTxHold>
path-cost-type <Shub::RstpPathCost>
Note: Parameters in this command are settings that apply to the bridge as a whole.
2 Specify RSTP settings applicable to a particular port of the SHubwith the following
command:
configure rstp network-port (port)
(no) priority <Shub::RstpPortPriority>
(no) disable-stp
path-cost <Shub::PortPathCost>
(no) edge-port
(no) admin-p2p <Shub::AdminP2p>
Note: RSTP operates on a port rather than on a VLAN.
3 In addition to the previous configuration command, there is a need to trigger a
specific SHub Port to revert to RSTP protocol, versus stp-compatible protocol. Use
admin bridge rstp port (port)
(clear-det-proto)
Note: RSTP operates on a port rather than on a VLAN.
configure rstp max-age 3000 hello-time 100 forward-delay 2000
tx-hold-count 5
configure rstp network-port 4 priority 160 admin-p2p force-true
admin bridge rstp port 4
Purpose
This procedure provides the steps to configure Open Shortest Path First (OSPF)
management on the NE.
Procedure
Proceed as follows to configure OSPF management:
1 Configure the OSPF parameters with the following command:
configure ospf enable
router-id <Ip::V4Address>
(no) as-border-router
(no) enable-opaque-lsa
(no) overflow-state-it <Ospf::OvrflowIntrvl>
(no) dis-rfc1583-comp
(no) abr-type <Ospf::AbrType>
(no) passive-interface
2 Configure the OSPF area parameters with the following command:
configure ospf area <Ip::V4Address>
3 Configure the OSPF interface parameters with the following command:
configure ospf area (area-id) interface (ip-addr)
(no) disable
(no) router-priority <Ospf::Priority>
(no) passive
(no) itf-type <Ospf::ITFType>
(no) authentication none | md5 | plain : prompt |
plain : plain : <Ospf::Key>
4 Configure the OSPF interface timers with the following command:
configure ospf area (area-id) interface (ip-addr) timers
(no) transit-delay <Ospf::TransDelay>
(no) retransmit-itvl <Ospf::RetransIntvl>
(no) hello-interval <Ospf::HelloIntvl>
(no) dead-interval <Ospf::DeadIntvl>
(no) poll-interval <Ospf::PollIntvl>
5 When MD5 is selected as authentication mode for an OSPF interface, use the
following command to configure the MD5 key:
configure ospf area (area-id) interface (area-id) (ip-addr)
md5-key (index)
key prompt | plain : <Ospf::MD5key> |
encrypted : <Ospf::MD5encryptedKey>
(no) accept-starts <Ospf::MD5startDelay>
(no) generate-starts <Ospf::MD5startDelay>
6 Configure the metric for an OSPF interface with the following command:
configure ospf area (area-id) interface (area-id) (ip-addr)
(no) metric value <Ospf::Metric>
7 Configure the OSPF stub area parameters with the following command:
configure ospf area (area-id) stub
(no) metric-type <Ospf::MetricType>
(no) metric <Ospf::StubMetric>
(no) summary
8 Configure the OSPF NSSA area parameters with the following command:
configure ospf area (area-id) nssa-area
(no) summary
(no) translation <Ospf::Trnsltn>
(no) trans-itvl <Ospf::TrnltnIntvl>
(no) asbr-rtr-trans
9 Configure the redistribution of the OSPF with the following command:
configure ospf redistribution
(no) enable
(no) local
(no) static
(no) rip
10 Configure the redistribution of the OSPF route parameters with the following
command:
configure ospf redistribution route-destination (dest-ip)
(no) metric-type <Ospf::RouteMetricType>
(no) metric <Ospf::RouteMetric>
(no) tag manual : <SignedInteger> | automatic
11 Configure the redistribution enable mask of the OSPF with the following command:
configure ospf redistribution enable-mask (enable-mask)
12 Configure the redistribution disable mask of the OSPF with the following command:
configure ospf redistribution disable-mask (disable-mask)
configure ospf enable router-id 192.168.123.123
as-border-router no passive-interface
configure ospf area 192.168.195.183
configure ospf area 192.168.195.183 interface 192.168.122.1
router-priority 10 authentication md5
timers retransmit-itvl 10 dead-interval 20 poll-interval 60
md5-key 1 key prompt
metric value 256
configure ospf area 192.168.195.183 stub metric 32164
configure ospf area 192.168.195.183 nssa import nssa
translation always asbr-rtr-trans
configure ospf redistribution enable local rip
configure ospf redistribution route-destination 192.168.100.99
metric-type as-ext-type1 tag automatic
configure ospf redistribution enable-mask rip
configure ospf redistribution disable-mask static
Purpose
This procedure provides the steps to configure Routing Information Protocol (RIP)
management on the NE.
Limitations
The following limitations apply:
RIP support is only offered for IPoA interfaces.
Only plain RIP messages will be handled, the triggered RIP protocol is not supported.
RIP message propagation is enabled/disabled on the user gateway interface of the
SHub, not per user PVC.
Procedure
Proceed as follows to configure RIP management:
1 Configure the maximum number of peers that can be simultaneously in
conversation with the RIP2 with the following command:
configure rip max-peer <Rip::Rip2Peer>
2 Configure RIP distribution with the following command:
configure rip redistribution
(no) enable
(no) default-metric <Rip::RouteMetric>
(no) local
(no) static
(no) ospf
3 Configure RIP interface parameters with the following command:
configure rip interface (ip-addr)
(no) authentication none | md5 | plain : prompt |
plain : plain : <Rip::Key>
default-metric <Rip::DefMetric>
(no) send <Rip::ConfSend>
(no) receive <Rip::ConfRcv>
(no) split-horizon <Rip::SpltHorizon>
4 Configure the RIP interface timers with the following command:
configure rip interface (ip-addr) timers
(no) update-timer <Rip::UpdateTmr>
(no) route-age-out <Rip::RouteAgeTmr>
(no) junk-collection <Rip::GrbTmr>
5 If the MD5 authentication method is selected for a RIP interface, then the MD5 key
can be configured with the following command:
configure rip interface (ip-addr) md5-key (index)
key prompt | plain : <Rip::MD5key>
starts <Rip::MD5startDelay>
expires <Rip::MD5expiryDelay>
6 Add or delete a route aggregation with the following command:
configure rip (no) aggregation (ip-addr)
7 Define a route map with the following command:
configure rip route-map (vlan-id) sub-index <Rip::SubIndex>
(no) direction <Rip::RouteMapDirection>
(no) deny
configure rip max-peer 50
configure rip redistribution enable default-metric 2
configure rip interface 192.168.105.105 default-metric 5
configure rip interface 192.168.105.105 timers update-timer 20
configure rip interface 192.168.105.105 md5-key 3 key prompt
starts now expires never
configure rip aggregation 192.168.105.105/16
configure rip route-map 200 sub-inex 5 ip-addr 192.168.105.105/16
DLP 109 Configure SNMP and Trap
Management
Purpose
SNMP
SNMP uses community names as a kind of password without user name to verify if a
request may be executed or not.
Note:
There must be at least one community with read-write privileges
An existing community cannot be modified.
Trap Management
An SNMP manager will receive traps when an event occurs in the system.
The manager can be easily flooded by events in the case where something happens with
the system. It can be specified in which traps the manager is interested (trap filtering) and
how the traps must be spread in time (trap shaping).
Traps that can not be delivered will be dropped:
cold-start
link-down
link-up
auth-failure
change-occurred
init-started
license-key-change-occurred
You can also set the minimum priority to be reported when a trap occurs. The priority can
be urgent, high, medium, or low.
security:
It is NOT advised to use insecure management channels such as
SNMPv1 or SNMPv2.
If SNMPv1/2 is used anyway, it is advised not to use community string
= public
It is advised to use secure management channels such as SNMPv3.
Procedure
Proceed as follows to configure SNMP and trap management:
1 Configure a view of a subtree with the following command:
configure system security snmp view (notify-view)
subtree <Snmp::ViewSubtree>
type <Snmp::FilterType>
2 Configure the SNMP community name with the following command:
configure system security snmp community (name)
host-address <Ip::V4Address>/<Ip::PrefixLengthFull>
(no) context <Transport::Context>
(no) privilege <Snmp::CommunityPrivilege>
(no) read-view <Snmp::ViewName>
(no) write-view <Snmp::ViewName>
(no) notify-view <Snmp::ViewName>
3 Do one of the following:
a If SNMP version 1 or version 2 is used, continue with step 7.
b If SNMP version 3 is used, continue with step 4.
4 Configure an SNMPv3 group with the following command:
configure system security snmp group (name)
security-level <Snmp::SecurityLevel>
context single : nt | shub | epon | all
(no) read-view <Snmp::ViewName>
(no) write-view <Snmp::ViewName>
(no) notify-view <Snmp::ViewName>
5 Configure an SNMPv3 user with the following command:
configure system security snmp user (name)
(no) authentication none | [md5|sha1]:prompt
| [md5|sha1]:plain:<Sec::PlainPassword>
| [md5|sha1]:encrypted:<Snmp::AuthEncryptedKey>
(no) privacy none | des:prompt | des:plain:<Sec::PlainPassword>
| des : encrypted : <Snmp::PrivacyEncryptedKey>
(no) public <Snmp::Identifier>
6 Map an SNMPv3 user to an SNMPv3 group with the following command:
configure system security snmp map-user-group (name)
group-name <Snmp::GroupName>
7 Configure a notify view with the following command:
configure system security snmp notify-view (notify-view)
subtree <Snmp::ViewSubtree>
type <Snmp::FilterType>
8 Configure an SNMP notification profile with the following command:
configure system security snmp notify-profile (name)
snmp-version v1 : <Snmp::CommunityString>
| v2 : <Snmp::CommunityString>
| v3 : <Snmp::SecurityName> : none | authentication
| privacy-and-auth
9 Configure a filter for a notification profile with the following command:
configure system security snmp notify-profile (name)
filter notify-view <Snmp::ViewName>
10 Configure an SNMP element manager with the following command:
configure system security snmp manager (name)
destination <Snmp::IpAddress> : <Snmp::AddressPort>
notify-profile <Snmp::NotifyProfile>
(no) nt
(no) shub
(no) epon
11 Configure community names on the SHub with the following command:
configure system security snmp shub community (index)
(no) privilege <Snmp::SHubCommunityPrivilege>
(no) ip-addr <Ip::V4Address>
12 Configure the SNMP trap manager with the following command:
configure trap manager <Ip::V4Address> : <Trap::Port>
(no) priority <Trap::Priority>
(no) cold-start-trap
(no) link-down-trap
(no) link-up-trap
(no) auth-fail-trap
(no) change-trap
(no) init-started-trap
(no) lic-key-chg-occr
(no) phys-line-trap
(no) eqpt-change-trap
(no) success-set-trap
(no) other-alarm-trap
(no) warning-trap
(no) minor-trap
(no) major-trap
(no) critical-trap
(no) redundancy-trap
(no) eqpt-prot-trap
(no) max-per-window <Trap::WindowCount>
(no) window-size <Trap::WindowSize>
(no) max-queue-size <Trap::QueueSize>
(no) min-interval <Trap::Interval>
(no) min-severity <Alarm::alarmSeverity>
13 Configure an SNMP manager of the SHub with the following command:
configure trap shub manager <Ip::V4Address> : <Trap::Port>
(no) cold-start-trap
(no) auth-fail-trap
(no) change-trap
(no) community-string <PrintableString-0-255>
(no) snmp-version <Snmp::SHubVersion>
(no) min-severity <Snmp::SHubAlarmSeverity>
14 Configure the trap definition table with the following command:
configure trap definition (name) priority <Trap::trapPriority>
15 If necessary, reset the trap table with the following command:
admin trap manager <Ip::V4Address> : <Trap::Port>
reset-trap-buffer
configure system security snmp view TargetParams
subtree snmpTargetParamsRowStatus.97.97.97 type include
configure system security snmp community public
host-address 192.168.119.117/24
configure system security snmp group Group1
security-level privacy-and-auth context all
configure system security snmp user User1Gr1
authentication none md5:prompt
privacy none des:prompt
configure system security snmp map-user-group UserGR1
group-name Group1
configure system security snmp notify-view TargetParams
subtree snmpTargetParamsRowStatus.97.97.97 type include
configure system security snmp notify-profile Notif01
snmp-version v3 : SecureName : privacy-and-auth
configure system security snmp notify-profile Notif01
filter notify-view TargetParams
configure system security snmp manager Manager01
destination 192.168.119.117:6666 notify-profile Notif01
configure system security snmp shub community (4)
name Public4 privilege read-write
configure trap manager 192.168.119.118:32456
cold-start-trap auth-fail-trap eqpt-change-trap warning-trap
minor-trap major-trap critical-trap min-severity warning
configure trap shub manager 192.168.119.118 : 32456
auth-fail-trap change-trap snmp-version v1 min-severity minor
configure trap definition auth-failure priority high
admin trap manager 192.168.119.118 : 32456 reset-trap-buffer
Purpose
This procedure provides the steps to manage the alarms in the NE.
Alarm management includes:
Management of the alarm logs
Viewing the alarm logs
Viewing the current alarms
Configuring and viewing of an alarm snap-shot
Configuring the SHub alarm parameters
Configuring and viewing of an SHub alarm snap-shot.
Procedure
Proceed as follows to manage alarms:
1 Configure the alarm log settings (alarm severity level, action to be taken when the
log buffer is full, minimum severity level for non-interface alarms) with the following
command:
configure alarm
log-sev-level <Alarm::alarmSeverity>
log-full-action <Alarm::alarmLogFullAction>
non-itf-rep-sev-level <Alarm::alarmSeverity>
2 Configure the management of local alarm entries with the following command:
configure alarm entry (index)
severity <Alarm::alarmSeverity>
(no) service-affecting
(no) reporting
(no) logging
3 Configure the the action to be taken when the alarm log buffer is completely full with
configure alarm delta-log
indet-log-full-action <Alarm::alarmDeltaLogFullAction>
warn-log-full-action <Alarm::alarmDeltaLogFullAction>
minor-log-full-action <Alarm::alarmDeltaLogFullAction>
major-log-full-action <Alarm::alarmDeltaLogFullAction>
crit-log-full-act <Alarm::alarmDeltaLogFullAction>
Note: If the action is set to Wrap, then older log records are overwritten by recent
ones. If the action is set to Halt, then logging is stopped until the log buffer is reset.
4 Configure the interface management parameters with the following command:
configure interface port (port)
(no) (admin-up)
(no) (link-updown-trap)
(no) user <Itf::asamIfExtCustomerId>
(no) severity <Itf::asamIfExtAlmReportingSeverity>
5 Configure the default severity for an alarm on a type of interface with the following
command:
configure interface alarm (index)
(no) default-severity
<Itf::asamIfExtAlmReportingSeverityDefault>
6 View the status of the different alarm logs with the following commands:
show alarm log table | equipment | eqpt-holder | plug-in-unit |
atm | ether-itf | sw-mgmt | xdsl misc | xdsl near-end |
xdsl far-end | tca-xdsl | eo-conversion | authentication|
bonding-group | redundancy | custom | sfp | llu-relay | atm-fent
(index)
Note: The output will differ from command to command. Refer to the CLI Commands
Guide for detailed information.
7 View the current status of the different alarms with the following commands:
show alarm current table | equipment | eqpt-holder | plug-in-unit
| atm | ether-itf | sw-mgmt | xdsl | tca-xdsl | eo-conversion |
authentication| bonding-group | redundancy | custom | sfp |
llu-relay | atm-fent (index)
Note: The output will differ from command to command. Refer to the CLI Commands
Guide for detailed information.
8 Make an alarm snapshot for a particular severity level with the following command:
admin alarm snap-shot (start)
9 View the alarm snapshot with the following command:
show alarm snap-shot table | equipment | eqpt-holder |
plug-in-unit | atm | ether-itf | sw-mgmt | xdsl | tca-xdsl |
eo-conversion | authentication | bonding-group | ipox | redundancy
| custom | sfp | llu-relay | ulc (index)
10 Stop the alarm snapshot with the following command:
admin alarm snap-shot stop
11 Configure the alarm SHub parameters with the following command:
configure alarm shub entry (index)
severity <Alarm::alarmSeverity>
(no) service-affecting
(no) reporting
12 Make an alarm snapshot on the SHub for a particular severity level with the following
command:
admin alarm shub snap-shot
start:<Severity>:<Alarm::alarmSnapShotOwner>
13 View the alarm snapshot with the following command:
show alarm shub snap-shot
14 Stop an alarm snapshot on the SHub with the following command:
admin alarm shub snap-shot stop
15 Clear log table - logging will start from index 1
admin alarm clr-logging
configure alarm log-sev-level warning
log-full-action wrap non-itf-rep-sev-level minor
configure alarm entry xdsl-act-not-feas severity major
service-affecting reporting logging
configure alarm delta-log indet-log-full-action wrap
warn-log-full-action wrap minor-log-full-action wrap
major-log-full-action halt crit-log-full-act halt
configure interface port xdsl-line:1/1/5/12
severity minor
configure interface alarm (index)
default-severity minor
show alarm log authentication (index)
show alarm current table authentication (index)
admin alarm snap-shot start:critical:Operator13
show alarm snap-shot table authentication (index)
admin alarm snap-shot stop
configure alarm entry fan severity warning
no service-affecting no reporting
admin alarm shub snap-shot start:critical:Operator13
show alarm shub snap-shot
admin alarm shub snap-shot stop
admin alarm clr-logging
DLP 111 Plan, Replan, and Unplan
Equipment
Purpose
This document describes the procedure to be used to to plan, replan, and unplan
equipment. Planning and replanning equipment uses the same command for configuring
equipment.
Procedure
Proceed as follows to plan, replan, and unplan equipment:
1 Plan or replan a shelf with the following command:
configure equipment shelf <Eqpt::Rack> / <Eqpt::Shelf>
class <Equipm::ShelfClass>
planned-type (Type)
unlock
2 Unplan a shelf with the following command:
no planned-type
3 Replan a plug-in unit other than an applique in any given slot position with the
following command:
configure equipment slot <Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::Slot>
planned-type <Type>
4 Unplan a plug-in unit other than an applique in any given slot position with the
following command:
no planned-type
configure equipment shelf 1/1 class main-ethernet
configure equipment shelf 1/1 class main-ethernet
no planned-type
configure equipment slot 1/1/5 planned-type LSM
configure equipment slot 1/1/5 no planned-type
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:
no unlock
Example:
configure equipment slot 1/1/5 no unlock
2 Unlock a plug-in unit with the following command:
unlock
Example:
configure equipment slot 1/1/5 unlock
Purpose
The system will auto-configure a number of equipment items and detect the presence of
the equipment at startup. It may therefore not be necessary to configure or reconfigure
all equipment. The procedure in this section is a guideline only.
Refer to the CLI Commands and Messages document for a complete description of the
commands used in this procedure.
Procedure
Proceed as follows to configure the NE equipment:
1 Configure the description of the system with the following command:
configure equipment gebc
(no) description <Description>
2 Configure the rack with the following command:
configure equipment rack <Eqpt::Rack>
(no) description <Description>
3 Configure the subrack or shelf with the following command:
(no) planned-type (Type)
(no) description (Description)
4 Use any of the following commands to view and verify the configuration of the
system:
show equipment gebc
This command shows the system configuration and status. This configuration is
fixed and hardcoded.
show equipment rack (rack)
This command shows the rack configuration and status.
show equipment shelf (shelf)
This command shows the shelf configuration and status.
show equipment slot (slot)
This command shows the configuration and status of all slots.
show equipment applique (applique)
This command shows the configuration and status of all appliques.
configure equipment gebc description Magabir Plant
configure equipment rack 1 no description
configure equipment shelf 1/1 planned-type mlts-b
description Testshelf_Lab class main-ethernet
show equipment rack 1
show equipment shelf 1/1
show equipment slot 1/1/5
show equipment applique 1/1/5
Purpose
The NE supports line protection and Equipment Protection Switching (EPS). EPS is a
mechanism that provides protection against internal failure of the active NT board, if a
second redundant NT board is equipped (NT redundancy).
For EPS, the concept of protection group is used.
A protection group is a group composed of protection and working elements, where the
protection element takes over the functionalities of a working element in case it is needed
(for example, failure of the working element).
For NT redundancy, the protection group consists of both protection elements. Each
element represents one NT board. In general, protection elements are defined on
slot-level. The protection group and elements are created implicitly by the system, as part
of the default configuration.
Refer to the CLI Commands and Messages document for a complete description of the
commands used in this procedure.
Procedure
The following commands can be used to configure NT redundancy or to view the NT
redundancy configuration:
1 Configure the administrative status of the protection group with the following
command:
configure equipment protection-group (index)
(no) admin-status <Equipm::PortGroupAdminStatus>
(no) eps-quenchfactor <TimeTicks>
Note: The default administrative status of the protection group is unlocked.
2 Configure the redundancy control status of a protection group element with the
following command:
configure equipment protection-element (index)
(no) redcy-ctrl-status <Equipm::ProtElementRedcyCtrlStatus>
3 View the protection group configuration parameters with the following command:
show equipment protection-group (prot-group-id)
4 View the protection element configuration parameters with the following command:
show equipment protection-element (slot-id)
configure equipment protection-group 1 admin-status unlock
configure equipment protection-element 1/1/3
redcy-ctrl-status forced_active
DLP 115 Create a L2 Terminated
Forwarder VLAN
Purpose
In the forwarder mode, the LTs operate as IP forwarder and the SHub operates as a
bridge.
For the LTs, the following applies:
The user-gateway interface is auto-created by the system when the operator
configures the VRF.
Subnets of the static users must be configured on the user-gateway interface.
Numbered IP interface (trusted or un-trusted) is configured on each network VLAN.
For the SHub, the following applies:
The SHub operates as a bridge.
IP addresses that are configured on the network VLANs are owned by the SHub.
Figure 11500-1: L2 Terminated Forwarder VLAN
This procedure provides the steps to configure a Layer 2 terminated forwarder VLAN.
SHub
VRF
VB
IPoE
(P-VLAN)
PPPoE/PPPoA, IPoE/IPoA
always untagged
ISP
P-VLAN
P-VLAN
LT
VRF

ARP
Proxy

LT

IPoE/A
Interface
DHCP
Relay
PPPoE/A Session
PPPoE/A
Interface
VRF
ARP
Proxy
IPoE/A Session
ARP
Proxy
P-VLAN
DHCP
Relay
P-VLAN
ISP
IPoE
(P-VLAN)
Prerequisites
The following prerequisites must be fulfilled before a Layer 2 terminated forwarder VLAN
can be configured:
A forwarder VRF; see DLP 122.
Note: In the configuration example, it is assumed that the VRF index of the forwarder
VRF is 16.
Procedure
Proceed as follows to configure a L2 terminated VLAN:
1 Create a L2-terminated VLAN on the NT with the following command:
configure vlan id <Vlan::UVlanIndex>
name <Vlan::AdminString>
mode layer2-terminated
(no) priority <Vlan::Priority>
(no) broadcast-frames
(no) protocol-filter <Vlan::ProtGroup>
2 Create a bridged VLAN on the SHub with the following command:
configure vlan shub id (vlanid)
(no) name <Vlan::AdminString>
mode residential-bridge
(no) mac-move-allow
3 Create an unnumbered network IP interface on the IPoX interface with the following
command:
configure ip vrf (vrf-index) network-itf (vlanid)
(no) arp-policy <Vrf::ArpPolicy>
unnumbered
4 Define the gateway IP interface with the following command:
configure ip vrf (vrf-index) gateway-itf
ip-address (ip-address)
5 Add the IP route with the following command:
configure ip vrf (index) route-dest (dest-ip-address)
next-hop direct : user-port:<Eqpt::Rack>/<Eqpt::Shelf>/
<Eqpt::LtSlot>/<Eqpt::Port>:<Atm::DefaultVpi>:
<Atm::DefaultVci>
| <Ip::V4Address>:network:vlan:stacked:
<Vlan::SVlanIndex>:<Vlan::CVlanIndex>
| <Ip::V4Address>:network:vlan:<Vlan::UVlanIndex>
| <Ip::V4Address>:network:any
| network:stacked:<Vlan::SVlanIndex>:<Vlan::CVlanIndex>
| direct: network:<Vlan::UVlanIndex>
| direct:user-bridgeport:<Eqpt::Rack>/<Eqpt::Shelf>/
<Atm::DefaultVci>
configure vlan id 100 name "ISPforwVLAN" mode layer2-terminated
configure vlan shub id 100 name ISPforwVLAN
configure ip vrf 16 network-itf 100 arp-policy trusted unnumbered
configure ip vrf 16 gateway-itf ip-address 192.168.128.1/21
configure ip vrf 16 route-dest 0.0.0.0/0 next-hop
192.168.128.1:network:vlan:100
DLP 116 Create a L2 Terminated
Router VLAN
Purpose
In the router mode, the LTs operate as an IP forwarder and the SHub operates as a
router.
Between the LTs and the SHub, one VLAN per VRF must be created to indicate the VRF
to which the IP packets belong. This VLAN is called as V-VLAN (VRF VLAN).
For the LTs, the following applies:
The user-gateway interface is auto-created by the system when the operator
configures the VRF.
Subnets of the static users must be configured on the user-gateway interface.
At least one IP address must be configured on the user-gateway interface.
Only one network VLAN (V-VLAN) can be created since LTs will have only one
network interface connected to LANX as gateway.
An unnumbered IP interface (trusted) is created on the V-VLAN since LTs don't have
an IP address on the network interface towards the SHub.
For the SHub, the following applies:
IP interfaces are created on the network VLANs towards the edge routers. IP interface
addresses are seen as the Next-Hop addresses in the downstream from edge routers
to Litespan.
User-gateway interface is the interface towards the users and it is created on V-VLAN.
IP address configured on the user-gateway interface represents the gateway IP
address for the users, and subnet configured on the user-gateway interface
represents the subnet of the users.
Figure 11600-1: L2 Terminated Router VLAN
This procedure provides the steps to configure a Layer 2 terminated router VLAN.
Prerequisites
The following prerequisites must be fulfilled before a Layer 2 terminated router VLAN can
be configured:
A router VRF; see DLP 123.
Note: In the configuration example, it is assumed that the index of the router VRF of
the LT is 16 and the index of the router VRF on the SHub is 5.
IPoE
(V-VLAN per VR)
IPoE
(P-VLAN)
PPPoE/PPPoA, IPoE/IPoA
always untagged
ISP
P-VLAN
V-VLAN
LT
VRF

ARP
Proxy

LT

SHub
ARP
VRF
IPoE/A
Interface
DHCP
Relay
Routing Protocols
(OSPF, RIPv2)
PPPoE/A Session
PPPoE/A
Interface
VRF
ARP
Proxy
IPoE/A Session
ARP
Proxy
V-VLAN
DHCP
Relay
Procedure
Proceed as follows to configure a Layer 2 terminated router VLAN:
1 Create a virtual L2-terminated VLAN on the LT with the following command:
2 Create a virtual VLAN on the SHub with the following command:
mode v-vlan
(no) mac-move-allow
3 Configure an egress port for the virtual VLAN on the SHub
configure vlan shub id (vlanid) egress-port
lt : <Eqpt::Rack> / <Eqpt::Shelf> / <Eqpt::Slot> | subatm
4 Create an IP interface on the virtual VLAN on the SHub with the following command:
configure interface shub vlan-id (vlanid)
5 Attach the IP interface to a VRF:
configure interface shub ip (vlanid) vrf-id <Vrf::VrfIndex>
6 Configure the IP address of the internal IP interface with the following command:
configure interface shub ip (vlanid)
ip-address <Ip::V4Address>/<Ip::PrefixLengthFull>
7 Set the administrative state of the VLAN interface to UP:
configure interface shub vlan-id (vlanid) admin-status up
8 Create a L2 network terminated VLAN on the Shub with the following command:
mode layer2-term-nwport
(no) mac-move-allow
9 Configure an egress port for the L2 network terminated VLAN on the SHub with the
following command:
network:<SHub:NetworkPort>
10 Create an IP interface on the L2 network terminated VLAN with the following
command:
configure interface shub vlan-id (vlanid)
11 Attach the IP interface to a VRF with the following command:
configure interface shub ip (vlanid) vrf-id <Vrf::VrfIndex>
12 Configure the IP address of the external IP interface with the following command:
configure interface shub ip (vlanid) ip-address (ip-address)
13 Set the administrative state of the VLAN interface to UP with the following
command:
configure interface shub vlan-id (vlanid) admin-status up
14 Create an unnumbered IP interface on the IPoX interface with the following
command:
configure ip vrf (vrf-index) network-itf (vlanid)
(no) arp-policy <Vrf::ArpPolicy>
unnumbered
15 Configure the gateway IP interface with the following command:
configure ip vrf (vrf-index) gateway-itf
ip-address (ip-address)
16 Add the IP route with the following command:
next-hop direct : user-port:<Eqpt::Rack>/<Eqpt::Shelf>/
<Atm::DefaultVci>
| <Ip::V4Address>:network:vlan:stacked:
| <Ip::V4Address>:network:vlan:<Vlan::UVlanIndex>
| <Ip::V4Address>:network:any
| network:stacked:<Vlan::SVlanIndex>:<Vlan::CVlanIndex>
| direct: network:<Vlan::UVlanIndex>
| direct:user-bridgeport:<Eqpt::Rack>/<Eqpt::Shelf>/
<Atm::DefaultVci>
configure vlan id 200 name "ISProutingVLAN"
configure vlan shub id 201 name ISPvvlanSHub mode v-vlan
configure vlan shub id 201 egress-port lt:1/1/4
configure interface shub vlan-id 201
configure interface shub ip 201 vrf-id 5
configure interface shub vlan-id 201 admin-status up
configure vlan shub id 202 name ISProutingVLAN
mode layer2-term-nwport
configure vlan shub id 202 egress-port network:2
configure interface shub vlan-id 202
configure interface shub ip 202 vrf-id 5
configure ip vrf 16 network-itf 200 arp-policy trusted unnumbered
configure ip vrf 16 gateway-itf ip-address 192.168.1.1/16
configure ip shub vrf 5 route-dest 192.168.100.1/24 next-hop
192.168.1.10 vlan-id 202
Purpose
This is the most straightforward VLAN cross-connect model where a single VLAN ID at
the EMAN side is associated with a given PVC at the user side. Any kind of traffic issued
by the subscriber is passed transparently towards the network using the selected VLAN
ID.
Cross-connect VLANs can be enabled to be protocol aware for IGMP and 802.1x and
support the configuration of DHCP Opt82 and PPPoE relay.
This procedure provides the steps to configure a Customer VLAN (C-VLAN).
Prerequisite
The following prerequisite must be fulfilled before a C-VLAN can be configured:
Procedure
Proceed as follows to configure a C-VLAN:
1 Create a C-VLAN:
i Create a C-VLAN on the LT with the following command:
mode cross-connect
(no) pppoe-relay
(dhcp-opt-82)
circuit-id <Vlan::CircuitId>
remote-id <Vlan::RemoteId>
ii Create a C-VLAN on the SHub with the following command:
configure vlan shub id <Vlan::UVlanIndex>
mode cross-connect
2 Create and configure an SHub network port:
i Create and configure an SHub network port with the following command:
mode automatic | [10mbps | 100mbps | 1gbps] : full | half
port-type network
(no) mc-flooding
ii Change the administrative status of the SHub network port with the following
command:
configure interface shub port (network-port) admin-status up
iii Configure the SHub network egress port on the network with the following
command:
network:<Shub::NetworkPort>
iv Configure the SHub network egress port on the LT with the following
command:
lt:<Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::LtSlot> | subatm
3 Create an xDSL line:
i Create an xDSL line with the following command:
configure xdsl line (if-index)
service-profile none | <Xdsl::ProfilePointer>
| name: <PrintableString>
spectrum-profile none | <Xdsl::ProfilePointer>
| name : <PrintableString>
(no) op-mode <Xdsl::OpModeTypeLinePreDef>
(no) carrier-data-mode <Xdsl::CarrierDataMode>
(no) admin-up
(no) bonding-mode <Xdsl::BondingMode>
ii Configure the xDSL line with the following command:
configure interface port
xdsl-line:<Eqpt::Rack>/<Eqpt::Shelf>/
<Eqpt::LtSlot>/<Eqpt::Port> admin-up
iii Do one of the following:
- To create an ADSL line, continue with step v
- To create a VDSL or VDSL2 line, continue with step vii.
iv Do one of the following:
- To create an ATM PVC in subatm, continue with step v.
- To create an ATM PVC in LT, continue with step vi.
v Create an ATM PVC with the following command:
configure atm pvc (port-index)
(no) admin-down
(no) aal5-encap-type llc-snap | vc-mux-bridged | automatic
vi Create an ATM PVC in subatm with the following command:
configure subatm unicast-port (port-index)
(no) accept-frame-type
(no) block-upmcast
(no) customer-id
(no) antispoof-enable
(no) service-category
(no) port-description
(no) admin-enable
(no) mac-learn-off
(no) max-unicast-mac
(no) pvid
default priority
vii Create a bridge port with the following command:
configure bridge port isam:(port) | subatm (port)
viii Associate a VLAN with the port with the following command:
configure bridge port isam:(port) | subatm (port) vlan-id
(index)
(no) tag
ix Set the PVID with the following command:
configure bridge port isam:(port) | subatm (port) pvid
<Vlan::UVlanIndex>
1. Example for ADSL line:
configure vlan id 300 name "ISP_C_VLAN" mode cross-connect
configure vlan id 300 dhcp-opt-82 circuit-id customer-id
remote-id customer-id
configure vlan shub id 300 name "ISP_C_VLAN" mode cross-connect
configure interface shub port 2 port-type network
configure interface shub port 2 admin-status up
configure xdsl line 1/1/5/12 service-profile 7
spectrum-profile 3 admin-up
configure interface port xdsl-line: 1/1/5/12 admin-up
configure atm pvc 1/1/5/12:8:35 aal5-encap-type
vc-mux-bridged-8023
configure bridge port isam:1/1/5/12:8:35
configure bridge port isam:1/1/5/12:8:35 vlan-id 300
configure bridge port isam:1/1/5/12:8:35 pvid 300
2. Example for VDSL or VDSL2 line:
configure vlan id 300 dhcp-opt-82 circuit-id customer-id
configure interface port xdsl-line 1/1/5/12 admin-up
configure bridge port isam:1/1/5/12
configure bridge port isam:1/1/5/12 vlan-id 300
configure bridge port isam:1/1/5/12 pvid 300
3. Example for subatm port:
configure vlan id 300 dhcp-opt-82 circuit-id customer-id remote-id
customer-id
configure subatm unicast-port 2:32 service-category ubr:8000
admin-enable enable-admin
configure bridge port subatm 2:32
configure bridge port subatm 2:32 vlan-id 300
configure bridge port subatm 2:32 pvid 300
Purpose
In this mode, the Service Provider VLAN (S-VLAN) ID at the EMAN side is associated
with a single subscriber interface at the user side. The C-VLANs carried within the
S-VLAN are passed transparently to the end user. This allows the end user to specify its
own end-to-end connectivity, while remaining transparent for the EMAN.
The NE acts as an S-VLAN aware bridge, with the restriction that only one subscriber
interface can be attached. Forwarding is only done based on the S-VLAN forwarding
context. The forwarding is transparent for the C-VLANs. Frames on the subscriber
interface may or may not have an S-VLAN tag. In case of an absent S-VLAN tag (that is
for C-VLAN tagged and untagged/priority tagged frames), the subscriber interfaces
pre-configured S-VLAN ID will be assigned.
This procedure provides the steps to configure an S-VLAN.
Procedure
Proceed as follows to configure an S-VLAN:
1 Create an S-VLAN:
i Create an S-VLAN on the LT with the following command:
configure vlan id
stacked:<Vlan::SVlanIndex>:<Vlan::CVlanIndex>
mode cross-connect
(no) pppoe-relay
(dhcp-opt-82)
circuit-id <Vlan::CircuitId>
remote-id <Vlan::RemoteId>
ii Create and configure an SHub network port with the following command:
mode cross-connect
mode automatic | 10mbps | 100mbps | 1gbps | full | half
port-type network
(no) mc-flooding
command:
command:
command:
service-profile <AsamProfilePointer>
spectrum-profile <AsamProfilePointer>
(no) admin-up
- To create a VDSL or VDSL 2 line, continue with step vii
- To create an ATM PVC in subatm, continue with step v
- To create an ATM PVC in LT, continue with step vi
(no) admin-down
(no) block-upmcast
(no) customer-id
(no) admin-enable
(no) mac-learn-off
(no) pvid
default priority
configure bridge isam:(port) | subatm(port)
vlan-id stacked :<Vlan::SVlanIndex>:<Vlan::CVlanIndex>
(no) tag
pvid stacked :<Vlan::SVlanIndex>:<Vlan::CVlanIndex>
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 isam:(port) | subatm(port)
pvid stacked :<Vlan::SVlanIndex>:4097
configure vlan id stacked:400:0 name "IPS_S_VLAN"
mode cross-connect configure vlan id stacked:400:0 dhcp-opt-82
circuit-id customer-id
configure vlan shub id 400 name "ISP_S_VLAN" mode cross-connect
configure atm pvc 1/1/5/12:8:35 aal5-encap-type vc-mux-bridged
configure bridge port isam:1/1/5/12:8:35 vlan-id stacked:400:0
configure bridge port isam:1/1/5/12:8:35 pvid stacked:400:0
2. Example for VDSL or VDSL 2 line:
configure bridge port isam:1/1/5/12 vlan-id stacked:400:0
configure bridge port isam:1/1/5/12 pvid stacked:400:0
configure vlan shub id 400 egress-port subatm
configure bridge port subatm 2:33 vlan-id 300
configure bridge port subatm 2:33 pvid 300
Purpose
The basic VLAN cross-connect mode suffers from the fact that the number of VLAN
identifiers is limited to 4K. Since the VLAN is a EMAN wide identifier, one ends up with a
scalability issue: there cannot be more than 4K end users connected to the whole EMAN.
To solve this issue, two VLANs are stacked and the cross-connection is then performed
on the combination (S-VLAN, C-VLAN) allowing to theoretically reach up to 16M end
users.
The NE acts as a C-VLAN aware bridge, with the restriction that only one subscriber
interface can be attached. Frames on the subscriber interface may be C-VLAN tagged or
untagged/priority tagged. In case of C-VLAN tagged frames, a check will be performed
on the received C-VLAN ID, while the subscriber interfaces preconfigured S-VLAN will
be assigned. In case of untagged/priority tagged frames, the subscriber interfaces
pre-configured C-VLAN and S-VLAN will be assigned.
This procedure provides the steps to configure or delete a stacked VLAN.
Procedure
Proceed as follows to configure an SC-VLAN:
1 Create an SC-VLAN:
i Create an S-VLAN on the LT with the following command:
configure vlan id stacked
ii Create a stacked SC-VLAN on the LT with the following command:
configure vlan id stacked
mode cross-connect
iii Create an cross-connect VLAN on the SHub with the following command:
mode cross-connect
mode automatic | 10mbps | 100mbps | 1gbps | full | half
port-type network
(no) mc-flooding
command:
command:
command:
(no) admin-up
- To create a VDSL or VDSL 2 line, continue with step vii
- To create an ATM PVC in subatm, continue with step v
- To create an ATM PVC in LT, continue with step vi
(no) admin-down
(no) block-upmcast
(no) customer-id
(no) admin-enable
(no) mac-learn-off
(no) pvid
default priority
configure bridge port isam:(port) | subatm(port) vlan-id
(index)
(no) tag
configure bridge port isam:(port) | subatm(port) pvid
<Vlan::UVlanIndex> | stacked
:<Vlan::SVlanIndex>:<Vlan::CVlanIndex>
configure vlan id stacked:500:0 name "ISP_SC_VLAN"
mode cross-connect
configure vlan shub id 500 name "ISP_SC_VLAN" mode cross-connect
configure bridge port isam:1/1/5/12:8:35 vlan-id stacked:500:600
configure bridge port isam:1/1/5/12:8:35 pvid stacked:500:600
2. Example for VDSL or VDSL 2 line:
mode cross-connect
configure bridge port isam:1/1/5/12 vlan-id stacked:500:600
configure bridge port isam:1/1/5/12 pvid stacked:500:600
mode cross-connect
configure subatm unicast-port 2:34 vlan-id stacked:500:600
configure bridge port subatm 2:34 pvid stacked:500:600
Purpose
The concept of a VLAN in intelligent bridging (iBridge) mode is that multiple NSPs are
each connected to the NE with a VLAN. The user ports are connected to the VLAN of
their corresponding NSP.
Note: The NE supports up to 128 iBridges.
This procedure provides the steps to create or delete an iBridge VLAN.
Procedure
Proceed as follows to configure an iBridge VLAN:
1 Create an iBridge VLAN on the LT with the following command:
(no) pppoe-relay <Vlan::PppoeRelayEnable>
2 After creation, following options can be set on this VLAN :
(no) dhcp-opt-82 <Vlan::DhcpOption82>
(no) circuit-id <Vlan::CircuitId>
(no) remote-id <Vlan::RemoteId>
3 Create an iBridge VLAN on the SHub with the following command:
configure vlan id 700 name "testvlan" mode residential-bridge
configure vlan id 700 circuit-id customer-id
configure vlan shub id 700 name "testvlan"
DLP 121 Add Network Interfaces to a
VLAN
Purpose
This procedure provides the steps to add network interface(s)(that is, network port(s)) to
a VLAN.
Procedure
Proceed as follows to add a network interface to a VLAN:
1 Create and configure an SHub network port with the following command:
(no) mode automatic | [10mbps | 100mbps | 1gbps] : full | half
(no) port-type <Sys::Type>
(no) (mc-flooding)
2 Change the administrative status of the SHub network port with the following
command:
admin-status up | down | auto-up
3 Configure the SHub network egress port with the following command:
4 Configure the SHub network egress port for untagged packets with the following
command:
configure vlan shub id (vlanid) untag-port <Shub::NetworkPort>
5 Configure the port VLAN ID for the untagged packets with the following command:
configure bridge shub port <Shub::NetworkPort>
pvid <Vlan::VlanOamIndex>
configure interface shub port 3 mode automatic
port-type network
configure interface shub port 3 admin-status auto-up
configure vlan shub id 200 untag-port network:3
configure bridge shub port 3 pvid 200
Purpose
In the forwarder mode, the NE is not seen as a hop in the IP path by the edge routers.
NE users are seen as directly attached hosts on the IP interfaces of the edge routers.
Multiple VRs can be supported.
User-to-user communication is not provided by the NE.
This procedure provides the steps to configure a Virtual Routing Forwarding (VRF)
context in forwarding mode on the NT.
Procedure
Proceed as follows to configure the forwarding VRF:
1 Create a VRF in forwarding mode on the NT with the following command:
configure ip vrf (index)
name <Vrf::VrfName>
(no) desc <Vrf::VrfDescription>
(no) contact <Vrf::VrfContact>
(no) my-ipaddress <Ip::V4Address>
(no) default-ttl <Vrf::DefaultTTL>
(no) reassem-timeout<Gauge>
mode forwarder
Example:
configure ip vrf 16
name forwardingvrf16
mode forwarder
Note: the parameter my-ipaddress is an optional parameter. However, if the VRF
will be used for PPPoE sessions, then the parameter must be filled in.
If this parameter is not filled in, the IP address is assumed to be 0.0.0.0. Most
PPPoE clients (running on the PC of the customers), will reject a PPPoE session
with a PPPoE server with IP address 0.0.0.0.
Purpose
In router mode, the NE is seen as an IP next-hop by the edge routers to route the IP
packets to the users connected to the NE.
Only one VR in router mode can be configured.
The advantages of the router mode are:
Redundancy for the network routes.
ARP table scalability at the edge routers
User-to-user communication can be provided by NE at IP level; user-to-user
communication can be disabled by ACL filters.
This procedure provides the steps to configure a VRF in routing mode.
Procedure
Proceed as follows to configure a VRF in routing mode:
1 Create a VRF in routing mode on the NT with the following command:
configure ip vrf (index)
name <Vrf::VrfName>
(no) desc <Vrf::VrfDescription>
(no) contact <Vrf::VrfContact>
(no) my-ipaddress <Ip::V4Address>
(no) default-ttl <Vrf::DefaultTTL>
(no) reassem-timeout<Gauge>
mode router
2 Create a VRF in routing mode on the SHub with the following command:
configure ip shub vrf (index)
name <Vrf::SHubVrfName>
fast-path-mode:ena-user-user-com
Note: The VRF on the SHub must always be created with mode fast-path-mode.
configure ip vrf 5 name routervrf5
my-ipaddress 192.168.100.100 mode router
configure ip shub vrf 5 name routervrf5
fast-path-mode:ena-user-user-com
Purpose
This procedure provides the steps to create an iBridge user.
Prerequisites
The following prerequisites must be fulfilled before an iBridge user can be created:
An iBridge VLAN must have been created; see NTP 105.
Procedure
Proceed as follows to create an iBridge user:
1 Create an xDSL line with the following command:
| name :<PrintableString>
(no) ansi-t1413
(no) etsi-dts
(no) g992-1-a
(no) g992-1-b
(no) g992-2-a
(no) g992-3-a
(no) g992-3-b
(no) g992-3-l1
(no) g992-3-l2
(no) g992-3-am
(no) g992-5-a
(no) g992-5-b
(no) ansi-t1.424
(no) etsi-ts
(no) itu-g993-1
(no) ieee-802.3ah
(no) g992-5-am
(no) admin-up
(no) tps-tc-mode <Xdsl::TpsTcMode>
Note: the value of the parameter tps-tc-mode must be set to atm if an ADSL service
is required. The value of the parameter can be left on ptm (default value) if a VDSL
or VDSL 2 service is required.
2 Configure the xDSL interface with the following command:
xdsl line:<Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::LtSlot>
/<Eqpt::Port>
admin-up
a For a user on an ADSL line, continue with step 5
b For a user on a VDSL or VDSL 2 line, continue with step 7.
a To create an ATM PVC in subatm, continue with step 5
b To create an ATM PVC in LT, continue with step 6
5 Create an ATM PVC with the following command:
(no) admin-down
(no) aal5-encap-type llc-snap | vc-mux-bridged-8023
6 Create an ATM PVC in subatm with the following command:
(no) accept-frame type
(no) block-upmcast
(no) customer-id
(no) admin-enable
(no) mac-learn-off
(no) pvid
default-priority
7 Create a bridge port with the following command:
8 Assign an iBridge VLAN to the bridge port with the following command:
configure bridge port isam:(port) | subatm(port) vlan-id (index)
9 Set the PVID with the following command:
configure bridge port isam:(port) | subatm(port) pvid (vlan-id)
1. For an ADSL user:
spectrum-profile 3 tps-tc-mode atm admin-up
configure interface port xdsl-line:1/1/5/12 admin-up
configure atm pvc 1/1/5/12:8:35 aal5-encap-type
vc-mux-bridged-8023
configure bridge port isam:1/1/5/12:8:35 vlan-id 700
configure bridge port isam:1/1/5/12:8:35 pvid 700
2. For a VDSL or VDSL 2 user:
3. For subatm port:
configure bridge port subatm2:35
configure bridge port subatm2:35 vlan-id 700
configure bridge port subatm2:35 pvid 700
Purpose
This procedure provides the steps to create an IPoA user.
Prerequisites
configured.
Procedure
Proceed as follows to create an IPoA user:
(no) ansi-t1413
(no) etsi-dts
(no) g992-1-a
(no) g992-1-b
(no) g992-2-a
(no) g992-3-a
(no) g992-3-b
(no) g992-3-l1
(no) g992-3-l2
(no) g992-3-am
(no) g992-5-a
(no) g992-5-b
(no) ansi-t1.424
(no) etsi-ts
(no) itu-g993-1
(no) ieee-802.3ah
(no) g992-5-am
(no) admin-up
2 Configure the xDSL line with the following command:
xdsl-line:<Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::LtSlot>
/<Eqpt::Port>
admin-up
(no) admin-down
(no) aal5-encap-type llc-snap-routed | vc-mux-routed
| automatic:ip
4 Create a route in the SHub towards the modem with the following command:
configure ip shub vrf (index) route-dest (dest)
next-hop <Ip::NextHopV4Address>
vlan-id <Vlan::VlanId>
where route-dest is the subnet which is assigned to the user and next-hop is the IP
address of the WAN side of the modem.
5 Create a user port interface with the following command:
configure ip vrf (index) user-itf port (port-interface)
(no) qos-profile none | name : <Vlan::IgnoredQosProfileName>
6 If the user is a static user, continue with the next step, else go to 8.
7 Configure the IP address to the IP interface with the following command:
next-hop direct:user-port <Eqpt::Rack>/<Eqpt::Shelf>/
<Eqpt::LtSlot>/<Eqpt::Port>
Note: This command must be repeated for each IP address assigned to that
particular user.
configure atm pvc 1/1/5/12:8:35 aal5-encap-type vc-mux-routed
configure ip shub vrf 16 route-dest 192.168.10.128/29
next-hop 192.168.16.2 vlan-id 4090
configure ip vrf 16 user-itf port 1/1/5/12:8:35
configure ip vrf 16 route-dest 192.168.100.25/32
next-hop direct:user-port 1/1/5/12:8:35
Purpose
This procedure provides the steps to create an IPoE user.
Prerequisites
The following prerequisites must be fulfilled before an IPoE user can be created:
created.
Procedure
Proceed as follows to create an IPoE user:
(no) ansi-t1413
(no) etsi-dts
(no) g992-1-a
(no) g992-1-b
(no) g992-2-a
(no) g992-3-a
(no) g992-3-b
(no) g992-3-l1
(no) g992-3-l2
(no) g992-3-am
(no) g992-5-a
(no) g992-5-b
(no) ansi-t1.424
(no) etsi-ts
(no) itu-g993-1
(no) ieee-802.3ah
(no) g992-5-am
(no) admin-up
xdsl-line:<Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::LtSlot>/<Eqpt::Port>
admin-up
(no) admin-down
configure bridge port isam:(port)
6 Create a user port interface with the following command:
configure ip vrf (index) user-itf bridgeport (port-interface)
7 If the user is a static user, continue with the next step, else go to 9.
8 Configure the IP address to the IP interface with the following command:
configure ip vrf (index) route-dest (dest-ip-address) next-hop
direct:user-bridgeport:<Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::LtSlot>
/<Eqpt::Port>:<Atm::DefaultVpi>:<Atm::DefaultVci>
configure ip vrf 16 user-itf bridgeport 1/1/5/12:8:35
direct:user-bridgeport:1/1/5/12:8:35
configure ip vrf 16 user-itf bridgeport 1/1/5/12
direct:user-bridgeport:1/1/5/12
Purpose
This procedure provides the steps to create a PPPoE user.
Prerequisites
The following prerequisites must be fulfilled before an PPPoE user can be created:
created.
A PPP profile must have been created; see DLP 149.
The PPP server must be enabled; see DLP 148.
Procedure
Proceed as follows to create a PPPoE user:
(no) ansi-t1413
(no) etsi-dts
(no) g992-1-a
(no) g992-1-b
(no) g992-2-a
(no) g992-3-a
(no) g992-3-b
(no) g992-3-l1
(no) g992-3-l2
(no) g992-3-am
(no) g992-5-a
(no) g992-5-b
(no) ansi-t1.424
(no) etsi-ts
(no) itu-g993-1
(no) ieee-802.3ah
(no) g992-5-am
(no) admin-up
xdsl-line:<Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::LtSlot>/<Eqpt::Port>
admin-up
(no) admin-down
configure bridge port (port) max-unicast-mac <Vlan::MaxMac>
6 Create a user PPPoX interface with the following command:
configure pppoe pppox-interface (port)
(no) max-num-session <PPPoE::MaxNumSessions>
(no) ppp-profile-name <AsamProfileName>
configure atm pvc 1/1/5/12:8:35 aal5-encap-type llc-snap
configure bridge port 1/1/5/12:8:35 max-unicast-mac 4
configure pppoe pppox-interface 1/1/5/12:8:35
max-num-session 16 ppp-profile-name PPPProf1
configure bridge port 1/1/5/12 max-unicast-mac 4
configure pppoe pppox-interface 1/1/5/12
max-num-session 16 ppp-profile-name PPPProf1
DLP 128 Add an LT or the subatm to a
VLAN
Purpose
This procedure provides the steps to add an LT port or the subatm port to a VLAN.
Procedure
Proceed as follows to add an LT to the correct VLAN service:
1 Configure an LT port on the SHub with the following command:
lt:<Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::Slot> | subatm
Example:
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 12900-1 describes the two types of profiles.
Table 12900-1: xDSL profiles
The parameters of the xDSL spectrum depend largely on the xDSL type (ADSL,
READSL, ADSL2(+), VDSL, or VDSL2). That is why the configuration of an xDSL
spectrum is in two steps: one step for configuring the general xDSL spectrum parameters
and one step for configuring the xDSL type specific parameters.
See the CLI Commands and Messages document for a full description of all related
parameters.
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
Procedure
Proceed as follows to create an xDSL profile:
1 Create an xDSL service profile with the following command:
configure xdsl service-profile (index)
name <AsamProfileName>
(scope)
version <SignedInteger>
(no) ra-mode-down <Xdsl::RAModeDownType>
(no) ra-mode-up <Xdsl::RAModeUpType>
(no) min-bitrate-down <Xdsl::BitRate>
(no) min-bitrate-up <Xdsl::BitRate>
(no) plan-bitrate-down <Xdsl::BitRate>
(no) plan-bitrate-up <Xdsl::BitRate>
(no) max-bitrate-down <Xdsl::BitRate>
(no) max-bitrate-up <Xdsl::BitRate>
(no) max-delay-down <Xdsl::InterleavingDelay>
(no) max-delay-up <Xdsl::InterleavingDelay>
(no) imp-noise-prot-dn <Xdsl::ImpNoiseProtection>
(no) imp-noise-prot-up <Xdsl::ImpNoiseProtection>
(no) erasure-detect-dn
(no) erasure-detect-up
Note: The value of min-bitrate-down is also used for the calculation of the available
bandwidth for multicast. See DLP 136.
2 Activate an xDSL service profile with the following command:
configure xdsl service-profile (index)
active
Caution: The xDSL service profile must be activated within 15 minutes after it has
been created, otherwise it will be deleted.
Note: 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 (refer to DLP 163).
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)
local-profile
(no) dis-ansi-t1413
(no) dis-etsi-dts
(no) dis-g992-1-a
(no) dis-g992-1-b
(no) dis-g992-2-a
(no) dis-g992-3-a
(no) dis-g992-3-b
(no) g992-3-l1
(no) g992-3-l2
(no) g992-3-am
(no) g992-5-a
(no) g992-5-b
(no) ansi-t1.424
(no) dis-etsi-ts
(no) itu-g993-1
(no) ieee-802.3ah
(no) g992-5-am
(no) g993-2-8a
(no) g993-2-8b
(no) g993-2-8c
(no) g993-2-8d
(no) g993-2-12a
(no) g993-2-12b
(no) g993-2-17a
(no) g993-2-30a
(no) min-noise-down <Xdsl::NoiseMargin>
(no) min-noise-up <Xdsl::NoiseMargin>
(no) trgt-noise-down <Xdsl::NoiseMargin>
(no) trgt-noise-up <Xdsl::NoiseMargin>
(no) max-noise-down <Xdsl::NoiseMarginPlus>
(no) max-noise-up <Xdsl::NoiseMarginPlus>
(no) carrier-mask-down <Xdsl::CarrierMaskDown>
(no) carrier-mask-up <Xdsl::CarrierMaskUp>
(no) rf-band-list <Xdsl::RFBand>
(no) power_mgnt_mode <Xdsl::LinePowerMgtMode>
(no) l0_time <Xdsl::LineTime>
(no) l2_time <Xdsl::LineTime>
(no) l2-agpow-red-tx <Xdsl::L2Atpr>
(no) modification <Xdsl::ModifyStatus>
4 If the xDSL type is ADSL or ADSL2, then the ADSL and ADSL2 specific part of an
xDSL spectrum profile can be managed with the following command:
configure xdsl spectrum-profile (index) adsl-adsl2
(no) proprietary-feat
(no) max-agpowlev-down <Xdsl::PowerLevel>
(no) max-agpowlev-up <Xdsl::PowerLevel>
(no) max-psd-down <Xdsl::Adsl2PowerSpectralDensityDown>
(no) max-psd-up <Xdsl::Adsl2PowerSpectralDensityUp>
(no) pbo-mode-up
(no) max-recv-power-up <Xdsl::RxPowerLevel>
5 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) max-psd-down <Xdsl::Adsl2PowerSpectralDensityDown>
(no) max-psd-up <Xdsl::Adsl2PowerSpectralDensityUp>
(no) pbo-mode-up
6 If the xDSL type is Reach Extented 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) max-psd-down <Xdsl::ReAdsl2PowerSpectralDensityDown>
(no) max-psd-up <Xdsl::ReAdsl2PowerSpectralDensityUp>
(no) pbo-mode-up
7 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) vdsl-band-plan <Xdsl::VdslBandPlan>
(no) optional-band <Xdsl::OptionalBandUsage>
(no) optional-endfreq <Xdsl::OptionalBandEndFreq>
(no) adsl-band allow-adsl | excl-adsl | excl-adsl2plus |
excl-adsl-upto : <Xdsl::AdslBandEndFreq>
(no) max-agpowlev-down <Xdsl::VdslPowerLevel>
(no) max-agpowlev-up <Xdsl::VdslPowerLevel>
(no) psd-shape-down ansi-ftt-ex-m1 | ansi-ftt-ex-m2 |
ansi-ftt-cab-m1 | ansi-ftt-cab-m2 |
etsi-p-ex-p1-m1 | etsi-p-ex-p1-m2 |
etsi-p-ex-p2-m1 | etsi-p-ex-p2-m2 |
etsi-p-cab-m1 | etsi-p-cab-m2 |
ansi-ftt-m1-adsl | ansi-ftt-m2-adsl |
ansi-ftt-m1-adsl-2plus |
ansi-ftt-m2-adsl-2plus | etsi-p-x-m1-adsl |
etsi-p-x-m2-adsl | etsi-p-m1-adsl-2plus |
etsi-p-m2-adsl-2plus |
<Xdsl::VdslCustPsdShape>
(no) psd-shape-up <Xdsl::VdslPsdShapeUp>
(no) pbo-mode-down
(no) rx-psd-shape-up ansi-a | ansi-f | ansi-custom-ex |
ansi-custom-cab | etsi-a | etsi-b |
etsi-c | etsi-d | etsi-e | etsi-f |
etsi-custom-ex | etsi-custom-cab |
(no) ghstones-pwr-mode <Xdsl::GhsTonesTxPwr>
(no) max-band <Xdsl::VdslMaxBandNum>
(no) max-freq <Xdsl::VdslMaxFrequency>
(no) m-psd-level-down <Xdsl::MaxPsdDown>
(no) m-psd-level-up <Xdsl::MaxPsdUp>
(no) psd-pbo-par-a-up <Xdsl::ParamType>
(no) psd-pbo-par-b-up <Xdsl::ParamType>
8 Configure the transmission power of the G.hs tones in VDSL environment. with the
following command:
configure xdsl spectrum-profile (index) vdsl ghstone-set-pwr-ctrl
(no) a43 standard | auto | manual : <Xdsl::GhsTonesTxPwrLvl>
(no) b43 standard | auto | manual : <Xdsl::GhsTonesTxPwrLvl>
(no) a43c standard | auto | manual : <Xdsl::GhsTonesTxPwrLvl>
(no) v43 standard | auto | manual : <Xdsl::GhsTonesTxPwrLvl>
9 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) max-agpowlev-down <Xdsl::VdslPowerLevel>
(no) max-agpowlev-up <Xdsl::VdslPowerLevel>
(no) psd-shape-down custom-psd-down | regiona-psd-down |
regionbm1-psd-down | regionbm2-psd-down |
(no) psd-shape-up custom-psd-up | regiona-psd-up |
regionbm1-psd-up | regionbm2-psd-up |
(no) rx-psd-shape-up ansi-a | ansi-f | ansi-custom-ex |
ansi-custom-cab | etsi-a | etsi-b |
etsi-c | etsi-d | etsi-e | etsi-f |
etsi-custom-ex | etsi-custom-cab |
(no) psd-pbo-e-len-up <Xdsl::PsdPboElectrLength>
(no) m-psd-level-down <Xdsl::MaxPsdDown>
(no) m-psd-level-up <Xdsl::MaxPsdUp>
(no) psd-pbo-par-a-up <Xdsl::ParamType>
(no) psd-pbo-par-b-up <Xdsl::ParamType>
(no) v-noise-snr-down <Xdsl::SnrmMode>
(no) v-noise-snr-up <Xdsl::SnrmMode>
(no) v-noise-psd-down <Xdsl::PsdDownType>
(no) v-noise-psd-up <Xdsl::PsdUpType>
10 Activate an xDSL spectrum profile with the following command:
activate
configure xdsl service-profile 7 name test_profile
local-profile version 1
configure xdsl service-profile 7 active
configure xdsl spectrum-profile 5 name test_profile
local-profile version 1
configure xdsl spectrum-profile 5 adsl2plus
proprietary-feat
configure xdsl spectrum-profile 5 activate
Purpose
xDSL bonding allows to carry the traffic to and from a single logical subscriber interface
over multiple physical multi-ADSL lines. It offers the following services:
Extended reach of DSL service
Provision of standard multi-ADSL services to subscribers that cannot receive these
services over a single ADSL line
Higher bit rate services (up to 30 Mbit/s downstream and 5.5 Mbit/s upstream).
This procedure provides the steps to configure xDSL bonding.
Prerequisites
The following prerequisites must be fulfilled before xDSL bonding can be configured:
An iBridge VLAN (see NTP 105), an IP aware bridge (see NTP 106) or an IP router
(see NTP 107) must have been configured.
Procedure
Proceed as follows to create an xDSL bonding group profile:
1 Configure (and activate) an xDSL bonding group profile with the following
command:
configure xdsl-bonding group-profile (index)
local-profile | network-profile
(no) min-bitrate-up <Xdsl::Bitrate>
(no) min-bitrate-down <Xdsl::Bitrate>
(no) plan-bitrate-up <Xdsl::Bitrate>
(no) plan-bitrate-down <Xdsl::Bitrate>
(no) max-bitrate-up <Xdsl::Bitrate>
(no) max-bitrate-down <Xdsl::Bitrate>
(no) active
Note: A bonding group profile can be created in one step (that is, with all the
necessary parameters and activation of the bonding group profile). It can also be
created in several steps by specifying a few parameters in each step and by
activating the bonding group profile in the last step.
2 Configure an xDSL bonding group with the following command:
configure xdsl-bonding group (index)
group-profile none | <Xdsl::GroupProfileIndexWithRemove>
| name : <PrintableString>
(no) admin-status
3 Configure the xDSL lines with bonding mode atm-bonding with the following
command:
(no) admin-up
bonding-mode atm-bonding
The following applies for these xDSL lines:
The two lines used for xDSL bonding must be subsequent lines
The first line must be an odd line
Further configuration (such as atm pvc, bridge port, and so on) must be done on
that first, odd line. Refer to DLP 124, DLP 125, DLP 126 or DLP 127 for the
configuration procedure.
configure xdsl-bonding group-profile 1 name grp1
network-profile version 1 min-bitrate-down 2048
plan-bitrate-down 3072 max-bitrate-down 12228 active
configure xdsl-bonding group 1/1/4/9 group-profile name:grp1
no admin-status
configure xdsl-bonding group 1/1/4/10 group-profile name:grp1
no admin-status
spectrum-profile 3 admin-up bonding-mode atm-bonding
spectrum-profile 3 admin-up bonding-mode atm-bonding
DLP 131 Create an xDSL Bonding
Group
Note
This procedure is no longer valid.
The correct procedure for configuring xDSL bonding is described in DLP 130.
DLP 132 Configure Filtering on SHub
and subatm
Purpose
This procedure provides the steps to configure filtering on the SHub and subatm.
The IP filters for the different protocols take into account source and/or destination IP
addresses; either or both must be specified. Optionally the ICMP message type and/or
the ICMP message code can be specified.
The physical ports where the filters have to be applied are configured subsequently, by
means of dedicated configuration commands.
When the filter is to be applied to incoming traffic, the command to configure the in-port
is to be used. When the filter is to be applied to outgoing traffic, the command to configure
the out-port is to be used.
Procedure
Proceed as follows to configure filtering on the SHub:
1 Configure the SHub MAC filter with the following command:
configure transport shub mac-filter (index-num)
(no) protocol-type <Sys::ProtocolType>
filter any - <Sys::MacAddr> | <Sys::MacAddr> - any
| <Sys::MacAddr> - <Sys::MacAddr>
vlan-id <Sys::FilterVlanId>
(no) action-drop
2 Configure the SHub MAC filter to a port with the following command:
configure transport shub mac-filter (index-num)
(no) in-port (port)
3 Configure an ICMP filter on the SHub with the following command:
configure system shub filter ip-filter icmp (index-num)
(no) action-drop
(no) dst-ip-addr <Ip::V4Address> / <Ip::PrefixLengthFull>
(no) src-ip-addr <Ip::V4Address> / <Ip::PrefixLengthFull>
(no) msg-type <Sys::MsgType>
(no) msg-code <Sys::MsgCode>
(no) direction <Sys::Direction>
4 Configure the physical ports where the ICMP filter related to incoming traffic is to be
applied with the following command:
(no) in-port (network-port)
5 Configure the physical ports where the ICMP filter related to outgoing traffic is to be
applied:
(no) out-port (port)
6 Configure a TCP filter on the SHub with the following command:
configure system shub filter ip-filter tcp (index-num)
(no) action-drop
(no) min-dst-port <Sys::Port>
(no) max-dst-port <Sys::Port>
(no) min-src-port <Sys::Port>
(no) max-src-port <Sys::Port>
(no) ack <Sys::AckBit>
(no) rst <Sys::RstBit>
(no) tos <Sys::Tos>
7 Configure the physical ports where the TCP filter related to incoming traffic is to be
8 Configure the physical ports where the TCP filter related to outgoing traffic is to be
applied:
(no) out-port (network-port)
9 Configure an UDP filter on the SHub with the following command:
configure system shub filter ip-filter udp (index-num)
(no) action-drop
(no) min-dst-port <Sys::Port>
(no) max-dst-port <Sys::Port>
(no) min-src-port <Sys::Port>
(no) max-src-port <Sys::Port>
10 Configure the physical ports where the UDP filter related to incoming traffic is to be
11 Configure the physical ports where the UDP filter related to outgoing traffic is to be
applied:
12 Configure an IP filter, for protocols other than ICMP, TCP or UDP, on the SHub with
configure system shub filter ip-filter port-filter (filter-rule)
(no) protocol <Sys::RestrictedProtocol>
(no) action-drop
13 Configure the physical ports where the IP filter related to incoming traffic is to be
(no) in-port (port)
14 Configure the physical ports where the IP filter related to outgoing traffic is to be
15 Configure the subatm MAC filter with the following command:
configure transport subatm mac-filter <Sys::MacAddr>
configure transport shub mac-filter 450 protocol-type 2222
filter any | 56:0D:9D:47:DD:AA vlan-id 500 action-drop
configure transport shub mac-filter 450 in-port lt:1/1/4
configure system shub filter ip-filter icmp 12 action-drop
src-ip-addr 192.168.0.1 / 16 direction out
configure system shub filter ip-filter icmp 14 in-port 3
configure system shub filter ip-filter icmp 12 out-port lt:1/1/4
configure system shub filter ip-filter tcp 12 action-drop
configure system shub filter ip-filter tcp 14 in-port 3
configure system shub filter ip-filter tcp 12 out-port nt:2
configure system shub filter ip-filter udp 12 action-drop
configure system shub filter ip-filter udp 14 in-port 3
configure system shub filter ip-filter udp 12 out-port nt:2
configure system shub filter ip-filter port-filter 10
protocol rsvp action-drop src-ip-addr 192.168.0.1 / 16
in-port 4
out-port lt:1/1/5
configure transport subatm mac-filter 00:01:02:03:04:05
Purpose
This procedure provides the steps to configure QoS on Layer 2.
Procedure
Proceed as follows to configure QoS on Layer 2 level:
1 Configure the ATM overhead factor with the following command:
configure qos
(no) atm-overhead-fact <Qos::AtmFactor>
(no) eth-efm-fact <Qos::EthEfmFactor>
(no) enable-alignment
2 Configure a marker for Dot1P alignment with the following command:
configure qos profiles marker d1p-alignment (name) (alignment)
3 Configure a marker for single dot-1P with the following command:
configure qos profiles marker d1p (name)
default-dot1p <Qos::ExtVlanSysPrio>
4 Configure a marker for single DCSP with the following command:
configure qos profiles marker dscp (name)
default-dscp <Qos::DscpToDot1PAlignmentDscpIndex>
(no) alignment
5 Configure the QoS police profiles with the following command:
configure qos profiles policer (name)
committed-info-rate <Qos::InfoRate>
committed-burst-size <Qos::CommittedBurstSize>
6 Configure the queue profile table with the following command:
configure qos profiles queue (name)
(bac-complex-type)
7 Configure the scheduler profile table with the following command:
configure qos profiles scheduler (name)
wfq-q1-weight <Qos::WfqQ1Weight>
Note For more information about QoS and the configuration of QoS,
refer to TNG 101.
8 Configure the CAC profile table with the following command:
configure qos profiles cac (name)
res-voice-bandwidth <Itf::mediumBandWidth>
max-mcast-bandwidth <Itf::mediumBandWidth>
res-data-bandwidth <Itf::mediumBandWidth>
9 Configure the session profile table with the following command:
configure qos profiles session (name)
logical-flow-type <Qos::LogicalFlowType>
(no) up-policer none | name : <Qos::IgnoredQosProfileName>
(no) down-policer none | name : <Qos::IgnoredQosProfileName>
(no) up-marker none | name : <Qos::IgnoredQosProfileName>
10 Configure the 802.1P class to queue mapping table with the following command:
configure qos tc-map-dot1p (index) queue <Qos::Queues>
11 Configure the DSL link table with the following command:
configure qos dsl-port (index)
(no) scheduler-profile name : <Qos::IgnoredQosProfileName>
(no) cac-profile name : <Qos::IgnoredQosProfileName>
12 Configure the LIM queue table with the following command:
configure qos dsl-port (index) queue (queue)
(no) queue-profile none | name : <Qos::IgnoredQosProfileName>
13 Configure the queues on the SHub ports with the following command:
configure qos shub queue-config (port)
(no) queue0-weight <Qos::ShubQueueWeight1>
(no) queue1-weight <Qos::ShubQueueWeight1>
(no) rx-pause
(no) egress-rate <Qos::ShubPortRate>
(no) dscp2p-enable
14 Configure the traffic classes on the SHub with the following command:
configure qos shub tc-map-dot1p (port)
traffic-class <Qos::ShubTrafficClass>
15 Configure ingress policing on SHub port with the following command:
configure qos shub meter (index)
(no) name <Qos::DisplayString>
max-ingress-rate <Qos::MeterIngressRate>
burst-size <Qos::MeterBurstSize>
16 Configure the various flows to be policed with the following command:
configure qos shub flow (index)
(no) name <Qos::DisplayString>
(no) (type)
17 Configure the policing association with the following command:
configure qos shub policer (port-id) flow <Qos::PolicerFlowIndex>
meter <Qos::PolicerMeterIndex>
18 Configure the QoS parameters of a bridge port with the following command:
configure qos enable-alignment
configure qos profiles marker d1p-alignment D1PAlign1 alignment
configure qos profiles marker d1p D1Pprio3 default-dot1p 3
configure qos profiles marker d1p DSCPprio12 default-dscp 12
alignment
configure qos profiles policer Policer1 committed-info-rate 64
committed-burst-size 132144
configure qos profiles queue QueProfTab1 tail-drop : 64
configure qos profiles scheduler SchedProfTab1 wfq-q1-weight 75
configure qos profiles cac CACProfTab1 res-voice-bandwidth 64
max-mcast-bandwidth 1024 res-data-bandwidth 3072
configure qos profiles session SessProfTab1
logical-flow-type pvc-vlan-combination down-policer Policer1
configure qos tc-map-dot1p 5 queue 3
configure qos dsl-port 1/1/4/1 scheduler-profile SchedProfTab1
cac-profile CACProfTab1
configure qos dsl-port 1/1/4/1 queue 2 queue-profile none
QueProfTab1
configure qos shub queue-config 3 queue0-weight 4
queue1-weight 6 egress-rate 800
configure qos shub tc-map-dot1p 2 traffic-class 1
configure qos shub meter 32 name QoSShubMeter32
max-ingress-rate 8192 burst-size 4
configure qos shub flow 22 name VLANFLow vlan:234
configure qos shub policer 11 flow 22 meter 33
configure bridge port isam:1/1/7/12: 8:36
qos-profile name:SessProfTab1
subatm example:
configure subatm unicast-port 2:36 admin-enable enable-admin
configure bridge port subatm:2:36 qos-profile name:ses1
Purpose
This procedure provides the steps to configure QoS on L3 level.
Procedure
Proceed as follows to configure QoS on L3 level:
1 Configure the QoS overhead factor with the following command:
configure qos
(no) atm-overhead-fact <Qos::AtmFactor>
(no) eth-efm-fact <Qos::EthEfmFactor>
(no) enable-alignment
2 Configure a marker for single dot-1P with the following command:
configure qos profiles marker d1p (name)
3 Configure a marker for single DCSP with the following command:
configure qos profiles marker dscp (name)
(no) alignment
4 Configure a marker for a DSCP contract table with the following command
configure qos profiles marker dscp-contract (name)
(no) alignment
5 Configure a codepoint for a DSCP contract table with the following command:
configure qos profiles marker dscp-contract (name)
codepoint (codepoint)
(no) dscp-value <Qos::DscpToDot1PAlignmentDscpIndex>
6 Configure a marker for a P-bits and DSCP contract table with the following
command:
configure qos profiles marker d1p-dscp-contract (name)
dot1p-value <Qos::ExtVlanSysPrio>
(no) alignment
7 Configure a codepoint for a P-bits and DSCP contract table with the following
command:
configure qos profiles marker d1p-dscp-contract (name)
codepoint (codepoint)
(no) value <Qos::DscpToDot1PAlignmentDscpIndex>
8 Configure a default P-bits and DSCP marking action with the following command:
configure qos profiles marker d1p-dscp (name)
(no) alignment
9 Configure a marker for Dot1P alignment with the following command:
configure qos profiles marker d1p-alignment (name) (alignment)
10 Configure the session profile table with the following command:
configure qos profiles session (name)
logical-flow-type <Qos::LogicalFlowType>
(no) up-policer none | name : <Qos::IgnoredQosProfileName>
(no) down-policer none | name : <Qos::IgnoredQosProfileName>
(no) up-marker none | name : <Qos::IgnoredQosProfileName>
11 Assign the created QoS profiles to the L3 interface with the following command:
configure ip vrf (index) user-itf bridgeport (port-interface)
configure qos enable-alignment
configure qos profiles marker d1p D1Pprio3 default-dot1p 3
configure qos profiles marker d1p DSCPprio12
default-dscp 12 alignment
configure qos profiles marker dscp-contract DSCPContractTab1
configure qos profiles marker dscp-contract DSCPContractTab1
codepoint 1 dscp-value 32
configure qos profiles marker d1p-dscp-contract D1PDscpContrTab1
dot1p-value 4
configure qos profiles marker d1p-dscp-contract D1PDscpContrTab1
codepoint 24 value 47
configure qos profiles marker dot1p-dscp D1PSingleDSCP1
default-dscp 45 default-dot1p 7
configure qos profiles marker d1p-alignment D1PAlign1 alignment
configure qos profiles session SessProfTab1
logical-flow-type generic up-marker D1PSingleDSCP1
configure ip vrf 56 user-itf bridgeport 1/1/7/12
qos-profile name:D1PSingleDSCP1
DLP 135 Configure a QoS Aware
VLAN
Purpose
The QoS aware VLAN cross-connect is not a new cross-connect mode on its own, but it
adds the possibility to support PVC-bundles as subscriber interfaces.
Note: the QoS aware VLAN cross-connect mode can be applied to all other VLAN
crossconnect modes defined above, i.e. C-VLAN, S-VLAN and S-VLAN/C-VLAN
cross-connects. In the last case, the cross-connect will consider the p-bits of the S-VLAN,
the C-VLAN p-bits remaining transparent.
In the downstream direction, the egress bridge port is found by means of the combination
of VLAN tag and p-bit. The p-bits are hence only used for a routing decision. There are
no additional QoSrequirements besides the generic QoS-handling available from the
'regular' cross-connect or residential bridging.
This procedure provides the steps to configure a QoS aware VLAN.
Prerequisites
The following prerequisites must be fulfilled before a QoS aware VLAN can be
configured:
A QoS policer profile must have been created
A QoS session profile must have been created
Procedure
Proceed as follows to configure a QoS aware VLAN:
1 Create a C-VLAN:
i Create a C-VLAN on the LT with the following command:
mode cross-connect
ii Create a C-VLAN on the SHub with the following command:
mode cross-connect
(no) (negotiate)
duplex <Sys::Duplex>
speed <Sys::Speed>
port-type network
(no) mc-flooding
command:
iii Configure the SHub network egress port with the following command:
(no) ansi-t1413
(no) etsi-dts
(no) g992-1-a
(no) g992-1-b
(no) g992-2-a
(no) g992-3-a
(no) g992-3-b
(no) g992-3-l1
(no) g992-3-l2
(no) g992-3-am
(no) g992-5-a
(no) g992-5-b
(no) ansi-t1.424
(no) etsi-ts
(no) itu-g993-1
(no) ieee-802.3ah
(no) g992-5-am
(no) admin-up
- To create an ADSL line, continue with step iv
- To create a VDSL or VDSL2 line, continue with step vi
iv Create the necessary ATM PVCs (i.e. a PVC bundle) with the following
command:
(no) admin-down
v For each of the created PVCs, create a bridge port with the following
command:
vi For each created bridge port, associate a VLAN with the bridge port and set
the priorities applicable for that port with the following command:
configure bridge port (port) vlan-id (index)
qos-profile name : <Vlan::IgnoredQosProfileName>
(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-ct
vii Set the PVID and the priority with the following command:
configure bridge port (port)
pvid <Vlan::UVlanIndex> | stacked :<Vlan::SVlanIndex> :
<Vlan::CVlanIndex>
(no) default-priority <Vlan::Priority>
(no) prio-regen-prof <Vlan::PrioRegenProfile>
Note: The priority regeneration profiles are fixed. They can be viewed with the
command:
show vlan priority-regen
configure vlan id 300 name "ISP_C_VLAN" mode qos-aware
configure xdsl line 1/1/5/12 service-profile 7 spectrum-profile 3
admin-up
configure bridge port 1/1/5/12:8:35 vlan-id 300
qos-profile name:qos-sess1 prior-ctrl-load prior-less-100ms
prior-less-10ms prior-nw-ctrl
configure bridge port 1/1/5/12:8:36
configure bridge port 1/1/5/12:8:36 vlan-id 300
qos-profile name:qos-sess1 prior-best-effort prior-background
prior-spare prior-exc-effort
configure bridge port 1/1/5/12:8:35 pvid 300 default-priority 5
configure bridge port 1/1/5/12:8:36 pvid 300 prio-regen-prof
cl-all-prio-3
subatm example:
configure subatm unicast-port 3:35 admin-enable enable-admin
configure bridge port subatm:3:35
configure gridge port subatm:3:35 vlan-id 120 qos-profile
name:FD_HSI_standard
configure bridge port subatm:3:35 pvid 120
Purpose
This procedure provides the steps to configure multicast (general parameters, capacity
and source table) on the NE.
Procedure
Proceed as follows to configure multicast on the LT:
1 Configure the general multicast parameters with the following command:
configure mcast general
(no) package-member <Igmp::Pkg>
(no) fast-change
(no) pkg-memb-bitmap <Igmp::PkgMemBitMap>
(no) max-bitrate <Igmp::GeneralMcastMaxBitRate>
(no) mean-bit-rate <Igmp::GeneralMcastMeanBitRate>
Note: The minimum bitrate available for multicast is configured with the command
configure xdsl service-profile; see DLP 129.
Note: The parameter pkg-memb-bitmap is kept for backward compatibility with
previous releases (R2.3).
2 Configure the multicast capacity parameters with the following command:
configure mcast capacity
(no) max-num-group <Igmp::McastCapacityMaxNumGroup>
(no) max-num-uncfg <Igmp::McastCapacityMaxNumUnCfg>
(no) cfg-res-time <Igmp::reserveTim>
(no) uncfg-res-time <Igmp::reserveTim>
3 Configure the multicast source with the following command:
configure mcast src (class-d-addr)
(no) package-member <Igmp::Pkg>
(no) dis-fast-change
(no) name <PrintableString-0-32>
(no) pkg-memb-bitmap <Igmp::PkgMemBitMap>
(no) atm-peak-bit-rate <Igmp::McastSrcAtmPeakBitRate>
(no) atm-sus-bit-rate <Igmp::McastSrcAtmSustainBitRate>
vlan-id <Igmp::McastSrcVLANID>
(no) service-name <PrintableString-0-32>
(no) preview-duration <Igmp::multicastSrcMaxPreDuration>
(no) preview-number <Igmp::multicastSrcMaxPreNumber>
(no) preview-blackout <Igmp::multicastSrcPreBlackout>
Note: The parameter pkg-memb-bitmap is kept for backward compatibility with
previous releases (R2.3).
4 Configure the multicast source package members with the following command:
configure mcast src (class-d-addr)
(no) packagemember (package)
configure mcast general max-bitrate 50000 mean-bit-rate 10000
configure mcast capacity max-num-group 128 max-num-uncfg 20
configure mcast src 224.1.1.0
atm-peak-bit-rate 50000 atm-sus-bit-rate 3000 vlan-id 400
configure mcast src 02:00:00:00:00:00:00:00 packagemember 50
Purpose
This procedure provides the steps to configure IGMP proxy on the LT. The bridge port
must be configured.
Procedure
Proceed as follows to configure proxy on the LT:
1 Configure the IGMP source channel parameters with the following command:
configure igmp channel (port)
(no) perm-pkg-bitmap <Igmp::PkgMemBitMap>
(no) fullview-packages (package)
(no) preview-packages (package)
(no) max-num-group <Igmp::ChannelMaxNumGroup>
2 Configure the package bitmaps. The package is intended primarily for use by a
network element manager, such as AWS, to support multiple sets of packages in
different regions.
The definition of a package is a group of zero or more multicast sources that share
a common access permission. By grouping the source channels into one or more
packages, this gives flexibility for the service provider to deliver different levels of
service to the end users.
Use the following command:
configure igmp package (index)
(no) name <PrintableString-0-32>
(no) template-name <PrintableString-0-32>
template-version <Igmp::igmpPackageTemplateVersion>
3 Configure the IGMP system parameters with the following command:
configure igmp system
src-ip-address <IP::V4Address>
(no) verify-checksum
(no) query-interval <Igmp::SystemQueryInterval>
(no) max-rsp-time <Igmp::SystemQueryMaxResponseTime>
(no) robustness <Igmp::SystemRobustness>
(no) mem-query-int <Igmp::MembQueryIntv>
(no) last-memb-cnt <Igmp::MembQueryCount>
(no) last-max-resp-tim <Igmp::SystemLastMembMaxRespTime>
(no) host-report-intv <Igmp::SystemUnsolicitedReportIntvl>
(no) start
(no) preview-valid <Igmp::SystemPrevalidIntval>
(no) cdr-validation <Igmp::SystemPrecdrvalidIntval>
(no) cdr-generation <Igmp::igmpSystemCdrAdmin>
configure igmp channel 1/1/4/1:8:35 fullview-packages 20
configure igmp channel 1/1/4/1:8:35 fullview-packages 20
configure igmp channel 1/1/4/1:8:35 preview-packages 49
configure igmp channel 1/1/4/1:8:35 max-num-group 2
Purpose
This procedure provides the steps to configure IGMP snooping on the SHub.
Procedure
Proceed as follows to configure IGMP snooping on the SHub:
1 Configure the IGS system parameters with the following command:
configure igmp shub igs-system
(no) start-snooping
(no) enable-snooping
self-ip-addr-mode <Igmp::SelfIpAddressMode>
(no) self-ip-addr <Ip::V4Address>
trace-selection <SignedInteger>
(no) router-purge-intv <Igmp::RouterInterval>
(no) host-purge-intv <Igmp::HostInterval>
(no) report-fwd-intv <Igmp::ForwardInterval>
2 Configure the response timer with the following command:
configure igmp shub response-timer (vlan-id)
(no) leave-rsp-timer <Igmp::LeaveResponse>
3 Configure the router port with the following command:
configure igmp shub vlan-router-port (vlan-id)
network-port <Shub::NetworkPort>
query-timer <Igmp::VlanRouterQueryTimer>
4 View the status of the IGMP VLAN router ports with the following command:
show igmp shub vlan-router-port (vlan-id)
5 Configure the VLAN filter with the following command:
configure igmp shub vlan-filter (filter-id)
(no) snoop-filter
configure igmp shub igs-system start-snooping
enable-snooping self-ip-addr-mode from-ip
configure igmp shub response-timer 560 leave-rsp-timer 3
configure igmp shub vlan-router-port 450 network-port 3
query-timer 120
show igmp shub vlan-router-port 450 network-port 3
configure igmp shub vlan-filter 450 snoop-filter
DLP 139 Configure DHCP Relay Agent
in iBridge Mode
Purpose
In the iBridge mode, the user subnets need to be configured on the user-gateway
interface of the SHub. This is needed to advertise the user subnet routes into the network
via routing protocols and also to forward user IP packets in downstream to LTs (in the
routing table of Shub, direct subnet routes need to be created on the V-VLAN).
DHCP Relay is configured per VLAN:
Enable/disable DHCP relay agent
Enable/disable Option-82 insertion
Option-82 insertion is configurable irrespective of the DHCP relay agent status.
The DHCP relay agent IP address (separate configuration parameter) is the IP
address of one of the VRF IP interfaces.
This procedure provides the steps to configure the DHCP relay agent in iBridge mode.
Procedure
Proceed as follows to configure the DHCP relay agent:
1 Configure the DHCP relay agent per VRF interface with the following command:
configure dhcp-relay agent (vrfid)
bcast-vlan
(no) option-82
(no) circuit-id <Dhcp::CircuitId>
(no) remote-id <Dhcp::RemoteId>]
2 Enable the SHub relay agent with the following command:
configure dhcp-relay shub relaying
3 Configure the list of DHCP Relay Server to a particular VRF with the following
command:
configure dhcp-relay shub server (index)
ip-addr <Ip::V4Address>
server-name <PrintableString-0-32>
4 Configure the DHCP relay agent parameters to a particular VRF with the following
command:
configure dhcp-relay shub agent (vrfid)
(no) enable-relaying
(no) secs-threshold <Dhcp::SecsThreshold>
(no) hops-threshold <Dhcp::HopThreshold>
(no) context-lifetime <Dhcp::ContextLife>
(no) agent-ip-addr <Ip::V4Address>
configure dhcp-relay agent 56 bcast-vlan l2-vlan:700
option-82 circuit-id customer-id physical-id customer-id
configure dhcp-relay shub server 56 ip-addr 192.168.125.13
server-name DHCPRel56
configure dhcp-relay shub relay-agent 56 enable-relaying
in Router Mode
Purpose
In the router mode, the user subnets need to be configured on the user-gateway interface
of SHub. This is needed to advertise user subnet routes into network via routing protocols
and also to forward user IP packets in downstream to LTs (in the routing table of SHub,
direct subnet routes need to be created on the V-VLAN).
Option-82 insertion is configurable irrespective of the DHCP relay agent status.
This procedure provides the steps to configure the DHCP relay agent.
Prerequisite
The following prerequisite must be fulfilled before a DHCP Relay Agent in router mode
can be configured:
a V-VLAN must have been created; see DLP 116.
Procedure
bcast-vlan none | l2-vlan : <Vlan::VlanId>
(no) option-82
3 Configure the list of DHCP Relay Server to a particular VRF with the following
command:
configure dhcp-relay shub server (index)
command:
configure dhcp-relay shub relay-agent (index)
agent-ip-addr <Ip::V4Address>
configure dhcp-relay agent 56 bcast-vlan l2-vlan:301
configure dhcp-relay shub server 56 ip-addr 192.168.101.12
server-name Antwerp56
configure dhcp-relay shub relay-agent 56
enable-relaying agent-ip-addr 192.168.125.13
in Forwarder Mode
Purpose
The DHCP relay port functionality provided by LTs is exactly the same as in the router
mode. One difference is that, in the forwarder mode, there is no need to have a dedicated
V-VLAN to be used as a broadcast VLAN for DHCP relay. Instead, one of the network
VLANs is used at the same time as a broadcast VLAN by LTs.
Option-82 insertion is configurable, irrespective of the DHCP relay agent status.
This procedure provides the steps to configure the DHCP relay agent.
Procedure
bcast-vlan none | l2-vlan : <Vlan::VlanId>
(no) option-82
3 Configure the list of DHCP relay servers to a particular VRF with the following
command:
configure dhcp-relay shub vrf (vrfid)
relay-server <Ip::V4Address>
command:
configure dhcp-relay shub relay-agent (vrfid)
agent-ip-addr <Ip::V4Address>
configure dhcp-relay agent 16 bcast-vlan layer2:450
configure dhcp-relay shub vrf 16
configure dhcp-relay shub vrf 16 relay-server 192.168.101.12
server-name Antwerp56
configure dhcp-relay shub relay-agent 16
enable-relaying agent-ip-addr 192.168.125.13
DLP 142 Configure the Security
Domain
Purpose
This procedure provides the steps to configure the security domain.
Procedure
Proceed as follows to configure the security domain:
1 Configure the security domain with the following command:
configure system security domain (name)
vrf-index <Aaa::DomainVrfIndex>
(no) vlan-id <Vlan::VlanIndexOrZero>
(no) primary-dns <Ip::V4Address>
(no) second-dns <Ip::V4Address>
(no) primary-nbns <Ip::V4Address>
(no) second-nbns <Ip::V4Address>
(no) sess-timeout <Aaa::DomainSessionTimeout>
(no) qos-policy none | name : <Aaa::IgnoredQosProfileName>
authenticator local | radius : <Aaa::RadPolicyName>
(no) admin-down
2 Define the security domain IP pool with the following command:
configure system security ip-addr-pool (name)
vrf-index <Aaa::IpVrfIndex>
start-addr <Ip::V4Address> / <Ip::PrefixLength>
(no) size <Aaa::IpAddressPoolSize>
(no) admin-down
3 Assign the security domain IP pool with the following command:
configure system security domain (name) ip-pool (name)
vrf-index <Aaa::VrfIndex>
priority <SignedInteger>
configure system security domain Domain1 vrf-index 15
vlan-id 56 authenticator local
configure system security ip-addr-pool PoolDomain1
vrf-index 15 start-addr 10.179.16.100/24 size 100 no admin-down
configure system security domain Domain1 ip-pool PoolDomain1
vrf-index 15 priority 3
DLP 143 Configure Local
Authentication
Purpose
This procedure provides the steps to configure local authentication.
Procedure
Proceed as follows to configure local authentication:
authenticator local
2 Define the domain users with the following command:
configure system security domain (name) user (name)
password <Password>
3 Change the password for a specific user with the following command:
configure system security domain (name) user (name) password
<new Password>
4 Delete a user from the authentication table with the following command:
configure system security domain (name) no user (name)
configure system security domain Domain1
vrf-index 15
authenticator local
configure system security domain Domain1 user JohnDoe
password zxspr#12
configure system security domain Domain1 user JohnDoe
password sh#34pea
configure system security domain Domain1 no user JohnDoe
Purpose
This procedure provides the steps to configure the Remote Authentication Dial-In User
Service (RADIUS).
Procedure
Proceed as follows to configure RADIUS:
1 Configure the RADIUS authentication server with the following command:
configure system security radius auth-server (name)
ip-address <Ip::V4Address>
(no) port <Aaa::InetPortNumber>
secret <Password>
(no) retry-limit <Aaa::RadiusRetryLimit>
(no) timeout-limit <Aaa::RadiusTimeout>
(no) admin-down
(no) dead-interval <Aaa::RadiusDeadInterval>
2 Configure the RADIUS accounting server with the following command:
configure system security radius acc-server (name)
(no) port <Aaa::InetPortNumber>
secret <Password>
(no) retry-limit <Aaa::RadiusRetryLimit>
(no) timeout-limit <Aaa::RadiusTimeout>
(no) admin-down
(no) dead-interval <Aaa::RadiusDeadInterval>
3 Configure the RADIUS policy with the following command:
configure system security radius policy (name)
nas-id <Printable-0-64>
nas-ip-address <Ip::V4Address>
(no) keep-domain-name
(no) disable-accnt-msg
(no) acc-interval <Aaa::AccInt>
(no) disable-eap
4 Configure the RADIUS server set with the following command:
configure system security radius policy (name) servers (index)
auth-server none | name : <Aaa::RadAuthServerName>
vrf-index-auth <Aaa::VrfIndex>
(no) acc-server none | name: <Aaa::RadAccServerName>
(no) vrf-index-acc <Aaa::VrfIndex>
priority <Aaa::Priority>
5 Enable the RADIUS relay on the SHub with the following command:
configure system security radius
(no) relay
(no) auth-super-user <Aaa::SuperUserAuth>
oper-policy-name <Aaa::RadPolicyName>
(no) vlan-id <Vlan::VlanIndexOrZero>
(no) primary-dns <Ip::V4Address>
(no) second-dns <Ip::V4Address>
(no) primary-nbns <Ip::V4Address>
(no) second-nbns <Ip::V4Address>
(no) sess-timeout <Aaa::DomainSessionTimeout>
(no) qos-policy none | name : <Aaa::IgnoredQosProfileName>
authenticator radius : <Aaa::RadPolicyName>
(no) admin-down
7 Configure the RADIUS Dynamic Authorization Clients with the following command:
configure system security radius dyn-auth-client (name) vrf-index
<Aaa::VrfIndex>
secret <Password>
(no) admin-down
configure system security radius auth-server RADAuthServ1
vrf-index 50 ip-address 192.168.120.120
secret Khinghkhongh timeout-limit 5
configure system security radius acc-server RADAccServ1
vrf-index 51 ip-address 192.168.121.121
secret Ahlakazam
configure system security radius policy RADPol23
nas-id MyNASID nas-ip-address 192.168.122.122
configure system security radius policy RADPol23 servers 2
auth-server name: RADAuthServ1 vrf-index-auth 50
acc-server name: RADAccServ1 vrf-index-acc 51 priority 162
configure system security radius relay auth-super-user enable
configure system security domain SecDomain1
vrf-index 56 authenticator radius : RADPol23
configure system security radius dyn-auth-client DynAuth1
vrf-index 64 ip-address 192.168.123.123 secret Khinghkhongh
Purpose
This procedure provides the steps to enable, disable, and configure parameters for
802.1x.
Procedure
Proceed as follows to configure 802.1x:
1 Enable 802.1x with the following command:
configure system security pae port-access
2 Configure the 802.1x parameters with the following command:
configure system security pae authenticator (port)
(no) controlled-port <Aaa::PaeControlledPortControl>
(no) quiet-period <Aaa::paeQuitTime>
(no) tx-period <Aaa::paeTime>
(no) supp-timeout <Aaa::paeTime>
(no) server-timeout <Aaa::paeTime>
(no) max-req <Aaa::paeMaxReq>
3 Configure the remote authenticator and enable authentication and handshake with
configure system security pae ext-authenticator (port)
(no) authentication
(no) init-authreq-off
(no) handshake
(no) handshake-period <Aaa::PortHandShakePeriod>
4 Enable initialization control for a port with the following command:
configure system security pae port (port)
(no) initialize
configure system security pae port-access
configure system security pae authenticator 1/1/4/1: 8:35
controlled-port force-unauthorized server-timeout 20
max-req 5
configure system security pae ext-authenticator 1/1/4/1: 8:35
authentication handshake
configure system security pae port 1/1/4/1: 8:35 initialize
Purpose
PPPoE relay needs no configuration. It should only be enabled or disabled on a specific
VLAN.
Procedure
Proceed as follows to enable or disable PPPoE relay:
1 Enable PPPoE relay with the following command:
configure vlan id (vlanid) pppoe-relay mode
Example:
configure vlan id 56 pppoe-relay mode residential-bridge
2 Disable PPPoE relay with the following command:
configure vlan id (vlanid) no pppoe-relay
Example:
configure vlan id 56 no pppoe-relay
DLP 147 Configure PPPoA-PPPoE
Relay
Purpose
This procedure provides the steps to configure PPPoA-PPPoE relay.
Prerequisites
The following prerequisites must be fulfilled before PPPoA-PPPoE relay can be
configured:
An iBridge VLAN must have been created; see NTP 105.
Procedure
Proceed as follows to configure PPPoA-PPPoE relay:
1 Configure PPPoA-PPPoE CC global parameters with the following command:
configure pppox-relay cross-connect global-session
(no) pado-timeout <PPPoX::PadTimeOut>
(no) pads-timeout <PPPoX::PadTimeOut>
(no) max-pad-attempts <PPPoX::PadRRetrials>
(no) trans-max-age <PPPoX::TransactionMaxAge>
(no) cc-max-age <PPPoX::CcMaxAge>
2 Configure the PPPoA-PPPoE CC engine with the following command:
configure pppox-relay cross-connect engine (vlan-id)
(no) name <PPPoX::EngineName>
(no) lock
(no) service-name <PPPoX::EngineName>
3 Enable monitoring of the PPPoA-PPPoE CC engine with the following command:
configure pppox-relay cross-connect engine (vlan-id) monitor
4 Configure PPPoA-PPPoE CC client port with the following command:
configure pppox-relay cross-connect client-port (port)
vlan-id <Vlan::UVlanIndex>
| <Vlan::SVlanIndex> : <Vlan::CVlanIndex>
default-priority <PPPoX::DefaultPriority>
(no) max-cc <PPPoX::MaxNumPppCc>
(no) qos-profile none | name : <PPPoX::IgnoredQosProfileName>
5 Enable monitoring of the PPPoA-PPPoE CC client port with the following command:
configure pppox-relay cross-connect client-port (port) monitor
configure pppox-relay cross-connect global-session
trans-max-age 500 cc-max-age 600
configure pppox-relay cross-connect engine 69
name PPPoXRelay69
configure pppox-relay cross-connect engine 69 monitor
configure pppox-relay cross-connect client-port 1/1/4/1:8:35
vlan-id 2000 default-priority 4
configure pppox-relay cross-connect client-port 1/1/4/1:8:35
monitor
Purpose
This procedure provides the steps to create the PPPoE server and the state of the PPPoE
server.
By default, the PPPoE server is disabled.
Procedure
Proceed as follows to configure the PPPoE server:
1 Configure the PPPoE server with the following command:
configure pppoe server-name <PPPoE::ServerName> enable-server
Example:
configure pppoe server-name PPPoEServer1 enable-server
Purpose
This procedure provides the steps to create and configure the PPPoE profiles.
Procedure
Proceed as follows to configure the PPPoE profiles:
1 Create and configure a PPPoE profile with the following command:
configure pppoe ppp-profile (index)
(no) auth-type <PPPoE::pppProfileAuthenType>
(no) keep-alive-intvl <PPPoE::ProfileKeepAliveInterval>
Example:
configure pppoe ppp-profile PPPProf1
auth-type chap-pap
Purpose
This procedure provides the steps to configure an ARP table entry.
Procedure
Use the following procedure to configure an ARP table entry:
1 Configure the IP Shub ARP parameters with the following command:
configure ip shub arp
(no) cache-timeout <Ip::ArpCacheTimeOut>
(no) cache-pending <Ip::ArpCachePendingTime>
(no) cache-refresh <Ip::ArpCacheRefreshTime>
(no) cache-retry-time <Ip::ArpCacheRetryTime>
(no) max-retry-itvl <Ip::ArpCacheMaxRetryTime>
(no) max-retries <Ip::ArpMaxRetries>
2 Configure the IP Shub ARP parameters per VLAN with the following command:
configure ip shub arp vlan (vlanid)
(no) gratuitous-arp
configure ip shub arp cache-timeout 10000 cache-pending 20
max-retries 5
configure ip shub arp vlan 250 gratuitous-arp
DLP 151 Shut down and Restart the
SHub
Purpose
This procedure provides the steps to restart the SHub.
Procedure
Proceed as follows to restart the SHub:
1 Prepare the system for shutdown with the following command:
admin equipment prepare-shutdown
2 Pull out the NT.
3 Make the necessary changes to the NT.
4 Insert the NT.
5 Restart the SHub with the following command:
Purpose
You can reboot the whole system in the following modes:
restart with self-test
restart without self-test
restart with removal of persistent data, but preserving the management channel
configuration data
restart with removal of all persistent data, including the management channel
configuration data
system hot restart
Procedure
Proceed as follows to reboot the system:
1 Reboot the system with the following command:
admin equipment reboot-isam <Equipm::SystemRestart>
Example:
admin equipment reboot-isam with-self-test
DLP 153 Shut down and Restart
Individual Equipment
Purpose
This procedure provides the steps to shut down and restart slots containing plug-in units
on the NE shelf.
General
The only individual pieces of equipment that may be necessary to restart are plug-in units
such as LTs. These can be shut down and restarted by powering down the slot in which
the plug-in unit is inserted.
Procedure
Proceed as follows to shut down and restart individual equipment:
1 Power down a plug-in unit with the following command:
power-down
Example:
configure equipment slot 1/1/5 power-down
2 Restore power to a plug-in unit with the following command:
no power-down
Example:
configure equipment slot 1/1/5 no power-down
DLP 154 Create a Snapshot Alarm
Table
Purpose
This procedure provides the steps to create a snapshot alarm table.
Procedure
Proceed as follows to create a snapshot alarm table:
1 Create an alarm snapshot table for a minimum severity level with the following
command:
admin alarm snap-shot (start)
Example:
admin alarm snap-shot start:major:tom
This command will create an alarm snapshot table for snap-shot owner "tom"
showing all the alarms with minimum severity-level "major" (=major and critical).
Note: The command will fail if the snap-shot is already in use. The snap-shot is only
kept for a limited time and will be automatically cleared.
2 The alarm snapshot table can be viewed with the following command:
show alarm snap-shot table (index)
Note: The command can be given with or without extra parameters:
When NO parameter is given, all the tables will be shown.
When a parameter (i.e. the index of the desired table) is given, onlt that table will
be shown.
3 Create the alarm snapshot table on the SHub with the following command:
admin alarm shub snap-shot start
Example:
admin alarm shub snap-shot start:major:tom
4 The SHub alarm snapshot table can be viewed with the following command:
show alarm shub snap-shot table (index)
Note: The command can be given with or without extra parameters:
When NO parameter is given, all the tables will be shown.
When a parameter (that is, the index of the desired table) is given, only that table
will be shown.
Purpose
This procedure provides the steps to monitor alarms. Monitoring alarms includes viewing
current alarms, a snapshot of the NE alarms, and the current configuration of the alarm
delta logs.
General
Refer to the CLI Commands and Messages document for a full description of all the
commands related to alarm monitoring. The most common commands are listed in the
procedure below.
Procedure
Proceed as follows to monitor alarms:
1 Use the following command to show the alarm log tables:
show alarm log table | equipment | eqpt-holder | plug-in-unit |
atm | ether-itf | sw-mgmt | xdsl misc | xdsl near-end |
xdsl far-end | tca-xdsl | eo-conversion | authentication|
bonding-group | redundancy | custom | sfp | llu-relay (index)
2 Use the following command to show the alarm snapshot table:
show alarm snap-shot table | equipment | eqpt-holder |
plug-in-unit | atm | ether-itf | sw-mgmt | xdsl | tca-xdsl |
eo-conversion | authentication | bonding-group | ipox | redundancy
| custom | sfp | llu-relay (index)
3 Use the following command to view the common values related to the alarm delta
logs:
show alarm delta-log alarm-changes
4 Use the following command to view the current alarms:
show alarm current table | equipment | eqpt-holder | plug-in-unit
| atm | ether-itf | sw-mgmt | xdsl | tca-xdsl | eo-conversion |
authentication | bonding-group | redundancy | custom | sfp |
llu-relay (index)
5 Use the following command to view the SHub alarms:
show alarm shub snap-shot table | snap-shot shub-gen |
snap-shot eth-shub | snap-shot rip | snap-shot ospf |
snap-shot uplink-group (index)
6 Use the following command to view the alarm entries:
show alarm entry (alarm-id)
7 To view the alarm delta log entries, use any of the following commands (see the
CLI Commands and Messages document for more information):
show alarm delta-log alarm-changes
show alarm delta-log indeterminate (index)
show alarm delta-log warning (index)
show alarm delta-log minor (index)
show alarm delta-log major (index)
show alarm delta-log critical (index)
DLP 156 Management of the SHub
Database
Note
The correct procedure is described in RTP 100.
Purpose
This document provides the steps to save the SHub configuration database.
Procedure
Proceed as follows to manage the SHub database:
1 Save the SHub database with the following command:
2 The status of the save operation (successful, failed, or still in progress) can be
viewed with the following command:
show software-mngt shub config-file
DLP 158 Management of the System
Database
Note
The correct procedure is described in RTP 100.
Purpose
This procedure provides the steps to manage the Operational Software Package
(OSWP).
Prerequisite
The NE contains one OSWP, which is committed and active on all the boards.
Procedure
Proceed as follows to manage the OSWP in the NE:
1 Configure the download of an OSWP with the following command:
configure software-mngt oswp (index)
primary-file-server-id <Ip::V4Address>
second-file-server-id <Ip::V4Address>
download-set cmplete-set
autofetch <SwMngt::autoFetch>
2 Start the actual OSWP download with the following command:
admin software-mngt oswp (index) download <SwMngt::oswpName>
3 Show download status with the following command:
show software-mngt oswp (index)
4 Abort an OSWP download with the following command:
admin software-mngt oswp (index) abort-download
5 Activate an OSWP with the following command:
admin software-mngt oswp (index) activate
<SwMngt::activationType>
6 Commit an OSWP with the following command:
admin software-mngt oswp (index) commit
configure software-mngt oswp 1
primary-file-server-id 192.168.111.112
second-file-server-id 192.168.111.212
download-set complete-set autofetch all-files
admin software-mngt oswp 1 download /OSWP_packages/OSWP1
admin software-mngt oswp 2 detail
admin software-mngt oswp 1 abort-download
admin software-mngt oswp 1 activate with-linked-db
admin software-mngt oswp 1 commit
DLP 160 View Version of the SHub
Software
Purpose
This procedure provides the steps to view the software version number for the SHub.
Procedure
Proceed as follows to view the software version number for the SHub:
1 View the software version of the SHub system parameters with the following
command:
show system shub entry version
Description
The NE supports licensing counters. By these counters, the NE management station is
able to license a set of features provided by the NE in its network. The licensing counters
are defined at the level of the DSL interfaces.
Features
The feature counters can be retrieved by a manager for monitoring. The following
features are monitored in the NE:
ADSL2+
READSL2
ADSL2/ADSL2+ Annex M
IGMP
IP-Forwarding
PPPoX Relay
PPPoX Termination
802.1x
Procedure
Proceed as follows to retrieve the feature counters:
1 View the number of software licenses for the feature wit hthe following command:
show system license adsl2-plus | readsl | igmp | ip-forward |
pppox-relay | pppox-termination | 802dot1x | annex-m | ipoa-cc
DLP 162 Modify the External
Management VLAN
Purpose
This procedure gives the steps to change the external management VLAN.
Procedure
Proceed as follows to change the external management VLAN:
1 View the external VLAN in the system with the following command:
info configure system
2 View the external VLAN in the SHub with the following command:
info configure system shub entry vlan
3 View the PVID on the management port with the following command:
info configure bridge shub port 1
4 Change the external VLAN in the system with the following command:
mgnt-vlan-id <Vlan::VlanOamIndex>
system-mac <Sys::MacAddr> / <Sys::MacAddr> / <Sys::Number>
(no) single-public-ip
5 Change the external VLAN in the SHub with the following command:
configure system shub entry vlan ext-vlan-id <Vlan::ExtVlanIndex>
6 Change the PVID on the management port with the following command:
configure interface shub port 1 pvid 4093
7 Save the SHub database with the following command:
8 To make these changes effective, the Shub must be restarted with the following
command:
info configure system
info configure system shub entry vlan
info configure bridge shub port 1
mgnt-vlan-id 4000
system-mac 99:62:12:34:56:5B / 98:45:43:6B:35:78 / 24
configure system shub entry vlan ext-vlan-id 4000
configure interface shub port 1 pvid 4093
Purpose
This procedure provides the steps to modify xDSL profiles.
Procedure
Proceed as follows to modify an xDSL profile:
1 Modify an xDSL service profile with the following command:
configure xdsl service-profile <profile index>
name <profile name>
(scope)
version <version number>
Note: Only the parameters name, scope and version can be changed for an existing
xDSL service profile. If the other parameters need to be changed, then a new xDSL
service profile must be created.
2 Start the modification of an xDSL spectrum profile with the following command:
configure xdsl spectrum-profile (index) modification start
3 Modify the parameters of an xDSL spectrum profile with the following command:
local-profile
(no) dis-ansi-t1413
(no) dis-etsi-dts
(no) dis-g992-1-a
(no) dis-g992-1-b
(no) dis-g992-2-a
(no) dis-g992-3-a
(no) dis-g992-3-b
(no) g992-3-l1
(no) g992-3-l2
(no) g992-3-am
(no) g992-5-a
(no) g992-5-b
(no) ansi-t1.424
(no) dis-etsi-ts
(no) itu-g993-1
(no) ieee-802.3ah
(no) g992-5-am
(no) g993-2-8a
(no) g993-2-8b
(no) g993-2-8c
(no) g993-2-8d
(no) g993-2-12a
(no) g993-2-12b
(no) g993-2-17a
(no) g993-2-30a
(no) min-noise-down <Xdsl::NoiseMargin>
(no) min-noise-up <Xdsl::NoiseMargin>
(no) trgt-noise-down <Xdsl::NoiseMargin>
(no) trgt-noise-up <Xdsl::NoiseMargin>
(no) max-noise-down <Xdsl::NoiseMarginPlus>
(no) max-noise-up <Xdsl::NoiseMarginPlus>
(no) carrier-mask-down <Xdsl::CarrierMaskDown>
(no) carrier-mask-up <Xdsl::CarrierMaskUp>
(no) rf-band-list <Xdsl::RFBand>
(no) power_mgnt_mode <Xdsl::LinePowerMgtMode>
(no) line_l0_time <Xdsl::LineTime>
(no) line_l2_time <Xdsl::LineTime>
(no) line_l2_atpr <Xdsl::L2Atpr>
4 Use one of the following commands to complete the modification of the xDSL
spectrum profile:
When the modifcations must be kept:
configure xdsl spectrum-profile (index) modification complete
When the modifications must be cancelled:
configure xdsl spectrum-profile (index) modification cancel
Modifying an xDSL service profile:
Suppose an xDSL service profile with name test-profile exists and that the
name must be changed to approved-profile:
configure xdsl service-profile 5 name approved-profile
Modifying an xDSL spectrum profile:
Suppose an xDSL spectrum profile with opmode adsl exists and that the
opmode must be changed to adsl2:
configure xdsl spectrum-profile 5 modification start
configure xdsl spectrum-profile 5 name test_profile
opmode adsl2plus
configure xdsl spectrum-profile 5 modification complete
Purpose
This procedure provides the steps to ping another host.
Procedure
Proceed as follows:
1 Ping another host with the following command:
ping (ip-addr)
(no) timeout <Ip::PingTimeout>
(no) tries <Ip::PingTries>
(no) mtu-size <Ip::PingMtu>
ping 192.168.103.104 tries 3
Purpose
This procedure provides the steps to perform a traceroute action, aiming at determining
the route to a destination address.
Note:
Only one traceroute can be ongoing at any point in time
A traceroute action must be explicitly terminated before a new traceroute action can
be initiated.
Procedure
Proceed as follows to perform a traceroute action:
1 Initiate a traceroute action with the following command:
admin ip traceroute (ip-addr)
(no) max-ttl <Ip::TracerouteTTL>
(no) min-ttl <Ip::TracerouteTTL>
(no) timeout <Ip::TracerouteTimeout>
(no) mtu-size <Ip::TracerouteMtu>
2 Terminate a traceroute action with the following command:
admin ip no traceroute (ip-addr)
3 View the result of a traceroute action with the following command:
show ip traceroute (ip-addr) hop <UnsignedInteger>
admin ip traceroute 192.168.103.104 mtu-size 30
admin ip no traceroute 192.168.103.104
show ip traceroute 192.168.103.104 hop 3
Purpose
This procedure provides the steps to configure the CPE management functionality.
The configuration of the remote CPE management functionality involves:
Enabling the CPE remote management function
Configuring the IP address of the CPE remote manager
Configuring the UDP trap port of the CPE remote manager (optional).
Procedure
Proceed as follows:
1 Configure the CPE remote management function with the following command:
configure cpeproxy
sys-cpemgnt-mode <CpeProxy::CpeProxySystemMode>
ip-address-cpemm <Ip::V4Address>
(no) udpport-cpemgnt <CpeProxy::CpeMgtStationPortNumber>
configure cpeproxy sys-cpemgnt-mode system-enable
ip-address-cpemm 192.168.200.200
Purpose
A script file is a file containing CLI commands, which can be used to restore a
configuration.
Script files are typically stored in the /var/cmd directory.
Warning: the /var/cmd is cleaned when the system resets, so the configuration file must
be transferred to another system with tftp before resetting the system.
Note: saving and restoring the configuration will not work for areas in which resource
identifiers are assigned dynamically by the system.
Procedure
Proceed as follows to create and execute a script file:
1 The complete configuration of the system can be stored in a script with the following
command:
info configure | tee <file.txt>
2 The configuration can be restored on an empty system with the following command:
exec /var/cmd/<file.txt>
info configure | tee config
exec /var/cmd/config
DLP 168 Modify the System
Management IP Parameters
Purpose
This document describes the procedure to modify the system management IP
parameters.
Procedure
Proceed as follows to modify the system management IP parameters :
1 If a default route was defined at the time of creation (see DLP 102), remove the
default route with the following command :
2 Configure the system IP address allocation to dynamic with the following
command:
configure system management host-ip-address bootp
3 Configure the new host IP address of the system with the following command :
configure system management host-ip-address
4 Configure the new default route of the system with the following command :
configure system management default-route <Ip::V4Address>
5 Remove the old SHub IP address with the following command :
configure interface shub ip (vlan-id) no ip-addr
6 Configure the new SHub IP address with the following command :
configure interface shub ip (vlan-id)
7 Change the administrative status of the management vlan on the SHub to down
with the following command :
configure interface shub vlan-id <Vlan::UVlanIndex>
admin-status down
8 Remove the IP address connected to the management vlan on the SHub via the
following command :
configure interface shub ip <Vlan::UVlanIndex>
no ip-addr <Ip::V4Address> / <Ip::PrefixLengthHost>
9 Configure the new IP address to the management vlan on the SHub via the following
command :
configure interface shub ip <Vlan::UVlanIndex>
ip-addr <Ip::V4Address> / <Ip::PrefixLengthHost>
10 Change the administrative status of the management vlan on the SHub to up with
the following command :
configure interface shub vlan-id <Vlan::UVlanIndex>
admin-status up
12 To make the changes effective, the SHub must be restarted with the following
command :
Configuration example
Assumption: the old SHub IP address was 192.168.204.23/24.
configure system management host-ip-address bootp
configure system management host-ip-address
manual:192.168.204.147/24
configure system management default-route 192.168.204.1
configure interface shub ip 4093 no ip-addr
configure interface shub vlan-id 4093 admin-status down
configure interface shub ip 4093 no ip-addr 192.168.204.23/24
DLP 169 Configure Cluster
Management
Purpose
Cluster management in the NE is implemented as follows:
Each node of a cluster still keeps its public IP address.
The EMS manages each node independently via its public IP address, but offers the
possibility to the operator to define clusters at the EMS Graphical User Interface
(GUI) level, and give commands which are valid for the complete cluster (profile
management, backup and restore, software management, alarm management). EMS
then executes the commands sequentially to each DSLAM of the cluster.
The EMS supports topology display, which is made possible by a topology collection
process in the NE. For this topology collection, the NE supports the
neighbor-discovery and topology-collection protocols as defined in the CCSA
cluster management standard.
The EMS defines a command and a backup node for each cluster. Both the command
and the backup node will perform topology collection for the cluster. EMS retrieves the
collected cluster topology from the command node. If the command node fails, EMS
retrieves topology information from the backup node.
The neighbor-discovery protocol is supported in each node of the cluster. It sends
neighbor-discovery packets (with information of its own node) on each of its up- and
subtending links in a regular time-interval (default 60s). Through these packets, each
NE learns its directly connected environment.
A topology-collection protocol is started from the command node. Topology collection
can be done automatically and periodically by the NE (in this case, the EMS is trapped
by the NE if the topology is changed), or the operator on the EMS can start a manual
topology collection request. The NE sends topology request messages on all the links
to its neighbours learned through neighbor discovery. Each neighbor answers with a
topology reply containing info on its directly connected environment. Each neighbor
also forwards the original topology request on its other links, and the second-level
neighbours will answer with topology response messages directly to the command
node using the command nodes MAC address.
With the information received in the topology response messages, the command and
backup nodes are able to construct tables giving the complete topology of a cluster
(including the MAC and IP address of each node).
This procedure provides the steps to configure cluster management.
Procedure
Proceed as follows to configure cluster management:
1 Configure the role of the NE and cluster name with the following command:
configure cluster system name <Cluster::clusterName>
role <Cluster::ClusterRole>
Note: Use this command for each NE that must be part of the cluster.
2 Configure the neighbour discovery on system level with the following command:
configure cluster neighbour
(no) discov-mode <Cluster::DiscoverySystemMode>
(no) interval <Cluster::DiscoveryInterval>
(no) hold-time <Cluster::DiscoveryHoldTime>
Note: By default, the automatic neighbourdiscovery mode is enabled.
3 Configure the topology collection on system level with the following command:
configure cluster collection
(no) collect-sys-off
(no) hop-delay <Cluster::CollectionHopDelay>
(no) port-delay <Cluster::CollectionPortDelay>
(no) scope <Cluster::CollectScope>
(no) interval <Cluster::CollectionInterval>
(no) manual <Cluster::CollectionManualMode>
Note: By default, the automatic topology-collection mode is enabled.
4 Configure the neighbour discovery and topology collection on port level with the
following command:
configure cluster port (port)
(no) discov-port-off
(no) collect-port-off
Note: By default, the automatic neighbour-discovery and topology-collection modes
are enabled on port level.
Figure 16900-1: Cluster Example
In the configuration shown in Figure 16900-1, LS01 is the command node, LS02 is
the backup node, and LS03, LS04, and LS05 are the member nodes.
LS01>#configure cluster system name Cluster1 role command
LS02>#configure cluster system name Cluster1 role backup
LS03>#configure cluster system name Cluster1 role member
Purpose
This procedure provides the steps to configure the SSH functionality.
When configuring SSH, the following must be taken into consideration:
SSH can only be configured by the CLI security administrator
In case of username/password authentication, the operator can login via SSH without
any further configuration. Once logged in, it is advised to disable the non-secure
channels (such as Telnet and TFTP). The operator can now configure the client
username/password for the SFTP client in the Litespan.
Before being able to login with a public key, the operator has to configure the
username/public key to the system, so the Litespan can authenticate the user. In
order to do this, the operator has to:
login via username/password
configure the username/key combinations
change to key authentication.
Again, the operator must make sure that the non-secure channels are closed.
For an SFTP client with public key, the operator has to:
generate the client private/public key pair (if not already done) in the Litespan
read out the username/public key to be stored in the SFTP server, so he can
authenticate the client.
The client private/public key pair generation and the reading of the username/public
can be done via CLI.
Procedure
Proceed as follows to configure the SSH functionality:
1 Configure the SSH server profile (retries, timeout, authentication algorithm, and
encryption algorithm) with the following command:
configure system security ssh server-profile
(no) server-retries <SSH::ServerRetries>
(no) idle-timeout <SSH::ServerIdleTimeOut>
(no) dis-hmac-sha-1
(no) dis-hmac-sha-1-96
(no) dis-aes
(no) dis-des-3
(no) dis-blowfish
(no) dis-des-56
2 Configure the secure shell user and the public-key, to be used while connecting,
with the following command:
configure system security ssh user (name)
key <SSH::SshClientPublicKey>
Note: Public-key is the one which got generated by the SSH Client using
ssh-keygen. Copy only the public-key from the generated output of ssh-keygen.
3 Configure the access channels with the following command:
configure system security ssh access
(no) sftp
(no) dis-cli-ssh
(no) dis-tl1-ssh
4 When necessary, the servers public key can be regenerated with the following
command:
configure system security ssh key-regen <SSH::RegenerateKey>
5 Read out the username/public key to store in the SFTP server with the following
command:
show security ssh server
6 Configure an SFTP user name, for when a client needs to connect, with the following
command:
configure system security ssh sftp-username (username)
password prompt | plain : <SSH::SftpPassword>
configure system security ssh server-profile
no dis-hmac-sha-1 no dis-blowfish
configure system security ssh user 10 key mySecret
configure system security ssh access no dis-tl1-ssh
configure system security ssh access cli-ssh
configure system security ssh key-regen rsa
show security ssh server
configure system security ssh sftp-username JohnDoe
Purpose
This procedure provides the steps to enable the management of EMS.
Procedure
Proceed as follows to enable the management of EMS:
1 Configure the SHub management VLAN filter IP address with the following
command:
configure system shub filter shub-manager (index)
src-ip-addr <Ip::V4Address>
2 Configure the SHub security SNMP community with the following command:
configure system security snmp shub community (index)
privilege <Snmp::SHubCommunityPrivilege>
configure system shub filter shub-manager 1
src-ip-addr 192.168.172.172
configure system security snmp shub community 1
name Community1 privilege read-write
DLP 172 Create a Default Operator
Profile
Purpose
This command allows the superuser to specify a default operator profile.
This default profile is used when an operator is authenticated via a RADIUS server, but
the RADIUS server does not support Vendor Specific Attributes.
This operator profile determines most of the operator properties.
Procedure
Proceed as follows to create a default operator profile:
1 Create a default operator profile with the following command:
configure system security default-profile (name)
(no) password-timeout <Sec::PasswordTimeout>
(no) terminal-timeout <Sec::InactivityTimeout>
(no) description <Sec::ProfileDesc>
(no) aaa <Sec::Aaa>
(no) atm <Sec::Atm>
(no) alarm <Sec::Alarm>
(no) dhcp <Sec::Dhcp>
(no) equipment <Sec::Equipment>
(no) igmp <Sec::Igmp>
(no) ip <Sec::Ip>
(no) ppoe <Sec::Ppoe>
(no) qos <Sec::Qos>
(no) software-mngt <Sec::Sw>
(no) transport <Sec::Transport>
(no) vlan <Sec::Vlan>
(no) xdsl <Sec::Xdsl>
(no) security <Sec::Security>
configure system security default-profile
no prompt
password-timeout 10
terminal-timeout 30
description superuser
aaa read
atm read
alarm write
no dhcp
equipment write
no igmp
ip write
ppoe write
qos write
software-mngt write
transport write
vlan write
xdsl write
security write
Task 100 Create an IPoA Cross-Connect User
Task 100 Create an IPoA
Cross-Connect User
Purpose
This procedure provides the steps to create an IPoA cross-connect user.
Prerequisites
The following prerequisites must be fulfilled before an IPoA cross-connect user can be
created:
Procedure
Proceed as follows to create an IPoA cross-connect user:
(no) ansi-t1413
(no) etsi-dts
(no) g992-1-a
(no) g992-1-b
(no) g992-2-a
(no) g992-3-a
(no) g992-3-b
(no) g992-3-l1
(no) g992-3-l2
(no) g992-3-am
(no) g992-5-a
(no) g992-5-b
(no) ansi-t1.424
(no) etsi-ts
(no) itu-g993-1
(no) ieee-802.3ah
(no) g992-5-am
(no) admin-up
xdsl-line:<Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::LtSlot>
Task 100 Create an IPoA Cross-Connect User
/<Eqpt::Port>
admin-up
(no) admin-down
(no) aal5-encap-type llc-snap-routed | vc-mux-routed
| automatic:ip
4 Create an IWL with the following command:
configure atm ip-cross-connect (interworking-port)
(no) cpe <Ip::V4Address>
(no) next-hop <Ip::V4Address>
configure atm pvc 1/1/5/12:8:35 aal5-encap-type vc-mux-routed
configure atm ip-cross-connect 1/1/5/12:8:35 cpe 192.168.100.17
next-hop 192.168.100.16
Purpose
This document describes the procedure to configure the system management IP
parameters.
Prerequisites
Communities must be configured on the SHub. The following commands give an
example:
configure system security snmp shub community 1 name NETMAN
privilege read-write ip-addr 127.0.0.2
configure system security snmp shub community 2 name PUBLIC
Procedure
Proceed as follows to configure the system management IP parameters:
1 Configure the system ID parameters with the following command:
mgnt-vlan-id <Vlan::VlanId>
system-mac <Sys::MacAddr> / <Sys::MacAddr> / <Sys::Range>
single-public-ip
2 Configure the host IP address of the system with the following command:
Note: In case of manual configuration of the IP addres: If the system IP address is
not configured (default 0.0.0.0), the users session setup requests are refused.
3 Configure the SNMP community name public with the following command:
4 Configure the SNMP community name NETMAN with the following command:
configure system security snmp community NETMAN
context shub
mgnt-vlan-id 100
system-mac 99:62:12:34:56:5B/98:45:43:6B:35:78/24
single-public-ip
manual:192.168.203.189/24
host-address 192.168.203.189/24
configure system security snmp community NETMAN
host-address 192.168.203.189/24 context shub
Task 100 Configure the Default Security Domain
Task 100 Configure the Default
Security Domain
Purpose
This procedure provides the steps to configure a default security domain to be used in
case PPP clients do not provide a domain name.
Prerequisites
The following prerequisites must be fulfilled before a default security domain can be
created:
A RADIUS server must have been configured; see DLP 144.
Procedure
Proceed as follows to configure the default security domain:
authenticator radius:<Aaa::RadPolicyName>
2 Configure the connection profile parameters with the following command:
configure system security conn-profile (name)
no reject-no-domain
domain-name <Aaa::DomainName>
3 Configure the security connection policy with the following command:
configure system security conn-policy conn-profile-name
<AsamProfileName>
In the following example, a default security domain with name unspecified is
created. The connection profile is named no-domain.
configure system security domain unspecified
authenticator radius:YourRadPolicy
configure system security conn-profile no-domain version 1
no reject-no-domain domain-name unspecified
configure system security conn-policy
conn-profile-name no-domain
Task 100 Configure the Default Security Domain

RTP 100 Backup the Configuration
RTP 101 Restore the Configuration
RTP 102 Retrieve Remote Inventory

Purpose
This procedure provides the steps to back up the NT database.
General
The SHub database is part of the NT database and is saved automatically at regular
intervals towards the NT database.
As there might be a difference between the last automated save of the SHub database
and the actual contents of the Shub database, it is recommended to manually save the
SHub database before performing a backup of the NT database.
The TFTP deamon on the AWS assumes a default home directory
/var/opt/aws/equipment.
The TFTP deamon on the AMS assumes a default home directory
/opt/ALAams/systemdata.
This means that all the tftps initiated from the Litespan result in a file written relative to
this point.
The filename of the database is dm_complete.tar.
Prerequisite
An empty file dm.tar must exist in the specified path on the FTP server before the upload
is started. Otherwise, the upload will fail (error upload-error : file-not-found).
Note: The superuser must create this file.
Create the dm_complete.tar file on the FTP server with the following commands ($
prompt is regular user, # prompt is superuser):
$ su
# cd /var/opt/aws/equipment/temp
(*)
# touch dm_complete.tar
# chmod 666 dm_complete.tar
# exit
$
The NT database can now be backed up.
Note:
(*)
For AMS, the command is cd /opt/ALAams/systemdata
Procedure
Proceed as follows to back up the NT database:
1 Back up the NT database (and SHub database) with the following command:
admin software-mngt database upload
actual-active:<Ip::V4Address>:<SwMngt::path>
where <IP::V4Address> is the IP address of the AMS or AWS server.
Example:
admin software-mngt database upload
actual-active:1.1.1.1:/dm_complete.tar
2 View the status of the database upload process and, in case of an upload failure,
the reason, with the following command:
show software-mngt upload-download
Purpose
This procedure provides the steps to restore the NT database (and SHub database) .
The filename of the database is dm_complete.tar.
Procedure
Proceed as follows to restore the NT database:
1 Download the database with the following command:
admin software-mngt database download
<Ip::V4Address>:<SwMngt::path>
where <IP::V4Address> is the IP address of the AMS or AWS server.
Example:
admin software-mngt database download 1.1.1.1:/dm_complete.tar
2 View the status of the database download process and, in case of an download
failure, the reason, with the following command:
show software-mngt upload-download
3 Activate the downloaded database with the following command:
admin software-mngt oswp (index current oswp) activate
with-linked-db
Example:
admin software-mngt oswp 1 activate with-linked-db
Purpose
This procedure provides the steps to retrieve and show the remote inventory information.
Table 10200-1 describes the RI information that is shown.
Table 10200-1: RI information
Procedure
Proceed as follows to retrieve and show remote inventory information:
1 View the RI information with the following command:
show equipment slot <Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::Slot>
detail
RI information Description
manufacturer An identification of the board manufacturer
inventory-pba The Alcatel Printed Board Assembly code of the code
inventory-fpba The Alcatel Printed Board Assembly code of the board, which also identifies the
boot software
inventory-ics The Item Change Status iteration code of the board
inventory-clie The (USA) Common Language Equipment Identification code of the board
serial-no The serial number of the board

TAP 101 F5 Loopback Test
TAP 102 Equipment Repair
TAP 103 Fault isolation and troubleshooting

Purpose
This procedure provides the steps to perform an F5 loopback end-to-end test on the NE.
Procedure
Proceed as follows to perform an F5 loopback test:
1 Start an F5 loopback test with the following command:
admin atm port (port) f5-loopback-ete start
Example:
admin atm port 1/1/4/1 : 8:35 f5-loopback-ete start
Note: The result of the test can be obtained with an info command.
Purpose
This procedure provides the steps to perform equipment repair on the NE.
Procedure
Proceed as follows to perform equipment repair tasks:
1 Lock equipment (mostly plug-in units); see DLP 112.
2 Shut down individual equipment; see DLP 153.
3 Pull out equipment.
Note: The NE does not keep time while the card is unplugged from the shelf. In
order for the time to be synchronized when the card boots up, it must be set to use
SNTP time synchronization with the management station. See DLP 103.
4 Replan equipment (for example, plug-in units); see DLP 111.
5 Plug in equipment.
6 Power up individual equipment; see DLP 153.
7 Unlock equipment (mostly plug-in units); see DLP 112.
8 Start up or shut down the system, select one of:
a Shut down or restart the SHub; see DLP 151.
b Reboot the entire system; see DLP 152.
Task 100 Fault isolation and troubleshooting
Task 100 Fault isolation and
troubleshooting
Purpose
This TAP provides steps to use the EMS (AWS or AMS) to isolate a problem indicated by
an alarm appearing in the EMS Event Viewer.
General
Resolve alarms that affect service before the alarms that do not affect service.
Use local procedures to correct problems associated with customized alarms.
Contact Alcatel customer technical assistance at 1-888-252-2832 (1-888-ALCATEC)
when a problem cannot be corrected.
Use alarm information obtained from the EMS Event Viewer during analysis. Use the TL1
or CLI autonomous messages generated during trouble locating and additional data,
such as visual or audible alarms, when available. Service states should also be
considered.
See the CLI Commands document for information on CLI syntax. See the TL1
Commands and Messages document for information on TL1 syntax.
Several of the protocols in this TAP may require the assistance of someone familiar with
UNIX systems and commands. Many of the UNIX troubleshooting protocols and most of
the UNIX commands require root access. If this is the case, Alcatel recommends that a
UNIX system administrator perform the troubleshooting.
Caution When an alarm has been disabled by the user, it is not
generated or displayed in the Event Viewer.
Alarms are identified by the following attributes, as listed in Table 10300-1:
Alarm ID (No.) unique identification of the alarm
Category category of the alarm:
communication (Com)
processing errors (Proc)
quality of service (QoS)
environmental (Envir)
equipment (Equip)
Severity level of severity assigned to the alarm:
indeterminate
warning
minor
major
critical
Service affecting specifies whether the alarm is service-affecting (SA) or not
service-affecting (NSA)
Report mode used to enable (ON) or disable (OFF) the reporting of the alarm
Logging mode used to enable (ON) or disable (OFF) the logging mode of the alarm
Procedure
Use this procedure to isolate a fault indicated by an alarm.
1 Click on the Events icon in the EMS Access Manager window.
The Event Viewer window opens and shows Standing NE Alarms; see
Figure 10300-1.
Figure 100-1: Standing NE Alarms window
2 Select the alarm you want to view.
An associated message appears at the bottom of the window.
3 Use Tables 10300-1 and 10300-2 to help you determine the cause of the alarm and
the appropriate action for resolving the alarm. You can use the category column of
the table to help locate an alarm in the table. Some alarms are not currently
supported.
Table 100-1: Alarm definitions
Note If multiple alarms are present, resolve alarms in the order listed
below:
Critical (red)
Major (orange)
Minor (yellow)
Alarm
(1)
No. Class Severity Service-
affecting
Report
mode
Logging
mode
Description
Alarm type = Equip (1); Index1 = eqptHolderld (index in equipment holder Table), Index22 = not used
No defects 0
(1 of 16)
Persistent data loss 1 Equip Critical SA ON ON System has lost all
persistent data after
RESTART. System is
not configured.
SNTP communication lost 2 Equip Major NSA ON ON The SNTP server does
not respond to the
requested messages.
NT disk 90% full 4 Equip Major NSA ON ON The NT disk has
reached a 90% full
level.
System clock not using
preferred timing mode
5 Com Major SA ON ON The system is
configured to work in
autonomous mode with
both timing modes
allowed and is not
using the preferred
timing mode because
all timing references
corresponding to the
preferred timing mode
are in failure.
System clock in holdover
mode or in free-run mode
6 Com Critical SA ON ON The system is
configured to work in
autonomous mode and
is either in holdover or
free-run mode because
all timing references
are in failure.
LANX loss of contact 8 Equip Critical SA ON ON Loss of contact with the
SHub. NT cannot
communicate with the
SHub.
Alarm type = EquipHolder (2); Index1 = eqptHolderId (index in equipment holder Table), Index2 = not used
No defects 0
Rack power 1 Equip Minor NSA ON ON Power fuse broken.
Rack fan unit 1 2 Equip Major NSA ON ON Fan unit 1 in rack
failing.
Rack fan unit 2 3 Equip Major NSA ON ON Two or more of the fans
in the rack have failed.
The rack will shut down
in approximately 2 min.
Shelf-type mismatch 7 Equip Minor NSA ON ON Shelf detected, but its
actual shelf type is
either unknown or it
differs from the planned
shelf type.
Extension chain
installation
8 Equip Critical SA ON ON A consistency problem
has been detected with
the installation of the
extension chain or
multiple chains.
Alarm
(1)
affecting
Report
mode
Logging
mode
Description
(2 of 16)
Shelf missing 9 Equip Major SA ON ON Shelf is planned, but no
shelf detected. A shelf
has been detected at
least once since it was
planned.
Alarm type = EquipHolder (2); Index 1 = eqptHolderId (index in equipment holder table to identify a shelf), Index 2 =
not used
No defects 0
Door 15 Envir Minor NSA ON ON Open cabinet door.
Applies only to the
ARAM-D shelf.
Fuse 17 Equip Critical NSA ON ON An indication has been
detected that exactly
one power feed is
inoperative within a
shelf. This can be due
to no input power or a
blown fuse.
This alarm applies to
the ARAM-B and
ARAM-D shelves.
Single fan 18 Equip Major NSA ON ON One or more of the
shelfs fans has failed.
This alarm applies to
the ARAM-B and
ARAM-D shelves.
Double fan 19 Equip Critical SA ON ON Two or more fans in the
shelf have failed, or the
fan tray was removed.
The shelf on which the
failure occurred will
automatically power
down after a fixed
delay.
This applies only to
ARAM-D shelves.
The ARAM-D shelf can
be a standalone, a
host, or an expansion
shelf.
System ac power failure 20 Envir Critical SA ON ON The shelf will shut
down in 15 min.
This alarm is externally
provided.
Alarm type = PlugInUnit (3); Index1 = eqptSlotId (index in equipment Board Table), Index2 = not used
No defects 0
Board-type mismatch 3 Equip Minor NSA ON ON Unit detected, but its
actual unit type is either
unknown or it differs
from the planned unit
type. This alarm
applies to all unit types:
NT, LSM, applique, and
ACU units.
Alarm
(1)
affecting
Report
mode
Logging
mode
Description
(3 of 16)
Waiting for software 4 Equip Major NSA ON ON This alarm is raised
when the system
cannot download all the
applicable software
files (supported by the
active OSWP) towards
the unit. The following
situations can be
distinguished:
The extender/LSM
unit belongs to a
unit type that the
active OSWP does
not support.
The detected LSM
unit belongs to a
unit type that the
active OSWP
supports.
However, one or
more of the
applicable SW files
are no longer
available on the file
disk of the NT unit.
Temperature exceeded 8 Equip Major NSA ON ON The temperature
threshold on the unit is
exceeded. This alarm
applies to NT and LSM
units.
Temperature shutdown 12 Equip Major SA ON ON The unit has powered
off as a result of
temperatures that are
too high. This alarm
applies only to LSMs
unit.
Defense 13 Equip Critical SA ON ON The plug-in unit is
disconnected from the
system as a means of
defense. The reason
for disconnecting
depends on the plug-in
unit type and the cause
of the failure:
LSM: disable or power
down
Board missing 14 Equip Major SA ON ON Unit is planned, no unit
is detected, but a unit
has been detected at
least once since it was
planned. This alarm
applies to all unit types:
NT, EDSE-A, SATU-A,
LSM, applique, and
ACU units.
Alarm
(1)
affecting
Report
mode
Logging
mode
Description
(4 of 16)
Alcatel 1540 Litespan Giga Ethernet Controller vii
Board installation missing 15 Equip Minor NSA ON ON Unit is planned, no unit
is detected, and no unit
has ever been detected
since it was planned.
This alarm applies to all
unit types: NT, LSM,
applique, and ACU
units.
Board initialization 16 Equip Major SA ON ON A unit initialization
failure has been
detected. This alarm
applies only to LSM
units.
Board reset protection 17 Equip Major SA ON ON The number of unit
reset within a certain
timeframe exceeded
the threshold. This
alarm applies only to
LSM units.
Board reset or
communication failure
30 Equip Major SA ON ON The LT unit has reset
(alarm on followed by
alarm off), or there is a
communication failure
(alarm on).
Alarm type = ATM (8); Index1 = ifIndex (of ATM physical port), Index2 = see specific alarm number
No defects 0
Connection
(3)
1 Equip Major SA ON ON A planned VPI/VCI
could not be marked as
a result of hardware
problems.
Remark index2 = VPC
Cell discard up (CDU) 2 QoS Minor SA OFF OFF ATM cell discarded in
the upstream direction.
Remark index2 =
VPI/VCI
Cell discard down (CDD) 3 QoS Minor SA OFF OFF ATM cell discarded in
the downstream
direction.
Remark index2 =
VPI/VCI
ASAM MAC conflict 6 Com Minor SA OFF ON Duplicate MAC
address from this PVC
(the port with the latter
coming MAC address
caused the conflict).
Remark index2 =
VPI/VCI
Detailed information,
such as the conflicting
MAC address and the
port on which the MAC
address was first
learned, can be
retrieved with the
diagnostics tool.
(2)
Alarm type = CustomizableAlarm (10); Index1 = Rack_ID (position of the rack, range 0 to 5), Index2 = not used
Alarm
(1)
affecting
Report
mode
Logging
mode
Description
(5 of 16)
viii Alcatel 1540 Litespan Giga Ethernet Controller
No defects 0
Customizable alarm 1 1 Envir Indeter-
minate
NSA ON ON
minate
NSA ON ON
minate
NSA ON ON
minate
NSA ON ON
minate
NSA ON ON
Alarm type = CustomizableAlarm (10); Index1 = eqptHolderID (shelf index in equipment holder table), Index2 = not
used
No defects 0
Alarm type = Redundancy (20); Index1 = not used, Index2 = not used
No defects 0
Switchover capability lost 1 Equip Major NSA ON ON Switchover capability in
a redundant system
has been lost.
Alarm type = EthItf (24); Index1 = ifIndex (of Ethernet port), Index2 = see specific alarm number
No defects 0
Ethernet port IP address
conflict
(3)
1 Com Critical NSA ON ON There is an IP address
conflict on the Ethernet
port.
Ethernet link down 2 Com Critical SA ON ON Ethernet down alarm.
Index2 = not used.
Alarm type = SwMgnt (29); Index1 = eqptSlotId (index in equipment Board Table for the NT), Index2 = not used
No defects 0
Implicit software rollback 1 Proc Major SA ON ON The system cannot
make the NotActive
OSWP and linked
database operational
(although no error in
the database is
detected). The system
performs an implicit
rollback to the previous
active OSWP (and
linked database).
Alarm
(1)
affecting
Report
mode
Logging
mode
Description
(6 of 16)
Alcatel 1540 Litespan Giga Ethernet Controller ix
Implicit database rollback 2 Proc Major SA ON ON The system cannot
make the selected
OSWP and linked
database operational
(an error is detected in
the linked database).
The system comes up
with the selected
OSWP and the
previous linked
database (if possible).
Autofetch failure
(3)
3 Proc Minor SNA ON ON The system cannot
fetch a specific file from
the corresponding file
server. The name of
the file that caused the
failure is sent together
with the alarm.
Alarm type = xDSL (38); Index1 = ifIndex (of xDSL physical port), Index2 = not used
No defects 0
Near end LOS 1 Com Minor SA ON ON Near End Loss of
Signal.
Near end LOF 2 Com Minor SA ON ON Near End Loss of
Frame.
Near end LOM 3 Com Minor SA ON ON Near End Loss of
Margin.
Near end ESE 4 Com Minor SA ON ON Near End Excessive
Server Errors.
Activation failure -
configuration error
5 Com Critical SA ON ON Line configuration data
cannot be used.
configuration not feasible
6 Com Major SA ON ON Line capacity not high
enough to set up
requested profile.
Near end - bit rate
threshold
7 Com Minor SA ON ON Upstream Planned Bit
rate not reached after
initialization.
Near end - NCD 8 Com Minor SA ON ON Near End No Cell
Delineation.
Near end - LCD 9 Com Minor SA ON ON Near End Loss of Cell
Delineation.
Far end - LOS 10 Com Minor SA ON ON Far End Loss of Signal.
Far end - LOF 11 Com Minor SA ON ON Far End Loss of Frame.
Far end - LPR 12 Com Minor SA ON ON Far End Loss of Power
(dying gasp detected).
Far end - LOL 13 Com Minor SA ON ON Far End Loss of Link
(no dying gasp
detected).
Far end - LOM 14 Com Minor SA ON ON Far End Loss of
Margin.
Alarm
(1)
affecting
Report
mode
Logging
mode
Description
(7 of 16)
x Alcatel 1540 Litespan Giga Ethernet Controller
Far end - ESE 15 Com Minor SA ON ON Far End Excessive
Severe Errors.
communication problem
16 Com Major SA ON ON No successful
initialization as a result
of communication
problems.
Activation failure - no peer
modem detected
17 Com Minor SA ON ON No peer modem
detected.
Far end - bit rate
threshold
18 Com Minor SA ON ON Downstream Planned
bit rate not reached
after initialization.
Far end - NCD 19 Com Minor SA ON ON Far End No Cell
Delineation.
Far end - LCD 20 Com Minor SA ON ON Far End Loss of Cell
Delineation.
Alarm type = xDSLTca (39); Index1 = ifIndex (of xDSL physical port), Index2 = not used
No defects 0
Near end - errored
seconds
1 QoS Minor NSA ON ON The number of errored
seconds encountered
by the ADSL line in the
current 15-minute
interval has reached its
threshold value.
Near end - severely
errored seconds
2 QoS Minor NSA ON ON The number of severely
errored seconds
encountered by the
ADSL line in the current
15-minute interval has
reached its threshold
value.
Near end - unavailable
seconds
3 QoS Minor NSA ON ON The number of
unavailable seconds
encountered by the
value.
Near end - errored
seconds in a day
seconds encountered
by the ADSL line in the
current one-day
threshold value.
Near end - severely
errored seconds in a day
errored seconds
encountered by the
one-day interval has
value.
Alarm
(1)
affecting
Report
mode
Logging
mode
Description
(8 of 16)
Alcatel 1540 Litespan Giga Ethernet Controller xi
Near end - unavailable
seconds in a day
unavailable seconds
encountered by the
value.
Far end - errored seconds 7 QoS Minor NSA ON ON The number of errored
seconds encountered
by the ADSL far-end
line in the current
value.
Far end - severely errored
seconds
errored seconds
encountered by the
ADSL far-end line in
the current 15-minute
threshold value.
Far end - unavailable
seconds
unavailable seconds
encountered by the
the current 15-minute
threshold value.
Far end - errored seconds
in a day
seconds encountered
by the ADSL far-end
line in the current
value.
Far end - severely errored
seconds in a day
errored seconds
encountered by the
the current one-day
threshold value.
Far end - unavailable
seconds in a day
unavailable seconds
encountered by the
the current one-day
threshold value.
Alarm type = eoConversion (50); Index1 = 100BASE-FX port identification (1 to 4 for ISAM), Index2 = not used
No defects 0
E/O conversion LOS 1 Equip Major SA ON ON E/O conversion module
loss of signal.
E/O conversion TX fault 2 Equip Major SA ON ON E/O conversion module
transmission fault.
Alarm
(1)
affecting
Report
mode
Logging
mode
Description
(9 of 16)
xii Alcatel 1540 Litespan Giga Ethernet Controller
Alarm type = bonding (54); Index1 = IfIndex (of bonding group), Index2 = not used
No defects 0
Bonding group upstream
planned bit rate threshold
1 Com Minor SA ON ON Group upstream actual
bit rate is above group
upstream minimum bit
rate but below group
upstream planned bit
rate.
minimum bit rate
threshold
2 Com Major SA ON ON Group upstream actual
bit rate dropped below
group upstream
minimum bit rate.
3 Com Major SA ON ON Group upstream actual
bit rate is not high
enough to set up the
configured group
upstream minimum bit
rate.
Bonding group
downstream planned bit
rate threshold
4 Com Minor SA ON ON Group downstream
actual bit rate is above
group downstream
minimum bit rate but
below group
downstream planned
bit rate.
Bonding group
downstream minimum bit
rate threshold
5 Com Major SA ON ON Group downstream
actual bit rate dropped
below group
downstream minimum
bit rate.
Bonding group
downstream configuration
not feasible
6 Com Major SA ON ON Group downstream
actual bit rate is not
high enough to set up
the configured group
downstream minimum
bit rate.
Alarm type = authentication (55); Index1 = ifIndex of interface on which authentication occurs (for example, the bridge
port interface for 802.1x, the PPPoE interface for PPPoE), Index2 = not used
No defects 0
VRF assignment failure 1 Proc Major SA ON ON Failure to assign a VRF
for a user session:
unknown VRF:
VRF returned by
RADIUS server is
not locally
configured in the
system; or
no VRF: RADIUS
server did not
return a VRF while
no default VRF is
locally configured
for the domain.
Alarm
(1)
affecting
Report
mode
Logging
mode
Description
(10 of 16)
Alcatel 1540 Litespan Giga Ethernet Controller xiii
VLAN assignment failure 2 Proc Major SA ON ON Failure to assign a
VLAN for a user
session:
unknown VLAN:
VLAN returned by
RADIUS server is
not locally
configured in the
system; or
no VLAN: RADIUS
server did not
return a VLAN
while no default
VRF is locally
configured for the
domain.
IP address pool
assignment failure
3 Proc Major SA ON ON Failure to assign an IP
address pool:
unknown pool-id:
pool-id returned by
the RADIUS server
is not locally
configured in the
system; or
no pool-id: no pool
id is returned by the
RADIUS server
while no pool is
assigned to the
domain; or
pool
administratively
locked: pool-id
returned by the
RADIUS server is
administratively
locked; or
VRF of the pool is
not consistent: this
can occur in the
following cases:
RADIUS server
returns a pool-id:
VRF of the
returned pool-id is
different from the
VRF of the
configured domain
RADIUS server
returns pool-id and
VRF: VRF of the
returned pool-id is
different from the
returned VRF
Alarm
(1)
affecting
Report
mode
Logging
mode
Description
(11 of 16)
xiv Alcatel 1540 Litespan Giga Ethernet Controller
QoS parameters
assignment failure
4 Proc Major SA ON ON Failure to assign QoS
parameters for a user
session:
unknown QoS
profile: QoS profile
returned by the
RADIUS server is
not locally
configured in the
system; or
QoS parameters
syntax error: QoS
parameters
returned by the
RADIUS server
contain a syntax
error.
IP address assignment
failure
5 Proc Major SA ON ON Failure to assign IP
address for a user
session:
IP address already
in use: IP address
returned by the
RADIUS server is
already allocated
for another user; or
no IP address
available: no IP
address available
in the IP address
pool of the domain
or in the IP address
pool returned by
the RADIUS
server.
Missing attributes 6 Proc Major SA ON ON RADIUS server should
always specify a
pool-id when it returns
a VRF.
Alarm type = IpoX (68); Index1 = ifIndex of IpoX interface on which session takes place, Index2 = not used
No defects 0
IP address preemption 1 Com Major SA ON ON A new IP session is
established with a user
IP address previously
assigned to another IP
session and the
previous session has
lower or equal
precedence with the
new one. The previous
session is terminated
and its IP address
preempted.
Alarm type = SFP (76); Index 1 = ifIndex of IPoX interface on which the session takes place, Index 2 = not used
No defects 0
Alarm
(1)
affecting
Report
mode
Logging
mode
Description
(12 of 16)
Alcatel 1540 Litespan Giga Ethernet Controller xv
Host SFP LOS 1 Com Critical SA ON ON Host shelf downlink
SFP loss of signal.
Host SFP Tx fail 2 Com Critical SA ON ON Host shelf downlink
SFP transmission
failure.
Host SFP missing 3 Com Critical SA ON ON Host shelf downlink
SFP detected but later
removed.
Host SFP invalid Alcatel
ID
4 Com Critical SA ON ON Host shelf downlink
SFP does not have a
valid Alcatel ID.
Host SFP control fail 5 Com Critical SA ON ON Host shelf downlink
SFP control failure.
Alarm type = SFP (76); Index 1 = eqptSlotId of corresponding LSM in ES, Index 2 = not used
No defects 0
ES SFP LOS 11 Com Critical SA ON ON Expansion Shelf SFP
loss of signal.
ES SFP TX fail 12 Com Critical SA ON ON Expansion Shelf SFP
transmission failure
ES SFP missing 13 Com Critical SA ON ON Expansion Shelf SFP
detected but later
removed
ES SFP invalid Alcatel ID 14 Com Critical SA ON ON Expansion Shelf SFP
does not have a valid
Alcatel ID.
ES SFP control fail 15 Com Critical SA ON ON Expansion Shelf SFP
control failure.
Alarm type = LLURelay (78); Index 1 = eqptSlotId (index in equipment board table), Index 2 = not used
No defects 0
Wrong applique for LLU 1 Com Major SA ON ON LLU relay set for some
ports but applique
inserted in slot is not
compatible with LLU
relay
Alarm type: LANX (51); Index1 = not used, Index2 = not used
No defects 0
LANX fan failure 1 Eqp Major NSA ON ON The SHub fan is not
functioning.
LANX power fan failure 2 Eqp Major NSA ON ON The SHub fan in the
power supply is not
functioning.
LANX database restore 3 Eqp Major SA ON ON The SHub database
restore has failed.
Emergency reboot 4 Eqp Major NSA ON ON The SHub has
rebooted from the
emergency boot
package.
Alarm
(1)
affecting
Report
mode
Logging
mode
Description
(13 of 16)
xvi Alcatel 1540 Litespan Giga Ethernet Controller
LANX SNTP
communication lost
5 Eqp Major NSA ON ON The SNTP server does
not respond to the
requested messages
from the SHub.
No ARP reply received for
next IP HOP
6 Com Major SA ON ON An ARP request has
been sent for a
statistically configured
next hop, but no ARP
reply has been
received in the
specified time interval.
Index1 = VRF ID
Index2 = IP address of
next hop
Alarm type = ethLanx (52); Index1 = port identification of LANX Ethernet port, Index2 = see specific alarm number
No defects 0
LANX Ethernet link down 1 Com Critical SA ON ON Ethernet link down
alarm.
Index 2 not used.
Ethernet Frame
discarded
(3)
2 QoS Minor SA ON ON The Ethernet frame has
been discarded due to
buffer overflow.
Index2 = not used
LANX MAC conflict 3 Com Minor SA ON ON Duplicate MAC
address from Ethernet
port of LAN switch.
Index 1 = port with the
latter coming MAC
address that causes
conflict.
Index 2 = VLAN ID of
domain on which the
conflict happened.
LANX MAC learning
(3)
4 Com Minor SA ON ON The MAC address
cannot be learned,
because it is learned on
a high-priority Ethernet
port of the LAN switch.
Index1 = the port with
the lower priority
Index2 = VLAN ID: the
VLAN domain on which
the conflict occurred
Alarm
(1)
affecting
Report
mode
Logging
mode
Description
(14 of 16)
Alcatel 1540 Litespan Giga Ethernet Controller xvii
Alarm type = OSPF (69); Index 1 = VRF-ID (VRF unique ID), Index 2 = see specific alarm number
No defects 0
OSPF interface
configuration error
1 Com Minor NSA ON ON Received a packet
with:
OSPF version
mismatch
area mismatch
(area ID or subnet
ID not matching)
netmask mismatch
hello interval
mismatch
dead interval
mismatch
options mismatch
Index2 = interface
index
OSPF interface
authentication error
2 Com Minor NSA ON ON Received a packet with
authentication type
mismatch
authentication
failure
Index2 = interface
index
OSPF interface received
bad packet
3 Com Critical SA ON ON Received a packet that
cannot be parsed.
Index2 = interface
index
OSPF LSDB approaching
overflow
4 Com Major NSA ON ON The external LSA
database has reached
90% of the external
LSA limit.
Index2 = LSDB limit
(percentage utilized)
OSPF LSDB overflow 5 Com Major NSA ON ON The external LSA count
has reached the
external LSA overflow
limit.
Index2 = LSDB limit
(percentage used)
OSPF neighbor state
change
6 Com Minor SA ON ON An OSPF neighborship
is newly established or
dismantled.
Index2 = interface
index (interface on
which the neighbor was
learned)
Alarm
(1)
affecting
Report
mode
Logging
mode
Description
(15 of 16)
xviii Alcatel 1540 Litespan Giga Ethernet Controller
Notes
(1)
The alarm names are listed exactly as they appear in the CLI.
(2)
See the Duplicate Mac Alarm Status command in the CLI Commands document for more information.
(3)
This alarm is not currently supported in the system.
Table 100-2: Troubleshooting alarms
OSPF interface state
change
7 Com Minor SA ON ON The OSPF interface
status has changed
(the DR or BDR may
have been changed
according to this OSPF
interface.
Index2 = interface
index (interface on
which the neighbor was
learned)
Alarm type = RIP (70); Index1 = VRF ID (VRF unique ID), Index2 = interface index
No defects 0
RIP interface
configuration error
1 Com Minor SA ON ON Received a packet
with:
RIP version
mismatch
netmask mismatch
RIP interface
authentication error
2 Com Minor SA ON ON Received a packet with
authentication type
mismatch
authentication
failure
RIP interface received
bad packet
3 Com Minor SA ON ON Received a packet that
cannot be parsed.
Alarm type = LANXuplinkgroup (75); Index1 = uplink group number, Index2 = not used
LANX uplink group down 7 Com Major SA ON ON The SHub uplink group
is down.
Alarm
(1)
affecting
Report
mode
Logging
mode
Description
(16 of 16)
Alarm
(1)
No. Advice for repair
Alarm type = Equip (1)
Persistent data loss 1 Reconfigure system.
SNTP communication lost 2 Check SNTP server.
NT disk 90% full 4 Clean up disk space.
System clock not using preferred timing
mode
5 Check all timing references that correspond to
the preferred timing mode for the peer
equipment and the link between the peer
equipment and the system.
(1 of 8)
Alcatel 1540 Litespan Giga Ethernet Controller xix
System clock in holdover or free-run
mode
6 Check all timing references for the peer
equipment and the link between the peer
equipment and the system.
LANX loss of contact 8 Check the external LAN switch.
Alarm type = EquipHolder (2)
Rack power 1 Check power supplies.
Rack fan 1 2 Check the fan.
Rack fan 2 3 Check the fan.
Shelf-type mismatch 7 Check equipment.
Check configuration.
Extension chain installation 8 Check cabling of the extension cable.
Shelf missing 9 Check presence of GENC on host shelf.
Check cabling to ES.
Check presence of EDSE on ES.
Check presence of LT on ES.
Check presence of PWIO-B on ES.
Check fan on ES.
Check power cable on ES.
Alarm type = EquipHolder (2)
Door 15 Close the door.
Fuse 17 Check fuse.
Check power feed.
Single fan 18 Check fan tray (the LED of the faulty fans tray
is lit red).
Double fan 19 Check fan tray of shelf that raised the alarm.
The shelf will power off within 3 min. of the
alarm.
System ac power failure 20 Check power installation.
Alarm type = PlugInUnit (3)
Board-type mismatch 3 Check configuration.
Waiting for software 4 Check configuration.
Download software.
Temperature exceeded 8 Check fans and restarts unit.
Temperature shutdown 12 Check ambient temperature.
Check operation of fans.
Check unit.
Defense 13 Replace unit.
Board missing 14 Check unit presence.
Board installation missing 15 Insert unit.
Board initialization 16 Force a cold reset of unit, and if this fails
again, repair unit.
Board reset protection 17 Force a cold reset of unit, and if this fails
again, repair unit.
Alarm
(1)
(2 of 8)
xx Alcatel 1540 Litespan Giga Ethernet Controller
Board Reset or Communication Failure 30 Check cabling if alarm is persistent.
If alarm toggles frequently, the board will go in
Board Reset Protection mode (alarm 3, 17)
and power down.
Alarm type = ATM (8)
Connection
(2)
1
Cell discard up (CDU) 2 No local repair action. Sender must lower
shaping rate.
Cell discard down (CDD) 3 No local repair action. Sender must lower
shaping rate.
ASAM MAC conflict 6 Use the diagnostic tool to find the detailed
information.
(3)
Alarm type = CustomizableAlarm (10)
Customizable alarm 1 1
Alarmtype = Redundancy (20)
Switchover capability lost 1 Check link on standby NT.
Check standby boards.
Wait for Quench timeout.
Alarm type = Ethltf(24)
Ethernet port IP address conflict
(2)
1
Ethernet link down 2 Check the Ethernet link.
Alarm type = SwMgnt (29)
Implicit software rollback 1 Remove the corrupted OSWP (ABORT
operation).
Download the desired OSWP again.
Activate the downloaded OSWP.
Implicit database rollback 2 Download the desired database again.
Autofetch failure
(2)
3
Alarm type = xDSL (38)
Near end LOS 1 Check the physical line.
Near end LOF 2 Check modem equipment.
Near end LOM 3 Check the physical line (new distributors).
Near end ESE 4 Check the physical communication medium.
Activation failure - configuration error 5 Update the profile parameters.
Ensure that the pilot tones are not marked.
If Glite is used, ensure that the bit rates fit
within the standard.
Alarm
(1)
(3 of 8)
Alcatel 1540 Litespan Giga Ethernet Controller xxi
Activate failure - configuration not
feasible
6 Check configuration data.
Check physical line (length and noise).
Near end - bit rate threshold 7 Lower planned upstream bit rate.
Near end - NCD 8 Check the quality of the line.
Near end - LCD 9 Check the quality of the line
Far end - LOS 10 Check the physical line.
Far end - LOF 11 Check modem equipment.
Far end - LPR 12 There is no repair required because this is the
normal power-down of CPE.
Far end - LOL 13 Check the physical line.
Far end - LOM 14 Check the physical line (new distributors).
Far end - ESE 15 Check the physical line.
Activation failure - communication
problem
16 Check the peer modem type.
Check the physical line.
Activation failure - no peer modem
detected
17 Wait until the modem is connected.
Check the physical line.
Far end - bit rate threshold 18 Lower the planned downstream bit rate.
Far end - NCD 19 Check the quality of the line.
Far end - LCD 20 Check the quality of the line.
Alarm type = xDSLTca (39)
Near end - errored seconds 1 Check the physical line.
Check the modem equipment.
Near end - severely errored seconds 2 Check the physical line.
Near end - unavailable seconds 3 Check the physical line.
Near end - errored seconds in a day 4 Check the physical line.
Near end - severely errored seconds in
a day
5 Check the physical line.
Near end - unavailable seconds in a day 6 Check the physical line.
Far end - errored seconds 7 Check the physical line.
Far end - severely errored seconds 8 Check the physical line.
Far end - unavailable seconds 9 Check the physical line.
Far end - errored seconds in a day 10 Check the physical line.
Alarm
(1)
(4 of 8)
xxii Alcatel 1540 Litespan Giga Ethernet Controller
Far end - severely errored seconds in a
day
11 Check the physical line.
Far end - unavailable seconds in a day 12 Check the physical line.
Alarm type = eoConversion (50)
E/O conversion LOS 1 Check the E/O conversion module.
Check the optic link.
E/O conversion TX fault 2 Check the E/O conversion module.
Alarm type = bonding (54)
Bonding group upstream planned bit
rate threshold
1 Lower group upstream planned bit rate.
Bonding group upstream minimum bit
rate threshold
2 Check physical line.
Check line state.
Bonding group upstream configuration
not feasible
Check physical line.
Bonding group downstream planned bit
rate threshold
4 Lower group downstream planned bit rate.
Bonding group downstream minimum
bit rate threshold
5 Check physical line.
Check line state.
Bonding group downstream
Check physical line.
Alarm type = authentication (55)
VRF assignment failure 1 Check the system configuration.
Check the RADIUS server configuration.
VLAN assignment failure 2 Check the system configuration.
IP address pool assignment failure 3 Check the system configuration.
QoS parameters assignment failure 4 Check the system configuration.
IP address assignment failure 5 Check the system configuration.
Missing attributes 6 Check the system configuration.
Alarm type = IpoX (68)
IP address preemption 1 Check IP address pool on DHCP server.
Check local IP address pool.
Alarm type = SFP (76)
Host SFP LOS 1 Check the physical line.
Host SFP Tx fail 2 Check the host shelf SFP module.
Host SFP missing 3 Check the host shelf SFP presence.
Alarm
(1)
(5 of 8)
Alcatel 1540 Litespan Giga Ethernet Controller xxiii
Host SFP invalid Alcatel ID 4 Check the host shelf SFP module ID.
Host SFP control fail 5 Check the host shelf SFP module or I2C bus.
If control of all host shelf SFPs fails, check the
GENC-E.
ES SFP LOS 11 Check the physical line.
ES SFP Tx fail 12 Check the Expansion Shelf SFP module.
ES SFP missing 13 Check the Expansion Shelf SFP presence.
ES SFP invalid Alcatel ID 14 Check the Expansion Shelf SFP module ID.
ES SFP control fail 15 Check the Expansion Shelf SFP module or
I2C bus.
Alarm type = LLURelay (78)
Wrong applique for LLU 1 Replace the applique by an applique
compatible with the LLU relay.
Alarm type = LANX (51)
LANX fan failure 1 Check the SHub fan module.
LANX power fan failure 2 Check the fan module in the SHub
(redundant) power supply.
LANX database restore 3 Check local flash.
Check remote file system.
Check availability of MIB database.
Emergency reboot 4 Check local flash.
Check remote file system.
Check availability of software package.
LANX SNTP communication lost 5 Check SNTP server.
No ARP reply received for next IP HOP 6 Check existence of configured Nexthop.
Check connection with configured Nexthop.
Alarm type = ethLANX (52)
LANX Ethernet link down 1 Check the Ethernet link.
Ethernet frame discarded
(2)
2
LANX MAC conflict 3 No special repair action required. The conflict
MAC address can be manually prohibited or
permitted if needed.
LANX MAC learning
(2)
4
Alarm type = OSPF (69)
OSPF interface configuration error 1 Check the configuration of the OSPF and
OSPF interface.
Check the configuration on the IP interface.
Check the OSPF hello packets received on
the OSPF interface.
OSPF interface authentication error 2 Check the authentication type and password
configured on the OSPF area and the OSPF
interface.
Check the authentication time range.
Alarm
(1)
(6 of 8)
xxiv Alcatel 1540 Litespan Giga Ethernet Controller
OSPF interface received bad packet 3 Check the connection between the RIP
interface and the cable.
OSPF LSDB approaching overflow 4 Dont input external routes anymore, except
for major external network routes.
Configure the OSPF area as a stub area if
possible.
OSPF LSDB overflow 5 Remove some external routes in the OSPF
domain.
Configure the OSPF area as a stub area if
possible.
Only input major external network routes.
OSPF neighbor state change 6 Check the OSPF neighbor table.
If the neighbor is established correctly,
the situation is normal.
If the neighbor is down unexpectedly,
check the OSPF process status or the
interface-related parameters.
OSPF interface state change 7 No special repair action required. Check and
modify the OSPF interface parameters if
desired to change the OSPF interface status.
Alarm type = RIP (70)
RIP interface configuration error 1 Check the configuration of the RIP send and
receive version.
Check the configuration of the IP interface.
Check the RIP request and update packets
received on the interface.
RIP interface authentication failure 2 Check the authentication type and password
configuration of the RIP interface.
Check the authentication time range.
RIP interface received bad packet 3 Check the connection between the RIP
interface and the cable.
Alarm
(1)
(7 of 8)
Alcatel 1540 Litespan Giga Ethernet Controller xxv
Notes
(1)
The alarm names are listed exactly as they appear in the CLI.
(2)
This alarm is not currently supported in the system.
(3)
See the Duplicate Mac Alarm Status command in the CLI Commands document for more
information.
Alarm type = LANXuplinkgroup (75)
LANX uplink group down 7
Alarm
(1)
(8 of 8)
xxvi Alcatel 1540 Litespan Giga Ethernet Controller

Training (TNG)
TNG 100 Service Installation
TNG 101 QoS Configuration
TNG 102 IGMP and Multicast Configuration
TNG 103 VBAS
TNG 104 DHCP Relay Agent Configuration
TNG 105 Overall Software Packages

General Information
This training document provides information on:
Forwarding Modes
Dynamic MAC Learning and Static Unicast MAC Addresses
MAC Learning Rules
MAC Learning on SHub and LT shelf (LIMs)
MAC Learning and Unicast Configuration
SHub MAC Filters.
Forwarding Modes
The system has the following forwarding modes:
Intelligent bridging VLAN (iBridge VLAN):
In this mode, several User Logical Ports (ULPs) can be associated with a single
VLAN.
The following applies (see Figure 10000-1):
1 VLAN per Litespan
1 IP subnet per Litespan
Complex IP address space management, complexity reinforced by static IP
subnet provisioning
Cross-connect VLAN:
In this mode, only one ULP can be associated with a VLAN. In this VLAN, MAC
learning is disabled.
There are several VLAN cross-connect models supported:
Basic VLAN cross-connect: C-VLAN cross-connect
VLAN stacking for business users: S-VLAN cross-connect
VLAN stacking for residential users: S-VLAN / C-VLAN cross-connect
QoS aware VLAN cross-connect: VLAN + p-bits cross-connect
Layer 2 termination:
In this mode, you can configure the system to use Point-to-Point Protocol over
Ethernet (PPPoE).
PPPoAoE Relay
IPoA/IPoE Forwarding:
In this mode, the NE can be seen as an IP Aware Bridge without being as an IP
next-hop. Users connected to the NE are seen as being directly attached to the edge
router IP interfaces.
1 VLAN for all Litespan
1 IP subnet for all Litespan
One single IP pool : IP addresses distributed at random over the whole access
network
IPoA/IPoE Routing:
In this mode, the NE is seen as an IP next-hop on the IP path towards the users. A
single Virtual Router (VR) can be configured in this mode, which can co-exist in the
same system with a number of VRs that are configured in IP Aware Bridge mode.
1 VLAN for all Litespan
1 IP subnet per Litespan
Complex IP address space management but some automation possible through
routing protocols
Figure 10000-1: Intelligent Briging
Figure 10000-2: IP Routing
Figure 10000-3: IP Forwarding
Deleting a VLAN on the LT shelf is impossible unless all egress ports have been removed
from the VLAN. There is no such restriction for the SHub.
Dynamic MAC Learning and Static Unicast MAC Addresses
The system provides standard Layer 2 MAC learning functionality. MAC address learning
and configuring is done independently on the SHub and LT shelf (LIM), as is MAC aging.
The system also supports static unicast MAC addresses on user logical ports, network
(trunk) ports, cascade (trunk) ports, and user Ethernet ports. MAC learning and
configuring are governed by secure MAC learning rules.
MAC Learning Rules
Different port types have different priorities for learning. The order of priority for learning
(lowest to highest) is:
ASAM/USER/SUBTENDING - NETWORK - CONTROL
This means that learning an address on a control port takes higher priority than any other
port. Similarly, NETWORK ports have a higher precedence than ASAM, USER, and
SUBTENDING ports. ASAM, USER, and SUBTENDING ports have the same priority.
Example:
1 MAC 'X' is learned on ASAM port. If packets with the same MAC address appear later
on the control port, then MAC 'X' is learned on the control port and the same entry is
removed from the ASAM port.
2 MAC 'X' is learned on ASAM port 1. If packets with same MAC address appear on
the USER port, then if MAC movement is enabled for the VLAN, the MAC address is
learned on the USER port. Otherwise, a duplicate alarm is raised and that particular
stream is discarded on the USER port.
A duplicate MAC alarm is raised whenever there is a MAC conflict between same-priority
ports, except when the two ports in question are network ports. This is because MAC
movement is by default enabled on network ports. Also, a duplicate MAC alarm is raised
when a lower-priority port tries to learn a MAC address in case a MAC address has
already been learned on any higher priority port. When the duplicate alarm is raised,
traffic with the same MAC address is blocked on the second port. The alarm is cleared
when the MAC address ages out on the first port.
Duplicate MAC alarms will not be raised when MAC movement is enabled. The MAC
address will always be learned on the port where the packet arrives. If a dynamic MAC
entry already exists on an other port, it is removed before learning the new MAC address
on that port.
MAC Learning on SHub and LT shelf (LIMs)
There are some differences as well as some similarities between MAC learning on the
SHub and MAC learning on a LIM in the LT shelf. Table 10000-1 compares the SHub with
the LT shelf.
Table 10000-1: MAC learning: SHub versus LT shelf
MAC Learning and Unicast Configuration
Static MAC addresses can be configured per VLAN on both the Shub and LIMs. The
egress port for a particular MAC address is specified by these static MAC entries. Unlike
dynamically learned MAC entries, static addresses can be configured to be permanent.
When configuring a static unicast MAC address for a port, the system removes the old
entry if the MAC address has been learned as a dynamic one in any port within the same
VLAN. The system then either accepts or rejects this configuration. It rejects the
configuration if the MAC address has been configured as a static one on another port
within the same VLAN or the port is not in a valid VLAN.
If the number of MAC addresses learned or configured has reached the limit, then one
dynamic entry is removed from the database when configuring a new static entry.
A duplicate MAC alarm is raised when a packet with the same MAC address as a
statically configured one on another port is encountered. The static entry is retained while
the dynamic entry is discarded.
SHub MAC Filters
The system supports global MAC filters. These filters are supported in the SHub. There
are no filters supported per user logical port. The system provides facilities to configure
MAC address filtering based on destination MAC address, source MAC address, or both
source MAC address and destination MAC address. The filter action is either Drop or
Allow on packet match.
SHub LT shelf (LIM)
MAC learning cannot be disabled MAC address learning can be disabled or
enabled on an ASAM LIM. MAC address learning
is disabled on a LIM in CC-VLAN mode.
Maximum number of MAC addresses that can be
learned on SHub is 16384. Once the maximum
limit is reached new addresses are not learned
and the packets are discarded.
Maximum number of MAC addresses that can be
learned on a LIM is 1024.
Secure MAC learning rules are applicable to
different port types
NA
Static MAC address can be configured. There is
a limit of 25 static MAC entries.
Static MAC address can be configured
Default aging time: 300 s Default aging time: 300 s
Aging time range: 10 to 1000000 s Aging time range: 10 to 1096 s
General Description
Rather than just delivering best-effort high-speed Internet services, todays xDSL access
networks are evolving to multi-service access networks that must be capable of
supporting a whole range of services:
conversational services (VoIP, Video telephony)
video services (VoD, Broadcast TV)
transparent LAN services for business customers
data services for business customers
data services for residential customers.
Clearly, these services must be delivered with the appropriate level of Quality of Service
(QoS). In case of xDSL access networks with Ethernet aggregation, there are a number
of network elements, for example, BRAS, IP edge routers, Litespan, or CPE, that must
each give the correct priority treatment to the various application flows.
This is achieved by classifying these application flows at ingress of the network into a
limited set of aggregate flows that are characterized by certain QoS markings. The
different network elements will then provide per QoS class queuing and scheduling for
these aggregate flows. Below, a concise overview is given of the role played by the
Litespan in end-to-end QoS.
Upstream QoS
From a high-level point of view, packets may be subject to the following traffic
engineering steps while traversing the Litespan in the upstream direction. On the
subscriber interfaces at ingress, the following applies:
A number of P-bit marking possibilities exist:
No P-bit marking. This implies that QoS markings received from the end-user are
accepted as they arrive. This possibility is useful in case of trusted end-user
devices (for example, in a business context).
The enforcement of a p-bit marking contract. In this case, QoS markings
received from the end-user are taken into account, but they are subject to a
contract that specifies what p-bit markings are allowed and what QoS markings
need to be re-marked.
Default p-bit markings. In this case all packets on the interface will be remarked
to the configured value.
Ingress policing:
End-users are subject to certain traffic contracts that specify how much traffic they can
send towards the network. To enforce these contracts, policers will be installed. A
policer may apply to an entire subscriber interface or to QoS sub-flows within the
subscriber interface. In this context, a QoS sub-flow (or sub-class) is defined as all the
packets flowing through the interface that are bound by a sub-contract and desire a
specific common treatment. In general, policing can be color-aware (i.e. incoming
color is taken into account) or color-blind. Out-of-profile traffic can be subject to packet
drop, but also to color remarking.
After traffic engineering on the ingress interfaces of the LIMs, packets will be forwarded
in the context of a Virtual bridge, VR or VLAN X-connection. Finally, packets will be
subject to per QoS class queuing and scheduling at the egress interfaces of the LAN-X.
Downstream QoS
In the downstream direction, frames arrive in the Litespan with p-bits that are properly
marked by service-aware edge devices (BRAS, edge-router, application gateway).
No traffic engineering will be done at ingress on the network interfaces.
The idea here is that ingress policing and ACLs at the Service Provider level have already
been applied in a (Access Provider-owned) box deeper in the network. After the
forwarding decision, the following traffic engineering steps can be performed on the
subscriber interfaces at egress:
Egress policing: End-users are subject to certain traffic contracts that specify how
much traffic they can receive on their xDSL connection. To enforce these contracts,
policers will be installed. A policer may apply to an entire subscriber interface or to a
QoS sub-flow (i.e. priority flow) within the subscriber interface.
Classification of traffic into QoS classes based on p-bit markings.
Per QoS class queuing and scheduling: In the downstream direction separate QoS
queues are provided per xDSL line. Buffer acceptance control can be done in a
color-ware fashion (WRED).
QoS Profiles
The NE uses QoS profiles to perform ingress and egress traffic policing, class queuing
and scheduling. You can create QoS profiles which you then assign to xDSL lines to
affect contractual rights and services on those subscriber lines.
Table 10100-1 describes the six types of QoS profiles.
Table 10100-1: QoS Profiles
QoS Profiles Profile Description
CAC profile Use the CAC profile for multicast video admission control of an xDSL interface in
the downstream direction.
Marker profile Use the marker profile to assign a dot-1p bit value within the 802.1x application
to all frames on an xDSL interface.
Policer profile Use a policer profile to enforce committed information rates and committed burst
size limits in 8 kb/s increments up to a maximum of 64 Mb/s. You need two
policer profiles, one for upstream and another for downstream, to associate with
a session profile.
Queue profile Use the queue profile for buffer acceptance control of frames arriving at the
buffer on the LT card from the services side of the network. RED and tail drop
queues types are supported.
Scheduler profile Use the scheduler profile to change the traffic priority of the controlled-load
queue and the BE queue downstream by adjusting the default weight assigned
to the controlled-load queue, which is 66%, in the WFQ.
TNG 102 IGMP and Multicast
Configuration
General Description
IP multicasting is the transmission of an IP datagram to a host group. A host group is a
set of one or more hosts identified by a single destination IP address.
IP hosts report their multicast group memberships to any neighboring multicast routers
using the Internet Group Management Protocol (IGMP). IGMP is an integral part of IP and
must be implemented for all hosts wanting to receive IP multicasts. IGMP messages are
encapsulated in IP datagrams, with an IP protocol of 2.
Figure 10200-1 shows a typical IGMP configuration of a subscriber connected to the
system watching a movie sent from the remote server connected on the network.
Figure 10200-1: Typical IGMP Configuration
IGMP Message Types
There are three types of IGMP messages related to the host-router interaction:
membership query (MQ):
general query, used to learn group members
group-specific query, used to learn if a particular group has any members
version 2 membership report
leave group message
IGMP Parameter Tables
IGMP is managed using a set of parameters arranged in various tables:
IGMP channel table
multicast source table
IGMP module table
IGMP package to multicast source table
IGMP system parameters
IGMP Channel Table
The IGMP channel table consists of multicast capacity parameters as well as statistics
and counters related to IGMP that are multicast per bridge. You can configure the
characteristics of an IGMP channel by specifying a unique index, a VCI, and a VPI for
each channel, as well as the following parameters:
port index:
Ranges from 1/1/3/1 to 1/1/16/48
VCI:
Ranges from 0 to 4095
VPI:
Ranges from 32 to 65535
Multicast source table
This table determines the characteristics of the multicast groups, which should be
multicast in cross-VLAN mode. The table contains a maximum of 1024 multicast source
entries.
IGMP module table
This table determines the distribution of statistic information maintained by the IGMP
proxy.
IGMP Package to Multicast Source Table
The IGMP package to multicast source table is intended primarily for use by a Element
Management System (EMS) (for example, the 5526 AMS). It allows the EMS to support
multiple sets of packages in different regions.
A package is a group of one or more multicast sources that share a common access
permission. By grouping the source channels in one or more packages, a service
provider is able to support and deliver services at various levels to the end users.
The IGMP package to multicast source table shows the following parameters for a
package:
The multicast group address
The multicast group source address
IGMP System Parameters
These parameters are used to maintain active memberships of connected multicast
channels and to process IGMP join, leave, and query messages.
It is highly recommended that all default values be left as is. However, should there be a
need to change the IGMP parameters, make sure to set all dependencies first. Failing to
do this may lead to rejection of a set, since some of the valid ranges are dependent on
other objects.
IGMP Snooping Configuration on the SHub
You can configure IGMP Snooping, Virtual LAN router port related parameters and the
Virtual LAN filter for the IGMP Snooping for a particular VLAN.
Viewing the IGMP Related Parameters
Table 10200-1 describes the commands available that allow you to view the IGMP
related parameters.
Table 10200-1: Parameter display commands
Multicast Configuration Guidelines
When configuring multicast, the sequence of configuration actions is very important.
When you are adding a multicast stream to the multicast source table, you need to
configure the VLAN ID on which this stream can be received.
You need to create and configure this VLAN ID prior to creating the multicast source table
entry. Failing to do this may cause difficulty in joining the multicast group.
Command Description
show igmp system Show all the IGMP system-related parameters
show igmp channel counter (port) Show the IGMP channel counter details
show igmp channel miscellaneous (port) Show the IGMP channel source details
show igmp package-to-src (package-id) Show the IGMP package to multicast source
parameters.
show igmp module-mcast-src (slot)
mcast-addr <MulticastAddress>
Show the distribution of statistic information
maintained by IGMP channels.
show igmp module counter (slot-index) Show the IGMP Module counters
show igmp module time (slot-index) Show the time-related parameters of the IGMP
module.
show igmp module miscellaneous (slot-index) Show miscellaneous parameters of the IGMP
module
show igmp shub vlan-router-port (vlan-id)
Show the status of the IGMP VLAN router ports.
TNG 103 VBAS
TNG 103 VBAS
General Description
The Virtual Broadband Access Server (VBAS) protocol is used between the Broadband
Access Server (BAS) and the system to get detailed information on the subscribers
physical address. The VBAS protocol has two phases. After completing these phases,
the BAS can get the physical address of any new subscriber. The two phases are:
VBAS Query
VBAS sends a VBAS Query Packet to the system to gather physical-port information
corresponding to the MAC address of the new subscriber.
VBAS Response
Upon receiving the request packet, the system sends a VBAS Response Packet to
the BAS. This packet includes the physical-port information of the new subscriber.
All VBAS packets carry a destination. If the packet is not destined for a specific system,
it will forward the packet to all subtending systems until it has reached its intended
destination.
In normal operation, the network port towards the BAS is tagged. This means that the
network port is able to process and respond to tagged VBAS frames.
If untagged packets are to be handled, then the network port is explicitly set as untagged.
Also a PVID is configured for the port. When the system receives a VBAS query, user
information is retrieved from the VLAN configured as PVID.
VBAS Configuration
No specific VBAS configuration as such is necessary on this system. However, as an
Operator, you need to make sure that the network port is configured in order to properly
communicate with the BAS.
There are two modes in which the network port can operate: tagged or untagged.
VBAS Configuration in Tagged Mode
If the network port is set up as a tagged port, it should be a part of all related VLANs. The
port will handle all tagged VBAS packets.
VBAS Configuration in Untagged Mode
If untagged VBAS frames are to be handled by the system, the network port must be
untagged and a PVID must be configured.
Example
A user with MAC address 00-B0-D0-BC-D5-D3 is connected to slot 7, port 23 on LIM1.
LIM1 is connected to ASAM port 1. The VLAN configured for the user is VLAN 100 on
both LIM and SHub.
TNG 103 VBAS
When the VBAS request arrives from the server on the SHub, the MAC address of the
user is retrieved in VLAN 100. Since the user MAC address is learned in VLAN 100, the
request is forwarded to LIM1.
LIM1 replies with VBAS response containing user information such as the slot and port
number. The SHub forwards the VBAS response to the server.
The process is shown in Figure 10300-1.
Figure 10300-1: VBAS Example
TNG 104 DHCP Relay Agent
Configuration
General Description
The Dynamic Host Configuration Protocol (DHCP) provides a framework for passing
configuration information to hosts on a TCP/IP network. DHCP is based on the Bootstrap
Protocol (BOOTP), adding the capability of automatic allocation of reusable network
addresses and additional configuration options. DHCP consists of two components: a
protocol for delivering host-specific configuration parameters from a DHCP server to a
host and a mechanism for allocation of network addresses to hosts. DHCP is built on a
client-server model, where designated DHCP server hosts allocate network addresses
and deliver configuration parameters to dynamically configured hosts.
Figure 10400-1 shows a typical DHCP configuration.
Figure 10400-1: Typical DHCP Configuration
IP Address Allocation Mechanisms
DHCP supports three mechanisms for IP address allocation:
automatic allocation
DHCP assigns a permanent IP address to a client.
dynamic allocation
DHCP assigns an IP address to a client for a limited period of time (or until the client
explicitly relinquishes the address).
manual allocation
A client's IP address is assigned by the network administrator, and DHCP is used
simply to convey the assigned address to the client.
A particular network will use one or more of these mechanisms, depending on the policies
of the network administrator.
DHCP Option 82
An option called Option 82 is inserted by the DHCP relay agent running on the system
when forwarding client-originated DHCP packets to a DHCP server. Servers recognizing
Option 82 may use the information to implement an IP address or other parameter
assignment policies. The DHCP server echoes the option back to the relay agent in
server-to-client replies. The system strips the option before forwarding the reply to the
client. Option 82 is organized as a single DHCP option that contains one or more
suboptions that convey information known by the relay agent.
DHCP Relay Parameters
Table 10400-1 describes the parameters used to configure DCHP.
Table 10400-1: DHCP parameter descriptions
Conditions and Restrictions
Note the following conditions and restrictions.
Before you can enable the DHCP relay agent, you need to configure the DHCP
servers on a VRF IP interface.
The DHCP relay agent can only be configured on one VRF IP interface.
A maximum of four DHCP servers can be configured on a VRF.
The DHCP servers configured on a VRF IP interface must be part of the set of DHCP
servers configured on the VRF.
Viewing the DHCP Configuration
There are several commands available that allow you to view the DHCP configuration.
Table 10400-2 describes each command.
Parameter Description
Relaying When enabled, the relay agent is active
Server When enabled, the relay agent forwards the packets to a specific
DHCP server
Server IP Address of the DHCP server to which the packets are to be
forwarded
secs-threshold/hops-threshold Thresholds for Option 82
Table 10400-2: Configuration display commands
See the CLI Commands and Messages document for more information on these
commands.
Command Description
show dhcp-relay Show the DHCP relay parameters
show dhcp-relay option Shows various parameters related to the number of
DHCP packets
show dhcp-relay if-conf (if-main-index) Shows the DHCP relay interface configuration
show dhcp-relay server (server-ip-addr)
server-vrf-id <SignedInteger>
Shows the DHCP relay server configuration
show dhcp-relay if-server (index) ip-addr
<Ip::V4Address>
Displays the DHCP relay server table
Introduction
This training document gives more information about:
Downloading a new OSWP.
Aborting an OSWP.
Activating a non-active OSWP.
Committing an OSWP.
Download a New OSWP
The following prerequisites must be fulfilled before a new OSWP can be downloaded:
The system must have only one Enabled/Active/Committed OSWP.
The management channel between the system and the manager has been
established.
The system is not involved in another OSWP download process.
The manager requests the system to download a new OSWP. He specifies:
The pathname of the overall descriptor files
The TFTP-servers where the overall descriptor files can be found.
The set of overall descriptor files he wants to have available on the system before
activating the new OSWP.
The system downloads the overall descriptor files and stores it persistently.
The system downloads the software files that are specified in the downloaded overall
descriptor files on condition that sufficient resources are available for their persistent
storage.
The manager has the possibility to monitor the progress of the download process with
granularity.
The download of the process can be implicitly or explicitly interrupted:
The implicit interruption can occur due to the following:
the unavailability of sufficient resources to store SWP files.
the system is not able to download or interpret the overall descriptor file.
the system is not able to download a selected SWP descriptor file.
The explicit interruption can occur when the manager requests the system to abort the
ongoing download process.
In case there are no exceptions, finally the system will have two OSWPs:
the Enabled/Active/Committed OSWP.
the new downloaded OSWP. The status of the new OSWP is
Enabled/NotActive/UnCommitted.
Abort an OSWP
The manager can abort an OSWP when the system has 2 OSWPs. The status of the first
OSWP is Enabled/Active/Committed while the second one will be in one of the following
three states:
Enabled/NotActive/UnCommitted
Downloading/NotActive/UnCommitted
Disabled/NotActive/UnCommitted.
The management channel between the system and the manager is established and the
system is not involved in any other SW download process.
The manager requests the system to remove the NotActive/UnCommitted OSWP. The
system removes all the persistent stored files and databases not related to the the
Enabled/Active/Committed OSWP. The status of the OSWP to be removed will be
Aborting/NotActive/UnCommitted during the complete remove operation.
After the abort is successful the system will have only one OSWP. The status of this
OSWP will be Enabled/Active/Committed. Only files and databases related to this OSWP
are stored persistently in the system.
Activate a Non-active OSWP
To activate a not-active OSWP, the system must have two OSWPs:
The first OSWP has the status Enabled/Active, while the second OSWP has the status
Enabled/NotActive.
The management channel between the system and the manager is established and the
system is not involved in another SW download process.
The manager requests the system to activate the Enabled/NotActive OSWP:
1 The system selects the database that is compatible with and linked to the
Enabled/NotActive OSWP among the available databases.
2 The system starts the activation procedure of the NotActive OSWP.
3 When the activation of the NotActive OSWP is successful, the system has two
OSWPs.
The previously NotActive OSWP is now active together with the selected compatible
database. The previously Active OSWP is still available but its status is now
Enabled/NotActive.
Commit an OSWP
To commit an OSWP, the system has two OSWPs. The first OSWP has the status
Enabled/Active/Uncommitted, while the status of the second OSWP is
Enabled/NotActive/Committed.
The manager requests the system to commit the active OSWP:
1 The system removes all the persistent stored files and databases that do not belong
to the Enabled/Active OSWP.
Note: The status of the OSWP to be committed will be Enabled/Active/Committing
during the entire commit operation.
2 After commit is successful, the system will have only one OSWP. The status of this
OSWP is Enabled/Active/Committed. Only files related to this OSWP are stored
persistently in the system.
Index
Index
Numbers
802.1x
configuring, DLP145-1
disabling, DLP145-1
802.1x parameters
A
alarm delta logs
alarm entries
configuring, DLP110-3, DLP110-3
alarm snapshot table
viewing, DLP155-1
alarm table entries
alarms
creating snapshots, DLP154-1
fault isolation, TAP104-1
managing, DLP110-1
monitoring, DLP155-1
troubleshooting, TAP104-1
viewing snapshots, DLP154-1
applique
ARP table entry
C
CC-VLAN, TNG100-2
channel source
CLI session
setting up, DLP100-1
current alarm table
viewing, DLP155-1
D
D
DHCP, TNG104-2
DHCP relay agent
conditions, TNG104-3
configuring, DLP139-2, DLP140-2, DLP141-1
general description, TNG104-1
parameters, TNG104-2
restrictions, TNG104-3
viewing, TNG104-3
E
EDSE-A
expansion links, TNG106-3
equipment
configuring and modifying, NTP103-2, NTP117-1
planning, DLP111-1
repairing, NTP114-1, NTP115-1, NTP116-1, NTP118-1, TAP101-1, TAP102-1
replanning, DLP111-1
restarting, DLP153-1
shutting down, DLP153-1
unplanning, DLP111-1
ES
CLI commands, TNG106-1
expansion link connections, TNG106-3
identifying, TNG106-1
MAC address, TNG106-1, TNG106-3
events
fault isolation, TAP104-1
troubleshooting, TAP104-1
expansion links
EDSE-A, TNG106-3
GENC-E, TNG106-3
F
fault isolation
alarms, TAP104-1
events, TAP104-1
forwarding modes
CC-VLAN, TNG100-2
layer 2 termination, TNG100-2
RB-VLAN, TNG100-2
G
GENC-E
E password
I
expansion links, TNG106-3
I
IGMP
parameters, TNG102-2
viewing configuration, TNG102-4
IGS system parameters
IP address allocation, TNG104-2
IP multicast
configuration guidelines, TNG102-4
IP paramters
configuring, DLP121-1, DLP122-1, DLP123-1, DLP124-1, DLP125-1,
DLP126-1, DLP127-1, DLP128-1, DLP171-1, DLP174-1
IP route parameters
L
layer 2 termination, TNG100-2
link aggregation
LT shelf
backing up, DLP157-1, RTP100-2
M
MAC address, TNG106-3
MAC learning, TNG100-5
multicast
multicast source statistics
N
network interfaces
P
package bitmaps
password
rules, DLP101-1
plug-in unit
locking, DLP112-1
unlocking, DLP112-1
plug-in unit system time
Q
plug-in units
configuring, NTP103-1
PPPoE interface
PPPoE profile
PPPoE relay
disabling, DLP146-1, DLP147-1
enabling, DLP146-1, DLP147-1
PPPoE server
PPPoE termination
Q
QoS
R
rack
RADIUS
RB-VLAN, TNG100-2
remote inventory
retrieving information, RTP102-1
response timer
configuring, DLP132-3, DLP136-2, DLP137-2, DLP150-1
RSTP
S
SEM
CLI commands, TNG106-1
expansion link connections, TNG106-3
identifying, TNG106-1
MAC address, TNG106-1, TNG106-3
planning, TNG106-3
services
configuring, NTP101-1, NTP104-2, NTP105-1, NTP106-1, NTP107-1,
NTP108-1, NTP109-1, NTP110-1, NTP111-1, NTP112-1, NTP113-1,
NTP119-1, NTP120-1, NTP121-2, NTP122-2, NTP123-1, NTP125-1
shelf
SHub
restarting, DLP151-1
T xDSL profile
T
restoring, RTP101-1
RSTP management, DLP106-1, DLP107-1, DLP108-1
shutting down, DLP151-1
VLAN filter, DLP103-2
SHub default gateway
SHub MAC filters, TNG100-6
SNMP
viewing, DLP102-3, DLP162-2
SNMP community parameters
SNTP
LT shelf, DLP102-3, DLP162-2
SHub, DLP102-3, DLP103-2, DLP162-2
subrack
system
configuring, NTP102-2
forwarding modes, TNG100-2
maintaining, NTP124-1
reboot modes, DLP152-1
rebooting, DLP152-1
system description
system parameters
configuring, DLP102-1, DLP137-1, DLP162-1, DLP175-1
system time
viewing, DLP102-3, DLP162-2
T
trap
reporting modes, DLP109-1
trap table
resetting, DLP109-4
troubleshooting
alarms, TAP104-1
events, TAP104-1
U
unicast configuration, TNG100-5
user
creating and configuring, DLP101-2, DLP172-1
V
V
verifying configuration, DLP113-1
VLAN
creating, DLP115-3, DLP116-3, DLP118-1, DLP119-1, DLP120-1, DLP142-1,
DLP143-1, DLP167-1, DLP168-1, DLP176-1
deleting, DLP119-2
VLAN filter
VRF
DLP127-2, DLP128-1, DLP171-1, DLP174-1
X
xDSL profile
DLP169-2, DLP170-2, DLP173-1
types, DLP129-1

Customer documentation and product support
Technical support
Customer documentation
Product manuals and documentation updates are available through the Alcatel Support
Documentation and Software Download service at Alcatel.com. If you are a new user and
require access to this service, please contact your Alcatel sales representative.
Customer documentation feedback
http:/ / www.alcatel.com/ support/
http:/ / www.alcatel.com/ osds/
documentation.feedback@alcatel.com


Sad-Gebc Cli Operations View Z Aiwu

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Sad-Gebc Cli Operations View Z Aiwu

Enviado por

Direitos autorais:

Formatos disponíveis

Alcatel 1540 Litespan Giga Ethernet Controller i

Edition 01 Proposal 3EC-41868-0001-TQZZA Operations and Maintenance Using CLI

Você também pode gostar