3HH-10693-AAAA-TQZZA-02-System Description For FD 24Gbps NT R4 4 X

Alcatel-Lucent 7302
INTELLIGENT SERVICES ACCESS MANAGER
Alcatel-Lucent 7330
INTELLIGENT SERVICES ACCESS MANAGER FIBER TO THE NODE
Alcatel-Lucent 7356
INTELLIGENT SERVICES ACCESS MANAGER FIBER TO THE BUILDING
SYSTEM DESCRIPTION FOR FD 24GBPS NT
R 4 . 4 . 02
3 H H - 1 0693- AAAA-T QZZA E ditio n 0 2 Re le ase d
Alcatel-Lucent Proprietary
This document contains proprietary information of Alcatel-Lucent and is not to be disclosed
or used except in accordance with applicable agreements.
Copyright 2012 © Alcatel-Lucent. All rights reserved.
Alcatel-Lucent assumes no responsibility for the accuracy of the information presented, which is
subject to change without notice.
Alcatel, Lucent and the Alcatel-Lucent logo are registered trademarks of Alcatel-Lucent. All other
trademarks are the property of their respective owners.
Copyright 2012 Alcatel-Lucent.

All rights reserved.
Disclaimers
Alcatel-Lucent products are intended for commercial uses. Without the appropriate network design
engineering, they must not be sold, licensed or otherwise distributed for use in any hazardous
environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft
navigation or communication systems, air traffic control, direct life-support machines, or weapons
systems, in which the failure of products could lead directly to death, personal injury, or severe physical
or environmental damage. The customer hereby agrees that the use, sale, license or other distribution
of the products for any such application without the prior written consent of Alcatel-Lucent, shall be at
the customer's sole risk. The customer hereby agrees to defend and hold Alcatel-Lucent harmless from
any claims for loss, cost, damage, expense or liability that may arise out of or in connection with the
use, sale, license or other distribution of the products in such applications.
This document may contain information regarding the use and installation of non-Alcatel-Lucent
products. Please note that this information is provided as a courtesy to assist you. While Alcatel-Lucent
tries to ensure that this information accurately reflects information provided by the supplier, please refer
to the materials provided with any non-Alcatel-Lucent product and contact the supplier for
confirmation. Alcatel-Lucent assumes no responsibility or liability for incorrect or incomplete
information provided about non-Alcatel-Lucent products.
However, this does not constitute a representation or warranty. The warranties provided for
Alcatel-Lucent products, if any, are set forth in contractual documentation entered into by
Alcatel-Lucent and its customers.
This document was originally written in English. If there is any conflict or inconsistency between the
English version and any other version of a document, the English version shall prevail.
When printed by Alcatel-Lucent, this document is printed on recycled paper.

Preface
This preface provides general information about the documentation set for the
7302 Intelligent Services Access Manager (7302 ISAM), the 7330 Intelligent
Services Access Manager Fiber to the Node (7330 ISAM FTTN) and the 7356
Intelligent Services Access Manager Fiber to the Building (7356 ISAM FTTB).
Scope
This documentation set provides information about safety, features and
functionality, ordering, hardware installation and maintenance, CLI and TL1
commands, and software upgrade and migration procedures.
Audience
This documentation set is intended for planners, administrators, operators, and
maintenance personnel involved in installing, upgrading, or maintaining the
7302 ISAM, the 7330 ISAM FTTN or the 7356 ISAM FTTB.
Readers must be familiar with general telecommunications principles.
Acronyms and initialisms

The expansions and optional descriptions of most acronyms and initialisms appear
in the glossary.
Assistance and ordering phone numbers

Alcatel-Lucent provides global technical support through regional call centers.
Phone numbers for the regional call centers are available at the following URL:
http://www.alcatel-lucent.com/myaccess.
Alcatel-Lucent 7302 ISAM | 7330 ISAM FTTN | 7356 ISAM FTTB R4.4.02 July 2012 iii
3HH-10693-AAAA-TQZZA Edition 02 Released System Description for FD 24Gbps NT
Preface
For ordering information, contact your Alcatel-Lucent sales representative.
Safety information
For safety information, see the Safety Manual for your product.
Documents
Refer to the Product Information document for your product to see a list of all the
relevant customer documents and their part numbers for the current release.
Customer documentation is available for download from the Alcatel-Lucent Support
Service website at http://www.alcatel-lucent.com/myaccess.
Product Naming
When the term “ISAM” is used alone, then the 7302 ISAM, the 7330 ISAM FTTN
and the 7356 ISAM FTTB are meant. If a feature is valid for only one of the products,
the applicability will be explicitly stated.
Special information
The following are examples of how special information is presented in this
document.
Danger — Danger indicates that the described activity or situation
may result in serious personal injury or death; for example, high
voltage or electric shock hazards.
Warning — Warning indicates that the described activity or situation

may, or will, cause equipment damage or serious performance
problems.
Caution — Caution indicates that the described activity or situation

may, or will, cause service interruption.
Note — A note provides information that is, or may be, of special

interest.
Procedures with options or substeps

When there are options in a procedure, they are identified by letters. When there are
required substeps in a procedure, they are identified by roman numerals.
iv July 2012 Alcatel-Lucent 7302 ISAM | 7330 ISAM FTTN | 7356 ISAM FTTB R4.4.02
System Description for FD 24Gbps NT Edition 02 Released 3HH-10693-AAAA-TQZZA
Preface
Procedure 1 Example of options in a procedure
At step 1, you can choose option a or b. At step 2, you must do what the step indicates.
1 This step offers two options. You must choose one of the following:
a This is one option.
b This is another option.
2 You must perform this step.
Procedure 2 Example of required substeps in a procedure
At step 1, you must perform a series of substeps within a step. At step 2, you must do
what the step indicates.
1 This step has a series of substeps that you must perform to complete the step. You
must perform the following substeps:
i This is the first substep.
ii This is the second substep.
iii This is the third substep.
2 You must perform this step.
Release notes
Be sure to refer to the release notes (such as the Customer Release Notes or
Emergency Fix Release Note) issued for software loads of your product before you
install or use the product. The release notes provide important information about the
software load.
Alcatel-Lucent 7302 ISAM | 7330 ISAM FTTN | 7356 ISAM FTTB R4.4.02 July 2012 v
Preface
vi July 2012 Alcatel-Lucent 7302 ISAM | 7330 ISAM FTTN | 7356 ISAM FTTB R4.4.02
Contents
Preface iii
Scope ............................................................................................... iii
Audience ............................................................................................... iii
Acronyms and initialisms ............................................................................. iii
Assistance and ordering phone numbers ........................................................... iii
Safety information ..................................................................................... iv
Documents .............................................................................................. iv
Product Naming ........................................................................................ iv
Special information.................................................................................... iv
Release notes............................................................................................ v
1— Introduction 1-1
1.1 General ................................................................................... 1-2
1.2 Supported User Interfaces ............................................................. 1-2
1.3 Document Structure .................................................................... 1-3
2— System interface overview 2-1

2.1 General ................................................................................... 2-2
2.2 Overview ................................................................................. 2-2
2.3 Multi-ADSL................................................................................ 2-4
2.4 VDSL ....................................................................................... 2-7
2.5 SHDSL .................................................................................... 2-10
2.6 Ethernet ................................................................................. 2-11
2.7 Inverse multiplexing for ATM......................................................... 2-13
2.8 ATM/PTM bonding...................................................................... 2-13
2.9 Overview of ISAM Voice interfaces .................................................. 2-14
2.10 E1 TDM Interface ....................................................................... 2-15
2.11 Overview of ISAM support for remote management of third-party
equipment. ....................................................................... 2-15
Alcatel-Lucent 7302 ISAM | 7330 ISAM FTTN | 7356 ISAM FTTB R4.4.02 July 2012 vii
Contents
3— Failure protection and redundancy provisions in ISAM 3-1

3.1 Overview ................................................................................. 3-2
3.2 ISAM single shelf configurations ...................................................... 3-5
3.3 ISAM subtending system protection ................................................. 3-12
3.4 Failure protection at layer 3 ......................................................... 3-15
3.5 Network path connectivity protection .............................................. 3-15
4— Management 4-1
4.1 Overview ................................................................................. 4-2
4.2 Management interfaces ................................................................ 4-3
4.3 Management interfaces security..................................................... 4-13
4.4 Management access models .......................................................... 4-15
4.5 Counters and statistics ................................................................ 4-18
4.6 Alarm management .................................................................... 4-18
4.7 Software and database management ............................................... 4-26
4.8 Equipment monitoring................................................................. 4-28
4.9 Access node control protocol ........................................................ 4-30
5— Line testing features 5-1

5.1 Overview ................................................................................. 5-2
5.2 Metallic test access ..................................................................... 5-4
5.3 Single-Ended Line Testing ............................................................. 5-7
5.4 Dual-ended line testing ................................................................ 5-8
5.5 Metallic-Ended Line Testing ........................................................... 5-9
5.6 ATM F5 ................................................................................... 5-10
5.7 Link Related Ethernet OAM ........................................................... 5-10
5.8 Narrowband Line Testing ............................................................. 5-12
5.9 SFP diagnostics ......................................................................... 5-15
6— Network timing reference support in ISAM 6-1

6.1 Introduction .............................................................................. 6-2
6.2 ISAM clock system and NTR extraction .............................................. 6-7
6.3 Downstream NTR clock distribution ................................................. 6-17
6.4 Applicable standards .................................................................. 6-18
7— xDSL features 7-1

7.1 Overview ................................................................................. 7-2
7.2 Configurable impulse noise protection .............................................. 7-3
7.3 RFI Notching ............................................................................. 7-4
7.4 Low-power modes....................................................................... 7-4
7.5 Seamless rate adaptation .............................................................. 7-6
7.6 Upstream power back-off.............................................................. 7-8
7.7 Downstream power back-off .......................................................... 7-9
7.8 Impulse noise monitor ................................................................. 7-10
7.9 Virtual noise ............................................................................ 7-11
7.10 Artificial noise .......................................................................... 7-12
7.11 Physical Layer Retransmission (RTX) ................................................ 7-13
7.12 Per-line configuration overrule ...................................................... 7-14
viii July 2012 Alcatel-Lucent 7302 ISAM | 7330 ISAM FTTN | 7356 ISAM FTTB R4.4.02
Contents
7.13 Configurable US/ DS memory split .................................................. 7-15

7.14 Vectoring ................................................................................ 7-15
7.15 Fall-back configuration for vectoring ............................................... 7-17
8— Integrated Voice service: ISAM Voice 8-1

8.1 Introduction .............................................................................. 8-3
8.2 Overall network topology .............................................................. 8-3
8.3 Product and market applicability.................................................... 8-12
8.4 Overall network support .............................................................. 8-13
8.5 Traffic types ............................................................................ 8-13
8.6 Traffic forwarding methods .......................................................... 8-14
8.7 Layer 2/layer 3 addressing topologies .............................................. 8-42
8.8 Protocol stacks ......................................................................... 8-76
8.9 Management interface ................................................................ 8-85
8.10 Permanent data storage .............................................................. 8-86
8.11 Management model .................................................................... 8-88
8.12 CDE profile management ............................................................. 8-96
8.13 Service profile management ......................................................... 8-97
8.14 Basic call handling ..................................................................... 8-98
8.15 Supplementary services ............................................................. 8-102
8.16 Registration procedure .............................................................. 8-111
8.17 Counters and Statistics .............................................................. 8-111
8.18 Reliability, Equipment / Connectivity / Overload Protection................. 8-120
8.19 Quality of Service .................................................................... 8-133
8.20 DNS interworking ..................................................................... 8-133
8.21 BITS Support .......................................................................... 8-135
8.22 Narrowband Line Testing ........................................................... 8-135
8.23 Termination local loop unbundling ................................................ 8-135
8.24 Alarm Treatment ..................................................................... 8-135
8.25 Lawful Intercept...................................................................... 8-137
8.26 Compliancy to standards ............................................................ 8-143
8.27 ISAM Voice migration ................................................................ 8-144
9— Layer 2 forwarding 9-1

9.1 Introduction .............................................................................. 9-2
9.2 The concept of Virtual LAN (VLAN)................................................... 9-2
9.3 ISAM Internal Architecture............................................................. 9-7
9.4 Support for Jumbo frames ............................................................ 9-13
9.5 Subscriber access interface on the LT board ...................................... 9-13
9.6 iBridge mode............................................................................ 9-16
9.7 VLAN cross-connect mode ............................................................ 9-32
9.8 Protocol-aware cross-connect mode ................................................ 9-43
9.9 IPoA cross-connect mode ............................................................. 9-47
9.10 Secure forwarding in iBridge and VLAN cross-connect ........................... 9-49
9.11 Virtual MAC.............................................................................. 9-54
9.12 PPP Cross-connect mode .............................................................. 9-59
Alcatel-Lucent 7302 ISAM | 7330 ISAM FTTN | 7356 ISAM FTTB R4.4.02 July 2012 ix
Contents
10 — Protocol handling in a Layer 2 forwarding model 10-1

10.1 Introduction ............................................................................. 10-2
10.2 Link aggregation........................................................................ 10-3
10.3 RSTP and MSTP ......................................................................... 10-5
10.4 Connectivity Fault Management ..................................................... 10-7
10.5 802.1x support........................................................................ 10-10
10.6 BCMP ................................................................................... 10-11
10.7 ARP ..................................................................................... 10-12
10.8 DHCP ................................................................................... 10-13
10.9 IGMP.................................................................................... 10-18
10.10 PPPoE .................................................................................. 10-18
10.11 DHCPv6 ................................................................................ 10-23
10.12 ICMPv6 ................................................................................. 10-24
11 — IP routing 11-1
11.1 Introduction ............................................................................. 11-2
11.2 IP routing features ..................................................................... 11-2
11.3 IP routing model........................................................................ 11-6
11.4 Routing in case of subtended ISAMs ................................................. 11-7
12 — Protocol handling in a Layer 3 forwarding model 12-1

12.1 Introduction ............................................................................. 12-2
12.2 IPv4 Routing Protocols................................................................. 12-2
12.3 ARP ....................................................................................... 12-3
12.4 DHCP relay agent....................................................................... 12-4
12.5 DHCP snooping.......................................................................... 12-7
13 — Multicast and IGMP 13-1

13.1 Overview ................................................................................ 13-2
13.2 Advanced capabilities ................................................................. 13-5
13.3 System decomposition............................................................... 13-14
13.4 Multicast and forwarding models .................................................. 13-14
14 — Quality of Service 14-1

14.1 Introduction ............................................................................. 14-2
14.2 Upstream QoS handling ............................................................... 14-2
14.3 Downstream QoS ....................................................................... 14-9
14.4 Hardware mapping of QoS functions .............................................. 14-11
14.5 Configuration of QoS................................................................. 14-17
15 — Resource Management and Authentication 15-1

15.1 Introduction ............................................................................. 15-2
15.2 RADIUS features ........................................................................ 15-2
15.3 802.1x authentication via RADIUS ................................................... 15-2
15.4 Operator authentication via RADIUS ................................................ 15-2
15.5 Encryption of authentication data .................................................. 15-3
15.6 Lawful interception .................................................................... 15-3
x July 2012 Alcatel-Lucent 7302 ISAM | 7330 ISAM FTTN | 7356 ISAM FTTB R4.4.02
Contents
16 — ATM Pseudowire emulation 16-1

16.1 Introduction ............................................................................. 16-2
16.2 Solution description ................................................................... 16-2
16.3 Cell concatenation ..................................................................... 16-3
16.4 QoS ....................................................................................... 16-4
16.5 Known restrictions ..................................................................... 16-4
16.6 Support on the ISAM ................................................................... 16-4
A. Cross-domain solutions A-1

A.1 Overview ................................................................................. A-2
A.2 Mobile backhaul ......................................................................... A-4
A.3 E1/T1 Leased Line Replacement ....................................................A-11
A.4 E1/PRA Interfaces on ISAM ...........................................................A-15
A.5 Ethernet Business Access over ISAM .................................................A-21
A.6 ISAM Backhaul (Rural DSL, Ultra-high Broadband) ................................A-26
A.7 Hospitality solution ....................................................................A-32
A.8 Open Community Broadband for Smart Communities ............................A-38
B. RADIUS Attributes B-1

B.1 RADIUS Attributes ....................................................................... B-2
B.2 Vendor specific RADIUS attributes.................................................... B-2
Glossary
Index
Alcatel-Lucent 7302 ISAM | 7330 ISAM FTTN | 7356 ISAM FTTB R4.4.02 July 2012 xi
Contents
xii July 2012 Alcatel-Lucent 7302 ISAM | 7330 ISAM FTTN | 7356 ISAM FTTB R4.4.02
1— Introduction
1.1 General 1-2
1.2 Supported User Interfaces 1-2
1.3 Document Structure 1-3
Alcatel-Lucent 7302 ISAM | 7330 ISAM FTTN | 7356 ISAM FTTB R4.4.02 July 2012 1-1
1 — Introduction
1.1 General
This document provides the system description for the following products:
• 7302 Intelligent Services Access Manager (ISAM)
• 7330 ISAM Fiber To The Node (FTTN)
• 7356 and 7357 ISAM Fiber To The Building (FTTB)
For specific product details on each of these systems, see the:
• 7302 ISAM Product Information
• 7330 ISAM FTTN Product Information
• 7356 ISAM FTTB User, Safety and Installation Manual
• 7357 ISAM FTTB User, Safety and Installation Manual
The ISAM is a frame-based Multi Service Access Platform, offering high-density

copper and fibre connections for multimedia, high-speed internet access, voice and
business services.
The position of the ISAM in the network is visualized in Figure 1-1, showing on the
left side the different types of user interfaces that terminate on the Line Termination
(LT) boards in the system.
The ISAM can be deployed with numerous interfaces and in different network
environments.
1.2 Supported User Interfaces
Depending on the Network Termination (NT) used in the system, the list of
supported user interfaces will be different.
The ISAM network architecture for systems equipped with an FD 24 Gbps NT is
shown in Figure 1-1.
1-2 July 2012 Alcatel-Lucent 7302 ISAM | 7330 ISAM FTTN | 7356 ISAM FTTB R4.4.02
1 — Introduction
Figure 1-1 ISAM Network Architecture

IP Edge Router
/ BRAS
Ethernet
Switch NSP IP backbone
ISAM
xDSL
FE/GE
Ethernet
Voice
EMAN NSP IP backbone
FE/GE
NSP IP backbone
xDSL xDSL
LT
Ethernet FE/GE
Eth
LT
Voice NT
Voice
LT
FE/GE
Depending on the type of LTs plugged into the system, three types of user interfaces
are available:
• a number of different DSL interfaces (depending on the related DSL line board
family),
• Ethernet interfaces
• voice interfaces
The three types of user interfaces can be implemented simultaneously in one system.
More detailed information on each of these interface types is available in chapter
“System interface overview”.
1.3 Document Structure
Following a general chapter about all of the system interfaces, this document is
organized in a number of functional areas providing an end-to-end view of the
different ISAM feature domains.
1 — Introduction
2— System interface overview
2.1 General 2-2
2.2 Overview 2-2
2.3 Multi-ADSL 2-4
2.4 VDSL 2-7
2.5 SHDSL 2-10
2.6 Ethernet 2-11
2.7 Inverse multiplexing for ATM 2-13
2.8 ATM/PTM bonding 2-13
2.9 Overview of ISAM Voice interfaces 2-14
2.10 E1 TDM Interface 2-15
2.11 Overview of ISAM support for remote management of

third-party equipment. 2-15
2 — System interface overview
2.1 General
This chapter provides a general description of the system interfaces.

The ISAM can be deployed with numerous interfaces and in different network
environments. In a basic deployment, the ISAM is used for providing High-Speed
Internet (HSI), Video, and Voice over IP (VoIP) services to subscribers.
A specific use of the ISAM is to provide classic telephony services to subscribers
being connected with classic Plain Old Telephone Service (POTS) or Integrated
Services Digital Network (ISDN) lines, and to convert within the ISAM the
corresponding signals to VoIP signaling and data packets. This specific use of the
ISAM is known as ISAM Voice.
2.2 Overview
The following section provides an overview of the different relevant aspects for
subscriber links.
Note — For ease of understanding, the ISAM Voice links are

described separately, see section “Overview of ISAM Voice
interfaces”.
Link transmission technology

In general, the subscriber links are terminated on the Line Termination (LT) boards.
The ISAM supports LT boards with various transmission types:
• ADSL, ADSL2, ADSL2+, and READSL2 (ITU-T G.992)
• VDSL2 (ITU-T G.993)
• SHDSL (ITU-T 991.2, YD/T1185-2002, IEEE 802.3)
• Ethernet (IEEE 802.3)
The Ethernet subscriber links can also be terminated on the Network Termination
(NT) boards or the NT I/O boards.
The network links (ISAM uplinks), subtending links (to the subtended ISAM) or
inter-shelf links (ISAM downlinks from the host shelf to remote shelves, Remote
Expansion Modules (7356 ISAM FTTB REMs) or Sealed Expansion Modules (7357
ISAM FTTB SEMs) are terminated by the Network Termination (NT) boards, by the
NT I/O boards, or by an Ethernet LT board operating in
Network-to-Network-Interfacing (NNI) modus.
Figure 2-1 shows a diagram of approximate achievable downstream bit rates for the
DSL transmission types mentioned above as a function of the line length for a 0.4
mm diameter (26 AWG) twisted pair.
Figure 2-1 DSL types: downstream bit rate as a function of line length
100
90
80
VDSL2
70
Do wn s tre a m b it ra te (Mb /s)

60
50
40 VDSL
30
ADSL2+
20
ADSL2
10
ADSL
0
0 1 2 3 4 5 6 7
Lin e le n g th (km)
Transfer modes
The ISAM supports the following transfer modes for the preceding transmission
types:
• Asynchronous Transfer Mode (ATM) is supported for all ADSL types and
SHDSL.
• Packet Transfer Mode (PTM) with 64/65 octet encapsulation/Ethernet in the First
Mile (EFM) is supported for SHDSL, VDSL2, and some ADSL2/2+ LT boards.
This transfer mode uses 64/65 byte block coding of variable size frames or frame
fragments at the transmission convergence sublayer in the modem.
For PTM over ADSL2/2+, preemption is supported in the upstream direction and
enabled by default (not configurable).
• IEEE 802.3 Ethernet frame transfer
Bonding
A number of methods exist to combine multiple physical links that apply the
preceding transmission types and transfer modes to a single logical subscriber
interface. This allows increasing either:
• the available service bandwidth for a subscriber
• the distance across which a standard service bandwidth package can be offered,
in case of transmission types for which the achievable link bandwidth depends
strongly on the length of the local loop
• a combination of the preceding two methods.
Bonding of multiple links is possible at different levels in the ISAM, where the traffic
of DSL links is aggregated. The broader the scope of the bonding capability, the
more flexibility an operator has to configure bonding groups.
The following bonding methods are defined within the standards:

• Inverse Multiplexing for ATM (IMA): ATM Forum Specification
af-phy-0086.001
• ATM Bonding: ITU-T G.998.1
• PTM Bonding: ITU-T G.998.2
• M-pair operation for SHDSL: ITU-T G.991.2
2.3 Multi-ADSL
The ISAM supports multi-ADSL subscriber lines. This section describes the
different supported ADSL types.
ADSL1
Asymmetric Digital Subscriber Line (ADSL) is used on existing metallic twisted
pairs (one per subscriber) between the Customer Premises Equipment (CPE) and a
Central Office (CO) exchange.
A Frequency Division Multiplexing (FDM) technique allows the simultaneous use
of high-speed data services and the existing Plain Old Telephone Service (POTS) or
Integrated Services Digital Network (ISDN).
Other advantages of ADSL are:
• The existing network is used by the network operator (reducing costs).
• The existing telephone service, including equipment, is retained by the customer.
Asymmetric nature of ADSL

The digital transmission capacity of the ADSL system is asymmetric in that the
downstream and upstream bit rates are different:
• The downstream bit rate can range from 32 kb/s up to 8 Mb/s (or 15 Mb/s with
the optional S=0.5). The bit rate granularity is 32 kb/s.
• The upstream bit rate can range from 32 kb/s to 1.5 Mb/s. The bit rate granularity
is 32 kb/s.
Note — In practice, the maximum achievable upstream bit rate is
typically below 1.5 Mb/s. For example, the maximum achievable
upstream bit rate for Annex A is 1.2 Mb/s.
The chosen rate depends on the bidirectional services to be supported and the loop
characteristics.
This transmission type allows high-bandwidth services, for example, digital audio
and video (multimedia), Ethernet interconnection to the customer, and so on.
Bidirectional transport
With ADSL, the transport system provides bidirectional asymmetric communication
over a single twisted pair without repeaters.
ADSL services
The multi-ADSL mode and maximum physical bit rate is automatically determined
during initialization of the modem, based on line conditions and the line
configuration. Modem initialization is done using a predefined noise margin and
within the constraints of the transmit power spectral density. This allows various
levels of service, for example, offering the highest bit rates at a premium or ensuring
a guaranteed bit rate.
Operational modes
Table 2-1 lists the supported ADSL1 operational modes.
Table 2-1 ADSL operational modes
Operation Mode Description
T1.413 Issue 2 ANSI standard; operation over POTS non-overlapped spectrum
DTS/TM-06006 ETSI standard; operation over ISDN non-overlapped spectrum
G.992.1 Annex A Also known as G.dmt; operation over POTS non-overlapped spectrum
G.992.1 Annex B Operation over ISDN non-overlapped spectrum
G.992.2 Annex A Also known as G.lite; operation over POTS non-overlapped spectrum.
This standard is a medium bandwidth version of ADSL that allows Internet
access at up to 1.5 Mb/s downstream and up to 512 kb/s upstream.
ADSL2
The ADSL2 family of ADSL standards adds features and functionality that boost the
performance, improve interoperability, and support new applications, services, and
deployment scenarios.
ADSL2 includes the following:
• Better rate and reach:
Improved modulation efficiency, improved initialization state machine, enhanced
signal processing algorithms, reduced framing overhead, and framing extension
allowing higher coding gain.
• Loop diagnostics:
Real-time performance-monitoring capabilities provide information regarding
line quality and noise conditions at both ends of the line (see chapter “Line testing
features”, section “Single-Ended Line Testing”). In addition, ADSL2 provides
Carrier Loop diagnostics based on Dual-Ended Line Testing (DELT) (see
chapter “Line testing features”, section “Dual-ended line testing”).
• Packet-based services:
ADSL2 amendment 1 brings native transport of packets such as Ethernet
• Impulse Noise Protection (INP):
See chapter “xDSL features”, section “Configurable impulse noise protection”.
• Physical Layer Retransmission (RTX):
See chapter “xDSL features”, section “Physical Layer Retransmission (RTX)”.
• Bonding:
ADSL2 also specifies IMA. However, this has been replaced by bonding support
as per G.998.1; see section “ATM/PTM bonding”.
• Low-power modes (L2/L3):
See chapter “xDSL features”, section “Low-power modes”.
• Seamless Rate Adaptation (SRA):
See chapter “xDSL features”, section “Seamless rate adaptation”.
• Carrier masking:
The carrier mask allows the suppression of each individual carrier in the upstream
and downstream direction.
• Mandatory receiver support of bit swapping:
Bit swapping reallocates data and power (that is, margin) among the allocated
subcarriers without modification of the higher layer features of the physical layer.
After a bit swapping reconfiguration, the total data rate is unchanged and the data
rate on each latency path is unchanged.
• Radio Frequency Interference (RFI) egress control and means for RFI ingress
control:
To minimize the impact of radio frequency interference from and with AM radio
and radio amateurs, multi-ADSL provides RFI egress control and means for RFI
ingress control.
Operational modes
Table 2-2 lists the supported ADSL2 operational modes.
Table 2-2 ADSL2 operational modes
G.992.3 Annex A Operation over POTS non-overlapped spectrum

G.992.3 Annex M Extended upstream operation (up to 3 Mb/s) over POTS non-overlapped
spectrum
G.992.3 Annex J All Digital Mode operation with non-overlapped spectrum and extended
upstream band (spectrally compatible with ADSLx over ISDN)
A license counter keeps track of all the installed lines on which G.992.3 or G.992.5
Annex M is enabled.
Annex J is enabled.
ADSL2+
A number of applications, such as some video streams or combinations of video and
data streams, can benefit from higher downstream rates than are currently possible
with ADSL2. By doubling the ADSL frequency range up to 2.2 MHz, downstream
bit rates of up to about 25 Mb/s can be provided.
Operational modes
Table 2-3 lists the supported ADSL2+ operational modes.
Table 2-3 ADSL2+ operational modes
G.992.5 Annex A Operation over POTS non-overlapped spectrum
G.992.5 Annex M Extended upstream operation (up to 3 Mb/s) over POTS non-overlapped
spectrum
G.992.5 Annex J All Digital Mode operation with non-overlapped spectrum and extended
upstream band (spectrally compatible with ADSLx over ISDN)
Annex M is enabled.
Annex J is enabled.
Reach Extended ADSL2

Reach Extended ADSL2 (READSL2) is specified by ADSL2 Annex L, proposing
new Power Spectral Density (PSD) masks that can result in a significant increase in
ADSL reach.
Operational modes
Table 2-4 lists the READSL2 operational modes.
Table 2-4 READSL2 operational modes
G.992.3 Annex L (WIDE) Operation over POTS non-overlapped spectrum, Range-Extended

Mode 1
G.992.3 Annex L (NARROW) Operation over POTS non-overlapped spectrum, Range-Extended
Mode 2
2.4 VDSL
Very high bit rate Digital Subscriber Line (VDSL) allows very high speed data
transmission on a metallic twisted pair between the operator network and the
customer premises. This service is provisioned by using the existing unshielded
copper twisted pairs, without requiring repeaters. By using a Frequency Division
Multiplexing (FDM) technique, the existing POTS or ISDN services can still be
provided on the same wires. VDSL transceivers use Frequency Division Duplexing
(FDD) to separate upstream and downstream transmission.
VDSL1
VDSL1 mode is not supported.
VDSL2
The VDSL2 standard (G.993.2) is an enhancement to VDSL1. VDSL2 specifies
Discrete Multi-Tone (DMT) modulation and is reusing concepts of G.993.1
(VDSL1) and G.992.3 (ADSL2) recommendations, using also the G.994.1
handshake procedure.
VDSL2 features
The main features of VDSL2 are:
• VDSL2 offers Packet Transport Mode (PTM) with 64/65B encapsulation:
• The definition of profiles supports a wide range of deployment scenarios:
• deployment from the exchange (Fiber To The Exchange (FTTEx))
• deployment from the cabinet (Fiber To The Cabinet (FTTCab))
• deployment from the building (Fiber To the Building (FTTB))
• VDSL2 supports higher bit rates than VDSL1; up to 100 Mb/s symmetrical.
The attainable maximum data rate depends on the VDSL2 profile used. Support
of 100 Mb/s requires the 30 MHz profile. Other profiles are better suited for
operation on longer loops, but with reduced maximum bit rate.
• VDSL2 offers improved performance over VDSL1:
• addition of Trellis coding
• increased maximum allowable transmit power
• VDSL2 features provide better support for triple play over VDSL
• improved Impulse Noise Protection (INP)
• physical layer retransmission (RTX)
• virtual noise (optional)
• VDSL2 has some ADSL2-like features:
• similar: loop diagnostics
• improved: PSD shaping
• improved management with regard to VDSL1
VDSL2 Operational Modes
Table 2-5 lists the supported VDSL2 operational modes.
Table 2-5 VDSL2 operational modes
G.993.2 profile 8A VDSL2 profile 8A
G.993.2 profile 8B VDSL2 profile 8B
G.993.2 profile 8C VDSL2 profile 8C
G.993.2 profile 8D VDSL2 profile 8D
G.993.2 profile 12B VDSL2 profile 12B

VDSL2 profile parameter overview
VDSL2 profiles mainly define variants with different bandwidths and transmit
powers. Table 2-6 provides a VDSL2 profile parameter overview.
Table 2-6 VDSL2 profile parameter overview
Parameter VDSL2 profile
8A 8B 8C 8D 12A 12B 17A
Max. aggregate DS transmit power (dBm) 17.5 20.5 11.5 14.5 14.5 14.5 14.5
Max. aggregate US transmit power (dBm) 14.5 14.5 14.5 14.5 14.5 14.5 14.5
US0 support(2) M M M M M O O
Annex A DS upper frequency (MHz) 8.5 8.5 8.5 8.5 8.5 8.5 17.664
(998)
US upper frequency (MHz) 5.2 5.2 5.2 5.2 12 12 12
Annex B DS upper frequency (MHz) 7.05 7.05 7.05 7.05 7.05 7.05 N/A
(997)
US upper frequency (MHz) 8.83 8.83 5.1 8.83 12 12 N/A
Annex B DS upper frequency (MHz) 7.05 7.05 7.05 7.05 7.05 7.05 14
(997E)
US upper frequency (MHz) 8.832 8.832 5.1 8.832 12 12 17.664
Annex B DS upper frequency (MHz) 8.5 8.5 8.5 8.5 8.5 8.5 17.664
(998E)
Annex B DS upper frequency (MHz) 8.5 8.5 8.5 8.5 8.5 8.5 17.664
(998ADE)
Notes
(1) US=upstream; DS=downstream
(2) M=Mandatory; O=Optional; N=Not supported
2.5 SHDSL
The Symmetric High-speed Digital Subscriber Line (SHDSL) technology is a

physical layer standard based on the ITU-T Recommendation G.991.2 (G.shdsl). The
recommendation describes a versatile transmission method for data transport in the
telecommunication access networks. SHDSL supports ATM, PTM, and EFM
transport.
SHDSL transceivers are designed primarily for duplex operation over mixed gauges
of two-wire twisted metallic pairs. Four-wire and M-pair operations can be used for
extended reach or bit rate. M-pair operation is supported for up to 4 pairs.
The use of signal regenerators for both the two-wire and multi-wire operations is
optional.
Multiple SHDSL circuits may be combined to support higher bandwidth using
Inverse Multiplexing for ATM (IMA) interface or the payload can be shared by
multiple circuits (using the M-pair mode). IMA and M-pair do not work
simultaneously over the same port or circuit. Generally, an SHDSL LT in the system
can support ATM or IMA, or ITU-T G.991.2 PTM, or IEEE 802.3ah EFM on a
per-port basis.
SHDSL transceivers are capable of supporting selected symmetric user data rates
ranging from 192 kb/s to 2312 kb/s, and optional up to 5696 kb/s, using Trellis Coded
Pulse Amplitude Modulation (TCPAM) line code. For spectral compatibility with
legacy services (including ADSLx), reach limitations can be imposed (typically by
the national regulator) in function of the SHDSL bit rate.
SHDSL transceivers support Cross-Talk Cancellation (CTC).
SHDSL transceivers do not support the use of analogue splitting technology for
coexistence with either POTS or ISDN.
Regional settings
Table 2-7 lists the supported regional settings.
Table 2-7 SHDSL regional settings
Standards Description
G.991.2 Annex A/F Standards applicable for North America (region 1) (ANSI)
G.991.2 Annex B/G Standards applicable for Europe (region 2) (ETSI)
Payload rates
The following payload rates are supported:
• 192 to 2304 kb/s in 64 kb/s steps for Annex A/B
• 192 to 5696 kb/s in 64 kb/s steps for Annex F/G
2.6 Ethernet
The ISAM supports the following Ethernet interfaces:

• Fast Ethernet (FE): supported on NT, NT I/O, and LT boards.
• Gigabit Ethernet (GE): supported on NT, NT I/O and LT boards.
Note 1 — The 7330 ISAM FTTN supports additional optical uplinks

through the expander unit, as well as optical expansion links
(downlinks).
Note 2 — For Ethernet features supported by the Ethernet Line
Termination (LT) board, refer to the Unit Data Sheet (UDS) of the
relevant board.
Ethernet offers the following advantages:

• high network reliability
• general availability of management and troubleshooting tools
• scalable to fit future needs
• low cost both in purchase and support
• easy migration from Ethernet or FE to GE
• flexible network design
Half and full duplex mode

Ethernet can operate in two modes:
• Half duplex: In half duplex mode, a station can only send or receive at one time.
• Full duplex: In full duplex mode, send and receive channels are separated on the
link so that a station can send and receive simultaneously.
The ISAM NTs supports both modes and can adapt to either mode by way of
auto-negotiation or manual configuration.
The ISAM Ethernet LTs only support the full duplex mode.
Hardware auto-negotiation
Hardware auto-negotiation provides the capability for a device at one end of the link
segment to:
• advertise its abilities to the device at the other end (its link partner)
• detect information defining the abilities of the link partner
• determine if the two devices are compatible.
Auto-negotiation provides hands-free configuration of the two attached devices.
Using auto-negotiation, the ISAM can determine the operational mode (full or half
duplex) and speed (only for electrical interfaces) to be applied to the link.
Note 1 — It is also possible to manually configure the transmission

mode and speed on the link.
Note 2 — Auto-negotiation is supported for both optical and electrical
GE.
ISAM NTs support auto-negotiation while the Ethernet LTs do not support it.
Fiber speed auto-sensing

Dual speed optical SFPs support both 100 Mb/s and 1 Gb/s modes of operations.
When using dual speed SFPs, it is sometimes operationally easier to leave the ISAM
automatically select the link speed in function of the CPE capabilities.
Though speed selection by means of auto-negotiation is standardized for electrical
interfaces, it is not the case for optical interfaces. In order to overcome this situation,
the ISAM supports a proprietary extension allowing the operator to enable the
so-called "fiber speed auto-sensing". Once enabled, the ISAM will automatically
detect the operating speed of the CPE and adapts its own line rate.
Note 1 — Whenever supported by the CPE (only standardized for
Gigabit Ethernet optical lines), the fiber speed auto-sensing process
will use auto-negotiation, allowing for faster convergence (1 Gb/s line
only).
Note 2 — When 100 Mb/s and 1 Gb/s rates are both supported by the
ISAM and the CPE, the highest available rate (that is, 1 Gb/s) is
always selected.
See the ISAM Product Information manual for supported dual speed optical SFP
modules per board type.
Software auto-negotiation
Software auto-negotiation institutes a propriety protocol to negotiate a higher
communication bandwidth between two auto-negotiation-capable boards (NT board
on one side and LT board on the other side). These two boards do not necessarily
have to reside in the same shelf.
The operator can configure the highest possible bandwidth between two capable
boards via the regular management channels. The software auto-negotiation protocol
will, based on the configured values, bring the bandwidth between two
auto-negotiation-capable boards to the configured maximum speed.
2.7 Inverse multiplexing for ATM
Inverse Multiplexing for ATM (IMA) is specified by ATM Forum Specification

af-phy-0086.001.
IMA allows an ATM cell stream to be transported on a number of lower-rate physical
links. This is done by grouping these physical links into a single logical transport
channel. The bandwidth of this logical channel is approximately equal to the sum of
the transmission rates of the individual links in the IMA group.
Figure 2-2 IMA
IMA Group IMA Group

Physical link #0
PHY PHY
Physical link #1
PHY PHY
Single ATM Cell stream Original ATM Cell
from ATM layer stream to ATM layer
Physical link #2
PHY PHY
IMA Virtual Link
IMA requires that all bonded links operate at the same nominal rate. The original
cells are not modified, and control (ICP) cells are inserted for OAM communication
between the two ends.
• In the Tx direction, the ATM cells are distributed across the links in a round robin
sequence.
• In the Rx direction, the ATM cells are recombined into a single ATM stream.
The IMA type of bonding is supported on SHDSL LT boards.
2.8 ATM/PTM bonding
ATM bonding
ATM bonding is specified by ITU-T G.998.1.
ATM bonding is applied to combine ATM-based transmission links with limited or
reach-dependent bandwidth, which do not exhibit an identical transmission speed,
specifically all types of ADSL. This technique does add sequence information to
ATM cells, and thus allows resequencing, that is, delay variation due to speed
variation across multiple physical links in one bonding group.
Up to 2 transmission links can be combined in one bonding group with ADSL ATM
bonding.
PTM bonding
PTM bonding is specified by ITU-T G.998.2.
PTM bonding applies to DSL links with or without identical transmission speed,
because PTM implies the use of variable size PDUs, which make the use of IMA
techniques impossible. PTM bonding is applied to combine EFM-based transmission
links with limited or reach- dependent bandwidth, specifically VDSL2, SHDSL, and
ADSL2(+). This technique adds sequence information to transmitted frames or
frame fragments, and thus allows resequencing, that is, delay variation due to speed
variations or to PDU size variations, or both, across multiple physical links in one
bonding group. Up to 8 transmission links can be combined in one bonding group
with VDSL2 or ADSL2(+) PTM bonding.
2.9 Overview of ISAM Voice interfaces
This section provides an overview of the different links of the ISAM Voice.
ISAM Voice supports LT boards with various types of Narrow Band (NB) subscriber
links:
• Plain Old Telephone Service (POTS) link
• Integrated Services Digital Network (ISDN) Basic Access (BA) link
ISAM Voice is connected to the network through Ethernet links as documented for
the ISAM. See section “Ethernet”.
POTS
The POTS interface is the Z interface, that is, an analog subscriber line for
connecting, for example, a POTS line. However, also other equipment such as faxes
can be connected. The principles of this interface are as standardized in ITU-T Q.551
and Q.552.
The Z interface carries signals such as speech, voice band analog data,
multi-frequency push button signals, and so on. In addition, the Z interface must
provide for DC feeding of the subscriber set and ordinary functions such as DC
signaling, ringing, metering, and so on, where appropriate.
The characteristics of this interface are as standardized in ITU-T Q.551 and Q.552.
It is recognized that the characteristics of analog interfaces vary considerably from
country to country and therefore the characteristics other than those defined in
Recommendations Q.551 and Q.552 are not subject to ITU-T Recommendations.
Within the ISAM, these are typically handled with the concept of a CDE profile.
ISDN BA
The ISDN BA interface corresponds to the U reference point of the Digital
Transmission System.
The interface provides full-duplex and bit-independent transmission via two wires at
a net bit rate of 144 kb/s. The net bit rate of 144 kb/s offers 1 D-channel of 16 kb/s
and 2 B-channels of 64 kb/s.
The ISDN BA layer 1 specification is given in ITU-T I.430. Both 2B1Q and 4B3T
encoding are applied through the use of different HW variants.
The D-channel signaling procedures are defined in the Q.920 and Q.930-Series, for
the basis particularly in Q.921 and Q.931.
2.10 E1 TDM Interface
The ISAM supports E1 interfaces by means of a dedicated E1 TDM pseudo-wire

SFP. The E1-TDM SFP can be inserted in a standard GE SFP cage of the ISAM's
NT, NT I/O or LT board. Per need basis any Gigabit Ethernet SFP port can be
converted into a TDM port and back. See the Product Information document for your
system for supported SFP modules per board type.
By performing Circuit Emulation Services (CES) encapsulating, the E1 TDM traffic
is transported in Ethernet Layer2 packets across the ISAM and Ethernet based
network. Allowing interoperability with other CES interworking devices the
E1-TDM SFP is using the Metro Ethernet Forum standard (MEF-8) payload format
and pseudo-wire (PW) technology.
The E1-TDM SFP is a dual-channel SFP allowing terminating up to two E1 TDM
lines, with a data-rate of 2,048 Mbps per E1. The CES interworking function of the
E1-TDM SFP initiates and terminates a dedicated pseudo-wire per E1 tributary.
The E1-TDM SFP supports structure agnositc E1 operation modes only. The
line-interface supports framed-E1 for Loss Of Framing detection and CRC-4 checks.
DS0 grooming or fractional E1 is not supported.
Different line impedances (75Ω, 120Ω) are software selectable. The receiver
sensitivity can be configured depending on the required distances (Long Haul, Short
Haul). The interface type is RJ45.
Using Synchronous Ethernet between the host board and the SFP, a high accurate
clocking reference is provided to meet the wander requirements for TDM traffic.
2.11 Overview of ISAM support for remote management of

third-party equipment.
Purpose
ISAM supports dedicated interfaces for the remote management of co-located
third-party equipment through Ethernet connections.
Examples are power supplies, timing supplies, Automatic Distribution Frames,
environment monitoring and conditioning equipment.
Assumptions made on third-party equipment management traffic

The following assumptions are made about the third-party equipment management
traffic:
• The equipment uses an Ethernet interface with untagged frames for remote
management.
• The third-party equipment can be identified in the network through either:
• a pre-configured IP address, for which a destination MAC address can be retrieved
through use of the ARP protocol.
• a public MAC address.
• The third-party equipment traffic is conveyed in a dedicated VLAN. This VLAN
is configurable by the operator
• The communication protocol used for remote managing of the third-party
equipment allows detection of communication corruption or disruption.
Stand-alone ISAM with NT functions
Physical interface
In this case, the third-party equipment can be connected to a free Ethernet port of the
NT function. This port has to be configured as a “direct user” port. The different
ISAM NT board types either:
• provide a combo electrical 100/1000 Base-T and optical 1 GE interface as “direct
user” port
• support the use of electrical 100/1000 Base-T SFPs in external port SFP cages.
Third-party management traffic handling and security

The applied NT port has to be configured for:
• VLAN-port tagging, with a dedicated third-party equipment management VLAN
value
• VLAN cross-connect.
Remote LT equipment without NT functions

In the case of ISAM REM and SEM equipment, the third-party equipment can be
connected to:
• any REM/SEM equipment by means of a DSL modem with 10/100Base-T
subscriber port connected to one of the REM/SEM ports. VLAN
tagging/stripping and destination MAC address filtering are configured on the
bridge port associated to the REM/SEM DSL line used for this purpose.
• FD-REM equipment by means of a 10/100Base-T electrical interface, provided
on the REM control board NRCD-x.
In this configuration, the average traffic load must not exceed 50 kb/s, or 50
packets/s.
Third-party management traffic handling and security

The FD-REM external equipment management port has to be configured for
VLAN-port tagging, with a dedicated third-party equipment management VLAN
value.
VLAN cross-connect behavior is default and not configurable on this port.
For enhanced security in remote cabinets, it is possible to restrict allowed destination
MAC addresses in upstream Ethernet traffic on this port to a white-list of 20 MAC
address ranges. Each entry of this list consists of:
• an Original manufacturer Unique Identifier (OUI) value, covering the three Most
Significant Bytes (MSB) of the public MAC address
• a start value and an end value of a single consecutive range of MAC addresses for
the above OUI, covering at maximum the full three Least Significant Bytes (LSB)
of the public MAC address.
The ISAM itself does not support detection of malfunctions on the FD-REM external
equipment management port, and will not generate alarms related to usage of this
port
3— Failure protection and redundancy
provisions in ISAM
3.1 Overview 3-2
3.2 ISAM single shelf configurations 3-5
3.3 ISAM subtending system protection 3-12
3.4 Failure protection at layer 3 3-15
3.5 Network path connectivity protection 3-15
3 — Failure protection and redundancy provisions in ISAM
3.1 Overview
When you provide protection for system functions and subsystems by use of
redundancy, you improve the reliability of those parts of the ISAM, and hence the
availability of the whole ISAM.
Redundancy aspects
Redundancy has different aspects, and each aspect has its advantages and
disadvantages which must be taken into account. The following aspects are
described:
• relation between essential and redundant resources
• operational mode of the additional redundant resources
• the scope of the protection - the impact of a failure
• the average duration of an outage - time to repair
• the number of simultaneous failures that have to be coped with
Relation between essential and redundant resources
• Bilateral:
One redundant resource can back up only a single dedicated essential resource
(notation 1:1 or 1+1).
The advantage is that the redundant resource can be fully preconfigured, and that
protection normally takes a minimal time. Also, the configuration data (static,
dynamic, or both) necessary for the redundant resource can be kept on the
redundant resource itself.
The disadvantage is that each essential resource has to be duplicated, which adds
to the cost, the space requirements, and the power consumption.
• Dynamic:
A redundant resource can replace any one resource out of a group of identical
essential resources (notation N:1 or N+1, or N:M or N+M in general).
Because each essential resource does not have to be duplicated, one or a few
additional resources can protect a much larger group of identical essential
resources.
The disadvantage is that this scheme only is applicable when multiple identical
essential resources are present in the ISAM. In many cases, the redundant
resource cannot be fully preconfigured. The redundant resource can only be
configured after the failing resource has been identified, which means the time for
protection has to be increased by the configuration time. Also, an up-to-date copy
of the configuration data (static, dynamic, or both) for the multiple essential
resources has to be kept in a place that is not affected by failure of the related
resource. This requires either additional storage on the redundant resource, or a
more complex data storage mechanism across all the protected resources.
Operational mode of the additional redundant resources
• Standby:
One or more redundant resources are kept inactive or on standby while one or
more essential resources perform all the required processing (notation 1:1,
N:1,N:M in general).
The advantages are that the ISAM architecture is relatively simple, and the
configuration and initialization of the redundant resource(s) starts from a
well-known state at the time of activation of the redundant resource(s) in case of
a protection switchover. The standby state can apply on the data path, the control
path and/or the management path (see “Redundancy provision” for more
information and practical examples).
The disadvantages are that the redundant resource does not contribute to the
operation (performance) of the ISAM for 99.9% or more of the time, while
requiring an additional, up to 100% investment in cost, space and power
consumption. Also, in many cases the redundant resource cannot be monitored or
tested for 100% of the functions that it has to perform, so a certain risk of dormant
faults exists.
• Active and load sharing:
All resources (reflected in the data path, control path and/or management path)
are active or operational, normally in a load-sharing mode, but the number of
resources in the ISAM exceeds the minimum needed to perform all the necessary
processing by one, or more (notation 1+1, N+1, or N+M in general). Some
resources can be implemented in load-sharing mode, while others are
implemented in active/standby mode (see “Redundancy provision” for more
information and practical examples).
If one or more of the active resources fail, the remaining resources take over the
whole processing load. Also, all the resources can be monitored in operational
conditions, and dormant faults cannot occur.
The advantage of this type of redundancy is that the ISAM performance increases
while no faults occur, by virtue of the more-than-necessary active resources.
The disadvantages are that the ISAM usually becomes more complex. A
dispatching or processing load distribution function is necessary, which must be
fair (that is, the load must be shared evenly over all the resources) and must be
able to recognize resource failures in time and to respond to them. Also, this
function must not constitute a (significant) single-point-of-failure in itself.
The scope of the protection - the impact of a failure

Usually, it is not economical to protect functions or sub-systems that affect only a
limited number of subscribers, interfaces or a limited amount of traffic. An often
applied principle is that central resources or aggregation resources (that is, resources
whose availability determines the availability of the whole ISAM) are protected,
while tributary resources are not protected. However, it depends on the specifics of
each individual case whether this principle is economically viable, in either
direction.
The average duration of an outage - time to repair

Redundancy of a resource nearly always should be optional. In many cases the need
for providing redundancy or not for a given resource is determined by the average
time to repair. A resource in a system may be reliable enough (that is, its Mean time
Between Failure (MTBF) is low enough) to operate in a non-protected way. This is
the case, for example, in an attended CO environment, where a stock of spare parts
and skilled staff are available and where short detection and intervention times can
be guaranteed. However, the same resource may require redundancy when deployed
in an unattended outdoor cabinet, in order to meet the same availability as in the CO.
The number of simultaneous failures that have to be coped with

Individual Replaceable Items (RI) in modern, carrier-grade telecommunication
equipment are already highly reliable, and provide an intrinsic availability of 99.99%
or even 99.999%, within the boundaries of the specified environmental operating
conditions. In order to achieve the generally required 99.9999% availability, coping
with a single resource failure (that is, providing at most one redundant resource) is
sufficient in all circumstances. The probability of dual simultaneous failures,
affecting the same type of resource, is low enough, and does not have to be taken into
account for protection.
Redundancy provision
The ISAM basically provides redundancy as an option for essential central or
aggregation functions and resources. These include:
• External link protection for:
• network links
• links with sub-tended ISAMs
• Equipment protection for the ISAM:
• Data path: the Ethernet switch fabric
• Control path: the Network Termination (NT) board processor
• Management path: the NT board processor
The ISAM does not protect all the central functions or resources by default. Essential
functions and resources reside on the NT board, which can be made redundant. In
practice, a number of different configurations with single, redundant NT and single
NT IO board are possible, each supporting a different amount or type of protection.
The ISAM can be configured in active/standby mode by means of an optional
standby NT board. The standby NT board is synchronized with the active NT board.
In order to speed-up the reconfiguration of the data plane after switchover and to
facilitate the rebuilding of the control plane, the dynamic switch configuration (L1
and L2) is also synchronized between the active NT board and the standby NT board.
The management plane is fully restored at the moment the new active NT board is
initialized.
3.2 ISAM single shelf configurations
Single NT
When using a single NT board only in the ISAM shelf, only redundancy for external
(network or subtending) links is available, and hence only external link protection is
possible. None of the central functions and resources are duplicated, except for the
external Ethernet interfaces on the faceplate of the NT board itself. The actual
number of these interfaces may vary with the NT type, but equals at least two. This
implies that one or more external network or subtending links can be configured to
protect other network or subtending links on the same NT board.
It must be clear that this link-only protection model does not protect equipment. If
the NT board fails, connectivity on all the links will be lost. The supported
mechanisms are described below.
External link protection: active/standby NT links

External NT links of the ISAM can be configured in active/standby mode on the
single NT board of the ISAM. In case an active NT link fails, all traffic will be
switched to the designated standby NT link as shown in Figure 3-1.
Figure 3-1 Link protection with active/standby external NT link
LT1 NT
Active
PHY
Standby
µP PHY
LTn
Link failure on the active NT link is detected by either:

• detection of “Loss of Signal” on the NT link
• the (Rapid) Spanning Tree Protocol (RSTP) or Multiple Instances Spanning Tree
Protocol (MSTP). Normally, xSTP will allow only one network link to be active,
while all other network links will be forced to standby, in order to avoid loops in
the Ethernet network.
External link protection: Link aggregation

A set of N (1 ≤N ≤8) physical NT interfaces can be configured in load-sharing mode
(link aggregation) as shown in Figure 3-2. Apart from increasing the capacity of the
resulting ISAM single network interface, this configuration also provides link
protection.
Figure 3-2 Link protection with load-sharing external NT links
LT1 NT
PHY 1
µP PHY 2
LTn
If an external link for a single NT with multiple external links in a load-sharing group
is lost, the traffic is redistributed across the remaining links of the load-sharing
group, by means of the link failure detection capability of the Link Aggregation
Control Protocol (LACP).
Single NT, with NTIO

When extending the preceding configuration with an additional NTIO board in the
ISAM shelf, only the number of external Ethernet interfaces is increased by the
number available on the NTIO board faceplate. This number may vary with the
NTIO board type.
Still none of the central functions and resources are duplicated beyond what is
available on the NT + NTIO board itself. Again, one or more external network or
subtending links can be configured to protect others on the same NT board, by either
(R)STP, MSTP or by LACP.
Figure 3-3 Link protection with load-sharing external NT links
LT1 NT
PHY
µP PHY
NTIO
PHY
PHY
LTn PHY
PHY
PHY
PHY
Dual NT (active/standby), no NTIO

When providing a second NT board in the same ISAM shelf, you can provide
equipment protection for the NT board. The duplication provides redundancy for all
the central functions and resources of the ISAM.
Note — In practice, the redundancy is limited to the central functions
and resources of the ISAM which are located on the NT board. The
central functions and resources located on the NTIO board, for
example, do not benefit of such equipment protection.
The ISAM supports active/standby NT equipment protection. Only one of the two
NT boards (and all its functions and resources) can be active at a time. NT switchover
is not revertive after the repair of a failed NT board. The protection capabilities exist:
Combined external link and NT equipment protection, common link set

Figure 3-4 illustrates the simplest configuration with a redundant NT pair, supporting
an active/standby external link configuration. The active external link is connected
to the active NT, while the standby external link is connected to the standby NT.
The operator can:
• configure a number of external link groups on the NT board
• designate any external link of the NT board to be a member of one of the groups
• configure a threshold for the minimum number of operational external links in
each group.
Figure 3-4 Combined link and NT protection with a shared set of active/standby external
interfaces
LT1 NT
Active
PHY
µP PHY
LTn
LT1 NT
Active
PHY
µP PHY
LTn
NT board protection, that is, switchover of traffic from the active NT to the standby
NT, and a related status change for both NT boards, is triggered by either of the
following two events:
• unavailability of a network interface, which brings the number of operational
network interfaces in any configured group below the configurable minimum.
• failure or removal of the NT board itself, detected by means of a dedicated
protection interface between both NT boards.
This configuration implies that when the active external NT link fails, the only
remedy is to trigger an NT switchover, by proper configuration of the original active
link in a link group of 1, and a minimum threshold of 1.
Also, when the NT itself fails and an NT switchover is triggered, an external link
switchover is imposed.
It must be noted that in all cases the standby NT board will not support traffic on its
external links, and hence will not support xSTP processing while in standby mode.
Combined external link and NT equipment protection, separate link sets

Figure 3-5 shows a configuration with active and standby external links on the same
NT board, in which a failure of the active external NT link does not have to lead to
NT switchover. However, in case of NT board failure, its active external link cannot
be kept operational, and traffic has to be switched to an additional standby link on
the standby NT. This configuration is expensive in the number of required external
standby links.
Figure 3-5 Combined link and NT protection with a separate set of active/standby
network interfaces on each
LT1 NT
Active
PHY
µP PHY
Standby
LTn
LT1 NT
Standby
PHY
µP PHY
Standby
LTn
Combined external link and NT equipment protection, load aggregation link

sets
Figure 3-6 shows a configuration with multiple external links that are grouped in a
load aggregation group on the same NT board. Failure of the active external NT link
does not have to lead to NT switchover, as long as the number of operational external
links in the group does not drop below the configured minimum for the group.
Figure 3-6 Combined link and NT protection with network link and aggregation
LT1 NT
PHY 1
µP PHY 2
LTn
LT1 NT
PHY 1
µP PHY 2
LTn
In case of NT board failure, when this external link group cannot be kept operational,
or in case the number of operational links on the active NT drops below the
configured minimum, all traffic will be switched to a standby link group on the
standby NT.
External link and NT equipment protection using passive optical splitters

Figure 3-7 and Figure 3-8 show redundant NT configurations that apply a passive
optical splitter to interconnect a same external optical link to ports of both the active
and standby NT board. These configurations are only possible for the 7302 ISAM
shelves, and only for optical interfaces (not for electrical interfaces). The presence of
the splitter consumes an extra 3 dB optical power of the optical link transmission
budget. Use of such splitters enables the following:
• NT board equipment protection without external link protection (Figure 3-7
without standby external link)
NT board equipment protection without external link protection is not possible in
the preceding redundant NT configurations. Traffic can only be sent or received
by the active one of the redundant NT pair, as the optical transmitters of the
standby NT are physically disabled, to protect the optical signal sent out by the
active NT on the shared fiber.
• Independent active/standby external link and NT board equipment protection
A single pair of external links in active/standby mode can be used, as shown in
Figure 3-7. It is possible to support external link protection without NT
switchover, and NT board protection without external link switchover, that is,
without making the peer ISAM switch traffic to the standby link.
• Independent load sharing external link group and NT board equipment
protection: see Figure 3-8.
Figure 3-7 Independent active/standby external link and NT protection with optical
splitters
LT1 NT
PHY Active
µP PHY Standby
LTn
LT1 NT
PHY
µP PHY
LTn
Figure 3-8 Independent load sharing external link and NT protection with optical
splitters
LT1 NT
PHY 1
µP PHY 2
LTn
LT1 NT
PHY
µP PHY
LTn
Dual NT, with NTIO

Figure 3-9 shows a redundant NT pair configuration with NTIO. The NTIO enables
independent external link protection and NT board equipment protection, for
external links connected to the NTIO. The NTIO replaces the passive optical
splitter(s) in Figure 3-7 and Figure 3-8 with an active board. The NTIO eliminates
the optical power budget reduction caused by the use of an optical splitter, and
enables independent external link protection and NT board equipment protection, for
electrical external links, if connected to the NTIO.
The external links on the NTIO can be configured in active/standby mode, or in load
aggregation group mode, as already discussed above.
In a redundant NT pair configuration with NTIO, the external links on the faceplate
of each NT, and the external links on the face plate of the common NTIO in practice
cannot be combined as such in a same group, for example for constructing a bigger
load aggregation group.
The reason is that in case of NT switchover, the NTIO external links will be
reconnected automatically to the new active NT, while the same is not possible for
external links plugged directly to the NT faceplate. It is possible to combine both
types of external links in a same load aggregation group when an optical splitter is
used for connecting the external links to the NT faceplate(s), as discussed for
previous configurations.
It should be noted that the NTIO board is not duplicated, and, therefore, not
protected. However, the probability of an NTIO failure that affects all of its external
interfaces is low, so in case of a failure, outage for all of its external links will be
limited to the actual duration of the board replacement.
Figure 3-9 Independent load sharing external link and NT protection with NT
LT1 NT
PHY
µP PHY
NTIO
PHY Active
PHY
PHY 1
LTn
PHY 2
LT1 NT PHY
PHY PHY
µP PHY
LTn
3.3 ISAM subtending system protection
You can cascade multiple single-shelf ISAM systems using standard Ethernet
subtending links. ISAM shelves can be connected together to provide a consolidated
interface to the network.
In principle, all of the above protection techniques and configurations can be applied,
for either network type links and subtending type links, or both. This depends on the
required link capacity for each type, and on the interface capacity of the applied NT
and NTIO board types. (R)STP, MSTP and LACP are supported on ISAM external
interfaces for subtending.
The following topologies show some examples for cascading of ISAM equipment
with protection:
• star topology; see Figure 3-10
• daisy-chain topology; see Figure 3-11
• ring topology: daisy chain with the last node connected to the first; see
Figure 3-12.
Up to three levels of cascading can be supported by the ISAM. It depends on the

operator network requirements what the actual appropriate number can be in
practice.
The last ISAM in the cascaded system can be any DSLAM, such as:
• a 7302 ISAM
• a 7300 ASAM with a FENT or GENT
• a 7325 Remote Unit
• a 7330 ISAM FTTN
Figure 3-10 Example of an ISAM subtending star topology

NT
μP PHY
PHY
Subtending
NTIO LAG links
PHY
PHY
PHY
μP NT PHY
N
PHY
T
PHY PHY
PHY
NT
μP PHY
PHY
NTIO
PHY
PHY
PHY Network
μP NT PHY
N
PHY links
T
PHY PHY
PHY
NT
μP PHY
PHY
NTIO LAG
PHY
PHY
PHY Subtending
μP NT PHY links
N
PHY
T
PHY PHY
PHY
Figure 3-11 Example of an ISAM subtending daisy chain topology

NT
μP PHY
PHY Subtending
NTIO links active
PHY
PHY
PHY
NT
LAG
μP N
PHY
PHY
T
PHY PHY
PHY
NT NT
μP PHY μP PHY
PHY PHY
NTIO LAG NTIO
PHY PHY
PHY PHY
PHY PHY
μP NT PHY μP NT PHY
N
PHY N
PHY
T
PHY PHY T
PHY PHY
PHY PHY
Network
NT
links
μP PHY
PHY
NTIO
PHY
PHY
PHY LAG
μP NT PHY
N
PHY
T
PHY PHY
PHY
Figure 3-12 Example of an ISAM subtending ring topology

NT
μP PHY
PHY Subtending
NTIO links active
PHY
PHY
PHY
μP NT PHY
N
PHY
T
PHY PHY
PHY
NT NT
μP PHY μP PHY
PHY PHY
NTIO NTIO
PHY PHY
PHY PHY
PHY PHY Network
μP NT PHY μP NT PHY links
N
PHY N
PHY
T
PHY PHY T
PHY PHY
PHY PHY
NT
μP PHY
PHY
NTIO
PHY
PHY
PHY
μP NT PHY
N
PHY
T
PHY PHY
PHY
3.4 Failure protection at layer 3
When the ISAM xHub is configured as a router in an layer 3 network, then

connectivity protection can be achieved by enabling one or more of the following
layer 3 features:
• Routing protocols: RIP, OSPF
• ECMP (supported on static routes and OSPF routes)
An example is given below whereby the ISAM is used as a router in a layer 3 network
and connected to more than one edge router on different subnets and physical ports.
Layer 3 packets will be routed over the best route selected by OSPF.
Figure 3-13 Example of layer3-based protection

Subnet 1
LT 1 NT
PHY Edge router 1
µP
PHY Edge router 2
Subnet 2
L3 switching and
OSPF enabled
LT n
3.5 Network path connectivity protection
Network path connectivity protection technique consolidates the path connectivity

between an ISAM and an upstream network device, typically the default gateway.
The feature supports both hub-only ISAMs and Hub with subtending ISAM
topologies connected by means of either a layer 2 or a layer 3 aggregation network,
to a redundant pair of layer 3 edge devices.
The network path connectivity protection applies to ISAM Voice access nodes that
offer the Megaco service and the SIP-based integrated voice service (with the
exception of the internally distributed SIP User Agent topology). It does not apply to
ISAM access nodes offering data services.
A configured path connectivity protection group is composed of a minimum of two
external network links or network Link Aggregation Groups (LAGs). One of these
external network links or LAGs is the “active” link and carries the traffic exchanged
between the ISAM and the layer 3 gateway. The other network link(s) is the
“passive” link.
A periodic path connectivity check may reveal a potential connectivity disruption on
the actual active network link or LAG. Upon the detection of such a connectivity
disruption, the ISAM triggers a switchover from the active network link or LAG to
(one of) the “passive” network link(s) or LAG(s)). Traffic that is exchanged between
the ISAM and the layer 3 gateway is now switched to the new “active” network link
or LAG.
The path connectivity check relies on periodically initiating ICMP “echo request”
packets to the target layer 3 device and listening for the ICMP “echo response”
replies.
The ISAM decides that a connectivity disruption has occurred when either a “layer
1 down” event for the current network link is received or when there has been no
reply to three consecutive ICMP “echo requests”.
In case a path connectivity protection group is composed of LAGs, the ISAM
attempts to recover from a connectivity disruption by relying on the redundancy
provided by the LAG concept, where possible. A switchover to another LAG in the
path connectivity protection group is performed if the internal LAG redundancy
cannot resolve the connectivity disruption.
Figure 3-14, Figure 3-15 and Figure 3-16 show the different types of network path
connectivity protection topologies.
Figure 3-14 Network path connectivity protection - Network topology 1
L3 network L3 network
device device
VRRP
L2/L3 L2/L3
switch switch
active passive
external external
link link
connectivity
protection
ISAM group

VRRP
device device
L2 L2
switch switch
active passive
external external
link link
connectivity
protection
ISAM group

VRRP
device device
L2 L2
switch switch
L2
switch
L2 L2
switch switch
active passive
external external
link link
connectivity
protection
ISAM
group
4— Management
4.1 Overview 4-2
4.2 Management interfaces 4-3
4.3 Management interfaces security 4-13
4.4 Management access models 4-15
4.5 Counters and statistics 4-18
4.6 Alarm management 4-18
4.7 Software and database management 4-26
4.8 Equipment monitoring 4-28
4.9 Access node control protocol 4-30
4 — Management
4.1 Overview
This chapter describes various management related topics of the ISAM. Table 4-1
below lists the information available in this chapter.
Table 4-1 Contents
Contents Section
Management interfaces 4.2
Management interfaces security 4.3
Management access models 4.4
Counters and statistics 4.5
Alarm management 4.6
Software and database management 4.7
Equipment monitoring 4.8
Access node control protocol 4.9
The Alcatel-Lucent-recommended management architecture is shown in Figure 4-1.
Figure 4-1 ISAM management
OSS
SOAP XML TL1 SOAP XML

xFTP
TL1 5529 5529 5529
5529 GW IDM OAD APC
5530 SDC
NA 5520 AMS PBMT
TL1
xFTP xFTP CLI xFTP
SNMP SNMP
Remote
CT
TL1
CLI
CLI SNMP
TL1 xFTP
Local TL1
ISAM
CT CLI
Alcatel-Lucent has an extensive management suite of products available (5520,

5529, 5530 range of Alcatel-Lucent products) to allow an efficient management of
an ISAM network. Southbound, towards the ISAM, it takes care of all ISAM
specifics and related protocols, while northbound it provides standard SOAP/XML
interfaces for an easy and smooth integration with any other OSS applications,
shielding from the DSLAM complexity.
Of course a direct interaction with the ISAM itself, using CLI or TL1, remains
possible, either directly connected to the ISAM or using a remote Craft terminal.
4 — Management
4.2 Management interfaces
The ISAM supports the following management interfaces:

• Simple Network Management Protocol (SNMP)
• Command Line Interface (CLI)
• Transaction Language 1 (TL1)
• File Transfer Protocols: TFTP, SFTP, and FTP
• Simple Network Time Protocol (SNTP)
• Secure Shell (SSH)
• System logging (Syslog)
• Debug port for troubleshooting
These management interfaces are all supported “inband”. This means that the
management interface is supported on top of an Ethernet / IP stack for which the
Ethernet links are the Ethernet network links as mentioned in chapter “System
interface overview”. If one such network link or uplink is dedicated only for
management traffic, outband management can be realized as well.
Only the CLI and TL1 management interfaces can also be realized with a dedicated
RS232 interface.
Note — When a firewall is in place between the network

management stations and the ISAM network, it is required that the
following UDP ports are opened on the firewall (for troubleshooting
and migration reasons):
• UDP port 23 as destination port
• UDP ports 928 – 939 (928 and 939 included) as source and
destination ports
Not opening these ports on the firewall may lead to a reduced or failed
troubleshooting access, or a failure to perform an ISAM migration, or
both.
Figure 4-2 ISAM management interfaces
Individual security control per management channel
RS232
serial interface
CLI TL1 SNMP File transfer
CLI Agent TL1 Agent SNMP SNMP Client Server Client Server Client
v1/v2 v3 TFTP SFTP FTP
SNMP
Telnet SSH Telnet SSH 161/162
server server server server 13001
23 22 1023 1022 69 115 20
UDP
TCP TCP UDP UDP TCP
Secure Secure Secure Secure

Insecure Insecure Insecure Insecure Insecure Insecure
Mutually exclusive
4 — Management
SNMP
The Simple Network Manager Protocol (SNMP) is used by network management
applications like the 5520 AMS, the 5529 Statistics and Data Collector, or the 5530
Network Analyser to manage the ISAM.
Three versions of SNMP exist:
• SNMP version 1 (SNMPv1) uses a community string (that is, a plain-text
password in the SNMP messages) to verify if a request may be executed or not.
This is very insecure.
• SNMP version2 (SNMPv2) has the same syntax and security level as SNMPv1,
but has more commands, more error codes, different traps, and improved
response
• SNMP version 3 (SNMPv3) provides authentication, privacy and administration
for safe configuration and control operation. SNMPv3 also offers
transaction-by-transaction security configuration settings.
Note — SNMPv3 is supported by default. but also SNMPv2 and

SNMPv1 messages can be processed.
SNMPv3
The security mechanisms defined in SNMPv3 protect against threats such as
masquerade, modification of information, message stream modification, and
disclosure.
The SNMPv3 security mechanisms provide:
• data origin authentication
• data integrity checks
• timeliness indicator
• encryption
SNMPv3 allows for three different security levels in that messages between agent
and manager can be:
• unauthenticated and unencrypted
• authenticated but unencrypted
• both authenticated and encrypted
Two security-related capabilities are defined in SNMPv3:
1 User-based Security Model (USM):
The USM provides authentication and privacy (encryption) functions and
operates at the message level. In addition, the USM includes a key management
capability that provides for key localization and key updates. The USM is used
to authenticate entities, and provides encryption services to secure
communication between agents and managers. Each agent keeps track of the
authorized user access via an internal table of user/secrets/access entries. Both
4 — Management
authentication and encryption utilize symmetric keys, which can be generated

from a password. Localization of the authentication, and encryption of keys by
hashing the generated key with the ID of each agent entity is strongly
recommended.
2 View-based Access Control Model (VACM):
The VACM verifies whether a given user is allowed to access a particular MIB
object and perform particular functions (MIB views: read, write or notify
access). The VACM makes an access control decision on the basis of:
• the principal asking for access
• the security model and security level used for communicating the request
• the context to which access is requested
• the type of access requested (read, write, notify)
• the actual object to which access is requested.
TL1
The ISAM supports Transaction Language 1 (TL1) as management interface. This
cross-vendor, cross-technology man-machine language is supported over UDP,
telnet and SSH.
Please check the following documents for the full list and details of all the supported
TL1 commands and events in the ISAM:
• Operations and Maintenance Using TL1 for FD 24Gbps NT
• TL1 Commands and Messages Guide for FD 24Gbps NT
The ISAM supports up to:
• five parallel TL1 sessions, when using TL1 over telnet or SHH
• ten parallel sessions are possible when using UDP
In total, a maximum of ten TL1 parallel sessions are supported. When using TL1
scripts, it is recommended to strictly limit the number of active, parallel TL1 scripts
to two. Anyway the TL1 response should be awaited before launching a new TL1
command to the ISAM.
An alarm is raised whenever a TL1 user logs in (successful or not), indicating the IP
address, account name and timestamp of the login trial. Severity, reporting and so on
of this alarm can be configured as with any other alarm. If the login was not
successful, the corresponding alarm needs to be cleared manually by the operator.
To avoid an overflow of failed login alarms (for example, due to a malicious user),
a new failed login alarm will only be generated either when 3 minutes have passed
since the last failed login alarm or when 90 failed logins occurred, whichever comes
first.
The TL1 login banner is configurable.
Note — The ISAM will refuse any TL1/UDP connection with a

source port < 12 to protect the ISAM against malicious attacks.
4 — Management
CLI
The ISAM supports a Command Line Interface (CLI) as management interface. This
interface is primarily intended as a man-machine interface for the ISAM and is
supported over telnet, SHH, and using the serial interface (Craft).
Please check the following documents for the full list and details of all the supported
CLI commands and events in the ISAM:
• Operations and Maintenance using CLI for FD 24Gbps NT
• CLI Command Guide for FD 24Gbps NT
The ISAM supports up to ten parallel CLI sessions, be it over telnet or over SSH.
There can only be one local Craft session.
An alarm is raised whenever a CLI user logs in (successful or not), indicating the IP
address, account name and timestamp of the login trial. Severity, reporting and so on
of this alarm can be configured as with any other alarm. If the login was not
successful, the corresponding alarm needs to be cleared manually by the operator.
To avoid an overflow of failed login alarms (for example, due to a malicious user),
a new failed login alarm will only be generated either when 3 minutes have passed
since the last failed login alarm or when 90 failed logins occurred, whichever comes
first.
xFTP
File Transfer Protocols

The ISAM supports 3 file transfer protocols: FTP, TFTP and SFTP.
TFTP is the simplest of the 3 file transfer protocols, but lacks reliability and security
capabilities. It runs on top of UDP and does not require any username-password
combination. There is also no encryption of data. The ISAM supports both a TFTP
client and server. In server mode, the ISAM can handle up to 14 TFTP sessions.
FTP also lacks any encryption, but requires a username-password identification
(“anonymous” access is not allowed) and runs on top of TCP/IP. The ISAM only
supports an FTP client.
SFTP has been introduced as part of the SSH implementation. When the ISAM acts
as an SFTP client towards an external SFTP server, the ISAM uses an
operator-configured username & password. The security settings like encryption,
hashing and signature protocols can be configured by the operator via CLI or
SNMPv3. The ISAM supports both an SFTP client and server. In server mode, the
ISAM supports two SFTP sessions simultaneously. Also, in SFTP server mode, the
user authentication coincides with the SSH authentication, that is, the same
username/password or username/key-pair combinations apply. This means that once
the operator has been configured for CLI or TL1 with a username/password or for
SSH with a username/key pair, the same username can be used for setting up an
SFTP session with the ISAM.
4 — Management
External xFTP servers

External (software download, backup/restore…) xFTP servers can be configured in
the ISAM. One and the same external server machine can be used as software
download and backup/restore server, but they can be different machines as well. The
servers might also be used in a redundant mode: if the first server cannot be reached,
automatically the redundant one is tried. Multiple configurations are possible,
depending on the situation and/or requirement of the customer.
Only one account (name, password) can be defined in the ISAM per external server:
• Even in case of multiple applications (software download, backup…) on one and
the same server, only one account can be specified
• The account data is stored in encrypted format
• The account data is not readable from any management interface, not even from
the SNMP manager.
In case of SFTP, only one account can be specified. This account will be used
towards all external xFTP servers.
In case of FTP, up to 8 external servers/accounts can be specified, each with their
own account.
In case of TFTP, no account is required, so also none (0) can be specified.
xFTP Protocol selection

The xFTP protocol to be used for example for software download/backup/restore/…
operations can be configured in the ISAM as a system-wide selection. That is, only
one xFTP protocol can be selected at a time per ISAM. The selected xFTP protocol
will be used for all applications requiring xFTP, independent of the used xFTP server
or application.
Note however that as an FTP server is not supported in the ISAM (see section
below), selecting FTP as protocol still allows to use the TFTP or SFTP server. When
SFTP is selected as protocol though, the TFTP server will be disabled in the ISAM.
Likewise, when selecting TFTP as protocol, the SFTP server will be disabled in the
ISAM.
xNTP
The ISAM system time can be set in two ways:
• The time can be retrieved from an (S)NTP time server by using the Simple
Network Time Protocol (SNTP)
• The time can be set manually by the operator
SNTP Client
Typically, the ISAM system time is retrieved using the Simple Network Time
Protocol (SNTP). The ISAM can cope with both SNTP servers and with NTP
servers, using the SNTP protocol in both cases.
4 — Management
The (S)NTP server can be configured in the ISAM by specifying:

• The IP address of the server
• The port to be used
Up to 3 (S)NTP servers can be configured in the ISAM by specifying:
• The IP address of the server
• The port to be used
• The relative priority among the 3 possible servers
The relative priority defines which server will be polled first to receive the time. An
alarm is raised when even after 3 retries none of the time servers can be reached.
The polling rate can also be specified on a per ISAM level, this is applicable to all
specified (S)NTP servers.
Apart from defining the (S)NTP servers, SNTP must first be set as the system-wide
option for the ISAM. The (S)NTP server always provides the Coordinated Universal
Time (UTC). No time zone or daylight savings settings are passed over the SNTP
protocol.
Manual setting
The ISAM system time can also be set manually by the operator. Note however that
if SNTP is enabled (see above), the set system time will be overwritten at the next
SNTP poll by the UTC time.
Note — As all management time stamping (alarms, syslog messages,

PM, …) is based on the ISAM system time, Alcatel-Lucent highly
recommends to use either SNTP or NTP and discourages any manual
time setting in the operational network.
Time zone offset

Using CLI or TL1 (not possible via SNMP), an operator can also specify a time zone
offset in the ISAM, allowing the operator to mimic “local” time. This time zone
offset:
• Is taken into account once the ISAM system time is set for the first time, either
via SNTP (at the first synchronization with the (S)NTP server), or manually (time
set by the operator)
• As long as the ISAM system time has not been set, the system time will remain fixed
to January 1, 1970
• The ISAM system time (taking into account the time zone offset) is also stored in
prozone and restored after a reset of the ISAM. If the time cannot be restored from
prozone, the ISAM system time is set fixed to January 1, 1970 again, until the time
is set, either manually or by using xNTP.
• Is independent of the fact whether SNTP is enabled or not, that is, it will also be
applied when SNTP is disabled
• Has an allowed range of -780 to +780 minutes, with a default value of 0 minutes
• Is stored persistently
4 — Management
The time zone offset is applied consistently for all applications in the ISAM,
including SNMP, Syslog and so on. The time applied by an application is always the
ISAM system time + the time zone offset (note the default value being 0, even in case
the operator did not specify any time zone offset value, the above statement still is
correct).
Additional notes
• Daylight savings cannot be specified nor are applied automatically in the ISAM.
• ISAM management applications (5520 AMS, 5529 SDC, 5530 NA, …) typically
expect UTC timestamps from the managed nodes: the ISAM management
application machine will typically apply a time zone and daylight savings
correction on the timestamps received from the nodes, before displaying on the
GUI, just like a with a PC. This also implies that if a time zone offset is set in the
ISAM, different from 0, the timestamps on the GUI will be wrong as time
corrections will be applied twice (once in the ISAM with the time zone offset and
again on the management application itself). The ISAM management application
typically will not take into account any time (zone) correction done in the node
itself. Please check on the management applications for this aspect.
• The granularity of the ISAM time information, as provided by the ISAM
applications exposing ISAM time information to external applications (Syslog,
5520 AMS, OSS, …), is seconds and has the following format
“yyyymmdd-hh:mm:ss”.
SSH
Secure Shell (SSH) is a protocol that provides authentication, encryption and data
integrity to secure network communications. On top of this protocol, SSH
implementations offer secure replacements for rsh, rlogin, rcp, ftp, and telnet, all of
which transmit data over the network as clear text. In addition, it offers secure
data-tunneling services for TCP/IP-based applications.
SSH has a client-server architecture. The ISAM acts as the SSH server toward the
manager; see Figure 4-3.
4 — Management
Figure 4-3 SSH and SFTP client-server architecture
SSH Appl. protocol

SSH CLI SSH CLI
client appl server appl
SSH transport
ssh client ssh server
authentication,
connnection
- DB of client
EMS NE - Public keys or
Server authentication
passwords
Secure link for CLI/TL1 SSH
SSH
Server
Client
- NE public key
Client authentication - NE private key
SFTP
Secure link for SFTP InterPeak - Supported algorithms
Server
SFTP
Client
SFTP
- SFTP client
File Client
- Username/password
SFTP
Secure link for Server
Secure link for the transfer
SW&DB from FileServer to NE (SW&DB)
SFTP Appl. protocol

SFTP server SFTP client
application application
SSH transport, authentic,
SSH server SSH client
connection protocol
System logging
System logging (SYSLOG) allows you to trace and audit system behavior related to
operator and /or system activities. System log entries are issued by actions such as
CLI and TL1 user logins, but also by alarms and video CDR records, for example.
With system logging, you can do the following:
• create up to 64 custom system logs that can be saved locally or to a remote server
location
• create filters to determine which messages are sent to the system log files
• monitor system logs
You can configure system logs using CLI, TL1 or an EMS. Locally stored syslog
files can be transferred to an external server using xFTP.
File sets
The system logging works with file sets consisting of two log files. The operator can:
• Trigger the wrap-around from file1 to file2 in order to upload a stable file1.
Note — The ISAM will also automatically copy file1 to file2 when
file1 is full. Both actions (automatic by system / manual by operator)
are performed independently of each other.
• Assign a name to this file set

• Specify the maximum size of the file set
4 — Management
Configuring system logs
You can configure the following 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. 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
• enable or disable logging
• delete a system log file
When a system log file is full, the ISAM will automatically copy the file (file1) to a
backup file (file2) and start overwriting the oldest entries in file1 again.
You can also view system-wide information for system logs. This system-wide
information includes the maximum message size allowed and statistics on the
amount of combined disk space used by the local system logs. The combined
maximum size of all locally saved system log files is 2 Mb.
System log filters
You can configure filters to define which messages get logged to which system log
files, based on the message type; by default, all message types are logged to the
system log files.
Table 4-2 lists the possible message type and log severity parameters. You can:
• select which messages are sent to specific system log files using filters
• group multiple message types.
4 — Management
Table 4-2 Message type and log severity parameters
Item Description Parameter
Message type Authentication actions AUTH
CLI commands CLI_CONFIG
TL1 commands TL1_CONFIG
CLI messages CLI_MSG
TL1 messages TL1_MSG
All message types ALL
Log severity Emergency EM
Alert AL
Critical CR
Error ER
Warning WN
Notice NO
Information IN
Debug DBG
Note — Besides these message types, the alarms and the errors
encountered in the system are also logged in the system log files.
Operator access to the system logs

The operator access to the log file is determined by the allowed priority (access
control). Different users have different access rights to the system log file, that is,
some users only have read priority, while other users with higher priority have read
and write (=delete) priority.
The local log files can be retrieved via xFTP to upload to an external server. In this
case the operator can access the log file only after successful xFTP authentication.
System log files are to be deleted explicitly by operator command.
Viewing and monitoring system logs

The contents of a system log can be viewed either dynamically or statically.
You can monitor remote system logs dynamically on your CLI or TL1 terminal.
Setting the destination server type for the system log file to all active CLI or all active
TL1 terminals sends all messages to the active terminals that have a management
session with the ISAM. When you are finished monitoring the system log, deactivate
system logging for that server.
You can view the static contents of a system log file that is saved or uploaded to a
4 — Management
4.3 Management interfaces security
In order to make the ISAM securely managed, the operator must make sure that:
• A dedicated management access model is applied.
• The secure variants of the used management channels are used.
• A secure operator authentication method is used
• Unused management interfaces are closed.
• The debug port for troubleshooting is closed.
Management interfaces
The following management interfaces can be secured (refer to Figure 4-2):
• Simple Network Management Protocol (SNMP):
Can be secured by way of SNMPv3
• Command Line Interface (CLI):
Can be secured by way of Secure Shell (SSH)
• Transaction Language 1 (TL1):
Can be secured by way of SSH
• Trivial File Transfer Protocol (TFTP) and File Transfer Protocol (FTP):
Can be secured by way of Secured File Transfer Protocol (SFTP)
Apart from xFTP, which is a system-wide, exclusive setting, the system allows both
the secure and the insecure variant of a management interface to coexist, so that the
operator is still able to contact the system in case the security setup would fail.
Simple Network Time Protocol (SNTP) does not have a secure variant. It is
configured to listen to a single SNTP server (for example the Element Management
System). This configuration is done via one of the management interfaces listed
above. Since the operator can secure these interfaces, the SNTP configuration can be
secured.
Encryption and authentication

SSH, SFTP and SNMPv3 support encryption and authentication. Table 4-3 shows
the supported combinations.
Table 4-3 Supported SSH and SNMP Authentication and Encryption Schemes
Security Encryption Authentication Authentication Combinations

protocol algorithm algorithm mechanism
SSH, SFTP 3DES, blowfish, Hmac-sha-1, Username/password(1) • Nothing

AES, DES-56 hmac-sha-1-96 Username/public and • Encryption
private Key only
• Authorization
only
• Encryption
and
authorization
(1 of 2)
4 — Management
Security Encryption Authentication Authentication Combinations

protocol algorithm algorithm mechanism
SNMPv3 DES-56 Hmac-sha-1, Username/password(1) • Authorization

hmac-md5 Note: Different only
password per SNMP • Encryption
engine. and
authorization
(2 of 2)
Note
(1) The username/password combinations of SSH and SNMPv3 cannot be reused.
Security configuration
The configuration of the initial security parameters and user names in the system is
only possible via CLI. Only the operator with security administrator rights has the
authorization to change the security configuration and to add or remove users.
Once the secure channel has been setup, the SNMPv3 parameters can also be
configured by way of the secured SNMPv3. For TL1 and CLI, the security
configuration remains a privilege of the security administrator (concept known in
both TL1 and CLI).
Default username and password

Two command session interfaces (CLI and TL1) are available to the operator to
configure the system. To access these interfaces for the first time, the operator has to
use the default username and password. However, for security purposes, the default
username and password must be changed as soon as possible. For CLI the system
prompts the operator to do this when he or she logs in for the first time.
Trace and Debug interface

The ISAM also supports a Trace&Debug (T&D) interface for troubleshooting
purposes. his interface gives access to low level ISAM functionality and is intended
to be used by trained Alcatel-Lucent personnel only.
Note — Alcatel-Lucent highly recommends to disable this interface

at any time during normal network operations.
Moreover, as an alternative management interface, the ISAM T&D interface is also

vulnerable to security issues. This can be avoided as much as possible by disabling
this interface whenever it is not used.
The T&D interface can be enabled or disabled using the configure system security
ssh access command: please refer to the CLI Command Guide for FD 24Gbps NT for
all details.
4 — Management
4.4 Management access models
Introduction
In most deployment models, the ISAM will use a specific management VLAN for
management. Management access security in this case is guaranteed as follows:
• Any management access to the ISAM via a VLAN which is not the management
VLAN is not possible. Such traffic will be dropped.
• There is a clear separation between management traffic and user traffic.
• Management access is only possible via network ports. The aggregation and core
network should be designed in such a way that non-authorized users cannot get
access to the management VLAN on the network port.
The management access policy will always be a combination of access checks on

different layers:
• Layer 1: specific serial connector (for example, CRAFT cable)
• Layer 2: a dedicated management VLAN.
• Layer 3: specific IP ACLs (checks on traffic received via ingress ports)
• Layer 4 - 7: authentication on protocol level
• Using SSH: user password or private public key
• Using Telnet: user password
• Using UDP: user password
The ISAM can support different management models to secure the access to the
management plane depending on the system configuration:
• Management via a single management IP address and a specific management
VLAN
• Management via the IP loopback address
Management via a single management IP address

A dedicated external management VLAN (4093) is used. The management IP
address and management protocols are only accessible via the external management
VLAN.
4 — Management
Figure 4-4 Management via a single management IP address
Management traffic
User traffic
ACL Management
IP stack
IACM default-route 10.177.127.254
Management IP Address 10.177.0.122/17
Phy
External
management
VLAN
4093
iBridge
VLAN 23
Phy
LAG VLAN 11
Phy
LT
NT
ISAM
Access Control List (ACL)-based filtering on the ingress ports is possible. The
filtering can be on source IP address/mask and destination port number/range. This
allows to protect management against DOS attacks.
Management via the IP loopback address

ISAM management via a loopback interface provides a management interfacing
capability in an IP routing forwarding model. The IP loopback address is used as
management IP address. This mode is required when the ISAM has to be managed
via an IP address reachable through the NT router.
The advantage of such an interface is that the management IP address of the ISAM
is decoupled from the IP subnet configured between the ISAM and the attached IP
edge router.
This allows a network configuration where the aggregation network contains several
IP edge routers all reusing the same IP subnet addresses towards the ISAMs they
aggregate (see Figure 4-5) and minimizes router configuration. The forwarding
tables of the edge routers are updated by a routing protocol such as RIP.
4 — Management
Figure 4-5 Management loopback interface

Intermediate Subnet C ISAM1 FIB (SHub)
allocated per IP edge,
shared over multiple ISAMs ISAM1 0.0.0.0/0 IP_C2;next-hop=IP_C1
Subnet C IP_C2; dir attached
RIP {IP_A1}(*)
VRF IP_A1
AMS FIB RIP {IP_A1,IP_A2}(*) IP_C2
IP_A1/32 IP_B1;next-hop=IP_B2
...
IP IP_C1
Loopback interface
Edge1 ISAM2 with 32 IP addresses
IP_B2
allocated for management
RIP {IP_A2}
AMS IP_B1
IP_C3 VRF IP_A2
IP Edge 1 FIB
EMAN
Subnet B IP_B1; dir attached ISAM3 (*) IP_Cx not advertised
Subnet C IP_C1; dir attached
IP_A1/32 IP_C1;next-hop=IP_C2 RIP {IP_A3}
IP_A2/32 IP_C1;next-hop=IP_C3
VRF IP_A3
... IP_C2
RIP {IP_A3,IP_A4}(*)
IP_B3 IP IP_C1 ISAM4

Edge2
RIP {IP_A4}
IP_C3 VRF IP_A4
host routes installed via RIP
Reusing the same IP subnet on all IP edge routers simplifies their configuration on
the ISAM side. It is required that the IP edge router does not advertise this shared IP
subnet to the network.
In order to save addressing space, the loopback IP address is configured as a /32
subnet mask.
Figure 4-6 Management via the IP loopback address
Management traffic
User traffic
Management
default-route: network interface IP address
IP stack
IACM
Loopback
IP address /32
Phy Internal
Unnumbered interface
management
VLAN
4093
VRF
External iBridge
management VLAN 23
VLAN network interface
Phy 600 IP address
LAG /18
Phy
VLAN 11
LT
NT
ISAM
4 — Management
The security in this case is based on:

• Layer 2 + Layer 3 combined:
• A specific external management VLAN
• ACL rules which limit the access to the management loopback IP address to this
external management VLAN
• Optional ACL rules which limit the access to specific management stations
identified by IP address
• Layer 4-7: specific authentication mechanisms on application level
4.5 Counters and statistics
Counters and statistics serve various purposes in the ISAM, like troubleshooting,
network dimensioning and SLA adherence and are defined on both the network and
subscriber side of the ISAM.
They can be retrieved from the ISAM using CLI, TL1, or an Element Management
System (EMS). See the following documents for detailed information and the
detailed command definitions for retrieving the ISAM counters and/or statistics
using CLI or TL1:
• Operations and Maintenance Using CLI for FD 24Gbps NT
• TL1 Commands and Messages for FD 24Gbps NT
4.6 Alarm management
Alarm management enables you to manage alarm reporting and logging for the
ISAM. You can manage the following alarm attributes and alarm reporting functions
for all basic system alarms, interface related alarms, derived alarms, and Threshold
Crossing Alarm (TCA) indications:
• alarm category and definition (fixed per release)
• alarm severity (intermediate, warning, minor, major, and critical)
• alarm is service affecting (yes, no)
• alarm must be reported (yes, no)
• alarm must be logged (yes, no)
• alarm lists and logs severity thresholds, that is, the minimum severity of an alarm
in order to be logged or reported in the alarm snapshot and the alarm-changed
trap)
• alarm filters: affect the way in which the ISAM reports its own alarms, as well as
the alarms from connected remote expansion units.
See the CLI Commands for FD 24Gbps NT and the TL1 Commands and Messages
for FD 24Gbps NT documents for alarm management command definitions.
4 — Management
Alarm categories and definition

There are four alarm categories:
• non-interface related alarms: these alarms include basic system alarms such as
equipment failure alarms.
• interface related alarms: these alarms involve ATM and xDSL interfaces.
• derived alarms: these alarms are raised in the system when programmed temporal
or spatial alarm filters are used (that is, alarms generated when the conditions set
in an alarm filter are met). See section “Programmable alarm filters” for more
information about temporal and spacial alarm filters and derived alarms.
• TCA alarms: these alarms are generated when a Performance Monitoring (PM)
counter or actual value of a parameter crosses a defined threshold value.
(Threshold Crossing Alert)
Alarms use the same definition method that consists of two main parts:
• the alarm type, which provides a general definition of the type of alarm; for
example, an xDSL alarm.
• the alarm number, which identifies a specific alarm within that type; for example,
a near-end LOS alarm
You can view alarm types and definitions as they are recorded in alarm lists and logs
using the TL1, CLI or an EMS like the 5520 AMS. See the Operation and
Maintenance Using CLI for FD 24Gbps NT / Operation and Maintenance Using TL1
for FD 24Gbps NT documents for a complete listing of all alarms, along with their
definitions (see TAP 2104). Alarm definitions are not user configurable.
Alarm severity
The operator can configure a (system-wide) minimum alarm severity level. There are
five alarm severity levels listed in ascending order of severity:
• indeterminate
• warning
• minor
• major
• critical
When the severity level of an alarm equals or exceeds the (system-wide) minimum
severity level, that particular alarm is forwarded to the alarm reporting and logging
filters where it is reported and logged as defined for that particular alarm. For TCA
alarms, when the TCA feature is enabled for an xDSL subscriber line, alarm
indications are always sent to the alarm reporting and logging filters. Whenever a
minor, major, or critical alarm is received, the corresponding alarm LED on the
faceplate of the alarm control unit installed in the shelf is activated.
You can configure the (system-wide) minimum alarm severity level and the
individual severity level of an alarm using CLI, TL1 or an EMS. See the CLI
Commands for FD 24Gbps NT and the TL1 Commands and Messages for FD
24Gbps NT for alarm management command definitions. Changing the severity level
for an alarm only affects new alarm events and does not affect alarm indications that
have already passed through the alarm reporting and logging filters.
4 — Management
Alarm lists and logs

You can set the alarm logging and reporting mode for individual alarms. When alarm
logging and reporting are enabled, alarm indications are always sent to the
appropriate alarm list and alarm log when the minimum alarm severity level for the
alarm is reached. Alarm logging and reporting are enabled by default.
There are three types of alarm list:
• current alarm list
• snapshot alarm list
• alarm severity delta logging list
The current alarm list and the snapshot alarm list display only the currently active
alarms. When the alarm reporting mode is enabled, alarm indications are sent to the
current alarm list.
The alarm severity delta logging list is a log of alarm indications (one for each alarm
severity) that can be accessed at any time and contains a historic record of alarm
events (start and end of active alarm). Only alarms that have their alarm logging
mode enabled appear on these alarm severity delta lists.
Current and snapshot alarm lists

The current alarm list changes dynamically as alarms are detected and pass through
the alarm filters. Because the list changes dynamically, it is impossible to get a
consistent view of the active alarm status. Therefore, if a stable view of the alarms is
preferred, the snapshot alarm list captures a momentary view of the active alarm
status at the time it is requested by the user. You can configure the minimum severity
level of the active alarms in the snapshot list and you have access to the snapshot
alarm list for a maximum time period of up to 120 seconds. The snapshot alarm list
provides the active alarms ordered first by severity (high to low), and then on
time-of-occurrence.
Alarm severity delta logging list

A separate alarm severity delta logging list exists for each of the five alarm severity
levels. Each change in the alarm condition, such as a change of alarm state from
alarm-on to alarm-off, is logged. Alarm state changes are logged in order of
occurrence, with a total capacity of 100 entries per alarm severity delta logging list.
You can set the action to be taken when the number of entries in alarm severity delta
logging list reaches full capacity:
• continuous wrap entries, where newer entries overwrite the oldest ones. A flag is
set to indicate that there was a wrap-around
• halt alarm logging when the logging list is full. In this case, alarm logging
resumes only after the alarm logging list is manually reset by the operator.
Resetting an alarm severity delta logging list empties the contents of that list.
4 — Management
Alarm clearing
Most alarms are cleared autonomously. Both the alarm-on and the alarm- off
situation are detected and reported. The alarm-off will result in the automatic
clearing of the alarm-on from the current alarm list.
However, some alarms cannot be cleared automatically and require operator
intervention to clear the alarm. The OSWP-Download-failure is an example of such
an alarm.
In order to clear these alarms, explicit operator intervention is needed using CLI
and/or an Element Management System. The list of alarms that need clearing
through operator intervention is specified in the Operation and Maintenance Using
CLI for FD 24Gbps NT / Operation and Maintenance Using TL1 for FD 24Gbps NT
documents for a complete listing of all alarms, along with their definitions. (see TAP
2104)
Alarm filters
There are three types of filters:
• alarm logging filter: determines if the alarm indication should be processed and
recorded in one of the five alarm severity delta logging lists.
• alarm reporting filter: determines if the alarm indication should be processed for
a current view or an alarm snapshot list.
• programmable alarm filters: enable you to customize how alarm reporting occurs
for specific diagnostic and monitoring scenarios.
Alarm filtering applies to both non-interface related alarms, such as equipment

failure alarms, and to interface related alarms, such as ATM and xDSL interfaces. It
is possible to enable and disable alarm filtering for individual alarms.
Programmable alarm filters

There are two types of programmable alarm filters:
• temporal alarm filters
• spatial alarm filters.
You can define a maximum of 31 temporal alarm filters and 31 spatial alarm filters.
See the TL1 Commands and Messages for FD 24Gbps NT document for
programmable alarm filter command definitions. The filters can also be configured
using an EMS. There is no CLI support.
When you use programmable temporal or spatial alarm filters, the ISAM raises a
derived alarm whenever the conditions of the alarm filter are met. The resulting
derived alarm has the same identification parameters as the alarm filter that
generated the derived alarm.
4 — Management
Temporal and spatial alarm filters
Using temporal alarm filters, you can limit the number of alarm state changes that
are reported for a particular alarm. For alarms that are frequently raised, you can
create a temporal alarm filter that will report only one alarm state change for a set
number of state changes that occur over a specified length of time. You can configure
the threshold for the number of state changes, and the time period of the filtering
window. Since temporal alarm filters are severity based, only alarm indications that
equal or exceed the alarm severity level are counted. In other words, it makes no
sense to configure a temporal alarm filter on an alarm that has a severity below the
global alarm severity level.
A temporal alarm is raised in the ISAM when:
• the number of alarm events reaches the set threshold during the filtering window
time period, OR
• the alarm event remains active for at least the filtering window time (even if the
set threshold is not met)
Figure 4-7 shows how a temporal alarm filter raises a derived alarm after the
configured threshold is reached (in this case set to 3). In the first case only 2 alarm
events occur during the filtering window time T, so no derived alarm is raised. In the
other cases, 3 alarm events occur in the window T, and a derived alarm is raised.
Figure 4-7 Temporal alarm by quantity

Only 2 events in time T:
no temporal alarm is
raised
Alarm
event
T T T
Threshold = 3
Temporal
alarm
Temporal alarm is cleared when

the alarm event is cleared
Figure 4-8 shows how a temporal alarm filter raises a derived alarm when the alarm
event is active for at least the filtering window time T. In the first case the alarm event
is cleared before T, so no derived alarm is generated; in the second case an alarm
event remains active for more then T, in which case the derived alarm is raised.
4 — Management
Figure 4-8 Temporal alarm by time

Event is cleared again
before time T expires:
no temporal alarm is raised
Alarm
event
T T
Threshold = 3
Temporal
alarm
Temporal alarm is cleared when

the alarm event is cleared
So the temporal alarm is always raised when the condition is met, and cleared
whenever the alarm event, triggering the alarm filter condition, is cleared,
independent of the filtering window time. See also Figure 4-7 and Figure 4-8.
A temporal alarm filter becomes active whenever the alarm event is raised on an
ISAM object (for example, on a port, ONT, …), i.e. at that moment timer T is started
(see figures above) and the number of occurences is counted. Each such filter can be
activated (by the alarm event) on at most 50 different objects at a time. A filter
becomes inactive again for a certain object whenever the condition is cleared (and so
no derived alarm is generated, or the derived alarm is cleared).
Temporal alarm filters are useful for, for example, TCA alarms that can be raised
frequently. Using temporal alarm filters, you can filter out minor TCA alarm
indications and provide better visibility of major TCA alarm conditions.
Using spatial alarm filters, you can create a unique alarm condition such that when
a specified group of individual alarms are raised, a derived alarm is reported. This is
used to identify alarm conditions that are characterized by a certain set of alarm
conditions occurring simultaneously. Say, for example, that 100 objects in the
system can experience the same alarm condition. A spatial alarm can be configured
on top of the basic alarm. The spatial alarm is generated (that is, derived alarm ON
condition) at the moment that a predefined number of these objects are in alarm (that
is, basic alarm ON condition).
Identification of alarm filters and derived alarms consists of two main parts: a type
identifier and a number. Temporal and spatial alarm filters have a unique filter type
identifier. Derived alarms have a unique alarm type identifier. The number used in
the identification of derived alarms matches the number assigned to the alarm filter
that generates the derived alarm. Additionally, each derived alarm entry recorded in
alarm reporting and logging lists contains the identification of the affected
component. In the case of an interface related derived alarm, the identification of the
affected interface is provided.
4 — Management
The state change of a derived alarm must pass through the alarm reporting and
logging filters before being added to the alarm reporting lists (current and snapshot
alarm lists) and the alarm severity delta logging lists respectively. A derived alarm
that is generated from a temporal filter is identified as an interface-related alarm if
the basic alarm, referenced by the filter, is also an interface-related alarm. The
derived alarms generated from spatial alarm filters are always identified as
non-interface-related alarms.
Configuring programmable alarm filters and derived alarms
You can activate and deactivate alarm filters after they are created using TL1 and/or
an EMS like the 5520 AMS. When you create a temporal or spatial alarm filter, the
ISAM automatically copies the parameter settings of the basic alarm to which the
alarm filter applies, and uses those parameter settings as default settings for the
derived alarm. The settings include:
• alarm category
• severity level
• service affecting or non-service affecting
• reporting mode
• logging mode
You can change these settings for the derived alarm, but not if the alarm filter is
active. You must first deactivate the alarm filter.
After the filter is deactivated, you can configure the filtering threshold, filtering
window, and the alarm to which the filter applies. Once configured, you must
manually reactivate the alarm filter.
Alarm reporting
Alarm reporting of the basic and derived alarms occurs differently, depending on
whether or not alarm filters are configured for the basic alarm.
If no alarm filters are configured for the basic alarm, then alarm state changes of the
basic alarm are always reported to the appropriate alarm reporting and logging lists
when the alarm conditions are met.
If a temporal alarm filter is configured for a basic alarm, only state changes of the
derived alarm are recorded in the appropriate alarm reporting and logging lists during
the time period when the derived alarm is on. During the off period, state changes of
the basic alarm are recorded in the appropriate alarm reporting and logging lists.
With spatial alarm filters, both the derived alarm state changes and the basic alarm
state changes are recorded in the appropriate alarm reporting and logging lists.
External alarms profiles

The ISAM equipment practices provide an extern alarm interface to which up to 5
external alarms can be connected, be it in a CO or cabinet environment. Upon alarm
condition detection, the ISAM will raise an external alarm, also known as
'customizable alarm' and/or 'environmental alarm', and are configured and handled
in the ISAM like any other, internal ISAM alarm (severity, logging, filtering, …).
4 — Management
For these external alarms, also an external alarms profile can be defined, reflecting a
configuration of external alarms parameters that correspond to a certain environment
where the ISAM is located (outdoor cabinet, CO, basement cabinet, …). Using these
external alarms profiles, we avoid the need to specify these parameters for each
ISAM separately.
The external alarms profile can be assigned either to the NT, or to the remote LT (in
case of a REM).
Note this profile is only applicable for the external alarms.
4 — Management
4.7 Software and database management
Software and database management is all about controlling the Operational

SoftWare Packages (OSWP) and databases on the system. A set of software and
database management features are available on the ISAM, that are both powerful and
efficient from an operational point of view.
A Push-Button Migration tool (PBMT) is delivered together with the ISAM
software. This tool provides all the required functionality to migrate and/or upgrade
an ISAM to a new software load, automating all the different steps of the software
upgrade and migration process.
The PBMT is expected to run on the same machine as the 5520 AMS, as the PBMT
needs certain specific files for its proper execution.
From R4.3.01 onwards, the PBMT is supported on both a Sparc and x86 platform
(Solaris OS), delivered as one installation package. At run tim, the correct libraries
and executables will be selected. Support is only provided for migrations to the target
release (that is, the release for which the PBMT is delivered).
OSWP and databases

The ISAM is capable of hosting an active (operational) and a non-active (stand-by)
Operational SoftWare Package (OSWP). Each package consists of a software
version and a set of system databases. Only one of the two OSWP packages can be
active in the ISAM, but the operator can switch between packages, making the one
operational, and the other stand-by.
Each package also consists of a set of system databases, more in particular the SHub
database, the IACM database and the xVPS databases (one physical database per
xVPS pair). From an operational point of view, if not mentioned otherwise explicitly,
the actions (backup, restore, migrate…) will be executed on the set as a whole, not
on an individual database of the set.
Software upgrade and migration

Of course there are rules on compatibility between software and databases: a package
can only become active, when the software version and the system databases in the
OSWP are compatible with one another. In this context, we make a distinction
between software upgrade and migration:
• Software upgrade is the process to upgrade a network element to a higher
software release not involving a migration of the system databases - there is no
system database change
This procedure is typically to be used when upgrading to a release in the same
software stream, for example, from R3.6.01 to R3.6.03c
• Migration is the process to upgrade a network element to a higher software
release requiring a migration of the system databases
This procedure is normally to be used when upgrading to a release from a higher
software stream, for example, from R3.6.01 to R4.0.02
4 — Management
A complete software upgrade/migration activity consists of a sequence of actions:

1 The operator demands the system to download a new OSWP. This demand is the
trigger for the system to initiate a file transfer session with the external file server
specified by the operator. So it is not the operator who puts the software on the
system disk.
2 The operator starts an off-line conversion of the database from the source release
to the destination release. It is the responsibility of the off-line migration tool to
upload the complete datbase, convert it to the destination release and to
download it to the node again.
3 When the new OSWP is downloaded, the operator activates this new software
and database set. The system will restart and come up with an upgraded software
version. All persistent configuration data remains available.
4 Once the upgrade is successful, the operator can remove the former software and
database package from the system in order to free space for the next upgrade.
Note that migrations and software upgrades do not have to be between consecutive
software releases/streams: the necessary functionality has been provided to be able
to 'skip' intermediate upgrade/migration steps. While no point for software upgrades,
this is less evident for migrations.
Also, in case of a failure to upgrade, the ISAM will automatically switch back to the
old software and database package and resume services.
Backup and restore

Next to a software upgrade and/or migration, database management also requires the
regular creation of backups in order to minimize the configuration loss in case of a
system crash. This can be done either manually or automatically. These ISAM
backups can afterwards be restored on the ISAM if needed.
Basically there is a distinction between two kinds of backup files:
• dm_complete<something>.tar
This is a backup of the complete ISAM database, including all the management
data, such as the IP address, the SNMP community strings and so on, which are
required to make remote management of the ISAM possible
• dm<something>.tar
This is the same as the 'dm_complete.tar' kind of file, but without all the
management data
Typically only the 'dm.tar' kind of file is restored as otherwise the management data,
required to have remote management of the ISAM, would be overwritten as well.
The <something> can be any text suitable for a file name, and, in case of automatic
backup enabled, this specifies the system IP address and the timestamp of creation.
Note that if automatic backup is enabled, the TFTP protocol cannot be used, as the
TFTP protocols require the file name to be known already up front at the server side.
Given the format of the generated backup file name, this is however not possible.
Alternatively the SFTP protocol or the FTP protocol can be used.
4 — Management
The configuration data of the ISAM is autonomously saved to the ISAM database on
the NT CF at different criteria:
• IACM: the database changes are cached in the system and autonomously saved
to the CF
• Every 60 seconds, and/or
• Whenever the cache of 5K is full (corresponds to 22 database updates), and/or
• On request of an IACM application, for example to safeguard some critical data
(software steered), and/or
• As part of an ISAM database backup request
• xVPS: the database changes are autonomously saved to CF
• Every 10 minutes if the xVPS configuration has changed indeed and the last xVPS
configuration change is at least 1 minute ago, and/or
• SHub: the database changes are autonomously saved to CF
• Every 10 minutes if the SHub configuration has changed indeed and the last SHUB
configuration change is at least 1 minute ago, and/or
The SHub configuration data can be saved to NT CF (database) at operator request
as well, for example, at the end of an SHub configuration script. This is however not
possible for the IACM data.
Active load
The release name of the current active ISAM software package (for example,
R3.6.01) can be consulted via EMS, TL1 and CLI.
Voice service management

The behavior of POTS voice services on ONTs can be controlled by downloading a
service configuration in XML format onto the ONT. This XML file can be sent to the
ONT via the in-band communication channel, used to provide data service.
In some cases, operators may require that the XML is downloaded to the ONT via
the Management VLAN, in order to provide a higher level of security. This approach
includes following steps:
1 The Element Manager generates the ONT service configuration in XML format
and makes it available on an FTP server reachable by the ISAM
2 The ISAM NT downloads the XML file from the FTP server
3 The XML file is sent to ONT using an internal OMCI channel
This approach is supported on Alcatel-Lucent Single Family Unit (SFU) and

Multi-Dwelling Unit (MDU) ONTs that do not use TR-069 for voice provisioning.
4.8 Equipment monitoring
4 — Management
NT CPU load
The average NT CPU load can be monitored using CLI, TL1 and/or an Element
Management System.
For SHub-based systems, both the IACM and the SHub CPU loads are monitored.
The CPU load is expressed as a percentage, ranging from 0% (no load at all) to 100%
(full load) and represents the average CPU load over the monitored period.
The monitoring is to be started and stopped explicitly at operator request. By default
(at ISAM start-up), the monitoring is not active. Once started at operator request, the
monitoring of the CPU load continues until the operator explicitly stops the
monitoring.
NT memory usage
The actual NT memory usage can be polled using CLI, TL1 and/or an Element
Management System.
For SHub-based systems, both the actual memory usage of the SHub and IACM is
counted.
Both the absolute value (expressed in Mbytes) as well as the relative value (used
percentage of the total available memory) is returned: always the actual values as of
the moment of the request are returned.
Thermal sensor data

Thermal sensor data can be retrieved from each board equipped with thermal sensors
and running software (so, for example, not from a passive splitter board).
Per thermal sensor, the following data can be retrieved (all expressed in degrees
Celsius):
• actual temperature
• low threshold temperature for TCA (T0_low)
• high threshold temperature for TCA (T0_high)
• low threshold temperature for shutdown (T1_low)
• high threshold temperature for shutdown (T1_high)
Only read access is provided for these parameters and none of the threshold
temperature parameters can be changed by the operator. They are fine-tuned by
Alcatel-Lucent in function of the actual board type and board variant.
The thermal sensor data as specified above can be retrieved via CLI, TL1 and/or
using an Element Management System, and are always the actual values as measured
at the moment of the request.
4 — Management
4.9 Access node control protocol
The purpose of the Access Node Control Protocol (ANCP) (also known as Layer 2
Control Protocol (L2CP)) is to allow a Broadband Network Gateway (BNG) to
manage service related parameters of a DSLAM. The relevant standard is still under
definition in IETF. In the ISAM a pre-standard is implemented.
In the draft ANCP standard some basic capabilities are defined, of which 2 are
currently supported on the ISAM:
• Access Topology Discovery:
Provides dynamic discovery of access topology by the BNG to provide tight QOS
control in the access network (that is, the Ethernet Aggregation network up to and
including the xDSL access loops). This can be done, for example, by shaping the
traffic towards the user at the bitrate currently available in the xDSL line of the
user.
• Layer 2 Operations and Maintenance:
BNG controlled, on-demand xDSL access loop test capability.
In the ISAM up to 62 ANCP partitions can be configured, each partition grouping a

number of xDSL subscriber lines (excluding VDSL bonding interfaces; ANCP on
SHDSL lines is only supported on NSLT-B). One particular xDSL subscriber line
can only belong to maximum 1 ANCP partition and each partition is managed by a
dedicated set of BRASs via an ANCP session. The partitions are created and
identified by the ISAM operator. The BNG/BRAS cannot set its own partition ID.
The partition ID can be signaled to the BNG/BRAS in the ANCP packet header.
Up to 62 different ANCP sessions are supported, where for each ANCP partition,
multiple sessions can be defined. But it is not allowed for one session to manage
multiple partitions.
The BRAS and aggregation switches are directly attached to the ISAM via a L2
EMAN, through a dedicated VLAN, distinct from the VLAN used for ISAM
management. The VLAN used for ANCP is hard coded to “6” and cannot be
modified.
An alarm is raised whenever the ANCP connection between BRAS and ISAM is lost
for some reason.
5— Line testing features
5.1 Overview 5-2
5.2 Metallic test access 5-4
5.3 Single-Ended Line Testing 5-7
5.4 Dual-ended line testing 5-8
5.5 Metallic-Ended Line Testing 5-9
5.6 ATM F5 5-10
5.7 Link Related Ethernet OAM 5-10
5.8 Narrowband Line Testing 5-12
5.9 SFP diagnostics 5-15
5 — Line testing features
5.1 Overview
This chapter describes the various line testing features within the ISAM and ISAM
Voice.
All line testing capabilities provide a means to execute pro-active and/or re-active
measurements to diagnose (potential) issues with the deployed equipment. As such
they can:
• bring OPEX savings such as the ability to save on buying external test equipment,
avoiding truck rolls.
• increase customer satisfaction due to decreased service degradations or
interrupts.
The line testing capabilities depend upon the type of interface. For an overview of
the different types of interfaces (both for ISAM and ISAM Voice), see
chapter “System interface overview”.
ISAM supports line testing for:
• Ethernet network and subtending interfaces
• DSL interfaces (ATM or PTM mode) at the subscriber side
• Active Ethernet interfaces
• POTS and ISDN lines at the subscriber side
But before considering the line test capabilities of these interfaces, we have to
consider the nature of DSL versus POTS and ISDN.
DSL is a transmission technology that works in overlay with POTS or ISDN lines:
• “narrowband” is used for the POTS or ISDN signals
• “broadband” is used for the DSL signal
Both narrowband and broadband signals can be transported simultaneously on one
physical line and a splitter technology is used to multiplex or split these signals. The
part of the ISAM processing broadband is named the DSL line. The part of the ISAM
Voice processing narrowband is named the POTS line or the ISDN line. Therefore,
although a DSL line and a POTS or ISDN line are distinct lines from the perspective
of the ISAM or the ISAM Voice, they can correspond to one physical line.
Therefore, some tests will test the DSL line (broadband), other tests will test the
POTS or ISDN line (narrowband), but some tests will affect both.
The splitter technology can be integrated or can be outside of the ISAM or the ISAM
Voice (refer to the 7302 ISAM Product Information or the 7330 ISAM FTTN Product
Information). If integrated, this technology is supported by dedicated boards
(appliques) that are managed from the ISAM, or is integrated within the DSL board.
The splitter boards work in conjunction with the DSL LT boards. The physical lines,
carrying both broadband and narrowband, are identified with the same identifier as
the DSL line.
The overview of the line testing features:
• tests for the physical subscriber line:
• Metallic Test Access (MTA)
• tests for a DSL line:

• MTA
• Single-Ended Line Test (SELT)
• Dual-Ended Line Test (DELT)
• Metallic-Ended Line Testing (MELT)
• the DSL line can be of ATM or of PTM mode:
• For DSL lines of ATM mode: ATM F5
• For DSL lines of PTM mode: Link related Ethernet OAM
• tests for a POTS or ISDN line:
• MTA
• Narrowband Line testing
• tests for an Ethernet subscriber line:
• Link related Ethernet OAM
• SFP diagnostics
• tests for an Ethernet network or subtending interface:
• SFP diagnostics
Note — MTA appears on the list of test capabilities for the physical
line, the DSL line, and for the POTS/ISDN line. This reflects that
some MTA tests are for broadband, some for narrowband, some are
outward toward the subscriber line, and some are inward to the
MODEM/SLIC.
Figure 5-1 Position line testing capabilities for DSL - POTS/ISDN lines
DSL applique
RTU (MTA)
Relays Subscriber line
DSL LT (SELT, DELT)

DSL
Modem LPF
line
Towards PSTN or ISAM Voice

Voice LT
POTS/ISDN Relays
SLIC
line
(Narrowband
line testing) Voice applique
5.2 Metallic test access
MTA provides a set of subscriber line tests both for narrowband and for broadband.
MTA is performed on a line-by-line basis using TL1 or AMS.
MTA is a partially integrated test facility:
• MTA relies on a non-integrated Remote Test Unit (RTU) that is connected to the
ISAM or ISAM Voice.
• MTA requires MTA-capable appliques terminating the subscriber line.
MTA can be used to set the relays so that the RTU gets outward access to, for
example, the narrowband physical line, the broadband physical line, or the full
physical line. MTA also allows setting the relays so the RTU gets inward access to
test, for example, the narrowband towards the LT board terminating the POTS or
ISDN line, or the broadband towards the LT board terminating the DSL line.
Note that it is possible to test the narrowband of a line from two different places:
• the narrowband line can be tested outward from the Voice applique, in which case
it is managed as a test of the POTS line.
Although the MTA technology applies in principle to POTS and ISDN, it must
be noted that it is supported only for POTS.
• the narrowband line can be tested outward from the splitter board (DSL applique)
that is associated with a DSL LT board, in which case it is managed as a test of
the DSL line.
In this way the MTA technology is supported for POTS and for ISDN lines.
It is also possible to equip collocated expansion shelves with MTA-capable

appliques and to connect them to the host shelf with a cable, to support the same tests
from the RTU connected to the host shelf.
Some tests can be executed during turn-up of a subscriber line, for example, the
operator can test the line to verify whether it is suited to carry the promised xDSL
service. After the service has been established, the operator can also perform a
variety of tests during routine or diagnostic testing.
Testing using MTA can be either single-ended or dual-ended.
Test access modes

The following test access modes are supported for each Test Access Port (TAP):
• Released mode: releases all test connections and frees all TAP resources.
• Loop around mode: characterizes the TAP so that its influence can be deducted
from the parameters measured during the split access mode.
• Split access mode: provides a breaking connection that allows the test system to
test outward towards the line and to test inward towards the LT equipment.
Note — Only full MTA requires all the test access modes.
Figure 5-2 shows the test access modes.
Figure 5-2 Test access modes

Released Loop around
Line Line
Facility pair Facility pair
RTU RTU
xTU-C xTU-C
Equipment pair Equipment pair
LPF LPF
DSLAM DSLAM
PSTN PSTN
Line
Facility pair
RTU
xTU-C
Equipment pair
LPF
DSLAM
PSTN
Split access
The two following access modes are partial implementations of the split-access
mode and are called “limited test access”:
• Limited outward access mode: provides a breaking connection that allows testing
outward toward the line. The Low Pass Filter (LPF) and the line to the Public
Switched Telephone Network (PSTN) remain connected to the line. This limits
the number of measurements that the test system is capable of.
• Undisturbed outward access mode: provides a breaking connection that allows
testing outward toward the line. The LPF and the line to the PSTN are either not
present or they have been removed from the line. This ensures that the
measurements are not disturbed by the presence of the LPF or the DC battery
voltage that is put on the line.
Figure 5-3 shows the partial implementations of split-access mode.
Figure 5-3 Partial implementations of split-access mode

Limited outward access Undisturbed outward access
Line Line
Facility pair Facility pair
RTU RTU
x-TU-C x-TU-C
Equipment pair LPF Equipment pair LPF
DSLAM DSLAM
PSTN PSTN
MTA support in the 7302 ISAM

Full test access scenarios are supported, using the Metallic Test Access Unit
(MTAU) function. The MTAU function is implemented using a test applique and LT
appliques, which are present in the splitter shelf. Using this function, a test head or
Remote Test Unit (RTU) can get metallic access to a line in the 7302 ISAM by way
of a TAP, to perform the necessary tests.
MTA support in the 7330 ISAM FTTN

Full test access scenarios are supported in the 7330 ISAM FTTN. The expansion
nodes (expansion shelf and REM/SEM) do not support MTA.
• The 7330 ISAM FTTN shelf supports MTA through an MTAU function
implemented by the test access board (or NTIO board with MTA function), in
conjunction with the multi-ADSL and POTS splitter appliques. All units must be
present in their respective shelf for the MTAU function to operate. Using this
MTAU function, a test head or RTU can use a single TAP on the test access board
to get metallic access to any subscriber line connected to the 7330 ISAM FTTN.
• The 7330 ISAM FTTN shelf uses an RJ-45 MTA connector on the test access
board as the TAP for the test in and test out signals between the testhead and the
shelf.
• The 7330 ISAM FTTN shelf uses these boards to provide a relay-based matrix to
connect the test in and test out signals with the backplane for connection to the
appropriate applique installed in the shelf.
• The 7330 ISAM FTTN shelf supports MTA on the multi-ADSL and POTS
splitter appliques. On-board relays are used to connect the test in and test out
signals to the appropriate connected subscriber line.
Note 1 — The MTA test bus may be interconnected / daisy-chained

for up to 8 collocated FTTN host nodes using a maximum cable
length of 10 m.
Note 2 — Since MTA is currently supported on host nodes only, the
Test Operating System must ensure that only one port in this daisy
chain configuration is enabled at any one time
Test Access Control

Test Access Control (TAC) is done with TL1 commands, which are sent using the
TL1 agent of the 7302 ISAM or 7330 ISAM FTTN shelves in response to the test
head.
5.3 Single-Ended Line Testing
Single-Ended Line Testing (SELT) tests the DSL line from the DSL LT board. SELT
does not require CPE to be connected to the peer side of the line.
SELT can be used as a base for a DSL service level agreement between provider and
customer, for fault detection and for monitoring of line degradation. SELT works
together with external data analysis software, such as the Alcatel-Lucent 5530
Network Analyzer (5530 NA), to provide loop pre-qualification and maintenance of
the network.
Note — See the 5530 Network Analyzer User Guide for more
information about SELT using the 5530 NA.
SELT can be performed from the DSL LT board without need for support by the CPE
or for a craftsman to be present at the customer premises.
SELT is based on Frequency Domain Reflectometry (FDR). An excitation signal is
sent on the line and its echo response is analyzed. Processing of the echo response is
done in the 5530 NA. The polarity and position of the reflections indicate the loop
length, the attenuation, the presence of a gauge wire change, and an open, short, or
bridged tap and its distance from the DSL LT board of the line under test.
SELT provides a line test tool built inside the xDSL modem to measure the loop
characteristics between the U-C and the U-R interface and allows for:
• detection and location of metallic faults (open/short).
• detection, location and length of bridge taps.
• noise measurement and detection of interferences.
• measurement of the line attenuation.
• estimation of the maximum achievable bit rate.
• estimation of the line length.
The operator can check the presence and quality of, for example, a wire termination
Main Distribution Frame (MDF) or SAI / DFI (Service Area / Feeder Distribution
Interface). This feature can be of help in situations where this interconnection is
being provisioned by a third party.
SELT support
SELT measurements are supported on the following boards:
• multi-ADSL LT boards
• VDSL LT boards
• VDSL2 LT boards
These boards can be located in the main subrack or in remote subracks (FD-REM,
VSEM-D, …).
SELT measurements
The following SELT measurements and tests are supported:
• uncalibrated echo response
• echo variance
• noise
The ISAM allows up to 5 simultaneous SELT measurements per LT board.
5.4 Dual-ended line testing
Dual-Ended Line Testing (DELT) tests the DSL line from the DSL LT board. DELT
requires a CPE to be connected to the peer side of the line.
This loop diagnostics function enables the immediate measurement of line
conditions at both ends of the line without dispatching maintenance technicians to
attach test equipment to the line. The resulting information helps to isolate the
location (inside the premises, near the customer end of the line, or near the network
end of the line) and the sources (cross-talk, radio frequency interference, and bridged
tap) of impairments.
DELT support
DELT measurements are supported on the following boards:
• VDSL LT boards
DELT measurements
The following diagnostic measurement data are collected during a test using DELT:
• actual operational mode
• operational mode capabilities (ATU-C/ATU-R)
• SNR margin (US/DS)
• loop attenuation (US/DS)
• signal attenuation (US/DS)
• aggregate output power (US/DS)
• actual PSD (US/DS)

• attainable bit rate (US/DS)
• modem identification parameter: ATU-R ModemVendorID
• carrier-related data: Hlog (US/DS), Hlin (US/DS), QLN PSD (US/DS), SNR
(US/DS)
5.5 Metallic-Ended Line Testing
Metallic-Ended Line Testing (MELT) tests the DSL line from the DSL LT board.
MELT does not require the CPE to be connected to the peer side of the line.
MELT can be used as a base for fault detection and monitoring of line degradation.
MELT works together with external data analysis software, such as the
Alcatel-Lucent 5530 Network Analyzer (5530 NA), to provide loop pre-qualification
and maintenance of the network. Also basic management, to start measurements and
report results, is provided through CLI.
Note — See the 5530 Network Analyzer User Guide for more
information about MELT using the 5530 NA.
MELT is performed from the DSL LT board without need for support by the CPE or
for a craftsman to be present at the customer premises.
The MELT functionality is based on the technology for the narrowband POTS
subscriber lines.
MELT provides a line test tool built inside the ISAM to measure the loop
characteristics between the U-C and the U-R interface and allows for:
• detection and location of metallic faults (open/short/bad contacts)
• detection of cable degradation (for example, due to cable moisture)
• detection of external voltages
• line pair identification
• detection of signature topologies
MELT support
MELT measurements are supported on the following boards:
• VDSL LT boards
• SHDSL boards
MELT measurements
The following MELT measurements and tests are supported:
• Foreign voltage (AC/DC): measures foreign voltage of a/Earth, b/Earth, and a/b
• Capacitance: measures capacitance of a/Earth, b/Earth, and a/b
• Insulating resistance: measures insulating resistance of a/Earth, b/Earth, and a/b

• Termination detection: detects whether a termination circuit connects to the line
• Pair identification tone generation
The ISAM allows up to one simultaneous MELT measurement per LT board.
5.6 ATM F5
On ATM based DSL interfaces it is possible to use ATM F5 loopback. The following
functionality, as is specified in ITU-T I.610, is supported:
• active: the operator asks for a loopback test
• passive: the CPE triggers a loopback test and the ISAM responds
5.7 Link Related Ethernet OAM
Introduction
Link-Related Ethernet OAM (IEEE 802.3 clause 57 standard) enables network
operators to monitor the health of the network and quickly determine the location of
failing links or fault conditions. The feature allows remote side information to be
retrieved for a link connected with a node for which SNMP may not be available as
default.
The feature does not include functions such as station management, bandwidth
allocation or provisioning functions, which are considered outside the scope of this
standard.
Figure 5-4 shows a typical Link Related Ethernet OAM configuration.
Figure 5-4 Typical Link Related Ethernet OAM Configuration
7302 ISAM
or
7330 FTTN
CPE
IEEE802.3 clause 57
(Link Ethernet OAM)
General description
Link-Related Ethernet OAM information is conveyed in Slow Protocol frames called
OAM Protocol Data Units (PDUs). Link-Related Ethernet OAM PDUs contain the
appropriate control and status information used to monitor, test, and troubleshoot
OAM-enabled links. Link-Related Ethernet OAM PDUs traverse a single link, and
as such, are not forwarded by MAC clients (for example, bridges or switches).
Link-Related Ethernet OAM provides a mechanism, called discovery, to detect the

presence of an OAM sub layer at the remote DTE. During the Discovery process, the
ISAM and the CPE exchange their respective configuration information and evaluate
the remote information to determine compatibility. The decision for accepting
remote configuration is based on the remote system OAM mode, version, maximum
PDU size, Parser Action, Multiplexer Action, and function supported information. If
these parameters are accepted, the discovery will complete and-Link Related
Ethernet OAM will be operational. Otherwise, the remote configuration is rejected
and requires operator intervention to rectify the conflicting parameters.
Link-Related Ethernet OAM has provision to retrieve one or more MIB variables,
also referred to as attributes, from the CPE. The operator can retrieve MAC layer
counters and PME counters from the CPE after successful completion of discovery.
The ISAM supports some Link-related Ethernet OAM functions on its Ethernet and
EFM user interfaces, that is, on interfaces terminated on LT boards.
Link-Related Ethernet OAM procedures

The following subsections describe the different Link-Related OAM phases as
defined in the standard IEEE 802.3-clause 57, and its support within the ISAM.
Discovery
The first phase of Link Related Ethernet OAM is discovery. This phase is started
when the operator enables the Link Related Ethernet OAM feature.
Discovery has 3 main functions:
• provide a mechanism to detect the presence of an OAM sub layer
• identify the devices in the network, along with OAM capabilities
• setup of the OAM link
During this discovery procedure the ISAM always negotiates to become the active
DTE. The ISAM never accepts to become the passive DTE. The ISAM never accepts
the peer DTE to become active (the standard allows both sides to be active).
Link monitoring
The standard defines link monitoring tools for detecting and indicating link faults
under a variety of circumstances. Both Event Notification and Variable Retrieve are
part of link monitoring.
1 Link monitoring uses the Event Notification OAM PDU, and sends events to the
peer OAM entity when the number of problems detected on the link cross a
threshold.
2 The manager can initiate a Variable Request to retrieve data about the link from
the peer side. This capability allows emulating a non-intrusive loopback. It
behaves like a “L2 ping” as each Variable Request shall be replied with a
Variable Response.
The ISAM does not support Event notifications: it does not generate Event
Notifications and ignores received Event Notifications.
The ISAM allows the manager to initiate a Variable Request to retrieve remote CPE
data to know the current link status. It supports to retrieve:
• Physical Medium Entity (PME) data
• PME Aggregation Function (PAF) data
By forcing the peer side to be in passive mode, the ISAM does not support the peer
side to retrieve data from the ISAM through Variable Requests / Responses.
Remote failure indication

A set of flags in the header of any OAM PDU allows an OAM entity to convey severe
error conditions to its peer.
The ISAM does not report critical events to the peer side, and does not report the
reception of critical events from the peer side to the operator.
Remote Loopback
Link-Related Ethernet OAM provides an optional data link layer frame-level
loopback mode, which is controlled remotely. This means: one side forces the peer
side to go in a loop mode and to send back the received frames.
The ISAM Ethernet line card supports a method to invoke remote loopback at the
peer end. The looped back traffic can be monitored using performance counters at
the Ethernet physical layer of the line card. ISAM does not support generation of test
traffic towards the peer and relies on network traffic (or an upstream device) to be
used during loopback.
As an active DTE, ISAM ignores any remote loopback request received from the
peer.
DSL LT boards do not support invocation of remote loopback at the peer end.
5.8 Narrowband Line Testing
Narrowband Line Testing provides a set of tests for the narrowband on POTS/ISDN
subscriber lines, to test the line from the SLIC on the Voice LT board. Narrowband
line testing support is LT board hardware and software dependent.
Management of the narrowband line test feature for ISAM Voice is supported by the
5530 Network Analyzer. Also basic management to start measurements and report
results is provided through CLI.
Narrowband line testing is supported for POTS/ISDN LT boards operating in the
H.248 and supported for POTS in SIP environment.
Line testing support on POTS

The following test can be performed with the narrowband line testing feature (on
POTS (H.248 and SIP):
• Electrical measurement tests:
The purpose of these tests is the measurement of electrical parameters. These tests
do not require customer assistance. Any or all of these tests can be invoked in the
same test request for a given user port. Electrical measurement tests are:
• Foreign voltage (AC/DC): measures foreign voltage of a/Earth, b/Earth, and a/b.
• Capacitance: measures capacitance of a/Earth, b/Earth, and a/b.
• Insulating resistance: measures insulating resistance of a/Earth, b/Earth, a/battery,
b/battery, and a/b.
• Impedance: measures the impedance of a/Earth, b/Earth, and a/b.
• Termination (M Socket detection): detects whether a phone, or just a resistance
connects the line.
• Feeding voltage: measures voltage over wires in open circuit and verifies that the
voltage remains within thresholds.
• Feeding current: for NPOT-A a resistor, loading the wires, is connected and the
current in limiting mode is measured. For NPOT-B and NPOT-C, the system will
measure the real feeding current on the subscriber line.
• Noise level: detects abnormal noise level, for example, crosstalk
• Longitudinal current (Supported on NPOT-B and NPOT-C, SIP only)
• Group test:
This test consists of a combination of the predefined electrical measurements
requested by the OS in previous electrical measurement tests. The test combines
voltage, capacitance and insulating resistance measurements.
• AC foreign voltage: a/Earth, b/Earth, and a/b
• DC foreign voltage: a/Earth, b/Earth, and a/b
• capacitance: a/Earth, b/Earth, and a/b
• insulation resistance: a/Earth, b/Earth, a/b, and b/a
• Detection of electronic ringers.
Two types of electronic ringers can be detected (Supported on NPOT-B and
NPOT-C, SIP only).
• Termination (M-Socket) detection)
Detects if the line is connected by an M-socket (470k ohm resistance in series
with a diode) or a resistance.
• Dial tone test:
This test checks the ability of the line circuit to detect an off-hook and to check
the provision of the dial tone. An off-hook condition is simulated in the ISAM.
This off-hook must be detected by the line circuit and is further processed by
call-handling software. For H.248 the MGC then interprets it as a real off-hook
and sends a dial tone. For SIP, ISAMV will generate a dial tone upon receiving
the off-hook event.
The time is measured and compared with a predefined threshold. Returned result
is the delay-to-dial tone.
• Howler tone test:

This test lets the user know that the handset is not on-hook and restores the user
state from parking to idle after the handset goes on-hook. If the user does not go
on-hook, the howler tone is stopped after a predefined time-out. The howler tone
level and frequency depend on the specifications in different countries.
• Status monitor:
This test lets the operator know the status of the indicated user.
• Talking tests are supported on ISAM, but not on NA5530. The following tests are
supported:
• Talking with Subscriber
• Subscriber Private Meter Pulses
• Resistance of user's loop (AB)
• Line Reverse
• Ring Subscriber with Auto Ring Trip
• DP/DTMF Signal
• Block Reading Mode:
One extended new test mode (only for Foreign Voltage AC/DC, Capacitance,
Insulation Resistance) for the basic electrical test types, it will return 20 reading
results of one electrical test item in each session.
• Continuous Reading Mode:
Another extended new test mode (only for Foreign Voltage AC/DC, Capacitance,
Insulation Resistance) for the basic electrical test types, in one test session, the
operator can repeat the test item after the last test result is reported to it. This
mode also accepts only one electrical test item in each session.
Line testing support on ISDN

ISDN line test is only supported in H.248 environment.
The following tests can be performed with the narrowband line testing feature on
ISDN (H.248):
• ISDN BA loopback test with test pattern:
• Complete loopback with test pattern.
Loopback of full bit stream (B1 and B2 and D channel)
• Loopback at ISDN LT and NT/NT1
Self test on layer 1 by the ISAM-V: ISAM-V generates a test pattern and activates
a loopback at the LT + verification and evaluation of received test pattern.
Test towards the NT/NT1: ISAM-V generates a test pattern and activates a loopback
at the NT + Verification and evaluation of received test pattern
Only when the transmitted and received patterns are exactly the same, the test is
considered as passed.
The test pattern is hard-coded (NOT configurable).
• Precondition for executing ISDN BA loop back test:
The ISDN BA loop back test will be rejected in case the ISDN B channel would be
busy.
Otherwise the ISDN BA loop back test (including loopback test to the NT board and
loopback test to the LT board) will be accepted and executed (on condition that the
ISDN user port has been provisioned).
• ISDN electric line tests:

• Foreign voltage (AC/DC): measures foreign voltage of a/Earth, b/Earth, and a/b
• Resistance: measures insulating resistance of a/Earth, b/Earth, a/b and b/a
• Capacitance: measures capacitance of a/Earth, b/Earth, and a/b
• Precondition for executing ISDN electric tests:
The tests should be supported in any port status except for line busy.
Extended Test modes

The following extended test modes can be performed:
• Block Reading Mode:
One extended new test mode (only for Foreign Voltage AC/DC, Capacitance,
Insulation Resistance) for the basic POTS electrical test types, it will return 20
reading results of one electrical test item in each session.
• Continuous Reading Mode:
Another extended new test mode (only for Foreign Voltage AC/DC, Capacitance,
Insulation Resistance) for the basic POTS electrical test types, in one test session,
the operator can repeat the test item after the last test result is reported to it. This
mode also accepts only one electrical test item in each session.
Note — Both extended test modes are not supported on ISDN.
5.9 SFP diagnostics
SFPs are used to terminate network, subtending, inter-shelf, line board Ethernet
interfaces or xPON.
The ISAM supports the digital diagnostics function in line with SFF-8472.
When isolating a data path problem, for example, fiber degradation, the operator can
use the management interface to retrieve the instantaneous received optical power
level and transmitted optical power level from an SFP.
This diagnostics functionality is available on all SFP, SFP+ and XFP interfaces of
the ISAM system.
6— Network timing reference support in
ISAM
6.1 Introduction 6-2
6.2 ISAM clock system and NTR extraction 6-7
6.3 Downstream NTR clock distribution 6-17
6.4 Applicable standards 6-18
6 — Network timing reference support in ISAM
6.1 Introduction
Scope
This chapter describes the different clock systems and Network Timing Reference
(NTR) capabilities of the ISAM. A specific ISAM board will not support all of these
capabilities. To know which of these functions are supported on a specific ISAM
board, refer to the Product Information document and/or the Unit Data Sheet (UDS)
of that board.
Contrary to most of the other chapters in this system description, this section is not
focused on only the 24Gbps NT family, or, only the 100Gbps/320Gbps NT and FX
NT family, since both families will be covered in this chapter. If an NTR function is
supported or not is board-dependent, and less family-dependent.
Example: SyncE is supported on some board variants in the 100Gbps/320Gbps NT
and FX NT family. While SyncE is not supported on most boards in the 24Gbps NT
family, it is supported on the NRNT-A (that is, the NT board for Standalone REM).
A summary of NTR capabilities of the most advanced board variants in each family
is given in Figure 6-1 and Figure 6-2. In many cases, less advanced board variants
with less or no NTR capabilities are available, and this for deployments where these
features are not needed. The following section clarifies at a high level when such
features are needed or not.
Applications as driver for specific clock or NTR requirements

This section discusses high-end NTR capabilities on the ISAM such as BITS, SyncE,
NTR on DSL, and so on. However, many applications such as High Speed Internet
(HSI), Video, Packet Voice, Data Offload in Mobile Backhaul do not require such
high-end clock system (see Table 6-1). So, for these applications the usual and less
complex NTs and LTs are sufficient for network deployments.
Each access technology (ADSL, VDSL2, SHDSL, Ethernet) may have its specific
clock requirements to guarantee synchronization and proper functioning between
both ends (CO and end-user). However, in general, these clock requirements are
taken care of in the design of LT boards for that specific access technology, and do
not impose any restrictions on the specific NT boards which can be used. Some
exceptions exist (for example, voice over POTS line) and they will be covered in the
section on that access technology. Clock requirements or restrictions related to a
specific access technology are in general not in the scope of this chapter.
Table 6-1 Specific clock requirements per application
Application Required on NT Required on LT

(over DSL, Ethernet)
High Speed Internet (HSI), External NTR source: not required All LTs are suited, that is,
Video, Local Clock Accuracy: low (32 or no specific clock
50 ppm is sufficient) requirements on LT.
Packet Voice
(1 of 2)
Application Required on NT Required on LT

(over DSL, Ethernet)
Voice via POTS line External NTR source: not required All voice LTs are suited,
Local Clock Accuracy: 4.6 ppm is that is, no specific clock
required requirements on LT.
Long fax or modem calls via POTS External NTR source: SyncE In or All voice LTs are suited,
line BITS In that is, no specific clock
requirements on LT.
NTR distribution from network • External NTR source: SyncE In NT or NTIO output can be
node to network node (for or BITS In used, and then no
example, to other DSLAMs) • NTR Out: SyncE Out or BITS requirements on LT.
Out Alternatively, SyncE
output on an Ethernet LT.
Mobile backhaul data offload External NTR source: not All LTs are suited, that is,
required no specific clock
Local Clock Accuracy: low (32 or requirements on LT.
50 ppm is sufficient)
Full mobile backhaul (with External NTR source: SyncE In or • DSL LTs: NTR on
frequency synchronization) BITS In VDSL2 or SHDSL (Note:
NTR on ADSL is not
supported on DSL-LTs)
• Ethernet LTs: SyncE
out
Full mobile backhaul with phase Not supported. Not supported.

synchronization or ToD Note: Phase synchronization or
requirement ToD is only required for some
mobile applications, and even
then in most cases an alternative
option exists which does not
require these features.
Alternative solution: Provide
Mobile Backhaul data offload
only, with phase sync or ToD via a
different channel (for example,
GPS receiver)
Packet-based Business External NTR source: not required All LTs are suited, that is,
applications Local Clock Accuracy: low (32 or no specific requirements
50 ppm is sufficient) on LT.
Business applications with NTR External NTR source: SyncE In or • DSL LTs: NTR over
requirements (for example, TDM BITS In SHDSL or VDSL2
leased lines) • Ethernet LTs: SyncE
out
(2 of 2)
Only some applications such as Full Mobile Backhaul (with frequency

synchronization) and some Business Applications (for example, TDM leased lines)
will require NTR support (see Table 6-1). This then means that NT boards are
required which either support BITS inputs or SyncE inputs, and LT boards
supporting NTR over DSL in case of SHDSL or VDSL2, and SyncE out on Ethernet
lines. For GPON LTs, there are no specific requirements, since the framing of GPON
has inherent sufficient high clock quality (assuming the appropriate NT is used). But,
an ONT needs to be selected with an NTR output (for example, SyncE on an Ethernet
output port, or a BITS out).
NTR in mobile applications, and especially in mobile backhaul, frequency

synchronization has always been sufficient in the past, and phase synchronization or
ToD was not required. With new mobile generations (for example, LTE) also the
latter requirements may appear. However, in general, different options exist in the
new mobile standards, and only some of these options (for example, TDD
technology) require ToD, while mostly alternative options (for example, FDD) exist
which do not require this. It depends very much on the selected technology which
will be used in a mobile network, if phase synchronization or ToD will be possibly
required there. And even if the latter is the case, the ISAM is then still capable to
transport the mobile data, if the phase synchronization or ToD timing signal is
transported in parallel via an alternative way (for example, via GPS/ GNSS).
To know which NT boards and LT boards in the ISAM portfolio support the specific
NTR requirements for a certain application (according to for example, Table 6-1),
please consult the Product Information document and/or the UDS of that board.
The ISAM NTR features support a very wide range of applications. On the market
still other clock solutions are available, which in most cases are just alternatives, that
is, they just support the same applications in a different way. In some cases, they may
be transparent to the ISAM, and could therefore also be used. An example is
Adaptive Clock Recovery (ACR). ACR requires larger buffers and a better local
oscillator in the end-receiver, and will therefore be more expensive. An investment
in a somewhat more expensive ISAM NT board with SyncE or BITS support will
probably be better than having to deploy a more expensive receiver with ACR at
every end-user. Furthermore, the larger buffers needed for ACR increase the
end-to-end delay and may therefore require echo-cancellation for interactive services
(for example, voice or video calls).
Overview of NTR support on ISAM

Table 6-1 made clear that NTR is not required for all applications. However, in some
cases it is required, and Figure 6-1 and Figure 6-2 give a high-level view on the
supported options on NT boards and LT boards for the FD 24Gbps NT family and
the FD 100/320Gbps NT and FX NT family, respectively.
Figure 6-1 Overview of possible NTR support on some LTs and some NTs in the FD
24Gbps NT ISAM family
Sync Eth
LT
8 kHz
kHz NTR
DSL
8
LT
Voice DSL
Optional GE GE PHY
NRNT -A
backplane
backplane DSL
network
8 kHz
8 kHz
backplane
backplane POTS/ISDN
Sync Eth Standalone REM

BITS
GE PHY
G.703
DSLLT
8 kHz Sync Eth 8 kHz
8 kHz NTR
Eth
LT
Voice DSL
backplane GE PHY backplane
backplane DSL
CTRL
8 kHz NTR 8 kHz
8 kHz
DSL
LT
NTIO
NT
backplane DSL backplane
backplane POTS/ISDN
Voice
8 kHz
SEM/Distributed REM
backplane POTS/ISDN
NTIO
8 kHz Sync Eth
Eth
Hub ISAM
backplane GE PHY
NTR
DSL
NT
8 kHz
LT
BITS Sync Eth
backplane DSL
NT
G.703 GE PHY
Voice
8 kHz
7330 RA backplane POTS/ISDN
Optional BITS
PDH/SDH G.703
network
Outdoor ISAM
Figure 6-2 Overview of possible NTR support on some LTs and some NTs in the FD
100/320Gbps NT ISAM family
GPON
8 kHz GPON PHY

BITS backplane GPON
G.703
8 kHz
DSL
8 kHz Sync Eth NTR
LT
Eth
backplane GE PHY backplane DSL

CTRL
Sync Eth
DSL
8 kHz NTR
NT
LT
Voice
GE PHY 8 kHz
backplane DSL
backplane
NTIO
POTS/ISDN
Voice
8 kHz
SEM/Distributed REM
backplane POTS/ISDN
Sync Eth
GPON
GE PHY 8 kHz GPON PHY

Sync Eth Sync Eth backplane GPON
BITS or Sync Eth
GE PHY
GE PHY GE PHY
NTIO
8 kHz Sync Eth

Eth
Hub ISAM Sync Eth Optional GE backplane GE PHY

GE PHY network
DSL
8 kHz NTR
NT
LT
G.703
backplane DSL
NT
Voice
8 kHz
backplane POTS/ISDN
Optional BITS Sync Eth
NT
PDH/SDH G.703 GE PHY

network
Collocated ISAM shelves Outdoor ISAM
The FX NT supports in addition also IEEE1588 as NTR source as indicated in Figure

6-3.
Figure 6-3 NTR options for FX NT ISAM family
GPON GPON GPON

8 kHz GPON PHY
BITS backplane GPON
G.703
8 kHz GPON PHY
backplane GPON
Sync Eth
NT
GE PHY 8 kHz GPON PHY
backplane GPON
NTIO
8 kHz Sync Eth
Eth
IEEE1588
backplane GE PHY
GE
GPON
8 kHz GPON PHY
GE PHY backplane GPON
Sync Eth Sync Eth
BITS or Sync Eth
GE PHY
GE PHY GE PHY
NTIO
GPON
8 kHz GPON PHY
Hub ISAM Sync Eth Optional GE backplane GPON
GE PHY network
IEEE1588
NT
GPON
IEEE1588 8 kHz GPON PHY
GE
G.703
GE backplane GPON
8 kHz Sync Eth
Eth
NT
backplane GE PHY
Optional BITS Sync Eth
PDH/SDH G.703 GE PHY
NT
network
Outdoor ISAM
Collocated ISAM shelves
Note — For an overview of which NT boards and which LT boards

support the required synchronization functions, refer to the Product
Information document of your system and/or the Unit Data Sheet
(UDS) of that board.
Although not shown in these figures, deployments with a mix of nodes are also
possible from both figures. For example, a standalone REM connected via SyncE to
an Ethernet output on an Hub ISAM with NT from the FD 100/320Gbps NT family.
Note — The distributed REM requires a fiber connection per LT

board for the data transport. However, only the fiber to LT1 transports
the NTR signal, which is then distributed in the REM to both LT
boards. Hence, when that fiber link is broken, the NTR features
described in this chapter are not fully supported anymore for all lines
in that distributed REM.
6.2 ISAM clock system and NTR extraction
High level description of the external port selection for NTR

Figure 6-4 gives a high level description on how the external port is selected that will
be used for NTR extraction. This is valid for BITS and SyncE which both are linked
to physical ports.
An ISAM hardware configuration has a number of external ports RJ45-a, RJ45-b,
SFP-1,…, SFP-n, XFP-1,…, XFP-m available on NT-A, and possibly also on NT-B,
and NTIO, in case the latter are also present. Not every port can be used for
synchronization input. Hardware design of the specific ISAM boards determines
which ports can be used for SyncE input (some Ethernet ports) or BITS input (some
RJ45 ports), and this will form a subset of the total number of external ports (see
Figure 6-4).
Figure 6-4 Port selection for external NTR (SyncE and BITS)
External
ports on NT-A, Ports which
(NT-B and support
NTIO) synchronisation
input (BITS or
SyncE)
Static
selection of Dynamic
RJ45-a 2 ports for selection of
RJ45-b Static NTR input ISAM 1 port for
HW design RJ45-a configur- clock NTR Clock
SFP-1 of specific RJ45-b ation on system distribution
e
… card SFP-f ISAM T operation on ISAM
renc
… … backplane
=R
R ef e
SFP-n SFP-g U to LTs
XFP-r and then
XFP-1 ... to access lines
… XFP-s
…
XFP-m
The operator needs to configure which of these ports are valid inputs for NTR in his
network deployment. Maximum 2 ports can be configured for this (T and U in Figure
6-4).
Note — There is also the option of an IEEE1588 slave as a T/U clock
source. This is however not indicated on Figure 6-4.
The ISAM clock subsystem will then dynamically select one of these 2 ports as NTR
reference, according to the actual quality of the NTR signals on these ports, the
configured priority of these ports, and so on. According to the ITU Rec G.871 section
5.6 criteria and selection algorithm.
Possible External NTR sources

The ISAM supports the following external NTR clock sources:
• One BITS / SSU interface per NT faceplate:
This interface supports a 2.048 MHz plain clock signal, an E1 framed signal, or a
DS1 framed signal. For ETSI markets, the default expected input is an E1 framed
signal.
SSM is not supported on this interface.
BITS has been a very common way of clock distribution in PDH/SDH networks
for a long time, and is therefore available in many COs. Even after migration from
PDH/SDH networks to Metro Ethernet, it is still available in many cases for clock
distribution. Because Synchronous Ethernet requires new specific hardware not
yet available on first generations of Metro Ethernet networks, BITS is still an
important option for providing NTR to ISAMs in COs.
• One or more Synchronous Ethernet interfaces on the NT or NTIO faceplates:
This can be only supported on optical 1 GE, 2.5 GE and 10 GE interfaces, and not
at other speeds (for example, 100 Mbps), nor on any electrical interface.
SSM can be enabled on these interfaces.
Further network rationalization is the driver to move all functions to the Metro
Ethernet, so the PDH/SDH network becomes completely obsolete. Consequently,
over time, SyncE will become the more important solution for NTR. Since
SyncE-support requires specific hardware, upgrades of some nodes in the Metro
Ethernet network may be required.
• One or more PTP (also known as IEEE1588v2) clock sources:
This is a packet-based clock synchronization method using Ethernet packets.
Next to support for frequency synchronization this protocol also provides support
for time synchronization over a packet network. ISAM currently only supports
frequency synchronization.
Figure 6-1 and Figure 6-2 give a high-level view of the possible interfaces to external
NTR sources for both the FD 24Gbps NT family and the FD 100/320Gbps NT and
FX NT family, respectively. More detailed information on the actual capabilities of
specific boards is available in the Product Information document of your product
and/or the UDS. These documents also indicate which ports on these boards can be
used as external NTR sources (and which ones not).
Single NT clock operation

Figure 6-5 shows the NTR configuration with a single NT board, and with an NTIO
board added as a possible option. The internal system NTR clock can be
synchronized to any of the external NTR sources described in the previous
subsection: BITS, SyncE and IEEE1588.
Figure 6-5 ISAM configuration for NTR provisioning with single NT.
SFP
NT Front plate LT 1
1 GE Ethernet Sync Eth out
Sync Eth out µP
SFP
NT Front plate
1 / 10 GE SFP+
Sync Eth in
SFP
NTIO Front plate
1 GE Sync Eth out
SFP
LT 18
PHY
NTIO Front plate SFP Sync Eth out
1 GE Sync Eth in PHY
SFP PTP
NTR clock generation

Sync Eth out T4 : BITS/SSU
NTR clock source

IEEE
1 GE NTIO 1588 1 out
selection
T3 : BITS /SSU 1 in
T0 8 kHz
S
NTIO Front plate NTR 1 to
XFP E
LT 1 -18
10 GE Sync Eth in L TC/
Sync Eth out OC XO
XFP
10 GE NTIO Single NT
The 8 kHz NTR signal generated by the internal system NTR clock is distributed to
the subscriber interface logic on the LT boards.
Up to two ports can be configured as valid external NTR input ports (see “High level
description of the external port selection for NTR”). One will be the reference, and
the other one is for protection (see “Clock protection: Overview”).
If all available external NTR clock sources fail, then this clock will switch to
Hold-over mode, if locking to the external NTR clock source was completed at the
time of failure.
In case no valid external NTR clock source is connected during system start-up, the
internal NTR clock will remain in free-running mode, that is, it will adapt to the
output frequency of its local oscillator.
Clock protection: Overview

When applications are running on equipment connected to ISAM which require
NTR, it is important that this NTR signal is provided uninterrupted, and that
protection is available against degradation or failure of selected external NTR
sources. This is supported in the following ways:
• Switching to another redundant external NTR clock source, if available (see
“Clock protection: External NTR source protection”).
• An internal NTR clock hold-over function (see Figure 6-6), which continues to
apply the last known clock correction data to the internal NTR clock, in order to
keep the NTR clock to dependent equipment as stable as possible during absence
of external references.
• Switching to a second NT with identical NTR clock system when the active NT
fails (see “Clock protection: NT redundancy”)
Figure 6-6 States and state transitions for the internal NTR clock
AUTONOMOUS MODE
Holdover mode Free-run mode

- freeze holdover - rest holdover
memory memory
- lock clock to - free-run clock Configure autonomous mode
holdover memory
Valid reference
available No valid reference
No valid reference nor memory
nor memory Locked mode available
available
- update holdover FORCED FREE-RUN MODE
memory
- lock clock to
selected reference Free-run mode
- rest holdover
Configure forced memory
free-run mode - free-run clock
Clock protection: External NTR source protection

Up to two ports can be configured as valid external NTR input ports (see “High level
description of the external port selection for NTR”). One port will be the reference,
the other port is for protection. If the reference fails, then the other selected NTR
input port will be used for clock synchronization.
NTR clock source failure is detected from:
• Loss of Signal
• A signal frequency that falls outside the capture range of the internal system NTR
clock
• Failure to receive SSM messages on an SSM enabled Synchronous Ethernet link
during more than 5 seconds
• Reception of SSM messages with a QL value below the configured threshold
value.
• Not locked on PTP packet stream (IEEE1588)
Per external NTR source type, the following protection is supported:
• BITS input redundancy always requires 2 NT boards, since maximum one BITS
input interface is available on NT boards. If the reference BITS input fails, then
the BITS input on the other NT will be used as NTR, even if this other NT board
is in standby mode. The ISAM is in general hardware-ready to support this type
of BITS input redundancy, but up to this release, software support for this has
been implemented on NANT-A and NANT-D only. BITS input redundancy is not
supported on other NTs, but this will be planned in a future release.
• SyncE source redundancy is supported with all input ports either on one NT
board, or on one NT board and NTIO board.
• The PTP circuitry on the active NT can perform the Best Master Algorithm on 3
different, configured PTP Masters, but it can track only 1 of these actively. In
redundant configurations, the Master configuration is shared by both NT boards.
Due to above restrictions it is recommended to protect a PTP GM as source for
frequency synchronization by means of legacy sources like SSU / BITS and
SyncE. Resilience with respect to L2 connectivity can be guaranteed via the usual
means like LAG.
Furthermore, any mix is supported when both inputs are on the same NT, or on one
NT and NTIO. For example, BITS as the reference for NTR, while SyncE as NTR
source protection.
However, such combinations are expected to be less common in the field, since either
the long-existing BITS on the PDH/SDH network is used, or else this network has
been completely outphased and the network has moved fully to metro Ethernet
aggregation and uses SyncE.
Clock protection: NT redundancy

Also in ISAM configurations with NT redundancy, the NTR function should restore
and this to the same quality, when an NT fails and the redundant NT takes over. The
following restrictions have to be taken into account:
• In case SSU / BITS is applied, a valid signal has to be provided to both NT board
front plates. This will guarantee that the system NTR clock on the stand-by NT
board can be synchronized to the network in case the active NT board hardware
fails or is removed.
The BITS signal on the NT in stand-by mode cannot be monitored.
Note 1 — Although some NT' support active/active operation, this
only refers to the data plane, since the control plane is still
active/standby.
Note 2 — This configuration does not support redundancy of BITS
input (see previous subsection on external NTR sources), except for
NANT-A and NANT-D.
• In case NT redundancy needs to be provided with SyncE for NTR, the SyncE
input(s) should be connected to the NTIO board which has connections to both
NTs. In this way, also SyncE input redundancy can be supported.
• Although each NT has its own PTP circuitry only the active NT will be actively
tracking the PTP Grand Master in current SW release.
Once the redundant NT has taken over from the failing NT and has arrived in a stable
state, the NTR function will be compliant to the typical related standards. These
standards also define the maximum allowed phase jump during a transient effect.
Switch-over from a failing NT to a redundant NT is one of these transient effects, and
ISAM does exceed in that case the maximum allowed phase jump. Since such NT
switch-overs are exceptional, and since phase jumps may be filtered to some extent
by end-user equipment, the impact on services is expected to be limited.
Detailed behavior of internal system NTR

The operator can configure the following elements regarding NTR:
• The external NTR source(s) to be used:
• BITS/SSU
• Synchronous Ethernet interfaces
• IEEE1588
• Enabling and disabling of the reception of SSMs that carry a QL, on the one or
two external NTR clock sources that have been configured as nominated for
network synchronization purposes by the operator.
The default setting is “DISABLE”. For the BITS/SSU and IEEE1588 interface,
this setting cannot be changed
• The QL value applied for an external NTR clock source, in the algorithm that
performs the selection of one external NTR clock source from up to two
configured as nominated, and in case reception of SSM for that NTR clock source
is disabled.
The default setting for the value is equal to “QL-PRC” (code 0010b) for ETSI,
and “QL-PRS” (code point 0000b) for ANSI.
• The target QL value that is applied as minimum threshold for eligibility of an
external NTR clock source, in the algorithm that performs the selection of one
external NTR clock source from up to two configured as nominated, and in case
reception of SSM for that NTR clock source is enabled.
The default setting for the value is equal to “QL- DNU” (code 1111b).
• The static relative priority to be applied for an external NTR clock source, in the
algorithm that performs the selection of one external NTR clock source from up
to two configured as nominated, in case the respective Quality Levels (QL) of the
two sources are identical. The QL for each of both NTR clock sources can be
either communicated via the Synchronization status Messages, or is fixed to a
default value.
• Revertive or non-revertive operation of the external NTR clock signal selection.
The default setting is “Revertive mode”
• Override of synchronization to any external NTR clock source, and forcing of
free-running or hold-over mode for the internal NTR clock function.
• The target QL to be applied as minimum threshold for the internal system NTR
clock, for generating an SSU / BITS out signal.
The default setting for this target QL value is equal to “QL- DNU” (code 1111b).
The system performs the following autonomous NTR clock management functions:
• Monitoring of the signal status (signal present, frequency within the capture
range) and the QL of up to two external NTR clock sources that are configured
by the operator as nominated.
• Selection of the external NTR clock source that fits best the selection criteria,
from up to two sources configured as nominated. Selection happens as specified
further.
• Disabling of the SSU / BITS output signal(s) in case the QL, which can be
attributed to the internal system NTR clock, drops below the configured
threshold.
The operator can retrieve the following information:

• The status of BITS / SSU, Synchronous Ethernet and/ or IEEE1588 interfaces
nominated as external NTR source(s): “not available”, “available but not used”,
“used”.
• The number of switch-over actions between nominated external NTR clock
sources. In revertive mode, switch-over between nominated external NTR clock
sources may happen without further alarm generation.
The operator can receive the following alarms

• Unavailability of any nominated external NTR clock source for reasons that
include:
• Frequency out of range
• Loss of Signal
• Time-out for SSM reception, if enabled
• Received SSM-QL below the target QL, default or configured
• Not locked on PTP packet stream (IEEE1588)
• Unavailability as described above of all nominated external NTR clock sources,
with defaulting to hold-over mode for the internal NTR clock
• BITS output signal disabled
• Internal system NTR clock QL drops below the output threshold QL, default or
configured.
In the default NTR switching mode (revertive mode), the ISAM selects the most
appropriate NTR clock source for synchronizing its output NTR signals, and for
protecting against failure of external NTR clock sources, as follows:
• In case two external NTR clock sources have been configured by the operator as
nominated, and both are active, then selection of the external NTR clock source,
to which the internal system NTR clock will synchronize, is subject to the
following rules:
• The external NTR clock with highest Quality Level (QL), is selected as actual
reference for the internal NTR clock. The QL of an external NTR clock source is
communicated by means of SSM messages received on the interface related to the
source. If SSM reception is not supported, or disabled on that interface, then a QL
value configured by the operator, or a default QL value is applied, as described
above.
• In case both external NTR clock sources exhibit the same QL, then their relative
priority is determined by the external NTR clock source priority list as configured
by the operator.
• After restoration or upgrading of an external NTR clock source, the selection
depends on revertive or non-revertive mode setting, as configured by the
operator.
• In case only one external NTR clock source has been configured by the operator
as nominated, or in case only one is active, then the internal system NTR clock
will switch to hold-over mode when this external NTR clock source fails, or is
removed.
In hold-over mode, the internal system NTR clock maintains application of the
last stored correction values which describe the deviation of the own free-running
oscillator signal relative to the external NTR clock source signal which was
applied last.
NTR management
Configuration: external NTR clock source priority list

This command allows the operator to configure two NTR clock sources, with an
operator assigned priority between them, as nominated references for the internal
system NTR clock. Each of these two sources can be independently designated to be:
• The BITS interface on the faceplate of an NT board.
• The 1GE /10GE interface on the faceplate of an NT board.
• One of the two dedicated 1GE interfaces on the faceplate of a 1GE NTIO board.
• The IEEE1588 interface receiving PTP messages from Master(s) over any
external interface.
The system factory default is “none”: no external clocks are selected. In this case the
system automatically selects the internal free-run system NTR clock for downstream
NTR timing.
Configuration: SSU/BITS input interface(s)

This command allows the operator to configure the BITS mode of the external clock
source to E1, DS1, 2048KHz or auto-select. The BITS mode applies for the system,
that is, any configured BITS clock source.
The system factory default is “auto-select”. In this case, the system automatically
selects E1 for the system with the NT capabilities for clock device type of E1, or DS1
for clock device type of T1. This setting can be viewed in the clock status command.
When the BITS mode is configured to “auto-select”, the actual BITS mode will
display “E1” or “DS1” depending on the NT capabilities.
However, the system does not restrict the manual configuration of “DS1” or “E1” to
a specific NT capability of the clock device type.
Configuration: Synchronous Ethernet input interface(s)

This command allows the operator to configure the Ethernet interface(s) which can
provide their extracted data clock as external NTR clock source. As mentioned
above, 1 or 2 external NTR sources can be configured as clocks for synchronizing
the internal system NTR clock too. Therefore, between 0 and 2 synchronous Ethernet
links can be designated as external NTR clock sources.
The selected Ethernet interface(s) is (are) identified by means of:
• The board slot: NT-A, NT-B, NTIO slot, or none
• The port type: SFP, XFP or none
• The port number on the board: depends on SyncE port supported, or none
The system factory default is “none”.
Configuration: IEEE1588
The following needs to be configured for IEEE1588:
• The IEEE1588 interface as well as the external interface on which PTP messages
will be received have to be attached to a L2 forwarder.
• Host IP address of the IEEE1588 slave and gateway IP address + mask
• Host IP address and priority of acceptable Master(s) from which PTP messages
will be received and used as external NTR clock source.
• IEEE1588 protocol specific parameters (PTP Domain and mode)
Configuration: NTR Switching Mode

This command allows the operator to configure the external NTR selection mode to
be either:
• Revertive:
the system NTR clock always selects as reference the external NTR clock source
with highest QL, or the one configured as preferred by the operator if the QLs of
both nominated external NTR clock sources are equal, whenever this clock
source is available.
• Non-revertive:
the system NTR clock keeps the currently selected external NTR clock source as
a reference, until it is no longer available for selection, for reasons listed above,
or until it is disabled by the operator. This is the case even if another external NTR
clock source, with better QL or higher preference as configured by the operator,
has become available since the selection of the currently selected external NTR
clock source.
The system factory default is “revertive”
Configuration: enabling of Synchronization Status Messaging (SSM)

Synchronization Status Messages (SSM) are required to allow the downstream
element that requires synchronization to know the quality of the upstream clock.
Typically, it allows a downstream element which has the choice between different
upstream clocks to select the clock with the best quality, or the clock which meets
the minimum required quality.
Even when there is only one upstream clock available (for example, in the case of a
mobile base station connected to a DSL line), SSM has value. If SSM indicates that
the quality of the upstream clock degrades below the quality of the local clock of the
base station, the latter can switch to the local clock for synchronization.
More information about SSM can be found in G.781 with extensions for
Synchronous Ethernet in G.8264.
Several commands allow an operator to enable or disable the support of the

Synchronization Status Message (SSM):
• the handling of received SSM messages on ports configured as NTR clock
source(s) can be enabled or disabled
• the transmission of SSM messages per port can be enabled or disabled, and this
for the following cases:
• Synchronous Ethernet output ports on NT cards, NTIO cards and NELT-B
• VDSL2 ports and SHDSL ports on some LT boards (only for SSM transmission, not
for SSM reception; and this feature is only supported in EFM mode and not in ATM
mode)
The system factory default is “disable”

SSM is not supported for BITS-A, BITS-B and IEEE1588.
Configuration: forcing selection of the internal system NTR clock

This command allows the operator to force the transmitted downstream NTR clock
to be synchronous to the internal system NTR clock, without synchronization to any
external NTR clock source. The internal NTR clock can be in free-running, or in
hold-over mode, when it was synchronized previously to an external NTR clock
source.
Status: nominated NTR clock status

This command allows the operator to query the status of the NTR clock source(s).
The following command results are listed:
• the NTR clock source: BITS-A, BITS-B, Sync Eth 1, Sync Eth 2, IEEE1588,
local
• the Quality Level (QL) of the source: code points 0000b - 1111b (0 … 15)
• the operator configured priority of the source: 1 … 3
• The operational status of the source:
• REFERENCE: the clock source is selected as the reference clock.
• VALID: the clock source is available for selection
• FAILED: the clock source failed or is not available for selection
• DO_NOT_USE: the clock must not be used as indicated by SSM (or time-out)
• UNKNOWN: the clock status is unknown (start-up, system fault)
• FORCED: the clock is manually selected
• NO_SYNCE_CONFIG: the synchronization source is not bound to a physical port.
• NO_SYNCE_SUPPORT: the syncE clock is bound to a port that does not support
syncE clock extraction.
• ON_PEERNT_NOT_READY: the clock is configured on the faceplate of a peer NT
that is not ready to participate in clock management.
• SYNCE_NOT_AVAILABLE: the syncE clock is not available because the required
equipment is not available.
• MISSING: No SSM packets received for 5 seconds
• INVALID: Incoming signal is valid on the hardware level, but the source is rejected
for quality reasons (below target QL)
6.3 Downstream NTR clock distribution
In the introduction of this chapter the drivers for NTR where explained, and include
distribution of NTR to other network nodes, as well as distribution of NTR over
access lines to the end-user or business user.
Figure 6-7 NTR distribution over access lines for different services
Mobile backhauling
ISAM Accurate synchronization
of base stations
Network Timing Reference
High-stability
clock on NT Leased lines
Network Timing Reference
Cost-effective central
BITS interface clock for synchronization
on NT of all CPEs
NTR support
Voice
on LTs
High-stability clock for
long-lasting fax and
modem calls
The typical options provided for delivering NTR to other network nodes are:
• BITS out on some NT boards
• SyncE out on some Ethernet interfaces on some NT, NTIO and Ethernet LT
boards.
This can be supported on optical Ethernet interfaces only, and not on electrical
ones. Secondly, it can be supported at speeds of 1 Gbps, 2.5 Gbps and 10 Gbps,
but not at for example, 100 Mbps.
In the normal default case, the BITS out on the NT board is filtered by the SETG
function (see Annex 7 in G.8262/G8264) in order to achieve compliance to G.813
option 1 for BITS out. But alternative configurations of the ISAM clock system are
possible as suggested in Annex7 in G.8262/G8264, allowing that the SyncE input(s)
are passed through unfiltered to the BITS output. Typically the unfiltered BITS
output will then be connected to an SSU device.
The typical options provided for delivering NTR to access lines or end-users are:
• NTR on VDSL2
• NTR on ADSL/ADSL2/ADSL2+ is not supported
• NTR on SHDSL
• SyncE out on some Ethernet interfaces on some NT, NTIO and Ethernet LT
boards.
This can be supported on optical Ethernet interfaces only, and not on electrical
ones. Secondly, it can be supported at speeds of 1 Gbps, 2.5 Gbps and 10 Gbps,
but not at for example, 100 Mbps.
To know which specific NT, NTIO, or LT boards do support the above NTR
distribution on their outgoing interfaces, refer to the Product Information document
and/or the UDS. A high-level view of the capabilities of the 24Gbps FD NT, the
100Gbps /320Gbps FD NT and the FX NT family is represented in Figure 6-1, Figure
6-2 and Figure 6-3 respectively.
6.4 Applicable standards
• Output NTR clock support on ADSL(2)(plus) lines: The NTR section in ITU Rec
G.992.1 / G.992.3 / G.992.5 is not supported. NTR for ADSL is not supported.
• Output NTR clock support on SHDSL lines: ITU Rec G.991.2
NTR for SHDSL is supported on selected ISAM SHDSL Line Termination board
types.
• Output NTR clock support on VDSL2 lines: ITU Rec G.993.2
NTR for VDSL is supported on selected ISAM VDSL Line Termination board
types.
• Output NTR clock support on POTS lines: Not Applicable
An analogue POTS interface does not provide a clock signal in downstream
direction
• Output NTR clock support on Synchronous Ethernet lines: ITU Rec
G.8261/Y.1361
NTR by means of Synchronous Ethernet is supported on selected ISAM Ethernet
Line Termination board types.
• Output NTR clock quality on ISAM NT:
• Output NTR clock free running accuracy, hold-over frequency accuracy, Jitter and
wander generation, phase variation in case of interruptions on synchronization input
signals:
- ETSI SSU: ITU-T G.813 Option 1 (Note: As explained above, ISAM is not fully
compliant in case of transient behavior.)
- ETSI Synchronous Ethernet: ITU-T G.8262 Option 1
• Output NTR clock jitter and wander transfer
- ETSI SSU: ITU-T G.813 Option 1
• Input external NTR clock source quality on ISAM NT
• Input NTR signal clock pull-in & pull-out ranges:
- ETSI SSU: ITU-T G.813 Option 1
• Input NTR signal jitter and wander tolerance:
- ETSI SSU: ITU-T G. 813 Option 1, G.823
- ETSI/ANSI PTP: ITU-T G.8261 (note: PDVs indirectly specified by means of
network topologies and traffic models)
• NTR management, including SSM: ITU-T G.781 Option 1 to a large extent
• SSM transport
• BITS / SSU: ITU-T G.704 (1998)
ISAM does not support SSM reception or generation on BITS / SSU interfaces.
• Synchronous Ethernet: IEEE 802.3 Organization Specific Slow Protocol (OSSP)
Annex 43B (2005), ITU-T G.8264
7— xDSL features
7.1 Overview 7-2
7.2 Configurable impulse noise protection 7-3
7.3 RFI Notching 7-4
7.4 Low-power modes 7-4
7.5 Seamless rate adaptation 7-6
7.6 Upstream power back-off 7-8
7.7 Downstream power back-off 7-9
7.8 Impulse noise monitor 7-10
7.9 Virtual noise 7-11
7.10 Artificial noise 7-12
7.11 Physical Layer Retransmission (RTX) 7-13
7.12 Per-line configuration overrule 7-14
7.13 Configurable US/ DS memory split 7-15
7.14 Vectoring 7-15
7.15 Fall-back configuration for vectoring 7-17
7 — xDSL features
7.1 Overview
Table 7-1 lists the different features described in this chapter, indicating for which
xDSL mode the feature is supported on xDSL LT boards.
Table 7-1 Supported xDSL features
Feature XDSL LT
ADSL ADSL2 ADSL2+ READSL2 VDSL2
Configurable impulse noise protection X X X X X
RFI Notching X X
Low-power modes X X X X X
L2 low-power mode X X X
L3 idle mode X X X X X
Seamless rate adaptation X X X X
Upstream power back-off X X X X
UPBO policing X
Equal RXPSD UPBO X
Equal FEXT UPBO X
Downstream power back-off X X X X X

Impulse noise monitor X
Virtual noise X
Artificial noise X X X X
Physical Layer Retransmission (RTX) X X X X
Per-line configuration overrule X X X X X
Configurable US/ DS memory split X
Vectoring X
Fall-back configuration for vectoring X
Table 7-2 gives an overview of the supported VDSL2 profiles. Each profile defines
normative values for a set of parameters, as defined by G.993.2.
Table 7-2 Supported VDSL2 profiles
VDSL2 Profile xDSL LT
8a, 8b, 8c, 8d X
12a, 12b X
17a X
7 — xDSL features
Table 7-3 gives an overview of the supported VDSL2 bandplans. A bandplan is a

partitioning of the frequency spectrum into non-overlapping frequency bands, each
of which is allocated for either upstream or downstream transmission.
Table 7-3 Supported VDSL2 bandplans
VDSL2 Bandplan xDSL LT
Region A(1) 998 X
Region B(2) 998 X
Region B 998E X
Region B 998ADE X
Region B 997 X
Region B 997E X
Notes
(1) Region A = North America
(2) Region B = Europe
7.2 Configurable impulse noise protection
Standards specify that a DSL link must comply with a Bit Error Ratio (BER) < 10-7,
in the presence of a Signal-to-Noise Ratio (SNR) margin of 6 dB. For some types of
service (for example IPTV, when using codecs with insufficient error concealing),
subscriber comfort requires even higher line quality, that is, BER < 10-10 or better.
DSL modems can be trained at initialization to achieve these quality levels in the
presence of the stationary background noise.
Impulse Noise Protection (INP) is the ability to protect the transmission against
impulse noises. These impulse noises differ from the stationary noise in the sense
that they are transitory noises and that their power levels are high enough to be able
to cause data errors on the xDSL lines. INP is important in the IPTV network. With
the general evolution from pure High-Speed Internet (HSI) to triple play service
offering, there is an increasing need for techniques that help to improve and assure
the stability of the DSL line.
Configuring INP provides the ability to configure the upstream and downstream
minimum INP parameters in the service profile.
The standards include several provisions to reduce the number of errors that occur
due to impulse noise. The primary one is interleaving combined with Forward Error
Correction (FEC) using Reed-Solomon (RS) error correcting codes.
Reed-Solomon
Reed-Solomon (RS) adds extra bytes to a group of data bytes when it is sent. These
bytes are also known as the “RS word”. When data corruption is detected at
reception, the RS decoder is able to use the extra bytes to locate the errors and to
recover the original message. However, this only is effective up to a certain
maximum number of errored bytes. In order to correct impulse noise errors, RS needs
to be combined with interleaving.
7 — xDSL features
Interleaving
Instead of transmitting the RS words directly on the line, the different RS words are
first mixed and spread over time. This process is called “interleaving”. This has the
advantage that when a burst of errors occurs on the line, it will hit bytes of different
RS words. After reconstruction of the original RS words (by the de-interleaver), the
errors will be spread over multiple RS words, such that each RS word is only affected
by a small amount of errors and is therefore much easier to correct. The RS word can
be corrected if its number of errors is within the RS correction boundaries.
The main disadvantage of interleaving is an extra “interleaving delay”. Constructing
the blocks that will finally be transmitted over the line takes time, as the modems
have to wait for a while before they can actually start transmitting. At the receiving
side, it also costs extra time to reconstruct the original RS word. The first original RS
word cannot be reconstructed before all of its bytes have been received.
Using smaller interleaving depths, that is, by taking bigger chunks of the original RS
words, can lead to a lower interleaving delay. This has the disadvantage that errors
will be spread over less RS words on the receiving side, with the possibility that they
cannot be corrected.
In the case that a high INP together with a low delay is required, extra RS bytes will
have to be added to increase the RS correction capability. This however can lead to
reduced bit rates.
It becomes clear from the above that when configuring the INP, a trade-off has to be
made between:
• robustness of the line against impulse noise
• interleaving delay
• achievable bit rate
7.3 RFI Notching
Radio Frequency Interference (RFI) notching is used to alleviate signal interference

in certain frequency bands. VDSL2 and ADSL2Plus provide the capability to reduce
the Power Spectral Density (PSD) within certain frequency bands and thus notch the
PSD in areas to reduce egress into certain services such as HAM radio. HAM radio
is an Amateur Radio service enjoyed by radio enthusiasts. Shortwave radio can
broadcast over long distances aided by relay signals.
7.4 Low-power modes
L2 low-power mode
First-generation ADSL transceivers operate in full-power mode day and night, even
when not in use. With several millions of deployed ADSL modems, a significant
amount of electricity can be saved if the modems engage in a stand-by mode or sleep
mode just like computers. This would also save power for ADSL transceivers
operating in small remote units and Digital Loop Carrier (DLC) cabinets that operate
under very strict heat dissipation requirements.
7 — xDSL features
To address these concerns, the ADSL2/ADSL2+ standards define two L2 low-power

management modes in addition to the full power mode (called “L0” power mode).
These power management modes help reduce the overall power consumption while
maintaining the ADSL “always-on” functionality for the subscriber.
The L2 low-power mode enables statistical powers savings at the ADSL transceiver
unit in the central office (ATU-C) by entering and exiting low power mode based on
the downstream subscriber traffic running over the ADSL connection.
By enabling the L2 low-power mode, the average power consumption and
dissipation of a line is reduced because the modem reduces dynamically the
downstream transmit Power Spectral Density (PSD) in case there is no subscriber
data to transmit in the downstream direction. A low-rate connection is however
always assured for minimum keep-alive data. The DSL line automatically returns to
the full PSD/full data rate if downstream subscriber data arrives in the DSLAM,
without loss of data.
In the L2 mode, only the downstream data rate is lowered. The data rate of the
upstream remains unchanged. This because in ADSLx the downstream transmitter
constitutes a much larger consumer of power than the upstream transmitter.
The L2 entry and exit mechanisms and resulting data rate adaptations are
accomplished without any service interruption or even a single bit error, and as such,
are not noticed by the subscriber.
However, L2 low-power modes will lead to time varying crosstalk which might
impact the stability of customers sharing the same binder.
Exit out of L2 mode into L0 mode can also be triggered from the CPE end, in case
of significantly changed channel conditions.
L3 idle mode
This mode enables overall power savings at both the XTU-C and the remote xDSL
transceiver unit (XTU-R) by entering into sleep/stand-by mode when the connection
is not being used for extended periods of time (that is, subscriber asleep, modem
asleep).
The L3 power mode is a total sleep mode where no traffic can be communicated over
the xDSL connection. When the subscriber goes back on-line, the line has to be
re-initialized to enter the L0 state again.
The modem can enter the L3 state upon guided power removal (L3 Request exchange
between xTU-R and xTU-C, also known as orderly shutdown), power loss or
persistent link failures during Showtime (also known as disorderly shutdown).
During the L3 state, power savings at the XTU-C are realized independent of the
used ADSLx or VDSL2 mode by putting certain Analog Front End (AFE) blocks and
line drivers in power down mode. This power saving mechanism is also available in
case no xTU-R is attached but the ports are in “listening mode” and configured in
admin-up.
Figure 7-1 illustrates the L2/L3 power modes.
7 — xDSL features
Figure 7-1 L2/L3 power modes

Initialization Low traffic causes switch to L2
Showtime
Resynchronisation or (L0) High traffic causes
L3 Power mode switchback to L0
Resynchronisation or “Low Power”

“Low Power”
IDLE (L3) L3 Power mode
Showtime (L2)
Showtime (L2)
7.5 Seamless rate adaptation
ITU-T G.997.1 defines 3 types of Rate Adaptation (RA) modes:

• RA Mode 1 (Operator Controlled):
Bit rate is configured by operator, no rate adaptation
• RA Mode 2 (Rate adaptive at startup):
At startup, the bit rate is selected between a configured minimum and a
configured maximum. The actual bit rate remains fixed while the modem is in
showtime.
• RA Mode 3 (Dynamic rate adaptive):
The bit rate dynamically changes between a configured minimum and a
configured maximum, even while the modem is in showtime.
The dynamic rate adaptive mode is also called “Seamless Rate Adaptation” (SRA).
This feature is supported in all ADSL2x (ADSL2, ADSL2+, READSL2) modes of
operation and in VDSL2 mode of operation.
SRA improves the stability of the line (that is, reduces the number of spontaneous
retrains) by dynamically reducing the bit rate, without loss of data and without bit
errors, in case of a slow decrease of the SNR to an SNR below a preset value. SRA
can also assure that at any moment in time the line operates at the maximum
achievable bit rate by dynamically increasing the bit rate, without loss of data and
without bit errors, in case the SNR increases above a preset value.
SRA enables the modem to change the data rate of the connection while in operation
without any service interruption. The modem detects changes in the channel
conditions (for example, increase in noise level) and adapts the data rate to the new
channel condition without a need to resynchronize the line.
The upshift and downshift noise margin thresholds and time intervals for SRA are
configurable.
Figure 7-2 illustrates SRA.
7 — xDSL features
Figure 7-2 Seamless Rate Adaptation

Maximum Noise Margin
Increase data rate if Upshift
time interval has elapsed
Upshift Noise Margin Increase
data rate
Target Noise Margin
Downshift Noise Margin Decrease

Decrease data rate if Downshift data rate
time interval has elapsed
Minimum Noise Margin
0 dB Margin
The upshift and downshift rate adaptation events due to SRA are counted in
15-minute and 24-hour Performance Monitoring (PM) intervals.
SRA can encounter upshift and downshift limitations on lines activated with
interleaving:
• ADSL2(+):
The SRA protocol can only change parameter L (number of bits per DMT
symbol).
SRA downshifts are limited by the configured maximum interleaving delay as
SRA downshift results in an increase of the delay.
SRA upshifts are limited by the configured minimum impulse noise protection as
SRA upshift results in a decrease of the impulse noise protection.
• VDSL2:
The SRA protocol can change both parameter L (number of bits per DMT
symbol) and D (interleaving depth). This allows to keep the delay and impulse
noise protection constant after a rate adapation. When all allocated interleaving
memory is used, upshift rate adaptations are still limited by the configured
minimum impulse noise protection.
7 — xDSL features
7.6 Upstream power back-off
Upstream Power Back-off (UPBO) is a remedy to the upstream far-end cross-talk

(FEXT) problem, see Figure 7-3.
Figure 7-3 Far end cross-talk
NE
CPE
short loop
FEXT CPE
long loop
weak Rx signal; strong FEXT signal from short loop
It allows to reduce the upstream transmit PSD on short lines in order not to impact
the upstream performance on longer lines unreasonably. Without UPBO, the nearby
CPE would transmit at full power and would inject excessive FEXT in the upstream
receiver of the long line.
UPBO policing
The main purpose of VDSL2 UPBO policing is to avoid the usage of a CPE not
complying with the UPBO configuration. When the CO modem detects such a
non-compliant CPE, an alarm is raised and optionally the line is automatically
shutdown. The expected behavior is configurable.
A line that has been automatically shut down because of policing can be triggered to
re-initialize by toggling its administrative state (down/up).
Equal RXPSD UPBO

This is the form of UPBO first standardized in G.993.2. The goal of this UPBO is to
equalize the upstream received signal PSD. The support of this form of UPBO is
mandatory at both DSLAM and CPE.
Equal FEXT UPBO

The goal of this second form of UPBO is to equalize the level of FEXT VDSL2
self-crosstalk noise. This results in available upstream bitrates that are further
optimized compared to the bitrates obtained with Equal RXPSD UPBO.
This form of UPBO is introduced because the equal RXPSD UPBO does not exactly
equalize the impact of all lines to each other, but gives a different FEXT level impact
proportional to the loop length, i.e. the short lines give a lower FEXT impact to long
lines then vice versa. As a consequence, the equal RXPSD UPBO is actually
implying too much power cutback on the short lines.
7 — xDSL features
The Equal FEXT UPBO can be explained as first applying the equal RXPSD method
but adding a loop-length-dependent delta FEXT factor, thereby equalizing the
impact among the lines. This equalization is executed with respect to a reference
FEXT level, characterized by a reference electrical length (kl0_ref). This parameter
is configurable for each upstream band. Alternatively an automatic configuration
mode is available: if the Equal FEXT parameters for all bands are all set to automatic,
the modem uses a dedicated mechanism to automatically calculate good values for
the Equal FEXT parameters, without manual configuration by the operator.
The equal FEXT UPBO method is standardized in G.993.2 Amendment 2, and is
supported in the ISAM.
7.7 Downstream power back-off
With the introduction of remote cabinets, one can have deployment of DSL lines
from different locations: some from the central office (CO), some from the remote
terminals (RT). In case lines deployed from the CO and lines deployed from the RT
share the same cable binder, a near-far crosstalk problem occurs.
The crosstalk from the near-end disturbers can be much higher than before, such that
the signal from the far-end transmitter is completely degraded. Very often this results
in a loss of the service on the line deployed from the CO.
This near-far effect both occurs in upstream and in downstream direction. In
upstream direction however, the typical services from the CO (ADSL2/2+) only use
lower frequencies, where the coupling is much lower than on higher frequencies.
That is why this problem mainly affects downstream communication (for the CO
lines).
In order to give equal priority both to CO and RT, the RT applies downstream power
reduction (also called Downstream Power Back-Off (DPBO)) on the frequencies that
it has in common with the lines from the CO. As such, the lines from the CO can be
protected, and also the RT can still have a decent bit rate on those overlapping
frequencies. See Figure 7-4.
Figure 7-4 Crosstalk in mixed CO-RT deployment

PSD
Remote Terminal Customer Premises

frequency
Central Office
RT NT
CO NT
PSD
Remote Terminal
PSD
PSD
frequency frequency
Initially, it was only possible to configure downstream PSD shaping by configuration

of a PSD Mask using a list of breakpoints, as part of the xDSL spectrum profile.
7 — xDSL features
Although such a list of breakpoints allows for a high degree of flexibility, it lacks
user friendliness. Within ITU-T, the so-called E-side Model for Downstream PSD
Shaping has been defined, which provides several high-level parameters that are
used to configure the PSD shape at the RT.
The E-side parameters are configurable via a special DPBO profile, which can be
assigned either to an xDSL LT board or to an xDSL port.
Since DPBO PSD shapes can be configured in several ways, a number of priority
rules apply:
• The DPBO profile parameters take precedence upon the downstream PSD shape
configured via the xDSL spectrum profile.
• The DPBO profile parameters configured at LT board level apply, unless
port-specific DPBO parameters are configured as well.
The DPBO profile parameters apply to ADSL1, ADSL2, ADSL2+ and VDSL2.
Shaped DPBO is not defined in the ADSL1 (G.992.1) and ADSL2 (G.992.3)
standards. However, if ADSL1 or ADSL2 are deployed from a remote location (for
example, from a remote VDSL2 LT board), the ADSL1 or ADSL2 downstream PSD
needs to be shaped for ensuring spectral compatibility with CO deployed xDSL.
7.8 Impulse noise monitor
The Impulse Noise Monitor (INM) collects data characterizing the impulse noise on
a particular line. This data can eventually be used to optimize the line configuration
for triple play (for example, minimum INP and maximum delay).
An impulse noise measurement can be started or stopped on a particular line for the
upstream direction, for the downstream direction, or for both. The upstream
measurements are performed by the XTU-C (CO side) and the downstream
measurements are performed by the XTU-R (CPE side), as illustrated in Figure 7-5.
The collected data is eventually represented as a set of impulse noise histograms,
both for the 15 minute and 24 hour PM intervals:
• Impulse Noise Inter arrival time histogram
• Impulse Noise Equivalent INP histogram
Figure 7-5 Impulse Noise Monitor in XTU-R and XTU-C

US xTU-C
INM PM
Impulse Noise INM Anomaly
counters
Sensor Counters 15min and 24h
Indication of xTU-R
Severely
Degraded Data DS
Symbols
EOC INM PM
Impulse Noise anomalies INM Anomaly
counters
Sensor Counters 15min and 24h
Impulse noise measurements can be performed without service interruption.
7 — xDSL features
7.9 Virtual noise
By configuring virtual noise, it is possible to minimize the impact of time varying

crosstalk on the stability of a DSL line. Virtual noise is an operator specified noise
PSD, using a piecewise linear model with breakpoints and a special SNRM mode. It
can be configured as a transmitter-referred noise PSD (TxRefVN, supported for
downstream and upstream) or as a receiver-referred noise PSD (RxRefVN,
supported for upstream only).
The transmitter-referred virtual noise PSD (TxRefVN) is converted by the receiver
to a receiver virtual noise PSD. The receiver determines its bitloading based on the
maximum of the received virtual noise and the received real noise. For a given
transmit signal PSD, the definition of a transmit virtual noise PSD can also be seen
as equivalent with setting a limit to the SNR that can be used by the receiver in the
bitloading process.
In downstream, when protecting a fixed data rate for all lines against VDSL2 self
FEXT crosstalk, the VN configuration is loop length independent. For more
elaborate cases, the TxRefVN can be configured using a limited set of profiles (for
example, to cover data rate with the loop length dependency, non FEXT noise, and
so on).
Transmitter referred virtual noise can also be used with a single or a limited set of
profiles in upstream if no UPBO is enabled.
When UPBO is enabled or in the presence of other noise (non FEXT), the TxRefVN
becomes highly loop length dependent. To cope with this loop length dependency,
the per line overrule mechanism can be used. In case the operator does not wish to
use a per line management, an alternative for upstream (where UPBO is applied) is
to use the receiver referred virtual noise (RxRefVN) configuration option that can
be configured with a unique VN profile setting independently of the loop length.
As indicated in Figure 7-6, during initialization, the DSLAM forwards the virtual
noise downstream (DS) breakpoints to the CPE. The CPE calculates the DS virtual
noise based on the DS loop attenuation and takes the maximum of this virtual noise
and the actual received DS noise. The DSLAM does the same in upstream (US)
direction, based on the received US noise, the US virtual noise and the US loop
attenuation (in case of TxREFVN).
Transmitter-referred virtual noise is included in the VDSL2 standard (G.993.2) as an
optional feature. The upstream receiver-referred virtual noise solution is not
standardized but does not pose any interoperability issue.
7 — xDSL features
Figure 7-6 Virtual noise concept
Loop attenuation
VN Breakpoints
DS/US
VDSL2
[Loop
attenuation]
CPE
DSLAM Received Received

Noise US Noise DS
7.10 Artificial noise
Since ADSL is widely deployed, changing the standard to support virtual noise is not
an effective solution. To overcome this limitation, for ADSL lines the ISAM has the
ability to physically inject additional noise on the line, that is, artificial noise, as
shown in Figure 7-7. This injection is executed during initialization as well as during
showtime.
The artificial noise behaves similar as the transmitter referred virtual noise in the
sense that it improves the stability and limits the SNR. The breakpoints also define
the noise at the transmit side and this noise and the transmit signal are attenuated by
the loop. The difference with virtual noise is that the CPE will see the power
summation of the attenuated artificial noise and the normal received noise. Artificial
noise is only implemented in downstream, and it can be used on top of any ADSL
flavor.
Figure 7-7 Artificial noise concept

ADSL
Artificial noise DS
+
Loop
CPE
Received
DSLAM Noise DS
7 — xDSL features
7.11 Physical Layer Retransmission (RTX)
The Bit Error Rate (BER) requirements for providing High Speed Internet (HSI)
service are not too stringent. Transmission errors on the line are effectively hidden
by retransmissions at the TCP-IP layer. With the evolution towards IPTV, much
lower BER figures are required.
Impulse noise is the common cause for errors on the DSL line. Two types of impulse
noise are defined:
• Single High Impulse Noise Environment (SHINE): impulse noise occurring at
random time instants
• Repetitive Electrical Impulse Noise (REIN): periodic impulse noise, occurring at
near equidistant time instants
Forward Error Correction (FEC) is the traditional error correction technique to deal
with impulse noise, as defined in the ADSL, ADSL2(Plus) and VDSL2 standards.
FEC is very well suited to protect against REIN, but due to the fixed overhead, FEC
is not very efficient to protect against SHINE.
An alternative technique for impulse noise protection is to use retransmission.
Because there is no fixed overhead, retransmission is best suited to protect against
SHINE. Retransmission is available at the higher layers (TCP-IP retransmission for
HSI, End-to-end retransmission for video), but is now also defined for the DSL
physical layer.
ITU-T recommendation G.998.4 (G.inp) specifies techniques beyond those defined
in the existing DSL recommendations to provide enhanced protection against
impulse noise or to increase the efficiency of providing impulse noise protection.
Both REIN and SHINE are handled efficiently on the DSL physical layer.
G.998.4 defines downstream retransmission both for VDSL2 mode and
ADSL2(Plus) mode. Support of retransmission in upstream is optional and only
defined for VDSL2 mode.
The concept of DSL physical layer retransmission is illustrated in Figure 7-8:
• The transmitter groups user data in Data Transfer Units (DTUs) and adds a Cyclic
Redundancy Check (CRC) and a sequence number.
• The receiver uses the CRC to detect errors and requests a retransmission of a DTU
when in error.
Figure 7-8 DSL physical layer retransmission concept
??
DTU CPE

DTU
DSLAM
7 — xDSL features
The configuration parameters for retransmission are defined within a separate RTX
profile. The RTX profile is optional when configuring an xDSL port. If no RTX
profile is assigned, retransmission will be disabled.
A specific set of Performance Monitoring (PM) parameters is defined, monitoring
the quality of the line when retransmission is enabled.
7.12 Per-line configuration overrule
The configuration parameters for xDSL lines are provisioned by means of profiles.
Typically, the same configuration profile is used on multiple lines that share similar
line characteristics and offer the same type of service. If some deviation is required
for the configuration of a particular line, then a completely new profile has to be
assigned to this line.
The per-line configuration overrule feature allows to overrule part of the xDSL
configuration parameters on a per-line basis, as shown in Figure 7-9.
Figure 7-9 Per-line configuration overrule
XDSL Profiles
Parameter 1
Parameter 2 Actual
configuration
… Parameter 3
… Parameter 1
Parameter N
Parameter 2
merge
Parameter 3
XDSL per-line …
overrule parameters Parameter N
Parameter 2
Parameter N
This feature allows fine-tuning the configuration of individual lines, deviating from
the overall settings configured via the profiles.
When using this feature, one should take care that the overruled parameter values do
not result in an inconsistency with the parameters that are configured via the profiles.
7 — xDSL features
For bonded XDSL lines, the data rate, the impulse noise protection and the delay
configuration of the individual lines are derived from the bonding profile parameters.
A subset of the per-line configuration overrule parameters related to data rate,
impulse noise protection or delay will also taken into account for bonded lines:
• Maximum data rate
• Minimum Impulse Noise Protection
7.13 Configurable US/ DS memory split
The aggregate interleaver or G.inp (G.998.4) memory supported for the different
VDSL2 profiles is defined by the VDSL2 standard (G.993.2). This aggregate
memory has to be split in the upstream and downstream direction, making a trade-off
between upstream and downstream data rate.
By default, a vendor discretionary algorithm is used to determine the memory split
between upstream and downstream. The configurable US/DS memory split feature
gives the operator manual control of the memory split. The percentage of memory
allocated to the downstream direction can be configured in steps of 1 percent. The
remaining memory is automatically allocated to the upstream direction.
By manually configuring the VDSL2 memory split, the operator has full control and
can make a better trade-off between upstream and downstream performance in case
the automatic algorithm does not provide the expected results.
7.14 Vectoring
VDSL2 vectoring takes full advantage of existing copper binders by making

conditions in the field as close to ideal as possible. Vectoring is not a method for
raising the theoretical maximum transport speeds. Instead, this noise-cancellation
technology addresses the gap between the theoretical maximum rate and the speeds
that service providers can deliver in typical field conditions.
In most deployments, telephone lines that carry VDSL2 signals are part of cables
(sometimes partitioned in smaller cable bundles) that contain 10 to a few hundred
lines positioned very closely together. This close proximity results in crosstalk, and
the higher the number of lines in a cable (bundle), the more crosstalk is generated.
Crosstalk is the main reason why lines in the field perform significantly lower than
their theoretical maximum. Vectoring enables each line to perform as if it is alone,
that is, without crosstalk. In a dynamic process, vectoring continually measures and
cancels this “crosstalk”, so all lines can operate at much higher capacity, as shown in
Figure 7-10.
7 — xDSL features
Figure 7-10 Typical vectoring gains

120
Optimal VDSL2 performance

100
80
Mbps
Near-optimal
field performance
60
with vectoring
40
Reduced field
performance due
20
to crosstalk
0
100 200 300 400 500 600 700 800 900 1000 1100 1200
Although most of the processing and necessary intelligence for vectoring resides in
the Digital Subscriber Line Access Multiplexer (DSLAM), minimal support is
needed at the Customer Premises Equipment (CPE) for the efficient estimation of the
crosstalk from the line into the neighboring lines and vice versa. This additional
functionality at the CPE side is defined by the International Telecommunication
Union (ITU) vectoring standard, G.993.5 (G.vector).
In order to achieve the full vectoring gain, all VDSL2 lines in the cable need to
participate in the crosstalk estimation. Otherwise, the crosstalk from some lines will
remain un-cancelled, reducing bit rates on vectored lines. The ultimate situation is
where all VDSL2 lines operate in G.vector mode.
Most of the existing VDSL2 CPEs in the field can be software upgraded to support
vectoring, or to be at least “vectoring-friendly”. The latter has recently been defined
by the ITU in Annexes X and Y of the VDSL2 standard (G.993.2) and allows the
crosstalk from the legacy line into the neighboring vectored lines to still be
measured. Annex X defines requirements for downstream friendliness such that the
crosstalk from the legacy line into the neighboring vectored lines can be estimated
and cancelled in downstream direction only. Annex Y defines requirements for full
friendliness, allowing estimation of crosstalk from the legacy line into the
neighboring vectored lines in up- and downstream direction. In principle, “friendly”
customers do not benefit from vectoring gains but their equipment no longer impairs
vectoring for subscribers who are paying for this enhancement.
Depending on the deployment scale (that is, the considered VDSL2 lines in the cable
binder) two vectoring types can be distinguished:
• Board Level Vectoring (BLV):
• Vectoring on one LT card (for example, 48 lines) and consequently only suited for
deployment scenario with deep fiber penetration where small remotes are installed.
• Only the crosstalk between the lines on the same card can be cancelled.
• System Level Vectoring (SLV):
• Vectoring over multiple LT cards and consequently suited for deployment scenarios
where bigger cabinets are installed.
• Crosstalk between lines on different LTs can be cancelled
7 — xDSL features
The main additional functional blocks for a vectoring system (compared to a

non-vectoring VDSL2 system) are the following:
• Vectoring Control Entity (VCE):
The VCE will control the Vectoring state machine and will use the incoming error
samples to do the calculation of the crosstalk coefficients.
The VCE is located on the LT board for BLV, whereas it is on the Vector
Processing board for SLV.
• Pre-/Post-coder
The Pre-/Post-coder will perform the actual crosstalk cancellation by
manipulating the outgoing/incoming signals from the different DSPs.
To configure vectoring on the ISAM you will need to create two new profiles: the
vectoring profile and the VCE profile. The VCE profile is assigned to the board
containing the VCE (LT card for BLV and Vector Processing card for SLV) while
the vectoring profile is assigned to the lines.
7.15 Fall-back configuration for vectoring
The vectoring profile specifies the type of CPE allowed on a line:

• G.Vector CPE
• G.Vector friendly CPE for downstream direction (G.993.2 Annex X)
• Full G.Vector friendly CPE (G.993.2 Annex Y)
• Legacy VDSL2 CPE
If the type of connected CPE does not match any of the allowed types, then by default
the line will not initialize in order not to disturb the other lines of the vectoring group.
As an alternative, the system can be configured to autonomously switch the line to a
fall-back VDSL2 configuration with limited spectrum usage in case a CPE capability
mismatch is detected. When the mismatch disappears, the line will autonomously
switch back to the normal configuration.
In case of communication problems between the LT and the VP card in case of SLV,
the lines configured with a vectoring profile will by default not initialize anymore in
order not to disturb the other lines of the vectoring group. As an alternative, the
system can be configured to autonomously switch the lines to a fall-back VDSL2
configuration with limited spectrum usage in case of detection of VP/LT
communication problems. When the communication recovers, the lines will
autonomously switch back to the normal configuration.
The definition of the fall-back configuration as well as the enabling of the fall-back
mechanism can be specified at XDSL LT board level:
• For BLV, the feature can optionally be enabled for the detection of a CPE
capability mismatch.
• For SLV, the feature can optionally be enabled for the detection of VP/LT
communication problems. If enabled, the feature can additionally be enabled for
detection of a CPE capability mismatch.
7 — xDSL features
8— Integrated Voice service: ISAM Voice
8.2 Overall network topology 8-3
8.3 Product and market applicability 8-12
8.4 Overall network support 8-13
8.5 Traffic types 8-13
8.6 Traffic forwarding methods 8-14
8.7 Layer 2/layer 3 addressing topologies 8-42
8.8 Protocol stacks 8-76
8.9 Management interface 8-85
8.10 Permanent data storage 8-86
8.11 Management model 8-88
8.12 CDE profile management 8-96
8.13 Service profile management 8-97
8.14 Basic call handling 8-98
8.15 Supplementary services 8-102
8 — Integrated Voice service: ISAM Voice
8.16 Registration procedure 8-111
8.17 Counters and Statistics 8-111
8.18 Reliability, Equipment / Connectivity / Overload

Protection 8-120
8.19 Quality of Service 8-133
8.20 DNS interworking 8-133
8.21 BITS Support 8-135
8.22 Narrowband Line Testing 8-135
8.23 Termination local loop unbundling 8-135
8.24 Alarm Treatment 8-135
8.25 Lawful Intercept 8-137
8.26 Compliancy to standards 8-143
8.27 ISAM Voice migration 8-144
8.1 Introduction
A specific use of the ISAM is to provide classic telephony services to subscribers

being connected with classic POTS/ISDN BRI lines, and to convert the
corresponding signals to VoIP signaling/data packets. An ISAM supporting the
integrated voice service is called ISAM Voice
The integrated voice service provides POTS or ISDN BRI service to subscribers over
copper pairs together or without xDSL service.
The voice information is converted to VoIP in the ISAM Voice access node and
forwarded to/from the service provider's Ethernet/IP network over optical fibers
along with the HSI and IPTV services carried by the access node.
VoIP networks are subject to standardization. Within standardization there are two
different approaches for the signaling:
• A set of standards driven by ITU-T, centered around ITU-T document H.248. In
a nutshell: a network based on this standard uses RTP for the voice and Megaco
for the signaling.
• A set of standards driven by IETF SIP. In a nutshell: a network based on this
standard uses RTP for the voice and SIP for the signaling.
VoIP SIP is supported by TISPAN compliant mode and non-IMS compliant
mode.
ISAM Voice supports both signaling methods and can be deployed in the
corresponding network topologies. However, ISAM Voice does not support both
methods to run concurrently in the same access node.
8.2 Overall network topology
This section describes the overall network topology for:

• Megaco ISAM Voice situated in a Next Generation Voice Network (NVGN).
• SIP ISAM Voice situated in a TISPAN-compliant NGN-IMS network.
• SIP ISAM Voice situated in a non-IMS-compliant network.
Megaco ISAM Voice situated in a NGVN network

Megaco ISAM Voice supports Narrowband (NB) services and provides the
connection to the NVGN for legacy Public Switching Telephone Network (PSTN)
users via Voice over IP (VoIP). It plays the role of Media Gateway (MG), also called
Access Media Gateway (AG).
Figure 8-1 Megaco ISAM Voice situated in a NGVN network
Subtending
ISAM Voice
Softswitch
PSTN
RTP
TGW P I
MGC ASP O S
T D
S N
Central Office
ISAM Voice POTS /
Servers ISDN
IP Network
H.248 / SIGTRAN
. P
O
T
L2 Aggregation M
S
IP G
BAS Network
edge
POTS/
ISDN
Remote
ISAM Voice
P I
P I O S
O S T D
T D S N
S N
POTS/ POTS/
ISDN ISDN
Remote
ISAM Voice
Megaco ISAM Voice connects legacy Narrow Band (NB) user interfaces, including
Plain Old Telephone Services (POTS) and Integrated Services Digital Network
(ISDN) BRI, to the NGVN.
Megaco ISAM Voice supports centralized configurations, where the NB user
interfaces and MG are integrated in the same node, and distributed configurations,
where the MG is located in a hub node and the NB user interfaces in remote nodes.
The remote nodes can be subtended by the ISAM Voice acting as a MG, or located
within the layer 2 aggregation or IP network.
A voice cluster is the aggregation of one Voice server pair, residing in the hub node,
together with its voice associated ISAM nodes, that is, together with the ISAM nodes
that contain Voice Line Termination (LT) boards that are managed by that particular
Voice server pair. A voice cluster can support a maximum of 5K subscribers. These
subscribers may be scattered over a maximum of 32 ISAM nodes and a maximum of
104 Voice LT boards.
A hub node may contain up to 8 Voice server pairs. In other words a hub node may
host up to 8 different Voice Clusters.
The hub ISAM Voice, combined with the subtending/remote ISAM Voice, provides
the view of a unique centralized MG. In subtending or remote configurations, the
connection to the hub is via Fast or Gigabit Ethernet (optical or electrical). The Trunk
MG links the NGVN with a legacy PSTN network.
The Softswitch is responsible for call control and charging, and communicates with
the Media Gateways (Megaco ISAM Voice) via the Media Gateway Control
(Megaco) protocol H.248.
SIGTRAN is used for ISDN BRI users, that is, Q921 is terminated in ISAM Voice
and SIGTRAN is implemented to transfer Q931 messages between ISAM Voice and
ASP.
SIP ISAM Voice situated in a TISPAN-compliant NGN-IMS network

SIP ISAM Voice supports Narrowband (NB) services and provides the connection
to Next Generation Networks (NGN) for legacy PSTN users via Voice over IP
(VoIP).
ISAM Voice plays the role as Voice Gateway (VGW) and communicates with the
IMS core via the SIP protocol.
Figure 8-2 SIP ISAM Voice situated in a TISPAN compliant NGN-IMS network
DHCP
Mgmt DN S
Se r ve r
Pla tfo r m Se r ve r
PSTN
SG F/ T-MG F
S_CSCF
MG CF ISAM Voice
AS I_CSCF
P P U
O O A
P_CSCF RTP T T
S S
POTS
HSS ISAM Voice

SIP
SBC
IMS
ER P P U
Co r e IP O O A
MRF T T
N e two r k S S
Vo ice L2 Ag g r e g a tio n POTS
x- CSCF/ BG CF
G a te wa y
N e two r k
IBCF/ IBGF
ISAM Voice
ER
O th e r IP P
O
P U
O
T A
Networks Se rve rs
T
S S
ISAM Voice POTS
P P
O O U
T T A
S S
BAS
POTS
ISAM Voice connects legacy Narrow Band (NB) user interfaces, the Plain Old
Telephone Services (POTS), to the NGN/IMS.
Each of the nodes connected to the layer 2 aggregation or IP network has the SIP UA
locally integrated on the Voice LT. The local SIP UA serves all NB user interfaces
connected to a Voice LT.
The Call Session Control Function (CSCF) establishes, monitors, supports and
releases multimedia sessions and manages the user's service interactions. The CSCF
can act as Proxy CSCF (P-CSCF), Serving CSCF (S-CSCF) or Interrogating CSCF
(I-CSCF):
• The P-CSCF is the first contact point for the ISAM Voice within the IM
subsystem (IMS).
• The S-CSCF fulfils the role of registrar and handles the session states in the
network.
• The I-CSCF is mainly the contact point within an operator's network for all IMS
connections destined to a subscriber of that network operator, or a roaming
subscriber currently located within that network operator's service area.
The Home Subscriber Server (HSS) is a master user database that supports the IMS
network entities that handle calls. It contains the subscription-related information
(user profiles), performs authentication and authorization of the user, and can
provide information about the user's physical location.
Interconnection with legacy PSTN networks is guaranteed at the signaling level via
the Signaling Gateway Function (SGF) (transport) and the Media Gateway Control
Function (MGCF) (call/service control). Interconnection at the media level is
provided by the Trunk Media Gateway Function (T-MGF).
Interconnection with other IP-based service subsystems (including other IMS
subsystems) is performed via the Interconnection Breakout Control function (IBCF)
at the signaling level and the Interconnection-Border Gateway Function (I-BGF) at
the media level.
Very often, to support lawful intercept, Voice traffic is switched along the Legal
Intercept gateway.
SIP ISAM Voice situated in a non-IMS-compliant network

SIP ISAM Voice supports the Narrowband (NB) services and provides the
connection to an IMS-like New Generation Network (NGN) for legacy PSTN users
via Voice over IP (VoIP).
ISAM Voice plays the role as Voice Gateway (VGW) and can interface with voice
feature servers acting as back-to-back SIP Servers via the SIP protocol.
Figure 8-3 SIP ISAM Voice situated in a non-IMS-compliant network

Management
DHCP server
Platform
ISAM
Voice
DHCP
SNMP/
CLI/TL1 P
O
IP T POTS
S
SIP
RTP / RTCP
Media
Gateway SIP
server
ISAM Voice connects legacy Narrow Band (NB) user interfaces, the Plain Old
Telephone Services (POTS), to a non-IMS compliant network.
Each of the nodes connected to the IP network has the SIP UA locally integrated on
the Voice LT. The local instance of the SIP User Agent (UA) serves all NB user
interfaces connected to a Voice LT.
The role of the SIP ISAM Voice is twofold:

• Access Gateway.
• Access Gateway Controller (maintains AG states, manages AG features,
implements SIP UA).
Access network L2/L3 topologies
Megaco ISAM Voice

ISAM Voice access nodes belonging to a Voice cluster may be connected by layer
2, layer 3 or even a mixture of a layer 2 aggregation network and a layer 3
aggregation network.
Different Voice clusters may be connected by layer 2, layer 3 or even a mixture of a
layer 2 aggregation network and a layer 3 aggregation networks.
The supported ISAM Voice Cluster topologies are shown in Figure 8-4, Figure 8-5,
Figure 8-6, Figure 8-7, Figure 8-8 and Figure 8-9.
Figure 8-4 Megaco ISAM Voice: Voice Cluster topology A
xVPS xVPS xVPS

pair 1 pair 2 pair 8
Main shelf
Voice Voice Voice LT shelf 1 Voice

LT 1 LT 2 Belongs to voice cluster LT 16
supervised by xVPS pair 1

supervised by xVPS pair2

Figure 8-5 Megaco ISAM Voice: Voice Cluster topology B
xVPS xVPS xVPS

Main shelf



Figure 8-6 Megaco ISAM Voice: Voice Cluster topology C
xVPS xVPS xVPS Voice Voice Voice

pair 1 pair 2 pair 3 LT 1 LT 2 LT 10
Voice LTs belongs to voice cluster

Main shelf supervised by xVPS pair 1



Figure 8-7 Megaco ISAM Voice: Voice Cluster topology D

Voice LTs belong to different voice clusters

Main shelf supervised by xVPS pair 1, 2 or 3



Figure 8-8 Megaco ISAM Voice: Voice Cluster topology E
xVPS xVPS xVPS

Main shelf
Voice LTs in Voice LTs in

Voice shelf 1 belong to voice Voice Voice shelf 1 belong to voice Voice
LT 1 LT N LT N+1 cluster supervised by
LT 16
cluster supervised by
xVPS pair 1 xVPS pair 2

LT 1 LT M LT M+1 cluster supervised by
LT 16
Voice Voice Voice LT shelf 8 (multiple) Voice

Figure 8-9 Megaco ISAM Voice: Voice Cluster topology F

Voice LTs belong to different voice clusters

Main shelf supervised by xVPS pair 1, 2 or 3

LT 1 LT N LT N+1 cluster supervised by
LT 16

LT 1 LT M LT M+1 cluster supervised by
LT 16

LT 1 LT 2 Belongs to different voice clusters LT 16
supervised by xVPS pair 1, 2 or 3
SIP ISAM Voice

ISAM Voice access nodes may be connected by layer 2, layer 3 or even a mixture of
a layer 2 aggregation network and a layer 3 aggregation network.
Figure 8-10 ISAM Voice access nodes connected to a layer 2 Aggregation Network
Iv Iv
Iv
L3 L2
Aggrega tion Aggrega tion Iv
Network Network
Iv
Iv
Iv = ISAM Voice
Iv
Figure 8-11 ISAM Voice access nodes connected to a layer 3 Aggregation Network
Iv Iv
Iv
L3
Aggrega tion Iv
Network
Iv
IV
IV= ISAM Voice
Iv
Figure 8-12 ISAM Voice access nodes connected to a layer 2/layer 3 Aggregation Network
Iv Iv
Iv
L3 L2
Aggrega tion Aggrega tion Iv
Network Network
Iv
Iv
Iv = ISAM Voice
Iv
8.3 Product and market applicability
Megaco
The H.248 (Megaco) signaling based integrated voice service is supported for the
following products:
• 7302 ISAM: POTS and ISDN BRI services supported. 18 LT slot positions can
be planned with Voice LT.
• 7330 ISAM FTTN: POTS and ISDN BRI services supported. 10 LT slot positions
can be planned with Voice LT.
• 7356 ISAM FTTB SB-REM: Only POTS service supported. Voice LT can be
planned for both the “master” (72-lines LT board only) and the “non-Master”
(48-lines and 72-lines LT board) slot positions.
SIP
The SIP-signaling-based integrated voice services are supported in:
• 7302 ISAM FD: POTS service supported. 18 LT slot positions can be planned
with the Voice LT board.
• 7330 ISAM FTTN FD: POTS service supported. 10 LT slot positions can be
planned with Voice LT.
• 7356 SB-REM (FD) ETSI: POTS service supported. The Voice LT board can be
planned for both the “master” (72-lines LT board only) and the “non-master” (48-
and 72-lines LT board) slot positions.
IMS
In an IMS network topology, the SIP signaling POTS service and the H.248
(Megaco) signaling based ISDN BRI service can be mixed in the same 7302 / 7330
ISAM shelf.
• In an IMS network topology, H.248 ISDN-BRI subscribers register to their Media
Gateway Controller and are managed by the local Media Gateway (Voice Server)
while SIP POTS subscribers register to their registrar and are managed by the
local SIP User Agent.
• Any VLAN topology for this mixed SIP/H.248 voice services is allowed, on the
condition that not more than 2 VLANS (Public or Private) of type Voice-VLAN
are configured per shelf.
• The mixed SIP signaling POTS and H.248 (Megaco) signaling based ISDN BRI
service is supported for both, the switched as well as the routed voice model.
• H.248 clustering is supported (Hub/Subtending/Remote ISAM Voice node).
• Integrated Line Test is supported for SIP signaling POTS terminations.
• MTA is supported for both SIP signaling POTS and H.248 ISDN BRI
terminations.
• Basic call service and Supplementary services are supported for both SIP
signaling POTS and H.248 ISDN BRI.
8.4 Overall network support
• Megaco ISAM Voice situated in a Next Generation Voice Network (NGVN):

supported
• SIP ISAM Voice (centralized and distributed architecture) situated in a
TISPAN-compliant NGN-IMS network: supported
• SIP ISAM Voice (centralized and distributed architecture) situated in a
non-IMS-compliant network: supported.
8.5 Traffic types
Megaco ISAM Voice

Four main traffic types can be distinguished:
• Management traffic (SNMP, CLI, TL1 (alarm display only)) exchanged between
the OSS platform and the Network termination (NT) and Voice server.
• Signaling traffic (Megaco, SIGTRAN) exchanged between the Media Gateway
Controller (MGC)/Application Server Process (ASP) and the Voice server.
• Internal signaling traffic (XLES) exchanged between the Voice server and its
underlying Voice LT boards hosted in either the hub, subtending or remote access
nodes.
• Voice data traffic (RTP, RTCP, Voice Band data).
Management traffic is exchanged in the external communication VLAN and as such
kept separate from the other traffic types. This is done for security reasons.
Voice data traffic and internal signaling traffic always share the same VLAN.
External signaling traffic may be exchanged in a dedicated signaling VLAN or may
even share the same VLAN as the Voice data and Internal signaling traffic. The latter
situation occurs when IP address/IP subnet optimization is preferred above signaling
and voice data traffic isolation.
SIP ISAM Voice

Three main traffic types can be distinguished:
• Management traffic (SNMP, CLI, TL1 (alarm display only)) exchanged between
the external management platform and the Network termination (NT).
• Signaling traffic (SIP) exchanged between the SIP Server and the SIP User Agent
residing at the Voice LT.
• Voice data traffic (RTP, RTCP, Voice Band data).
Management traffic is exchanged in the external communication VLAN and as such
kept separate from the other traffic types. This is done for security reasons.
External signaling traffic may be exchanged in a dedicated signaling VLAN or may

even share the same VLAN as the Voice data signaling traffic. The latter situation
occurs when IP address/IP subnet optimization is preferred above signaling and
voice data traffic isolation.
8.6 Traffic forwarding methods
The internal forwarding is frame based. Frame based forwarding is done either based
on layer 2 (Ethernet), layer 3 (IP) or layer 4 (UDP/TCP) information carried in the
frames.
The applied forwarding methods may be different for upstream and downstream
traffic forwarding.
For layer 2 forwarding, see chapter “Layer 2 forwarding”. For layer 3 forwarding,
see chapter “IP routing”.
The basic concept of layer 4 forwarding is explained in the following section.
Conceptual models
MEGACO switched model

Figure 8-13 shows the MEGACO ISAM Voice switched model.
Figure 8-13 Megaco ISAM Voice: switched model
Main ISAM Voice

Fast path VRF
Voice LT IP address voice Voice VLAN
Signaling VLAN
IP address
XLES
Voice NT
server
IP address
signalling
• The network signaling VLAN terminates at the Voice server

• The network RTP/RTCP (XLES) VLAN terminates at the voice LT board/Voice
server
• The signaling VLAN is configured as type “Voice-VLAN” or “RB-VLAN”
• The RTP/RTCP/XLES VLAN is configured as type “Voice-VLAN”
• The source/destination IP address for H.248 signaling traffic is configured at the
Voice server
• The source/destination IP address for XLES traffic is configured at the Voice
server
• The source/destination IP address for RTP/RTCP traffic is configured at the

SHub and is shared by all the Voice LT boards
• The SHub performs L4 forwarding for RTP/RTCP/XLES traffic destined to the
voice LT board
• The SHub performs L2 forwarding for upstream/downstream signaling traffic
• The SHub performs L3 forwarding for upstream RTP/RTCP/XLES traffic.
MEGACO routed model

Figure 8-14 shows the MEGACO ISAM Voice routed model.
Figure 8-14 Megaco ISAM Voice: routed model
Main ISAM Voice

Fast path VRF
Network
Voice LT IP address VLAN 1
IP address
Internal
network 1
Voice
Voice
VLAN IP address IP address
User 1 network 2 Network
VLAN 2
IP address
XLES
Voice NT
Internal
server signaling
IP address VLAN
signalling
The conceptual architecture shows different VLANs carrying H.248 signaling and
RTP/RTCP/XLES traffic at the network side than at the user side of the VRF.
The internal VLAN that carries RTP/RTCP/XLES traffic must be of type
“voice-VLAN” as to perform L4 forwarding in downstream direction.
The internal VLAN that carries the signaling traffic may be of type “Voice-VLAN”
or “RB-VLAN”.
• VRF user side: a numbered IP interface is configured on top of the internal voice
VLAN for the following reasons:
• This IP interface is used as the destination IP address for RTP/RTCP/XLES packets
addressed to the voice LT board. For this purpose, the Voice subnet is advertised (as
host subnet) to the upstream network.
• The SHub is considered as the first next hop for the RTP/XLES packets sent in the
upstream direction by the xVPS board.
• VRF user side: A numbered IP interface is configured on top of the internal
signaling VLAN. The SHub is seen as the first next hop for the H.248 signaling
traffic that originates from the Media Gateway running at the xVPS board.
The signaling subnet is advertised (as host subnet) to the upstream network.
• Network side: A numbered IP interface is configured on top of the network-side
signaling VLAN.
• Network side: A numbered IP interface is configured on top of the network-side
TP/RTCP/XLES VLAN.
In the upstream direction, the selection of the network interface/VLAN will happen
as the result of the IP DA look-up in the L3 forwarding table, and this for all the voice
service related traffic (H.248 signaling, XLES, RTP and RTCP).
In the downstream direction, voice-service-related traffic (H.248 signaling, XLES,
RTP and RTCP) may be received at any network interface/VLAN. The SHub must
perform the further L3 forwarding to:
• the appropriate internal VLAN
• and to the destined xVPS
• and to the destined voice LT board (by L4 forwarding)
From a downstream forwarding perspective, seen from the edge router, the ISAM
Voice access node is configured as the next-hop.
SIP ISAM Voice (centralized architecture): switched model

Figure 8-15 shows the SIP ISAM Voice (centralized architecture) switched model.
Figure 8-15 SIP ISAM Voice (centralized architecture): switched model
Main ISAM Voice

Fast path VRF
Voice LT IP address voice Voice VLAN
Signaling VLAN
IP address
signalling
NT
• The network signaling VLAN terminates at the voice LT board

• The network RTP/RTCP VLAN terminates at the voice LT board
• Both VLANs are configured as type “Voice-VLAN”
• The source/destination IP address for SIP signaling traffic is configured at the
SHub. It is shared by all the voice LT boards
• The source/destination IP address for RTP/RTCP traffic is configured at the
SHub. It is shared by all the voice LT boards
• The SHub performs L4 forwarding for SIP signaling/RTP/RTCP traffic destined
to the voice LT board
• The SHub performs L3 forwarding for upstream SIP signaling/RTP/RTCP
traffic.
SIP ISAM Voice - centralized architecture: routed model

Figure 8-16 shows the SIP ISAM Voice (centralized architecture) routed model.
Figure 8-16 SIP ISAM Voice (centralized architecture): routed model
Main ISAM Voice

Fast path VRF
Internal
Voice Network
Voice LT VLAN IP address VLAN 1
IP address
network 1
Voice
IP address IP address
Internal
signaling network 2 Network
signaling
VLAN VLAN 2
NT
The conceptual architecture shows different VLANs carrying SIP signaling and
RTP/RTCP traffic at the network and the user side (VLAN) of the VRF.
Both internal VLANs must be of type “Voice VLAN” as to perform L4 forwarding
in downstream direction.
• VRF user side: A numbered IP interface is configured on top of the internal voice
VLAN. This IP address is used as destination IP address for RTP/RTCP packets
addressed to the voice LT board. For this purpose, the Voice subnet is advertised
(as host subnet) to the upstream network.
signaling VLAN. This IP address is used as destination IP address for SIP
signaling packets addressed to the voice LT board. For this purpose, the signaling
subnet is advertised (as host subnet) to the upstream network.
• VRF network side: A numbered IP interface is configured on top of the network
voice VLAN
signaling VLAN.
as the result of the IP DA look-up in the L3 forwarding table. And this for all the
voice service related traffic (SIP signaling, RTP and RTCP).
In the downstream direction, voice service related traffic (SIP signaling, RTP and
RTCP) may be received at any network interface/VLAN. The SHub must perform
the further L3 forwarding to:
• the appropriate internal VLAN
• and to the destined voice LT board (by L4 forwarding)
SIP ISAM Voice - distributed architecture: switched model

Figure 8-17 shows the SIP ISAM Voice (distributed architecture) switched model.
Figure 8-17 SIP ISAM Voice (distributed architecture): switched model
Main ISAM Voice

Fast path VRF
IP address Voice VLAN

voice
IP address
signalling Signaling VLAN
Voice LT
NT
• The network signaling VLAN terminates at the voice LT board

• The network RTP/RTCP VLAN terminates at the voice LT board
• At the SHub, both VLANs are configured as type “iBridge” or “Voice VLAN”
• The source/destination IP address for SIP signaling traffic is configured at the
voice LT boards. Each voice LT board owns a different signaling IP address.
• The source/destination IP address for RTP/RTCP traffic is configured at the voice
LT boards. Each voice LT board owns a different signaling IP address.
• The SHub performs L2 forwarding for SIP signaling/RTP/RTCP traffic destined
to the voice LT board
• The SHub performs L2 forwarding for upstream SIP signaling/RTP/RTCP
traffic.
SIP ISAM Voice - distributed architecture: routed model

Figure 8-18 shows the SIP ISAM Voice (distributed architecture) routed model.
Figure 8-18 SIP ISAM Voice (distributed architecture): routed model
Main ISAM Voice

Fast path VRF
Internal
Voice Network
IP address
VLAN IP address VLAN 1
Voice IP address
network 1
User 1
signaling IP address
Internal
signaling
VLAN VLAN 2
Voice LT
NT
The conceptual architecture shows different VLANs carrying SIP signaling and
RTP/RTCP traffic at the network and the user side (VLAN) of the VRF.
At the VRF user side, internal VLANs are configured as type “iBridge” or “Voice
VLAN”.
• VRF user side: A numbered IP interface is configured on top of the internal voice
VLAN.
Note — The IP address configured at the voice LT board is used as
destination IP address for RTP/RTCP packets addressed to the voice
LT board. For this purpose, the Voice subnet is advertised (as host
subnet) to the upstream network.
signaling VLAN.
Note — The IP address configured at the voice LT board is used as
destination IP address for SIP signaling packets addressed to the voice
LT board. For this purpose, the signaling subnet is advertised (as host
subnet) to the upstream network.
voice VLAN.
signaling VLAN
The SHub will be considered as the first next hop for the SIP signaling and for the
RTP/RTCP traffic that originates from the voice LT board. For this reason, a
numbered IP interface is configured on both the internal signaling VLAN and the
internal RTP/RTCP VLAN at the VRF user side.
as the result of the IP DA look-up in the L3 forwarding table. And this for all the
voice service related traffic (SIP signaling, RTP and RTCP).
In the downstream direction, voice-service-related traffic (SIP signaling, RTP and
RTCP) may be received at any network interface/VLAN. The SHub must perform
the further L3 forwarding to the appropriate internal VLAN and to the destined voice
LT board.
Subtended topology: switched model

Figure 8-19 shows the MEGACO/SIP ISAM voice subtended topology for the
switched model.
Figure 8-19 Subtended topology: switched model
Main ISAM Voice

Fast path VRF
Voice VLAN
Signaling VLAN
NT
Subtending ISAM
Fast path VRF
NT
Subtended topology: routed model

Figure 8-20 shows the MEGACO/SIP ISAM voice subtended topology for the
routed model.
Figure 8-20 Subtended topology: routed model
Main ISAM Voice

Fast path VRF
Network
IP address VLAN 1
IP address
network 1
User 1
VLAN 2
NT sub 1 sub 2
Main ISAM Voice

Fast path VRF
NT
The subtending ISAM Voice access node remains configured as a switching device.
Only the main ISAM Voice access node fulfills the routing service.
The conceptual traffic forwarding models depicted in a previous chapter for the
SHub based system without Remote Expansion Module also apply to the SHub based
system with Remote Expansion Module. (The physical position of the voice LT
board, locally connected in the host access node or remotely connected by means of
a REM, is transparent to the operational behavior of the VoIP service)
• Megaco ISAM Voice Service:
• Remote Expansion Module may host 1 or 2 voice LT boards: Voice LT board can
be planned for both the “master” (72-line LT board only) and the “non-Master”
(48-line and 72-line LT board) slot position.
• Remote Expansion Module cannot host the Voice Server.
• SIP ISAM Voice Service:
• Remote Expansion Module may host 1 or 2 voice LT boards: Voice LT board can
be planned for both the “master” (72-line LT board only) and the “non-Master”
(48-line and 72-line LT board) slot position.
Layer 4 forwarding
The layer 4 forwarding applies to downstream traffic only and is installed at the
SHub on a per-VLAN basis. This forwarding method uses the contents of the
destination port field in the transport protocol header of the packet to forward a
packet to a voice LT. The configuration of an IP interface on top of a VLAN
configured as Voice-VLAN automatically installs the layer 4 forwarding property.
Each voice LT gets assigned a fixed transport protocol port range. The SHub port that
connects the voice LT inherits this port range mapping. The transport protocol port
range for free usage (IANA) that is, 49153 - 65535 is divided in 32 equal portions
and the lower part of each portion is mapped to the different SHub ports. The
mapping algorithm is fixed to achieve the same range to SHub port mapping. Upon
receipt of a downstream packet within a layer 4 forwarding capable VLAN and with
the destination IP address configured on top of this VLAN, the destination port value
of the transport protocol header included in the packet is compared against all
defined transport protocol ranges. When a match is found, the corresponding SHub
port mapping is read and the packet is forwarded to the voice LT that connects to this
SHub port.
As described, the layer 4 forwarding uses the combination {destination IP address +
destination Transport Protocol port} to decide about the further downstream
forwarding of an IP packet.
Layer 4 forwarding may be applied to external signaling, internal signaling and voice
data traffic.
Layer 4 forwarding supports packet fragmentation at IP layer because unlike Voice
traffic, SIP signaling traffic may be fragmented at the IP layer.
The transport protocol port range to SHub mapping is the same in every ISAM Voice
node.
The described algorithm is schematically shown in Figure 8-21.
Figure 8-21 Layer 4 forwarding approach
SHub
ARP ARP
Match (Transport Prot port range1, port a1 )

(VLAN ID + (Transport Prot portrange2, port a 2 )
own Y
…
MAC address/
(Transport Prot port rangeN, port an )
IP address)?
Ingress
N
Layer 4 forwarding Egress
Layer 3 IP table
Layer 2 VLAN/MAC table
Layer 2/layer 3 forwarding
User-to-user communication
The integrated voice service requires that user-to-user communication is enabled for
RTP/XLES traffic. (Megaco based integrated voice service only).
Two VLAN types are applicable to the deployment of the integrated Voice service:
• iBridge VLAN type
• Voice VLAN type
The VLAN type that needs to be applied depends on the downstream signaling/voice
traffic forwarding behavior being required at the SHub:
• L4 forwarding: only the Voice VLAN type can be used.
• L2 forwarding: both the Voice VLAN type and the iBridge VLAN type may be
used.
If the iBridge VLAN type is used then L2/L3 user-to-user communication must be
enabled for this VLAN.
If the Voice VLAN type is used, then L2/L3 user-to-user communication is
autonomously enabled by the system. In addition, the configuration of an IP interface
on top of this VLAN of type Voice VLAN autonomously enables the L4 forwarding
behavior in downstream direction at the ASAM port(s).
Megaco ISAM Voice as switching device
Signaling traffic
Signaling traffic originates and terminates at the Voice server.
In the upstream direction, the Voice server determines the IP next hop for the
destination IP address of the packet, performs ARP the next hop IP address and
forwards the IP packet appropriately. The local SHub and any potential intermediate
SHub perform layer 2 forwarding.
In the downstream direction: The local SHub and any potential intermediate SHub
perform layer 2 forwarding.
Figure 8-22 Megaco ISAM Voice (switched): signaling forwarding

L4 forwarding
L3 forwarding
Remote node Main node
NT board Signaling
NT board L2 forwarding IP address Voice
XLES server
IP address
SHub Voice SHub Voice
Voice LT IP address IP address Voice LT
board L2 board
aggregation
network
L4 forwarding
Remote node Subtending node
NT board NT board
L3
aggregation
network
board board
L4 forwarding
MGC ASP
SoftSwitch
XLES traffic
XLES traffic originates at the Voice server or at the Voice LT board and terminates
respectively at the Voice LT board or the Voice server.
• XLES traffic originating at the Voice server and destined to the Voice LT board
(see Figure 8-23):
The destined Voice LT is connected to:
• the local access node or
• an access node subtending to the local access node or
• an access node connected via a L2 aggregation network with the local access node.
The destination (Shub) IP address of the packet can directly be reached in the
local subnet. The Voice server performs ARP for the destination (Shub) IP
address and forwards the IP packet to this (Shub) IP address.
The destined Voice LT board is reachable via a layer 3 aggregation network. The
Voice server determines the IP next hop for the destination (Shub) IP address of
the packet, performs ARP for the next hop IP address and forwards the IP packet
appropriately.
The (destined) SHub that connects the destined Voice LT performs layer 4
forwarding.
Any potential intermediate Shub in between the Voice Server and the destined
Shub performs layer 2 forwarding.
• XLES traffic originating at the Voice LT board and destined to the Voice server
(see Figure 8-24):
The Voice LT board forwards the XLES packet to the local SHub.
• The access node of the Voice LT board and the access node of the Voice server are
the same or
• The access node of the Voice LT board subtends to the access node of the Voice
server or
• The access node of the Voice LT board is connected via a layer 2 aggregation
network with the access node of the Voice server
The local SHub detects that the destination IP address of the packet can directly
be reached via the local subnet. The local Shub performs ARP for the destination
IP address and forwards the IP packet appropriately.
The destined Voice Server is reachable via layer 3 aggregation network: The local
SHub determines the IP next hop for the destination IP address of the packet,
performs ARP the next hop IP address and forwards the IP packet appropriately.
The SHub that connects the Voice server performs layer 2 forwarding.
Any potential intermediate SHub in between the Voice LT's local Shub and the
Voice Server L2 forwarding.
Figure 8-23 Megaco ISAM Voice (switched): XLES packet originating at the Voice server
L4 forwarding
L3 forwarding
NT board Signaling
XLES server
IP address
board L2 board
aggregation
network
L4 forwarding
NT board NT board
L3
aggregation
network
board board
L4 forwarding
MGC ASP
SoftSwitch
Figure 8-24 Megaco ISAM Voice (switched): XLES packet originating at the Voice LT
board
L3 forwarding
NT board Signaling
XLES server
IP address
board L2 board
aggregation
network
L3 forwarding
NT board NT board
L3
aggregation
network
board board
L3 forwarding
MGC ASP
SoftSwitch
Voice traffic
Voice traffic originates at the Voice LT board and is destined to a voice termination
point either at the same Voice LT board, at another Voice LT board in the same
Voice cluster or outside the voice cluster.
In some cases the voice traffic is sent along the Voice server (as to support some
supplementary services or an optimized IP addressing scheme).
Voice traffic is relayed to the SHub prior to the forwarding to the destined voice
termination point. This relay is either done by the Voice LT board (voice traffic that
may not pass the Voice server) or the Voice server (voice traffic that must pass the
voice server).
Voice traffic not passing the Voice server:
• Voice traffic destined to an external termination point:
• The voice LT board forwards the voice traffic to the local SHub.
• The local SHub determines the IP next hop for the voice traffic destination IP
address
• The local SHub performs ARP for the next hop IP address and forwards the IP
packet appropriately.
• Any potential intermediate SHub between the local Shub and the next hop performs
layer 2 forwarding.
• Voice traffic destined to a voice termination point connected to the same Voice
LT board in the local access node:
• The voice LT board forwards the upstream voice packet to the local SHub.
• The local SHub detects that the destination IP address of the packet is identical to
the own Voice IP address and treats the voice traffic locally.
• The local SHub performs layer 4 forwarding to the Voice LT board from which the
packet originated.
• Voice traffic destined to a voice termination point connected to a different Voice

LT board in the local access node:
• The voice LT board forwards the upstream voice packet to the local SHub.
the own Voice IP address and treats the voice traffic locally.
• The local SHub performs layer 4 forwarding to the Voice LT board to which the
destined voice termination point is connected.
• Voice traffic destined to a voice termination point residing at a Voice LT in
another access node of the voice cluster:
• The voice LT board forwards the upstream voice traffic to the local SHub.
• One of the following takes place:
1. The destined Voice termination point is reachable via a layer 3 aggregation
network:
The local SHub determines the IP next hop for the destination of the voice traffic IP
address. The local SHub performs ARP the next hop IP address and forwards the
voice traffic appropriately.
2. The destined Voice termination point reachable via a layer 2 aggregation
network:
The local SHub detects that the destination of the voice traffic is reachable via the
local subnet. The local xHub performs ARP the destination IP address and forwards
the voice traffic appropriately.
• Any potential intermediate SHub between the local Shub and the destined SHub
performs layer 2 forwarding.
• The SHub that connects the destined voice termination point (Voice LT board)
Voice traffic passing the Voice server:

• Voice traffic destined to the Voice server:
• The voice LT forwards the upstream voice traffic to the local SHub.
• If the destined Voice Server is reachable via layer 3 aggregation network:
The local SHub determines the IP next hop for the Voice server, performs ARP for
the next-hop IP address and forwards the voice traffic appropriately.
• If the destined Voice Server is reachable via layer 2 aggregation network (in case
the access node of the Voice LT board is either equal to the access node of the Voice
server, or to an access node that subtends to the access node of the Voice server or
to an access node connected via a layer 2 aggregation network with the access node
of the Voice server):
the local SHub detects that the Voice server is reachable within the local subnet. The
local Shub performs ARP for the IP address of the Voice server and forwards the IP
packet appropriately
• The SHub that connects the Voice server performs layer 2 forwarding.
• Any potential intermediate SHub between the local Shub and the SHub that
connects the Voice server performs layer 2 forwarding.
• Voice traffic relayed by the Voice server to a voice termination point connected
to a Voice LT board in the same access node:
• The Voice server invokes the NAPT facility and forwards the voice traffic along the
local SHub to itself (this is a basic forwarding condition to allow the support of
External packet forwarding serving Lawful Intercept).
• The Voice server detects that the destination of the voice traffic is reachable via the
local subnet and forwards the voice traffic to the IP address of the local SHub.
• The local SHub performs layer 4 forwarding to the Voice LT board that connects the
Voice termination point.
• Voice traffic relayed by the Voice server to a voice termination point connected
to a Voice LT board in another access node of the voice cluster:
• The destined Voice Termination point is reachable via layer 3 aggregation network.
The Voice server determines the IP next hop for the destination of the voice traffic,
performs ARP for the next hop IP address and forwards the voice traffic
appropriately.
• The destined Voice Termination point is reachable via layer 2 aggregation network
(in case the Voice Termination point is connected to an access node subtending to
the local access node or an access node connected via a layer 2 aggregation network
with the local access node):
The Voice server invokes the NAPT facility and forwards the voice traffic along the
The Voice Server detects that the destination of the voice traffic is reachable via the
local subnet, performs ARP for the destination IP address and forwards the voice
traffic appropriately.
• The SHub that connects the Voice termination point (Voice LT board) performs
layer 4 forwarding.
• Any potential intermediate SHub between the Voice server and the SHub
connecting the destined voice termination performs layer 2 forwarding.
• Voice traffic relayed by the Voice server to an external voice termination point:
• The Voice Server determines the IP next hop for the destination of the voice traffic,
appropriately.
• Any potential intermediate SHub in between the Voice server and the next hop
Figure 8-25 Megaco ISAM Voice (switched): Voice packet originating at the Voice LT
board
L4 forwarding
NT board Signaling
XLES server
IP address
board L2 board
aggregation
network
L3 forwarding
NT board NT board
L3
aggregation
network
board board
L4 forwarding L3 forwarding
MGC ASP
SoftSwitch
Figure 8-26 Megaco ISAM Voice (switched): Voice packet originating at the Voice server
L4 forwarding
L3 forwarding
NT board Signaling
XLES server
IP address
board L2 board
aggregation
network
L2 forwarding
L2 forwarding
NT board NT board
L3
aggregation
network
board board
L3 forwarding
MGC ASP
SoftSwitch
OAM traffic
The management platform of the customer forwards the Voice OAM traffic to the
public OAM IP address of the ISAM access node hosting the Voice server.
Voice OAM traffic is distinguishable by a Voice specific SNMP community
string/context identifier from non-Voice OAM traffic and in addition distinguishable
through the same SNMP community string/context identifier amongst the Voice
server pairs (maximum 8) that may be hosted in the same ISAM access node.
Internally, the voice-specific OAM traffic is relayed to the Voice server.
Voice OAM responses generated by the Voice server are internally passed to the
ISAM SNMP agent that forwards them to the management platform of the customer.
Any potential intermediate SHub performs layer 2 forwarding and this in both
directions.
Refer also to chapter “Management”.
Megaco ISAM Voice as routing device

The following routing topologies are supported:
• Single ISAM-V access node topology:
in this topology, only the main shelf is present. The main shelf behaves as a
routing device.
• Subtending ISAM-V access node topology:
in this topology, the main shelf and one or more subtending shelves are present.
Only the main shelf behaves as routing device. The subtending shelves behave as
switching device.
Summarized: An ISAM-V access node that is directly connected to the upstream

voice network can be configured as a routing device. An ISAM-V access node that
is not directly connected to the upstream voice network must be configured as
switching device.
Security considerations
The ISAM supports only a single fast path VRF. As a result, access nodes that are
deployed in mixed mode (that is, narrowband services and broadband services are
concurrently deployed by the same access node) must include protections that
guarantee that data is kept secret against unwanted, unintended and malicious
listeners and this for both the narrowband services and the broadband services.
This can be achieved as follows:
• At the network side of the VRF, the broadband data path is separated from the
narrowband data path by configuring different VLANs for these different data
paths (= different IP subnets).
In this respect, path protection can be guaranteed by the routing protocols
(different areas).
• At the user side of the VRF, ACLs need to be installed at the ports connection the
LT boards to block broadband traffic from interfering with narrowband traffic
and vice versa (that is, traffic received in the broadband path is not allowed to be
destined to a narrowband user and, vice versa, traffic received in the narrowband
path is not allowed to be destined to a broadband user).
• The ACLs will be built upon destination IP address/subnet and/or source IP
address/subnet.
Signaling traffic
Signaling traffic originates and terminates at the Voice server.
destination IP address of the packet, performs ARP for the next hop IP address and
forwards the IP packet appropriately.
The local SHub is configured as the next hop for signaling packets originating at the
Voice server.
The local SHub performs layer 3 forwarding in upstream and downstream direction.
Figure 8-27 Megaco ISAM Voice (routed): signaling forwarding

L3 forwarding Main node
Remote node
L3 forwarding NT board Signaling

NT board IP address Voice
SHub signaling
SHub network user IP XLES server
IP address address IP address
SHub network
SHub Voice IP address
Voice LT user IP Voice LT
board address board
L3 SHub Voice
aggregation user IP
network address
NT board NT board
SHub network
IP address

Voice LT user IP IP address Voice LT
board address board
Signaling
MGC ASP
SoftSwitch
XLES traffic
XLES traffic originates at the Voice server or at the Voice LT board and terminates
respectively at the Voice LT board or the Voice server.
• XLES traffic originating at the Voice server and destined to the Voice LT board:
The destined Voice LT is connected:
• to the local access node, or
• to an access node subtending to the local access node, or
• to an access node connected via a L3 aggregation network with the local access
node.
destination IP address of the packet, performs ARP for the next hop IP address /
destination IP address and forwards the IP packet appropriately.
The local SHub is configured as the next hop for the XLES packets originating at
the Voice server (in case the destined voice LT board connects to the local access
node, the local SHub IP address is equal to the destination IP address).
The (destined) SHub that connects the destined Voice LT board performs layer 3
followed by layer 4 forwarding.
• XLES traffic originating at the Voice LT board and destined to the Voice server:
The Voice LT board relays the XLES packet to the local SHub.
The access node of the Voice LT board and the access node of the Voice Server
are the same: the local SHub detects that the destination IP address of the packet
can directly be reached via the local subnet. The local Shub performs ARP for the
destination IP address and forwards the IP packet appropriately.
The access node of the Voice LT board subtends to the access node of the Voice
Server: The local SHub determines the IP next hop for the destination IP address
of the packet, performs ARP for the next hop IP address and forwards the IP
The access node of the Voice LT board is connected via a layer 3 aggregation
network to the access node of the Voice server: The local SHub determines the IP
next hop for the destination IP address of the packet , performs ARP for the next
hop IP address and forwards the IP packet appropriately.
The SHub that connects the Voice server performs layer 3 forwarding.
Figure 8-28 Megaco ISAM Voice - Routed: XLES packet originating at the Voice Server
L4 forwarding
Remote node

SHub signaling
SHub network L3 forwarding user IP XLES server
SHub network
board address board
L3 SHub Voice
aggregation user IP L4 forwarding
network address
NT board NT board
SHub network
IP address

board address board
L4 forwarding
L3 forwarding
MGC ASP
SoftSwitch
Figure 8-29 Megaco ISAM Voice - Routed: XLES packet forwarding at the Voice LT board.
L3 forwarding
Remote node

SHub signaling
SHub network
board address board
L3 SHub Voice
aggregation user IP
network address
NT board NT board
SHub network
IP address

board address board
L3 forwarding
MGC ASP
SoftSwitch
Voice traffic
Voice traffic originates at the Voice LT board and is destined to a voice termination
at the same Voice LT board, a voice termination at another Voice LT board in the
Voice cluster or a voice termination outside the voice cluster.
In some cases the voice traffic must be sent along the Voice server (as to support
some supplementary services or an optimized IP addressing scheme).
In all cases, voice traffic is relayed to the SHub prior to the forwarding to the destined
voice termination. This relay is either done by the Voice LT board (voice traffic that
does not pass the Voice server) or the Voice server (voice traffic that passes the voice
server).
A) Voice traffic not passing the Voice server.
• Voice traffic destined to a termination outside the voice cluster:
• The voice LT board forwards the upstream voice traffic to the local SHub.
• The local SHub determines the IP next hop for the voice traffic destination.
• The local Shub performs ARP for the next hop IP address and forwards the IP packet
appropriately.
• Voice traffic destined to a voice termination connected to the same Voice LT
board in the local access node:
• The Voice LT board relays the upstream voice traffic to the local SHub.
• The local SHub detects that the destination of the voice traffic equals the local Voice
IP address and treats the voice traffic locally.
• The local SHub performs layer 4 forwarding to the Voice LT voice from which the
voice traffic originated.
• Voice traffic destined to a voice termination connected to a different Voice LT

board in the local access node:
• The voice LT board relays the upstream voice traffic to the local SHub.
• The local SHub detects that the destination of the voice traffic equals the local Voice
IP address and treats the voice traffic locally.
destined voice termination is connected.
• Voice traffic destined to a voice termination connected to a Voice LT board in
another access node of the voice cluster:
• The local SHub determines the IP next hop for the destination of the voice traffic.
The local SHub performs ARP for the next hop IP address and forwards the voice
• The SHub that connects the destined voice termination (Voice LT board) performs
layer 3 forwarding followed by layer 4 forwarding.
B) Voice traffic passing the Voice server.

• Voice traffic destined to the Voice server:
• The local SHub determines the IP next hop for the Voice server, performs ARP for
the next hop IP address and forwards the voice traffic appropriately.
• In case the access node of the Voice LT board and the access node of the Voice
Server are the same, the local Shub performs ARP for the Voice server IP address
and forwards the IP packet appropriately.
• Voice traffic relayed by the Voice server to a voice termination connected to a
Voice LT board in the same access node:
• The Voice server invokes the NAPT facility and forwards the voice traffic along the
• The Voice server detects that the destination of the voice traffic is reachable within
the local subnet, performs ARP for the destination IP address and forwards the IP
• The local SHub performs layer 4 forwarding to the Voice LT board that connects the
Voice termination point.
• Voice traffic relayed by the Voice server to a voice termination connected to a
Voice LT board in another access node of the voice cluster:
appropriately.
• The Voice termination is connected to an access node subtending to the local access
node:
The Voice server invokes the NAPT facility and forwards the voice traffic along the
The Voice Server detects that the destination of the voice traffic is reachable within
the local subnet, performs ARP for the destination IP address and forwards the voice
• The SHub that connects the Voice termination (Voice LT board) performs layer 4
forwarding.
• Voice traffic relayed by the Voice server to a voice termination outside the voice
cluster:
appropriately.
Figure 8-30 Megaco ISAM Voice (routed): Voice packet originating at the LT board
L4 forwarding
Remote node L3 forwarding Main node

SHub signaling
SHub network
board address board
L3 SHub Voice
SHub
aggregation subtended user IP L3 forwarding
network IP address address
NT board NT board
SHub network
IP address

board address board
L3 forwarding L3 forwarding
L4 forwarding
MGC ASP
SoftSwitch
Figure 8-31 Megaco ISAM Voice (routed): Voice packet originating at the Voice server
L4 forwarding

SHub signaling
SHub network L3 forwarding user IP XLES server
SHub network
board address board
L3 SHub Voice
SHub
aggregation subtended user IP L3 forwarding
network IP address address
NT board NT board
SHub network
IP address

board address board
L3 forwarding
MGC ASP
SoftSwitch
OAM traffic
public OAM IP address of the ISAM access node hosting the Voice server.
Voice OAM traffic is distinguishable by a Voice specific SNMP community
string/context identifier from non-Voice OAM traffic and in addition distinguishable
through the same SNMP community string /context identifier amongst the Voice
server pairs (maximum eight) that may be hosted in the same ISAM access node.
Internally, the voice specific OAM traffic is relayed to the Voice server.
ISAM SNMP agent that forwards them to the customer's management platform.
SIP ISAM Voice as switching device
Signaling traffic
Signaling traffic originates at the Voice LT.
• Centralized SIP architecture = Single IP address:
• In the upstream direction: the Voice LT board forwards the signaling packet to the
local SHub. The Local SHub determines the IP next hop for the destination IP
address of the packet, performs ARP for the next hop IP address and forwards the
IP packet appropriately.
• In the downstream direction: upon the receipt of a signaling packet, the local SHub
performs layer 3 forwarding followed by layer 4 forwarding to the destined Voice
LT board.
Figure 8-32 SIP ISAM Voice (switched, centralized): Signaling packet originating at the
Voice LT/Upstream layer 3 forwarding at the SHub
L3 forwarding
NT board Signaling
XLES server
IP address
Voice LT SHub signaling Voice LT

SHub signaling
board IP address L2 IP address board
aggregation
network
NT board NT board
L3
aggregation
network
Voice LT Voice LT
SHub signaling SHub signaling
board IP address IP address board
S-CSCF L3 forwarding
I-CSCF
AS
IP
HSS IMS
MRF Core
Figure 8-33 SIP ISAM Voice (switched, centralized): Signaling packet destined to the
Voice LT/Downstream layer 4 forwarding at the SHub
Remote node L4 forwarding Main node
NT board NT board
L2 forwarding

Voice LT SHub signaling Voice LT

SHub signaling
board IP address L2 IP address board
aggregation
network
NT board NT board
L3
aggregation
network
Voice LT Voice LT
SHub signaling SHub signaling
board IP address IP address board
I-CSCF
AS
IP
HSS IMS
MRF Core
• Distributed SIP architecture = Multiple IP address:

• In the upstream direction: the Voice LT board determines the IP next hop for the
destination IP address of the packet and forwards the IP packet appropriately. Any
potential intermediate SHub performs layer 2 forwarding.
performs layer 2 forwarding to the destined Voice LT board.
Figure 8-34 SIP ISAM Voice (switched, distributed): Signaling packet originating at the
Voice LT/Upstream layer 3 forwarding at the Voice LT
L3 forwarding
L2 forwarding NT board
NT board
L2 forwarding
Signaling
IP address Signaling
IP address
Voice LT Voice LT
board L2 board
Voice aggregation
IP address Voice
network IP address
NT board NT board
L3
aggregation
Signaling network Signaling
Voice LT Voice LT
board board
Voice Voice
L2 forwarding
I-CSCF
AS
IP
HSS IMS
MRF Core
Figure 8-35 SIP ISAM Voice (switched, distributed): Signaling packet destined to the
Voice LT/Downstream layer 2 forwarding at the SHub
L2 forwarding NT board
NT board
L2 forwarding
Signaling
IP address Signaling
IP address
Voice LT Voice LT
board L2 board
Voice aggregation
IP address Voice
network IP address
NT board NT board
L3
aggregation
Signaling network Signaling
Voice LT Voice LT
board board
Voice Voice
L2 forwarding
S-CSCF
I-CSCF
AS
IP
HSS IMS
MRF Core
Voice traffic
For both the centralized as well as the distributed architecture, the forwarding of the
voice traffic in upstream as well as in downstream direction is identical as shown
above for the signaling traffic.
• Voice traffic exchanged between a local and a remote voice termination:
The forwarding behavior is identical to signaling traffic.
• Voice traffic exchanged between two voice terminations connected to the same
voice LT board:
The forwarding behavior depends on the destination IP address received from the
IMS core, for example, all the voice traffic might be forced to be forwarded along
a voice gateway.
Should the IMS core have decided that the voice traffic may be switched
internally in the access node then this voice traffic will be switched either
internally on the Voice LT board or along the local Shub depending on the Voice
LT board type being planned.
• Voice traffic exchanged between two voice terminations connected to different
voice LT boards in the same access node:
a voice gateway.
Anyhow, switching voice traffic between Voice Terminations, connected to the same
Voice LT board, along the local SHub is only possible in the centralized SIP
architecture, not in the distributed SIP architecture.
Centralized SIP architecture:
• The voice LT board forwards the voice packet to the local SHub.
the own Voice IP address. As such the packet is treated locally.
destined voice termination point is connected (that is, the Voice LT board from
which the voice packet originated).
Summarized, the SIP ISAM Voice forwards the voice traffic in accordance with the
destination IP address dictated by the SIP signaling and the Voice LT board type.
OAM traffic
management IP address of the ISAM access node hosting the Voice server.
Any potential intermediate SHub performs layer 2 forwarding and this in both
directions.
SIP ISAM Voice as routing device
Security considerations
The SHub supports only a single fast path VRF. As a result, access nodes that are
deployed in mixed mode (that is, narrowband services and broadband services are
concurrently deployed by the same access node) must include protections that
guarantee that data is kept secret against unwanted, unintended and malicious
listeners and this for both the narrowband services and the broadband services.
This can be achieved as follows:
• At the network side of the VRF, the broadband data path is separated from the
narrowband data path by configuring different VLANs for these different data
paths (= different IP subnets).
In this respect, path protection can be guaranteed by the routing protocols
(different areas).
• At the user side of the VRF, ACLs need to be installed at the ports connection the
LT boards to block broadband traffic from interfering with narrowband traffic
and vice versa (that is, traffic received in the broadband path is not allowed to be
destined to a narrowband user and, vice versa, traffic received in the narrowband
path is not allowed to be destined to a broadband user).
• The ACLs will be built upon destination IP address/subnet and/or source IP
address/subnet.
Signaling traffic
Signaling traffic originates at the Voice LT.
• Centralized SIP architecture = Single IP address:
• In the upstream direction: the Voice LT board forwards the signaling packet to the
local SHub. The Local SHub determines the IP next hop for the destination IP
address of the packet, performs ARP for the next hop IP address and forwards the
IP packet appropriately.
performs layer 3 forwarding followed by layer 4 forwarding to the destined Voice
LT board.
Figure 8-36 SIP ISAM Voice (routed, centralized): Signaling packet originating at the
Voice LT/Upstream layer 3 forwarding at the SHub
L3 forwarding
L3 forwarding
NT board SHub netw. SHub netw. NT board
Signaling Signaling SHub user
SHub user
IP address IP address Signaling
Signaling
IP address
IP address
SHub netw.
Voice LT Voice Voice LT
board SHub netw. IP address
SHub user SHub user
board
Voice
Voice IP address Voice
L3
IP address SHub IP address
aggregation subtending
network IP address
NT board SHub netw. NT board

SHub user Signaling
Signaling IP address
IP address SHub dignaling
IP address
Voice LT Voice LT
SHub Voice
board SHub netw. IP address board
SHub user Voice
Voice IP address
IP address
I-CSCF
AS
IP
HSS IMS
MRF Core
Figure 8-37 SIP ISAM Voice (routed, centralized): Signaling packet destined to the Voice
LT/Downstream layer 4 forwarding at the SHub
L3 forwarding
L3 forwarding
NT board SHub netw. SHub netw. NT board
Signaling Signaling SHub user
SHub user
IP address IP address Signaling
Signaling
IP address
IP address
SHub netw.
SHub user SHub user
board
Voice
L3
IP address SHub IP address
network IP address
NT board SHub netw. NT board

SHub user Signaling
Signaling IP address
IP address SHub dignaling
IP address
Voice LT Voice LT
SHub Voice
board SHub netw. IP address board
SHub user Voice
Voice IP address
IP address
I-CSCF
AS
IP
HSS IMS
MRF Core
• Distributed SIP architecture = Multiple IP address:

• In the upstream direction: the Voice LT board determines the IP next hop for the
destination IP address of the packet and forwards the IP packet appropriately.
performs layer 3 forwarding to the destined Voice LT board.
Figure 8-38 SIP ISAM Voice (routed, distributed): Signaling packet originating at the
Voice LT/Upstream layer 3 forwarding at the Voice LT
L3 forwarding
L3 forwarding
SHub user NT board SHub netw. SHub netw. NT board SHub user
Signaling Signaling Signaling Signaling
IP address IP address IP address IP address
Signaling Signaling
SHub netw.
SHub user
board
SHub user Voice
Voice Voice Voice
Voice IP address L3
IP address
IP address SHub IP address IP address
network IP address
SHub user NT board SHub netw. NT board

Signaling Signaling
Signaling Signaling
Voice LT Voice LT
board SHub netw. board
SHub user Voice
IP address Voice IP address
IP address
S-CSCF L2 forwarding L3 forwarding
I-CSCF
AS
IP
HSS IMS
MRF Core
Figure 8-39 SIP ISAM Voice (routed, distributed): Signaling packet destined to the Voice
LT/Downstream layer 2 forwarding at the SHub
L3 forwarding
L3 forwarding
SHub user NT board SHub netw. SHub netw. NT board SHub user
Signaling Signaling Signaling Signaling
IP address IP address IP address IP address
Signaling Signaling
SHub netw.
SHub user
board
SHub user Voice
Voice Voice Voice
Voice IP address L3
IP address
IP address SHub IP address IP address
network IP address
SHub user NT board SHub netw. NT board

Signaling Signaling
Signaling Signaling
Voice LT Voice LT
board SHub netw. board
SHub user Voice
IP address Voice IP address
IP address
I-CSCF
AS
IP
HSS IMS
MRF Core
Voice traffic
For both the centralized as well as the distributed architecture, the forwarding of the
voice traffic in upstream as well as in downstream direction is identical as shown
above for the signaling traffic.
• Voice traffic exchanged between a local and a remote voice termination:
The forwarding behavior is identical to signaling traffic.
• Voice traffic exchanged between two voice termination connected to the same
voice LT board:
a voice gateway.
Should the IMS core have decided that the voice traffic may be switched
internally in the access node then this voice traffic will be switched either
internally on the Voice LT board or along the local Shub depending on the Voice
LT board type being planned.
• Voice traffic exchanged between two voice termination connected to different
voice LT boards in the same access node:
a voice gateway.
Anyhow, switching voice traffic between Voice Terminations, connected to the same
Voice LT board, along the local SHub is only possible in the centralized SIP
architecture, not in the distributed SIP architecture.
Centralized SIP architecture:
• The voice LT board forwards the voice packet to the local SHub.
the own Voice IP address. As such the packet is treated locally.
destined voice termination point is connected (that is, the Voice LT board from
which the voice packet originated).
Summarized, the SIP ISAM Voice forwards the voice traffic in accordance with the
destination IP address dictated by the SIP signaling and the Voice LT board type.
OAM traffic
management IP address of the ISAM access node hosting the Voice server.
8.7 Layer 2/layer 3 addressing topologies
Megaco ISAM Voice as switching device

Three addressing topologies are supported for Megaco ISAM Voice:
• Basic layer 2/layer 3 addressing topology
• IP subnet reduction topology
• IP subnet and IP address reduction topology
The following is common to all three addressing topologies:
• Equipment and platform management entity is hosted at the NT
• Integrated Voice service Management entity is hosted at the Voice server
• Media gateway is hosted at the Voice server
• External communication VLAN carries the external management traffic
• Public OAM IP interface is configured at the NT
• External communication VLAN: see chapter “Management”
• Public OAM IP address: see chapter “Management”
Basic layer 2/layer 3 addressing topology

The following applies for the basic layer 2/layer 3 addressing topology:
• A distinct VLAN is configured for signaling and Voice/XLES traffic.
• The public Voice IP interface is configured at the SHub.
• The public signaling IP interface is configured at the Voice server.
• The public XLES IP interface is configured at the Voice server.
• Upstream packet forwarding:
• Signaling traffic and XLES traffic originating at the Voice server: layer 3
forwarding at the Voice server and layer 2 forwarding at the SHub.
• Voice/XLES traffic originating at the Voice LT board: Voice/XLES packet
internally relayed from the Voice LT to the SHub and layer 3 forwarding at the
SHub.
• Downstream packet forwarding:
• Signaling traffic and XLES traffic destined to the Voice server is layer 2 forwarded
at the SHub.
• Voice/XLES traffic destined to the Voice LT board is layer 4 forwarded from the
SHub to the Voice LT.
• Signaling VLAN:
The VLAN is of “iBridge” mode and configurable.
Ports associated with this VLAN are the ASAM port(s) connecting the Voice
server and the network port(s).
The signaling VLAN terminates at the Voice server and carries the Megaco and
SIGTRAN signaling traffic exchanged between the MGC (Call Server)/ ASP
(Application Server Process) and the MG (ISAM Voice).
• Voice/XLES VLAN:
The VLAN is of “Voice-VLAN” mode and configurable.
server, the ASAM port(s) connecting the Voice LT, subtending port(s), and
network port(s).
The VLAN terminates at both the Voice server and the Voice LT and carries:
• RTP traffic exchanged between end users.
• RTCP traffic.
• XLES traffic (internal signaling, control and management) exchanged between the
Voice server and the Voice LT.
The basic layer 2/layer 3 addressing topology is shown in the following figures:
• For a hub ISAM Voice, see Figure 8-40
• For a subtending ISAM Voice, see Figure 8-41
• For a remote ISAM Voice, see Figure 8-42
Figure 8-40 Basic layer 2/layer 3 addressing topology - hub ISAM Voice (switching)
MG
In te r n a l O AM VLAN
Vo ice Se r ve r 1
Exte r n a l O AM VLAN
MG
IACM
Vo ice Se r ve r N
SIG N ALIN G VLAN
Vo ice LT 1
SHu b
NT
VO ICE VLAN
Public O AM IP Address
Public Signa ling IP Address
Public Voice / XLES IP Address
Priva te O AM IP Address
Vo ice LT M
Public Voice IP Address
Figure 8-41 Basic layer 2/layer 3 addressing topology - subtending ISAM Voice
(switching)
IACM
Vo ice LT 1
SHu b
NT
VO ICE VLAN
Public Voice IP Address Vo ice LT M
Figure 8-42 Basic layer 2/layer 3 addressing topology - remote ISAM Voice (switching)
IACM
Vo ice LT 1
SHu b
NT
VO ICE VLAN
Public Voice IP Address Vo ice LT M
Relying on the former layer 2 forwarding scheme, the layer 3 IP address scheme
looks then as follows:
• Public signaling IP address:
• Residing at the Voice server.
• Single IP address shared by a redundant pair of Voice servers.
• Configurable
• Public Voice IP address:
• Single IP address per ISAM Voice access node.
• Residing at the SHub.
• Configurable
• Public XLES IP address:
• Shared by a redundant pair of Voice servers.
• Configurable.
IP subnet reduction topology

This model intends to reduce the number of IP subnets (that is, the total amount of
reserved IP addresses), required for the voice service.
• A single, shared VLAN is used for signaling and Voice/XLES traffic.
• The public Voice IP interface is configured at the SHub.
• A single, shared public signaling/XLES IP interface is configured at the Voice
server.
• Voice/XLES traffic originating at the Voice LT board: Voice/XLES packet
internally relayed from Voice LT to SHub and layer 3 forwarding at the SHub.
• Signaling traffic traffic and XLES traffic destined to the Voice server is layer 2
forwarded at the SHub.
• Voice/XLES traffic destined to the Voice LT board is layer 4 forwarded from the
SHub to the Voice LT.
• Shared signaling/Voice/XLES VLAN:
server, the ASAM port(s) connecting the Voice LT, Subtending port(s) and the
network port(s).
The shared VLAN terminates at the Voice server and the Voice LT and carries:
• Megaco and SIGTRAN signaling traffic exchanged between the MGC (Call
Server)/ ASP (Application Server Process) and the MG (ISAM Voice)
• RTP traffic exchanged between end users
• RTCP traffic
The basic layer 2/layer 3 addressing topology with IP subnet reduction is shown in
the following figures:
• For a hub ISAM Voice, see Figure 8-43.
• For a subtending ISAM Voice, see Figure 8-44.
• For a remote ISAM Voice, see Figure 8-45.
Figure 8-43 IP subnet reduction - hub ISAM Voice (switching)
MG
Vo ice Se r ve r 1
MG
IACM
Vo ice Se r ve r N
Shared SIG N ALIN G/VOICE VLAN
Vo ice LT 1
SHu b
NT
Public shared Signaling/Voice/XLES IP Address
Vo ice LT M
Figure 8-44 IP subnet reduction - subtending ISAM Voice (switching)
IACM
Vo ice LT 1
SHu b
NT
Public OAM IP Address

Vo ice LT M
Figure 8-45 IP subnet reduction - remote ISAM Voice (switching)
IACM
Vo ice LT 1
SHu b
NT

Vo ice LT M
Relying on the former layer 2 forwarding scheme, the layer 3 IP address scheme then
looks as follows:
• Shared public signaling/XLES IP address:
• Configurable.

• Configurable.
IP subnet and IP address reduction

This model further reduces the total amount of public IP addresses, required for the
integrated voice service.
Note — For topologies that contain remote ISAM Voice access

nodes, 2 options are possible:
• Case A: the remote ISAM Voice is associated with the public
signaling/Voice/XLES VLAN. In this case a public voice IP
interface is configured at the SHub of the remote ISAM Voice
access node.
• Case B: the remote ISAM Voice is associated with the private
Voice/XLES VLAN. In this case a private voice IP interface is
configured at the SHub of the remote ISAM Voice access node.
• A single, shared public VLAN is used for (case A) signaling/Voice/XLES or
(case B) signaling/Voice traffic.
• A single, shared private VLAN is used for Voice/XLES traffic.
• A shared public (case A) signaling/Voice/XLES or (case B) signaling/Voice IP
interface is configured at the Voice server.
• A private voice IP interface is configured at the SHub.
• A private XLES IP interface is configured at the Voice server.
• Upstream packet forwarding in shared VLAN for signaling and Voice/XLES
traffic:
• Signaling traffic originating at the Voice server: layer 3 forwarding at the Voice
server and layer 2 forwarding at the SHub.
• Voice/XLES traffic originating at the Voice server: layer 3 forwarding at the Voice
server and layer 2 forwarding at the SHub.
• Voice/XLES traffic originating at the ISAM Voice (Figure 8-48 - CASE A):
Voice/XLES packet internally relayed from the Voice LT to the SHub and layer 3
forwarding at the SHub.
• Downstream packet forwarding in shared VLAN for signaling and Voice/XLES
traffic:
• Signaling traffic destined to the Voice server: layer 2 forwarding at the SHub.
• Voice/XLES traffic destined to the Voice server: layer 2 forwarding at the SHub.
• Voice/XLES traffic destined to Voice LT board in remote ISAM Voice (Figure 8-48
- CASE A): layer 4 forwarding from the SHub to the Voice LT board.
• Upstream packet forwarding in the private Voice VLAN:
• Voice/XLES traffic:
Voice/XLES packet internally relayed from Voice LT to the SHub and layer 3
• Downstream packet forwarding in the private Voice VLAN:
• Voice/XLES traffic:
layer 4 forwarding from the xHub to the Voice LT.
• Case A: Shared public signaling/Voice/XLES VLAN:

The VLAN is of “Residential Bridge” mode in the Hub ISAM Voice and of
“Voice-VLAN” mode in the Remote ISAM Voice, and configurable.
server in the Hub ISAM Voice, the ASAM port(s) connecting the voice LT
boards in the remote ISAM Voice, and the network port(s).
The shared VLAN terminates at the Voice server and at the Voice LT in the
Remote ISAM Voice nodes. It carries:
Server)/ ASP (Application Server Process) and the MG (ISAM Voice).
• RTP traffic originated from or destined to end users connected to a remote ISAM
Voice node.
• RTP traffic originated from an external end user and destined to an end user
connected to the hub node or subtending node.
• RTP traffic originated from an end user connected to the hub or Subtending node
and destined to an external end user.
• RTCP traffic
Voice server and the Voice LT hosted in the remote ISAM Voice node.
• Case B: Shared public signaling/Voice VLAN:
The VLAN is of “Residential Bridge” mode in the Hub ISAM Voice and
configurable.
server in the Hub ISAM Voice and the network port(s).
The shared VLAN terminates at the Voice server. It carries:
connected to the Hub node, Subtending node or Remote node.
• RTP traffic originated from an end user connected to the Hub, Subtending or
Remote node and destined to an external end user.
• RTCP traffic.
• Private Voice VLAN:
The VLAN is of “Voice-VLAN” mode and is configurable.
server, the ASAM port(s) connecting the Voice LT and the subtending port(s).
The private Voice VLAN terminates at the Voice server and the Voice LT and the
SHub of the Hub, the Subtending (Case B) and/or Remote ISAM Voice node. It
carries:
• RTP traffic originated or destined to end users connected to the hub and subtending
ISAM Voice nodes.
• RTCP traffic.
Voice server and the Voice LT residing in the Hub, the Subtending (Case B) and/or
the Remote ISAM Voice node.
The basic layer 2/layer 3 addressing topology with IP subnet reduction and IP
address reduction is shown in the following figures:
Figure 8-46 IP subnet and IP reduction - hub ISAM Voice (switching)

MG
Vo ice Se r ve r 1
MG
IACM
Vo ice Se r ve r N
Private VOICE/XLES VLAN
Vo ice LT 1
SHu b
NT
Shared SIGNALING/VO ICE VLAN
Private Voice IP Address
Public shared Signaling/Voice / XLES IP Address
Vo ice LT M
Private XLES IP Address
Figure 8-47 IP subnet and IP reduction - subtending ISAM Voice (switching)

IACM
Private VOICE/XLES VLAN
Vo ice LT 1
SHu b
NT
Vo ice LT M
Figure 8-48 IP subnet and IP address reduction - remote ISAM Voice (switching)
CASE A
IACM
Vo ice server N
Shared SIGNALLING/VO ICE VLAN
Vo ice LT 1
SHu b
NT

Vo ice LT M
CASE B
IACM
Vo ice server N
Shared SIGNALLING/VO ICE VLAN
Vo ice LT 1
SHu b
NT

Vo ice LT M
looks as follows:
• Shared public signaling/Voice/XLES IP address:
• Configurable.
• Public Voice IP address (for remote ISAM Voice node):
• Configurable.
• Private Voice IP address (for hub ISAM Voice node and subtending ISAM Voice
node):
• Configurable.
• Private XLES IP address (for hub ISAM Voice node):
• Configurable.
Megaco ISAM Voice as routing device

Three addressing topologies are supported for Megaco ISAM Voice as routing
device:
• Basic layer 3 addressing topology
• IP subnet reduction topology
• IP subnet and IP address reduction topology
The following is common to all three forwarding models:
• Equipment and platform management entity is hosted at the NT
• Integrated Voice service Management entity is hosted at the Voice server
• Media gateway is hosted at the Voice server
• External communication VLAN carries the external management traffic (see
chapter “Management”)
• Public OAM IP interface is configured at the NT (see chapter “Management”)
Basic layer 3 addressing topology

The following applies for the basic layer 3 addressing topology:
• Distinct user side VLANs for signaling traffic and for Voice/XLES traffic are
configured at the user side of the fast path VRF.
• Distinct network side VLANs for signaling traffic and for Voice/XLES traffic are
configured at the network side of the fast path VRF.
• A distinct user side subtending VLAN for Voice/XLES traffic exchanged with
the subtending ISAM Voice is configured at the user side of the fast path VRF.
• The public Voice IP interface is configured at the user side of the fast path VRF
at the SHub.
• The public signaling IP interface is configured at the Voice server.
• The public XLES IP interface is configured at the Voice server.
• A user-side next hop IP interface is configured on top of the user side signaling
VLAN at the user side of the fast path VRF.
• A network-side next hop IP interface is configured on top of both the
network-side signaling VLAN and the network-side Voice/XLES VLAN at the
network side of the fast path VRF.
• A user-side next hop IP interface is configured on top of the user side subtending
• Voice traffic and XLES traffic originating at the Voice LT board: the Voice/XLES
packet is internally relayed from the Voice LT board to the SHub and layer 3
• Voice traffic and XLES traffic originating at the subtending interface: layer 3

• Signaling traffic and XLES traffic destined to the Voice server: layer 3 forwarded at
the SHub.
• Voice traffic and XLES traffic destined to the Voice LT: layer 3 followed by layer
4 forwarded from the SHub to the Voice LT board.
• Voice traffic and XLES traffic destined to the subtending interface: layer 3
• Signaling VLAN at the user side of the fast path VRF:
server(s).
The signaling VLAN terminates at the SHub/Voice server and carries the Megaco
and SIGTRAN signaling traffic exchanged between the MGC (Call Server)/ ASP
(Application Server Process) and the MG (ISAM Voice).
• Voice/XLES VLAN at the user side of the fast path VRF:
The VLAN is of “Voice-VLAN” mode, and configurable.
server and the ASAM port(s) connecting the Voice LT board.
The VLAN terminates at the SHub and both, the Voice server and the Voice LT
board and carries:
• RTP traffic exchanged between end users.
• RTCP traffic.
Voice server and the Voice LT board).
• Subtending Voice/XLES VLAN at the user side of the fast path VRF:
The VLAN is of “iBridge” mode and configurable
Ports associated with this VLAN are the subtending port(s).
The VLAN terminates at the SHub and the Voice LT board(s) connecting to the
subtending ISAM Voice and carries:
• RTCP traffic
• XLES traffic exchanged between the Voice server and the subtending Voice LT
board(s)
The basic layer 3 addressing topology is shown in the following figures:

• For a hub ISAM Voice, see Figure 8-49
• For a subtending ISAM Voice, see Figure 8-50
• For a remote ISAM Voice, see Figure 8-51
Figure 8-49 Basic layer 2/layer 3 addressing topology - hub ISAM Voice (routing)
MG
Internal OAM VLAN
Voice Server 1
External OAM VLAN

MG
SIGNALING VLAN Voice Server N
Network VLAN Fast-path VRF
Voice LT 1
Network VLAN
NT
Voice LT M
Subtending
VLAN
VOICE VLAN
Public OAM IP address Public Voice IP address

Public Signaling IP address Network IP address
Public Voice /XLES IP address User IP address
Private OAM IP address Subtending IP address
Figure 8-50 Basic layer 2/layer 3 addressing topology - subtending ISAM Voice (routing)
External OAM VLAN
Fast-path VRF
Voice LT 1
NT
Subtending VLAN
Public OAM IP address

Public Voice IP address Voice LT M
Figure 8-51 Basic layer 2/layer 3 addressing topology - remote ISAM Voice (routing)
External OAM VLAN
Voice LT 1
NT
VOICE VLAN
Network IP address Voice LT M
The layer 3 IP address scheme looks then as follows:

• Public signaling IP address:
• Configurable
• Single IP address per ISAM Voice access node configured at the user side of the fast
path VRF.
• Configurable
• Public XLES IP address:
• Configurable.
• Signaling path:
• User-side next hop IP address configured at the user side of the fast path VRF
(SHub)
• Network-side next hop IP address configured at the network side of the fast path
VRF (SHub)
• Voice / XLES path:
Network-side next hop IP address configured at the network side of the fast path
VRF (SHub)
(SHub) for the subtending link.
IP subnet reduction topology

This model intends to reduce the number of IP subnets (that is, the total amount of
reserved IP addresses), required for the integrated voice service.
• The same user-side VLAN is shared by signaling and Voice/XLES traffic and
• The same network-side VLAN is shared by signaling and Voice/XLES traffic and
configured at the network side of the fast path VRF.
• The public Voice IP interface is configured at the user side of the fast path VRF
at the SHub.
• A shared public signaling/XLES IP interface is configured at the Voice server.
• A distinct-user side subtending VLAN for Voice/XLES traffic exchanged with
the subtending ISAM Voice is configured at the user side of the fast path VRF.
• A network-side next hop IP interface is configured on top of the network side
signaling/ Voice/XLES VLAN at the network side of the fast path VRF.
• A user-side next hop IP interface is configured on top of the user-side subtending
• Signaling traffic and XLES traffic originating at the Voice server : layer 3
• Voice/XLES traffic originating at the Voice LT: Voice/XLES packet internally
relayed from Voice LT board to SHub and layer 3 forwarding at the SHub.
• Voice/XLES traffic originating at the subtending interface: layer 3 forwarding at the
SHub.
• Signaling traffic and XLES traffic destined to the Voice server: layer 3 forwarded at
the SHub.
• Voice traffic and XLES traffic destined to the Voice LT: layer 3 followed by layer
4 forwarded from the SHub to the Voice LT board.
• Voice traffic and XLES traffic destined to the subtending interface: layer 3
• Shared signaling/Voice/XLES VLAN at the user side of the fast path VRF:
server and the ASAM port(s) connecting the Voice LT.
The shared VLAN terminates at the SHub/Voice server and the Voice LT board
and carries:
Server)/ ASP (Application Server Process) and the MG (ISAM Voice)
• RTCP traffic
• RTCP traffic
• XLES traffic exchanged between the Voice server and the subtending Voice LT
board(s)
The basic layer 3 addressing topology with IP subnet reduction is shown in the
following figures:
Figure 8-52 IP subnet reduction - hub ISAM Voice (routing)
MG
Internal OAM VLAN
Voice Server 1
External OAM VLAN

MG
Shared SIGNALING
Voice Server N
/VOICE VLAN
Voice LT 1
NT
Subtending
VLAN
Public OAM IP Address Private OAM IP Address Voice LT M

Public Voice IP Address Network IP address
Public shared Signaling/Voice/XLES Subtending IP address
IP Address
Figure 8-53 IP subnet reduction - subtending ISAM Voice (routing)
External OAM VLAN
VOICE VLAN
Fast-path VRF
Voice LT 1
NT

Voice LT M
Figure 8-54 IP subnet reduction - remote ISAM Voice (routing)
External OAM VLAN
Voice LT 1
NT
VOICE VLAN
Network IP address Voice LT M
The layer 3 IP address scheme then looks as follows:

• Shared public signaling/XLES IP address:
• Configurable.
path VRF at the SHub.
• Configurable.
• Signaling/Voice path:
• Network-side next hop IP address configured at the network side of the fast path
VRF (SHub
IP subnet and IP address reduction

This model further reduces the total amount of public IP addresses, required for the
integrated voice service.
• A single public VLAN shared by signaling/Voice/XLES is configured at the user
side of the fast path VRF
• A private VLAN for Voice/XLES traffic is configured at the user side of the fast
path VRF (Applies to the HUB and subtending ISAM Voice only)
• A network-side VLAN shared by signaling/Voice/XLES is configured at the
• A single public IP interface shared by signaling/Voice/XLES IP interface is
configured at the Voice server.
• A private voice IP interface is configured at the user side of the fast path VRF at
the SHub.
• A private XLES IP interface is configured at the Voice server.
• A distinct user side private subtending VLAN for Voice/XLES traffic exchanged
with the subtending ISAM Voice is configured at the user side of the fast path
VRF.
• A network-side next-hop IP interface is configured on top of the network side
signaling/ Voice/XLES VLAN at the network side of the fast path VRF.
• A user-side next-hop IP interface is configured on top of the user side

signaling/Voice/XLES VLAN at the user side of the fast path VRF.
• A user-side next-hop IP interface is configured on top of the user side subtending
• Upstream packet forwarding in shared VLAN for signaling/Voice/XLES traffic:
• Signaling traffic and XLES traffic + Voice traffic originating at the Voice server:
layer 3 forwarding at the Voice server and layer 3 forwarding at the SHub.
• Voice traffic and XLES traffic originating at the Remote ISAM Voice: Voice/XLES
packet is internally relayed from the Voice LT board to the SHub and layer 3
• Downstream packet forwarding in shared VLAN for signaling/Voice/XLES
traffic
• Signaling traffic, XLES traffic and Voice traffic destined to the Voice server: layer
3 forwarding at the SHub.
• Voice traffic and XLES traffic destined to the Voice LT board (Remote ISAM
Voice): layer 3 followed by layer 4 forwarding from the SHub to the Voice LT
board.
• Upstream packet forwarding in the private Voice VLAN (HUB / Subtending
ISAM Voice only):
Voice traffic and XLES traffic originating at the voice LT board: Voice/XLES
packet is internally relayed from Voice LT board to the SHub and layer 3
• Downstream packet forwarding in the private Voice VLAN (HUB / Subtending
ISAm Voice only):
Voice traffic and XLES traffic destined to the voice LT: layer 3 followed by layer
4 forwarding from the SHub to the Voice LT board.
• Shared public signaling/Voice/XLES VLAN at the user side of the fast path VRF:
The VLAN is of “Residential Bridge” mode in the Hub ISAM Voice and of
“Voice-VLAN” mode in the remote ISAM Voice, and configurable.
server in the Hub ISAM Voice and the ASAM port(s) connecting the voice LT
board boards in the remote ISAM Voice.
The shared VLAN terminates at the SHUB / Voice server and at the Voice LT
board in the Remote ISAM Voice nodes. It carries:
• RTP traffic originated from or destined to end users connected to a remote ISAM
Voice node.
connected to the hub node or subtending node.
• RTP traffic originated from an end user connected to the hub or Subtending node
and destined to an external end user.
• RTCP traffic.
Voice server and the Voice LT board hosted in the remote ISAM Voice node.
• Private Voice VLAN:
server and the ASAM port(s) connecting the Voice LT.
The private Voice VLAN terminates at the SHUB, Voice server and the Voice
LT. It carries:
• RTP traffic originated or destined to end users connected to the Hub, Subtending
(Case B:) and/or Remote ISAM Voice nodes.
• RTCP traffic.
Voice server and the Voice LT board residing in the Hub, the Subtending (Case B)
and/or the Remote ISAM Voice node.
• RTCP traffic
• XLES traffic exchanged between the Voice server and the subtending Voice LT(s)
The basic layer 3 addressing topology with IP subnet reduction and IP address
reduction is shown in the following figures:
Figure 8-55 IP subnet and IP reduction - hub ISAM Voice (routing)
MG
Internal OAM VLAN
Shared SIGNALING/VOICE VLAN Voice Server 1
External OAM VLAN

MG
Voice Server N
Private VOICE VLAN
Fast-path VRF
Network VLAN
Voice LT 1
NT
Voice LT M
Subtending
VLAN
Public OAM IP Address Private XLES IP Address
Private Voice IP Address Network IP address
Public shared Signaling/XLES IP Address User IP address
Private OAM IP Address Subtending IP address
Figure 8-56 IP subnet and IP reduction - subtending ISAM Voice (routing)

External OAM VLAN
Private VOICE VLAN

Fast-path VRF
Voice LT 1
NT

Voice LT M
Figure 8-57 IP subnet and IP address reduction - remote ISAM Voice (routing)
External OAM VLAN
Shared SIGNALLING
/VOICE VLAN
Voice server N
Voice LT 1
NT

Network IP address
Voice LT M

• Shared public signaling/Voice/XLES IP address:
• Configurable.
• Public Voice IP address (for remote ISAM Voice node):
path VRF.
• Configurable.
• Private Voice IP address (for hub ISAM Voice node and subtending ISAM Voice
node):
path VRF.
• Configurable.
• Private XLES IP address (for hub ISAM Voice node):
• Configurable.
• Public Signaling / Voice path:
Network-side next hop IP address configured at the network side of the fast path
VRF (HUB and Remote SHub).
User-side next hop IP address configured at the user side of the fast path VRF
(HUB SHub).
SIP ISAM Voice as switching device

Four addressing topologies are supported:
• Distributed IP address topology - shared signaling/Voice IP address.
• Distributed IP address topology - distinct signaling/Voice IP address.
• Centralized IP address topology - distinct signaling/Voice IP address.
• Centralized IP address topology - shared signaling/Voice IP address.
The following is common to all four addressing topologies:

• Equipment, platform and integrated voice service management entity is hosted at
the NT.
• A SIP UA instance is hosted at the Voice LT.
• The external communication VLAN carries the external management traffic (see
chapter “Management”).
• The public OAM IP interface is configured at the NT (see chapter
“Management”).
Distributed IP address topology - shared signaling/Voice IP address
• A single VLAN shared by signaling traffic and by Voice traffic is configured at

the SHub.
• A single source/destination IP interface shared by signaling traffic and by Voice
traffic is configured at the voice LT board.
• Layer 3 forwarding of signaling/Voice packet at the Voice LT board.
• Layer 2 forwarding of signaling/Voice packet at the SHub.
• Layer 2 forwarding of signaling/Voice packet from subtending to network side.
• Shared signaling/Voice VLAN:

Ports associated with this VLAN are the ASAM port(s) connecting the Voice LT,
the network port(s) and the subtending port(s).
The shared signaling/Voice VLAN terminates at the Voice LT and carries:
• SIP signaling traffic exchanged between the SIP server and the SIP UA (ISAM
Voice).
• RTP traffic exchanged between end-users.
• RTCP traffic.
Figure 8-58 shows the layer 3 addressing topology for this model.
Figure 8-58 Distributed IP address topology (switching): shared signaling/voice IP

address
SIP UA
Voice LT 1
OAM VLAN
SIP UA
Voice LT K
Shared SIGNALING/VOICE VLAN
Fast-path VRF SIP UA
Voice LT L
NT SIP UA
OAM IP Address
Shared signaling/Voice IP Address
Voice LT X
Subtending
node
looks as follows:
• Signaling/Voice IP interface:
• Configurable at the Voice LT.
• Multiple IP address per ISAM Voice access node.
Distributed IP address topology - distinct signaling/Voice IP address
• Distinct VLANs are configured for signaling traffic and for Voice traffic at the
SHub.
• Distinct IP interfaces for signaling traffic and for Voice traffic are configured at
the Voice LT board.
• Signaling VLAN:
The signaling VLAN terminates at the Voice LT board and carries the SIP
signaling traffic exchanged between the SIP server and the SIP User Agent
(ISAM Voice).
• Voice VLAN:
The Voice VLAN terminates at the Voice LT and carries the RTP traffic
exchanged between end users and RTCP traffic.
Figure 8-59 shows the layer 2/layer 3 addressing topology for this model.
Figure 8-59 Distributed IP address topology (switching): distinct signaling/voice IP

address
SIP UA
External OAM VLAN Voice LT 1
SIP UA
SIGNALING VLAN
Fast-path VRF Voice LT K
SIP UA
Voice LT L
VOICE VLAN
NT SIP UA

Public Signaling IP Address
Voice LT X
Subtending
node
looks as follows:
• signaling IP interface:
• Configurable at the Voice LT board.
• Voice IP address:
Centralized IP topology - distinct signaling/Voice IP address
SHub.
the SHub.
• Signaling/Voice packet is internally relayed from Voice LT board to SHub
• Layer 4 forwarding of signaling/Voice packet from the SHub to the Voice LT board.
• Layer 2 forwarding of signaling/Voice packet from network to subtending side.
• Signaling VLAN:
Ports associated with this VLAN / V_VPLS are the ASAM port(s) connecting the
Voice LT, the network port(s) and the subtending port(s).
(ISAM Voice).
• Voice VLAN:
The Voice VLAN terminates at the Voice LT and carries the RTP traffic
exchanged between end users and RTCP traffic.
Figure 8-60 Centralized IP address topology (switching): distinct signaling/voice IP

address
SIP UA
Voice LT 1
External OAM VLAN

SIP UA
Voice LT K
SIGNALING VLAN
Fast-path VRF
SIP UA
Voice LT L
VOICE VLAN SIP UA
NT
Voice LT X

Public Signaling IP Address
Public Voice IP Address Subtending
node
looks as follows:
• Signaling IP address:
• Configurable at the SHub.
• Shared by a redundant pair of SHubs.
Centralized IP address topology - shared signaling/Voice IP address

the SHub.
• A single IP interface shared by signaling traffic and by Voice traffic is configured
at the SHub.
• Layer 4 forwarding of signaling/Voice packet from the SHub to the Voice LT board.
• Shared signaling/Voice VLAN:
The signaling/Voice VLAN terminates at the Voice LT board and carries:
Voice).
• RTCP traffic.
Figure 8-61 Centralized IP address topology (switching): shared signaling/voice IP

address
SIP UA
Voice LT 1
External OAM VLAN
SIP UA

Voice LT K
Fast-path VRF
SIP UA
NT Voice LT L
OAM IP Address
Shared Signaling/Voice IP Address
SIP UA
Subtending Voice LT X
node
looks as follows:
• Shared signaling/Voice IP interface:
• Single IP interface per ISAM Voice access node.
SIP ISAM Voice as routing device

Four addressing topologies are supported:
• Distributed IP address topology - shared signaling/Voice IP address.
• Distributed IP address topology - distinct signaling/Voice IP address.
• Centralized IP address topology - distinct signaling/Voice IP address.
• Centralized IP address topology - shared signaling/Voice IP address.
The following is common to all four addressing topologies:

• Equipment, platform and integrated voice service management entity is hosted at
the NT.
• A SIP UA instance is hosted at the Voice LT.
• The external communication VLAN carries the external management traffic (see
chapter “Management”).
• The public OAM IP interface is configured at the NT (see chapter
“Management”).
• Different VLANs at the network side and at the user side of the fast path VRF.
Distributed IP address topology - shared signaling/Voice IP address

the user side of the fast path VRF.
the network side of the fast path VRF.
• A single IP interface shared by signaling traffic and by Voice traffic is configured
at the voice LT board.
• A single subtending VLAN shared by signaling traffic and by Voice traffic is
• A next hop IP interface is configured on top of the signaling/voice VLAN at the
user side of the fast path VRF.
• A next hop IP interface is configured on top of the subtending VLAN at the user
side of the fast path VRF.
• Signaling/Voice VLAN at the user side of the fast path VRF:
Ports associated with this VLAN are the ASAM port(s) connecting the Voice LT.
The signaling/Voice VLAN terminates at the Voice LT and carries:
Voice).
• RTCP traffic.
• Subtending signaling/Voice VLAN at the user side of the fast path VRF:
The user-side signaling/Voice VLAN terminates at the Voice LT(s) connected to
the subtending ISAM Voice and carries:
Voice).
• RTCP traffic.
Figure 8-62 shows the layer 3 addressing topology for this model.
Figure 8-62 Distributed IP address topology (routing): shared signaling/voice IP address

SIP UA
Voice LT 1
OAM VLAN
SIP UA
Voice LT K
Network VLAN Voice LT L
Network VLAN
NT SIP UA
OAM IP Address
Network IP address
Voice LT X
User IP address
Subtending
Subtending IP address node

• Signaling/Voice IP interface:
• Configurable at the Voice LT.
• Multiple IP interfaces per ISAM Voice access node.
• User-side signaling/voice VLAN: next-hop IP interface configured at the user
side of the fast path VRF (SHub)
• Network-side signaling/voice VLAN: next-hop IP interface configured at the
network side of the fast path VRF (SHub)
• User-side subtending signaling/voice VLAN: next-hop IP interface configured at
the user side of the fast path VRF (SHub)
Distributed IP address topology - distinct signaling/Voice IP address
the Voice LT board.
• Distinct subtending VLANs for signaling traffic and for Voice traffic are
• A next hop IP interface is configured on top of the signaling VLAN at the user
• A next hop IP interface is configured on top of the voice VLAN at the user side
of the fast path VRF.
• A next hop IP interface is configured on top of the signaling VLAN at the network
• A next hop IP interface is configured on top of the voice VLAN at the network
• A next hop IP interface is configured on top of the subtending signaling VLAN
at the user side of the fast path VRF.
• A next hop IP interface is configured on top of the subtending voice VLAN at the
• Signaling VLAN at the user side of the fast path VRF:
(ISAM Voice).
• Voice VLAN at the user side of the fast path VRF:
The Voice VLAN terminates at the Voice LT and carries the:
• RTCP traffic.
• Subtending VLAN for signaling and voice at the user side of the fast path VRF:
These VLANs are of “iBridge” mode and configurable.
The subtending signaling/Voice VLAN terminates at the Voice LT(s) connected
to the subtending ISAM Voice and carries:
• SIP signaling traffic exchanged between the SIP server and the SIP User
Agent (ISAM Voice).
• RTCP traffic.
Figure 8-63 Distributed IP address topology (routing): distinct signaling/voice IP address

SIGNALING VLAN
SIP UA
VOICE VLAN
Voice LT 1
External OAM VLAN

SIP UA
Voice LT K
Fast-path VRF
SIP UA
Voice LT L
Network VLAN
Network VLAN SIP UA
NT
OAM IP Address
Voice LT X
User IP Address
User IP Address
Network IP Address
Subtending IP Address
Subtending IP Address Subtending
Signalling IP Address node
Voice IP Address

• Signaling IP interface:
• Multiple IP interfaces per ISAM Voice access node.
• User-side signaling VLAN and user-side Voice VLAN: next-hop IP interface
configured at the user side of the fast path VRF (SHub).
• Network-side signaling VLAN and network-side Voice VLAN: next-hop IP
interface configured at the network side of the fast path VRF (SHub).
• User-side subtending signaling VLAN and user-side subtending voice VLAN:
next-hop IP interface configured at the user side of the fast path VRF (SHub).
Centralized IP topology - distinct signaling/Voice IP address
• Distinct VLANs for signaling traffic and for Voice traffic are configured at the
• Distinct VLANs for signaling traffic and for Voice traffic are configured at the
the user side of the VRF at the SHub.
• Distinct subtending VLANs for signaling traffic and for Voice traffic are
• A next hop IP interface is configured on top of the signaling VLAN at the network
• A next hop IP interface is configured on top of the voice VLAN at the network
• A next hop IP interface is configured on top of the subtending signaling VLAN
at the user side of the fast path VRF.
• A next hop IP interface is configured on top of the subtending voice VLAN at the
• Layer 3 followed by layer 4 forwarding of signaling/Voice packet from the SHub to
the Voice LT board.
• Signaling VLAN:
(ISAM Voice).
• Voice VLAN at the user side of the fast path VRF:
The Voice VLAN terminates at the Voice LT and carries:
• RTCP traffic.
• Subtending VLANs for signaling and Voice at the user side of the fast path VRF:
The subtending signalling/ Voice VLAN terminates at the Voice LT board
connected to the subtending ISAM Voice and carries:
Voice)
• RTCP traffic.
Figure 8-64 shows the topology for this model.
Figure 8-64 Centralized IP address topology (routing): distinct signaling/voice IP address

SIGNALING VLAN
SIP UA
VOICE VLAN
Voice LT 1
External OAM VLAN

SIP UA
Voice LT K
Fast-path VRF
SIP UA
Voice LT L
Network VLAN
Network VLAN SIP UA
NT
OAM IP Address
Voice LT X
Signaling IP Address
Voice IP Address
Network IP Address
Subtending IP Address
Subtending IP Address Subtending
node

• Signaling IP address:
• Configurable at the SHub (user-side fast path VRF).
• Configurable at the SHub (user side fast path VRF).
• Network-side signaling VLAN and network-side Voice VLAN: next-hop IP
• User-side subtending signaling VLAN and user-side subtending voice VLAN:
next-hop IP interface configured at the user side of the fast path VRF (SHub).
Centralized IP address topology - shared signaling/Voice IP address

the user side of the fast path VRF.
the network side of the fast path VRF.
• A single IP interface is configured at the user side of the VRF at the SHub.
• A single subtending VLAN shared by signaling traffic and by Voice traffic is

• A next hop IP interface is configured on top of the subtending VLAN at the user
• Signaling/Voice packet is internally relayed from Voice LT to SHub.
• Layer 3 followed by layer 4 forwarding of signaling/Voice packet from the SHub to
the Voice LT board.
• Signaling/Voice VLAN at the user side of the fast path VRF:
The signaling/Voice VLAN terminates at the Voice LT and carries:
Voice).
• RTCP traffic.
• Subtending signaling/Voice VLAN at the user side of the fast path VRF:
The subtending signaling/Voice VLAN terminates at the Voice LT(s) connected
to the subtending ISAM Voice and carries:
Voice).
• RTCP traffic.
Figure 8-65 shows the addressing topology for this model.
Figure 8-65 Centralized IP address topology (routing): shared signaling/voice IP address

SIP UA
Voice LT 1
OAM VLAN
SIP UA
Voice LT K
Network VLAN Voice LT L
Network VLAN
NT SIP UA
OAM IP Address
Network IP address
Voice LT X
User IP address
Subtending
Subtending IP address node

• Shared signaling/Voice IP interface:
• Configurable at the SHub (user side fast path VRF).
• Single IP interface per ISAM Voice access node.
• Network-side VLAN sharing signaling traffic and voice traffic: next-hop IP
• User-side subtending VLAN sharing signaling traffic and voice traffic: next-hop
IP interface configured at the user side of the fast path VRF (SHub).
8.8 Protocol stacks
Megaco ISAM Voice Signaling Protocol Stack (Switching / Routing

Both POTS and ISDN BRI lines are supported.
H.248 and SIGTRAN signaling packets are exchanged between the MG (Voice
server) and the MGC (Call Server). The XLES proprietary protocol is used to
exchange internal signaling packets between the Voice server and the Voice LT
boards residing in the hub, subtending or remote ISAM Voice access nodes.
H.248 and XLES signaling packets are encapsulated with UDP, IP and layer 2
frames. SIGTRAN signaling packets are encapsulated with SCTP, IP and layer 2
frames. The layer 2 frames are formatted according to Ethernet II format (that is,
using the type field) and VLAN 802.1Q tagged including priority setting according
to IEEE 802.1p.
H.248, SIGTRAN and XLES signaling packets include configured DSCP and .1P
values.
Figure 8-66 shows the H.248 signaling protocol stack for a POTS termination
connected directly to the hub ISAM Voice. The Z interface is terminated at the Voice
LT. User events like hook off, hook on and so on are converted into XLES/LAPV5
packets which are sent to the Voice server. The Voice server in turn converts the
internal proprietary XLES/LAPV5 protocol into Megaco messages sent to the MGC.
Figure 8-66 POTS signaling protocol stack - hub ISAM Voice (switching)
Hub ISAM Voice
XLES XLES
H.248 H.248
LapV5 LapV5
UDP UDP UDP UDP
IP IP IP IP IP
L3 IP
802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q

Generic Generic
Z Itf Z Itf
PHY PHY
802.3 802.3 802.3 802.3 802.3 802.3
Termination Voice LT Voice Server SHub EMAN Edge Router MGC
Figure 8-67 POTS signaling protocol stack - hub ISAM Voice (routing)
Hub ISAM Voice
XLES XLES
H.248 H.248
LapV5 LapV5
UDP UDP UDP UDP
IP IP IP IP IP IP
L3 IP
802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q

Generic Generic
Z Itf Z Itf
PHY PHY
802.3 802.3 802.3 802.3 802.3 802.3
For POTS terminations connected to a remote or subtending ISAM Voice, the Z

interface is terminated at the Voice LT residing at the remote or subtending ISAM
Voice. Information transfer between the remote or subtending ISAM Voice and the
hub ISAM Voice happens through the proprietary XLES/LAPV5 protocol that is
terminated at the Voice server. The Voice server in turn converts the internal
proprietary XLES/LAPV5 protocol into Megaco messages sent to the MGC.
Figure 8-68 POTS signaling protocol stack - subtending ISAM Voice (switching)
Subtending ISAM Voice Hub ISAM Voice
XLES XLES
H.248 H.248
LapV5 LapV5
UDP UDP UDP UDP
IP IP IP IP IP
L3 IP
802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q

Generic Generic
Z Itf Z Itf
PHY PHY
802.3 802.3 802.3 802.3 802.3 802.3 802.3 802.3
Termination Voice LT SHub SHub Voice Server SHub EMAN Edge Router MGC
Figure 8-69 POTS signaling protocol stack - subtending ISAM Voice (routing)
XLES XLES
H.248 H.248
LapV5 LapV5
UDP UDP UDP UDP
IP IP IP IP IP IP IP
L3 IP
802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q

Generic Generic
Z Itf Z Itf
PHY PHY
802.3 802.3 802.3 802.3 802.3 802.3 802.3 802.3
Figure 8-70 POTS signaling protocol stack - remote ISAM Voice (switching)
Remote ISAM Voice Hub ISAM Voice
XLES XLES
H.248 H.248
LapV5 LapV5
UDP UDP UDP UDP
IP IP IP IP IP
L3 IP
802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q

Generic Generic
Z Itf Z Itf
PHY PHY
802.3 802.3 802.3 802.3 802.3 802.3 802.3 802.3 802.3
Termination Voice LT SHub EMAN SHub Voice Server SHub EMAN Edge Router MGC
Figure 8-71 POTS signaling protocol stack - remote ISAM Voice (routing)
XLES XLES
H.248 H.248
LapV5 LapV5
UDP UDP UDP UDP
IP IP IP IP IP
L3 IP
IP IP IP
802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q

Generic Generic
Z Itf Z Itf
PHY PHY
802.3 802.3 802.3 802.3 802.3 802.3 802.3 802.3 802.3
For ISDN BRI terminations, the Voice server behaves as the signaling Gateway
(SG). It communicates with the ASP through the SIGTRAN protocol. The D-channel
layer 2 protocol (Q.921) is terminated at the Voice LT. The D-channel layer 3
protocol (Q.931) is fully transparent to the Voice server. Q.931 is encapsulated with
SIGTRAN and fully transparently forwarded to the ASP.
The ISAM Voice still acts as the MG for the call control in calls involving
B-channels.
Figure 8-72 ISDN BRI signaling protocol stack - hub ISAM Voice (switching)
Hub ISAM Voice
Q931 Q931
XLES XLES
IUA IUA
Q921 Q921 LapV5 LapV5
UDP UDP SCTP SCTP
IP IP IP IP IP
L3 IP
I410 I410 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q

Generic
PHY
802.3 802.3 802.3 802.3 802.3 802.3 802.3
Figure 8-73 ISDN BRI signaling protocol stack - hub ISAM Voice (routing)
Hub ISAM Voice
Q931 Q931
XLES XLES
IUA IUA
UDP UDP SCTP SCTP
IP IP IP IP IP IP
L3 IP
I410 I410 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q

Generic
PHY
802.3 802.3 802.3 802.3 802.3 802.3 802.3
For ISDN BRI Terminations connected to a remote or subtending ISAM Voice, the
D-channel layer 2 protocol (Q.921) is terminated at the Voice LT residing at the
remote or subtending ISAM Voice. Information transfer between the remote or
subtending ISAM Voice and the hub ISAM Voice happens through the proprietary
XLES/LAPV5 protocol that is terminated at the Voice server. The Voice server in
turn converts the internal proprietary XLES/LAPV5 protocol into SIGTRAN
messages sent to the ASP.
Figure 8-74 ISDN BRI signaling protocol stack - subtending ISAM Voice (switching)
Q931 Q931
XLES XLES
H.248 IUA
UDP UDP UDP

L3 SCTP
IP IP IP IP IP IP
I410 I410 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q
Generic
PHY
802.3 802.3 802.3 802.3 802.3 802.3 802.3 802.3 802.3
Figure 8-75 ISDN BRI signaling protocol stack - subtending ISAM Voice (routing)
Q931 Q931
XLES XLES
H.248 IUA
UDP UDP UDP

L3 SCTP
IP IP IP IP IP IP IP IP
I410 I410 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q
Generic
PHY
802.3 802.3 802.3 802.3 802.3 802.3 802.3 802.3 802.3
Figure 8-76 ISDN BRI signaling protocol stack - remote ISAM Voice (switching)
Q931 Q931
XLES XLES
H.248 IUA
UDP UDP UDP L3 SCTP
IP IP IP IP IP IP
I410 I410 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q
Generic
PHY
802.3 802.3 802.3 802.3 802.3 802.3 802.3 802.3 802.3 802.3
Figure 8-77 ISDN BRI signaling protocol stack - remote ISAM Voice (routing)
Q931 Q931
XLES XLES
H.248 IUA
UDP UDP UDP L3 SCTP
IP IP IP IP IP IP IP IP IP
I410 I410 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q 802.1Q
Generic
PHY
802.3 802.3 802.3 802.3 802.3 802.3 802.3 802.3 802.3 802.3
SIP ISAM Voice Signaling Protocol Stack (Switching / Routing)

Only POTS lines are supported.
SIP signaling packets are exchanged between the Voice gateway and the SIP server.
All signaling packets are encapsulated with UDP, IP and layer 2 frames. The layer 2
frames are formatted according to Ethernet II format (that is, using the type field) and
VLAN 802.1Q tagged including priority setting according to IEEE 802.1p.
SIP signaling packets will include configured DSCP and .1P values.
Figure 8-78, Figure 8-79, Figure 8-80, Figure 8-81, Figure 8-82 and Figure 8-83
show the SIP signaling protocol stack for a POTS termination for the different
architectures. The Z interface is terminated at the Voice LT board. User events like
hook off, hook on, and so on are converted into SIP messages sent to the SIP server.
Figure 8-78 POTS signaling protocol stack - distributed architecture (switching)

Hub ISAM Voice
SIP SIP
UDP UDP
IP IP IP
L3 IP
802.1Q 802.1Q 802.1Q 802.1Q

Generic Generic
Z Itf Z Itf
PHY PHY
802.3 802.3 802.3 802.3
Termination Voice LT SHub EMAN Edge Router TGW
Figure 8-79 POTS signaling protocol stack - distributed architecture (routing)

Hub ISAM Voice
SIP SIP
UDP UDP
IP IP IP IP
L3 IP
802.1Q 802.1Q 802.1Q 802.1Q

Generic Generic
Z Itf Z Itf
PHY PHY
802.3 802.3 802.3 802.3
Figure 8-80 POTS signaling protocol stack - centralized architecture - upstream

(switching)
Hub ISAM Voice
SIP SIP
UDP UDP
IP IP IP IP
L3 IP
802.1Q 802.1Q 802.1Q 802.1Q

Generic Generic
Z Itf Z Itf
PHY PHY
802.3 802.3 802.3 802.3
Figure 8-81 POTS signaling protocol stack - centralized architecture - upstream

(routing)
Hub ISAM Voice
SIP SIP
UDP UDP
IP IP IP IP
L3 IP
802.1Q 802.1Q 802.1Q 802.1Q

Generic Generic
Z Itf Z Itf
PHY PHY
802.3 802.3 802.3 802.3
Figure 8-82 POTS signaling protocol stack - centralized architecture - downstream

(switching)
Hub ISAM Voice
SIP SIP
UDP UDP UDP
IP IP IP IP
L3 IP
802.1Q 802.1Q 802.1Q 802.1Q

Generic Generic
Z Itf Z Itf
PHY PHY
802.3 802.3 802.3 802.3
Figure 8-83 POTS signaling protocol stack - centralized architecture - downstream

(routing)
Hub ISAM Voice
SIP SIP
UDP UDP UDP
IP IP IP IP IP
L3 IP
802.1Q 802.1Q 802.1Q 802.1Q 802.1Q

Generic Generic
Z Itf Z Itf
PHY PHY
802.3 802.3 802.3 802.3 802.3
Voice protocol stack

Voice traffic, using Real-Time Protocol (RTP) providing the information needed to
restore the original digital voice stream, is encapsulated in UDP/IP. The same
encapsulation method is applied to Real-Time Control Protocol (RTCP), the control
protocol associated to RTP.
The encapsulated voice traffic (RTP/RTCP) includes a configurable DSCP and .1P
bit value. As a result the voice packets can use separate queues in the layer 2/layer 3
network to minimize delay and jitter.
Figure 8-84 MEGACO POTS Voice protocol stack - Upstream - Switching model
Hub ISAM Voice
RTP RTP
UDP UDP
IP IP IP IP
L3 IP
802.1Q 802.1Q 802.1Q 802.1Q

Generic Generic
Z Itf Z Itf
PHY PHY
802.3 802.3 802.3 802.3
Figure 8-85 MEGACO Voice protocol stack - Upstream - Routing model
Hub ISAM Voice
RTP RTP
UDP UDP
IP IP IP IP
L3 IP
802.1Q 802.1Q 802.1Q 802.1Q

Generic Generic
Z Itf Z Itf
PHY PHY
802.3 802.3 802.3 802.3
Figure 8-86 MEGACO POTS Voice protocol stack - Downstream - Switching model
Hub ISAM Voice
RTP RTP
UDP UDP UDP
IP IP IP IP
L3 IP
802.1Q 802.1Q 802.1Q 802.1Q

Generic Generic
Z Itf Z Itf
PHY PHY
802.3 802.3 802.3 802.3
Figure 8-87 MEGACO Voice protocol stack - Downstream - Routing model

Hub ISAM Voice
RTP RTP
UDP UDP UDP
IP IP IP IP IP
L3 IP
802.1Q 802.1Q 802.1Q 802.1Q 802.1Q

Generic Generic
Z Itf Z Itf
PHY PHY
802.3 802.3 802.3 802.3 802.3
Figure 8-88 SIP POTS Voice protocol stack - Distributed Architecture - Switching model
Hub ISAM Voice
RTP RTP
UDP UDP
IP IP IP
L3 IP
802.1Q 802.1Q 802.1Q 802.1Q

Generic Generic
Z Itf Z Itf
PHY PHY
802.3 802.3 802.3 802.3
Termination Voice LT SHub EMAN Edge Router MGC
Figure 8-89 SIP POTS Voice protocol stack - Distributed Architecture - Routing model
Hub ISAM Voice
RTP RTP
UDP UDP
IP IP IP IP
L3 IP
802.1Q 802.1Q 802.1Q 802.1Q

Generic Generic
Z Itf Z Itf
PHY PHY
802.3 802.3 802.3 802.3
Figure 8-90 SIP POTS Voice protocol stack - Centralised Architecture - Upstream -
Switching model
Hub ISAM Voice
RTP RTP
UDP UDP
IP IP IP IP
L3 IP
802.1Q 802.1Q 802.1Q 802.1Q

Generic Generic
Z Itf Z Itf
PHY PHY
802.3 802.3 802.3 802.3
Figure 8-91 SIP Voice protocol stack - Centralised Architecture - Upstream - Routing
model
Hub ISAM Voice
RTP RTP
UDP UDP
IP IP IP IP
L3 IP
802.1Q 802.1Q 802.1Q 802.1Q

Generic Generic
Z Itf Z Itf
PHY PHY
802.3 802.3 802.3 802.3
Figure 8-92 SIP Voice protocol stack - Centralised Architecture - Downstream -

Switching model
Hub ISAM Voice
RTP RTP
UDP UDP UDP
IP IP IP IP
L3 IP
802.1Q 802.1Q 802.1Q 802.1Q

Generic Generic
Z Itf Z Itf
PHY PHY
802.3 802.3 802.3 802.3
Figure 8-93 SIP Voice protocol stack - Centralised Architecture - Downstream - Routing
model
Hub ISAM Voice
RTP RTP
UDP UDP UDP
IP IP IP IP IP
L3 IP
802.1Q 802.1Q 802.1Q 802.1Q 802.1Q

Generic Generic
Z Itf Z Itf
PHY PHY
802.3 802.3 802.3 802.3 802.3
8.9 Management interface
MEGACO ISAM Voice
CLI / SNMP
The SNMPV3 agent hosted at the Voice Server serves as the management interface
for the integrated VoIP service. However, neither CLI nor SNMP commands can
directly be addressed to the Voice Server. (The Integrated VoIP service cannot be
managed by means of TL1, although, one exception, the retrieval of the VoIP service
alarms through TL1 is supported.)
All CLI or SNMP commands to manage the integrated VoIP service are addressed
to the public OAM IP address of the access node and are subsequently relayed to the
correct Voice Server by means of the “voice server context name” present in the
management command.
A Voice server context name is mapped to a private IP address, out of the range
127.0.0.11 to 127.0.0.26. The private IP address is assigned to a Voice Server. This
IP address to Voice Server mapping is fixed and based on the physical slot position
of the Voice Server.
SNMP commands, carrying a “voice server context name”, are addressed to the NT
SNMP agent which in turn relays the command to the destined Voice Server.
CLI commands, carrying a “voice server identifier”, are addressed to the NT CLI
agent, where it becomes translated into the appropriate SNMP command and
forwarded to the NT SNMP agent. The NT SNMP agent in turn relays the SNMP
command to the destined Voice Server.
DHCP
DHCP is not supported for Megaco ISAM Voice.
Batch configuration CLI command support for subscriber management

A subscriber is a logical entity managed by the MG that sources and/or sinks media
and/or control streams. Subscriber have unique identities, called “TerminationIDs”
assigned by the MG at the time of their creation. The ISAM Voice allows to make
use of 3 different formats for the “TerminationID”:
• The FLAT termination ID:
Typical Format: 'prefix<tidXXXXX>'
• The LEGACY HIERARCHICAL termination ID:
Typical format: “Prefix/Dslam_Id/rack/shelf/slot/port(/channel”
• The IMPROVED HIERARCHICAL termination ID:
Typical format: “Prefix/Dslam_Id/rackXXXXX/shelfXXXXX/slotXXXXX/
portXXXXX/channel”
In case the customer decides to make use of the FLAT termination ID format, then
such termination id is to be configured for each of the terminations.
The FLAT termination ID can be provisioned in two different ways:
• By initiating a single “create” command per termination and provisioning the
value for the Flat Termination ID.
• By initiating a batch “create” command for a series of terminations (typically
within the limits of a voice LT board). In this case, the operator doesn't provision
a value for the Flat termination ID parameter. The system autonomously creates
the terminations for a voice LT board and assigns autonomously the value of the
Flat Termination ID, starting from 1 or previously successfully completed
“create” command and increment it by 1 for every subsequent termination being
created.
If the customer decides to make use of the HIERARCHICAL termination ID format,

then the desired pattern is to be configured once and the system will autonomously
create the appropriate hierarchical termination id for each of the terminations.
It must be noted, that in this case also the flat termination ID is to be configured for
each of the terminations as this is still internally used by ISAM Voice.
SIP ISAM Voice
CLI / SNMP
The Integrated VoIP Service Management interface is fully supported by the SNMP
and CLI agents that reside at the NT.
All CLI or SNMP commands to manage the integrated VoIP service are addressed
to the public OAM IP address of the access node.
The integrated VoIP service cannot be managed by means of TL1. Only the retrieval
of the VoIP service alarms through TL1 is supported.
DHCP
DHCP is not supported for the SIP centralised model.
The SIP Distributed model allows configuring the SIP UA address parameters to be
retrieved through a DHCP request. DHCP options 1 (subnet mask), 3 (default route),
and 6 (DNS server IP address) are supported.
8.10 Permanent data storage
Megaco ISAM Voice

The VoIP service permanent data is archived by the VoIP database(s) stored on the
system disk. The system maintains a separate voice database for each of the Voice
Servers. Up to 8 VoIP database(s) may be present on the system disk.
The voice database is managed by the integrated voice service management entity
hosted at the Voice Server. At regular time, each Voice Server uploads its voice
database to the system disk.
SIP ISAM Voice

The VoIP permanent data is archived by the VoIP database stored on the system disk.
The VoIP database is managed by integrated voice service management entity hosted
at the NT board.
8.11 Management model
Megaco ISAM Voice

Figure 8-94 shows the Megaco ISAM Voice conceptual management model.
Figure 8-94 Megaco ISAM Voice Conceptual Management Model

Read-only H.248 Protocol and Network Management Model
Read-Write
Equipment Equipment
Base Class Board 1..24 Node
1
1 0..32
1
File Input 0..72 1 1
1
H.248 0..5000 Voice XLES
Termination Server
1 1 1
0..1 0..1 1 0..1

1..N 1..N 1
POTS ISDN Media
Line Line Gateway
0..72 0..24 1
1 1 0..1
POTS ISDN Signaling Line Id Syntax
LT Board LT Board Gateway 1..2 Profile
Voice
LT Board
1 1
LT Board POTS ISDN Voice Server

CDE Profile CDE Profile CDE Profile
NT Board CDE Profile
VoIP NarrowBand Line Test Management Model
Line Test
Session Voice Server
Parameters 1..1024 1
1 1
1 1
1..72 1
Available
Line Identity Session
1..N
Session
Report
VoIP Database Model
VoIP Database Voice Server

1 1
• The classes “SYSTEM”, “NT”, “LT Board” and “Voice Server” reflect the
Access Node, the Network Termination, the Line Termination and Voice server
hardware being involved in the integrated voice service. These classes are not
further elaborated in subsequent sections.
• The class “Voice LT Board” is an instantiation of the class “LT Board”. This class
is not further elaborated in subsequent sections.
• The classes “POTS LT Board” and “ISDN LT Board” are instantiations of the
class “Voice LT Board”. This class is not further elaborated in subsequent
sections.
• The classes “POTS Line” and “ISDN Line” are instantiations of the class “H.248
Termination”. The class “H.248 Termination” is elaborated in subsequent
sections.
• The classes “POTS CDE Profile”, “ISDN CDE Profile” and “Voice Server CDE”
are instantiations of the class “CDE Profile”. The class “POTS CDE Profile” is
elaborated in subsequent sections.
H.248 Protocol and Network Management Model.

This management model offers the capability to provision the Voice Cluster, the
Media and Signaling gateway as well as the network related H.248 protocol
parameters.
A Voice Cluster is the aggregation of the ISAM Voice network elements controlled
by a single Voice Server (pair). The entire Voice Cluster is provisioned by means of
the following 2 classes:
• The class “EquipmentNode” includes the attributes and methods that allow the
provisioning of the ISAM Voice access nodes that belong to the voice cluster.
• The class “EquipmentBoard” includes the attributes and methods that allow the
provisioning of the Voice LT boards that belong to each of the access nodes in the
voice cluster.
The class “Media Gateway” includes the attributes and methods that allow the
provisioning of the H.248 protocol, L2 and L3 network connection and the network
redundancy parameters as well as the quality of service characteristics for the
signaling as well as the voice stream.
The class “H.248 Termination” includes the attributes and methods that allow the
provisioning of the individual POTS or ISDN termination characteristics.
The class “XLES” includes the attributes and methods that allow provisioning of the
internal Voice cluster signaling characteristics.
The class “Signaling Gateway” includes the attributes and methods that allow the
provisioning of the L3/L4 and network redundancy characteristics of the Assignment
Source Point (ASP).
The Class “Line Id Syntax Profile” includes the attributes and methods that allow the
provisioning of the POTS and / or ISDN termination ID format.
The classes “POTS CDE Profile”, “ISDN CDE Profile” and “Voice Server CDE
Profile” include the attributes and methods that allow the provisioning of the
physical subscriber line, the Z-interface, the tone pattern, the protocols that run at the
end user side and LT board hardware characteristics.
VoIP Database Model

The class “VoIP Database” includes the attributes and methods that allow managing
the SIP Voice Database.
VoIP Narrowband Line Test Management Model

The class “Available Session” includes the attributes and methods to schedule a new
narrowband line test session.
The class “Session” includes the attributes and methods that allow the provisioning
of the narrowband line test session characteristics.
The class “Line Identity” includes the attributes and methods that allow the
provisioning of the subscriber lines involved in the narrowband line test session.
The class “Line Test Parameters” includes the attributes and methods that allow the
provisioning of the parameters to be considered in the course of a narrowband line
test session.
The class “Session Report” includes the attributes and methods that allow retrieving
the results of the completed narrowband line test session.
SIP ISAM Voice

The following figures show the SIP ISAM Voice conceptual management models.
Figure 8-95 SIP ISAM Voice - Statistics and Counters Management Model
Read-only File Input
Read-Write Base Class

SIP Per-Line Stats
Termination 1 1 Current 15 min
Per-Line Stats
Per-Board Stats History 15 min
Current 15 min 96
Per-Line Stats
Per-Board Stats
1 Current 1 day
History 15 min
Per-Line Stats
Per-Board Stats Line Termination
3 History 1 day
Current 1 day 1 Board
Per-Call Stats
Per-Board Stats
History 15 min
History 1 day 0..N
TCA
Threshold
CPU Load 1
1
Per-Line
Performance
Memory Resource 1 Monitoring Info
Occupation 1
Subscriber Line
Performance System Availability
1 1
Monitoring Info 1
Stats
1 Configuration
Figure 8-96 SIP Protocol and Network Management model
VSP SIP
Dial Plan
1 0..N Termination
1 1
1 1 0..1
1..256
1 1
Digit Map
POTS
SIP Timers Line
N
SIP Server
1..N 1
NAPTR
1..N Resource Record
POTS
DNS Server MIB LT Board
0..6 SRV
Readiness
1..N Resource Record
ONLY
Session Timer A 1
0..1 1..N Resource Record Voice
LT Board
Line Id Syntax
Profile User Agent
1
Access Point 0..1
1..18 LT
Transport Board
Protocols 1..2 1
1
User Agent
Registration
1
NT
MIB
Network DHCP
Authentication Readiness
Redundancy 1 ONLY
1
Figure 8-97 VoIP services management model
SIP
VSP
0..N Termination
1 1
1 0..1
1
POTS
Line
N
1 1
POTS CDE POTS

Profile 1 LT Board
1..N
CDE Voice
Profile 1 LT Board
1..N
SIP LT
Service Profile 1 Board
1
NT
Figure 8-98 VoIP Narrowband Line Test model and VoIP database model
VoIP NarrowBand Line Test Model
Line Test
Session NT
Parameters 1..1024 1..16
1 1
1 1
1..72 1..16
Available
Line Identity Session
1..N
Session
Report
VoIP Database Model
VoIP Database NT
1 1
• The classes “SYSTEM”, “NT”, “LT Board” reflect the Access Node, the
Network Termination, and the Line Termination hardware being involved in the
integrated voice service. These classes are not further elaborated in subsequent
sections.
• The class “Voice LT Board” is an instantiation of the class “LT Board”. This class
is not further elaborated in subsequent sections.
• The class “POTS LT Board” is an instantiation of the class “Voice LT Board”.
This class is not further elaborated in subsequent sections.
• The class “POTS Line” is an instantiation of the class “SIP Termination”. The
class “SIP Termination is elaborated in subsequent sections.
• The class “POTS CDE Profile” is an instantiation of the class “CDE Profile”. The
class “POTS CDE Profile” is elaborated in subsequent sections.
Statistics and Counters Management Model

This management model offers the capability to provision the TCA thresholds as
well as to retrieve the SIP termination availability, the SIP termination voice and
board resource occupancy statistics and counters.
The class “TCA Threshold” includes the attributes and methods that allow the
provisioning of the threshold crossing alarms on a per SIP termination.
The class “Per-Line Stats Current 15 min” includes the attributes and methods that
allow retrieving the per-line measured values during the current 15-minutes interval.
The class “Per-Line Stats History 15 min” includes the attributes and methods that
allow retrieving the per-line measured values for the past 96 15-min intervals.
The class “Per-Line Stats Current 1 day” includes the attributes and methods that
allow retrieving the per-line measured values during the current 1-day interval.
The class “Per-Line Stats History 1 day” includes the attributes and methods that
allow retrieving the per-line measured values for the past three 1-day intervals.
The class "Per-Board Stats Current 15 min" includes the attributes and methods that
allow retrieving the per-board measured values during the current 15-minutes
interval.
The class "Per-Board Stats History 15 min" includes the attributes and methods that
allow retrieving the per-board measured values for the past 96 15-min intervals.
The class "Per-Board Stats Current 1 day" includes the attributes and methods that
allow retrieving the per-board measured values during the current 1-day interval.
The class "Per-Board Stats History 1 day" includes the attributes and methods that
allow retrieving the per-board measured values for the past 3 1-day intervals.
The class “Per-Call Stats History 15 min” includes the attributes and methods that
allow retrieving the per-call measured values for the past 96 15-minutes intervals.
The class “CPU Load” includes the attributes and methods that allow retrieving the
CPU occupancy during the past 180 s time period at the Line termination / Network
termination board.
The class “Memory Resource Occupation” includes the attributes and methods that
allow retrieving the actual dynamic memory resource allocation at the Line
termination / Network termination board.
The class “Subscriber Line Availability”: includes the attributes and methods that
allow retrieving the actual service state of the subscriber lines.
The class “Per-Line Performance Monitoring Info” includes the attributes and
methods that allow retrieving the validity of the measured data during the several
intervals.
The class "Per-Board Performance Monitoring Info" includes the attributes and
methods that allow retrieving the validity of the measured data during the several
intervals.
The class "Stats Configuration" includes the attributes and methods that allow to:
• enable/disable performance monitoring overall
• identify an “incoming call” / “outgoing call” during performance monitoring.
SIP Protocol and Network Management Model

This management model offers the capability to provision the access gateway as well
as the network related SIP protocol parameters.
The class “VSP” includes the attributes and methods that allow the provisioning of
the Voice Service Provider properties.
The class “SIP Timers” includes the attributes and methods that allow the
provisioning of the SIP protocol timers.
The class “Dial Plan” includes the attributes and methods that allow the provisioning
of the dial plan that applies to the network of the Voice Service Provider.
The class “Digit Map” includes the attributes and methods that allow the
provisioning of the Digit Map that applies to the network of the Voice Service
Provider.
The class “SIP Server” includes the attributes and methods that allow the
provisioning of the (list of) SIP server(s) being installed in the network of the Voice
Service Provider.
The Class “DNS Server” includes the attributes and methods that allow the
provisioning of the (list of) DNS server(s) being installed in the network of the Voice
Service Provider.
The Class “Session Timer” includes the attributes and methods that allow the
provisioning of the Session Timer extension of the SIP protocol.
The Class “Line Id Syntax Profile” includes the attributes and methods that allow the
provisioning of the POTS termination ID format.
The Class “Transport Protocols” includes the attributes and methods that allow the
provisioning of the transport protocols the SIP User Agent must listen to for
incoming SIP requests.
The Class “Registration” includes the attributes and methods that allow the
provisioning of the SIP Register Method behavior in the network of the Voice
Service Provider.
The Class “Network Redundancy” includes the attributes and methods that allow the
provisioning of the Voice Service Provider's network redundancy characteristics
together with the expected SIP User Agent redundancy behavior.
The Classes “User Agent” and “User Agent Access Point” includes the attributes and
methods that allow the provisioning of the L2 and L3 network connection together
with the quality of service characteristics for the signaling as well as the voice
stream.
The class “Termination” includes the attributes and methods that allow the
provisioning of the individual SIP termination characteristics.
VoIP Services Management Model

This management model offers the capability to provision the physical subscriber
line interface, the Z-interface, the tone pattern, the Basic call and Supplementary
Services related parameters. The provisioning of these parameters happens by means
of a couple of profiles being downloaded by the access node. The customer cannot
manually update these profiles.
The class “SIP Service Profile” includes the attributes and methods that allow the
provisioning of the Basic call and Supplementary service characteristics.
The class “POTS CDE Profile” includes the attributes and methods that allow the
provisioning of the physical subscriber line, the Z-interface, the tone pattern, the
protocols that run at the end-user side and LT board hardware characteristics.
VoIP Database Model

The class “VoIP Database” includes the attributes and methods that allow managing
the SIP Voice Database.
VoIP Narrowband Line Test Management Model

The class “Available Session” includes the attributes and methods to schedule a new
narrowband line test session.
The class “Session” includes the attributes and methods that allow the provisioning
of the narrowband line test session characteristics.
The class “Line Identity” includes the attributes and methods that allow the
provisioning of the subscriber lines involved in the narrowband line test session.
The class “Line Test Parameters” includes the attributes and methods that allow the
provisioning of the parameters to be considered in the course of a narrowband line
test session.
The class “Session Report” includes the attributes and methods that allow retrieving
the results of the completed narrowband line test session.
8.12 CDE profile management
Apart from the regular management interface to configure the network and end user
associated database parameters for the integrated voice service, the ISAM Voice
node makes use of additional configuration input under the format of a downloadable
file. Allowing the integrated voice service to become fully operational requires the
presence of CDE profiles at the Voice server (Megaco ISAM Voice only) and the
Voice LT (both Megaco ISAM Voice and SIP ISAM Voice).
The content of CDE profiles is customer dependent. CDE profiles are produced
off-line at the factory. The content is collected by means of a questionnaire that needs
to be filled out by the customer. The content is considered to be of static nature and
concerns mainly the physical subscriber line characteristics of the NB user interface
together with the Voice LT hardware related configuration data and protocols that
run at the end user side.
There is a dedicated CDE profile for the POTS Voice LT board, the ISDN BRI Voice
LT board and the Voice server. The ISDN BRI Voice LT board profile and the Voice
server profile are only applicable to the Megaco ISAM Voice. The CDE profile for
the POTS Voice LT board is voice-topology independent meaning that the same
CDE profile can be used in either a MEGACO environment or a SIP environment.
The CDE profiles for the POTS/ISDN BRI Voice LT and Voice server are included
in one CDE.tar file. This file must be downloaded and activated in the individual
ISAM Voice access nodes (SIP ISAM Voice). For Megaco ISAM Voice that is, the
hub node, the subtending nodes and the remote nodes.
The CDE.tar file is delivered to the customer together with the software package and
all other associated files that are required to install an ISAM Voice in the access
network.
The system itself takes care that a CDE profile is downloaded to the Voice server
(Megaco ISAM Voice only) and/or the Voice LT board.
The system supports CDE profile upgrades. They are an integral part of the offline
database migration during software upgrade.
8.13 Service profile management
SIP ISAM Voice has introduced the concept of “Service profile” to maximize
flexibility on:
• IOT with multiple Application Servers, including the flexibility of a new IOT
during a maintenance phase of an ISAM release
• re-using application software: as such, application software will be data driven,
based on the selected options from the SIP service profile.
The service profile applies to the POTS SIP Voice LT board only and is provisional
and downloadable via the CDE profile framework.
The content of the service profile is customer dependent. A service profile is
produced off-line at the factory. The content is collected from the voice service
requirements defined by the customer.
The service profile is appended to the CDE profile in the CDE profile file. As such
it is downloaded together with the CDE profile in the individual ISAM Voice access
nodes, that is, the hub node and the subtending nodes.
8.14 Basic call handling
Megaco ISAM Voice
General Properties (POTS / ISDN)
• Interfacing at the side of the subscriber according to the Z POTS interface.

• DTMF/pulse digit detection/processing.
• Caller identification services (FSK, DTMF, on/off hook).
• FSK/DTMF configurable per line
• Signaling events processing
• en-bloc dialing.
• Voice activity detection, comfort noise, and packet loss concealment.
• Configurable jitter buffer: adaptive or fixed size (per call).
• G.168/G.165 echo cancellation with an echo tail length at 16ms
• Tone generation: Ring tone, Dial Tone, Special (Information) Dial Tone, Ring
Back Tone, Congestion Tone, Busy Tone, and Howler tone.
• Balanced ringing
• Flexible Termination ID format including wildcard
• Flat termination ID format
• Hierarchical termination ID format:
- Configurable Termination ID syntax
- A character string composed of a number of pre-defined keywords.
• Configurable ephemeral termination ID range.
• Audit of ephemeral termination with support of the wildcard *.
• Capability of configuring 2 dial plans in the CDE profile, each with a max size of
4 Kbytes including digit map patterns and digit map pattern separators. The digit
patterns are consecutively stored with the 4 Kbytes buffer, separated by a digit
pattern separator.
• Capability to store up to 512+51 dial plans (one dial plan/call; downloaded by the
MGC), each with a max size of 4 Kbytes including digit map patterns and digit
map pattern separators.
• T.38 Fax
• Softswitch is responsible of voice/T.38 call control & charging.
• Fax over IP according to ITU-T Rec. T.38
• Between 2 Group 3 facsimile terminals.
• UDP transportation
• V21 flag detection
• Byte based and frame based
• FEC and redundancy
• 2400 bps, 4800 bps, 7200 bps, 9600 bps, 12200 bps, 14400 bps.
• Maximum Speed is 14400bps depending on the network situation.

• ISDN : Support of T.38 MGC Transitioning method. (T.38 Autonomous
transitioning method is NOT supported).
• T30 Fax, requiring full control at the MGC.
• Detected tones reported to MGC
• Switch to VBD mode upon receipt of MGC command.
• Transparent modem/fax service (v.150 VBD mode)
• Capability to detect fax/modem tones from network side or local side.
• In-band tones compliant with RFC2833 (for example, frequency, duration,
volume, modulation, and so on shall be same).
• “In-band tone detection” of fax/modem/text tones from remote side (voice band
codecs, commonly G.711, and so on), which serves both as a VBD stimulus and
a coordination technique to guarantee autonomous behavior.
• In-band fax/modem tones trigger ISAM Voice to switch to VBD mode
• For H.248, only tone detected from local side will be reported to MGC in case of
T30/modem full control by MGC.
• Support of the reception of all RFC4734 NTE events, allowing to swap to VBD.
• Support of enhanced fax/modem in-band tone detection from local / IP side with
additional tones treated in compliancy with RFC4733 (when defined). Additional
fax/modem tones support together with IP side in-band tone detection can be
activated simultaneously. This causes some density decrease (density of 48-line
voice LT board becomes 40 instead of 48). IP side in-band tone detection can be
turned off via CDE Profile.
• Fax: V.21, V.17, V.27 ter, V.29, V.34
• Modem (or textphone): V.18, V.21, V.22, V.22bis, V.23, V.32, V.32bis, V.32ext,
V.34, V.90, V.92, Baudot, Bell103, Bell 212A, V.25/V.8/V.8bis compliance.
• Support of reverse polarity as a (configurable) pulse type as well as 12k/16kHz
metering pulses in the amet package.
• Public Payphone (reverse polarity)
• Line Polarity Reverse at answer. (H.248: driven by CDE profile input and MGC
command input)
• 12 /16 Khz Metering (1 TR 110 - 1) for POTS lines connected to public coin
boxes and payphones.
• Periodic Pulsing Only
• Burst once then Periodic Pulsing
• Periodic Bursts
• Periodic bursts with Periodic Pulsing in between the bursts
• Burst once at the begin of a call
• Tariff changes during a call
• Configuration of Line impedance on a per subscriber port basis
• Payload format 'audio/telephone_event' and associated dynamic payload type
number.
• Delay before Reduce battery: Apply reduced power feed in case the analogue line
continues to remain Off-Hook without being associated to any connection. The
ISAM Voice shall trigger timeout of cg/bt and xcg/roh signal and starts a timer in
case the physical termination is in NULL Context or is the only termination in a
non NULL context. Upon timer expiry, all active signals are disabled and the
reduced battery line state is autonomously entered. The timer is disabled by
'On-Hook' event or 'stimal/stedsig=reduced battery' signal.
• Termination of the ISDN BRI U interface (ITU G.961).

• Q921 protocol termination.
• Q931 protocol relay via SIGTRAN.
• CODECs:
• 48 lines POTS LT / 24 lines ISDN LT: G.711 A/u law (10ms, 20ms, 30ms),
G.729AB (10ms, 20ms, 30ms, 40ms, 50 ms, 60ms), G.723.1 (5.3kbps, 6.3kbs, with
30ms), T.38, RFC2833
• 72 lines POTS LT: G.711 A/u (10ms, 20ms, 30ms), G.729 A/B (10ms, 20ms, 30ms,
40ms, 50ms, 60ms), G.723.1 (5.3 kb/s/30ms, 6.3 kb/s/30ms), T.38, RFC 2833;
• For G.711, DTMF or RFC2833 signaling is supported
• For G.729, RF2833 signaling is supported
• ISDN: Test based formatted ISDN IUA Interface identifier.
• Support of the port status:
• Call Status: Onhook, Offhook, Dialing, Calling, IdleOffhook, BusyTone,
HowlerTone, Ringing, Releasing, RingBack, CallerConnected, CalleeConnected
• OperStateDownReason: Registering, RegistrationFailure, PhysicalFailure
• Test status: NoTesting, MtaTesting, IntegratedLineTesting
• ISDN: Idle, B1-Busy, B2-Busy, 2B-Channels-Busy
• ISDN: port power status i.e. whether an ISDN user port is locally powered at the NT
or remotely powered from the line card in the central office
• Support of the configurable TX Line Gain by means of the usual management
channel.
• Support of the configurable RX Line Gain by means of the usual management
channel.
SIP ISAM Voice
General properties (POTS)
• Interfacing at subscriber's side according to the Z POTS interface.

• Caller Identification Services (FSK, DTMF, on/off hook).
• FSK/DTMF configurable per line
• Signaling events processing.
• Voice activity detection, comfort noise, and packet loss concealment.
• G.168 echo cancellation
• en-bloc dialing
• Overlap dialing
• Multiple-invite method
• In-dialog (INFO method)
• Capability of configuring one dial plan through the usual management interface.
• The dial plan has a maximum size of 4 Kbytes including digit patterns and digit
pattern separators.
• The dial plan needs to be configured by means of a maximum of 128 MIB table rows
with a size of 32 bytes each.
• Each row may contain one or more digit patterns separated by a digit pattern
separator.
• A digit pattern must not be split over 2 or more rows.
• CODECs:
• 48-lines POTS LT: G.711 A/u law (10ms, 20ms, 30ms), G.723.1 (5.3kbps, 6.3kbs,
with 30ms), G.729A/B (10ms, 20ms, 30ms), T.38. RFC2833
• 72-lines POTS LT: G.711 A/u (10ms, 20ms, 30ms), G.723.1 (5.3kbps, 6.3kbs, with
30ms), G.729 A/B (10ms, 20ms, 30ms), T.38, RFC 2833
• DTMF can be transmitted by G.711 in-band or RFC2833.
• Audible ringing to calling line
• Tone generation: Ring tone, Dial Tone, Special (Information) Dial Tone, Ring
Back Tone, Congestion Tone, Busy Tone, and Howler tone.
• E2E Dynamic payload type negotiation (RFC3264) - dynamic payload value out
of the range 96...127.
• T.38 Fax
• Fax over IP according to ITU-T Rec. T.38
• UDP transport
• V21 flag detection
• Byte based and frame based
• FEC and redundancy
• 2400 bps, 4800 bps, 7200 bps, 9600 bps, 12200 bps, 14400 bps
• Support of enhanced fax/modem in-band tone detection from local / IP side. IP
side in-band tone detection can be turned off via CDE Profile. (Density of 48 lines
voice LT board becomes 40 iso 48 when IP side detection is turned on).
• Support of the reception of all RFC4734 NTE events, allowing to swap to VBD.
• Fax: V.21, V.17, V.27 ter, V.29, V.34
• Modem (or textphone): V.18, V.21, V.22, V.22bis, V.23, V.32, V.32bis, V.32ext,
V.34, V.90, V.92, Baudot, Bell103, Bell 212A, V.25/V.8/V.8bis compliance.
• Flexible SIP URI provisioning:
Operator control on 'userinfo' part of SIP-URI
• full operator control: The operator can configure a string per SIP Termination Point.
This configured string will be integrally copied into the 'userinfo' part of the
SIP-URI where it will be completed with the '@' character.
• the MSAN itself generates a 'termination-id' string for the 'userinfo' part. This string
shall be generated according a syntax that is under operator control. The string
generated according the syntax will be completed with the '@' character.
Operator control on 'hostport' part of SIP-URI
• hostname: port
• IPv4address: port
• Hostname
• IPv4address
• Flexible Termination ID provisioning:
• Configurable Termination ID syntax
• A character string composed of a number of pre-defined keywords and operator
defined characters.
• Public Payphone (reverse polarity): Line Polarity Reverse at answer.
• 12 /16 Khz Metering (1 TR 110 - 1) for POTS lines connected to public coin
boxes and payphones.
• Periodic Pulsing Only
• Burst once then Periodic Pulsing

• Periodic Bursts
• Periodic bursts with Periodic Pulsing in between the bursts
• Burst once at the begin of a call
• Tariff changes during a call
• Configuration of Line impedance on a per-subscriber port basis
• Delay before Reduce battery Procedure: Apply reduced power feed in case the
analogue line continues to remain Off-Hook without being associated to any
connection after a certain period of time. The delay is provisionable.
• Support of the port status:
• Call Status: Onhook, Offhook, Dialing, Calling, Connected, IdleOffhook,
BusyTone (not applicable anymore after R4.1), HowlerTone (not applicable
anymore after R4.1), Ringing, Releasing, RingBack.
• OperStateDownReason: Registering, RegistrationFailure, PhysicalFailure
• Test status: NoTesting, MtaTesting, IntegratedLineTesting
• Support of the configurable TX Line Gain by means of the usual management
channel.
• Support of the configurable RX Line Gain by means of the usual management
channel.
• Support of the configurable Line Impedance by means of the usual management
channel.
• Support of Pre-conditions:
• Enable/disable SIP pre-conditions.
• Backwards compatibility: irrespective of SIP pre-conditions being enabled or
disabled. The system supports call set-up with the remote party not supporting SIP
Pre-conditions.
• Support of segmented QoS pre-condition during call origination:
Resource reservation before sending initial INVITE.
Indicate the support of SIP pre-conditions in the Supported header of the INVITE.
Prevent media-stream from flowing until the SIP pre-conditions are met.
• Support of segmented QoS pre-condition during call termination:
Resource reservation before returning SDP answer.
Hold ringing the callee until the pre-conditions are met.
Hold call waiting tone and/or CLIP for incoming call until the required SIP
pre-conditions are met.
Prevent media-stream from flowing until SIP pre-conditions are met;
• Support segmented QoS pre-condition in supplementary services:
Hold ringing, call waiting tone and/or CLIP for incoming call until the required SIP
pre-conditions are met.
• Support segmented QoS pre-condition during handling of early dialog:
Only when the SIP pre-conditions are met, the system decides whether to present the
received early media to the user.
8.15 Supplementary services
Supplementary services are widely used in traditional PSTN networks. When

customers consider migrating from a TDM network to an NGN network, they expect
feature parity to support legacy services.
MEGACO ISAM Voice
Megaco: POTS Service

The following is a list of representative POTS supplementary services that are
available via the ISAM-Voice working in conjunction with different vendor MGC
products.
• Multi-Party Services:
• Call Waiting (CW)
• Call Hold (HOLD)
- Hold for enquiry
- Stockbroker
• 3-Party Conference (3PTY)
• Add-on Conference (CONF)
• Explicit Call Transfer (ECT)
• Abbreviated Address/Dialling (AA)
• Administrative Call Barring (ACB)/ Bad Payer
• Alarm Call (AC)
• Announcement Connection
• Anonymous Call Rejection (ACR)
• Call completion to Busy Subscriber (CCBS) / Ring Back
• Call Completion on no Reply (CCNR)
• Calling Line Identification Services:
• Calling Line Identification Presentation (CLIP)
• Calling Line Identification Rejection (CLIR)
- Permanent
- On a per call basis
• CWID service
• Call Diversion Services:
- Call Forwarding Unconditional (CFU)
- Call Forwarding on Busy (CFB)
- Call Forwarding on No Reply (CFNR)
- Call Forwarding to Fixed Announcement (CFFA)
- Call Forwarding to Voice Mail (CFVM)
• Call Pick-UP (CPU)
• Call Return (CR)
• Coin box (CB)
• Connected Line Identification Restriction (COLR)
• Distinctive Ringing
• Do Not Disturb (DND)
• Fixed Destination Call (FDC)
• Hotline
• Warmline
• General Deactivation (GD)
• Incoming Call Barring (ICB)
• Inhibition of Incoming Forwarded Calls (IIFC)
• Lawful Interception (LI)
• Line Hunting (LH)

• Malicious Call Identification (MCID)
• Message Waiting Indication (MWI)
• Numbering Plan and Dialed Digits
• Outgoing Call Barring (OCB)
• Outgoing Call Screening (OCS)
• Special Dial Tone
• Call Park
• Last Call return
Interoperability of the ISAM Voice access node with a third party Voice Application
Server can be supported through commercial agreement.
Please contact the ISAM PU for the supported supplementary services list
Megaco: ISDN Service

The following is a list of representative ISDN BA supplementary services that are
available via the ISAM-Voice working in conjunction with different vendor MGC
products.
- Hold for enquiry
- Stockbroker
• Alarm Call (AC)
• Calling Line Identification Rejection (CLIR)
- Permanent
• Calling Line Identification Rejection Override (CLIR-O)
• Call Forwarding Unconditional (CFU)
• Call Forwarding on Busy (CFB)
• Call Forwarding on No Reply (CFNR)
• Connected Line Identification Services:
• Connected Line Identification Presentation (COLP)
• Connected Line Identification Restriction (COLR)
• Connected Line Identification Restriction Override (COLR-O)
• Fixed Destination Call (FDC):
• Hotline
• Warmline
• Incoming Call Barring (ICB)
• Inhibition of Incoming Forwarded Calls (IIFC)

• Malicious Call Identification (MCID)
• Outgoing Call Barring (OCB)
• Multiple Subscriber Number (MSN)
• Sub Addressing (SUB)
• Terminal Portability (TP)
• Direct Dialling In (DDI)
• Change Password
Please contact the ISAM PU for the supported supplementary services list.
SIP ISAM Voice

For the delivery of PSTN services, TISPAN defines 2 models: the PSTN emulation
subsystem (PES) and the PSTN simulation subsystem (PSS).
The PSS simulates a limited set of PSTN-like services to subscribers with no
requirement to obtain transparency regarding “look and feel” of the services.
Subscribers use more advanced terminals (for example, native SIP phone) to connect
directly to the IMS network without the need for gateways. In this respect, PSS is the
preferred approach for new SIP services.
This model is not adopted by SIP ISAM Voice.
The PES emulates the PSTN services to subscribers with full transparency regarding
the “look and feel” of the services. Subscribers can continue to use their legacy
terminals connected to the IMS network via gateways. In this respect, PES is the
preferred approach for PSTN replacement.
This model has been adopted by SIP ISAM Voice.
TISPAN PES defines two models on how the Voice Gateway interacts with the
Application Server with respect to SIP call manipulation for supplementary services.
In the tightly coupled model, the VGW remains mostly ignorant to the call control
logic of the supplementary service. It simply acts under the direction of the
Application Server (AS) and will report any event to the AS who will manipulate the
call leg(s). Supplementary service logic is mostly centralized in the AS.
In the loosely coupled model, service logic is pushed into the VGW. The VGW will
autonomously interpret user events and will autonomously manipulate the call legs
accordingly.
SIP ISAM Voice supports both models.
A mixture of both models in one and the same deployment is not supported.
Tightly Coupled Model: SIP ISAM Voice support
• “Call Waiting”:
• Flash-hook only: Calling termination presses the flash-hook to switch between the
current called termination and a 3rd party.
• Flash-hook + SOC (Switch Order Command): Calling termination presses
flash-hook and dials an additional digit to switch between the current called
termination and a third party
• “Call Hold”:
• Hard Hold:
Only calling and called termination involved.
Allowing calling termination to Flash Hook once to put the called termination on
hold, and to Flash Hook once again to resume the call with the hold termination.
• Call Hold Consultation:
Calling termination, called termination and third party involved.
Allowing calling termination to put an existing call on hold and to initiate a second
call to a third party
• “3-party Conference”:
• Automatically bridged call by AS
• User dialing decided conference call
• “Explicit Call Transfer”:
• Consultative call transfer: for forwarding a call after the first person who was called
spoke to the caller. (for example, this is useful if a secretary is called and forwards
the call afterwards to the responsible person).
• 3-Way Call transfer: With 3-Way Call Transfer, a termination can set up a 3-way
call and then disconnect, allowing the remaining parties to continue the
conversation.
• Blind call transfer: to transfer a call without talking to the called party.
• “Malicious Call Identification”:
• Permanent (transparent to ISAM-Voice).
• After call completion.
• During call (transparent to ISAM-Voice).
Note: in this case the Application Server cannot make any difference between
flash-hook for MCID or flash-hook for other supplementary services. For example,
put the call on hold.
As such, the Application Server does either support MCID or the rest of the
supplementary service activated by flash-hook, but cannot support both
simultaneously.
Loosely Coupled Model: SIP ISAM Voice support
• “Call Waiting”:
• Supported in compliancy with ETSI TS183043 C.9.1/C.16.1 Loose Coupling, 3GPP
ES 23.228 chap5.11.1, ES 24.228 chap10.1, and China Mobile spec; Generates
re-INVITE message when the supplementary service becomes activated due to
pressing the hook-flash.
• The user is notified by a CW-tone that a second incoming call arrived. The user can
either decide to ignore the call waiting tone or accept the waiting call. Two variants
are supported:
- Simplified CW with Flash-hook only: Calling termination presses the flash-hook
to accept the waiting call and hold the current call. Continuously switching between
both parties by subsequent flash-hook events. To reject the waiting call, the user just
ignores the CW-tone.
- CW with Flash-hook + SOC (Switch Order Command): Calling termination
presses flash-hook and dials an additional digit to either indicate:
- Accept waiting call with release of current call
- Accept waiting call with hold of current call
- Reject waiting call
- Toggle between both calls
- Merge two calls into a 3-way-call conference
• “Call Hold”:
• Complies with ETSI TS183043 C.9.1/C.16.1 Loose Coupling, 3GPP ES 23.228
chap5.11.1, ES 24.228 chap10.1, and China Mobile spec; Generates re-INVITE
message when the supplementary service becomes activated due to pressing the
hook-flash.
• The user can hold the initial call and initiate an inquiry call to a third party by
making a hook-flash event and dial the third party number. Once the enquiry call is
established the user can switch between both calls by making a subsequent
hook-flash event. Following flavours are supported:
- Simplified Call hold with HF-only: the user can continuously switch between both
calls by making a Hook-flash event
- Call Hold with Hook-flash + SOC: user makes a hook-flash event and gets dial
tone. User dials a 1 digit SOC to either:
- Release held call and continue with current active call
- Go back to held call with release of current active call
- Switch continuously between both calls
- Join both calls into a 3-way-call conference
• “3 Party Conference”:
• Compliant to both TISPAN and NON-TISPAN specification, noted that the
Y-function hosts in the MRF/MS, not in SIP ISAM Voice. Although, the 72 lines
Voice LT board is also able to do audio mixing. (NON-TISPAN implementation
only supports IOT with Broadworks FS.)
• Supported in compliancy with ETSI TS183 043 C.14.2 Loose Coupling option 1
(with local RTP-stream mixing at the ISAMV) and option 3 (with RTP-stream
mixing at the MRF of the core under control of the core application server).
• The user can hold the initial call and initiate an inquiry call to a third party by
making a hook-flash event and dial the third-party number. Once the enquiry call is
established the user can join both calls into 3-way conference by a subsequent
Hook-flash event.
• “Explicit Call Transfer”:

• Compliant to both TISPAN and NON-TISPAN specification. (NON-TISPAN
implementation only supports IOT with Broadworks FS.)
• Supported in compliancy with 3GPP ES 23.228 chap 5.11.6 Session Transfer and
ES 24.228 chap 10.5.
• Support REFER message to send the DTMF to the AS according to RFC 3515
“REFER Method/Refer-to header” and RFC 3892 “Referred-By header”.
• Consultative call transfer: for forwarding a call after the first person who was called
spoke to the caller. (for exampel, this is useful if a secretary is called and forwards
the call afterwards to the responsible person).
• 3-Way Call transfer: With 3-Way Call Transfer, a termination can set up a 3-way
call and then disconnect, allowing the remaining parties to continue the
conversation.
• Blind call transfer: to transfer a call without talking to the called party.
For example,in case *23 is the blind call transfer service code, the digitmap shall
include “*23S” as prefix of those patterns to be dialed as transfer target of blind call
transfer service. Those patterns are used for blind call transfer only.
For example, pattern 11xxx is used for basic call, and *23S11xxx is used for blind
call transfer.
• “Malicious Call Identification”:
• Permanent (transparent to ISAM-Voice).
• After call is finished (not supported during a call).
POTS Service: Supplementary Services supported by SIP ISAM Voice

The following is a list of representative POTS supplementary services that are
available via the ISAM-Voice working in conjunction with the ALU IMS solution.
More extensive treatment of the supplementary services supported is available in the
associated ALU IMS documentation.
• Explicit Call Transfer (ECT)
• Calling Line Identification Rejection (CLIR):
- Permanent
• CWID service
• Malicious Call Identification (MCID):
- Permanent
- After call ended

• Call Forwarding Unconditional (CFU)
• Call Forwarding on Busy (CFB)
• Call Forwarding on No Reply (CFNR)
• Call Forwarding to voice mail
• Selective Call Forwarding (SCF)
• Notification services:
• Special dialtone in case diversion service activated
• Special dialtone in case Message waiting service activated and new waiting
messages at VMS for the account of the user.
• ISAM Voice supports the TS183 043 standardized solution (Annex A) for dialtone
management based on unsolicited NOTIFY SIP messages using the ua-profile XML
body
• Distinctive Ringing
• Call Barring services
• Outgoing Call Barring (OCB):
- Administrative controlled
- User controlled
• Incoming call barring
- Administrative controlled
- User controlled
• Bad-payer
• Selective call barring services
• Selective call rejection
• Selective call acceptance
• Anonymous Call Rejection (ACR)
• Fixed Destination Call (FDC)
• Hotline
• Warmline:
Activated/De-Activation/Subscribed (activation / de-activation / interrogation via
service code
• 12 / 16 kHz metering
• SIP MD5 digest Authentication
Please contact the ISAM PU for the supported supplementary services list.
Additional Details regarding SIP ISAM Voice supported Supplementary Services
• “CLIP”:
• Primary source for the Calling Line Identity is either the “From” header or the
“P-Asserted Identity” header (RFC3325). The primary source to be considered is
configurable in ISAM Voice.
• In case the end-user becomes identified to the CLIP service as “No subscription”,
“Private” or “Unavailable”, part of the “From” header or from the “P-Asserted
Identity” header will be set to a dedicated value by the IMS core network.
ISAM Voice allows to configure whether either “Display Name” or “User Part”
(PAI / From) or both do include this dedicated value.
• The dedicated value(s) for “No Subscription”, “Private” and “Unavailable” are
configurable in ISAM Voice.
• Should a termination not be subscribed to the CLI service, then no CLI data
transmission signalling sequence is applied.
• Should a termination be identified as “Private CLI”, then the calling Line identity
parameter is omitted. Instead, “Reason for absence of calling line ID=private” is
propagated.
• Should a termination be unavailable, then the calling Line identity parameter is
omitted. Instead, “Reason for absence of calling line ID=unavailable” is propagated.
• Should both, a tel-uri as well as a sip-uri formatted P-Asserted Identity header be
present, then precedence is given to one of these headers in accordance with the
precedence policy configured in ISAM Voice.
• In general, IMS networks do provide calling number information in the global
number format identified by the leading “+” character (Ref. RFC3966).
ISAM Voice is able to convert the leading “+” into a configurable
international-prefix before the CLI propagated in the CLIP FSK data message.
• ISAM Voice allows to configure whether the “Date and Time” parameter is to be
included in the CLIP FSK data message. ISAM Voice allows to configure whether
the date and time shall be taken from the SIP INVITE Date Header or from the local
ISAM Voice time reference.
• The Privacy header with value “id”, “user”, “header” is used for Calling Party
Number/Name restriction. Number only, Name only, both Number and Name
restriction are configurable by ISAM Voice.
• Privacy header with value “none” means that CLI is not forbidden by Privacy
header. Whether CLI is presented or not still depends on the CLIP subscription
status.
• Release Control Procedure: ISAM Voice supports the services:
• Called Subscriber Held (also known as, re-answer),
• Calling party hold by emergency operator,
• Other calls to/from non-emergency operators for which to hold
• Calling party hold for malicious calling indication in compliancy with the call flow
diagrams documented in NICC ND1021 (v.0.13.1), chapter E.2.7 & E.2.8 (support
of INVITE 'no ring').
• Audible and Visual Message Waiting Indication.
• ISAM Voice supports the NOTIFY messages with Messages-Waiting parameter in
the application/simple-message-summary body. If the message waiting indicator
state is ON, then Stutter Tone (Message Waiting Indicator Tone) will be output
during call origination (replacing normal Dial Tone).
• Visual Indication FSK will be output to the telephone set.
• Fixed line SMS service:

• ISAM Voice supports the “Fixed line SMS” service in compliancy with SIN413
“Fixed Line SMS”.
• To be able to make use of this service, the termination needs to install an SMS
enabled terminal (SM-TE).
• Once the call between the SM-TE and SM_SC has been successfully established,
either SM-TE or SM-SC will initiate the FSK data transmission in compliancy with
ETSI EN 300 659 -2 (Off-hook data transmission).
• The TE-alerting signal (TAS) used to signal that data-transmission shall be carried.
Upon the receipt of the TAS (line side and IP side), the ISAM Voice switches to
VBD mode.
• Only the Dual Tone TE-alerting signal can be used for off-hook data transmission,
as is specified in EN 300 659 - 1 (On-hook data transmission).
8.16 Registration procedure
MEGACO-based ISAM Voice

The Voice Server in its capacity as Media Gateway announces its existence to the
Media Gateway Controller by means of a registration command. This registration
instantiates a control association between MG and MGC.
The Voice Server notifies the Media Gateway Controller that a termination or group
of terminations is about to be taken out of service or has just been returned to service.
A situation where such notification is to be done simultaneously for multiple
terminations might create an overload situation at the MGC.
To guarantee that all terminations are “registered” at the MGC with the correct state,
the Voice Server invokes the termination-state-notify recovery procedure that
verifies the termination state at periodic time interval and that initiates “state change”
retries when necessary.
SIP-based ISAM Voice

From a system perspective, the registration of SIP terminations is done by all SIP
UAs in parallel.
From a SIP UA perspective, as a general rule, SIP terminations are registered on an
individual basis and in the order that the SIP terminations become administratively
enabled.
In situations where the registration is to be done simultaneously for multiple
terminations, an anti-avalanche procedure is invoked as to avoid stressing the SIP
Server.
8.17 Counters and Statistics
Counters and statistics serve various purposes in the ISAM Voice, like
troubleshooting and network dimensioning and are defined at the subscriber side of
the ISAM Voice.
For the Megaco ISAM Voice, the statistics are reported to the MGC after the call has
finished in either the subtract or the audit reply.
Neither of these statistics are supported through the usual management interface.
For the SIP ISAM Voice, the statistics can be retrieved using CLI or an Element
Management System (EMS). See the related documents for detailed information and
the detailed command definitions for retrieving the ISAM counters and/or statistics.
(ISAM Operations and Maintenance Guide Using CLI, 5529 Statistics and Data
Collector Installation and User Guide).
Megaco ISAM Voice

Statistics are autonomously enabled by the system.
The Megaco ISAM Voice supports the “nt” as well as the “rtp” package for the
permanent and ephemeral terminations.
Table 8-1 Overview of the H.248 supported statistics
Package Statistics Contained in CLI/SNMP Notes
subtract reply audit reply

nt dur Y Y - Provides the duration of time the
termination has existed or been out of the
NULL context.
os Y Y - Provides the number of octets sent from

the termination or stream since the
NULL Context. The octets represent the
egress media flow excluding all transport
overhead. At the termination level, it is
equal to the sum of the egress flows over
all streams.
or Y Y - Provides the number of octets received on

NULL Context. The octets represent the
ingress media flow excluding all transport
overhead. At the termination level, it is
equal to the sum of the ingress flows over
all streams.
(1 of 2)
Package Statistics Contained in CLI/SNMP Notes
subtract reply audit reply
rtp ps Y Y - Provides the number of packets sent from

NULL Context.
pr Y Y - Provides the number of packets received

on the termination or stream since the
NULL Context.
pl Y Y - Provides the current rate of packet loss on

an RTP stream, as defined in RFC 3550.
Packet loss is expressed as percentage
value: number of packets lost in the
interval between two reception reports,
divided by the number of packets
expected during that interval.
jit Y Y - Provides the current value of the

inter-arrival jitter on an RTP stream as
defined in RFC 3550. Jitter measures the
variation in inter-arrival time for RTP data
packets.
delay Y Y - Provides the current value of packet

propagation delay expressed in timestamp
units. This is the same as average latency.
(2 of 2)
SIP ISAM Voice

SIP ISAM Voice makes use of the Performance History Storage Framework for the
collection and reporting of statistics and counters. This basic framework relies on
current and historical intervals to store the history of the statistics and counters. This
is typically one interval per 15 minutes or 24 hours. The start and end time of each
interval (15 minutes / 24 hours) are aligned with the quarter hours / 24 hours of the
wall clock.
Should the duration of a call session exceed the interval boundary, then the statistics
and counters for such call session will be collected and reported spread over multiple
intervals. The post-processing, that is the concatenation / sum-up of all portions for
such statistics and counters, in order to calculate the results for the full call, is not
supported by the ISAM-Voice access node; It is to be done by an external expert
system (for example, SDC).
Figure 8-99 SIP ISAM Voice Performance Monitoring Result Post-Processing
OSS Platform
2. Associate PM record 1. Generate PM record
with CDR record by using the for dialog A including
Dialog Reference Dialog Reference
CDR
Other NE
SDC
2. Generate PM record for dialog A including Dialog Reference.
1. Retrieve all PM portions for dialog A using Dialog Reference
Dialog A “Elapse” time

Dialog A “active” time – portion 1 Dialog A “active” time – portion 2
Dialog A Dialog A
Dialog A Dialog A e.g. put Dialog A Dialog A
Portion_1 Portion_2 on hold Portion_3 Portion_4
PM record PM record PM record PM record
Recent 15 min interval N-1 Recent 15 min interval N Recent 15 min interval N+1
1 PM record for dialog A 2 PM records for dialog A 1 PM record for dialog A

in this 15 min interval in this 15 min interval in this 15 min interval
The SIP ISAM Voice supports voice related per-line, per-board and per call statistics
/ counters, System-wide resource utilization related statistics / counters and
System-wide Subscriber Line Utilization and service availability statistics/ counters.
For the per-line statistics and counters, the current 15-min / 24-hours interval
together with a set of 96 15-min and three 24-hours history intervals is supported.
For the per-call statistics and counters, a set of 96 15-min history intervals is
supported (the current 15-min interval is not supported).
For the per-board statistics and counters, the current 15 min / 24 hours interval
together with a set of 96 x 15 min and 3 x 24 hours history intervals is supported.
The system-wide resource utilization related statistics and counters are short-lived.
They are supported as operational counters and are not based on the History Interval
Framework. These statistics and counters are supported by means of the System MIB
(not the Voice MIB).
The system-wide Subscriber Line Utilization and service availability statistics and
counters are short-lived. They are supported as operational counters and are not
based on the History Interval Framework. These statistics and counters are supported
by means of the System MIB (not the Voice MIB).
The SIP ISAM Voice supports TCA handling. The TCA can be enabled / disabled
for each individual subscriber line. Both the high and the low TCA threshold is
configurable.
Statistics can be explicitly enabled / disabled by means of the regular management
channel. The system does not allow to enable/disable a particular performance
minitoring category. Either PM is enabled for all categories (per-Line, per-Board,
per-System, per-Call) or PM is disabled for all categories (per-Line, per-Board,
per-System, per-Call).
Table 8-2 Overview of Per-line Statistics and Counters
Statistics Description
Packets Sent The number of RTP packets sent by a SIP termination during a single
Packets Received The number of RTP packets received by a SIP termination during a
single interval
Octets Sent The number of octets sent by a SIP termination during a single
interval
Octets Received The number of octets received by a SIP termination during a single
interval
Average Inter-Arrival Jitter The average Inter-Arrival Jitter for (an) RTP data stream(s) of a SIP
termination in a single interval.
Peak Inter-Arrival Jitter The peak Inter-Arrival Jitter measured for (an) RTP data stream(s)
exchanged by a SIP termination during a single interval.
Average Round Trip Delay The average Round Trip Delay for (an) RTP data stream(s) of a SIP
termination during a single interval
Peak Round Trip Delay The peak Round Trip Delay measured for (an) RTP data stream(s)
exchanged by a SIP termination during a single interval
Average Jitter Buffer Fill The average jitter buffer fill level for a SIP termination during a
level single interval
Average Jitter Buffer Fill The average jitter buffer fill level measured during the receipt of
level G711a (an) RTP stream(s), encoded with G711_a by a SIP termination
during a single interval
level G711u (an) RTP stream(s), encoded with G711_u by a SIP termination
level G723 (an) RTP stream(s), encoded with G723 by a SIP termination during
a single interval
level G729 (an) RTP stream(s), encoded with G729 by a SIP termination during
a single interval
Total Packet Loss The total (absolute) amount of packets lost for a SIP termination
during a single interval.
Successful (Re-) Register The number of (re-)registration requests which are successfully
requests replied in this interval i.e. a response = 200 OK with expire header
time = 0 or expire header <> 0 has been returned by the Registrar.
Failed (Re-) Register The number of (re-)registration requests which failed in this interval
requests i.e a response <> 200 OK was retruned by the SIP First Hop server /
Registrar or that SIP transaction timed-out.
Active Registrations The number of registrations being active at a subscriber port at the
start of the interval. In the current implementation, only 1
registration can be active at a subscriber port at a time. An active
registration is counted when a registration request has been
successfully completed in the past (200 OK received to register
request with "expire header" time <> 0) and the register expiration
interval hasn't expired.
(1 of 2)
Outgoing Calls Answered The number of outgoing call attempts in this interval for which an
initial INVITE request is sent AND for which a response is received.
The system allows to provision what kind of response must be
received as to be counted as a successful outgoing call attempt. The
system offers the following options:
• Any response be received (irrespective of whether this is a
successful or unsuccessful response).
• A successful response be received (180 or 200 response only).
Incoming Calls Answered The number of incoming call attempts in this interval for which a SIP
response is sent being the result of the off-hook event been
detected. The system allows to provision the kind of response that
will be considered as to be counted as a successful incoming call
attempt. The system offers the following options:
• Any response be sent.
• 180 response be sent.
(2 of 2)
Table 8-3 Overview of Per-call Statistics and Counters
Packets Sent The number of RTP packets sent by a SIP termination since the call
is established/ the start of the interval and the end of the call/ the
expiry of the interval
Packet Received The number of RTP packets received by a SIP termination since the
call is established/ the start of the interval and the end of the call/
the expiry of the interval
Octets Sent The number of octets sent by a SIP termination since the call is
established / the start of the interval and the end of the call/ the
Octets Received The number of octets received by a SIP termination since the call is
established/ the start of the interval and the end of the call/ the
Average Inter-Arrival Jitter The average Inter-Arrival Jitter for the RTP data stream since the
call is established/ the start of the interval and the end of the call/
the expiry of the interval.
Peak Inter-Arrival Jitter The peak Inter-Arrival Jitter for the RTP data stream since the call
expiry of the interval.
Average Round Trip Delay The average Round Trip Delay for the RTP data stream since the call
Peak Round Trip delay The peak Round Trip Delay for the RTP data stream since the call is
established/ the start of the interval and the end of the call/ the
Total Packet Loss The total (absolute) amount of packets lost for the RTP data stream
since the call is established/ the start of the interval and the end of
the call/ the expiry of the interval.
Total Packet Loss due to The total (absolute) amount of packets lost due to Jitter Buffer
Jitter Buffer Overrun Overrun for the RTP data stream since the call is established/ the
start of the interval and the end of the call/ the expiry of the
interval.
Table 8-4 Overview of the Per-Board statistics and counters
Packets Sent The number of RTP packets sent by all SIP terminations of an LT
board during a single interval
Packets Received The number of RTP packets received by all SIP terminations of an LT
board during a single interval
Octets Sent The number of octets sent by all SIP terminations of an LT board
Octets Received The number of octets received by all SIP terminations of an LT board
Average Inter-Arrival Jitter The average Inter-Arrival Jitter for (an) RTP data stream(s)
exchanged by an LT board during a single interval.
Peak Inter-Arrival Jitter The peak Inter-Arrival Jitter measured for (an) RTP data stream(s)
exchanged by an LT board during a single interval.
Average Jitter Buffer Fill The average jitter buffer fill level for an LT board during a single
level interval
Average Round Trip Delay The average Round Trip Delay for (an) RTP data stream(s) exchanged
by an LT board during a single interval
Peak Round Trip Delay The peak Round Trip Delay measured for (an) RTP data stream(s)
exchanged by an LT board during a single interval
Total Packet Loss The total (absolute) amount of packets lost by an LT board during a
single interval.
level (an) RTP stream(s), encoded with G711_a for an LT board during a
single interval
level G711u (an) RTP stream(s), encoded with G711_u for an LT board during a
single interval
level G723 (an) RTP stream(s), encoded with G723 for an LT board during a
single interval
level G729 (an) RTP stream(s), encoded with G729 for an LT board during a
single interval
Spare POTS Ports Total amount of POTS ports, which are not configured in the SIP
termination Table, but present at the LT board. The value is taken
at the beginning of the respective interval
Active POTS Ports Total amount of available configured (configured and not
administratively blocked) POTS ports (independent of line status and
registration) at the LT board. The value is taken at the beginning of
the respective interval
Inactive POTS Ports Total amount of not-available configured (configured and

administratively blocked) POTS ports (independent of line status and
registration) at the LT board. The value is taken at the beginning of
the respective interval.
Average CPU Load Average CPU load measured at an LT board during a single interval
Average Memory Utilization Average amount of semi and dynamic memory being used at an LT
board / NT board) during a single interval. Expressed as a
percentage.
Average Free Memory Average amount of free semi and dynamic memory measured at an
LT board / NT board during a single interval. Expressed in Mbytes.
Average Memory Used Average amount of semi and dynamic memory being used at an LT
board / NT board) during a single interval. Expressed in Mbytes.
Total Memory The total amount of semi and dynamic memory available at an LT
board / NT board. Expressed in Mbytes
Successful (Re-) Register The number of (re-)registration requests which are successfully
requests replied in this interval i.e. a response = 200 OK with expire header
time = 0 or expire header <> 0 has been returned by the Registrar.
Failed (Re-) Register The number of (re-)registration requests which failed in this interval
requests i.e a response <> 200 OK was retruned by the SIP First Hop server /
Registrar or that SIP transaction timed-out.
Active Registrations The number of registrations being active at a subscriber port at the
start of the interval. In the current implementation, only 1
registration can be active at a subscriber port at a time. An active
registration is counted when a registration request has been
successfully completed in the past (200 OK received to register
request with "expire header" time <> 0) and the register expiration
interval hasn't expired.
Outgoing Calls Answered The number of outgoing call attempts in this interval for which an
initial INVITE request is sent AND for which a response is received.
The system allows to provision what kind of response must be
received as to be counted as a successful outgoing call attempt. The
system offers the following options:
• Any response be received (irrespective of whether this is a
successful or unsuccessful response).
• A successful response be received (180 or 200 response only).
Incoming Calls Answered The number of incoming call attempts in this interval for which a SIP
response is sent being the result of the off-hook event been
detected. The system allows to provision the kind of response that
will be considered as to be counted as a successful incoming call
attempt. The system offers the following options:
• Any response be sent.
• 180 response be sent.
Table 8-5 Overview of the System-wide Resource Utilization statistics and counters
Average CPU Load The average CPU load for a particular LT board (180 sec)
Detailed CPU load Detailed list of the CPU load measured with a 1 sec interval over a
total period of 180 sec
Absolute Memory The absolute value of the total amount of memory resources utilized
Utilization by a particular LT board.
Percentage of Memory The percentage of memory resource utilization compared to the

Utilization available dynamic memory resources for a particular LT board
Table 8-6 Overview of the System-wide Subscriber line Utilization and service
availability statistics and counters
Non-Configured Lines The amount of planned/equipped subscriber lines for which no entry
could be found in the SIP Termination Table.
Operational Configured The amount of subscriber lines configured in the SIP Termination
Lines Table and for which the operational state equals “up”.
Non-Operational The amount of subscriber lines configured in the SIP Termination
Configured Lines Table and for which the operational state equals “down”.
8.18 Reliability, Equipment / Connectivity / Overload Protection
Equipment Protection
NT redundancy
For further details about NT redundancy, see chapter “Failure protection and
redundancy provisions in ISAM”.
Megaco ISAM Voice: Voice Server redundancy

The Voice server may be installed as a 1+1 Redundancy pair. Both Voice servers of
a 1+1 redundancy pair must be equipped in neighboring slot positions.
One Voice server is active while the other runs in standby mode. In case the active
Voice server encounters a hardware or software problem, the standby Voice server
takes over and becomes the active Voice server for the integrated voice service.
Upon switchover, the recovery time is less than 7 s for call signaling and less than 3
s for voice traffic.
Stable calls are not lost during the switchover. Non-stable calls that is, calls in the
set-up phase may be lost due to a Voice server switchover. This applies to both,
POTS and ISDN BRI calls.
Connectivity Protection
Besides the support of Spanning Tree Protocol (STP), Rapid Spanning Tree Protocol
(RSTP) or Multiple Spanning Tree Protocol (MSTP) and Link Aggregation Control
Protocol (LACP) on the network links of the ISAM Voice node, some additional,
more voice specific connectivity protection concepts are introduced.
Megaco ISAM Voice: Geo_Redundancy

GEO-Redundancy implies the provisioning of a primary, secondary and optionally
tertiary Softswitch / Application Server Process (ASP) with each of these
Softswitches / Application Server Process being provisioned with a different IP
address, and allowing, in case of a failure of the primary control association, to make
a switch-over to the secondary or tertiary Softswitch / ASP preserving of stable calls.
It is to be noted that the possibility to preserve stable calls during a switch-over
depends on the capabilities supported by the Softswitch.
A failure of the current control association may be detected as described hereafter:
• Upon no reply received on a transaction request initiated by the Voice server:
Megaco ISAM Voice allows to provision the maximum number of retries per
transaction together with the retry mode. The latter being either the fixed retry
interval mode or the increasing retry interval mode. In the latter case, the retry
interval doubles for each subsequent retry.
• Through the support of the Inactivity Timer package:

The purpose of this package event is to allow the MG to detect periods of silence
of messaging from the MGC. Once the period of silence exceeds a threshold, the
MG assumes a control connection failure with that MGC.
• Active Heartbeat mode:
The MG checks the connectivity with the MGC at regular time interval by means of
the “notify” package. The following modes are supported:
- Configured heartbeat interval: The interval by which the “notify” packages are
initiated by the MG is provisioned.
- Learnt heartbeat interval: The interval by which the “notify” packages are initiated
by the MG is learnt from the “Inactivity Timer” package notification of the MGC.
The system decides upon a failure of the current control association from the
moment 7 subsequent “notify” packages were not replied by the MGC.
A “Notify” package is sent on the condition that no other Megaco message is
received from the MGC within the learnt/configured heartbeat interval.
• Passive Heartbeat mode:
The MGC checks the connectivity with the MG at regular time interval by means of
the “audit” package. The following modes are supported:
- Configured heartbeat interval: The interval by which the “audit” packages are
initiated by the MGC is provisioned.
- Learnt heartbeat interval: The interval by which the “audit” packages are initiated
by the MGC is dynamically learnt by the MG. The MG awaits 3 consecutive “audit”
packages from the MGC to calculate the heartbeat interval.
The system decides upon a failure of the current control association from the
moment 8 subsequent heartbeat intervals have passed without receiving neither an
“audit” nor a regular Megaco package from the MGC.
Megaco ISAM Voice: Network Local-Redundancy

Network Local-Redundancy implies the provisioning, at ISAM Voice side, of
• either a single Softswitch and a single Application Server Process (ASP). At the
network side, both instances of the Softswitch together with both instances of the
ASP share the same IP address; see Figure 8-100.
• or a single Softswitch and 2 ASP instances.
At the network side, both instances of the Softswitch share the same IP address
while each instance of the ASP owns a different IP address which is different
form the IP address shared by the Softswitch instances; see Figure 8-101.
Figure 8-100 Softswitch + 1 ASP
ISAM Voice MGC1

Active
ion IP@_1
MG/SG iat
soc
as
nt rol ASP1
8 co Active
.24 tion
H ol a ssocia
contr IP@_1
IP address of MGI SCTP
IP address of SGI
H.248
contr MGC2
SC ol ass
TP ociati Standby
on
co
ntr
ol IP@_1
as
so
cia
tio ASP2
n
Standby
IP@_1
Figure 8-101 Softswitch + 2 ASP
ISAM Voice MGC1

Active
ion IP@_1
MG/SG iat
soc
as
t rol ASP1
on Active
8c on
. 24 ociati
H ol ass
T P contr IP@_2
IP address of MGI SC
IP address of SGI
H.248
contr MGC2
SC ol ass
TP ociati Standby
on
co
ntr
ol IP@_1
as
so
cia
tio ASP2
n
Standby
IP@_3
A Softswitch switchover is fully transparent to the MG, however it cannot be

guaranteed that the same applies to the ASP switch-over. In the latter case, usually
the following scenario is followed:
• Upon ASP/SCTP switchover, the new active SCTP instance initiates an SCTP
INIT to the MG.
• Upon the receipt of such SCTP-INIT, the MG starts the recovery timer T(r), does
not remove any termination context and starts queing Q.931 messages for
terminations involved in a stable ISDN call (Q.931 messages from terminations
involved in calls that have not reached the stable phase are NOT queued).
• In compliancy to RFC4233, th recovery timer T(r) can be configured to a value
in the range 1 - 5 s in the ISAM Voice CDE profile
• The MG is able to buffer Q.931 messages for up to 564 stable ISDN calls with the
restriction that only the most recent Q.931 data message is queued.
• Upon the receipt of “ASP active” notification, prior to T(r) expiry, all the buffered
Q.931 messages are sent to the active ASP. The MG gradually forwards the
messages to the new active ASP as to avoid ASP overload.
• Should the recovery timer expire prior to the receipt of an ASP active notification,
then ISAM Voice turns the signaling gateway status to operational down, drops
the queued Q.931 messages, removes all ISDN termination contexts and sends
Service Change “904” for all ISDN terminations
Note — The buffer for queueing SCN messages is not synchronised

to the standby Voice Server.
Megaco ISAM Voice: ESA-Redundancy

An ESA Softswitch is to be understood as an MGC that supports a minimum feature
set, such that the basic and the emergency call can remain supported in situations of
a simultaneous failure of all usual MGCs (primary and secondary). In that respect, it
is assumed that the ESA Softswitch functionality is limited to:
• Basic POTS calls. (ISDN calls and supplementary services are not supported
during ESA mode activation).
• Establishing calls between user ports controlled by the MG(s) that has (have) a
control association with the ESA SoftSwitch.
• Emergency call.
Based on the above, ESA-Redundancy requires the provisioning of at least 2 MGCs
with the strict condition that the ESA softswitch must be provisioned as the lowest
priority MGC. The provisioning of both, Primary + ESA softswitch as well as
Primary + Secondary + ESA Softswitch is allowed.
In case of a failure of the Primary (Primary + ESA) or both simultaneously, Primary
and Secondary (Primary + Secondary + ESA) MGC, ISAM-V will make a
switch-over to the MGC with the lowest priority potentially allowing for the
preservation of stable calls. The possibility to preserve stable calls during a
switch-over depends on the capabilities supported by the MGC.
The ISAM-V, from a perception of being an MG, does not have any notion about the
capabilities of a SoftSwitch being configured as primary, secondary or tertiary MGC.
The ISAM-V treats all configured MGCs equally.
The ISAM-V assumes that:
• The ESA SoftSwitch accepts “on-hook” notifications for calls that were
established in the course of the control association being established between the
MG and the Primary / Secondary MGC but finished in the course of the control
association being established between the MG and the ESA SoftSwitch.
• The ESA SoftSwitch is responsible to “subtract” the contexts for calls that were
established in the course of the control association being established between the
MG and the Primary / Secondary MGC but finished in the course of the control
association being established between the MG and the ESA SoftSwitch.
• The ESA SoftSwitch is responsible for the alive monitoring of Primary (and
Secondary) MGC when ESA mode is active.
• While the ESA SoftSwitch has an active control relationship with the MG, it shall
continuously monitor both the primary and the secondary MGC by repeating to send
a ServiceChange message with method = “FailOver SVC Forced”.
• Should a reply “ERROR 403 syntax Error” be received from either the Primary or
the Secondary MGC, the ESA SoftSwitch will immediately send a ServiceChange
message with Method = “HandOff” and [Primary/Secondary MGC] address to the
ISAM Voice MG.
The capability of the ESA Softswitch to poll only one MGC or multiple MGCs does
not have any impact on the ISAM-V in its capacity as MG. This may only influence
the time period after which the usual voice service can be resumed.
Control association failure detection and switch-over from Primary/secondary MGC

to ESA MGC is identical as described for the GEO-Redundancy.
Megaco ISAM Voice: Network Connectivity Protection

Also known as “Path Connectivity Check and Protection” (PCCP).
This protection technique aims at consolidating the connectivity between a Megaco
ISAM Voice and a network device, mostly its default gateway.
The Network Connectivity Protection must not be active when the ISAM Voice
behaves as routing device.
For further details about Network Connectivity Protection: ref. Section “Failure
protection and redundancy provisions in ISAM”.
SIP ISAM Voice: SIP Server Redundancy and SIP Server Fail-Over / Fail-Back
SIP Server Redundancy entails the grouping of individual SIP servers which as a
group can support the ability for a SIP User Agent in the access node to recover and
resume service in spite of a failure of one or multiple of the individual SIP servers.
Figure 8-102 SIP Server redundancy
L2 / L3 Primary Site
Network
I-CSCF HSS
ISAM-V
Site connection S-CSCF

P-CSCF
1_1
First Hop SIP Server Redundancy

ISAM-V
The ISAM Voice SIP User Agent supports the interworking with a group of “first
hop SIP servers” that form a SIP server redundancy group and whereby all SIP
servers get assigned a different priority. The SIP server with the highest priority acts
as the primary SIP server, while the rest of the SIP servers act as secondary SIP
servers. A “first hop SIP Server” is to be understood as the SIP Server being selected
by the SIP User Agent to send the initial REGISTER/INVITE requests to. Such SIP
server redundancy group consists of a primary and one or multiple secondary SIP
servers.
A SIP server redundancy group can be provisioned by means of:
• A Domain Name whereby the IP address of the individual SIP servers must be
resolved through the Domain Name Service NAPTR, SRV and A resource record
look-up,
• A list of Fully Qualified Domain Names whereby the IP address of the individual
SIP servers must then be resolved through the Domain Name Service A resource
record look-up,
• A list of IP addresses of the individual SIP Servers.
The SIP User Agent triggers autonomously a SIP server Fail-over upon the failure of
the actually selected first hop SIP server. A failure is to be understood as a situation
where a reply is no longer received for an out-of-dialog SIP request or the receipt of
an unsuccessful response code to an out-of-dialog SIP request. In the course of a SIP
Server Fail-Over, the SIP terminations that are currently registered via the failing SIP
server are moved to another SIP server within the same redundancy group.
The SIP server Fail-over trigger default conditions can be customized by means of
SIP Service Profile provisioning.
Once the failed primary SIP server is back in service, the SIP User Agent triggers
autonomously a SIP server Fail-back. In the course of a SIP server Fail-back, the SIP
terminations that are currently registered via a secondary SIP server are moved to the
primary SIP server within the same redundancy group.
The SIP server fail-back is performed gracefully meaning that the SIP User agent
triggers a fail-back for a SIP termination from the moment it has the on-hook state.
Neither ongoing dialogs nor ongoing transactions are interrupted.
Neither for the SIP server Fail-over nor for the SIP server fail-back ongoing dialogs
and transactions are transferred to the selected fail-over / fail-back SIP server, and
this neither at the signaling plane (SIP) nor at the media plane (RTP).
Foreground Service Health Monitoring
Foreground Service Health Monitoring helps the SIP User Agent to rapidly detect
whether the currently selected first hop SIP server can still be addressed for new SIP
requests. Foreground Service Health Monitoring makes use of the SIP REGISTER
Method. One termination out of the group of terminations that have the following in
common:
These SIP terminations get the same service route returned upon successful
registration
AND
These SIP terminations addressed the same First Hop SIP server for their initial
registration.
Re-registers with a configurable high frequent interval (typically 90 sec) while the
rest of the terminations re-register with the usual frequency.
Background Service Health Monitoring
Background Service Health Monitoring applies to all First Hop SIP Servers being a
fail-over candidate SIP server. The SIP user Agent transmits periodically
(configurable period) an out-of-dialog OPTIONS message to determine the health
status of the fail-over candidate First Hop SIP Server.
Having this information in advance helps to reduce the elapse time to perform
fail-over and subsequently the establishment of new call sessions.
Background Service Health Monitoring makes use of the OPTIONS method.
Fail-Over Hysteresis Threshold
In order to allow the SIP User Agent to distinguish accidental from persistent error
conditions and as such to prevent connection toggling between first hop SIP servers
within a redundancy group, a Fail-over Hysteresis Threshold can be configured.
A SIP Server Fail-over is triggered from the moment the amount of error conditions
has exceeded the Fail-Over Hysteresis Threshold.
Stable Operation Observation Period
Stable operation observation intends to observe the stability of the SIP server once
this SIP server has resumed service after having failed.
Should an observed SIP server remain uninterrupted in-service from the start till the
expiry of the (configurable) stable operation observation period, then this SIP server
is declared stable and ready to be a fail-over / fail-back candidate SIPs server.
The stable-operation observation starts from the moment a failed SIP server has
resumed operation, detected by the SIP User Agent via the background service health
monitoring.
Deliberate Update
For reason of maintenance activities, a SIP server may be temporarily put out of
service. To avoid service interruption, the ISAM-V allows to announce such
upcoming activity by an update of the list of SIP servers being part of a redundancy
group (DNS zone file, SIP server table).
In case such update is recognized by the SIP User Agent and the removed SIP server
is a SIP server via which SIP terminations are registered, then the SIP User Agent
will trigger a Fail-over to the highest priority SIP Server still present in the list.
A Deliberate Update is performed gracefully, meaning that the SIP User agent
triggers a fail-over for a SIP termination from the moment it has the on-hook state.
Neither ongoing dialogs nor ongoing transactions are interrupted.
SIP ISAM Voice: GEO Redundancy and GEO Fail-Over / Fail-Back

Geographic redundancy entails the physical distribution of individual SIP servers or
SIP server redundancy groups that can support the ability for a SIP User Agent in the
access node to recover and resume service in spite of a failure or a catastrophe at a
particular physical location.
Figure 8-103 SIP GEO redundancy
L2 / L3 GEO Primary Site

Network
I-CSCF HSS
ISAM-V
GEO primary site connection S-CSCF

P-CSCF
1_1
GEO back-up site connection
GEO Back-up Site

ISAM-V GEO
redundancy
GEO Back-up Site
I-CSCF HSS
ISAM-V
GEO primary site connection S-CSCF

P-CSCF
1_1
GEO back-up site connection
GEO Primary Site

ISAM-V
The ISAM Voice SIP User Agent supports the interworking with a first hop
Geo-redundant SIP server topology.
A Geo-redundant SIP server topology can be provisioned by means of:
• The Domain Names of the geo primary and geo back-up site whereby the IP
address of the individual SIP servers of these sites must be resolved through the
Domain Name Service NAPTR, SRV and A resource record look-up,
• A list of Fully Qualified Domain Names for both the geo primary and the geo
back-up site whereby the IP address of the individual SIP servers must then be
resolved through the Domain Name Service A resource record look-up,
• A list of IP addresses of the individual SIP Servers for both the geo primary and
the geo back-up site.
The SIP User Agent triggers a Geo Fail-Over / Geo Fail-Back upon explicit request
of the operator. See the related documents for detailed information and the detailed
command definitions for initiating such Geo Fail-Over / Geo Fail-back (ISAM
Operations and Maintenance Guide Using CLI).
The ISAM-V supports manually triggered GRACEFUL GEO Fail-over / Fail-Back,
meaning that a SIP termination is individually moved to the GEO Back-Up / Primary
site on the condition that the SIP termination has the call state “on-hook”. For any
other call state, the system will defer the GEO Fail-Over for this SIP termination till
the call state has become “on-hook”.
The ISAM-V supports manually triggered FORCED GEO Fail-over / Fail-Back,

meaning that all ongoing dialogs and transactions are immediately aborted and that
all SIP terminations become immediately moved to the GEO Back-up / Primary site
(The system does not await the “on-hook” call state of the SIP termination to perform
the GEO Fail-over / Fail-Back).
Neither in the graceful, nor in the forced GEO Fail-over / Fail-back, ongoing dialogs
and transactions are transferred, and this neither at the signaling plane (SIP) nor at
the media plane (RTP).
SIP ISAM Voice: ESA Redundancy and ESA Fail-Over / Fail-Back

Emergency StandAlone redundancy is considered to be a restrictive redundancy
mode of the GEO redundancy. The ESA Primary side has an identical SIP server
topology as if it was a Geo Primary side. However, the Back-up side only hosts a
single ESA SIP server that locally maintains the subscriber database, consistent with
the ESA Primary site IMS provisioning, and that supports a minimum call handling
feature set:
• The Basic Call Service.
• Special lines can be directly connected to Emergency Offices for Emergency Call
• The Billing system is not available
Figure 8-104 SIP ESA redundancy
L2 / L3 ESAPrimary Site
Network
I-CSCF HSS
ISAM-V
ESA Primary S-CSCF

P-CSCF
Site connection
1_1
First Hop SIP Server Redundancy

ISAM-V
ESA redundancy
ESA Back-up ESA

Site connection SIP server
The ISAM-V triggers an autonomous ESA Fail-Over at the moment that the
connectivity with the ESA Primary Site has completely been lost (none of the First
Hop SIP servers at the ESA primary site are still addressable).
A SIP termination is individually moved to the ESA Back-Up site on the condition
that the SIP termination is not involved in a stable call. For any other call state, the
system will defer the ESA Fail-Over for this SIP termination till the call state has
become “on-hook”.
The ISAM-V does not support the DNS location service for the ESA Back-up site.
The ISAM-V triggers an autonomous ESA Fail-Back at the moment that at least one
of the SIP servers located at the ESA Primary Site can again be addressed.
A SIP termination is individually moved to the ESA Primary site on the condition
that the SIP termination has the call state “on-hook”. For any other call state, the
system will defer the ESA Fail-Back for this SIP termination till the call state has
become “on-hook”.
The ISAM-V does not transfer neither ongoing dialogs nor ongoing transactions to
the ESA Primary / Back-up site, and this neither at the signaling plane (SIP) nor at
the media plane (RTP).
SIP ISAM Voice: NT switch-over interaction with SIP server Redundancy

The Voice LT board monitors the receipt of the Uplink Switch-over notification from
the NT. Upon the receipt of this signal, meaning that an NT switch-over was
triggered, the LT board starts a 3 minute “restoration-blocked” timer. While this
timer is running, the complete Geo and SIP server Fail-over / Fail-back handling
becomes blocked meaning that neither a SIP server Fail-over, nor a SIP server
Fail-back, Geo Fail-Over or Geo Fail-back can be triggered and this neither
autonomously nor manually.
The ISAM-V also does not block any out-of-dialog request, any in-dialog request,
foreground health service monitoring, background health service health monitoring,
DNS look-up request during the period that the “restoration-blocked” timer is
running.
Overload Protection
Megaco ISAM Voice: MG (ISAM Voice Server) Overload Protection

The overload protection, based on software Watchdog monitoring, as supported by
the Voice server aims at guaranteeing self-protection and robustness for the ISAM
Voice.
Software Watchdog Monitoring
The software Watchdog monitors the system in verifying whether all defined
software tasks become scheduled in a reasonable time frame. Should this not be the
case anymore, the software Watchdog will trigger a software application-defined
call-back function in trying to resolve the actual CPU overload problem. The actions
taken by the several software applications depend on these software application
policies.
The software Watchdog's responsibility is to detect that there is a problem in the
system, not to resolve the problem. The latter aspect is the responsibility of the
clients that subscribed to the software Watchdog warnings.
An overload situation is reached when the Voice server runs at 100% of its CPU
capacity. In such a situation, the received Megaco packets get a priority treatment;
Received Line events (off-hook, on-hook, flash-hook, dialed digits…) run the risk to
be ignored. This depends on the robustness level being applicable at that moment:
• Robustness Level 1: reached when the Voice Server remains running at 100% of
its CPU capacity during the next 40 seconds.
• A Megaco “ADD” command being received from the MGC is replied with error 510
(Insufficient Resources).
• Any incoming “auditvalue” or “auditcapability” command is discarded (this
includes the “heartbeat” audit too).
• Robustness level 2: reached when the Voice Server runs in Level 1 mode and
remains running at 100% of its CPU capacity during the next 160 seconds.
• Any new Megaco command (Add, Modify, Subtract, Move, AuditValue,
AuditCapabilities and ServiceChange) being received from the MGC is discarded
by the Voice server.
• Intra voice subsystem polling intervals are enlarged (This also includes the intervals
to establish / maintain the XLES connection with the voice LT boards)
• Commands been received from the MGC but not yet replied by the Voice server, are
treated with long timer timeout; no “pending” will be sent for those transactions.
• Robustness level 3: reached when the Voice server runs in Level 2 mode and
remains running at 100% of its CPU capacity during the next 320 seconds.
• The Voice server initiates a board reset.
Outgoing Megaco packets as well as outgoing internal signaling (XLES) packets
remain treated as is the case when the Voice server runs in a non-overload situation.
MG Control Overload package
An additional overload mechanism based on CPU load monitoring and in line with
H.248.11 (MG Control Overload Package) is implemented (ocp).
This package protects an MG from processing overload that prevents the timely
execution of Megaco transactions.
The MGC, supporting the MG Control Overload Package, adaptively throttles the
rate with which it sets up calls using the ISAM Voice Server to maximize the
effective throughput of the MG whilst bounding its response times.
It does this by throttling the rate at which transactions that set-up new calls or that
new call legs are sent to the overloaded MG, so the rate of overload notifications
which the MGC receives from the overloaded MG converges to a suitably low level.
To prevent a toggling between CPU-overload and end-of-CPU-overload, an (End of)
Overload Persistency Time has been introduced.
The Overload Persistency Time is the time period the CPU load of the ISAM Voice
Server must exceed the High-Water-Mark before it can enter the CPU overload state.
Similarly, the End of Overload Persistency Time is the time period the CPU load of
the ISAM Voice Server must be below the Low-Water-Mark before it leaves the
CPU overload state.
The End of Overload Persistency Time is set larger than the Overload Persistency
time as to ensure that the CPU load is below the Low-Water-Mark for a sufficiently
long time so as not to immediately cause a new CPU overload situation.
• CPU load monitoring:
• Monitors the overall CPU load of the Voice server by measuring the run time of the
IDLE task.
• Informs registered software applications in case of overload detection
• Upon being notified of an overload situation, the software application takes action
to reduce the load.
• CPU load monitoring parameters (not configurable):
High water (percentage): 95% (5% IDLE task)
Low water (percentage): 93% (7% IDLE task)
Overload persistency (time): 2000 ms
End of overload persistency (time): 3000 ms
Sample interval (time): 1000 ms (each sample period, the CPU load (as a function
of the time given to the idle task) is measured)
• Upon the receipt of Overload-condition notification, the Voice server takes the
following actions:
• If requested by MGC and after having received and replied to a Megaco “ADD”
command, report the ocp/mg_overload event (irrespective of the events reporting
settings being configured in the H.248 MIB.
• If not requested by the MGC, reports the ocp/mg_overload event if the
MG-Overload event is enabled in the H.248 MIB (after having received and replied
to a Megaco “ADD” command).
• Raise the MG-Overload alarm.
• Upon the receipt of Overload-condition-Ended notification, the Voice server
takes the following actions:
• Stop the reporting ocp/mg_overload event.
• Clear the MG-Overload alarm
SIP ISAM Voice: SIP Overload Handling

Transactions are the main building blocks of the SIP protocol; Each dialog is
composed out of a number of independent message exchanges called transactions.
A SIP transaction consists of a single request and any responses to that request,
which include zero or more provisional responses and a final response.
Limiting the total number of simultaneous active transactions at the LT board level
has proven to be an effective way to safeguard the system. By introducing a
Maximum Transaction Limit (MaxTx), the LT board becomes protected against
consuming all the available system resources when high loads of incoming SIP
traffic need to be processed.
The MaxTx value is an internal system dimensioning parameter set by Alcatel
Lucent in accordance with the engineered capacity of the system. However, if
MaxTx Limit is reached, the system does not simply react by gently rejecting all
new, incoming, out-of-dialog SIP requests by sending a 503 “Service Unavailable”
response including a Retry-After header.
Instead, the following rules were incorporated as a local prioritization policy when
applying the MaxTx Limit:
• Requests for ongoing sessions have priority over requests that setup a new
session.
• Response messages are not targeted by overload protection.
• Requests that relieve stress from the system are not targeted by overload
protection mechanisms
• Outgoing calls/requests are not subjected to MaxTx
The following incoming SIP requests are considered “priority” requests:
• Session refreshes (in-dialog INVITE requests with Session-Expires header)
• in-dialog requests such as BYE, PRACK, UPDATE and INFO
• CANCEL requests
• out-of-dialog OPTIONS requests (typically used for heartbeat/polling)
Figure 8-105 shows the system behavior.
Figure 8-105 SIP overload handling
Nbr of transactions in use

Zone 3
Total Tx Limit
margin Zone 2
MaxTx limit
Zone 1
time
• Zone 1: Incoming traffic stays below Max Tx Limit: All incoming SIP requests
are accepted
• Zone 2: Incoming traffic rises above MaxTx but below Total Tx Limit: All
low-priority SIP requests are rejected with a 503 Service Unavailable response;
High priority requests are still handled
• Zone 3: Incoming traffic reaches Total Tx Limit: No more SIP transactions
available in the system; All incoming SIP requests are rejected with a 503 Service
Unavailable response
8.19 Quality of Service
For VoIP to be a realistic replacement for standard public switched telephone

network (PSTN) telephony services, customers need to receive the same quality of
voice transmission they receive with basic telephone services, meaning consistently
high-quality voice transmissions. Like other real-time applications, VoIP is
extremely sensitive with regard to bandwidth and delay. For VoIP transmissions to
be intelligible to the receiver, voice packets should not be dropped, excessively
delayed, or suffer varying delay (otherwise known as jitter).
VoIP can guarantee high-quality voice transmission only if the voice packets, for
both the signaling and the voice channel, are given priority over other kinds of
network traffic.
For VoIP to be deployed so that users receive an acceptable level of voice quality,
VoIP traffic must be guaranteed certain compensating bandwidth, latency, and jitter
requirements. QOS ensures that VoIP voice packets receive the preferential
treatment they require.
P-bit marking (layer 2) and DSCP marking (layer 3) for signaling and voice
(including fax and modem) traffic are supported.
The p-bit as well as the DSCP values are configurable for signaling and voice traffic.
Megaco ISAM Voice
• Signaling traffic: The p-bit and DSCP values are configurable at Media Gateway
level.
• Voice traffic (including fax and modem): The p-bit and DSCP values are
configurable at Media Gateway and Termination level.
SIP ISAM Voice
• Signaling traffic: the p-bit and DSCP values are configurable at SIP UA level.
• Voice traffic (including fax and modem): the p-bit and DSCP values are
configurable at SIP UA level.
8.20 DNS interworking
Megaco ISAM Voice

DNS interworking is not supported for Megaco ISAM Voice.
SIP ISAM Voice

The usual Management interface (SNMP, CLI) allows configuring the SIP servers
by manual input or for these values to be retrieved through DNS access.
In the latter case, either the Domain Name or the Fully Qualified Domain Name
(FQDN) must be specified to allow the system to resolve the related IP address by
making use of the Domain Name Service.
To resolve Domain names and/or Fully Qualified Domain Names, the ISAM Voice
supports the NAPTR, SRV and/or A resource record look-up to recursive Domain
Name Servers.
In addition, to guarantee the Domain Name Service availability, the ISAM Voice
supports DNS server redundancy, that is multiple DNS servers can be provisioned
whereby the DNS Server being provisioned with the highest priority is addressed as
the primary DNS server.
Should no reply be received from the primary DNS Server, then the DNS look-up is
repeated to the DNS server with the next highest priority in the list. This repeat cycle
may be continued till a reply is received from a particular DNS server in the list or
the end of the list is reached.
Should all Domain Name servers once been queried but without success and the DNS
Maximum Number of Retransmissions parameter has been provisioned with a value
different from zero, then the ISAM Voice shall again retransmit the DNS look-up to
the Name Servers in the list, starting again with the highest priority DNS server.
Should still no reply be received from none of the DNS servers in the list, then the
re-initiation of the DNS look-up over the complete list will be repeated for as many
times as provisioned in the afore mentioned parameter. Upon the maximum number
of Retransmissions handled, an alarm is raised notifying the customer that none of
the DNS servers reply.
To support the Domain Name Service for GEO redundant network topologies, the
ISAM Voice allows to provision a separate list of DNS servers for the Geo Primary
and the Geo Back-up site.
The ISAM Voice caches the retrieved NAPTR, SRV and A resource records for a
period equalling:
{MIN {DNS Purge Time; MIN of [NAPTR,SRV,A] TTL values for a particular DN}}
whereby the provisionable DNS Purge Timer allows to limit the TTL value, should
some of the resource records own an excessively long TTL value.
In order to reduce the call set-up elapse time and/or to reduce the burden on the
network, where possible, the DNS Resolver limits the number of DNS queries to a
strict minimum. This is achieved by supporting the “additional section” in the DNS
server reply.
8.21 BITS Support
An accurate synchronization is mandatory for the voice service, especially for

voice-band-data services and ISDN services. The NT can be connecting by an
external BITS clock or using its integrated BITS module (< 5ppm) to reach a decent
voice quality. The NTs without BITS module (50ppm) are not valid and not
permitted for voice application.
8.22 Narrowband Line Testing
Megaco ISAM Voice

See chapter “Line testing features”.
SIP ISAM Voice
See chapter “Line testing features”.
8.23 Termination local loop unbundling
ISAM Voice with FD-Combo ETSI practice has been optimized for the combo
service deployment (combined PSTN and xDSL services).
In such a situation it might be possible that subscribers desire to have the xDSL
service provided by a different service provider than the integrated voice service.
This can be achieved through a correct configuration of the Local Loop Unbundling
relay (configurable on a per subscriber basis).
The default setting of the LLU relay is that there is only a straight connection of the
subscriber copper pair to the Voice LT.
Megaco ISAM Voice
Local loop unbundling is supported.
SIP ISAM Voice
Local loop unbundling is supported.
8.24 Alarm Treatment
Alarm Definition
Megaco Based ISAM Voice

Alarms are defined to warn the customer about:
• A loss of the Control Association with the Media Gateway Controller.
• A loss of the Control Association with the ASP.
• A loss of the XLES connection between the Voice server and voice LT board.
• A mismatch between the planned and the actually equipped voice LT board type.
• A H.248 subscriber been configured at the ISAM Voice is not known by the
Media Gateway Controller.
• The current threshold of the physical POTS port being exceeded.
• The temperature threshold of the physical POTS port being exceeded.
• A L1 activation failure at an ISDN line.
• The current threshold of the physical ISDN port being exceeded. (One of the 2
wires is grounded).
• Line showering.
• The Voice Server having lost all persistent data after board reset.
• The Voice Server database storage area at the board being occupied for at least
90%.
• The Voice Server not being able to activate the most recent downloaded database.
• Media gateway overload.
• A Voice Database corruption.
• An invalid CDE file.
• The CDE file being missing.
• A CDE file activation failure due to hash key mismatch.
SIP Based ISAM Voice

Alarms are defined to warn the customer about:
• The Digit Map that is not usable.
• A lack of resources that prohibits the Voice LT board from establishing additional
calls.
• The DHCP server that is not reachable.
• A SIP first hop server that is not reachable.
• The register server that is not reachable.
• A SIP subscriber been configured at the ISAM Voice not known by the IMS core
network.
• The current threshold of the physical POTS port being exceeded. (One of the 2
wires is grounded).
• The temperature threshold of the physical POTS port being exceeded.
• A SIP Registration request failure due to a domain name being unresolvable.
• A SIP Registration request failure due to an authentication failure.
• A SIP Registration request failure due to a transaction timeout.
• A SIP Registration request failure due to a non-successful response.
• A SIP Invite request failure due to a domain name being unresolvable.
• A SIP Invite request failure due to an authentication failure.
• A SIP Invite request failure due to a transaction timeout.
• A SIP Invite request failure due to a non-successful response.

• A SIP Subscribe request failure due to a non-successful response.
• Jitter Buffer Fill Level TCA threshold being exceeded.
• A DNS look-up failure.
• Not any DNS server being configured.
• None of the SIP first hop servers still reply.
• No SIP first hop server being configured.
• A mismatch between the transport protocol(s) actually supported by ISAM Voice
and the transport protocol(s) to be used to access a SIP first hop.
• A Voice Database corruption.
• An invalid CDE file.
• The CDE file being missing.
• A CDE file activation failure due to hash key mismatch.
Subscriber Line Showering
Megaco Based ISAM Voice

In case the amount of on-hook and/or off-hook events for a particular subscriber line
exceeds 20 events / minute, the subscriber line will be put in Line Showering state,
this service change is notified to the Media Gateway Controller and an alarm is
raised.
This means that all subsequent events still occurring on this subscriber line will be
ignored by the system; the subscriber is not able anymore to make outgoing calls nor
is the subscriber able to receive terminating calls.
Also from a narrowband line test perspective, when in showering state, the
subscriber line is observed as being out-of-service.
Once the amount of on-hook and/or off-hook events decreases to less than 10 events
/ minute, the system will put the subscriber line back into normal operation state.
The upper and lower event thresholds are not configurable, neither in the CDE
profile nor in the MIB.
SIP Based ISAM Voice

In case the amount of on-hook and/or off-hook events for a particular subscriber line
exceeds 20 events / minute, the subscriber line will be put in Line Showering state.
No alarm is raised; The system continues to handle the subscriber line being put in
showering state as if it was not put in this state.
8.25 Lawful Intercept
Overall Lawful Intercept strategy

The global Lawful Intercept (LI) solution complies with the international
standardization definition of ETSI TISPAN WG7 and ES 201 671(ETSI TC LI). LI
is considered to be fully transparent for ISAM Voice access node:
• Voice packet replication is assumed to be done by external equipment situated in
the voice network.
• The control path is assumed to provide the IP address of the external equipment
as the destination address of the bearer channel.
Megaco ISAM Voice: External Packet Forwarding (EPF)

In order to support Lawful Intercept, voice traffic exchanged between two voice
termination points must be intercepted by an interception point (CCIF and IRIIF)
prior to receipt at the destination voice termination point.
In the feature described hereafter, the interception point is situated outside the ISAM
Voice access node, further upstream in the voice network of the customer.
Obviously, all voice traffic originating at an ISAM Voice access node and destined
to either a termination point connected to the same ISAM Voice access node, or a
termination point connected to an ISAM Voice access node that subtends to the
originating ISAM Voice, or a termination point connected to a remote ISAM Voice
access node, or a termination point that resides outside the ISAM Voice cluster, must
be brought outside of the originating ISAM Voice access node as to allow this voice
traffic to be tapped to the Lawful Intercept device.
To serve such Lawful intercept topology, Megaco ISAM Voice allows enabling the
External Packet Forwarding facility. In addition, the EPF facility requires the IP
address of the external device to which the voice traffic is to be forwarded as a
configuration input. The external destination device must be directly connected to
the ISAM Voice.
When EPF is enabled, all voice traffic that originates from a voice termination point
A connected to the ISAM Voice and destined to a voice termination point B, either
connected to the same ISAM Voice, or connected to an ISAM Voice that subtends
to the former ISAM Voice, or connected to an ISAM Voice that together with the
former ISAM Voice subtends to the same Hub ISAM Voice, or to an ISAM Voice
connected by means of a layer 2/layer 3 aggregation network with the former ISAM
Voice, is forwarded in upstream direction to the external device as being pointed to
by the configured IP address prior to the downstream forwarding to the destined
voice termination point.
The same forwarding principle as mentioned before, applies when either voice
termination point A or voice termination point B becomes replaced by the Voice
server due to the support of some supplementary services or the support of an
optimized IP addressing scheme.
Local ISAM Voice RTP traffic switching:
To allow the support of the External Packet Forwarding facility, the RTP traffic will
always be switched along the SHUB, even if the two voice terminations among
which the RTP traffic is to be exchanged are connected to the same voice LT board.
Restrictions:
1 The External Packet Forwarding facility is supported on all equipment practices.
2 The External Packet Forwarding facility is supported on the HUB, Subtending
and Remote ISAM Voice access nodes.
3 The External Packet Forwarding facility is supported on VLANS of type
“Voice-VLAN” and “Residential Bridge”.
4 The External Packet Forwarding facility supports L2 aggregated network links
through static L2 aggregation group configuration.
through LACP.
6 The External Packet Forwarding facility supports xSTP.
7 The External Packet Forwarding facility is supported for POTS only (excluding
T.38).
8 The External Packet Forwarding facility is supported in case the ISAM Voice
Access node connects directly or by means of (an) intermediate ISAM Voice
access node(s) to the external EPF device by means of a L2 switching network.
9 Supporting (enabling) the External Packet Forwarding facility is mutual
exclusive to the support (configuration) of the private IP addressing topology (IP
Address and IP Subnet reduction topology).
10 The External Packet Forwarding facility shall only be enabled for the VLAN that
carries the RTP traffic (might be a vlan sharing both RTP and signaling traffic).
11 The External EPF device must allow to disable the ICMP Redirect facility.
Figure 8-106 Megaco ISAM Voice - Switched device - External Packet Forwarding
enabled
NT board Signaling
XLES server
IP address
board L2 board
aggregation
network
NT board NT board
L3
aggregation
network
board board
Edge Router serves as

"external device" from
MGC ASP where the voice traffic
is tapped to the LI device
SoftSwitch
Figure 8-107 Megaco ISAM Voice - Switched device - External Packet Forwarding
disabled
NT board Signaling
XLES server
IP address
board L2 board
aggregation
network
NT board NT board
L3
aggregation
network
board board
MGC ASP
SoftSwitch
SIP ISAM Voice: External Packet Forwarding (EPF)

In order to support Lawful Intercept, voice traffic exchanged between 2 voice
termination points must be intercepted by an interception point (CCIF and IRIIF)
prior to receipt at the destination voice termination point.
In the feature described hereafter, the interception point is situated outside the ISAM
Voice access node, further upstream in the voice network of the customer.
Obviously, all voice traffic originating at an ISAM Voice access node and destined
to either a termination point connected to the same ISAM Voice access node, or a
termination point connected to an ISAM Voice access node that subtends to the
originating ISAM Voice, or a termination point that resides outside the ISAM Voice,
must be brought outside of the originating ISAM Voice access node to allow this
voice traffic to be tapped to the Lawful Intercept device.
To serve such Lawful intercept topology, SIP ISAM Voice allows enabling the
External Packet Forwarding facility. In addition, the EPF facility requires the IP
address of the external device to which the voice traffic is to be forwarded as a
configuration input. The external destination device must be directly connected to
the ISAM Voice.
When EPF is enabled, all voice traffic that originates from a voice termination point
A connected to the ISAM Voice and destined to a voice termination point B, either
connected to the same ISAM Voice, or connected to an ISAM Voice that subtends
to the former ISAM Voice, or connected to an ISAM Voice that together with the
former ISAM Voice subtends to the same Hub ISAM Voice, is forwarded in
upstream direction to the external device as being pointed to by the configured IP
address prior to the downstream forwarding to the destined voice termination point.
Local ISAM Voice RTP traffic switching:

To allow the support of the External Packet Forwarding facility, the RTP traffic will
always be switched along the SHUB, even if the 2 voice terminations among which
the RTP traffic is to be exchanged are connected to the same voice LT board.
This RTP switching model applies to the SIP Centralised Model only.
(SIP Distributed model: when RTP traffic is to be exchanged among 2 voice
terminations connected to the same voice LT board, the RTP traffic is switched
internally at the voice LT board.)
Restrictions:
1 The External Packet Forwarding facility is supported on all equipment practices.
2 The External Packet Forwarding facility is supported on the HUB, Subtending
and Remote ISAM Voice access nodes.
3 The External Packet Forwarding facility is supported on VLANS of type
"Voice-VLAN" and "Residential Bridge".
through static L2 aggregation group configuration.
through LACP.
6 The External Packet Forwarding facility supports xSTP.
7 The External Packet Forwarding facility is supported for POTS only (excluding
T.38).
8 The External Packet Forwarding facility is supported in case the ISAM Voice
Access node connects directly or by means of (an) intermediate ISAM Voice
access node(s) to the external EPF device by means of a L2 switching network.
9 Supporting (enabling) the External Packet Forwarding facility is mutual
exclusive to the support (configuration) of the private IP addressing topology (IP
Address & IP Subnet reduction topology).
10 The External Packet Forwarding facility shall only be enabled for the VLAN that
carries the RTP traffic (might be a vlan sharing both RTP and signaling traffic).
11 The External EPF device must allow to disable the ICMP Redirect facility.
Figure 8-108 SIP ISAM Voice - Switched device - External Packet Forwarding enabled
NT board NT board

board L2 board
aggregation
network
NT board NT board
L3
aggregation
network
board board
Edge Router serves as

"external device" from
MGC ASP where the voice traffic
is tapped to the LI device
SoftSwitch
Figure 8-109 SIP ISAM Voice - Switched device - External Packet Forwarding disabled
NT board NT board

board L2 board
aggregation
network
NT board NT board
L3
aggregation
network
board board
MGC ASP
SoftSwitch
8.26 Compliancy to standards
ISAM Voice is fully/partially compliant to the following standards (further details

are provided in the related Protocol Information Compliancy Sheets (PICS
documents)):
Megaco ISAM Voice
• RFC768, RFC791, RFC792, RFC826, RFC894, RFC919, RFC920, RFC950,

RFC1157, RFC2327, RFC2960, RFC3057, RFC3389, RFC3550, RFC4233,
RFC4734
• IEEE Std 802.3, IEEE Std 802.1Q, IEEE Std 802.1P
• ITU-T Study Group 16: H248.1v2, H248.1v3 annex F, H248.2, H248.3, H248.8,
H248.11, H248.14, H248.16, H248.23, H248.26, H248.27, H248.34, H248.45
• ITU-T Study Group II: Basic Call Progress Tones Generator with Directionality,
Expanded Call Progress Tones Generator Package, Basic Services Tones
Generation Package.
• ITU-T Recommendation Q.921, ITU-T T.38 Recommendation Fax over IP,
• ITU-T recommendation V.23 (FSK), ITU-T recommendation Q.552:
Transmission characteristics at a 2-wire analogue interface of digital exchanges
• ITU-T Recommendation Q.1950: Bearer independent call bearer control
protocol,
• ITU-T Recommendation V.152: Procedures for supporting voice-band data over
IP networks
• ITU-T I.603 SERIES I: INTEGRATED SERVICES DIGITAL NETWORK
(ISDN) Maintenance principles; Application of maintenance principles to ISDN
basic accesses
• Telcordia Bell 202 (FSK)
• ETSI EN 300 659-1 V1.3.1 DTMF for on-hook data transmission
• ETSI EN 300 659-1 V1.3.1, ETSI EN 300 659-2 V1.3.1, ETSI EN 300 659-3
V1.3.1: Subscriber line protocol over the local loop for display (and related)
services.
• ETSI EMC 300 386 v1.3.1: Electromagnetic Compatibility Requirements
• ETSI ES 283 002: H.248 Profile
• Telcordia recommendation GR-30 LSSR: “LSSR: Voice band Data
Transmission Interface (FSD 05-01-0100)”, 1998
• Calling Line Identification service SIN 227, issue 3.2. British Telecom
specification, 2002
SIP ISAM Voice
• RFC768, RFC791, RFC792, RFC950, RFC919, RFC920, RFC2131, RFC2327,

RFC2833, RFC2976, RFC3261 (ETSI TS102 027-1), RFC3262, RFC3263,
RFC3264, RFC3265, RFC3311,RFC3321, RFC3323, RFC3325, RFC3326,
RFC3389, RFC3515, RFC3550, RFC3551, RFC3665, RFC3680, RFC3725,

RFC 3842, RFC3891, RFC3892, RFC3959, RFC3960, RFC4028, RFC4244,
RFC4780, RFC5009, RFC5366, RFC5806
• Draft-kaplan-sip-session-id-02: A Session Identifier for the Session Initiation
Protocol (SIP)
• Draft-ietf-sipping-sip-offer/answer: SIP (Session Initiation Protocol) Usage of
the Offer/Answer Model
• ITU-T Recommendation V.152: Procedures for supporting voice-band data over
IP networks
• 3GPP ETSI TS 23.167: IP Multimedia Subsystem (IMS) emergency sessions
• 3GPP ETSI TS 23.228: IP Multimedia Subsystem (IMS)
• 3GPP ETSI TS 24.228: Signalling flows for the IP multimedia call control based
on Session Initiation Protocol (SIP) and Session Description Protocol (SDP)
• 3GPP ETSI TS 24.229: IP multimedia call control protocol based on Session
Initiation Protocol (SIP) and Session Description Protocol (SDP)
• 3GPP ETSI TS 24.406: Message Waiting Indication (MWI)
• 3GPP ETSI TS 24.407: Originating Identification Presentation (OIP) and
Originating Identification Restriction (OIR)
• 3GPP ETSI TS 24.408: Terminating Identification Presentation (TIP) and
Terminating Identification Restriction (TIR)
• 3GPP ETSI TS 24.410: Communication HOLD (HOLD)
• 3GPP ETSI TS 24.447: Advice Of Charge (AOC)
• 3GPP ETSI TS 24.504: Communication Diversion (CDIV)
• 3GPP ETSI TS 24.505: Conference (CONF)
• 3GPP ETSI TS 24.529: Explicit Communication Transfer (ECT)
• 3GPP ETSI TS 24.615: Communication Waiting (CW) using IP Multimedia (IM)
Core Network (CN) subsystem
• 3GPP ETSI TS 183.043: IMS-based PSTN/ISDN Emulation
• 3GPP ETSI TS 183.047: NGN IMS Supplementary Services; Advice Of Charge
(AOC)
8.27 ISAM Voice migration
Off-line SW Migration
The ISAM Voice uses the ISAM offline migration procedure, that is, the integrated
voice service databases and related CDE profiles are considered to be an integral part
of the ISAM offline database migration (next to the NT and SHub databases). This
implies that at software migration time:
• The integrated voice service databases and related CDE profiles are uploaded to
the migration server offline migrated via the Push Button Migration Tool.
• The offline migrated integrated voice service database and associated CDE
profiles are downloaded to the ISAM and activated together with the new
software package.
Megaco ISAM Voice off-line software migration

An “Upgrade/Migration cluster” is the aggregation of all ISAM Voice clusters
served by a hub ISAM Voice node, this hub ISAM Voice node included.
Note — The following restriction applies:
All Voice servers equipped in a hub ISAM Voice node are supervised
by one and the same Voice Service Provider.
In order for the integrated voice service to work correctly, the same software package
must be downloaded to all ISAM Voice nodes of an ISAM Voice cluster, that is, in
particular with focus on the integrated voice service, the software (maintenance)
release on the voice LT boards must be the same as the software (maintenance)
release on the Voice server and this for the complete ISAM Voice cluster.
The same applies within one ISAM Voice node. Only one software (maintenance)
release can be active at an ISAM Voice node at the same time.
This implies that all Voice server pairs in the hub ISAM Voice node must run the
same software (maintenance) release. As a consequence, for the integrated voice
service to work, all ISAM Voice nodes within the same upgrade/migration cluster
must be on the same software (maintenance) release.
The above rules imply that for both a software upgrade and a software migration, the
upgrade/offline migration procedure for the full upgrade/migration cluster must be
completed in a single maintenance window.
Figure 8-110 Voice upgrade/migration cluster (centralized topology)

Voice Upgrade / Migration Cluster concept in the context of
a Centralised Voice Topology.
Upgrade / Migration Cluster

Main ISAM Voice Node
Voice Voice Voice Voice Voice Voice Voice Voice

Server Server Server Server Server Server Server Server
Pair 1 Pair 2 Pair 3 Pair 4 Pair 5 Pair 6 Pair 7 Pair 8
LTs LTs LTs LTs LTs LTs LTs LTs

Non-main Non-main Non-main Non-main Non-main Non-main Non-main Non-main
node 1a node 2a node 3a node 4a node 5a node 6a node 7a node 8a

node 1b node 2b node 3b node 4b node 5b node 6b node 7b node 8b

node 1x node 2x node 3x node 4x node 5x node 6x node 7x node 8x

Cluster 1 Cluster 2 Cluster 3 Cluster 4 Cluster 5 Cluster 6 Cluster 7 Cluster 8
Figure 8-111 Voice upgrade/migration cluster (distributed topology)

Voice Upgrade / Migration Cluster concept in the context of
a Distributed Voice Topology.
Upgrade / Upgrade / Upgrade / Upgrade / Upgrade / Upgrade / Upgrade / Upgrade /

Migration Migration Migration Migration Migration Migration Migration Migration
Main ISAM Main ISAM Main ISAM Main ISAM Main ISAM Main ISAM Main ISAM Main ISAM
Voice Node 1 Voice Node 2 Voice Node 3 Voice Node 4 Voice Node 5 Voice Node 6 Voice Node 7 Voice Node 8

Server Server Server Server Server Server Server Server
Pair Pair Pair Pair Pair Pair Pair Pair

Non -main Non -main Non -main Non -main Non -main Non -main Non -main Non -main
node 1a node 2a node 3a node 4a node 5a node 6a node 7a node 8a

node 1b node 2b node 3b node 4b node 5b node 6b node 7b node 8b

node 1x node 2x node 3x node 4x node 5x node 6x node 7x node 8x

Megaco ISAM Voice Backwards Compatibility in the Migration Scenario

Under the conditions and constraints as stipulated in the section below, ISAM Voice
indeed strives for backwards compatibility between releases, starting from R4.0v
onwards, in that any next voice release after R4.0v will take backwards compatibility
into account. That is, both the R4.0v maintenance releases and the R4.1v releases
(main and maintenance) will take into account backwards compatible with R4.0v.
Disclaimer: Alcatel-Lucent, though remaining confident that this might be a rare
case, is not in a position to guarantee backwards compatibility at all time, as, due to
new feature introductions or problem resolution reasons, Alcatel-Lucent can be
forced to break the backwards compatibility in a certain release, even under the
conditions and constraints as stipulated below. In case of such happening, the
customer will be informed by Alcatel-Lucent, clearly specifying the reasons why the
backwards compatibility had to be broken and the related consequences for the
customer. Also, Alcatel-Lucent will recover the backward compatibility on the
earliest successive release possible.
Conditions and restrictions:
Backwards compatibility over ISAM Voice releases is considered:
• Between a main release and its maintenance releases (for example, R4.0v and
R4.0.02c), starting from R4.0v onwards
• Between 2 releases of 2 consecutive release streams (for example, R4.0.03d and
R4.1.02c), starting from R4.0v onwards
• From the xVPS pair to the voice boards, that is, it is assumed the voice boards are
always at a lower or equal release then the xVPS pair, but never at a higher release
This ISAM Voice backwards compatibility has the following restriction:

• New services, as part of the newly introduced release, might not work as long as
there is more than one release active in the network.
ISAM Voice backwards compatibility is supported only at following conditions:

• At any time there are no more than 2 different releases in the network, being main
or maintenance releases of consecutive release streams
• Having 2 releases in the network can last for at most 2 weeks
Failing to do so will not only block any roll-out of new services in the network of
the customer, but will also make it impossible to guarantee tracking and fixing
problems in the voice network
• Before an upgrade or migration is started to a next release, all ISAM Voice access
nodes in the network must be at the same release (main or maintenance)
SIP ISAM Voice off-line SW migration

Since the scope of the Voice upgrade/migration cluster principle is restricted to a
single ISAM access node, an upgrade/migration of a SIP ISAM Voice access node
follows exactly the upgrade and offline migration procedure for an ISAM access
node.
H.248 to SIP functional Migration

ISAM Voice allows a voice access node / voice cluster being deployed in an H.248
based integrated voice service mode, to migrate to a SIP based integrated voice
service deployment.
The following restrictions apply:
• It is not allowed that such a H.248 to SIP functional migration coincides with
either a software upgrade or an off-line software migration or a Switching to
Routing functional migration (see next chapter).
• The target migration SIP architecture is the centralized architecture.
• A complete voice cluster is functionally migrated in one maintenance window.
• Distinct VLANs for signaling and RTP traffic.
• The same VLAN is used to carry RTP traffic in H.248 and SIP mode.
• The same VLAN is used to carry signaling traffic in H.248 and SIP mode.
• The same VLAN is used to carry OAM traffic in H.248 and SIP mode.
The main logical steps to be taken in the H.248 to SIP functional migration are:
1 Configure the SIP voice database
2 Check the ongoing calls and the emergency calls for graceful shutdown
3 Lock the H.248 MGI interface
4 Disconnect the Voice server at L2 from the voice LT boards
5 (re-)Configure the L2/L3 topology to run in SIP mode
6 Unplan the voice LT boards (configured with capability profile = H.248-profile)
7 Replan the voice LT boards with capability profile = SIP-profile
8 Reload the voice LT board with the SIP software package

9 Perform a SIP voice database NT-LT audit
10 Register the SIP terminations
11 Verify the SIP-based voice service
12 Unplan the Voice server (the Voice server must be kept running till the
verification has proven that the SIP-based voice service behaves correctly)
Switching to Routing functional Migration

ISAM Voice allows a voice access node/voice cluster being deployed in a switched
mode, to migrate to a routed mode.
The switching to routing functional migration applies to both an ISAM Voice access
node deployed in H.248 mode and an ISAM Voice access node deployed in SIP
mode.
The following restrictions apply:
• A functional migration from switching mode to routing mode may NOT coincide
with:
• a software upgrade
• an off-line software migration
• an H.248 to SIP functional migration.
• ISAM Voice does not support the functional migration of a subtending access
node. In other words, the subtending access node behaves at all times as a
switched device.
• The same signaling VLAN ID remains used at the IACM part of the ISAM Voice
before and after the migration from switching device to routing device.
• The same RTP VLAN ID remains used at the IACM part of the ISAM Voice
before and after the migration from switching device to routing device.
• The same source / destination signaling IP address remains configured at the
xVPS (H.248) / SHub (SIP).
• The same source / destination RTP IP address remains configured at the xVPS
(H.248) / SHub (SIP and H.248).
The main logical steps to be taken in the switching to routing functional migration
are:
1 Configure the routing protocol (OSPF / RIP)
2 Optionally, configure the static routes
3 (re-)Configure L2/L3 topology to run in route mode.
4 Reset the NT board.
9— Layer 2 forwarding
9.2 The concept of Virtual LAN (VLAN) 9-2
9.3 ISAM Internal Architecture 9-7
9.4 Support for Jumbo frames 9-13
9.5 Subscriber access interface on the LT board 9-13
9.6 iBridge mode 9-16
9.7 VLAN cross-connect mode 9-32
9.8 Protocol-aware cross-connect mode 9-43
9.9 IPoA cross-connect mode 9-47
9.10 Secure forwarding in iBridge and VLAN cross-connect 9-49
9.11 Virtual MAC 9-54
9.12 PPP Cross-connect mode 9-59
9 — Layer 2 forwarding
9.1 Introduction
This chapter focuses on L2 forwarding, consistent with the standards of the Electrical
and Electronics Engineers (IEEE).
Concretely, in the ISAM this involves the iBridge and VLAN cross-connect
forwarding mode.
Note — Strictly speaking, only iBridge and VLAN cross-connect

forwarding modes can be considered as L2 forwarding in term of
IEEE context. For practical reasons however, this chapter will also
cover an additional forwarding mode which is not really part of L2
forwarding family but still closely related: PPP cross-connect
forwarding.
Although PPP cross-connect mode has distinctive differences with
iBridge and VLAN cross-connect, it has also similarities. For more
information, see section “PPP Cross-connect mode”.
9.2 The concept of Virtual LAN (VLAN)
VLANs are standardized by the Institute of Electrical and Electronics Engineers

(IEEE) in 802.1q (VLAN basic concept) and the 802.1ad/D6.0 (VLAN stacking).
VLAN tagging in IEEE 802.1q

Tagging of an Ethernet frame consists of adding a IEEE 802.1q tag of four bytes that
specifies the VLAN ID and the priority (from 0 to 7) that indicate the QoS class.
Table 9-1 shows the frame types used with their properties.
Table 9-1 Frame types
Property Tagged frame Priority-tagged Untagged

frame frame
Carries the tag of four bytes Yes Yes No
Value of VLAN ID Non-zero value Zero NA
Indication priority bits QoS class QoS class NA
Figure 9-1 shows an untagged and a tagged/priority-tagged Ethernet frame.
Figure 9-1 Untagged and tagged/priority-tagged Ethernet frames

Untagged frame
dest src length
preamble SFD data + pad FCS
addr addr type
7 1 6 6 2 46…1500 4
(priority-)tagged frame
MAC client
dest src 802.1q VLAN
preamble SFD length data + pad FCS
addr addr tag tag
type
7 1 6 6 2 2 2 46...1500 4
VLAN Tagging as a means to support Virtual LAN (VLAN

The use of VLAN Tagging on Ethernet frames has allowed the co-existence of a
multiplicity of Virtual LANs (VLANs) which are logically isolated from each other
although sharing the same physical infrastructure. Each VLAN is only aware of the
Ethernet Frames tagged with the specific VLAN tag of this VLAN.
By using the VLAN tags of the frames as VLAN discriminator, end-stations and
frame forwarders within a given VLAN have no contact with end-stations or frame
forwarders operating in another VLAN even when they share the same physical
infrastructure. Figure 9-2 shows an example of VLANs.
Figure 9-2 Example of VLAN
e VLAN A
on 8
9
c kb i tch 7
Ba
6
Sw 5
4
2
3
VLAN B
1
9
8
i tch 7
Sw 6 VLAN C
5
4
3
2
1
In general the VLAN is shared between a group of several end-stations, forming a

meshed configuration. In some special cases, the VLAN is used in a strict
point-to-point configuration between two end-stations. Within a VLAN, frame
forwarding takes place at layer 2 (L2) by using Ethernet-related information.
The ISAM supports the VLAN concept applied to access networks.
Usage of VLANs in access networks

In the access network, each NSP operates in a dedicated VLAN. The role of the
ISAM is to attach every subscriber to the NSP(s) of their choice, that is, to the
corresponding VLAN(s).
Network side
Frames coming from the upstream Ethernet network are generally tagged, each tag
being typical of a given NSP. The frame VLAN tag determines the VLAN the frame
belongs to and the way the ISAM should forward it to the subscriber, via iBridge
mode or VLAN cross-connect mode. Untagged frames can also be received from the
network interface, for example when the ISAM is directly connected to an NSP IP
router. In this case, a port-based default VLAN is required on the network interface.
Subscriber side
On an ADSL link carrying PVCs, the subscriber accesses different NSPs by using
one PVC per NSP. On a PVC frames are typically untagged (in some rare network
deployments, frames could also be priority tagged).
When the ISAM receives untagged frames or priority-tagged frames from the
subscriber, a port default VLAN (or port-and-protocol-based default VLAN)
determines the NSP VLAN on the network side to which the frame must be
forwarded (more on this in section “Forwarding of untagged/priority-tagged frames
received from the subscriber”).
Although not typical, tagged frames can also be used on PVCs to allow multiplexing
several services on the same PVC.
When the ISAM receives tagged frames, the frame tag is used to determine the NSP
VLAN to which the frame should be forwarded. User frames received with an
unexpected tag are discarded. Figure 9-3 shows an example.
Figure 9-3 Example of PVCs used on ADSL links

NE
ADSL link 1
PVC 0,32
default VLAN 100
PVC 0,33
default VLAN 101
PVC 0,34
VLAN 102
ADSL link 2
PVC 0,34
default VLAN 100
VLAN 101, 102
Figure 9-3 shows two ADSL links:

• ADSL link 1 with 3 PVCs:
• PVC 0,32 accepts untagged packets, priority-tagged packets, and packets with
VLAN ID 100
• PVC 0,33 accepts untagged packets, priority-tagged packets, and packets with
VLAN ID 101
• PVC 0,34 accepts tagged packets, with VLAN ID 102
• ADSL link 2 with 1 PVC:
• PVC 0,34 accepts untagged packets, priority-tagged packets, and tagged packets
with VLAN ID 100, 101 and 102
We have seen that for ATM-based DSL lines, one separate PVC per service (and per
NSP) is deployed and the frames between the ISAM and CPE are typically untagged.
Each PVC is related to a NSP VLAN in the aggregation network and vice versa.
However, this is not possible for VDSL access and point-to-point Ethernet access
since these are based on EFM technology. Hence, tagged traffic on VDSL and
point-to-point subscriber access lines becomes the rule, with each VLAN identifying
a given NSP.
Multi-VLAN tagged subscriber traffic over VDSL lines is actually the equivalent of
multi-PVC over ATM-based DSL lines.
Point to multipoint configuration (1:N) and point to point configurations (1:1)

The ISAM allows two L2 access modes, respectively the 1:N and the 1:1 mode:
• In the 1:N mode, the ISAM allows the NSP network VLAN to be shared by a
group of N subscribers. This is done by means of the iBridging forwarding mode
(also called Residential Bridging)
• In the 1:1 mode, the ISAM allows the NSP network VLAN to be shared by only
one subscriber. This is done by means of the VLAN cross-connect forwarding
mode.
Generic forwarder model in ISAM

The ISAM uses a generic L2 forwarding model directly mapping to the VLAN
concept. In this model, the ISAM associates to every NSP a dedicated L2 forwarder,
that is, an iBridge or a VLAN cross-connect. Each L2 Forwarder operates in the
context of a dedicated VLAN on the network side.
Further, the ISAM uses the following notions on the user side:
• Bridge port:
a bridge port is a generic Ethernet interface on the user side. In practice, a bridge
port can be an Ethernet PVC, an EFM link or a physical user Ethernet link. A
bridge port can carry a mix of untagged, priority-tagged or tagged frames.
• VLAN port:
a VLAN port is a generic Tagged Ethernet interface on the user side. In practice,
a VLAN port results from the association of a VLAN ID and a bridge port. So a
VLAN port is the ISAM entry point for user Ethernet traffic tagged with the
corresponding VLAN ID on the corresponding bridge port. Tagged frames

received by the ISAM which cannot be related to a configured VLAN port are
discarded.
• Port Default VLAN ID (PVID):
A bridge port can be configured with a PVID. The PVID has only relevance for
iBridging or VLAN cross-connect. It is the VLAN ID which untagged or
priority-tagged traffic should inherit from this bridge port when subjected to
iBridging or VLAN cross-connect. In that case, untagged frames are considered
by the ISAM “as if” tagged by the user with the PVID. See more details in
section “Forwarding of untagged/priority-tagged frames received from the
subscriber”.
From a black box point of view, the operator needs to create an NSP Network VLAN.
Then, attaching a subscriber to an NSP is done by associating a subscriber VLAN
port to the NSP Network VLAN.
An interesting feature of this generic L2 forwarding model is that it does not impose
that the VLAN port has the same VLAN ID as the NSP VLAN to which it is attached.
This allows the possibility of VLAN translation by which subscribers can access an
NSP using frames tagged with another VLAN than the NSP VLAN. Obviously,
de-coupling network VLAN from user VLAN allows more flexibility in terms of
network deployment.
The need for VLAN translation becomes apparent when comparing with the familiar
multi-PVC model in ATM-based aggregation networks.
In the multi-PVC model, each PVC must be given a VPI/VCI value on the access
link. To facilitate provisioning, these VPI/VCI values are often chosen to be the same
for all subscribers to a given service, for example 8/35 for HSI. These subscriber-side
Virtual Channel Links (VCLs) are then cross-connected to VCLs at the network side
with different VPI/VCI values.
In the multi-VLAN context, the same reasoning applies. Provisioning can be
simplified by using the same C-VLAN IDs at the subscriber side for all subscribers.
These subscriber-side C-VLANs indicate the service. For S+C-VLAN
cross-connects, (see section “S+C-VLAN cross-connect: VLAN stacking for
residential subscribers”) the network side C-VLAN IDs are typically used to identify
the subscriber, with the S-VLAN identifying the service.
Hence a subscriber-side VLAN ID can have a local significance, which means that
the user VLAN ID is just used to select a particular forwarding context. Then, the
subscriber-side VLAN ID is stripped from the packet, the forwarding decision is
made, and a new network-side VLAN ID is supplied with the packet when it is
transmitted on the network interface.
As indicated in previous sections, although multi-VLAN originally came from the
requirement to support multi-services above EFM for VDSL subscriber access lines,
some customers may want to use multi-VLAN on top of PVC for ADSL as well.
Doing so can be interesting to create a uniform network configuration, or to alleviate
some possible CPE limitation.
To limit the configuration complexity of ADSL lines, the operator must however
make a decision per ADSL line and segregate services either via PVCs or via
VLANs. In the latter case, a single PVC will carry all the different VLANs.
Figure 9-4 shows an example of multi-VLAN and VLAN tag translation. In this
example there are two VDSL access lines: EFM1 and EFM2. PVCs supporting
multi-vlans are also shown. Note that this example applies to ADSL, VDSL and
point-to-point Ethernet subscriber access lines.
Figure 9-4 Multi-VLAN and VLAN translation example
Ethernet
T PVC1_VLAN1
Ethernet
NSP 1 VLAN_1 VLAN MAC T PVC2_VLAN1
ports FDB
Ethernet
iBridge T EFM1_VLAN1
Ethernet
T PVC1_VLAN2
NSP 2 VLAN_2 VLAN MAC Ethernet
T PVC3_VLAN17
ports FDB
iBridge Ethernet EFM2_VLAN2
T
VLAN_3 Ethernet
NSP 3 VLAN CC T EFM1_VLAN3
Ethernet
NSP 4 VLAN_4 VLAN CC T EFM2_VLAN34
Ethernet
NSP 5 VLAN_5 VLAN CC T EFM1_VLAN5
EMAN ISAM
Note 1 — Multi-VLAN makes flexible wholesaling possible without

impacting the CPE configuration. For example, starting from a set of
predefined subscriber VLAN tags at the CPE side (say, the same
values hard-coded in all CPEs), it is possible to re-tag the received
packet with a new network VLAN tag, so that the traffic can be passed
to the correct NSP for a specific service.
Note 2 — From R4.1 on, the restriction that one cannot attach two
VLAN ports on the same bridge port to the same Layer 2 forwarding
engine is removed.
9.3 ISAM Internal Architecture
Layer 2 forwarding in ISAM is generally distributed over the LT boards and NT

board in a two stage architecture. There may be also cases where only the NT board
takes part in the Layer 2 forwarding - when users are directly connected to the NT
board or when a subtending ISAM comes in the picture. This is shown in Figure 9-5.
Note — Figure 9-5 does not show the VLAN translation capability on
the user side of the LT board.
Figure 9-5 Layer 2 Forwarding in ISAM
L2 Fwdr
NSP A
L2 Fwdr
NSP B
L2 Fwdr LT
Phy/LAG NSP A
L2 Fwdr
Phy/LAG NSP A
L2 Fwdr
NSP B
L2 Fwdr
NT NSP B
LT
ISAM
The basic strategy for the layer 2 forwarding data plane is that:
• When subscribers are connected to LT boards, the NT board forwards
downstream frames to the proper LT board(s) and the LT board forwards
downstream frames to the proper subscriber line/VLAN.
• It is the LT board that implements the difference between the VLAN
cross-connect mode, the iBridge mode and the stacked iBridge mode. The NT
board behavior is identical for iBridge and VLAN cross-connect.
• It is the LT board that takes care to translate user VLAN into network VLAN
(optionally); the NT board does not perform VLAN translation.
• The NT board behaves as much as possible as a standard bridge. However, some
restrictions may be required or desired for a consistent interworking with the
specific LT boards forwarding modes, iBridge or VLAN cross-connect. User
security and privacy may also require specific rules in the NT board, as further
developed below.
• The NT board and the LT board behave as much as possible as two independent
Layer 2 systems. For example, they both will learn and age independently on
MAC addresses. Note that the ageing timer is independent in the NT board and
the LT boards but for proper operation it should be configured identical. There is
one ageing timer common for all LT boards.
Although the NT board is originally derived from a standard bridge, its behavior will
typically be constrained to fit access network requirements such as for instance
security and privacy. For that purpose the ISAM makes the distinction between ports
facing users and ports facing the EMAN network side:
• Ports connected to subtending ISAMs, to LT boards or directly facing users
instantiate the so-called “user side”. Such ports are considered untrusted.
• Ports connected to the EMAN or directly to service provider equipment (for
example, BRAS) instantiate the so-called “network side”. Such ports are
considered trusted.
With the notion of User side and Network side, the NT has the capability to deviate
from a normal standard bridge in particular in term of controlling traffic switching
(or flooding) and controlling MAC address learning.
In typical network deployment, the NT board will be constrained such that
• Frames received from the network side can be passed:
• back to the network side, possibly on the same physical interface but using another
VLAN (this is to support a ring).
• to the user side (an LT board, a user, or a subtending ISAM).
• Frames received from the user side (an LT board, a user or a subtending ISAM)
can only be passed to the network side.
Note 1 — The forwarding of broadcast frames or frames with

unknown (unicast / multicast) destination MAC address will be based
on these rules: flood to all allowed interfaces only.
Note 2 — The operator can enable communication from user side
back to user side provided that both users are on different physical NT
interfaces thereby allowing inter-LT traffic forwarding. Up to 10
VLAN per NT can support communication from user side back to
user side.
Note 3 — The operator can enable communication from user side
back to the same user side (that is, the same LT board) for the VLAN
supporting communication from user side back to user side. This
system level provisioning command allows intra-LT traffic
forwarding. When this voice services feature is used, the operator
must also invoke secure-forwarding on the LT (see “Secure
forwarding in iBridge and VLAN cross-connect”).
Obviously, the NT board is VLAN aware. More specifically, every NT bridge

instance operates within the context of a single distinct VLAN. Only tagged frames
matching the VLAN of a bridge will be handled by that bridge. If the frame is
multiple tagged, only the most exterior VLAN tag is used to determine whether the
frame should be handled by a given bridge or not.
Another strategy employed to enable ISAM to participate in a maximum of network
deployments scenarios is to subtended network elements (such as remote ISAM)
directly from the LT board, as shown in Figure 9-6.
Figure 9-6 Subtended network elements
UNI port
L2 Fwder
NSP A
L2 Fwder
NSP B UNI port
L2 Fwder LT
NSP A
L2 Fwder
NSP A
L2 Fwder L2 Fwder
L2 Fwder
NSP A
NSP B NSP A
L2 Fwder
L2 Fwder
NSP B L2 Fwder
NT NSP B
NSP B
LT
LT NT
ISAM Subtended ISAM
NNI port
Such deployment scenario introduces the concept of User to Network Interface

(UNI) and Network to Network Interface (NNI).
• A UNI is a reference point for all interactions between subscriber services and the
ISAM.
• An NNI is a reference point for all interactions between a remote aggregator
(business NTU, residential MDU, Ethernet switch, subtended ISAM, …) and the
ISAM.
On the Hub-ISAM, the NNI subtending interfaces will support L2 forwarding

dimensioning required to subtend an aggregation node (such as for example
increased scaling for VLANs, multicast channels and MAC learning, …).
Detailed configuration models
iBridge configuration model

Figure 9-8 shows the iBridge configuration model.
Figure 9-7 iBridge configuration model
RB
VLAN 19
Network Ports Network VLAN LT Ports
RB
VLAN 23
VLAN 19 LT
Phy/LAG (= iBridge)
RB
Phy/LAG VLAN 19
VLAN 23
(= iBridge)
RB
NT VLAN 23
LT
ISAM
To configure a bridge for a given VLAN in the NT board, the operator needs to:
• Create the VLAN
• Associate the proper network / LT / subtending / user interface to this VLAN.
VLAN cross-connect configuration model

The configuration of the NT board is the same as for the iBridge forwarding model,
only the configuration of the LT board is different, as shown in Figure 9-8.
Figure 9-8 VLAN cross-connect configuration model
C 11
VLAN 11 C-VLAN CC
VLAN CC
(=Bridge)
S17 +C23
VLAN 17 S+C-VLAN CC
VLAN CC
(=Bridge)
LT
(No VLAN translation
shown on user side)
VLAN 13 S17 +C29

(=Bridge) S+C-VLAN CC
VLAN CC
S 13
VLAN 19 S-VLAN CC
(=Bridge) VLAN CC
LT
NT
C-, S+C- or
ISAM S-VLAN CC
Note — The different types of VLAN cross-connect (C-VLAN,

S+C-VLAN and S-VLAN) are explained further in this chapter.
9.4 Support for Jumbo frames
To take care of various encapsulation protocols overhead, Jumbo frames with 2048
bytes are supported in the data plane all over the ISAM, including all forwarding
modes (iBridge, VLAN cross-connect, PPP cross-connect, VRF) and all Ethernet
interface types. However, the final frame size will be constrained by the LT hardware
limitation (the hardware of some LT boards cannot support more than 1580 bytes).
This requirement is to allow some room to add protocol overhead to upstream user
frames, in function of the forwarder used.
Note — The requirements for large MTU do not make a distinction
between the network and the user side. Of course, frames from the
user side which are for example encapsulated with MPLS should be
smaller than the allowed maximum.
Figure 9-9 Support for Jumbo frames
3, 4
DSL line
Ethernet MAC larger subscriber Ethernet payload
specific
DA, SA,
SA Qtags, Type/Length, FCS
Edge
1 2 3, 4
MPLS & larger subscriber Ethernet payload
Ethernet MAC (with additional VLAN tags)
other blue sky
DA, SA, Qtags, type/length, FCS
Scope of jumbo frames:

1. To cope with more VLAN tags being added on network side
2. To cope with additional encapsulating protocols, for example, MPLS on network side
3. To cope with user having larger payload data
4. NOT to cope with user having larger payload control
9.5 Subscriber access interface on the LT board
The ISAM has the capability to receive user frames from ATM PVCs (ADSL), EFM
(VDSL) or Ethernet Physical interfaces on the LT board.
Attaching subscribers to iBridges and VLAN cross-connect forwarders

VLAN ports are always used to attach subscribers to iBridges and VLAN
cross-connect, as shown in Figure 9-10.
This applies to tagged Ethernet frames, but also to untagged Ethernet frames, via Port
Default VLAN (PVID) and even to IPoA frames via the so-called Interworking
Layer (IWL) located on the LT board. The IWL takes care to convert IPoA frames
into IPoE frames; see section “Protocol-aware cross-connect mode” for more
information.
Figure 9-10 shows the subscriber access interface model.
Figure 9-10 Subscriber access interface model for iBridges and VLAN cross-connect
Of frame tag or Managed

VLAN port PVID if untagged frame VLAN port (from PVID) by IWL
Bridge port Bridge port
PVC EFM PVC
ATM ATM
ADSLx VDSLx Eth Phy ADSLx
PPPoE or IPoE IPoA

Frames Frames
Attaching subscribers to PPP cross-connect forwarders

The interfaces that can be used to attach subscribers to PPP cross-connect forwarders
- that is, the interfaces on which PPP client ports can be configured - are shown in
Figure 9-11.
Figure 9-11 Subscriber access interface model for PPP cross-connect forwarder
VLAN port
Bridge port
PVC EFM PVC EFM
ATM ATM
ADSLx VDSLx Eth Phy ADSLx VDSLx Eth Phy
Tagged PPPoE PPPoA or untagged PPPoE Untagged PPPoE

Frames Frames on PVC Frames on EFM or Eth Phy
Frame Encapsulation on PVCs

ATM PVCs are configured on top of the ATM-based DSL links. A maximum of
eight PVCs can be configured per DSL link. AAL5 is used to transport frames over
ATM PVCs.
When a frame is received on a PVC, the ISAM will try to determine whether the
AAL5 frame carries:
• an IPoA frame
• a PPPoA frame
• an Ethernet frame
For this, the ISAM inspects the encapsulation of each received AAL5 frame and
compares it with the encapsulation allowed on the PVC receiving the frame.
The ISAM supports the following ATM AAL5 encapsulation types:

• LLC/SNAP bridged (Ethernet)
• VC Mux bridged (Ethernet)
• LLC/SNAP routed (IPoA)
• VC Mux routed (IPoA)
• LLC/NLPid (PPPoA)
• VC Mux PPP (PPPoA)
The operator can configure each PVC in such a way that either one of the following
encapsulation modes is allowed:
• one single encapsulation type only is allowed on the PVC. This is called static
encapsulation mode. Only the frames matching this encapsulation will be
accepted.
• several encapsulation types are allowed on the PVC. In this case, the PVC works
in auto-detect encapsulation mode: the ISAM adapts itself to the encapsulation
selected by the CPE. If the encapsulation of the received frame matches one of
the allowed encapsulations, the frame is accepted. Otherwise, the frame is
discarded. This mode allows the subscriber to change his CPE without requiring
the operator to reconfigure the ISAM.
Auto-detect encapsulation possibilities

It is not possible to have a universal auto-detect function accommodating any frame
format without ambiguity. Hence, several auto-detect modes have been defined, each
one with a limited number of allowed encapsulations. When an operator wants a
PVC to work in auto-detect mode, he can configure the PVC with one of the
following modes:
• Autodetect_IP allows auto-detection of the following frame encapsulations:
• LLC-SNAP-Routed (for IPoA) or
• LLC-SNAP-Bridge (for IPoE) or
• VCMUX-Routed (for IPoA)
Note: VCMUX-Bridge cannot be detected in this mode since it is ambiguous with
VCMUX-Routed when the IP address starts with 00 (hex)
• Autodetect_PPP allows auto-detection of the following frame encapsulations:
• LLC-NLPID-PPP (for PPPoA) or
• VCMUX-PPP (for PPPoA) or
• LLC-SNAP-Bridge (for PPPoE) or
• VCMUX-Bridge (for PPPoE)
• Autodetect_PPPoA allows auto-detection of the following frame encapsulations:
• VCMUX-PPP (for PPPoA)
• Autodetect_IPoE_PPP allows auto-detection of the following frame

encapsulations:
• VCMUX-PPP (for PPPoA) or
• LLC-SNAP-Bridge (for PPPoE or IpoE) or
• VCMUX-Bridge (for PPPoE or IpoE)
Note: LLC-SNAP-Routed and VCMUX-Routed (that is, for IPoA) cannot be

detected in this mode.
Note — The auto-detect feature is aimed to cope with occasional CPE

reconfiguration: when the ISAM detects a valid change of
encapsulation, it will clear data related to PPP or DHCP sessions
related to this PVC, if any is present. Also, it is possible that a few
frames are lost during the transition.
9.6 iBridge mode
In iBridge mode, each NSP is connected to the ISAM at the network side by a
dedicated VLAN.
Depending on the port configuration and LT board type, iBridges accept tagged
and/or untagged traffic for forwarding. For untagged traffic, the ISAM makes use of
a default VLAN configured per port to identify the NSP VLAN. More details about
default VLANs are provided in section “Forwarding of untagged/priority-tagged
frames received from the subscriber”.
iBridges allows the connection of several subscribers to the same network VLAN
and the connection of several hub-ISAM NNI ports to the same network VLAN.
The iBridge mode is a forwarding model based on a single tagged network VLAN.
In alignment with customer evolving deployment models, the ISAM platform also
support stacked VLAN iBridges mode. With a stacked VLAN iBridge, in addition to
performing bridging operations, the ISAM can add/remove a VLAN header to
customer upstream / downstream traffic, thus allowing supporting different
broadband access solutions.
The following are example of different use cases for stacked VLAN iBridges mode:
• The outer-tag (S-TAG) represents the NSP, while the inner-tag (C-TAG)
represents the NSP-Service
A Stacked VLAN iBridges is considered to be a VLAN aware bridge, where each

N:1 VLAN (S-Bridge) is a separate Virtual Bridge (VB) instance. Each VB performs
independent source MAC address learning and frame forwarding processing.
The ISAM Stacked VLAN iBridges offer two modes of operations:
• S+C iBridge
• S-Tunnel iBridge
The S+C iBridge mode allows for C-VLAN tag operations, such as C-VLAN
translation, in addition to adding/removing an S-VLAN header. Such forwarding
mode requires the operator to configure a VLAN port for each C-VLAN.
The S-Tunnel iBridge mode allows the operator to minimize provisioning by
creating a tunnel VLAN port on a specific bridge port where all customer frames (i.e.
untagged, tagged), matching the tunnel VLAN port, are going to be encapsulated by
an S-VLAN header.
Note 1 — S-VLAN ID cannot be shared between S+C iBridge and
S-Tunnel iBridge.
Note 2 — S-Tunnel iBridge mode is currently only supported on
GPON and EPON access solutions
General considerations on iBridges
DHCP option 82
iBridge supports the DHCP snooping features for DHCP Option 82 handling.
Likewise, iBridge supports DHCPv6 snooping for the insertion of DHCPv6 Option
18 and Option 37. For more information on DHCP, see chapter “Protocol handling
in a Layer 2 forwarding model” and chapter “Protocol handling in a Layer 3
forwarding model”.
Note — DHCP option 82 is not supported on traffic received on

hub-ISAM NNI ports. The remote aggregator access node (connected
to the hub-ISAM) will perform such function if required.
Network and subscriber ports

The iBridge and stacked iBridge modes makes a distinction between network ports
and subscriber ports, in contrast with standard bridging where all ports are treated
equally. Frames received from a subscriber will always be sent towards the network
and never to another subscriber.
This behavior is also true when the iBridge mode is used to forward traffic from
hub-ISAM LT board NNI ports. All the upstream traffic will be sent towards the
network and never to another NNI port.
Prevention of broadcast problems

To prevent broadcast storms, the amount of broadcast traffic on each port can be
limited.
When standard bridging is used, a broadcast frame (ARP, PPPoE, DHCP, ICMPv6
or DHCPv6) will be sent to all ports in a particular VLAN. In iBridge mode,
broadcast traffic from the subscriber only goes to the network. Broadcast traffic from
the network is either passed to all ports or blocked on the subscriber ports. This
behavior can be configured per VLAN.
Note — This behavior is also true for Stacked iBridge modes.
Also broadcast as a consequence of flooding, which happens with standard bridging

when the MAC destination address is unknown or with multicast, is avoided in
iBridge mode.
In context of Hub-ISAM LT board NNI ports, all NNI upstream broadcast traffic will
be sent towards the network and never to another NNI port. Broadcast from the
network is passed to all NNI ports. This behavior is not configurable for NNI ports.
Frame types
In iBridge mode, only the following frame types are accepted from the subscriber
ports:
• IP over Ethernet (IPoE) (IPv4)/ARP/Reverse Address Resolution Protocol
(RARP)
• IPv6 over Ethernet (IPv6oE), including Neighbor Discovery and ICMPv6
Note — Neighbor Discovery and ICMPv6 are identified by a Next
Header value of 58 in the immediately preceding IPv6 header
• PPPoE (discovery and session)

• PPPoE relay
• IPoE (IPv4)/ARP/RARP/PPPoE (discovery and session)
• IPoA (per enhanced iBridge) (for IPv4 only)
• all Ethernet types
• Extensible Authentication Protocol Over LAN (EAPOL):
EAPOL frames are dedicated packets that are never forwarded but are processed
by the ISAM.
Other frames, including multicast data frames, will be discarded.

In the context of hub-ISAM LT NNI ports, in iBridge mode, only the following
frame types are accepted from the NNI ports:
• IP over Ethernet (IPoE) (IPv4)/ARP/Reverse Address Resolution Protocol
(RARP)
• IPv6 over Ethernet (IPv6oE)
• PPPoE
• all Ethernet types
Other frames, including multicast data frames, will be sent towards the network and
never to another NNI port.
iBridge Deployment
In iBridge mode, the operator will avoid putting two ISAMs within the same network
VLAN on the same Ethernet Metropolitan Area Network (EMAN) to reach the same
NSP IP router.
Sharing the same VLAN between two ISAMs would allow inter-ISAM user-to-user
traffic to by-pass the NSP, which is undesirable. Figure 9-12 details this
misconfiguration:
• The Ethernet switch will learn all subscriber MAC addresses. If subscriber A can
obtain the MAC address of subscriber C, then subscriber A can send traffic
directly to subscriber C without the traffic going to the NSP IP router. This is
direct user-to-user communication and should be prevented in iBridge mode.
• In such a configuration, an ISAM would receive all broadcast/flooded frames
from any ISAM in the VLAN. This causes potential performance problems and
should not be allowed in iBridge mode.
Figure 9-12 VLAN with two ISAMs

ISAM 1
A
EMAN
B VLAN
NSP
Not allowed NSP IP backbone
ISAM 2
Hub-ISAM LT NNI iBridge deployment example

The ISAM supports the ability to subtend network elements (such as remote ISAM)
directly from the LT. This is done, in this time frame, by using the NNI port type on
the GE Ethernet line board.
As shown in Figure 9-13, by using the iBridge mode on the NNI ports, the operator
can leverage the Hub-ISAM access aggregation capabilities in order to aggregate
traffic towards the EMAN network.
Figure 9-13 Hub-ISAM with iBridge
E
UNI
F
UNI
A
UNI
S-ISAM 1
NNI
NSP IP B
EMAN
Backbone UNI
C
UNI
S-ISAM 1
NNI
D
UNI
Hub-ISAM Remote Aggregator

(subtended ISAM)
Note — The Hub-ISAM can also perform local access and access
aggregation, as shown in Figure 9-13.
MAC learning
In the ISAM, each layer 2 forwarder has its own MAC learning process, independent
from the other layer 2 forwarders. In other words, the text in the section below has to
be understood “within the same network VLAN context”. This means that a MAC
address is unique within a VLAN, but not across VLANs. If a port is connected to
two VLANs, the MAC address is learned twice.
MAC address learning on the NT board

When a frame is received with an unknown MAC Source Address (SA) or the MAC
SA is received on a different bridge port than previously learned, the ISAM will learn
this MAC address with the following restrictions:
• If the MAC address is learned from a subscriber port but the number of MAC
addresses already learned on that port has reached a certain maximum, the MAC
address is not learned and the frame is dropped.
Note — The secured MAC learning mechanism can be disabled to
allow, for example, an unlimited number of MAC addresses in case
of cross-connect mode.
• If the MAC address is learned from a subscriber port, but the same MAC address
is already learned from the EMAN network, the MAC address is not learned and
the frame is dropped (MAC address duplication).
• If the MAC address is learned from a subscriber port, but the same MAC address
was already on another subscriber port, the new MAC address is not learned and
the frame is dropped (MAC address duplication).
• If the MAC address is first learned on a subscriber port, and then learned from the
EMAN network, this movement is accepted and the MAC address is learned. This
means that the MAC address is removed from the subscriber port (MAC address
movement, that is, the last learned MAC address takes priority).
• If the MAC address is first learned on a subtending, subscriber or internal LT port
and then on another subtending, subscriber or internal LT port, then the MAC
address is not learned on the second port (that is, no MAC address movement is
performed)
• Well-known MAC addresses (for example, multicast MAC addresses, MAC
addresses allocated for IEEE protocols, and so on) are not learned.
Note — These restrictions are valid in both iBridge mode and VLAN
cross-connect mode.
These principles apply also for subtending ports. In this context, a subtending port
behaves at the same level as a subscriber port.
MAC address learning on the LT board

The ISAM LT boards provide a protection about the maximum number of MAC
addresses that can be learned per port:
• On ATM-based interfaces, the limit is applied per PVC.
• On PTM-based DSL interfaces, and Ethernet physical interfaces, the limit is
applied per interface.
The way this protection is implemented depends on the LT board type:

• On layer 2+ LT boards and on layer 3 LT boards, this protection allows the
operator to configure a maximum per port and this maximum is also committed.
• On layer 2 LT boards, this protection allows the operator to work with
overbooking. The operator can configure a maximum per port and a committed
number per port.
The committed number of MAC addresses per port is the number of entries reserved
in the forwarding database for that port. This number of entries can be used by the
subscriber connected to that port at all times, that is, independent of any activity of
other subscribers.
However, if not all the available entries on an LT board have been assigned to a port,
then the remaining entries are dynamically assigned to ports based on MAC address
learning with the protection that the total number of entries per port cannot exceed
the configured maximum number of MAC entries per port.
The ISAM LT boards also provides protection against duplicate MAC addresses in
the VLAN context of the forwarder.
When a frame is received on a subscriber port with a source MAC address which was
already learned on another port for this VLAN, this generates a duplicate MAC
address alarm and:
• On layer 2 LT boards, the frame is discarded and the MAC address is not moved
from the original port. Moreover, the offending end-subscriber PVC is locked.
The subscriber port is unlocked again (and the duplicate MAC address alarm is
cleared) after a time period equal to three times the MAC address aging time.
• On layer 3 and point-to-point Ethernet LT boards, the frame is discarded and the
MAC address is not moved from the original port. The port carrying the offending
frame remains fully operational for frames received with non-offending source
MAC address. The alarm is cleared after a time period free of MAC address
conflict.
• The Hub-ISAM LT NNI ports concept is currently supported on the GE Ethernet LT
board only.
• As such, the MAC address learning and the associated duplicate MAC address
alarming does apply to UNI and NNI ISAM LT ports with the same level of
precedence between the two port types.
MAC aging time

A MAC address that was previously learned on a given iBridge is automatically
removed from the MAC forwarding table of that iBridge when no traffic has been
received from that MAC address during the MAC aging time.
MAC aging time configuration

It is important that the MAC ageing time is properly configured, otherwise
data-plane connectivity may get lost between the network and the ISAM subscribers
(due to the fact that traffic is not flooded to these subscribers when their MAC
address is no longer present in the forwarding database):
• For PPPoE traffic, the MAC aging time can be kept small, because PPP has a
built-in keep-alive mechanism.
• For DHCP-based service scenarios (IPv4 or IPv6), the MAC aging time must be
taken in the same order of magnitude as the DHCP lease time (unless there is
another time that can be used, for example, an ARP refresh interval, an
application-layer keep-alive time, and so on).
The MAC aging time is configurable between 10 s and 1.000.000 s with a default
value of 300 s.
Note — On layer 2 LT boards, the MAC aging time is limited to a

maximum of 1096 s by the hardware. In that case, the management
interface allows the operator to configure a higher aging time, but the
hardware caps this configured value to 1096 s.
A MAC aging time can be configured per iBridge forwarding instance as for some
services the MAC aging time should be kept low, while for other services (for
example, DHCP-based services) the MAC aging time should be increased.
VLAN tagging modes in the iBridge
Concepts
Section “Generic forwarder model in ISAM” has introduced the concepts of bridge
ports and VLAN ports defined on the subscriber side and used by iBridges and
VLAN cross-connects.
Forwarding of untagged/priority-tagged frames received from the subscriber

The subscriber bridge ports (that is, PVCs, EFM or Ethernet Physical link) are
connected to the VLAN of the appropriate NSP by means of a default VLAN ID.
Figure 9-14 shows the concept of the iBridge mode for untagged subscriber traffic.
Figure 9-14 iBridge mode - untagged subscriber traffic

NSP 1
A NSP 1-VLAN
B NSP 2
NSP1
C
NSP 2-VLAN NSP IP backbone
D NSP2
E NSP3
F NSP 3-VLAN
NSP 3
G
NSP IP backbone
Typical of an iBridge, several subscriber ports can be associated to a single VLAN.

In Figure 9-14, the following subscriber ports are connected to the different VLANs:
• subscriber ports A, B and C connected to NSP 1-VLAN
• subscriber ports D and E connected to NSP 2-VLAN
• subscriber ports F and G connected to NSP 3-VLAN
There are two ways to determine a default VLAN ID (and P-bits) for untagged
frames received on a bridge port:
• Port-based classification:
For port-based VLAN classification within a bridge, the VLAN ID associated
with an untagged or priority-tagged frame (that is, a frame with no tag header, or
a frame with a tag header that carries the null VLAN ID) is uniquely determined
by the bridge port through which the frame is received. This classification
mechanism requires the operator to configure a specific PVID on each bridge
port. In this case, the PVID provides the VLAN ID for untagged and
priority-tagged frames received through that bridge port. The PVID is always
associated with a VLAN port on the bridge port.
• Port- and Protocol- based classification:
For bridges that implement port/protocol-based VLAN classification, the VLAN
ID associated with an untagged or priority-tagged frame is determined by the
bridge port through which the frame is received and the protocol type of the
frame. This classification mechanism requires the operator to configure one
Port-Protocol-VLAN ID per protocol type on each bridge port. Each
Port-Protocol-VLAN ID is always associated with a specific VLAN port on the
bridge port.
When a PVID and Port-Protocol-VLAN ID(s) are both configured on a given
bridge port, the ISAM always selects the Port-Protocol-VLAN ID if applicable.
In practice, the ISAM operator can configure up to two port-Protocol-VLAN ID
per bridge port:
• one for IP and related protocols (for example, ARP) and
• one for the PPP protocol
Note — For more information about the handling of priority-tagged

frames, see chapter “Quality of Service”.
When a subscriber generates a frame or a frame is received from the upstream

Ethernet switch, a MAC address lookup is done in the forwarding table identified by
the VLAN. Each NSP has its own forwarding table in the ISAM.
The ISAM receives untagged or priority-tagged frames on a given bridge port, and
forward these in the context of an iBridge. To achieve this, the operator creates a
C-VLAN port on top of the bridge port, and couples it to the specified iBridge. Next,
the operator installs a Port-default VLAN ID (PVID) (see Figure 9-15) or a
Port-protocol-default VLAN ID (see Figure 9-16) that points to the VLAN port.
Figure 9-15 Forwarding untagged/priority-tagged frames in an iBridge (iBridge shown

with only one subscriber)
Network-side Configured VLAN
User-side traffic
traffic ports
Bridge port BP1
Ut,C1 VLAN port (BP1/ 0,C1)

iBridge (C1) Ut,Ut
BP1:PVID = 0,C1
Si,X (any i) or
Ut,Cj (j ≠ 1)
Legend for traffic characterization:

Ut,C1 means S-VLAN = untagged and C-VLAN = C1
S1,X means S-VLAN = S1 and C-VLAN = do not care (tagged or untagged)
Ut,Ut means no S-VLAN, no C-VLAN
Legend for VLAN port configuration:
0,C1 means a C-VLAN port
S1,0 means an S-VLAN port
Figure 9-16 Protocol-based VLAN selection (iBridge shown with only one subscriber)
User-side traffic
traffic ports
Bridge port BP1

iBridge (C1) Ut,Ut
BP1: IPoE VID = 0,C1

Ut,C2 PPPoE VID = 0,C2
iBridge (C2) VLAN port (BP1/ 0,C2)
Si,X (any i) or
Ut,Cj (j ≠ 1,2)

S1,0 means an S-VLAN port
Note — The behavior described in this section is also true when the
iBridge mode is used to forward traffic from Hub-ISAM LT NNI
ports.
Forwarding of C-VLAN tagged frames

The CPE accessing an NSP via iBridge mode send their traffic to the ISAM tagged
with an NSP. With the multi-VLAN and VLAN translation capability, a bridge port
can access several NSPs simultaneously. Figure 9-17 shows the concept of the
iBridge mode with tagged subscriber traffic.
Figure 9-17 iBridge mode - tagged subscriber traffic

NSP 1
VDSL EMAN NSP IP backbone

Bridge port
NSP 1-VLAN
NSP1 NSP 2
VLAN-a
NSP 2-VLAN NSP IP backbone
VLAN-b NSP2
VLAN-c
NSP3
NSP 3-VLAN
NSP 3
NSP IP backbone
In Figure 9-17 the VDSL subscriber is connected to 3 NSPs in iBridge mode. When
a subscriber generates a frame or a frame is received from the upstream Ethernet
switch, a MAC address lookup is done in the forwarding table identified by the
network VLAN. This means that each NSP has its own forwarding table in the
ISAM. This is indicated by the black boxes labeled with “NSPx”. The subscriber
VLAN-a, VLAN-b and VLAN-c are translated in the ISAM to NSP 1-VLAN, NSP
2-VLAN and NSP 3-VLAN respectively at the subscriber-side boundary.
The ISAM receives C-VLAN-tagged frames on a given bridge port, and forwards
these in the context of an iBridge. To achieve this, the operator creates a C-VLAN
port on top of the bridge port, and couples it to the iBridge.
• When no VLAN translation is needed, the VLANs used in the network are
extended all the way to the subscribers. In this case, the subscriber side VLAN
IDs are said to have a network-wide scope; see Figure 9-18.
Note — The behavior described in this section is also true when the
iBridge mode is used to forward traffic from Hub-ISAM LT NNI
ports.
• In case of VLAN translation, the network-side and subscriber-side VLAN IDs are
different. iBridging, in combination with VLAN translation, is typically used
when a loose coupling is needed between the C-VLAN IDs used on the access
link and the C-VLAN IDs used in the aggregation network; see Figure 9-19.
Note — VLAN translation is not supported on Hub-ISAM LT NNI
ports.
Figure 9-18 Subscriber-side VLAN-IDs with a network-wide scope (iBridge shown with
only one subscriber)
User-side traffic
traffic ports
Bridge port BP1

iBridge (C1) Ut,C1

iBridge (C2) Ut,C2
BP1: no PVID
Si,X (any i) or
Ut,Cj (j ≠ 1,2) or
Ut,Ut

Figure 9-19 Support for VLAN translation (iBridge shown with only one subscriber)
User-side traffic
traffic ports
Bridge port BP1

iBridge (C1) T Ut,C3

iBridge (C2) T Ut,C4
BP1: no PVID
Si,X (any i) or
Ut,Cj (j ≠ 3,4) or
Ut,Ut

VLAN tagging modes in the stacked iBridge modes

Section “VLAN tagging modes in the iBridge” has explained the VLAN tagging
modes in the iBridge for normal ISAM LT bridge ports.
In this section, our intention is to explain the VLAN tagging modes in the Stacked
iBridge mode.
Concepts
VLAN cross-connects. These concepts are also valid for stacked iBridge modes.
Two stacked iBridge modes are supported:
• S+C iBridge
• S-Tunnel iBridge
The S+C iBridge mode allows for C-VLAN tag operations, such as C-VLAN
translation, in addition to adding/removing an S-VLAN header. This forwarding
mode requires the operator to configure a VLAN port for each C-VLAN.
The S-Tunnel iBridge mode allows the operator to minimize provisioning by
creating a tunnel VLAN port on a specific bridge port where all the customer frames
(i.e. untagged, tagged) matching the tunnel VLAN port, are going to be encapsulated
by an S-VLAN header.
Forwarding of untagged/priority-tagged/VLAN tagged frames in S+C iBridge

The forwarding behaviors described in section “VLAN tagging modes in the
iBridge” are, for the most part, also pertinent for the operations of an S+C iBridge
forwarding model. As such, the S+C iBridge supports forwarding of
untagged/priority-tagged and VLAN-tagged customer frames.
• Forwarding of untagged/priority-tagged customer frames requires the
configuration of the PVID.
• Forwarding of tagged customer frames requires the configuration of a VLAN
port.
The main difference being that an S+C iBridge offers the ability of VLAN stacking
(see section “About VLAN stacking”). An S+C iBridge is considered to be a
S-VLAN aware bridge, where each N:1 VLAN (S-Bridge) is a separate Virtual
Bridge (VB) instance. Each VB performs independent source MAC address learning
and frame forwarding processing.
This forwarding mode resembles to the ISAM S+C VLAN cross-connect forwarding
model. The main difference is that in the S+C iBridge mode, the C-VLAN ID can be
shared across multiple UNIs. This is not true with the S+C CC mode, where a
C-VLAN ID is restricted to a single UNI.
The S+C iBridge mode support both protocol-unaware and protocol-aware modes of
operations. For example, DHCP option 82 insertion, PPPoE Intermediate Agent and
secure forwarding (ARP Relay, DHCP Snooping, IP anti-spoofing) is supported for
protocol-aware S+C iBridge operations.
Note 1 — S-Tunnel iBridge is not supported on DSL LT boards.
Note 2 — A given S-VLAN ID cannot be shared between an S+C

iBridge and an S-Tunnel iBridge.
Note 3 — DSL LT boards support stacked iBridge mode for unicast
traffic only.
Note 4 — On DSL LT boards stacked iBridge does not support PPP
MAC address concentration, IPoA, PPPoX Relay and VRRP Proxy
On DSL LT boards secure-forwarding, broadcast control and aging time are

individually controlled at the S+C level while other configurations are inherited from
the S level.
VLAN tagging modes in the iBridge (Hub-ISAM LT NNI ports concept)

Section “VLAN tagging modes in the iBridge” has explained the VLAN tagging
modes in the iBridge for normal ISAM LT bridge ports, also known as UNI ports.
This section explains the VLAN tagging modes in the iBridge when used in context
of the Hub-ISAM LT NNI ports.
Concept
VLAN cross-connects. These concepts are also valid for iBridges defined on NNI
ports.
As noted earlier, the Hub-ISAM LT NNI ports concept is currently supported on the
GE Ethernet line card only.
There are two VLAN iBridge models supported on GE Ethernet LT board NNI ports:
• C-VLAN iBridge: basic VLAN bridge mode
• S-VLAN iBridge: supporting mapped and tunnel VLAN bridge modes
Forwarding of untagged/priority-tagged/VLAN tagged frames in C-VLAN iBridge

Section “VLAN tagging modes in the iBridge” explains the forwarding behaviors of
a C-VLAN iBridge configured on the GE Ethernet line card port type.
Forwarding of untagged/priority-tagged/VLAN tagged frames in S-VLAN iBridge

The forwarding behaviors described in section “VLAN tagging modes in the
iBridge” are, for the most part, also pertinent for the operations of an S-VLAN
iBridge configured on the GE Ethernet line card NNI port type.
The main difference being that an S-VLAN iBridge offers the ability of VLAN
stacking (see “About VLAN stacking”)
When the Hub-ISAM GE Ethernet line card NNI port is configured with an S-VLAN
iBridge, the ISAM Access Node is considered to be a VLAN aware bridge, where
each N:1 S-VLAN is a separate Virtual Bridge (VB) instance. Each VB performs
independent source MAC address learning and frame forwarding process as
described in 802.1D and 802.1Q.
The GE Ethernet line card S-iBridge forwarder, supported on the NNI port type, does
support Mapped and Tunneled modes:
• In Tunnel Mode, the ISAM systematically adds a VLAN tag to frames
originating from the NNI. This mode is enabled by configuring an S-VLAN
PVID on the Bridge Port. It is to be noted that S-VLAN iBridge accepts
indifferently untagged and single tagged frames.
• In Mapped Mode, the ISAM considers NNI traffic as if already inside a tunnel.
In Mapped mode, the ISAM just extends the NNI tunnel further to the EMAN
without adding any extra VLAN tag. With Mapped mode, it is not possible to
translate the NNI S-VLAN into a different network S-VLAN.
Both the Tunnel mode and the Mapped mode can co-exist simultaneously in the
ISAM. Whether a frame has to be handled in S-VLAN Tunnel or Mapped iBridge
results from a comparison between the most external frame tag (if any) and the
Bridge port PVID.
Thus the GE Ethernet LT board S-iBridge forwarding behaviors can be summarized

as:
• When upstream traffic on a given NNI bridge port does not match a defined
S-VLAN port attached to a given S-iBridge and no S-VLAN port default VLAN
exists on that bridge port, then this traffic is dropped.
• When upstream traffic on a given NNI bridge port matches a defined S-VLAN
port attached to a given S-iBridge and no S-VLAN port default VLAN exists on
that bridge port, then this traffic is accepted into the VB instance for bridging
functions. In this case, no new tag will be added on upstream egress. This mode
of operation is referred as mapped mode.
• When an S-VLAN port default VLAN has been defined on an NNI bridge port,
then all traffic is accepted into the VB instance for bridging functions and this
traffic will be added an S-VLAN tag on upstream egress. This mode of operation
is referred to as tunnel mode.
9.7 VLAN cross-connect mode
Concept
The VLAN cross-connect approach consists of building a connection-oriented model
across the connectionless Ethernet access network, using VLANs. In VLAN
cross-connect mode, one VLAN contains only one subscriber port. However,
multiple VLANs (multi-VLAN feature) may be configured on a single subscriber
port. Figures 9-20 shows the VLAN cross-connect mode.
Figure 9-20 VLAN cross-connect mode
NSP 1

A VDSL
bridge port Subscriber A &
Service a
VLAN-a
A VLAN
NSP 2
VLAN-b
Subscriber A &
B Service b NSP IP backbone
VLAN
xDSL
B bridge port C
Subscriber B & NSP 3
Service c
VLAN-c VLAN NSP IP backbone
Note — Although Figure 9-20 is DSL copper access specific, the

same concept applies for point-to-point Ethernet access solutions.
Figure 9-21 shows the cross-connect network topology.
Figure 9-21 Cross-connect network topology
Cross-connect
logical view
NSP
Network VLAN
User VLAN
Cross-connect
physical EMAN
topology
Bridge
Bridge Bridge NSP

Bridge
User VLAN
Network VLAN
Usage
A particular subscriber VLAN ID, without VLAN translation, can be configured
only once:
• on any of the subscriber ports in the ISAM
• over all the ISAMs in the complete Ethernet network to which the ISAM is
connected
When VLAN stacking is not used (see “About VLAN stacking”), the VLAN
cross-connect mode should only be used:
• in small networks, where the ISAM is directly connected to the IP Edge router or
Broadband Remote Access Server (BRAS) of a Network Service Provider (NSP),
for business customers
• for a larger network in combination with VLAN translation.
Supported models in ISAM

There are several VLAN cross-connect models supported:
• C-VLAN cross-connect: basic VLAN cross-connect
• S+C-VLAN cross-connect: VLAN stacking for residential subscribers (mapped
or tunnel mode)
• S-VLAN cross-connect: VLAN stacking for business subscribers
Note — These VLAN cross-connect models are also supported on the

Hub-ISAM LT NNI ports.
About VLAN stacking
VLAN-stacking introduces another VLAN layer. One “outer” VLAN can bundle a
number of “inner” VLANs, similar to one LAN bundling a number of VLANs. This
way, one VLAN, called the Service-VLAN or S-VLAN, bundles a number of
smaller VLANs, called Customer-VLANs or C-VLANs. Traffic in this S-VLAN
may, in its turn, be bridged according to a forwarding context proprietary to the
S-VLAN. This is done in S-VLAN-aware bridges.
Figure 9-22 shows the protocol stack for S- and C-VLANs and the function of the
different bridge types. C-VLANs can be carried up to the subscriber (hence the “C”).
S-VLANs can be used to transparently convey traffic to specific large business
customers with their proprietary VLAN-organization, or to group a set of residential
subscribers to a single service provider (hence the “S”).
Figure 9-22 S-VLAN- and C-VLAN-aware bridges

VLAN-unaware C-VLAN-aware S-VLAN-aware S-VLAN-aware C-VLAN-aware
terminal bridge bridge bridge terminal
C-VLAN
termination
anything S-VLAN S-VLAN anything
Bridging termination termination
Eth C-VLAN C-VLAN C-VLAN

Bridging Bridging
S-VLAN S-VLAN S-VLAN S-VLAN
Eth Eth Eth
Eth Eth Eth Eth
C-VLAN cross-connect (basic VLAN cross-connect)
C-VLAN cross-connect is the most straightforward VLAN cross-connect model,

where a single VLAN ID at the EMAN side is associated with a C-VLAN port at the
subscriber side. In the ISAM, a bridge port is either an Ethernet PVC, an EFM link
or a physical user Ethernet link. Any kind of traffic issued by the subscriber is
forwarded transparently to the network using the selected VLAN ID.
As illustrated in Figure 9-24, similar to iBridging the C-VLAN cross-connect allows:
• user-VLAN to network-VLAN translation
• handling of untagged traffic by means of PVID or Port-Protocol-VLAN ID
default VLANs.
Forwarding of untagged/priority-tagged frames in C-VLAN cross-connect

The ISAM receives untagged or priority-tagged frames on a given bridge port, and
forwards these in the context of a C-VLAN cross-connect. To achieve this, the
operator creates a C-VLAN port on top of the bridge port, and couples it to the
C-VLAN cross-connect. Next, the operator configures on the bridge port a PVID or
a Port-protocol-default VLAN that points to the VLAN port.
Forwarding of C-VLAN tagged frames in C-VLAN cross-connect
The ISAM receives C-VLAN-tagged frames on a bridge port, and forwards these in
the context of a C-VLAN cross-connect. To achieve this, the operator creates a
C-VLAN port on top of the bridge port, and couples it to the C-VLAN cross-connect.
When no VLAN translation is needed, the VLANs used in the network are extended
all the way to the end subscribers. In this case, the end-subscriber side VLAN IDs
are said to have a network-wide scope. For VLAN translation, the network-side and
subscriber-side VLAN IDs are different.
VLAN translation is not supported on Hub-ISAM LT NNI ports.
Figure 9-23 shows the C-VLAN cross-connect model.
Figure 9-23 C-VLAN cross-connect concept

C-VLAN C-VLAN port
cross-connect
C-VLANs T
EMAN NE CPE(s)
Figure 9-24 shows a detailed example of C-VLAN cross-connects.
Figure 9-24 C-VLAN cross-connect detailed model

Configured C-VlanPort: Traffic from
{BrP, S-VlanId, C-VlanId} BrP10 Subscriber
(say, no PVID)
Outer Tag: 117 {10, 0,17} Outer Tag: 17
X Trsl
X Trsl
Anything else
BrP11
PVID = (0,19)
X Trsl
Outer Tag: 19 {11, 0,19} Untagged (*)
X Trsl
Anything else
(*) Outer Tag: 19 is also accepted
Legend:
BrP10: bridge port 10
{10, 0, 19}: C-VLAN port on bridge port 10 with User-C-VLAN ID = 19
S+C-VLAN cross-connect: VLAN stacking for residential subscribers
In the basic VLAN cross-connect mode, the number of VLAN identifiers is limited
to 4 K. Since the VLAN is an EMAN-wide identifier, there is a scalability issue:
there cannot be more than 4 K subscribers connected to the whole EMAN. To solve
this issue, two VLANs are stacked and the cross-connection is then performed on the
combination (S-VLAN, C-VLAN), theoretically reaching up to 4 M subscribers.
An S+C-VLAN cross-connect can be seen as the generalization of a C-VLAN
cross-connect. It has the same mode of operation and the same configuration model
except that with an S+C-VLAN cross-connect, the user C-VLAN is always
translated into a dual tag S+C Network VLAN.
Figure 9-25 shows the concept of the S+C-VLAN cross-connect mode.
Figure 9-25 S+C-VLAN cross-connect concept
C-VLAN to PVC
C-VLANs cross-connects C-VLAN port
S-VLAN
EMAN NE CPE(s)
Figure 9-26) shows a detailed example of S+C-VLAN cross-connects.
Figure 9-26 VLAN translation in case of the S+C-VLAN cross-connect

Configured C-VlanPort: Traffic from
{BrP, S-VlanId, C-VlanId} BrP10 Subscriber
(say, no PVID)
(23, 117) {10, 0,17} Outer Tag: 17
X Trsl
(23, 17) {10, 0,19} Outer Tag: 19
X Trsl
Anything else
BrP11
(say, no PVID)
(29, 119) {11, 0,17} Outer Tag: 17
X Trsl
(29, 219) {11, 0,19} Outer Tag: 19
X Trsl
Anything else
Legend:
BrP10: bridge port 10
{10, 0, 19}: C-VLAN port on bridge port 10 with User-C-VLAN ID = 19
(29, 119): (S, C) dual tag, with S being the outer tag with VLAN ID = 29
Note 1 — In the ISAM, the S+C-VLAN cross-connect is always

performing VLAN translation, even when the subscriber-side and
network-side C-VLAN IDs are the same. For instance in Figure 9-26
the subscriber-side VLAN (0, 17) is translated into the network-side
VLAN (23,17).
Note 2 — In the ISAM, the C-VLAN tag may not be identical to the
S-VLAN tag.
Note 3 — S+C-VLAN cross-connect is also supported on the
hub-ISAM LT NNI ports.
Special note about MAC address conflict prevention
The purpose of S+C-VLAN cross-connect is to regroup different subscribers

identified by their own C-VLAN in the same shared S-VLAN. Doing so improves
the EMAN scalability by allowing the EMAN to collectively bridge all users' traffic
in the same S-VLAN context.
Because the EMAN is only aware of the S-VLAN context when performing
bridging, the ISAM must make sure that no two subscribers use the same source
MAC address in upstream when put in the same S-VLAN.
While on the LT boards, each S+C VLAN cross-connect defines a distinct
forwarding context, and hence there cannot be any MAC address conflict, this is not
true on the NT board. The NT board acts as an S-VLAN bridge, unaware of the
C-VLANs so traffic of multiple end-users that share the same S-VLAN ID is treated
in the same forwarding context. If a given MAC address is first learned on an LT port
and later on a second LT port, then no MAC movement occurs, but instead a
“duplicate MAC address” alarm is raised by the NT board.
S-VLAN cross-connect: VLAN stacking for business subscribers
Like for the S+C-VLAN cross-connect, in S-VLAN cross-connect mode, two levels
of VLAN tags are used, supporting hierarchical addressing:
• the customer VLAN: C-VLAN
• the service provider VLAN: S-VLAN
The difference however is that in the S-VLAN cross-connect mode, the EMAN and
the ISAM are totally unaware of the C-VLANs. This contrasts with S+C VLAN
cross-connects, for which the ISAM is aware of both the S-VLAN and the C-VLANs
to identify individual S+C cross-connections.
In an S-VLAN cross-connect, the C-VLANs carried within the S-VLAN are passed
transparently to the end subscriber. The S-VLAN cross-connect plays the role of a
“transport pipe” between the subscriber and the remote site.
In this mode, the S-VLAN ID at the EMAN side is associated with an S-VLAN port
at the subscriber side. This allows the subscriber to specify its own end-to-end
connectivity, while remaining transparent for the EMAN.
Figure 9-27 shows the S-VLAN cross-connect model.
Figure 9-27 S-VLAN cross-connect model concept

S-VLAN
S-VLAN port
cross-connect
C-VLANs S-VLAN T ATM PVC or EFM C-VLANs
EMAN NE
The ISAM operator configures an S-VLAN cross-connect by configuring an

S-VLAN port and associating it with an S-VLAN network VLAN.
The S-VLAN cross-connect is available in two modes for realizing the “transparent
pipe” transfer of subscriber traffic: the S-VLAN tunnel cross-connect and the
S-VLAN mapped cross-connect.
• In tunnel mode, the ISAM systematically adds a VLAN tag to frames originating
from the subscriber. This mode is enabled by configuring an S-VLAN PVID on
the bridge port. S-VLAN tunnel cross-connect accepts indifferently untagged,
single, dual or multi-tagged frames.
• In mapped mode, the ISAM considers subscriber traffic as if already inside a
tunnel originated at subscriber side. In mapped mode, the ISAM just extends the
subscriber tunnel further to the EMAN without adding any extra VLAN tag. With
mapped mode, it is possible to translate the user S-VLAN into a different network
S-VLAN.
Both the tunnel mode and the mapped mode can co-exist simultaneously in the
ISAM. Whether a frame has to be handled in S-VLAN tunnel cross-connect or
S-VLAN mapped cross-connect results from a comparison between the most
external frame tag (if any) and the bridge port PVID.
S-VLAN cross-connect is also supported on the hub-ISAM LT NNI ports.
Figure 9-28 and Figure 9-29 explain the principle by the means of detailed examples.
For VLAN cross-connect, only the most external VLAN tag is used to determine the
type of VLAN cross-connect to be applied to the frame, independently whether
additional tags would be present or not (subscriber frames with more than 2 VLAN
tags are not shown in the figures).
Figure 9-28 Detailed example of ISAM Configuration with PVID = S-VLAN and resulting
behavior
S-VLAN tunnel mode

17 Ut
17,13 13
17,17 17
17,17,19 (17,0), PVID
17, 19
17,31,19 31, 19
S-VLAN mapped mode (29, 0)

29 29
29,19 29,19
23 (0, 23) 23
23, 37 23, 37
BridgePort
Legend
Ut Untagged frame
13 Frame with single tag = 13
17, 13 Frame with double tag = 17 (external tag) and 13
17, 31, 19 Frame with triple tag = 17 (external tag), 31 and 19
X No frame output
(17, 0) S-VLAN VlanPort configured
(0, 23) C-VLAN VlanPort configured
Figure 9-29 Detailed example of ISAM Configuration with PVID different from S-VLAN
and resulting behavior
S-VLAN mapped mode
17 17
17, 19 (17,0) 17, 19
S-VLAN mapped mode
29 29
29,19 29,19
(29, 0)
23 Ut
23 23
23, 37 23. 37
X (0, 23), PVID 13
X 31, 19
BridgePort
Legend
Ut Untagged frame
13 Frame with single tag = 13
17 Frame with double tag = 17 (external tag) and 13
X No frame output
(17, 0) S-VLAN VlanPort configured
(0, 23) C-VLAN VlanPort configured
MAC learning
The same MAC learning concepts apply as for iBridge; see section “MAC learning”
Transparent VLAN cross-connect

The ISAM supports transparent VLAN cross-connect for use in a business
environment on all LT boards except layer 2 LT boards. A transparent VLAN
cross-connect is a special mode of operation of the S-VLAN cross-connect,
C-VLAN cross-connect or S+C-VLAN cross-connect. Transparent VLAN
cross-connect is also supported on the hub-ISAM LT NNI ports.
A transparent VLAN has the following additional features compared with the usual
VLAN cross-connect:
• L2CP frames are transparently forwarded (except pause frames).
• MAC address learning is disabled in the NT board for better scalability.
L2CP frames are those frames with the following destination MAC addresses:
• 01-80-C2-00-00-00 through 01-80-C2-00-00-0F
• 01-80-C2-00-00-10
• 01-80-C2-00-00-20 through 01-80-C2-00-00-2F
Note — The ECNT-A can only partly support fully transparent
VLAN-cross-connect. It can only recognize those L2CP frames
which have the following MAC addresses:
• 01-80-C2-00-00-00
• 01-80-C2-00-00-10
• 01-80-C2-00-00-20 through 01-80-C2-00-00-2F
L2CP protocols is a family of link-related protocols. It comprises the following
protocols:
• Spanning Tree protocol
• Rapid Spanning Tree protocol
• Multiple Spanning Tree protocol
• Pause (802.3x) protocol
• Link Aggregation protocol
• Marker protocol
• Authentication (802.1x) protocol
• LAN Bridge Management Group Block of protocols
• Generic Attribute Registration Protocol (GARP) Block of protocols
• and so on
Pause frames are those L2CP frames identified by:

• Destination MAC address = 01-80-C2-00-00-01
• Ethernet type and op-code can be anything
The purpose of transparent VLAN cross-connect is to emulate a physical link, as
illustrated in Figure 9-30.
Figure 9-30 Use of transparent VLAN cross-connect
L2CP: Sp. tree

Br
Br Br
L2CP: Sp. tree
Br
Br Link aggregate L2CP:LACP Br
Br
LAG
LAG
LAG
Br
Br L2CP:LACP Br
Over Transparent VLAN-CC
L2CP
VLAN1
Br
Br x x Br
Br
Br
Br VLAN2 L2CP Br
Br
x x
LAG
LAG
LAG
LAG
Br
Br VLAN3 L2CP Br
Br
x x
EMAN
Assu m p tio n :
EMAN tr a n sp a r e n t to ta g g e d L2 CP traffic
In the upstream direction, in a transparent VLAN cross-connect, untagged subscriber

L2CP frames are considered as data traffic and are tagged by the default PVID
configured on the PVC/EFM with the exception of:
• tagged pause frames, which are always discarded
• untagged 802.1x frames, which are extracted to the LT OBC when 802.1x is
enabled, whether L2CP transparency is enabled or disabled on the LT board
• untagged link-based Ethernet OAM, which is extracted to the OBC when
link-based Ethernet OAM is enabled, whether L2CP transparency is enabled or
disabled on the LT board.
Note — IEEE802.3ah OAM is currently not supported on hub-ISAM

LT NNI ports.
In the downstream direction, in a transparent VLAN cross-connect, tagged

subscriber L2CP frames are considered as data traffic and are passed untagged to the
subscriber. The handling of untagged downstream L2CP frames is not affected by
the transparent VLAN cross-connect.
Because L2CP protocols are link related, the deployment model implies that only
one transparent VLAN cross-connect is configured per PVC (or per EFM); see
Figure 9-31. Having more than one cross-connect can lead to undesired effects in
L2CP protocols.
Figure 9-31 One transparent VLAN cross-connect per PVC/EFM
L2CP
CPE PVC/EFM x x PVC/EFM CPE

VLAN1
PVID = VLAN1
EMAN
CPE PVC/EFM x
L2CP
VLAN1
x
PVC/ EFM CPE
x
VLAN2
CPE PVC/EFM x PVID= VLAN1

EMAN
9.8 Protocol-aware cross-connect mode
The protocol-aware cross-connect mode behaves like the formerly described

cross-connect modes for the dataplane, but it also adds some protocol awareness
similar to the iBridge mode, for protocols such as 802.1x, DHCP, IGMP, PPPoE,
DHCPv6 and ICMPv6.
This mode provides a connectivity scheme compatible with a fully centralized
subscriber management, where each individual subscriber is connected to an IP Edge
(IP connectivity) or a BRAS (PPP connectivity) through a single bit-pipe. In this
configuration, the subscribers are sharing the same subnet for scalability reasons and
do not present their private network configuration to the network.
VLAN cross-connect for business and residential subscribers

The VLAN cross-connect feature cross-connects a subscriber PVC (or DSL line in
case of EFM, Ethernet link in case of point-to-point Ethernet) with a “private”
VLAN at the EMAN side. Depending on the subscriber type, two VLAN
cross-connect configurations are considered:
• Business cross-connect:
This mode provides a connectivity scheme for business subscribers which is as
transparent as possible and emulates a fully featured routed network. In this
configuration, the IP subnets of the private subscribers are made visible to the
network and the configuration data of those private subnets and the subnets
further in the network are exchanged through routing protocols.
Figure 9-32 shows the IP network model for business cross-connect.
Figure 9-32 IP network model for business cross-connect
Edge EMAN NE CPE
VRF
VL
VRF
Services VRF
VRF
VRF
Customer
premises
IP subnet IP address VLAN IP subnet
• Residential cross-connect:
This mode provides a connectivity scheme compatible with a fully centralized
subscriber management where each individual subscriber is connected to an IP
edge (IP connectivity; see Figure 9-33) or a BRAS (PPP connectivity; see Figure
9-34) through a single bit pipe. In this configuration, the subscribers are sharing
the same subnet for scalability reasons and (normally) do not present their private
network configuration to the network.
Figure 9-33 IP network model for residential cross-connect using IP connectivity
Edge EMAN NE CPE
VLAN-CC
Services VRF
IP subnet IP address VLAN
Figure 9-34 IP network model for residential cross-connect using PPP connectivity
Edge EMAN NE CPE
VLAN-CC
IP PPP
Services Routing Termina-
tion
IP subnet IP address
PPP session VLAN
Note — Figure 9-33 and Figure 9-34 apply for residential subscribers
that are using bridged CPE or router CPEs with NAT. In those cases,
only single IP address(es) are allocated to the subscriber, and no
(directly or non-directly) attached subnets.
Though not typically associated with residential subscribers, router
CPEs without NAT can be supported too. The data forwarding in the
VLAN cross-connect model is fully based on the VLAN tag(s) and
does not need to look at the IP addresses (that is, need to support an
IP next-hop behavior in the downstream direction).
However, this possibility is rather heavy from an operational point of
view: subscriber subnets need to be configured by the operator in the
IP edge. If IP address anti-spoofing is switched on in the ISAM, the
subscriber subnets must be configured there as well.
Business cross-connect features

In a business context, the VLAN cross-connect model is used to provide a
transparent VPN service. Several variants exist:
• Layer 2 VPN: the subscriber sends C-VLAN tagged frames, which are wrapped
at ingress of the ISAM into an S-VLAN pipe that is carried through the Ethernet
aggregation network. In the ISAM, this model can be realized using the S-VLAN
cross-connect.
• Layer 3 VPN: the subscriber router CPE (Customer Edge, CE) is connected to a
Provider Edge (PE) located in the service provider network. In ATM-based DSL
aggregation networks, a similar service is provided, often with IPoA
encapsulation. The idea is that the Business cross-connect safeguards the
parameters of the original service as it exists in the ATM environment: no
changes in IP configuration, transparency for the (routing) protocols involved,
same QoS offering, and so on. In the ISAM, this model can be realized using the
C-VLAN cross-connect or S+C VLAN cross-connect.
The business version of the VLAN cross-connect mode supports the following
features:
• point-to-point Ethernet interface types
• supported on the hub-ISAM LT NNI ports
• DSL interfaces types:
• ATM:
- Bridged encapsulation carrying IPoE traffic
- IPoA with the required interworking to convert the traffic to IPoE
- PPPoA encapsulation or encapsulation auto-detection is not expected in a business
context
• Ethernet:
- VDSL EFM
- Ethernet LT ports
• Subscriber identification:
A single or a stacked VLAN tag towards the network is associated to a single
business subscriber. Various VLAN assignment schemes exist:
• S-VLAN cross-connect: The S-VLAN indicates the subscriber while the C-VLANs
represent various subscriber-defined services.
• S+C-VLAN cross-connect: The C-VLAN indicates the subscriber, while the
S-VLAN indicates the DSLAM (or the DSLAM-PE pair).
• IP addressing scheme for layer 3 VPNs:
IP addresses are statically assigned to the CPE and PE. Since IP subnets are not
shared between business subscribers, it is sufficient to use a /30 subnet between
the CPE and the PE. The DSLAM must be transparent for routing protocols
between CPE and PE. IP addresses used in the private domain (at the LAN side
of the CPE) are not known to the operator, therefore, these should not be required
in the DSLAM configuration.
• Security features:
For bridged encapsulation: optional limitation of the number of MAC addresses
per VLAN cross-connect.
• Service enforcement:
Policing per subscriber interface (PVC (ATM), subscriber-side VLAN within a
VDSL port/Ethernet LT port (EFM), and so on).
Residential cross-connect features

The VLAN cross-connect supports the following features in the context of
residential subscribers:
• point-to-point Ethernet interface types
• supported on the hub-ISAM LT NNI ports
• DSL interfaces types:
• ATM:
- Bridged encapsulation carrying both PPPoE and IPoE traffic
- PPPoA with the required interworking to convert the traffic to PPPoE
- Encapsulation auto-detection as the encapsulation of residential subscribers is
generally unknown
• Ethernet:
- VDSL EFM
- LT ports
• Subscriber identification:
• A single (C-VLAN) or a stacked (S+C-VLAN) VLAN tag towards the network is
associated to a single residential subscriber
• Optional addition of the PPPoE relay tag (that is, the line ID parameter) in the
PPPoE control messages (this is not supported however on the hub-ISAM LT NNI
ports)
• Optional addition of the DHCP Option 82 (that is, the line ID parameter) in the
DHCP messages (this is not supported however on the hub-ISAM LT NNI ports)
• Optional addition of the DHCPv6 Option 18 and/or Option 37 (that is, the interface
ID and the relay agent remote ID parameters) in the DHCPv6 messages
• Security features:
• 802.1x authentication to allow or disallow the traffic (PPPoE and IPoE) through the
pre-configured VLAN cross-connect in function of the connected CPEs (this is not
supported however on the hub-ISAM LT NNI ports)
• Optional limitation of the number of MAC addresses per VLAN cross-connect
• ACLs: though this should typically be done by the IP edge, it might happen that the
latter does not own enough processing capacity to support that feature
• IP address anti-spoofing: this should ideally be done centrally in the network, but IP
address anti-spoofing might not always be available centrally and/or might suffer
from some dimensioning/performance issues when used for a large amount of
subscribers
• Service enforcement:
• Policing per subscriber interface (PVC (ATM), subscriber-side VLAN within a
VDSL port/Eth LT port (EFM), and so on).
• Further detailed policing actions based on CoS and/or ACL results should be
typically performed centrally where the service awareness is present.
• QoS policy: in case a single PVC is used to carry multiple services and the CPE is
not generating priority tagged frames, segregating services is then only possible at
IP level using the QoS policies offered by the ISAM QoS Policy framework. For
instance, one can define IP sub-flows based on, for example, DSCP values, IP
source or destination addresses or even UDP/TCP port addresses. Each of these
sub-flows can then have its QoS parameters re-marked and/or can be policed. The
same applies for VDSL ports that only carry untagged frames.
• Service selection: performed centrally
• Service accounting: performed centrally
• Local multicast handling: driven by IGMP
See also “Protocol handling in a Layer 2 forwarding model” for more information.
9.9 IPoA cross-connect mode
The IPoA cross-connect mode offers a solution for connecting subscribers with
RFC-2684-routed encapsulation (IPoA) via the GE uplink with the same services as
in an ATM environment. For example, it offers no changes in IP configuration,
transparency for the involved (routing) protocols, QoS, and so on. IPoA is only
supported for IPv4.
Note — The IPoA cross-connect mode is comparable with the VLAN
cross-connect mode, but with IPoA instead of IPoE at the CPE side.
The IPoA cross-connect model implies a cross-connection between the PVC of a

subscriber whose encapsulation is IPoA with a VLAN at the EMAN side.
The following applies for the subscriber subnet behind the customer CPE:
• the CPE performs Network Address Translation (NAT), that is, the subscribers
behind the CPE have a private subnet and the CPE translates the private
subscriber IP address to the public CPE IP address
• the subscribers have IP addresses from the public range and, as a consequence,
the public subscriber IP addresses become visible in the IP network.
In any case, the subnet configuration at the subscriber side (behind the CPE) is
transparent to the ISAM. The ISAM only sees the IP address of the CPE and the IP
address of the edge router; see Figure 9-35 and Figure 9-36.
Figure 9-35 IP network model for business IPoA cross-connect
NE CPE
IP
100.100.100.9 100.100.100.8 /30 Network CPE 100.100.100.10
side side
CPE
Edge IP
100.100.100.13 100.100.100.12 /30 100.100.100.14
Router
CPE
100.100.100.17 100.100.100.16 /30 IP 100.100.100.18
= IP interface IPoE IPoA
Figure 9-36 Ethernet network model for business IPoA cross-connect

IPoE IPoA
IP PVC11
C_VLAN1 CPE1
PVC12
Edge PVC21
Router S_VLAN IP
C_VLAN2 CPE2
PVC22
PVC31
C_VLAN3 IP
CPE3
PVC32
= L2 interface
IPoA cross-connect features

The following features are supported for the IPoA cross-connect mode:
• The IP address of the CPE is static (no dynamic CPE IP address assignment via
DHCP).
• The ISAM is transparent for routing protocols between CPE and PE.
• Only /30 subnet is supported between the ISAM and the CPE.
• A given CPE can be associated with up to 30 different subnets (multi-VPN). Each
of these subnets will then be served with a separate PVC and separate VLAN.
• There is VLAN stacking on the GE uplink. Typically, the C-VLAN indicates the
CPE and the S-VLAN indicates the ISAM (or the paired ISAM-PE).
• There is internal prioritization based on Differentiated Services CodePoint
(DSCP) bits, both for the upstream and the downstream direction.
• There is upstream p-bit marking.
Cross-connect from IPoA to IPoE (upstream)

The IP packet is extracted from ATM (IPoA) and encapsulated into Ethernet (IPoE),
as follows:
• Unicast IP packets:
The LIM MAC address is used as the source MAC address and the destination
MAC address is the MAC address of the edge router which is resolved from the
edge router IP address via ARP.
• Broadcast and multicast IP packets:
The LIM MAC address is used as the source MAC address and the destination
MAC address is derived from the broadcast or multicast destination IP address.
Cross-connect from IPoE to IPoA (downstream)

The IP packet is extracted from Ethernet (IPoE) and encapsulated into ATM (IPoA).
The CPE interface (PVC) is determined from the VLAN (or S-VLAN and C-VLAN
combination) since it is cross-connect mode.
The destination MAC address can either be the LIM MAC address (the ISAM
responds to an ARP request for the CPE IP address generated by the edge router), or
a broadcast or multicast MAC address.
9.10 Secure forwarding in iBridge and VLAN cross-connect
Secure forwarding is a feature applicable to iBridge and VLAN cross-connect

forwarders. It increases the network security by making use of the IP characteristics
of the traffic. It is applicable both for IPoA (IPv4 only) and IPoE (IPv4 or IPv6) user
traffic. When enabled, secure forwarding provides the following features::
• IP session awareness:
DHCP messages are snooped to dynamically learn IP session information.
• IP address anti-spoofing is activated both for dynamic IP sessions and statically
configured IP addresses/subnets.
Any IP packets whose IP source address does not match any of the following are
discarded:
• any IP addresses allocated to the subscriber interface through DHCP
• any static IP addresses
• any IP subnets programmed by the operator
In case of IPv6, the ISAM discards any IPv6 packets whose IPv6 source address
does not match any IPv6 addresses or prefixes that are either statically configured
or dynamically to the user interface. The ISAM will only check the first 64 bits
of the 128-bit IPv6 address. This is sufficient because the last 64 bits of the IPv6
address hold the “Interface Identifier”. The Interface ID is typically based on the
interface MAC address and therefore not of relevance to the IPv6 anti-spoofing
function.
• ARP relay is performed both for dynamic IP sessions and statically configured IP
addresses/subnets.
Downstream broadcast ARP messages are forwarded to the correct subscriber
port only. This provides some security against malicious subscribers doing a
“theft of service”.
Secure forwarding relies on DHCP snooping (for more information on DHCP, see
chapter “Protocol handling in a Layer 2 forwarding model” and chapter “Protocol
handling in a Layer 3 forwarding model”.
The operator can enable or disable the secure forwarding feature per iBridge / VLAN
cross-connect.
When secure forwarding is applied to iBridges, it is sometimes referred to as
Enhanced iBridge forwarding.
Figure 9-37 Enhanced iBridge architecture
IS AM
Useer r
Us CPE L
LT
DHCP s nooping/ ARP
Useer r
Us CPE S tatic config. Relay
VLAN IP Subnet
Useer r
Us CPE iBridge
Useer r
Us CPE L
LT NT
DHCP s nooping/ ARP
Useer r
Us Relay EMA IP
CPE S tatic config. IP
network
Useer r
Us iBridge Bridge IP edge
CPE
Useer r
Us CPE L
LT
DHCP s nooping/ ARP
Useer r
Us CPE S tatic config. Relay
Useer r
Us CPE iBridge
Us ers can belong to a

different public s ubnet
ubnet.
Secure forwarding is supported by all ISAM LT types: DSL and point-to-point

Ethernet.
Secure forwarding is supported for S+C iBridge on DSL and P2P ETH (UNI).
Full support of anti-spoofing for IPV4 (dynamic addresses via DHCP, static
addresses via configuration, ARP, data plane)
Basic support of anti-spoofing for IPV6 (dynamic addresses via DHCPV6, static
addresses via configuration).
Secure forwarding is not supported on the hub-ISAM LT NNI ports.
IP session awareness
The ISAM snoops DHCP messages to learn what IP addresses/subnets have been
allocated to a subscriber port.
Note — For more information about DHCP, see Chapter “Protocol

handling in a Layer 2 forwarding model” and Chapter “Protocol
handling in a Layer 3 forwarding model”.
The ISAM keeps the IP session information (that is, IP address and associated subnet
of the subscriber, lease time, default gateway IP address, DHCP server IP address,
and so on) during the lifetime of the DHCP session.
The IP session information is used during ARP relay and to install IP anti-spoofing
filters.
IP address anti-spoofing
The following applies for IP address anti-spoofing:
• IPv4 address anti-spoofing for dynamic IP addresses learned through DHCP.
Any IP packets whose IP source address does not match any IP address allocated
to the subscriber interface through DHCP are discarded.
Though the main scenario when considering IP awareness in the iBridge VLAN
cross-connect context is a configuration where IP addresses are dynamically
allocated by a DHCP server, static IP addresses and/or subnets must also be
supported to cover the following cases:
• migration from legacy network where CPEs are already configured with a static IP
address
• DHCP servers that do not support Option 82
• IPv6 address anti-spoofing for dynamic IPv6 addresses learned through
DHCPv6.
The ISAM discards any IPv6 packets whose IPv6 source address does not match
any IPv6 addresses or prefixes allocated to the user interface. The ISAM will only
check the first 64 bits of the 128-bit IPv6 address.
• IPv6 address anti-spoofing for static IP addresses and/or IP subnets (IP prefix +
length) configured by the operator.
Any IPv6 packets whose IPv6 source address does not match any static IPv6
addresses and/or prefixes programmed by the operator are discarded. The ISAM
will only check the first 64 bits of the 128-bit IPv6 address.
• IP address anti-spoofing for control messages.
IP address anti-spoofing is applied to control messages like ARP, IGMP and
DHCP.
ARP relay
The iBridge forwarding rules allow a basic ARP handling:
• Downstream ARP messages
When setting the broadcast flag for a given iBridge, downstream ARP requests
are forwarded to all subscribers connected to the iBridge.
• Upstream ARP messages

ARP requests originating from the subscriber are broadcast to all network bridge
ports.
A more intelligent way of dealing with ARP messages is ARP relay.

Note — ARP relay is not the same as the so-called “ARP-proxy”
defined in the context of IP forwarding. Indeed, the ISAM will never
answer with its own MAC address in the context of iBridging but will
direct the message to the host in charge of answering.
ARP relay is composed of the following features:

• Broadcast ARP messages received from the network are forwarded to the single
relevant subscriber bridge port.
The ISAM does not broadcast ARP messages to all subscribers. Instead, the
ISAM only forwards an ARP message to the subscriber interface whose IP
address(es) and/or subnet(s) match the IP address targeted by the ARP message.
This in order to reduce the load on the subscriber interfaces and avoid security
flaws by broadcasting ARP messages to all subscribers in an uncontrolled way. It
is then up to the subscriber to reply to the ARP message (there is no ARP state
machine in the ISAM).
To simplify the downstream forwarding of ARP messages in the ISAM, the IP
addresses that are statically configured or learned via DHCP on a subscriber port
must be non-overlapping with any other IP addresses that exist on the same or any
other subscriber port. This is guaranteed in the following way:
• Configuring a static IP address/subnet that overlaps with any other static one is
prevented at the time of configuration.
• When a DHCP session is set up that contains overlapping IP address, the DHCP
message exchange between the subscriber client and the DHCP server is completed
as usual. However, the IP address/subnet is not learned on the subscriber port, so no
data traffic will be possible with that IP address/subnet due to the IP anti-spoofing
filter. In addition, an alarm is generated.
• Non-local ARP messages received from the subscribers are broadcast to all
network bridge ports.
ARP messages coming from a subscriber, provided they are not targeted to the
same subscriber, are broadcast to all network interfaces, allowing the edge routers
to reply with their own MAC address. To avoid bothering the network with ARP
messages intended for hosts located on the local network of the subscriber, the
ISAM discards any ARP messages, whose targeted IP address belong to the list
of IP addresses and/or subnets defined for IP address anti-spoofing on that
subscriber’s interface.
Because iBridging in the ISAM does not allow user-to-user traffic, the edge
router must support local ARP proxy and IP traffic hair-pinning (that is, traffic
received on a given interface that must be forwarded to the same interface based
on the routing table) if user-to-user traffic is needed.
ICMPv6
The details of ICMPv6 protocol handling are captured in Chapter “Protocol handling
in a Layer 2 forwarding model”.
IPoA support for secure forwarding

By similarity with IPoA VLAN cross-connect, secure forwarding is supported with
IPoA encapsulation: IPoA upstream traffic is converted into IPoE traffic and
vice-versa.
9.11 Virtual MAC
Layer 2 forwarding models typically identify a subscriber device using a MAC

address. However, since these devices are not directly controlled by the operator,
their MAC address cannot be trusted. Various mechanisms have been put in place to
deal with this, such as the duplicate MAC address control of the ISAM iBridge.
However, this only partially solves the issue, because:
• MAC address uniqueness can only be guaranteed at the ISAM level and not
across the whole access network
• The ISAM can detect a duplicate MAC address but cannot differentiate the
well-meaning subscriber from the malicious one
The concept of virtual MAC (vMAC) offers a complete solution by replacing the
MAC address of the subscriber with a MAC address defined by the operator (and
therefore, fully controlled). Enabling vMAC allows improving layer 2 forwarding
models in the following two areas:
• Security:
Translating the MAC address of the subscriber by an operator-defined MAC
address ensures, by definition, the uniqueness of the MAC address across the
whole access network, automatically alleviating all issues related with duplicate
MAC addresses.
• Scalability:
By guaranteeing that a MAC address is unique across the whole access network,
an operator can now choose to connect multiple DSLAMs to the edge router
through the same network VLAN. By doing so, the operator increases the number
of subscribers sharing the same subnet and, consequently, improves the pooling
effect when allocating IP addresses.
Caution — Although vMAC addresses are saved during an LT board

reset, they are not saved if the LT board is powered down.
Note — vMAC is currently not supported on the hub-ISAM LT NNI

ports.
Deployment scenario example

One possible deployment scenario for vMAC is shared network VLAN for IP
address pooling.
Without enabling vMAC, the iBridge implementation only guarantees MAC address
uniqueness at ISAM level, that is, not across the whole access network. In that case,
you can only avoid duplicate MAC addresses by guaranteeing that the traffic from a
DSLAM is not mixed with the traffic of another DSLAM in the EMAN, before
entering the IP edge. In other words, avoiding duplicate MAC addresses is achieved
by assigned a dedicated network VLAN per DSLAM; see Figure 9-38.
Figure 9-38 iBridge

Edge EMAN ISAM CPE
I-Bridge
VRF Bridge
I-Bridge
IP subnet IP address
Activating vMAC support in iBridge removes the preceding constraint and allows
sharing a same network VLAN across multiple DSLAMs. This network VLAN
sharing improves the scalability of the access network regarding IP address
allocation; see Figure 9-39.
Figure 9-39 iBridge with vMAC enabled

Edge EMAN ISAM CPE
vMAC
bridge
VRF Bridge
vMAC
bridge
VLAN / IP subnet IP address
Sharing a network VLAN across multiple DSLAMs might lead to enabling

user-to-user communication between subscribers connected to different DSLAMs
through the Ethernet switches. This is typically not wanted by the access network
operators and must be blocked by either the Ethernet switch (using the concept of
split horizon at layer 2) or by the DSLAM itself.
vMAC features
vMAC has the following features:
• vMAC support can be enabled or disabled per network VLAN
• maximum number of vMAC per port is programmable
• silent discard of packets received with a new subscriber MAC address when no
free vMAC is left
• vMAC translation is not applied to multicast, broadcast and invalid MAC address
• the DSLAM ID is programmable by the operator

• DHCP algorithm
• ARP algorithm
• ICMPv6 algorithm
• Ethernet OAM algorithm
• user-to-user communication can optionally be blocked
• vMAC address - MAC address translation table recovery
• application or not of vMAC to DHCP Option61 user MAC address
Enable/disable vMAC support per network VLAN

vMAC support can be enabled per network VLAN and this independently of the
forwarding model.
vMAC can be used in conjunction with:
• C-VLAN cross-connect
• S+C-VLAN cross-connect (vMAC is an S-VLAN level attribute)
• iBridge
• stacked iBridge
Note 1 — vMAC cannot be used in conjunction with S-VLAN

cross-connect or layer 2-terminated VLAN.
Note 2 — vMAC is controlled at S Level for an S+C iBridge
vMAC can also be used in conjunction with IP routing where the NT board acts as
IP router and the LT board as iBridge.
vMAC support together with the IP routing model (and LT board acting as iBridge)
is advised, so that any issues with duplicate MAC addresses are avoided. This is what
you would expect with a black box IP router DSLAM (that is, the IP router should
still work even if all subscribers were using the same MAC address).
vMAC support is characterized as follows:
• Upstream traffic:
• Each time a new MAC address is received from the subscriber, a free vMAC is
associated with the MAC address of that subscriber.
• The MAC source addresses of the Ethernet packets are overwritten with the vMAC
associated with the subscriber MAC address found into the MAC source address
field.
• vMAC algorithms (ALGs) might be applied to control plane messages (ARP,
DCHP, Link Related Ethernet OAM, and so on).
• Downstream traffic:
• The MAC destination addresses of the Ethernet packets are overwritten with the
subscriber MAC address associated with the vMAC found in the MAC destination
address field.
• vMAC ALGs might be applied to control plane messages (ARP, DCHP, Link
Related Ethernet OAM, and so on).
When unused, vMAC are freed based on the standard MAC address aging process.
Note — All the dimensioning parameters related to the standard

MAC address (for example, average number of MAC addresses per
subscriber, maximum number of MAC addresses per subscriber, and
so on) also apply when vMAC is enabled within a given network
VLAN.
Maximum number of vMAC addresses per port is programmable

The maximum number of vMAC addresses that are allowed on a given subscriber
port can be specified.
Note — This limit is programmed by setting the maximum number of
MAC addresses per port (generic MAC address related feature).
Silent discard
Packets received with a new subscriber MAC address when no free vMAC is left are
silently discarded.
Any packet received from a subscriber, and whose MAC source address should be
learned because it is still unknown, will be silently discarded if there is no free
vMAC left for that subscriber.
vMAC translation is not applied to multicast, broadcast and invalid MAC address
A vMAC will only be assigned to a unicast and valid MAC address received from
the subscriber. Any other valid MAC address is kept unchanged (multicast and
broadcast).
DSL/Eth LT vMAC format

In the vMAC format, the DSLAM ID can be set by the operator, see Table 9-2.
To ensure uniqueness of the vMAC within the EMAN, vMAC cannot be enabled on
any network VLAN until the DSLAM ID has been programmed by the operator. It
is the responsibility of the operator to ensure that unique DSLAM IDs are assigned;
otherwise duplicate vMAC addresses may be generated by different DSLAMs.
Table 9-2 vMAC format for data traffic forwarding
MAC Address Configurable Description
Bit 47...45 No Rack ID (minus 1)
Bit 44 No ISAM xDSL vMAC set to 0
Bit 43...42 No Reserved field for other applications, set to 0’s for the vMAC
application
Bit 41 No U/L field set to 1 (local MAC address validity)
Bit 40 No I/G field set to 0 (unicast address)
(1 of 2)
MAC Address Configurable Description
Bit 39...21 Yes DSLAM ID set by the operator [1...524287]

A unique DSLAM ID within an EMAN connected to the same IP
edges
Bit 20...15 No Slot ID of the line board [0…63]

The logical position of the line card within the DSLAM.
Bit 14...6 No Port ID of the subscriber interface [0…511]

Bit 5...0 No MAC ID unique to each subscriber MAC address
(2 of 2)
DHCP algorithm
The chaddr field of the DHCP messages must be translated as follows:
• Upstream: the subscriber MAC address is replaced by the associated vMAC
address
• Downstream: the vMAC address is replaced by the associated subscriber MAC
address
Note — When vMAC is enabled, the DHCP lease time must be less
than the MAC aging timer (on the ISAM or on the VLAN), or else the
vMAC address for the subscriber will be forgotten before the DHCP
session expires. In this case, when the subscriber attempts to renew
the session, it is possible that the network is reached using a different
vMAC address, causing it to be discarded.
ARP algorithm
The MAC address field present in the ARP message payload is updated in a similar
way as for DHCP.
ICMPv6 algorithm
The MAC address field present in the ICMPv6 Neighbor Discovery message
payload is translated as follows:
• Upstream Neighbor Solicitation (NS): translate the MAC address carried in the
“source link-layer address” option. This option contains the MAC address of the
routed modem (or PC behind a bridged modem), hence it must be translated to the
vMAC address
• Upstream Neighbor Advertisement (NA): translate the MAC address carried in
the “target link-layer address”
• Upstream Router Solicitation: translate the MAC address carried in the “source
link-layer address” option.
Ethernet OAM algorithm

The MAC address field present in the payload of Ethernet OAM messages
exchanged with the subscribers is updated in a similar way as for the DHCP case.
User-to-user communication can optionally be blocked

If an operator wants to share a VLAN across multiple DSLAMs, but the Ethernet
switches are unable to block user-to-user traffic, the operator can enable dedicated
filters at ISAM level to discard subscriber traffic received from other DSLAMs.
Those filters must be implemented so that they do not prevent using typical access
network topologies (for example, star, ring, dual homing, and so on).
The filter is implemented per VLAN at LT board level so that the NT board still
behaves as a normal bridge, in order to support all access network topologies (for
example, ring).
The LT filter discards any Ethernet packet received from the NT board within the
specified VLAN and whose MAC source address matches the non-DSLAM specific
fields of the vMAC (that is, DSLAM ID, rack/shelf/slot/Port/MAC IDs).
vMAC address - MAC address translation table recovery

Enabling vMAC support makes the iBridge implementation state full. The ISAM
recovers the stable states in case of LT software failure, LT board reset or LT
software upgrade.
In this manner, a correct vMAC-address-to-IP-address mapping is maintained to
avoid issues with:
• DCHP servers: for example, IP address lease renewal, where the subscriber is
identified using the vMAC (that is, chaddr)
• IP routers implementing IP address anti-spoofing by coupling the vMAC and the
IP address learned through DHCP snooping
9.12 PPP Cross-connect mode
PPP cross-connect is a forwarding mode in which the ISAM forwards traffic from
PPP sessions from the user side through PPP sessions at the network side towards a
BRAS and conversely, and this as long as the user PPP session is living. There is
always a 1:1 relationship between the PPP session at user side and the PPP session
at network side. This justifies the use of the term “cross-connect” which must be
understood as “PPP session cross-connect”
By nature the PPP session is PPPoE at the network side. The network VLAN of a
PPP cross-connect can be single tagged (like an iBridge or a C-VLAN cross-connect)
or dual tagged (like an S+C-VLAN cross-connect).
It should be noted that PPP cross-connect does not require that the user encapsulation
is Ethernet. It works as well with PPPoA as with PPPoE although the PPP session
setup handling is different:
• In case of PPPoA, the ISAM is responsible for setting up and releasing the PPPoE
session which will encapsulate the user PPP packets.
• In case of PPPoE, the PPPoE session is set up and released by the user himself
and the ISAM just relays it to the network side.
For this to happen, the following must take place:

• The operator statically configures the PPP cross-connect forwarder, which
network VLAN it uses and which users may use it. It is possible that multiple user
sessions are multiplexed via PPPoE in one N:1 network VLAN, and it is possible
that there is a 1:1 relationship between the user and the network VLAN.
• Each time a user initiates a PPP session, the ISAM goes though a dynamic PPP
session marking phase: during this phase, the ISAM sets up information
necessary to forward packets between user and network.
When the PPP session is terminated, the ISAM deletes the marked session
information.
A property of PPP cross-connect is that the ISAM sends PPPoE packets to the
network using its own MAC address as source address. Thus, for the network, the
ISAM looks like the PPP client itself and actually performs user MAC address
concentration.
Note — The possibility exists - for legacy purpose - to configure PPP

cross-connect without MAC address concentration. In this mode, only
PPPoA traffic is accepted by the PPP cross-connect, whereas PPPoE
is automatically iBridged or VLAN cross-connected to the same
network VLAN as the PPP cross-connect. When not specified, the
term “PPP cross-connect” must always be understood as “PPP
cross-connect with MAC address concentration”
The general model of a PPP cross-connect engine with MAC address concentration
is quite intuitive. It is shown in Figure 9-40.
Figure 9-40 General PPP cross-connect engine
PPP CC Client Port PVC, EFM, VLANPort or GE
iBridge VLAN
PPPoE
PPPoE
or PPPCCE
PPPCCE
Server
Server
CC VLAN
PPPoA
&
PPPoE
In case of PVC
The VLAN which is attached to a PPP cross-connect Engine on the network side
must be of iBridge or VLAN cross-connect type. Of course, when the VLAN is of
type cross-connect, only one user is attached to the engine.
The type of interface on which a PPP Client Port can be configured must be one of
the following:
• EFM interface for untagged PPPoE traffic
• PVC for PPPoA and/or untagged PPPoE traffic
• Ethernet interface for untagged PPPoE traffic

• VLAN port interface for tagged PPPoE traffic
Note — It is intentionally not possible to create a client port on a

bridge port.
All the supported encapsulations for PVCs are shown in Figure 9-41.
Figure 9-41 Accepted ATM encapsulation for PPP cross-connect Forwarding with MAC
address concentration
asamAtmVclEncapsAutodetect
Client
Client Port
Port disabled(1) or
autoDetectPPPoA(4)
PPPCCE
PPPCCE PPPoA
VC
VC asamAtmVclEncapsType
llcNlpid(3) or
vcMuxPppoa(6)
Client
Client Port
Port
Untagged
PPPCCE
PPPCCE
PPPoE
VC
VC asamAtmVclEncapsAutodetect
disabled(1),
asamAtmVclEncapsType
Client
Client Port
Port llcSnapBridged(1) or
Tagged vcMuxBridged(4)
PPPCCE
PPPCCE
PPPoE
VlanPortBridgePort VC
VLANPort VC
asamAtmVclEncapsAutodetect
autoDetectPPP(3) or
Client
Client Port autoDetectIpoePpp (5)
Port PPPoA
PPPCCE
PPPCCE
or asamAtmVclEncapsType
Untagged llcSnapBridged(1),
VC
VC
PPPoE llcNlpid(3),
vcMuxBridged(4),
vcMuxPPPoA(6)
PPP cross-connect implementation

The object model of a PPP cross-connect depicted in Figure 9-40 is quite simple:
• a forwarding engine applying PPP cross-connect forwarding rules
• one network VLAN
• one or several client ports on top of PVCs, VLAN port interfaces, EFM interface
or Ethernet interface to attach users
Note — PPP cross-connect is not supported in hub-ISAM LT NNI

ports.
PPP Cross-connect inside the ISAM

PPP cross-connect forwarding is implemented by a cooperation of functions in the
LT board and NT board as shown in Figure 9-42.
Figure 9-42 PPP cross-connect inside the ISAM
PVC, EFM, VlanPort or EthPhy

PPP CC Client Port
PPP CC Engine
L2 Fwd PPPCCE
PPPCCE
EMAN L2 Fwd
LT
NT
DSLAM
10 — Protocol handling in a Layer 2
forwarding model
10.2 Link aggregation 10-3
10.3 RSTP and MSTP 10-5
10.4 Connectivity Fault Management 10-7
10.5 802.1x support 10-10
10.6 BCMP 10-11
10.7 ARP 10-12
10.8 DHCP 10-13
10.9 IGMP 10-18
10.10 PPPoE 10-18
10.11 DHCPv6 10-23
10.12 ICMPv6 10-24
10 — Protocol handling in a Layer 2 forwarding model
10.1 Introduction
Layer 2 protocol handling can be divided into two parts of handling:

• Layer 2 Control Protocol handling:
Layer 2 Control Protocols are protocols defined for use within the Layer 2
network. They are defined to influence the forwarding behavior within this Layer
2 network and/or to maintain and troubleshoot this Layer 2 network. This
includes protocols that have an individual or group of interfaces as scope, and it
includes protocols that have the end-to-end connectivity within this Layer 2
network as scope.
• Application protocol handling:
These are protocols defined at a layer higher than Layer 2. They are used for
communication between nodes connected to the Layer 2 network and/or nodes
deeper in the IP (Layer 3) network. Participation of the ISAM - being the
boundary node of the service provider network - in processing these protocols,
enables the general network or nodes deeper in the network to provide better
services to subscribers
Layer 2 Control Protocol handling

Table 10-1 shows the protocols of the Layer 2 control protocol handling.
Table 10-1 Layer 2 control protocol handling
Protocol Described in Section
Link Aggregation 10.2
Rapid Spanning Tree Protocol and Multiple Spanning Tree Protocol 10.3
Connectivity fault management 10.4
802.1x 10.5
Broadband Access Network Cluster Management Protocol (BCMP) 10.6
Application protocol handling

Table 10-2 shows the protocols of the application protocol handling.
Table 10-2 Application protocol handling
ARP 10.7
DHCP 10.8
IGMP 10.9
PPPoE 10.10
DHCPv6 10.11
(1 of 2)
ICMPv6 10.12
(2 of 2)
These protocols play an important role in the way subscribers establish connectivity
and/or access broadband services. The ISAM supports a set of protocol processing
features in order to maintain network security and allow customer identification and
troubleshooting. These are defined in the next sections.
The use of these control protocols can lead to security issues when malicious users
try to perform a (Distributed) Denial of Service attack towards the systems handling
the user-generated control traffic (for example, a BRAS, an Edge Router or a DHCP
server). In order to protect these systems, the ISAM can be configured to perform
upstream policing for the following protocols: ARP, DHCP, DHCPv6, IGMP,
ICMPv6, PPPoE and Connectivity Fault Management. The policing rate and
maximum burst size can be configured separately for each of the mentioned
protocols.
10.2 Link aggregation
Link Aggregation allows one or more links to be aggregated together to form a Link
Aggregation Group, such that a MAC client can treat the Link Aggregation Group as
if it were a single link. Link aggregation is defined in IEEE 802.3-2005, clause 43.
This specification specifies the establishment of Link Aggregation Groups,
consisting of N parallel instances of full duplex point-to-point links operating at the
same data rate.
This Link Aggregation Group provides increased bandwidth and/or increased
availability. Link aggregation is defined with a load sharing mechanism that
distributes the traffic over the active links of the Link Aggregation Group. When one
of the physical links of the link Aggregation Group is no longer active, then the load
sharing adapts and distributes the traffic over the remaining active links. If the total
traffic exceeds the bandwidth of an active link, then normal QoS handling applies.
Figure 10-1 shows an example of link aggregation.
Figure 10-1 Link aggregation

IP Edge Router /
BRAS
Link Aggregation
Ethernet
Group 1 NSP IP backbone
Bridge
NE
ADSL
m x FE/GE
FE/GE n x FE/GE
Link Aggregation
Group 2
NSP IP backbone
Link Aggregation is defined for use between any type of Ethernet nodes (that is, both
bridges and end stations). The binding of links into Link Aggregation Groups may
be under manual control by an operator. In addition, automatic determination,
configuration, binding, and monitoring may occur through the use of a Link
Aggregation Control Protocol (LACP).
Link Aggregation Control Protocol

The Link Aggregation Control Protocol (LACP) is part of the IEEE 802.3-2005
clause 43. The LACP provides a standardized means for exchanging information
between Partner Systems on a link to allow their Link Aggregation Control instances
to reach agreement on the identity of the Link Aggregation Group to which the link
belongs, move the link to that Link Aggregation Group, and enable its transmission
and reception functions in an orderly manner.
Also the use of LACP requires some operator control. Especially important is the
configuration of actor-keys per physical link. This parameter identifies the Link
Aggregation Group and is exchanged within the protocol to the peer side to assure
that the links of one link aggregate really connect to the same node.
When an inconsistency is detected between the configured information and the
connectivity of a link, the involved link is not activated.
If a link fails, this is detected by LACP. It removes the link from the active set of the
link aggregate. When the link comes up again, LACP puts the link back in the active
set of the link aggregate.
Link aggregation support

Link aggregation is supported on:
• network links
• subtending links
• the GE Ethernet LT board UNI and NNI port types
Link Aggregation Groups are defined by configuring individual physical links with
identical link aggregation parameters. Especially the parameter actor-key is
important as the Link Aggregation Group is defined as the set of links with the same
value for this parameter.
The use of the LACP protocol can be enabled or disabled.
Load balancing is supported and the load balancing criteria can be configured to use
the source and/or destination MAC address, or to use the source and/or destination
IP address.
Figure 10-2 shows link aggregation support.
Figure 10-2 Link aggregation support

network links
n LT links
xHub L LT
n
L.A.G. s s
.
L.A.G. subtending links PVCs
(on top of xDSL links)
network links L.A.G.
n n
xHub LT links LT
L
s s
L.A.G. subtending links PVCs

(on top of xDSL links)
n: link type is network link
L: link type is LT link
s: link type is subtending link
Note — Link aggregation is not supported on subscriber links (with

the exception of the GE Ethernet LT board UNI subscriber links) .
10.3 RSTP and MSTP
The ISAM can be configured with several network interfaces. They can be used to
connect the ISAM to multiple Ethernet Bridges, see Figure 10-3 as example, or
directly to end stations such as, for example, a Router or a BRAS.
For an Ethernet network to function properly, only one active path can exist
throughout an EMAN Network between two end stations. These paths are
symmetrical, that is, they are used for both directions of communication.
Figure 10-3 Spanning Tree between NE and EMAN

IP Edge Router /
BRAS
Ethernet
NSP IP backbone
Bridge
NE m x FE/GE
ADSL
FE/GE
n x FE/GE
: Link disabled by spanning tree protocol NSP IP backbone

Selected root of spanning
RSTP
The Rapid Spanning Tree Protocol (RSTP) as defined in IEEE 802.1D-2004, clause
17, is a Layer 2 Control Protocol that provides path redundancy while preventing
undesirable loops in the network.
Providing path redundancy starts with having a physically redundant network
topology.
Multiple active paths between end stations cause L2 loops in the network. If a loop
exists in the network topology, the potential exists for duplication of messages.
Therefore the task of RSTP is defining a single active path between each pair of end
stations.
To realize this single active path, RSTP forces certain redundant data paths into a
standby (blocked) state. The logical topology that is realized in this way is a single
tree with a selected root end station and with the other end stations at leave positions.
Ethernet Bridges are involved in selecting the active path and blocking the standby
paths. After a network node or link has become unavailable, RSTP will run again to
define a new tree topology.
MSTP
If the network contains more than one VLAN, the logical network configured by a
single RSTP would work, but better use can be made of the available redundant
nodes and links by using an alternate spanning tree for different (groups of) VLANs.
Multiple Spanning Tree Protocol (MSTP) which uses RSTP for rapid convergence,
enables VLANs to be grouped into a spanning-tree instance. Each instance has a
spanning-tree topology independent of other spanning-tree instances. This
architecture provides multiple forwarding paths for data traffic, enables load
balancing and limits the number of spanning-tree instances required to support a
large number of VLANs. MSTP is defined in IEEE 802.1Q clause 13.
Support of RSTP and MSTP

The ISAM can be configured to act as an Ethernet Bridge within an EMAN Network.
Then RSTP and MSTP is supported on network links, on subtending links, and on
subscriber links terminated on the NT board. The MSTP protocol is also supported
on the GE Ethernet LT board NNI port type.
The ISAM can be configured to act as Router. This router functionality is provided
on top of the Layer 2 Bridging functionality. All ISAM links are considered as being
part of a single EMAN Network. In that case the ISAM acts as an end station
connected to this EMAN Network. Then, as before, RSTP and MSTP are supported
within this EMAN Network on network links, on subtending links, and on subscriber
links terminated on the NT board.
Note — The GE Ethernet LT board NNI port type is used for access
aggregation or business services access but not as a network uplink
interface.
In some network topologies the use of RSTP or MSTP will not provide any benefit.
This is the case when the single active path is already realized at physical level. An
example is that the user equipment connected to LT boards (must) have already by
construction a single physical interface and inherently this will form a single active
path. Therefore and because of this RSTP and MSTP are not supported on these
interfaces. Other examples are the use of a single link (aggregation group) between
a hub and a subtending ISAM. Therefore, RSTP and MSTP can be enabled or
disabled per Ethernet interface of the ISAM. As an example, RSTP and MSTP shall
be disabled on the network interface of the subtending ISAM in case it is disabled on
the corresponding subtending interface in the Hub ISAM.
Note 1 — The 7302 ISAM supports RSTP and MSTP towards
DSLAMs in a ring.
Note 2 — The 7302 ISAM and the 7330 ISAM FTTN support STP
(IEEE 802.1D-1998, clause 8) for inter-operability with older routers.
10.4 Connectivity Fault Management
This section describes Connectivity Fault Management (CFM) and identifies the
level of support in the ISAM.
CFM elements
Connectivity Fault Management (CFM) is an Ethernet Operations and Maintenance
(OAM) capability that allows service providers or network operators to verify and
isolate connectivity faults and configuration problems at layer 2. CFM is specified in
the standard IEEE 802.1ag.
To support CFM functionality, network operators must configure software entities
called Maintenance Points (MPs) on selected bridge ports on the network. MPs are
points where CFM messages are inserted, extracted, or monitored to verify
connectivity within part or within the whole of the Layer 2 network.
MPs are organized into Maintenance Associations (MAs) and Maintenance Domains
(MDs) on a network. Table 10-3 describes the CFM elements that must be
configured on an Ethernet network.
Table 10-3 CFM elements
CFM element Description
MD An MD corresponds to the administrative OAM domain and is assigned a level from

1 to 8. A typical example is that an administrative OAM domain is defined per
operator involved in the offering of a service with the Layer 2 network.
Associated to an MD are one or multiple MAs.
(1 of 2)
CFM element Description
MA An MA is defined as an OAM maintenance entity per service instance per MD. The
service instance could be a VLAN or a set of VLANs. The OAM maintenance entity
scope is defined by a set of associated Maintenance end Points (MEP). The MEPs
define a closed segment of the VLAN in the Layer 2 network. The segment
matches the scope or involvement of a particular administrative OAM domain
(operator) in that VLAN.
As such, MDs/MAs allow network operators to test the segment of a given VLAN
that is within their own scope. For example, it allows them to perform a test on
all links and nodes of their own network and being used by the VLAN or service.
Typically, the set of operator segments are all at the same MD level and then the
MDs/MAs cannot overlap.
MDs/MAs also allow network operators to divide a network into separate
hierarchical administrative OAM domains. An MD/MA at a higher level has no
visibility inside an MD/MA at a lower level. Also, at the higher level the same
concepts apply: the scope is delimited by MEPs and the MDs/MAs at the same
higher level cannot overlap.
There may be one or more MA, that is, service instances, per MD. There may be
multiple MAs for the same service instance (VLAN) if these are within different
MDs and the lower level MDs/MAs are terminated with MEPs.
MP MPs are organized into MAs and MDs and are configured on ports within an MD/MA
(VLAN).
There are two types of MPs:
• Maintenance end points (MEPs)
• Maintenance intermediate points (MIPs)
MEPs are points that identify the border of a maintenance entity. MEPs can
initiate or terminate CFM messages.
MIPs are points inside the network segment that is defined as a maintenance
entity. MIPs can respond to and allow the transit of CFM frames originated from
another MP.
(2 of 2)
IEEE 802.1ag defines these generic CFM OAM procedures. DSLF TR-101 defines
the usage of these procedures in a Layer 2 Access Network.
An access aggregation network typically has the following MD levels:
• Service provider domain from the edge router/BNG to the CPE
• Carrier domain from the edge router/BNG or Ethernet switch to the user port on
the ISAM
• Intra-carrier domain from the edge router/BNG or Ethernet switch to the network
port on the ISAM
• Access link domain from the user port on the ISAM to the CPE
Figure 10-4 shows CFM implemented on a typical access aggregation network.
When a customer contacts the service provider helpdesk because of lack of service,
the service provider can run a test in the service provider domain from the BNG
towards the CPE. If the fault is isolated to a specific section, the service provider can
notify the owner of that section who can run tests at a lower level within his domain.
This continues until the failing point is identified.
Figure 10-4 CFM on the access aggregation network

ME Service provider
MD level 7
ME carrier
MD level 5
ME Intra-carrier
MD level 3
Access link ME
MD level 1
CPE
Ethernet
access Regional
network network
RG Ethernet
DSLAM
switch BNG
MEP Scope of access Scope of service

MIP network operator provider operator
CFM functions
The CFM protocols define multiple functions that act as tools to test and isolate
connectivity faults in the network.
The CFM link trace acts as an ICMP traceroute command. Multicast Link Trace
Messages (LTMs) are sent from the originating MEP and are addressed to another
MEP of the MA. Each MIP along the trace path inspects the message to determine
whether the target MAC address of the LTM is known. If the MIP knows the MAC
address, the MIP forwards the LTM to the next MEP, and a response in the form of
a Link Trace Reply (LTR) message is sent back to the originating MEP. An MIP that
does not know the target MAC address does not send back an LTR. When the target
MP responds with a successful LTR message, the link trace test is successfully
completed.
A CFM loopback acts as an ICMP ping command. Multicast or unicast loopback
messages (LBMs) are sent from the originating MEP. In the case of a unicast LBM,
the MAC address of the destination MP is inserted. When the target MP receives the
LBM with the matching MAC address, it sends back a loopback response (LBR) to
the originating MP. When the originating MP receives the LBR, the loopback is
complete. In the case of a multicast LBM, each MEP within the targeted MA in the
MD level that receives the LBM request will reply with an LBR.
A connectivity check (CC) is a message multicast to all MEPs in the same MA at
fixed intervals. When a peer MEP does not receive a specified number of CCM reply
messages in a given time, a fault is raised.
CFM support in the ISAM

The ISAM supports the configuration of MDs, MAs and MEPs. MIPs are created by
the ISAM based on the parameter setting of the MA.
The service instance managed by an MA covers a single VLAN.
The ISAM supports MIPs and network facing MEPs at UNI ports (which includes
UNI ports supported by the GE Ethernet LT board). The ISAM also supports MIPs
at the GE Ethernet LT board NNI ports. Within these MPs the ISAM responds to
LBMs and to LTMs coming from the network. The ISAM responds to LBM coming
from the user (see DSLF TR-101).
The ISAM supports network facing MEPs on the LT board at its GE interface
towards the NT board. Within these MEPs the ISAM responds to LBMs and to
LTMs.
10.5 802.1x support
The 802.1X protocol complies with both the IEEE 802.1X and the CCSA
specification. Its purpose is to control the access of users to the Layer 2 Access
Network. Each 802.1X-enabled user port (including the GE Ethernet LT board UNI
user ports) is by default in a closed status and successful authentication is needed to
open the port.
Packets from unauthenticated subscribers are dropped at the LT until an 802.1x
session is set-up after authentication by an external RADIUS Server, see Figure 10-5.
• For an un-authenticated port, all subscriber frames are discarded.
• For an authenticated port, all subscriber frames are processed based on the Layer
2 configuration
Note — The GE Ethernet LT board NNI ports do not support 802.1x
Figure 10-5 802.1x in the ISAM
LIM xHub Ethernet ER
802.1x Performs authentication

NT by means of contacting
LIM a RADIUS server.
Control The result is sent back
CPE
to the LT.
Handles the 802.1x protocol, communicates with the system

controller to perform the authentication, controls the port state.
10.6 BCMP
The Broadband Access Network Cluster Management Protocol is a a protocol

defined within the context of using radio cable access for IP-based networks. The
BCMP protocol is used by the BCMP client to retrieve management related
configuration (such as management VLAN, management IP, SNMP community
name and so on) from BCMP server. The BCMP client is usually collocated with the
EPON over Coax (EOC) Head-end, and utilized by the EOC Head-end to get above
configuration data during initialization. Once the EOC Head-end gets the
configuration, it can be managed by the network management system.
The BCMP protocol can be enabled or disabled by the operator to allow the EPON
OLT to act as the BCMP proxy for resolution of BCMP packets which are sent from
the BCMP client, and the BCMP server, and further to forward relay the BCMP
packets to between the BCMP client, and the BCMP server.
For BCMP protocol handling on the LT board:
• in upstream: BCMP receives the L2 packets, extracts the L2 information and then
sends it to the NT board
• in downstream: BCMP receives L2 information from the NT board, constructs a
L2 response packet for forwarding through the host message interface
For BCMP protocol handling on the NT board:

• in upstream: BCMP receives the L2 information from the LT board, constructs
L3 packets to maintain the BCMP forwarding table, and relays upstream packets
towards configured BCMP server
• in downstream: BCMP receives the L3 response from the BCMP server, looks up
the BCMP forward table, constructs the L2 information and relays it to the
corresponding LT board
• The BCMP proxy uses the same IP address as the one used for OLT management
and OAM
Figure 10-6 shows an overview of the BCMP protocol.
Figure 10-6 BCMP Protocol Overview
BCMP server
NT-BCMP proxy NT-BCMP proxy
OLT LT LT LT LT
PON ... PON PON ... PON
ODN ODN
ONU ONU
HS
BCMP client BCMP client
EOC EOC
CDN CDN
EOC EOC
The user data stream can be forwarded through the EPON OLT using the S+C RB
mode. However, to forward the SNMP packet transparently through the OLT,
configuration of a specific management VLAN for the SNMP packet is required.
10.7 ARP
The IETF RFC 826 defined Address Resolution Protocol (ARP) is a protocol defined
within the context of using IP over Ethernet. An IP node uses the ARP protocol to
obtain the Ethernet MAC address of another IP node identified by a known IP
address and connected to the same Layer 2 network.
The ISAM provides ARP handling functionality sufficient to prevent broadcast
storms toward the subscribers. This is achieved in the following ways:
• in iBridge mode:
• When an ARP request is received from a user port, the ARP request is broadcast to
the Ethernet network interface. This deviates from the standard Ethernet broadcast
because the ARP request is not broadcast to the other user ports. This behavior is
also true for the GE Ethernet LT board NNI ports.
• When an ARP request is received from an Ethernet network interface, the ARP
request is only broadcast in the VLAN when downstream broadcast is enabled in the
VLAN. Otherwise, the ARP request is dropped. In case of the GE Ethernet LT board
NNI ports, the ARP request is only broadcast in the VLAN (not configurable).
• in VLAN cross-connect mode:
ARP requests are forwarded transparently downstream or upstream like any other
data packet.
• in both forwarding modes:

ARP reply messages receive no special treatment compared to any other data
packet.
• in secure-forwarding-enabled iBridge/VLAN cross-connect mode:
An ARP relay function exists to forward the downstream ARP request messages
to the right user only. This is achieved by forwarding downstream ARP request
messages to the user port that owns the IP address that is to be resolved via the
ARP request.
In the upstream direction this ARP relay will perform IP address anti-spoofing,
that is, it checks the <IP,MAC> binding of a specific customer, learned via DHCP
snooping. An ARP packet is only accepted if the MAC source address and the IP
source address in the ARP payload correspond to a specific customer having
established IP connectivity on that port. Valid ARP requests will be forwarded to
the network. In case of static IP address configuration, the ARP relay performs a
similar check for the sender IP address. The packet is accepted if this address is
configured on that port.
The ISAM supports counters that track the number of ARP packets that have been
dropped per VLAN port because they contain spoofed information in the ARP
payload.
Note 1 — The ARP-Relay function learns the IP addresses from the
end-users either via DHCP snooping or via static configuration.
Note 2 — The GE Ethernet LT board NNI ports do not support secure
forwarding.
Note 3 — For DSL LTs, the above description applies to S+C iBridge
forwarding mode as well.
10.8 DHCP
The Dynamic Host Configuration Protocol (DHCP) is a client-server protocol that

enables DHCP Servers to configure internet hosts. The DHCP protocol is defined on
top of UDP/IP. DHCP simplifies the configuration of a host since no IP addresses,
subnet masks, default gateways, domain names, or DNSs must be locally configured
within the host. Instead, with DHCP, this information is dynamically leased from the
DHCP Server for a predefined amount of time. Because the information is stored on
a server, it centralizes IP address management, it reduces the number of IP addresses
to be used, and it simplifies maintenance. DHCP is defined in IETF RFC 2131.
A problem to solve when using this technology is that the DHCP Client must be able
to communicate to the DHCP Server. This is achieved by the DHCP Client starting
the communication with a broadcast message. The DHCP Server will receive this
message in case the Server is connected to the same Layer 2 network as the Client.
IETF RFC 2131 and RFC 3046 define a DHCP Relay Agent for when this is not the
case. Then a DHCP Relay Agent connected to the Layer 2 network of the Client will
convert the broadcast message to a unicast message and send it to a server further in
the IP network. In doing so, the DHCP Relay Agent can add 'option 82' information.
That information can be used by the DHCP Server to identify the subscriber, and
when mirrored back in reply messages it helps the DHCP Relay Agent to forward the
replies to the correct Client. In its definition this DHCP Relay Agent is a function
within a router for which it can be referred to as a 'Layer 3' DHCP Relay Agent.
DSLF TR-101 defines a “Layer 2” DHCP Relay Agent, that is, a Relay Agent
functionality in the middle of the Layer 2 Access Network. The Layer 2 DHCP Relay
Agent is assigned to be a responsibility of the DSLAM. It shall add option 82
information (which allows the server to identify the subscriber) but leaves the
broadcast message a broadcast message. Converting the broadcast message to a
unicast message is not needed when the DHCP Server is connected directly to the
Layer 2 Access Network, or is the responsibility for a real DHCP Relay Agent at the
edge of the Layer 2 Access Network.
The ISAM provides Layer 2 DHCP Relay Agent functionality when it is configured
for Layer 2 forwarding and a full (Layer 3) DHCP relay when it acts as an IP Router.
Layer 2 DHCP Relay Agent

The ISAM provides Layer 2 DHCP Relay Agent functionality for IPoE and IPoA
subscriber access interfaces for all of the Layer 2 forwarding modes that provide
IPoE and/or IPoA:
• the iBridge
• the protocol-aware cross-connect (that is, C-VLAN cross-connect and
S/C-VLAN cross-connect)
• the iBridge and cross-connect with IPoA to IPoE interworking function
This Layer 2 DHCP Relay Agent is supported for the L2 forwarding modes above,
irrespective of secure forwarding being enabled or not.
The Layer 2 DHCP Relay Agent functions can be split in three parts:
• Relaying DHCP messages to and from network and subscriber interfaces
• Option 82 handling
Note — The layer 2 DHCP Relay Agent is only supported on the GE

Ethernet LT board UNI ports.
Relaying DHCP messages to and from network and subscriber interfaces

Relaying DHCP messages in iBridge and VLAN cross-connect
The Layer 2 DHCP Relay Agent for the iBridge and for the protocol-aware
cross-connect forwarding modes is distributed over the LT boards.
Figure 10-7 Layer 2 DHCP relay implementation)

US: Bridge to the network interfaces (unicast packet forward based on FDB, broadcast
packet: flood to all the network interfaces that participate in the VLAN
DS: Bridge to the LTs/subtending interfaces (unicast packet: forward based on FDB,
broadcast: flood to all network interfaces that participate in the VLAN
DHCP relay
LT xHub Ethernet ER
IP
DHCP client network
LT NT
CPE DHCP
server
US/DS: DHCP boadcast US: adds option 82 and sends packet to xHub
or unicast packet DS: remove option 82 and send on to correct user port
The DHCP client can send broadcast or unicast DHCP messages. These will be
forwarded in the upstream direction:
• If the insertion of option 82 is enabled, the ISAM verifies the DHCP message and
adds option 82 to a valid DHCP message as described further on.
• If the insertion of option 82 is disabled, the ISAM still verifies the DHCP message
as described further but does not add an option 82.
But with or without option 82 insertion, the broadcast message remains a broadcast
message, the unicast message remains a unicast message. For more information on
the handling and configuration of DHCP Option 82; see section “Option 82
handling”.
In the downstream direction the DHCP Relay within the Edge Router (or the DHCP
server in case it is directly connected to the Layer 2 Access Network) sends broadcast
or a unicast DHCP messages. This depends on the broadcast flag inside the DHCP
message sent from the DHCP Client. In all cases the Layer 2 DHCP Relay Agent will
forward the DHCP message to the correct user only. For a unicast DHCP message
the user is identified from the MAC address in the Ethernet header, for broadcast
DHCP messages the user is identified from the payload of the DHCP messages, for
example, chaddr. In any case the option 82 is removed before forwarding the DHCP
message.
Relaying DHCP messages in the iBridge and cross-connect mode with IPoA to
IPoE interworking function
The Layer 2 DHCP Relay Agent for the iBridge and cross-connect mode with IPoA
to IPoE interworking function is very similar to the Layer 2 DHCP Relay Agent
when the IPoA to IPoE interworking function is absent. Its implementation is also
distributed over the LT boards. The possibilities for option 82 insertion are also the
same.
But here, IPoA packets from and to the user do not have an Ethernet header. As such,
the chaddr in the upstream DHCP messages is normally not a MAC address. The
ISAM will insert itself an identifier in the chaddr of upstream messages. This field
being returned by the DHCP Server allows the ISAM to identify the correct user. The
ISAM will restore the original chaddr before sending the DHCP message to the user.
Option 82 handling
IETF RFC 3046 defines a “Relay Agent Information option” and assigns it the code
82. In this way the option is often referred to as “option 82". Option 82 provides
security when DHCP is used in public access networks. It provides the DHCP Server
with trusted information on who is requesting an IP address.
But to make it really a trustable identifier the ISAM shall also discard upstream
messages with an option 82 already added by the user. Therefore, the ISAM also
makes some validity checks on upstream DHCP messages.
In the upstream direction, the insertion of DHCP option 82 is configurable. If
enabled, option 82 parameters are inserted both for unicast and broadcast DHCP
messages. If disabled the ISAM does not add option 82. The validity checks are
however executed also when option 82 insertion is disabled.
IETF RFC 3046 defines option 82 as containing two sub-options: the circuit-id being
sub-option 1 and the remote-id being sub-option 2.
In addition to enabling or disabling option 82 insertion, it is possible to control the
insertion and contents of the sub-options:
• the circuit ID: this can be configured with one of the following values:
• do not add this sub-option into option 82
• add the customer ID into the circuit-id sub-option
• generate a physical line ID and add this into the circuit-id sub-option
• the remote ID: this can be configured with one of the following values:
• do not add this sub-option into option 82
• add the customer ID into the remote-id sub-option
• generate a physical line ID and add this into the remote-id sub-option
Note — The values for the circuit ID and the remote ID are not
allowed to be identical.
Insertion of the circuit ID and/or remote ID can be enabled or disabled per VLAN in
iBridge or VLAN cross-connect mode.
Customer ID
The Customer ID is fully configurable for each DSL line, ATM PVC, Ethernet
interface or VLAN port by the operator (string with a length between 0 and 64 bytes).
In case the Customer ID is configured for one user at various levels, for example, at
ATM PVC and at DSL line level, then the most fine grained level will be used. For
example, the Customer ID configured for an ATM PVC will take precedence over
the customer ID configured at the DSL line.
Physical line ID
By default, the Physical line ID is auto-generated by the ISAM and contains
information used to identify the precise circuit from which the DHCP message
originates (for example, DSL line, ATM PVC, Ethernet interface or VLANport).
The Physical line ID syntax is configurable. The Physical line ID syntax is a
concatenation of keywords, separators, and free text strings:
• for ATM-based DSL interfaces, the default value is “Access_Node_ID atm
Rack/Frame/Slot/Port:VPI.VCI”
• for EFM-based DSL and for Ethernet interfaces, the default value is
“Access_Node_ID eth Rack/Frame/Slot/Port”
You can use the following predefined keywords:

• Access_Node_ID: identifies the ISAM. The ISAM will insert the identifier that
is configured as “System ID”
• Rack: rack number in the access node
• Frame: shelf number in the rack. The variable is called 'Frame' to be inline with
TR-101.
• Slot: slot number in the shelf.
• Port: port number on the LT. On DSL or point-to-point LT boards, the “port”
stands for an end-user DSL/fiber interface
• VPI: VPI on user interface in case of ATM over DSL
• VCI: VCI on user interface in case of ATM over DSL
• Q-VID: VLAN ID on user interface (when applicable)
• N-VID: refers to the C-VLAN ID at the network-side, which may be different
from the user-side “Q-VID”
• U-VID: VLAN ID on user interface in case of tagged frames and nothing inserted
as VLAN id in case of untagged frames. The special character / delimiter in front
of this keyword in case of untagged frames is not inserted.
• DUVID: same as U-VID, but in this case the special character / delimiter in front
of this keyword incase of untagged frames is inserted.
• LzQVID: VLAN ID on user interface with 4 digits and leading zeroes (for
example, VLAN ID 1 denoted as 0001, VLAN ID 10 denoted as 0010, VLAN ID
100 denoted as 0100 and VLAN ID 1000 denoted as 1000).
• I-VID: Refers to the second or inner VLAN-id in dual-tagged Ethernet frames.
Note — <ShSlt> and <ShPrt> keywords can also be used instead of

respectively <slot> and <port>. The keywords <ShSlt> and <ShPrt>
can be used to specify the slot and port number without leading zero.
This gives an alternative for the <Slot> and <Port> keywords as
defined above and provides full flexibility as to the wanted/required
syntax.
Bandwidth information
DSLF TR-101 defines additional sub-options on top of those defined in IETF RFC
3046, such as a set of sub-options to pass DSL line bandwidth characteristics.
You can also enable or disable the insertion of the line rate characteristics per VLAN
in iBridge or VLAN cross-connect mode.
The ISAM can be configured to either add only the actual line rate information in
DHCP option 82, or to add the full set of access line parameters defined in TR-101.
For example, this includes the minimum, maximum, attainable and actual line rates
and interleaving delays.
This functionality is supported on the DSL and Ethernet LT boards.
(Layer 3) DHCP Relay Agent

This is further described in chapter “Protocol handling in a Layer 3 forwarding
model”, section “DHCP relay agent”.
DHCP snooping
If secure forwarding in Enhanced iBridge respectively in VLAN cross-connect is
configured, DHCP messages are snooped in order to learn the IP address associated
with the end user.
More information on DHCP snooping can be found in chapter “Protocol handling in
a Layer 3 forwarding model”.
10.9 IGMP
For more information about IGMP, see chapter “Multicast and IGMP”.
10.10 PPPoE
Point-to-Point Protocol over Ethernet (PPPoE) is a network protocol for

encapsulating Point-to-Point Protocol (PPP) frames inside Ethernet frames. PPP is
the commonly used protocol in dialup connections. PPPoE allows to connect one or
multiple PPP Client computer subscribers through an Ethernet LAN to a PPP Server.
PPPoE is defined in IETF RFC 2516.
PPPoE relay
In many cases the Layer 2 (Ethernet) Access network extends Ethernet into the home
network. A CPE in the home network terminates the DSL link or Ethernet interface
that provides the connectivity with the Access Network. One possibility is that the
CPE is a router. Then this router CPE will be the single PPP Client establishing
PPPoE sessions. Another possibility is that a bridge CPE transparently bridges the
request coming from a device deeper in the home network. Something in between
can be that a CPE multiplexes PPPoE sessions coming from multiple devices deeper
in the home network.
All these cases have in common that PPPoE frames are sent from the user equipment,
through the ISAM, to a BRAS more centrally in the network. DSLF TR-101
specifies that in such case the DSLAM has to add some subscriber information to the
upstream discovery messages, that is, to the PADI, PADR and upstream PADT
packets.
So for PPPoE relay, the ISAM inserts a PPPoE Relay tag in all the upstream PPPoE
messages in the discovery phase (that is, frames with EtherType = 0x8863). This
information insertion is the only intervention of the ISAM on PPPoE frames in the
upstream direction. This means that all PPPoE messages forwarded to the BRAS will
still contain the MAC address of the subscriber as source MAC address (MAC SA)
and the broadcast MAC (PADI) or the MAC address of the PPPoE Server (PADR,
PADT) as destination MAC address (MAC DA).
The ISAM does not make an intervention in the downstream direction.
All PPPoE messages in the session phase are forwarded without any processing.
Note — PPPoE Relay is only supported on the GE Ethernet LT board

UNI port type.
Figure 10-8 PPPoE relay

PPPoE traffic
LIM xHub Ethernet ER
PPPoE traffic
CPE
LIM NT
CPE
US/DS: PPPoE session

setup frames US: add PPPoE relay session ID, and forward
DS: forward
PPPoE relay tag

The “PPPoE Relay tag” is in fact a confusing name. It refers to the “PPPoE vendor
specific tag” that can be inserted by the ISAM in order to provide access loop
identification data towards the PPPoE Server (typically a BRAS).
The access loop identification conveyed by the PPPoE vendor specific tag is similar
as conveyed by DHCP option 82. Its format is defined in BBF TR-101. As for DHCP
option 82, the tag contains the identification of the access loop on which the PADI,
PADR, or PADT packet was received in the ISAM and possibly the line rate
information about this loop.
The insertion of the PPPoE vendor specific tag and the sub-options to be added are
configurable per VLAN.
The ISAM can be configured to either add only the actual line rate information in
PPPoE discovery messages, or to add the full set of access line parameters defined
in TR-101, such as the minimum, maximum, attainable and actual line rates and
interleaving delays. This functionality is supported for the DSL and Ethernet LT
boards.
PPPoA to PPPoE interworking

In some cases the Layer 2 (Ethernet) Access network does not extend Ethernet into
the home network. In some situations the home network is connected to the Access
Network with a traditional PPP over ATM over DSL interface. Because the
remainder of the Access Network is using Ethernet at the physical layer, it becomes
the responsibility of the ISAM to provide an interworking function between both
technologies. This interworking function is also specified in BBF TR-101.
Figure 10-9 Network topology

PPPoA - PPPoE Interworking
ATM
termination
IP Edge
USB Local Loop ISP
USB Modem EMAN

Ethernet
IP Srv: Video
Bridge
I
IP
Routing
NE Srv: VoIP
Gateway
L2TP
PPP-L2TP
interworking
In case of PPPoA to PPPoE interworking, the PPP forwarder is a further

enhancement of the iBridge. The PPP forwarder is still essentially a Layer 2
forwarding model, but it also uses information from the PPP layer in its forwarding
decisions.
PPPoA packets on the DSL line are translated into PPPoE on the uplink as follows:
1 When a subscriber initiates a PPPoA session, the ISAM first initiates a PPPoE
session toward the BRAS. The involved PAD-x messages are sent with a VLAN
tag with priority 7.
2 Once the PPPoE session is established, the initial PPP (LCP) request from the
subscriber is forwarded within that PPPoE session.
3 The remainder of the PPP negotiation happens between the subscriber terminal
and the BRAS.
The initial PPP request packet and all further packets sent within the established
PPPoE session are sent with a VLAN tag with the priority configured for the PPP
client port.
During the session, every upstream PPP packet is encapsulated in PPPoE, where the
MAC address of the ISAM is used as MAC source address. Downstream, the reverse
operation takes place and the MAC layer is stripped. From a BRAS perspective, the
session looks like any normal standard PPPoE session.
To give the Access Service Provider (ASP) the maximum information that can help
him to accept a PPPoE session establishment or to silently ignore the request, the
ISAM provides the PPPoE Server with access loop identification and line rate
information just as for PPPoE Relay. The difference is that in this case these
messages are generated by the ISAM.
Beside all these similarities there is still something special:
The ISAM can inform the PPPoE Server that the PPPoE session being established is
an “interworked session, that is, a session established on behalf of a user. This could
be useful for the BRAS. For example, to use a different a approach for limiting the
number of sessions per client. This information is provided through the insertion of
the BBF-IWF-tag sub-option in the PPPoE vendor specific tag. This sub-option is
defined in BBF TR-101.
Adding this sub-option can be enabled or disabled per PPP cross-connect Engine.
A second special thing relates to the Maxim Transmit Unit (MTU). In this scenario
the PPP Client is a PPPoA user and it assumes it can send PPP packets of 1500 bytes.
To encapsulate these frames in Ethernet, the interworking function shall add 8 bytes
of PPPoE header and as such the frame does no longer fit in a standard Ethernet
frame with a maximum payload of 1500 bytes. The normal procedure then requires
the PPP Client and the PPP Server to negotiate about the MTU. To facilitate the
convergence of this negotiation, the ISAM supports Ethernet frames that are 8 bytes
longer then standard Ethernet. This facility is signaled in the PADI message to the
PPPoE Server by adding the PPP-Maximum-Payload tag. This tag is defined in IETF
RFC 4638.
Adding this tag can be enabled or disabled per PPP cross-connect Engine.
Also for the release phase the ISAM cannot restrict to passively forwarding frames.
When the PPP session is terminated, the ISAM also terminates the corresponding
PPPoE session. The involved PAD-T message is sent with a VLAN tag with priority
7.
Normally, when a DSL line has gone out of service, the PPPoE session will only
time-out in the BRAS after a certain time (typically 3 minutes). This delay is
considered too long, for example, by service providers that offer a PPP-based HSI
service with time-based billing.
Therefore, the ISAM removes an interworked PPPoE session and sends a PPPoE
PAD-T message to the BRAS upon a loss-of-connectivity to the subscriber (this can
be indicated by loss of DSL synchronization on the associated subscriber line).
Note — PPPoA to PPPoE interworking is not supported on the GE

Ethernet LT board. It is also not supported on DSL LTs in Stacked
iBridge model.
PPPoE relay with MAC address concentration

In theory, if the CPE terminates the PPPoE protocol, there should not be any issue to
install an end-to-end connectivity between such a CPE and a BRAS located into the
Ethernet network. PPPoE frames contain enough routing information (that is, MAC
addresses) to reach the BRAS across the EMAN using standard bridging.
However, many legacy Ethernet switches cannot cope with the large number of
MAC addresses required to route PPPoE frames to the large number of DSL
subscribers connected to the EMAN through the ISAMs (at least 1 MAC address per
DSL subscriber).
This scalability issue is solved by the PPPoE relay with MAC address concentration
feature: the ISAM replaces the large number of MAC addresses, issued by the
subscribers, with the ISAM MAC address(es). The EMAN now only needs to cope
with a few MAC addresses per connected ISAM instead of tens of thousands of
MAC addresses for all connected subscribers.
Next to solving the scalability issue, the PPPoE relay with MAC address
concentration also increases the security within the network. The MAC address of
the subscriber does not enter the EMAN anymore. This address is replaced by the
own MAC address(es) of the ISAM and, consequently, all issues related to duplicate
subscriber MAC addresses are solved. The subscriber MAC address has only a local
meaning (that is, local to the PVC) and, consequently, even if all the subscribers
would present the same MAC address to the ISAM, they could still be connected to
the BRAS without any problem.
Spoofing the MAC address of another subscriber will not allow to grab its traffic
because the subscriber MAC address is not used by the EMAN nor by the ISAM to
route the traffic.
MAC address concentration can be enabled or disabled per PPP cross-connect
Engine.
Note 1 — PPPoE relay with MAC address concentration is not
supported on the GE Ethernet LT board NNI port type.
Note 2 — PPPoE relay with MAC address concentration is not
supported on DSL LTs for Stacked iBridge model.
If enabled the ISAM behaves very much like in the PPPoA to PPPoE interworking
scenario with the difference that the interworking applies to multiple PPPoE sessions
coming from users instead of to PPPoA sessions.
10.11 DHCPv6
Lightweight DHCPv6 Relay Agent

The ISAM can be configured to act as a Lightweight DHCPv6 Relay Agent (LDRA).
In this configuration, the Edge Router deeper in the network will act as a DHCPv6
Relay Agent.
The DHCPv6 packet headers will be created in accordance with
draft-ietf-dhc-dhcpv6-ldra. The DHCPv6 packet received from the user is copied in
the Relay-Message option of the relayed DHCPv6 packet.
The Access Node is able to encode the access loop identification in the Interface-ID
Option (option 18, defined in RFC 3315) to the DHCPv6 Relay-forward messages
sent to the BNG.
The encoding must uniquely identify the Access Node and the access loop logical
port on the Access Node on which the DHCPv6 message was received. The
Interface-ID contains a locally administered ASCII string generated by the Access
Node, representing the corresponding access loop logical port.
The actual syntax of the access loop identification in the Interface-ID can take the
same values as the ones supported for the DHCP option 82 sub-option 1:
• No Circuit ID (empty)
• Syntax defined in TR-101 section 3.9.3, that is, physical line ID using a default
or a configured syntax at system level
• Customer-ID
• Physical line ID in CCSA format
This allows the operator to migrate to IPv6 in a VLAN cross-connect model, without
losing access line information.
The Access Node is also able to add the Relay Agent Remote-ID Option (option 37,
defined in RFC 4649) to the DHCPv6 Relay-forward messages sent to the BNG. This
is used in order to further refine the access loop logical port identification.
The Relay Agent Remote-ID contains an operator-configured string of 63 characters
maximum that (at least) uniquely identifies the user on the associated access loop on
the Access Node on which the DHCPv6 Solicit message was received.
The actual syntax of the user identification in the Relay Agent Remote-ID can take
the same values as the ones supported for the DHCP option 82 sub-option 2:
• No Remote ID (empty)
• Customer-ID
• Physical line ID (using a default or a configured syntax at system level)
In the ISAM implementation the LDRA is enabled when either option 18 insertion
or option 37 insertion is enabled, and LDRA is disabled when both option 18
insertion and option 37 insertion are disabled. The operator can enable/disable the
insertion of option 37 into upstream DHCPv6 messages for each lightweight
DHCPv6 Relay Agent instance.
Bandwidth information
The Lightweight DHCPv6 Relay Agent supports the insertion of the
"Vendor-specific Information" Option (option 17) as defined in RFC 3315 in order
to add information about access loop characteristics. This is similar to the DHCP
behavior specified for IPv4 (see section “Bandwidth information”). The ISAM can
be configured to add the full set of access line parameters in DHCPv6 option 17, as
defined in TR-101. This includes among others the minimum, maximum, attainable
and actual line rates and interleaving delays.
This functionality is supported for the DSL and Ethernet LT boards, except the
72-port ADSL2+ linecards.
DHCPv6 trusted/untrusted port configuration

The interface (VLAN) where the LDRA is enabled, can be configured as trusted or
untrusted interface.
When the interface is configured as trusted, then the LDRA accepts DHCPv6
Relay-Forward messages from user side with options 18 and/or 37 already inserted.
The ISAM will relay these Relay-Forward messages in accordance with
draft-ietf-dhc-dhcpv6-ldra. In that case hop count is incremented in the upstream and
is decremented in the downstream.
When the interface is configured as untrusted, then Relay-Forward messages from
user side will be discarded and not relayed.
DHCPv6 Relay Agent

See chapter “Protocol handling in a Layer 3 forwarding model”, section “DHCPv6
Relay Agent”.
DHCPv6 snooping
See chapter “Protocol handling in a Layer 3 forwarding model”.
10.12 ICMPv6
ICMPv6 includes Neighbour Discovery (ND) messages as well as Multicast Listener

Discovery (MLD) messages. In general, upstream and downstream ICMPv6
messages are handled transparently without specific processing. This means that
downstream multicast ICMPv6 messages are typically flooded by default.
The filtering of ICMPv6 unicast and multicast ICMPv6 packets in an iBridge or
VLAN cross-connect forwarder can be enabled or disabled. This allows finetuning
of the ICMPv6 message handling for security purposes.
When enabled, the following ND and MLD messages must be discarded:
• Downstream multicast Neighbor Solicitation (NS) (downstream unicast NS
messages should be handled according to normal MAC-based forwarding rules)
• Downstream Router Solicitation (RS)
• Upstream Router Advertisement
• Upstream Redirect
• Upstream MLD Multicast Listener Queries

• Downstream Multicast Listener Done (MLDv1)
• Downstream Multicast Listener Report (MLDv1 and MLDv2)
When using MAC address translation or virtual MAC addresses, the MAC address
field present in the ICMPv6 Neighbor Discovery message payload must be
translated. See section “Virtual MAC” for more information on virtual MAC
addresses.
11 — IP routing
11.2 IP routing features 11-2
11.3 IP routing model 11-6
11.4 Routing in case of subtended ISAMs 11-7
11 — IP routing
11.1 Introduction
The IP routing model of the ISAM is a typical router implementation with increased
security and scalability, allowing to use cheaper devices (that is, simple Ethernet
switches) in the aggregation network. It can be characterized as follows:
• Packets are forwarded based on the IP Destination Address (DA) with the ISAM
acting as a next hop.
• IP connectivity towards the end user can be established statically by the operator
or learned dynamically by inspecting the DHCP messages exchanged between
the subscriber and the DHCP server during the IP session establishment.
• IP connectivity towards the network and the subtending nodes can be established
statically by the operator or dynamically by routing protocols.
• Service Level Agreement (SLA) enforcement can be achieved by means of
policing and an Active Control List (ACL), and this at various granularity levels.
• Improved security:
• Subscriber MAC addresses are never propagated to the network (inherent IP
routing)
• ARP messages do not cross the ISAM leading to not broadcasting ARP messages to
all subscribers
• IP address anti-spoofing and ACL
• Improved scalability
• The ISAM presents a single MAC address towards the network
• The broadcast message load generated by the subscribers towards the network is
reduced by either handling them locally (for example, ARP) or by converting them
into unicast messages (for example, L3 DHCP relay).
11.2 IP routing features
Packet forwarding based on the IP addresses

Implementing a forwarding based on IP addresses allows to:
• terminate the Ethernet segment at the subscriber side and consequently, avoid the
need to propagate the MAC address of the subscriber to the network solving at
the same time many security and scalability issues.
• forward packets based on addresses assigned by the operator, enforcing a high
security level.
• introduce IP awareness in the DSLAM, which facilitates support of enhanced
features such as IP address anti-spoofing, ACLs and so on.
Next hop behavior

The ISAM is seen as a next hop by the network and the subscribers, which allows
increased scalability. Indeed, the IP edge router does not have to know each
subscriber individually (which results in a reduced ARP table size) and ARP
messages issued by the subscribers are terminated by the ISAM, reducing the control
plane load at the IP edge.
11 — IP routing
Subscriber interface - Encapsulation types
• The IP routing model supports all types of subscriber interface IPoX

encapsulations, which can be connected to an iBridge on the LT:
• ATM subscriber interface (IPoE over ATM and IP over ATM)
• EFM/Ethernet subscriber interface (IPoE)
• IPoE subscriber interface:
• User interface can be authenticated through 802.1/RADIUS protocols before
connecting to a router in ISAM.
• vMAC can be enabled when subscribers do not have unique MAC address
• PPPoE and PPPoA subscriber interface encapsulations are not supported by IP
routing.
802.1x/RADIUS authentication
Subscriber interfaces (IPoE over ATM or EFM/Ethernet) can be authenticated
through 802.1/RADIUS protocols before connecting to a router in ISAM.
Subscriber interface - Unnumbered

In order to make the subscriber addressing scalable, subscriber interfaces (on the
DSL lines) are considered as unnumbered IP interfaces attached to the IP router. That
is, there is no need to allocate an IP address (note that this is only from the logical
point of view and no need to explicitly configure unnumbered IP interface on the
subscriber lines). This allows to share a subnet across many subscribers and,
consequently, to increase the scalability and ease of operations.
DHCPv4 relay agent

DHCP messages from the subscribers are forwarded through a layer 3 DHCP relay
instance. This allows to:
• Convert broadcast messages into unicast messages towards a set of predefined
DHCP servers to reduce the broadcast traffic load in the network.
• Add option 82 to uniquely identify the requesting subscriber by inserting the
identification of his DSL line into the DHCP messages.
Subscriber routes - Dynamically learned through DHCP snooping

For a router in general, interfaces are usually configured statically (by the operator),
and the routes are learned dynamically via routing protocols. This is not typical for
the subscriber side in ISAM because the devices of the subscriber do not typically
support routing protocols and secondly the amount of subscribers to be configured in
a DSLAM is high. The better method for ISAM is to learn the IP addresses by
snooping DHCP messages.
11 — IP routing
The ISAM can automatically manage the forwarding parameters associated with the
interfaces of the subscribers by snooping the DHCP messages exchanged with these
subscribers (populate the snooped IP address of the subscriber, remove that IP
address once the snooped IP address lease time is elapsed). This basically reduces the
operator's cost of operation since the connectivity establishment is performed
dynamically at IP session set-up time without any involvement of the operator.
However, an operator may still configure subscribers statically if desired (for
example, business users). Static configuration is required whenever a subnet needs
to be assigned to a subscriber, while ISAM only supports dynamic subscriber's IP
address allocation for an individual IP address.
Network routes - Dynamically learned through routing protocol

Network routes can be learned dynamically through routing protocols, hence
reducing the cost of operation: connectivity to the network is automatically
established by means of IP routing protocols. Additionally, routing protocols can
also be used to increase the network reliability by advertising alternative routes
whenever a failure occurs in the network (for example, dual homing from the ISAM
to two different routers).
The operator can also configure static routes to the network if desired.
Routes advertised to network and subscribers

IPv4 network routes can be advertised to the subscribers using RIP.
IPv4 subscriber routes (individual or aggregated routes) can be advertised to the
network using RIP or other routing protocols. This reduces the provisioning
workload at the network side, at the CPE side, or both.
User-to-user communication
User-to-user communication can be enabled or disabled at the VRF level. When
disabled, user-to-user traffic will be discarded. When enabled, local ARP proxy also
needs to be enabled on the user gateway IP interface.
IPv4 option processing

ISAM supports the processing of following IP options:
• Router alert
• Time stamp
• Record route
ISAM does not process source route option, that is, IP packets including source route
options are discarded.
TTL=0 forwarding
Standard IP routers are expected to discard packets received with TTL=0 and not
intended for one of the router interface IP addresses. However, some specific
network configurations require the ISAM to forward such packets.
11 — IP routing
TTL=0 forwarding is disabled by default. This option is configurable. This mode is

only supported for IPv4.
MTU
The L2 MTU size is fixed to 2048 and not configurable.
Implementation notes:
• The ISAM does not perform IP packet fragmentation for forwarded packets
(packets generated by the ISAM itself are subject to fragmentation)
• Packets received with a length larger than the MTU are discarded.
ECMP
Up to 4 Equal Cost Multi Path (ECMP) next-hops are supported per route.
Directed broadcast
ISAM does not support forwarding of the broadcast IP packets directed to the
directly connected subscriber subnets (where subnet is all zeros or all ones). Directed
broadcast IP packets are discarded by ISAM.
ICMP redirect
ISAM does not support ICMP redirect.
11 — IP routing
11.3 IP routing model
The IP routing model of the ISAM consists of iBridge forwarders (with secure
forwarding enabled) on the LT boards connected to a standard IP forwarder on the
NT board.
Figure 11-1 shows the IP routing model based on iBridge.
Figure 11-1 IP routing model based on iBridge

Users ca n belong to a
different public subnet.
User C E LT ISAM
DHCP snooping/ ARP
User C E Sta tic config. relay
I-bridge
V-VLAN per VRF
User C E
User C E LT NT
DHCP snooping/ ARP Routing
User relay DHCP Rela y ARP
C E Sta tic config. protocols Agent
EMAN IP
User C E I-bridge VRF IP Ed g e N e two r k
User C E LT
DHCP snooping/ ARP User ga tewa y IP interfa ce
User C E Sta tic config. relay
on the V-VLAN
User I-bridge
C E
iBridge forwarders on the LT boards offer the following security features:

• IP address anti-spoofing (data-plane)
• ARP relay: ARP messages from the NT board are forwarded to the targeted
subscribers, not broadcast to everyone
• layer 2 DHCP relay (adding option-82)
• DHCP snooping: the subscriber IP address is learned through DHCP, which
allows to configure the ARP relay and IP address anti-spoofing
• 802.1x/RADIUS authentication
IP router on the NT board offers the following functions:
• IP forwarding (data-plane), only one Virtual Forwarding and Routing (VRF)
instance is supported
• ARP to network and to subscribers on the LT boards
• User-to-user communication at layer 3 (including local ARP proxy)
• IP option processing
• Programmable TTL=0 forwarding
• Layer 3 DHCP relay
• Routing protocols (OSPF, RIP)
11 — IP routing
An internal VLAN is established between the LT boards and the NT board acting as
an IP router. There is typically one v-VLAN per VRF instance. Multiple v-VLANs
for a single VRF can be considered whenever a given VRF is forwarding multiple
services and the services are associated with either a different PVC or a different
VLAN at the subscriber interface.
Note — The ISAM supports only one VRF (IP routing) instance.
The user gateway interface is the IP interface, which is facing the subscribers, and
which is created on top of the V-VLAN. The subnet of the subscriber gateway
interface is shared among the subscribers connected to the iBridge instance identified
by the V-VLAN on the LT boards. The IP address of the subscriber gateway interface
is used as the gateway IP address for the subscribers directly attached to the subnet
of the subscriber gateway interface.
Multi-netting is also supported for the subscriber gateway interface to allow multiple
subscriber subnets.
11.4 Routing in case of subtended ISAMs
When grooming traffic from multiple subtended ISAMs into a Hub ISAM, the ISAM
supports two approaches:
• Subtended nodes operating as Layer 2 devices (Preferred)
• Subtended nodes operating as L3 devices
Subtended nodes operating as Layer 2 devices (Preferred)

In this node, IP routing and L3 DHCP relay are kept centralized on the Hub ISAM
(H-ISAM) so that remote nodes - subtended ISAM or S-ISAM - can be kept as
simple as possible (both from a hardware implementation and from a provisioning
point of view). This allows centralizing routing protocols and subnet management at
the H-ISAM while keeping the S-ISAMs untouched, that is, any addition of a new
pool of IP addresses will only impact the H-ISAM.
The potential drawbacks of this configuration are related to H-ISAM scalability:
• larger Forwarding Database and ARP tables
• higher processing load.
This configuration is shown in Figure 11-2. In the hub ISAM, the router function is
configured while in the S-ISAMs layer 2 forwarding is in place.
11 — IP routing
Figure 11-2 ISAM sub-network configuration for video traffic (e.g VDSL)
Seen by the operator as
one big virtual router
ONT
RG
R
Aggregation
Network
DHCP
Relay
L2
One single IP subnet

over all Hub + Sub ISAMs
Hub ISAM
LT NT
EiB R
LT NT
Identical LT configuration
EiB B in Hub and Sub ISAMs
Sub ISAM
EiB: Enhanced iBridge
EiB: Enhanced -Bridge
Subtended nodes operating as L3 devices

All nodes operate as IP routers, allowing the operator to define a similar
configuration for all nodes. The approach leads to inefficient IP subnet usage.
The S-ISAM forwards upstream traffic to the H-ISAM via the default route
announced from the H-ISAM.
Figure 11-3 provides a network view. The assumption is that RIP is used to distribute
routes towards the subscribers. The red dots indicate where an IP interface is
configured.
11 — IP routing
Figure 11-3 Subtended ISAM operating as a L3 device
IGP
L3
IGP
Aggregation
L3 Network
IGP
L3
11 — IP routing
12 — Protocol handling in a Layer 3
forwarding model
12.2 IPv4 Routing Protocols 12-2
12.3 ARP 12-3
12.4 DHCP relay agent 12-4
12.5 DHCP snooping 12-7
12.1 Introduction
This section addresses layer 3 protocols in the scope of a layer 3 forwarded model as
described in chapter “IP routing”.
Layer 3 protocols can be divided into two parts:
• routing protocols: see section “IPv4 Routing Protocols”
• user access protocols:
• ARP: see section “ARP”
• DHCP Relay: see section “DHCP relay agent”
• DHCP snooping: see section “DHCP snooping”
12.2 IPv4 Routing Protocols
Introduction
The supported routing protocols are:
• RIP
• OSPF-v2
These routing protocols are supported on network interfaces and interfaces towards
a subtended ISAM. In addition, the RIP protocol can be supported on subscriber
interfaces to advertise the routes towards the routers at the network side of the ISAM.
The ISAM does not accept any route advertisement from the subscribers for security
reasons.
The ISAM will report alarms to inform the Manager about lack of resources, major
issues and state transitions in the protocol.
RIP
The Routing Information Protocol (RIP) is a distance vector protocol. It calculates
the shortest distance, and therefore the most desirable path, between source and
destination addresses, all based on the lowest hop count.
The ISAM supports:
• RFC 1812 defined for IPv4 routers for handling IP packets that are forwarded and
destined to the system
• RFC 2453 defined for RIPv2 protocol
• RFC 1058 defined for RIPv1 protocol
• RFC 2082 defined for RIPv2 MD5 authentication
RIPv1 compatibility
The ISAM is compatible with RIPv1 and RIPv2 versions of the RIP protocol. It
supports the configuration of the version of the RIP PDUs that are transmitted and
received by the RIP router in the ISAM.
OSPF-v2
Open Shortest Path First (OSPF) is a dynamic routing protocol used to learn and
populate the forwarding database in the DSLAMs and the edge devices at the
network side.
The ISAM complies with the following standards:
• RFC 1812 defined for IPv4 routers for handling IP packets that are forwarded and
destined to the system.
• RFC 2328 defined for OSPF-2 protocol.
• RFC 3101 defined for OSPF to support the Not-So-Stubby Area (NSSA) option.
The NSSA option is used by deployments to reduce the size of the LSA database.
There is no external route imported into an NSSA area from other OSPF areas. In an
NSSA, external routes learned by OSPF routers in the NSSA area are advertised
within the NSSA area and are translated by ABRs into external route advertisements
for distribution into other areas of the OSPF domain.
• RFC 1765 for OSPF database overflow in case of conditions when the system
receives updates from the neighbors that exceed the available database limit.
• RFC 2370 for OSPF opaque LSA option.
Area support
The ISAM supports areas, as defined in RFC 2328, for OSPF-2 protocol. The OSPF
router on the ISAM can associate interfaces with the backbone area, a normal area,
a stub area, or an NSSA area.
12.3 ARP
The IETF RFC 826 defined Address Resolution Protocol (ARP) is a protocol defined
within the context of using IP over Ethernet. An IP node uses the ARP protocol to
obtain the Ethernet MAC address of another IP node identified by a known IP
address and connected to the same Layer 2 network.
This section describes ARP handling in ISAM in case of an IP routing model.
Note — For more information on ARP relay; see section “ARP

relay”.
ARP handling on the subscriber side
• ARP request from users, for another user in the same subnet:
The ISAM acts as an ARP proxy for local user subnet IP addresses.
When the ISAM receives an ARP request for another user in the same subnet, the
ISAM sends an ARP response. However the request will be discarded for these
exception cases:
• IP address anti-spoofing verification reveals that the user is not known: the source
IP address is not known to belong to the incoming interface
• both users are connected to the same user interface: subscribers should
communicate by way of the internal interface at the subscriber side.
• ARP request from users, for user gateway IP address;
When the ISAM receives an ARP request for the user gateway IP address, the
ISAM will send an ARP response when the IP anti-spoofing verification is
successful.
• ARP initiated by the ISAM to resolve a user MAC:
An ARP request for a user IP address is not broadcast to all users attached to the
same gateway IP interface. It is relayed to the user interface where the target user
is learned.
ARP responses from the user are validated with respect to IP address
anti-spoofing.
ARP protocol tracing can be enabled on a few subscriber interfaces. The system can
provide the list of messages exchanged with the subscriber to the ISAM syslog utility
that will determine the destination of the traces (that is, CLI screen, remote server,
local file)
ARP handling on the network side

Standard ARP Handling applies at the network side:
• for ARP requests received from the network.
• for ARP requests ISAM sends to the network.
12.4 DHCP relay agent
DHCP is a subscriber access protocol that enables DHCP servers to configure

internet hosts. The ISAM provides DHCP relay agent functionality for IPoE/IPoA
subscriber access interfaces in the IP routing mode.
The DHCP relay agent functionality is composed of two main components:
• layer 2 DHCP relay agent
• layer 3 DHCP relay agent
Layer 2 DHCP relay agent

The functionality is equal to the functionality of the DHCP Relay Agent as described
in chapter “Protocol handling in a Layer 2 forwarding model”.
DHCP protocol tracing can be enabled on a few subscriber interfaces. The system
can provide the following to the ISAM syslog utility that will determine the
destination of the traces (that is, CLI screen, remote server, local file):
• the stable states and/or exceptional events related with DHCP handling
• the list of messages exchanged with the subscriber
Layer 3 DHCP relay agent
Basic functionality
The ISAM can act as layer 3 DHCP relay agent for the subscribers in the following
forwarding modes:
• IP routing
• iBridge
Note — The functionality is also provided in case of iBridge

forwarding mode, though such configuration is not recommended and
is planned to be phased out.
The layer 3 DHCP relay agent is responsible to relay DHCP messages between the
subscribers and DHCP servers as follows:
• Upstream:
Broadcast DHCP messages received from the subscribers are unicast to the
configured DHCP servers of the VR (of an IP router) associated with the interface
of the subscriber.
Note — The L3 DHCP relay agent only relays broadcast packets to
the configured servers. The L3 DHCP Relay agent never forwards or
relays unicast DHCP packets from subscribers to servers.
• Downstream:
Unicast DHCP messages received from the DHCP servers are either unicast or
broadcast (based on the broadcast flag) to the correct subscriber interfaces.
Subscribers connected to the same interface may get IP addresses in the same subnet
or from different subnets. User-to-user communication between those subscribers
would be via the ISAM (in the IP routing mode) and via the IP edge router (in the
iBridge mode), even though there is a direct connectivity between them.
Note — The layer 2 DHCP relay agent is located at the LT board and
the layer 3 DHCP relay agent is located at the SHub.
Multiple DHCP relay instances per VRF

Multiple instances of a layer 3 DHCP relay per VRF are supported in case of the IP
routing model. The DHCP Relay Agents are located on the NT.
When multiple services are offered via the same VRF while each service uses a
dedicated IP address range managed by a different set of DHCP servers, the operator
can enable multiple layer 3 DHCP relay instances per router, and dedicate the usage
of each instance to one service. This approach avoids overloading DHCP servers
(with a given service) with DHCP messages that are not relevant for that service.
A layer 3 DHCP relay instance is characterized by:
• VRF ID
• Relay agent IP address
• List of DHCP servers to be addressed
When receiving a DHCP message from a user and which must be handled by a layer
3 DHCP relay agent, the incoming IP interface (or VLAN where the DHCP message
came in) is used to select one of the relay agent instances configured within the VRF.
Thus, the ISAM will only relay the DHCP message to those DHCP servers which are
associated with the selected DHCP relay instance.
This is shown in Figure 12-1.
Figure 12-1 Multiple DHCP relay instances per VRF
LT L2-enhanced
forwarder A
IPa1
User L2 DHCP NT
Subs 1 Relay A v-
IPb1
VL
User A
N DHCP
A
L2-enhanced server
forwarder B IP a,b
L3 DHCP IP x
IPc1 Relay Agent A
User Subs 2 L2 DHCP
Relay B
ISP DHCP
server
LT L2-enhanced IP c,d
L3 DHCP
IPa2 forwarder A
User Relay Agent B IP y
B
AN
IPb2 L2 DHCP
User Subs 3 Relay A
VL
v-
IPc2
User L2-enhanced
Notation:
forwarder B
IPd1 : is an IP interface
User Subs 4
L2 DHCP giaddr=any VRF IP address
Relay B Option 82 insertion,
session snooping
12.5 DHCP snooping
In the IP routing, iBridge model, the ISAM maintains the relation between the
subscriber IP addresses and the corresponding subscriber interfaces by snooping the
DHCP messages. The DHCP snooping is distributed and performed by every LT
board. There is no NT board involvement.
The LT board snoops the following information:
• the subscriber IP address:
required for IP anti-spoofing in the upstream direction (that is, an IP packet
received with a source IP address which is not learned from the incoming
subscriber interface is discarded).
• IP address lease:
The ISAM also monitors the IP address lease. The relation between the subscriber
IP address and the subscriber interface is removed when the lease time is expired.
In case the lease is infinite, the subscriber IP address can only be removed by a
manual operator action (by locking the subscriber interface or powering-off the
corresponding LT board).
As the NT board is not using data retrieved from the DHCP snooping (that is, no
dataplane configuration), DHCP sessions are by definition preserved against:
• an NT board reset or switchover due to a software or a hardware failure
• an NT board reset due to software upgrade
The ISAM supports counter that track the number of packets that have been dropped
per line because they contain a spoofed IPv4 source address. These counters can be
made available to an external management system for troubleshooting.
The DHCP sessions are stored in the reset-safe memory of the LT and NT boards and
are preserved against:
• an LT board reset due to recoverable or unrecoverable software failure leading or
not to the power-on reset
• an LT board reset due to software upgrade
• an LT board reset due to hardware failure
• an LT board replacement
In cases where the DHCP sessions could not be preserved (exceptional case of
combined NT and LT board failures, for example, during complete ISAM power
down), the subscribers will have to re-establish DHCP sessions in order to recover
the IP connectivity.
13 — Multicast and IGMP
13.1 Overview 13-2
13.2 Advanced capabilities 13-5
13.3 System decomposition 13-14
13.4 Multicast and forwarding models 13-14
13.1 Overview
Multicast is the simultaneous transmission from a single device (such as a video head
end) to a group of recipients (such as video Set Top Boxes) using the most efficient
strategy to deliver the data over each link of the network only once.
The ISAM supports IP Multicast based on VLAN bridging (layer 2) technology.
Internet Group Management Protocol (IGMP) is the control protocol for multicast in
a layer 2 network. It is used between the recipients (hosts) and multicast routers to
join and leave a group.
Note — IGMP is specified in IETF RFC 2236 (IGMPv2) and RFC

3376 (IGMPv3).
By default, bridges flood multicast frames as well as IGMP packets between the
multicast router and the hosts. This not only creates a security issues when end users
can see each other's IGMP messages, but also the resulting bandwidth waste is
unacceptable on relatively low bandwidth interfaces like xDSL. Bridges can
optimize the bandwidth usage by snooping the IGMP control packets exchanged
between hosts and multicast router. Efficient multicast trees are constructed from the
learned information. The ISAM supports IGMP proxy, which serves as an alternative
variant for IGMP snooping.
Note — IGMP snooping is specified in IETF RFC 4541.
Figure 13-1 IGMP enabled bridges
Member group A Host

Video
Head
Member group A end
Edge
Router
LAN
Bridge IP network
Bridged
Member group A VLAN
Member group B
data
IGMP
Member group B
Data plane
IP Multicasting uses IP datagrams with a multicast destination IP address, which is
a class D address in the range “224.0.0.0” through “239.255.255.255”.
In the layer 2 network between the hosts and the edge router, the IP datagrams are
encapsulated in Ethernet frames with a multicast destination MAC address that is
derived from the multicast destination IP address. Hosts should not only accept
frames with a destination MAC address matching their own MAC address, but also
frames with a multicast destination MAC address of the groups of which they are a
member.
Note — Remark that multiple (32) IP addresses map to the same

multicast IEEE 802 MAC address.
Bridges maintain multicast forwarding tables, also known as multicast Forwarding

Data Base (FDB), representing the replication trees.
The ISAM maintains a multicast forwarding table per VLAN. The entries are known
as multicast trees in the management plane. Multicast trees are indexed with the
multicast IP address, rather than with the multicast MAC address. This makes it easy
to correlate the data plane with the control plane (IGMP) which is based on IP
addresses.
Note — The use of IP addresses does not eliminate the issue of
many-to-1 mapping from IP addresses to MAC addresses, since there
are still components in ISAM that forward based on the MAC
address.
In Figure 13-2, the multicast forwarder is shown as segregated from the unicast
forwarder for the same VLAN. Multicasting is only supported in VLANs that have
IGMP enabled, so-called multicast VLANs.
Figure 13-2 Multicast data plane

DSL interfa ce Port P2
Unicast forwarding VLAN Port GE interface
iBridge
Multicast forwarding 224.0.10.2

Port P1
240.0.10.1
Multicast Fwd Ta ble

VLAN Multicast IP address Egress ports
15 240.010.1 { P1 }
15 240.010.2 { P1, P2 }
IGMP can only be enabled on network VLANs whose unicast forwarder is an

iBridge, but not a cross-connect VLAN.
If IGMP is not enabled, then the forwarder is either transparent for or discards IGMP
packets and multicast frames. Refer to Table 13-1.
Control plane
The ISAM supports an IGMP Proxy. Compared to an IGMP Snooper, an IGMP
Proxy maintains independent “Router” state machines towards the hosts and “Host”
state machines towards the routers. this offers some advantages, such as spreading
the load of queries towards subscribers.
The IGMP Proxy updates the mFIB tables dynamically, based on the control plane
events (join requests, leave requests).
Note — IGMP Proxy is defined in IETF RFC 4605.
Figure 13-3 IGMP control plane
IGMP
R Proxy H
upda te
join 240.0.10.1
join 240.0.10.2 Multica st Fwd
join 240.0.10.1
VLAN port
IGMP version 2 as well as IGMP version 3 are supported. The system can be
configured to only accept IGMPv3 and drop incoming IGMPv2 messages. IGMPv1
messages will always be dropped.
Multicast services are configured on subscriber ports by creating an IGMP channel
on top of the subscriber port. This enables IGMP proxy on the subscriber port.
By enabling IGMP on a network VLAN, that is, making it a multicast VLAN, IGMP
snooping is enabled on all network ports and subtending ports that are in that VLAN.
When IGMP is encapsulated over PPP, it is handled transparently
13.2 Advanced capabilities
The regular multicast mechanisms are suited to provide a very basic video service.
More advanced capabilities are available. Most of these capabilities require the
configuration of the list of IP addresses of the multicast channels that can be joined
by the ISAM subscribers. This is known as the list of preconfigured multicast
channels, or “premium” video channels.
Join requests received from the subscribers are identified as targeting a
preconfigured multicast channel by comparing the join (multicast IP address, source
IP address) against the list of preconfigured multicast channels identified as follows:
• Cross-VLAN multicast (see section “Cross-VLAN multicasting”): (multicast IP
address, source IP address)
• Fixed multicast VLAN per IGMP channel (see section “Fixed multicast VLAN
per IGMP channel”): (multicast IP address, source IP address, multicast VLAN)
Some of the advanced capabilities also apply to non-configured “best-effort” video

channels, that is, to IP addresses that are not configured in the ISAM.
Provisioning multicast channels can be simplified by manipulating “ranges of
channels”. A range of channels is characterised by a set of channels sharing the same
characteristics (source IP address, multicast VLAN (optional), bandwidth
parameters, …) and whose multicast IP address belongs to a given range.
Such a “channel range” can be manipulated as one management object by the
operator.
Static infeed
The availability and join latency of popular multicast channels can be improved by
feeding them statically up to the ISAM. The channel is semi-permanently streamed
in the aggregation network up to the ISAM uplink, whether hosts joined the channel
or not. There is no need for the edge router to react on IGMP requests to join this
channel.
Statically fed channels towards subtending nodes are configured in the ISAM by
configuring static multicast branches, as opposed to the dynamic multicast branches
created through IGMP signaling. By doing so, the root of the replication tree
becomes static. It is also possible to configure a list of static egress ports (branches)
on subtending ports or on network ports, so the channel is also statically fed up to the
next node.
Note — Statically fed channels still support dynamic branches,

controlled through IGMP signaling.
Figure 13-4 Static infeed
Subtending ISAM ISAM Aggregation network

No IGMP
necessary Edge
Router
No IGMP
necessary
IGMP static
Branch Root
dynamic
Cross-VLAN multicasting
Multicasting in an iBridge is normally contained within the same VLAN. As a
consequence multicast-enabled subscriber ports would need to be VLAN ports
within the multicast VLAN.
With cross-VLAN multicasting ALL the subscriber ports that are multicast-enabled
can receive multicast traffic from ALL the multicast VLANs. This makes it possible
to:
• mix multicast and other services at the subscriber ports, yet segregate these
services in the aggregation network in different VLANs.
• offer multicast services on subscriber ports of different iBridges, yet share the
multicast channels in a common VLAN. Cross-VLAN thus reduces the number
of copies of the same multicast channel.
• offer multicast services on subscriber ports that employ other forwarding modes
than iBridge, such as VLAN cross-connects. Without cross-VLAN multicasting,
multicast traffic would be discarded or would be transparent, implying no
efficient replication.
• organize multicast channels in multiple multicast VLANs, without limiting the
access possibilities of the subscriber.
Figure 13-5 Cross-VLAN multicast - forwarding view
240.0.10.2
Multicast VLAN
forwarding
(network-side)
SAP
Unicast forwarding VLAN

VLAN port (iBridge)
(network-side)
SAP
Unicast forwarding
VLAN
(VLAN-CC)
VLAN port (network-side)
SAP
In cross-VLAN multicasting, when the subscriber joins a channel, the ISAM finds
the multicast VLAN from the preconfigured multicast channel. If the requested
multicast IP address, possibly extended with source IP address - see “Source Specific
Multicasting”, is not in the list of multicast channels, then the join is handled in the
scope of the subscriber VLAN. In case the subscriber VLAN forwarder is an iBridge
(that is, multicasting is supported), the join is proxied as a “best-effort” video service.
Else, the join is transparently forwarded or is discarded, see Table 13-1.
Figure 13-6 Cross-VLAN multicast - network view
ISAM Aggregation network
STB Edge
router
Fwd BTV VLAN 15
BTV + VOD
Fwd VOD VLAN 16
Multicast
channel list
Multicast
VLAN
IP address
240.0.10.1 15
240.0.10.2 15
Source Specific Multicasting

The multicast IP address range is unique. In a wholesale environment, different
multicast service operators would need to make agreements to use non-overlapping
subranges.
Source Specific Multicasting (SSM) makes it possible for multicast service operators
to use overlapping multicast IP address ranges because SSM-mode multicast
channels are identified by the combination of the multicast IP address and a source
IP address, which refers to the multicast service provider. When configured in
IGMPv3, subscribers can join to SSM-mode channels and the ISAM can distinguish
the requests by means of the source IP address, even if the multicast IP address is the
same.
Even though subscribers can join based on the combination of multicast IP address
and source IP address, the multicast forwarding table of the ISAM (and possibly also
in the aggregation network) does not support the source IP address. That is, the data
plane is SSM-unaware. For this reason, the same multicast IP address can only be
reused in combination with a different VLAN. When receiving a join for an
SSM-mode channel, the ISAM finds the associated VLAN in the list of
preconfigured multicast channels.
SSM channels must therefore be preconfigured as multicast channels.
Note — The method to use SSM in the control plane but not in the
data plane of L2 networks is specified in DSLF TR-101.
Figure 13-7 Source Specific Multicasting
Aggregation network Video

ISAM
Head End
STB
Edge
(240.0.10.1,140.20.20.1) router
Fwd 140.20.20.1
BTV VLAN 15
(240.0.10.1,144.30.30.1)
Fwd
VOD VLAN 36
144.30.30.1
Multicast Multicast
Fws table channel list
Multicast Multicast Source
VLAN VLAN
IP address IP address IP address
240.0.10.1 15 240.0.10.1 140.20.20.1 15
240.0.10.1 36 240.0.10.1 144.30.30.1 36
Fixed multicast VLAN per IGMP channel

Using a fixed multicast VLAN per IGMP channel offers an alternative to SSM based
IPTV wholesale with following characteristics:
• ASM based deployment (IGMPv2 or IGMPv3 ASM) with overlapping group
address ranges across Video Service Providers:
This approach simplifies multicast address management within the access
network. Indeed, there is no need anymore for Video Service Providers to agree
upon non-overlapping multicast address sub-ranges when using IGMPv2 or
IGMPv3-ASM.
• SSM based deployment with overlapping source addresses across Video Service
Providers:
An example of such a configuration is a network where multiple Video Service
Providers distribute IPTV services from the same Video Content Provider
generating video traffic over IP, including its source IP address. Each Video
Service Provider wants to keep control on its own offering, leading to overlapping
IP source addresses in the network.
In order to support overlapping “Group Address” or “Source Address” across Video

Service Providers, the ISAM allows to assign a dedicated Video Service Provider
(that is, Multicast VLAN) per subscriber (that is, IGMP channel) so that the (S,G)
processing is instantiated per Video Service Provider, allowing full freedom.
This feature changes the algorithm for determining the multicast VLAN, as it was
explained in “Cross-VLAN multicasting”. With “fixed multicast VLAN per IGMP
channel”, the multicast VLAN, both for preconfigured and non-configured multicast
channels, is determined by the multicast VLAN configured per IGMP channel.
From R4.3.01 on:
This feature changes the algorithm for determining the multicast VLAN, as it was
explained in “Cross-VLAN multicasting”. With “fixed multicast VLAN per IGMP
channel”, the multicast VLAN for preconfigured multicast channels, is determined
by the per-IGMP channel configured multicast VLAN. The VLAN for
non-configured multicast channels remains the unicast VLAN as it is the case for the
cross-VLAN multicast model.
Figure 13-8 Fixed Multicast VLAN per IGMP channel

SP own (unique)
Access/ NNI Mcast groups
Aggregation
network
Mcast content provider
(for example, Free-To-Air TV)
Fwd
BTV S-VLAN 15
BTV + VOD SP #2
Fwd
BTV S-VLAN 16
Unicast (VOD, HSI, ...)

Fwd S-VLAN (+ C-VLANs) SP #1
Example:
(S,G)=(140.20.20.1,240.0.10.1) stream
will be requested by end-users over
SP own (unique) both BTV VLANs 15 and 16
Mcast groups
The “fixed Multicast VLAN per IGMP channel” mode is defined at system level and
cannot be used simultaneously with other modes where multiple Video Service
Providers can be selected by the subscribers by means of either the “Group Address”
(ASM) or the “Source Address” (SSM).
Fast leave
In the normal leave procedure of IGMP, when a host leaves a multicast channel, the
router queries the port for any other hosts that must still receive the multicast
channel. It typically takes more than 1 second before the router can decide there is
no more interest in the multicast channel and that the Multicast Fwd table is updated
to stop replication on that port.
Note — The situation of multiple hosts on a user port can occur in
case of a bridged CPE and multiple STBs.
Zapping behavior is such that the host which left the multicast channel does not wait
until the multicast channel is stopped and immediately joins another multicast
channel. During a short time, both the old and the new multicast channel are
therefore present on the subscriber port. For xDSL lines, which bandwidth is often
tailored to accommodate a limited number of multicast channels, the extra bandwidth
from the old channel may lead to frame loss.
With fast leave, the ISAM keeps track of all the hosts that joined a certain multicast
channel and immediately knows when the last host on the subscriber port has left the
multicast channel. If that is the case, then the ISAM immediately updates the
Multicast Fwd table to stop replication on that port.
Fast leave can be enabled per multicast channel.
Figure 13-9 Fast leave on subscriber ports
Normal leave Fast leave
ISAM ISAM
STB STB
CPE CPE
Bandwidth Bandwidth
240.0.0.1 240.0.0.1
Leave 240.0.0.1 Leave 240.0.0.1

Query 240.0.0.1 240.0.0.1
Join 240.0.0.2 Join 240.0.0.2

240.0.0.2 240.0.0.2
>1s
Query 240.0.0.1
240.0.0.1
Time Time
Resource admission control on the subscriber port

Video services can tolerate only very minimal frame loss, therefore an
oversubscription of video bandwidth should be avoided. Also, it may not be
acceptable that lower-priority services, such as HSI, are completely blocked by video
traffic. In this respect, the ISAM supports 2 mechanisms to control the resources on
the subscriber ports. If any of the checks fail, then join messages are rejected.
• Control the number of multicast channels per subscriber port:
This mechanism, which is primarily intended for access control, can be used as a
simple multicast-only RAC assuming that all multicast channels have more or
less the same bandwidth.
The maximum number of multicast channels is configured per IGMP channel.
• Control the downstream bandwidth per physical (xDSL) line
This mechanism takes into account the actual bandwidth of each multicast
channel, as configured per multicast channel. It is integrated in a multi-service
RAC.
A maximum video bandwidth can be configured in the CAC profile, refer to
chapter “Quality of Service”, section “CAC profile”.
Resource admission control on the uplink

Video services can tolerate only very minimal frame loss, therefore an
oversubscription of video bandwidth should be avoided. Also, it may not be
acceptable that lower priority services, such as HSI, are completely blocked by video
traffic. In case traffic engineering techniques are insufficient, ISAM supports 2
mechanisms to control the resources on the network ports. If any of the checks fail,
then join messages are rejected.
Both mechanisms apply to the aggregation of network ports.

• Control the number of multicast channels on the ISAM
This mechanism can be used as a simple multicast-only RAC assuming that all
multicast channels have more or less the same bandwidth.
The maximum number of multicast channels is configured per system.
• Control the downstream multicast bandwidth on the ISAM
channel, as configured per multicast channel. It is still a multicast-only RAC.
The maximum video bandwidth is configured per system.
Both mechanisms can also apply per bundle. A bundle is a set of multicast channels.
In a wholesale environment, each multicast service provider can hold its own bundle.
Assigning resources per bundle is a way to achieve fairness between the different
multicast service providers. The bundle is configured indirectly by configuring per
multicast channel whether the multicast channel belongs to a bundle, and if so,
configure the bundle name.
• Control the number of multicast channels per multicast bundle
This mechanism can be used as a simple multicast-only RAC assuming that all
multicast channels have more or less the same bandwidth.
The maximum number of multicast channels is configured per multicast bundle.
• Control the downstream multicast bandwidth per multicast bundle
channel, as configured per multicast channel. It is still a multicast-only RAC.
The maximum video bandwidth is configured per multicast bundle.
Access control
Access control limits subscribers access to multicast services.
The ISAM can restrict the access to a predefined set of multicast channels and
disallow joining any other multicast channels, like some kind of ACL. For this
purpose multicast packages are configured, containing a set of preconfigured
multicast channels. The set of multicast packages that are allowed to be viewed is
then configured per IGMP channel.
Packages can also be used to give limited preview access to multicast channels. The
set of multicast packages that are allowed to be previewed is then configured per
IGMP channel. With preview access, subscribers can view the multicast channel
during a short time period.
Call Detailed Records

The ISAM can generate Call Detailed Records (CDRs). The CDRs log the actual
viewing behavior of the individual subscribers. CDRs for example report the identity
of the subscriber port, the multicast channel joined, the start time and view duration.
They are sent in real time to a server using TFTP or syslog protocol. The server can
use the information to bill the subscribers on a Pay-Per-View basis.
CDR generation can be enabled and configured in the IGMP system.
Static router ports

The IGMP Proxy dynamically learns the router port as the network port from which
it received the queries, that is, behind which the multicast router resides. Join
messages and leave messages are sent on that learned router port. There can be only
one dynamic router port.
In some network topologies there is a need for multiple router ports. This can be
achieved by configuring static router ports.
For example, a network topology may have two multicast routers directly attached
to the ISAM. In that case, only one multicast router will assume the role of the
querier, the other multicast router serves as backup. To be fully prepared to take over
in the event of a failure of the querier router, the non-querier router must also be
aware of the multicast channels that need to be injected in the aggregation network.
By configuring both network ports as (multicast) router port, all the join messages
and the leave messages are sent to both routers.
Figure 13-10 Example of static router port
ISAM
non-Querier
STB
Join 240.0.0.1
0.1
Join 240.0.
Join 240.0.0.
1
Query
Querier
MR SAP
IGMP forking
An Edge Router implementing hierarchical scheduling, shapes downstream traffic
according to the actual user line rate, minus the bandwidth taken by multicast
channels streamed on this user line. Such Edge Router needs to be aware of that
bandwidth.
An IGMP Proxy enhanced with IGMP forking copies every upstream IGMP packet
towards the Edge Router into the same VLAN on which it has been received. The
forked packets contain the original source MAC and IP address from the STB. By
monitoring all the IGMP traffic on the user line, the Edge Router can thus calculate
the bandwidth taken by multicast channels on this user line.
IGMP Forking can be enabled in the IGMP system or on the IGMP channel.
Figure 13-11 Example of IGMP forking
ISAM
Aggregation network Edge
Proxy Router
( Proxied Join )
Join
STB Fwd
BTV VLAN 15
Forked Join
BTV+HSI+Voice Fwd
HSI+Voice VLAN 16
Warning — IGMP forking generates many IGMP packets.
To be effective in avoiding overload issues, the operator should make sure that these
forked IGMP packets are not snooped/proxied in the ISAM or elsewhere in the
aggregation network. In particular, the operator should:
• choose a BTV VLAN different from any unicast forwarding VLAN in which
forked packets are inserted
• not deploy non-configured (best effort) multicast service in any unicast VLAN in
which forked packets are inserted
• not deploy L2 LT boards in the ISAM (because such cards apply IGMP proxy on
ALL the network VLANs, even on unicast VLANs that may carry forked IGMP
traffic)
• enable IGMP snooping on maximum 5 VLANs in the SHub (if more, then the
SHub will snoop ALL the VLANs). Remark that, by default, VLANs in the SHub
are created with IGMP snooping enabled.
13.3 System decomposition
Multicast services impact both the LT boards and the SHub.

The LT board implements a multicast forwarder and IGMP proxy. The LT board
forwards multicast streams from internal LT-NT ports to user ports. Advanced
features like cross-VLAN multicasting, fast leave, most of SSM, RAC on the user
line, access control and CDRs are implemented in the LT board.
The SHub implements a multicast forwarder and IGMP snooper. The snooper
operates completely in the scope of a VLAN, that is, there is no cross-VLAN support
in the SHub. Advanced features like static infeed, RAC on the uplink and static
router ports are implemented in the SHub.
Figure 13-12 shows the system decomposition for multicast and how the
management concepts map on the system components. Although some concepts can
be configured both on the LT boards and on the SHub, this is not always necessary.
Refer to the Operations and Maintenance using CLI for FD 24Gbps NT.
Figure 13-12 System decomposition for multicast
LIM
STB IGMP Proxy
Unicast VLAN
mcast fwd
SHub
Multicast IGMP Snooper
VLAN Aggregation
LIM mcast fwd network
IGMP Proxy
mcast fwd
Multicast VLANs
Multicast channels
Multicast VLANs Multicast bundles
Multicast channels Router ports
IGMP channels Multicast trees
Multicast packages
13.4 Multicast and forwarding models
This section focuses on the case where the ISAM participates in the multicast data
and control plane. Depending on the forwarding model and on the configuration
(multicast enabled or not, joined channel in the list of multicast channels or not), the
ISAM does or does not participate. If the ISAM does not participate, the ISAM may
discard or transparently pass the multicast data and control frames. Table 13-1
provides a summary of the handling of IGMP packets and multicast frames in
forwarders.
Table 13-1 Handling of IGMP packets and multicast frames in forwarders
Forwarder to which IGMP channel not IGMP channel IGMP channel

the user is linked for created created, requested created, requested
unicast traffic multicast channel multicast channel in
not in list list
VLAN Cross-Connect IGMP and mcast IGMP and mcast IGMP proxy and
transparent transparent mcast replication
iBridge (IPoE) IGMP and mcast IGMP proxy and IGMP proxy and
discarded mcast replication mcast replication
iBridge (PPPoE) IGMP and mcast Not supported Not supported

transparent
PPP cross-connect IGMP and mcast Not supported Not supported
transparent
14 — Quality of Service
14.2 Upstream QoS handling 14-2
14.3 Downstream QoS 14-9
14.4 Hardware mapping of QoS functions 14-11
14.5 Configuration of QoS 14-17
14.1 Introduction
In addition to delivering best-effort, high-speed Internet services, xDSL access

networks are evolving to multiservice access networks that must be capable of
supporting a whole range of services, such as:
• conversational services (Voice over IP (VoIP), video telephony)
• video services (Video on Demand (VoD), Broadcast TV)
• transparent LAN services for business customers
• data services for business customers
• data services for residential customers
These services must be delivered with the appropriate level of QoS. In the case of
xDSL access networks with Ethernet aggregation, there are a number of network
elements, for example, BRAS, IP edge routers, ISAM, or CPE, that must each give
the correct priority treatment to the various application flows. Network performance
objectives for the different service types are documented in the ITU-T
Recommendation Y.1541 (Network performance objectives for IP-based services).
This is achieved by classifying these application flows at the ingress of the network
into a limited set of aggregate flows that are characterized by certain QoS markings.
The different network elements will then provide per-QoS class queuing and
scheduling for these aggregate flows.
The following section provides an overview of the role played by the ISAM in
end-to-end QoS.
14.2 Upstream QoS handling
This section deals with subscriber- or ISAM-originated traffic that is transmitted on

the network link.
Overview
Figure 14-1 shows the standard QoS model which includes a configurable
system-wide p-bit-to-traffic-class mapping, four queues and a fixed scheduling
scheme. Some LT board types support an eight-queue model, as explained in the
following notes. If an LT board type is not explicitly mentioned in the following,
then it only supports the standard QoS model.
The GE Ethernet LT board supports 8 queues. When this board is deployed, it is
recommended to modify the default p-bit to traffic class mapping to use 8 traffic
classes. See section “QoS on a GE Ethernet LT board” for more details.
Figure 14-1 Qos Overview - Standard model

mapping of
DSCP
ISAM queues Traffic classes .1p
to P-bits
111
GE/FE Voice TC3
110
SP 101
Video TC2
100
011
CL TC1
WRR 010
WFQ BE TC0
001
000
priority scheduling mapping to queues mapping to p-bit marking classification

traffic classes
Classification
The purpose of classification is to identify flows or streams of traffic which need a
different treatment, that is, which require a different quality of service.
Figure 14-2 QoS: classification for Standard model
1. Voice
2. Video (VoD, BTV)
3. Controlled load (home working)
4. Best effort (HSI)
classification
For the standard model, four main traffic classes have been identified: Voice, Video,
Controlled Load (CL) and Best Effort (BE). These traffic classes are listed in
Table 14-1, together with their application and recommended 802.1p value.
This approach segregates network control, voice and video-telephony into the
highest priority traffic class, broadcast video and video-on-demand into the second
traffic class, business customer data traffic into a third traffic class, and residential
customer data traffic into the fourth.
Table 14-1 Classes, application, and recommended 802.1p value
Traffic class Application Recommended 802.1p value
Voice • Voice 110

• Video telephony (111)
• + network control)
Video • Broadcast video 100

• Video-on-demand
(1 of 2)
Traffic class Application Recommended 802.1p value
Controlled load HSI for business access 011
Best effort HSI for residential access 000
(2 of 2)
It is also possible to use an eight traffic class model.

• For LT boards that support only four queues, the eight traffic classes are mapped
to four queues, according to a fixed scheme. See “Mapping and queueing” for
details.
• For LT boards that support eight queues, each traffic class is mapped to its own
queue.
Classification is based on layer 2/layer 3/layer 4 parameters

Note — The classification can already be done by the CPE (priority
tagged frames or tagged frames), but the ISAM can be configured to
overrule the marking done by the CPE.
When the outcome of classification is “discard”, we're dealing with Traffic filtering
by means of Access Control Lists (ACLs). In this way, it is possible to filter out
certain packet flows based on multi-field classification at layer 3/4 or layer 2.
Control plane and management plane traffic is separately classified based on
protocol type.
Marking
Marking is defining the value of:
• layer 2: p-bits - part of the VLAN-tag
• layer 3: DSCP - part of the IP packet header
Figure 14-3 QoS: marking

.1p
111
110
101
100
011
010
001
000
p-bit marking classification
In upstream direction, there are four possibilities:

• Trusted Subscriber Interface:
• No re-marking of DSCP or p-bit; QoS markings received by the user are accepted
as they are. This possibility is useful in case of trusted subscribers (for example, in
a business context).
• DSCP or p-bit contract enforcement/remarking. In this case, QoS markings received
from the subscriber are taken into account, but they are subject to a contract that
specifies what DSCP or p-bit markings are allowed and what QoS markings need to
be re-marked. In essence, this functionality provides support for correct marking in
case of multi-QoS Service Access Points (SAPs). This mapping to p-bit markings
applies to the IPv4 DSCP value as well as to the IPv6 Traffic Class field.
• Non-trusted Subscriber Interface:
• Default DSCP or p-bit marking per subscriber interface. In this case, all the packets
on the interface will be re-marked to the configured value.
• DSCP or p-bit marking per QoS subflow using layer 2/layer 3/layer 4 filters (based
on multi-field classification into QoS subflows).
In addition to above policies it is also possible to align the p-bits, that is, p-bits are
derived from the DSCP codepoint. There is a single system-wide p-bit alignment
table for upstream.
For stacked VLANs, there are some additional points to note related to p-bit
marking:
• In case of S+C VLAN cross-connect, both S- and C-VLAN p-bits are set to the
same value.
• In case of S-VLAN cross-connect tunnel, the C-VLAN p-bit is never modified.
The S-VLAN p-bit is set according to the preceding explanation.
The p-bit marking of protocol frames is handled in a different way to data plane
traffic. The handling differs according to the protocol.
• IGMP frames sent by the ISAM are always marked with highest priority, that is,
p-bits=7.
• DHCP frames:
• When traffic is received with p-bits marked at user side, the marking is left
unchanged.
• When unmarked traffic is received, the default p-bit marking for the given VLAN is
applied.
• PPP control frames (for example, PADI/PADO) are marked with fixed p-bits=7.
The CDE option exists to configure in the same way as done for DHCP:
• When traffic is received with p-bits marked at user side, the marking is left
unchanged.
• When unmarked traffic is received, the default p-bit marking for the given VLAN is
applied.
• ARP frames are tagged always with highest priority (p-bit=7)
Policing
Subscribers are subject to certain traffic contracts that specify how much traffic they
can send towards the network. Policers are installed to enforce these contracts.
A policer may apply to an entire subscriber interface or to QoS subflows within the
subscriber interface. In this context, a QoS subflow (or subclass) is defined as the
aggregate of packets flowing through the interface that are bound by a subcontract
and require a specific common treatment.
Two types of policer are supported:
• single token bucket policer
• two-rate three-color policer (supported only on GE Ethernet LT board)
The characteristics of these two types are explained in “Policer profile”.
Figure 14-4 QoS: policing

.1p
P
111
110
P
101
100
P
011
010
001
P
000
Figure 14-5 illustrates the policing feature implementation for a single token bucket
policer.
Figure 14-5 Policing implementation framework
QoS Session Profile
QoS Policer QoS Policer QoS Policer QoS Policy

Profile UP Profile DOWN Profile DOWN List DOWN
L2 filter
CIR L3 filter
CBS Policy-action=
Policer-Profile
Per-SAP policing
Subflow policing
L2 filters L3+ filters

DST MAC address + prefix length DST IP address + prefix length
SRC MAC address + prefix length SRC IP address + prefix length
Ethertype Min/max DST port ID
P-Bit Min/max SRC port ID
User-side VLAN ID Protocol
CFI DSCP value
Mapping and queueing

Mapping to queues is the action of assigning a frame to the appropriate queue based
on the p-bit determined during classification (see above). Queue sizes and scheduling
mechanisms can then be tuned to fit optimally to the traffic class at hand.
Traffic is classified into either four or eight traffic classes. At any congestion point
in the system, ISAM supports either four or eight queues to distinguish four or eight
different traffic classes.
Figure 14-6 shows the different QoS queues the different QoS queues for the
standard QoS model, employing 4 traffic classes and 4 queues. The configurable
mapping of p-bits to traffic class is system-wide. The mapping of traffic class to
queue is a non-configurable one-to-one mapping.
Figure 14-6 QoS queues for standard model

mapping of
DSCP
to P-bits
111
Voice TC3
110
101
Video TC2
100
011
CL TC1
010
001
BE TC0
000
mapping to mapping to p-bit marking classification

queues traffic classes
When eight traffic classes are used, the traffic classes are mapped either to four
queues or to eight queues.The selection of which mapping to use is hardware
dependent. It depends on how many hardware queues are supported by a specific LT
board type. Again this mapping is non-configurable. The mapping of eight traffic
classes to eight queues is a one-to-one mapping. The mapping of eight traffic classes
to eight queues, and the mapping of eight traffic classes to four queues is as in Table
14-2.
Table 14-2 Mapping of Traffic Classes into Queues
Traffic Class 4-Queue Mapping 8-Queue Mapping
7 3 7
6 3 6
5 2 5
4 2 4
3 1 3
2 1 2
1 0 1
(1 of 2)
Traffic Class 4-Queue Mapping 8-Queue Mapping
0 0 0
(2 of 2)
For UNI ports on a GE Ethernet LT board, it is required to configure the p-bit to

traffic class mapping per forwarder for use in the downstream direction. The
configuration should normally be the same as the system-wide mapping. Refer to
“QoS on a GE Ethernet LT board” for further details.
It is also optionally possible to define a mapping of p-bits to color marking. There
are two types of color marking available:
• Policer color marking (green, yellow, or red)): based on received p-bit value,
applicable to the GE Ethernet LT board
• Drop Precedence (DP) color marking (either green or yellow), based on remarked
p-bit value, applicable to other LT board types
The color marking is used as input to color-aware BAC. See “Queue configuration
and queue profile” for description of color-aware BAC. The policer color marking is
used as input to color-aware policing.
Note — The output of the policing will also be used as input to

color-aware BAC.
Only the GE Ethernet LT board supports color-aware policing. Only the GE Ethernet
LT board supports color-aware BAC in the upstream direction.
Scheduling and shaping
Standard scheduling model
Figure 14-7 QoS: scheduling

mapping of
DSCP
to P-bits
111
GE/FE Voice TC3
110
SP 101
Video TC2
100
011
CL TC1
WRR 010
WFQ BE TC0
001
000
priority scheduling mapping to queues mapping to

traffic classes
The standard scheduling model is presented in Figure 14-8.
Figure 14-8 Reference scheduling hierarchy
Voice
Video SP
CL
WFQ
BE
The priority scheduling is as follows:

1 Voice traffic is scheduled first (strict priority)
2 Video traffic is scheduled next (strict priority)
3 CL and BE packets compete for bandwidth in a fair manner (Weighted Fair
Queuing or Deficit Round Robin). The bandwidth ratio is determined by the
weight of CL respectively BE. The sum of the weights for BE and CL must be
equal to 100.
Scheduling is work-conserving, that is, lower QoS classes can occupy bandwidth
that is not actually consumed by higher QoS classes.
This model implies that both voice and video traffic are very well contained and only
trusted sources are allowed to use the high-priority traffic classes.
Flexible Scheduling Model

In the flexible scheduling model, each queue can be provisioned with a priority and
a weight. The scheduling settings are as follows:
• Queues with a higher priority are scheduled ahead of queues with a lower priority.
• Queues with the same priority are scheduled according to their relative weights.
The flexible scheduling model is applicable to the GE Ethernet LT board
downstream scheduling.
Shaping on network ports

ISAM supports port-level shaping of traffic on the network ports.
14.3 Downstream QoS
This section deals with traffic received from the network link and transmitted on the
subscriber link or locally terminated on the ISAM.
Downstream traffic is subject to similar QoS actions as upstream traffic. This section
will focus on the differences between downstream and upstream QoS handling.
Classification
Same capabilities as for upstream QoS handling (see “Classification”).
Marking
In the downstream direction, frames usually arrive in the ISAM with DSCP or p-bits
properly marked by service-aware edge devices (such as BRAS, edge router,
application gateway, and so on). If this is not practical for some reason, the p-bits can
be aligned to the DSCP found in the packet IP header.
Further, multi-field based marking is supported in downstream; SAP-based marking
is only supported in upstream.
Same capabilities for marking of protocol frames as for upstream QoS handling
(see “Marking”).
Policing
No traffic engineering will be done at ingress on the network interfaces. The idea
here is that ingress policing and ACLs at the service provider level have already been
applied in a (access provider-owned) box deeper in the network.
However, after the forwarding decision egress policing may apply. Subscribers are
subject to certain traffic contracts that specify how much traffic they can receive on
their DSL connection. Policers are installed to enforce these contracts. A policer may
apply to an entire subscriber interface or to a QoS subflow within the subscriber
interface.
As for upstream, it is possible to configure either single token bucket policers or
two-rate three-color policers.
Mapping and queuing

In the downstream direction, separate QoS queues (one per traffic class) are provided
per DSL line. Frames are mapped to the appropriate queue based on the p-bit
determined during classification.
Optionally, it is possible (as for the upstream case) to define a mapping of p-bits to
color marking. There are two types of color marking available:
• Drop Precedence (DP) color marking (either green or yellow), based on remarked
p-bit value, applicable to other LT board types
• Policer color marking (green, yellow, or red)), based on received p-bit value,
applicable to the GE Ethernet LT board
The use of the color marking is similar to the upstream case.

Buffer Acceptance Control (BAC) can be done by means of Tail Drop or Random
Early Detect (RED). The Tail Drop or RED can optionally be color-aware.
Scheduling and Shaping

In the downstream direction, for the DSL lines, the same capabilities apply as for
upstream scheduling (see “Scheduling and shaping”).
The scope of shaping is different though. In the downstream direction shaping

applies to the per-subscriber queues.
A GE Ethernet LT board supports the following scheduling and shaping capabilities:
• Scheduling of queues at the port level. The scheduling can be strict priority or
WFQ and is configurable per queue (applies to both UNI and NNI ports)
• Scheduling of ports at the board level with configurable port weights (applies to
UNI ports only)
• Shaping at both the queue level and the port level (applies to both UNI and NNI
ports)
Connection Admission Control

The ISAM allows associating bandwidth parameters to known multicast video
streams. Per subscriber line, a maximum bandwidth (in kb/s) can be configured for
(downstream) multicast. In addition, a portion of the link bandwidth can be reserved
for voice and data. Based on the bandwidth available for multicast, the ISAM
executes a CAC for known multicast sessions(*).
ISAM also supports CAC for multicast on the uplink.
Note — (*) Video on Demand (VoD) traffic is not taken into account.
14.4 Hardware mapping of QoS functions
QoS on the NT boards

The QoS functions of the NT are fully implemented at the switch port/service level.
In the ISAM, per-flow or per-session QoS is handled on the LT boards, for example,
QoS at the DSL port bottleneck and rate limitation of user sessions.
The following QoS features are supported in the SHub switch hardware:
• Classifying packets
• Metering packet flows
• DSCP-to-p-bit alignment (IPv4 only)
• Mapping packets to a queue
• Buffer acceptance and scheduling at egress port side
• Per port egress rate limitation
• Uplink CAC
Downstream, frames are expected to arrive with correct priority markings. If the
video feed interface is a dedicated Ethernet interface, a default p-bit value can be
attached to video frames. If, for various reasons, it is impractical to set the p-bits in
the upstream node, the SHub allows to align the p-bits to the DSCP for IP packets
incoming on the external interfaces.
The NT supports Connection Admission Control on the uplink for multicast traffic;
the bandwidth of known multicast streams is checked against net available
bandwidth on the uplink. Consequently, a multicast join request for a multicast
stream that was not yet present on the uplink will only be honored if the check is
successful.
QoS on the LT boards
QoS on layer 3/layer2+ LT boards

Figure 14-9 shows the logical architecture for QoS on layer 3/layer 2+ LT boards.
This includes all the ISAM LT boards except the layer 2 LT boards.
Figure 14-9 Logical architecture for QoS on layer 3 LT boards

downstream
Per-DSL line ATM or EFM
Logical Policing, segmentation DSL
GE Input segregation Classification, PVC
aggregate processing per DSL line Queuing, forwarding
Scheduling decision
upstream
Segregation into DSL
GE output buffers
Per-DSLline
Per-DSL li Input ATM or EFM
aggregate (802.1P aggregates) Policing processing
processing reassembly
The input-processing entity stands for all the protocol and forwarding-plane
processing functions. Each frame received from the network interface will have a
handler or meta-data that will contain all the fields needed by subsequent
QoS-related functions.
The next phase is the classification, policing and segregation process within a DSL
link; see Figure 14-10.
Session rate limitation is achieved by way of policing. Policing can be done at
different subscriber SAPs: bridge port, VLAN port, IP interface, or PPP CC client
port.
Both upstream and downstream policing is possible with possibly asymmetrical
values.
The ISAM handles policer conflicts in such way that, for each frame, the policer
installed on the highest layer of the interface hierarchy will be applicable. No frame
will be policed by more than one policer.
Figure 14-10 Per DSL-port scheduler

BACC voice
Traffic BAC video DSL

Policing SP
SP
class
entity BAC CL
switch
WFQ
WFQ
Rule per SAP: Based on: BAC BE
• PVC • 802.1P
• PPP Modes:
• VLAN ID • Taildrop
• 802.1X • RED
• IP interface
Traffic class mapping on the LT boards is governed by a system wide p-bit-to-queue

mapping table.
Note — The traffic class mapping on the NT boards is governed by
another system wide table.
BAC is either Tail Drop or RED per downstream queue (optionally DP-aware).
A WFQ scheduler ensures fair redistribution of the remaining bandwidth between
CL and BE traffic. Some boards also support shaping per downstream queue.
Figure 14-11 shows the Ethernet-to-ATM QoS transition.
Figure 14-11 Ethernet-to-ATM QoS transition

Frame Domain Cell Domain
Segmentation
VOICE buffers VC1
Add correct
1 frame VPI/VCI VC2
VIDEO
SP
SP fields
VC3
CL Rate limitation to
WFQ
WFQ DSL bandwidth
DSL
BE
Ethernet (frame level)
scheduler
Scheduling is done solely on the Ethernet frame level, even for ATM-based DSL
transmission types.
The queuing decision (within a DSL port) is independent from the forwarding
decision. There is no explicit fairness between different PPPoE or IPoE sessions
within a DSL link. Their peak rate is enforced independently by way of policing, and
then they share the same First In First Out (FIFO) per traffic class.
Marking is generally applicable upstream, although with the policy framework, it is
possible to modify downstream p-bit and DSCP values. Packets may arrive from user
ports tagged, untagged, or priority-tagged. At the bridge port and VLAN port level,
the ISAM supports a remarking table which maps all user-defined P-values to
allowed values. Untagged frames can be marked based on subscriber SAP defaults
(statically configured).
The ISAM allows also DSCP-marking for various subscriber SAPs. DSCP-to-DSCP
re-marking is also possible, just like p-bit re-marking for tagged and priority-tagged
frames. Finally, a global DSCP-to-p-bit alignment table is provided to align
DSCP-marked traffic on selected interfaces to p-bits, as traffic segregation still relies
on p-bits. Note that these marking capabilities related to DSCP are available only for
IPv4 packets, not IPv6 packets.
PPP-session marking for p-bits is possible based on the QoS session profile
attributes.
QoS on the layer2 LT boards

Layer 2 LT boards have a different QoS architecture. Queuing is per PVC, and all
the downstream unicast frames are using the same First In First Out (FIFO) queue.
This queue is scheduled with a priority that is inferred from the upstream p-bits
attached to the bridge port that was created on top of the VC.
Layer 2 LT boards support 4 priority levels downstream. Upstream there is no
bottleneck, hence no queuing other than AAL5 reassembly is required.
Traffic within a VC can have different priorities:
• unicast traffic priority is inferred from the port default upstream p-bits
• broadcast traffic has the same priority as unicast traffic
• multicast has priority 2 (second highest) if the multicast source is preconfigured
in the multicast source table, otherwise 0 (lowest)
Prioritization within a VC is strict priority. Also, across multiple VCs, fairness is

guaranteed only per datagram-priority and not per VC bandwidth.
Upstream PVCs are mono-QoS (that is, one P code point can be attached to them).
Each PVC will have an attribute that contains the default and unique VLAN ID and
the 802.1-bit value. The default 802.1-bit value can be specified by the operator by
means of the management interface.
The bit used for marking upstream frames is also used for downstream prioritization
of unicast traffic (the priority level equals p-bits/2).
Note — Only fixed p-bit value marking is supported; no DSCP

marking, nor dot1p-alignment.
Traffic segregation into downstream queues is combined with the forwarding

decision: determining the outgoing port and PVC and determining the correct queue
with the appropriate priority is done in a single shot. For normal data traffic, this
relies on the VLAN ID (which is configured by the operator manually) and the MAC
DA (which is learned) and does not rely on the 802.1-bits.
Session rate limitation is achieved by way of policing. Policing can be done per PVC.
QoS on a GE Ethernet LT board

A GE Ethernet LT board supports both UNI and NNI ports. The NNI port is typically
employed to connect a subtending system (such as another ISAM) or a business
customer. Therefore, it is expected that NNI ports will have simplified upstream QoS
requirements, since many QoS functions will have already been performed. In the
case of a GE Ethernet LT board, the QoS capabilities of both UNI and NNI ports are
summarized in Table 14-3.
Table 14-3 QoS capabilities of UNI ports and NNI ports
Feature NELT-A NELT-B
UNI UNI NNI
P-bit-handling P-bit-based classification Y Y Y
P-bit to traffic class mapping System System or VLAN System
Port default p-bit (untagged frames) Y Y Y
VLAN-based priority (tagged frames) Y Y Y
P-bit regeneration profile Y Y Y
DSCP-handling DSCP-to-p-bit alignment Y BP BP
DSCP-to-DSCP contract table Y N N
Subflow L2/L3 filters Y BP, VP BP, VP

Subflow policing and marking Y BP, VP BP, VP
DSCP range support for L3 filters N Y Y
Policing SAP based policing Y BP, VP BP, VP

trTCM (Two Rate Three Colour N Y Y
Metering) – Colour aware and blind
variants
Queueing WRED (# of colours) 1C 3C 3C
Weighted tail drop (# of colours) 1C 3C 3C
Downstream programmable weights Y Y Y

between WFQ queues
Downstream configurable SP/WRR N Y Y

queue scheduler at port level
Downstream programmable weights - Y -

between ports (scheduling at board
level)
Shaping Port shaping N Y Y
Queue shaping N Y Y
Legend:
BP: supported at Bridge Port level
VP: supported at VLAN port level
The following limitations apply to the NNI ports:

• downstream L2/L3 filters are not supported
• downstream policers are not supported on VLAN port level
• downstream trTCM is not supported

• L2 filter with MAC address is not supported
Note — Regarding the p-bit to-traffic-class mapping:
By default, the system level p-bit-to-traffic-class mapping maps the

eight p-bits to four traffic classes. When the GE Ethernet LT is
deployed, this mapping should be modified to map the eight p-bits to
eight traffic classes. Since the GE Ethernet LT supports eight queues,
each traffic class will be mapped to its own queue. On other LT types
which only support four queues, the eight traffic classes are mapped
to four queues (see section “Mapping and queueing”).
Since the GE Ethernet LT is designed to use the eight queue model,
unexpected behavior may occur if the p-bit-to-traffic-class mapping is
not configured with eight traffic classes both at the system level and
at the VLAN level.
Usually, it is expected that both system level and VLAN level
mappings will be configured identically. There are cases where a
different mapping could be used at the VLAN level, however. For
example, where it is desired to have a “queue per VLAN” model (for
example, to allow per-VLAN shaping downstream). In that case, all
the p-bits for a VLAN are mapped to a single traffic class. This traffic
class is then mapped to a specific queue.
Link Aggregation on a GE Ethernet LT board

The GE Ethernet LT board supports link aggregation of up to eight ports per link
aggregation group (LAG). The ports may be either all UNI ports or all NNI ports,
and all ports in the LAG must be on the same LT board and must be all operating at
the same link speed. There are some special considerations related to the QoS for the
LAG:
• Downstream queues, queue profiles and scheduler node profiles are all
configured on the LAG port and the configuration is applied identically to each
physical port in the LAG.
• A downstream queue shaper applies across all ports of the LAG, for the queues
of a specific traffic class. In the case of a UNI LAG, the aggregate of the traffic
across all queues is shaped. In the case of an NNI LAG, if the shaper rate is R and
the number of active links is N, then each queue is shaped to a rate of R/N.
• A downstream port shaper applies across all ports of the LAG. In the case of a
UNI LAG, the aggregate of the traffic across all ports is shaped. In the case of an
NNI LAG, if the shaper rate is R and the number of links is N, then each port is
shaped to a rate of R/N.
• A policer associated with an LAG will be applied to traffic for all active links in
the LAG.
• As usual, a session profile is attached to a bridge port or a VLAN port. Since the
bridge port or VLAN port is associated with the entire LAG (not just one physical
port) then the session profile applies to all physical ports in the LAG. This is also
true for the marker profile, policers and filters that belong to the session profile.
• p-bit marking/remarking configured on the bridge port or a VLAN port of an
LAG is applicable to all physical ports of the LAG.
• CAC checks are made using the aggregate bandwidth of the LAG, not the
bandwidth of the individual physical ports.
• QoS counters apply to the LAG, not to the individual physical ports of the LAG.
14.5 Configuration of QoS
The ISAM uses QoS profiles to perform ingress and egress traffic policing, class
queuing, and scheduling. QoS profiles can be created and then assigned to QoS
resources and SAPs.
IACM part
The following QoS profiles are supported on the LTs (IACM part):
• CAC profile
• Queue profile
• Session profile
• Marker profile
• Policer profile
• Policy profile
• Layer 2 filter
• Layer 3 filter
• Policy action profile
CAC profile
A CAC profile is primarily used to perform multicast video admission control for an
individual xDSL port in the downstream direction. The maximum downstream
bandwidth to be occupied by video can be further constrained by setting the
maximum multicast bandwidth parameter in the CAC profile.
A CAC profile contains three configurable rate parameters:
• the minimum reserved bandwidth for voice
• the maximum allowed bandwidth for multicast video
• the minimum reserved bandwidth for data traffic
The ISAM derives the line rate from the physical interfaces and calculates an
estimate of the available Ethernet bandwidth using configurable overhead factors.
The line rate taken into account may be the guaranteed sync rate or the actual line
rate in case of xDSL, based on a global configuration. In the profile, a part of the
available downstream bandwidth can be reserved for voice and data applications, and
the remaining part will be kept by the system as the available bandwidth for multicast
video. Only pre-configured multicast streams are considered for CAC. Unicast
video, regardless of whether or not it is premium content or generic internet
streaming video, is ignored by the CAC function.
A CAC profile can be associated with an xDSL interface, using the QoS DSL link
configuration command, see the CLI Commands for FD 24Gbps NT and the
Operations and Maintenance Using CLI for FD 24Gbps NT documents for more
information.
Ingress QoS profile (p-bit to traffic class mapping)

The ingress QoS profile is used to map traffic to the correct traffic class. A profile is
associated with each forwarder (VLAN) or per VLAN port. The configurable profile
specifies for each p-bit value, the traffic class to which it is mapped. Up to 8 traffic
classes can be specified.
The ingress QoS profile is supported for GE Ethernet LT board (UNI ports only).
For other LT board types, there is a single configurable system-wide mapping table
that maps p-bits to the traffic class. For the GE Ethernet LT board:
• NNI ports use the system-wide mapping table
• UNI ports use the system-wide mapping table if no ingress QoS profile has been
configured.
Queue configuration and queue profile
For the Layer 3 LT boards, in the downstream direction, the queue weight is
configured for the Controlled Load (CL) queue and the Best Effort (BE) queue. The
default weight of the CL queue is 66 and the default weight of the BE queue is 34.
A queue profile is associated with each queue. The queue profile is a BAC profile
that contains admission control information for frames arriving at the buffer from the
services side of the network. There are a number of default BAC profiles which can
be used, but which can not be modified nor deleted.
Two basic BAC types are supported in downstream: RED and tail drop. However,
their color-aware variants are also available on some LT boards:
• Two color tail drop
• Two color RED
• Three color tail drop (GE Ethernet LT board only)
• Three color RED (GE Ethernet LT board only)
A RED queue has three configurable parameters:

• MinThreshold: the average queue filling level for which frame discard will start
to occur (threshold expressed in number of packets)
• MaxThreshold: the average queue filling level for which frame discard will start
be 100% (threshold expressed in number of packets)
• DropProbability: the probability of frame discard for average queue filling levels
just below the maximum threshold.
Figure 14-12 RED configuration parameters

Drop probability
Discard
probability
Minimum Maximum Weighted average

threshold threshold Filling level
Note — The weight, used for calculating average buffer sizes in

RED, is not configurable.
Arriving frames are accepted as long as the average queue filling level remains below
the minimum threshold. Frames received at the moment the minimum threshold is
exceeded will be dropped with a probability as indicated by the RED curve.
For tail drop queues, only a max queue size has to be configured. Queue size is set
as the number of frames that can be stored in the queue. Arriving frames are queued
as long as the queue is not full. After the queue is full, all incoming frames are
discarded until the queue can transmit a frame over the xDSL line and space in the
queue is made available.
In the case of color-aware BAC, a separate curve must be configured for each color.
That means, in the case of color-aware RED, that MinThreshold, MaxThreshold and
DropProbability are configured separately for each color. In the case of color-aware
tail drop, only MaxThreshold needs to be configured for each color. The following
two figures illustrate the three-color WRED and the three-color tail drop,
respectively.
Figure 14-13 Three Color WRED
Drop
probability
100%
Averaged queue
filling level
red red yellow green

min max/ max/ max
yellow green
min min
Figure 14-14 Three color tail drop
Drop
probability
100%
Actual queue
filling level
red yellow green

max max max
Note 1 — BAC configuration for upstream queues on LT is fixed.
Note 2 — L3 LTs support buffer oversubscription.
Shaper profile
ISAM uses shaper profiles to capture shaper configuration parameters. For a DSL
line, a shaper profile contains the following configuration parameters:
• Type: only single-token bucket shapers are currently supported.
• Committed Information Rate (CIR): in 16 kb/s increments up to a maximum of
128 Mb/s (a theoretical maximum of 2,147,483,647 Kb/s exists on the GE
Ethernet LT board, to accommodate shaping across link aggregation groups).
• Committed Burst Size (CBS): in byte increments up to a maximum of 256Kbyte
(this parameter is not used by shapers on GE Ethernet LT).
A DSL shaper profile may be associated with a downstream queue. For a GE

Ethernet LT board, a shaper may also be associated with a port (either UNI or NNI).
Scheduler node profile

The GE Ethernet board uses the scheduler node profile. It provides the flexibility
needed for flexible, hierarchical scheduling and shaping. The scheduler node profile
does not specify weight or priority for its associated queues. Instead, the queues
themselves have weight and priority parameters. Also the scheduler node profile can
have a variable number of associated queues (either four or eight). The scheduler
node profile includes the following parameters.
• Weight and priority:
used to schedule at the next level scheduler. For example, if the scheduler node is
at the UNI level, its output will be next scheduled at the board level (GE Ethernet
LT).
• Shaper profile:
used when the output of the scheduler node requires shaping.
Session profile
The QoS session profile is the main building block for conveying user traffic,
contractual rights, and treatment of subscriber services through the network element.
This profile is a macro profile that has its own parameter settings, as well as
references to other profiles.
A QoS session profile is always a user SAP. Please consult the CLI Commands for
FD 24Gbps NT document for the most recent list of supported SAP types.
A QoS session profile is composed of a logical flow type, a marker profile and two
policer profiles for up and downstream policing of the logical interface to which a
certain session profile is attached.
Figure 14-15 Composition of QoS session profile
QoS Session Profile
Logical Flow QoS Policer QoS Policer QoS Marker QoS Policy QoS Policy
Type Profile Up Profile Down Profile Up List Up List Down
The logical flow type is a mandatory parameter but is ignored from R4.0 onwards,
that is, the logical flow type is always considered null (generic). Hence, the QoS
Session profile can be attached to any interface, provided that the settings inside the
profile can be configured on the target hardware. Unsupported fields/actions are
silently ignored at run-time.
QoS Session profiles are assigned statically, as specified by the operator.
Marker profile
The marker profile is a building block of the QoS session profile. The marker profile
is used to convey upstream marking settings to the Service Access Point (SAP).
The marker profile carries a flag for enabling DSCP to p-bits alignment of the SAP,
based on the global DSCP to p-bits alignment table of the layer 3 boards. This further
allows to specify the SAP default p-bits, the DSCP, or the DSCP contract table
(depending on the SAP type). The marker profile can also be used to re-mark the
p-bit based on trTCM packet color.
Six types of marker profiles exist:
• d1p: fixed value imposed for p-bit
• dscp-contract: DSCP code-point translated
• d1p-dscp: fixed value imposed both for p-bit and DSCP code-point
• dscp: fixed value imposed for DSCP code-point
• d1p-dscp-contract: fixed value imposed for p-bit, while DSCP code-point
translated
• d1p-alignment: p-bit value derived from DSCP code-point
All types of marker profile are supported in the upstream direction
Only the first type of marker profile is supported for IPv6 packets (that is, a fixed
value imposed for p-bit).
See the CLI Commands for FD 24Gbps NT and the Operations and Maintenance
Using CLI for FD 24Gbps NT documents for more information about marker
profiles.
Policer profile
The ISAM uses policer profiles to enforce predetermined limits on upstream and
downstream subscriber traffic. Single-token bucket policers are supported where the
action upon the conformance result is either pass or discard. The layer 3 LT boards
support policing, both upstream and downstream.
A single-token bucket policer profile contains following policer parameters can be
set:
• Committed Information Rate (CIR) in 16 kb/s increments up to a maximum of
128 Mb/s for both upstream and downstream policing.
Note — For the GE Ethernet LT, CIR is up to a maximum of 2.5 Gb/s
for UNI downstream and 100 Gb/s for NNI and UNI upstream. These
large values are applicable in the case of link aggregation groups.
• Committed Burst Size (CBS) up to a maximum of 128 Mbyte. Note that the
maximum is dependent on the LT type:
• L3 LT based on Intel or CATE: 256 KB
• NELT-A: 2 MB
• L3 DSL LT based on CATAN: 64 MB
• NELT-B:
- UNI downstream: 64 MB
- UNI upstream: 128 MB
- NNI upstream/downstream: 128 MB
The GE Ethernet LT board also supports the two-rate Three Color Marker (trTCM).
This is a type of policer that marks each packet with a color - green, yellow, or red.
The trTCM contains some additional parameters:
• Excess information rate (EIR)
• Excess Burst Size (EBS)
• Color mode: either color-aware or color-blind
• Green action: forward, or forward and re-mark the green packets. Re-marking can
either re-mark the p-bit or set the DEI based on the color.
• Yellow action: forward, discard, or forward and remark the yellow packets
• Red action: forward, discard, or forward and remark the red packets
• Coupling flag: enabled or disabled.
The trTCM is intended to be used in conjunction with the color-aware BAC types
described in “Queue configuration and queue profile”. The color-aware mode makes
use of the Drop Precedence marking described in “Mapping and queuing”. The Drop
Precedence marking is either in-profile (green), out-of-profile (yellow or red). The
coupling flag is defined in the MEF 10.1 and only is applicable for color-aware
mode.
You need to create a separate policer profile for each direction. When you create and
configure a session profile, you have the option to associate both an upstream and a
downstream policer profile with that session profile. Once configured and
associated, policing is applied to all the frames within the session with which the
policer profiles are associated. As such, rate enforcement is performed uniformly for
all subscriber lines that are associated with that session profile.
In addition to this fast path policer, there is also a slow path policer that limits the
number of (upstream) control frames that are excepted to the on-board processor for
each subscriber line. This mechanism has been put in place to protect this shared
resource against DoS attacks from malicious users.
The slow path policer is also a single token bucket policer with Committed
Information Rate expressed in terms of packets per second and Committed Burst
Size expressed in terms of number of packets. This policer type is not subject to
profiling.
Policy framework
A generic policy framework provides finer-grained control over subscriber traffic. It

provides for generic layer2 or layer3 classifiers and associated policy rules, which
can be attached with a certain priority to subscriber Service Access Points (SAPs).
One pair of classifier (or policy condition) and policy action list form the basic
building block of a unidirectional policy. On each supported SAP, a QoS session
profile can be attached, which contains two lists of policies: one for upstream and one
for downstream. The policy precedence defines the order in which policy conditions
(the filters) are configured in hardware per SAP. The rule is that the first filter that a
given packet matches will cause its associated actions to be carried out and no further
filtering rules are verified for that frame.
Figure 14-16 shows the policy building blocks.
Note — When P-bits and DSCP are used as a policy match condition
they relate to the remarked values. However, for the GE Ethernet LT
board, the received p-bit is used.
Figure 14-16 Policy building blocks
L2 Filter L3 Filter Policy Action

MAC Destination Address IP Destination Address Default Disposition
MAC DA Prefix IP DA Prefix
Set DSCP
MAC Source Address IP Source Address Set P-bits
MAC SA Prefix IP SA Prefix
Police
Ethertype DSCP Sharing
P-bits Protocol Type
CFI bit Destination Port Range
VLAN ID Source Port Range
A set of non-conflicting actions can be grouped in a Policy Action list. This includes
a default disposition (permit/deny statement for ACL functionality), setting p-bit and
DSCP and policing. All packets identified by way of the associated filter can be rate
limited by a policer instance. Some subflow policies can share common attributes,
such as policing. The “Sharing” property of a policy action table enables or disables
policer sharing. Policer sharing will be used when the same policy action list is
referenced more than once on the same SAP in the same direction, and if the Sharing
attribute was set to “enable”.
The ISAM LT boards support more policies in the upstream direction than in the
downstream direction. This is in line with the typical requirements, as more security
policies are required in the ingress direction, while in the egress, mostly only traffic
class rate limitation applies.
There is a complex sanity check in place for avoiding conflicting policies, such as
filtering on MAC DA for IPoA traffic, and so on. In the downstream direction,
p-bit/DSCP code point modifications can only be realized by means of a policy
action.
The following restrictions apply to IPv6 packets:
• Layer 3 filters are not supported for IPv6 packets. This implies that corresponding
policy actions are not possible for such packets, unless applied via a Layer 2 filter.
• It is not possible to set the DSCP field in an IPv6 packet as a Layer 2 filter action.
Counters and Threshold Crossing Alarms

QoS counters and related alarms serve the purpose of debugging the network for
traffic problems. SLA-based accounting is served by SAP-counters and as such
queue counters should only be enabled when debugging or testing the network.
Enabling the queue counters may reduce the maximum throughput of the system.
QoS counters are designed to provide evidence of traffic issues in case there are
problems. The queue counters are a basic building block which can be used by a
network operator to learn whether queue overflows occur in a certain traffic class,
and if so how often.
In a normal troubleshooting scenario the operator would enable or reset queue
counters and start up the services to observe whether the queue drop and pass
counters are incrementing. Queue drop counters provide evidence of buffer
overflows, which needs to be avoided in high-priority traffic classes transporting
non-responsive flows. Queue pass counters provide evidence of ongoing traffic,
which is a basic feedback whether there is connectivity or not and if traffic falls into
the right queues.
Alarms are useful to observe events that occur rarely. QoS alarms have been defined
to detect in part traffic misbehaviors and in part system performance issues. While
queue counters can be used for device-under-study testing, alarms are useful to
detect conditions that occur rarely and would cost too much to be tracked by OAM
engineers.
The counters and threshold crossing alarms (TCAs) can be divided in two categories:
line/ queue based and line-card based.
Figure 14-17 QoS Counters and TCAs on layer 3 Boards

Queue Counters:
Passed Bytes/Frames
Dropped Bytes/Frames
OBC counters: Load
Dropped OBC frames US
Dropped OBC frames DS Queue TCAs:
OBC Dropped Frames
OBC TCAs: Load
Dropped OBC frames US
Dropped OBC frames DS
Tx
SP
WFQ System Bus Counters
(per Traffic Class):
Passed Bytes/Frames
Load
Memory Pool Master
Tx
Downstream
System Bus TCA):
Load
SP
WFQ
Tx
Aggregate buffer counters:
Dropped frames US
Dropped frames DS
Dropped low prio frames High
priority Line Counters:
Passed Bytes/Frames
Aggregate buffer TCAs: threshold Droppedd Bytes/Frames
Dropped frames US Load
Dropped frames DS
Dropped low prio frames
The following line/queue based counters and alarms are supported:

• number of packets passed (per queue/line)
• number of packets dropped (per queue/line)
• number of bytes passed (per queue/line)
• number of bytes dropped (per queue/line)
• threshold crossing alarm for dropped packets (per queue)
• queue load meter per queue (sync rate vs. bytes passed in this queue)
• total load meter per line (sync-rate vs. bytes passed per line)
• threshold crossing alarm for the load inflicted by traffic in one queue on the parent
physical interface (taking into account sync rate and encapsulation format)
The queue/line loads and counters are calculated on a 15-minute basis. No long
history is kept; only the current and previous 15-minute counters are retrievable.
The total buffer pool is divided in two regions: a common region and a region saved
for high-priority traffic (that is, voice or video packets). The preliminary buffer pool
threshold can be specified in terms of percentage of total buffer pool, above which
only high-priority traffic is permitted into the buffer pool (both upstream and
downstream).
Figure 14-18 Buffer pool regions on IXP boards
Max usage of a queue

Total Physical Packet from the total pool (no
memory guaranteed minimum
on L3 boards)
Area that can

be saved for
high priority
traffic via
configuring
partial buffer Area for both low and
overflow high priority traffic
threshold
(configurable in
% of total pool)
For upstream and downstream (which share the same pool on L3 cards) there are
dedicated threshold crossing alarms that can be triggered when more than a
programmable number of OBC, resp. non-OBC packets are dropped. Packet loss in
the total buffer pools may occur when:
• the egress queue sizes have been enlarged to a large extent, and many egress ports
on multiple queues suffer large backlogs
• when exceptionally high loads with smallest packet sizes persist over a long
duration (basically several hundreds of packets at gigabit speeds with less than
100 bytes each)
OBC-directed packets (that is, control packets) are also tracked for packet loss and
associated threshold crossing alarms can be activated. The queues towards the OBC
may overflow when:
• there are large bursts of control frames in the downstream direction
• there are large and correlated bursts on many ingress lines in the upstream
direction
Due to the fact that each subscriber line has a programmable packet policer for
control traffic it is inconceivable that the OBC-directed queues should overflow as a
result of just one subscriber line.
The following line-card level counters and alarms are supported:
• number of packets passed (per Traffic Class)
• number of bytes passed (per Traffic Class)
• total system bus load meter (per Traffic Class)
• threshold crossing alarm for system bus total load
• aggregate buffer overflow events for upstream resp. downstream traffic
• aggregate buffer overflow events for upstream resp. downstream OBC directed
traffic
• partial buffer overflow events for low priority traffic (that is, Controlled Load and
Best Effort)
• threshold crossing alarm for dropped upstream resp. dropped downstream traffic
due to aggregate buffer overflow
• threshold crossing alarm for dropped upstream resp. dropped downstream OBC
directed traffic due to aggregate buffer overflow
• threshold crossing alarm for dropped low priority traffic due to partial buffer
overflow
The system maintains 32 15-minute counter sets and one previous and current 1-day
counter set related to aggregate buffer overflow (aggregate upstream, aggregate
downstream, aggregate upstream OBC, aggregate downstream OBC and partial
buffer pool overflow).
Fan-out load per traffic class is useful to trigger operator attention to unusually high
load conditions per LT board. In case the system bus gets overloaded (via normal but
rare or abnormal load conditions) this information can be used to take action in terms
of limiting the number of subscribers provisioned per LT board or finding problems
with multicast sources. The system automatically calculates fan-out loads (that is, the
load that goes down the system bus after multicast replication has occurred) vs. the
actual system bus bandwidth (as this varies with hardware versions).
For fan-out load the system keeps 96 15-minute counters sets (load, pass
bytes/frames per Traffic Class) and one previous and current 1-day counter set (pass
bytes/frames) in addition to rolling counters. The 15-minute history counters are
useful for tracking system load evolutions over the day. Since the load is calculated
per traffic class, not only per LT board, this information can be used to track the
system load and bandwidth usage for the multicast video service (as this could not
possibly be tracked deeper in the network).
SHub part
P-bit-to-queue mapping
The SHub has its own dedicated p-bit-to-queue mapping.
DSCP-to-P-bit alignment
On the SHub there is a single DSCP-to-p-bits alignment table that can be enabled per
SHub external interface for incoming traffic. It applies to all incoming (IPv4 only)
traffic for all VLANs.
CAC profile
A Resource Admission Control mechanism is supported on the uplink as well. See
chapter “Multicast and IGMP” for more detailed information.
Queue profile
Queue settings are hard-coded (that is, not operator configurable).
Scheduler profile
The following scheduling parameters can be configured on external interfaces:
• port level rate shaping
• relative weight of Controlled Load, respectively Best Effort traffic
Scheduling parameters can be configured per member of a Link Aggregation Group
and is replicated to other members.
Supported range of shaping rates is [64Kbps - 10Gbps] in steps of 64 Kbps.
Supported range of WRR weights is [1-15].
Scheduling on internal interfaces is not configurable at all.
Flow profile
A flow definition is used to describe the scope of a policer instance. A flow definition
can be instantiated on multiple ports, but only once per port. On different ports it can
be paired with different policers.
Following flow types are supported:
• Port
• VLAN
• VLAN.P
• VLAN.DSCP (for IPv4 only)
Meter profile
The operator can create (62) policer prototypes. A policer prototype contains rate and
burst tolerance information, and can be used on multiple ingress ports and on
multiple flows. Following ranges are supported for the respective policer parameters:
• information rate: [1Kbps - 10Gbps] units of 64Kbps
• burst tolerance: [3Kbytes - 512Kbytes] 8 discrete values
15 — Resource Management and
Authentication
15.2 RADIUS features 15-2
15.3 802.1x authentication via RADIUS 15-2
15.4 Operator authentication via RADIUS 15-2
15.5 Encryption of authentication data 15-3
15.6 Lawful interception 15-3
15 — Resource Management and Authentication
15.1 Introduction
Remote Authentication Dial-in User Service (RADIUS) is a standardized method of

information exchange between a device that provides network access to users
(RADIUS clients) and a device that contains authentication and profile information
for the users (RADIUS server). The ISAM supports RADIUS for both layer 2 and
layer 3 forwarding.
Authentication via RADIUS provides the following advantages:
• password management is centralized so there are fewer password databases and
passwords to maintain.
• support of strong authentication in a cost-effective way. The same RADIUS
server or a back-end authentication server supports strong authentication. In the
case of local authentication, strong authentication may not be feasible.
15.2 RADIUS features
The following features are supported:

• User authentication via an external RADIUS authentication server.
• A RADIUS Authentication client:
• encrypts all password fields in the messages.
• supports multiple RADIUS Authentication servers.
• A flexible authentication mechanism:
• support of Password Authentication Protocol (PAP) and Challenge-Handshake
Authentication Protocol (CHAP) authentication
• support of Extensible Authentication Protocol (EAP)
• Fallback to a configurable default operator profile when the RADIUS server does
not support vendor specific attribute.
15.3 802.1x authentication via RADIUS
RADIUS support provides the ability to authenticate 802.1x sessions at an external

database (residing at the RADIUS server). Apart from authentication, RADIUS can
also be used to provide accounting for 802.1x sessions. In addition, when
authenticating the subscriber, RADIUS can return configuration parameters to the
ISAM, which enables the dynamic provisioning of certain subscriber aspects. These
aspects include dynamic mapping to a service provider (service selection), QoS, and
ACL. RADIUS not only provides secure authentication and accounting, but also
facilitates subscriber provisioning.
15.4 Operator authentication via RADIUS
CLI and TL1 operators can be authenticated either locally on each DSLAM or
remotely via a central RADIUS server.
There is one restriction: if CLI or TL1 over SSH with key authentication is used, then
the authentication has to be done locally. RADIUS does not support keys.
This functionality is only supported for CLI and TL1. The authentication occurs once
for a complete session. Operator authentication is not supported for SNMP operators
as SNMP does not work with the concept of session. Communication with a
RADIUS server would have to be set up for each SNMP request, in order to
authenticate the originator.
A centralized authentication server has a lot of benefits for the management of
operator accounts, but is a danger with regard to availability and security. It is
advisable to support redundant RADIUS servers (this is supported by the ISAM). In
addition, the ISAM will fallback to local authentication in case the communication
with the RADIUS server fails.
Typically, the local database only contains the administrator account in case
RADIUS is used. To prevent isolation, one default local operator profile can be
configured, which applies when RADIUS is not reachable and when the operator is
not configured in the local database.
Note — No accounting is performed for authenticated CLI/TL1
operator sessions.
15.5 Encryption of authentication data
Passwords, RADIUS secrets, and other authentication data are encrypted in such a
way in the system database that the plain form cannot be derived from the system
database when this is not required for normal operation (for example, passwords for
PAP local authentication). In cases where it is necessary to retrieve the plain text
form, adequate encryption (MD5) is used to avoid unauthorized retrieval. This
applies for authentication on all the management interfaces and on all the user
interfaces.
15.6 Lawful interception
Lawful Interception (LI) is done by Law Enforcement Agencies (LEA) of

governments in order to combat crime and other anti-constitutional activities.
The ISAM family performs the role of Content of Communication Interception
Function (CCIF) by mirroring the data to be intercepted. The target to be intercepted
is identified by an external Lawful Intercept Administration Function (LIAF) by
means of interfacing with the RADIUS and/or the DHCP servers.
The LIAF then triggers the ISAM to intercept the associated target based on
identifiers received from RADIUS and/or DHCP servers.
Once the data is mirrored (duplicated) in the ISAM, the same data is forwarded to an
external Lawful Interception Mediation Function (LIMF), which in turn securely
transmits the data towards the LEA.
Due to the sensitive nature of Lawful Interception, the administration of Lawful
Interception is restricted to authenticated operators only. Non-authenticated
operators are not able to administer the Lawful Interception function in the ISAM.
Lawful Interception administration on the ISAM can be done either via CLI or by
SNMPv3 by exclusively authenticated operators.
In order to securely transmit the content of communication data, all intercepted

(mirrored) packets are encapsulated before forwarding to the LIMF.
The upstream / downstream traffic to the user is not impacted by enabling lawful
interception on the user. The intercepted traffic is forwarded to the LIMF by means
of tunneling techniques. It is possible to set the priority of the intercepted packets.
16 — ATM Pseudowire emulation
16.2 Solution description 16-2
16.3 Cell concatenation 16-3
16.4 QoS 16-4
16.5 Known restrictions 16-4
16.6 Support on the ISAM 16-4
16.1 Introduction
When migrating from an ATM-based access network to an Ethernet packet-based

access network, operators are faced with the challenge to maintain their existing
ATM-based services. Many ATM services are based on AAL5 encapsulation (that
is, these services are packet-based) and are rather straightforward to migrate by
terminating the AAL5 layer in an Ethernet Access Node. However, also
non-AAL5-based ATM services are commonly used, in which case this is not
possible. Moreover, an operator offering wholesale services to 3rd party service
providers has no view on the legacy ATM services that are used by the wholesaler.
The ISAM supports ATM Pseudowire (ATM PWE3) technology on a number of
ADSL2+ and SHDSL LT boards. This enables the transport of legacy ATM services
over a packet-based access network.
16.2 Solution description
The ATM Pseudowire network architecture is shown in Figure 16-1.
Figure 16-1 ATM Pseudowire network architecture

Protocol stack
ATM
VLAN or S-VLAN
PWE3
MPLS Pseudowire
VLAN
IP DSLAM ATM PVC
PWE3 in N:1
8/35 mode with N > 1
80/32
PWE3 GW
Residential
8/35
80/33
Aggregation Network
8/35
80/32
80/34 80/33
80/34
8/35 90/32
OLO with shared
90/32
bandwidth
9/40 90/33 90/33

8/35 VLAN A 90/34
90/34
92/32
92/32 92/33
8/35
OLO with dedicated
bandwidth/business
92/33 93/33
8/36
8/35 93/33 94/33
8/35 94/33
PWE3 in N:1
mode with N = 1
The “ATM Pseudowire” feature is based on IETF RFC 4717, and is also referred to
as ATM Pseudowire Emulation Edge to Edge (ATM PWE3). In this mode, the ISAM
can receive upstream ATM traffic from DSL subscribers and encapsulate this traffic
into one or more ATM Pseudowires sent over an MPLS tunnel towards the
aggregation network. On the other side of the network, a Pseudowire Gateway (for
example, the Alcatel-Lucent 7750) terminates the ATM Pseudowires from several
ISAMs and aggregates the traffic on one or more STM-1 interfaces connected to the
ATM core network.
In downstream direction, the PWE3 Gateway encapsulates the received ATM traffic
into the corresponding ATM Pseudowires, and sends them in MPLS tunnels towards
the different ISAMs. The ISAM terminates the MPLS tunnels and ATM
Pseudowires, extracts the ATM cells and sends them on the correct DSL line.
The feature co-exists with the standard ISAM L2 forwarding behavior, that is, on the
same ISAM LT board some user ports can be configured as regular Ethernet / AAL5
lines while other user ports can be configured for ATM Pseudowire handling.
Each ATM Pseudowire can be configured to either carry traffic from a single ATM
PVC or from multiple ATM PVCs:
• “N-to-One mode, with N=1”: the ATM Pseudowire only carries traffic from a
single ATM PVC. Each ATM Pseudowire packet either contains a single ATM
cell, or multiple ATM cells all using the same VPI/VCI
• “N-to-One mode, with N>1”: the ATM Pseudowire carries traffic from multiple
ATM PVCs. Each ATM Pseudowire packet either contains a single ATM cell, or
multiple ATM cells using the same or different VPI/VCIs
In order to establish the MPLS tunnels and ATM Pseudowires, the ISAM supports
the necessary commands to configure the connections.
It should be noted that the ATM Pseudowire functionality is supported on the DSL
LT board, with no intervention of the NT card. As a result of this, each DSL LT board
which offers ATM Pseudowire services will have to be configured with one or more
separate IP interfaces and MPLS tunnels. This increases the total number of MPLS
tunnels at the system level. For instance, if each DSL LT board would be configured
with one MPLS tunnel, then there will be 16 MPLS tunnels at system level.
16.3 Cell concatenation
In case each ATM cell is encapsulated in a separate ATM Pseudowire packet, the
additional overhead of the MPLS header can become very high, making the solution
less bandwidth efficient. To avoid this, it is possible to group multiple ATM cells
into a single ATM Pseudowire packet. This “cell concatenation” feature reduces the
encapsulation overhead, making the solution more bandwidth efficient.
The maximum number of ATM cells that may be concatenated into a single ATM
Pseudowire packet can be configured. Up to eight cells can be concatenated.
Configuring a high value of cell concatenation could result in putting an additional
transmission delay on the ATM cells, since the ATM Pseudowire packet would only
be sent out once the ATM Pseudowire packet has been filled up to its maximum
number of concatenated cells. To avoid excessive transmission delays, the maximum
additional transmission delay that may be put on the ATM cells can be configured.
When the configured transmission delay is reached, the ATM Pseudowire packet
will be sent out, regardless of whether or not it contains the maximum number of
concatenated cells.
16.4 QoS
The QoS implementation is based on the regular DSL LT QoS framework. All QoS
features are packet-based, not ATM cell-based. QoS is based on the use of the
Ethernet priority bits and the MPLS Exp bits. This means there is no ATM QoS, no
cell-based QoS, and no F4/F5 termination. Different service types can be defined
which are identified with different Ethernet p-bits or MPLS Exp bits. This allows
mixing Residential/shared bandwidth and Business/dedicated bandwidth services
over the ATM Pseudowires.
When mapping ATM cells into an ATM Pseudowire packet, the ISAM supports
setting the p-bits and MPLS Exp bits of those packets according to a two-rate Three
Color Marker. Policing can be done on a combination of the Committed Information
Rate (CIR) and the Excess Information Rate (EIR).
In downstream direction, color-aware RED can be applied to the different queues, in
order to discard traffic with a relative lower priority.
16.5 Known restrictions
The MPLS control plane is not supported. In other words, MPLS tunnel and ATM
Pseudowire configuration needs to be provisioned rather than signaled.
Note — Please consult the Customer Release Notes for additional

details concerning the restrictions of the ATM Pseudowire Emulation
implementation.
16.6 Support on the ISAM
The ISAM supports configuring ATM Pseudowires (ATM PWE3) in combination

with the NANT-A Network Termination board.
A. Cross-domain solutions
A.1 Overview A-2
A.2 Mobile backhaul A-4
A.3 E1/T1 Leased Line Replacement A-11
A.4 E1/PRA Interfaces on ISAM A-15
A.5 Ethernet Business Access over ISAM A-21
A.6 ISAM Backhaul (Rural DSL, Ultra-high Broadband) A-26
A.7 Hospitality solution A-32
A.8 Open Community Broadband for Smart Communities A-38
Alcatel-Lucent 7302 ISAM | 7330 ISAM FTTN | 7356 ISAM FTTB R4.4.02 July 2012 A-1
A.1 Overview
This section provides a description of various applications for which the ISAM
provides an effective solution.
Mobile Backhaul
Fixed operators and converged fixed/mobile operators can benefit from leveraging
cost-optimized residential broadband access infrastructure for backhauling traffic
from mobile base stations. The ISAM access node, in cooperation with dedicated cell
site devices fulfills the requirements for backhaul of 2G/3G and LTE base stations in
terms of bandwidth, TDM/ATM/ETH service delivery, high availability, QoS and
base station synchronization; for data as well as for mission critical voice services,
and this for the range of DSL, and point-to-point fibre access technologies.
E1/T1 Leased Line Replacement

Legacy E1/T1 leased line services can be converged over the modern IP DSLAM.
This allows to decommission legacy line systems or ATM DSLAMs. The ISAM
access node, in combination with a pseudowire capable device at the business
premises fulfills the requirements for leased line replacement in terms of bit error
rate, delay, availability and synchronization.
Ethernet Business Access

Access and service providers are migrating the delivery of business access services,
originally dominated by TDM and ATM-based offerings, to Ethernet access. This
migration is driven mainly to achieve converged access and aggregation networks,
thereby reducing CAPEX and OPEX. In a fully converged access network, we
expect residential-, business- and mobile backhaul customers to be served from the
same access node. The ISAM, in conjunction with a portfolio of CPEs/NTU/ONTs
is equipped with best-in-class features to fulfill the requirements for Ethernet
business access services, and this over a choice of copper and fiber access
technologies.
ISAM Backhaul (Rural DSL, Ultra-high Broadband)

The ISAM (remote or CO) relies on the availability of Gigabit Ethernet fiber to
provide uplink network connectivity. In some cases this fiber is not available. This
is typically the case in rural areas or emerging and developing countries. But this is
also true for industrialized countries having fiber-dark-spots. For both cases a
solution can be proposed allowing broadband deployment with ISAM in all areas.
For rural areas and industrialized areas different bandwidth requirements apply and
hence different architectural solutions can be proposed.
Hospitality solution
To remain competitive in their market segment many hoteliers are looking to
increase the overall guest experience in their hotel. The ISAM can provide
triple-play and enhanced media applications in the hotel guest room, conference
rooms, lobby, and so on, by leveraging on the existing copper wiring (Cat3). The
existing Cat3 wiring, currently used for Voice (PABX), can be enabled with xDSL
without rewiring or other labor cost.
A-2 July 2012 Alcatel-Lucent 7302 ISAM | 7330 ISAM FTTN | 7356 ISAM FTTB R4.4.02
Open Community Broadband for Smart Communities

The aim of the Open Community Broadband solution is to offer a very flexible
wholesaling framework allowing sharing of access and aggregation infrastructure by
multiple service providers allowing end-users to pick-and-play in flexible and
on-demand way.
A.2 Mobile backhaul
Scope
This section describes solutions for backhaul of 2G/3G and LTE mobile base stations
over ISAM 7302/7330/7356/7360.
Mobile backhaul over (bonded) ADSL2+, over (bonded) SHDSL, over (bonded)
VDSL2, over point-to-point Ethernet (FE/GE) is included, covering solutions for
data off-load as well as full backhaul of voice and data.
Apart from the ISAM 7302/7330/7356/7360 node, the solution also proposes the cell
site devices (residential DSL CPE, dedicated DSL CPE for business/mobile
backhaul, 7705 SAR-F/7705 SAR-M) for which the solution is validated.
Apart from this, an end-to-end mobile backhaul solution also requires an aggregation
network and a gateway device that interfaces to the mobile gateways. These are not
specified here. Please refer to the Alcatel Lucent Mobile Backhaul Blueprint
Solutions for a description of Alcatel Lucent end-to-end mobile backhaul solutions.
Introduction
Mobile backhaul (mobile backhaul) is about transporting traffic between mobile base
stations (2G BTS, 3G NodeB, LTE eNodeB) and a centralized mobile gateway (2G
BSC, 3G RNC, LTE S-GW).
Mobile backhaul comes from a legacy of 2G base stations, carrying low volumes of
traffic (voice and low BW data) and backhauled over a TDM (PDH/SDH) network,
with first mile access to the TDM network typically over 1 or 2 copper (or
microwave) E1/T1. The TDM network inherently provided synchronization as well
as resilience and QoS for mission critical services.
With the growth of data services in 3G and LTE, traffic volumes are increasing
rapidly and exponentially and mobile operators need more bandwidth fast. On the
other hand, mobile ARPU is more or less flat and consequently there is pressure on
the cost per bit, also for backhaul. The legacy TDM backhaul infrastructure cannot
scale in a cost effective way.
The following evolutions are happening:
• transition from copper (and TDM microwave) to fibre (and packet microwave) in
mobile backhaul access, at a pace allowed by investment levels
• transition from TDM transport to packet transport (carrier Ethernet, IP/MPLS)
• convergence of residential/business/mobile backhaul over a common transport
infrastructure (the High Leverage Network)
In this context there is a clear incentive for fixed access operators to leverage
residential broadband assets (existing or new rollouts) for mobile backhaul.
Using broadband access technologies for mobile backhaul allows to re-use existing
outside plant (copper). Moreover, broadband access technologies (DSL,
point-to-point Ethernet) are existing, cost optimized platforms and will enable
significantly reduced port cost per mobile base station/mobile site.
Technical challenges
The following technical challenges arise when leveraging broadband access
infrastructure for mobile backhaul:
Bandwidth
Mobile backhaul bandwidth requirements have evolved from 1-2 E1/T1 (2-4Mbps)
for a 2G site to more than 250Mbps for a full blown multi-provider, multi-generation
2G/3G/LTE site.
With respect to this bandwidth evolution, the different broadband access
technologies can be positioned as follows:
• (bonded) ADSL2+ and (bonded) SHDSL can be positioned as short-to-mid
term tactical solutions for 3G bandwidth relief. For example, four pair bonded
g.SHDSL.bis can support symmetrical bandwidth up to 22.8 Mbps. ADSL2+
deployment will in practise be limited to data off-load, while SHDSL can and will
typically be used in full off-load scenarios (*). For SHDSL, ATM IMA and EFM
bonding are preferred for reasons of resiliency (if one pair goes down, the group
will not be impacted). Of the two, EFM bonding is superior with respect to
bandwidth efficiency, provisioning and flexibility in data rates for the different
pairs.
• For example, with bandwidths of ~ 400/100 Mbps downstream/upstream at 500
m, 250/50 Mbps downstream/upstream at 1000 m for 8-pair bonded VDSL2,
bonded VDSL2 is a strategic, rather than a tactical solution for evolution to and
including LTE. VDSL2 could be deployed in off-load scenarios but definitely
have full backhaul as the final goal (*).
• Point-to-point fibre is a full-blown solution capable of supporting all scenarios
to LTE. Again, point-to-point fibre could be deployed in off-load scenarios but
definitely has full backhaul as the final goal (*).
Note — (*): See the section on “QoS and High Availability for
mission critical traffic” for distinction between data off-load and full
backhaul.
Access node features: Physical layer interfaces, DSL bonding.
TDM/ATM/Ethernet service delivery

2G base stations have TDMoE1 interfaces. 3G base stations can come in any of 3
flavors: all ATM IMAoE1, hybrid ATM IMAoE1 (for voice) and Ethernet (for data),
all Ethernet. LTE base stations have all Ethernet interfaces. Typically, 2G/3G/LTE
base stations will be collocated on a single site and will be backhauled over a
common access link.
Transport of TDM and ATM services over a packet network (potentially along with
Ethernet service) requires the use of pseudo wires (PWE3 TDM/ATM/Ethernet
pseudo wires for IP/MPLS, MEF-8 TDM pseudowire for Carrier Ethernet). Pseudo
wires are typically set up between by a dedicated cell site gateway (CSG) device at
the cell site and a peer device at the mobile controller site.
Access node features: Transparent for the access node.
Synchronization
Base stations with legacy E1 interfaces need frequency synchronization for the
purpose of TDM transport (that is, to avoid frame slips).
All base stations also need frequency synchronization for the purpose of providing
an accurate wireless carrier frequency.
In addition, Time Division Duplex (TDD) base stations need phase synchronization
for the TDD mechanism to operate. Frequency Division Duplex (FDD) systems may
also need phase synchronization for specific advanced wireless features like MBMS
and network MIMO, but deployment of these must be considered longer term and is
of no immediate concern.
Base stations can be synchronized in multiple ways:
• using a synchronized E1/T1 from a TDM network (frequency synchronization
only)
This is the synchronization method in the legacy TDM network. It is also the
synchronization method in a data off-load approach, where synchronization (and
voice) remain to be transported by the TDM network, but data is off-loaded to the
packet network.
• using an on-site GPS (frequency and phase synchronization)
This is the synchronization mechanism in CDMA and will most likely be the first
synchronization mechanism in TDD and FDD deployments requiring phase sync.
• using synchronization from the packet network
These synchronization methods classify in 2 flavours:
• Physical layer mechanisms
These provide end-to-end synchronization on the physical layer. Several physical
layer synchronization mechanisms are standardized: NTR for DSL, SyncE for
Ethernet.
• Packet layer mechanisms
These include NTP, 1588v2 point-to-point, ACR, DCR. Of these, 1588v2 is the
more forward looking with evolution to provide phase synchronization as well as
frequency sync.
In contrast to packet layer mechanisms, physical layer mechanisms are inherently

deterministic and insensitive to network traffic load conditions and QoS design.
It is recommended to use physical layer synchronization mechanisms whenever
available. That is, BITS or SyncE into the ISAM in CO and physical layer
synchronization (NTR, SyncE) from there to the business site. If no BITS or SyncE
is available in the CO, we recommend to terminate 1588v2 in an external client in
the CO, to feed the output of that client into the BITS of the ISAM and to go with
physical layer synchronization from there.
Access node features:
• NT with BITS/SyncE in
• DSL NTR/SyncE on the last mile.
QoS and High Availability for mission critical traffic

Today, mobile operators have mission critical voice services running over a TDM
backhaul network, with stringent guarantees for loss, delay, jitter and availability
provided by the PDH/SDH network.
By no means should these guarantees be impacted when moving to a packet based
backhaul.
A conservative approach is to move into a data off-load scenario as a first step: voice
and synchronization remain on the TDM network, whereas high volume data traffic
(with less stringent QoS requirements) is off-loaded to the packet network.
In the full backhaul scenario, the mobile backhaul solution needs to provide QoS and
High Availability inherently.
• The ISAM access node, being already engineered for triple play services is well
positioned to provide differentiated QoS for mobile voice and data traffic streams
of varying nature, also in competition with residential and business traffic in the
same node.
• In terms of High Availability, prime concerns are focused on the network links
and - elements that aggregate a (large) number of base stations and less so on the
first mile.
For these links/nodes, High Availability is taken care of by either IP/MPLS
mechanisms (possibly initiated from an IP/MPLS capable cell side device) or
carrier Ethernet mechanisms, or a mixture thereof. Dual homing of the access
node to the aggregation network is essential for protecting the second mile (with
LAG or xSTP) and the first aggregation node (with multi-chassis LAG or xSTP).
DSL bonding inherently provides a level of resiliency for a first mile over bonded
DSL.
Figure A-1 High availability: points of failure

ISAM dual uplinks with LAG,
multi-chassis LAG, mSTP
ISAM NT
redundancy
TDM
ATM AGG GTW
ETH
CSG AN L2 aggregation
AGG GTW
Base station Controller
inherent redundancy in DSL bonding
IP/MPLS or Carrier
Ethernet repair mechanisms

• QoS (as for triple play)
• NT redundancy
• dual homed ISAM uplinks (with LAG, multi-chassis LAG or xSTP)

• transparent for IP/MPLS based redundancy (handled in the cell site gateway
and/or in the IP/MPLS core)
Demarcation
End-to-end OAM features and SLA monitoring (including the first mile) are
typically handled by the cell site gateway device, either by IP/MPLS mechanisms or
by carrier Ethernet mechanisms. 802.1ag and Y.1731 can be used between the cell
site device and the gateway device for end-to-end checks of connectivity, loss and
delay, either on a continuous basis or on-demand. Optionally, 802.1ag MEPs and
MIPs can be placed in ISAM for further troubleshooting and fault isolation.
• Transparent for end-to-end IP/MPLS OAM and 802.1ag/Y.1731 OAM
• Optional 802.1ag MIP/MEPs in the access node for troubleshooting.
Solution description
Figure A-2 shows the different access options for mobile backhaul over ISAM and
the associated cell site gateway portfolio.
Figure A-2 Mobile backhaul cell site device portfolio

ADSL2+ CPE (o)
1-2p ADSL2+
3 rd party SHDSL CPE

1-4p SHDSL
1-4p SHDSL + 1-2p xDSL
SAR-M combo 2p VDSL2

CellPipe 5Ve.A4010 (o)
7302/7330 ISAM
2-8p VDSL2 or 2p ADSL2+
SAR-M xDSL
point-to-point Ethernet (FE|GE)
SAR-M/SAR-F (o) offload only
Low-end residential type DSL CPEs (ADSL2+, 7130 Cellpipe VDSL2) are low-cost
solutions for data off-load of 3G base station Ethernet interfaces (for base stations
with hybrid ATM/Ethernet interfaces).
Dedicated 3rd party SHDSL CPEs for business/mobile backhaul can be positioned as
mid-range solutions for full backhaul of TDM, ATM and Ethernet services over
(bonded) SHDSL.
7705 SAR-F (fiber uplink) and 7705 SAR-M (with modular uplink of fiber), 2-8pair
bonded VDSL2, 4-pair bonded SHDSL + 2-pair bonded ADSL2+ (SAR-M combo)
are high-end solutions for off-load and full backhaul of TDM, ATM and Ethernet
services. 7705 SAR-F and 7705 SAR-M are IP/MPLS based.
Figure A-3 shows the logical end-to-end topologies for mobile backhaul between
multiple mobile base stations and a centralized mobile controller.
Figure A-3 Mobile backhaul end-to-end-topologies (logical)
IP/MPLS
TDM TDM
ATM ATM
ETH ETH
CSG AN AGG L2 tunnel (IP/MPLS) GTW

PWE3 IP/MPLS pseudowire (TDM/ATM/ETH)
Mixed
TDM TDM
ETH ETH
CSG AN AGG L2 tunnel (IP/MPLS) GTW

MEF8 PW (TDM) + raw Ethernet
Carrier Eth
TDM TDM
ETH Carrier Ethernet ETH
CSG AN AGG GTW

MEF8 PW (TDM) + raw Ethernet
The solution components are:

• A cell site gateway (CSG) that performs media adaptation between the base
station interfaces (TDMoE1, ATM IMAoE1, Ethernet) and the first mile physical
layer (DSL, point-to-point FE/GE) and initiates pseudo wires when applicable. In
addition, it can perform synchronization and demarcation functions when
applicable. On the network side, the cell site gateway can be either IP/MPLS
based (TDM/ATM/Ethernet PWE3 pseudo wires) or Ethernet based (raw
Ethernet + TDM MEF8 pseudo wires).
• The access node (AN) is typically operated in L2 transparent VLAN
cross-connect mode for mobile backhaul, with each cell site gateway or service
cross-connected to the first aggregation node.The access node is typically shared
with residential and possibly other business users.
• The aggregation network can be carrier Ethernet based or IP/MPLS based. In the
latter case IP/MPLS from the cell site gateway is typically tunneled in a L2
IP/MPLS service. A flat IP/MPLS model is also possible in principle, but requires
hybrid (access/MPLS) interfaces on the first aggregation node.
• A controller side Gateway Device (GTW), peering with the cell site gateway on
the pseudowire level and interfacing to the mobile controller(s) over TDM
STM-x, ATM STM-x or Ethernet interfaces.
Access nodes can be dual homed to redundant aggregation nodes and mobile
controllers can be dual homed to redundant gateway devices for High Availability
purposes.
Figure A-4 shows the physical layer synchronization architecture of ISAM.
Figure A-4 ISAM physical layer synchronization architecture (DSL and point-to-point)
BITS G.703 SHDSL.bis PHY NTR E1

FE/GE (SAR-M)
SHDSL
GigE FE/GE unsynchronized
LT 3rd party CPErd
SyncE 7705 SAR-M (3 party CPE)
Base station interface

NT
VDSL2 PHY NTR E1
FE/GE
VDSL2
LT
7705 SAR-M
Optical GE SyncE E1
FE/GE
PTP
GE LT
7705 SAR-M
8 kHz
backplane Optical GE SyncE Optical GE SyncE
to 7354 REM direct connection to base station
7302/7330 ISAM
Physical layer synchronization can be fed into ISAM either via BITS or via SyncE
from the network through synchronization-capable dedicated NT variants. If no
BITS or SyncE is available in the CO, we recommend to terminate 1588v2 in an
external client in the CO, to feed the output of that client into the BITS of the ISAM
and to go with physical layer synchronization from there.
Synchronization can then be propagated over the first mile to a
synchronization-capable cell site gateway through a physical layer mechanism:
SHDSL NTR, VDSL2 NTR, or SyncE (GE point-to-point LT board). 7356 ISAM
FTTB deployments also support physical layer synchronization from CO to the
cabinet through SyncE.
Finally, the cell site gateway provides synchronization to the base station either
through a synchronized E1 or through a SyncE interface.
The physical layer synchronization entails frequency synchronization only.
A.3 E1/T1 Leased Line Replacement
Scope
This section describes solutions for emulation of (E1/T1) leased line services with
access over ISAM over SHDSL, using 3rd party SHDSL CPEs (single or multiple
E1/T1 interface).
In principle, E1/T1 leased lines can also be emulated over point-to-point ethernet
access, with a dedicated fibre CPE.
Introduction
Operators may benefit from consolidation of legacy (E1/T1) leased line services on
broadband access equipment rolled out for residential (and business) services.
This may allow them to, for example, decommission dedicated line systems for
(E1/T1) leased line access. It may also be an element in an ongoing decommissioning
(partial of full) of the legacy TDM network in favour of a packet switched network.
Technical Challenges
Leased line emulation

TDM pseudowire technology is used for emulation of (E1/T1) leased line services
over a Packet Switched Network (PSN). Structured and unstructured E1/T1 can be
transported using RFC 4553 SAToP (Structure Agnostic TDM over Packet) and
RFC 5086 CESoPSN (Circuit Emulation Service over PSN) encapsulations
respectively. The TDM pseudowire can be transported over Ethernet (MEF8), over
MPLS, or over MPLS/GRE.
In this solution, TDM pseudo wires are set up between a dedicated device on the
customer premises (3rd party SHDSL CPE) and a peer device (either a peer CPE on
another customer site or a centralized device interfacing to the core TDM network,
usually over STM1/STM4).
Symmetrical bandwidth
Physical layer bandwidth requirements for transporting an E1/T1 will depend on the
encapsulation type (Ethernet, MPLS) and the TDM payload size in the pseudo wire,
but will amount to more than 2 Mbps symmetrical per E1/T1. In practise, for copper
access this (together with delay and synchronization requirements) rules out
ADSL2+ in favour of SHDSL. Bonded SHDL links, as well as SHDSL repeaters can
be used to increase the reach of SHDSL segments for leased line replacement. ATM
IMA and EFM bonding are preferred for SHDSL for reasons of resiliency (if one pair
goes down, the group will not be impacted). Of the two, EFM bonding is superior
with respect to bandwidth efficiency, provisioning simplicity and flexibility in data
rates for the different pairs.
Key Performance Indicators (KPIs) for loss and delay

The legacy TDM network guarantees stringent requirements for loss and delay for
TDM traffic. These cannot be impacted by moving to an emulated service over a
packet switched network under load (in competition with residential and other
business services).
The ISAM access node, being already engineered for triple play services (including
loss sensitive video and delay/jitter sensitive voice) is well positioned to provide low
loss/low delay guarantees.
SHDSL is a low latency technology that complies to delay requirements for leased
line.
Tuning of the payload size and de-jitter buffer size of the pseudo wire allows to meet
delay and loss requirements under background network packet delay variation
(PDV).
Synchronization
Both ends of an E1/T1 leased line connection need to be synchronized to avoid frame
slips in the TDM transport (that is, wander needs to comply to the ITU-T G.823
traffic mask).
This solution assumes a network clock is imposed upon the customer TDM
equipment.
For leased line emulation, the clock reference has to be distributed through the packet
network. As discussed in the mobile backhaul section, this can be done via physical
layer mechanisms (SHDSL NTR, SyncE) or via packet layer mechanisms (NTP,
1588v2 PTP, ACR, DCR).
It is recommended to use physical layer synchronization mechanisms whenever
available. For instance, BITS or SyncE into the ISAM in CO and physical layer
synchronization (NTR, SyncE) from there to the business site. If no BITS or SyncE
is available in CO, we recommend 1588v2 termination in a client in the CO and to
go with physical layer synchronization from there. This can be an external client
device that feeds into the BITS.
• NT with BITS/SyncE in
• SHDSL NTR on the last mile.
High Availability
In terms of High Availability, prime concerns are focused on the network links and
network elements that aggregate a (large) number of customers and less so on the
first mile. For these links/nodes, High Availability is taken care of by either
IP/MPLS mechanisms (possibly initiated from an IP/MPLS capable business CPE)
or Carrier Ethernet mechanisms, or a mixture thereof. Dual homing of the access
node to the aggregation network is essential for protecting the second mile (with
LAG or xSTP) and the first aggregation node (with multi-chassis LAG or xSTP).
DSL bonding inherently provides a level of resiliency for a first mile over bonded
DSL.

• NT redundancy
• dual homed ISAM uplinks (with multi-chassis LAG or xSTP)
• transparent for IP/MPLS based redundancy (handled in business CPE)
• inherent redundancy in DSL bonding (ATM IMA and EFM).
Figure A-5 shows the access components for a leased line replacement solution over
(bonded) SHDSL.
Figure A-5 Access components for E1/T1 leased line replacement
3 rd party SHDSL CPE

1-4p shdsl
1-4 * E1/T1 (+ Eth)
7302/7330 ISAM
3rd party SHDSL business CPEs provide circuit emulation for a single or multiple
E1/T1 (possibly in conjunction with Ethernet access) over SHDSL (single pair
g.SHDSL at max 2.3Mbps Mbps up to 4 pair EFM bonded g.SHDSL.bis at max 22.8
Mbps). The pseudo wire encapsulation is IP/MPLS with static MPLS labels. SAToP
and CESoPSN encapsulations are supported.
Figure A-6 shows the logical end-to-end topologies for leased line emulation
between 2 business customer sites.
Figure A-6 End-to-end topologies for E1/T1 leased line emulation
TDM pseudowire (MEF-8 or IP/MPLS)
E1 CPE/ Aggregation CPE/ E1

B-0404G AN AN B-0404G
ONT (ETH, IP/MPLS) ONT
Customer Customer
TDM equipment TDM equipment
TDM pseudowire (MEF-8 or IP/MPLS)
E1 CPE/ Aggregation(*) SDH E1

CES
B-0404G AN GTW
ADM
ONT (ETH, IP/MPLS)
Customer Customer
TDM equipment TDM equipment
(*): optionally, AN could also directly connect to CES GTW in CO
Two connectivity models can be envisaged and will possibly be deployed in parallel:
• A business CPE connected back-to-back over an end-to-end pseudo wire to a peer
business CPE, without crossing a SDH/PDH segment.
• A business CPE connected over a pseudowire to a core SDH/PDH network
(typically groomed over an STM1/STM4 interface). The pseudo wire could cover
the access segment only (with the pseudowire terminated and dropped on TDM
equipment in the CO). Alternatively, it could span the full metro Ethernet
aggregation network (TDM equipment in a centralized PoP location).

• A business CPE that performs media adaptation to the access technology
(SHDSL) and initiates/terminates the TDM pseudo wire(s). It will also perform
synchronization functions.
• The access node (AN) is typically operated in L2 transparent VLAN
cross-connect mode for leased line emulation, with each business CPE
cross-connected to the first aggregation node.The access node is typically shared
with residential and possibly other business and mobile backhaul users.
• The aggregation network can be carrier Ethernet based or IP/MPLS based. In the
latter case IP/MPLS from the cell site gateway is typically tunneled in a L2
IP/MPLS service. A flat IP/MPLS model is also possible in principle, but requires
hybrid (access/MPLS) interfaces on the first aggregation node. See section
“Mobile backhaul” for more details on the aggregation options.
• A CES gateway device (CES GTW) (not present in the back-2-back scenario),
peering with the TDM core network.
Access nodes can be dual homed to the aggregation network and SDH equipment can
be dual homed to redundant gateway devices for High Availability purposes.
In this solution, the customer TDM equipment is timed by the network clock. In the
second connectivity model, this is also the clock of the core TDM network. As per
the Alcatel-Lucent synchronization strategy, an end-to-end physical layer
synchronization is preferred. This means that physical layer synchronization is fed
into ISAM either via BITS or via SyncE from the network through synchronization
capable dedicated NT variants.
If no BITS or SyncE is available in the CO, we recommend to terminate 1588v2 in
an external client in the CO, to feed the output of that client into the BITS of the
ISAM and to go with physical layer synchronization from there.
Synchronization can then be propagated over the first mile to the business CPE over
SHDSL NTR.
Finally, the business CPE provides a synchronized E1/T1 to the customer TDM
equipment.
A.4 E1/PRA Interfaces on ISAM
Scope
This chapter describes the ISAM capabilities to terminate E1 TDM lines or ISDN
PRA (PRI) on an ISAM faceplate port. A similar approach is taken as in the previous
section “E1/T1 Leased Line Replacement”but with this difference that we are not
using a CPE or ONT to terminate the E1 but an SFP (Small Form-factor Pluggable)
instead. The E1 or the ISDN PRA is directly terminated on the ISAM. The ISAM can
be in a central office location or in a remote outdoor cabinet.
The E1 TDM SFP is terminating the TDM circuits and carrying the TDM data via
Ethernet packets through the ISAM and across a packet switched network (i.e. using
pseudowire technology). We are NOT referring to Trunking Gateway functionality
where PSTN data is converted into VoIP.
Introduction
The SFP (SmartSFP) used in this solution is a dual-channel TDM SFP, capable of
terminating up to two E1 ports. The SFP is MSA compliant and fits into a standard
Gigabit Ethernet SFP cage.
Figure A-7 Dual-Channel TDM Pseudowire SFP
E1
SFP cage
VLAN ECID PAYLOAD
CES
CES
E1 VLAN ECID PAYLOAD
RJ45 GE
shielded
connector
Via its build-in TDM pseudowire interworking function (CES), the SFP is
encapsulating/extracting TDM traffic into/from Ethernet packets. The Metro
Ethernet Forum standard (MEF-8) payload format and pseudo-wire (PW)
technology is used to allow interoperability with third-party CES interworking
devices.
Figure A-8 E1/PRA Termination (pseudowire) in ISAM: MEF8 interworking
Using an SFP-based approach provides a flexible and scalable solution for legacy
interfaces on the ISAM. No dedicated board is required, it is a port-based solution:
any GE SFP port can be converted in an E1/PRA port by plugging in the E1 TDM
PW SFP.
Fully integrated in the ISAM management system, the E1 TDM PW SFP can be
provisioned and monitored via ISAM CLI/TL1 and through the 5520 AMS.
Technical characteristics
Line termination
The E1 TDM PW SFP is a dual-channel SFP capable of terminating two independent
tributaries. Each tributary has its own pseudowire to transport its TDM data across
the packet switched network.
The connector type of the SFP is a shielded RJ45 connector which is standard pin
compliant for a single E1. If two E1 needs to be terminated on the RJ45 connector a
dedicated Y-split cable is required to terminate the 2nd E1.
The E1 line impedance can be configured to 75Ω or 120Ω. An unbalanced (Coax) or
balanced (RJ45) cable is provided according the requested line/impedance type.
The TDM line interface supports both framed (LOF and CRC4 checks only) and
unframed E1.
Depending on the distance requirement the receiver sensitivity can be configured for
Short Haul or Long Haul applications.
Pseudowire capabilities
As shown in Figure A-7, a pseudowire is applied per tributary. The pseudowire is
constructed according to the implementation agreement for the emulation of PDH
circuits over Metro Ethernet Networks (MEF8).
Although the line interface framer supports both framed and unframed lines, the
pseudowire encapsulation is structure-agnostic. The TDM payload is backhauled
transparently via the pseudowire over the packet switched network.
Due to the structure-agnostic emulation only, DS0 grooming or fractional E1
backhaul is not supported.
The tributary pseudowire will be uniquely identified via its circuit-identifier in
compliance with MEF8. Dedicated VLAN, CoS priority, source and destination
MAC addresses can be configured per pseudowire (per tributary) if required.
Synchronization
To meet the TDM wander requirements (per ITU-T G.823), both ends of the
pseudowire connection need to be synchronized.
Different options exist to provide an end-to-end solution to synchronize the
interconnected circuits (E1/PRA). The solution requires a PRC-traceable network
clock to be provided to the E1 TDM SFP. There are several ways in providing the
network clock (derived from PRC) to the SFP. This is depending on the node (NT)
features where the SFP is residing. Depending on the controller type of the ISAM,
the NT can be synchronized via BITS, SyncE or IEEE1588v2. Through the
backplane clock circuit, all boards in the shelf are being synchronized. The
synchronization of the SFP itself is done via SyncE (SERDES) to provide the
network timing from the NE (ISAM).
The network clock can be imposed upon the customer TDM network, both tributaries
of the SFP can be synchronized from the SFP (host) clock which is derived from the
network clock via SyncE, as described above.
Alternatively, the SFP can take one of the E1s as clock source.
The 2E1-SFP solution in ISAM does not support the transport of the E1 service clock
across the packet network.
An overview of the different synchronization options in an end-to-end solution is
provided in Figure A-9.
Figure A-9 E1 TDM SFP, End-to-End Synchronization options
Alarms
E1 and TDM related alarms detected by the SFP are autonomously reported to the
ISAM and AMS. On request the operator can also retrieve the active alarms on the
SFP through the ISAM.
Depending on the configuration of the E1 line interface, whether in framed or
unframed mode additional alarm detection and reporting is supported. In unframed
mode, the SFP supports LOS and AIS detection. In the framed mode, the SFP can
also detect RDI, REI, LOF, LOMF and CRC4 bit failure on top of the LOS and AIS.
Besides the alarm detection and reporting, the SFP allows also the forwarding of
alarms, either towards the network via circuit emulation (MEF8) or towards the line
interface (E1). The forwarding of alarms can be configured per alarm (AIS, RDI and
REI) and for each direction (network or E1) independently.
Service diagnostic capabilities

Loopbacks
The 2E1-SFP supports different type of loopbacks. Loopbacks can be activated in
both, E1 and packet network direction. In each direction, loopback points can be set
on different places on the SFP, e.g. framer only, including the pseudowire
interworking function or not. The following loopback options are supported:
• Loopbacks towards E1 (see Figure A-10):
• Loopback towards E1 line interface without including the framer function
• Loopback towards E1 line interface, including the framer function
• Loopback towards E1 on SGMII, including the framer and CES IWF.
• Loopbacks towards packet network (see Figure A-11):

• Loopback towards Ethernet network, passing the CES IWF, without including the
framer
• Loopback towards Ethernet network, passing the CES IWF and including the framer
• Loopback towards Ethernet network on SGMII. This loop will be in front of the CES
IWF and only does the MAC address swap on the pseudowire packets.
• Loopback on SERDES towards Ethernet network, not passing any function of the
SFP.
Figure A-10 2E1-SFP loopback towards E1 (including framer)
FRAMER
SERDES
ETH-ITF
CESoP
SGMII
(IWF)
LIU
E1 ISAM (PSN)
Figure A-11 2E1-SFP loopback towards network (including framer)

FRAMER
SERDES
ETH-ITF
CESoP
SGMII
(IWF)
LIU
E1 ISAM (PSN)
Performance monitoring via E1 CRC4 checks

For framed E1 the 2E1-SFP can perform bit error monitoring through CRC4. When
the CRC4 check is activated, the SFP will raise a CRC4 alarm when a frame with bad
CRC has been received.
An additional CRC4 threshold alarm is raised when the bad CRC4 frame count
reaches a certain threshold (currently set to 915 frames).
TDM Pseudowire packet-loss detection
The 2E1-SFP has ability to detect packet-loss on the pseudowire. A time window (in
msec) can be configured in which packet-loss is being monitored.
In case a loss of packet is detected a LOS (from IWF) is asserted. When in the same
window no packet-loss is detected anymore, the LOS alarm is de-asserted.
A specific packet-loss LOS alarm is supported per tributary pseudowire.
The picture below illustrates possible deployment scenarios. In summary, the E1
TDM SFP based solution:
• Is providing a flexible pluggable solution: pay as you grow
• Leverages on existing ISAM and Ethernet based aggregation/service network for
TDM (V)LL for TDM service/network migration resulting in CAPEX and OPEX
savings.
• Is a scalable solution: SFP based, no need for dedicated board which consumes a
full slot.
• Supports solid synchronization through Synchronous Ethernet
• Is fully integrated in the ISAM provisioning system and element manager (5520
AMS)
• Is ITU (E1) compliant
• Uses MEF8 encapsulation ensuring transparency to any TDM networking
protocol
Figure A-12 Solution Description ISAM E1/PRA backhaul
A.5 Ethernet Business Access over ISAM
Scope
This section describes solutions for Ethernet business access over ISAM:
• Over (bonded) SHDSL, using a 7230 BG 3Se Series Cellpipe CPE, 1521 CLIP,
7705 SAR-M(E) combo or a third party SHDSL business CPE/NTU at the
customer premises.
Introduction
Access and service providers are gradually migrating the delivery of business access
services, originally dominated by TDM and ATM-based offerings, to Ethernet
access.
This migration is driven mainly to achieve converged access and aggregation
networks, thereby reducing CAPEX and OPEX. In a fully converged access network,
we expect residential-, business- and mobile backhaul customers to be served from
the same access node.
The ISAM, in conjunction with a portfolio of CPEs/NTUs/ONTs is equipped with
best-in-class features to fulfill the requirements for Ethernet business access
services, and this over a choice of copper and fiber access technologies.
Technical Challenges
Bandwidth
Ethernet business access subscribers may have bandwidth requirements varying
anywhere from a few Mbps up to 1Gbps. A scalable solution tailored to the
bandwidth needs is required. Bandwidth requirements for Ethernet business access
are mostly symmetric (except for business internet access).
ISAM provides high symmetrical bandwidth over SHDSL by means of g.SHDSL.bis
(up to 5.7 Mbps per copper pair over 3km nominally) and g.SHDSL.bis bonding (up
to 8 pairs for ATM IMA; up to 4 pairs for PTM (providing a bandwidth of 22.8 Mbps
nominally)). Of the bonding flavors, ATM IMA and PTM bonding are preferred for
reasons of resiliency: if one pair goes down, the group will not be impacted. Of the
two, PTM bonding is superior with respect to bandwidth efficiency, provisioning
simplicity and flexibility in data rates for the different pairs.
Access node features: g.SHDSL.bis and SHDSL bonding.
Ethernet Business Service Delivery

The Ethernet business services that this solution covers include:
• L2 VPN (E-LINE, E-LAN, E-TREE)
• L3 VPN
• Business Internet Access (BIA)
In each of these service models, the function of the business CPE/NTU/ONT and the
access node is to provide a layer 2 access spoke to an aggregation network
implementing the layer 2 service (L2 VPN) or connecting to the layer 3 router (L3
VPN, BIA).
Figure A-13 Ethernet Business Service Delivery
inter-metro
CPE L2 VPN
ETH
or AN AGG L2 aggregation inter-metro
NTU
L3 VPN
Customer
router internet
BIA
L2 access segment L2 aggregation
virtual line or virtual LAN
carrier Ethernet or IP/MPLS
Ethernet business services may be offered with varying levels of functionality and
quality; from low-end basic connectivity to high-end service delivery governed by
stringent SLAs.
For L2 VPNs (and in extrapolation also for the layer 2 access to L3 VPN and BIA
services), the Metro Ethernet Forum (MEF) provides a framework for the definition
of layer 2 services at the UNI between the customer equipment and the service
provider, and this for all but the more basic connectivity services.
MEF Service Requirements at the UNI (MEF6.1, MEF10.2) specify such things as:
• Service types: E-LINE, E-LAN, E-TREE.
• Service multiplexing and service selection: all:1, 1:1, n:1 VLAN mapping.
• Transparency for customer frames (VLANs, MTUs, L2CP, multicast/broadcast
and so on)
• Layer 2 control protocol (L2CP) handling: discard, tunnel, peer
• Ingress and Egress bandwidth profiles and - rate limiting.
Service Requirements at the UNI (MEF of other) can be implemented by either of
two architectures:
• In the UNI model, the UNI requirements are implemented by the access node LT
board. The customer premises device connecting to the customer router can be a
simple CPE or media convertor with basic functionality.
• In the NTU model, the UNI requirements are implemented by a dedicated,
operator managed NTU/ONT at the customer premises. The NTU/ONT has
enhanced demarcation features over a simple CPE/media convertor and is
possibly MEF-certified. The access node should be transparent in this model.
Figure A-14 Implementing service requirements at the UNI

UNI model
UNI
Customer site
UNI-N
ETH
CPE/MC AN L2 aggregation
Customer
router
NTU model
UNI
Customer site
UNI-N
ETH
NTU AN L2 aggregation
Customer
router
As a particular instance of the service requirements at the UNI, full transparency for
customer frames is required for particular L2 VPN service delivery models (for
example, Ethernet private lines). Transparency requirements may pertain to such
features as preservation of customer VLAN tags (including 802.1q p-bits), support
of customer MTUs, transparency for multicast/broadcast and for L2CP protocols that
the customer wants to use to manage his network end-to-end (like LACP, (m)STP
and so on).
ISAM implements full transparency for customer frames, by making use of
transparent VLAN cross-connect forwarding mode.
• UNI model: transparent VLAN cross-connect (1:1, tunneling mode, mapping
mode), L2CP handling (discard, tunnel), MTUs, ingress rate limiting
• NTU model: transparency of VLAN cross-connect
High availability
In terms of high availability of the Ethernet business service, prime concerns are
focused on the network links and elements that aggregate a (large) number of
customers (ISAM node and ISAM uplinks, aggregation nodes and aggregation links,
edge routers implementing L3VPN or BIA), and less so on the first mile.
Figure A-15 High Availability: points of failure
ISAM dual uplinks with LAG,

multi-chassis LAG, mSTP
ISAM NT
redundancy
AGG
CPE/
NTU AN L2 aggregation
AGG
Customer
router
IP/MPLS or Carrier
Ethernet repair mechanisms

• NT redundancy
• dual homed ISAM uplinks
• Ethernet based redundancy (with LAG, multi-chassis LAG or xSTP)
• inherent redundancy in DSL bonding (ATM IMA and EFM bonding).
QoS
Business services come with more or less stringent SLAs governing QoS KPIs of
bandwidth, loss, delay and jitter for the service or services presented at the UNI. In
general, business traffic will have to compete with residential traffic (and possibly
mobile backhaul traffic) running in the same access node.
The ISAM access node, being already engineered for triple play services is well
positioned to provide differentiated QoS for business traffic streams of varying
nature, also in competition with residential and mobile traffic in the same node.
• Ingress policing/color marking
• four queues per port
• QoS marking.
OAM, including SLA monitoring

Stringent SLAs on Ethernet service availability (% availability, maximum time to
restore, and so on) require that operators have tools for connectivity fault monitoring
and -troubleshooting.
Also, business access customers may require SLA monitoring and SLA reporting
(availability, loss, delay, jitter).
In carrier Ethernet, 802.1ag/Y.1731 connectivity fault monitoring and its Y.1731
extensions for performance monitoring provide the means for above OAM functions.
• Transparency for end-to-end 802.1ag/Y.1731 OAM PDUs
• Optional 802.1ag MIP/MEPs in the access node for troubleshooting
Figure A-16 shows the solution components for Ethernet business access over
(bonded) SHDSL using ISAM 7302/7330.
Figure A-16 Ethernet Business Access Portfolio

1-4p SHDSL
1521 CLIP
or 3 rd party SHDSL NTU/CPE
1-4p SHDSL + 1-2p xDSL

7302/7330 ISAM
SAR-ME combo
Low-end SHDSL CPEs are low-cost solutions for basic ethernet business access
services, using UNI-N functionality of the ISAM SHDSL LT board.
1521 CLIP, 7705 SAR-ME combo and dedicated 3rd party SHDSL NTUs can be
positioned as mid-range to high-end solutions for SHDSL access in an NTU
architecture.
For the logical end-to-end topologies for Ethernet business services (L2VPN,
L3VPN, BIA), see Figure A-13.
• A customer router that connects to the L2 VPN/L3 VPN/BIA service. The
customer router is beyond the responsibility of the business access provider.
• A provider managed NTU at the customer premises, or a simpler CPE/media
convertor.
In the NTU model, the service selection is fully performed by the NTU, adding a
per-service VLAN. The NTU also performs other UNI-N functions (L2CP
handling, ingress rate limiting, and so on) as well as non-UNI-N functions
required for service assurance (connectivity monitoring, SLA monitoring, and so
on).
• The access node (AN) cross-connects customer traffic to a per-service VLAN.
In the NTU model, this is a 1:1 cross-connect of the service VLAN added by the
NTU. In VLAN cross-connect mode, full transparency for customer frames is
assured.
In the UNI model, the service selection (all:1, 1:1, n:1) is performed by the ISAM
LT board, along with other UNI-N functions.
The aggregation network implements either a point-to-point service (E-LINE) or a

LAN service (E-LAN). This L2 aggregation function is valid, both for a L2 VPN
service as for the L2 aggregation function towards a L3 edge router implementing a
L3 VPN or BIA service. Local bridging in ISAM is not required to implement an
E-LAN service. Instead, a L2 spoke through the CPE/NTU and ISAM to the first
aggregation node can be implemented, while the aggregation network takes on the
E-LAN functionality.
The aggregation network can be either carrier Ethernet or IP/MPLS. In the case of
IP/MPLS based aggregation, the first aggregation router performs the MPLS PE
function.
For L3 VPN and BIA services, an edge router at a PoP location takes on the L3
functions and is fed by the L2 aggregation network. The L3 function could also be
distributed.
In terms of high availability, the access node can be dual homed to a single
aggregation node or to redundant aggregation nodes (with LAG, multi-chassis LAG
or xSTP).
The aggregation network is protected by either carrier ethernet or IP/MPLS based
resiliency mechanisms with no dependency on the access segment.
Access to resilient L3 edge routers is either handled by the customer router or by the
L2 aggregation network and has no dependency on the access segment.
For SHDSL, ATM IMA bonding and PTM bonding inherently provide a level of
resiliency for the first mile.
In terms of QoS, the ingress bandwidth enforcement (optionally including color
marking) is performed by the NTU in the NTU-model and by the ISAM LT board in
the UNI-model. The regular ISAM QoS features enable differentiated treatment of
business traffic in competition with residential and mobile traffic inside the node as
well as correct marking of packets for further QoS treatment in the aggregation
network (upstream) or in the NTU (downstream).
In terms of OAM, end-to-end monitoring of the business access service (including
the first mile) is typically handled between an NTU at the customer premises and
either a peer NTU (for L2 VPN) or the edge router at the PoP location (for L3 VPN,
BIA). 802.1ag and Y.1731 can be used for end-to-end checks, either on a continuous
basis (connectivity fault monitoring, SLA monitoring) or on-demand
(troubleshooting). The ISAM should be transparent for end-to-end 802.1ag/Y.1731
PDUs. Optionally, 802.1ag MEPS and MIPS can be placed in ISAM for further
troubleshooting and fault isolation.
A.6 ISAM Backhaul (Rural DSL, Ultra-high Broadband)
Introduction
The absence of fiber may not be blocking for remote ISAM deployments. Also in
fiber-poor areas, ISAMs for DSL broadband access can be deployed. Taking the
approach of backhauling the fiber-link (point-to-point Gigabit Ethernet) by an
alternative transport technology leaves no further constraints deploying the ISAM in
rural areas or other markets where the exclusive use (dark-fiber) of fiber is not
possible to connect the ISAM.
Depending on the market, available regional or national infrastructure or customer
requirements, we can distinguish possible domains:
• Rural areas (Broadband for all)
• Early/fast deployments in emerging markets re-using legacy (incumbent)
network
• Re-use of high-capacity national infrastructure
• Complementing fiber based FTTN deployment
The base of the solution is finding the best way for backhauling the Gigabit Ethernet
fiber link. The choice of the backhaul transport technology is depending on the
backhaul distance, the available infrastructure to leverage upon, regulations (for
example, in the case of wireless backhaul options) and required throughput.
The backhaul is accomplished by using a converter which converts the optical
Gigabit Ethernet transport layer into an other Ethernet-based transport layer
(illustrated by Figure A-17). The new transport layer consists of a physical layer
depending on the available infrastructure and a data-layer supporting the transport of
Ethernet frames. Depending on the different physical layers different framing
options apply: EFM (G.SHDSL), GFP (Generic Framing Procedure ITU-T G.7041),
HDLC (High-level Data Link Control ISO-13239, ML-PPP (Multi-Link
Point-to-Point Protocol RFC-1990), and so on.
Figure A-17 ISAM fiber backhaul

Optical Remote / Cabinet Location
Central Office / Aggregation
Distribution
Location
Network
7330 ISAM FTTN

ODF
7302 ISAM CO
ISP 1
7354/7324 ISAM RU
Aggregation Active Optical
Network Network
ISP 2 7330 ISAM CO
7356 ISAM REM
7330 ISAM RA
Ethernet
7357 ISAMSEM
Corporations
and Residences
Remote / Cabinet Location

Central Office / Aggregation
Backhaul option
Location
7330 ISAM FTTN
7302 ISAM CO
ISP 1
7354/7324 ISAM RU
Converter
Converter
Aggregation
Network Transport
ISP 2 Network
7330 ISAM CO
7356 ISAM REM
7330 ISAM RA
Ethernet
7357 ISAMSEM
Corporations
and Residences
A converter will be required at the Central Office location and at the Remote/Cabinet
location. These converters can be point-to-point, where one Ethernet link
corresponds to one link in the transport network or they can be point-to-multipoint
where Ethernet frames are bridged between one Gigabit Ethernet link on the ISAM
side and multiple transport links on the backhaul network side (for example,
ML-PPP).
Bandwidth
In many cases the backhaul transport network cannot offer the full 1 Gbps connection
which is supported on the ISAM product family. This is typically not an issue for
rural areas where the number of remote subscribers to be served are limited per rural
site with a limited total amount of bandwidth need, or for emerging markets where
connectivity with a rather limited bandwidth is the primary requirement. An
assessment must be made on a case-by-case base to see whether the network capacity
is sufficient in the backhaul transport network for the target end-user services (Voice,
High Speed Internet, and so on). Possibly multiple links need to be bundled to
increase the bandwidth.
In industrialized countries with subscriber dense areas and high bandwidth per user
(for example, 20 Mbit/s), where typically fiber is being used for FTTN deployments,
higher capacities are required for the backhaul link. The backhaul approach is taken
for those locations which cannot be served by fiber (fiber black spots) to obtain 100%
user coverage with ISAM based broadband access.
Transparency
The backhaul connection between the remote ISAM and CO ISAM must provide a
transparent Ethernet service. The bridging function between the network port of the
ISAM (uplink and/or subtended link) and the backhaul transport network can be
done by an external converter. The converters and backhaul transport network must
ensure that, both the remote ISAM and the CO node, are able to extract the original
frames sent by the other side, in the same order as they were sent, that is, no
frame-reordering or fragmentation.
Service differentiation
ISAM deployments in a backhaul scenario, and especially in those cases with limited
backhaul capacity like rural areas, must support proper queuing and scheduling
mechanisms to provide service differentiation in both up- and downstream direction.
Voice must get strict priority over other services like Video and High-Speed Internet,
and management connectivity must be ensured at all times.
Congestion is likely to occur on the backhaul link between the remote ISAM and the
CO node due to the limited available bandwidth on this link. The buffer-acceptance,
queuing and scheduling in the upstream direction on the remote ISAM and in the
downstream direction on the CO node are particularly important.
Next to the queuing and scheduling mechanisms, proper service classification must
be done on the backhaul link. At least the p-bits in the VLAN-tag should be
configurable as a means to map VLAN-tagged traffic in the appropriate queues.
To overcome congestion and eventually packet drop (high priority traffic) on the
backhaul link we can use the buffer mechanism of the ISAM, in both upstream and
downstream direction. Using the interface rate-limiting capabilities of the ISAM
network ports, uplink at the remote ISAM and subtended link at the CO node, service
differentiation can be done based on the available bandwidth on the backhaul link.
The port rate-limiting allows traffic scheduling (queue handling) to be done at a
speed (bit rate) matching the available bandwidth in the backhaul transport network.
The dimensioning of the rate-limited on ISAM network ports will depend on the
encapsulation overhead added by framing mechanism implemented on the backhaul
transport equipment (that is, converters) and the Ethernet frame sizes used by the
data services. When forwarding the Ethernet frames over the transport link, headers
and trailers are added to the Ethernet frame. This results in a lower Ethernet packet
throughput than natively supported by the backhaul link. The overhead, headers and
trailers added, depends on the encapsulation method used. Figure A-19 shows an
example of the header/trailer bytes added by the GFP and HDLC encapsulation
method.
Figure A-18 Encapsulation overhead GFP versus HDLC
GFP Encapsulation HDLC Encapsulation
As a result the port rate-limit will be set to a rate according the supported packet
bit-rate and not to bit-rate natively (on the wire) supported by the transport network,
which can be a lot lower, depending the Ethernet frame sizes. See below an example
based on GFP-F on E1 to illustrate this.
Table A-1 GFP Encapsulation overhead calculation
Framed E1 (31 Timeslots) = 1984 kbit/s

GFP-F Overhead = 12 bytes
Ethernet frame size Max throughput Overhead Rate limiter ISAM

(bytes) (kbit/s) (%) (x 64 kbit/s)
64 1670 15,83 26
128 1813 8,62 28
256 1895 4,49 29
512 1938 2,32 30

1024 1961 1,16 30
1500 1968 0,81 30
In a second step packet buffers and schedulers of the converters can be used to deal
with service differentiation when sudden bandwidth drop occurs on the backhaul link
(for example, link failure). The priority scheduler in the converter will ensure high
priority traffic (for example, voice) gets precedence over other concurrent traffic in
case of congestion. This is illustrated in Figure A-19.
Figure A-19 ISAM backhaul with point-to-multipoint converter
Central Office / Aggregation Remote / Cabinet Location

Location Backhaul option
PDH (nxE1)
NT NT LT
Protocol based
VLAN tag. + Pbit
Converter Converter
ML-PPP
DSL Link Policies

DSL
1
E1
VoIP VoIP
VoIP VoIP
shaping
GE UP
shaping
SP SP
NW Ctrl FE/ NW Ctrl
FE/ NW Ctrl SP SP NW Ctrl
GE ... GE
GE
WRR HSI HSI WRR
HSI HSI
E1
VoIP DOWN
NW Ctrl SP
WRR DSL
HSI 48
NT
GE
Mgmt IP
VoIP : Strict Priority 1

NW Ctrl : Strict Priority 2
HSI : Best Effort
In case of point-to-point converters (see Figure A-20), the ISAM ensures the service
differentiation. Flushing the queues will be done at the rate of the available bit-rate
on the link giving precedence to the frames in the highest priority queue.
Figure A-20 ISAM backhaul with point-to-point converter
Central Office / Aggregation Remote / Cabinet Location

Location Backhaul option
PDH (nxE1)
NT NT LT
Protocol based
VoIP
VLAN tag. + Pbit
VoIP
shaping
SP SP
shaping
NW Ctrl NW Ctrl
DSL Link Policies
GE E1 E1 GE
WRR WRR
HSI HSI
DSL
1
VoIP VoIP
shaping
SP GE
NW Ctrl SP UP
shaping
NW Ctrl
GE E1 E1 GE
WRR
L WRR
HSI L HSI
A
A
GE G VoIP
VoIP G VoIP DOWN
shaping
shaping
NW Ctrl SP
NW Ctrl SP SP
NW Ctrl
GE E1 E1 GE
WRR DSL
WRR WRR
HSI
HSI HSI 48
VoIP VoIP
NT
shaping
SP SP
shaping
NW Ctrl NW Ctrl
GE E1
E1 GE
GE
WRR WRR Mgmt IP
HSI HSI
VoIP : Strict Priority 1

NW Ctrl : Strict Priority 2
HSI : Best Effort
Resiliency
To limit the impact of single failures, the backhaul solution should provide the
necessary resiliency at all levels of the architecture. Depending on the backhaul
transport network different resiliency mechanisms apply: ML-PPP, EFM bonding,
SDH VCAT (Virtual Concatenation), APS (Automatic Protection Switching), and so
on. On top packet based link-aggregation can be done using LACP (LAG) or path
redundancy using RSTP.
Bonding or aggregation functions do not only allow a level of resiliency but also
offer the means to provide more aggregated bandwidth on the backhaul link.
As shown in Figure A-19 the LAG function of the ISAM is being used to aggregate
4x E1 based backhaul links into one pipe. Figure A-20 shows an example where the
bonding of the backhaul link is done in the transport network using ML-PPP
(typically 16xE1).
The end-to-end path resiliency will only work when “fault-propagation” is supported
by the converters and any other intermediate node. Any link-failure causing a service
outage in the path must be propagated in the forward and backward direction towards
the connected ISAM. The CO ISAM will take proper measures when the link-failure
(operational down) is detected: an alternative route might be chosen based on the
implemented resiliency function (for example, LAG) and a port-down alarm (LOS)
is presented to the management system. In a non-redundant backhaul scenario the
alert should indicate that the remote site is no longer reachable.
Ethernet bridging converter options

Alcatel-Lucent offers a wide range of products supporting different transport
network options combined with the required Ethernet interfaces and Ethernet
bridging functionality.
Given the rich Alcatel-Lucent portfolio supporting any transport option, the ISAM
can be deployed in any environment:
• Re-using available incumbent transport infrastructure which lowers the CAPEX
investment for the remote DSLAM deployment
• Leveraging on equipment already used by the Telecom provider to have limited
OPEX impact: no new logistical processes required, re-use of in-house skills,
unified management …
• Fast go-to-market with Broadband access by providing early connectivity prior to
fiber roll-out. No DSLAM replacement is required after upgrading the network
infrastructure later on.
Figure A-21 provides a high-level overview of possible ISAM configurations and

converters to provide the backhaul connectivity.
Figure A-21 ISAM backhaul options
A.7 Hospitality solution
Introduction
Many hotels and retirement homes are wired with Category3 cable which was very
popular in the 1990's. The Cat3 twisted pair is mainly used to provide hotel and
public telephony services for the hotel guests, in the room and in public areas, and
the hotel staff.
With the emergence of broadband internet access, WiFi (shared) hotspots were made
available where the hotel guest can connect to. In many cases the internet hotspot
belongs to an ISP. The user connects to the internet via the user registration portal of
the ISP after paying a connection fee (pre-paid) via a credit-card.
Figure A-22 Standard offering for voice and internet access in hotel guest rooms
In order to remain competitive, to increase revenue opportunities and to enrich the

guest experience, hotels need to upgrade their IT infrastructure to offer high-speed
and secure internet access, voice and multi-media applications and need to get into
the value chain.
Via similar ways a Telecom operator offers Triple play services to residential
subscribers via xDSL and IP DSLAM. The hotelier can offer IP based triple play
services to the hotel guest with xDSL provided by an IP DSLAM.
By re-using the existing Cat3 wiring for xDSL the hotelier can achieve this over the
existing infrastructure, without too costly cabling costs. So no “rip & replace” but
fully leverage on the existing infrastructure providing triple play-services. The
choice between ADSL2+ or VDSL2 depends on the length of the copper-wire and
the required data throughput.
Figure A-23 Enhanced multi-media experience in hotel guest rooms with xDSL
High level architecture hospitality solution

The ISAM is installed in the existing telecom closet/room near the existing terminal
blocks or distribution frame.
From here DSL connectivity is provided to each room to offer voice (VoIP), video
(IP TV), high speed internet and other data services (multi-media, gaming, …) using
a single copper pair.
A modem (for example, ALU 7130 CellPipe gateway) distributes the services within
the hotel room by providing connectivity to STBs, VoIP or POTS phones, laptop
PCs, (personal) multimedia devices and in-room control (wake-up call, mini-bar,
…).
Gigabit Ethernet interfaces from the ISAM provide connectivity to the supporting
network for the different data services, billing servers/firewalls and management
systems.
Not all hotels or retirement homes are the same. They differ not only in size, in terms
of number of guest rooms, but also in building architecture. Depending on the
building and infrastructure architecture different product solutions can be offered:
• Small to medium size hotels consisting out of one building, having a single,
centralized equipment room where all the terminal blocks are residing. In such a
case a CO ISAM or a standalone FTTN node is used to terminate the copper pairs
from all the guest rooms on one central location; see Figure A-24.
• Medium to large size hotels with multiple equipment rooms (for example, on each
floor) in one building are addressed using the distributed ISAM solution. In such
a case a 7356 ISAM REM chassis can be installed at the different terminal blocks.
An aggregation node aggregates the distributed nodes via GigE optical
connections and provides a single uplink to the network; see Figure A-25.
• A variant to the previous deployment scenario is with larger properties where the
hotel guest rooms are distributed over different buildings or multiple, collocated,
remote sites (for example, a campus). The same ISAM solution applies as in the
previous case; see Figure A-26.
Figure A-24 IP DSLAM Deployment scenario for hospitality, centralized
Figure A-25 IP DSLAM Deployment scenario for hospitality, distributed (single building)
Figure A-26 IP DSLAM Deployment scenario for hospitality, distribute (multiple sites)
DSL and POTS in hospitality solutions

Proven xDSL technology is used on the existing copper pair towards the guest rooms
for the IP/Ethernet based services. This copper pair is used traditionally to provide
telephony (POTS) services.
Figure A-27 ISAM in hospitality: triple-play high-level network topology
Two options apply:

• The existing telephony/POTS can co-exist on the same pair as the DSL services.
Voice and DSL use a different frequency band (POTS uses narrowband, DSL
broadband) on the copper wire. Splitters are used to separate the POTS from DSL.
The DSL terminates on the DSL LT of the ISAM and POTS is further relayed to
the voice switching system of the hotel. If desired the splitter function can be
provided by the ISAM using a dedicated POTS splitter board or a DSL LT board
with integrated splitter technology.
The same splitter technology is required on the modem side. The POTS splitter is
usually supplied via wall socket with a connector for both the POTS/analogue
phone and the modem (see Figure A-27, “room 1”).
• The copper pair is used for DSL only (naked or dry-loop DSL) and the existing
telephony/POTS is replaced by a Voice-over-IP service. In this case the IP
telephony service is delivered to the guest room over the DSL connection.
This scenario does not require any splitter technology. The analogy voice is
packetized into a VoIP (RTP) stream via the DSL gateway in the guest room or a
VoIP phone set is being used (see Figure A-27, “room 2 and 3"). In both cases the
VoIP is handled as any other data stream on DSL. A higher quality of service
treatment is applied to the voice, than the concurrent data streams (Internet, IPTV,
and so on) on the same DSL line.
Broadband bandwidth requirements

The total bandwidth required is determined by the services offered to the hotel guest.
To a large extent the bandwidth requirements are defined by the IPTV service
offering. IPTV is recognized as a high value added service for the hotelier. Especially
with the emergence of HD TV an attractive offering for the hotel guests can be made.
The capacity required for IPTV is determined by:
• High Definition (HD) or Standard Definition (SD) TV or both (for example, SD
broadcast TV combined with HD Video-on-Demand)
• Encoding used: MPEG2, MPEG4
• Number of TVs in the room or suite.
Internet access is no longer a nice-to-have service but has become a necessity. On
top, with the use of internet for social networking, file sharing, video-conferencing,
business, and so on, internet is no longer seen as a best-effort service. Also
high-speed internet access comes with a minimum of bandwidth guarantees and
quality of service.
IP Telephony is probably the least bandwidth consuming service but requires the
highest quality of services and needs to be prioritized accordingly.
Other services are online gaming (might be part of Internet service), in-room control,
hotel camera views (for example, bar, swinging-pool, …), and so on.
Figure A-28 Hotel Room Bandwidth requirement
SD TV MPEG2 Channel: 2 - 5 Mb/s
HSI: 1 - 5 Mb/s
HD TV MPEG4 Channel: 5 - 10 Mb/s
Online gaming: 4 - 8 Mb/S
SD TV MPEG4 Channel: 1.5 - 2 Mb/s
In control room: 0.5 Mb/s
VoIP: 160 Kb/s
All the data-streams described in Figure A-28 can run over a single DSL copper pair.
In the ISAM and the DSL gateway in the room the proper quality of service
provisioning is done for each of the services. Policing and rate-limiting might apply
depending on the guest profile and service package subscribed to.
The available DSL bandwidth on the copper pair depends on the DSL technology
used:
• ADSL2+ with a theoretical maximum downstream bandwidth of 25 Mb/s.
• Supports longer loops than VDSL2
• Typically 15-20 Mb/s
• Artificial Noise can be applied to increase stability of the line
• VDSL2 (17a profile) has a theoretical maximum downstream bandwidth of 100

MB/s
• Due to the use of higher frequencies on the copper pair the distance is limited
• Typically 25-40 Mb/s
• Virtual Noise increases stability
Other factors influencing the actual copper and therefore the bandwidth are:
• Cable type: Gauge, twisted-pair, shielding, and so on
• Distance: loop length limits, especially for VDSL2
• Bridged Taps: copper pairs that are interconnected together are causing reduced
DSL performance
• Environment Interference: air-conditioning, elevator engines, and so on
• Interference by cross-talk: caused by other services on adjacent pairs.
Global or individual DSL line settings can be applied on the ISAM to minimize the
impact of the different factors described above by configuring DSL profiles
accordingly. DSL profiles can be DSL line specific or uniform across a line card
and/or an ISAM chassis.
A.8 Open Community Broadband for Smart Communities
Introduction
End-user's expectations on access to Broadband connectivity are becoming nearly as
widespread as for the classic commodities (water, gas, electricity, telephony). Not
just private end-users but also businesses and local authorities need broadband
access. However, the geographical coverage by the classic operators is not total, and
not all greenfield opportunities are covered. Backed by government incentives, more
and more local authorities are considering the deployment of a community-wide
access network to fill the gaps and ensure digital attractiveness of their locality (for
social and economic reasons). This is the Smart community concept, whereby there
is a variety of levels for the “community”: building site, campus or estate, city
district, and complete city. One important aspect for attractiveness is the openness to
multiple service providers, promoting service competition rather than access
competition. The applications include but go beyond the classic triple play, also
encompassing business services and specific services for public authorities like
municipalities.
The aim of the Open Community Broadband solution is to offer a way for those new
entrants to build out, deploy and manage such a single access and aggregation
infrastructure at their local level, which can then be opened to and shared by multiple
third party service providers, from which the end-users can select a mix of
applications. In other words, to offer a very flexible wholesaling framework.
The OCB solution as such comprises the passive infrastructure, the active
infrastructure, the management sub-system, and the professional services for
guidance of the local authority to roll out the infrastructure. OCB is part of the wider
context of Smart Communities, developed by Strategic Industries. The scope is
greenfield deployments, encompassing FTTH networks (point-point Ethernet) and
other flavours of FTTx depending on the case-by-case needs.
The converged ISAM can play a prominent and competitive role in the OCB
solution, by offering a variety of access technologies (point-point optical access,
FTTx) in a single platform with the necessary mechanisms to create and manage the
connectivities in an open context. Other advantages of the ISAM are port density, the
modular approach (extend-as-you-grow with LTs), and high temperature range.
OCB context
Wholesaling
Three layers can be identified in the delivery of broadband access. The first is the
passive infrastructure (ducts, cables, fibres, splitters). The active infrastructure
consists of all network equipment, and uses the passive infrastructure for giving
connectivity between the end-users and the applications. Finally, the service layer
uses the active and passive infrastructure to deliver the applications.
In traditional networks the approach is a vertically integrated one; the different
incumbent operators integrate all layers, competing with each other on access
infrastructure and less on the services offered.
It is possible to introduce wholesaling to this situation, splitting the responsibilities
over multiple roles, to varying degrees, as illustrated in Figure A-29. In the passive
wholesale case, a single passive network is shared and made accessible to multiple
vertical service providers. In the active wholesale case, a single vertical
infrastructure provider offers connectivity to multiple retail service providers
(RSPs). Finally in the most separated case, a single passive provider gives access to
its infrastructure to the active network operated by a single network operator which
connects towards multiple service providers. Note that even here a single player can
combine the roles of active infrastructure owner and service provider (by offering its
own services), but the important point is that it remains open to third party retail
service providers.
Figure A-29 OCB: roles and wholesaling levels
The focus of OCB lies on the full separation case.
Roles and responsibilities

As shown in Figure A-30, in the fully separated case there are distinct responsibilities
at each level.
Figure A-30 OCB: roles and responsibilities
Solution description: Active architecture
Requirements
The OCB network must carry residential (triple play + RF video), business (L2 VPN,
L3 VPN, Business Internet Access) and public applications (VPN, e-care, and so on)
with the corresponding levels of security, availability and QoS differentiation. It can
hence be based on existing converged network architectures for residential and
business applications (public applications can be mostly considered as business
services). There are some new requirements though with respect to existing
environments, namely the level of wholesaling and the need for an integrated
management approach:
• each end-user is able to select applications from multiple service providers
simultaneously
• the network operator can sell white label services to third-party service providers
who can then include this service next to their own into their commercial bundle
towards the end-user
• the network operator must have the management tools to operate the network, the
users and their selection of services in the most integrated possible way. A certain
level of dynamism is introduced by allowing end-users to select the services per
service provider via a self-provisioning portal.
• The network operator needs to provide the ability for Retails Service Providers
(RSP) to offer competitive and differentiating service offerings. The OCB
network as to support a very granular configuration of bandwidth and QoS per
RSP per end-user.
Architecture: Ethernet open access

The Customer Premises Network (CPN) can either consist of a CPE followed by one
RGW per RSP (delivered by the RSP), or of a CPE followed by a single RGW
(delivered by the network operator). In both cases there is one IP address allocated
per RSP. Note that in the first case each RGW falls under responsibility of its
corresponding RSP, and that in the second case the RGW is managed by the network
operator.
The access and edge network is characterized by the following features;
• Generic:
In general the connectivity is similar to the broadband networks for residential
and business applications. As a single user can now connect to different service
providers simultaneously, the service provider separation on the first-mile is done
by means of VLAN tagging by the CPE (port-based). Traffic is further separated
in the network at L2 by means of VLANs (separate broadcast domains) and at
MPLS level by means of VPLS or VLL instances. There is also a separate VLAN
and VPLS instance for the CPE management (for example, TR-069), which is
fully terminated by the network provider. At the edge of the network operator,
there is a L2 hand-off to the different service providers. In other words, there is
no routing within the network operator domain.
A new feature introduced in OCB is the self-provisioning portal, offering the
possibility for end-users to dynamically check their service subscriptions and
select specific services from the service providers they have subscribed to. The
portal is best positioned at the network operator, to consolidate the view of the
end-user on all its services (see paragraph on management subsystem).
• Specifically for residential services:
All requirements of classic triple-play deployments apply, in terms of L2 and L3
security, QoS handling, connectivity capabilities, IGMP handling, DHCP
proxying, and so on….
However, a couple of features are additionally required in the specific context of
OCB:
• the support of multiple service providers (with potentially overlapping multicast
addressing schemes) in the network, possibly also multiple multicast IPTV services
per subscriber. This must be taken into account in the multicast replication points
and in the CDRs (Charging Detailed Record) for viewing statistics.
• the QoS, access control and resource control policies in the network also have to be
applicable at per-service subscriber level.
• Specifically for business/public services:
There are no specific OCB requirements on the architecture other than the
simultaneous co-existence of multiple VPNs offered by multiple service
providers. Note that for business services there is a separation per service instance
in the access and aggregation network.
The Ethernet open access is the most straightforward deployment model in terms
of node complexity and involvement burden of the network operator (IP
auto-configuration and service configuration can be left to the service providers).
Note however that it implies a mapping of CPN (Customer Premises Network)
terminals on service providers.
Figure A-31 L2 access architecture for OCB (residential user shown with 1 RGW per RSP)
Solution description: Management subsystem

The management subsystem covers the set of applications in charge of managing the
telecommunication infrastructure, the end users, the services and the service
providers.
A solution for the OSS/BSS/CRM (Customer Relation Management)/EMS of the
network operator plays an important role in the OCB context. It must support the
traditional roles of subscriber provisioning and management, service provisioning
and management, statistics gathering, alarm management, and customer care in the
wholesale context to multiple service providers per end-user. Additionally, in the
case of OCB a self-provisioning portal would allow the end-user to select and
monitor its services. Note that in OCB the network provider is a new entrant,
meaning that it does not have experience or legacy systems to rely upon. Hence the
importance of an affordable and comprehensive solution.
This can be fulfilled by a combination of the classic EMS platforms (AMS for ISAM
and SAM for ESS and SR) with an integrated management platform, which acts as
OSS/BSS/CRM by interacting with end-users, network operator and service
provider:
• customer self-provisioning portal (restricted access by end-user): users monitor
their profile and select their services
• service provider portal (restricted access by service providers): service providers
monitor and manage their subscribers
• technical portal (restricted access by network operator): network operator sets the
per-subscriber service policies, keeps usage statistics, by directly interacting with
the corresponding network elements
• customer care portal (restricted access by service providers): allows the service
providers to manage the customer trouble tickets
The dedicated EMS platforms take care of the initial user provisioning and
consolidated alarm management.
B. RADIUS Attributes
B.1 RADIUS Attributes B-2
B.2 Vendor specific RADIUS attributes B-2
Alcatel-Lucent 7302 ISAM | 7330 ISAM FTTN | 7356 ISAM FTTB R4.4.02 July 2012 B-1
B.1 RADIUS Attributes
NAS-Port
The system sets the NAS-port attribute as described below:
• 802.1x sessions:
The NAS-port attribute contains the ifIndex of underlying bridge port.
• PPPoE sessions:
The NAS-port attribute contains the ifIndex of the PPPoE sessions.
NAS-Port-Id
The system sets the NAS-Port-Id attribute according to the following text format:
atm <rack>/<shelf>/<slot>/<DSL-Line>:<VPI>.<VCI>
The fields indicated between “<” and” “>” is the information retrieved from the
management model:
• Rack & shelf:
Rack and shelf number of the board that terminates the DSL line. Each item is
represented with 1 ASCII character.
• Slot & DSL-line:
Slot number and port number of the board and of the DSL-line within the board,
each item is represented with 2 ASCII characters that correspond with the
decimal number.
For example, port 12 is represented with character “1” followed by character “2”.
Port 5 is represented by character “0” followed by character “5”.
• VPI:
VPI represented with between 1 and 3 ASCII characters, using the number of
characters that is needed.
For example, VPI 12 is represented with character “1” followed by character “2”.
VPI 5 is represented by character “5”. VPI 0 is represented by character “0”.
• VCI:
VCI represented with between 1 and 5 ASCII characters, using the number of
characters that is needed.
For example, VCI 32 is represented with character “3” followed by character “2”.
The fixed separators, including the blanks are characters that are inserted in
between the previous characters.
B.2 Vendor specific RADIUS attributes
B-2 July 2012 Alcatel-Lucent 7302 ISAM | 7330 ISAM FTTN | 7356 ISAM FTTB R4.4.02
General
Vendor ID 637 is used for 7302 ISAM.
The “Vendor type” field has a length of two bytes where the highest byte is the
project ID and the lowest byte is the project specific attribute ID.
The “Vendor length” field has a length of one byte.
The project ID 7 is assigned to 7302 ISAM project. This means that the vendor
specific attribute range from 1792 to 2047 will be used for the 7302 ISAM.
Note — If the radius server supplies the 7330 with VSA privileges in
the authentication response for a CLI operator, the response must
contain a VSA and privilege level for all supported VSA's on the
7330. Otherwise, the 7330 will use the default values for ALL
attributes as set in the default-profile on the ISAM. The
default-profile settings can be viewed in CLI using the info configure
system security default-profile command.
VRF-Name
• Vendor Type: 1792

• Vendor Length: 4 < length < 35
• Vendor Value: STRING
• Packet: Access-Accept
VLAN-ID

• Vendor Length: 7
• Vendor Value: INTEGER
QoS-Profile-Name
The QoS-Profile-Name is a character string of maximum 32 characters identifying
the QoS user profile configured in the system. The QoS user profile contains both
marker and policer information.
Note: This attribute cannot be specified together with QoS-Parms attribute.
QoS-Parms
Note: This attribute cannot be specified together with QoS-Profile-Name attribute.
Possible values are:

• [marker up {.1p <value(0:7)>}]
• [policer up {cir <value> cbs <value>}]
• [policer down {cir <value> cbs <value>}]
where:
• cir: 4 bytes in kbit/s
• cbs: 4 bytes in bytes
TL1 domain parameters

Table B-1 lists the VSAs and their default values for the TL1 domain.
Table B-1 TL1 domain parameters
Domain VSA Value Default Value

Maintenance 1536 Integer (0..7) 4
Provisioning 1537 Integer (0..7) 4
Security 1538 Integer (0..7) 7

Test 1539 Integer (0..7) 0
The possible values for each domain are:

• 0: no privilege
• 1: privilege level 1
CLI domain parameters

Table B-2 lists the VSAs and their default values for the CLI domain.
Table B-2 CLI domain parameters
Domain VSA Value Default Value
AAA 1801 Integer (0..3) 1
ATM 1802 Integer (0..3) 3
Alarm 1803 Integer (0..3) 3
DHCP 1804 Integer (0..3) 3
EQP 1805 Integer (0..3) 3
IGMP 1806 Integer (0..3) 3

CPEproxy 1807 Integer (0..3) 3
IP 1808 Integer (0..3) 3
PPPoE 1809 Integer (0..3) 3
QoS 1810 Integer (0..3) 3
SWMgt 1811 Integer (0..3) 3
Transport 1812 Integer (0..3) 3
VLAN 1813 Integer (0..3) 3

XDSL 1814 Integer (0..3) 3
Security 1815 Integer (0..3) 0
Cluster 1816 Integer (0..3) 3

SLOT-NUMBERING 1820 Integer (0..2) 2
Service 1821 Integer (0..3) 3
Debug 1822 Integer (0..3) 3

Debugmirror 1823 Integer (0..3) 3
Filter 1824 Integer (0..3) 3
Link 1825 Integer (0..3) 3
Log 1826 Integer (0..3) 3
OAM 1827 Integer (0..3) 3
SIP 1828 Integer (0..3) 3
MEGACO 1829 Integer (0..3) 3
LACP 1830 Integer (0..3) 3
MSTP 1831 Integer (0..3) 3

DROUTER 1832 Integer (0..3) 3
The possible values for each domain are:

• 0: no privilege
• 1: read privileges
• 2: write privileges
• 3: read-write privileges
CLI profile parameters

Table B-2 lists the VSAs and their default values for the CLI profile.
Table B-3 CLI profile parameters
Profile parameter VSA Value Default Value Length
Prompt 1817 String (< 19 characters) %n%d%c 18 bytes
Password timeout 1818 Integer (0..365 days) 0 -

Description 1819 String (< 31 characters) ““ 30 bytes
Glossary
Numbers
10/100Base-T 10- to 100-Mb/s LAN

An IEEE standard for 10/100 Mb/s twisted-pair Ethernet wiring.
10Base-T An IEEE 802.3 LAN transmission standard for Ethernet. 10Base-T carries
data at 10 Mb/s to a maximum distance of 328 ft (100 m) over unshielded
twisted-pair wire.
10GBase-LR An IEEE 802.3ae standard for 10 Gigabit Ethernet. 10GBase-LR carries data
at 10 Gb/s to a maximum distance of 6.2 mi (10 km) over single-mode fiber.
100Base-LX An IEEE 802.3 LAN transmission standard for 100 Mb/s Fast Ethernet using
Long Wavelength (LX) laser transmitters over MMF for distances up to 1.25
mi (2 km). The 7302 ISAM and 7330 ISAM FTTN support an SMF
implementation of 100Base-LX for distances up to 9.3 mi (15 km).
100Base-TX An IEEE 802.3 LAN transmission standard for Fast Ethernet. 100Base-TX
carries data at 100 Mb/s over two pairs of shielded twisted-pair or
Category 5 unshielded twisted-pair wire.
1000Base-BX10 An IEEE 802.3 LAN transmission standard for bidirectional point-to-point
1000 Mb/s Gigabit Ethernet over SMF for distances of up to 6.2 mi (10 km).
Always used in pairs, wavelength division multiplexing is performed in the
SFP module to split the optical signal into two light paths. The
1000Base-BX10-D (downstream) SFP module transmits a 1490 nm signal
and receives a 1310 nm signal. The 1000Base-BX10-U (upstream) SFP
module transmits a 1310 nm signal and receives a 1490 nm signal.
1000Base-EX A nonstandard implementation of the 1000Base-LX transmission standard
with an extended reach up to 24.9 mi (40 km).
Alcatel-Lucent 7302 ISAM | 7330 ISAM FTTN | 7356 ISAM FTTB R4.4.02 July 2012 GL-1
Glossary
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 A nonstandard implementation of the 1000Base-LX transmission standard
operating at 1550 nm for distances up to 49.7 mi (80 km).
23 inch preconfigured A 23 inch, 7 foot equipment rack with one or two ARAM-D shelves
rack preinstalled. The rack can be extended to 9 ft or 11.5 ft in height.
3DES Triple DES
A mode of the DES encryption algorithm that encrypts data three times
instead of once. Three 64-bit keys are used for an overall key length of 192
bits; the first encryption is encrypted with a second key, and the resulting
cipher text is encrypted with a third key.
5520 AMS The Alcatel-Lucent UNIX-based, client-server architecture controller for
various NE systems.
5526 AMS The Alcatel-Lucent 5526 Access Management System
A UNIX-based, client-server architecture controller for 7330 ISAM FTTN
systems.
7302 ISAM The Alcatel-Lucent 7302 Intelligent Services Access Manager
A DSLAM that operates in a packet aggregation network. The 7302 ISAM
enables deployment of triple-play services, such as video on demand,
high-definition TV, and broadcast TV services for all subscribers
simultaneously.
7330 ISAM FTTN The Alcatel-Lucent 7330 Intelligent Services Access Manager Fiber to the
Node
A standalone DSLAM designed for the ease and rapid deployment of
high-bandwidth IP services between high-bandwidth, optical fiber-based
transmission media, and copper-based xDSL subscribers.
AAL ATM Adaptation Layer

A protocol used by ATM to segment and reassemble data for insertion into
an ATM cell; also performs error checking and correction.
AAL1 ATM Adaptation Layer 1
Type 1 class of AAL service supporting constant bit rate, and
time-dependent traffic such as voice and video.
GL-2 July 2012 Alcatel-Lucent 7302 ISAM | 7330 ISAM FTTN | 7356 ISAM FTTB R4.4.02
Glossary

Type 2 class of AAL service characterized by voice and video transfer.
Type 5 class of AAL service characterized by high-speed data transfer.
ACL Access Control List
ACO Alarm Cut Off
An easily accessible switch on the equipment that allows audible alarms to
be extinguished without affecting the visual alarms. The audible alarms can
be toggled as enabled or disabled.
ACU Alarm Control Unit
A plug-in unit or built-in subsystem that collects shelf alarms and provides
an alarm interface to the CO alarm system.
ADSL Asymmetric DSL
A variant of DSL with asymmetric upstream and downstream data rates.
ADSL provides more bandwidth for downstream traffic (server to client)
than for upstream (client to server). There are several types of ADSL
including ADSL, ADSL2, READSL. All these types are collectively
referred to as multi-ADSL.
AES Advanced Encryption Standard
A symmetric 128-bit block data encryption algorithm.
AF Assured Forwarding
AGG Node Aggregation Node
AIS Alarm Indication Signal
AMP Champ A common name for a 25-pair connector used on the 7330 ISAM FTTN to
connect POTS CO lines and subscriber drop lines.
AMSL Above Mean Sea Level
ANCP Access Node Control Protocol
ANSI American National Standards Institute
A nonprofit, nongovernmental body supported by over 1000 trade
organizations, professional societies, and companies; ANSI was established
for the creation of voluntary industry standards.
APS Automatic Protection Switching
The capability of a transmission system to detect a failure on a working
facility and switch to a protection facility to recover the traffic, thus
increasing overall system reliability.
Glossary
ARP Address Resolution Protocol

A protocol within TCP/IP that maps IP addresses to Ethernet MAC
addresses. TCP/IP requires ARP for use with Ethernet.
AS Autonomous System
ASCII American Standard Code for Information Interchange
A coding method used to convert letters, numbers, punctuation, and control
codes into digital form.
ASP Access Service Provider
ATI Alarms, Test Access, and Interfaces
ATM Asynchronous Transfer Mode
A multiplexed information transfer method in which the information is
organized into fixed-length cells of 53 bytes and transmitted according to the
needs of each user.
ATP Aggregate Transmit Power
ATU-C ADSL Transceiver Unit – Central Office
ATU-R ADSL Transceiver Unit – Remote
AWG American Wire Gauge
A standard measuring gauge for non-ferrous conductors.
BAC Buffer Acceptance Control

BE Best Effort
BER Bit Error Rate
A measure of transmission quality expressed as the percentage of received
bits in error compared to the total number of bits received.
BFD Bidirectional Forwarding Detection
BGP Border Gateway Protocol
BITS Building Integrated Timing Source
A clock that supplies a composite clock timing reference to all other clocks
in a building over BITS clock cables.
BITSoIP BITS over IP - refers to IEEE1588
blowfish A freely available symmetric block cipher designed as a drop-in replacement
for DES or IDEA. Blowfish allows variable-length keys of up to 448 bits.
Glossary
BNC Bayonet Neil-Concelman

A locking connector for slim coaxial cables, such as those used for Ethernet.
BNG Broadband Network Gateway
BOOTP Bootstrap Protocol
A member of the IP family of protocols that allows a diskless client machine
to learn, among other information, its IP address. BOOTP starts a networked
machine by reading boot information from a server. BOOTP is commonly
used for desktop workstations and LAN hubs.
BRAS Broadband Remote Access Server
BRI Basic Rate Interface
An ISDN interface consisting of two 64 kb/s B-channels and one 16 kb/s
D-channel for a total of 144 kb/s.
BW Bandwidth
CAC Connection Admission Control

An algorithm that evaluates whether or not a new connection can be added
to the node.
CAC examines QoS objectives defined by the PVC service category, as well
as its configured traffic descriptor and traffic rates. CAC determines whether
the system can satisfy these criteria for the PVC and whether the PVC will
affect the guaranteed QoS that existing PVCs already have on the node.
CBR Constant Bit Rate
CBS Committed Burst Size
CCSA Checkpoint Certified Security Administrator
or
China Communications Standards Association
CDC Carrier Data Collection
CDE Customer Dependant Engineering
The CDE file on a card contains country-specific information.
CDR Clock Data Recovery
CES Circuit Emulation Service
Glossary
CEV Controlled Environmental Vault

A temperature- and humidity-controlled underground vault that houses the
7330 ISAM FTTN system at a remote location.
CFM Cubic Feet per Minute
or
Connectivity Fault Management
CFM is an Ethernet OAM capability for testing network connectivity at
Layer 2. CFM allows service providers or network operators to verify and
isolate link and node faults on a bridged network. CFM is specified in the
standard IEEE 802.1ag.
CHAP Challenge Handshake Authentication Protocol
A PPP authentication method for identifying a dial-in user. The user is given
an unpredictable number and challenged to respond with an encrypted
version. CHAP does not itself prevent unauthorized access; it only identifies
the remote end.
CIR Committed Information Rate
CL Controlled Load
CLEI Common Language Equipment Identifier
A 10-character code used to identify telecommunications equipment. The
10-character structure, outlined in the Telcordia specification, specifies the
basic product type, features, source document, and associated drawings and
versions. A CLEI code is unique to a specific piece of equipment.
CLI Command Line Interface
A workstation access method interface that uses CLI commands to
communicate to any network element in the 7330 ISAM FTTN network.
CMOS Complementary Metal Oxide Semiconductor
CMP Communications Plenum Cable
CO Central Office
A telephone switching center that connects subscribers within a telephone
network.
CODEC Coder decoder
COLO Collocation
CPCS Common Part Convergence Sublayer
The portion of the convergence sublayer of an AAL that remains the same
regardless of traffic.
Glossary
CPE Customer Premises Equipment

Customer-owned telecommunications equipment at customer premises used
to terminate or process information from the public network.
CPE-MM CPE Management Machine
CPR Continuing Property Record
A six-character code that can be used to classify equipment items into
various property types.
CPRs also provide property record unit identification that allows network
service providers to create asset records for the purpose of equipment
engineering, ordering, invoice processing, asset management, and auditing.
CPU Central Processing Unit
The part of a computer that performs the logic computational and
decision-making functions.
CSMA/CD Carrier Sense Multiple Access with Collision Detection
A data communications mode in a shared medium in which access
contention problems are solved by denying access to one of the contenders.
Craft terminal A workstation that has element management system software installed on it.
The workstation can be an ASCII terminal or a PC or laptop computer
equipped with terminal emulator software. The craft terminal typically uses
CLI or TL1 for managing network elements, either remotely over a network
connection or locally over a local connection.
CT See Craft terminal
C-VLAN Customer VLAN
CWDM Coarse Wavelength Division Multiplexing
DA Destination Address
DB-9 A 9-pin D-shell connector used for the craft port on the 7330 ISAM FTTN.
DBA Dynamic Bandwidth Allocation
The capacity of subdividing large high-capacity network transmission
resources among multiple applications almost instantaneously and providing
each application only the share of bandwidth each application requires
DBPO Downstream Power Back-Off
DELT Dual Ended Line Testing
Glossary
DES Data Encryption Standard

An ANSI symmetric-key encryption method that uses a 56-bit key and the
block cipher method, which breaks text into 64-bit blocks and then encrypts
them. DES was standardized by ANSI in 1981 as ANSI X.3.92.
DES-56 See DES.
DHCP Dynamic Host Configuration Protocol
A client/server service that is an extension of the BOOTP protocol. DHCP
simplifies the configuration of a client workstation since no IP addresses,
subnet masks, default gateways, domain names, or DNSs must be
programmed. With DHCP, this information is dynamically leased from the
DHCP server for a predefined amount of time. Because the information is
stored on a server, it centralizes IP address management, reduces the number
of IP addresses to be used, and simplifies maintenance. RFC 2131 defines
DHCP.
DLC Data Link Connection
A frame relay connection.
or
Digital Loop Carrier
DLP Detailed Level Procedure
DMT Discrete Multitone
DNS Domain Name Server
DoD Downstream on Demand
DoU Downstream Unsolicited
DS1 Digital Service Level-1
A digital circuit with a total bandwidth or transmission speed of 1.5444
million bits per second. The trunk level-1 standard of 1.5444 is in support of
24-voice conversations each encoded at 64 Kb per second.
DSCP Differentiated Services Code Point
A six-bit value encoded in the type-of-service field of an IP packet header.
It identifies the CoS that the packet should receive.
DSL Digital Subscriber Line
A modem technology that enables high-speed data transmission between
two modems, one at a service provider location and one at the subscriber
premises, over a single twisted-pair copper telephone wire.
Glossary
DSLAM Digital Subscriber Line Access Multiplexer

A network device that converts xDSL signals into ATM traffic. For a service
management application, if the service user is connected to the ATM
network through a DSLAM port, the network access is provisioned using a
DSLAM attachment type.
DSP Digital Service Provider
EAR Ethernet Access Router

EAPOL Extensible Authentication Protocol Over LAN
ECI Equipment Catalog Item
A six-digit numeric code that translates into the bar code on the bar code
label. ECI codes are also used as internal processing codes.
ECMP Equal Cost Multi-Path routing
EEC Ethernet Equipment Clock
Option 1 : designed for interworking with 2048 kHz hierarchy based TDM
equipment
Option 2 : designed for interworking with 1544 kHz hierarchy based TDM
equipment
EF Expedited
EFM Ethernet in the First Mile
A set of copper and fiber-based access technologies that are based entirely
on Ethernet packet transport.
eHCL Electrical High Capacity Link
EIA Electronic Industries Association
A group that specifies electrical transmission standards. The EIA and TIA
have developed numerous well-known communications standards,
including EIA/TIA-232 and EIA/TIA-449. For EIA-spaced equipment
racks, 1 RU equals 1.75 in. (4.45 cm).
EM Element Manager
EMAN Ethernet Metropolitan Area Network
EMC Electromagnetic Compatibility
EMC designates the ability of commodities to function normally in the
electromagnetic environment (this ability is termed Electromagnetic
Susceptibility [EMS]), and the ability not to generate unbearable
electromagnetic interference to other devices and equipment in the same
environment (this ability is termed Electromagnetic Interference [EMI].
Glossary
These two abilities are collectively named EMC.

EMI Electromagnetic Immunity
EMS Element Management System
A system that manages the components of a network.
EOC Embedded Operations Channel
EPS Equipment Protection Switching
The capability of physical equipment to detect a failure on a working facility
and switch to a protection facility to recover the traffic, thus increasing
overall system reliability.
ES Expansion Shelf
An expansion shelf using the same shelf as the 7330 ISAM FTTN host shelf
(ARAM-D shelf), but with some different units installed to provide
additional subscriber line connections for the host shelf.
ESD Electrostatic Discharge
Ethernet A data link layer protocol for interconnecting computer equipment into
CSMA/CD LANs, jointly developed by Xerox, Digital Equipment
Corporation, and Intel. This standard forms the basis for IEEE 802.3.
The Ethernet protocol specifies how data is placed on, and retrieved from, a
common transmission medium. It is used as the underlying transport vehicle
by several upper-level protocols, including TCP/IP and UDP/IP.
ETR Extended Temperature Range
ETSI European Telecommunications Standards Institute
The European counterpart to ANSI. Established to produce
telecommunication standards integration in the European community for
users, manufacturers, suppliers, and Post Telephone and Telegraph
administration.
FC Forwarding Class
FDB Forwarding Database
FDD Frequency Division Duplexing
FDM Frequency Division Multiplexing
A form of multiplexing in which several independent signals are allocated
separate frequency bands for transmission over a common channel.
FE Fast Ethernet
FEC Forward Error Correction
Glossary
FEMF Foreign Electro-Motive Force

FENT Fast Ethernet Network Termination
FEXT Far-end XTalk (crosstalk)
FIB Forwarding Information Base
An internal table containing only the IP routes actually used by a router to
forward IP traffic.
FIFO First In, First Out
FPGA Field Programmable Gate Array
An integrated chip with functions that can be programmed by software.
FTP File Transfer Protocol
FTTN Fiber to the node
See 7330 ISAM FTTN.
GE Gigabit Ethernet
Ethernet interface running at 1000 Mb/s.
GEM GPON Encapsulation Method
GFC General Facilities Card
GPON Gigabit-capable Passive Optical Network
GMMI Gigabit Media Independent Interface, with data clock of 125 MHz and clock
accuracy of ± 1.0×10-4 (100 ppm)
GUI Graphical User Interface
A user screen that includes menus, tables, or icons to query or change data;
usually distinguished from a command line interface.
H1 High-1
H2 High-2
HSI High Speed Internet
Glossary
IACM Intelligent Access Termination, Control and Management

iBridge Intelligent Bridging mode, also known as residential bridging mode
ICMP Internet Control Message Protocol
ICS Item Change Status
A code that identifies the change status of an Alcatel-Lucent unit or
component.
IDEA International Data Encryption Algorithm
A symmetric-key encryption method that uses a 128-bit key and the block
cipher method, which breaks text into 64-bit blocks and then encrypts them.
IEEE Institute of Electrical and Electronics Engineers
A worldwide engineering publishing and standards-making body. It is the
organization responsible for defining many of the standards used in the
computer, electrical, and electronics industries.
IETF Internet Engineering Task Force
An organization that provides the coordination of standards and
specification development for TCP/IP networking.
IGMP Internet Group Management Protocol
A protocol used between hosts and multicast routers on a single physical
network to establish hosts’ membership in particular multicast groups.
Version 2 of IGMP is described in RFC 2236.
IGS IGMP System on the SHub
IMA Inverse Multiplexing for ATM
INP Impulse Noise Protection
INP provides forward error correction techniques to protect user traffic from
excessive noise, which can result in data loss.
IP Internet Protocol
A connectionless packet-switching protocol that works together with TCP.
IPCP IP Control Protocol
A protocol that configures, enables, and disables the IP protocol modules on
both ends of a point-to-point link. IPCP is tied to PPP, and activated when
PPP reaches the network layer-to-protocol phase. If IPCP packets are
received prior to this phase, they are discarded.
IPoA Internet Protocol over ATM
IPoE Internet Protocol over Ethernet
Glossary
IPTV IP Video/Television
The delivery of video services over an end-to-end IP infrastructure. IPTV
can include various classes of video services including video on demand,
broadcast TV, video conferencing, and mobile video.
ISAM Intelligent Services Access Manager
See 7302 ISAM or 7330 ISAM FTTN.
ISDN Integrated Services Digital Network
ISP Internet Service Provider
ITSC Integrated Test and Sealing Current
A feature that includes narrowband line testing functionality as well as
sealing current for subscriber lines connected to the equipment.
ITU International Telecommunications Union
A standards organization that develops international telecommunications
recommendations.
IXL Index List
L1 Low-1
L2 Low-2
L2 Layer 2
L3 Layer 3
LACP Link Aggregation Control Protocol
An IEEE specification (802.3ad) that allows you to bundle several physical
ports together to form a single logical channel.
LAG Link Aggregation Group
A LAG increases the bandwidth available between two network elements by
grouping ports into one logical link. The aggregation of multiple physical
links allows for load sharing and offers seamless redundancy. If one of the
links fails, traffic is redistributed over the remaining links.
LAN Local Area Network
A type of network that sends and receives communications over a small area,
such as within an office or group of buildings.
LC Lucent Connector
A small optical fiber connector.
Glossary
LCP Link Control Protocol

A protocol that LCP establishes, configures, and tests data-link connections
for use by PPP.
LDP Label Distribution Protocol
LED Light Emitting Diode
A semiconductor diode that emits light when a current is passed through it.
LIM Line Interface Module
LMI Line Management Interface
LOS Loss of Signal
A condition at the receiver or a maintenance signal transmitted in the
physical overhead, indicating that the receiving equipment has lost the
received signal.
LPF Low-pass Filter
A single transmission band extending from zero frequency up to a specified
cutoff frequency, not infinite.
LP slot A slot in the 7330 ISAM FTTN shelf where an applique is installed.
LSA Link State Advertisement
A message of the OSPF routing protocol that informs about network
topology changes.
LSDB Link State Database
A database used to compute network routes after each change of topology
that has been reported by the routing protocol.
LSM Line Server Module
A generic term including xDSL line interface modules and any other server
application-specific module.
LT Line Termination
MA Maintenance Association
MAC Media Access Control
The IEEE sublayer in a LAN that controls access to the shared medium by
LAN attached devices.
Glossary
MAIP Maintenance Access Interface Port

or
Multipurpose Alarm Interface Panel
A panel, located in the electronics compartment of a 52-type cabinet that
provides fused dc power to the 7330 ISAM FTTN shelf and cabinet fans, as
well as cabinet and power alarm outputs.
MAU Media Attachment Unit
MBS Maximum Burst Size
MC Multicast
MD Maintenance Domain
MD5 Message Digest algorithm 5
A security algorithm that takes an input message of arbitrary length and
produces as an output a 128-bit message digest of the input. MD5 is intended
for digital signature applications, where a large file must be compressed
securely before being encrypted.
MDF Main Distribution Frame
MDI Medium-Dependent Interface
A type of Ethernet port for use with twisted-pair wiring.
MDIX Medium-Dependent Interface Crossover
The crossover version of MDI that enables the connection of like devices
using straight-through twisted-pair for MDI port-to-MDIX port connections,
and crossover twisted-pair for MDI-to-MDI or MDIX-to-MDIX
connections.
MDU Multi Dwelling Unit
ME Managed Entity
Megaco Media Gateway Controller
MEP Maintenance Endpoint
MEPID Maintenance Endpoint Identifier
MHF MIP Half Function
MIB Management Information Base
MIP Maintenance Intermediate Point
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.
Glossary
MOS Metal Oxide Semiconductor

MP Maintenance Point
M-pair Multi-pair
MPLS Multi Protocol Label Switching
MSTP Multiple Spanning Tree Protocol
An extension of RSTP that allows different spanning trees to co-exist on the
same Ethernet switched network.
MTA Metallic Test Access
MTAU Metallic Test Access Unit
MTBF Mean Time Between Failures
Multi-ADSL A general term that refers to more than one type of ADSL (for example,
ADSL, ADSL2, and READSL).
NACP Network Access Control Protocol

NAT Network Address Translation
NC Network Control
NE Network Element
NEBS Network Equipment Building Standards
Performance, quality, environmental, and safety standards set by Telcordia
for telecommunications equipment.
NFS Network File System
A distributed file system protocol suite developed by Sun Microsystems that
allows remote file access across a network. NFS is one protocol in the suite.
The protocol suite includes NFS, RPC, and XDR. These protocols are part
of a larger architecture that Sun refers to as ONC.
NNI Network to Network Interface
NSA Non-Service Affecting
NSP Network Service Provider
NT Network Termination
A plug-in unit that provides a link to a broadband network, such as ATM or
IP.
NTA slot Network Termination slot A
Glossary
NTB slot Network Termination slot B

NTIO Network Termination Input/Output
NTP Non-Trouble Procedure
or
Network Timing Protocol
NTR Network Timing Reference
OAM Operation, Administration, and Maintenance

Broad categories of functions found in a communications network and/or the
business processes found in network service provider companies.
OBC On-Board Controller
OLR OnLine Reconfiguration
OLT Optical Line Termination
ONC Open Network Computing
ONT Optical Network Terminal
Equipment that provides voice, data, and video services and terminates the
network at a subscriber location. ONTs provide services to a single family
home, a business location, or a multidwelling residence, such as an
apartment complex or condominium. Services can include POTS,
high-speed Ethernet, IPTV, and RF video
ONU Optical Network Terminal
Equipment that provides voice, data, and video services and terminates the
network at a subscriber location. ONTs provide services to a single family
home, a business location, or a multidwelling residence, such as an
apartment complex or condominium. Services can include POTS,
high-speed Ethernet, IPTV, and RF video
OOS Out-of-service
The status of a primary rate link when it is out of service.
OS Operations System
A standalone software system that supports network-related operations
functions.
OSP Outside Plant
Glossary
OSPF Open Shortest Path First

A dynamic routing protocol that responds quickly to network topology
changes. As a successor to RIP, it uses an algorithm that builds and
calculates the shortest path to all known destinations.
OSS Operations Support System
OSWP Overall Software Package
PADI PPPoE Active Discovery Initiation

PBO Power Back-Off
PC Personal computer
A PC can be used as a craft terminal.
PDF Power Distribution Frame
PDV Packet Delay Variation
PDU Protocol Data Unit
PID Protocol Identifier
A part of the SNAP header that identifies the protocol to be encapsulated.
PIR Peak Information Rate
PM Performance Monitoring
P-OLT Packet Optical Line Termination
PoE Power over Ethernet
PON Passive Optical Network
A fiber-based network that uses passive splitters to deliver signals to
multiple users.
POTS Plain Old Telephone Service
A term for narrowband, voice-only telephone service.
PPP Point-to-Point Protocol
A protocol that allows a computer to use TCP/IP with a standard telephone
line and a high-speed modem to establish a link between two terminal
installations.
PPPoA Point-to-Point Protocol over ATM
Glossary
PPPoE Point-to-Point Protocol over Ethernet

A specification for connecting multiple computer users on an Ethernet LAN
to a remote site through common CPE. PPPoE allows users to share a
common xDSL, cable modem, or wireless connection to the Internet. PPPoE
combines the PPP protocol, commonly used in dial-up connections, with the
Ethernet protocol, which supports multiple users in a LAN. The PPP
protocol information is encapsulated within an Ethernet frame.
PSD Power Spectral Density
PSTN Public Switched Telephone Network
A telephone network based on normal telephone signaling and ordinary
switched long distance telephone circuits.
PTC Positive Temperature Coefficient
A type of thermal resistor used for current limiting in circuitry.
PTP Precision Timing Protocol
PSU Power Supply Unit
PTM Packet Transfer Mode
A DSL framing mode that allows DSL equipment to transport packet-based
(for example, Ethernet or IP packets) rather than ATM-based data. PTM
involves 64/65 byte block coding of variable size frames or frame fragments
at the transmission convergence sublayer in the modem. PTM is defined in
the G.992.3 (ADSL2) and G.992.5 (ADSL2+) standards.
PVC Permanent Virtual Connection
PVID Port VLAN Identifier
PWE3 Pseudo Wire Emulation Edge to Edge
QL Quality Level of an external NTR source, determined by SSM messaging, or

by default, as specified in ITU-T Rec G.781 section 5.3.1
QoS Quality of Service
A measure of the quality of a data communications link provided to a
subscriber.
RADIUS Remote Authentication Dial-in User Service

A standardized method of information exchange between a device that
provides network access to users (RADIUS client) and a device that contains
authentication and profile information for the users (RADIUS server).
Glossary
RAL Restricted Access Location

RAM Remote Access Multiplexer
RARP Reverse Address Resolution Protocol
RB VLAN Residential Bridging VLAN
RDI Remote Defect Indication
READSL2 Reach Extended ADSL2
RED Random Early Detection
REN Ringer Equivalence Number
RFC Request for Comments
The name of the result and the process for creating a standard on the Internet.
New standards are proposed and published online, as a Request For
Comments. The IETF is the consensus-building body that facilitates
discussion, and eventually a new standard is established.
RFC is the prefix for all published IETF documents for Internet environment
standards; for example, the official standard for e-mail is RFC 822. RFC
documents typically define IP, TCP, and related application layer protocols.
RFT Remote Feeding Telecommunication
RG Residential Gateway
RIP Routing Information Protocol
An interior gateway protocol defined by the IETF (RIPv1 - RFC 1058 and
RIPv2 - RFC 2453) that specifies how routers exchange routing table
information. RIP is a routing protocol based on the distance vector
algorithm. With RIP, routers periodically exchange entire tables.
RJ-45 A single-line jack for digital transmission over ordinary phone wire, either
untwisted or twisted. It is the interface for Ethernet standards 10Base-T and
100Base-T.
RMI Remote Management Interface
RNM Residential Network Manager
RR Round Robin
RS Reed-Solomon
RSTP Rapid Spanning Tree Protocol
A protocol specified in IEEE 802.1w. It replaces the spanning tree protocol
specified by IEEE 802.1d. RSTP is targeted at switched networks with
point-to-point interconnections, and allows for much quicker
reconfiguration time (approximately 1 s) by allowing a rapid change in port
roles.
RT Remote Terminal
Glossary
RTL Routine Task List

RTP Real-time Transport Protocol
RTU Remote Test Unit
RU Rack Unit
A unit of vertical space in a standard 19 inch or 23 inch equipment rack. For
EIA-spaced racks, 1 RU equals 1.75 in. (4.45 cm). For WECO-spaced racks,
1 RU equals 2 in. (5.08 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
SAI Service Area Interface
SAP Service Access Point
SC Standard Connector
A small optical fiber connector.
SDU Service Data Unit
A unit of information from an upper-layer protocol that defines a service
request to a lower-layer protocol.
SELT Single-Ended Line Testing
SELV Safety Extra Low Voltage
SEM Sealed Expansion Module
A remote expansion unit for the 7330 ISAM FTTN. The SEM is a single LT
unit in a flood resistant, environmentally hardened enclosure designed for
remote outside deployment in hard-to-reach or low-density locations.
SFP Small Form-factor Pluggable
A specification for a new generation of optical modular transceivers. The
devices are designed for use with small form-factor connectors, and offer
high speed and physical compactness. They are hot-swappable.
SFTP Secured File Transfer Protocol
Glossary
SHDSL Symmetric High-speed Digital Subscriber Line

SHub Service Hub
7330 ISAM FTTN and 7302 ISAM Network Termination card Ethernet
switch (also known as LANX).
SI Système international d’unités
SIP Session Initiation Protocol
SLA Service Level Agreements
SLIC Subscriber Line Interface Circuit
SMF Single Mode Fiber
An optical fiber with a core diameter of less than 10 μm that is used for
high-bandwidth transmission over long distances.
SNMP Simple Network Management Protocol
A protocol used by network management to retrieve information about
connection status, configuration, and performance.
SNR Signal-to-Noise Ratio
SNTP Simple Network Time Protocol
A method of synchronizing network nodes. An SNTP server can be used by
multiple nodes to synchronize themselves.
SOHO Small Office Home Office
SONET Synchronous Optical Network
A transmission network that uses high-speed optical carriers.
SP Strict Priority
SRA Seamless Rate Adaptation
SSCS Service-specific convergence sublayer
SSH Secure Shell
SSM Source-specific multicast
or
Synchronization Status Message : indicate the synchronization status of a
communication link (SDH/SONET or Synchronous Ethernet based)
Glossary
STP Spanning Tree Protocol

A technique based on an IEEE 802.1d standard that detects and eliminates
forwarding loops in a bridged network. When multiple paths exist, STP
selects the most efficient path for the bridge to use. If that path fails, STP
automatically reconfigures the network to activate another path. This
protocol is used mostly by local bridges.
STU-C SHDSL Transceiver Unit – Central Office
STU-R SHDSL Transceiver Unit – Remote
S-VLAN Stacked VLAN
SWDB SoftWare DataBase
SWP SoftWare Package
TAC Test Access Control

TAP Test Access Port
or
Trouble Analysis Procedure
TAU Test Access Unit
TBC Time base correction
TC Transmission Convergence Layer
TCA Threshold Crossing Alarm
T-CONT Transmission Container, Traffic Container
TCP Transmission Control Protocol
A protocol for establishing a duplex connection between end systems for the
reliable delivery of data.
TCPAM Trellis Coded Pulse Amplitude Modulation
TCP/IP Transmission Control Protocol/Internet Protocol
A networking protocol that provides communication across interconnected
networks, and between computers with different hardware architectures and
various operating software.
TDM Time Division Multiplex
A transmission technique used to transmit several signals across a single
channel or bus by interleaving the signals in successive time slots. A specific
time slot or interval is assigned to each signal source
Glossary
TFTP Trivial File Transfer Protocol

TIA Telecommunications Industries Association
The group responsible for setting telecommunications standards in the
United States.
TL1 Transaction Language 1
Human-machine language standard for controlling network elements.
TNG Training Document
TNV Telecom Network Voltage
TOP Task-Oriented Practice
The TOP method is a documentation system that supports the installation,
operation, and maintenance of telecommunications equipment and software
through different layers of documentation.
Tx transmit
To send or carry signals or data from a device; any part of the equipment that
converts or encodes signals or data exiting from the equipment into the
desired form for transmission to other equipment.
UA User Agent
UC Unicast
UDP/IP User Datagram Protocol/Internet Protocol
A transport layer, connectionless mode protocol, providing a datagram mode
of communication for delivery to a remote or local user. UDP is part of the
TCP/IP suite.
UDS Unit Data Sheet
UNI User-to-Network Interface
UPBO Upstream Power Back-Off
UPS Uninterruptible Power Supply
upstream Transmission from the customer location to the network. On the network
termination (NT) side, transmit (Tx) indicates the upstream direction of the
transmission to the network. On the line termination (LT) side, receive (Rx)
indicates the upstream direction of the transmission to the OLT.
URI Universal Resource Identifier
USM User-based Security Model
Glossary
VACM View-based Access Control Model

VBAS Virtual Broadcast Access Server
VC Virtual Channel
A single communications connection identified by an office equipment
number, VPI, and VCI.
VCC Virtual Channel Connection
VCI Virtual Channel Identifier
An identifier in an ATM cell that distinguishes the data of one VC from the
data of another VC.
VCL Virtual Channel Link
VC/VP/VR Virtual Channel/Virtual Path/Virtual Router
VDSL Very High Bit Rate DSL
A variant of DSL that provides very high speed asymmetric data
transmission rates over a single twisted-pair copper telephone wire, but at
shorter ranges than other xDSL types. There is more than one type of VDSL.
VID VLAN Identifier
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 Video on Demand
VoIP Voice over IP
VoIP carries voice transmissions in packets and uses Internet Protocols (IP)
instead of using legacy public switched telephone network (PSTN)
circuit-switched technologies and protocols.
VP Virtual Path
A single communications connection identified by an office equipment
number and a VPI.
VPI Virtual Path Identifier
An identifier in an ATM cell that distinguishes the data of one VP from the
data of another VP.
VPLS Virtual Private LAN Service
VPRN Virtual Private Routed Network
Glossary
VP/VC Virtual Path/Virtual Channel

VRF Virtual Routing Forwarder
A logical or virtual routing function with associated routing table that can be
instantiated in a router capable of supporting IP VPN services.
VTU-C VDSL Transceiver Unit – Remote
VTU-R VDSL Transceiver Unit – Central Office
WAN Wide Area Network

WDM Wavelength Division Multiplexing
WECO Western Electric Company
For WECO-spaced racks, 1 RU equals 2 in. (5.08 cm).
WFQ Weighted Fair Queue
WRED Weighted Random Early Detection
WRR Weighted Round Robin
xDSL A general term that is used to refer to more than one type of DSL (for
example, ADSL, ADSL2, READSL, SHDSL, VDSL, VDSL2).
xTU-C xDSL Transceiver Unit – Central Office
xTU-R xDSL Transceiver Unit – Remote
XFP 10 Gigabit Small Form Factor Pluggable
An XFP optical module is a hot-swappable, protocol-independent optical
transceiver, typically operating at 850nm, 1310nm or 1550nm, for 10 Gb/s
SONET/SDH, Fiber Channel, Gigabit Ethernet, 10 Gigabit Ethernet and
other applications. XFP was developed by the XFP Multi Source Agreement
Group.
XoA encapsulation A general term used to refer to an unspecified type of encapsulation over
ATM.
Index
Numbers alarm types, 4-19

critical alarm LED, 4-19
802.1x current alarm list, 4-20
support, 10-10 derived alarms, 4-19, 4-22
disable alarms, 4-20
A enable alarms, 4-20
major alarm LED, 4-19
Access node control protocol
minor alarm LED, 4-19
about, 4-30
NSE alarms, 4-19
ADSL
programmable alarm configuration, 4-24
about, 2-4
programmable alarm filters, 4-21
ADSL1
SE alarms, 4-19
about, 2-4
snapshot alarm list, 4-20
ADSL2
spatial alarm filters, 4-21, 4-22
about, 2-5, 2-5
temporal alarm filters, 4-21, 4-22
ADSL2+
view alarms, 4-20
about, 2-6, 2-6
ARP
alarm filters
layer 2, 10-12
logging filters, 4-21
layer 3, 12-3
programmable filters, 4-21
Artificial noise
reporting filters, 4-21
about, 7-12
alarm LEDs, 4-19
ATM PW
alarm management, 4-18
about, 16-2
alarm delta logging, 4-20
cell concatenation, 16-3
alarm filters, 4-21
description, 16-2
alarm identification, 4-19
QoS, 16-4
alarm lists, 4-20
restrictions, 16-4
alarm logging, 4-20
support, 16-4
alarm severity, 4-19
Alcatel-Lucent 7302 ISAM | 7330 ISAM FTTN | 7356 ISAM FTTB R4.4.02 July 2012 IN-1
Index
B — logging alarms
B ISAM Voice
call handling
Bonding, 2-3 MEGACO, 8-98
about, 2-3 SIP, 8-100
ATM, 2-13 forwarding
ATM bonding, 2-13 Layer 4, 8-21
EFM, 2-14 MEGACO, 8-22
PTM bonding, 2-14 SIP, 8-35, 8-39
L2/L3 addressing
C MEGACO, 8-43, 8-52
SIP, 8-62, 8-67
C-VLAN cross-connect, 9-34
market applicability, 8-12
Configuration overrule
MEGACO
about, 7-14
network topology, 8-3
current alarm list, 4-20
product applicability, 8-12
D protocol stacks
MEGACO, 8-76
DELT SIP, 8-80
about, 5-8 SIP
derived alarms, 4-19, 4-22 network topology, 8-5
DHCP supplementary services, 8-102
layer 2, 10-13 traffic types
layer 3, 12-4 MEGACO, 8-13
DPBO, 7-9 SIP, 8-13
E L
EFMOAM LACP
general description, 5-10 about, 10-4
Ethernet layer 2
about, 2-11, 2-11 protocol handling, 10-2
ethernet user access interface, 9-13
auto-negotiation, 2-11 layer 2 forwarding
modes, 2-11 IPoA cross-connect, 9-47
layer 2 forwarding mode
I iBridge, 9-16
VLAN cross-connect, 9-32
iBridge, 9-16 layer 3
iBridge mode features, 9-17 forwarding, 11-2
IEEE 802.1q tagging, 9-2 protocol handling, 12-2
IGMP Line Instability
forwarding models, 13-14 Test features, 5-12
Impulse noise sensor Link transmission technology, 2-2
about, 7-10 logging alarms, 4-20
IPoA cross-connect, 9-47
IN-2 July 2012 Alcatel-Lucent 7302 ISAM | 7330 ISAM FTTN | 7356 ISAM FTTB R4.4.02
Index
Low power modes — S-VLAN/C-VLAN cross-connect
Low power modes programmable alarm filters, 4-21

L2 low-power mode, 7-4 configuration, 4-24
L3 idle power mode, 7-4 spatial alarm filters, 4-22
low power modes temporal alarm filters, 4-22
about, 7-4 protocol aware cross-connect, 9-43
Protocol Tracing
M about, 5-15
PSD shaping
MSTP about, 7-9
about, 10-6
MTA Q
in 7302 ISAM, 5-6
in 7330 ISAM FTTN, 5-6 QoS
TAC, 5-7 about, 14-2
test access modes, 5-5 downstream, 14-9
multi-ADSL policy framework, 14-23
ADSL, 2-4 profiles, 14-17
ADSL2, 2-5 traffic classes, 14-11
ADSL2+, 2-6 QoS profiles
READSL2, 2-7 CAC profile, 14-17
SELT, 5-8, 5-8 marker profile, 14-21
multi-VLAN, 9-5 policer profile, 14-22
multicast queue profile, 14-18
forwarding models, 13-14 session profile, 14-21
N R
non-service affecting alarms, 4-19 RADIUS
NT redundancy about, 6-2, 15-2
about, 3-2 authentication, 15-2
link only protection, 3-5 encryption, 15-3
features, 15-2
O proxy, 15-2
server, 15-2
Operational modes READSL
ADSL1, 2-5 about, 2-7
ADSL2, 2-6 READSL2
ADSL2+, 2-7 about, 2-7
READSL, 2-7 RSTP
about, 10-6
P
in 7302 ISAM, 10-6
performance statistics, 4-18
PPPoE S
about, 10-18 S-VLAN cross-connect, 9-37
PPPoE relay, 10-18 S-VLAN/C-VLAN cross-connect, 9-35
Alcatel-Lucent 7302 ISAM | 7330 ISAM FTTN | 7356 ISAM FTTB R4.4.02 July 2012 IN-3
Index
Seamless rate adaptation — xDSL
Seamless rate adaptation profile overview, 2-9

modes, 7-6 profiles, 2-9
SELT Virtual noise
about, 5-7 about, 7-11
multi-ADSL, 5-8, 5-8 VLAN cross-connect, 9-32
VDSL, 5-8, 5-8 C-VLAN cross-connect, 9-34
service affecting alarms, 4-19 protocol aware cross-connect, 9-43
SHDSL S-VLAN cross-connect, 9-37
about, 2-10, 2-10, 2-10 S-VLAN/C-VLAN cross-connect, 9-35
supported standards, 2-10 VLAN stacking, 9-33
snapshot alarm list, 4-20 VLAN forwarding, 9-2
SRA VLAN frame
about, 7-6 frame type usage, 9-4
statistics multi-VLAN, 9-5
performance statistics, 4-18 tagging, 9-2
system logs VLAN translation, 9-5
configuring, 4-11 VLAN translation, 9-5
filters, 4-11
message types, 4-11 X
monitoring, 4-12
severity level, 4-11 xDSL
INP, 7-3
T
Test
Line Instability, 5-12
Transfer modes, 2-3
U
UPBO
equal FEXT, 7-8
policing, 7-8
user access interface
layer 2, 9-13
V
VDSL
about, 2-7
SELT, 5-8, 5-8
VDSL1
about, 2-8, 2-8
VDSL2
about, 2-8, 2-8
operational modes, 2-9
IN-4 July 2012 Alcatel-Lucent 7302 ISAM | 7330 ISAM FTTN | 7356 ISAM FTTB R4.4.02
Customer documentation and product support
Customer documentation
http://www.alcatel-lucent.com/myaccess
Product manuals and documentation updates are available at
alcatel-lucent.com. If you are a new user and require access to this
service, please contact your Alcatel-Lucent sales representative.
Technical Support
http://www.alcatel-lucent.com/support
Documentation feedback
documentation.feedback@alcatel-lucent.com
© 2012 Alcatel-Lucent. All rights reserved.
3HH-10693-AAAA-TQZZA Edition 02 Released

3HH-10693-AAAA-TQZZA-02-System Description For FD 24Gbps NT R4 4 X

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3HH-10693-AAAA-TQZZA-02-System Description For FD 24Gbps NT R4 4 X

Uploaded by

Copyright:

Available Formats

Alcatel-Lucent 7302

INTELLIGENT SERVICES ACCESS MANAGER

Copyright 2012 Alcatel-Lucent.

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

Acronyms and initialisms

Assistance and ordering phone numbers

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

Warning — Warning indicates that the described activity or situation

Caution — Caution indicates that the described activity or situation

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

Procedures with options or substeps

Procedure 1 Example of options in a procedure

a This is one option.

b This is another option.

2 You must perform this step.

Procedure 2 Example of required substeps in a procedure

i This is the first substep.

ii This is the second substep.

iii This is the third substep.

2 You must perform this step.

2— System interface overview 2-1

3— Failure protection and redundancy provisions in ISAM 3-1

5— Line testing features 5-1

6— Network timing reference support in ISAM 6-1

7— xDSL features 7-1

7.13 Configurable US/ DS memory split .................................................. 7-15

8— Integrated Voice service: ISAM Voice 8-1

9— Layer 2 forwarding 9-1

10 — Protocol handling in a Layer 2 forwarding model 10-1

12 — Protocol handling in a Layer 3 forwarding model 12-1

13 — Multicast and IGMP 13-1

14 — Quality of Service 14-1

15 — Resource Management and Authentication 15-1

16 — ATM Pseudowire emulation 16-1

A. Cross-domain solutions A-1

B. RADIUS Attributes B-1

1.1 General 1-2

1.2 Supported User Interfaces 1-2

1.3 Document Structure 1-3

The ISAM is a frame-based Multi Service Access Platform, offering high-density

1.2 Supported User Interfaces

Figure 1-1 ISAM Network Architecture

1.3 Document Structure

2.1 General 2-2

2.2 Overview 2-2

2.3 Multi-ADSL 2-4

2.4 VDSL 2-7

2.5 SHDSL 2-10

2.6 Ethernet 2-11

2.7 Inverse multiplexing for ATM 2-13

2.8 ATM/PTM bonding 2-13

2.9 Overview of ISAM Voice interfaces 2-14

2.10 E1 TDM Interface 2-15

2.11 Overview of ISAM support for remote management of

This chapter provides a general description of the system interfaces.

Note — For ease of understanding, the ISAM Voice links are

Link transmission technology

Do wn s tre a m b it ra te (Mb /s)

The following bonding methods are defined within the standards:

Asymmetric nature of ADSL

Table 2-1 lists the supported ADSL1 operational modes.

Table 2-1 ADSL operational modes

Operation Mode Description