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 2007 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.
PRINTED ON
RECYCLED PAPER
Preface
This preface provides general information about the documentation set for the
7302 Intelligent Services Access Manager (7302 ISAM) and the 7330 Intelligent
Services Access Manager Fiber to the Node (7330 ISAM FTTN).
Scope
This documentation set provides information about safety, features and
functionality, ordering, hardware installation and maintenance, CLI and TL1
commands, and software upgrade and migration procedures.
Audience
This documentation set is intended for planners, administrators, operators, and
maintenance personnel involved in installing, upgrading, or maintaining the
7302 ISAM or the 7330 ISAM FTTN.
Prerequisite knowledge
The reader must be familiar with general telecommunications principles.
Safety information
For safety information, see the 7302 ISAM Safety Manual. For ANSI safety
information, see the Mandatory Regulations chapter in the 7330 ISAM FTTN ANSI
documentation.
iii
Edition 02 Released
Preface
Documents
Table 1 lists the documents that make up the 7302 ISAM Release 3.2 documentation
set.
Table 1 7302 ISAM documentation set
Title
Description
Part number
Product Information
3HH-04069-AAAA-TCZZA
System Description
3HH-04064-AAAA-TQZZA
Safety Manual
3HH-04071-AAAA-TCZZA
3HH-04065-AAAA-TQZZA
3HH-04072-AAAA-TQZZA
XD Modular Hardware
Installation Guide
3FE-21578-AAAA-RJZZA
FD Hardware Installation
Guide
3FE-03591-AAAA-RJZZA
3FE-21575-AAAA-RJZZA
CLI Commands
Describes the CLI commands for the 7302 ISAM and the
7330 ISAM FTTN
3HH-04067-AAAA-TCZZA
3HH-04068-AAAA-TCZZA
3HH-03390-AAAA-RJZZA
General documentation
Hardware documentation
Software documentation
Software Management User
Guide
Special information
The following are examples of how special information is presented in this
document.
Danger Danger indicates that the described activity or situation
Preface
interest.
This step offers two options. You must choose one of the following:
a
v
Edition 02 Released
Preface
This step has a series of substeps that you must perform to complete the step. You
must perform the following substeps:
i
ii
iii
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.
vi
Edition 02 Released
Contents
Preface
iii
Scope
.............................................................................................................................. iii
Audience .............................................................................................................................. iii
Prerequisite knowledge ......................................................................................................... iii
Safety information.................................................................................................................. iii
Documents ............................................................................................................................ iv
Special information ................................................................................................................ iv
Introduction
1.1
1.2
1.3
1-1
IXL 100-1
vii
Edition 02 Released
Contents
NTP 100-1
NTP 101-1
NTP 102-1
NTP 103-1
NTP 104-1
NTP 105-1
NTP 106-1
NTP 107-1
NTP 108-1
NTP 109-1
NTP 110-1
NTP 111-1
NTP 112-1
NTP 113-1
NTP 114-1
NTP 115-1
viii
Edition 02 Released
Contents
NTP 116-1
NTP 117-1
NTP 118-1
NTP 119-1
NTP 120-1
NTP 121-1
NTP 122-1
NTP 123-1
NTP 124-1
NTP 125-1
NTP 126-1
NTP 127-1
NTP 128-1
DLP 100-1
DLP 101-1
ix
Edition 02 Released
Contents
DLP 102-1
DLP 103-1
DLP 104-1
DLP 105-1
DLP 106-1
DLP 107-1
DLP 108-1
DLP 109-1
DLP 110-1
DLP 111-1
DLP 112-1
DLP 113-1
DLP 114-1
DLP 115-1
DLP 116-1
DLP 117-1
DLP 118-1
DLP 119-1
x
Edition 02 Released
Contents
DLP 120-1
DLP 121-1
DLP 122-1
DLP 123-1
DLP 124-1
DLP 125-1
DLP 126-1
DLP 127-1
DLP 128-1
DLP 129-1
DLP 130-1
DLP 131-1
DLP 132-1
DLP 133-1
DLP 134-1
DLP 135-1
DLP 136-1
DLP 137-1
xi
Edition 02 Released
Contents
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 142-1
DLP 143-1
DLP 144-1
DLP 145-1
DLP 146-1
DLP 147-1
DLP 148-1
DLP 149-1
DLP 150-1
DLP 151-1
DLP 152-1
DLP 153-1
DLP 154-1
xii
Edition 02 Released
Contents
DLP 155-1
DLP 156-1
DLP 157-1
DLP 158-1
DLP 159-1
DLP 160-1
DLP 161-1
DLP 162-1
DLP 163-1
DLP 164-1
DLP 165-1
DLP 166-1
DLP 167-1
DLP 169-1
DLP 170-1
DLP 171-1
xiii
Edition 02 Released
Contents
DLP 172-1
DLP 173-1
DLP 174-1
DLP 175-1
DLP 176-1
DLP 177-1
DLP 178-1
DLP 179-1
DLP 180-1
DLP 182-1
DLP 183-1
DLP 184-1
DLP 185-1
DLP 187-1
DLP 188-1
xiv
Edition 02 Released
Contents
DLP 189-1
DLP 190-1
DLP 191-1
DLP 192-1
DLP 193-1
DLP 195-1
DLP 196-1
DLP 197 View port configuration and operational data DLP 197-1
DLP 198 Configure multicast on the SHub
DLP 198-1
DLP 199-1
RTP 100-1
RTP 101-1
RTP 102-1
xv
Edition 02 Released
Contents
TAP 100-1
TAP 101-1
TAP 102-1
TAP 103-1
TAP 104-1
Training (TNG)
TNG 100 Service installation
TNG 100-1
TNG 101-1
TNG 102-1
TNG 103-1
TNG 104-1
TNG 105-1
TNG 107-1
TNG 108-1
xvi
Edition 02 Released
Contents
TNG 109-1
TNG 110-1
TNG 111-1
TNG 113-1
TNG 114-1
Glossary
Index
xvii
Edition 02 Released
Contents
xviii
Edition 02 Released
1 Introduction
1.1 Introduction
1-2
1-2
1-5
1-1
Edition 02 Released
1 Introduction
1.1
Introduction
This document provides instructions on CLI operation and maintenance tasks and
procedures for the Alcatel 7302 ISAM and the 7330 ISAM FTTN.
These tasks and procedures are identical for the 7302 ISAM and the
7330 ISAM FTTN, unless specified otherwise.
Throughout the document, the 7302 ISAM and the 7330 ISAM FTTN will be
referred to as the Network Element (NE).
See the CLI Commands document for more detailed information about the CLI
command syntax.
1.2
TOP layers
The TOP documentation method uses the following layers:
Figure 1-1 shows the layers and logical path of the TOP documentation method.
1-2
Edition 02 Released
1 Introduction
Non-Trouble
Clearing Procedure
(NTP)
User Training
Package
(TNG)
Trouble Analysis
Procedure
(TAP)
Routine Task
Procedure
(RTP)
Detailed Level Procedure
(DLP) or Chart
Trouble Analysis
Data
(TAD)
All layers do not apply to all documents. This document contains only contains the
layers needed to complete operation and maintenance tasks and procedures specific
to the NE through the EMS.
Index List (IXL)
The IXL lists each task and procedure (for example, Log on to the 5526 AMS), along
with related supporting information and the identification number of the
corresponding document (for example, DLP 500). This lets users know where to find
the appropriate documentation.
Non-Trouble Procedure (NTP)
NTPs are procedures that describe how to perform a task (what to do), such as how
to accept a system after it has been installed, turn up a system for service, or maintain
a system according to a maintenance plan. NTPs are made up of steps that refer to
detailed procedures (DLPs) or to supporting information (provided in TNGs). This
allows inexperienced users (or experienced users who want more information) to go
to the DLP or TNG for the additional information they need to complete the task. If
user go to the referenced DLP or TNG, they must return to the NTP to continue the
task.
NTPs are typically referenced from the IXL.
Detailed Level Procedure (DLP)
1-3
Edition 02 Released
1 Introduction
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)
1-4
Edition 02 Released
1 Introduction
1.3
Configuration examples
Configuration examples are provided in the DLPs.
TNG 114 gives a summary of the configuration used in these examples.
1-5
Edition 02 Released
1 Introduction
1-6
Edition 02 Released
Edition 02 Released
Edition 02 Released
NTP number
NTP 113
NTP 110
NTP 125
NTP 111
NTP 112
NTP 100
Cluster management
NTP 122
NTP 104
NTP 105
NTP 109
NTP 106
Configure an IP router
NTP 107
NTP 121
Equipment configuration
NTP 103
Equipment repair
NTP 114
NTP 128
NTP 124
Monitor alarms
NTP 115
NTP 118
Script files
NTP 101
Secure shell
NTP 123
(1 of 2)
IXL 100-1
Edition 02 Released
Title
NTP number
Service adaptation
NTP 119
Service installation
NTP 108
SHDSL configuration
NTP 127
Software management
NTP 116
NTP 102
NTP 126
NTP 117
Troubleshooting commands
NTP 120
(2 of 2)
DLP number
DLP 128
DLP 121
Configure 802.1x
DLP 145
DLP 135
DLP 150
DLP 169
DLP 166
DLP 188
DLP 186
DLP 141
DLP 139
DLP 140
DLP 102
DLP 132
DLP 195
DLP 187
DLP 137
DLP 138
DLP 183
DLP 192
DLP 194
DLP 105
DLP 143
DLP 136
(1 of 4)
IXL 100-2
Edition 02 Released
Title
DLP number
DLP 198
DLP 185
DLP 104
DLP 181
Configure OSPF
DLP 107
DLP 149
DLP 146
DLP 147
DLP 133
DLP 134
DLP 199
Configure RADIUS
DLP 144
Configure RIP
DLP 108
Configure RSTP
DLP 106
DLP 177
DLP 182
DLP 175
DLP 109
Configure SSH
DLP 170
DLP 180
DLP 179
DLP 103
DLP 178
DLP 113
DLP 142
DLP 190
DLP 189
DLP 196
DLP 130
DLP 184
Create a C-VLAN
DLP 117
DLP 172
DLP 122
DLP 115
DLP 116
DLP 127
DLP 123
(2 of 4)
IXL 100-3
Edition 02 Released
Title
DLP number
DLP 154
DLP 120
DLP 174
DLP 125
DLP 126
Create an SC-VLAN
DLP 119
Create an S-VLAN
DLP 118
DLP 131
DLP 124
DLP 101
DLP 129
EMS management
DLP 171
DLP 191
DLP 193
DLP 148
DLP 112
Manage alarms
DLP 110
DLP 157
Management of OSWP
DLP 159
DLP 156
DLP 158
DLP 162
DLP 168
DLP 163
Monitor alarms
DLP 155
NT redundancy
DLP 114
DLP 176
Ping command
DLP 164
DLP 111
DLP 152
Script files
DLP 167
DLP 100
DLP 153
DLP 151
DLP 161
DLP 173
Traceroute command
DLP 165
(3 of 4)
IXL 100-4
Edition 02 Released
Title
DLP number
DLP 197
DLP 160
(4 of 4)
RTP number
RTP 100
RTP 101
RTP 102
TAP number
Equipment repair
TAP 102
F5 loopback test
TAP 101
TAP 104
TAP 100
TAP 103
TNG number
TNG 112
TNG 111
Configuration examples
TNG 110
TNG 104
TNG 114
TNG 102
Multi-ADSL parameters
TNG 113
TNG 105
TNG 109
QoS configuration
TNG 101
Service installation
TNG 100
SHDSL parameters
TNG 108
Specifying 7330 ISAM FTTN remote expansion units using the CLI
TNG 106
(1 of 2)
IXL 100-5
Edition 02 Released
Title
TNG number
VBAS
TNG 103
VDSLx parameters
TNG 107
(2 of 2)
IXL 100-6
Edition 02 Released
Edition 02 Released
Edition 02 Released
-3
Edition 02 Released
-4
Edition 02 Released
General
Figure NTP 100-1 shows the management topology of the NE system.
Figure NTP 100-1: Management Topology
EMS
(e.g. AWS 5523)
SNMP
UDP161/
162
CLI
Terminal
TL1
Terminal
Telnet
TCP1023
SSH
TCP1022
Telnet
TCP23
SSH
TCP22
TL1
Craft Terminal
TL1
TL1 Gateway
TL1
UDP13001
CLI
Craft Terminal
RS232
RS232
ISAM
TL1
agent
CLI
agent
SNMP
agent
IACM
subsystem
SNMP
agent
MIB SHub
SHub
subsystem
Active DB
NTP 100-1
Edition 02 Released
Description
EMS
TL1 CT
CLI CT
See the CLI Commands and Messages document for detailed information about the CLI
command syntax.
The use of TL1 commands is still supported.
Procedure
Proceed as follows to set up the CLI session and configure the CLI users:
1
NTP 100-2
Edition 02 Released
Procedure
In order to use script files, you need to perform the following tasks:
1
NTP 101-1
Edition 02 Released
NTP 101-2
Edition 02 Released
Prerequisite
A CLI session must have been set up; see DLP 100.
Security Considerations
Note The following must be taken into account with regard to system
security:
NTP 102-1
Edition 02 Released
Procedure
Proceed as follows to configure the system:
1
see DLP 175 for configuring the system in single IP address mode
see DLP 102 for configuring the system in dual IP address mode
Note To convert the system IP address mode, that is from dual mode
to single mode or from single mode to dual mode; see DLP 184.
Configure the SHub database save location and the restore source file; see
DLP 157.
NTP 102-2
Edition 02 Released
General
The NE consists of a single shelf with plug-in units. You can perform the actions
described in Table NTP 103-1 to configure the equipment.
Table NTP 103-1: Configure plug-in units
Action
Description
Planning equipment
Unplanning equipment
(1 of 2)
NTP 103-1
Edition 02 Released
Action
Description
Replanning equipment
When necessary, you can lock any equipment, most often a unit, to put it out
of service. Locking a unit renders it inactive. No traffic is generated or
received by the units. However, the unit is not removed from the
configuration, and as soon as you unlock the unit, it becomes active again.
It goes back to operational mode without restart or initialization, and traffic
can resume immediately.
Similarly, you can power down the unit and restart it at a later time. In this
case, however, the unit will go through a complete startup cycle before
traffic is possible.
(2 of 2)
Procedure
Proceed as follows to configure or modify the system equipment:
1
NTP 103-2
Edition 02 Released
NTP 104-1
Edition 02 Released
VLAN X
VLAN Y
VLAN A
VLAN B
NE
PC
Network
Procedure
The procedures for creating a cross-connect VLAN are described in the following DLPs:
1
NTP 104-2
Edition 02 Released
VLAN X
NE
Video VLAN
Internet
Video
NTP 105-1
Edition 02 Released
NE
PC
Network
Procedure
Proceed as follows to configure an iBridge VLAN:
1
Add the network interface to the iBridge VLAN; see DLP 121.
NTP 105-2
Edition 02 Released
NE
Video VLAN
Internet
Video
Video VLAN is
always in iBridge
NTP 106-1
Edition 02 Released
NE
PC
Network
Procedure
Proceed as follows to configure an IP-aware bridge:
1
Add the network interfaces to the L2 terminated forwarder VLANs; see DLP 121.
NTP 106-2
Edition 02 Released
NTP 107-1
Edition 02 Released
NE
Video VLAN
Internet
Video
VLAN Y
Virtual VLAN
Video VLAN is
always in iBridge
NE
PC
Network
Procedure
Proceed as follows to configure an IP router:
1
NTP 107-2
Edition 02 Released
xDSL profiles
Quality of Service (QoS)
Internet Group Management Protocol (IGMP) and multicast
Dynamic Host Configuration Protocol (DHCP) relay agent and Option 82
Authentication
Point-to-Point Protocol (PPP) configuration
NT redundancy
Link aggregation
Rapid Spanning Tree Protocol (RSTP)
Routing protocols (optional)
Voice Session Initiation Protocol (SIP)
Network Access Control Protocol (NACP) session
Procedure
To configure a service, you need to perform the following tasks:
1
For the configuration of the service profiles and the spectrum profiles; see DLP
129.
ii
iii
For the configuration of virtual noise values for VDSL2; see DLP 189.
Configure general bridge parameters for LT and SHub; see DLP 195.
NTP 108-1
Edition 02 Released
Configure QoS:
i
ii
iii
iv
ii
iii
For the configuration of IGMP proxy on the LT; see DLP 137.
iv
For the configuration of IGMP snooping on the SHub; see DLP 138.
For the configuration of the DHCP relay agent in iBridge mode; see DLP 139.
ii
For the configuration of the DHCP relay agent in router mode; see DLP 140.
iii
For the configuration of the DHCP relay agent in forwarder mode; see
DLP 141.
iv
ii
iii
iv
For the configuration of operator authentication via RADIUS; see DLP 181.
vi
For the configuration of the default security domain; see DLP 178.
ii
NTP 108-2
Edition 02 Released
10
11
12
If necessary, configure routing protocols such as OSPF and RIP. the configuration
is optional (depends if the network elements which are connected to the ISAM, are
using those protocols). The routing protocols are handled in the Shub.
i
For the configuration of Open Shortest Path First (OSPF) management; see
DLP 107.
ii
13
14
15
NTP 108-3
Edition 02 Released
NTP 108-4
Edition 02 Released
Procedure
To configure PPPoE termination, you need to perform the following tasks:
1
NTP 109-1
Edition 02 Released
NTP 109-2
Edition 02 Released
Prerequisites
The following prerequisites must be fulfilled before an iBridge user can be created:
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.
NTP 110-1
Edition 02 Released
NTP 110-2
Edition 02 Released
Prerequisites
The following prerequisites must be fulfilled before an IPoA user can be 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.
NTP 111-1
Edition 02 Released
Add the LT to the VLAN, for the first user to be created on the LT for that VLAN; see
DLP 128.
NTP 111-2
Edition 02 Released
Prerequisites
The following prerequisites must be fulfilled before an IPoE user can be created:
Procedure
Proceed as follows to add an IPoE user:
1
If the first IPoE user to be created on a VLAN needs DHCP, configure the VRF for
DHCP; see DLP 140.
Add the LT to the correct VLAN (service), for the first user to be created on the LT
for that VLAN; see DLP 128.
NTP 112-1
Edition 02 Released
NTP 112-2
Edition 02 Released
Prerequisites
The following prerequisites must be fulfilled before an PPPoE user can be created:
Procedure
Proceed as follows to add a PPPoE user:
1
Add the LT to the correct VLAN (service), for the first user to be created on the LT
for that VLAN; see DLP 128.
NTP 113-1
Edition 02 Released
NTP 113-2
Edition 02 Released
Procedure
Proceed as follows to perform equipment repair tasks:
1
Plan, unplan, and replan equipment (for example, plug-in units); see DLP 111.
Pull out and plug in equipment. For the procedures, refer to the XD Modular
Hardware Installation Manual for the 7302 ISAM or the Hardware Installation and
Maintenance Practices for the 7330 ISAM FTTN.
Lock and unlock equipment (mostly plug-in units); see DLP 112.
NTP 114-1
Edition 02 Released
NTP 114-2
Edition 02 Released
Procedure
Proceed as follows to monitor the alarms:
1
NTP 115-1
Edition 02 Released
NTP 115-2
Edition 02 Released
Procedure
The following steps can be used to perform software management:
1
NTP 116-1
Edition 02 Released
NTP 116-2
Edition 02 Released
Procedure
The steps below show the procedures for modifying different system parameters:
1
NTP 117-1
Edition 02 Released
NTP 117-2
Edition 02 Released
Procedure
The following tasks can be performed:
1
Viewing the configuration and operational data of a port: see DLP 197
NTP 118-1
Edition 02 Released
NTP 118-2
Edition 02 Released
Procedure
To adapt a service, you can perform the following tasks:
1
NTP 119-1
Edition 02 Released
NTP 119-2
Edition 02 Released
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
NTP 120-1
Edition 02 Released
NTP 120-2
Edition 02 Released
CPE-MM
RMI
LMI
NE
xDSL CPE
NTP 121-1
Edition 02 Released
The CPE-MM is responsible for the management of CPE. The following interfaces are
defined:
Note This NTP is for CPE management using SNMP. For IPProxy
CPE management; see NTP 128.
Procedure
To configure SNMP proxy CPE management, you need to perform the following tasks:
1
NTP 121-2
Edition 02 Released
Purpose
As a result of the massive deployment of xDSL, many more DSLAMs are provisioned in
the network. They are mostly managed separately, which makes the management
workload heavy and complicated.
To simplify the management workload of the operator, cluster management groups
multiple DSLAMs as one logical management domain. The logical management domain
of a cluster is formed by a physically interconnected group of DSLAMs. The operator can
organize its clusters according to, for example, physical location.
Topology display will present the connectivity and status of DSLAMs in a connected
environment, possibly over more than one cluster. Moreover, separately managed
DSLAMs use more public IP addresses, which are limited.
NTP 122-1
Edition 02 Released
Cluster No. 2
(A logical DSLAM)
Management
Command
to Cluster 2
EMS (AWS)
Management
Command
to Cluster 1
Single Logical
Management Path
DSLAM
No. 7
Cluster No.1
(A logical DSLAM)
DSLAM
No. 8
DSLAM
No. 2
DSLAM
No. 1
DSLAM
No. 9
DSLAM
No. 10
DSLAM
No. 3
DSLAM
No. 11
DSLAM
No. 4
DSLAM
No. 5
DSLAM
No. 6
Procedure
To configure cluster management, you need to perform the following tasks:
1
NTP 122-2
Edition 02 Released
Procedure
To configure the SSH functionality, you need to perform the following tasks:
1
NTP 123-1
Edition 02 Released
NTP 123-2
Edition 02 Released
Procedure
Perform this procedure to maintain the system:
1
NTP 124-1
Edition 02 Released
NTP 124-2
Edition 02 Released
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
NTP 125-1
Edition 02 Released
NTP 125-2
Edition 02 Released
General
System statistics logs are user configurable and you can create up to 64 system logs.
System logs can be saved locally, to a remote server, or to all active CLI or all active TL1
terminals.
You can perform the following three main tasks using CLI:
Using filters, you can determine which messages are sent to the system log file, as well
as set the severity level of the system log.
The following applies when using SYSLOG in an operational (E2E) environment:
See the 7302 ISAM | 7330 ISAM FTTN CLI Command Guide document for more
information about CLI commands used to configure system logging.
NTP 126-1
Edition 02 Released
See the 7302 ISAM | 7330 ISAM FTTN System Description document for more
information about system and security statistics logging.
Procedure
Use this procedure to manage system logging for the NE. See the references for detailed
procedures and safety information.
1
Enable and disable logging for all system logs; see DLP 179.
NTP 126-2
Edition 02 Released
Procedure
Proceed as follows to configure SHDSL:
1
NTP 127-1
Edition 02 Released
NTP 127-2
Edition 02 Released
EMS
IP@/UDP
IP@/TCP
IP@/UDP
IP@/TCP
RMI
RMI
Relay
LMI
Telnet/ IP/AAL5/ATM/DSL
TFTP/ IP/AAL5/ATM/DSL
NTP 128-1
Edition 02 Released
For IPProxy CPE Management, the CPE must support both Telnet & TFTP server
functions. The CPE-MM must support Telnet & TFTP client functions. The NE relays the
Telnet and TFTP messages between the CPE-MM and the CPE.
The CPE-MM is responsible for the management of CPE. The following interfaces are
defined:
Management channel
Data channel
Prerequisites
The following prerequisites must be fulfilled:
The CPE must have a Telnet and TFTP service on IPoA over ATM PVC 1,39
The CPE IP must be configured to be 192.168.1.1 for IPoA on ATM PVC 1,39
Procedure
To configure IPProxy CPE management, you need to perform the following tasks:
1
If not already done, enable the dual tagging mode in the SHub; see DLP 191
Configure the S-VLAN to be used for IPProxy CPE Management; see DLP 192
Configure one or more IPProxy CPE Management sessions; see DLP 194
NTP 128-2
Edition 02 Released
Edition 02 Released
Edition 02 Released
Edition 02 Released
Edition 02 Released
Edition 02 Released
Edition 02 Released
Procedure
Proceed as follows to set up a CLI session:
1
After the question Would you like a CLI(C) or a TL1 login(T) or TL1 normal
session(N)? [N]:, type C and press Enter.
Enter the default user name (isadmin) and password (i$@mad-) that were provided
to you with the system. If you do not have the default user name and password,
contact Alcatel technical support.
Note 1 For security purposes, change the default user name and
password. The system will prompt you to do this when you log in for the
first time.
Note 2 For remote CLI, after you set up the management channel,
you can set up a remote CLI session using Telnet.
4
DLP 100-1
Edition 02 Released
DLP 100-2
Edition 02 Released
Password Rules
The following rules apply to a plain text password:
DLP 101-1
Edition 02 Released
Never specify a new password in an encrypted format, because you can enter any
hexadecimal string that is not necessarily linked to a password. It is almost impossible to
calculate a password from an encrypted string. This method of specifying passwords is
only intended to restore an existing configuration.
An operator will be requested to enter a new password after logging in for the first time
after a password change.
Procedure
Proceed as follows to create an operator instance:
1
Create and configure the operator profile to which the operator will belong with the
following command:
configure system security profile (name)
(no) prompt <Sec::Prompt>
(no) password-timeout <Sec::PasswordTimeout>
(no) terminal-timeout <Sec::InactivityTimeout>
(no) slot-numbering <Sec::SlotDesc>
(no) description <Sec::ProfileDesc>
(no) aaa <Sec::Aaa>
(no) atm <Sec::Atm>
(no) alarm <Sec::Alarm>
(no) dhcp <Sec::Dhcp>
(no) equipment <Sec::Equipment>
(no) igmp <Sec::Igmp>
(no) ip <Sec::Ip>
(no) pppoe <Sec::Pppoe>
(no) qos <Sec::Qos>
(no) software-mngt <Sec::Sw>
(no) transport <Sec::Transport>
(no) vlan <Sec::Vlan>
(no) xdsl <Sec::Xdsl>
(no) security <Sec::Security>
DLP 101-2
Edition 02 Released
Configuration example:
configure system security profile profile1 no prompt
password-timeout 10 terminal-timeout 30 description Profile1
aaa read atm read alarm write no dhcp equipment write igmp write
ip write pppoe write qos write no software-mngt transport write
vlan write xdsl write security write
configure system security operator jimphelpsmi profile admin
password plain:isam123! prompt %s:%n%d%c description Operator
for MI
DLP 101-3
Edition 02 Released
DLP 101-4
Edition 02 Released
Security Considerations
Note The following must be taken into account with regard to system
security:
Procedure
Proceed as follows to configure the system management IP parameters:
1
By default, the system will start up in single IP address mode. You can set the
mode to dual IP address (refer also to DLP 103, step 1) with the following
command:
configure system id <Sys::systemId>
no single-public-ip
DLP 102-1
Edition 02 Released
Configure the network port management (inband or outband) with the following
command:
configure interface shub port (network-port)
port-type <Sys::Type>
where port-type can be:
user: port to a directly connected user
subtending: port to a subtended ISAM
network: port to the service provider (ISP)
unused: port is not in use
outband-mngt: port is used for outband-management
Select network for inband management or outband-mngt for outband management
Inband or outband management can be checked with the following commands (output of the
commands is an example):
DLP 102-2
Edition 02 Released
up
up
one-gb
outband
full
up
down
one-gb
user
full
up
down
one-gb
subtending
full
up
down
one-gb
network
full
up
up
hundred-mbps
network
full
up
up
hundred-mbps
network
half
----------------------------------------------------------------
Configure the SHub system IP group configuration with the following command:
configure system shub entry ip ip-cfg-mode <Sys::DefIpAddr>
Configure the default route of the system with the following command:
configure system management default-route (default-route)
Set the adminstrative status of the OAM VLAN to down with the following
command:
configure interface shub ip 4093 admin-status down
ii
iii
Set the adminstrative status of the OAM VLAN to up with the following
command:
configure interface shub ip 4093 admin-status up
DLP 102-3
Edition 02 Released
iv
Configure the default route in the SHub with the following command:
configure ip shub vrf 0 route-dest 0.0.0.0/0
next-hop <gateway-ip-address>
vlan-id 4093
Specify the set of ports which are statically allocated as egress ports for the SHub
management VLAN with the following command:
configure vlan shub id 4093 egress-port (port)
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)
10
11
Configuration example for dynamic configuration via BOOTP (for tagged network):
configure system id SystemID02 no single-public-ip
configure system management host-ip-address bootp
show transport ip-address
configure interface shub port 7 port-type network
configure system shub entry ip ip-cfg-mode dynamic
configure vlan shub id 4093 egress-port network:7
configure bridge shub port 7 pvid 4093
DLP 102-4
Edition 02 Released
Configuration example for static configuration via manual configuration (for tagged
network):
configure system id SystemID02 no single-public-ip
configure system management host-ip-address
manual:10.177.0.112/17
show transport ip-address
configure interface shub port 7 port-type network
show vlan global
show interface shub port
configure system shub entry ip ip-cfg-mode manual
configure system management default-route 10.177.127.254
configure interface shub vlan-id 4093 admin-status down
configure interface shub ip 4093 ip-addr 10.177.0.113/17
configure interface shub vlan-id 4093 admin-status up
configure ip shub vrf 0 route-dest 0.0.0.0/0
next-hop 10.177.127.254 vlan-id 4093
configure vlan shub id 4093 egress-port network:7
configure bridge shub port 7 pvid 4093
DLP 102-5
Edition 02 Released
DLP 102-6
Edition 02 Released
Procedure
Proceed as follows to configure the system parameters:
1
DLP 103-1
Edition 02 Released
Note 2 The system MAC address must only be configured when the
system has no System MAC Address Storage (SMAS) functionality (that
is, when no SMAS board or GFC board are present in the system).
2
If necessary, configure the system loop ID syntax with the following command:
configure system loop-id-syntax
(no) atm-based-dsl <Sys::AtmBasedDsl>
(no) efm-based-dsl <Sys::EfmBasedDsl>
DLP 103-2
Edition 02 Released
Configure the system clock source and the clock source priority scheme with the
following command:
configure system clock-mgmt
(no) priority-scheme <Sys::SysClkSrcPriorityScheme>
(no) ext-source <Sys::SysClkExtSource>
View information about the SNTP and its related parameters with the following
command:
show sntp
DLP 103-3
Edition 02 Released
Configuration example:
configure system id SystemID02 name Test_Asam location Magabir
contact-person Ewan Tendunnit (Phone ext 345) mgnt-vlan-id 4093
configure system shub entry id contact Hugh Shuckman (Phone ext
003) location Magabir
configure system loop-id-syntax atm-based-dsl
Access_Node_ID atm Rack-Frame-Slot-Port:VPI.VCI
configure system loop-id-syntax efm-based-dsl
Access_Node_ID eth Rack-Frame-Slot-Port:0.0
admin sntp system-time 2007-01-01:23:55:00
configure system sntp server-ip-addr 10.176.5.5 enable
timezone-offset 6
configure system clock-mgmt priority-scheme local
configure error log-full-action wrap
show sntp
DLP 103-4
Edition 02 Released
DLP 104-1
Edition 02 Released
DLP 104-2
Edition 02 Released
Network links:
The number of aggregation links depends on the NT board type
For ECNT-A: an aggregation can exist of maximum 7 component links.
For ECNT-C, NANT-A: an aggregation can exist of maximum 8 component links.
Subtending links:
For an FE type link or a GE type link, an aggregation can exist of maximum 7
component links
This document describes the procedure to configure the link aggregation usage.
DLP 105-1
Edition 02 Released
General
This node allows specification of Link Aggregation Group parameters.
A Link Aggregation Group is identified by means of the primary link, also referred to as
aggregator-port. The primary link for an Aggregation Group is the link with the lowest port
number within the group, provided the operational state of the link is UP.
The configuration should be performed for the primary link. The settings configured for
the primary link of the Aggregation Group apply to each and every link that is a member
of the Link Aggregation Group.
The link which is denoted as primary link may change during the lifetime of the
aggregation group. To cope with this phenomenon, the operator is advised to repeat the
configurations described in this procedure for each link of the Aggregation Group. Care
must be taken to configure identical settings for all links within the Aggregation Group.
Prerequisite
The following prerequisites must be fullfilled before link aggregation can be configured:
The port-type of the network port must be network or subtending.
This can be verified with the command
show interface shub port
Procedure
Proceed as follows to configure link aggregation usage:
1
Specify the Link Aggregation Group parameters with the following command:
configure la aggregator-port (network-port)
name <Shub::AggName>
(no) link-up-down-trap
(no) actor-sys-prio <Shub::LaPortActorSysPriority>
selection-policy <Shub::AggSelectPolicy>
actor-key <Shub::LacpKey>
(no) actor-port-prio <Shub::LaPortActorPortPriority>
(no) active-lacp
(no) short-timeout
(no) aggregatable
lacp-mode <Shub::LacpMode>
Use the following command to configure Link Aggregation on the SHub. It merely
allows to enable or disable the Link Aggregation feature:
configure la no disable-lacp
DLP 105-2
Edition 02 Released
View information for a Link Aggregation Group configured on the Service Hub with
the following command:
show la aggregator-info (port)
Configuration example:
configure interface shub port [1...2] port-type subtending
configure la aggregator-port [1...2] aggregatable name testsub
lacp-mode enable-lacp active-lacp actor-key 1234
link-up-down-trap
configure la no disable-lacp
show la aggregator-info [1...2]
show la network-port-info [1...2]
DLP 105-3
Edition 02 Released
DLP 105-4
Edition 02 Released
Prerequisite
The following prerequisite must be fullfilled before RSTP can be configured:
The port-type of the network port must be different from unused.
This can be verified with the command
show interface shub port
DLP 106-1
Edition 02 Released
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>
Specify RSTP settings applicable to a particular port of the SHub with 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>
View the bridge RSTP operational information (port states, port roles, and so on)
with the following command:
show rstp port-info (port)
DLP 106-2
Edition 02 Released
Configuration example:
configure rstp max-age 2500 hello-time 200 forward-delay 2000
tx-hold-count 3
configure rstp network-port 7 priority 160 admin-p2p force-true
admin bridge rstp port 7
show rstp port-info 7
DLP 106-3
Edition 02 Released
DLP 106-4
Edition 02 Released
General
An OSPF network is divided into areas. These are logical groupings of routers whose
information may be summarized towards the rest of the network. Several special area
types are defined:
Backbone area:
The backbone area (also known as area zero) forms the core of an OSPF network.
All other areas are connected to it, and inter-area routing happens via a router
connected to the backbone area. It is the logical and physical structure for the
Autonomous System (AS) and is attached to multiple areas. The backbone area is
responsible for distributing routing information between non-backbone areas. The
backbone must be contiguous, but it does not need to be physically contiguous;
backbone connectivity can be established and maintained through the configuration
of virtual links.
Note: All OSPF areas must connect to the backbone area
Stub area:
A stub area is an area which does not receive external routes. External routes are
defined as routes which were distributed in OSPF from another routing protocol.
Therefore, stub areas typically need to rely on a default route to send traffic to routes
outside the present domain. This implies that AS external routes are not fed into stub
areas
Not-so-stubby area:
A not-so-stubby area (NSSA) is a type of stub area that can import AS external routes
and send them to the backbone, but cannot receive AS external routes from the
backbone or other areas.
DLP 107-1
Edition 02 Released
Procedure
Proceed as follows to configure OSPF management:
1
Configure the OSPF parameters and attributes with the following command:
configure ospf enable
router-id <Ip::V4Address>
(no) as-border-router
(no) enable-opaque-lsa
(no) overflow-state-it <Ospf::OvrflowIntrvl>
(no) dis-rfc1583-comp
(no) abr-type <Ospf::AbrType>
(no) passive-interface
ii
iii
iv
When MD5 is selected as authentication mode for an OSPF interface, use the
following command to configure the MD5 key:
configure ospf area (area-id) interface (ip-addr)
md5-key (index)
key prompt | plain: <Ospf::MD5key>
| encrypted: <Ospf::MD5encryptedKey>
(no) accept-starts <Ospf::MD5startDelay>
(no) generate-starts <Ospf::MD5startDelay>
DLP 107-2
Edition 02 Released
vi
Configure the metric for an OSPF interface with the following command:
configure ospf area (area-id) interface (ip-addr)
(no) metric value <Ospf::Metric>
vii
viii External route summarization is specific to external routes that are injected into
OSPF via redistribution. Also, make sure that external ranges that are being
summarized are contiguous. Summarization overlapping ranges from two
different routers could cause packets to be sent to the wrong destination.
Configure an OSPF aggregate from external autonomous system with the
following command:
configure ospf area (area-id) extern-aggr-addr (dest-ip)
(no) advertise <Ospf::ExtAggregateEffect>
ii
Configure the OSPF stub area interface with the following command:
configure ospf stub-area (area-id) interface (ip-addr)
(no) disable
(no) router-priority <Ospf::Priority>
(no) passive
(no) itf-type <Ospf::ITFType>
(no) authentication <Ospf::AuthType>
iii
Configure the OSPF stub area interface timers with the following command:
configure ospf stub-area (area-id) interface (ip-addr) timers
(no) transit-delay <Ospf::TransDelay>
(no) retransmit-itvl <Ospf::RetransIntvl>
(no) hello-interval <Ospf::HelloIntvl>
(no) dead-interval <Ospf::DeadIntvl>
(no) poll-interval <Ospf::PollIntvl>
DLP 107-3
Edition 02 Released
iv
Configure the metric for an OSPF stub area interface with the following
command:
configure ospf stub-area (area-id) interface (ip-addr)
(no) metric value <Ospf::Metric>
vii
Configure the OSPF NSSA area parameters with the following command:
i
ii
Configure the OSPF NSSA area interface with the following command:
configure ospf nssa-area (area-id) interface (ip-addr)
(no) disable
(no) router-priority <Ospf::Priority>
(no) passive
(no) itf-type <Ospf::ITFType>
(no) authentication <Ospf::AuthType>
iii
Configure the OSPF NSSA area interface timers with the following command:
configure ospf nssa-area (area-id) interface (ip-addr) timers
(no) transit-delay <Ospf::TransDelay>
(no) retransmit-itvl <Ospf::RetransIntvl>
(no) hello-interval <Ospf::HelloIntvl>
(no) dead-interval <Ospf::DeadIntvl>
(no) poll-interval <Ospf::PollIntvl>
DLP 107-4
Edition 02 Released
iv
Configure the metric for an OSPF NSSA area interface with the following
command:
configure ospf nssa-area (area-id) interface (ip-addr)
(no) metric value <Ospf::Metric>
vii
viii Configure an OSPF NSSA aggregate from external autonomous systems with
the following command:
configure ospf nssa-area (area-id) extern-aggr-addr (dest-ip)
(no) advertise <Ospf::ExtAggregateEffect>
Configure the redistribution of the OSPF route parameters with the following
command:
configure ospf redistribution route-destination (dest-ip)
(no) metric-type <Ospf::RouteMetricType>
(no) metric <Ospf::RouteMetric>
DLP 107-5
Edition 02 Released
Configuration example:
configure interface shub port [4...5] port-type network
DLP 107-6
Edition 02 Released
DLP 107-7
Edition 02 Released
DLP 107-8
Edition 02 Released
Limitations
The following limitations apply:
Procedure
Proceed as follows to configure RIP management:
1
DLP 108-1
Edition 02 Released
If the MD5 authentication method is selected for a RIP interface (see step 5), then
the MD5 key can be configured with the following command:
i
ii
An MD5 key for a RIP interface can be managed with the following command:
admin rip interface (ip-addr) md5-key <Rip::Md5KeyIndex>
expires <Rip::MD5expiryDelay>
DLP 108-2
Edition 02 Released
10
Configuration example:
configure rip max-peer 50
configure rip redistribution enable default-metric 2
configure rip interface 192.168.80.39 default-metric 1 receive
rip2
send rip2 split-horizon poison-reverse
configure rip interface 192.168.80.39 timers update-timer 30
route-age-out 180 junk-collection 120
configure rip interface 192.168.80.39 md5-key 4
key plain:AlcatelTest expires 2147483647 starts 0
configure rip interface 192.168.80.39 authentication md5
configure rip redistribution enable static ospf
configure ospf redistribution rip
configure rip route-map 70 sub-index 1 ip-addr 192.168.145.1/32
no deny
DLP 108-3
Edition 02 Released
DLP 108-4
Edition 02 Released
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.
Alcatel 7302 ISAM R3.2 February 2007
Operations and Maintenance Using CLI 3HH-04065-AAAA-TQZZA
DLP 109-1
Edition 02 Released
Security Considerations
Note The following must be taken into account with regard to system
security:
Procedure
Proceed as follows to configure SNMP and trap management:
1
DLP 109-2
Edition 02 Released
10
11
DLP 109-3
Edition 02 Released
12
13
14
15
Configuration example:
Example for SNMPv1 or SNMPv2:
configure system security snmp view view1 subtree * type include
configure system security snmp view view1
subtree 1.3.6.1.4.1.637.61.1.48.* type exclude
configure system security snmp community public
host-address 10.176.0.0/15 context nt privilege read-write
configure system security snmp community NETMAN
host-address 10.176.0.0/15 context shub
configure system security snmp community comm1
host-address 10.176.0.0/15 context nt read-view protected
write-view view1 notify-view everything
configure system security snmp shub community 3 name NETMAN
privilege read-write ip-addr 10.176.8.8
configure system security snmp notify-view nview1 subtree *
type include
configure system security snmp notify-view nview1
subtree bondingMIB.* type exclude
configure system security snmp notify-profile nprof1
snmp-version v1:trapcomm
configure system security snmp notify-profile nprof1 filter
notify-view nview1
DLP 109-4
Edition 02 Released
DLP 109-5
Edition 02 Released
DLP 109-6
Edition 02 Released
Note The commands for viewing the different alarms are described in
DLP 155.
Prerequisite
The following prerequisite must be fullfilled:
DLP 110-1
Edition 02 Released
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>
ii
Modify the alarm severity and actions on individual alarms with the following
command:
configure alarm entry (index)
severity <Alarm::alarmSeverity>
(no) service-affecting
(no) reporting
(no) logging
iii
Configure the action to be taken when the alarm log buffer is completely full
with the following command:
configure alarm delta-log
indet-log-full-action <Alarm::alarmDeltaLogFullAction>
warn-log-full-action <Alarm::alarmDeltaLogFullAction>
minor-log-full-action <Alarm::alarmDeltaLogFullAction>
major-log-full-action <Alarm::alarmDeltaLogFullAction>
crit-log-full-act <Alarm::alarmDeltaLogFullAction>
If the action is set to Wrap, then older log records are overwritten by recent ones.
If the action is set to Halt, then logging is stopped until the log buffer is reset.
iv
Tune the alarm reporting for individual ports (for example, xDSL lines) with the
following command:
configure interface port (port)
(no) severity <Itf::asamIfExtAlmReportingSeverity>
Configure the default severity for an alarm on a type of interface with the
following command:
configure interface alarm (index)
(no) default-severity
<Itf::asamIfExtAlmReportingSeverityDefault>
vi
DLP 110-2
Edition 02 Released
Configure an alarm profile for remote LT boards with the following command:
configure alarm custom-profile (name)
(no) mnemonic1 <Alarm::AlarmMnemonic>
(no) description1 <Alarm::AlarmDescription>
(no) visible1 <Alarm::VisibleOutput>
(no) audible1 <Alarm::AudibleOutput>
(no) polarity1 <Alarm::InversePolarity>
(no) severity1 <Alarm::AlarmSeverity>
(no) mnemonic2 <Alarm::AlarmMnemonic>
(no) description2 <Alarm::AlarmDescription>
(no) visible2 <Alarm::VisibleOutput>
(no) audible2 <Alarm::AudibleOutput>
(no) polarity2 <Alarm::InversePolarity>
(no) severity2 <Alarm::AlarmSeverity>
(no) mnemonic3 <Alarm::AlarmMnemonic>
(no) description3 <Alarm::AlarmDescription>
(no) visible3 <Alarm::VisibleOutput>
(no) audible3 <Alarm::AudibleOutput>
(no) polarity3 <Alarm::InversePolarity>
(no) severity3 <Alarm::AlarmSeverity>
(no) mnemonic4 <Alarm::AlarmMnemonic>
(no) description4 <Alarm::AlarmDescription>
(no) visible4 <Alarm::VisibleOutput>
(no) audible4 <Alarm::AudibleOutput>
(no) polarity4 <Alarm::InversePolarity>
(no) severity4 <Alarm::AlarmSeverity>
(no) mnemonic5 <Alarm::AlarmMnemonic>
(no) description5 <Alarm::AlarmDescription>
(no) visible5 <Alarm::VisibleOutput>
(no) audible5 <Alarm::AudibleOutput>
(no) polarity5 <Alarm::InversePolarity>
(no) severity5 <Alarm::AlarmSeverity>
Configuration example:
configure alarm log-sev-level warning log-full-action wrap
non-itf-rep-sev-level minor
configure alarm entry xdsl-act-not-feas severity major
service-affecting reporting logging
configure alarm entry no-bonding-cpe severity major
service-affecting reporting logging
configure alarm delta-log indet-log-full-action wrap
warn-log-full-action wrap minor-log-full-action wrap
major-log-full-action halt crit-log-full-act halt
configure interface port xdsl-line:1/1/5/12 severity major
configure interface alarm xdsl-line default-severity critical
DLP 110-3
Edition 02 Released
DLP 110-4
Edition 02 Released
DLP 111-1
Edition 02 Released
Procedure
Proceed as follows to plan, replan, and unplan equipment:
1
Plan a plug-in unit other than an applique in any given slot position with the following
command:
configure equipment slot (index)
planned-type <Equipm::BoardType>
(no) power-down
(no) unlock
(no) alarm-profile <Equipm::AlarmProf>
capab-profile <Equipm::CapabilityProfile>
Unplan a plug-in unit other than an applique in any given slot position with the
following command:
configure equipment slot (index)
no planned-type
DLP 111-2
Edition 02 Released
Configuration example:
configure equipment shelf 1/1 description "***Mainshelf***"
configure equipment slot 1/1/1 planned-type aacu-c
configure equipment slot nt-b planned-type ecnt-c
configure equipment applique iont:1/1 planned-type ecnc-a
configure equipment slot lt:1/1/4 planned-type evlt-c
configure equipment slot lt:1/1/5 planned-type eblt-c
configure equipment slot lt:1/1/6 planned-type polt-b
configure equipment slot lt:1/1/7 planned-type eblt-k
configure equipment slot lt:1/1/8 planned-type eblt-k
configure equipment slot 1/1/9 planned-type smlt-k
info configure equipment slot flat
show equipment slot
DLP 111-3
Edition 02 Released
DLP 111-4
Edition 02 Released
Procedure
Proceed as follows to lock and unlock a plug-in unit:
1
Configuration example:
configure equipment slot 1/1/5 no unlock
sleep 60
configure equipment slot 1/1/5 unlock
DLP 112-1
Edition 02 Released
DLP 112-2
Edition 02 Released
Procedure
Proceed as follows to configure the NE equipment:
1
DLP 113-1
Edition 02 Released
Use any of the following commands to view and verify the configuration of the
system:
show equipment isam detail
This command shows the system configuration and status. This configuration is
fixed and hardcoded.
show equipment rack (rack) detail
This command shows the profile-id associated with a profile name, the description
of the profile and the board type associated with a given profile.
5
Configuration example:
configure equipment isam description Magabir Plant
configure equipment rack 1 description ***Main Rack***
configure equipment shelf 1/1 description Testshelf_Antwerp
show equipment rack 1 detail
show equipment shelf 1/1 detail
show equipment slot 1/1/5 detail
show equipment applique 1/1/2 detail
DLP 113-2
Edition 02 Released
DLP 114-1
Edition 02 Released
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>
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>
ii
Set the adminstrative status of the port(s) to up with the following command:
configure interface shub port (network-port)
admin-status up
DLP 114-2
Edition 02 Released
Configure the NT 1+1 protection group on the SHub with the following
command:
configure interface shub group (group-id)
Add 1 (or more) network port(s) to the NT 1+1 protection group with the
following command:
configure interface shub group (group-id) port (port)
iii
By default, there is no APS-EPS coupling in the NE. That means that the
minimum number of links to be in state operational UP in the protection-group
is 0 by default. Or in other words, a link failure will not trigger a switchover from
the active NT to the standby NT.
If a coupling is required (that is NT switchover in case of link failure), the SHub
has to be configured with a threshold > 0 as follows:
configure interface shub group (group-id)
threshold <Itf::Threshold>
iv
You can view the protection group configuration parameters with the following
command:
show equipment protection-group (prot-group-id)
You can view the protection element configuration parameters with the following
command:
show equipment protection-element (slot-id)
DLP 114-3
Edition 02 Released
Configuration example:
configure equipment protection-group 1 admin-status unlock
eps-quenchfactor 60000
configure equipment protection-element nt-a
redcy-ctrl-status normal
configure interface shub port [1...2] mode automatic
port-type subtending
configure interface shub port [1...2] admin-status up
configure interface shub group 1
configure equipment protection-group 1 admin-status lock
configure interface shub group 1 port [1...2]
configure interface shub group 1 threshold 2
configure equipment protection-group 1 admin-status unlock
configure equipment protection-element nt-b
redcy-ctrl-status normal
DLP 114-4
Edition 02 Released
DLP 115-1
Edition 02 Released
SHub
VRF
P-VLAN
ISP
VRF
DHCP
Relay
ARP
Proxy
P-VLAN
VB
P-VLAN
LT
IPoE/A Session
IPoE/A
Interface
ARP
Proxy
DHCP
Relay
VRF
P-VLAN
ISP
ARP
Proxy
PPPoE/PPPoA, IPoE/IPoA
always untagged
IPoE
(P-VLAN)
IPoE
(P-VLAN)
Prerequisites
The following prerequisites must be fulfilled before a Layer2-terminated forwarder VLAN
can be configured:
DLP 115-2
Edition 02 Released
Procedure
Proceed as follows to configure a Layer2-terminated forwarder VLAN:
1
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
DLP 115-3
Edition 02 Released
Configure the SHub network egress port on the network with the following
command:
configure vlan shub id (vlanid) egress-port
network:<Shub::NetworkPort>
ii
Configure the SHub network egress port on the LT with the following
command:
configure vlan shub id (vlanid) egress-port
lt:<Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::LtSlot>
Configure the DHCP relay agent per VRF (for handling broadcast frames) with the
following command:
configure dhcp-relay agent (vrfid)
bcast-vlan <Dhcp::VlanId>
(no) option-82
(no) circuit-id <Dhcp::CircuitId>
(no) remote-id <Dhcp::RemoteId>
(no) mac-concent <Dhcp::MacConcentration>
(no) dhcp-linerate <Dhcp::Dhcp-linerate>
Configuration example:
configure vlan id 101 name ISPforwVLAN-101
mode layer2-terminated
configure vlan shub id 101 name ISPforwVLAN-101
mode residential-bridge
configure ip vrf 16 network-itf 101 arp-policy trusted unnumbered
configure ip vrf 16 gateway-itf ip-address 192.168.116.1/21
configure ip vrf 16 route-dest 0.0.0.0/0
next-hop 10.179.136.1:network:vlan:101
configure vlan shub id 101 egress-port network:7
configure vlan shub id 101 egress-port lt:1/1/[4...19]
configure dhcp-relay agent 16 bcast-vlan l2-vlan:101
DLP 115-4
Edition 02 Released
IP interfaces are created on the network VLANs towards the edge routers. IP interface
addresses are seen as the Next-Hop addresses in the downstream from edge routers
to ISAM.
User-gateway interface is the interface towards the users and it is created on V-VLAN.
IP address configured on the user-gateway interface represents the gateway IP
address for the users, and subnet configured on the user-gateway interface
represents the subnet of the users.
DLP 116-1
Edition 02 Released
VRF
PPPoE/A
Interface
ARP
Proxy
SHub
V-VLAN
P-VLAN
IPoE/A
Interface
ARP
Proxy
DHCP
Relay
ARP
VRF
ISP
VRF
LT
IPoE/A Session
Routing Protocols
(OSPF, RIPv2)
V-VLAN
DHCP
Relay
ARP
Proxy
PPPoE/PPPoA, IPoE/IPoA
always untagged
IPoE
(V-VLAN per VR)
IPoE
(P-VLAN)
Prerequisites
The following prerequisites must be fulfilled before a Layer2-terminated router VLAN can
be configured:
DLP 116-2
Edition 02 Released
Procedure
Proceed as follows to configure a Layer2-terminated router VLAN:
1
Add the virtual VLAN to the LT port where the Layer2-terminated router is active with
the following command:
configure vlan shub id (vlanid)
egress-port lt:<Eqpt::RackId>/<Eqpt::ShelfId>/<Shub::SlotId>
Create an IP interface on the virtual VLAN on the SHub with the following command:
configure interface shub vlan-id (vlanid)
Configure the IP address of the internal IP interface with the following command:
configure interface shub ip (vlanid)
ip-address <Ip::V4Address>/<Ip::PrefixLengthFull>
Set the administrative state of the VLAN interface to up with the following command:
configure interface shub vlan-id (vlanid) admin-status up
Create a L2 network terminated VLAN on the Shub with the following command:
configure vlan shub id (vlanid)
(no) name <Vlan::AdminString>
mode layer2-term-nwport
(no) mac-move-allow
Create and configure an SHub network port with the following command:
configure interface shub port (network-port)
(no) mode automatic | 10mbps:full | 10mbps:half | 100mbps:full
| 100mbps:half | 1gbps:full | 1gbps:half
port-type network-port
(no) mc-flooding
10
Change the administrative status of the SHub network port with the following
command:
configure interface shub port (network-port)
DLP 116-3
Edition 02 Released
admin-status up
11
Configure an egress port for the L2 network terminated VLAN on the SHub with the
following command:
configure vlan shub id (vlanid) egress-port
network:<Shub::NetworkPort>
12
Configure the SHub network egress port for untagged packets with the following
command:
configure vlan shub id (vlanid) untag-port <Shub::NetworkPort>
13
Configure the port VLAN ID for the untagged packets with the following command:
configure bridge shub port <Shub::NetworkPort>
pvid <Vlan::VlanOamIndex>
14
15
16
Configure the IP address of the external IP interface with the following command:
configure interface shub ip (vlanid) ip-address (ip-address)
17
Set the administrative state of the VLAN interface to up with the following command:
configure interface shub vlan-id (vlanid) admin-status up
18
19
20
DLP 116-4
Edition 02 Released
21
Configure the DHCP relay agent per VRF (for handling broadcast frames) with the
following command:
configure dhcp-relay agent (vrfid)
bcast-vlan <Dhcp::VlanId>
(no) option-82
(no) circuit-id <Dhcp::CircuitId>
(no) remote-id <Dhcp::RemoteId>
(no) mac-concent <Dhcp::MacConcentration>
(no) dhcp-linerate <Dhcp::Dhcp-linerate>
22
DLP 116-5
Edition 02 Released
DLP 116-6
Edition 02 Released
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
DLP 117-1
Edition 02 Released
ii
iii
Create and configure an SHub network port with the following command:
configure interface shub port (network-port)
(no) mode automatic | 10mbps:full | 10mbps:half | 100mbps:full
| 100mbps:half | 1gbps:full | 1gbps:half
port-type network
(no) mc-flooding
admin-status up
ii
Configure the SHub network egress port on the network with the following
command:
configure vlan shub id (vlanid) egress-port
network:<Shub::NetworkPort>
iii
Configure the SHub network egress port on the LT with the following
command:
configure vlan shub id (vlanid) egress-port
lt:<Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::LtSlot>
DLP 117-2
Edition 02 Released
Configuration example:
1. Example for ADSL line:
configure vlan id 300 name "ISP_C_VLAN_300" mode cross-connect
configure vlan id 300 dhcp-opt-82 circuit-id-dhcp physical-id
remote-id-dhcp customer-id
configure vlan shub id 300 name "ISP_C_VLAN_300"
mode cross-connect
configure interface shub port 7 port-type network admin-status up
configure vlan shub id 300 egress-port network:7
configure vlan shub id 300 egress-port lt:1/1/5
configure xdsl line 1/1/5/1 service-profile 7 spectrum-profile 5
admin-up
configure atm pvc 1/1/5/1:8:35 aal5-encap-type
vc-mux-bridged-8023
configure bridge port 1/1/5/1:8:35
configure bridge port 1/1/5/1:8:35 vlan-id 300
configure bridge port 1/1/5/1:8:35 pvid 300
DLP 117-3
Edition 02 Released
DLP 117-4
Edition 02 Released
Prerequisite
The following prerequisite must be fulfilled before an S-VLAN can be configured:
Procedure
Proceed as follows to configure an S-VLAN:
1
Create an S-VLAN:
i
DLP 118-1
Edition 02 Released
(no)
(no)
(no)
(no)
(no)
ii
priority <Vlan::Priority>
broadcast-frames
protocol-filter <Vlan::ProtGroup>
pppoe-relay
pppoe-relay-tag <Vlan::PppoeRelayEnableR3.1>
iii
Create and configure an SHub network port with the following command:
configure vlan shub id <Vlan::UVlanIndex>
name <Vlan::AdminString>
mode cross-connect
Create and configure an SHub network port with the following command:
configure interface shub port (network-port)
(no) mode automatic | 10mbps:full | 10mbps:half | 100mbps:full
| 100mbps:half | 1gbps:full | 1gbps:half
port-type network
(no) mc-flooding
admin-status up
ii
Configure the SHub network egress port on the network with the following
command:
configure vlan shub id (vlanid) egress-port
network:<Shub::NetworkPort>
iii
Configure the SHub network egress port on the LT with the following
command:
configure vlan shub id (vlanid) egress-port
lt:<Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::LtSlot>
DLP 118-2
Edition 02 Released
Configuration example:
1. Example for ADSL line:
configure vlan id stacked:400:0 name IPS_S_VLAN-400
mode cross-connect
configure vlan shub id 400 name ISP_S_VLAN-400
mode cross-connect
configure interface shub port 7 port-type network admin-status up
configure vlan shub id 400 egress-port network:7
configure vlan shub id 400 egress-port lt:1/1/5
configure xdsl line 1/1/5/2 service-profile 7 spectrum-profile 5
admin-up
configure atm pvc 1/1/5/2:8:35 aal5-encap-type
vc-mux-bridged-8023
configure bridge port 1/1/5/2:8:35
configure bridge port 1/1/5/2:8:35 vlan-id stacked:400:0
configure bridge port 1/1/5/2:8:35 pvid stacked:400:0
DLP 118-3
Edition 02 Released
DLP 118-4
Edition 02 Released
Prerequisite
The following prerequisite must be fulfilled before an SC-VLAN can be configured:
DLP 119-1
Edition 02 Released
Procedure
Proceed as follows to configure an SC-VLAN:
1
Create an SC-VLAN:
i
ii
iii
iv
DLP 119-2
Edition 02 Released
Create and configure an SHub network port with the following command:
configure interface shub port (network-port)
(no) mode automatic | 10mbps:full | 10mbps:half | 100mbps:full
| 100mbps:half | 1gbps:full | 1gbps:half
port-type network-port
(no) mc-flooding
admin-status up
ii
Configure the SHub network egress port on the network with the following
command:
configure vlan shub id (vlanid) egress-port
network:<Shub::NetworkPort>
iii
Configure the SHub network egress port on the LT with the following
command:
configure vlan shub id (vlanid) egress-port
lt:<Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::LtSlot>
Configuration example:
1. Example for ADSL line:
configure vlan id stacked:500:0 name ISP_SC_VLAN-500
mode layer2-terminated
configure vlan id stacked:500:600 name ISP_SC_VLAN-500-600
mode cross-connect
configure vlan shub id 500 name ISP_SC_VLAN-500
mode cross-connect
configure interface shub port 7 port-type network admin-status up
configure vlan shub id 500 egress-port network:7
configure vlan shub id 500 egress-port lt:1/1/5
configure xdsl line 1/1/5/3 service-profile 7 spectrum-profile 5
admin-up
configure atm pvc 1/1/5/3:8:35
aal5-encap-type vc-mux-bridged-8023
configure bridge port 1/1/5/3:8:35
configure bridge port 1/1/5/3:8:35 vlan-id stacked:500:600
configure bridge port 1/1/5/3:8:35 pvid stacked:500:600
DLP 119-3
Edition 02 Released
DLP 119-4
Edition 02 Released
Procedure
Proceed as follows to configure an iBridge VLAN:
1
DLP 120-1
Edition 02 Released
Configuration examples:
configure vlan id 56 name vlan56 mode residential-bridge
DLP 120-2
Edition 02 Released
Prerequisite
The following prerequisite must be fulfilled before network interfaces can be added to a
VLAN:
A VLAN must have been created; see DLP 117, DLP 118, DLP 119 or DLP 120.
Procedure
Proceed as follows to add a network interface to a VLAN:
1
Create and configure an SHub network port with the following command:
configure interface shub port (network-port)
(no) mode automatic | 10mbps:full | 10mbps:half | 100mbps:full
| 100mbps:half | 1gbps:full | 1gbps:half
(no) port-type <Sys::Type>
(no) mc-flooding
Change the administrative status of the SHub network port with the following
command:
configure interface shub port (network-port)
admin-status auto-up
Configure the SHub network egress port with the following command:
configure vlan shub id (vlanid) egress-port
network:<Shub::NetworkPort>
DLP 121-1
Edition 02 Released
Configure the SHub network egress port for untagged packets with the following
command:
configure vlan shub id (vlanid) untag-port
network:<Shub::NetworkPort>
Configure the port VLAN ID for the untagged packets with the following command:
configure bridge shub port <Shub::NetworkPort>
pvid <Vlan::VlanOamIndex>
Configuration example:
configure interface shub port 3 mode automatic port-type network
configure interface shub port 3 admin-status auto-up
configure vlan shub id 100 egress-port network:3
configure vlan shub id 100 egress-port lt:1/1/[4...7]
configure vlan shub id 100 untag-port network:3
configure vlan shub id 200 egress-port network:7
configure vlan shub id 200 egress-port lt:1/1/[4...9]
configure bridge shub port 3 pvid 100
DLP 121-2
Edition 02 Released
Procedure
Proceed as follows to configure the forwarding VRF:
1
DLP 122-1
Edition 02 Released
Configuration example:
configure ip vrf 16 name forwardingvrf16 mode forwarder
DLP 122-2
Edition 02 Released
Procedure
Proceed as follows to configure a VRF in routing mode:
1
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
DLP 123-1
Edition 02 Released
Note The VRF on the SHub must always be created with mode
fast-path-mode.
Configuration example:
configure ip vrf 5 name routervrf5 mode router
configure ip shub vrf 15 name routervrf15
fast-path-mode:ena-user-user-com
DLP 123-2
Edition 02 Released
Prerequisites
The following prerequisites must be fulfilled before an iBridge user can be created:
Procedure
Proceed as follows to create an xDSL user:
1
DLP 124-1
Edition 02 Released
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
g992-3-am
g992-5-a
g992-5-b
ansi-t1.424
etsi-ts
itu-g993-1
ieee-802.3ah
g992-5-am
carrier-data-mode <Xdsl::CarrierDataMode>
admin-up
bonding-mode <Xdsl::BondingMode>
transfer-mode <Xdsl::TpsTcMode>
Create an ATM PVC (or the necessary ATM PVCs) with the following command:
configure atm pvc (port-index)
(no) admin-down
(no) aal5-encap-type llc-snap | llc-snap-routed | llc-nlpid
| vc-mux-bridged-8023 | vc-mux-routed
| vc-mux-pppoa | automatic:ip
| automatic:ppp | automatic:pppoa
For each of the created PVCs, create a bridge port with the following command:
configure bridge port (port)
(no) pvid <Vlan::StackedVlan>
(no) default-priority <Vlan::Priority
(no) mac-learn-off
(no) max-unicast-mac <Vlan::MaxMac>
(no) accept-frame-type <Vlan::VlanFrameTypes>
(no) qos-profile <Vlan::QosProfileName>
(no) prio-regen-prof <Vlan::PrioRegenProfile>
DLP 124-2
Edition 02 Released
For each created bridge port, assign a VLAN to the bridge port and set the priorities
applicable for that port with the following command:
configure bridge port (port) vlan-id (index)
(no) (tag)
(no) qos-profile none | 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-ctr
Configuration examples:
1. For an ADSL user:
configure xdsl line 1/1/5/12 service-profile 7 spectrum-profile 5
transfer-mode atm admin-up
configure atm pvc 1/1/5/12:8:35 aal5-encap-type
vc-mux-bridged-8023
configure bridge port 1/1/5/12:8:35
configure bridge port 1/1/5/12:8:35 vlan-id 200
configure bridge port 1/1/5/12:8:35 pvid 200
DLP 124-3
Edition 02 Released
DLP 124-4
Edition 02 Released
Prerequisites
The following prerequisites must be fulfilled before an IPoA user can be created:
Procedure
Proceed as follows to create an IPoA user:
1
DLP 125-1
Edition 02 Released
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
g992-5-b
ansi-t1.424
etsi-ts
itu-g993-1
ieee-802.3ah
g992-5-am
carrier-data-mode <Xdsl::CarrierDataMode>
admin-up
bonding-mode <Xdsl::BondingMode>
transfer-mode <Xdsl::TpsTcMode>
Create a route in the SHub towards the modem with the following command:
configure ip shub vrf (index) route-dest (dest)
next-hop <Ip::NextHopV4Address>
vlan-id <Vlan::VlanId>
where:
route-dest is the subnet which is assigned to the user
next-hop is the IP address of the WAN side of the modem.
If the user is a static user, continue with the next step, else go to 9.
DLP 125-2
Edition 02 Released
Configuration example:
configure xdsl line 1/1/5/13 service-profile 7 spectrum-profile 5
admin-up
configure atm pvc 1/1/5/13:8:35 no admin-down
aal5-encap-type vc-mux-routed
configure ip vrf 16 user-itf port 1/1/5/13:8:35
configure ip vrf 16 route-dest 10.178.14.53/32
next-hop direct:user-port:1/1/5/13:8:35
DLP 125-3
Edition 02 Released
DLP 125-4
Edition 02 Released
Prerequisites
The following prerequisites must be fulfilled before an IPoE user can be created:
Procedure
Proceed as follows to create an IPoE user:
1
DLP 126-1
Edition 02 Released
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
g992-5-b
ansi-t1.424
etsi-ts
itu-g993-1
ieee-802.3ah
g992-5-am
carrier-data-mode <Xdsl::CarrierDataMode>
admin-up
bonding-mode <Xdsl::BondingMode>
transfer-mode <Xdsl::TpsTcMode>
If the user is a static user, continue with the next step, else go to 9.
DLP 126-2
Edition 02 Released
Configuration examples:
1. For an ADSL user:
configure xdsl line 1/1/5/14 service-profile 7 spectrum-profile 5
transfer-mode atm admin-up
configure atm pvc 1/1/5/14:8:35 aal5-encap-type vc-mux-bridged
configure bridge port 1/1/5/14:8:35
configure ip vrf 16 user-itf bridgeport 1/1/5/14:8:35
DLP 126-3
Edition 02 Released
DLP 126-4
Edition 02 Released
Prerequisites
The following prerequisites must be fulfilled before an PPPoE user can be created:
Procedure
Proceed as follows to create a PPPoE user:
1
DLP 127-1
Edition 02 Released
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
g992-3-l2
g992-3-am
g992-5-a
g992-5-b
ansi-t1.424
etsi-ts
itu-g993-1
ieee-802.3ah
g992-5-am
carrier-data-mode <Xdsl::CarrierDataMode>
admin-up
bonding-mode <Xdsl::BondingMode>
transfer-mode <Xdsl::TpsTcMode>
DLP 127-2
Edition 02 Released
Configuration examples:
1. For an ADSL user:
configure xdsl line 1/1/5/15 service-profile 7 spectrum-profile 5
transfer-mode atm admin-up
configure interface port xdsl-line:1/1/5/15 user TestUser1
configure atm pvc 1/1/5/15:8:35 aal5-encap-type llc-snap
configure bridge port 1/1/5/15:8:35 max-unicast-mac 4
configure pppoe pppox-interface 1/1/5/15:8:35 max-num-session 16
ppp-profile-name PPPProf1
DLP 127-3
Edition 02 Released
DLP 127-4
Edition 02 Released
Procedure
Proceed as follows to add an LT to the correct VLAN service:
1
Configuration example:
configure vlan shub id 200 egress-port lt:1/1/4
DLP 128-1
Edition 02 Released
DLP 128-2
Edition 02 Released
General
Before you can create an xDSL line, you need to create the necessary profiles.
Table DLP 129-1 describes the two types of profiles.
Table DLP 129-1: xDSL profiles
Profile
Description
Service Profile
Spectrum Profile
The parameters of the xDSL spectrum depend largely on the xDSL flavour (ADSL,
READSL, ADSL2(+), VDSL, or VDSL2). That is why the configuration of an xDSL
spectrum is done in two steps:
1
used profiles
noise margins
power management mode
Seamless Rate Adaptation (SRA) parameters
Configure the xDSL flavour specific parameters.
Refer to the System Description for more information on power management mode,
SRA,...
See the CLI Commands and Messages document and TNG 107 for a full description of
all related parameters.
DLP 129-1
Edition 02 Released
Procedure
Proceed as follows to create an xDSL profile:
1
DLP 129-2
Edition 02 Released
Create an xDSL spectrum profile and configure the parameters common to all the
DSL flavors with the following command:
configure xdsl spectrum-profile (index)
name <AsamProfileName>
local-profile
version <SignedInteger>
(no) dis-ansi-t1413
(no) dis-etsi-dts
(no) dis-g992-1-a
(no) dis-g992-1-b
(no) dis-g992-2-a
(no) dis-g992-3-a
(no) dis-g992-3-b
(no) g992-3-l1
(no) g992-3-l2
(no) g992-3-am
(no) g992-5-a
(no) g992-5-b
(no) ansi-t1.424
(no) dis-etsi-ts
(no) itu-g993-1
(no) ieee-802.3ah
(no) g992-5-am
(no) g993-2-8a
(no) g993-2-8b
(no) g993-2-8c
(no) g993-2-8d
(no) g993-2-12a
(no) g993-2-12b
(no) g993-2-17a
(no) g993-2-30a
(no) min-noise-down <Xdsl::NoiseMargin>
(no) min-noise-up <Xdsl::NoiseMargin>
(no) trgt-noise-down <Xdsl::NoiseMargin>
(no) trgt-noise-up <Xdsl::NoiseMargin>
(no) max-noise-down <Xdsl::NoiseMarginPlus>
(no) max-noise-up <Xdsl::NoiseMarginPlus>
(no) carrier-mask-down <Xdsl::CarrierMaskDown>
(no) carrier-mask-up <Xdsl::CarrierMaskUp>
(no) rf-band-list <Xdsl::RFBand>
(no) power_mgnt_mode <Xdsl::LinePowerMgtMode>
(no) l0-time <Xdsl::LineTime>
(no) l2-time <Xdsl::LineTime>
(no) l2-agpow-red-tx <Xdsl::L2Atpr>
(no) modification <Xdsl::ModifyStatus>
(no) rau-noise-down <Xdsl::NoiseMargin>
(no) rau-noise-up <Xdsl::NoiseMargin>
(no) rau-time-down <Xdsl::RaTime>
(no) rau-time-up <Xdsl::RaTime>
(no) rad-noise-down <Xdsl::NoiseMargin>
(no) rad-noise-up <Xdsl::NoiseMargin>
(no) rad-time-down <Xdsl::RaTime>
(no) rad-time-up <Xdsl::RaTime>
(no) l2-agpw-to-red-tx <Xdsl::LineL2Atpr>
DLP 129-3
Edition 02 Released
If the xDSL type is ADSL or ADSL2, then the ADSL and ADSL2 specific part of an
xDSL spectrum profile can be managed with the following command:
configure xdsl spectrum-profile (index) adsl-adsl2
(no) proprietary-feat
(no) max-agpowlev-down <Xdsl::PowerLevel>
(no) max-agpowlev-up <Xdsl::PowerLevel>
(no) max-psd-down <Xdsl::Adsl2PowerSpectralDensityDown>
(no) max-psd-up <Xdsl::Adsl2PowerSpectralDensityUp>
(no) pbo-mode-up
(no) max-recv-power-up <Xdsl::RxPowerLevel>
If the xDSL type is ADSL2+, then the ADSL2+ specific part of an xDSL spectrum
profile can be managed with the following command:
configure xdsl spectrum-profile (index) adsl2-plus
(no) proprietary-feat
(no) max-agpowlev-down <Xdsl::PowerLevel>
(no) max-agpowlev-up <Xdsl::PowerLevel>
(no) max-psd-down <Xdsl::Adsl2PlusPowerSpectralDensityDown>
(no) max-psd-up <Xdsl::Adsl2PlusPowerSpectralDensityUp>
(no) pbo-mode-up
(no) max-recv-power-up <Xdsl::RxPowerLevel>
(no) psd-shape-down <Xdsl::Adsl2PlusPsdShapeDown>
If the xDSL type is Reach Extended ADSL2 (READSL2), then the READSL2
specific part of an xDSL spectrum profile can be managed with the following
command:
configure xdsl spectrum-profile (index) re-adsl
(no) proprietary-feat
(no) max-agpowlev-down <Xdsl::PowerLevel>
(no) max-agpowlev-up <Xdsl::PowerLevel>
(no) max-psd-down <Xdsl::ReAdsl2PowerSpectralDensityDown>
(no) max-psd-up <Xdsl::ReAdsl2PowerSpectralDensityUp>
(no) pbo-mode-up
(no) max-recv-power-up <Xdsl::RxPowerLevel>
DLP 129-4
Edition 02 Released
If the xDSL type is VDSL, then the VDSL specific part of an xDSL spectrum profile
can be managed with the following command:
configure xdsl spectrum-profile (index) vdsl
(no) proprietary-feat
(no) vdsl-band-plan <Xdsl::VdslBandPlan>
(no) optional-band <Xdsl::OptionalBandUsage>
(no) optional-endfreq <Xdsl::OptionalBandEndFreq>
(no) adsl-band <Xdsl::AdslBandUsage>
(no) max-agpowlev-down <Xdsl::VdslPowerLevel>
(no) max-agpowlev-up <Xdsl::VdslPowerLevel>
(no) psd-shape-down <Xdsl::VdslPsdShapeDown>
(no) psd-shape-up <Xdsl::VdslPsdShapeUp>
(no) pbo-mode-down
(no) rx-psd-shape-up <Xdsl::RxVdslPsdShapeUp>
(no) ghstones-pwr-mode <Xdsl::GhsTonesTxPwr>
(no) max-band <Xdsl::VdslMaxBandNum>
(no) max-freq <Xdsl::VdslMaxFrequency>
(no) m-psd-level-down <Xdsl::MaxPsdDown>
(no) m-psd-level-up <Xdsl::MaxPsdUp>
(no) psd-pbo-par-a-up <Xdsl::ABParamType>
(no) psd-pbo-par-b-up <Xdsl::ABParamType>
(no) cust-psd-sc-down <Xdsl::PsdScaleBit>
(no) cust-psd-ty-down <Xdsl::PsdTypeBit>
(no) cust-rx-psd-sc-up <Xdsl::PsdScaleBit>
(no) cust-rx-psd-ty-up <Xdsl::PsdTypeBit>
Configure the transmission power of the G.hs tones in VDSL environment. with the
following command:
configure xdsl spectrum-profile (index) vdsl ghstone-set-pwr-ctrl
(no) a43 standard | auto | manual:<Xdsl::GhsTonesTxPwrLvl>
(no) b43 standard | auto | manual:<Xdsl::GhsTonesTxPwrLvl>
(no) a43c standard | auto | manual:<Xdsl::GhsTonesTxPwrLvl>
(no) v43 standard | auto | manual:<Xdsl::GhsTonesTxPwrLvl>
DLP 129-5
Edition 02 Released
If the xDSL type is VDSL2, then the VDSL2 specific part of an xDSL spectrum profile
can be managed with the following command:
configure xdsl spectrum-profile (index) vdsl2
(no) proprietary-feat
(no) max-agpowlev-down <Xdsl::VdslPowerLevel>
(no) max-agpowlev-up <Xdsl::VdslPowerLevel>
(no) psd-shape-down <Xdsl::Vdsl2PsdShapeDown>
cs-psd-shape-dn <Xdsl::Vdsl2CustPsdShape>
cs-psd-shape-up <Xdsl::Vdsl2CustPsdShape>
(no) psd-shape-up <Xdsl::Vdsl2PsdShapeUp>
(no) rx-psd-shape-up <Xdsl::RxVdslPsdShapeUp>
(no) psd-pbo-e-len-up <Xdsl::PsdPboElectrLength>
(no) m-psd-level-down <Xdsl::MaxPsdDown>
(no) m-psd-level-up <Xdsl::MaxPsdUp>
(no) psd-pbo-par-a-up <Xdsl::ABParamType>
(no) psd-pbo-par-b-up <Xdsl::ABParamType>
(no) v-noise-snr-down <Xdsl::SnrmMode>
(no) v-noise-snr-up <Xdsl::SnrmMode>
(no) v-noise-psd-down <Xdsl::VirtualNoisePsdDownType>
(no) v-noise-psd-up <Xdsl::VirtualNoisePsdUpType>
(no) cust-psd-sc-down <Xdsl::PsdScaleBit>
(no) cust-psd-ty-down <Xdsl::PsdTypeBit>
(no) cust-psd-sc-up <Xdsl::PsdScaleBit>
(no) cust-psd-ty-up <Xdsl::PsdTypeBit>
(no) cust-rx-psd-sc-up <Xdsl::PsdScaleBit>
(no) cust-rx-psd-ty-up <Xdsl::PsdTypeBit>
10
11
Configuration example:
configure xdsl service-profile 7 name ADSL_profile version 1
configure xdsl service-profile 7 active
DLP 129-6
Edition 02 Released
DLP 129-7
Edition 02 Released
DLP 129-8
Edition 02 Released
Prerequisites
The following prerequisites must be fulfilled before xDSL bonding can be configured:
DLP 130-1
Edition 02 Released
Procedure
Proceed as follows to create an xDSL bonding group profile:
1
Configure the xDSL lines to be bonded with bonding mode atm-bonding with the
following command:
configure xdsl line (if-index)
service-profile <AsamProfilePointer>
spectrum-profile <AsamProfilePointer>
(no) op-mode <Xdsl::OpModeTypeLinePreDef>
(no) carrier-data-mode <Xdsl::CarrierDataMode>
(no) admin-up
bonding-mode atm-bonding
Note 1 The following applies for these xDSL lines in case of chipset
level bonding:
The two lines used for xDSL bonding must be subsequent lines
The first line must be an odd line
Note 2 The following applies for the first line (also known as bonding
group index):
Note A bonding group profile can be created in one step (that is, with
all the necessary parameters and activation of the bonding group profile).
It can also be created in several steps by specifying a few parameters in
each step and by activating the bonding group profile in the last step.
3
DLP 130-2
Edition 02 Released
Configure the bonding group assembly timeout with the following command:
configure xdsl-bonding group-assembly-time <SignedInteger>
Configuration example:
configure xdsl-bonding group-assembly-time 0
configure xdsl-bonding group-profile 1 name XBOND_0_0
local-profile version 1
configure xdsl-bonding group-profile 1 min-bitrate-up 0
plan-bitrate-up 0 max-bitrate-up 0 max-delay-up 16
imp-noise-prot-up 0
configure xdsl-bonding group-profile 1 min-bitrate-down 0
plan-bitrate-down 0 max-bitrate-down 0 max-delay-down 16
imp-noise-prot-dn 0
configure xdsl-bonding group-profile 1 active
configure xdsl-bonding group-profile 2 name GroupProfile1
local-profile version 1
configure xdsl-bonding group-profile 2 min-bitrate-up 800
plan-bitrate-up 1500 max-bitrate-up 2200 max-delay-up 16
imp-noise-prot-up 0
configure xdsl-bonding group-profile 2 min-bitrate-down 10000
plan-bitrate-down 20000 max-bitrate-down 40000 max-delay-down 16
imp-noise-prot-dn 0
configure xdsl-bonding group-profile 2 active
configure xdsl line 1/1/8/47 service-profile name:XSRVC_0_0
spectrum-profile 5 bonding-mode atm-bonding admin-up
Alcatel 7302 ISAM R3.2 February 2007
Operations and Maintenance Using CLI 3HH-04065-AAAA-TQZZA
DLP 130-3
Edition 02 Released
DLP 130-4
Edition 02 Released
DLP 131-1
Edition 02 Released
DLP 131-2
Edition 02 Released
Procedure
Proceed as follows to configure filtering on the SHub:
1
Configure the SHub MAC filter to a port with the following command:
configure transport shub mac-filter (index-num)
(no) in-port (port)
DLP 132-1
Edition 02 Released
Configure the physical ports where the ICMP filter related to incoming traffic is to be
applied with the following command:
configure system shub filter ip-filter icmp (index-num)
(no) in-port (network-port)
Configure the physical ports where the ICMP filter related to outgoing traffic is to be
applied:
configure system shub filter ip-filter icmp (index-num)
(no) out-port (port)
Configure the physical ports where the TCP filter related to incoming traffic is to be
applied with the following command:
configure system shub filter ip-filter tcp (index-num)
(no) in-port (network-port)
Configure the physical ports where the TCP filter related to outgoing traffic is to be
applied:
configure system shub filter ip-filter tcp (index-num)
(no) out-port (network-port)
DLP 132-2
Edition 02 Released
10
Configure the physical ports where the UDP filter related to incoming traffic is to be
applied with the following command:
configure system shub filter ip-filter udp (index-num)
(no) in-port (network-port)
11
Configure the physical ports where the UDP filter related to outgoing traffic is to be
applied:
configure system shub filter ip-filter udp (index-num)
(no) out-port (port)
12
Configure an IP filter, for protocols other than ICMP, TCP or UDP, on the SHub with
the following command:
configure system shub filter ip-filter port-filter (filter-rule)
(no) protocol <Sys::RestrictedProtocol>
(no) action-drop
(no) dst-ip-addr <Ip::V4Address>/<Ip::PrefixLengthFull>
(no) src-ip-addr <Ip::V4Address>/<Ip::PrefixLengthFull>
(no) direction <Sys::Direction>
(no) vlan-id <Vlan::VlanFilterIndex>
13
Configure the physical ports where the IP filter related to incoming traffic is to be
applied with the following command:
configure system shub filter ip-filter port-filter (filter-rule)
(no) in-port (port)
14
Configure the physical ports where the IP filter related to outgoing traffic is to be
applied with the following command:
configure system shub filter ip-filter port-filter (filter-rule)
(no) out-port (port)
15
DLP 132-3
Edition 02 Released
Configuration example:
configure transport shub mac-filter 450 protocol-type 2222 filter
any-56:0d:9d:47:dd:aa vlan-id 100 action-drop
configure transport shub mac-filter 451 protocol-type 2222 filter
any-56:0d:9d:47:dd:bb vlan-id 100 action-drop
configure transport shub mac-filter [450...451] in-port lt:1/1/4
DLP 132-4
Edition 02 Released
Note For more information about QoS and the configuration of QoS,
refer to TNG 101.
Procedure
Proceed as follows to configure QoS on layer 2 level:
1
ii
Configure the upstream QoS DSL Control Packet Policer for incoming packets
with the following command:
configure qos dsl-ctrl-pkt-policer
(no) sustained-rate <Qos::SustainedRate>
(no) burst-size <Qos::DslCtrlBurstSize>
iii
If required, configure the downstream traffic class mapping table with the
following command:
configure qos tc-map-dot1p (index) queue <Qos::Queues>
DLP 133-1
Edition 02 Released
ii
iii
Configure a marker for a DSCP contract table with the following command:
configure qos profiles marker dscp-contract (name)
(no) alignment
iv
Configure a codepoint for a DSCP contract table with the following command:
configure qos profiles marker dscp-contract (name)
codepoint (codepoint)
(on) dscp-value <Qos::DscpToDot1PAlignmentDscpIndex>
Configure a marker for Dot1P and the DSCP contract table with the following
command:
configure qos profiles marker d1p-dscp-contract (name)
dot1p-value <Qos::ExtVlanSysPrio>
(no) alignment
vi
Configure a codepoint for Dot1P and the DSCP contract table with the
following command:
configure qos profiles marker d1p-dscp-contract (name)
codepoint (codepoint)
(no) dscp-value <Qos::DscpToDot1PAlignmentDscpIndex>
vii
Configure a marker for Dot1P and single DSCP with the following command:
configure qos profiles marker d1p-dscp (name)
default-dscp <Qos::DscpToDot1PAlignmentDscpIndex>
default-dot1p <Qos::ExtVlanSysPrio>
viii Configure a marker for Dot1P alignment with the following command:
configure qos profiles marker d1p-alignment (name)
(alignment) enable
DLP 133-2
Edition 02 Released
Configure a queue profile (that is, the used algorithm (tail-drop or Random Early
Detection (RED) and threshold(s)) with the following command:
configure qos profiles queue (name)
tail-drop:<Qos::MaxThreshold> |
red:<Qos::MinThreshold>:<Qos::MaxThreshold>:
<Qos::DiscardProbability>
Configure QoS policy actions, using the policer profiles created in step 2, with the
following command:
configure qos profiles policy-action (name)
(no) dscp-value <Qos::SetDscpValue>
(no) dot1p-value <Qos::SetDot1pValue>
(no) discard-packet
(no) shared-policer
(no) policer-profile <Policer Profile name>
DLP 133-3
Edition 02 Released
10
Configure the session profile table (using policer profiles created in step 1 and
marker profiles used in step 3) with the following command:
configure qos profiles session (name)
logical-flow-type <Qos::LogicalFlowType>
(no) up-policer none | name:<Policer Profile name>
(no) down-policer none | name:<Policer Profile name>
(no) up-marker none | name:<Marker Profile name>
ii
iii
11
Attach the created session profile to a bridge port with the following command:
configure bridge port <Rack/Shelf/Slot/Port:VCI:VPI>
(no) qos-profile <Session-profile>
12
Attach the created scheduler profile (see step 4) and CAC profile (see step 5) to a
DSL port with the following command:
configure qos dsl-port (index)
scheduler-profile <Qos::ProfileName>
cac-profile <Qos::ProfileName>
13
Attach the created queue profile (see step 6) to a DSL port with the following
command:
configure qos dsl-port (index) queue (queue)
queue-profile <Qos::QosProfileName>
14
DLP 133-4
Edition 02 Released
Configuration example:
configure qos atm-overhead-fact 87 eth-efm-fact 84
no enable-alignment
configure qos dsl-ctrl-pkt-policer sustained-rate 14 burst-size
11
DLP 133-5
Edition 02 Released
DLP 133-6
Edition 02 Released
Note For more information about QoS and the configuration of QoS,
refer to TNG 101.
Procedure
Proceed as follows to configure QoS on layer 3 level:
1
ii
Configure the upstream QoS DSL Control Packet Policer for incoming packets
with the following command:
configure qos dsl-ctrl-pkt-policer
(no) sustained-rate <Qos::SustainedRate>
(no) burst-size <Qos::DslCtrlBurstSize>
iii
If required, configure the DSCP to Dot1P Alignment Table for layer 3 forwarded
traffic with the following command:
configure qos dscp-map-dot1p (index)
dot1p-value <Qos::DscpToDot1PAlign>
DLP 134-1
Edition 02 Released
ii
iii
Configure a marker for a DSCP contract table with the following command:
configure qos profiles marker dscp-contract (name)
(no) alignment
iv
Configure a codepoint for a DSCP contract table with the following command:
configure qos profiles marker dscp-contract (name)
codepoint (codepoint)
(on) dscp-value <Qos::DscpToDot1PAlignmentDscpIndex>
Configure a marker for Dot1P and the DSCP contract table with the following
command:
configure qos profiles marker d1p-dscp-contract (name)
dot1p-value <Qos::ExtVlanSysPrio>
(no) alignment
vi
Configure a codepoint for Dot1P and the DSCP contract table with the
following command:
configure qos profiles marker d1p-dscp-contract (name)
codepoint (codepoint)
(no) dscp-value <Qos::DscpToDot1PAlignmentDscpIndex>
vii
Configure a marker for Dot1P and single DSCP with the following command:
configure qos profiles marker d1p-dscp (name)
default-dscp <Qos::DscpToDot1PAlignmentDscpIndex>
default-dot1p <Qos::ExtVlanSysPrio>
viii Configure a marker for Dot1P alignment with the following command:
configure qos profiles marker d1p-alignment (name)
(alignment) enable
DLP 134-2
Edition 02 Released
Configure a queue profile (that is, the used algorithm (tail-drop or Random Early
Detection (RED) and threshold(s)) with the following command:
configure qos profiles queue (name)
tail-drop:<Qos::MaxThreshold> |
red:<Qos::MinThreshold>:<Qos::MaxThreshold>:
<Qos::DiscardProbability>
Configure QoS policy actions, using the policer profiles created in step 2, with the
following command:
configure qos profiles policy-action (name)
(no) dscp-value <Qos::SetDscpValue>
(no) dot1p-value <Qos::SetDot1pValue>
(no) discard-packet
(no) shared-policer
(no) policer-profile <Policer Profile name>
DLP 134-3
Edition 02 Released
10
Configure the session profile table (using policer profiles created in step 1 and
marker profiles used in step 3) with the following command:
configure qos profiles session (name)
logical-flow-type <Qos::LogicalFlowType>
(no) up-policer none | name:<Policer Profile name>
(no) down-policer none | name:<Policer Profile name>
(no) up-marker none | name:<Marker Profile name>
ii
iii
11
Attach the created session profile to a bridge port with the following command:
configure bridge port <Rack/Shelf/Slot/Port:VCI:VPI>
(no) qos-profile <Session-profile>
12
Attach the created scheduler profile (see step 4) and CAC profile (see step 5) to a
DSL port with the following command:
configure qos dsl-port (index)
scheduler-profile <Qos::ProfileName>
cac-profile <Qos::ProfileName>
13
Attach the created queue profile (see step 6) to a DSL port with the following
command:
configure qos dsl-port (index) queue (queue)
queue-profile <Qos::QosProfileName>
14
Configuration example:
configure qos profiles policer ppUsSap256k
committed-info-rate 256 committed-burst-size 32000
configure qos profiles policer ppDsSap3M committed-info-rate 3000
committed-burst-size 96000
configure qos profiles policer ppVoice100k
committed-info-rate 100 committed-burst-size 3000
DLP 134-4
Edition 02 Released
DLP 134-5
Edition 02 Released
DLP 134-6
Edition 02 Released
Prerequisites
The following prerequisites must be fulfilled before a QoS-aware VLAN can be
configured:
DLP 135-1
Edition 02 Released
Procedure
Proceed as follows to configure a QoS-aware VLAN:
1
ii
Create and configure an SHub network port with the following command:
configure interface shub port (network-port)
(no) mode automatic | 10mbps:full | 10mbps:half | 100mbps:full
| 100mbps:half | 1gbps:full | 1gbps:half
port-type network
(no) mc-flooding
ii
Change the administrative status of the SHub network port with the following
command:
configure interface shub port (network-port) admin-status up
iii
Configure the SHub network egress port with the following command:
configure vlan shub id (vlanid) egress-port
network:<Shub::NetworkPort>
iv
Configure the SHub network egress port on the LT with the following
command:
configure vlan shub id (vlanid) egress-port
lt:<Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::LtSlot>
DLP 135-2
Edition 02 Released
Configuration example:
configure vlan id 350 name ISP_C_VLAN-350 mode qos-aware
configure vlan shub id 350 name ISP_C_VLAN-350
mode cross-connect
configure interface shub port 7 port-type network admin-status up
configure vlan shub id 350 egress-port network:7
configure vlan shub id 350 egress-port lt:1/1/5
configure xdsl line 1/1/5/4 service-profile 7 spectrum-profile 5
admin-up
configure atm pvc 1/1/5/4:8:35 aal5-encap-type llc-snap
configure atm pvc 1/1/5/4:8:36 aal5-encap-type llc-snap
configure bridge port 1/1/5/4:8:35
configure bridge port 1/1/5/4:8:35 vlan-id 350 prior-ctrl-load
prior-less-100ms prior-less-10ms prior-nw-ctrl
configure bridge port 1/1/5/4:8:36
configure bridge port 1/1/5/4:8:36 vlan-id 350 prior-best-effort
prior-background prior-spare prior-exc-effort
configure bridge port 1/1/5/4:8:35 pvid 350 default-priority 5
configure bridge port 1/1/5/4:8:36 pvid 350
prio-regen-prof cl-all-prio-3
DLP 135-3
Edition 02 Released
DLP 135-4
Edition 02 Released
Procedure
Proceed as follows to configure multicast on the LT:
1
DLP 136-1
Edition 02 Released
Configure the multicast source package members with the following command:
configure mcast src (class-d-addr)
(no) packagemember (package)
Configuration example:
configure mcast general package-member 50
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.10 eth-peak-bit-rate 5000
eth-sus-bit-rate 3000 vlan-id 100
configure mcast src 224.1.1.10 packagemember 50
DLP 136-2
Edition 02 Released
Procedure
Proceed as follows to configure proxy on the LT:
1
Configure the IGMP source channel parameters with the following command:
configure igmp channel (port)
(no) perm-pkg-bitmap <Igmp::PkgMemBitMap>
(no) max-num-group <Igmp::ChannelMaxNumGroup>
Configure the IGMP channel permission package members with the following
command:
configure igmp channel (port)
(no) fullview-packages (package)
Configure the IGMP channel preview package members with the following
command:
configure igmp channel (port)
(no) preview-packages (package)
DLP 137-1
Edition 02 Released
Configure the package bitmaps. The package is intended primarily for use by a
network element manager, such as AWS, to support multiple sets of packages in
different regions.
A package is a group of zero or more multicast sources that share a common access
permission. By grouping the source channels into one or more packages, it provides
flexibility for the service provider to deliver different levels of services to the
end-users, for example, Basic Package, Middle-Tier Package, and Premium
Package.
Use the following command:
configure igmp package (index)
(no) name <PrintableString-0-32>
(no) template-name <PrintableString-0-32>
template-version <Igmp::igmpPackageTemplateVersion>
Configuration example:
configure igmp channel 1/1/5/1:8:35 max-num-group 2
configure igmp channel 1/1/5/1:8:35 fullview-packages 20
configure igmp channel 1/1/5/1:8:35 preview-packages 49
configure igmp package 20 name IGMPpack20 template-version 1
configure igmp system src-ip-address 192.168.100.100 start
cdr-generation
DLP 137-2
Edition 02 Released
Procedure
Proceed as follows to configure IGMP snooping on the SHub:
1
Configure the SHub response timer for a VLAN with the following command:
configure igmp shub response-timer (vlan-id)
(no) leave-rsp-timer <Igmp::LeaveResponse>
View the status of the IGMP VLAN router ports with the following command:
show igmp shub vlan-router-port (vlan-id)
network-port <Shub::NetworkPort>
DLP 138-1
Edition 02 Released
Configure the VLAN filter to enable or disable IGMP snooping on that specific VLAN
with the following command:
configure igmp shub vlan-filter (filter-id)
(no) snoop-filter
Configure the IGMP Connection Admission Control (CAC) bundle with the following
command:
configure igmp shub bundle (bundle)
(no) bandwidth <Igmp::BundleBandWidth>
(no) max-num-channel <Igmp::BundleMaxChannel>
Configuration example:
configure igmp shub igs-system start-snooping
enable-snooping self-ip-addr-mode configure
self-ip-addr 192.168.100.100
configure igmp shub response-timer 500 leave-rsp-timer 3
configure igmp shub vlan-router-port 500 network-port 3
query-timer 120
show igmp shub vlan-router-port 500 network-port 3
configure igmp shub vlan-filter 4090 no snoop-filter
configure igmp shub bundle MyBundle bandwidth 5000
max-num-channel 10
DLP 138-2
Edition 02 Released
This procedure provides the steps to configure the DHCP relay agent in iBridge mode.
Prerequisite
The following prerequisite must be fulfilled before DHCP relay agent can be configured
on an iBridge VLAN:
The iBridge VLAN must have been created; see DLP 120.
DLP 139-1
Edition 02 Released
Procedure
Proceed as follows to configure the DHCP relay agent:
1
Add DHCP Option-82 to the iBridge VLAN with the following command:
configure vlan id (vlanid)
dhcp-opt-82
circuit-id-dhcp <Vlan::CircuitIdDhcp>
remote-id <Vlan::RemoteId>
Add an IP address to the iBridge VLAN, and add the VLAN to the VRF with the
following commands:
i
Change the administrative status of the iBridge VLAN to down with the
following command:
configure interface shub vlan-id (vlan-id)
admin-status down
ii
iii
iv
Change the administrative status of the iBridge VLAN to up with the following
command:
configure interface shub vlan-id (vlan-id)
admin-status up
Configure the list of DHCP relay server to a particular VRF with the following
command:
configure dhcp-relay shub server (index)
ip-addr <Ip::V4Address>
server-name <PrintableString-0-32>
DLP 139-2
Edition 02 Released
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>
Configuration example:
configure ip shub vrf 10 name ibridge-relay-vrf10 slow-path-mode
configure vlan id 100 dhcp-opt-82 circuit-id-dhcp physical-id
remote-id customer-id
configure interface shub vlan-id 100 admin-status down
configure interface shub ip 100 vrf-id 10
configure interface shub ip 100 ip-addr 192.168.100.2/24
configure interface shub vlan-id 100 admin-status up
configure dhcp-relay shub relaying
configure dhcp-relay shub server 10 ip-addr 192.168.100.13
server-name DHCPRel10
configure dhcp-relay shub agent 10 enable-relaying
agent-ip-addr 192.168.100.2
DLP 139-3
Edition 02 Released
DLP 139-4
Edition 02 Released
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:
DLP 140-1
Edition 02 Released
Procedure
Proceed as follows to configure the DHCP relay agent:
1
Configure the DHCP relay agent per VRF interface with the following command:
configure dhcp-relay agent (vrfid)
bcast-vlan <Dhcp::VlanId>
(no) option-82
(no) circuit-id <Dhcp::CircuitId>
(no) remote-id <Dhcp::RemoteId>
(no) dhcp-linerate <Dhcp::Dhcp-linerate>
Configure the list of DHCP Relay Server to a particular VRF with the following
command:
configure dhcp-relay shub server (index)
ip-addr <Ip::V4Address>
server-name <PrintableString-0-32>
Configure the DHCP relay agent parameters to a particular VRF with the following
command:
configure dhcp-relay shub agent (index)
(no) enable-relaying
(no) secs-threshold <Dhcp::SecsThreshold>
(no) hops-threshold <Dhcp::HopThreshold>
(no) context-lifetime <Dhcp::ContextLife>
agent-ip-addr <Ip::V4Address>
Configuration example:
configure dhcp-relay agent 5 bcast-vlan l2-vlan:4090
option-82 circuit-id physical-id remote-id customer-id
configure dhcp-relay shub relaying
configure dhcp-relay shub server 15 ip-addr 10.178.14.66
server-name Antwerp15
configure dhcp-relay shub agent 15 enable-relaying
agent-ip-addr 10.178.14.97
DLP 140-2
Edition 02 Released
This procedure provides the steps to configure the DHCP relay agent.
Procedure
Proceed as follows to configure the DHCP relay agent:
1
Add DHCP Option-82 to the forwarder VLAN on the LT with the following command:
configure dhcp-relay agent (vrfid)
bcast-vlan <Dhcp::VlanId>
(no) option-82
(no) circuit-id <Dhcp::CircuitId>
(no) remote-id <Dhcp::RemoteId>
DLP 141-1
Edition 02 Released
Add an IP address to the forwarder VLAN, and add the VLAN to the VRF with the
following commands:
i
Change the administrative status of the VLAN to down with the following
command:
configure interface shub vlan-id (vlan-id)
admin-status down
ii
iii
iv
Configure the list of DHCP relay servers to the VRF with the following command:
configure dhcp-relay shub server (vrfid)
ip-addr <Ip::V4Address>
server-name <PrintableString-0-32>
Configure the DHCP relay agent parameters to the VRF with the following
command:
configure dhcp-relay shub agent (vrfid)
(no) enable-relaying
(no) secs-threshold <Dhcp::SecsThreshold>
(no) hops-threshold <Dhcp::HopThreshold>
(no) context-lifetime <Dhcp::ContextLife>
agent-ip-addr <Ip::V4Address>
DLP 141-2
Edition 02 Released
Configuration example:
configure ip shub vrf 17 name forw-relay-vrf17 slow-path-mode
configure dhcp-relay agent 16 bcast-vlan l2-vlan:101
option-82 circuit-id physical-id remote-id customer-id
configure interface shub vlan-id 101 admin-status down
configure interface shub ip 101 vrf-id 17
configure interface shub ip 101 ip-addr 192.168.116.2/24
configure interface shub vlan-id 101 admin-status up
configure dhcp-relay shub relaying
configure dhcp-relay shub server 17 ip-addr 192.168.116.13
server-name Antwerp17
configure dhcp-relay shub agent 17 enable-relaying
agent-ip-addr 192.168.116.2
DLP 141-3
Edition 02 Released
DLP 141-4
Edition 02 Released
Procedure
Proceed as follows to configure the security domain:
1
DLP 142-1
Edition 02 Released
Configuration example:
configure system security domain Domain1 vrf-index 16 vlan-id 56
authenticator local
configure system security ip-addr-pool PoolDomain1 vrf-index 16
start-addr 10.179.16.100/24 size 100 no admin-down
configure system security domain Domain1 ip-pool PoolDomain1
vrf-index 16 priority 3
DLP 142-2
Edition 02 Released
Prerequisite
The following prerequisite must be fulfilled before local authentication can be configured:
Procedure
Proceed as follows to configure local authentication:
1
Change the password for a specific user with the following command:
configure system security domain (name) user (name) password
<new Password>
Delete a user from the authentication table with the following command:
configure system security domain (name) no user (name)
DLP 143-1
Edition 02 Released
Configuration example:
configure system security domain Domain1 vrf-index 16
authenticator local
configure system security domain Domain1 user JohnDoe
password zxspr12
configure system security domain Domain1 user JohnDoe
password acdd35d
configure system security domain Domain1 no user JohnDoe
DLP 143-2
Edition 02 Released
Procedure
Proceed as follows to configure RADIUS:
1
DLP 144-1
Edition 02 Released
Enable the RADIUS relay on the SHub with the following command:
configure system security radius
(no) relay
(no) auth-super-user <Aaa::SuperUserAuth>
oper-policy-name <Aaa::OperatorRadPolicyName>
Configure the RADIUS Dynamic Authorization Clients with the following command:
configure system security radius dyn-auth-client (name) vrf-index
<Aaa::VrfIndex>
ip-address <Ip::V4Address>
secret <Password>
(no) admin-down
DLP 144-2
Edition 02 Released
Configuration example:
configure ip vrf 1 name Dummy
configure system security radius auth-server RADAuthServ1
vrf-index 0 ip-address 10.176.5.5 secret Khinghkhongh
timeout-limit 5
configure system security radius acc-server RADAccServ1 vrf-index
0 ip-address 10.176.5.55 secret Ahlakazam
configure system security radius policy RADPol23 nas-id MyNASID
nas-ip-address 192.168.122.122
configure system security radius policy RADPol23 servers 2
auth-server name:RADAuthServ1 vrf-index-auth 0 acc-server
name:RADAccServ1 vrf-index-acc 0 priority 162
configure system security domain SecDomain1 vrf-index 1
authenticator radius:RADPol23
configure system security radius dyn-auth-client DynAuth1
vrf-index 0 ip-address 10.176.5.5 secret Khinghkhongh
DLP 144-3
Edition 02 Released
DLP 144-4
Edition 02 Released
Procedure
Proceed as follows to configure 802.1x:
1
Configure the remote authenticator and enable authentication and handshake with
the following command:
configure system security pae ext-authenticator (port)
(no) authentication
(no) init-authreq-off
(no) handshake
(no) handshake-period <Aaa::PortHandShakePeriod>
DLP 145-1
Edition 02 Released
Configuration example:
configure system security pae port-access
configure system security pae authenticator 1/1/5/1:8:35
controlled-port force-unauthorized server-timeout 20 max-req 5
configure system security pae ext-authenticator 1/1/5/1:8:35
authentication handshake
configure system security pae port 1/1/5/1:8:35 initialize
DLP 145-2
Edition 02 Released
true:
if pppoe-relay-tag is set to true, then the values of circuit-id-pppoe and of
remote-id-pppoe are irrelevant.
The NE adds the vendor-specific tag and always puts the customer-id parameter into
the remote-id suboption, and will always generate a string (access node, rack,...) to
put in the circuit-id suboption.
false (default):
if pppoe-relay-tag is false, then the values of circuit-id-pppoe and of remote-id-pppoe
are irrelevant.
The NE does not add the vendor-specific tag.
configurable:
if pppoe-relay-tag is set to configurable, then the values of circuit-id-pppoe and of
remote-id-pppoe are relevant and subject to the same rules as for DHCP.
The NE adds the vendor specific tag according the settings of these suboptions. The
DHCP-like rules that apply are that the values of both suboptions cannot be identical
(2 x customer-id would result in adding the same configurable string in both
suboptions, 2 x notAdd would result in a vendor-specific tag with without suboptions).
DLP 146-1
Edition 02 Released
In both cases where a string is to be generated (that is, the case where pppoerelaytag is
configurable and circuit-id-pppoe is set to physcial-id; and the case where pppoerelaytag
is set to true), the string format is identified by:
Prerequisite
The following prerequisite must be fulfilled before PPPoE can be enabled on a VLAN:
A VLAN must have been created; see DLP 117, DLP 118, DLP 119 or DLP 120.
Procedure
Proceed as follows to enable or disable PPPoE relay:
1
Enable PPPoE relay and, if required, configure the vendor-specific tag with the
following command:
configure vlan id (vlanid)
(no) pppoe-relay-tag <Vlan::PppoeRelayEnableR3.1>
(no) pppoe-linerate <Vlan::Pppoe-linerate>
(no) circuit-id-pppoe <Vlan::CircuitIdPppoe>
(no) remote-id-pppoe <Vlan::RemoteIdPppoe>
Configuration example:
configure vlan id 560 mode residential-bridge name PPPoXVlan560
configure vlan id 560 pppoe-relay-tag configurable
circuit-id-pppoe physical-id remote-id-pppoe customer-id
pppoe-linerate addactuallinerate
configure vlan id 560 no pppoe-relay-tag
DLP 146-2
Edition 02 Released
Prerequisites
The following prerequisites must be fulfilled before PPPoX relay can be configured:
Procedure
Proceed as follows to configure PPPoX relay:
1
DLP 147-1
Edition 02 Released
Enable monitoring of the PPPoX CC client port with the following command:
configure pppox-relay cross-connect client-port (port) monitor
Configuration example:
configure pppox-relay cross-connect global-session
trans-max-age 250 cc-max-age 600
configure pppox-relay cross-connect engine 560 name PPPoXRelay560
configure pppox-relay cross-connect engine 560 monitor
configure pppox-relay cross-connect engine 560 max-payload-tag
insert
configure xdsl line 1/1/5/10 service-profile 7 spectrum-profile 5
admin-up
configure interface port xdsl-line:1/1/5/10 user Line1152:8.35
configure atm pvc 1/1/5/10:8:35 no admin-down
aal5-encap-type automatic:ppp
configure pppox-relay cross-connect client-port 1/1/5/10:8:35
vlan-id 560 default-priority 4
DLP 147-2
Edition 02 Released
Procedure
Proceed as follows to configure the PPPoE server:
1
Configuration example:
configure pppoe server-name PPPoEServer1 enable-server
DLP 148-1
Edition 02 Released
DLP 148-2
Edition 02 Released
Procedure
Proceed as follows to configure the PPPoE profiles:
1
Configuration example:
configure pppoe ppp-profile PPPProf1 auth-type chap-pap
DLP 149-1
Edition 02 Released
DLP 149-2
Edition 02 Released
Prerequisite
The following prerequisite must be fulfilled before an ARP table entry can be configured:
A VLAN must have been created; see DLP 117, DLP 118, DLP 119 or DLP 120.
Procedure
Use the following procedure to configure an ARP table entry:
1
Configure the IP Shub ARP parameters per VLAN with the following command:
configure ip shub arp vlan (vlanid)
(no) gratuitous-arp
DLP 150-1
Edition 02 Released
Configuration example:
configure ip shub arp cache-timeout 10000 cache-pending 35
max-retries 5
configure ip shub arp vlan 4093 gratuitous-arp
DLP 150-2
Edition 02 Released
Procedure
Proceed as follows to restart the SHub:
1
Configuration example:
admin equipment prepare-sys-shutdown
DLP 151-1
Edition 02 Released
DLP 151-2
Edition 02 Released
Procedure
Proceed as follows to reboot the system:
1
Configuration example:
admin equipment reboot-isam with-self-test
DLP 152-1
Edition 02 Released
DLP 152-2
Edition 02 Released
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
DLP 153-1
Edition 02 Released
Configuration example:
configure equipment slot 1/1/5 power-down
sleep 60
configure equipment slot 1/1/5 no power-down
DLP 153-2
Edition 02 Released
General
In the NE, a lot of different alarms may occur. This can sometimes make it difficult for an
operator to investigate, since alarms can appear, disappear, and so on.
Therefore, the snapshot principle exists. A snapshot is in fact a picture of all the alarms
that are present on the moment the snapshot is taken.
A table is created which contains a copy of the alarms which are present in the system at
the time the snapshot was taken.
The operator can filter this table by specifying a minimum alarm level. Only alarms with
a level equal or higher than the specified level, will be present in the table.
This table is only temporary and exist only for 4 minutes. After the 4 minutes, the table is
cleared automatically (the alarms are not displayed anymore), and a new snapshot can
be taken.
The operator can also clear the table manually if he wants to take a new snapshot
immediately (that is, not wait for the 4 minute timer to expire).
DLP 154-1
Edition 02 Released
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)
Note The command will fail if the snap-shot is already in use. The
snap-shot is only kept for a limited time and will be automatically cleared.
The alarm snapshot table can be viewed with the following command:
show alarm snap-shot table | equipment | eqpt-holder |
plug-in-unit | atm | ether-itf | sw-mgmt | xdsl | tca-xdsl |
eo-conversion | authentication | bonding-group | ipox | redundancy
| custom | sfp | llu-relay | custom-ext-alarm | plug-in-unit-ext
(index)
Create an alarm snapshot table on the SHub with the following command:
admin alarm shub snap-shot (start)
The SHub alarm snapshot table can be viewed with the following command:
show alarm shub snap-shot table (index)
The alarm snapshot table can be cleared with the following command:
admin alarm snap-shot stop
Note The alarms are not shown anymore and a new snapshot can
now be taken, if required.
DLP 154-2
Edition 02 Released
The alarm snapshot table on the SHub can be cleared with the following command:
admin alarm shub snap-shot stop
Note The alarms are not shown anymore and a new snapshot can
now be taken, if required.
Configuration example:
The following command creates an alarm snapshot table for snap-shot owner tom
showing all the alarms with severity-level major and higher.
admin alarm snap-shot start:major:tom
The following command displays more information for the alarm type equipment.
show alarm snap-shot equipment
The following command creates an alarm snapshot table on the SHub for snap-shot
owner tomtom showing all the alarms with severity-level indeterminate and
higher.
admin alarm shub snap-shot start:indeterminate:tomtom
The following command displays the complete alarm table for the SHub.
show alarm shub snap-shot table
The following command displays more information for the alarm type eth-shub on
the SHub.
show alarm shub snap-shot eth-shub
The following command clears the alarm snap shot on the SHub.
admin alarm shub snap-shot stop
DLP 154-3
Edition 02 Released
DLP 154-4
Edition 02 Released
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
View the general alarm log table with the following command:
show alarm log table
ii
Use the following command to view the common values related to the alarm delta
logs:
show alarm delta-log alarm-changes
DLP 155-1
Edition 02 Released
To view values related to the alarm delta log entries, use any of the following
commands:
a
To display common values related to the delta log alarm, use the following
command:
show alarm delta-log alarm-changes
To display indeterminate values related to the delta log alarm, use the following
command:
show alarm delta-log indeterminate (index)
To display warning values related to the delta log alarm, use the following
command:
show alarm delta-log warning (index)
To display minor values related to the delta log alarm, use the following
command:
show alarm delta-log minor (index)
To display major values related to the delta log alarm, use the following
command:
show alarm delta-log major (index)
To display critical values related to the delta log alarm, use the following
command:
show alarm delta-log critical (index)
DLP 155-2
Edition 02 Released
Configuration example:
show alarm log table
show alarm log equipment 1
show alarm log xdsl misc
show alarm delta-log alarm-changes
show alarm current table
show alarm delta-log alarm-changes
show alarm delta-log indeterminate
show alarm delta-log warning
show alarm delta-log minor
show alarm delta-log major
show alarm delta-log critical
DLP 155-3
Edition 02 Released
DLP 155-4
Edition 02 Released
DLP 156-1
Edition 02 Released
DLP 156-2
Edition 02 Released
The SHub database can be saved manually with the following command:
admin software-mngt shub database save
Procedure
Proceed as follows to manage the SHub database:
1
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 157-1
Edition 02 Released
Configuration example:
show software-mngt shub config-file
show system shub entry status
DLP 157-2
Edition 02 Released
DLP 158-1
Edition 02 Released
DLP 158-2
Edition 02 Released
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
DLP 159-1
Edition 02 Released
Configuration example:
configure software-mngt oswp 2
primary-file-server-id 192.168.111.112
second-file-server-id 192.168.111.212
admin software-mngt oswp 2 download OSWP_packages/OSWP1
admin software-mngt oswp 2 activate with-linked-db
admin software-mngt oswp 2 commit
DLP 159-2
Edition 02 Released
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
Configuration example:
show system shub entry version
DLP 160-1
Edition 02 Released
DLP 160-2
Edition 02 Released
Features
The feature counters can be retrieved by a manager for monitoring. The following
features are monitored in the NE:
ADSL2+
READSL2
ADSL2/ADSL2+ Annex M
IGMP
IP-Forwarding
PPPoX Relay
PPPoX Termination
802.1x
IPoA-CC
Procedure
Proceed as follows to retrieve the feature counters:
1
View the number of software licenses for the feature with the following command:
show system license adsl2-plus | readsl2 | igmp | ip-forward |
pppox-relay | pppox-termination | 802dot1x | annex-m | ipoa-cc
DLP 161-1
Edition 02 Released
Configuration example:
show system license
DLP 161-2
Edition 02 Released
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
ii
View the external VLAN in the SHub with the following command:
info configure system shub entry vlan
iii
View the PVID on the management port with the following command:
info configure bridge shub port 1
Change the external VLAN in the system with the following command:
configure system id <Sys::systemId>
name <PrintableString-0-255>
location <PrintableString-0-255>
contact-person <PrintableString-0-255>
(no) en-snmp-auth-traps <Transport::SnmpAuthTraps>
(no) ether-shape-rate <Sys::etherShapeRate>
mgnt-vlan-id <Vlan::VlanOamIndex>
system-mac <Sys::MacAddr>/<Sys::MacAddr>/<Sys::Number>
(no) single-public-ip
(no) port-num-inpro <Sys::PortNumberInprotocol>
DLP 162-1
Edition 02 Released
Change the external VLAN in the SHub with the following command:
configure system shub entry vlan ext-vlan-id <Vlan::ExtVlanIndex>
Configure the network port as egress port with the following command:
configure vlan shub id (vlanid)
egress-port network:<Shub::NetworkPort>
Configure the untag port and the PVID with the following commands:
configure vlan shub id (vlanid)
untag-port network:<Shub::NetworkPort>
ii
Change the PVID on the management port with the following command:
configure bridge shub port (network-port)
pvid <Vlan::VlanOamIndex>
Configuration example:
info configure system
info configure system shub entry vlan
info configure bridge shub port 7
configure system mgnt-vlan-id 72
configure system shub entry vlan ext-vlan-id 72
configure vlan shub id 72 egress-port network:7
configure bridge shub port 7 pvid 72
admin software-mngt shub database save
DLP 162-2
Edition 02 Released
Prerequisite
The following prerequisite must be fullfilled before an xDSL spectrum profile can be
modified:
The xDSL spectrum profile must have been created; see DLP 129.
Procedure
Proceed as follows to modify an xDSL spectrum profile:
1
Start the modification of an xDSL spectrum profile with the following command:
configure xdsl spectrum-profile (index) modification start
Modify the parameters of an xDSL spectrum profile with the following command:
configure xdsl spectrum-profile (index)
name <AsamProfileName>
local-profile
version <SignedInteger>
(no) dis-ansi-t1413
(no) dis-etsi-dts
DLP 163-1
Edition 02 Released
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
(no)
dis-g992-1-a
dis-g992-1-b
dis-g992-2-a
dis-g992-3-a
dis-g992-3-b
g992-3-l1
g992-3-l2
g992-3-am
g992-5-a
g992-5-b
ansi-t1.424
dis-etsi-ts
itu-g993-1
ieee-802.3ah
g992-5-am
g993-2-8a
g993-2-8b
g993-2-8c
g993-2-8d
g993-2-12a
g993-2-12b
g993-2-17a
g993-2-30a
min-noise-down <Xdsl::NoiseMargin>
min-noise-up <Xdsl::NoiseMargin>
trgt-noise-down <Xdsl::NoiseMargin>
trgt-noise-up <Xdsl::NoiseMargin>
max-noise-down <Xdsl::NoiseMarginPlus>
max-noise-up <Xdsl::NoiseMarginPlus>
carrier-mask-down <Xdsl::CarrierMaskDown>
carrier-mask-up <Xdsl::CarrierMaskUp>
rf-band-list <Xdsl::RFBand>
power_mgnt_mode <Xdsl::LinePowerMgtMode>
l0-time <Xdsl::LineL0Time>
l2-time <Xdsl::LineL2Time>
l2-agpow-red-tx<Xdsl::LineL2Atpr>
rau-noise-down <Xdsl::NoiseMargin>
rau-noise-up <Xdsl::NoiseMargin>
rau-time-down <Xdsl::RaTime>
rau-time-up <Xdsl::RaTime>
rad-noise-down <Xdsl::NoiseMargin>
rad-noise-up <Xdsl::NoiseMargin>
rad-time-down <Xdsl::RaTime>
rad-time-up <Xdsl::RaTime>
l2-agpw-to-red-tx <Xdsl::LineL2Atpr>
Use one of the following commands to complete the modification of the xDSL
spectrum profile:
a
DLP 163-2
Edition 02 Released
Configuration example:
configure xdsl spectrum-profile 22 modification start
configure xdsl spectrum-profile 22 name test_profile
configure xdsl spectrum-profile 22 modification complete
DLP 163-3
Edition 02 Released
DLP 163-4
Edition 02 Released
Procedure
Proceed as follows:
1
(ip-addr)
timeout <Ip::PingTimeout>
tries <Ip::PingTries>
mtu-size <Ip::PingMtu>
Configuration example:
ping 10.176.5.5 tries 3
DLP 164-1
Edition 02 Released
DLP 164-2
Edition 02 Released
Procedure
Proceed as follows to perform a traceroute action:
1
DLP 165-1
Edition 02 Released
Configuration example:
traceroute 10.176.5.5 first-hop 2 last-hop 4 mtu-size 30
DLP 165-2
Edition 02 Released
Procedure
Proceed as follows:
1
Configure the CPE remote management function with the following command:
configure cpe-management proxy-mode snmp
DLP 166-1
Edition 02 Released
Configure on the SHub the VLAN that will be used to transport IP packets for a CPE
management session inside the system with the following command:
configure cpe-management shub vlan-id (vlan-id)
View the global statistics and the statistics per CPE managerwith the following
command:
show cpe-management snmpproxy-statistics
Configuration example:
configure cpe-management proxy-mode snmp vlan-id 400
configure cpe-management manager 192.168.200.200:2000
configure cpe-management shub vlan-id 400
DLP 166-2
Edition 02 Released
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>
Configuration example:
info configure | tee config
info configure alarm flat | tee alaflat.cli
exec /var/cmd/alaflat.cli
DLP 167-1
Edition 02 Released
DLP 167-2
Edition 02 Released
Procedure
Proceed as follows to modify the system management IP parameters:
1
If a default route was defined at the time of creation (see DLP 102 or DLP 175),
remove the default route with the following command:
configure system management no default-route
Configure the new host IP address of the system with the following command:
configure system management host-ip-address
manual:<Ip::V4Address>/<Ip::PrefixLengthHost>
Configure the new default route of the system with the following command:
configure system management default-route <Ip::V4Address>
DLP 168-1
Edition 02 Released
Change the administrative status of the management vlan on the SHub to down
with the following command:
configure interface shub vlan-id <Vlan::UVlanIndex>
admin-status down
Optionally, remove the IP address connected to the management vlan on the SHub
via the following command:
configure interface shub ip <Vlan::UVlanIndex>
no ip-addr <Ip::V4Address>/<Ip::PrefixLengthHost>
Configure the new IP address to the management vlan on the SHub via the following
command:
configure interface shub ip <Vlan::UVlanIndex>
ip-addr <Ip::V4Address>/<Ip::PrefixLengthHost>
Change the administrative status of the management vlan on the SHub to up with
the following command:
configure interface shub vlan-id <Vlan::UVlanIndex>
admin-status up
10
Configure the default route in the SHub with the following command:
configure ip shub vrf 0 route-dest 0.0.0.0/0
next-hop <gateway-ip-address>
vlan-id 4093
11
12
To make the changes effective, the SHub must be restarted with the following
command:
admin equipment reboot-shub systemreset
13
Configuration example:
1. Configuration example for a single IP address system:
configure system management no default-route
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.254
DLP 168-2
Edition 02 Released
DLP 168-3
Edition 02 Released
DLP 168-4
Edition 02 Released
DLP 169-1
Edition 02 Released
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).
Procedure
Proceed as follows to configure cluster management:
1
Configure the role of the NE and cluster name with the following command:
configure cluster system name <Cluster::clusterName>
role <Cluster::ClusterRole>
Note Use this command for each NE that must be part of the cluster.
Configure the neighbour discovery on system level with the following command:
configure cluster neighbour
(no) discov-mode-off <Cluster::DiscoverySystemMode>
(no) interval <Cluster::DiscoveryInterval>
(no) hold-time <Cluster::DiscoveryHoldTime>
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>
DLP 169-2
Edition 02 Released
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
Configuration example:
configure cluster system name cluster1 role command
configure cluster neighbour no discov-mode-off interval 60
hold-time 180
configure cluster collection interval 3000
configure cluster port 7 discov-port-off
DLP 169-3
Edition 02 Released
DLP 169-4
Edition 02 Released
General
When configuring SSH, the following must be taken into consideration:
DLP 170-1
Edition 02 Released
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
Configure the SSH user and the public key, to be used while connecting, with the
following command:
configure system security ssh user (name)
key <SSH::SshClientPublicKey>
Configure the access channels (for example, disable the non-secure channels) with
the following command:
configure system security ssh access
(no) ftp <SSH::ChannelFTP>
(no) cli <SSH::ChannelCLISSH>
(no) tl1 <SSH::ChannelTL1SSH>
DLP 170-2
Edition 02 Released
Configure an SFTP user name and password for when the NE has to connect to an
external SFTP server with the following command:
configure system security ssh sftp-user (username)
password prompt | plain:<SSH::SftpPassword>
Note The SFTP user created with the command above, is unique in
the system. In case of a second attempt to create such an SFTP user, the
first one will be overwritten.
6
Configuration example:
configure system security ssh server-profile server-retries 3
idle-timeout 1800 no dis-hmac-sha-1 no dis-hmac-sha-1-96
no dis-aes no dis-des-3 no dis-blowfish no dis-des-56
configure system security ssh user SSH01
configure system security ssh user SSH02
key AAAAB3NzaC1yc2EAAAABJQAAAIEAnDR5OYM3lhz3tYC3wGQhumJhrum9pyGJ
3Ic0WGW0nJ7SW5CkMm7WfDUXujqwY09I2vZ2s1fMtpPHr/yrSAQ29qnLvmnhAeMd
can1YoVMgp0TAEjWKdKonn9SlGH9oPe6FFRb+1eJoPNNH3CGpGk03mqROeM0KQWo
U/nRlcYFa9c=
configure system security ssh access cli telnet-ssh
configure system security ssh sftp-user JohnDoe password
plain:sshpsw01
DLP 170-3
Edition 02 Released
DLP 170-4
Edition 02 Released
Procedure
Proceed as follows to enable the management of EMS:
1
Configure the SNMP community name public with the following command:
configure system security snmp community public
host-address <Ip::V4Address>/<Ip::PrefixLengthFull>
Configure the SNMP community name NETMAN with the following command:
configure system security snmp community NETMAN
host-address <Ip::V4Address>/<Ip::PrefixLengthFull>
context shub
Go to step 8.
Configure the SNMP community name public with the following command:
configure system security snmp community public
host-address <Ip::V4Address>/<Ip::PrefixLengthFull>
DLP 171-1
Edition 02 Released
Configure the SHub management VLAN filter IP address with the following
command:
configure system shub filter shub-manager (index)
src-ip-addr <Ip::V4Address>
where <Ip::V4Address> is the IP address of the EMS
Configure the SHub security SNMP community with the following command:
configure system security snmp shub community (index)
name <name>
privilege read-write
no ip-addr
Configuration example:
Configuration example for single IP address mode
configure system security snmp community public
host-address 10.176.0.0/15
configure system security snmp community NETMAN
host-address 10.176.0.0/15 context shub
DLP 171-2
Edition 02 Released
Procedure
Proceed as follows to create a default operator profile:
1
DLP 172-1
Edition 02 Released
Configuration example:
configure system security default-profile no prompt
password-timeout 10 terminal-timeout 30 description defaultprof
aaa read atm read alarm write no dhcp equipment write no igmp
ip write pppoe write qos write software-mngt write transport write
vlan write xdsl write security write
DLP 172-2
Edition 02 Released
Procedure
Proceed as follows to switch a user from ADSL service to VDSL (1 or 2) service:
1
At the creation of the service and spectrum profiles, fill in the correct values both for
the ADSL and VDSL profiles; see DLP 129.
Enable the modification by changing the value of the parameter transfer-mode from
atm to ptm with the following command:
configure xdsl line (if-index)
service-profile none | <Xdsl::ProfilePointer>
| name: <PrintableString>
spectrum-profile none | <Xdsl::ProfilePointer>
| name:<PrintableString>
transfer-mode ptm admin-up
Note The existing interfaces on top of the xDSL line (such as pvc,
bridge port and so on) will be automatically removed.
DLP 173-1
Edition 02 Released
Create the new forwarding model. Refer to DLP 115 to DLP 127 for the correct
procedure for the different modes.
Configuration example:
configure xdsl line 1/1/4/1 service-profile 7 spectrum-profile 5
transfer-mode ptm admin-up
DLP 173-2
Edition 02 Released
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:
1
DLP 174-1
Edition 02 Released
DLP 174-2
Edition 02 Released
10
Configuration example:
configure vlan id 2200 name ISP_C_VLAN mode cross-connect
configure vlan shub id 2200 name ISP_C_VLAN mode cross-connect
configure xdsl line 1/1/5/7 service-profile 7 spectrum-profile 5
admin-up
configure interface port xdsl-line:1/1/5/7
user IPoA cross-connect
configure atm pvc 1/1/5/7:8:35 no admin-down
aal5-encap-type llc-snap-routed
configure atm ip-cross-connect 1/1/5/7:8:35 next-hop
192.168.150.1 cpe 192.168.150.2
configure bridge port 1/1/5/7:8:35 mac-learn-off
configure bridge port 1/1/5/7:8:35 vlan-id 2200
configure bridge port 1/1/5/7:8:35 pvid 2200
DLP 174-3
Edition 02 Released
DLP 174-4
Edition 02 Released
Prerequisites
Communities must be configured on the SHub. The following commands give an
example:
Procedure
Proceed as follows to configure the system management IP parameters:
1
Configure the system to use a single IP address with the following command:
configure system id <Sys::systemId>
single-public-ip
DLP 175-1
Edition 02 Released
Configure the default route of the system with the following command:
configure system management default-route (default-route)
Configure the network port management (inband or outband) with the following
command:
configure interface shub port (network-port)
(no) mode automatic | 10mbps:full | 10mbps:half | 100mbps:full
| 100mbps:half | 1gbps:full | 1gbps:half
(no) port-type <Sys::Type>
(no) admin-status <Shub::AdminStatus>
(no) mc-flooding
where port-type can be:
user: port to a directly connected user
subtending: port to a subtended ISAM
network: port to the service provider (ISP)
unused: port is not in use
outband-mngt: port is used for outband-management
Select network for inband management or outband-mngt for outband management
Inband or outband management can be checked with the following commands (output of the
commands is an example):
DLP 175-2
Edition 02 Released
up
up
one-gb
outband
full
up
down
one-gb
user
full
up
down
one-gb
subtending
full
up
down
one-gb
network
full
up
up
hundred-mbps
network
full
up
up
hundred-mbps
network
half
----------------------------------------------------------------
Specify the set of ports which are statically allocated as egress ports for the SHub
management VLAN with the following command:
configure vlan shub id 4093 egress-port (port)
Specify the egress ports which should transmit packets for the SHub management
VLAN as untagged with the following command:
configure vlan shub id 4093 untag-port (network-port)
DLP 175-3
Edition 02 Released
Configuration example:
Configuration example for dynamic configuration via BOOTP (for tagged network):
configure system id SystemID01 single-public-ip
configure system management host-ip-address bootp
show transport ip-address
configure system management no default-route
configure interface shub port 7 port-type network
show vlan global
show interface shub port
configure vlan shub id 4093 egress-port network:7
configure bridge shub port 7 pvid 4093
Configuration example for static configuration via manual configuration (for tagged
network):
configure system id SystemID02 single-public-ip
configure system management host-ip-address
manual:10.177.0.112/17
show transport ip-address
configure system management default-route 10.177.127.254
configure interface shub port 7 port-type network
show vlan global
show interface shub port
configure vlan shub id 4093 egress-port network:7
configure bridge shub port 7 pvid 4093
DLP 175-4
Edition 02 Released
Procedure
The following steps can be used for performance monitoring:
1
DLP 176-1
Edition 02 Released
10
11
Use the following command to show the IP SHub ARP Statistics per VRF forwarding
statistics:
show ip shub arp (vrf-id)
DLP 176-2
Edition 02 Released
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)
13
14
15
16
Use the following command to show the statistics related to the SNMP protocol:
show transport snmp protocol-stats
17
18
19
DLP 176-3
Edition 02 Released
20
DLP 176-4
Edition 02 Released
21
Use the following command to show the statistics related to CPE management:
show cpe-management snmpproxy-statistics (address)
show cpe-management ipproxy-statistics (dslport)
22
Configuration example:
show xdsl counters near-end line current-interval
show xdsl counters far-end line current-interval
show xdsl counters near-end line current-1day
show xdsl counters far-end line current-1day
show xdsl counters near-end line previous-interval
show xdsl counters far-end line previous-interval
show xdsl counters near-end line previous-1day
show xdsl counters far-end line previous-1day
show atm tc-current-int one-day
show atm tc-current-int fifteen-min
show interface port bridge-port:1/1/4/1
show la aggregator-info
show la aggregate-list
show la network-port-info
show rstp port-info
show bridge network-port
show pppoe statistics-pppoe-itf tx-pkt
show pppoe statistics-pppoe-itf rx-pkt
show pppoe statistics-pppoe-itf stats
show pppoe ppp-statistics
show qos statistics buffer-overflow total 1/1/4
show igmp channel counter
show ip vrf-statistics
show ip shub arp
show dhcp-relay port
DLP 176-5
Edition 02 Released
DLP 176-6
Edition 02 Released
DLP 176-7
Edition 02 Released
DLP 176-8
Edition 02 Released
General
Downlink SFP ports on a GENC-E or GENC-F card installed in a host shelf are
configurable using CLI. You can set the rack, shelf, and slot ID for each downlink port.
For the 7330 ISAM FTTN ES, the SFP port settings must match the shelf jumper settings
of the connected ES and the slot number must match the number of the LT slot in which
the connected remote LT unit is installed. The 7330 ISAM FTTN SEM derives its rack and
shelf IDs from the SFP port.
Figure DLP 177-1 shows the downlink port assignments on the faceplate of the GENC-E
card. The port assignments for the GENC-F card are identical.
Figure DLP 177-1: GENC-E card faceplate port assignments
11
13
15
17
14
16
ACU
12
17
16
10
15
14
Down links
9 11 13 15 17
8 10 12 14 16
Port
13
12
Tx
11
9
8
10
7
6
Tx
Rx
5
4
Up links
5
4
Rx
Configuration up or down
7
6
LEDs
DLP 177-1
Edition 02 Released
Each SFP port must have a unique rack, shelf, and slot ID. The host shelf is always
assigned to rack 1, shelf 1 in an expansion configuration. As such, the rack, shelf, and
slot combination used for SFP ports cannot be on the host shelf; for example, do not
assign rack 1, shelf 1, slot 1 to an SFP port.
The following conditions apply specifically to the SEM:
if you connect a SEM directly to downlink ports 8, 9, or 10, the SEM is automatically
assigned rack 3, shelf 1, 2, or 3 respectively without requiring configuration; however,
you are still required to configure the slot number for the SFP port
to use any downlink port other than ports 8, 9, and 10, you must configure a rack,
shelf, and slot ID for those downlink ports
use only rack 3
the slot number is always slot 4
up to three shelves are supported in a rack
shelf jumper settings override the default rack and shelf assignments of downlink
ports 8, 9, and 10.
you are required to configure the rack, shelf, and slot ID for each SFP port to which
an ES is connected
if the SFP port is preplanned using CLI, you must set the shelf jumpers to match and
connect the corresponding remote LT unit
use only racks 1 and 2
the slot number is the LT slot on the ES that contains the remote LT unit connected
to the downlink port
up to three shelves are supported in a rack
DLP 177-2
Edition 02 Released
See 7330 ISAM FTTN Product Information for more information about expansion
configurations and configurable SFP ports.
See TNG 106 for more information about rack and shelf assignments for remote
expansion units.
Procedure
Proceed as follows to configure the rack, shelf, and rack IDs for an SFP port on a
GENC-E or GENC-F card.
1
Configure the traffic direction of the two configurable external-links on the host
expansion card with the following command:
configure equipment external-link-host (SFP index 6 or 7)
(no) direction <Equipm::ExternalLinkConfigType>
View actual rack, shelf, and slot settings of the connected remote LT unit:
show equipment external-link-host (index 6-17) detail
Configuration example:
configure equipment external-link-host 6 direction remote-lt
info configure equipment external-link-host
show equipment external-link-host detail
DLP 177-3
Edition 02 Released
DLP 177-4
Edition 02 Released
Prerequisites
The following prerequisites must be fulfilled before a default security domain can be
created:
Procedure
Proceed as follows to configure the default security domain:
1
DLP 178-1
Edition 02 Released
Configuration example:
In the following example, a default security domain with name unspecified is
created. The connection profile is named no-domain.
configure system security domain unspecified authenticator
radius:RADPol23 vrf-index 1
configure system security conn-profile no-domain version 1
no reject-no-domain domain-name unspecified
configure system security conn-policy conn-profile-name no-domain
DLP 178-2
Edition 02 Released
General
There are three main tasks you can perform using CLI when configuring system logging:
The NE supports up to 64 system log files and up to 64 remote system log servers. You
can enable or disable logging for all system logs and view system-wide information for
system logs.
You can view system-wide information for local system logs, such as the maximum
message size allowed and statistics about how much combined disk space the local
system logs utilize. System-wide information for local system log files are displayed using
the show CLI command and can be displayed in four different formats.
You can create and configure up to 64 system logs. The combined maximum size of all
locally saved system log files is 2 Mbytes. For each system log file, you can set the
method of cycling messages when the system log file is full. Cycling of system log
messages is performed in one of two ways: wrap new entries to overwrite the oldest
entries, or discard all new entries.
DLP 179-1
Edition 02 Released
You can configure the following parameters for each system log file:
system log filename (local only), entered using up to eight alphanumeric characters
followed by a dot separator and a three-alphanumeric character extension; for
example, Alrmhigh.txt
destination server type:
all active TL1 and CLI terminals (all-users)
all active CLI terminals (all-CLI)
all active TL1 terminals (all-TL1)
single active Tl1 terminal (tl1-user)
local file (file:name:size)
remote host (udp:port:serv-ip-addr)
destination server address, entered as an alphanumeric host name or in standard dot
format (maximum value 255.255.255.255); where 0.0.0.0 is entered for local files
action taken when the system log file is full (wrap or discard)
activate and deactivate logging
delete a system log file
view the configuration of a system log file
By default, all message types are logged to the system log files. In addition, alarms
generated in the system and the errors encountered are logged to the system log files.
You can configure filters to define which messages get logged to which system log file
based on message type.
Table DLP 179-1 lists the possible message type and log severity parameters. You can
select which messages are sent to specific system log files using filters and can group
multiple message types.
Table DLP 179-1: Message type and log severity parameters
Item
Description
Parameter
Message type
Authentication actions
AUTH
CLI_CONFIG
TL1_CONFIG
CLI messages
CLI_MSG
TL1 messages
TL1_MSG
ALL
(1 of 2)
DLP 179-2
Edition 02 Released
Item
Description
Parameter
Log severity
Emergency
EM
Alert
AL
Critical
CR
Error
ER
Warning
WN
Notice
NO
Information
IN
Debug
DBG
(2 of 2)
When activating or deactivating system logs, you must specify the following information:
The index number is an integer from 1 to 64. Use the information command to view the
settings of a system log file before entering the message type and log severity of the
system log file to activate or deactivate.
To monitor remote system logs dynamically, set the destination server type to all active
CLI or all active TL1 terminals for a particular system log. This sends all messages to the
active terminals that have a management session with the NE. When you are done
monitoring, deactivate system logging for that server. You can view the static contents of
a system log file that is saved to a remote server location using any text-based editor.
You can also configure system and security logging using TL1 or SNMP. See the
7302 ISAM | 7330 ISAM FTTN TL1 Commands and Messages or the latest MIB for more
information.
Procedure
Proceed as follows to configure system logs:
1
View system-wide information for local system logs with the following command:
show system syslog (type)
Where:
Type is how to display the information, which can be either detail, hierarchical, flat, or xml.
Create the system log and set the system log filename and configure the destination
server type with the following command:
configure system syslog destination (name)
type <Sys::ServerType>
no disable
DLP 179-3
Edition 02 Released
Configure which messages must be sent to a given system log destination and
assign the appropriate system log parameters to them with the following command:
configure system syslog route (name) msg-type <Sys::MessageType>
facility <Sys::LogFacility>
(no) emergency
(no) alert
(no) critical
(no) error
(no) warning
(no) notice
(no) information
(no) debug
Retrieve the configuration of a specific system log with the following command:
info configure system syslog destination (name)
type <Sys::ServerType> detail
Retrieve the configuration for all configured system logs with the following
command:
info configure system syslog destination detail
Configuration example:
DLP 179-4
Edition 02 Released
Prerequisite
The following prerequisite must be fulfilled before static MAC addresses can be
configured:
A VLAN must exist; see DLP 117, DLP 118, DLP 119 or DLP 120.
The board must have been planned; see DLP 111.
xDSL profiles must have been created; see DLP 129.
Procedure
Proceed as follows to configure static MAC addresses:
1
DLP 180-1
Edition 02 Released
Configure a static MAC address on the SHub with the following command:
configure vlan shub [unicast-mac (unicast-mac)
vlan-id <Vlan::VlanIndex>
forward-port lt:<Eqpt::RackId>/<Eqpt::ShelfId>/<Eqpt::SlotId>
| network:<Shub::NetworkPort> | nt
Configuration example:
configure vlan unicast-mac 00:00:00:00:00:05 vlan-id 200
forward-port 1/1/5/12:8:35
configure vlan shub unicast-mac 00:00:00:00:00:01 vlan-id 200
forward-port network:7
DLP 180-2
Edition 02 Released
Note This procedure can be used for the default superuser isadmin.
Procedure
Proceed as follows to configure operator authentication via RADIUS:
1
DLP 181-1
Edition 02 Released
Enable the RADIUS for the superuser with the following command:
configure system security radius
(no) relay
auth-super-user
Configuration example:
configure system security radius auth-server RADAuthServ1
vrf-index 0 ip-address 10.176.5.5 secret Khinghkhongh
timeout-limit 5 no admin-down dead-interval 1
configure system security radius policy oper_e14 nas-id E14
nas-ip-address 10.177.0.112 disable-accnt-msg disable-eap
configure system security radius policy oper_e14 servers 1
auth-server name:RADAuthServ1 vrf-index-auth 0 no acc-server
priority 1
configure system security radius operator-policy name:oper_e14
DLP 181-2
Edition 02 Released
Procedure
Proceed as follows:
1
DLP 182-1
Edition 02 Released
Manage the SHDSL unit profile in one SHDSL span with the following command:
configure shdsl unit (if-index) unit-id <Shdsl::UnitId>
(no) loop-attenuation <Shdsl::UnitLoopAttenThreshold>
(no) snr-margin <Shdsl::UnitSnrMarginThreshold>
(no) loopback-timeout <Shdsl::UnitLoopbackTimeout>
Configure the SHDSL segment points on either side of an SHDSL unit with the
following command:
configure shdsl segment (if-index) unit-id <Shdsl::UnitId>
side <Shdsl::SegmentSide>
(no) loopback <Shdsl::SegmentTermLoopbackConf>
pbo-mode <Shdsl::SegmentTermPowerBackoff>
DLP 182-2
Edition 02 Released
Configuration examples:
The first configuration example is for 4-wire Multi-pair bonding, the second
configuration example is for IMA and the third configuration example is for EFM
(4-wire EFM, no bonding).
configure shdsl span 1/1/9/1 active wire-mode four-wire
min-line-rate 2048 max-line-rate 5120 margin-down-worst 5
margin-up-worst 5 admin-up
configure shdsl span 1/1/9/3 active wire-mode four-wire
min-line-rate 2048 max-line-rate 5120 margin-down-worst 5
margin-up-worst 5 admin-up
configure shdsl unit 1/1/9/1 unit-id stu-r loopback-timeout 10
configure shdsl segment 1/1/9/1 unit-id stu-c side customer
loopback normal
configure atm pvc 1/1/9/1:8:35 no admin-down
aal5-encap-type llc-snap
configure atm pvc 1/1/9/3:8:35 no admin-down
aal5-encap-type llc-snap
configure bridge port 1/1/9/1:8:35
configure bridge port 1/1/9/1:8:35 vlan-id 100
configure bridge port 1/1/9/1:8:35 pvid 100
configure bridge port 1/1/9/3:8:35
configure bridge port 1/1/9/3:8:35 vlan-id 100
configure bridge port 1/1/9/3:8:35 pvid 100
DLP 182-3
Edition 02 Released
DLP 182-4
Edition 02 Released
Prerequisite
The following prerequisite must be fulfilled before IMA can be configured on SHDSL links:
the SHDSL links must have been created (and have operational mode ima); see
DLP 182.
Procedure
Proceed as follows:
1
DLP 183-1
Edition 02 Released
Activate the IMA line interface with one of the following commands:
configure ima group (if-index) admin-up
configure interface port
ima-line:<Eqpt::Rack>/<Eqpt::Shelf>/<Eqpt::LtSlot>/<Eqpt::Port>
admin-up
Configuration example:
configure ima group 1/1/9/16 active admin-up min-tx-links 2
min-rx-links 2
configure ima link 1/1/9/16 grp-index 1/1/9/16
configure ima link 1/1/9/18 grp-index 1/1/9/16
configure ima link 1/1/9/21 grp-index 1/1/9/16
configure ima link 1/1/9/24 grp-index 1/1/9/16
configure atm pvc 1/1/9/16:0:35 aal5-encap-type
vc-mux-bridged-8023 no admin-down
configure bridge port 1/1/9/16:0:35
configure bridge port 1/1/9/16:0:35 vlan-id 100
configure bridge port 1/1/9/16:0:35 pvid 100
DLP 183-2
Edition 02 Released
General
The EMS (5526 AMS or 5523 AWS) supports the creation of an NE using a single IP
address for the NE only or dual IP addresses for the NE and SHub. After you have
created the NE and configured it to use a single or dual IP address, you can convert the
node from single to dual IP address mode, or from dual to single IP address mode, using
the CLI commands in this DLP. SNMPv3 is only supported in single IP address mode.
You cannot convert a system configured with SNMPv3 to dual IP mode.
Before you perform the steps in this DLP, you must have already set up the NE for EMS
(5526 AMS or 5523 AWS) management and have configured the system for single or
dual IP address mode.
Note You can lose communication with the NE when you change the
IP address. To ensure that the connection is maintained, perform these
procedures from the craft port.
Prerequisites
The NE must be administered by the EMS (5526 AMS or 5523 AWS).
DLP 184-1
Edition 02 Released
Procedure
Proceed as follows to convert the IP address mode on the NE:
1
Go to step 12.
Remove the single IP address mode configuration with the following command:
configure system no single-public-ip
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
Configure the new IP address to the management vlan on the SHub via the following
command:
configure interface shub ip <Vlan::UVlanIndex>
ip-addr <Ip::V4Address>/<Ip::PrefixLengthHost>
Change the administrative status of the management vlan on the SHub to up with
the following command:
configure interface shub vlan-id <Vlan::UVlanIndex>
admin-status up
Configure the default route in the SHub with the following command:
configure ip shub vrf 0 route-dest 0.0.0.0/0
next-hop <gateway-ip-address>
vlan-id 4093
10
Configure the SHub filter (access list) with the following command:
configure system shub filter shub-manager <index> src-ip-addr
<Ip::V4Address>
where <Ip::V4Address> is the IP address of the EMS
DLP 184-2
Edition 02 Released
11
Configure the SNMP SHub community string with the following command:
configure system security snmp shub community <index> name <name>
privilege read-write no ip-addr
12
Configuration example:
The following example shows the procedure to convert from dual to single IP
address:
configure system single-public-ip
The following example shows the procedure to convert from single to dual IP
address:
configure system no single-public-ip
configure interface shub vlan-id 4093 admin-status down
configure interface shub ip 4093 ip-addr 10.177.0.113/17
configure interface shub vlan-id 4093 admin-status up
configure ip shub vrf 0 route-dest 0.0.0.0/0
next-hop 10.177.127.254 vlan-id 4093
configure system shub filter shub-manager 1
src-ip-addr 10.176.8.8
configure system security snmp shub community 4 name NETMAN
privilege read-write no ip-addr
DLP 184-3
Edition 02 Released
DLP 184-4
Edition 02 Released
The NE does not reply to requests for a TCP connection from an unknown BNG.
This means:
If the TCP Retry Timer is zero, the NE will not start the TCP connection.
If the TCP Retry Timer is not zero, the NE will start the setup of a TCP connection to
the BNG whose IP address has been configured.
If the GSMP Retry Timer is zero, the NE will not start the GSMP Adjacency Protocol,
but instead be prepared to handle GSMP Adjacency Protocol messages from that
BNG.
If the GSMP Retry Timer is not zero, the NE starts the GSMP Adjacency Protocol in
addition to being prepared to handle GSMP Adjacency Protocol messages from that
BNG.
DLP 185-1
Edition 02 Released
Procedure
Proceed as follows to configure an NACP session:
1
Configure the NACP session parameters for a given session ID with the following
command:
configure l2cp session (index)
bras-ip-address <L2cp::InetAddress>
(no) gsmp-version <L2cp::Version>
(no) gsmp-sub-version <L2cp::SubVersion>
(no) encap-type <L2cp::EncapType>
(no) topo-discovery <L2cp::AccessTopologyDiscovery>
(no) layer2-oam <L2cp::Layer2OAM>
(no) alive-timer <L2cp::AliveTimer>
(no) port-reprt-shaper <L2cp::ReportShaper>
(no) aggr-reprt-shaper <L2cp::AggrReportShaper>
(no) tcp-retry-time <L2cp::TcpRetryTimer>
(no) gsmp-retry-time <L2cp::GsmpRetryTimer>
(no) dslam-name <L2cp::DslamName>
(no) window-size <L2cp::WindowSize>
(no) tcp-port <L2cp::InetPortNumber>
(no) vrf-id <L2cp::VrfIndex>
Configuration example:
configure l2cp session 1 bras-ip-address 192.168.200.100
gsmp-retry-time 0
DLP 185-2
Edition 02 Released
DLP 186-1
Edition 02 Released
Procedure
Proceed as follows to configure the DHCP MAC concentration:
1
Add DHCP option to the forwarder VRF on the LT with the following command:
configure dhcp-relay agent (vrfid)
bcast-vlan <Dhcp::VlanId>
option-82
circuit-id <Dhcp::CircuitId>
remote-id <Dhcp::RemoteId>
(no) dhcp-linerate <Dhcp::Dhcp-linerate>
Configuration example:
configure dhcp-relay agent 16 bcast-vlan l2-vlan:101 option-82
circuit-id physical-id remote-id customer-id
configure dhcp-relay agent 16 client-hw-address copysourcemac
DLP 186-2
Edition 02 Released
broadcast-frames:
This parameter determines whether broadcast frames must be switched for each
VLAN.
This parameter applies to iBridge VLANs.
priority-policy:
This parameter specifies how to deal with ethernet priority of the upstream frames.
This parameter applies to iBridge VLANs, cross-connect VLANs and QoS-aware
VLANs.
Procedure
Proceed as follows to configure the general VLAN parameters:
1
DLP 187-1
Edition 02 Released
DLP 187-2
Edition 02 Released
ADSL2+
VDSL
VDSL2
DLP 188-1
Edition 02 Released
Procedure
Proceed as follows to configure custom PSD points:
1
ii
Configure the PSD for ADSL2+ as custom PSD with the following command:
configure xdsl spectrum-profile (index) adsl2-plus
psd-shape-down custom-psd-down
iii
iv
3
Go to step 8
ii
Configure the downstream PSD for VDSL as custom PSD with the following
command:
configure xdsl spectrum-profile (index) vdsl psd-shape-down
custom-psd-down
iii
Configure the downstream PSD scale and type with the following command:
configure xdsl spectrum-profile (index) vdsl
cust-psd-sc-down linear | logarithmic
cust-psd-ty-down mask | template
DLP 188-2
Edition 02 Released
iv
v
4
Go to step 8
ii
Configure the upstream PSD for VDSL as custom PSD with the following
command:
configure xdsl spectrum-profile (index) vdsl rx-psd-shape-up
custom-rx-psd-up
iii
Configure the upstream PSD scale and type with the following command:
configure xdsl spectrum-profile (index) vdsl
cust-rx-psd-sc-up linear | logarithmic
cust-rx-psd-ty-up mask | template
iv
v
5
Go to step 8
ii
Configure the downstream PSD for VDSL2 as custom PSD with the following
command:
configure xdsl spectrum-profile (index) vdsl2 psd-shape-down
custom-psd-down
iii
Configure the downstream PSD scale and type with the following command:
configure xdsl spectrum-profile (index) vdsl2
cust-psd-sc-down linear | logarithmic
cust-psd-ty-down mask | template
DLP 188-3
Edition 02 Released
iv
v
6
Go to step 8
ii
Configure the upstream Rx PSD for VDSL2 as custom PSD with the following
command:
configure xdsl spectrum-profile (index) vdsl2 rx-psd-shape-up
custom-rx-psd-up
iii
Configure the upstream Rx PSD scale and type with the following command:
configure xdsl spectrum-profile (index) vdsl2
cust-rx-psd-sc-up linear | logarithmic
cust-rx-psd-ty-up mask | template
iv
v
7
Go to step 8
ii
Configure the upstream PSD for VDSL2 as custom PSD with the following
command:
configure xdsl spectrum-profile (index) vdsl2 psd-shape-up
custom-psd-up
iii
Configure the upstream PSD scale and type with the following command:
configure xdsl spectrum-profile (index) vdsl2
cust-psd-sc-up linear | logarithmic
cust-psd-ty-up mask | template
DLP 188-4
Edition 02 Released
iv
Configuration examples:
Configuration example for ADSL2+:
configure xdsl spectrum-profile 11 name adsl2-plus version 1
configure xdsl spectrum-profile 11 adsl2-plus psd-shape-down
custom-psd-down
configure xdsl spectrum-profile 11 adsl2-plus cust-psd-pt-down 1
frequency 1000 psd 55
configure xdsl spectrum-profile 11 adsl2-plus cust-psd-pt-down 2
frequency 1200 psd 65
configure xdsl spectrum-profile 11 active
DLP 188-5
Edition 02 Released
DLP 188-6
Edition 02 Released
DLP 188-7
Edition 02 Released
DLP 188-8
Edition 02 Released
DLP 189-1
Edition 02 Released
Procedure
Proceed as follows to configure virtual noise values for VDSL2:
1
Configure the virtual noise values in downstream direction with the following
command:
configure xdsl spectrum-profile (index) vdsl2
v-noise-psd-pt-down (psdpt)
frequency <Xdsl::CustFreq>
psd <Xdsl::CustPsd>
Configure the virtual noise values in upstream direction with the following command:
configure xdsl spectrum-profile (index) vdsl2
v-noise-psd-pt-up (psdpt)
frequency <Xdsl::CustFreq>
psd <Xdsl::CustPsd>
Configuration example:
configure xdsl spectrum-profile 17 name vdsl2-4
configure xdsl spectrum-profile 17 vdsl2 v-noise-psd-pt-down 1
frequency 1000 psd 55
configure xdsl spectrum-profile 17 vdsl2 v-noise-psd-pt-down 2
frequency 1200 psd 65
configure xdsl spectrum-profile 17 vdsl2 v-noise-psd-pt-up 1
frequency 1000 psd 55
configure xdsl spectrum-profile 17 vdsl2 v-noise-psd-pt-up 2
frequency 1200 psd 65
configure xdsl spectrum-profile 17 active
DLP 189-2
Edition 02 Released
Note Ensure that the TCA alarm is set to reporting and has a severity
equal to or greater than the non-itf-rep-sev-level; see DLP 110.
Prerequisites
The following prerequisites must be fulfilled before a TCA can be configured:
DLP 190-1
Edition 02 Released
Procedure
Proceed as follows to configure and enable a TCA:
1
Configuration example:
configure xdsl line 1/1/5/6 tca-line-threshold enable
ses-day-nearend 30
DLP 190-2
Edition 02 Released
Procedure
Proceed as follows to configure dual tagging mode:
1
Set the dual tag mode in the SHub with the following command:
configure vlan shub dual-tag-mode
Disable the dual tag mode in the SHub with the following command:
configure vlan shub no dual-tag-mode
Configuration example:
configure vlan shub dual-tag-mode
DLP 191-1
Edition 02 Released
DLP 191-2
Edition 02 Released
Prerequisites
The following prerequisites must be fulfilled before IPProxy CPE management can be
configured:
Procedure
Proceed as follows to configure IPProxy CPE management:
1
Create the S-VLAN to be used for IPProxy CPE management in the system with the
following command:
configure vlan id stacked:<Vlan::SVlanIndex>:0 name
<Vlan::AdminString> mode layer2-terminated
Associate the S-VLAN created with the IPProxy CPE management function with the
following command:
configure cpe-management vlan-id <CpeProxy::VlanIndex>
DLP 192-1
Edition 02 Released
Associate the S-VLAN created in the SHub with the IPProxy CPE management
function with the following command:
configure cpe-management shub vlan-id <CpeProxy::ShubVlanIndex>
Configuration example:
configure vlan id stacked:512:0 name IPProxyVLAN
mode layer2-terminated
configure cpe-management vlan-id 512
configure vlan shub id 512 mode layer2-terminated
configure cpe-management shub vlan-id 512
DLP 192-2
Edition 02 Released
Prerequisites
The following prerequisites must be fulfilled before IPProxy CPE management can be
enabled:
Procedure
Proceed as follows to enable IPProxy CPE management:
1
Configuration example:
configure cpe-management proxy-mode ip
DLP 193-1
Edition 02 Released
DLP 193-2
Edition 02 Released
Prerequisites
The following prerequisites must be fulfilled before IPProxy CPE management session
can be configured:
The IPProxy CPE Management S-VLAN must have be configured; see DLP 192
The IPProxy CPE Management S-VLAN function must have be enabled; see
DLP 193
The LT to which the CPE is connected must be planned and unlocked; see DLP 111
and DLP 112 respectively.
xDSL profiles must have been created; see DLP 129.
Procedure
Proceed as follows to configure a IPProxy CPE management session:
1
Configure the xDSL line to which the CPE is connected with the following command:
configure xdsl line
<Eqpt::RackId>/<Eqpt::ShelfId>/<Eqpt::SlotId>/<Eqpt::PortId>
service-profile <Xdsl::LineServiceProfile>
spectrum-profile <Xdsl::LineSpectrumProfile>
admin-up
DLP 194-1
Edition 02 Released
Add the SHub LT port to which the CPE is connected to the IPProxy CPE
Management S-VLAN (if not already added) with the following command:
configure vlan shub id <Sys::VlanId> egress-port
lt:<Eqpt::RackId>/<Eqpt::ShelfId>/<Eqpt::SlotId>
If the NT type is not of type ECNT-C, add the SHub NT port to the S-VLAN (if not
already added) with the following command:
configure vlan shub id <Sys::VlanId> egress-port nt
Configure the SC-VLAN to be used for this session. In this step, the CVlanIndex
given must be calculated as follows based on the LT port on which the IPProxy
session must be configured:
CVlanIndex = 48 x (LT slot# - 1) + LT port# + 1
where:
LT slot# has the range [1..16] (1 for left most LT slot on rack 1, shelf 1 and 16 for the last LT slot on
rack 1, shelf 1)
LT port# has the range [1..48] (1 for the first LT port and 48 for the last LT port).
Configure the PVC for this session with the following command:
configure atm pvc <Eqpt::RackId>/<Eqpt::ShelfId>/
<Eqpt::SlotId>/<Eqpt::PortId>:<Eqpt::VpiId>:Eqpt::VciId>
aal5-encap-type llc-snap-routed
Configure an IPoA cross-connect for this session with the following command:
configure atm ip-cross-connect <Eqpt::RackId>/<Eqpt::ShelfId>/
<Eqpt::SlotId>/<Eqpt::PortId>::<Eqpt::VpiId>:<Eqpt::VciId>
cpe <Ip::V4AddressHex>
next-hop <Ip::V4AddressHex>
Configure a bridge port for this session with the following command:
configure bridge port <Eqpt::RackId>/<Eqpt::ShelfId>/
<Eqpt::SlotId>/<Eqpt::PortId>:<Eqpt::VpiId>:<Eqpt::VciId>
mac-learn-off
Configure the SC-VLAN on the bridge port with the following command:
configure bridge port <Eqpt::RackId>/<Eqpt::ShelfId>/
<Eqpt::SlotId>/<Eqpt::PortId>:<Eqpt::VpiId>:<Eqpt::VciId>
vlan-id stacked:<Vlan::SVlanIndex>:<Vlan::CVlanIndex>
DLP 194-2
Edition 02 Released
10
Configure a PVID on the bridge port as the SC-VLAN with the following command:
configure bridge port <Eqpt::RackId>/<Eqpt::ShelfId>/
<Eqpt::SlotId>/<Eqpt::PortId>:<Eqpt::VpiId>:<Eqpt::VciId>
pvid stacked:<Vlan::SVlanIndex>:<Vlan::CVlanIndex>
11
12
Configuration example:
configure xdsl line 1/1/5/8 service-profile 7 spectrum-profile 5
admin-up
configure interface port xdsl-line:1/1/5/8 user IPProxy CPE M
configure vlan shub id 512 egress-port lt:1/1/5
configure vlan id stacked:512:57 name IPProxyCPE54
mode cross-connect
configure atm pvc 1/1/5/8:1:39 aal5-encap-type llc-snap-routed
configure atm ip-cross-connect 1/1/5/8:1:39 cpe 192.168.1.1
next-hop 192.168.1.2
configure bridge port 1/1/5/8:1:39 mac-learn-off
configure bridge port 1/1/5/8:1:39 vlan-id stacked:512:57
configure bridge port 1/1/5/8:1:39 pvid stacked:512:57
configure cpe-management session 1/1/5/8
DLP 194-3
Edition 02 Released
DLP 194-4
Edition 02 Released
Procedure
Proceed as follows to configure the system parameters for all bridge ports:
1
Configure specify the aging time for dynamically learned MAC addresses in the
filtering database of the LT with the following command:
configure bridge
ageing-time <Vlan::AgingTime>
Configure specify the aging time for dynamically learned MAC addresses in the
filtering database of the SHub with the following command:
configure bridge shub
ageing-time <Shub::AgingTime>
DLP 195-1
Edition 02 Released
Configure specify the MAC learning states with the following command:
configure bridge shub mac-learning
(no) disable-nw-port
Configuration example:
configure bridge ageing-time 360
configure bridge shub ageing-time 360
configure bridge shub mac-learning no disable-nw-port
DLP 195-2
Edition 02 Released
Prerequisite
The following prerequisite must be fullfilled before Voice SIP can be configured:
Procedure
Proceed as follows to configure Voice SIP:
1
Manage the Voice SIP server profile with the following command:
configure voice sip server (name)
admin-status up
domain <Sip::ApplicationServerDomain>
primary-ip-addr <Sip::ApplicationServerIpAddr>
(no) primary-udpport <Sip::ApplicationServerUdpPort>
secondary-ip-addr <Sip::ApplicationServerIpAddr>
(no) secondary-udpport <Sip::ApplicationServerUdpPort>
(no) server_type <Sip::ApplicationServerType>
Note The parameter server_type is not visible when a new Voice SIP
server profile is created, but only when an existing profile is modified.
DLP 196-1
Edition 02 Released
Manage the Voice SIP dial plan profile with the following command:
configure voice sip dialplan (name)
(no) pre-activated <Sip::DialPlanPreActivated>
(no) static-prefix <Sip::DialPlanStaticPrefix>
(no) static-suffix <Sip::DialPlanStaticSuffix>
by DHCP: go to step 4
manually: go to step 6
Configure the Voice SIP user agent profile management by DHCP with the following
command:
configure voice sip user-agent-dhcp (name)
associated-slot <Equipm::LtSlotIndex>
associated-server <Sip::ApplicationServerName>
associated-dialplan <Sip::DialPlanName>
(no) user-agent-domain <Sip::UserAgentUaDomain>
admin-status <Sip::UserAgentAdminStatus>
(no) udp-port <Sip::UserAgentUdpPort>
vlan-id <Sip::UserAgentVlanId>
(no) signal-dscp <Sip::UserAgentSignalDscp>
(no) signal-pbits <Sip::UserAgentSignalPbits>
(no) rtp-dscp <Sip::UserAgentRtpDscp>
(no) rtp-pbits <Sip::UserAgentRtpPbits>
Go to step 7.
Configure the Voice SIP user agent profile mangement manually with the following
command:
configure voice sip user-agent-manual (name)
associated-slot <Equipm::LtSlotIndex>
associated-server <Sip::ApplicationServerName>
associated-dialplan <Sip::DialPlanName>
(no) user-agent-domain <Sip::UserAgentUaDomain>
admin-status <Sip::UserAgentAdminStatus>
ip-address <Sip::UserAgentIpAddr>
prefix-length <Sip::PrefixLength>
gateway-ip <Sip::UserAgentIpAddr>
domain-server <Sip::UserAgentIpAddr>
(no) udp-port <Sip::UserAgentUdpPort>
vlan-id <Sip::UserAgentVlanId>
(no) signal-dscp <Sip::UserAgentSignalDscp>
(no) signal-pbits <Sip::UserAgentSignalPbits>
(no) rtp-dscp <Sip::UserAgentRtpDscp>
(no) rtp-pbits <Sip::UserAgentRtpPbits>
Manage the Voice SIP dial plan digitmap with the following command:
configure voice sip digitmap (name)
type <Sip::DialPlanDigitmapType>
rule <Sip::DialPlanDigitmapValue>
(no) access-type <Sip::DialPlanDigitmapAccessType>
DLP 196-2
Edition 02 Released
Manage the Voice SIP termination profile with the following command:
configure voice sip termination (termination)
user-agent <Sip::UserAgentName>
(no) directory-number <Sip::TermDnumber>
(no) user-name <Sip::TermUserName>
(no) uri <Sip::TermUri>
(no) direct-uri <Sip::TermUri>
(no) line-feed <Sip::TermLineCharacter>
(no) md5-realm <Sip::MD5Realm>
(no) md5-password <Sip::MD5Realm>
(no) admin-status <Sip::TermAdminStatus>
Manage the Voice SIP port Local Loop Unbundling with the following command:
configure voice sip local-loop (line)
(no) unbundle
Note This command can only be used when ALTS-U subracks are
being used.
10
Configuration example:
configure voice sip server SIPServer1 domain SIPDomain
primary-ip-addr 200.200.1.1
configure voice sip server SIPServer1 server_type alcatel
configure voice sip server SIPServer1 admin-status up
configure voice sip dialplan SIPDialplan1
configure voice sip user-agent-dhcp SIPAgent1
associated-slot 1/1/6 associated-server SIPServer1
associated-dialplan SIPDialplan1 admin-status up vlan-id 650
configure voice sip digitmap Digitmap1 type regular rule 120
configure voice sip termination 1/1/6/1 user-agent SIPAgent1
directory-number 123456 admin-status up
DLP 196-3
Edition 02 Released
DLP 196-4
Edition 02 Released
Procedure
The following commands can be used for viewing the configuration and operational data
of ports:
1
DLP 197-1
Edition 02 Released
Configuration example:
show xdsl config-data-port 1/1/5/12
show xdsl oper-data-port 1/1/5/12
DLP 197-2
Edition 02 Released
Prerequisites
The following prerequisites must be fulfilled before multicast on the SHub can be
configured:
Procedure
Proceed as follows to configure multicast on the SHub:
1
Configure the multicast related parameters applicable to the SHub with the following
command:
configure mcast shub
(no) active-streams <Igmp::MaxMcastLearn>
(no) max-bw <Igmp::SystemMaxbandwidth>
(no) max-no-rate-based <Igmp::SystemMaxNoRateBased>
Configure entries in the IP multicast table for the SHub with the following command:
configure mcast shub mcast-addr (mcast-addr)
vlan-id <Vlan::VlanId>
DLP 198-1
Edition 02 Released
Configure the ports to which the traffic related to the specified multicast IP address
will be forwarded with the following command:
configure mcast shub mcast-addr (mcast-addr)
vlan-id <Vlan::VlanId>
(no) egress-port (port)
Configuration example:
configure mcast shub active-streams 200
configure mcast shub mcast-addr 224.1.1.10 vlan-id 200
configure mcast shub mcast-addr 224.1.1.10 vlan-id 200
egress-port lt:1/1/5
configure mcast shub src 224.1.1.1 vlan-id 200 ip-addr 0.0.0.0
eth-sus-bit-rate 4250 guaranteed-serv bundle name:MyBundle
DLP 198-2
Edition 02 Released
Note For more information about QoS and the configuration of QoS,
refer to TNG 101.
Prerequisites
The following prerequisites must be fulfilled before QoS on the SHub can be configured:
The egress port must have been added to the VLAN; see DLP 128.
Procedure
Proceed as follows to configure QoS on the SHub:
1
Configure the queues on the SHub ports with the following command:
configure qos shub queue-config (port)
(no) queue0-weight <Qos::ShubQueueWeight1>
(no) queue1-weight <Qos::ShubQueueWeight1>
(no) rx-pause
(no) egress-rate <Qos::ShubPortRate>
(no) dscp2p-enable
Configure the traffic classes on the SHub with the following command:
configure qos shub tc-map-dot1p (port)
traffic-class <Qos::ShubTrafficClass>
DLP 199-1
Edition 02 Released
Configure the mapping of the DSCP value to the 802.1p value with the following
command:
configure qos shub dscp-map-dot1p (dscp-index)
dot1p-value <Qos::ShubDSCPPriority>
Configure the ingress policing parameters on SHub port with the following
command:
configure qos shub meter (index)
(no) name <Qos::DisplayString>
max-ingress-rate <Qos::MeterIngressRate>
burst-size <Qos::MeterBurstSize>
Configuration example:
configure qos shub queue-config 3 queue0-weight 4
queue1-weight 6 egress-rate 800
configure qos shub tc-map-dot1p 2 traffic-class 1
configure qos shub dscp-map-dot1p 13 dot1p-value 2
configure qos shub meter 32 name QoSShubMeter32
max-ingress-rate 8192 burst-size 4
configure qos shub flow 22 name VLANFLow vlan:300
configure qos shub policer 3 flow 22 meter 32
DLP 199-2
Edition 02 Released
Edition 02 Released
Edition 02 Released
The SHub database can be saved manually with the following command:
admin software-mngt shub database save
General
The TFTP daemon on the AWS assumes a default home directory
/var/opt/aws/equipment.
The TFTP daemon on the AMS assumes a default home directory
/opt/ALAams/systemdata.
This means that all the TFTPs initiated from the NE result in a file written relative to this
point.
RTP 100-1
Edition 02 Released
dm_complete.tar
dm.tar: This is the dm_complete.tar without the management data
Prerequisite
An empty file dm_complete.tar must exist in the specified path on the TFTP server before
the upload is started. Otherwise, the upload will fail (error upload-error:file-not-found).
Create the dm_complete.tar file on the TFTP server with the following commands
($ prompt is regular user, # prompt is superuser):
$ su
# cd /var/opt/aws/equipment/temp (*)
# touch dm_complete.tar
# chmod 666 dm_complete.tar
# exit
$
The NT database can now be backed up.
Note
RTP 100-2
Edition 02 Released
(*)
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.
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
Configuration example:
show system shub entry status
admin software-mngt shub database save
show system shub entry status
admin software-mngt database upload
actual-active:10.176.5.5:dm.tar
show software-mngt upload-download
sleep 100
show software-mngt upload-download
admin software-mngt database upload
actual-active:10.176.5.5:dm_complete.tar
sleep 100
show software-mngt upload-download
RTP 100-3
Edition 02 Released
RTP 100-4
Edition 02 Released
Procedure
Proceed as follows to restore the NT database:
1
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
RTP 101-1
Edition 02 Released
Configuration example:
admin software-mngt database download 10.176.5.5:dm_complete.tar
show software-mngt upload-download
sleep 60
show software-mngt upload-download
admin software-mngt oswp 1 activate with-linked-db
RTP 101-2
Edition 02 Released
Description
manufacturer
inventory-pba
inventory-fpba
The Alcatel Printed Board Assembly code of the board, which also identifies the
boot software
inventory-ics
inventory-clie
serial-no
Procedure
Proceed as follows to retrieve and show remote inventory information:
1
RTP 102-1
Edition 02 Released
Configuration example:
show equipment slot detail
show equipment applique detail
RTP 102-2
Edition 02 Released
Edition 02 Released
Edition 02 Released
To PSTN
Shelf
Test
TAU
SPLITTER
NTIO
TL1 gateway
installed
Computer/WS
(Median Device
software installed)
Power
-48v
Test Head
NT
LT
Lab
Network
SHub
Computer
(test head
Software installed)
TAP 100-1
Edition 02 Released
ACT-USER command
CONN-LPACC-MET command
CONN-TACC-MET command
CHG-SPLIT command
CONN-MON command
DISC-TACC command
REPT-STAT command
REPT-INITZN command
REPT-OPSTAT-TACC command
CANC-USER command
ACT-USER Command
Command Syntax
ACT-USER:[tid]:uid:[ctag]::pid;
Command Description
This command activates the user session.
Configuration Example
ACT-USER::SUPERUSER:::PASWD;
CONN-LPACC-MET Command
Command Syntax
CONN-LPACC-MET:[tid]:aid_circuit:[ctag]::[tap]:[configrn];
Command Description
This command controls TAP selection, access point designation, and TAP loop around
for the remote test unit to calibrate for the next test.
Configuration Example
CONN-LPACC-MET: LAB: XDSL-1-1-1-1:::1:2WA;
TAP 100-2
Edition 02 Released
CONN-TACC-MET Command
Command Syntax
CONN-TACC-MET:[tid]:[tap]:[ctag];
Command Description
This command enables the NE to provide a zero-loss, high-impedance monitor
connection to the transmission pair of the circuit and complete circuit access.
It also removes the TAP loop around and connects the appropriate TAP lead pair to the
access point.
Configuration Example
CONN-TACC-MET:LAB:1:;
CHG-SPLIT Command
Command Syntax
CHG-SPLIT:[tid]:[tap]:[ctag];
Command Description
This command instructs the NE to provide the necessary connection to the TAP and split,
at the access point, the pair or pairs specified by the access command of the circuit under
test.
Use this command to provide access to the lead pair in order to induce TDR testing.
Configuration Example
CHG-SPLIT:LAB:1:;
CONN-MON Command
Command Syntax
CONN-MON: [tid]:[tap]:[ctag];
Command Description
This command is used to establish a monitor state without having to re-access the circuit
under test. Use this command to get from the SPLIT mode to MONITOR mode.
Configuration Example
CONN-MON:LAB:1:;
TAP 100-3
Edition 02 Released
DISC-TACC Command
Command Syntax
DISC-TACC:[tid]:[tap]:[ctag];
Command Description
This command causes the NE to restore the circuit under test to its through state and
release all TAP connections to that access point.
Configuration Example
DISC-TACC:LAB:1:;
REPT-STAT Command
Command Syntax
REPT-STAT:[tid]::[ctag];
Command Description
This command is sent from the OS to the RTU or the NE to check that the link between
them is in operation. Additionally, if the NE does not receive this command from the OS
or the RTU for a period of 75 seconds, it shall release any access at the TAP.
Configuration Example
REPT-STAT:LAB::;
REPT-INITZN Command
Command Syntax
REPT-INITZN:[tid]::[ctag];
Command Description
This input command message is used to indicate an initialization by an OS to a RTU or
by a RTU to NE or by NE to RTU.
As input command, it is sent from the OS to the RTU or NE to indicate the OS has
initialized. The RTU and NE will disconnect any accesses that are up at the request of
the OS sending this command.
If the RTU initializes, this command is sent to all NE's providing test access causing the
accesses to release.
If the NE initializes, this input command will be send to the RTU providing test access
causing the RTU to release all resources.
Configuration Example
REPT-INITZN:LAB::;
TAP 100-4
Edition 02 Released
REPT-OPSTAT-TACC Command
Command Syntax
REPT-OPSTAT-TACC:[tid]:[tap]:[ctag];
Command Description
This command reports the status of the test access port (TAP).
Following options are supported for STATE:
Configuration Example
REPT-OPSTAT-TACC:LAB:1:;
CANC-USER Command
Command Syntax
CANC-USER:[tid]:[uid]:[ctag];
Command Description
This command terminates the user session and releases all TAP resources on the NE.
Configuration Example
CANC-USER: LAB::;
TAP 100-5
Edition 02 Released
TAP 100-6
Edition 02 Released
Procedure
Proceed as follows to perform an F5 loopback test:
1
Configuration example:
admin atm port 1/1/5/1:8:35 f5-loopback-ete start
info admin atm port 1/1/5/1:8:35
TAP 101-1
Edition 02 Released
TAP 101-2
Edition 02 Released
Procedure
Proceed as follows to perform equipment repair tasks:
1
Pull out equipment; see the XD Modular Hardware Installation Manual for the 7302
ISAM or the Hardware Installation and Maintenance Practices for the 7330 FTTN.
Note The NE does not keep time while the card is unplugged from the
shelf. In order for the time to be synchronized when the card boots up, it
must be set to use SNTP time synchronization with the management
station. See DLP 103.
4
Plug in equipment; see the XD Modular Hardware Installation Manual for the 7302
ISAM or the Hardware Installation and Maintenance Practices for the 7330 FTTN.
TAP 102-1
Edition 02 Released
TAP 102-2
Edition 02 Released
TAP 103-1
Edition 02 Released
TAP 103-2
Edition 02 Released
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.
TAP 104-1
Edition 02 Released
Alarms are grouped by alarm type in Table TAP 104-1 and each alarm has the following
parameters listed in the order they appear in the table:
Except where otherwise specified, the report and logging modes for each alarm are
enabled.
Procedure
Use this procedure to isolate a fault indicated by an alarm.
1
To access the alarms using the 5526 AMS, see NTP 111 Manage alarms
and events in the 7330 ISAM FTTN Operations and Maintenance Using the
5526 AMS guide.
To access the alarms using 5523 AWS, see Chapter 3 AWS Admin
overview in the 5523 AWS ADMIN User Guide.
To access the alarms using CLI, see NTP 115 Monitor alarms in the
7330 ISAM FTTN Operations and Maintenance Using CLI guide.
Note If multiple alarms are present, resolve alarms in the order listed
below:
Critical (red)
Major (orange)
Minor (yellow)
TAP 104-2
Edition 02 Released
Use Tables TAP 104-1 and TAP 104-2 to help you determine the cause of the alarm
and the appropriate action for resolving the alarm. Alarms are grouped by type. You
can use the class column of the table to help locate an alarm in the table. Some
alarms are not currently supported.
Note Tables TAP 104-1 and TAP 104-2 list in parentheses the alarm
names as they appear for the CLI configure command. Alarm names as
they appear in the CLI show alarm commands are slightly different.
Table TAP 104-1: Alarm definitions for the 7302 ISAM and the 7330 ISAM FTTN
Alarm (grouped by alarm type)
No.
Applies to
Description
Class
Severity
SA
7302
7330
Alarm type = Equip (1); Index1 = eqptHolderld (index in equipment holder Table), Index22 = not used
0
No defects
Equip
Critical
Equip
Major
Equip
Major
Com
Major
Com
Critical
Equip
Critical
Equip
Major
Equip
Critical
(persist-data-loss)
2
8
25
(back-pnl-inv)
28
Alarm type = EquipHolder (2); Index1 = eqptHolderId (Index in equipment holder table), Index2 = not used
0
No defects
Equip
Minor
(rack-power)
(1 of 17)
TAP 104-3
Edition 02 Released
Description
No.
Class
Severity
SA
Equip
Major
Equip
Major
Equip
Applies to
7302
7330
Minor
Equip
Critical
Equip
Major
(rack-fan-unit1)
3
Shelf-type mismatch
alarm
(shelf-type-mismatch)
Extension chain
installation alarm
(ext-chain-instl)
Alarm type = EquipHolder (2); Index 1 = eqptHolderId (index in equipment holder table to identify a shelf), Index 2 =
not used
0
15
No defects
Door alarm
Envir
Minor
Equip
Critical
Equip
Major
Equip
Critical
(door)
17
Fuse alarm
(fuse)
18
19
Envir
Critical
(ac-power-fail)
Alarm type = PlugInUnit (3); Index1 = eqptSlotId (index in equipment Board Table), Index2 = not used
0
No defects
Board-type mismatch
alarm (1)
Equip
Minor
(board-mismatch)
(2 of 17)
TAP 104-4
Edition 02 Released
Class
Severity
SA
Equip
Major
(sw-download)
Temperature exceeded
Temperature shutdown
alarm
Defense alarm
Board installation
missing alarm (1)
Board initialization
alarm (1)
Equip
Major
Equip
Critical
Equip
Major
Equip
Minor
Equip
Major
Equip
Major
(board-init)
17
(board-inserted)
16
(board-present)
15
(defense)
14
7330
Major
(temp-shutoff)
13
7302
Equip
(temperature)
12
Applies to
Description
(number-of-resets)
28
Equip
Critical
29
Equip
Critical
Equip
Major
(sem-ups-fail)
30
Board reset or
communication failure (1)
(board-reset-cf)
(3 of 17)
TAP 104-5
Edition 02 Released
Description
Class
Severity
SA
Equip
Critical
(shub-uplink)
Applies to
7302
7330
Alarm type = ATM (8); Index1 = ifIndex (of ATM physical port), Index2 = see specific alarm number
0
No defects
QoS
Minor
(cell-discard-up)
Index2 = VPI/VCI
Report mode = disabled
Logging mode = disabled
QoS
Minor
(cell-discard-down)
Com
Minor
(mac-conflict)
Alarm type = CustomizableAlarm (10); Index1 = Rack_ID (position of the rack, range 0 to 5), Index2 = not used
0
No defects
CustomizableAlarm 1
Envir
Indeterminate
Envir
Indeterminate
Envir
Indeterminate
Envir
Indeterminate
Envir
Indeterminate
(custom1)
2
CustomizableAlarm 2
(custom2)
CustomizableAlarm 3
(custom3)
CustomizableAlarm 4
(custom4)
CustomizableAlarm 5
(custom5)
Alarm type = CustomizableAlarm (10); Index1 = eqptHolderID (shelf index in equipment holder table), Index2 = not
used
0
11
No defects
HECustomizableAlarm 1
Envir
Indeterminate
Envir
Indeterminate
(he-custom1)
12
HECustomizableAlarm 2
(he-custom2)
(4 of 17)
TAP 104-6
Edition 02 Released
Class
Severity
SA
HECustomizableAlarm 3
Envir
Indeterminate
Envir
Indeterminate
Envir
Envir
(he-custom3)
14
HECustomizableAlarm 4
(he-custom4)
15
HECustomizableAlarm 5
(he-custom5)
16
HECustomizableAlarm 6
Applies to
Description
(he-custom6)
7302
7330
Indeterminate
Indeterminate
Alarm type = IMA-group (13)l Index1 = IfIndex (of IMA-group), Index2 = not used
0
No defects
Alarm type = IMA-link (14); Index1 = IfIndex (of IMA-link), Index2 = not used
0
No defects
Alarm type = Redundancy (20); Index1 = not used, Index2 = not used
0
No defects
Switchover capability
lost (loss-swo-cap)
Equip
Major
Alarm type = EthItf (24); Index1 = ifIndex (of Ethernet port), Index2 = see specific alarm number
0
No defects
Com
Critical
(ether-linkdown)
Alarm type = SwMgnt (29); Index1 = eqptSlotId (index in equipment board table for the NT), Index2 = not used
0
No defects
Proc
Major
Proc
Major
(sw-rollback)
Implicit database
rollback
(db-rollback)
Alarm type = TmpFilter (34); Index1 = 0, Index2 = 0 Remark: These values are inherited from the related basic alarm
0
No defects
Com
Indeterminate
Com
Indeterminate
(5 of 17)
TAP 104-7
Edition 02 Released
Description
No.
Class
Severity
SA
Com
Indeterminate
Com
Indeterminate
Com
Applies to
7302
7330
Indeterminate
Com
Indeterminate
Com
Indeterminate
Com
Indeterminate
Com
Indeterminate
10
Com
Indeterminate
11
Com
Indeterminate
12
Com
Indeterminate
13
Com
Indeterminate
14
Com
Indeterminate
15
Com
Indeterminate
16
Com
Indeterminate
17
Com
Indeterminate
18
Com
Indeterminate
(6 of 17)
TAP 104-8
Edition 02 Released
Applies to
Description
No.
Class
Severity
SA
19
Com
Indeterminate
20
Com
Indeterminate
21
Com
22
23
7302
7330
Indeterminate
Com
Indeterminate
Com
Indeterminate
24
Com
Indeterminate
25
Com
Indeterminate
26
Com
Indeterminate
27
Com
Indeterminate
28
Com
Indeterminate
29
Com
Indeterminate
30
Com
Indeterminate
31
Com
Indeterminate
No defects
Com
Indeterminate
Com
Indeterminate
Com
Indeterminate
(7 of 17)
TAP 104-9
Edition 02 Released
Description
No.
Class
Severity
SA
Com
Indeterminate
Com
Indeterminate
Com
Applies to
7302
7330
Indeterminate
Com
Indeterminate
Com
Indeterminate
Com
Indeterminate
10
Com
Indeterminate
11
Com
Indeterminate
12
Com
Indeterminate
13
Com
Indeterminate
14
Com
Indeterminate
15
Com
Indeterminate
16
Com
Indeterminate
17
Com
Indeterminate
18
Com
Indeterminate
19
Com
Indeterminate
(8 of 17)
TAP 104-10
Edition 02 Released
Applies to
Description
No.
Class
Severity
SA
20
Com
Indeterminate
21
Com
Indeterminate
22
Com
23
24
7302
7330
Indeterminate
Com
Indeterminate
Com
Indeterminate
25
Com
Indeterminate
26
Com
Indeterminate
27
Com
Indeterminate
28
Com
Indeterminate
29
Com
Indeterminate
30
Com
Indeterminate
31
Com
Indeterminate
Alarm type = xDSL (38); Index1 = ifIndex (of xDSL physical port), Index2 = not used
0
No defects
Com
Minor
Com
Minor
Com
Minor
Com
Minor
(9 of 17)
TAP 104-11
Edition 02 Released
Description
No.
Class
Severity
SA
Activation failure
configuration error
Com
Critical
Applies to
7302
7330
(line-config)
6
Activation failure
configuration not
feasible (line-capacity)
Com
Major
Com
Minor
(near-end-bitrate)
8
Com
Minor
Com
Minor
10
Com
Minor
11
Com
Minor
12
Com
Minor
13
Com
Minor
(xdsl-fe-lol)
14
Com
Minor
15
Com
Minor
16
Activation failure
Communication problem
Com
Major
Com
Minor
(xdsl-init)
17
Activation failure No
peer modem detected
(peer-modem)
18
Com
Minor
19
Com
Minor
20
Com
Minor
Alarm type = xDSLTca (39); Index1 = ifIndex (of xDSL physical port), Index2 = not used
0
No defects
QoS
Minor
(10 of 17)
TAP 104-12
Edition 02 Released
Class
Severity
SA
QoS
Minor
QoS
Minor
7302
7330
(xtca-ne-ses)
3
Applies to
Description
(xtca-ne-uas)
4
QoS
Minor
QoS
Minor
(xtca-ne-day-ses)
6
QoS
Minor
QoS
Minor
QoS
Minor
QoS
Minor
QoS
Minor
QoS
Minor
QoS
Minor
(xtca-fe-ses)
9
10
11
12
Alarm type = eoConversion (50); Index1 = 100BASE-FX port identification (1 to 4 for ISAM), Index2 = not used
0
No defects
Equip
Major
Equip
Major
(loss-of-signal)
2
(11 of 17)
TAP 104-13
Edition 02 Released
Description
Class
Severity
SA
Applies to
7302
7330
Alarm type = bonding (54); Index1 = IfIndex (of bonding group), Index2 = not used
0
No defects
Com
Minor
(up-plan-bitrate)
2
Com
Minor
Com
Major
Bonding group
downstream planned bit
rate threshold
Com
Minor
Com
Minor
Com
Major
Com
Minor
Com
Minor
(down-plan-bitrate)
5
Bonding group
downstream minimum
bit rate threshold
(down-min-bitrate)
Bonding group
downstream
configuration not
feasible
(down-config-not-feas)
Bonding group no
bonding CPE connected
(no-bonding-cpe)
Alarm type = authentication (55); Index1 = ifIndex of interface on which authentication occurs (for example, the bridge
port interface for 802.1x, the PPPoE interface for PPPoE), Index2 = not used
0
1
No defects
Proc
Major
(vrf-assign-fail)
(12 of 17)
TAP 104-14
Edition 02 Released
Class
Severity
SA
Proc
Major
(vlan-assign-fail)
IP Address pool
assignment failure
Proc
Major
QoS parameters
assignment failure
Proc
Major
IP address assignment
failure
Proc
Major
Missing attributes
Proc
Major
(rad-pool-id)
(ip-addr-assign-fail)
7330
(qos-assign-fail)
7302
(ip-pool-assign-fail)
Applies to
Description
Alarm type = IpoX (68); Index1 = ifIndex of IpoX interface on which session takes place, Index2 = not used
0
No defects
(13 of 17)
TAP 104-15
Edition 02 Released
Description
No.
Class
Severity
SA
IP address preempt
Com
Major
(ip-addr-preempt)
Applies to
7302
7330
Alarm type = SFP (76); Index 1 = ifIndex of IPoX interface on which the session takes place, Index 2 = not used
0
No defects
Com
Critical
Com
Critical
Com
Critical
Com
Critical
Com
Critical
(host-sfp-los)
2
(host-sfp-ctrl-fail)
Alarm type = SFP (76); Index 1 = eqptSlotId of corresponding LSM in ES, Index 2 = not used
0
No defects
11
Com
Critical
Com
Critical
Com
Critical
Com
Critical
Com
Critical
(exp-sfp-los)
12
13
14
15
Alarm type = LLURelay (78); Index 1 = eqptSlotId (index in equipment board table), Index 2 = not used
0
No defects
Com
Major
(wrong-or-no-applq)
(14 of 17)
TAP 104-16
Edition 02 Released
Applies to
Description
Class
Severity
SA
7302
7330
Alarm type = SHDSL_ISAM (82); Index1 = IfIndex (of SHDSL physical port), Index2 = linkID (higher 16 bits) + device
ID (lower 16 bits)
0
No defects
Alarm type = CustomExternalAlarms (83); Index1 = eqptSlodId (index in equipment board table), Index2 = not used
0
No defects
CustomizableExternalAl
arm1 (ext-alarm1)
Equip
Major
CustomizableExternalAl
arm2 (ext-alarm2)
Equip
Major
CustomizableExternalAl
arm3 (ext-alarm3)
Equip
Major
CustomizableExternalAl
arm4 (ext-alarm4)
Equip
Major
CustomizableExternalAl
arm5 (ext-alarm5)
Equip
Major
Alarm type = PlugInUnit2 (84); Index1 = eqptSlotId (index in equipment board table), Index2 = not used
0
No defects
Fan
Equip
Major
Equip
Major
Equip
Major
Equip
Critical
Equip
Critical
(fan-alarm)
2
DC A
(dc-a-alarm)
DC B
(dc-b-alarm)
Dying gasp
(dg-alarm)
Alarm type: LANX (51); Index1 = not used, Index2 = not used
0
No defects
Eqp
Major
Eqp
Major
Eqp
Major
Eqp
Major
(power-fan)
3
Emergency reboot
(emergency-reboot)
(15 of 17)
TAP 104-17
Edition 02 Released
Description
No.
Class
Severity
SA
LANX SNTP
Communication Lost
Eqp
Major
Com
Major
(sntp-comm)
6
Applies to
7302
7330
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
0
No defects
Com
Critical
(link-down)
3
COM
Minor
(mac-conflict)
Alarm type = OSPF (69); Index 1 = VRF-ID (VRF unique ID), Index 2 = see specific alarm number
0
No defects
OSPF interface
configuration error
Com
Minor
(config)
OSPF interface
authentication error
Com
Minor
(authen)
Com
Critical
(rcv-bad-pkt)
4
OSPF LSDB
approaching overflow
Com
Major
(lsdb-90)
5
Com
Major
(lsdb-ovfl)
(16 of 17)
TAP 104-18
Edition 02 Released
Class
Severity
SA
Com
Minor
(nhbr-statchg)
7
Applies to
Description
7302
7330
Minor
(nhbr-itfchg)
Alarm type = RIP (70); Index1 = VRF ID (VRF unique ID), Index2 = interface index
0
No defects
RIP interface
configuration error
Com
Minor
RIP interface
authentication error
Com
Minor
Com
Minor
(auth-fail)
3
(config-err)
2
Alarm type = LANXuplinkgroup (75); Index1 = uplink group number, Index2 = not used
0
No defects
Com
Major
(uplink-down)
(17 of 17)
Notes
(1)
The alarm names are listed exactly as they appear in the CLI configure command. Note that the term board as it appears
in the CLI alarms is referred to as either unit or card throughout the 7330 ISAM FTTN documentation; for example, the
ECNT-A card is a type of NT unit and the EVLT-A card is a type of LT unit.
(2)
No rack shutdown occurs on an ARAM-D shelf that has the following PWIO-B cards installed: 3FE 24323 AC or
3FE 24323 AD.
(3)
See the Duplicate Mac Alarm Status command in the CLI Commands document for more information.
Description
Recommendation
persist-data-loss
Reconfigure system.
sntp-comm-lost
nt-disk-90%full
(1 of 11)
TAP 104-19
Edition 02 Released
Description
Recommendation
No.
preferred-mode
timing-reference
shub-loc
25
BackPanel-type invalid
(back-pnl-inv)
lost
28
rack-power
Rack power
rack-fan-unit1
Rack fan 1
rack-fan-unit2
shelf-type-mismatch
Shelf-type mismatch
Check equipment.
Check configuration.
ext-chain-instl
shelf-missing
Shelf missing
15
door
Door
17
fuse
Fuse
Check fuse.
Check power feed.
18
single-fan-fail
Single fan
19
double-fan-fail
20
ac-power-fail
board-mismatch (1)
Board-type mismatch
Check configuration.
sw-download
Check configuration.
Download software.
temperature
Temperature exceeded
(2 of 11)
TAP 104-20
Edition 02 Released
12
temp-shutoff
Description
Temperature shutdown
Recommendation
13
defense
Defense
Replace unit.
board-present (1)
Board missing
15
board-inserted (1)
Insert unit.
16
board-init (1)
Board initialization
17
number-of-resets
28
sem-power-fail
SEM AC fail
29
sem-ups-fail
SEM PS fail
30
board-reset-cf (1)
31
shub-uplink
cell-discard-up
cell-discard-down
mac-conflict
custom1
Customizable alarm 1
custom3
Customizable alarm 2
custom3
Customizable alarm 3
custom4
Customizable alarm 4
custom5
Customizable alarm 5
11
he-custom1
HE Customizable alarm 1
12
he-custom2
HE Customizable alarm 2
13
he-custom3
HE Customizable alarm 3
14
he-custom4
HE Customizable alarm 4
15
he-custom5
HE Customizable alarm 5
16
he-custom6
HE Customizable alarm 6
(3 of 11)
TAP 104-21
Edition 02 Released
Description
Recommendation
loss-swo-cap
ether-linkdown
sw-rollback
db-rollback
der-temp1
der-temp2
der-temp3
der-temp4
der-temp5
der-temp6
der-temp7
der-temp8
der-temp9
10
der-temp10
11
der-temp11
12
der-temp12
13
der-temp13
14
der-temp14
(4 of 11)
TAP 104-22
Edition 02 Released
15
der-temp15
Description
Recommendation
16
der-temp16
17
der-temp17
18
der-temp18
19
der-temp19
20
der-temp20
21
der-temp21
22
der-temp22
23
der-temp23
24
der-temp24
25
der-temp25
26
der-temp26
27
der-temp27
28
der-temp28
29
der-temp29
30
der-temp30
31
der-temp31
der-spa1
der-spa2
der-spa3
(5 of 11)
TAP 104-23
Edition 02 Released
der-spa4
Description
Recommendation
der-spa5
der-spa6
der-spa7
der-spa8
der-spa9
10
der-spa10
11
der-spa11
12
der-spa12
13
der-spa13
14
der-spa14
15
der-spa15
16
der-spa16
17
der-spa17
18
der-spa18
19
der-spa19
20
der-spa20
21
der-spa21
22
der-spa22
23
der-spa23
(6 of 11)
TAP 104-24
Edition 02 Released
24
der-spa24
Description
Recommendation
25
der-spa25
26
der-spa26
27
der-spa27
28
der-spa28
29
der-spa29
30
der-spa30
31
der-spa31
xdsl-ne-los
xdsl-ne-lof
xdsl-ne-lom
xdsl-ne-ese
line-config
line-capacity
near-end-bitrate
xdsl-ne-ncd
xdsl-ne-lcd
10
xdsl-fe-los
11
xdsl-fe-lof
12
xdsl-fe-lpr
13
xdsl-fe-lol
14
xdsl-fe-lom
15
xdsl-fe-ese
16
xdsl-init
(7 of 11)
TAP 104-25
Edition 02 Released
17
peer-modem
Description
Recommendation
18
far-end-bitrate
19
xdsl-fe-ncd
20
xdsl-fe-lcd
xtca-ne-es
xtca-ne-ses
xtca-ne-uas
xtca-ne-day-es
xtca-ne-day-ses
xtca-ne-day-uas
xtca-fe-es
xtca-fe-ses
xtca-fe-uas
10
xtca-fe-day-es
11
12
xtca-fe-day-ses
xtca-fe-day-uas
loss-of-signal
transmission
up-plan-bitrate
up-min-bitrate
(8 of 11)
TAP 104-26
Edition 02 Released
up-config
Description
Recommendation
down-plan-bitrate
down-min-bitrate
down-config-not-feas
no-peer-cpe
no-bonding-cpe
vrf-assign-fail
vlan-assign-fail
ip-pool-assign-fail
qos-assign-fail
ip-addr-assign-fail
rad-pool-id
Missing attributes
ip-addr-preempt
IP address preemption
host-sfp-los
host-sfp-tx-fail
host-sfp-not-prst
host-sfp-inv-id
host-sfp-ctrl-fail
11
exp-sfp-los
ES SFP LOS
12
exp-sfp-tx-fail
ES SFP Tx fail
13
exp-sfp-not-prst
ES SFP missing
14
exp-sfp-inv-id
(9 of 11)
TAP 104-27
Edition 02 Released
15
exp-sfp-ctrl-fail
Description
Recommendation
wrong-or-no-applq
ext-alarm1
ext-alarm2
ext-alarm3
ext-alarm4
ext-alarm5
fan-alarm
REM fan
dc-a-alarm
REM DC A
dc-b-alarm
REM DC B
dg-alarm
apsf-alarm
fan
power-fan
db-restore
emergency-reboot
Emergency reboot
sntp-comm
arp-reply
link-down
mac-conflict
(10 of 11)
TAP 104-28
Edition 02 Released
Description
Recommendation
config
authen
rx-bad-pkt
lsdb-90
lsdb-ovfl
nhbr-statchg
nhbr-itfchg
config-err
auth-fail
rcv-bad-pkt
uplink-down
(11 of 11)
Notes
(1)
The alarm names are listed exactly as they appear in the CLI configure command. Note that the term board as it appears
in the CLI alarms is referred to as either unit or card throughout the 7330 ISAM FTTN documentation; for example, the
ECNT-A card is a type of NT unit and the EVLT-A card is a type of LT unit.
TAP 104-29
Edition 02 Released
(2)
No rack shutdown occurs on an ARAM-D shelf that has either of the following PWIO-B cards installed: 3FE 24323 AC or
3FE 24323 AD.
(3)
See the Duplicate Mac Alarm Status command in the CLI Commands document for more information.
TAP 104-30
Edition 02 Released
Training (TNG)
Edition 02 Released
Edition 02 Released
Forwarding Modes
Dynamic MAC Learning and Static Unicast MAC Addresses
MAC Learning Rules
MAC Learning on SHub and LT board (LIMs)
MAC Learning and Unicast Configuration
SHub MAC Filters
TNG 100-1
Edition 02 Released
Forwarding Modes
The system has the following forwarding modes:
TNG 100-2
Edition 02 Released
Edge
EMAN
ISAM
CPE
I-Bridge
VRF
Bridge
I-Bridge
IP subnet
IP address
Figure TNG 100-2: IP Routing
Edge
EMAN
ISAM
CPE
IP
Router
VRF
Bridge
IP
Router
IP subnet
IP address
TNG 100-3
Edition 02 Released
Edge
EMAN
ISAM
CPE
IP
Fwder
Bridge
VRF
IP
Fwder
IP subnet
IP address
Deleting a VLAN on the LT board is impossible unless all egress ports have been
removed from the VLAN. There is no such restriction for the SHub.
MAC 'X' is learned on ASAM port. If packets with the same MAC address appear later
on the control port, then MAC 'X' is learned on the control port and the same entry is
removed from the ASAM port.
MAC 'X' is learned on ASAM port 1. If packets with same MAC address appear on
the USER port, then if MAC movement is enabled for the VLAN, the MAC address is
learned on the USER port. Otherwise, a duplicate alarm is raised and that particular
stream is discarded on the USER port.
TNG 100-4
Edition 02 Released
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.
LT board (LIM)
NA
TNG 100-5
Edition 02 Released
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.
TNG 100-6
Edition 02 Released
TNG 101-1
Edition 02 Released
a DSL interface
an ATM PVC on a DSL interface
a PPPoE session
a VLAN
an IP interface
The basic paradigm of subscriber SLA enforcement revolves around applying the correct
policies to the subscriber SAP. Therefore, the solution is to attach QoS rules to such
SAPs.
Logical Flow
Type
QoS Policer
Profile Up
QoS Policer
Profile Down
QoS Marker
Profile Up
Qos Policy
List Up
Qos Policy
List Down
Supported
Markers
Supported
Filters
Remarks
Generic
all
L2, L3
PVC
all
(L2, L3)
802.1x session
all
PVC.VLAN
all
L2, L3
(for cross-connect
mode only)
PPP
all
L3
IP
all
L3
IPoE VLAN CC
all
L2, L3
(1 of 2)
TNG 101-3
Edition 02 Released
Logical Flow
Type
Supported
Markers
Supported
Filters
Remarks
PPPoE VLAN CC
single dot1p
L2
PPPoA CC
single dot1p
IPoE IBridge
all
PPPoE IBridge
single dot1p
PPPoA relay
single dot1p
IPoE IP-aware
Bridge
all
L3
IPoA IP-aware
Bridge
all
L3
(2 of 2)
To create a QoS Session profile via CLI, use the following command:
> configure qos profile session <qosSessionProfileName> log-flow-type
<flowType>
Committed Information Rate (CIR): designates the token accumulation rate in Kbit/s
Committed Burst Size (CBS): designates the maximum token count in the bucket
Note The big tolerance for small rate is caused by unit conversion.
The CIR unit in NP is KBytes, so integers are accepted. Values are
rounded up. As such, any roundup value will have a tolerance of
0.00000...01 to 0.9999...9 KBytes, which is obvious for small rate.
Example: take a CIR of 10 Kbit. This corresponds to 1.25 KB (=10/8). The
roundup value becomes to 2 KB in NP.
The actual result is 8 x 2KB = 16Kbits. This matches the actual CIR value
in NP.
For other CIR values: see Table TNG 101-2.
Table TNG 101-2: Upstream Policer Characterization
CIR
CBS
Result
CIR in HW
Description
10K
1600
16K
16K
100K
1600
104K
102K
300K
1600
305K
297K
500K
1600
506K
492K
800K
1600
690K
781K
1000K
1600
690K
977K
1500K
1600
690K
1469K
TNG 101-5
Edition 02 Released
Basic concepts
In principle there is always a dominant entity that determines the code points to be
applied on a frame. Such entities are for example: a parent bridge port, port default VLAN,
ingress DSCP, ingress P-bits, or other header information (see marking based on
sub-flow policies 4.7). One notable exception is when the port is trusted. For trusted ports
received frames will keep their DSCP and P-bits, and un-tagged frames will get code
point P=0 in the 802.1q header.
Note that a port default P-bit marking can be configured on bridge ports even in the
absence of a QoS Session profile. The convention is that the QoS Session profile
provided it contains a marker for P-bits has precedence over a bridge port-based
default. Also note, that there is a system-wide switch that determines whether code points
are derived from bridge-port default settings or are VLAN-based.
> configure vlan priority-policy <vlan-specific | port-default>
Last, setting the DSCP is not supported for non-IP packets (including when IP packets
are bridged with PPP-encapsulation). For such packets, the set-DSCP rule is
automatically skipped.
TNG 101-6
Edition 02 Released
Marker Type
Default P-bits
DSCP
DSCP Contract
Table
DSCP-to-P-bits
Alignment Table
TNG 101-7
Edition 02 Released
P-bits
DSCP
DSCP
Contract
Table
Alignment
Flag
Comments
singleDot1P
singleDscp
dscpContract
dot1PandDscp
dot1PandDscp
Contract
dscpToDot1P
Alignment
In general, a code point can suffer multiple alterations, but this is not the purpose. P-bits
can be set port-based, then altered in the policy processor block. Also, P-bits specified
by the policy processor could be altered by the alignment. This is not the intention.
The intention is to set either both code points in one shot according to the determining
entity (like parent port) or mark the incoming DSCP with a contract table and align P-bits
to it. The complex things are there not to be used for simple cases, but to suit the needs
of special deployment scenarios.
TNG 101-8
Edition 02 Released
L2 and L3 Filters
L2 and L3 filters are stored as profiles, and are reusable in both upstream and
downstream direction. Filters are multi-field classifiers. In other words, they contain a set
of protocol headers, where each can be enabled or ignored or partially masked. However,
the total evaluation of the fields is an AND function. Therefore a full-match is required.
When an OR function is desired, several sub-flow policies can be used to achieve the
desired behavior (see Policy Sharing).
Figure TNG 101-3: L2 and L3 Filter Structure
L2 Filter
L3 Filter
Address Type
MAC DA Prefix
IP Destination Address
IP DA Prefix
MAC SA Prefix
IP Source Address
Ethertype
IP SA Prefix
P-bits
DSCP
CFI bit
Protocol Type
VLAN ID
MAC address prefixes in L2 filters can be used for ACL functionality, for instance to
specify a certain category of access boxes (like a residential gateway or STB of a certain
type from a specific vendor). To specify a L2 policy that applies for all ingress frames,
mask out the complete source or destination MAC address.
TNG 101-9
Edition 02 Released
Policy Action
Default Disposition
Set DSCP
Set P-bits
Police
Sharing
TNG 101-10
Edition 02 Released
Setting the DSCP is only supported for IP frames (which includes terminated PPP
sessions, since the system does have an IP interface at hand). Setting DSCP is not
supported for bridged PPP traffic, as well as for SAPs at layer 2 that are not yet supported
by the policy framework.
Policing a certain sub-flow means that the selected traffic is not subject to the port-level
policer. Therefore is a SAP has a port policer of 1Mbps and two sub-flow policies of
100Kbps, then the total traffic that can pass is 1.2Mbps. However, if the sub-flow policy
does not contain policing, then the frame is subject to the port policer. This concept is
some times referred as policer inheritance, which applies also across service access
points that are on top of each other (like PPP sessions over a bridge port). Marking and
sub-flow policies are not inherited across SAPs.
Policy Sharing
There are cases when a certain policy should apply to a set of micro-flows within a SAP
that is difficult or impossible to capture with one filter. If this is the case when the policy
is to apply an upper bound on the bandwidth to be used in common by such micro-flows,
then policy sharing comes to help.
Basically, policy sharing if enabled will cause the policies within a QoS Session profile
that use the same Policy Action profile in the same direction more than once to share the
instantiated policer. This way a common upper bound is placed on the rate of a set of
ingress flows. It makes no sense to use policy sharing if no policer is named inside the
policy action profile.
TNG 101-11
Edition 02 Released
Global Table
DSCP to
P-bits
alignment
Set P and
DSCP for
Yes subflow if
specified
Port default
DSCP
Yes
Alignment
enabled?
Filter
match?
(4)
(3)
Yes,
port
default
No, (2)
trusted DSCP
set?
DSCP
contract
table
Yes,
contract
P-bit contract
table
Yes,
untrusted
As mentioned earlier, in a typical deployment scenario only a small fraction of all this is
needed. For instance, it is rather common to set only a port default P-bit value.
Downstream marking is typically not done in the DSLAM. The ISAM can do downstream
P-bit and DSCP modification via the policy processors, but there are no explicit means to
do session-based downstream marking. If for some reason this is required, a
downstream generic filter has to be defined with action to modify the desired code point
to the desired value.
untagged frames from user, where a port default P-bit is always applied
tagged or priority tagged frames where correct P-bit marking is enforced via a P-bit
contract table.
Port default P-bits can be configured also without a QoS profile, simply by configuring a
P-bit on the bridge port level or using VLAN-based defaults. In case a QoS Session profile
is attached that contains P-bit settings, this latter will overwrite port or VLA-based
defaults.
P-bit contract table is not yet possible to specify within a QoS marker profile, and only
possible to configure on top of bridge ports (so no IP interfaces).
TNG 101-12
Edition 02 Released
TNG 101-13
Edition 02 Released
Configuration Example
This section explains the steps required to create and configure a QoS Session profile
and its components through an example.
Figure TNG 101-6: The QoS Session profile and component objects
QoS Session Profile
Logical Flow
Type
QoS Policer
Profile Up
QoS Policer
Profile Down
QoS Marker
Profile Up
Qos Policy
List Up
Qos Policy
List Down
1..16
QoS Policer
Profiles
1..4
Qos Policy
Table
QoS Marker
Profiles
or
L2 Filter
Table
L3 Filter
Table
Policy Action
Table
Example: Create a multi-QoS Session profile for an IP-aware bridge interface, with voice
traffic limited in both direction to 100Kbps, VoD control traffic with enhanced priority and
to limit the rest of traffic to 3Mbps downstream and 256Kbps upstream.
Before we create the session profile, it is required that the components are created first.
Step 1: Create the Policer profiles
Create a Policer profile for upstream rate limitation for the service access point to
256Kbps, with burst tolerance of 32 Kbytes:
> configure qos profiles policer ppUsSap256k committed-info-rate 256
committed-burst-size 32000
Create a Policer profile for downstream rate limitation for the service access point to
3Mbps, with burst tolerance of 96 Kbytes:
> configure qos profiles policer ppDsSap3M committed-info-rate 3000
committed-burst-size 96000
Create a Policer profile for voice rate limitation to 100Kbps, with burst tolerance of 3
Kbytes:
> configure qos profiles policer ppVoice100k committed-info-rate 100
committed-burst-size 3000
TNG 101-14
Edition 02 Released
Downstream we could use the same address for the IP destination addresses, or the
used DiffServ code point. We choose to use the IP subnet.
> configure qos profiles l3-filter f3pDsVoiceIp dst-ip-addr
192.170.0.0/16
To identify VoD control packets upstream we can use the IP destination address of the
VoD portal (e.g.: 192.180.2.2):
> configure qos profiles l3-filter l3pUsVodIp dst-ip-addr
192.180.2.2/0
The same IP address (this time as source) we can use for identifying VoD control traffic
in the downstream direction:
> configure qos profiles l3-filter l3pDsVodIp src-ip-addr
192.180.2.2/0
For VoD, the policy action is simply to raise it out of the BE traffic class, which can be
again used both upstream and downstream.
> configure qos profiles policy-action apVod dot1p-value 3
TNG 101-15
Edition 02 Released
The VoD policy used the VoD filters to simply set the code point to 3. Upstream this will
cause packets being marked with P-bit = 3, downstream it will cause the packet being
redirected to the controlled load queue.
> configure qos profiles policy pcyUpVod policy-action name:apVod
filter l3-name:l3pUsVodIp
> configure qos profiles policy pcyDnVod policy-action name:apVod
filter l3-name:l3pDsVodIp
Remarks:
1
VoD control traffic - although treated via a sub-flow policy for marking - is still policed
with the entire session. This may cause that from time to time subscriber data traffic
consumes the allowed bandwidth for the session and VoD control traffic will be
impacted as well. This will not happen to voice traffic, since the voice policy contains
a dedicated policer. Therefore, it may be useful to add a policer to the VoD subflow
policy such that the session-based policer does not apply to VoD control frames.
Although some of the profiles can be reused for many building blocks, it may be wise
to reuse them only when they refer to the same entity. Example, the reuse of the
voice policy in many session profiles is probably wise to do. If it has to change (e.g.,
the rate or the filter IP address) it is likely that most of them will change. However,
reusing the upstream policer on the session profile for the downstream policing of the
VoD control traffic may cause some complications if later one or the other has to
change.
TNG 101-16
Edition 02 Released
iSAM 7300
or
7330 FTTN
Internet
Video
server
TNG 102-1
Edition 02 Released
port index:
Ranges from 1/1/3/0 to 1/1/18/47
VCI:
Ranges from 0 to 4095
VPI:
Ranges from 32 to 65535
Refer to the 7302 ISAM CLI Command and Messages document for a description of all
parameters.
TNG 102-2
Edition 02 Released
TNG 102-3
Edition 02 Released
Description
TNG 102-4
Edition 02 Released
VBAS Query
VBAS sends a VBAS Query Packet to the system to gather physical-port information
corresponding to the MAC address of the new subscriber.
VBAS Response
Upon receiving the request packet, the system sends a VBAS Response Packet to
the BAS. This packet includes the physical-port information of the new subscriber.
All VBAS packets carry a destination. If the packet is not destined for a specific system,
it will forward the packet to all subtending systems until it has reached its intended
destination.
In normal operation, the network port towards the BAS is tagged. This means that the
network port is able to process and respond to tagged VBAS frames.
If untagged packets are to be handled, then the network port is explicitly set as untagged.
Also a PVID is configured for the port. When the system receives a VBAS query, user
information is retrieved from the VLAN configured as PVID.
VBAS Configuration
No specific VBAS configuration as such is necessary on this system. However, as an
Operator, you need to make sure that the network port is configured in order to properly
communicate with the BAS.
There are two modes in which the network port can operate: tagged or untagged.
TNG 103-1
Edition 02 Released
Example
A user with MAC address 00-B0-D0-BC-D5-D3 is connected to slot 7, port 23 on LIM1.
LIM1 is connected to ASAM port 1. The VLAN configured for the user is VLAN 100 on
both LIM and SHub.
When the VBAS request arrives from the server on the SHub, the MAC address of the
user is retrieved in VLAN 100. Since the user MAC address is learned in VLAN 100, the
request is forwarded to LIM1.
LIM1 replies with VBAS response containing user information such as the slot and port
number. The SHub forwards the VBAS response to the server.
The process is shown in Figure TNG 103-1.
Figure TNG 103-1: VBAS Example
ISAM/L Shub:
06.00.00.00.00.80
ETHERNET
VBAS
Req
VBAS Resp:
DA: 02.00.40.00.00.80
VL AN: 100
User: 00.b0.d0.bc. d5.d3
VBAS
Resp
User:
MAC: 00.b0.d0.bc. d5.d3
Slot: 2
Port: 23
VLAN: 100
TNG 103-2
Edition 02 Released
iSAM 7302
or
7330 FTTN
Internet
DHCP
server
Upstream packet
Downstream
17704
TNG 104-1
Edition 02 Released
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.
Description
Relaying
Server
Server IP
secs-threshold/hops-threshold
TNG 104-2
Edition 02 Released
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.
Description
See the CLI Commands and Messages document for more information on these
commands.
TNG 104-3
Edition 02 Released
TNG 104-4
Edition 02 Released
The system downloads the overall descriptor files and stores it persistently.
The system downloads the software files that are specified in the downloaded overall
descriptor files on condition that sufficient resources are available for their persistent
storage.
The manager has the possibility to monitor the progress of the download process with
granularity.
TNG 105-1
Edition 02 Released
In case there are no exceptions, finally the system will have two OSWPs:
Abort an OSWP
The manager can abort an OSWP when the system has 2 OSWPs. The status of the first
OSWP is Enabled/Active/Committed while the second one will be in one of the following
three states:
Enabled/NotActive/UnCommitted
Downloading/NotActive/UnCommitted
Disabled/NotActive/UnCommitted.
The management channel between the system and the manager is established and the
system is not involved in any other SW download process.
The manager requests the system to remove the NotActive/UnCommitted OSWP. The
system removes all the persistent stored files and databases not related to the
Enabled/Active/Committed OSWP. The status of the OSWP to be removed will be
Aborting/NotActive/UnCommitted during the complete remove operation.
After the abort is successful the system will have only one OSWP. The status of this
OSWP will be Enabled/Active/Committed. Only files and databases related to this OSWP
are stored persistently in the system.
The system selects the database that is compatible with and linked to the
Enabled/NotActive OSWP among the available databases.
TNG 105-2
Edition 02 Released
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.
After commit is successful, the system will have only one OSWP. The status of this
OSWP is Enabled/Active/Committed. Only files related to this OSWP are stored
persistently in the system.
TNG 105-3
Edition 02 Released
TNG 105-4
Edition 02 Released
TNG 106-1
Edition 02 Released
TNG 106 Specifying 7330 ISAM FTTN remote expansion units using the CLI
Rack #2
Rack #3
Shelf #1
Shelf #1
Shelf #1
Shelf #2
Shelf #2
Shelf #2
Shelf #3
Shelf #3
Shelf #3
18027
Rack 1 must always contain the host 7330 ISAM FTTN ARAM-D shelf in the topmost
position and the host shelf must be assigned rack 1, shelf 1. Up to five ES can be installed
in racks 1 and 2. Rack 3 is reserved for the SEM. Although the SEM is a remote
expansion module and not a shelf, the 7330 ISAM FTTN system and management
software identifies each SEM according to the rack and shelf designation shown in
Figure TNG 106-1.
The SEM will nearly always be installed in remote locations, away from the host shelf that
is installed in the CO. Expansion shelves can be co-located with the host shelf or be
installed in remote locations. As such, racks 2 and 3 are virtual racks. This means that
they do not necessarily need to be physical racks installed in the same CO location as
rack 1, which contains the host shelf. Shelves 2 and 3 in rack 1 can also be assigned to
remotely located ES.
Note You can assign expansion shelves to rack 1 and rack 2 only.
Rack 3 is reserved for SEM remote expansion units.
For the ES, rack and shelf assignments are derived from the shelf jumper settings. For
the SEM, the rack and shelf assignment is derived from the downlink port on the GENC-E
or GENC-F card to which the SEM is connected. Rack and shelf assignments for
downlink ports are configurable using CLI.
TNG 106-2
Edition 02 Released
TNG 106 Specifying 7330 ISAM FTTN remote expansion units using the CLI
When you connect a SEM to downlink ports 8, 9, or 10 on the GENC-E or GENC-F card,
the SEM is automatically assigned rack 3, shelf 1, 2, or 3 respectively. Only downlink
ports 8, 9, and 10 automatically assign a rack and shelf ID to the SEM. The jumper
settings of the ES override the default rack and shelf assignments of downlink ports 8, 9,
and 10 without requiring configuration using CLI.
After an ES is connected to a downlink port and is operational, swapping expansion link
cables disrupts communications over the affected expansion links and an alarm is raised
in the system software. If the rack and shelf assignment for a downlink port is already
configured using CLI and you connect a remote LT unit from an ES that has a different
rack and shelf jumper setting, an alarm is raised and the remote LT unit does not come
in to service. If you connect a remote LT unit from an ES to downlink ports 8, 9, or 10 after
a SEM unit was previously connected and commissioned, an alarm is raised and the
remote LT unit does not come in to service.
Using the CLI, you can change the shelf and rack ID assignments for all downlink ports
on the GENC-E or GENC-F card. Configuration using the CLI overrides the default rack
and shelf assignments of downlink ports 8, 9, and 10. Do not change shelf and rack ID
assignments using CLI after remote expansion units are connected and operational.
Service disruptions will result and an alarm is raised. Service and port configurations are
mapped to the optical expansion link. All affected port and service configurations that
were affected will require reconfiguration.
TNG 106-3
Edition 02 Released
TNG 106 Specifying 7330 ISAM FTTN remote expansion units using the CLI
For shelves, you must enter the LT slot number that contains the card you want to
configure. For a horizontally mounted ARAM-D shelf, the bottommost LT slot is LT1. The
LT slot number increments for each successive LT slot in the shelf. The topmost LT slot
in a horizontally mounted shelf is LT4.
Table TNG 106-1 lists the ES shelf contents and indicates what you must enter using the
CLI to reference a specific slot. The orientation of the table rows is the same as the slots
of a horizontally mounted ARAM-D shelf, where the GFC slot has the topmost position in
the shelf and slot LP1 has the bottommost position.
Table TNG 106-1: ES slot designations for CLI
Slot type
ES slot content
Slot identifier to
enter using CLI
GFC
PWIO-B card
ATI
SATU-A card
NT slot B (NTB)
Filler plate
NT slot A (NTA)
EDSE-A card
LT slot 4 (LT4)
LT slot 3 (LT3)
LT slot 2 (LT2)
LT slot 1 (LT1)
LP slot 4 (LP4)
LP slot 3 (LP3)
LP slot 2 (LP2)
LP slot 1 (LP1)
Subscriber ports are uniquely identified by the rack, shelf, slot, and port number. The port
number is determined by the cable pinout when subscriber lines are connected to the
applique installed in the shelf, or to the SEM xDSL drop line break-out cable.
TNG 106-4
Edition 02 Released
TNG 106 Specifying 7330 ISAM FTTN remote expansion units using the CLI
TNG 106-5
Edition 02 Released
TNG 106 Specifying 7330 ISAM FTTN remote expansion units using the CLI
TNG 106-6
Edition 02 Released
Re-initialization triggers
VDSLx configuration management
Line operation configuration
VDSLx common configuration parameters
Flavor-dependent configuration parameters
Flavor-specific configuration parameters
Supported operational data parameters
TNG 107-1
Edition 02 Released
Re-initialization triggers
During showtime (L0 line state), the VDSLx Modem Subsystem performs
persistency/severity checking and correlation on the defects/anomalies, in order to detect
re-initialization triggers. Table TNG 107-1 lists them for the VTU-O and includes the
required persistency time for each showtime error.
Table TNG 107-1: Re-initialization triggers
Related Defect/Anomaly
Far-End
(f)los
5 1 sec
6 1 sec
sef/rdi
5 1 sec
6 1 sec
(f)lom
60 1 sec
60 1 sec
(f)se
10 1 sec
10 1 sec
(f)ncd
15 1 sec
17 1 sec
(f)lcd
15 1 sec
17 1 sec
(f)npd/(f)lpd
15 1 sec
15 1 sec
The VDSLx modem subsystem triggers/initiates re-activation of the modem when any of
those triggers is fired. No other re-initialization triggers (annex timer values) are used by
the modem subsystem than the ones mentioned in Table TNG 107-1.
All the far-end countdown timers are frozen when any near-end defect occurs. When all
the near-end defects have disappeared, the ar-end count-down timers resume from the
frozen values (ignoring the in-between time).
All the near-end defects are correlated independent from each other. The same holds for
all the far-end defects in absence of near-end defects.
TNG 107-2
Edition 02 Released
In case a parameter is indicated as optional, the input value is do not care, and any
value is accepted without having impact on the modem subsystem behavior.
In case a parameter is indicated to be required to a certain level (for example, only a
limited set of defined number of input values), only input values corresponding to the
required level are accepted. If the input parameter is not accepted, the modem
subsystem raises a failure indication to the xDSL manager indicating Configuration
Error
In case extra consistency checks need to be performed on a parameter or between
parameters and the configuration should be rejected, rejection always means that
the modem subsystem raises a failure indication to the xDSL Manager indicating
Configuration Error, rather that a returned error of the considered xDSL API call.
An xDSL API configuration request is replied with an error only when the call is done
in a wrong administrative state.
TNG 107-3
Edition 02 Released
Operating modes
Rate adaptation mode
Target noise margin
Minimum noise margin
Maximum noise margin
Carrier mask
RF band data
Minimum bitrate
Maximum bitrate
Rate adaptation ratio
Maximum interleaving delay
Minimum impulse noise protection
Band plan:
Custom band plan
Predefined band plan
Maximum number of bands
Maximum usable frequency
ADSL band mode
ADSL band mode end frequency
Optional band mode
Optional band mode end frequency
US power backoff mode
DS G.HS tones power:
DS G.hs tones power mode
DS G.hs tones power manual level
Table TNG 107-2: Operating modes
Name
Operating Modes
Description
Specifies which xDSL standard shall be applicable: ANSI T1.424 (old trial use
standard), ETSI TS 101 270, ITU-T G993.1, IEEE 802.3ah, or ITU-T G.993.2
(VDSL2) different Profiles.
Instances
Line
(1 of 2)
TNG 107-4
Edition 02 Released
Values
Bitmap:
OpModesITU_G993_2_8A_Bit
OpModesITU_G993_2_8B_Bit
OpModesITU_G993_2_8C_Bit
OpModesITU_G993_2_8D_Bit
OpModesITU_G993_2_12A_Bit
OpModesITU_G993_2_12B_Bit
OpModesITU_G993_2_17A_Bit
OpModesITU_G993_2_30A_Bit
OpModesANSI_T1_424Bit
OpModesETSI_TS_101_270Bit
OpModesITU_G993_1Bit
OpModesIEEE802.3ah_Bit
(2 of 2)
Description
Instances
Line DS, US
Values
raModeManual
raModeAtInit
Description
Instances
DS, US
Values
0..31
0.1 dB
TNG 107-5
Edition 02 Released
Description
Instances
DS, US
Values
0..31
0.1 dB
Description
Specifies the maximum noise margin sustained by the modem. This parameter
is both used during initialization and in showtime.
during initialization:
When the noise margin for transport configuration is higher than the
Maximum Noise Margin, then the modem takes action to reduce the
power to get the actual noise margin below this value.
When the noise margin is lower than the Maximum Noise Margin, then
the modem tries to optimize the Receive Power below the configured
masks to get the noise margin as high as possible (still below the
Maximum Noise Margin).
in showtime:
When the current noise margin gets above the Maximum Noise Margin,
the modem attempts to reduce the far-end output power to get the noise
margin below this limit (by means of bit-swap actions).
When the current noise margin gets below the Maximum Noise Margin,
then the ATU attempts to increase the far-end output power (still below
the maximum allowed templates or masks) to get the noise margin as
high as possible (by means of bits-swap actions).
If the Maximum Noise Margin is configured lower than the Target Noise Margin,
the configuration is rejected, and the configuration error failure is raised.
The special value NoMaximumNoiseMargin is interpreted as meaning that no
Maximum Noise Margin limit must be applied.
Other values strictly bigger than 31.0 are converted to the special value
NoMaximumNoiseMargin.
Instances
DS, US
Values
0.1 dB
For clarification, Figure TNG 107-1 gives an overview of the noise margin parameters,
and the required actions from the modem.
TNG 107-6
Edition 02 Released
RF Band Data
Description
Specifies the list of RF bands (HAM band or AM band) for egress control and
ingress cancelling. Band RF type, ingress level and egress control parameters
can be set independently from each other.
Up to 16 bands shall be supported: RFBandi (i = 0..15).
Egress control can be requested and applied in up to 16 bands
simultaneously.Ingress level can be specified for each RF band such that it can
be taken into account by the modem at initialization (usage for RFI cancelling
purposes is vendor discretionary). However, when different ingress settings are
configured for RF bands being in the downstream bandplan (gDS RF bandsh),
the stronger ingress setting shall be assumed for all those DS RF bands.
Instances
Line
(1 of 2)
TNG 107-7
Edition 02 Released
Values
(2 of 2)
Minimum Bitrate
Description
Defines the minimum requested transport bitrate which is set up and which is
maintained during showtime by the VTU.
Instances
Bearer DS, US
Values
0..262143
1 kbit/s
Maximum Bitrate
Description
Defines the maximum allowed transport bitrate which is set up and which is
maintained during showtime by the VTU. This parameter is relevant only in
'atInit' RA Mode. When RA Mode is manual, the Maximum Bitrate parameter
is ignored.
The VDSLx modem subsystem raises failure indication Configuration Error for
configurations where Maximum Bitrate < Minimum Bitrate for one of the
directions in case of the atInit RA Mode.
Instances
Bearer DS, US
Values
0..262143
1 kbit/s
TNG 107-8
Edition 02 Released
Description
The Rate Adaptation Ratio specifies the ratio that should be taken into account
for allocating available data rate (in excess of the minimum data rate summed
over all bearer channels) among the different bearer channels in a given
direction.
The ratio is defined as a percentage from 0 to 100. The sum of the raRatios for
all bearers must be 100.
The excessive bitrate (that is, the available bitrate minus the sum of the
minimum bitrates) must be distributed among the different bearers according to
their respective raRatio.
When the maximum bitrate is achieved for one of the bearers, the raRatio of that
bearer must be distributed to the other bearers according to their respective
raRatio share.
This parameter is only meaningful in case multiple bearers are used (for
example, 2 for dual latency) and is ignored in case of single latency.
Instances
Bearer DS, US
Values
0..100
1%
TNG 107-9
Edition 02 Released
Description
Instances
Values
Bearer DS, US
0..63, and special value onems.
0 is a special value used as don't care indication, that is, the interleaving
delay is not restricted.
1 is a special value used to disable the interleaving (fast mode).
onems is a special value used to select 1 ms maximum interleaving delay.
Other values directly give the maximum impulse noise protection, in
milliseconds.
1 ms
Description
Instances
Bearer DS, US
Values
Description
Specifies custom band plan in case Predefined Band Plan selection (see
Predefined band plan) is set to bandPlanCustom, ignored otherwise. It always
excludes the Upstream or Downstream optional Band control.
Instances
Line
Values
1 kHz
TNG 107-10
Edition 02 Released
Description
Instances
Line
Values
bandPlanCustom: custom defined band plan (see also VDSLx Custom Band
Plan parameter)
bandPlanA: 998 band plan
bandPlanB: 997 band plan
bandPlanC: Fx band plan (see also Fx Band Plan Parameter)
bandPlanAext: ITU-T G.993.2 VDSL2 Annex C band plan
bandPlanChina1: China band plan 1
bandPlanChina2: China band plan 2
bandPlanAnnexA: ITU-T G.993.2 VDSL2 Annex A (extended) band plan
bandPlanAnnexB998E: ITU-T G.993.2 VDSL2 Annex B band plan type 998E
bandPlanAnnexB997E: ITU-T G.993.2 VDSL2 Annex B band plan type 997E
bandPlanAnnexB998ADE: ITU-T G.993.2 VDSL2 Annex B band plan type
998ADE
bandPlanAnnexBHPE: ITU-T G.993.2 VDSL2 Annex B band plan type HPE
Description
Specifies the maximum number of bands to be supported for the given band
plan. In case the selected band plan (see Custom band plan and Predefined
band plan) contains more bands, the modem disables bands located at higher
frequencies first.
Otherwise, this parameter has no effect.
The optional band is NOT counted as a band, and does not take part to the
number of bands (example: if the maximum number of bands is set to 3, the
modem is allowed to use the optional band + DS1 + US1 + DS2).
The special value unlimited disables the maximum number of band constraint.
Instances
Line
Values
unlimited, 2..8
Unit
Bands
TNG 107-11
Edition 02 Released
Description
Specifies the maximum frequency usable both VTU-O and VTU-R VDSL
modems, in showtime.
The special value unlimited disables the maximum usable frequency
constraint.
In case the configuration of this parameter would conflict with other parameters,
the configuration is rejected.
Note: This parameter is not equivalent to the MUF parameter commonly used
when dealing with CO-RT mixed deployment and PSD shaping. This last MUF
parameter is equivalent to the ADSL band mode end frequency parameter.
Instances
Line
Values
Unit
kHz
Description
Specifies whether the VDSLx modem is allowed to use the ADSL spectrum or
not in DS. The end frequency of the ADSL band is specified by the ADSL band
mode end frequency.
It controls the use of the ADSL spectrum within the defined VDSLx band plan,
with the exception of the optional band, which is not impacted by this parameter.
Note: whatever the value of this parameter, the modem is never allowed to
exceed the configured PSD mask (see PSD ceiling).
Instances
Values
Line
0: usage of ADSL spectrum is allowed.
1: usage of the ADSL spectrum is not allowed.
Description
This parameter specifies the ADSL band end frequency. The start frequency is
always 25 kHz. It is used together with parameter 0 (see ADSL band mode).
It controls the use of the ADSL spectrum within the defined VDSLx band plan,
with the exclusion of the optional band, which is only controlled through the
Optional band mode.
This parameter is ignored when the ADSL spectrum usage is allowed.This
parameter is assumed 1104 kHz if no value, or if the special 0 kHz value is
configured.
Instances
Line
Values
0 kHz, 276..2208kHz
1 kHz
TNG 107-12
Edition 02 Released
Description
Instances
Line
Values
Description
When the optional band usage is enabled (see Optional band mode), this
parameter specifies the optional band end frequency. The start frequency is
always 25 kHz on POTS cards, and 138 kHz on ISDN cards.
The beginning of the first DS band is shifted accordingly (no spectrum overlap).
When the optional band usage is disabled, this parameter still fixes the
beginning of the normal DS band. It is assumed 138 kHz if no value, or if the
special 0 kHz value is configured.
Instances
Line
Values
1 kHz
Description
PBO Off (PBO with Transmit PSD Mask): The VTU directly uses the US
PSD Mask parameter (see above) as the transmit PSD mask.
PBO On (PBO with Receive PSD Mask): The VTU derives the transmit PSD
mask from the US Power BackOff PSD Mask parameter.
Instances
Line US
Values
psdPboOff
psdPboOn
TNG 107-13
Edition 02 Released
Description
An NSIF field is introduced for V43 back off communication from VTU-O to
VTU-R. If the final derived value falls below the minimum value handled by the
G.994.1 standard for the considered set, that minimum allowed value is used.
Instances
Line
Values
Si
Si in conservative
mode(1)
A43
TBD dBm/Hz
-65 dBm/Hz
B43
TBD dBm/Hz
-70 dBm/Hz
A43c
TBD dBm/Hz
-70 dBm/Hz
V43
TBD dBm/Hz
-70 dBm/Hz
Notes
(1)
Alcatel will determine if the conservative mode shall be used or not. This has to be hardcoded in the
chipset implementation.
TNG 107-14
Edition 02 Released
Description
This parameter determines the maximum power of DS tones used during G.hs
(handshake) sequence, in case the manual mode is selected. It is defined as an
array of 4 PSD values: one per possibly used DS tone set in VDSLx mode: A43,
B43, A43c, and V43:
GhsPSD = [manual_A43; manual_B43; manual_A43c; manual_V43]
Each value is given in dBm/Hz. The power of each tone of a considered set is
equivalent to the given PSD value integrated in a total bandwidth of 4.3125 kHz.
One special value is defined: the value -99 dBm/Hz indicates that the full set is
not used (that is, no power allowed).
Instances
Line
Values
-99..-40 dBm/Hz
0.5 dBm/Hz
Modem features
Maximum aggregate transmit power
PSD ceiling
Custom MIB PSD Mask
US Power BackOff PSD:
US power backOff PSD mask selection
US power backOff PSD AB parameters
US power backoff PSD full custom parameters
Table TNG 107-26: Modem features
Name
Modem Features
Description
Instances
Line
Values
Bitmap
TNG 107-15
Edition 02 Released
Description
Specifies the maximum total power level that is allowed to be transmitted in the
corresponding direction.
This parameter is used to reduce the maximum allowed PSD derived from
Custom MIB PSD Mask, VDSL 1 Limit Tx PSD mask or VDSL 2 Limit Tx PSD
mask.
Note that this parameter overrules maximum aggregate Tx power standard
restrictions, except if the special value standard is configured.
The special value standard is used as special value:
For VDSL1:
If the selected PSD is referring to a predefined PSD, then the maximum
aggregate transmit power defined in the corresponding DSL standard
must be used, in accordance with the deployment type PSD: FTTEx or
FTTCab.
Otherwise (customized PSD): no power limitation has to be applied.
For VDSL2:
The applicable maximum power constraint is the one corresponding to
the selected VDSL2 profile.
Instances
Line DS, US
Values
0.1 dBm
Maximum PSD
Description
The PSD ceiling parameter specifies the maximum power spectral density level
allowed on the line at the transmitter output (upstream and downstream) for
initialization and showtime signals.
This parameter shall be used to further restrict the maximum Tx PSD mask
derived from Custom MIB PSD Mask, VDSL 1 Limit Tx PSD mask or VDSL 2
Limit Tx PSD mask.
The value no_constraint is used as special value, which avoids restrictions to
the maximum Tx PSD mask.
Note that this parameter is defined on the PSD template, not on the PSD mask.
Instances
Line DS, US
Values
0.1 dBm/Hz
Notes
(1)
The Maximum PSD parameter cannot be used to boost the PSD beyond the configured LimitTxPSD
and MIB Mask (See Custom MIB PSD Mask, VDSL 1 Limit Tx PSD mask or VDSL 2 Limit Tx PSD
mask), it can only be used to put additional constraints, i.e. to further lower the PSD. The modem
supports extended maximum PSD range under to -80 dBm/Hz.
TNG 107-16
Edition 02 Released
Description
Instances
Values
Line DS, US
Up to 20 PSD points can be specified and are supported for US
Up to 32 PSD points can be specified and are supported for DS
PSD point = [Frequency, PSD value]
(1 of 2)
TNG 107-17
Edition 02 Released
Values
(continued)
(2 of 2)
Description
Specifies the maximum receive PSD allowed for the US direction on a VDSLx
line in case of psdPboOn (see US power backoff mode), ignored otherwise.
The VDSLx modem subsystem checks consistency between the PSD Mask
settings and other configuration parameters. If not consistent, the configuration
is rejected by raising the Configuration Error failure (for example, the modem
subsystem rejects configurations with inconsistent DS and US PSD mask
settings).
Instances
US Power BackOff
(1 of 2)
TNG 107-18
Edition 02 Released
Values
psdMaskANSI_A
psdMaskANSI_F
psdMaskANSI_CustomEx (1)
psdMaskANSI_CustomCab (1)
psdMaskETSI_A
psdMaskETSI_B
psdMaskETSI_C
psdMaskETSI_D
psdMaskETSI_E
psdMaskETSI_F
psdMaskETSI_CustomEx (1)
psdMaskETSI_CustomCab (1)
Remarks:
The ANSI noise profiles are not defined yet for types B, C, D and E. The
modem subsystem rejects the configuration of those ones.
The ETSI UPBO masks for noise types A and B are the same.
The modem subsystem rejects the configuration if an ANSI UPBO mask is
used together with the ETSI operating mode, and vice versa (VDSL1 only).
The _CustomEx/Cab masks allow the modem subsystem to use
customized and pre-defined UPBO masks for specific deployment
scenarios.
(2 of 2)
Notes
(1)
This psdMask is outphasing
Description
Specifies the a and b values in order to compute the PSDREF to be used for
USPBO.
If US Power Back Off is psdMaskABParameters, it is applied as follows:
PSDREF(f) = -(a + b f)
They are structured as an array [a b], f is the frequency in MHz.
This parameter is only used when the mask selection is set to
PsdMaskABParameters (see US power backOff PSD mask selection).
Instances
Values
[40..80.95; 0..40.95]
TNG 107-19
Edition 02 Released
Description
Instances
Values
[40..80.95; 0..40.95]
Description
For DS and US: specifies the maximum transmit PSD allowed for the
corresponding direction on a VDSL1 line.
A pre-defined set of standard PSD masks is defined. It is the responsibility of
the VDSL1 modem subsystem to translate the PSD Mask number into the
standard definition.
The VDSL1 modem subsystem checks consistency between the PSD Mask
settings and other configuration parameters. If not consistent, the configuration
is rejected by raising the Configuration Error failure (for example, the modem
subsystem rejects configurations with inconsistent DS and US PSD mask
settings).
Instances
Line DS, US
(1 of 2)
TNG 107-20
Edition 02 Released
Values
psdMaskCustom: custom defined PSD Mask (see Custom MIB PSD Mask)
Line DS/US:
psdMaskANSI_FTTEx_M1
psdMaskANSI_FTTEx_M2
psdMaskANSI_FTTCab_M1
psdMaskANSI_FTTCab_M2
psdMaskANSI_FTTCab_M1_ADSL: FTTCab.M1 used for US
psdMaskANSI_FTTCab_M2_ADSL: FTTCab.M2 used for US
psdMaskANSI_FTTCab_M1_ADSL2+: FTTCab.M1 used for US
psdMaskANSI_FTTCab_M2_ADSL2+: FTTCab.M2 used for US
Remarks:
The modem subsystem rejects the configuration if another band plan than
998 has been selected in combination with ANSI PSD masks.
The modem subsystem rejects the configuration if the ETSI Operating
Mode has been selected in combination with those ANSI PSD masks.
The modem subsystem uses the value of the Optional Band Mode
parameter whether to use one of both variants for the P.M1 and P.M2 US
masks.
The modem subsystem uses the value of the ADSL Band Mode parameter
whether to use variant A or B for the Pcab masks.
The modem subsystem uses the value of the VDSLx Band Plan parameter
whether to use the 998 or 997 variants of the ETSI PSD masks.
The modem subsystem rejects the configuration if another band plan than
998 or 997 has been selected in combination with ETSI PSD masks.
The modem subsystem rejects the configuration if the ANSI Operating
Mode has been selected in combination with those ETSI PSD masks.
(2 of 2)
TNG 107-21
Edition 02 Released
Description
Instances
Line
Values
3750..12000
1 kHz
Description
For DS and US: specifies the maximum transmit PSD allowed for the
corresponding direction on a VDSL2 line.
A pre-defined set of standard PSD masks is defined. It is the responsibility of
the VDSL2 modem subsystem to translate the PSD Mask number into the
standard definition.
The VDSL2 modem subsystem checks consistency between the PSD Mask
settings and other configuration parameters. If not consistent, the configuration
is rejected by raising the Configuration Error failure (for example, the modem
subsystem rejects configurations with inconsistent DS and US PSD mask
settings).
Instances
Line DS, US
(1 of 2)
TNG 107-22
Edition 02 Released
Values
psdMaskCustom: custom defined PSD Mask (see Custom MIB PSD Mask).
In this case, there is no limit mask (unlimited), and the maximum Tx PSD
mask envelope is determined by the Custom MIB PSD mask.
PsdMaskRegionA: refers to North American standard Annex A
Remarks:
Detailed PSD Mask for region A can be derived from the MGMT_R9.34
parameter, which fixes US0/DS1 transition frequency.
PsdMaskRegionB_M1
PsdMaskRegionB_M2: refers to European standard Annex B
Remarks:
Detailed PSD Mask for region B has to be used in combination with the
Predefined band plan parameter to check validity.
Detailed PSD Mask for region B can be derived from other parameters.
The modem subsystem shall reject the configuration if another band
plan than 998 or 997 has been selected in combination with ETSI PSD
masks.
PsdMaskRegionC: refers to Japanese standard Annex C
PsdMaskRegionC corresponds to the G993.2 [5] AnnexC (Japan region)
and shouldnt be misinterpreted as the G993.1 [4] AnnexC. It is also
associated to the BandPlanAext band plan (see Band plan).
(2 of 2)
Description
This parameter tells the VTU-O to override the kl0 (electrical length) estimated
by the VTU-R.
One special value is defined: the value electricalLengthEstimated indicates
that the US Power Back-off electrical length estimated by the VTU-T is not
overwritten by the VTU-O.
Instances
Values
Line
0..127.5; Electrical Length Estimated
Default Value is Electrical Length Estimated
Note: We consider here that electrical length is positive when the loop gain is
negative in dB (smaller than one in linear).
0.1 dB @ 1 MHz
TNG 107-23
Edition 02 Released
Description
Instances
Values
Line
PSD component of breakpoint: -40 dBm/Hz..-140 dBm/Hz
Special Value (default):NoVirtualNoise (-dBm/Hz)
Frequency component of breakpoint: 0..30000 kHz
Description
Selects the reference noise PSD that shall be considered when evaluating the
noise margin.
Instances
US, DS
Values
Note:
TNG 107-24
Edition 02 Released
Description
MaskContent:
Three 32 bits words, one per VDSL2 annex:
W0 = a31 a30 a29 ... a2 a1 a0 for VDSL2 annex A
W1 = b31 b30 b29 ... b2 b1 b0 for VDSL2 annex B
W2 = c31 c30 c29 ... c2 c1 c0 for VDSL2 annex C
The MSB (that is, the bit #31) of each word is ignored (the applicable VDSL2
annex type is derived from the selected VDSL 2 Limit Tx PSD mask).
Other mode bits are mapped to G.994.1 US0 octets of the corresponding
annex, from LSB to MSB: G.994.1 octet #k shall be mapped to bits x(k-1)*6
-> xk*6-1.
Bits not explicitly mapped to G.994.1 mode are ignored.
Mode:
Indicates how to restrict US0 modes:
disabled: no restriction applies (MaskContent is ignored).
mask: the MaskContent bitmap defines a mask to be applied on top of
the negotiated US0 mode capabilities (that is, a cleared bit indicates a
forbidden mode).
NoMatchBehaviour:
Defined what to do when, after the restriction, there is no matching US0
mode:
noUS0: no match: US0 is turned off (standard behavior).
noInit: no match: the initialization sequence is aborted, and the modem
raises a configuration not feasible failure.
Instances
Line
Values
See above.
Description
Instances
Bearer US, DS
Values
When set to 1, it indicates that the VTU receiver shall select framing parameters
so that INP_no_erasurep > INP_minConfigured. This means that the minimum
configured INP (together with maximum interleaver delay) will already be
achieved with the erasure detection mechanism disabled.
When set to 0, it indicates that VTUs receivers are not required to select framing
parameters that ensures INP_no_erasurep > INP_minp. In all cases, the VTU-R
receiver meets the requirement, INPp > INP_minConfigured.
This applies to all latency paths.
Unit
Binary (0/1)
TNG 107-25
Edition 02 Released
TNG 107-26
Edition 02 Released
Description
The operational mode used for the current operation of the VDSLx modem
subsystem (see Operating modes).
Instances
Line
Values
Initialization value
Update frequency
NA
Description
The total set of operational modes supported by the VTU-O and the VTU-R
respectively.
Instances
Near-end/Far-end
Values
Update frequency
NA
SNR Margin
Description
Indicates the current showtime noise margin: the maximum increase (in dB) of
the reference noise PSD (at all relevant frequencies), such that the BER of each
TPSTC stream does not exceed the maximum BER specified, without any
change of PMD parameters (that is, bits and gains) and PMS-TC parameters
(for example, FEC parameters). The BER is referenced to the output of the
PMS-TC function (that is, the / interface). * the maximum increase (in dB) of
the reference noise power that can be tolerated such that the VTU can still meet
the target BER requirement.
The reference noise PSD, in VDSL2 mode, does not correspond with the total
(internal + external) noise.
The SNR Margin in a given band shall assume a PSD noise increase in the
relevant band only.
Instances
Global DS/US for VDSLx, and per band for VDSL2 on top (including US0 band).
Values
-64..+63 dB
0.1 dB
Update frequency
TNG 107-27
Edition 02 Released
Loop Attenuation
Description
The difference in dB between the power received at one end and that
transmitted at the opposite end over all subcarriers during initialization. It is not
updated during showtime.
Instances
Values
0..102.3 dB
Note: when the actual loop attenuation is exceeding an extremum value that can
be represented, clamping to this extremum representable value is done.
0.1 dB
Accuracy
0.5 dB
Update frequency
NA
Signal Attenuation
Description
The difference in dB between the power received at one end and that
transmitted at the opposite end over all subcarriers during showtime. It
corresponds to the Line Attenuation as defined in G.997.1, 7.4.4/5.
Note: difference with Loop Attenuation is that the transmit power has changed
for the subcarriers and that the total number of subcarriers during showtime
typically will be less than during initialization.
Instances
Values
0..102.3 dB
Note: when the actual loop attenuation is exceeding an extremum value that can
be represented, clamping to this extremum representable value is done.
0.1 dB
DS: each = 10 seconds via EOC @ VTU-O
US: each < 10 seconds @ VTU-O
TNG 107-28
Edition 02 Released
Description
Actual aggregate output power (that is, the total output power for the carriers of
the corresponding direction) when the modem is in showtime.
Instances
DS/US
Values
-31..+31 dBm
Note: when the actual aggregate transmit power is exceeding an extremum
value that can be represented, clamping to this extremum representable value
is done.
0.1 dBm
Accuracy
Update frequency
Description
Actual Average (in dB) Transmit power spectrum density over the loaded
subcarriers.
Instances
DS/US
Values
-95..0 dBm/Hz.
A special value Out of Range indicates the parameter is out of range to be
represented.
0.1 dBm/Hz
Accuracy
0.1 dBm/Hz
Update frequency
Description
Instances
DS (VTU-O)/US (VTU-R)
Values
Update frequency
Not Applicable
TNG 107-29
Edition 02 Released
Description
Indicates the maximum bitrate the modem can sustain on the line (that is, the
transported payload plus all overhead from the PMD (If a Trellis encoder would
be used, the overhead shall be included in the Attainable Line Bitrate), PMS-TC
and TPS-TC layers) taking the current configuration into account (for example,
the Attainable Line Bitrate assumes that the current interleaver and coding
settings are not changed). If multiple bearer channels are active, the calculation
assumes that all capacity would be allocated to the bearer channel with the
highest coding gain.
The value only depends on the actual noise margin on the line.
Instances
Values
DS/US
0..65535
Remark: in case of no EOC, the initialization value for Attainable DS Line Bitrate
is returned.
1 kbps
DS: each = 10 seconds via EOC @ VTU-O
US: each < 10 seconds @ VTU-O
Description
The line rate corresponding to the Actual transport Bitrate (that is, the actual
transported payload plus all overhead information from the PMD (If a Trellis
encoder would be used, the overhead shall be included in the Attainable Line
Bitrate), PMS-TC and TPS-TC layers). The line rate is given by the number of
bits per DMT symbol, multiplied with the number of DMT symbols per second,
divided by 1000 (kbps).
Instances
DS/US
Values
0..262143
1 kbps
Update frequency
NA
Description
The ratio of the Actual Line Bitrate and the Attainable Line Bitrate when both are
available.
In case of an activation error Configuration not feasible, it is set to 100 % for
each direction where the minimum bitrate cannot be sustained.
Instances
DS/US
Values
0..100%
(1 of 2)
TNG 107-30
Edition 02 Released
1%
Update frequency
(2 of 2)
Description
Indicates the maximum net data bitrate (that is, transported payload plus
TPS-TC layer overhead) the VTU can sustain on the line taking the current
configuration into account, with margin not lower than Target Noise Margin. This
parameter is provided for each activated bearer channel. The calculation
estimates the attainable transport Bitrate assuming that all available capacity is
allocated to that bearer channel and that current interleaver and Reed-Solomon
settings are not changed.
The value depends on the actual noise margin on the line.
Instances
Values
0..262143
1 kbps
Update frequency
Description
The actual transport rate (that is, the transported payload plus header bytes)
expressed in kbps.
Instances
Values
0..262143
1 kbps
Update frequency
NA
Description
Instances
Values
0..63
1 ms
Update frequency
NA
TNG 107-31
Edition 02 Released
Table TNG 107-55: Actual impulse noise protection (per bearer channel)
Name
Description
Actual value of the impulse noise protection offered by the interleaving and
coding functionality.
Instances
Values
Update frequency
NA
Description
The TPS-TC layer mode used for the current operation of the VDSLx modem
subsystem.
Instances
Per line
Values
Same bitmap as TPS-TC mode capabilities. Only 1 bit can be set to 1 at a time.
Update frequency
NA
Description
The total set of TPS-TC modes supported by the VTU-O and the VTU-R
respectively.
Instances
Line Near-end/Far-end
Values
Bitmap:
TPSTCModesATMBit
TPSTCModesPTM_64_65Bit
TPSTCModesPTM_HDLCBit
Update frequency
NA
TNG 107-32
Edition 02 Released
Description
Instances
DS/US
Values
Bitmap:
SingleToneSpacingBit
DoubleToneSpacingBit
Update frequency
NA
Instances
VTU-R/VTU-O
Note: We consider here that electrical length is positive when the loop gain is
negative in dB (smaller than one in linear).
This is data is only available in VDSL2 operational mode.
Values
0..127.5
0.1 dB @ 1 MHz
Description
Defines the VTU-R timing advance. Positive values indicates that the
transmitted symbol will be advanced more with respect to the received symbol.
The VTU-R instance represents the initial TA as proposed by the VTU-R, and
the VTU-O instance represents the final VTU-R TA value, after VTU-O
correction (if any).
Instances
Values
-250..+250
10 ns
Accuracy
+/- 25 ns
TNG 107-33
Edition 02 Released
Description
Defines the highest carrier for which the SNR is sufficient, such that the bit
loading allocates at least 1 bit.
Rounding rule: Value is rounded to the lowest frequency bigger or equal to the
highest used carrier.
Instances
US/DS
Values
0..30000
1 kHz
Instances
US/DS
Values
1, 2, 4, or 8.
Unit
Number of carriers
Description
Actual Maximum Transmit power spectrum density over the loaded subcarriers.
Instances
US/DS
Values
-95..0
A special value Out of Range indicates the parameter is out of range to be
represented.
0.1 dBm/Hz
Accuracy
0.1 dBm/Hz
Update frequency
TNG 107-34
Edition 02 Released
Description
Instances
VTU-O/VTU-R
Values
Three times 32 bits word: [W2, W1, W0], according to parameter description
above.
Description
Returns the actual applicable ITU-T.993.2 ([5]) standard limit PSD mask,
including the US0 mode/variant.
The returned data are three 32 bits words, and a limit PSD indicator: [W2, W1,
W0, M].
The first three words (Mx) identify the actual standard annex and US0
mode/variant, following the format defined in VDSL2 annex modes capabilities.
Up to one word has raised bits: the word associated with the actual standard
annex. In this word, the MSB (that is, the bit #31) is raised, together with up to
one other bit identifying the actual US0 mode.
The PSD indicator (M) identifies the actual limit PSD mask, taken from Table
TNG 107-66
The unknown answer type is used when the transceiver does not find any
match with standard PSDs, or when no direct match is found (that is, short name
if PSD is NONE).
The other answer type is used when a match is found with the current
standard, but the corresponding PSD or Annex is missing from the PSD list.
(see Table TNG 107-66).
Instances
Line
Values
Three times 32 bits word: [W2, W1, W0], according to parameter description
above.
TNG 107-35
Edition 02 Released
TNG 107-36
Edition 02 Released
Annex
PSD
Invalid
Unknown
Other Annex
Unknown in Annex A
Other in Annex A
Unknown in Annex B
Other in Annex B
997-M1c-A-7
997-M1x-M-8
997-M1x-M
997-M2x-M-8
997-M2x-A
997-M2x-M
998-M1x-A
998-M1x-B
998-M1x-NUS0
998-M2x-A
998-M2x-M
998-M2x-B
998-M2x-NUS0
Unknown in Annex C
Other in Annex C
Description
VDSL2 only
This operational data is matched with DS configuration parameter Virtual Noise
SNRM_MODE when the VTU-R support virtual noise. Otherwise, it shall be
SNRM_MODE1.
Instances
DS
Values
SNRM_MODE1, SNRM_MODE2
Description
Instances
DS/US
Values
0: Not used
1: Used
Boolean.
Description
Indicates the actual cyclic extension used on the line (in showtime).
Instances
Line
Values
2, 3, 4, 5, , 16.
TNG 107-37
Edition 02 Released
Description
Indicates the following actual used framing parameters, per bearer. and linked
to the latency path that carries that bearer:
Instances
Values
Nfec: bytes, ranging from 0 to 255. The value 0 indicates no Reed Solomon
coding.
Rfec: bytes, ranging from 0 to 16. The value 0 indicates no Reed Solomon
coding.
Lsymb: bits (per symbol), ranging from 0 to 65536.
Dintlv: ranges from 1 to 4096. The value 1 indicates no interleaving.
Iintlv: ranges from 4 to 255, plus the 1 value that indicates no interleaving.
See Values.
TNG 107-38
Edition 02 Released
Re-initialization triggers
Supported span operation configuration parameters
Supported unit operation configuration parameters
Supported segment termination operation configuration parameters
Supported span operational data parameters
Supported unit operational data parameters
Supported segment termination operational data parameters
TNG 108-1
Edition 02 Released
Re-initialization triggers
During showtime (L0 line state), the SHDSL Modem Subsystem performs
persistency/severity checking and correlation on the defects/anomalies, in order to detect
re-initialization triggers. Table TNG 108-1 lists them for the SHDSL Transceiver Unit at
the Central office side (STU-C) and includes the required persistency time for each
showtime error.
Table TNG 108-1: Re-initialization triggers
Related Defect/Anomaly
Far-End
(f)los
5 1 sec
6 1 sec
sef/rdi
5 1 sec
6 1 sec
(f)lom
60 1 sec
60 1 sec
(f)se
10 1 sec
10 1 sec
(f)ncd
15 1 sec
17 1 sec
(f)lcd
15 1 sec
17 1 sec
(f)npd/(f)lpd
15 1 sec
15 1 sec
The SHDSL Modem Subsystem triggers/initiates re-activation of the modem when any of
those triggers is fired. No other re-initialization triggers (annex timer values) are used by
the Modem Subsystem than the ones mentioned in Table TNG 108-1.
All far-end count-down timers are frozen when any near-end defect occurs. When all
near-end defects have disappeared, far-end count-down timers resume from frozen
values (ignoring the in-between time).
All near-end defects are correlated independent from each other. The same holds for all
far-end defects in absence of near-end defects.
TNG 108-2
Edition 02 Released
In case a parameter is indicated as optional, the input value is dont care, and any
value is accepted without having impact on the modem subsystem behavior.
In case a parameter is indicated to be required to a certain level (for example, only
limited set of defined number of input values), only input values corresponding to the
required level are accepted. If the input parameter is not accepted, the modem
subsystem raises a failure indication to the xDSL Manager indicating Configuration
Error
In case extra consistency checks need to be performed on a parameter or between
parameters and the configuration should be rejected, 'rejection' always means that
the modem subsystem raises a failure indication to the SHDSL Manager indicating
Configuration Error, rather that a returned error of the considered SHDSL API call.
An SHDSL API configuration request is replied with an error only when the call is done
in a wrong administrative state.
The SHDSLx Modem Subsystem allows that the configuration can be independently set
on individual line basis.
M-pair (1 < M < 4) stands for a multiple-pair operation over SHDSL span for some
applications having higher data rate requirements for end users.
Four-wire mode is identical to M-pair mode with M = 2, except for the method of assigning
ordinal numbers to the wire pairs.
Data Rates: M-pair operational mode is capable of supporting user (payload) data
rates from M *192 kbit/s to M *2.312 Mbit/s in increments of M * 8 kbit/s, where 1 < M
< 4. Note that optional extensions described in Annex F/G allow user data rates up to
M *5696 kbit/s. Four-wire mode is identical to M-pair mode with M = 2, except for the
method of assigning ordinal numbers to the wire pairs.
Embedded Operations Channel (EOC): For optional M-pair operation, each EOC
message is sent in parallel such that redundant and identical messages are sent over
all M loops. In M-pair mode, eoc01 - eoc20 on Pair 1 carries the primary EOC data.
The corresponding Pair 2 to Pair M eoc bits are duplicates of the Pair 1 eoc bits.
SHDSL Transceiver Unit at the Remote side (STU-R) Power Status: In M-pair mode,
ps on Pair 1 carries the primary power status indication. The ps bit on all other pairs
are duplicates of the Pair 1 ps bit.
Power Feeding/Wetting Current: In the optional M-pair mode, the requirements for
remote power feeding or wetting current for each of the M pairs are identical to the
requirements for a single pair.
Activation Procedure: In devices supporting the optional M-pair mode, the core
activation procedure is considered as an independent procedure for each pair. Such
devices are capable of detecting the completion of activation for all pairs and upon
completion will initiate the transmission of user data over all pairs.
Line Probe: In the optional M-pair mode, STU-R remote probe signal Pri and STU-C
central probe signal Pci are sent in parallel on all wire pairs.
G.994.1: In the optional 4-wire mode, Pair 1 and Pair 2 are determined during the
preactivation sequence procedures defined in Annex B/G.994.1 entitled, Operation
over multiple wire pairs. Pair 1 is defined as the pair on which the final G.994.1
transaction is conducted. In the optional M-pair mode, the G.994.1 exchange follows
the defined procedures for multi pair operation.
TNG 108-3
Edition 02 Released
Operating Modes
Operating Modes
Description
(1) ATM-Native
(2) ATM-IMA (ATM Forum)
(3) PTM-64/65B
(4) PTM-HDLC
The standards that need to be supported for the current projects are listed in
SHDSL_R24.
Operational modes not supported by the STU-C shall be ignored (that is, they
are not considered selected).
Multiple mode selection is not allowed.
The operational mode is selected by the SHDSL Manager before startup the
line, each lines operational mode are independent to the other lines, with
exception of M-pair mode which requires all lines belong to a M-pair
configuration in the same operational mode.
Operational modes are not exchanged by G.hs.
The modem rejects the configuration and raises the Configuration error
activation failure in the following scenarios:
In IMA Mode, Minimum and Maximum Requested Data Rates are to be set to
the same value, which would be the same for all links in the IMA group. For this
reason, the IMA mode selection and Group assignment needs to be made at the
same time as the initial provisioning.
IMA is not supported over M-pair links.
Instances
Span
Values
shdsl_native_mode
shdsl_ima_mode
shdsl_efm_mode
Number of Repeaters
Number of Repeaters
Description
Configures the number of SRU (repeater) units to be configured for this SHDSL
span. It controls the number of SRU (repeater) entries in the unit configuration.
Instances
Span
(1 of 2)
TNG 108-4
Edition 02 Released
Values
0-8
(2 of 2)
Spectral Profile
Description
Specifies the spectral mode in which this SHDSL span is to be configured with.
Two options are supported:
AsymmetricProfile
SymmetricProfile
Examples:
Annex A/2-Wire: 768 kb/s & 1536 kb/s
Annex A/4-Wire: 1536 kb/s & 3072 kb/s
Annex B/2-Wire: 2048 kb/s & 2304 kb/s
Annex B/4-Wire: 4096 kb/s & 4608 kb/s
Instances
Span
Values
symmetricProfile
asymmetricProfile
Wire Mode
Wire Mode
Description
Instances
Span
(1 of 2)
TNG 108-5
Edition 02 Released
Values
shdsl_two_wire
shdsl_four_wire
shdsl_six_wire
shdsl_eight_wire
(2 of 2)
Description
Instances
Span
Values
disabled
enabled
Regional Setting
Regional Setting
Description
Specifies the regional setting for the SHDSL line per the ITU-T G.992.1
Annexes (Annex A/F and Annex B/G).
Instances
Span
Values
BitMap:
Bit
Setting
---
---------
Region 1
Region 2
TNG 108-6
Edition 02 Released
Description
Defines the minimum requested transport payload bitrate which shall be set up
and which shall be maintained during showtime by the STU.
When line probe is enabled, the SHDSL line is probed for levels between this rate
and the maximum requested data rate. The Line will not be activated at a lower
rate.
Only ATM/EFM Mapping is supported, this limits the resulting data rates to
multiples of 64k (192 to 5696) in TwoWire mode; and to multiples of 128k (384 to
11,392) in FourWire mode, to multiples of 192k (576 to 17,088) in SixWire mode,
to multiples of 256k (768 to 22,784) in EightWire mode.
In IMA Mode, Minimum and Maximum Requested Data Rates are to be set to the
same value which would be the same for all links in the IMA group. This result in
a constraint to use exact 64 kb/s multiples in provisioning.
Instances
Values
Span
2-wire: 192 to 5696 in multiple of 64, and 2312
4-wire: 384 to 11,392 in multiple of 128
6-wire: 576 to 17,088 in multiple of 192
8-wire: 768 to 22,784 in multiple of 384
Maximum Bitrate
Description
Specifies the maximum requested SHDSL data rate which can range from 192 to
5696 kb/s in Two Wire mode, plus the rate of 2312; and from 384 to 11.392 kb/s
in FourWire mode; from 576 to 17,088 kb/s in SixWire mode; from 768 to 22.784
kb/s in EightWire mode
The SHDSL line is probed for levels between this rate and the minimum
requested data rate. The Line will not be activated at a higher rate.
Only the ATM/EFM Mapping is supported, this limits the resulting data rates to
multiples of 64k (192 to 5696) in TwoWire mode; and to multiples of 128k (384 to
11.392) in FourWire mode, to multiples of 192k (576 to 17.088) in SixWire mode,
to multiples of 256k (768 to 22.784) in EightWire mode.
In IMA Mode, Minimum and Maximum Requested Data Rates are to be set to the
same value which would be the same for all links in the IMA group. This result in
a constraint to use exact 64 kb/s multiples in provisioning.
This parameter is relevant only in line probe enabled mode. When line probe is
not enabled, the Maximum Bitrate parameter is ignored.
As the data rate granularity is in multiple of 64 kbps, the following rounding
scheme for Minimum and Maximum Bitrates is implemented:
The SHDSL modem subsystem raises failure indication Configuration Error for
configurations where Maximum Bitrate < Minimum Bitrate for one of the
directions when line probe is enabled.
Instances
Span
(1 of 2)
TNG 108-7
Edition 02 Released
Values
(2 of 2)
Description
Instances
Span
Values
-11to 10
1 dB
TNG 108-8
Edition 02 Released
Description
Specifies the Target Margin in the Downstream direction, relative to the Current
noise conditions, to be used during handshake and line-probe procedure in
gauging a BER better than 1E-7.
Target margin is used by the receiver to determine if a data rate can be
supported with this margin under current noise measured during line probe
and/or reference worst-case noise specified in Annexes A and B. A data rate
may be included in the capabilities list resulting from line probe only if the
estimated SNR associated with that data rate minus the SNR required for BER
= 1E-7 is greater than or equal to the target margin in dB. If both worst-case
target margin and current-condition target margin are specified, then the
capabilities exchanged shall be the intersection of data rates calculated using
each noise condition separately.
The use of negative target margins with respect to reference worst-case noise
corresponds to reference noise with fewer disturbers. This may be applicable
when the number of disturbers is known to be substantially fewer than specified
by the reference worst-case noise. Use of negative target margins with respect
to current conditions is not advised. Use of the current-condition target margin
mode may result in retrains if the noise environment changes significantly.
The negotiation of the target margins is done as follows:
The target margins to be used by both the STU-C and the STU-R for
determining the supported data rates are under the control of the STU-C. In the
PMMS parameter exchange, the STU-C shall set the upstream and
downstream PMMS target margins to identical values. This does not imply that
the worst-case and current-conditions target margins are the same.
To determine which data rates the STU-C can support, the STU-C can choose
to use the upstream PMMS target margin transmitted by the STU-R in the
PMMS parameter exchange, or the STU-C may choose to use an alternative
internal value for the PMMS target margins. The STU-R shall use the
downstream PMMS target margin parameters sent by the STU-C for
determining which data rates the STU-R can support. This procedure is
applicable to both the current-condition and the worst-case target margins.
In M-pair operation, the same Downstream Target Noise Margin is used on all
pairs.
A value of -11 indicates not to use the Worst Case method in the downstream
direction.
Instances
Span
Values
-11to 10
1 dB
TNG 108-9
Edition 02 Released
Description
Specifies the Target Margin in the Upstream direction, relative to the reference
Worst Case, to be used during handshake and line-probe procedure in gauging
a BER better than 1E-7.
Target margin is used by the receiver to determine if a data rate can be
supported with this margin under current noise measured during line probe
and/or reference worst-case noise specified in Annexes A and B. A data rate
may be included in the capabilities list resulting from line probe only if the
estimated SNR associated with that data rate minus the SNR required for BER
= 1E-7 is greater than or equal to the target margin in dB. If both worst-case
target margin and current-condition target margin are specified, then the
capabilities exchanged shall be the intersection of data rates calculated using
each noise condition separately.
The use of negative target margins with respect to reference worst-case noise
corresponds to reference noise with fewer disturbers. This may be applicable
when the number of disturbers is known to be substantially fewer than specified
by the reference worst-case noise. Use of negative target margins with respect
to current conditions is not advised. Use of the current-condition target margin
mode may result in retrains if the noise environment changes significantly.
The negotiation of the target margins is done as follows:
The target margins to be used by both the STU-C and the STU-R for
determining the supported data rates are under the control of the STU-C. In the
PMMS parameter exchange, the STU-C shall set the upstream and
downstream PMMS target margins to identical values. This does not imply that
the worst-case and current-conditions target margins are the same.
To determine which data rates the STU-C can support, the STU-C can choose
to use the upstream PMMS target margin transmitted by the STU-R in the
PMMS parameter exchange, or the STU-C may choose to use an alternative
internal value for the PMMS target margins. The STU-R shall use the
downstream PMMS target margin parameters sent by the STU-C for
determining which data rates the STU-R can support. This procedure is
applicable to both the current-condition and the worst-case target margins.
In M-pair operation, the same Downstream Target Noise Margin is used on all
pairs.
A value of -11 indicates not to use the Worst Case method in the downstream
direction.
Instances
Span
Values
-11to 10
1 dB
TNG 108-10
Edition 02 Released
Description
Specifies the Target Margin in the Upstream direction, relative to the Current
noise conditions, to be used during handshake and line-probe procedure in
gauging a BER better than 1E-7.
Target margin is used by the receiver to determine if a data rate can be
supported with this margin under current noise measured during line probe
and/or reference worst-case noise specified in Annexes A and B. A data rate
may be included in the capabilities list resulting from line probe only if the
estimated SNR associated with that data rate minus the SNR required for BER
= 1E-7 is greater than or equal to the target margin in dB. If both worst-case
target margin and current-condition target margin are specified, then the
capabilities exchanged shall be the intersection of data rates calculated using
each noise condition separately.
The use of negative target margins with respect to reference worst-case noise
corresponds to reference noise with fewer disturbers. This may be applicable
when the number of disturbers is known to be substantially fewer than specified
by the reference worst-case noise. Use of negative target margins with respect
to current conditions is not advised. Use of the current-condition target margin
mode may result in retrains if the noise environment changes significantly.
The negotiation of the target margins is done as follows:
The target margins to be used by both the STU-C and the STU-R for
determining the supported data rates are under the control of the STU-C. In the
PMMS parameter exchange, the STU-C shall set the upstream and
downstream PMMS target margins to identical values. This does not imply that
the worst-case and current-conditions target margins are the same.
To determine which data rates the STU-C can support, the STU-C can choose
to use the upstream PMMS target margin transmitted by the STU-R in the
PMMS parameter exchange, or the STU-C may choose to use an alternative
internal value for the PMMS target margins. The STU-R shall use the
downstream PMMS target margin parameters sent by the STU-C for
determining which data rates the STU-R can support. This procedure is
applicable to both the current-condition and the worst-case target margins.
In M-pair operation, the same Downstream Target Noise Margin is used on all
pairs.
A value of -11 indicates not to use the Worst Case method in the downstream
direction.
Instances
Span
Values
-11to 10
1 dB
Description
Specifies support for Line Probe (rate adaptation) of the units in a SHDSL line.
When Line Probe is enabled, the system performs Line Probing to find the best
possible rate. If Line probe is disabled, the rate adaptation phase is skipped to
shorten set up time.
Instances
Span
Values
disabled
enabled
TNG 108-11
Edition 02 Released
Description
Instances
Unit
Values
0-127
1 dB
Description
Specifies the SNR Margin Threshold Value in dBs, for generated associated
alarms.
A value of 0 disables alarm generation.
Instances
Unit
Values
0-15
1 dB
Loopback Timeout
Table TNG 108-17: Loopback Timeout
Name
Loopback Timeout
Description
Instances
Unit
Values
0-4095
1minute
TNG 108-12
Edition 02 Released
Loopback Config
Specifies the loopbacks for the associated side of an SHDSL unit.
Only Network Side loopbacks are supported for SRU and STU-R units
Instances
Segment Termination
Values
NoLoopback
NormalLoopback
Description
Instances
Segment Termination
Values
Default
Selected
Soft Restart
Soft Restart
Initiate a Soft Restart message towards the relevant segment termination.
When the value of this object is set from 0 to 1, a Soft Restart EOC message is
initiated. After 5 minutes the value of the object is automatically set back to 0.
Instances
Values
Segment Termination
0 (Normal Operation)
1 (Soft Restart)
TNG 108-13
Edition 02 Released
Span State
Span State
Description
Instances
Span
Values
unknown
unequipped
faulty
idle
startup
active
Initialization value
Idle
Showtime value:
Active
Update frequency
NA
TNG 108-14
Edition 02 Released
Detected Units
Detected Units
Description
Indicates the units that have been detected on this SHDSL span, bits are set(1)
for detected units.
Instances
Span
Values
Bitmap:
Bit
Unit
---
------
STU-C
STU-R
SRU-1
SRU-2
SRU-3
SRU-4
SRU-5
SRU-6
SRU-7
SRU-8
Initialization value
NA
Showtime value:
Update frequency
NA
Configured Units
Configured Units
Description
Indicates the units in the SHDSL span which have been successfully
configured, bits are set (1) for units which have been successfully configured.
Instances
Span
Values
Bitmap:
Bit
Unit
---
------
STU-C
STU-R
Initialization value
NA
Showtime value:
Update frequency
NA
TNG 108-15
Edition 02 Released
Span Status
Span Status
Description
Instances
Span
Values
Bitmap:
Bit
Condition
---
---------
No Error
LOSW
DC Continuity Fault
Device Fault
Configuration Error
Loopback(s) Active
10
Loss of Power
11
Initialization value
NA
Showtime value:
Update frequency
NA
TNG 108-16
Edition 02 Released
Description
Provides the correlation between the actual ports and their dynamic designation
as fistPair and secondPair and thirdPair and fourthPair (if M>2 is supported) as
a result of the pre-activation sequence in a modem ASIC. (firstPair is defined as
the pair on which the final G.994.1 transaction is conducted)
For 4-wire mode:
00000100b: if the first port is the first pair, second port is the second pair
00000001b: if the second port is the first pair
00100100b: if the first port is the first pair, second port is the second pair,
third port is the third pair
00010010b: if the second port is the first pair, third port is the second pair
00001001b: if the third port is the first pair, first port is the second pair
11100100b: if the first port is the first pair, second port is the second pair,
third port is the third pair, fourth port is the fourth pair
10010011b: if the second port is the first pair
01001110b: if the third port is the first pair
00111001b: if the fourth port is the first pair
Instances
Span
Values
Bitmap:
Bit
Condition
---
---------
1,0 wirePair of the 1st modem ASIC port for 6/8-wire, 1st/3rd numbered port
for 4-wire
3,2 wirePair of the 2nd modem ASIC port for 6/8-wire, 2nd/4th numbered port
for 4-wire
5,4
wirePair of the 3rd modem ASIC port for 6/8-wire, set to 0 for 4-wire
7,6
wirePair of the 4th modem ASIC port for 8-wire, set to 0 for 4/6-wire
wirePair
value
----------
--------
1stPair
00
2ndPair
01
3rdPair
10
4thPair
11
Initialization value
NA
Showtime value:
Update frequency
NA
TNG 108-17
Edition 02 Released
Unit DC Powering
Unit DC Powering
Description
Indicates whether this unit is powered locally, or derives power from the SHDSL
span.
Instances
Unit
Values
LocalPowered
spanPowered
Initialization value
NA
Showtime value:
Update frequency
NA
TNG 108-18
Edition 02 Released
Description
Instances
Segment Termination
Values
Bitmap:
Bit
Condition
---
---------
No Error
LOSW
DC Continuity Fault
Device Fault
Configuration Error
Loopback(s) Active
10
Loss of Power
11
Initialization value
NA
Showtime value:
Update frequency
NA
TNG 108-19
Edition 02 Released
Loopback State
Loopback State
Description
Instances
Segment Termination
Values
noLoopback
normalLoopback
specialLoopback
Initialization value
noloopback
Showtime value:
Update frequency
NA
SNR Margin
SNR Margin
Description
Instances
Segment Termination
Values
-128 to 127 dB
1 dB
Accuracy
1 dB
Initialization value
Showtime value:
Update frequency
TNG 108-20
Edition 02 Released
Loop Attenuation
Loop Attenuation
Description
Instances
Segment Termination
Values
-128 to 127 dB
1 dB
Accuracy
1 dB
Initialization value
Showtime value:
NA
Update frequency
NA
Description
Instances
Segment Termination
Values
0 to 31 dB
1 dB
Accuracy
1 dB
Initialization value
Showtime value:
NA
Update frequency
NA
TNG 108-21
Edition 02 Released
Description
Indicates the current state of the Tip/Ring pair at this SHDSL segment
termination.
Instances
Segment Termination
Values
normal
reversed
Accuracy
Initialization value
Showtime value:
NA
Update frequency
NA
Description
Instances
Segment Termination
Values
default
selected
Accuracy
Initialization value
Showtime value:
NA
Update frequency
NA
TNG 108-22
Edition 02 Released
TNG 109-1
Edition 02 Released
TNG 109-2
Edition 02 Released
Both ADSL and VDSL port configuration examples are provided. Unless otherwise
specified, the examples in this TNG apply to both the 7302 ISAM and 7330 ISAM FTTN.
Note The examples in this TNG use the command repetition (also
called ranging) feature of CLI. This feature can be used to execute a
command over a group of ports. See the 7330 ISAM FTTN Operations
and Maintenance Using CLI document for more information about
command repetition.
Parameters for examples
All of the examples in this TNG assume that the NE has the following settings.
TNG 110-1
Edition 02 Released
Enable single IP address mode. See the 7302 ISAM | 7330 ISAM FTTN System
Description document for more information about single IP address mode.
configure system single-public-ip
Attach the management VLAN to the network management port on the NT unit:
configure vlan shub id 4093 egress-port network:1
Equipment planning
This section shows an example of the steps required to plan the equipment of an NE.
This example assumes that the NE is a 7330 ISAM FTTN ARAM-D shelf with the
following cards installed:
TNG 110-2
Edition 02 Released
Note In CLI, LT1 is identified as 1/1/4, LT2 as 1/1/5, LT3 as 1/1/6, and
LT4 as 1/1/7.
Configure a VDSL spectrum profile. This profile is called g993_vdsl11 and supports
only VDSL without upstream power backoff.
configure xdsl spectrum-profile 1 name g9931_vdsl1 dis-etsi-dts
dis-ansi-t1413 dis-g992-1-a dis-g992-1-b dis-g992-2-a
dis-g992-3-a dis-g992-3-b dis-etsi-ts itu-g993-1
Configure the VDSL options for the profile, such as band plan and upstream power
backoff mode:
configure xdsl spectrum-profile 1 vdsl vdsl-band-plan
band-plan-a4 optional-band up adsl-band allow-adsl
max-agpowlev-down 145 max-agpowlev-up 145 psd-shape-down
ansi-ftt-cab-m2 psd-shape-up ansi-ftt-cab-m2 pbo-mode-down
rx-psd-shape-up ansi-a
TNG 110-3
Edition 02 Released
Configure a service profile for 25 Mb/s downstream and 3 Mb/s upstream service.
The profile is called 25Mpbs_3Mbps.
configure xdsl service-profile 1 name 25Mbs_3Mbps
min-bitrate-down 32 min-bitrate-up 32 plan-bitrate-down 512
plan-bitrate-up 512 max-bitrate-down 25024 max-bitrate-up 3008
max-delay-down 8 max-delay-up 8 imp-noise-prot-dn 10
imp-noise-prot-up 10
Assign the spectrum and service profiles to the VDSL ports and put the ports in
service:
If all the physical connections are made, you can now train a VDSL modem on LT1 and
LT2.
Configure a spectrum profile. The profile is called multi_adsl and supports ADSL,
ADSL2, READSL, and ADSL2+.
configure xdsl spectrum-profile 2 name multi_adsl g992-3-l1
g992-3-l2 g992-3-am g992-5-a
Configure a service profile for 15 Mb/s downstream and 1 Mb/s upstream service.
The profile is called 15Mpbs_1Mbps and has minimum delay and impulse noise
protection configured.
configure xdsl service-profile 2 name 15Mbps_1Mbps
min-bitrate-down 32 min-bitrate-up 32 plan-bitrate-down 1024
plan-bitrate-up 256 max-bitrate-down 15360 max-bitrate-up 1024
max-delay-down 1 max-delay-up 1 imp-noise-prot-dn 0
imp-noise-prot-up 0
TNG 110-4
Edition 02 Released
Assign the spectrum and service profiles to the multi-ADSL ports and put the ports in
service:
If all the physical connections are made, you can now train a multi-ADSL modem on LT3
and LT4.
vlan-id; the vlan-id parameter makes the port a member of the VLAN so traffic can
flow through the system
pvid; the pvid parameter is used to place the untagged Ethernet frames from the xDSL
port into the correct VLAN; by default, all traffic is sent toward the end user with no
VLAN tag
max-unicast-mac; the max-unicast-max parameter limits the number of devices that
can be active on a bridge port
TNG 110-5
Edition 02 Released
Assign the data traffic and VDSL ports to VLAN 101 on the SHub. This ensures the
traffic is bridged from the network port to the appropriate VDSL LT unit.
configure vlan shub id 101 egress-port network:2
configure vlan shub id 101 egress-port lt:1/1/4
configure vlan shub id 101 egress-port lt:1/1/5
Assign the data traffic and multi-ADSL ports to VLAN 102 on the SHub. This ensures
the traffic is bridged from the network port to the appropriate multi-ADSL LT unit.
configure vlan shub id 102 egress-port network:2
configure vlan shub id 102 egress-port lt:1/1/6
configure vlan shub id 102 egress-port lt:1/1/7
For each multi-ADSL port, create an ATM PVC that matches the PVC configured on
the multi-ADSL modem. This step is not required for VDSL ports.
TNG 110-6
Edition 02 Released
NT
LT1
SHub
3
VLAN 101
It:1/1/4
BP
BP
24
CPE
VLAN 101
CPE
Backplane connection
between NT and LT
TNG 110-7
Edition 02 Released
Assign the data traffic and xDSL ports to the appropriate VLANs on the SHub. This
ensures the traffic is bridged from the network port to the appropriate LT unit:
network:2
lt:1/1/4
network:2
lt:1/1/5
network:2
lt:1/1/6
network:2
lt:1/1/7
TNG 110-8
Edition 02 Released
For each multi-ADSL port, create an ATM PVC that matches the PVC configured on
the multi-ADSL modem. This step is not required for VDSL ports.
TNG 110-9
Edition 02 Released
SHub
VLAN 124
VLAN 101
3
2
VLAN101
LT1
BP
It:1/1/4
1
CPE
VLAN 124
BP
24
CPE
Backplane connection
between NT and LT
VLAN 124
TNG 110-10
Edition 02 Released
Multicast
This example shows one of the ways you can configure multicast for a 7302 ISAM or
7330 ISAM FTTN. Multicast is the transmission from a single device (such as an IPTV
host) to a group of recipients (such as xDSL subscribers). See the
7302 ISAM / 7330 ISAM FTTN System Description document for more detailed
information on multicast.
This example assumes that the NE has the following settings.
The system is configured for basic data traffic using the cross-connect VLAN model.
This configuration allows for all multicast traffic to be delivered to the NE on a single
VLAN separate from the VLAN configured on the subscriber bridge port. The system
then connects the subscriber to a multicast group and forwards it to the subscriber
VLAN when the subscriber requests the group using IGMP. See the
7302 ISAM / 7330 ISAM FTTN System Description document for more detailed
information about multicast and IGMP.
All multicast traffic is delivered on network port 2, with a VLAN ID of 10.
The multicast sources available to subscribers are 224.1.1.1 to 224.1.1.100.
There is an IGMP router connected to the NE on network port 2.
The NE is not required to restrict multicast connections based on bandwidth.
The IP addresses used by the NE for IGMP messaging are:
toward the subscribers: 192.168.1.1
toward the network: 10.10.10.1
Configure VLAN 10 on the SHub so that multicast traffic can be delivered to all LT
units:
configure vlan shub id 10 mode residential-bridge
configure vlan shub id 10 egress-port network:2
configure vlan shub id 10 egress-port lt:1/1/[47]
Configure the multicast source table on the NE. This table contains the list of all
multicast groups available to subscribers and the corresponding VLAN group for
each multicast group.
configure mcast src 224.1.1.[1100] vlan-id 10
atm-peak-bit-rate 0 atm-sus-bit-rate 0
Configure the system to disallow the joining of unconfigured multicast groups for
iBridge subscribers:
configure mcast general no package-member [1...1024]
configure mcast capacity max-num-uncfg 0
Set the maximum number of unique groups that can be active on a single LT unit:
configure mcast capacity max-num-group 256
TNG 110-11
Edition 02 Released
Start the IGMP system and configure the IP address used for IP messaging toward
the subscribers and the SHub. This address is not used for messaging toward the
router.
configure igmp system src-ip-address 192.168.1.1 start
Configure the VLAN IP address used for IGMP messaging toward the upstream
router:
configure interface shub vlan-id 10 admin-status down
configure interface shub ip 10 ip-addr 10.10.10.1/24
configure interface shub vlan-id 10 admin-status up
Configure the port and VLAN ID connection for the router upstream of the NE:
configure igmp shub vlan-router-port 10 network-port 2
query-timer 125
10 Disable the snooping filter on the multicast VLAN. This step enables snooping on the
VLAN.
configure igmp shub vlan-filter 10 no snoop-filter
11 Enable the snooping filter on the subscriber VLANs. This disables snooping on the
VLANs, since there should be no IGMP on these VLANs.
configure igmp shub vlan-filter [101124] snoop-filter
configure igmp shub vlan-filter [201224] snoop-filter
configure igmp shub vlan-filter [301348] snoop-filter
configure igmp shub vlan-filter [401448] snoop-filter
12 Enable IGMP on the subscriber interface and limit the maximum number of multicast
groups to which a subscriber can belong at any one time:
configure igmp channel 1/1/4/[1...24] max-num-group 10
configure igmp channel 1/1/5/[1...24] max-num-group 10
configure igmp channel 1/1/6/[1...48]:8:35 max-num-group 10
configure igmp channel 1/1/7/[1...48]:8:35 max-num-group 10
13 STOP. This procedure is complete.
Subscribers can now join configured multicast groups from xDSL ports using IGMP.
802.1x authentication
This example shows how to set up 802.1x authentication. See the
7302 ISAM / 7330 ISAM FTTN System Description document for more detailed
information about 802.1x authentication on a 7302 ISAM or 7330 ISAM FTTN.
TNG 110-12
Edition 02 Released
The system is configured for basic data traffic using the iBridge or cross-connect
VLAN model.
A RADIUS server is available upstream of the NE.
The RADIUS server is configured as follows:
accessible over management VLAN 4093
authentication server IP address is 192.168.2.22
accounting server IP address is 192.168.2.23
default domain is ALCATEL
NAS-ID for the NE is ISAM-1
NAS-IP for the NE is 192.168.1.1
TNG 110-13
Edition 02 Released
Configure the server used for authentication. The shared RADIUS secret key is
mysecret.
configure system security radius auth-server sampleAuth
vrf-index 0 ip-address 192.168.2.22 secret mysecret
Configure the server used for accounting. The shared RADIUS secret key is
mysecret.
configure system security radius acc-server sampleAcc
vrf-index 0 ip-address 192.168.2.23 secret mysecret
Configure a RADIUS policy for the NE specifying the NAS-ID and the NAS-IP:
configure system security radius policy sampleRadPol
nas-id ISAM-1 nas-ip-address 192.168.1.1
Configure the policy to use the authentication and accounting servers. These servers
were created in steps 1 and 2.
configure system security radius policy sampleRadPol servers 1
auth-server name:sampleAuth vrf-index-auth 0 priority 40
acc-server name:sampleAcc vrf-index-acc 0
Create a connection profile for the ALCATEL domain and configure handling of
requests without a domain:
configure system security conn-profile sampleConnProf
version 1 domain-name ALCATEL no reject-no-domain
reject-inv-domain
Configure the connection profile for the connection policy defined in step 6:
configure system security conn-policy conn-profile-name
sampleConnProf
TNG 110-14
Edition 02 Released
General
Table TNG 111-1 lists the correlation between the LT port number entered in CLI and the
GENC-E downlink port linked by fiber to the EDSE-A card on the ES.
Table TNG 111-1: LT port numbers: GENC-E to CLI correlation
GENC-E downlink port number
(1)
(1)
10
11
10
12
11
13
12
14
13
15
14
16
15
17
16
18
17
19
TNG 111-1
Edition 02 Released
Note
(1)
Dual-mode port. This port can be configured as an uplink or downlink port. The default setting is
uplink. The SFP alarms behave differently depending on whether the port is configured as uplink or
downlink.
Procedure
Use this procedure to configure the ES.
1
Example:
configure system id 7330-ES1
configure system management host-ip-address
manual:138.120.217.171/24
configure system management default-route 138.120.217.1
configure interface shub port [1...5] port-type network
admin-status auto-up
configure vlan shub id 4093 egress-port network:1
configure vlan shub id 4093 untag-port network:1
configure bridge shub port 1 pvid 4093
TNG 111-2
Edition 02 Released
Plan the ECNT-A and GENC-E or GENC-F cards on the host shelf:
configure equipment slot 1/1/1 planned-type genc-e|genc-f unlock
configure equipment slot nt-b planned-type ecnt-a unlock
Example:
configure equipment slot 1/1/1 planned-type genc-e unlock
configure equipment slot nt-b planned-type ecnt-a unlock
Example:
configure equipment shelf 1/2 planned-type aram-d
Example:
configure equipment slot 1/2/2 planned-type edse-a unlock
configure equipment applique 1/2/2 planned-type satu-a
Example:
configure equipment slot 1/2/4 planned-type eblt-c unlock
configure equipment applique 1/2/4 planned-type hlpc-h
TNG 111-3
Edition 02 Released
Example:
configure xdsl service-profile 1 name xsrvc1 local-profile
configure xdsl service-profile 1 version 1 min-bitrate-down 22500
min-bitrate-up 384 plan-bitrate-down 22500 plan-bitrate-up 784
max-bitrate-down 25000 max-bitrate-up 1500 max-delay-down 1
max-delay-up 1
configure xdsl service-profile 1 active
Example:
configure xdsl spectrum-profile 1 name xlne1 local-profile
version 1 dis-etsi-dts dis-g992-1-b dis-g992-3-b g992-3-l1
TNG 111-4
Edition 02 Released
Example:
configure vlan id 101 mode residential-bridge
configure vlan shub id 101 mode residential-bridge
configure vlan shub id 101 egress-port network:3
configure vlan shub id 101 egress-port lt:1/1/10
If one or more dual-mode ports are used to connect the GENC-E to the EDSE-A on
the ES, configure the dual-mode ports as downlink ports:
configure equipment external-link-host dualport# direction
remote-lt
where
dualport# is the number of the dual-mode port as shown in Table TNG 111-1; you can enter a single
port number or a range of port numbers
Example:
configure equipment external-link-host [6...7] direction
remote-lt
111-5
Edition 02 Released
10
Example:
configure xdsl line 1/2/4/1 service-profile 1 spectrum-profile 1
admin-up
configure atm pvc 1/2/4/1:8:35
configure bridge port 1/2/4/1:8:35
configure bridge port 1/2/4/1:8:35 vlan-id 101
configure bridge port 1/2/4/1:8:35 pvid 101 no mac-learn-off
max-unicast-mac 4
11
111-6
Edition 02 Released
General
Subtending allows several 7330 ISAM FTTN nodes to be connected to the network
through a single node. For more information about subtending, see the
7302 ISAM | 7330 ISAM FTTN System Description.
Figure TNG 112-1 shows an example of subtended 7330 ISAM FTTN nodes.
TNG 112-1
Edition 02 Released
Node #2
Traffic on
VLAN 200
Network
VLAN associations:
4093 100 200
300 400
Node #4
Traffic on
VLAN 400
Subtended NE
(subtending host: Node #2)
Node #1
Traffic on
VLAN 100
VLAN associations:
4093 300
Node #3
Traffic on
VLAN 300
Subtended NEs
(subtending host: Node #1)
18850
In this example:
The master subtending node, Node 1 in Figure TNG 112-1, receives the management
and customer traffic from the network and distributes it to the appropriate node.
Management traffic is sent to all nodes. Customer traffic is sent only to the appropriate
node, which is determined by the VLAN associated with the customer traffic. In the
example in Figure TNG 112-1, the customer traffic is distributed as follows.
TNG 112-2
Edition 02 Released
For each node (Node 1, Node 2, Node 3, and Node 4), configure the network port
and the SHub management VLAN.
configure interface shub port 1 port-type network
configure vlan shub id 4093 egress-port network:1
For each subtending node (Node 1 and Node 2), configure the management
VLAN ID:
configure bridge shub port 1 pvid 4093
For each node (Node 1, Node 2, Node 3, and Node 4), configure the VLAN
associated with the node:
configure vlan id 100 mode residential-bridge
configure vlan shub id 100 egress-port network:1
configure vlan id 200 mode residential-bridge
configure vlan shub id 200 egress-port network:1
configure vlan id 300 mode residential-bridge
configure vlan shub id 300 egress-port network:1
configure vlan id 400 mode residential-bridge
configure vlan shub id 400 egress-port network:1
For each node (Node 1, Node 2, Node 3, and Node 4), configure the egress ports
associated to each VLAN:
configure vlan shub id 100 egress-port lt:1/1/4
configure vlan shub id 200 egress-port lt:1/1/4
configure vlan shub id 300 egress-port lt:1/1/4
configure vlan shub id 400 egress-port lt:1/1/4
For each subtending node (Node 1 and Node 2), create and configure the VLAN
associated with the nodes subtended to it:
i
Node 1:
configure vlan shub id 200 mode residential-bridge
configure vlan shub id 200 egress-port network:1
configure vlan shub id 300 mode residential-bridge
configure vlan shub id 300 egress-port network:1
ii
Node 2:
configure vlan shub id 400 mode residential-bridge
configure vlan shub id 400 egress-port network:1
TNG 112-3
Edition 02 Released
For each subtending node (Node 1 and Node 2), configure the subtending ports for
each subtending node:
i
Node 1:
configure interface shub port 3 port-type subtending
configure vlan shub id 4093 egress-port network:3
configure vlan shub id 200 egress-port network:3
configure vlan shub id 300 egress-port network:3
ii
Node 2:
configure interface shub port 3 port-type subtending
configure vlan shub id 4093 egress-port network:3
configure vlan shub id 400 egress-port network:3
TNG 112-4
Edition 02 Released
Re-initialization triggers
Multi-ADSL configuration management
Line operation configuration
Multi-ADSL common configuration parameters
Flavor-dependent configuration parameters
ADSL2plus-specific configuration parameters
Supported operational data parameters
TNG 113-1
Edition 02 Released
Re-initialization triggers
During showtime (L0 line state), the Multi-ADSL Modem Subsystem performs
persistency/severity checking and correlation on the defects/anomalies, in order to detect
re-initialization triggers. Table TNG 113-1 lists them for the ATU-C and includes the
required persistency time for each showtime error.
Table TNG 113-1: Re-initialization triggers
Related Defect/Anomaly
Far-End
(f)los
5 1 sec
6 1 sec
sef/rdi
5 1 sec
6 1 sec
(f)lom
60 1 sec
60 1 sec
(f)se
10 1 sec
10 1 sec
(f)ncd
15 1 sec
17 1 sec
(f)lcd
15 1 sec
17 1 sec
(f)npd/(f)lpd
15 1 sec
15 1 sec
Note All the triggers, except los and sef based triggers, make up the
high-ber-hs condition, specified in G.992.3 ([6]), annex D. The
Multi-ADSL modem subsystem implements correct state behavior as
specified in the different standards, according to the actual operation
mode,
The Multi-ADSL modem subsystem triggers/initiates re-activation of the modem when
any of those triggers is fired. No other re-initialization triggers (annex timer values) are
used by the modem subsystem than the ones mentioned in Table TNG 113-1.
All the far-end countdown timers are frozen when any near-end defect occurs. When all
the near-end defects have disappeared, the far-end count-down timers resume from the
frozen values (ignoring the in-between time).
All the near-end defects are correlated independent from each other. The same holds for
all the far-end defects in absence of near-end defects.
TNG 113-2
Edition 02 Released
In case a parameter is indicated as optional, the input value is do not care, and any
value is accepted without having impact on the modem subsystem behavior.
In case a parameter is indicated to be required to a certain level (for example, only a
limited set of defined number of input values), only input values corresponding to the
required level are accepted. If the input parameter is not accepted, the modem
subsystem raises a failure indication to the xDSL manager indicating Configuration
Error
In case extra consistency checks need to be performed on a parameter or between
parameters and the configuration should be rejected, rejection always means that
the modem subsystem raises a failure indication to the xDSL Manager indicating
Configuration Error, rather that a returned error of the considered xDSL API call.
An xDSL API configuration request is replied with an error only when the call is done
in a wrong administrative state.
TNG 113-3
Edition 02 Released
Operating modes
Auto-mode criterion
Rate adaptation mode
Target noise margin
Minimum noise margin
Maximum noise margin
Carrier mask
RF band data
Minimum bitrate
Maximum bitrate
Rate adaptation ratio
Maximum interleaving delay
Minimum impulse noise protection
L3 Power State Permission
L2 Power State Permission
L0 Time
L2 Time
L2 ATPR
L2 Bitrate Downstream
L2 ATPRT
Bonding Mode
BondingGroupId
Upshift Noise Margin
Downshift Noise Margin
Minimum Time Interval for Upshift Rate Adaptation
Minimum Time Interval for Downshift Rate Adaptation
Artificial Noise PSD
Impulse Noise Monitor (INM):
INM Sensitivity Threshold
INM Pulse-Gap-Bridging Value
Warm Re-Init Disable
Programmable Resynch Triggers
TNG 113-4
Edition 02 Released
Operating Modes
Description
This parameter defines which standards are allowed for the Modem Subsystem
for line activation.
Different DSL standards can be allowed by the XDSL Manager. The Modem
Subsystem does the following:
check if allowed modes are not conflicting (see MGMT_R12), and raise an
error if there is a conflict.
if allowed modes are accepted, try to initialize with peerend modem in one
of the allowed operation modes. Selection of best-fit mode shall be done
according to MGMT_R13.
Instances
Line
Values
Bitmap:
ANSI.T1.413 (1998)
Alcatel-proprietary ETSI mode
G.992.1 Annex A & B, each overlapped & non-overlapped
G.992.2 Annex A (non-overlapped) & B (overlapped)
G.992.3 Annex A, B, I, J & L, M each overlapped & nonoverlapped
G.992.4 Annex A & I, each overlapped & non-overlapped
G.992.5 Annex A, B & I, M each overlapped & non-overlapped
Auto-Mode Criterion
Description
This parameter shall be used to set the policy to select optimal operation mode
in case READSL2 operation mode has been enabled. If no READSL2 operation
mode has been set by the xDSL Manager, this parameter shall be ignored.
Currently, three policies are defined:
Line
Values
Bitmap:
ANSI.T1.413 (1998)
Alcatel-proprietary ETSI mode
G.992.1 Annex A & B, each overlapped & non-overlapped
G.992.2 Annex A (non-overlapped) & B (overlapped)
G.992.3 Annex A, B, I, J & L, M each overlapped & nonoverlapped
G.992.4 Annex A & I, each overlapped & non-overlapped
G.992.5 Annex A, B & I, M each overlapped & non-overlapped
TNG 113-5
Edition 02 Released
Description
Remarks:
In case the CPE does not support SRA or if a line initializes in an XDSL flavour
(f.i. ADSL1) which does not support SRA, RA mode 3 behavior shall be identical
to RA mode 2. In state L2, no Downstream SRA bit rate change is allowed.
Instances
Values
Line DS, US
RaModeManual
RaModeAtInit
RaModeDynamic
TNG 113-6
Edition 02 Released
Description
Instances
DS, US
Values
0.0..31.0
0.1 dB
Description
Instances
DS, US
Values
0.0..31.0
0.1 dB
TNG 113-7
Edition 02 Released
Description
Specifies the maximum noise margin sustained by the modem. This parameter
is both used during initialization and in showtime.
during initialization:
When the noise margin for transport configuration is higher than the
Maximum Noise Margin, then the modem takes action to reduce the
power to get the actual noise margin below this value.
When the noise margin is lower than the Maximum Noise Margin, then
the modem tries to optimize the Receive Power below the configured
masks to get the noise margin as high as possible (still below the
Maximum Noise Margin).
in showtime:
When the current noise margin gets above the Maximum Noise Margin,
the modem attempts to reduce the far-end output power to get the noise
margin below this limit (by means of bit-swap actions).
When the current noise margin gets below the Maximum Noise Margin,
then the ATU attempts to increase the far-end output power (still below
the maximum allowed templates or masks) to get the noise margin as
high as possible (by means of bits-swap actions).
DS, US
Values
0..51.1
0.1 dB
For clarification, Figure TNG 113-1 gives an overview of the noise margin parameters,
and the required actions from the modem.
Figure TNG 113-1: Noise margin parameters
TNG 113-8
Edition 02 Released
Carrier mask
Description
The Carrier Mask specifies the sub-carriers that can be used for data transport
by the Modem Subsystem. There is one mask for each direction. A sub-carrier
shall be masked, i.e. not used for data transport (bi=gi=0), when the XDSL
manager has set the bit for that sub-carrier to 1.
The total number of carriers for which the mask is specified: 512 (carrier #0 to
carrier #511).
The usage of this information depends on the actual used operation mode:
ADSL1x :
US : modem subsystem shall request no bits and no power on masked
sub-carriers in bit loading process.
DS : modem subsystem shall not transmit masked sub-carriers during
medley signal.
ADSL2x :
US & DS : masked sub-carriers shall be indicated as not supported in
G.hs CL messages.
Note 1: Besides respecting the carrier mask, the modem subsystem must also
respect the standard band plans and configured PSD masks. This means that
the fact that a sub-carrier is not masked in one direction does not necessarily
mean that it can be used for data transmission in that direction.
Note 2 : In ADSL1x operation modes, when carrier masking is applied, and
modem initialization continuously fails, the masking may be suspected as cause
for these init problems. Therefore, when conditions for activation failures CMP
or CNF are met, the modem subsystem replaces them by CE activation failure
if masking is applied on carriers between tone 60 and 100, and the selected
operational mode is ADSL1x mode.
Instances
US, DS
Values
TNG 113-9
Edition 02 Released
RF Band Data
Description
Specifies the list of RF bands (HAM band or AM band) for egress control and
ingress canceling.
Egress requirements shall be used in ADSL2plus operation mode, but with
some minor modifications (see Figure TNG 113-2): the modem subsystem shall
determine all PSD points based on the RF band Start and Stop frequency given
by the operator. For this it will take into account the PSD shape or Custom PSD
shape parameters.
1. PSD(i+1), PSD5,PSD6 and PSD(i+4) to be determined by the modem based
on ALA MIB "Custom Shape" parameter (MGMT_R11.2) (and the PSD shape
(MGMT_R11.1) )
2. PSD(i+2) = PSD(i+3) = -80 dBm/Hz fixed in ALA TRS(MGMT_R9.8)
3. t(i+2)= RFI_f_start and t(i+3)= RFI_f_stop as specified in ALA MIB "RF band"
parameter (MGMT_R9.0)
4. t(i+1) and t(i+4) to be determined by the modem based on MIB specified
"Custom Shape" parameter (MGMT_R11.2) and the PSD shape
(MGMT_R11.1))
In other operation modes, egress control is optional.
Ingress parameter is for information of the Multi-ADSL modem subsystem,
usage for RFI canceling purposes is vendor discretionary.
Egress control of up to 2 different RF bands simultaneously shall be supported.
Any RF bands configured shall affect the PSD shape even if DPBO (see XXXX)
is active.
Instances
Line
Values
From these 8 specified RF bands, only 2 are relevant for the spectra used by
the different ADSLx operation modes (and especially ADSL2plus). All other
bands will be specified for higher frequencies, typically in VDSL bands.
The Modem Subsystem scans the complete set of RF bands, checks the start
frequency for each band, and only considers the bands, which are in-band for
the current operation mode. All other RF bands are ignored.
When the number of RF bands to be considered is higher than the supported
number of RF bands (min 2 for the spectra used by the different ADSLx
operation modes ), the Modem Subsystem generates a configuration error
towards the XDSL Manager.
Granularity & Unit
TNG 113-10
Edition 02 Released
Figure TNG 113-2: Restrictions on breakpoints and PSD mask for RFI band
specification
PSD in
dBm/Hz
Limitmask(f)
< 33.5 dB
PSD(i+1)
< 33.5 dB
PSD5
PSD6
PSD(i+4)
PSD(i+2)
PSD(i+3)
t(i+1)
t(i+2)
t(i+3) t(i+4)
Tone index
TNG 113-11
Edition 02 Released
Minimum Bitrate
Description
Defines the minimum requested bitrate which will be set up and which will be
maintained during showtime by the ATU.
Rounding of bitrate parameters is as follows:
For ADSL1x:
The Minimum Bitrate is rounded up and the Maximum Bitrate is rounded
down according to the bitrate granularity (32 kbps) when for the
corresponding direction Maximum Bitrate Minimum Bitrate after rounding.
Otherwise, both bitrates are rounded up and Minimum Bitrate = Maximum
Bitrate after rounding.
In case of the current showtime makes use of s=0.5 in dowstream, the
downstream bitrate granularity is 64 kbps instead of 32 kbps.
For ADSL2:
The accuracy of the bit rates parameters "net_max" and "net_min" passed
in G.Hs have a granularity of 4kb/s.
G9923_net_max = rounddown_to_next_4k ( G9971_maximum_datarate)
G9923_net_min = roundup_to_next_4k ( G9971_minimum_datarate)
For ADSL2plus:
The accuracy of the bit rates parameters "net_max" and "net_min" passed
in G.Hs have a granularity of 8kb/s.
G9925_net_max = rounddown_to_next_8k (G9971_maximum_datarate)
G9925_net_min = roundup_to_next_8k ( G9971_minimum_datarate)
General
If G992x_net_max < G992x_net_min then new G992x_net_max =
G992x_net_min = highest of both
In other words: in case of ADSL2 fixed rate (i.e.
G9923_net_max=G9923_net_min), the value exchanged during the
handshake can be up to 4kb/s above the user specified value and the actual
bitrate value in showtime can be 8kb/s above the value exchanged during
the handshake which means in G992.3 the actual rate can be up to
4kb/s+8kb/s=12 kb/s above the user configured value. For G992.5, the
actual bitrate can be up to 8kb/S+8kb/s=16 kb/s above the user configured
value.
The minimum supported data rate is be 32 kbps. Lower configured rates may
be rounded to 32 kbps.
Instances
Path DS, US
Values
0..65535
1 kbit/s
Notes
(1)
In G.lite operating mode, supported bitrates are only up to 512 kbps US and up to 1500 kbps DS.
When the minimum bitrate is configured above this limitation, and selected operation mode is G.lite,
the Multi-ADSL modem subsystem might still try to activate at this higher bitrate. If however
initializations continuously fail due to this minimum setting, the modem subsystem raises the
activation failure "Configuration not feasible on line". At the same time, the Relative Capacity
Occupation for the direction causing the problem is set to 100%.
TNG 113-12
Edition 02 Released
Maximum Bitrate
Description
Defines the maximum allowed transport bitrate which is set up and which is
maintained during showtime by the ATU. This parameter is relevant only in
'atInit' RA Mode.
For the rounding of bitrate parameters: see Table TNG 113-10.
The Multi-ADSL modem subsystem raises failure indication Configuration
Error for configurations where Maximum Bitrate < Minimum Bitrate for one of
the directions in case of the atInit RA Mode.When RA Mode is manual, the
Maximum Bitrate parameter will be ignored.
Instances
Bearer DS, US
Values
0..65535
1 kbit/s
Description
The Rate Adaptation Ratio specifies the ratio that should be taken into account
for allocating available data rate (in excess of the minimum data rate summed
over all bearer channels) among the different bearer channels in a given
direction.
The ratio is defined as a percentage from 0 to 100. The sum of the raRatios for
all bearers must be 100.
The excessive bitrate (that is, the available bitrate minus the sum of the
minimum bitrates) must be distributed among the different bearers according to
their respective raRatio.
When the maximum bitrate is achieved for one of the bearers, the raRatio of that
bearer must be distributed to the other bearers according to their respective
raRatio share.
This parameter is only meaningful in case multiple bearers are used (for
example, 2 for dual latency) and is ignored in case of single latency.
Instances
Bearer DS, US
Values
0..100
1%
TNG 113-13
Edition 02 Released
Description
Instances
Values
Bearer DS, US
0 - 63. All integer values between these borders shall be supported.
1 ms
TNG 113-14
Edition 02 Released
Description
Instances
Values
Bearer DS, US
0.0 to 8.0 DMT Symbols.
INP_min = 0 is a special value indicating no impulse noise protection bound is
being imposed
If the CO modem subsystem is not able to follow the minimum INPrequirement,
it raises the activation failure " configuration not feasible".
The modem subsystem checks standard compliancy of the CPE, i.e. the CO
checks whether the actual INP proposed by the CPE is > the CPE_INP_min.
If the CPE doesn't follow the Minimum INP requirement, the modem subsystem
raises the activation failure.
The INP implementation is applicable both for ADSL2x and ADSL1x operating
mode
Notes
(1)
Support of INP_min values 4 and 8:
The ITU standards require mandatory support of the INP_min values 0.0, 0.5, 1.0 and 2.0 while
support of the INP_min values 4 and 8 is optional. This MGMT-requirement requests support of
INP_min values 4 and 8.
(2)
Support of INP_min=2 up to the highest supported DS and US interleaved net data rates.
The ATU-C shall support bitrates up to 2.6 Mbps upstream and 22.8 Mbps downstream for INP_min
=2. This proprietary behaviour shall be coupled to the modem features bitmap.
Note: This means support of higher interleaving depth D_ds > 64, D_us > 8. In case ATU-C or ATU-R
is not supporting these bitrates the following behavior (as mentioned in ITU) is applicable:
Configuration of Minimum Net Data rates such that the sum of all Minimum Net Data rates over all
bearer channels results in values higher than the ITU standard tables with min INP and maxium delay
related net data rates limits may lead to configuration errors by the ATU-C and/or initialization failures
with configuration error failure cause by the ATU-R.
(3)
TNG 113-15
Edition 02 Released
Description
This bit controls allowed link state transitions to L3 power management state:
This bit has the same interpretation for all ADSL1x and ADSL2x opmodes.
Instances
Line
Values
Description
This bit controls allowed link state transitions to L2 power management state:
Line
Values
L0-TIME
Description
Instances
Line
Values
0 to 1800 s
Unit
1s
TNG 113-16
Edition 02 Released
L2-TIME
Description
Specifies the minimum time between L2 entry and first power trim or 2
consecutive power trims.
Instances
Line
Values
0 to 1800 s
Unit
1s
Description
The proposed value of PCBds (in dB) in any L2 trim command is limited by
following constraint:
PCBds(proposed) - PCBds(current) < L2_ATPR
where
Instances
Line
Values
0 to 31 dB
1 dB
TNG 113-17
Edition 02 Released
L2 Bitrate Downstream
Description
Specifies the minimum bitrate that shall be set up during L2 state (up to eventual
rounding within 8 kbps, see Description in Table TNG 113-10).
The same value is used by the Modem Subsystem as maximum DS bitrate
measured in fixed, consecutive 1 second intervals that may not be exceeded during a time interval MAXIMUM (10s, L0-TIME) - as trigger for transition to L2
state.
In case of multiple used latency paths, the DS actual bitrate must be below the
threshold for each path during MAXIMUM (10s, L0-TIME), before transition to
L2 occurs. The total bitrate during L2 will then be at least the sum of all
configured L2 bitrates.
Note: In case L0min > L2min, additional restrictions are implemented such that
there is no possibility to swap to L2 Mode in case this would lead to a bitrate
increase.
Note: if the actual DS bitrate in L2 state is lower than the configured L2 Bitrate
Downstream (this is always the case if the configured L2 Bitrate Downstream
force an Lp larger than 1024), the modem refuses the transition to L2 state.
Instances
Bearer Channel DS
Values
0 to 65535 kbps
1 kbps
Description
Instances
Line
Values
0 to 31 dB
1 dB
TNG 113-18
Edition 02 Released
Figure TNG 113-3: Illustration of the Layer 2 power state control parameters
PSD in
dBm/ Hz
PSD2 = -36.5
PSD1 = -95
t1
t2
Bonding Mode
Description
This parameter indicates whether the bearer channel is used to carry one
complete ATM stream (native mode) or used on a pair within a bonding group
(atmBonding). In the latter case, ATM bonding is be set up according to all
requirements.
In case ATM bonding would not be supported by the chipset, a configuration
error is raised upon startUpLine command if ATM bonding would have been
configured.
Instances
Values
Bearer
Enumeration:
TNG 113-19
Edition 02 Released
BondingGroupId
Description
This parameter provides the group identification number of the bonding group
the bearer channel belongs to in case the bondingMode (see previous) is set to
atmBonding. The bonding group ID 0 is not used.
Instances
Bearer
Values
unsigned long
Instances
DS, US
Values
0.0..31.0
0.1 dB
Instances
DS, US
Values
0.0..31.0
0.1 dB
TNG 113-20
Edition 02 Released
Table TNG 113-26: Minimum Time Interval for Upshift Rate Adaptation
Name
Description
Instances
DS, US
Values
0..16383
1s
Table TNG 113-27: Minimum Time Interval for Downshift Rate Adaptation
Name
Description
Instances
DS, US
Values
0..16383
1s
Description
Values
TNG 113-21
Edition 02 Released
Description
Instances
Values
Line DS
-40 dB.. 40 dB
Default: 0 dB
0.1 dB
Description
Instances
Line DS
Values
1 - 10
Default: 0 (no Pulse-Gap-Bridging)
Description
Instances
Line
Values
Bit: 0/1
Default: 0
TNG 113-22
Edition 02 Released
Description
This array of integers controls the values of the required resynch triggers at both
the xTU-C and xTU-R. For each trigger, a special value is used for disabling.
The parameters applicable to the far-end are communicated to the CPE.
Meaning:
Persistency in seconds of [los; sef; lom; se; ncd; lcd; flos; rdi; flom; fse; fncd;
flcd]
Instances
Values
Line
[0255; c ; 0255] with a minimum of 3 seconds for (f)los
Default: [5; 5; 60; 10; 15; 15; 6; 6; 60; 10; 17; 17]
Special persistency value for each trigger: 0: disable trigger (except for (f)los)
1 second
Modem features
Maximum aggregate transmit power
Maximum value of Maximum Aggregate Transmit Power for nonoverlapped operating
modes
Maximum PSD
Maximum value of Maximum PSD
Power backoff mode
Maximum aggregate receive power
Table TNG 113-33: Modem features
Name
Modem Features
Description
Line
(1 of 2)
TNG 113-23
Edition 02 Released
Values
Bitmap
(2 of 2)
Description
Specifies the maximum total power level that is allowed to be transmitted in the
corresponding direction.
The maximum value (25.5 dBm) is used as special value to indicate that the
value defined in the corresponding Multi-ADSL standard must be used.
The usage of this parameter shall depend upon the used operation mode:
When the configured value is above the maximum aggregate transmit power
allowed by the relevant standard, the configured value is ignored.
Instances
Line DS, US
Values
0 to 25.5 dBm
0.1 dBm
The constraints imposed by the standards are summarized in Table TNG 113-35.
Table TNG 113-35: Maximum value of Maximum Aggregate Transmit Power for
nonoverlapped operating modes
MaxATP US
MaxATP DS
ADSL1/ADSL2/ADSL2plus Annex A
12.5 dBm
19.9 dBm
ADSL1/ADSL2/ADSL2plus Annex B
13.3 dBm
19.3 dBm
12.5 dBm
19.3 dBm
READSL2
12.5 dBm
18.8 dBm
Note
(1)
The aggregate transmit power across the whole passband and measured at the line terminals, must
not exceed the values of Table TNG 113-35 by more than 0.5 dB, in order to accommodate
implementation tolerances
TNG 113-24
Edition 02 Released
Maximum PSD
Description
Instances
Line DS, US
Values
0.1 dBm/Hz
Notes
(1)
The Maximum PSD parameter cannot be used to boost the PSD beyond the standard PSD, it can
only be used to put additional constraints on top of the standard. The constraints imposed by the
standards are summarized in Table 9.
Maximum PSD
DS
ADSL1/ADSL2
-38 dBm/Hz
-40 dBm/Hz
READSL2 Mode 1
-36.4 dBm/Hz
-37 dBm/Hz
READSL2 Mode 2
-32.9 dBm/Hz
-37 dBm/Hz
ADSL2plus
-38 dBm/Hz
-40 dBm/Hz
-40.4 dBm/Hz
-40 dBm/Hz
TNG 113-25
Edition 02 Released
Instances
Values
Line US
PsdPboOff
PsdPboOn
Description
Specifies the maximum allowed total receive power level allowed for ADSL2x .
This parameter shall only be used when Psd PBO parameter (see Power
backoff mode) is on.
The input shall correspond to parameter MAXRXPWR
This parameter shall be ignored for ADSL1x.
Instances
Line US
Values
0.1 dBm
TNG 113-26
Edition 02 Released
PSD shape
Custom PSD shape:
Custom DS PSD Shape
Custom US PSD Shape
PSD Shape
Description
Instances
Values
Line DS, US
Enumeration. Next PSD Shapes Tags are defined for ADSL2plus:
DOWNSTREAM:
TNG 113-27
Edition 02 Released
PSD1 = -95
t1
t2
This results in a total of 19 PSD Masks for Cabinet deployment, as illustrated in Table 10
Table TNG 113-41: ADSL2+ PSD masks for Cabinet deployment
PSD Mask
t1
t2
f1 (kHz)
f2 (kHz)
ADSL2Plus Ca 100
73
100
314.8125
431.25
ADSL2Plus Ca 110
83
110
357.9375
474.375
ADSL2Plus Ca 120
93
120
401.0625
517.5
ADSL2Plus Ca 130
103
130
444.1875
560.625
ADSL2Plus Ca 140
113
140
487.3125
603.75
ADSL2Plus Ca 150
123
150
530.4375
646.875
ADSL2Plus Ca 160
133
160
573.5
625 690
ADSL2Plus Ca 170
143
170
616.6875
733.125
ADSL2Plus Ca 180
153
180
659.8125
776.25
ADSL2Plus Ca 190
163
190
702.9375
819.375
ADSL2Plus Ca 200
173
200
746.0625
862.5
ADSL2Plus Ca 210
183
210
789.1875
905.625
ADSL2Plus Ca 220
193
220
832.3125
948.75
ADSL2Plus Ca 230
203
230
875.4375
991.875
ADSL2Plus Ca 240
213
240
918.5625
1035
ADSL2Plus Ca 250
223
250
961.6875
1078.125
ADSL2Plus Ca 260
233
260
1004.813
1121.25
ADSL2Plus Ca 270
243
270
1047.938
1164.375
ADSL2Plus Ca 280
253
280
1091.063
1207.5
TNG 113-28
Edition 02 Released
Description
The PSD shape is made by connecting the PSD points via linear or logarithmic
interpolation (as in standard).
Following rules apply:
(*)
The operator can specify a custom PSD shape with brick wall or with more
strict requirements than specified in section 8.5.1 of G.992.5. It's the
responsibility of the modem subsystem to translate these requirements
according to the section 8.5.1 points 1-4 of G.992.5. As a minimum
requirement the modem subsystem shall at least be able to implement a
custom shape according to these standard requirements. The operator only
gets guarantees on the standard PSD shape. However this doesn't prevent
the modem subsystems to implement a PSD shape that approximates the
operator custom PSD shape more closely.
The RFI band specification is described in RF band data
The successive PSD points must have increasing ( ) frequencies.
It is allowed that for two successive PSD points, different PSD levels are
defined at the same frequency f (brick wall):
point x: PSDx, f
point x+1: PSDx+1,f
In case DPBO parameters are specified, the Downstream Custom PSD
Shape parameter is ignored.
Reject shall be done by raising the "Configuration Error" failure.
Instances
Line DS
Values
TNG 113-29
Edition 02 Released
Description
The PSD shape is made by connecting the PSD points via linear or logarithmic
interpolation (as in standard).
Following rules apply:
(*)
The operator can specify a custom PSD shape with brick wall or with more
strict requirements than specified in section 8.5.1 of G.992.5. It's the
responsibility of the modem subsystem to translate these requirements
according to the section 8.5.1 points 1-4 of G.992.5. As a minimum
requirement the modem subsystem shall at least be able to implement a
custom shape according to these standard requirements. The operator only
gets guarantees on the standard PSD shape. However this doesn't prevent
the modem subsystems to implement a PSD shape that approximates the
operator custom PSD shape more closely.
The successive PSD points must have increasing ( ) frequencies.
It is allowed that for two successive PSD points, different PSD levels are
defined at the same frequency f (brick wall):
point x: PSDx, f
point x+1: PSDx+1,f
Reject shall be done by raising the "Configuration Error" failure.
Instances
Line US
Values
TNG 113-30
Edition 02 Released
Description
The operational mode used for the current operation of the Multi-ADSL modem
subsystem (see Operating modes).
Instances
Line
Values
Initialization value
Update frequency
NA
TNG 113-31
Edition 02 Released
Description
The total set of operational modes supported by the ATU-C and the ATU-R
respectively.
Instances
ATU-C / ATU-R
Values
Update frequency
NA
Initialization value
ATU-C: parameter reflects all the standards the modem chipset is able to
support.
ATU-R: parameter reflects the CPE supported standards indicated in G.hs. If
ANSI or ETSI activation tones have been detected, also the operation mode bits
for these mode are set.
SNR Margin
Description
Indicates the current noise margin relative to the noise power that the ATU can
tolerate and still meet the target BER of 10-7 at 0 dB noise margin accounting
for all coding gains included in the design.
The SNR Margin given shall be the average of the margins (expressed in dB) of
all loaded carriers.
ADSL2:
According to ADSL2 standard an SNRM value of -512 is a special value
indicating that signal to noise ratio margin is out of range.
For downstream this special value -512 is translated to 51.2 dB.
For upstream the complete range -64 to 63 dB can be used
Instances
DS/US
Values
-64.0..+63.0 dB
0.1 dB
Accuracy
0.5 dB
Update frequency
Loop Attenuation
Description
The difference in dB between the power received at one end and that
transmitted at the opposite end over all subcarriers during initialization. It is not
updated during showtime.
Instances
DS/US
(1 of 2)
TNG 113-32
Edition 02 Released
Values
0..102.3 dB
Note: when the actual loop attenuation is exceeding an extremum value that can
be represented, clamping to this extremum representable value is done.
0.1 dB
Accuracy
0.5 dB
Update frequency
NA
(2 of 2)
Signal Attenuation
Description
The difference in dB between the power received at one end and that
transmitted at the opposite end over all subcarriers during showtime.
Note: difference with Loop Attenuation is that the transmit power has changed
for the subcarriers and that the total number of subcarriers during showtime
typically will be less than during initialization.
Instances
Values
DS/US
0..102.3 dB
Note: when the actual loop attenuation is exceeding an extremum value that can
be represented, clamping to this extremum representable value is done.
0.1 dB
Accuracy
0.5 dB
Update frequency
TNG 113-33
Edition 02 Released
Description
Actual aggregate output power (that is, the total output power for the carriers of
the corresponding direction) when the modem is in showtime.
Instances
DS/US
Values
-31.0..+31.0 dBm
Note: when the actual aggregate transmit power is exceeding an extremum
value that can be represented, clamping to this extremum representable value
is done.
0.1 dBm
Accuracy
Update frequency
Actual Tx PSD
Description
Actual transmit power spectrum density over the subcarriers at the U interface,
including artificial noise.
Instances
DS/US
Values
-127.0 to 0 dBm/Hz.
A value indicated as noPSD is a special value. It indicates that no power is
transmitted on that carrier.
0.1 dBm/Hz
Accuracy
0.1 dBm/Hz
Update frequency
Description
Instances
DS/
(1 of 2)
TNG 113-34
Edition 02 Released
Values
0 to 32
Update frequency
Not Applicable
(2 of 2)
Description
Indicates the maximum bitrate the modem can sustain on the line (i.e. the ATM
payload plus all overhead from the PMD, PMS-TC and TPS-TC layers) taking
the current configuration (INP, delay, carriermask, coding ) into account (e.g.
assuming same type of coding gain). If multiple bearer channels are active, the
calculation assumes that all capacity would be allocated to the bearer channel
with the highest coding gain.
Note: the ATU-C takes the CPE capabilities into account (e.g. if the CPE does
not support S=1/2, even if the CO supports S=1/2 the reported rate is the value
without S=1/2 support)
The accuracy of this attainable line bitrate is 10 %. This means that if the modem
retrains - without change in loop or noise conditions - the actual line bitrate is
within 10% of the reported attainable line bitrate before re-initialisation.
Instances
Values
DS/US
0..65535
Remark: in case of no EOC, the initialization value for Attainable DS Line Bitrate
is returned.
1 kbps
Update frequency
Description
The total line rate currently set up by PMD layer (i.e. the actual ATM payload
plus all overhead information from the PMD, PMS-TC and TPS-TC layers). The
Line Bitrate is given by the number of bits per DMT symbol, multiplied with the
number of DMT symbols per second, divided by 1000 (kbps).
Instances
DS/US
Values
0..65535
1 kbps
Update frequency
TNG 113-35
Edition 02 Released
Description
The ratio of the Actual Line Bitrate and the Attainable Line Bitrate when both are
available.
In case of an activation error Configuration not feasible, it is set to 100 % for
each direction where the minimum bitrate cannot be sustained.
Note : L2 state transitions shall be transparent, i.e. DS Line Relative Capacity
Occupation shall always be L0 line bitrate, even if line state is L2 !
Instances
DS/US
Values
0..100%
1%
Update frequency
Description
Indicates the maximum ATM bitrate (i.e. ATM payload plus header bytes) the
ATU can sustain on the line taking the current configuration (INP, delay,
carriermask, coding ) into account, with margin not lower than Target Noise
Margin. This parameter is provided for each activated bearer channel. The
calculation estimates the attainable ATM Bitrate assuming that all available
capacity is allocated to that bearer channel.
Note: the ATU-C takes the CPE capabilities into account (e.g. if the CPE does
not support S=1/2, even if the CO supports S=1/2 the reported rate is the value
without S=1/2 support)
The accuracy of this attainable ATM bitrate is 10 %. This means that if the
modem retrains - without change in loop or noise conditions - the actual ATM
bitrate is within 10% of the reported attainable ATM bitrate before
re-initialisation.
Instances
Values
0..65535
1 kbps
Update frequency
Description
The actual transport rate (that is, the transported payload plus header bytes)
expressed in kbps in the L0 state.
Instances
Values
0..65535
1 kbps
Update frequency
TNG 113-36
Edition 02 Released
Description
Instances
Values
0..63
1 ms
Update frequency
Table TNG 113-58: Actual impulse noise protection (per bearer channel)
Name
Description
Instances
Values
0..8.0 DMT symbols. Actual INP values of 16 DMT symbols will be ceiled to
actual INP of 8 DMT symbols.
Update frequency
NA
Table TNG 113-59: Actual L2 low power ATM Bitrate (per bearer channel)
Name
Description
The actual ATM rate (i.e. the ATM payload plus header bytes) expressed in
kbps in the L2 state.
Instances
Values
0 65535
1 kbps
Update frequency
Description
The total set of TPS-TC modes supported by the VTU-O and the VTU-R
respectively.
(1 of 2)
TNG 113-37
Edition 02 Released
Instances
Line Near-end/Far-end
Values
Bitmap:
TPSTCModesATMBit
TPSTCModesPTM_64_65Bit
TPSTCModesPTM_HDLCBit
Update frequency
NA
(2 of 2)
Description
Actual artificial noise power spectrum density per subcarrier at the constellation
encoder.
Instances
Values
-140 to 0 dBm/Hz
A value indicated as noPSD is a special value (default). It indicates that no
artificial noise is transmitted on that carrier.
0.1 dBm/Hz
Update frequency
TNG 113-38
Edition 02 Released
Equipment
Table TNG 114-1 lists the equipment.
Table TNG 114-1: Equipment
Equipment
Board Type
Subrack
XD
acu
aacu-c
nt-a, nt-b
ecnt-c
iont
ecnc-a
lt:1/1/4
evlt-c
lt:1/1/5
eblt-c
lt:1/1/6
polt-b
lt:1/1/7
eblt-k
lt:1/1/8
eblt-k
lt:1/1/9
smlt-k
TNG 114-1
Edition 02 Released
xDSL profiles
Table TNG 114-2 lists the configured xDSL profiles.
Table TNG 114-2: xDSL profiles
Service profile
Spectrum profile
Bonding
ID
Name
ADSL_profile
VDSL_profile
10
XSRVC_0_0
vdsl_profile
adsl_profile
GroupProfile1
Notes
(1)
Other profiles are not used for actual lines
SHub ports
Table TNG 114-3 lists the configured SHub ports.
Table TNG 114-3: SHub ports
Port
Port Type
Subtending
Subtending
Network
Network
Network
Network
Network
TNG 114-2
Edition 02 Released
VLANs
Table TNG 114-4 lists the configured VLANs.
Table TNG 114-4: VLANs
VLAN
LT mode
SHub mode
LT 1/1/x
Network port
4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 0 1 2 3 4 5 6 7
56
residential-bridge
70
layer2-term-netwport
80
layer2-term-netwport
T
T
100
residential-bridge
residential-bridge
x x x x
101
layer2-terminated
residential-bridge
x x x x x x x
200
residential-bridge
residential-bridge
x x x x x x
300
cross-connect
cross-connect
301
cross-connect
cross-connect
350
qos-aware
cross-connect
cross-connect
400
400:0
cross-connect
T
T
cross-connect
500
cross-connect
500:0
layer2-terminated
500:600
cross-connect
501
cross-connect
501:0
layer2-terminated
501:601
cross-connect
512
layer2-terminated
512:0
layer2-terminated
512:57
cross-connect
560
residential-bridge
1450
layer2-term-netwport
2200
cross-connect
cross-connect
4090
layer2-terminated
v-vlan
4093
cross-connect
401
401:0
x x x x x x
reserved
Notes
(1)
U: untagged - T: tagged
TNG 114-3
Edition 02 Released
VRFs
Table TNG 114-5 lists the VRFs on the LT.
Table TNG 114-5: LT VRFs
VRF
Mode
VLAN
Forwarder
Router
4090
16
Forwarder
101
Gateway
10.178. 14.97/27
192.168.116. 1/24
Mode
Slow-path
10
15
17
VLAN
IP Address
Slow-path
100
192.168.100.2/24
182.168.100.13
Fast-path
70
192.168.70.39/24
80
192.168.80.39/24
1450
10.178.14.85/27
4090
10.178.14.97/27
101
192.168.116. 2/24
Slow-path
10.178.14.97
192.168.116. 2
Lines
VDSL
Table TNG 114-7 lists the VDSL lines.
Table TNG 114-7: VDSL lines
Line
Mode
VLAN
1/1/4/1
Cross-connect
301
1/1/4/2
Stacked
401:0
1/1/4/3
Stacked
501:601
1/1/4/12
Residential-bridge
200
1/1/4/14
IPoE
4090
1/1/4/15
PPPoE
101
TNG 114-4
Edition 02 Released
VRF
CPE IP
Address
16
ADSL
Table TNG 114-8 lists the ADSL lines.
Table TNG 114-8: ADSL lines
Line
Mode
VLAN
VRF
CPE IP
Address
1/1/5/1
Cross-connect
300
1/1/5/2
Stacked
400:0
1/1/5/3
Stacked
500:600
1/1/5/4
QoS-aware
350
1/1/5/7
IPoA cross-connect
2200
192.168.150.2
1/1/5/8
IPoA cross-connect
512:37
192.168.1.1
1/1/5/10
PPPoA-PPPoE relay
1/1/5/12
Residential-bridge
1/1/5/13
IPoA
16
1/1/5/14
IPoE
16
1/1/5/15
PPPoE
200
10.178.14.53
Bonding
SHDSL
TNG 114-5
Edition 02 Released
IP bridge
LT-y
CPE
SHub
VLAN
100
RB
RB
Network
VRF 10
DHCP
relay
IP forwarder
CPE
VLAN
101
LT-y
VRF 16
SHub
VLAN
101
RB
L2-term
Network
VRF 17
DHCP
relay
TNG 114-6
Edition 02 Released
IP router
CPE
VLAN
4090
LT-y
VRF 5
L2-term
VLAN
1450
SHub
V-VLAN
VRF 15
L2-term-nwp
Network
router
&
DHCP
relay
10.178.14.97/27
10.178.14.85/27
TNG 114-7
Edition 02 Released
TNG 114-8
Edition 02 Released
Glossary
10/100Base-T
10Base-T
100Base-TX
1000Base-BX10-D (-U) An IEEE 802.3 LAN transmission standard for bidirectional point-to-point
1000 Mb/s Gigabit Ethernet over single-fiber for distances of up to 6.2 mi
(10 km). Always used in pairs, wavelength division multiplexing is
performed in the SFP to split the optical signal into two light paths. The
1000Base-BX10-D (downstream) transmits a 1490 nm signal and receives a
1310 nm signal. The 1000Base-BX10-U (upstream) transmits a 1310 nm
signal and receives a 1490 nm signal.
1000Base-EX
An IEEE 802.3 LAN transmission standard for 1000 Mb/s Gigabit Ethernet
using Long Wavelength (LX) laser transmitters over fiber-optic cable for
distances up to 24.9 mi (40 km).
1000Base-LX
An IEEE 802.3 LAN transmission standard for 1000 Mb/s Gigabit Ethernet
using Long Wavelength (LX) laser transmitters over fiber-optic cable for
distances up to 6.2 mi (10 km).
1000Base-SX
An IEEE 802.3 LAN transmission standard for 1000 Mb/s Gigabit Ethernet
using Short Wavelength (SX) laser transmitters over fiber-optic cable.
1000Base-ZX
An IEEE 802.3 LAN transmission standard for 1000 Mb/s Gigabit Ethernet
using Long Wavelength (LX) laser transmitters over fiber-optic cable for
distances up to 49.7 mi (80 km).
GL-1
Edition 02 Released
Glossary
3DES
Triple DES
A mode of the DES encryption algorithm that encrypts data three times
instead of once. Three 64-bit keys are used for an overall key length of 192
bits; the first encryption is encrypted with a second key, and the resulting
cipher text is encrypted with a third key.
7302 ISAM
AACU-C
AAL
AAL1
AAL2
AAL5
ACL
ACO
ACU
GL-2
Edition 02 Released
Glossary
ADSL
AES
AFAN-K
AFAN-L
AIS
AMS
AMSL
ANSI
APS
ARAM-B
Two-LT-Slot Shelf
The shelf type used for the 7330 ISAM FTTN that has two LT slots and
holds all the other shelf components. The ARAM-B shelf has mounting
flanges that enable it to be mounted horizontally in a 23-inch rack, or
horizontally or vertically in a CO, CEV, and OSP cabinet.
ARAM-D
Four-LT-Slot Shelf
The shelf type used for the 7330 ISAM FTTN and for the ES that has four
LT slots and holds all the other shelf components. The ARAM-D shelf has
mounting flanges that enable it to be mounted horizontally in a 23-inch rack,
or horizontally or vertically in a CO, CEV, or OSP cabinet.
ARP
GL-3
Edition 02 Released
Glossary
ASAM
ASCII
ASP
ATM
ATU-C
ATU-R
AVPC-A
AWG
AWS
Alcatel WorkStation
BAC
BE
Best Effort
BER
BITS
blowfish
BNC
Bayonet Neil-Concelman
A BNC connector is a locking connector for slim coaxial cables, such as
those used for Ethernet.
GL-4
Edition 02 Released
Glossary
BOOTP
Bootstrap Protocol
BOOTP is a member of the IP family of protocols that allows a diskless
client machine to learn, among other information, its IP address. BOOTP
starts a networked machine by reading boot information from a server.
BOOTP is commonly used for desktop workstations and LAN hubs.
BRAS
BRI
CAC
CBR
CCSA
CDE
CEV
CFM
CHAP
CL
Controlled Load
CLEI
CLI
GL-5
Edition 02 Released
Glossary
CMOS
CMP
CO
Central Office
Telephone switching center that connects subscribers within a telephone
network.
COLO
Collocation
CPCS
CPE
CPE-MM
CPR
CPU
CSMA/CD
CT
Craft Terminal
Workstation that has element management system software installed on it.
C-VLAN
CWDM
DA
Destination Address
DES
DES-56
See DES.
GL-6
Edition 02 Released
Glossary
DHCP
DLC
DLP
DNS
DSCP
DSL
DSLAM
DSNC-A
DSP
EAPOL
EBLT-C
GL-7
Edition 02 Released
Glossary
EBLT-E
EBLT-K
ECI
ECMP
ECNT-A
EDSE-A
EFM
eHCL
EIA
EMAN
EMS
EPS
GL-8
Edition 02 Released
Glossary
ES
Expansion Shelf
An expansion shelf using the same shelf (ARAM-D) as the
7330 ISAM FTTN host shelf, but with some different units installed to
provide additional subscriber line connections for the host shelf.
ESD
Electrostatic Discharge
ETR
ETSI
EVLT-A
FDM
FE
Fast Ethernet
FENT
FIB
FIFO
FPGA
FTP
GE
Gigabit Ethernet
Ethernet interface running at 1000 Mb/s.
GENC-E
GENC-F
GL-9
Edition 02 Released
Glossary
GFC
GUI
HCUT-C
HLPC-H
HLPC-J
HSI
IACM
iBridge
IDEA
IEEE
IETF
IGFET
IGMP
GL-10
Edition 02 Released
Glossary
IGS
INP
IP
Internet Protocol
Connectionless packet-switching protocol that works together with TCP.
IP@
IPCP
IP Control Protocol
A protocol that configures, enables, and disables the IP protocol modules on
both ends of a point-to-point link. IPCP is tied to PPP, and activated when
PPP reaches the network layer-to-protocol phase. If IPCP packets are
received prior to this phase, they are discarded.
IPoA
IPoE
IPTV
IP Video/Television
The delivery of video services over an end-to-end IP infrastructure. IPTV
can include various classes of video services including video on demand,
broadcast TV, video conferencing, and mobile video.
ISAM
ISDN
ISP
ITSC
ITU
IXL
Index List
JFET
L2-based LIMs
L3-based LIMs
GL-11
Edition 02 Released
Glossary
LACP
LAN
LANX
7330 ISAM FTTN Network Termination board Ethernet switch (also known
as SHub)
LCP
LED
LIM
LMI
LOS
Loss of Signal
A condition at the receiver or a maintenance signal transmitted in the
physical overhead, indicating that the receiving equipment has lost the
received signal.
LPF
Low-pass Filter
LFP is a single transmission band extending from zero frequency up to a
specified cutoff frequency, not infinite.
LP slot
LSA
LSDB
LSM
LT
Line Termination
GL-12
Edition 02 Released
Glossary
MAC
MAIP
MDF
MDI
Medium-Dependent Interface
MDI is a type of Ethernet port for use with twisted-pair wiring.
MDIX
MIB
MMF
Multimode Fiber
An optical fiber with a core diameter of 50 to 100 m. Most commonly used
in short distance LANs. The larger core diameter allows broader light
sources such as LEDs. Modal dispersion is a problem over longer distances.
MOS
MTA
MTAU
MTBF
Multi-ADSL
NAT
NE
Network Element
NFS
GL-13
Edition 02 Released
Glossary
NSA
Non-Service Affecting
NSP
NT
Network Termination
A plug-in unit that provides a link to a broadband network, such as ATM or
IP. The 7330 ISAM FTTN uses the ECNT-A board for network termination.
NTA slot
NTB slot
NTP
Non-Trouble Procedure
OAM
OBC
On-Board Controller
OOS
Out-of-service
The status of a primary rate link when it is out of service.
OS
Operations System
Standalone software system that supports network-related operations
functions.
OSP
Outside Plant
OSPF
OSS
OSWP
PADI
POTS
PPP
Point-to-Point Protocol
GL-14
Edition 02 Released
Glossary
PPPoE
PSD
PSTN
PVC
PVIC
PWIO-B
QoS
Quality of Service
Measure of the quality of a data communications link provided to a
subscriber.
RA
Rate Adaptation
RADIUS
RAM
RARP
RB VLAN
RDI
GL-15
Edition 02 Released
Glossary
READSL2
RED
RFC
RIP
RJ-45
The RJ-45 is a single-line jack for digital transmission over ordinary phone
wire, either untwisted or twisted. It is the interface for Ethernet standards
10Base-T and 100Base-T.
RMI
RNM
RSTP
RTL
RTU
RU
Rack Unit
A rack unit is a unit of vertical space in a standard 19-inch equipment rack.
One RU is 1.75 in. (4.45 cm).
Rx
receive
To receive or carry signals or data to a device; any part of the equipment that
converts or decodes signals or data entering the equipment into the desired
form for use by the equipment.
SA
Service Affecting
or
Source Address
GL-16
Edition 02 Released
Glossary
SAP
SATU-A
SDU
SELT
SEM
A 24-port VDSL and POTS splitter remote expansion module for the 7330
ISAM FTTN ARAM-D shelf. The SEM features a flood resistant,
environmentally hardened enclosure that is compliant with GR-950-CORE.
SFP
SFTP
SHub
7330 ISAM FTTN and 7302 ISAM Network Termination board Ethernet
switch (also known as LANX).
SI
SMF
SNMP
SNTP
SONET
SRA
SSCS
SSH
Secure Shell
GL-17
Edition 02 Released
Glossary
STP
S-VLAN
Stacked VLAN
SWDB
SoftWare DataBase
SWP
SoftWare Package
TAC
TAP
TCA
TCP
TCP/IP
TFTP
TIA
TL1
Transaction Language 1
Human-machine language standard for controlling network elements.
TNG
Training Document
TOP
Task-Oriented Practice
The TOP method is a documentation system that supports the installation,
operation, and maintenance of telecommunications equipment and software
through different layers of documentation.
Tx
transmit
To send or carry signals or data from a device; any part of the equipment that
converts or encodes signals or data exiting from the equipment into the
desired form for transmission to other equipment.
GL-18
Edition 02 Released
Glossary
UDP/IP
UDS
UPS
VBAS
VC
Virtual Channel
Single communications connection identified by an office equipment
number, VPI, and VCI.
VCC
VCI
VCL
VC/VP/VR
VDSL
VLAN
Virtual LAN
A VLAN divides a physical LAN into multiple virtual LANs whose
members are not necessarily based on location. VLAN specifications are
contained in IEEE 802.1q.
VoD
Voice on Demand
VoIP
Voice over IP
VP
Virtual Path
Single communications connection identified by an office equipment
number and a VPI.
VP/VC
VPI
GL-19
Edition 02 Released
Glossary
VPSC-D
VRF
WAN
WFQ
WRED
xDSL
XoA encapsulation
GL-20
Edition 02 Released
Index
Numbers
A
ADSL profile
configuration example, TNG 110-3
alarms
creating snapshots, DLP 154-2
fault isolation, TAP 104-1
managing, DLP 110-2
monitoring, NTP 115-1, DLP 155-1
troubleshooting, TAP 104-1
viewing alarm logs, DLP 110-2
viewing current alarms, DLP 110-2
viewing snapshots, DLP 154-2
C
CC-VLAN, NTP 104-2, TNG 100-2
configure QoS-aware VLAN, DLP 135-2
create S-VLAN, DLP 118-1
create SC-VLAN, DLP 119-2
CLI session
setting up, DLP 100-1
cluster management, NTP 122-2
configure, DLP 169-2
configuration
7330 ISAM FTTN ES, TNG 111-1
7330 ISAM FTTN subtending, TNG 112-1
backing up, RTP 100-3
IN-1
Edition 02 Released
Index
CPE management IP multicast
D
database
restore, RTP 101-1
DHCP Option 82, TNG 104-2
DHCP relay agent
conditions, TNG 104-3
configuring
forwarder mode, DLP 141-1
iBridge mode, DLP 139-2
MAC concentration, DLP 186-2
router mode, DLP 140-2
general description, TNG 104-1
parameters, TNG 104-2
restrictions, TNG 104-3
viewing, TNG 104-3
DSL profile
configuration example, TNG 110-3
F
F5 loopback test, TAP 101-1
fault isolation
alarms, TAP 104-1
events, TAP 104-1
forwarding modes
CC-VLAN, TNG 100-2
iBridge VLAN, TNG 100-2
layer 2 termination, TNG 100-2
G
GENC-E
expansion links, TNG 106-3
EDSE-A
expansion links, TNG 106-3
EMS
management, DLP 171-1
equipment
configuring, DLP 113-1
configuring and modifying, NTP 103-2
planning, DLP 111-2
repairing, NTP 114-1, TAP 102-1
replanning, DLP 111-2
restarting, DLP 153-1
shutting down, DLP 153-1
unplanning, DLP 111-2
equipment planning
configuration example, TNG 110-2
ES
CLI commands, TNG 106-1
configuration, TNG 111-1
expansion link connections, TNG 106-3
IN-2
Edition 02 Released
iBridge
add user, NTP 110-1
iBridge VLAN, TNG 100-2
configuration example, TNG 110-11
creating, DLP 120-1
IGMP
configuring IGMP proxy, DLP 137-1
parameters, TNG 102-2
system parameters
configuring, DLP 137-1
viewing configuration, TNG 102-4
IMA
configure, DLP 183-1
IP address
convert to dual IP address, DLP 184-1
convert to single IP address, DLP 184-1
IP address allocation, TNG 104-2
IP multicast
configuration guidelines, TNG 102-4
Index
IP router QoS
IP router
configure, NTP 107-2
IP-aware bridge
configure, NTP 106-2
IPoA
add cross-connect user, NTP 125-1
create cross-connect user, DLP 174-1
create user, DLP 125-1
IPoE
add user, NTP 112-1
create user, DLP 126-1
IPProxy CPE
configure management, DLP 192-1
configure session, DLP 194-1
enable management, DLP 193-1
IPProxy CPE management, NTP 128-2
L
L2CP
configure session, DLP 185-2
layer 2 termination, TNG 100-2
link aggregation
configuring, DLP 105-2
local authentication
configuring, DLP 143-1
M
MAC address, TNG 106-3
MAC concentration
configuration, DLP 186-2
MAC learning, TNG 100-5
multicast
configure on LT, DLP 136-1
configure on the SHub, DLP 198-1
configuring, DLP 137-1
N
NT redundancy
configuring, DLP 114-2
OSFP
configuring, DLP 107-2
P
password
rules, DLP 101-1
performance monitoring, NTP 118-1
commands, DLP 176-1
ping, DLP 164-1, DLP 182-1
planning equipment
configuration example, TNG 110-2
plug-in unit
locking, DLP 112-1
unlocking, DLP 112-1
plug-in units
configuring, NTP 103-1
port
view configuration, DLP 197-1
view operational data, DLP 197-1
PPPoA-PPPoE relay
disabling, DLP 147-1
enabling, DLP 147-1
PPPoE
add user, NTP 113-1
create user, DLP 127-1
enable PPPoE server, DLP 148-1
PPPoE profile
configure, DLP 149-1
PPPoE relay
disabling, DLP 146-2
enabling, DLP 146-2
PPPoE termination
configure, NTP 109-1
Q
QoS
configuring
L2, DLP 133-1
L3, DLP 134-1
QoS-aware VLAN, DLP 135-2
configuring on the SHub, DLP 199-1
operator
create default profile, DLP 172-1
Alcatel 7302 ISAM R3.2 February 2007
Operations and Maintenance Using CLI 3HH-04065-AAAA-TQZZA
IN-3
Edition 02 Released
Index
R system parameter
R
rack
configuring, DLP 113-1
RADIUS
configuring, DLP 144-1
operator authentication, DLP 181-1
remote expansion units, TNG 110-1
remote inventory
retrieving information, RTP 102-1
RIP
configuring, DLP 108-1
RSTP
configuring, DLP 106-2
S
S-VLAN
create, DLP 118-1
SC-VLAN
create, DLP 119-2
script files, NTP 101-1
create, DLP 167-1
secure shell, NTP 123-1
security domain
creating, DLP 142-1
creating default domain, DLP 178-1
SELT, TAP 103-1
SEM
CLI commands, TNG 106-1
expansion link connections, TNG 106-3
identifying, TNG 106-1
MAC address, TNG 106-1
planning, TNG 106-3
services
adaptation, NTP 119-1
configuring, NTP 108-1
SHDSL
configuration parameters
segment, TNG 108-13
span, TNG 108-3
unit, TNG 108-12
IN-4
Edition 02 Released
Index
T xDSL profile
T
TCA
configure, DLP 190-2
traceroute, DLP 165-1
traffic
configuration example, TNG 110-5
trap
configuring, DLP 109-2
reporting modes, DLP 109-1
troubleshooting
alarms, TAP 104-1
events, TAP 104-1
troubleshooting commands, NTP 120-1
U
unicast configuration, TNG 100-5
user
create IPoA user, DLP 125-1
create IPoE user, DLP 126-1
create PPPoE user, DLP 127-1
create xDSL user, DLP 124-1
creating and configuring, DLP 101-2
Voice SIP
configure, DLP 196-1
VRF
creating, DLP 121-1
forwarding VRF, DLP 122-1
router VRF, DLP 123-1
X
xDSL
create user, DLP 124-1
xDSL bonding group
create, DLP 130-2
create profile, DLP 130-2
xDSL profile
create, DLP 173-1
custom PSD points
ADSL2+, DLP 188-2
VDSL, DLP 188-2
VDSL2, DLP 188-2
modify, DLP 163-1
types, DLP 129-1
VDSL2 virtual noise, DLP 189-2
V
VDSL profile
configuration example, TNG 110-3
verifying configuration, DLP 113-1
VLAN
add an LT to a VLAN, DLP 128-1
add network interfaces, DLP 121-1
configure iBridge VLAN, NTP 105-2,
NTP 127-1
configuring global parameters, DLP 187-1
creating, DLP 115-3, DLP 116-3
cross-connect VLAN configuration
example, TNG 110-12
iBridge VLAN configuration example,
TNG 110-11
modifying
external management VLAN,
DLP 162-1
subtending configuration for 7330 ISAM
FTTN, TNG 112-1
Alcatel 7302 ISAM R3.2 February 2007
Operations and Maintenance Using CLI 3HH-04065-AAAA-TQZZA
IN-5
Edition 02 Released
Index
IN-6
Edition 02 Released
Technical support
http://www.alcatel.com/support/