7342 ISAM FTTU OLT ETSI R04.06.11 Product Information 3FE 53568 AAAA TCZZA PDF

Alcatel-Lucent 7342
INTELLIGENT SERVICES ACCESS MANAGER FIBER TO THE USER

P-OLT R04.06.11
ETSI PRODUCT INFORMATION MANUAL
3FE 53568 AAAA TCZZA Edition 01
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 2010 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, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All
other trademarks are the property of their respective owners.
Copyright 2010 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
7342 ISAM Fiber to the User (7342 ISAM FTTU).
Scope
This documentation set provides information about safety, features and
functionality, ordering, hardware installation and maintenance, CLI and TL1
commands, and software installation procedures.
Audience
This documentation set is intended for planners, administrators, operators, and
maintenance personnel involved in installing, upgrading, or maintaining the
7342 ISAM FTTU.
Prerequired knowledge
The reader must be familiar with general telecommunications principles.
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:
www1.alcatel-lucent.com/comps/pages/carrier_support.jhtml.
For ordering information, contact your Alcatel-Lucent sales representative.
Alcatel-Lucent 7342 ISAM FTTU P-OLT R04.06.11 May 2010

3FE 53568 AAAA TCZZA Edition 01 ETSI Product Information Manual
iii
Preface
Alcatel-Lucent quality processes

Alcatel-Lucents 7342 ISAM FTTU optical network terminals (ONTs)
manufacturing, testing, and inspecting practices are in compliance with
GR-1252-CORE and TL 9000 requirements. These requirements are documented in
the Operations Quality Plan 8BD-00023-4204-QRZZA, the Alcatel North American
Quality Manual 8BD-00001-0000-QRZZA, and the Wireline Network Quality
Manual 8AB-83179-0001-QRAAA.
The quality plans and practices adequately ensure that technical requirements and
customer end-point requirements are met. The customer or its representatives may
be allowed to perform on-site quality surveillance audits, as agreed upon during
contract negotiations.
Safety information
This documentation set provides safety guidelines for specific ETSI or ANSI
markets.
Documents
Documentation available for the 7342 ISAM FTTU is listed in the 7342 ISAM FTTU
P-OLT Planning and Ordering Guide.
Special information
The following are examples of how special information is presented in this
documentation set.
Danger Danger indicates that the described activity or situation
may result in serious personal injury or death; for example, high

voltage or electric shock hazards.
Warning Warning indicates that the described activity or situation
may, or will, cause equipment damage or serious performance

problems.
Caution Caution indicates that the described activity or situation
may, or will, cause service interruption.
Note A note provides information that is, or may be, of special
interest.
iv
May 2010 Alcatel-Lucent 7342 ISAM FTTU P-OLT R04.06.11

ETSI Product Information Manual Edition 01 3FE 53568 AAAA TCZZA
Preface
Procedures with options or substeps

In a procedure, options are identified by letters, substeps are identified by roman
numerals.
Procedure 1 Example of options in a procedure

At step 1, you can choose option a or b. At step 2, you must do what the step indicates.
1
This step offers two options. You must choose one of the following:
a
This is one option.
This is another option.
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.
You must perform this step.
Multiple PDF document search

You can use Adobe Reader Release 6.0 and later to search multiple PDF files for a
common term. Adobe Reader displays the results in a single display panel. The
results are grouped by PDF file, and you can expand the entry for each file.
Note The PDF files in which you search must be in the same
folder.

Preface
Procedure 3 To search multiple PDF files for a common term

1
Open Adobe Acrobat Reader.
Choose EditSearch from the Acrobat Reader main menu. The Search PDF panel
appears.
Enter the search criteria.
Click on the All PDF Documents In radio button.
Select the folder in which to search using the drop-down menu.
Click on the Search button.

Acrobat Reader displays the search results. You can expand the entries for each
document by clicking on the + symbol.
vi

ETSI P-OLT safety guidelines
This chapter provides information about the mandatory regulations that govern the
installation and operation of the 7342 ISAM FTTU packet optical line termination
(P-OLT) system.
Safety instructions
This section describes the safety instructions that are provided in the
7342 ISAM FTTU customer documentation, equipment, and location where the
equipment resides.
Safety instruction boxes

The following are instructions provided in the 7342 ISAM FTTU customer
documentation. Observe the instructions whenever you see them to meet safety
requirements.
The following is an example of the Danger box.
Danger Possibility of personal injury.
The Danger box indicates that the described activity or situation may pose a threat to
personal safety. It calls attention to a situation or procedure which, if not correctly
performed or adhered to, may result in death or serious physical harm.
Do not proceed beyond a Danger box until the indicated conditions are fully
understood and met.

vii
The following is an example of the Warning box.

Warning 1 Possibility of equipment damage.
Warning 2 Possibility of data loss.
The Warning box indicates that the described activity or situation may, or will, cause
equipment damage, loss of data, or serious performance problems. It calls attention
to a possible equipment-damaging situation or provides essential information for
avoiding degradation of system operations or data.
Do not proceed beyond a Warning box until the indicated conditions are fully
understood and met.
The following is an example of the Caution box.
Caution 1 Possibility of service interruption.
Caution 2 Service interruption.
The Caution box indicates that the described activity or situation may, or will, cause
service interruption.
Do not proceed beyond a Caution box until the indicated conditions are fully
understood and met.
The following is an example of the Note box.
Note Information of special interest.
The Note box provides information that assists the personnel working with
7342 ISAM FTTU. It does not provide safety related instructions.
Safety related labels

Safety warning labels are located on P-OLT equipment. The following are sample
safety labels.
ESD warning label
Figure 1 shows the electrostatic discharge (ESD) warning label that contains the ESD
awareness symbol for devices and assemblies that are susceptible to ESD.
viii


Figure 1 ESD warning label
18456
Hazardous voltage warning label
Figure 2 shows the hazardous voltage warning label. The symbol calls attention to
the risk of electric shock. It is generally used for voltages in excess of 1000 V, but
can also be used for lower voltages if an explanation is provided in the
documentation.
Figure 2 Hazardous voltage warning label
18457
Laser warning labels
The following figures show the labels related to laser product, classification and
warning.
Figure 3 shows a laser product label.
Figure 3 Laser product label
18455
Figure 4 shows a laser classification label. Laser classification labels may be

provided in other languages.

ix

Figure 4 Laser classification label
CLASS 1 LASER PRODUCT
'
PRODUCTO LASER
CLASE 1
'
CLASE
1 DEL LASER
LASER CLASSE 1
18992
Figure 5 shows a laser warning label and an explanatory label for laser products.
Explanatory labels may be provided in other languages. The explanatory label
provides the following information:
a warning that calls attention to the invisible laser radiation

an instruction against staring into the beam or view directly with optical
instruments
wavelength
normal output power
maximum output power


Figure 5 Laser warning labels
INVISIBLE LASER RADIATION

DO NOT STARE INTO BEAM
OR VIEW DIRECTLY WITH
OPTICAL INSTRUMENTS
Wavelength(s): xxxx nm
Normal output power: xx m W
Max output power: yyy m W
Laser Warning Label
Laser Warning Label
CLASS 1 LASER PRODUCT
RAYONNEMENT LASER CLASSE 1

RAYONNEMENT LASER INVISIBLE
EVITER TOUTE EXPOSITION AU FAISCEAU
NE PAS DEMONTER. FAIRE APPEL A UN PERSONNELL QUALIFIE
'
CLASE 1 DEL LASER

RADIACION DE LASER INVISIBLE. EVITAR CUALOUIER EXPOSICION AL
RAYO LASER. NO DESMONTAR. LLAMAR A PERSONAL AUTORIZADO
INVISIBLE LASER RADIATION PRESENT AT FIBER OPTIC CABLE
WHEN NOT CONNECTED. AVOID DIRECT EXPOSURE TO BEAM.
Laser Warning Label
18993
Protective grounding terminal
Figure 6 and Figure 7 show the symbols indicating a terminal that must be connected
to earth ground before any other connections to the equipment can be made.
Figure 6 shows the symbol for a supply wire protective earth terminal. The symbol
is placed at the equipment earthing point and is mandatory for all grounding
equipment.
Figure 6 Supply wire protective earth terminal
9717
Figure 7 shows the symbol for an earth terminal.

Figure 7 Earth terminal
9718

xi
Safety standards compliance

This section describes the compliance of the P-OLT equipment to European safety
standards.
EMC, EMI, and ESD standards compliance

The P-OLT equipment has been tested for compliance with the following EMC,
EMI, and ESD requirements:
EN 300-386 V1.3.2 (2003-05): Electromagnetic Compatibility and Radio
Spectrum Matters (ERM): Telecommunications Network Equipment;

Electromagnetic Compatibility (EMC) requirements; Electrostatic Discharge
(ESD) requirements.
EN55022 (1998): Class A, Information Technology Equipment, Radio
Disturbance Characteristics, limits and methods of measurement (OLTS-M
system configuration)
EN55022 (1998): Class B, Information Technology Equipment, Radio
Disturbance Characteristics, limits and methods of measurement (ALTS-N
system configuration)
EN55024 (1998): Information Technology Equipment, Immunity
Characteristics, limits and methods of measurement
European Union EMC Directive 89/336/EEC of May 3 1989
Environmental standards compliance

The P-OLT equipment has been tested for compliance with the EN 300-019
European environmental requirements.
Equipment safety standards compliance

The P-OLT equipment has been tested for compliance with the EN 60950-1
requirements for Safety of Information Technology Equipment for use in a restricted
location (R-269).
Laser product standards compliance

The P-OLT equipment has been tested for compliance with the EN 60825-1 and IEC
60825-2 requirements for laser products.
Resistibility requirements compliance

The ALTS-N (containing GLT2-A, EHNT-A, and ancillary cards) P-OLT
equipment has been tested and is compliant to the requirements of the ITU
Recommendation K.20 for resistibility of telecommunication equipment installed in
a telecommunication center to overvoltage and overcurrents.
xii

Electrical safety guidelines

This section provides information about electrical safety guidelines for the P-OLT
rack equipment.
Equipment classification
The P-OLT equipment is classified as Class 1 according to its protection against
electric shock.
The P-OLT rack equipment is dc powered by:
a branch battery A with one, two, or three feeders (A1, A2, A3) for the dc power
supply from battery A in the power plant
a branch battery B with one, two, or three feeders (B1, B2, B3) for the dc power
supply from battery B in the power plant
one, two, or three insulated BATRET conductors for battery return to both
batteries
The 7342 ISAM FTTU rack equipment supports both 3-wire and 2-wire power
configuration options. For a 2-wire power supply, the ground is achieved by
connecting the frame ground connection to BATRET. For a 3-wire power supply, an
additional PE conductor is required to provide a path to ground for the metal rack
structure on external surfaces.
Note In a 3-wire system with fixed shelf powering feeders A1, A2,
B1, and B2 power the two shelves. Feeder A3 powers the upper fan
unit and feeder B3 powers the lower fan unit. One or two insulated
BATRET conductors provide battery return.
Protection against indirect contact must be provided by a circuit breaker or fuse

release.
Access area restriction for rack equipment

The P-OLT rack equipment is classified as permanently connected equipment and
must be installed in a restricted access location (RAL).
The P-OLT rack equipment is installed in the central office or remote cabinet. Both
locations are classified as RAL in accordance with EN 60950-1.
In an RAL, dangerous voltages or hazardous energy levels can cause personal harm
and equipment damage. Only qualified service personnel should have access to the
area where the rack equipment reside. The installation, operations, and maintenance
of the rack equipment must be restricted to qualified personnel.
Observe the following warning:
Warning Possibility of equipment damage. Dangerous voltages
and electrical shock by unintentional contact with circuits exist inside
the rack.

xiii
Note There are no operator serviceable parts inside the P-OLT
equipment rack. Refer all service operations to qualified service

personnel.
Battery feed circuit breaker

Before replacing the P-OLT rack equipment, ensure that the battery feed circuit
breakers are off.
Battery voltage
There is a risk of personal injury from unintentional contact with connectors. Service
personnel must be protected against the battery voltage present on the connectors.
Observe the following warning:
Danger Electrical shock hazard due to battery voltage present at
connectors.
Note There are no operator serviceable parts inside the P-OLT
equipment rack. Refer all service operations to qualified service

personnel.
Electrical SFP cable safety

Use shielded CAT 5e or better grade Ethernet cables for use with electrical interfaces
on the NT cards.
Laser safety guidelines

In accordance with EN 60825-1, the P-OLT equipment is classified as a Class 1 laser
product based on the accessible emission. The classification of the P-OLT as a Class
1 laser product is based on the transmit optical outputs for the P-OLT.
Observe the following warning when performing installation, operations, and
maintenance tasks on the P-OLT equipment.
Danger Invisible laser radiation could be present at the fiber optic
cable when the cable is removed from the connector. Avoid direct
exposure to the beam.
Only qualified service personnel who are thoroughly familiar with laser radiation
hazards should install or remove the fiber optic cables and units in this system.
Figure 3, Figure 4, and Figure 5 show the laser warning labels on the P-OLT
equipment.
xiv

Transmit optical output

The maximum transmit optical output of the 7342 ISAM FTTU components are
listed as follows:
EHNT-A, EHNT-B and EXNT-A:

1-GE 850 nm 550 m SFP: 4.0 dBm
1-GE 1310 nm 10 km SFP: 3.0 dBm
1-GE 1310 nm 40 km SFP: 0 dBm
1-GE 1550 nm 80 km SFP: +5 dBm
10-GE 850 nm 300 m XFP: 1.08 dBm
10-GE 1310 nm 10 km XFP: 0.5 dBm
10-GE 1550 nm 40 km XFP: 4.0 dBm
GLT2-A and GLT2-B: +5 dBm
GLT4-A: +5 dBm
Laser classification
The P-OLT is a Class 1 laser product. According to the EN 60825-1 and IEC 60825-2
requirements, lasers must not exceed the accessible emission limit of Class 1 under
all condition of operations, maintenance, service, and failure.
The P-OLT equipment contains two network termination (NT) cards for redundancy.
Each NT card contains 1-GE SFP and 10-GE XFP pluggable optical modules. These
optical modules are classified as Hazard Level 1 laser product.
The following is a laser hazard warning box typically seen in the 7342 ISAM FTTU
installation and maintenance procedures. Eyes can be damaged when they are
exposed to a laser beam. Take necessary precautions before plugging in the optical
modules.
Danger Possibility of equipment damage. Risk of eye damage by
laser radiation.
Normal laser operation

The optical fiber communication systems used in the rack consist of a laser
transmitter module and an optical receiver. For connection to the external optical
cable system, optical connectors have been provided at the front panel of the NT card
for GE links.
In normal operation, the laser transmitter is enclosed by the optical connector and the
external optical fiber. Laser radiation is always present when the laser unit is
powered on, limited to maximum 1 mW.
Observe the following warning. Eyes can be damaged when they are exposed to a
laser beam. Operating personnel must observe the instructions on the laser
explanatory label before plugging in the optical module.
Danger Risk of eye damage by laser radiation.

xv
Location class
According to EN 60825-2, the laser device, when mounted in the rack, is classified
as a hazard level 1 product. The fiber cables pass through the bottom (or top) rack
entrance. The use of cable supports and guides protects the receptacles from strain.
The 7342 ISAM FTTU rack equipment is placed in the central office or remote
cabinets, which is an RAL. In an RAL, activities inside the rack equipment must be
conducted by qualified personnel only. Direct viewing of the laser beam is only
possible when there is a disconnected fiber in an open rack.
Note The remote cabinet application requires that temperature
hardened optical modules be used in the NT card.
ESD safety guidelines

The 7342 ISAM FTTU equipment is sensitive to ESD. See Figure 1 for the ESD
awareness label.
During installation and maintenance, operating personnel must take precautions by
wearing a wrist strap to protect potential damages caused by ESD.
It is recommended that site preparation be performed before installing the P-OLT
equipment. In addition, there shall be measures to control relative humidity, use
static dissipating material for furniture or flooring, and restrict the use of air
conditioning.
Precautions
The necessary precautions must be taken to discharge operating personnel by the use
of approved discharge straps or links and a conductive layer on the exchange floor.
The following precautions must be observed.
Wear an antistatic wristband when:

replacing plug-in units.
operating circuit breakers in the rack.
the ESD awareness label is present; see Figure 1.
Do not wear or use clothes made of wool, nylon, or any synthetic material.
Such fabrics are major sources of static build-up.

When handling cards, do not use gloves and finger covers, unless they are made
of cotton.
Always handle the cards by the edges.
Do not touch conductor paths with fingers or palms.
Remove the antistatic wristband and connection cord from the rack after use.
They must not be left inside the rack when not used.
Earth bonding points for the wristband are provided on the rack, and are indicated by
the label shown in Figure 8.
xvi


Figure 8 Label for earth bonding point
EARTH
BONDING
POINT
17659
Environmental requirements
Observe the following requirements when handling the P-OLT equipment.
Storage
According to ETS 300-019-1-1 - Class 1.1, storage of P-OLT equipment must be in
Class 1.1, weather-protected, not temperature-controlled storage locations.
Transportation
According to EN 300-019-1-2 - Class 2.3, transportation of the P-OLT equipment
must be packed, public transportation with no rain on packing allowed.
Stationary use
According to EN 300-019-1-3 - Class 3.1/3.2/3.E, stationary use of P-OLT
equipment must be in a temperature-controlled location, with no rain on packaging
allowed, and with no condensation allowed,.
Thermal limitations
When the P-OLT is installed in the CO or CEV, install air filters on the P-OLT. The
thermal limitations for P-OLT operation in a CO or CEV are:
operating temperature: 5C (41F) to 40C (104F)

short-term temperature: 5C (23F) to 50C (122F)
operating relative humidity: 5% to 85%
short-term relative humidity: 5% to 95%, but not to exceed 0.024 kg of water/kg
End-of-life collection and treatment

At the end of life, the P-OLT products are subject to the applicable local legislations
that implement the European Directive 2002/96EC on waste electrical and electronic
equipment (WEEE).
There can be different requirements for collection and treatment in different member
states of the European Union.

xvii
xviii

ETSI environmental and CRoHS guidelines
This chapter provides information about the ETSI environmental China Restriction
of Hazardous Substances (CRoHS) regulations that govern the installation and
operation of the 7342 ISAM FTTU packet optical line termination (P-OLT) and
Optical Network Termination (ONT) systems. This chapter also includes
environmental operation parameters of general interest.
Environmental labels
This section describes the environmental instructions that are provided in the
7342 ISAM FTTU customer documentation, equipment, and location where the
equipment resides.
Overview
CRoHS is applicable to Electronic Information Products (EIP) manufactured or sold
and imported in the territory of the mainland of the Peoples Republic of China. EIP
refers to products and their accessories manufactured by using electronic information
technology, including electronic communications products and such subcomponents
as batteries and cables.
Environmental related labels

Environmental labels are located on appropriate equipment. The following are
sample labels.

xix
Products below Maximum Concentration Value (MCV) label
Figure 1 shows the label that indicates a product is below the maximum
concentration value, as defined by standard SJ/T11363-2006 (Requirements for
Concentration Limits for Certain Hazardous Substances in Electronic Information
Products). Products with this label are recyclable. The label may be found in this
documentation or on the product.
Figure 1 Products below MCV value label
18986
Products containing hazardous substances above Maximum Concentration

Value (MCV) label
Figure 2 shows the label that indicates a product is above the maximum
concentration value, as defined by standard SJ/T11363-2006 (Requirements for
Concentration Limits for Certain Hazardous Substances in Electronic Information
Products). The number contained inside the label indicates the
Environment-Friendly User Period (EFUP) value. The label may be found in this
documentation or on the product.
xx


Figure 2 Products above MCV value label
18985
Together with major international telecommunications equipment companies,

Alcatel-Lucent has determined it is appropriate to use an EFUP of 50 years for
network infrastructure equipment and EFUP of 20 years for handsets and
accessories. These values are based on manufacturers' extensive practical experience
of the design, manufacturing, maintenance, usage conditions, operating
environments and physical condition of infrastructure and handsets after years of
service. The values reflect minimum values and refer to products operated according
to the intended use conditions. See Hazardous Substances Table (HST) for more
information.
Hazardous Substances Table (HST)

This section describes the compliance of the P-OLT and ONT equipment to the
CRoHS standard when the product and subassemblies contain hazardous substances
beyond the MCV value. This information is found in this user documentation where
part numbers for the product and subassemblies are listed. It may be referenced from
ordering information in other P-OLT and ONT documentation.
In accordance with the Peoples Republic of China Electronic Industry Standard
Marking for the Control of Pollution Caused by Electronic Information Products
(SJ/T11364-2006), customers may access the Alcatel-Lucent Hazardous Substance
Table, in Chinese, from the following location.
http://www.alcatel-sbell.com.cn/wwwroot/images/upload/private/1/media/ChinaR
oHS.pdf
Other environmental requirements

Observe the following requirements when handling the P-OLT or ONT equipment.

xxi
ONT environmental requirements

See the ONT technical specification documentation for more information about
temperature ranges.
Storage
According to ETS 300-019-1-1 - Class 1.1, storage of P-OLT equipment must be in
Class 1.1, weather-protected, not temperature-controlled storage locations.
Transportation
According to EN 300-019-1-2 - Class 2.3, transportation of the P-OLT equipment
must be packed, public transportation with no rain on packing allowed.
Stationary use
According to EN 300-019-1-3 - Class 3.1/3.2/3.E, stationary use of P-OLT
equipment must be in a temperature-controlled location, with no rain on packaging
allowed, and with no condensation allowed.
Thermal limitations
When the P-OLT is installed in the CO or CEV, install air filters on the P-OLT. The
thermal limitations for P-OLT operation in a CO or CEV are:
operating temperature: 5C (41F) to 40C (104F)

short-term temperature: 5C (23F) to 50C (122F)
operating relative humidity: 5% to 85%
short-term relative humidity: 5% to 95%, but not to exceed 0.024 kg of water/kg
Material content compliance

European Union (EU) Directive 2002/95/EC, Restriction of the use of certain
Hazardous Substances (RoHS), restricts the use of lead, mercury, cadmium,
hexavalent chromium, and certain flame retardants in electrical and electronic
equipment. This Directive applies to electrical and electronic products placed on the
EU market after 1 July 2006, with various exemptions, including an exemption for
lead solder in network infrastructure equipment. Alcatel-Lucent products shipped to
the EU after 1 July 2006 comply with the EU RoHS Directive.
xxii

End-of-life collection and treatment

Electronic products bearing or referencing the symbol shown in Figure 3 when put
on the market within the European Union (EU), shall be collected and treated at the
end of their useful life, in compliance with applicable EU and local legislation. They
shall not be disposed of as part of unsorted municipal waste. Due to materials that
may be contained in the product, such as heavy metals or batteries, the environment
and human health may be negatively impacted as a result of inappropriate displosal.
Note In the European Union, a solid bar under the crossed-out
wheeled bin indicates that the product was put on the market after 13
August 2005.
Figure 3 Recycling/take back/disposal of product symbol
At the end of life, the P-OLT products are subject to the applicable local legislations
that implement the European Directive 2002/96EC on waste electrical and electronic
equipment (WEEE).
There can be different requirements for collection and treatment in different member
states of the European Union.
Moreover, in compliance with legal requirements and contractual agreements, where
applicable, Alcatel-Lucent will offer to provide for the collection and treatment of
Alcatel-Lucent products bearing the logo at the end of their useful life, or products
displaced by Alcatel-Lucent equipment offers. For information regarding take-back
of equipment by Alcatel-Lucent, or for more information regarding the requirements
for recycling/disposal of product, please contact your Alcatel-Lucent account
manager or Alcatel-Lucent takeback support at takeback@alcatel-lucent.com.

xxiii
xxiv

Contents
Preface
iii
Scope
............................................................................................... iii
Audience ............................................................................................... iii
Prerequired knowledge ............................................................................... iii
Assistance and ordering phone numbers ........................................................... iii
Alcatel-Lucent quality processes .................................................................... iv
Safety information ..................................................................................... iv
Documents .............................................................................................. iv
Special information.................................................................................... iv
Procedures with options or substeps ................................................. v
Procedure 1 Example of options in a procedure................................... v
Procedure 2 Example of required substeps in a procedure ...................... v
Multiple PDF document search........................................................................ v
Procedure 3 To search multiple PDF files for a common term ................. vi
vii
Safety instructions .................................................................................... vii

Safety instruction boxes ............................................................. vii
Safety related labels..................................................................viii
Safety standards compliance........................................................................ xii
EMC, EMI, and ESD standards compliance ......................................... xii
Environmental standards compliance .............................................. xii
Equipment safety standards compliance .......................................... xii
Laser product standards compliance ............................................... xii
Resistibility requirements compliance ............................................. xii
Electrical safety guidelines......................................................................... xiii
Equipment classification ............................................................ xiii
Access area restriction for rack equipment ...................................... xiii

xxv
Contents
Battery feed circuit breaker.........................................................xiv

Battery voltage ........................................................................xiv
Electrical SFP cable safety ..........................................................xiv
Laser safety guidelines...............................................................................xiv
Transmit optical output .............................................................. xv
Laser classification.................................................................... xv
Normal laser operation ............................................................... xv
Location class ..........................................................................xvi
ESD safety guidelines.................................................................................xvi
Precautions.............................................................................xvi
Environmental requirements ....................................................................... xvii
Storage................................................................................. xvii
Transportation ........................................................................ xvii
Stationary use ........................................................................ xvii
Thermal limitations .................................................................. xvii
End-of-life collection and treatment ............................................. xvii
xix
Environmental labels .................................................................................xix

Overview ...............................................................................xix
Environmental related labels........................................................xix
Hazardous Substances Table (HST).................................................................xxi
Other environmental requirements ................................................................xxi
ONT environmental requirements ................................................. xxii
Storage................................................................................. xxii
Transportation ........................................................................ xxii
Stationary use ........................................................................ xxii
Thermal limitations .................................................................. xxii
Material content compliance ....................................................... xxii
End-of-life collection and treatment ............................................ xxiii
General system description

1
Overview
1.1
1.2
1.3
1.4
xxvi
1-1
7342 ISAM FTTU overview.............................................................. 1-2

GPON features ........................................................................... 1-4
Services features ........................................................................ 1-4
Voice service.......................................................................... 1-4
Data and IPTV services .............................................................. 1-4
RF video service ...................................................................... 1-5
CES encapsulated DS1/E1 ........................................................... 1-5
Network interfaces ..................................................................... 1-5
P-OLT interfaces ..................................................................... 1-5
V-OLT interfaces ..................................................................... 1-6
ONT interfaces........................................................................ 1-6
Contents
1.5
Feature descriptions
2.1
2.2
2.3
2.4
2.5
2.6
2.7
2.8
2.9
2.10
2.11
2.12
2.13
2.14
2.15
4.4
4-1
Overview ................................................................................. 4-2

7342 ISAM FTTU system architecture ................................................ 4-2
P-OLT functional blocks ................................................................ 4-2
Network termination ................................................................ 4-4
Line termination...................................................................... 4-6
V-OLT functional blocks................................................................ 4-8
RF video signal distribution......................................................... 4-8
RF video services ..................................................................... 4-8
Upstream signal and data channels ............................................... 4-9
RF video service management ..................................................... 4-9
Equipment layout
5.1
5.2
3-1
Overview ................................................................................. 3-2

Release FGU 04.04.xx application notes ............................................ 3-2
Release FGU 4.3.5 application notes................................................. 3-3
Release FGU 4.3.0 application notes................................................. 3-3
Release FGU 4.2 application notes ................................................... 3-4
Functional description
4.1
4.2
4.3
2-1
Overview ................................................................................. 2-2

Release FGU 04.06.08 features ....................................................... 2-2
Release FGU 04.06.00 and 04.06.01 features....................................... 2-3
Release FGU 04.04.10 and 04.04.10a features ..................................... 2-8
Release FGU 04.04.00 and 04.04.01 features....................................... 2-9
Release FGU 4.3.5 features .......................................................... 2-11
Release FGU 4.3 features ............................................................. 2-11
Application notes
3.1
3.2
3.3
3.4
3.5
Element management system ......................................................... 1-6

5523 AWS .............................................................................. 1-6
5520 AMS .............................................................................. 1-6
5528 WAM ............................................................................. 1-7
5-1
Overview ................................................................................. 5-2

P-OLT equipment layout ............................................................... 5-2
OLT rack ............................................................................... 5-2
OLT ALTS-N shelf ..................................................................... 5-4
P-OLT OLTS-M shelf .................................................................. 5-6

xxvii
Contents
5.3
5.4
5.5
Operations, administration, and maintenance

6.1
6.2
6.3
6.4
6.5
6.6
7.5
7.6
7.7
7.8
7.9
6-1
Overview ................................................................................. 6-2

Management interfaces ................................................................ 6-2
Craft terminal ........................................................................ 6-4
TL1 and CLI access protocol options .............................................. 6-5
Ethernet ports on the AACU and the P-OLT backplane......................... 6-5
5520 AMS connection options ...................................................... 6-5
5528 WAM connection options ..................................................... 6-5
EMS functions ............................................................................ 6-6
5520 AMS .............................................................................. 6-6
5528 WAM ............................................................................. 6-6
Operations, administration and maintenance ...................................... 6-7
Hardware operation, administration, and maintenance tasks ................ 6-7
ONT repair and return information................................................ 6-8
Troubleshooting ......................................................................... 6-8
OSMINE certification .................................................................... 6-8
Technical specifications
7.1
7.2
7.3
7.4
xxviii
OLT shelf backplane ................................................................. 5-7

Cards in the OLT shelf ............................................................... 5-7
V-OLT equipment layout ............................................................... 5-9
Video coupler equipment layout...................................................... 5-9
Video coupler fiber rack ........................................................... 5-10
Video coupler shelf ................................................................. 5-10
Video coupler WDM tray............................................................ 5-10
ONT equipment layout ................................................................ 5-12
ONT connection capacity .......................................................... 5-12
7-1
Overview ................................................................................. 7-2

P-OLT equipment........................................................................ 7-2
Video coupler equipment .............................................................. 7-3
System and service capacity specifications ......................................... 7-4
Service and system capacity ....................................................... 7-4
P-OLT performance and distance .................................................. 7-7
PON bandwidth ....................................................................... 7-7
P-OLT connection capacities ....................................................... 7-7
Video coupler connection capacity................................................ 7-7
GPON optical and RF line rates ....................................................... 7-8
P-OLT optical budgets .................................................................. 7-8
Video coupler optical budget ......................................................... 7-9
Environmental requirements .......................................................... 7-9
Power specifications.................................................................... 7-9
P-OLT input voltage.................................................................. 7-9
P-OLT power consumption ......................................................... 7-10

Contents
Detailed system description

8
Alarms and troubleshooting

8.1
8.2
DHCP and PPPoE relay agents

9.1
9.2
9.3
9.4
9.5
10.3
10.4
10.5
10.6
10.7
10.8
10-1
Overview ................................................................................ 10-2

Monitoring OLT and ONT optics ...................................................... 10-2
Optical power levels ................................................................ 10-2
Optics module status ............................................................... 10-2
Downstream threshold monitor ................................................... 10-2
Ping....................................................................................... 10-3
RMON Ethernet statistics.............................................................. 10-3
Statistics and performance monitoring ............................................. 10-3
VoIP call statistics................................................................... 10-3
TCA counters and alarms ............................................................. 10-3
TCA alarms ........................................................................... 10-4
TCA provisioning..................................................................... 10-4
DS1 and E1 loopbacks.................................................................. 10-4
Ethernet OAM ........................................................................... 10-5
Continuity check tests.............................................................. 10-7
Link trace tests ...................................................................... 10-8
Loopback tests....................................................................... 10-9
11 IP multicast and IGMP

11.1
11.2
11.3
9-1
Overview ................................................................................. 9-2

DHCP relay agent........................................................................ 9-2
DHCP Option 82....................................................................... 9-2
DHCP Option 60....................................................................... 9-3
DHCP relay configuration parameters ............................................... 9-3
DHCP relay agent configuration parameters ..................................... 9-3
Virtual router DHCP relay configuration parameters ........................... 9-4
PPPoE relay agent....................................................................... 9-4
PPPoE relay agent configuration parameters ....................................... 9-5
10 Fault isolation
10.1
10.2
8-1
Overview ................................................................................. 8-2

General ................................................................................ 8-2
Alarm storm prevention ............................................................ 8-2
Isolating faults indicated by alarms .................................................. 8-3
11-1
Overview ................................................................................ 11-2

IP multicast stream flow .............................................................. 11-2
IGMP infrastructure .................................................................... 11-3
IGMP signaling ....................................................................... 11-4
IGMP proxy ........................................................................... 11-5
IGMP snoop ........................................................................... 11-6
IGMP snoop versus IGMP proxy .................................................... 11-6

xxix
Contents
11.4
11.5
11.6
11.7
11.8
11.9
11.10
Join and leave messages .............................................................. 11-7

LT-to-ONT signaling mode enabled............................................... 11-7
LT-to-ONT signaling mode disabled (default)................................... 11-7
Processing limits .................................................................. 11-10
IGMP expedited leave ............................................................ 11-11
IGMP configuration requirements.................................................. 11-11
Subscriber and video management ................................................ 11-12
Terminology........................................................................ 11-12
Package ............................................................................. 11-13
Access control ..................................................................... 11-13
Access modes ...................................................................... 11-15
Control Data Records ............................................................. 11-15
Wholesale video through residential-bridging ................................ 11-16
IP multicast service networks ...................................................... 11-17
IP subscriber access network .................................................... 11-17
PPPoE subscriber access network............................................... 11-18
Dynamic and static multicast streams ............................................ 11-19
Dynamic multicast stream ....................................................... 11-19
Static multicast stream .......................................................... 11-19
P-OLT IP multicast features ........................................................ 11-20
ONT IP multicast features .......................................................... 11-20
12 Layer 2 forwarding
12.1
12.2
12.3
12.4
12.5
12.6
12.7
12.8
12.9
xxx
12-1
Overview ................................................................................ 12-2

Layer 2 forwarding rules .............................................................. 12-2
Classifying of interfaces............................................................ 12-2
Switching flood traffic.............................................................. 12-3
Learning MAC addresses............................................................ 12-3
Layer 2 forwarding modes ............................................................ 12-4
Residential bridge mode ........................................................... 12-4
Residential bridge with VLAN pass-through mode ............................. 12-6
Residential bridge with C-VLAN forwarding mode ............................. 12-6
VLAN cross-connect mode ......................................................... 12-7
VLAN translation and customer service flow.................................... 12-8
Residential bridge mode configuration requirements ............................ 12-8
Upstream frame forwarding ....................................................... 12-9
Downstream frame forwarding.................................................... 12-9
Configuration requirements ....................................................... 12-9
Residential bridge with VLAN pass-through mode configuration
requirements................................................................... 12-10
Residential bridge with C-VLAN forwarding mode configuration
requirements................................................................... 12-10
VLAN cross-connect mode configuration requirements ........................ 12-11
Configuration requirements ..................................................... 12-11
Forwarding ......................................................................... 12-11
Forwarding unicast traffic in the LT card ........................................ 12-12
Residential bridge mode upstream ............................................. 12-12
Residential bridge mode downstream ......................................... 12-12
Cross-connect unicast upstream traffic ....................................... 12-12
Cross-connect unicast downstream traffic .................................... 12-12
MAC filters ............................................................................ 12-13
Contents
12.10
12.11
Pause frames..........................................................................
Subscriber scalability ................................................................
Implementation considerations .................................................
Restrictions and limitations .....................................................
13 NT redundancy
13.1
13.2
13.3
13.4
13.5
13.6
15.4
15.5
14-1
Overview ................................................................................ 14-2

Functional description................................................................. 14-2
Proxy ARP process flow ............................................................... 14-2
ARP table persistence ................................................................. 14-3
Static ARP IP address .................................................................. 14-3
ARP snooping......................................................................... 14-4
15 QoS
15.1
15.2
15.3
13-1
Overview ................................................................................ 13-2

Single bridge port configuration ..................................................... 13-2
Multiple bridge port configuration .................................................. 13-3
Multiple upstream switches configuration ......................................... 13-3
Redundancy between NT and LT cards ............................................. 13-4
Dynamic data synchronization ....................................................... 13-4
14 Proxy ARP
14.1
14.2
14.3
14.4
14.5
12-13
12-13
12-13
12-16
15-1
Overview ................................................................................ 15-2
QoS infrastructure ..................................................................... 15-2
Traffic classification and marking elements ....................................... 15-4
CoS .................................................................................... 15-4
P-bit ................................................................................... 15-4
DSCP................................................................................... 15-5
DSCP to p-bit mapping ............................................................. 15-5
P-bit to CoS mapping ............................................................... 15-5
C-VLAN to S-VLAN p-bit translation .............................................. 15-6
UNI-side to network-side p-bit translation profile ............................. 15-6
QoS marker and session profiles .................................................. 15-7
Traffic policing elements ............................................................. 15-8
Traffic meter ........................................................................ 15-8
Ingress rate........................................................................... 15-8
Maximum burst size ................................................................. 15-8
Traffic flow .......................................................................... 15-8
Egress rate ........................................................................... 15-9
Congestion management elements .................................................. 15-9
Switch ................................................................................. 15-9
Ports................................................................................. 15-10
Scheduler and queues ............................................................ 15-10
P-bit to queue mapping .......................................................... 15-10
Traffic scheduler .................................................................. 15-11
Downstream rate limiting to ONT .............................................. 15-12
Priority queue profile............................................................. 15-16
T-CONTs and GEM ports .......................................................... 15-16

xxxi
Contents
15.6
15.7
15.8
15.9
15.10
Traffic shaping elements............................................................

PON bandwidth ....................................................................
Bandwidth profile .................................................................
Reserved bandwidth ..............................................................
Dynamic bandwidth allocation (DBA) ..........................................
QoS configuration ....................................................................
Downstream queuing and scheduling .............................................
From the network (EMAN) to the NT ...........................................
From the NT to the LT............................................................
From the LT across the GPON to the ONT .....................................
From the ONT to the subscriber ................................................
Upstream queuing and scheduling.................................................
From the ONT to the LT ..........................................................
From the LT to the NT............................................................
From the NT to the network (E-MAN) ..........................................
Recommended DSCP to p-bit mapping............................................
16 Statistics and performance monitoring

16.1
16.2
16.3
16.4
17.8
17.9
17.10
xxxii
16-1
Overview ................................................................................ 16-2

Statistics, counters, and performance monitoring................................ 16-2
15-min counters ..................................................................... 16-3
Rolling counters ..................................................................... 16-4
Status reports........................................................................ 16-5
P-OLT performance monitoring ...................................................... 16-5
RMON Ethernet statistics support for the P-OLT .................................. 16-5
17 Security
17.1
17.2
17.3
17.4
17.5
17.6
17.7
15-20
15-20
15-20
15-21
15-21
15-25
15-26
15-27
15-27
15-28
15-28
15-29
15-30
15-31
15-32
15-32
17-1
Overview ................................................................................ 17-2

Secured MAC learning ................................................................. 17-3
Access control lists..................................................................... 17-3
RADIUS proxy and server .............................................................. 17-4
SNMP encryption ....................................................................... 17-6
SSH ....................................................................................... 17-7
802.1x authentication ............................................................... 17-11
802.1x support assumptions ..................................................... 17-11
Authentication protocols......................................................... 17-12
Port-based authentication ....................................................... 17-12
User session disconnection by system.......................................... 17-13
Statistics and operational data ................................................. 17-13
Restart scenarios .................................................................. 17-13
Re-authentication ................................................................. 17-14
System log for security and NE actions ........................................... 17-15
Logged message or information types ......................................... 17-15
Message filtering .................................................................. 17-16
Syslog format ...................................................................... 17-16
Syslog file destinations ........................................................... 17-17
User account management ......................................................... 17-17
IPSec ................................................................................... 17-17
Sun Solaris and OLT interworking............................................... 17-19

Contents
17.11
Anti-spoofing mechanism ...........................................................

Gratuitous ARP discard ...........................................................
Source address anti-spoofing ....................................................
Per-service anti-spoofing ........................................................
18 VLANs
18.1
18.2
18.3
18.4
18.5
18.6
18.7
18.8
18.9
17-19
17-19
17-20
17-21
18-1
Overview ................................................................................ 18-2
General description.................................................................... 18-2
Definition ............................................................................. 18-3
Purpose ............................................................................... 18-3
VLAN types .............................................................................. 18-4
Residential bridge VLAN............................................................ 18-4
Cross-connect VLAN................................................................. 18-5
Flow mirroring VLAN ................................................................ 18-6
VLAN models ............................................................................ 18-8
VLAN per subscriber model ........................................................ 18-8
VLAN per service model ............................................................ 18-9
VLAN tagging.......................................................................... 18-12
VLAN tagging modes at the LT .................................................. 18-13
P-bit marking modes at the LT.................................................. 18-14
Downstream tagging modes at the ONT UNI .................................. 18-15
Upstream tagging modes at the ONT UNI...................................... 18-16
Compatible tagging modes....................................................... 18-20
Frame processing at the LT......................................................... 18-20
Downstream tagging at the LT .................................................. 18-20
Upstream tagging at the LT ..................................................... 18-22
Frame processing at the ONT ...................................................... 18-25
Downstream tagging at the ONT ................................................ 18-26
Upstream tagging at the ONT ................................................... 18-27
Network interface CAC bandwidth check ........................................ 18-35
CAC at NT port or LAG............................................................ 18-35
CAC for S-VLAN capacity ......................................................... 18-36
PON CAC at the LT ................................................................ 18-36
GPON and SHub VLAN bandwidth synchronization ........................... 18-37
VLAN bridging scalability............................................................ 18-37
Services descriptions
19 VoIP overview
19.1
19.2
19-1
Overview ................................................................................ 19-2

VoIP service operation modes ..................................................... 19-2
TISPAN support ...................................................................... 19-2
Common service operation mode features...................................... 19-3
Voice gateway mode................................................................... 19-4
GR-303/TR008 mode................................................................ 19-5
V5 mode .............................................................................. 19-5

xxxiii
Contents
19.3
19.4
19.5
19.6
19.7
19.8
H.248 softswitch mode ................................................................ 19-6

Softswitch call flow ................................................................. 19-7
SIP modes................................................................................ 19-8
SIP service features ................................................................. 19-8
SIP call flow ........................................................................ 19-10
VoIP service configuration .......................................................... 19-12
Process for country-specific POTS configuration files ....................... 19-13
XML files for package C ONTs ................................................... 19-13
Service and protocol configuration............................................. 19-13
Configuration profile ............................................................. 19-15
iConfig .............................................................................. 19-16
SIP-specific provisioning parameters........................................... 19-16
Security ................................................................................ 19-38
DHCP Option 90.................................................................... 19-38
HTTP digest ........................................................................ 19-38
VoIP call statistics.................................................................... 19-39
Statistics collection ............................................................... 19-39
RTCP failure alarm ................................................................ 19-40
XML file configuration data for package C ONTs ................................ 19-40
20 HSI service
20.1
20.2
20.3
20.4
20.5
20-1
Overview ................................................................................ 20-2

Network example ...................................................................... 20-2
Downstream flow across the 7342 ISAM FTTU access network ............... 20-2
Upstream flow across the 7342 ISAM FTTU access network .................. 20-3
HSI service configuration elements ................................................. 20-3
HSI elements ......................................................................... 20-4
Relationship among the HSI elements ........................................... 20-5
QoS characteristics .................................................................... 20-6
Data traffic........................................................................... 20-7
P-bit ................................................................................... 20-7
Traffic queuing and scheduling ................................................... 20-7
Tagging ............................................................................... 20-9
HSI service configuration example .................................................. 20-9
21 RF video services
21.1
21.2
21-1
Overview ................................................................................ 21-2

Breakdown of the RF 1550 nm and 1490 nm overlay .......................... 21-2
Network example ...................................................................... 21-3
22 Triple play service delivery architecture in access

network
22.1
22.2
xxxiv
22-1
Triple play services .................................................................... 22-2

TPSDA .................................................................................... 22-2
IP/MPLS network .................................................................... 22-3
IP edge aggregation and routing component.................................... 22-4
7342 ISAM FTTU access network .................................................. 22-6

Contents
22.3
22.4
22.5
7342 ISAM FTTU service delivery across the TPSDA............................... 22-9

Downstream .......................................................................... 22-9
Upstream ........................................................................... 22-10
Configuring the 7342 ISAM FTTU for triple play ................................. 22-10
Configure the equipment ........................................................ 22-11
Configure QoS...................................................................... 22-11
Configure VLANs ................................................................... 22-16
Configure VLAN for DHCP relay ................................................. 22-17
Configure IGMP and multicast................................................... 22-19
Configure services................................................................. 22-20
Triple play configuration example ................................................ 22-22
Configuration exclusions ......................................................... 22-22
Configuration details ............................................................. 22-23
Configuring the equipment ...................................................... 22-30
Configuring QoS profiles for ONT UNI port and HSI service................. 22-31
Configuring VLANs................................................................. 22-32
Configuring the subscriber VLAN for DHCP relay. ............................ 22-33
Configuring IGMP and multicast system ....................................... 22-34
Configuring services .............................................................. 22-35
Verifying the configuration data................................................ 22-36
23 CES DS1 and E1 interfaces

23.1
23.2
23.3
23.4
23.5
23.6
23.7
Overview ................................................................................ 23-2

Network example ...................................................................... 23-2
Service options ...................................................................... 23-3
Structured and unstructured DS1 and E1 services handling for CES............ 23-4
Structured DS1/E1 .................................................................. 23-5
Unstructured DS1/E1 ............................................................... 23-5
Payload size .......................................................................... 23-6
Jitter buffering, congestion handling, and alarms................................ 23-6
CES clocking and synchronization ................................................... 23-7
Configuring DS1 and E1 port parameters ........................................... 23-8
Structured and unstructured framing mode .................................... 23-8
Framing type ......................................................................... 23-8
Line encoding ........................................................................ 23-9
Line length and line impedance .................................................. 23-9
Configuring CES PW services ....................................................... 23-10
24 Support for the micro span CES

24.1
24.2
24-1
Overview ................................................................................ 24-2

Network example ...................................................................... 24-2
High-level workflow ................................................................ 24-4
25 Ethernet services for business and residential

applications
25.1
25.2
23-1
25-1
Overview ................................................................................ 25-2

Metro Ethernet services infrastructure ............................................. 25-4

xxxv
Contents
25.3
25.4
25.5
Ethernet virtual connection .......................................................... 25-6

EVC types ............................................................................. 25-6
Implementation of EVC on the 7342 ISAM FTTU ................................ 25-8
Configuration elements ............................................................ 25-9
EVC models............................................................................ 25-11
Internal EVC models .............................................................. 25-12
External EVC models.............................................................. 25-16
Constraints ............................................................................ 25-17
System constraints ................................................................ 25-17
Hardware constraints ............................................................. 25-17
Configuration constraints ........................................................ 25-19
Unit data sheets

26 Index of unit data sheets
26.1
26.2
26.3
Overview ................................................................................ 26-2

Unit data sheet overview ............................................................. 26-2
Index list of unit data sheets for 7342 ISAM FTTU ................................ 26-2
27 AACU-C unit data sheet

27.1
27.2
27.3
27.4
27.5
27.6
27.7
xxxvi
27-1
Identification ........................................................................... 27-2

Features and application notes ...................................................... 27-2
Alarm control function ................................................................ 27-4
CO alarm system .................................................................... 27-4
Telemetry alarm system ........................................................... 27-5
Rack-level alarms ................................................................... 27-5
Alarm LEDs .............................................................................. 27-5
Interfaces and connections ........................................................... 27-6
Interface to the TRU................................................................ 27-6
Interface for alarm input/output ................................................. 27-6
Interface for AACU OAM............................................................ 27-6
Interface for Ethernet OS port .................................................... 27-7
Interface to the NT cards .......................................................... 27-7
Physical description.................................................................... 27-8
28 AFAN-H unit data sheet

28.1
28.2
28.3
28.4
28.5
28.6
28.7
28.8
28.9
26-1
28-1
Identification ........................................................................... 28-2

Front panel.............................................................................. 28-3
Back panel............................................................................... 28-3
Fan and cable assembly ............................................................... 28-4
Filter assembly ......................................................................... 28-4
Electrical specifications............................................................... 28-4
Contents
29 AFAN-S unit data sheet

29.1
29.2
29.3
29.4
29.5
29.6
29.7
Identification ........................................................................... 29-2

Front panel.............................................................................. 29-3
Filter assembly ......................................................................... 29-3
Electrical specifications............................................................... 29-3
30 ALTS-N unit data sheet

30.1
30.2
30.3
30.4
30.5
30.6
30.7
30.8
31.5
31.6
31-1
Identification ........................................................................... 31-2

Front panel.............................................................................. 31-3
Indicator LEDs and test button.................................................... 31-3
Circuit breakers ..................................................................... 31-4
Earth bonding point................................................................. 31-4
PBA-ATRU-G board ..................................................................... 31-4
32 ATRU-N unit data sheet

32.1
32.2
32.3
32.4
30-1
Identification ........................................................................... 30-2

Backplane connectors and cables ................................................... 30-4
Physical location identification ...................................................... 30-6
Power distribution ..................................................................... 30-6
Thermal limitation ..................................................................... 30-7
Front cover ........................................................................... 30-8
Rear cover............................................................................ 30-8
Fiber management kit .............................................................. 30-8
Specifications ........................................................................ 30-8
31 ATRU-M unit data sheet

31.1
31.2
31.3
31.4
29-1
32-1
Identification ........................................................................... 32-2

Front panel........................................................................... 32-5
Power input terminal blocks ...................................................... 32-7
PBA-ATRU-G board ................................................................ 32-10
CO interface connector .......................................................... 32-11
ACU/FAN alarm interface connectors.......................................... 32-13
Jumpers............................................................................. 32-16
Dimensions ......................................................................... 32-17
Safety requirements .............................................................. 32-17
Specifications ...................................................................... 32-18

xxxvii
Contents
33 ATRU-U and GTRU-B unit data sheet

33.1
33.2
33.3
33.4
33.5
33.6
Identification ........................................................................... 33-2

Front panel.............................................................................. 33-3
Indicator LEDs and test button.................................................... 33-3
Circuit breakers ..................................................................... 33-4
Earth bonding point................................................................. 33-4
PBA-ATRU-G board ..................................................................... 33-4
34 BITS-B unit data sheet

34.1
34.2
34.3
34.4
xxxviii
37-1
Identification ........................................................................... 37-2

Network interface modules........................................................... 37-7
Interfaces and connectors ............................................................ 37-7
Status LEDs .............................................................................. 37-7
Power .................................................................................... 37-9
Physical description.................................................................. 37-10
38 EXNT-A and pluggable optical modules unit data sheet

38.1
38.2
38.3
38.4
38.5
38.6
36-1
Identification ........................................................................... 36-2

37 EHNT and pluggable optical modules unit data sheet

37.1
37.2
37.3
37.4
37.5
37.6
37.7
37.8
35-1
Identification ........................................................................... 35-2

36 Blank NT filler plate unit data sheet

36.1
36.2
36.3
36.4
34-1
Identification ........................................................................... 34-2

Location ................................................................................. 34-3
35 Blank LT filler plate unit data sheet

35.1
35.2
35.3
35.4
33-1
38-1
Identification ........................................................................... 38-2

Status LEDs .............................................................................. 38-6

Contents
38.7
38.8
Power .................................................................................... 38-7

39 FILT-A and FILT-B unit data sheet

39.1
39.2
39.3
39.4
Identification ........................................................................... 39-2

Shelf power distribution ........................................................... 39-3
Power and grounding signals ...................................................... 39-3
40 GLT2 unit data sheet

40.1
40.2
40.3
40.4
40.5
40.6
40.7
40.8
42-1
Identification ........................................................................... 42-2

Optical budgets......................................................................... 42-3
Status LEDs .............................................................................. 42-4
Power .................................................................................... 42-5
43 NT card unit data sheet

43.1
43.2
43.3
41-1
Identification ........................................................................... 41-2

Optical budgets......................................................................... 41-3
Status LEDs .............................................................................. 41-3
Power .................................................................................... 41-5
42 LT card unit data sheet

42.1
42.2
42.3
42.4
42.5
42.6
42.7
42.8
40-1
Identification ........................................................................... 40-2

Optical budgets......................................................................... 40-4
Status LEDs .............................................................................. 40-4
Power .................................................................................... 40-7

41.1
41.2
41.3
41.4
41.5
41.6
41.7
41.8
39-1
43-1
Identification ........................................................................... 43-2


xxxix
Contents
43.4
43.5
43.6
43.7
43.8

Optical module power and modulation frequencies ........................... 43-3
Optical budgets...................................................................... 43-4
Status LEDs ............................................................................ 43-10
Power .................................................................................. 43-10
44 OLT rack unit data sheet

44.1
44.2
44.3
44.4
Identification ........................................................................... 44-2

45 OLTS-M unit data sheet

45.1
45.2
45.3
45.4
45.5
45.6
45.7
45.8
47.4
xl
47-1
Identification ........................................................................... 47-2

Tyco ................................................................................... 47-2
LGX .................................................................................... 47-5
48 Tyco video coupler subrack unit data sheet

48.1
48.2
48.3
46-1
Identification ........................................................................... 46-2

47 Racks for video coupler unit data sheet

47.1
47.2
47.3
45-1
Identification ........................................................................... 45-2

Backplane connectors and cables ................................................... 45-5
Physical location identification ...................................................... 45-6
Power distribution ..................................................................... 45-6
Thermal limitation ..................................................................... 45-7
P-OLT thermal defense for individual card protection ........................ 45-8
P-OLT thermal defense in FGU 4.6 and later systems ....................... 45-10
Front cover ......................................................................... 45-12
Fiber management shelf ......................................................... 45-12
Specifications ...................................................................... 45-12
46 SANC-D unit data sheet

46.1
46.2
46.3
46.4
44-1
48-1
Identification ........................................................................... 48-2

Contents
49 Tyco VCS8-A unit data sheet

49.1
49.2
49.3
49.4
49.5
49.6
Identification ........................................................................... 49-2

Optical safety........................................................................... 49-3
Environment requirements ........................................................... 49-3
Connections ............................................................................. 49-4
50 Tyco VCW4-A unit data sheet

50.1
50.2
50.3
50.4
50.5
50.6
51-1
Identification ........................................................................... 51-2

Alarms.................................................................................... 51-3
Connections ............................................................................. 51-3
52 LGX VCW2 unit data sheet

52.1
52.2
52.3
52.4
52.5
52.6
52.7
52.8
50-1
Identification ........................................................................... 50-2

Optical safety........................................................................... 50-3
Connections ............................................................................. 50-3
51 VCSL-A LGX unit data sheet

51.1
51.2
51.3
51.4
51.5
51.6
49-1
52-1
Identification ........................................................................... 52-2

Optical budget.......................................................................... 52-3
Optical safety........................................................................... 52-4
Connections ............................................................................. 52-5
Glossary
Index

xli
Contents
List of figures
Figure 1 ESD warning label .......................................................................... ix
Figure 2 Hazardous voltage warning label ........................................................ ix
Figure 3 Laser product label ........................................................................ ix
Figure 4 Laser classification label ................................................................... x
Figure 5 Laser warning labels ....................................................................... xi
Figure 6 Supply wire protective earth terminal .................................................. xi
Figure 7 Earth terminal .............................................................................. xi
Figure 8 Label for earth bonding point .......................................................... xvii
Figure 1 Products below MCV value label ........................................................ xx
Figure 2 Products above MCV value label ........................................................xxi
Figure 3 Recycling/take back/disposal of product symbol .................................. xxiii
Figure 1-1 7342 ISAM FTTU GPON network topology .......................................... 1-3
Figure 4-1 P-OLT functional blocks with an EHNT ............................................. 4-3
Figure 4-2 P-OLT functional blocks with an EXNT.............................................. 4-3
Figure 5-1 Rack mounted ATRU-M and P-OLT (ALTS-N) with cover attached.............. 5-3
Figure 5-2 Rack mounted ATRU-U and P-OLT (OLTS-M) ....................................... 5-4
Figure 5-3 OLT shelf with cards, fan tray, and fiber routing tray installed................ 5-5
Figure 5-4 OLTS-M shelf with cards installed ................................................... 5-6
Figure 5-5 Tyco video coupler fiber rack ....................................................... 5-11
Figure 6-1 AACU-C craft and Ethernet connections............................................ 6-2
Figure 6-2 ALTS-N backplane craft and Ethernet connections ............................... 6-3
Figure 6-3 OLTS-M backplane craft and Ethernet connections............................... 6-4
Figure 8-1 Alarm storm prevention............................................................... 8-3
Figure 10-1 Remote loopback .................................................................... 10-5
Figure 10-2 Ethernet OAM components ......................................................... 10-6
Figure 10-3 Continuity check process for the NE.............................................. 10-7
Figure 10-4 CC messages on ONTs ............................................................... 10-8
Figure 10-5 Link trace test sequence ........................................................... 10-9
Figure 10-6 Loopback test sequence .......................................................... 10-10
Figure 11-1 IGMP infrastructure ................................................................. 11-3
Figure 11-2 IGMP snoop versus IGMP proxy .................................................... 11-6
Figure 11-3 Processing of IGMP messages at the ONT ........................................ 11-8
Figure 11-4 Processing of join messages at the LT card ..................................... 11-9
Figure 11-5 Multicast source, multicast stream, and channel ............................ 11-13
Figure 11-6 Package example with sample subscribers .................................... 11-13
Figure 11-7 Steps for creating multicast packages and providing access to
subscribers ..................................................................... 11-14
Figure 11-8 IP subscriber access network architecture and signaling flow ............. 11-17
Figure 11-9 PPPoE subscriber access network architecture and signaling flow ........ 11-18
Figure 12-1 Subscriber scaling using T-CONT per Service with GEM port per
subscriber ...................................................................... 12-15
Figure 13-1 Single bridge port network topology ............................................. 13-2
Figure 13-2 Multiple bridge port network topology........................................... 13-3
Figure 13-3 Multiple upstream switches ........................................................ 13-4
Figure 15-1 QoS infrastructure ................................................................... 15-3
Figure 15-2 C-VLAN to S-VLAN p-bit translation at the LT................................... 15-6
Figure 15-3 One-to-one p-bit translation, single-tagged frames ........................... 15-7
Figure 15-4 Many-to-one p-bit translation, single-tagged frames .......................... 15-7
Figure 15-5 Downstream rate limiting ........................................................ 15-13
xlii

Contents
Figure 15-6 Per-ONT downstream rate limiting ............................................. 15-14

Figure 15-7 Per-service downstream rate limiting .......................................... 15-15
Figure 15-8 T-CONT per service model ....................................................... 15-18
Figure 15-9 T-CONTs and GEM ports .......................................................... 15-19
Figure 15-10 T-CONT per subscriber/per service model ................................... 15-19
Figure 15-11 Downstream queuing from EMAN to subscriber ............................. 15-27
Figure 15-12 Downstream queuing and scheduling at the ONT ........................... 15-29
Figure 15-13 Upstream queuing from subscriber to EMAN ................................. 15-30
Figure 15-14 Upstream scheduling at the ONT .............................................. 15-31
Figure 17-1 7342 ISAM FTTU and network security features ................................ 17-2
Figure 17-2 RADIUS on the NT and SHub........................................................ 17-5
Figure 17-3 RADIUS operator authentication .................................................. 17-6
Figure 17-4 SSHv2 security........................................................................ 17-8
Figure 17-5 Syslog system....................................................................... 17-15
Figure 17-6 IPSec internal protocol suite..................................................... 17-18
Figure 17-7 ONT packet authorization ........................................................ 17-20
Figure 18-1 Example of VLAN .................................................................... 18-3
Figure 18-2 Residential bridge VLAN model.................................................... 18-5
Figure 18-3 C-VLAN cross-connection model................................................... 18-6
Figure 18-4 Network topology of the VLAN per subscriber model for two
subscribers ....................................................................... 18-8
Figure 18-5 VLAN per business ONT subscriber connection.................................. 18-9
Figure 18-6 VLAN per service model .......................................................... 18-10
Figure 18-7 VLAN per service model with shared S-VLAN for VoIP ....................... 18-11
Figure 18-8 VLAN per service model for the business ONT ................................ 18-11
Figure 18-9 Tagging of an Ethernet frame ................................................... 18-12
Figure 18-10 Cross-connect VLAN in stacked VLAN mode.................................. 18-14
Figure 18-11 VLAN translation mode example............................................... 18-17
Figure 18-12 EtherType classification mode ................................................. 18-19
Figure 18-13 Translation algorithm in VLAN translation mode............................ 18-29
Figure 18-14 Tagging of upstream traffic in VLAN translation mode with
EtherType classification...................................................... 18-31
Figure 18-15 CAC bandwidth check ........................................................... 18-35
Figure 19-1 Voice gateway network topology ................................................. 19-4
Figure 19-2 Softswitch network topology ...................................................... 19-7
Figure 19-3 Call flow of a SIP call originating from the ONT .............................. 19-11
Figure 19-4 Call flow of a SIP call terminated at the ONT................................. 19-12
Figure 20-1 Delivery of data services across the TPSDA ..................................... 20-2
Figure 20-2 HSI service configuration elements in a networking topology................ 20-4
Figure 20-3 Relationships among HSI elements................................................ 20-5
Figure 20-4 Upstream traffic queuing for single priority queue profile ................... 20-8
Figure 20-5 Upstream traffic queuing with two priority queue profiles................... 20-8
Figure 21-1 1550 nm and 1490 nm RF overlay on the 7342 ISAM FTTU .................... 21-3
Figure 21-2 RF video service in 7342 ISAM FTTU .............................................. 21-4
Figure 22-1 Triple play services.................................................................. 22-2
Figure 22-2 7342 ISAM FTTU TPSDA ............................................................. 22-3
Figure 22-3 Architectural elements of a router ............................................... 22-3
Figure 22-4 IP/MPLS network..................................................................... 22-5
Figure 22-5 7342 ISAM FTTU access network .................................................. 22-7
Figure 22-6 7342 ISAM FTTU access network within TPSDA ................................. 22-9
Figure 22-7 Triple play workflow .............................................................. 22-11
Figure 22-8 Assignment of profiles to network elements .................................. 22-12
xliii
Contents
Figure 22-9 BSR-to-BSA downstream QoS configuration.................................... 22-14

Figure 22-10 BSA-to-BSR upstream QoS configuration...................................... 22-15
Figure 22-11 Downstream traffic for VLAN 10 ............................................... 22-17
Figure 22-12 IP address assignment with DHCP ............................................. 22-18
Figure 22-13 Implementation of IGMP across the TPSDA................................... 22-19
Figure 22-14 Triple play provisioning example .............................................. 22-22
Figure 22-15 Provisioning details .............................................................. 22-23
Figure 23-1 CES DS1 or E1 traffic between the ONT and PSTN over the GPON via
the P-OLT......................................................................... 23-3
Figure 23-2 Structured TDM frames encapsulated into CES MEF-8 packets ............... 23-5
Figure 23-3 Unstructured TDM traffic encapsulated into CES MEF-8 packets............. 23-6
Figure 24-1 Network example of micro span collocated with 7342 ISAM FTTU........... 24-3
Figure 24-2 CES VLAN example using micro span, 7342 ISAM FTTU, and ONTs ........... 24-4
Figure 25-1 Metro Ethernet services model .................................................... 25-4
Figure 25-2 Example of MEN...................................................................... 25-5
Figure 25-3 Point-to-point EVC .................................................................. 25-7
Figure 25-4 Multipoint-to-multipoint EVC ...................................................... 25-7
Figure 25-5 Rooted-multipoint EVC ............................................................. 25-8
Figure 25-6 Ethernet service element relationships .......................................... 25-9
Figure 25-7 EVC and Ethernet services configuration ...................................... 25-10
Figure 25-8 Internal EVC with bundling and single CoS .................................... 25-13
Figure 25-9 Internal EVC with all-to-one bundling and single CoS ....................... 25-14
Figure 27-1 AACU front and side views ......................................................... 27-4
Figure 28-1 Front, top, and side views of the AFAN-H fan unit............................. 28-3
Figure 28-2 AFAN-H front panel.................................................................. 28-3
Figure 28-3 AFAN-H back panel .................................................................. 28-3
Figure 28-4 Fan and cable assembly ............................................................ 28-4
Figure 29-1 Front view of the AFAN-S fan unit ................................................ 29-3
Figure 30-1 ALTS-N shelf with P-OLT cards and components ............................... 30-3
Figure 30-2 ALTS-N backplane ................................................................... 30-5
Figure 30-3 ALTS-N shelf .......................................................................... 30-8
Figure 31-1 ATRU-M AA variant front panel .................................................... 31-3
Figure 31-2 PBA-ATRU-G connector and jumper locations .................................. 31-5
Figure 32-1 Diagram of ATRU-N for fixed shelf powering (up to two ALTS-N
shelves) ........................................................................... 32-4
Figure 32-2 Parts of the ATRU-N................................................................. 32-5
Figure 32-3 ATRU-N front panel ................................................................. 32-5
Figure 32-4 ATRU-N front panel LEDs ........................................................... 32-6
Figure 32-5 Power-input terminal blocks (two fabrication variants)....................... 32-7
Figure 32-6 Power connection of P-OLT rack to PDF ......................................... 32-9
Figure 32-7 Layout of the ATRU-G board (jumpers factory set) .......................... 32-11
Figure 32-8 D-SUB 37-pin connector .......................................................... 32-12
Figure 32-9 D-SUB 50-pin connector .......................................................... 32-14
Figure 33-1 ATRU-U front panel ................................................................. 33-3
Figure 33-2 GTRU-B front panel ................................................................. 33-3
Figure 33-3 PBA-ATRU-G connector and jumper locations .................................. 33-5
Figure 34-1 BITS-B card ........................................................................... 34-2
Figure 37-1 Front view of EHNT-A ............................................................... 37-8
Figure 37-2 Front view of EHNT-B ............................................................... 37-8
Figure 38-1 Front view of EXNT-A ............................................................... 38-6
Figure 39-1 FILT-A on the ALTS-N backplane .................................................. 39-3
Figure 39-2 Caution label on the shelf backplane ............................................ 39-4
xliv

Contents
Figure 40-1
Figure 40-2
Figure 41-1
Figure 41-2
Figure 43-1
Figure 43-2
Figure 45-1
Figure 45-2
Figure 47-1
Figure 47-2
Figure 48-1
Figure 48-2
Figure 49-1
Figure 50-1
Figure 51-1
Figure 52-1
Figure 52-2
Front view of the GLT2-A card .................................................... 40-5

Side view of the GLT2-A card...................................................... 40-6
Front view of the GLT4 card ....................................................... 41-4
Side view of the GLT4 card ........................................................ 41-5
Optical and electrical SFP module components ................................ 43-3
Electrical SFP in an NT card ....................................................... 43-3
OLTS-M shelf with P-OLT cards and 19in. mounting ears...................... 45-4
OLTS-M backplane ................................................................... 45-5
Video coupler fiber rack............................................................ 47-4
Rack for video coupler and recommended layout .............................. 47-6
Video coupler subrack, front view ................................................ 48-2
Open VCS with 5 trays .............................................................. 48-3
VCS8 tray ............................................................................. 49-4
VCW4 tray and connectors ......................................................... 50-4
VCSL-A shelf .......................................................................... 51-3
VCW2-C................................................................................ 52-3
VCW2-C input and output connectors ............................................ 52-5
List of tables
Table 2-1 Features for FGU 04.06.08 ............................................................. 2-2
Table 2-4 Features for FGU 04.06.00 and 04.06.01 ............................................ 2-4
Table 2-8 Features for FGU 04.04.10 and 04.04.10a ........................................... 2-9
Table 2-9 Features for FGU 04.04.00 and 04.04.01 ............................................ 2-9
Table 2-10 Features for FGU 4.3.5 ............................................................... 2-11
Table 2-11 Features for FGU 4.3 ................................................................. 2-11
Table 3-1 Application notes for FGU 04.04.xx................................................... 3-2
Table 3-2 Application notes for FGU 4.3.5....................................................... 3-3
Table 3-3 Application notes for FGU 4.3.0....................................................... 3-3
Table 3-4 Application notes for FGU 4.2 ......................................................... 3-4
Table 5-1 Optical modules ......................................................................... 5-8
Table 7-1 P-OLT components ...................................................................... 7-2
Table 7-2 Installable and field-replaceable cards .............................................. 7-3
Table 7-3 P-OLT unit weight specifications...................................................... 7-3
Table 7-4 Video coupler equipment .............................................................. 7-4
Table 7-5 Service and system capacity ........................................................... 7-4
Table 7-6 P-OLT optical budgets .................................................................. 7-8
Table 7-7 P-OLT environmental requirements .................................................. 7-9
Table 7-8 Video coupler environmental requirements ......................................... 7-9
Table 7-9 P-OLT input voltage .................................................................... 7-10
Table 7-10 P-OLT power consumption ........................................................... 7-10
xlv
Contents
Table 9-1 DHCP relay agent parameters ......................................................... 9-3

Table 9-2 Vendor-specific tag...................................................................... 9-5
Table 10-1 Ethernet OAM components .......................................................... 10-6
Table 10-2 Ethernet OAM supported tools ...................................................... 10-7
Table 11-1 IGMP message types .................................................................. 11-4
Table 11-2 Processing limits .................................................................... 11-10
Table 11-3 Multicast data configuration requirements ..................................... 11-11
Table 11-4 Wholesale video through residential-bridging .................................. 11-16
Table 11-5 P-OLT IP multicast features ....................................................... 11-20
Table 11-6 ONT IP multicast features ......................................................... 11-21
Table 12-1 Unicast frame forwarding rules ..................................................... 12-2
Table 12-2 Rules for learning MAC addresses................................................... 12-3
Table 12-3 Upstream layer 2 in residential bridge with C-VLAN forwarding mode ....... 12-7
Table 12-4 Residential bridge LT card configuration parameters ........................... 12-9
Table 12-5 Residential bridge system configuration parameters.......................... 12-10
Table 12-6 Cross-connect configuration parameters ........................................ 12-11
Table 12-7 Upstream layer 2 forwarding in residential bridge mode ..................... 12-12
Table 12-8 Subscriber scaling based on T-CONT and GEM usage .......................... 12-15
Table 15-1 QoS infrastructure elements ........................................................ 15-3
Table 15-2 Scheduling of queues at the NT by weighting factor .......................... 15-11
Table 15-3 Scheduling of queues at the LT by weighting factor .......................... 15-12
Table 15-4 Default traffic scheduler at the LT............................................... 15-12
Table 15-5 Upstream scheduling of queues at the ONT by weighting factor ............ 15-16
Table 15-6 T-CONT models ...................................................................... 15-16
Table 15-7 MinBW for Delay Tolerance ........................................................ 15-22
Table 15-8 Bandwidth types..................................................................... 15-22
Table 15-9 Allocation of bandwidth by T-CONT type ....................................... 15-23
Table 15-10 T-CONT prioritization ............................................................. 15-24
Table 15-11 QoS elements by configuration task ............................................ 15-25
Table 15-12 VLAN configurations ............................................................... 15-26
Table 15-13 Forwarding classes................................................................. 15-32
Table 15-14 Recommended CoS mapping ..................................................... 15-33
Table 16-1 15-min counters ....................................................................... 16-3
Table 16-2 Rolling counters ....................................................................... 16-4
Table 16-3 RMON Ethernet statistics and definitions.......................................... 16-6
Table 17-1 SSH and SNMPv3 security combinations............................................ 17-9
Table 17-2 Lockout times for failed login attempts ......................................... 17-10
Table 17-3 IPSec protocol suite................................................................. 17-17
Table 17-4 Anti-spoofing control types and traffic exemptions ........................... 17-21
Table 18-1 Tagging options for upstream and downstream VLAN traffic .................. 18-2
Table 18-2 Tagging specifications for mirror packets ......................................... 18-7
Table 18-3 Features of flow mirroring VLANs .................................................. 18-7
Table 18-4 P-bit marking mode ................................................................. 18-14
Table 18-5 Compatible configurations for p-bit marking mode ........................... 18-15
Table 18-6 VLAN translation configuration example ........................................ 18-17
Table 18-7 VLAN translation and EtherType classification for upstream
forwarding...................................................................... 18-18
Table 18-8 VLAN translation and EtherType classification for downstream
forwarding...................................................................... 18-18
Table 18-9 Downstream tagging at the LT .................................................... 18-20
Table 18-10 Downstream tagging at the LT in stacked VLAN mode....................... 18-21
Table 18-11 Downstream tagging at the LT in unstacked VLAN mode.................... 18-22
xlvi

Contents
Table 18-12 Downstream tagging at the LT in VLAN pass-through mode ................ 18-22
Table 18-13 Upstream tagging at the LT ...................................................... 18-23
Table 18-14 Upstream tagging at the LT in stacked VLAN mode .......................... 18-24
Table 18-15 Upstream tagging at the LT in unstacked VLAN mode ....................... 18-24
Table 18-16 Upstream tagging at the LT in VLAN pass-through mode .................... 18-25
Table 18-17 Downstream tagging at the ONT ................................................ 18-26
Table 18-18 P-bit marking rules for untagged frames....................................... 18-27
Table 18-19 Upstream tagging at the ONT in the untrusted mode........................ 18-28
Table 18-20 Upstream tagging at the ONT in the VLAN pass-through mode............. 18-28
Table 18-21 Upstream tagging at the ONT in VLAN translation mode .................... 18-30
Table 18-22 Upstream tagging at the ONT in VLAN translation mode with
EtherType classification...................................................... 18-32
Table 18-23 Upstream tagging at the ONT in EtherType classification mode ........... 18-32
Table 18-24 Upstream tagging at the ONT in flexible mode ............................... 18-34
Table 18-25 VLAN bridging scalability ......................................................... 18-37
Table 19-1 Common features of VoIP service operation modes ............................. 19-3
Table 19-2 SIP service features ................................................................... 19-8
Table 19-3 ETSI call feature configuration.................................................... 19-10
Table 19-4 Sources of SIP configuration data................................................. 19-12
Table 19-5 Voice gateway mode considerations ............................................. 19-14
Table 19-6 DHCP options and VoIP modes .................................................... 19-14
Table 19-7 SIP-specific provisioning parameters............................................. 19-16
Table 19-8 ONT digit map elements, symbols, and modifiers ............................. 19-35
Table 19-9 Collected VoIP call statistics ...................................................... 19-39
Table 19-10 XML file configuration data for package C ONTs.............................. 19-41
Table 20-1 HSI service configuration elements ................................................ 20-4
Table 20-2 Relationships among HSI elements ................................................. 20-6
Table 20-3 Tagging modes ......................................................................... 20-9
Table 21-1 RF and MoCA channel breakdown................................................... 21-3
Table 22-1 IP edge aggregation and routing architectural elements ....................... 22-5
Table 22-2 7342 ISAM FTTU access network architectural elements ....................... 22-8
Table 22-3 QoS profiles and their network elements ....................................... 22-13
Table 22-4 Configuration requirements by service .......................................... 22-21
Table 22-5 Pre-service configuration requirements for HSI service....................... 22-21
Table 22-6 Pre-service configuration requirements for a VoIP service ................... 22-21
Table 22-7 Configuration details ............................................................... 22-23
Table 22-8 QoS profiles .......................................................................... 22-31
Table 23-1 Voice, data, and video service options ............................................ 23-3
Table 23-2 Business ONT features ................................................................ 23-4
Table 23-3 DS1 and E1 framing ................................................................... 23-8
Table 23-4 DS1 and E1 line encoding ............................................................ 23-9
Table 23-5 Line lengths supported for DS1 and DSX-1 ...................................... 23-10
Table 23-6 CES PW parameters ................................................................. 23-10
Table 25-1 Functionality supported by Ethernet services .................................... 25-2
Table 25-2 EVC and Ethernet service configuration elements ............................. 25-11
Table 25-3 Configuration for internal EVCs with bundling and single CoS ............... 25-13
Table 25-4 Configuration for internal EVCs with bundling and multiple CoSs ........... 25-14
Table 25-5 Configuration for internal EVCs with all-to-one bundling and single
CoS............................................................................... 25-15
Table 25-6 Configuration for internal EVCs with all-to-one bundling and multiple
CoSs ............................................................................. 25-15
Table 25-7 Configuration for external EVCs with one T-CONT per EVC .................. 25-16
xlvii
Contents
Table 25-8 Configuration for external EVCs with one T-CONT per COS .................. 25-17
Table 25-9 Maximum number of portals per GLT card and system ....................... 25-18
Table 25-10 Ethernet services support for ONT types....................................... 25-18
Table 25-11 EVC configuration constraints ................................................... 25-19
Table 26-1 Overview of unit data sheets for the 7342 ISAM FTTU .......................... 26-2
Table 26-2 Alphabetical list of unit data sheets by description ............................. 26-3
Table 27-1 Identification of ACCU-C ............................................................. 27-2
Table 27-2 Alarm LEDs ............................................................................. 27-6
Table 27-3 DB-9 connector pin assignment ..................................................... 27-7
Table 27-4 NT interface ........................................................................... 27-7
Table 27-5 AACU physical specifications ........................................................ 27-8
Table 28-1 Identification of AFAN-H ............................................................. 28-2
Table 28-2 AFAN-H physical specifications ..................................................... 28-5
Table 29-1 Identification of AFAN-S.............................................................. 29-2
Table 29-2 Status LED indications ................................................................ 29-3
Table 29-3 AFAN-S physical specifications ...................................................... 29-4
Table 30-1 Identification of ALTS-N.............................................................. 30-2
Table 30-2 Backplane connectors and related cables ......................................... 30-5
Table 30-3 Power and grounding signals ........................................................ 30-7
Table 30-4 Physical specifications of the ALTS-N .............................................. 30-9
Table 31-1 Identification of ATRU-M............................................................. 31-2
Table 31-2 Front panel LED indicators........................................................... 31-3
Table 31-3 CO connector pin layout ............................................................. 31-5
Table 31-4 ATRU-M physical specifications ..................................................... 31-6
Table 32-1 Identification of ATRU-N ............................................................. 32-2
Table 32-2 Front panel LEDs ...................................................................... 32-6
Table 32-3 Power input connection and grounding provisions ............................... 32-8
Table 32-4 PDF circuit breaker rating and power cable sections.......................... 32-10
Table 32-5 Pin layout of CO interface connector ............................................ 32-12
Table 32-6 Pin layout of ACU/FAN alarm connectors ....................................... 32-14
Table 32-7 Factory jumper settings............................................................ 32-16
Table 32-8 Application-dependent jumper setting .......................................... 32-16
Table 32-9 ATRU-N dimensions ................................................................. 32-17
Table 32-10 Physical specifications of the ATRU-N .......................................... 32-18
Table 33-1 Identification of ATRU-M............................................................. 33-2
Table 33-2 Front panel LED indicators........................................................... 33-4
Table 33-3 Lamp rack connector (X311)......................................................... 33-5
Table 33-4 Door alarm connector (X312)........................................................ 33-6
Table 33-5 ATRU-U and GTRU-B physical specifications ...................................... 33-6
Table 34-1 Identification of BITS-B .............................................................. 34-2
Table 35-1 Identification of the blank LT filler plate ......................................... 35-2
Table 35-2 Dimensions of the LT filler plate ................................................... 35-3
Table 36-1 Identification of the blank NT filler plate......................................... 36-2
Table 36-2 Dimensions of the NT filler plate ................................................... 36-2
Table 37-1 Identification of EHNT-A and the associated optical modules ................. 37-2
Table 37-2 Specific information for 1AB 3566300XX modules................................ 37-4
Table 37-3 EHNT port LEDs ........................................................................ 37-9
Table 37-4 EHNT diagnostic LEDs................................................................. 37-9
Table 37-5 EHNT physical specifications ...................................................... 37-10
Table 38-1 Identification of EXNT-A and the associated optical modules ................. 38-2
Table 38-2 EXNT-A UNIT LEDs ..................................................................... 38-7
Table 38-3 NETWORK and O&M LEDs............................................................. 38-7
xlviii

Contents
Table 38-4 EXNT-A physical specifications...................................................... 38-8

Table 39-1 Identification of FILT-A and FILT-B................................................. 39-2
Table 39-2 Signal identification .................................................................. 39-3
Table 39-3 FILT-A physical specifications ....................................................... 39-4
Table 39-4 FILT-B physical specifications ....................................................... 39-4
Table 40-1 Identification of GLT2 ................................................................ 40-2
Table 40-2 GLT2-A, GLT2-B and GLT2-C differences .......................................... 40-3
Table 40-3 GLT2 LEDs .............................................................................. 40-4
Table 40-4 GLT2 physical specifications ........................................................ 40-7
Table 41-1 Identification of GLT4 ................................................................ 41-2
Table 41-2 GLT4 LEDs .............................................................................. 41-3
Table 41-3 GLT4 physical specifications ........................................................ 41-5
Table 42-1 LT card identification information ................................................. 42-2
Table 42-2 LT card features and application notes............................................ 42-2
Table 42-3 LT card general description ......................................................... 42-3
Table 42-4 Optical budgets of the LT card...................................................... 42-3
Table 42-5 LT card LEDs ........................................................................... 42-4
Table 42-6 LT card interfaces and connections ................................................ 42-4
Table 42-7 LT card physical specifications...................................................... 42-5
Table 43-1 NT card identification information ................................................. 43-2
Table 43-2 NT card features and application notes ........................................... 43-2
Table 43-3 NT card general description ......................................................... 43-2
Table 43-4 Optical module specifications....................................................... 43-4
Table 43-5 Optical budgets for the 1-GE 850 nm 550 m SFP ................................. 43-4
Table 43-6 Optical budgets for the 1-GE 1310 nm 10 km SFP................................ 43-5
Table 43-10 Optical budgets for the 10-GE 850 nm 300 m XFP .............................. 43-7
Table 43-11 Optical budgets for the 10-GE 1310 nm 10 km XFP ............................ 43-8
Table 43-14 NT card interfaces and connections .............................................. 43-9
Table 43-15 NT card LEDs ....................................................................... 43-10
Table 43-16 NT card power information ...................................................... 43-10
Table 43-17 EHNT physical specifications..................................................... 43-10
Table 44-1 Identification of the OLT rack assembly........................................... 44-2
Table 44-2 OLT rack assembly components list ................................................ 44-3
Table 44-3 Physical specifications of ETSI racks ............................................... 44-5
Table 45-1 Identification of OLTS-M ............................................................. 45-2
Table 45-2 Backplane connectors and related cables ......................................... 45-6
Table 45-3 Power and grounding signals ........................................................ 45-7
Table 45-4 Physical specifications of the OLTS-M ........................................... 45-12
Table 46-1 Identification of the SANC-D ........................................................ 46-2
Table 47-1 Identification of the rack for the video coupler.................................. 47-2
Table 47-2 Physical dimensions of the Tyco video coupler fiber rack ...................... 47-7
Table 47-3 54.82 cm (23 in) rack dimensions................................................... 47-7
Table 48-1 Identification of the subrack for video coupler .................................. 48-2
Table 49-1 Identification of VCS8-A.............................................................. 49-2
Table 49-2 Extreme rating for optical components ........................................... 49-4
Table 50-1 Identification of VCW4-A............................................................. 50-2
xlix
Contents
Table 51-1 Identification of VCSL-A.............................................................. 51-2

Table 51-2 Physical specifications ............................................................... 51-3
Table 52-1 Identification of VCW2-C............................................................. 52-2
Table 52-2 Optical budget of VCW2 connectors ............................................... 52-3
Table 52-3 Optical budget of WDM............................................................... 52-3
Table 52-5 VCW2 physical specifications........................................................ 52-5

General system description
1 Overview
2 Feature descriptions
3 Application notes
4 Functional description
5 Equipment layout
6 Operations, administration, and maintenance
7 Technical specifications


Overview
1.1 7342 ISAM FTTU overview

1.2 GPON features
1-2
1-4
1.3 Services features

1.4 Network interfaces
1-4
1-5
1.5 Element management system

1-6
1-1
1 Overview
1.1
7342 ISAM FTTU overview

The 7342 ISAM FTTU is a set of all-optical fiber-to-the-user systems that delivers
voice, data, and video services to residential and business subscribers. The
7342 ISAM FTTU collects and distributes high-speed digital information, using the
gigabit passive optical network (GPON) technology.
The 7342 ISAM FTTU consists of the following equipment:
P-OLT: the packet optical line termination unit that provides central processing,
switching, and control functions
V-OLT: the video optical line termination unit that distributes video signals
across the GPON
ONT: the optical network terminal located at the subscriber premises
EMS: the element management systems, including:
5528 WAM
5520 AMS
5523 AWS
Figure 1-1 shows the 7342 ISAM FTTU equipment deployed in a GPON network
topology.
1-2

1 Overview
Figure 1-1 7342 ISAM FTTU GPON network topology
Network
Central office or
remote terminal
Fiber
distribution
Passive
outside
plan
ONTs
End user
Optical link length 1
Optional RF
overlay
RF Video
provider
network
Ethernet
V-OLT/EDFA
1,550 nm
IPTV
MDU
WDM
Internet
Edge switch
router
1,490 nm
1,550 nm
2.4 Gb/s
1,310 nm
1.2 Gb/s
P-OLT
PSTN
Voice
gateway
EMS/NMS
Class 5
switch
Softswitch
1 The maximum optical link length depends on the specific equipment and deployment conditions
19684
The GPON optical fiber network connecting the P-OLT and the ONTs is a passive
optical network (PON) with no active or powered elements. The G.984.x series of
standards define how traffic is packetized and transported over the GPON.
Each GPON network connection from the P-OLT is a single optical fiber connection
that supports line rates of 2.4 Gb/s downstream and 1.2 Gb/s upstream as per the
ITU-T G.984 protocol.
Alcatel-Lucent recommends using FEC to reduce the impact of BER events on
downstream IP video traffic. With FEC applied, the 28 dB optical budget of the
GPON connection may reach up to 29.5 dB performance. Actual performance will
vary, depending on the specific equipment and deployment conditions.
Note Video performance varies according to the unique
characteristics of the customer-specific setup, such as channel

loading, video backbone, and delivery service quality. Due to high
variations in customer requirements, contact your Alcatel-Lucent
sales representative to determine the guaranteed video performance
for your specific network and video application.
1-3
1 Overview
The P-OLT supports up to a maximum of 32 GPON network connections.

The 7342 ISAM FTTU supports multiple services over the GPON, including: voice,
data, and video. Using the V-OLT, the 7342 ISAM FTTU supports standard cable
television video services, as well as analog and digital channels. The V-OLT
supports the full radio frequency (RF) spectrum of 47 MHz to 862 MHz.
1.2
GPON features
The 7342 ISAM FTTU provides the following GPON features:
bidirectional voice, data, and IPTV services for a maximum of 64 outdoor, indoor
1.3
or business ONTs per PON

forward error correction (FEC) on PON interface
RF video distribution services that support analog and digital channels
Raman reduction on PON interface for RF video service
configuration support for Multimedia over Coaxial Alliance (MoCA) for ONTs
that support MoCA
line rates of 2.488 Gb/s downstream and 1.244 Gb/s upstream
a maximum of 18.6 miles (30 km) reach
GEM-based encapsulation on the GPON
compliance with full service access network (FSAN) standards
Services features
The 7342 ISAM FTTU supports multiple services, including: voice, data, IPTV and
RF video, and CES encapsulated DS1 or E1 over the packet-switched network
(PSN).
Voice service
The 7342 ISAM FTTU interoperates with both the traditional Class 5 switches over
the public switched telephone network (PSTN) and the softswitches over the
broadband data network to provide voice over IP (VoIP) service to subscribers. The
VoIP service supports protocols that include H.248/Megaco, and session initiation
protocol (SIP).
Data and IPTV services

The 7342 ISAM FTTU supports data and IPTV services that are delivered through
the same high-speed Ethernet interface. The IPTV service is provided in-band of the
Ethernet data service. Subscribers need a set-top box to use the IPTV service.
1-4

1 Overview
RF video service
The 7342 ISAM FTTU supports RF video service. The RF video service supports the
full cable television (CATV) spectrum from 47 MHz to 862 MHz. The CATV
service options supported include: video on demand (VOD), interactive video for
games, and standard or premium analog and digital channels. Service provider
supplies and installs a set-top box at the subscriber premises for access to RF video
service.
Consider the following when planning video deployments:
ONTs supporting video overlays only support a 1:4 split ratio

The maximum supported length of RG9 or RG59 coax cable is 100 ft (30.48 m)
CES encapsulated DS1/E1
The 7342 ISAM FTTU P-OLT seamlessly passes CES DS1 or E1 traffic across the
Ethernet-based GPON packet-switched network. The P-OLT receives packetized
TDM traffic from the service provider through one of the Gigabit Ethernet network
connections on the NT unit, or from the GPON on any of the GPON GEM ports of
the LT unit.
1.4
Network interfaces
The 7342 ISAM FTTU provides a high-speed and high-bandwidth access network.
This access network includes the following interfaces:
the P-OLT interfaces between the gigabit Ethernet (GE) network and the ONTs
the V-OLT interfaces between the video service provider network and the ONTs
the ONT interfaces between the P-OLT and the subscriber equipment
The interfaces support the following connectors:
P-OLT optical network connection to the Ethernet network: LC/UPC

P-OLT optical network connection to the GPON: SC/UPC
ONT optical network connection to the GPON: SC/APC
P-OLT interfaces
The P-OLT system provides the core processing, switching, and control functions.
In the upstream direction, the P-OLT interacts with the Ethernet switch and voice
gateway using the network termination (NT) cards.
In the downstream direction, the P-OLT distributes voice, data and in-band video,
and CES DS1 or E1 traffic to the ONTs over the GPON. At the P-OLT, line
termination (LT) cards terminate the GPON connections.
The P-OLT also contains an alarm control card and craft interfaces that allows EMS
access to the 7342 ISAM FTTU system for operation, administration, and
maintenance (OAM) purposes.

1-5
1 Overview
Each P-OLT system supports a maximum of:
two NT cards
16 LT cards
32 PONs per P-OLT with each LT card supporting two PONs
64 indoor ONTs, outdoor ONTs, or business ONTs per PON
48-Gb/s switching capability
V-OLT interfaces
The V-OLT distributes RF video services across the PON from the video service
provider to the subscribers.
The V-OLT provides the interface between the video service provider network and
wavelength division multiplexing (WDM) unit. The ONTs connect to the video
service provider network using the GPON and WDM.
The video coupler amplifies the video signal that is carried over a PON using the
erbium doped fiber amplifiers (EDFAs).
ONT interfaces
See the 7342 ISAM FTTU ONT Product Information Manual for more information
about ONT interfaces.
1.5
Element management system

The EMS manages the P-OLT remotely from a central location. This release
supports the following.
5523 AWS
The 5523 AWS is a full-featured EMS. The 5523 AWS covers fault, configuration,
and performance management of access networks. The 5523 AWS can manage up to
one million lines and 100 operator positions. The 5523 AWS is also scalable to meet
performance demands as the managed network grows.
For more information, see the 5523 AWS operations and maintenance manual.
5520 AMS
The 5520 AMS provides an intelligent GUI to translate simple point-and-click
actions to complex MIB variables and sequences of TL1 or SNMP commands. The
5520 AMS uses a UNIX-based client-server architecture.
1-6

1 Overview
The network manager allows the 7342 ISAM FTTU components that are far from
the CO to be managed from one location. The network manager can perform remote
fault management, including 24 hour/day remote alarm surveillance with logs and
alarm history. This includes real-time alarm and event monitoring with user-defined
alarm views. It can also perform daily performance monitoring, including
performance history, traffic monitoring, test management, and diagnostics. It allows
TL1 cut-through and flow-through provisioning.
The 5520 AMS has a Java-based platform and provides advanced OSS interfaces
based on Web Services (XML/SOAP).
For more information, see the 7342 ISAM FTTU Operations and Maintenance using
5520 AMS.
5528 WAM
The 5528 WAM can be used as a low-cost, web-based enhanced craft terminal
(ECT) or a web-based element manager server. The 5528 WAM allows registered
users to log in to the P-OLT through the Internet to monitor, provision, and configure
network elements. The 5528 WAM is highly scalable and can manage a wide range
of network domains. The web client-server architecture provides mobility and
flexibility for equipment management operation. The instant access to the local
database in P-OLT provides run-time equipment condition and effective operation.
The plug-and-play capability and the complete TL1/CLI scripting environment with
cut-through window also offers non-service affecting customization to address
specific operational needs.
For more information, see the 5528 WAM customer documentation.

1-7
1 Overview
1-8

Feature descriptions
2.1 Overview
2-2
2.2 Release FGU 04.06.08 features
2-2
2-2
2-3
2.5 Release FGU 04.06.00 and 04.06.01 features

2-6
2-6
2-8
2.9 Release FGU 04.04.10 and 04.04.10a features

2.10 Release FGU 04.04.00 and 04.04.01 features
2-3
2-8
2-9
2-11
2.12 Release FGU 4.3 features
2-11
2-12
2-13
2-14

2-1
2.1
Overview
This chapter provides a brief description of the features for the 7342 ISAM FTTU.
2.2
Release FGU 04.06.08 features

Table 2-1 describes the features for 7342 ISAM FTTU FGU 04.06.08.
Table 2-1 Features for FGU 04.06.08
Feature
Description
VoIP configuration and

functionality changes
For SIP and Megaco:
modification of G.729 codec negotiation to add an additional option

fixed dBm value for DTMF out-of-band
identical p-time values in the respond and the invite
tone updates for bye and busy line
option to handle whether route header is included in outgoing requests
option to remove port number from URI
Support for multiple new calling features on the Centile softswitch.

Review critical temperature
thresholds
Migration support
The operator can use CLI to review current temperatures and thresholds for
temperature TCAs for NT, LT, and ACU cards.
Migration support to Release 04.06.08 from:
04.06.04
04.06.xx
04.05.x (latest FGU 4.5. release)
Alarms for LT resets
Support for the NT to raise an alarm each time an LT reboots, including details on the
slot where the reboot occurred.
Business service support on the

Next Generation ONTs
(I-x4xG-B)
The Current Generation ONTs (I-24x, I-040, B-0404-A) must be enabled for port-to-port
communication to support the flexible mode; in this communication mode, a business
service can only be configured on port 1, and the service is replicated on the other
enabled ports.
The Next Generation ONTs (I-x4xG-B) do not have to be in port-to-port communication
to support the flexible mode, and support business services separately on each of their
4 UNI ports.
CIDR support
The system supports CIDR (Classless Inter-Domain Routing) on the management

interface.
User-controlled rate limiting on

the ONT for IGMP, DHCP, and
ARP
For the protocols IGMP, DHCP, and ARP, the system provides a facility to enable rate
limiting on a per protocol per UNI basis.
IGMP channels multicast

bandwidth usage at ONT UNI
Ability to disable LT monitoring of multicast bandwidth consumption by the ONT UNI

for IGMP channels, to support vendor-specific applications.
Enhanced RSSI support
Support for enhanced RSSI capabilities with a new variant of the GLT4-A card
2.3

Table 2-2 describes the features for FGU 7342 ISAM FTTU FGU 04.06.06.
2-2

Feature
Description
ARP snooping on a per VLAN

basis on the LT
The system supports ARP snooping on the LT on a per PON VLAN basis. This function
enables the LT to snoop ARP responses to hosts to learn their MAC address and IP
address, so that the system can dynamically add their static entries in the ARP table.
This function is useful for deployments where IP addresses that are statically assigned
to hosts cannot be entered manually in the system, such as Video-on-Demand.
2.4

Feature
Description
VoIP configuration and

functionality changes
For SIP:
change to the configuration value to determine a different method of putting calls

on hold using the inactive method
change to the far_end_symmetry parameter behavior
For MEGACO:
change to the configuration value to determine a different method of putting calls

on hold using the inactive method
Increase in the configurable

number of MAC addresses
The ONT Ethernet port supports up to 2048 dynamic and/or static configured MAC
addresses.
Configurable LT slot ranges
The operator can configure the lt_slot range that is used in DHCP Option 82, 802.1x,
and other messaging. The allowable ranges are 1-18 and 3-20.
Interoperability enhancements
with third-party ONTs
The operator can configure some parameters that apply to certain third-party ONTs, to
make interoperability easier.
Configurable ENV alarm

description field
The operator can configure the description of an ENV environmental condition alarm,
to make the alarm more representative of the condition it is reporting.
VoIP service alarm change
The VDHCPERR alarm is renamed to VNTWKERR, to better represent that the cause of
a service error alarm may be due to DHCP or PPPoE problems.
Remove IP addresses from ARP

table
You can, per VRF, identify and remove a specific IP address or range of IP addresses
from the ARP table
Multicast translation in
different VLANs
The operator can configure the system to use RIP to analyze downstream packets from
a specific VLAN and have those packets replicated to associated GEM ports.
2.5
Release FGU 04.06.00 and 04.06.01 features

Table 2-4 describes the features for 7342 ISAM FTTU FGU 04.06.00 and 04.06.01.

2-3
Table 2-4 Features for FGU 04.06.00 and 04.06.01
Feature
Description
SNMP community names

increased
The system now supports SNMP community name configuration for up to forty entries
or managers, or both (different communities or network access rules, or both) on the
P-OLT and SHub.
Downstream rate-limiting to
ONT on a per-service basis
Downstream rate-limiting can be configured on an ONT to operate in one of two ways:

on a per-ONT basis or a per-service basis. In the latter case, downstream rate-limiting
service schedulers are created and applied to HSI, CES PW, and VoIP services, and to
portals.
T-CONT per EVC
The T-CONT per EVC model allows multiple services for a single subscriber to share the
same T-CONT.
T-CONT per CoS
The T-CONT per CoS model allows multiple services for different subscribers to share
the same T-CONT.
T-CONT per service
The T-CONT per service model allows multiple subscribers of the same service to share
the same T-CONT.
Port-to-port communications
The system supports enabling and disabling of port-to-port communications on the I-24x
and I-040 indoor series ONTs.
ONT-to-ONT communications
for VoIP services
ONT-to-ONT communication using the LT cards is configurable, to allow ONT-to-ONT

VoIP VLANs.
FTP server security

configuration support
You can configure an FTP server username and password, to secure XML configuration
file downloading.
NT reboot alarm support
An alarm is raised when an NT card reboots.
SNMP error log message IDs
You can use RTRV-ERRORLOG to view the reasons why some SNMP Gets and Sets failed.
Additional RSSI capabilities
Ability to enable or disable the collection of the ONT RSSI levels and to display the
history using the TL1 command REPT-OPSTAT-OPTICSHIST.
Report distance between ONT

and OLT
Additional parameter of the REPT-OPSTAT-ONT command to display the estimated

distance between an ONT and the OLT.
Lowercase support for TID and

SID
Both the TID and SID can contain any combination of lowercase and uppercase letters,
numbers, and hyphens, and are case-sensitive when compared to each other.
Thermal status of P-OLT

equipment
The system supports the retrieval of thermal readings for NT, ACU, and LT cards.
Prioritization of IP filters
The IP filter number uniquely identifies an IP filter, and also designates the priority of
the IP filter relative to others, such that the lowest numbered filter has the highest
priority.
Delivery of SLID to P-OLT
The system supports two modes to deliver a permanent SLID from the ONT to the P-OLT:
The proprietary mode uses the proprietary PLOAM message used in the predecessor
to FGU 04.06.00.
The registration ID mode uses the password PLOAM message defined in G.984.3.
The system uses the proprietary PLOAM message to deliver a volatile SLID.
(1 of 3)
2-4

Feature
Description
Ethernet services for business

and residential applications
The system supports Ethernet services for business and residential applications, which
provide the following functionality:
Subscriber scalability
six basic models to configure a leg of an EVC on the 7342 ISAM FTTU, including:
bundling and single CoS
bundling and multiple CoS
all-to-one bundling and single CoS
all-to-one bundling with multiple CoS
T-CONT per EVC
T-CONT per CoS
single-tagged frames in a stacked VLAN, to support all-to-one bundling
transparent pass-through of untagged frames from the CPE, to support all-to-one
bundling
transparent pass-through of double-tagged frames across the FTTU access network,
to support wholesaling services on the PON, and mixed business services, such as
point-to-point and xDSL.
setting of p-bit in the outer S-VLAN tag to a defined value while retaining the
subscriber p-bit, to support the bundling of a number of C-VLANs in a single S-VLAN
for a network service provider
mapping of business traffic at the LT to the CoS in the aggregation network, while
retaining the subscriber p-bit
mapping and translation of both the customer p-bit and VLAN ID on the UNI side to
their equivalent customer p-bit and C-VLAN ID on the network side
multiple cross-connect VLANs on the same ONT UNI
T-CONT sharing across multiple ONT UNIs on the same ONT for a single service
T-CONT sharing across multiple services on the same ONT UNI
T-CONT sharing across multiple services across multiple ONT UNIs on the same ONT
upstream segregation of single- and double-tagged frames in the same service to
GEM ports
Subscriber scalability is supported by the ability to disable MAC learning and enable
subscribers of a service to share a T-CONT as follows:
disable MAC learning for LT ports on a range of VLANS on the SHub

configure a T-CONT per service EVC model that supports T-CONT sharing across
multiple UNIs on an ONT for a single service
Decimal IGMP package numbers
IGMP package numbers may now be entered as decimal values, in addition to the
hexadecimal format currently supported.
AES disable support
In cases where an ONT supporting AES is replaced by an ONT that does not support AES,
the system will automatically disable AES for that particular ONT. No profile change is
required.
Increased number of IGMP

packages
The maximum number of IGMP packages is increased to 1024.
Increased IGMP signaling

channels
The maximum number of IGMP signaling channels per PON is increased to 288.
The maximum number of IGMP signaling channels per GLT2 is increased to 576.
The maximum number of IGMP signaling channels per GLT4 is increased to 1152.
Support for mis-sequenced and

dropped packets on the SHub
caused by reconvergence of a
blocked link
To minimize the number of mis-sequenced or dropped packets when a blocked link is

removed and reconnected, ensure that the root bridge forward delay time for the SHub
matches the ageing time-out for dynamic MAC entries. For more information, see
7342 ISAM FTTU Operations and Maintenance Procedures Guide using TL1 and CLI.
Support for Cisco routers
Typically, a proxy ARP request is sent from the LT to the CPE with a source IP address
of 0.0.0.0. The ONT can now send the proxy ARP packet to the CPE with the source IP
address set to the destination IP address, for routers that validate the source IP
address.
Retrieve PON bandwidth
Ability to retrieve the booked and currently provisioned aggregated PON bandwidth
details, such as CIR, AIR, and EIR.
(2 of 3)

2-5
Feature
Description
LT card software download
Ability to trigger the download of an LT card OSWP load to a user-specified range of

cards.
ONT software version control

table
Table entries that associate an ONT hardware version and hardware variant to an ONT
software file. An automatic ONT software download is accomplished if ONT is set for
auto download and the hardware criteria matches the table entry.
(3 of 3)
2.6

Feature
Description
2048 kHz clock source
The BITS interface on the EHNT-B and EXNT-A supports a 2048 kHz clock source.
Additional optical SFP and XFP

modules
Support for new optical modules, allowing greater flexibility in deployment lengths and
wavelength management.
Virtual Router Redundancy

Protocol (VRRP) transparency
The facility to enable multicast flooding on a SHub VLAN basis is provided, so that VRRP
packets are not blocked and are forwarded to a second network port.
Migration of dynamic data on

the SHub
In some cases, the ODMT did not migrate the dynamic data on the SHub. The ODMT now
migrates both the static and dynamic data on the SHub whenever possible. Migration of
the dynamic data lessens the load on the SHub, and enables fast recovery of the system
as tables do not have to be rebuilt and entries re-learned. Traffic such as multicast
traffic, resumes more quickly.
Wholesale video
Wholesale video is available through residential-bridging.
SLID
The P-OLT can also communicate with the ONT if the ONT is installed and the P-OLT
knows the SLID of the ONT. Configuration of the ONT and its services can be done at
the P-OLT before or after the ONT is installed. After the P-OLT polls the PON for new
ONTS and the ONT sends its SLID, range, and registration information, the P-OLT
searches the P-OLT database for the same SLID. If a match is found, the P-OLT registers
the serial number of the ONT, and downloads ONT and service configuration data to the
ONT.
2.7

Feature
Description
Increase in number of
bandwidth profiles
The number of provisionable bandwidth profiles increases from 50 to 250.
Network interface port statistics
The ability to retrieve 32-bit performance monitoring counters for a network interface
port on the SHub using CLI is provided.
(1 of 3)
2-6

Feature
Description
Ethernet port auto detection
The parameter values for Ethernet port auto detection are updated.
Protocol type filtering
The ability to filter on protocol type only (also known as EtherType) is provided. The
CLI commands configure transport shub mac-filter and show transport shub mac have
been modified to allow and show protocol filtering across all source and destination
MAC addresses. For the CLI command configure transport shub mac-filter, the filter
parameter has been modified to allow filtering on the range of any source MAC address
to any destination MAC address. For example, this feature enables you to block LLTD
(Link Layer Topology Discovery) in Windows Vista based on EtherType 88d9.
Gratuitous ARP discard
The 7342 ISAM FTTU supports a discard mechanism that filters incoming traffic for
gratuitous ARP requests. When gratuitous ARP discard is enabled, incoming gratuitous
ARP requests are discarded. Gratuitous ARP discard is configured on an ONT UNI port
basis.
Support for T-CONT type 2 and

T-CONT type 3
The ITU-T G.984.3 standard classifies T-CONTs into five types of containers. The DBA
algorithm now supports T-CONT types 1 through 5. T-CONT type 2, assured bandwidth,
and T-CONT type 3, assured bandwidth and non-assured bandwidth, are available.
Dynamic source address

anti-spoofing with DHCP
Where the IP or MAC source addresses are not known, dynamic source address
anti-spoofing is available.When dynamic anti-spoofing is enabled, an IP address is
dynamically added to the anti-spoofing table of authorizing source addresses when a
host sends a DHCP ACK message, and is deleted when the DHCP lease expires.
VDSL2 supported in lieu of

VDSL1
VDSL consists of two versions: VDSL1, which is the original VDSL, and VDSL2. The
7342 ISAM FTTU system no longer supports VDSL1 configuration. However, VDSL2 is still
configurable using xDSL TL1 commands. The upgrade to FGU 4.05.05 requires the
migration of existing VDSL1 services to VDSL2. However, a modem with VDSL1 firmware
can transparently convert a VDSL2 service to VDSL1.
EXNT support for OLTS-M
The ETSI configuration for the 7342 ISAM FTTU system using the OLTS-M shelf, now
supports the use of the EXNT card.
RSSI: Measure optic power levels

on OLT/ONT
The ability to provide on demand RSSI values for a GLT4 PON 1490nm transmit, a GLT4
PON 1310nm receive and a specified ONT 1490nm receive. The optical power level is
reported as a dBm value and has an accuracy of +/-3dB.
Support for IEEE-1588v2

network clock synchronization
The EXNT-A card can be configured to use the Precision Timing Protocol (PTP) to
synchronize the 7342 ISAM FTTU system clock to the 1588 master clock in the network.
LT event logging
Protection switching events and LT card resets are both logged by syslog. The syslog
output can be reviewed to track LT card behavior.
Secondary softswitch IP address

configuration
A second softswitch IP address can be configured using TL1, eliminating the need for a
DHCP server in some network configurations.
Emergency call in progress

alarm
Support for a new alarm that alerts the network equipment operator that an emergency
call is in progress on an ONT or MDU.
Flushing of learned MAC address

entries
When an Ethernet port goes out of service, the learned MAC address entries in the VLAN
forwarding database for the port are flushed. This feature enables an installer to move
from one ONT to another using the same MAC source address, without having to wait
for the learned MAC address entries to age.
Duplicate MAC filters on LT card
The BridgePort does not get blocked when a duplicate MAC address is detected.
When a duplicate MAC address is detected, a MAC filter is installed on the LT card to
drop subsequent packets from the BridgePort with the same source MAC address.
Frames with different source MAC addresses are not discarded; traffic destined to the
duplicate MAC address is forwarded to the first BridgePort where the duplicate MAC
address was learned.
To handle duplicate MACs, the GLT4 reserves 64 MAC filters and the GLT2 reserves 32
MAC filters. When all reserved MAC filters are installed, the bridge port is blocked when
an additional duplicate MAC address is detected.
(2 of 3)

2-7
Feature
Description
Optical reach
The 7342 ISAM FTTU system typically supports a maximum of 18.6 mile (30 km) span,
for all GLT cards.
Layer 3 support on EXNT-A
The EXNT-A card provides layer 3 support. Layer 3 is the network layer of the OSI model
that determines how data is transferred from a source to a destination through the
network, while maintaining QoS service level agreements.
(3 of 3)
2.8

Feature
Description
Increase of number of
provisionable multicast sources
The number of provisionable entries in the multicast source table increases from 2048
to 4096.
EXNT-A High Capacity NT
Introduction of a new NT card that supports redundant XAUI links to GLT4-A and GLT2-C
cards in the OLTS-L and OLTS-M shelf types.
Failure/Fault data captured
Failure data is captured if the NT crashes. This data includes NT and LANX information
and is retrieved using TFTP.
SMAC alarm
Alarm indicating a problem with the SMAC card on the OLT shelf.
Ping the LANX VRF using CLI
Perform a ping test to a VRF ID on the SHub.
Bridgeport disabled alarm
Alarm indicating when a bridge port has been disabled as the result of too many
exceptions.
Card synchronization alarm
Alarm indicating a card synchronization clock input failure.
Deletion of dynamic MAC

address entries
The capability to delete a MAC address entry that is learned dynamically in a VLAN
forwarding table at the LT card is provided.
64-bit counters
The P-OLT supports 64-bit counters for the SHub bridge ports.
Megaco pull/break dial tone test
The Megaco (H.248) pull/break dial tone test returns time measurements in 0.1 second
increments for both the pull and break portions of the test, if the test result is with
data.
Physical address format of

Option 82 field
The ability to set the physical address format for the Option 82 field is provided.
Configurable p-bit setting for

IGMP signaling
The ability to configure the p-bit setting for IGMP signaling is provided at both the
system and subscriber level.
Gigabit Ethernet interface

requirements
Maximum Ethernet frame size of 2000 bytes supported at the OLT and ONT interface.
2.9
Release FGU 04.04.10 and 04.04.10a features

Table 2-8 describes the features for 7342 ISAM FTTU FGU 04.04.10 and 04.04.10a.
2-8

Table 2-8 Features for FGU 04.04.10 and 04.04.10a
Feature
Description
Physical address format for

Option 82 circuit ID
You can choose the physical address format for Option 82 circuit ID.
IP-based multicast forwarding
Forwarding of IP multicast streams is based on the destination IP multicast address, to

allow for static and dynamic multicast streams that map to the same multicast MAC
address.
TL1 management over telnet
TL1 over telnet is supported for this release. The 7342 ISAM FTTU also provides the
following management sessions for CLI and TL1:
CLI via telnet and SSH

TL1 via UDP and SSH
Management loopback interface

on the SHub
A management loopback interface can be configured on the SHub using CLI and TL1
commands.
Full characters in TL1

commands.
The exclamation mark ! can be used in TL1 commands unless otherwise indicated.
SNTP configuration via TL1
The 7342 ISAM FTTU supports full SNTP configuration via TL1.
LANX VLAN PM counters
The 7342 ISAM FTTU supports VLAN performance monitoring counters.
1000Base-T electrical SFP

interface
A new 1-GigE electrical small factor pluggable interface for the 7342 ISAM FTTU.
802.1ag OAM statistics
You can collect statistics on OAM diagnostic tests.
VLAN translation and EtherType

classification
Using VLAN translation in combination with EtherType classification, you can support
IPoE and PPPoE data traffic that uses the same p-bit and same C-VLAN to go on to
different network VLANs.
OLTS-M support
Support for the OLTS-M shelf in the ETSI market, which contains 14 LT slots that support
GLT4 cards in either a 2200 mm standard ETSI rack or in a 19-in. rack for the APAC
market.
2.10
Release FGU 04.04.00 and 04.04.01 features

Table 2-9 describes the features for 7342 ISAM FTTU FGU 04.04.00 and 04.04.01.
Table 2-9 Features for FGU 04.04.00 and 04.04.01
Feature
Description
System logging for

7342 ISAM FTTU
A logging mechanism for collecting data from the device, which can be retrieved even
after a system reset. The log includes debugging details, such as:
New VLAN IDs available
BCM counters
resource failure statistics
memory error counters
port link status
CPU packet counter
protocol packet counters
event triggered logging for application resets and watchdog timer resets
Formerly reserved VLAN IDs in the OLT (4091, 4092, and 4093) are now configurable,
allowing operators to use these ranges for other purposes.
(1 of 3)

2-9
Feature
Description
VLAN stacking for voice
A single VLAN (CVLAN) now can be configured for all the voice traffic on an ONT. (Not
supported on the M-300 MDU.)
Flow mirroring
Non-intrusive mirroring or tapping of OLT/ONT virtual connections is provided for

diagnostic purposes.
C-VLAN forwarding
A new VLAN type of iBridge with C-VLAN forwarding is available to allow for the
occurrence of duplicate MAC addresses when residential gateways are purchased over
the counter.
DSCP to p-bit mapping
The mapping of blocks of DSCP numbers to a p-bit value is configurable at the service
interface level.
AGC offset setting point
Using an EMS interface, the operator can enter the number of analog channels and the
number of digital 256-QAM channels, which set the measurement offset that the ONT
should use if it operates in AGC mode
Provisionable EtherType
The EtherType of the S-VLAN is provisionable with a a default value of

8100 hexadecimal.
Dynamic bandwidth allocation
The operator can associate a new bandwidth profile to a provisioned service while it is
in service to change its bandwidth characteristics.
Multicast package support
This feature provides improved ONT PIM call statistics.
IP and MAC anti spoofing
A filter is implemented at the ONTs to allow the access nodes to inspect each upstream
packet for source address.
POTS UNI alarms
Nine POTS UNI alarms are introduced:
VoIP client alarms
iConfig subscription failure

iConfig notify failure
iConfig HTTP redirect failure
SIP registration failure
SIP invite failure
SIP subscribe failure
SIP message time-out TCA
Bearer packet loss TCA
Jitter TCA
Three VoIP client alarms are introduced:
iConfig subscription failure

iConfig notify failure
iConfig HTTP redirect failure
VLAN-based performance
monitoring
Performance monitoring of traffic flow through the NT and LT units are available by
C-VLAN and p-bit in addition to current statistics by MAC source address, MAC
destination address, and S-VLAN.
IPSec and IKE configuration and

status checking
Using CLI, the operator can configure and verify the status of the Internet protocol
security (IPSec) and Internet key exchange (IKE) services.
OAM 8021.ag diagnostics
The 802.1ag standard defines OAM mechanisms for Ethernet. The following OAM
diagnostics are supported:
TL1 management over telnet
TL1 over telnet is supported for this release. The 7342 ISAM FTTU also provides the
following management sessions for CLI and TL1:
Multicast packages
link traces
loopbacks
continuity checks
CLI via telnet and SSH

TL1 via UDP and SSH
Multicast streams can be grouped into one or more multicast packages that are offered
to subscribers as a group of viewing or listening channels.
(2 of 3)
2-10

Feature
Description
New TL1 and CLI guide
Creation of a new 7342 ISAM FTTU Operations and Maintenance Procedures Guide using
TL1 and CLI with the following sections:
TL1 and CLI training

P-OLT system turn up
P-OLT system configuration
Security configuration and maintenance
VLAN configuration
Preservice configuration
Data service configuration
Voice service configuration
Multicast IGMP service configuration
RF video service configuration
Statistics
Maintenance tasks
Traceroute procedure
Steps documenting how to perform a traceroute action are included in the renamed
Remote debugging DLP along with steps for performing a ping test.
DELT support
TL1 commands for obtaining XDSL statistics are now documented.
(3 of 3)
2.11

Feature
Description
Hardware watchdog
The hardware watchdog process monitors system software to ensure that sufficient CPU
cycles exist to handle the current usage load. This feature is automatically configured,
and requires no user intervention.
2.12
Release FGU 4.3 features

Table 2-11 describes the features for 7342 ISAM FTTU FGU 4.3.
Table 2-11 Features for FGU 4.3
Feature
Description
CAC bandwidth check
A CAC bandwidth availability check is performed every time a subscriber service is

added to a GPON VLAN and when an SHub VLAN is added to a network port or LAG.
FEC error correction
FEC error correction can be applied to the 1310 nm upstream and 1490 nm downstream
GPON links between the P-OLT and ONTs to improve performance on links that are
framing properly and have a recovery clock but are experiencing BER.
(1 of 2)

2-11
Feature
Description
GPON throughput rate
The GPON downstream throughput rate on the LT is increased to enable the maximum
line rate of 2.4 Gb/s on each PON. This is accomplished by improving the throughput
efficiency on the LT and by duplicating multicast streams so that each PON has access
to the same multicast channels.
IGMP v3
IGMP v3 is now supported. The NT cards support the IGMP proxy function and the ONTs
support the IGMP snooping function.
Hashing improvements
The platform has been improved to use downstream multicast as part of the hashing
function. (All hashing at the P-OLT is based on at least a source and destination IP
address.)
RIPv2
Static multicast channel support allows the transmission of RIPv2 multicast packets on
both the LT and the NT.
New UNI modes
Two new UNI modes are added. These are Ethertype translation mode and VLAN
translation mode.
Performance monitoring (PM)

enhancements
All PM counters on the OLT are 15-min interval counters. Some counters are redefined
to specifically be always on or on demand, and some implementations are limited
to a per port or per shaper basis rather than per queue.
VLAN translation improvements
Formerly, incoming CVLANs were overwritten by the SVLAN towards the network when
unstacked mode was used. Now, when a customer sends a CVLAN upstream (using
either stacked mode or unstacked mode), the same CVLAN tag is returned. VLAN
swapping is allowed as well, and the customer can configure a mapping table between
CVLANs and SVLANs to accommodate CVLAN/SVLAN translation according to WT-101.
Multicast rate increase
The 1 Gb/s multicast rate limit over the eHCL connections from the NT cards to each
LT card has been increased through hashing to 4 Gb/s.
User account and security

logging
Additional security features are introduced to log actions performed on the

7342 ISAM FTTU to a security system log (syslog).
OLT management improvements
TL1 commands have been added to create and manage VLANs on the SHub at the
network side and to retrieve PM counters. Several TL1 error codes have also been
modified to include SNMPv3 parameters.
Information label field

extension
The information label fields are extended to 80 characters for several TL1 commands.
SHub software version and

bootrom version access
CLI commands are used to retrieve the NT SHub software version and bootROM version.
(2 of 2)
2.13

Feature
Description
DHCP Option 82
The remote node ID for DHCP is supported. When DHCP is enabled on the VLAN, the
GLT2 sends the remote node ID sub-option in Option 82 of DHCP requests. The remote
node ID is configurable in one of two formats: Do not add or customer ID. The customer
ID is an ASCII string configurable for each UNI for each service. You cannot configure
both the circuit ID and remote node ID as customer ID.
MoCA configuration support
MoCA configuration is supported at the P-OLT.
(1 of 2)
2-12

Feature
Description
OLT security
Accept All and Reject All authentication requests are supported. When there is an NT
restart or network problem, all RADIUS servers of a VRF may be unreachable. In this
case, the OLT provides two authentication options. The default is to reject all
authentication requests. When Accept All is configured, an EAP Success is returned to
the ports that are trying to authenticate with a lease time of 30 min.
Performance monitoring
enhancements
Enhancements to the 15-min statistics counters allow for the retrieval of the
in-progress count for the current 15-min interval.
Additional internal 15-min and rolling counters for the collection of statistics are
provided for VLAN-based traffic at the NT unit and LT unit on the P-OLT.
TCA notification support is provided for selected 15-minute statistics counters.
Ping
From a TL1 management session with the P-OLT, you can initiate a ping from the ONT
to any host device or server on the GPON. You can also disable the ONT from responding
to ping requests. The ONT responds to ping requests by default.
PPPoE
The sub-option 2 of PPPoE is supported. When PPPoE is enabled on the VLAN, the OLT
inserts sub-option 2. The sub-option 2 can be configured in one of the two formats: Not
add or customer ID. You cannot configure both sub-option 1 and sub-option 2 as
customer ID at the same time.
QoS
The QoS function supports 8 priority queues in the downstream direction towards each
PON and 8 priority queues for the GE port in the upstream direction. The queues are
serviced in strict priority or WRR which is configurable on a per port basis. The mapping
of p-bits is configurable on a system-wide basis. The highest priority queue is reserved
for internal VLAN traffic using VLAN ID 4094. The number of queues, scheduling
methods, and buffer sizes on the internal and external GE ports of SHub are
configurable.
Raman crosstalk reduction
The P-OLT provides Raman crosstalk reduction that you can enable using TL1 to reduce
the effect of downstream digital signals from causing interference on overlaid video
broadcast services on the GPON system.
RMON Ethernet statistics
The P-OLT supports RMON Ethernet statistics (RFC 2819) on its NT Ethernet ports using
any RMON SNMP manager.
Static IP addresses
Static IP addresses for residential gateways are supported. Service provider can
configure static IP addresses in the P-OLT and enable DHCP relay. When static IP
addresses are used, GLT2 periodically uses ARP to allow the users to obtain their MAC
addresses.
Upstream FEC
Forward Error Correction (FEC) is used by the GEM transport layer between the ONTs
and an P-OLT, and is based on transmitting the data in an encoded format. The
encoding introduces redundancy, which allows the decoder to detect and correct the
transmission errors.
(2 of 2)
2.14


2-13
Feature
Description
Compliance to industry
standards
The 7342 ISAM FTTU equipment has been tested and is compliant with industry safety
standards in both the ANSI and ETSI markets.
GPON
The following GPON features are supported:
P-OLT
10-GE XFP 850 nm MMF 984 ft (300 m)

10-GE XFP 1310 nm SMF 6.21 mi. (10 km)
GPON grant rate calculation improvement
support for SLID repair scenarios
temperature hardened XFP
definition of SFPs
The following P-OLT features are supported:
persistent proxy ARP data over an LSM reset

DHCP Option 82 relay agent
PPPoE relay agent
802.1x re-authentication
VLAN pass-through
increased scalability parameters
management of video overlay services
V-OLT
The V-OLT and the video coupler are supported. The V-OLT and the video coupler are
managed by the P-OLT.
OAM
The 7342 ISAM FTTU is OSMINE certified.
2.15

Table 2-14 lists and describes the features for 7342 ISAM FTTU FGU 4.0.
Feature
Description
7342 ISAM FTTU
The 7342 ISAM FTTU is an environmentally hardened GE IP solution for deployment in

both ANSI and ETSI markets. The system provides voice, data, and video/television
services for up to 2048 subscribers using passive fiber optics. The system has a reach of
up to 12.4 miles (20 km), depending on the bandwidth.
P-OLT
The 7342 ISAM FTTU is a single-shelf system. In a CO or CEV environment, at least one
P-OLT is installed on a rack. The P-OLT consists of one alarm card, two NT cards, and
one to 16 LT cards. Each LT card has two PONs. Each PON supports a maximum of 64
ONTs. Each system provides a 48 Gb/s switching matrix. Each NT card supports four
northbound GE interfaces and one 10-GE northbound interface (a maximum of 14 Gb/s
per NT). A second 10-GE interface provides redundancy between the two NT cards. The
NT provides 2 Gb/s upstream and downstream per LT card. Each LT card has two PONs;
each PON provides 2.4 Gb/s downstream and 1.2 Gb/s upstream bandwidth for a
maximum of to 64 ONTs.
GPON MAC FPGA
The GPON MAC FPGA supports the GEM protocol as specified in G.984.2 (physical layer),
G.984.3 (TC), and G.984.4 (OMCI). The GPON MAC FPGA supports a maximum line rate
of 2.488 Gb/s downstream and 1.244 Gb/s upstream with a maximum split of 1:64
between the P-OLT and LTs.
(1 of 2)
2-14

Feature
Description
GPON optics
The 7342 ISAM FTTU supports a 28 dB optical budget between the P-OLT and the ONTs.
The 7342 ISAM FTTU provides an optical leveling mechanism during the operation of the
P-OLT and ONTs.
HSI
The 7342 ISAM FTTU supports PPP- or DHCP-based IP address allocation. The
7342 ISAM FTTU supports multiple VLANs and the required bridging modes, as well as
ITU-T 802.1 requirements for QoS and security.
IPTV service
The IPTV service is provided through the Ethernet connection on the ONTs. The ONTs
support a configurable IGMP snooping function. The ONT can be configured with the
maximum age for a multicast stream. The ONT UNI port can be configured with the
maximum number of multicast streams, maximum number of hosts, and maximum
number of IGMP messages allowed in a 1-s interval. Both IGMP v1 and v2 are supported.
The system response time for a zap is 100 ms. The IGMP control packets take
precedence over data packets.
NT redundancy
The NTs are used in pairs for both link aggregation and redundancy support. If an NT
card fails, the active/standby concept is used to provide continued support by the
remaining NT.
Management
The 7342 ISAM FTTU uses OMCI, SNMP, TL1, and CLI for management. The management
functions include configuration management, NE software download, performance
monitoring management, alarms and fault management, security management, and
database management. The management interfaces are provided via 5528 WAM.
Security
7342 ISAM FTTU supports SNMP version 3, SSH, and user authentication.
(2 of 2)

2-15
2-16

Application notes
3.1 Overview
3-2
3.2 Release FGU 04.04.xx application notes

3.3 Release FGU 4.3.5 application notes
3-3
3.4 Release FGU 4.3.0 application notes
3-3
3.5 Release FGU 4.2 application notes

3-2
3-4
3-1
3 Application notes
3.1
Overview
This chapter provides a brief description application notes of interest to
7342 ISAM FTTU users. These application notes were first reported in the
7342 ISAM FTTU Customer Release Notes for the FGU release.
See the 7342 ISAM FTTU ONT Product Information Manual for application notes
for ONTs.
3.2
Release FGU 04.04.xx application notes

Table 3-1 describes the application notes for 7342 ISAM FTTU FGU 04.04.xx
releases.
Table 3-1 Application notes for FGU 04.04.xx
Application note
Details
Reference
The OLTS-L only accepts the EHNT-B, AACU, GLT2-C, and

the GLT4-A for R04.04.00 and later. The OLTS-K only
accepts the EHNT-A, GLT2-C, GLT2-B, and the ACCU-C
cards.
See the 7342 ISAM FTTU

P-OLT Hardware
Installation and
Maintenance Guide
When the LANX is down or resetting in a simplex system,

the L2 forwarding tables cannot be retrieved until the NE
is back in service and the audit of LT cards is complete.
The hot reset command does not

apply to GLT2 cards.
The command INIT-SYS::LT-1-1x:::5 is not performed if

entered.

TL1 Commands and
Messages Reference
Session and marker profiles
Session and marker profile editing is not supported. The

network manager does not inhibit modification of these
profiles. Changing these profiles is service affecting.

TL1 Commands and
Messages Reference
GLT4 card editing
Editing a GLT4 card to a GLT2 card is not supported.
OAM MP support
The maximum number of MPs supported is 200.
Operator-triggered switchovers
If all four active ports are on the active NT, and all four
standby ports are on the standby NT, performing an
operator-triggered switchover may result in traffic
interruption for less than 3 s.
PQ profiles.
Changing PQ profile for any service requires configuration

of the queues on the ONT. It is advisable not to make such
fundamental changes during operation of the ONT. If such
changes are required, make sure the ONT is reinitialized
immediately for the changes to take effect.

P-OLT and ONT Operations
and Maintenance
Procedures
The outage time of the TL1 management channel

following a system reset is 15 min on a fully provisioned
system.
Hardware considerations
Equipment considerations.
Initialization
Forwarding table retrieval
Provisioning
Services
Other
Management channel
(1 of 2)
3-2

3 Application notes
Application note
Details
Reference
ACCU port.
The port does not auto-negotiate the speed to 10 Mbps.

It operates at 100 Mbps full or half duplex. Set the
terminals connected to the port to 100 Mbps.
Inhibit switchover note
Before applying inhibit switchover on a standby NT, shut

down the network port to avoid traffic loss.
(2 of 2)
3.3
Release FGU 4.3.5 application notes

Table 3-2 describes the application notes for 7342 ISAM FTTU FGU 4.3.5.
Table 3-2 Application notes for FGU 4.3.5
Application note
Details
Reference
If you use CLI to log in, then reset the system time and
date, all CLI account passwords immediately expire.

CLI Commands Guide
Static multicast streams are not

included in the PON multicast
CAC calculation.
The provisioning of a static multicast stream does not fail

due to exceeding the maximum allowed PON bandwidth.
Do not use the TSLOTMAP

parameter to increase or
decrease the number of DS0s to
carry on a CES pseudo wire
service.
Use the TSLOTMAP parameter in the ED-SERVICE-CESPW

TL1 command to rearrange DS0s.

TL1 Commands and
Messages Reference
Initialization
You must configure the network
time and date before using CLI
to log in.
Services
3.4
Release FGU 4.3.0 application notes

Table 3-3 describes the application notes for 7342 ISAM FTTU FGU 4.3.0.
Table 3-3 Application notes for FGU 4.3.0
Application note
Details
Reference
When the operational state of network-bound Ethernet

interfaces is down, changes to the interfaces
administrative state are not reported to the management
system.
Initialization
Ethernet interface state
reporting
Provisioning
(1 of 2)

3-3
3 Application notes
Application note
Details
Reference
802.1x session timeouts
Changes to the 802.1x session timeout value does not

apply to existing sessions, but does apply to subsequent
sessions. If the session timeout value is set to 0, existing
sessions do not time out. These sessions must be deleted
to force a new session to use the non-0 value.
See chapter 17.
See chapter 16
For timeout value

information, see the
7342 ISAM FTTU CLI
Commands Guide
Services
Performance monitoring
When both port- and VLAN-specific, and flow-specific

counters are enabled for the same port, only the
flow-specific counter is incrimented.
Ethernet counters on the network interface are not
initialized after 15-minute interval counter retrieval.
OAM
RMON counter restriction
The etherStatsDropEvents RMON counter on an NT

network port does not increment for packet discards
See chapter 16
(2 of 2)
3.5
Release FGU 4.2 application notes

Table 3-4 describes the application notes for 7342 ISAM FTTU FGU 4.2.
Table 3-4 Application notes for FGU 4.2
Application note
Details
Reference
The P-OLT equipment has completed UL, FCC, NEBS1,

and CE certification.
See the appropriate safety

information at the
beginning of each
7342 ISAM FTTU document
for more information.
Hardware considerations
Certification testing of
hardware
Certification of NEBS Level 3 functionality is currently

ongoing by a third-party testing facility.
Detailed test reports can be made available on request.
Thermal limitations
Thermal limitations limit the maximum number of ALTS-N

shelves on rack to two.
Use of non-Alcatel-Lucent SFPs

and XFPs
Do not use unauthorized SFPs or XFPs. Such misuse

adversely affects the P-OLT and requires operator
intervention. Authorized SFPs and XFPs are labeled with
the Alcatel-Lucent brand and approved CLEI codes.
See DLP 110 in the ETSI

7342 ISAM FTTU P-OLT
Hardware Installation and
Maintenance.
If an SFP or XFP is replaced with an authorized SFP or XFP,

run the following CLI command to synchronize the port
state:
See EHNT and pluggable

optical modules unit data
sheet for identification
tables listing the CLEI
codes for authorized SFPs
and XFPs.
configure interface shub port

<port-number> admin-status down
configure interface shub port
<port-number> admin-status up
Initialization
(1 of 3)
3-4

3 Application notes
Application note
Details
Reference
Compliance with RADIUS

protocol
FGU 4.3 is compliant with the RADIUS protocol as defined

by the RFC 2865.
See section 17.4 for more

information about RADIUS
servers.
The operation of the RADIUS implementation is

compatible with the RADIUS server available from
Juniper Networks (formerly FUNK Software Inc), and the
SteelBeltedRADIUS server version 5.03 on the UNIX
system with Solaris v2.8.
Refer to the RADIUS server manuals for details regarding
the configuration of the RADIUS server dictionary
information.
No support of concurrent SFTP
transfers
The P-OLT supports a single SFTP transfer at a time. Do

not perform concurrent transfers.
Changing NT interfaces from

manual IP to BOOTP
The NT board must be reset to activate changes when the

NT interface configuration is changed from manual IP to
BOOTP.
DLP 104 in the

Software Installation
Procedures
NT boards in a redundant system
Do not manually pull out the active NT in a redundant

system for at least 60 s after issuing a provisioning
command.
See DLP 110 in the ETSI

Hardware Installation and
Maintenance.
the SWCAP alarm is raised for the second NT card

when the system is configured in simplex NT mode
the SWCAP alarm is raised when Shub data is
provisioned, while the two NTs are synchronized;
however, the alarm will not be seen if the amount of
provisioning is minimal
to avoid excessive P-OLT loading, clear all
extraneous ONT alarms by setting inactive ONTs
out-of-service
See chapter 8
when two or more GigE links are used to connect the

P-OLT to an upstream switch, ensure
auto-negotiation is enabled on the 7342 ISAM FTTU
and the upstream switch
configure the bridge priority of the Shub greater than
32678 to ensure the upstream switch is always the
root bridge in an RSTP configuration
GigE links between a GenBand G6 and a Layer 2
switch should not be enabled for STP, RSTP, or link
aggregation
See DLP 114 in the ANSI or

ETSI version of the
Procedures.
Provisioning
Alarm application notes
GigE links and RSTP
See chapter 13
PPOoE Option 82 slot numbering
Slot numbering begins at 3 on the 7342 ISAM FTTU.
See chapter 9
Actions when maximum number

of unicast MAC addresses
reached
When the MAXMACNUM value is reached, the LT receives

messages indicating that the maximum number of unicast
MAC addresses has been exceeded for the ONT.
See the appropriate

service provisioning DLP in
the 7342 ISAM FTTU ONT
Procedures
This causes anti-spoofing mechanisms to disable the port.

The port recovers automatically when the P-OLT detects
no further messages from the additional MAC address.
Time to Live parameter for
multicast traffic
Set the TTL to greater than two for multicast traffic sent
to the P-OLT.
See DLP 109 in the

Procedures
Other
(2 of 3)

3-5
3 Application notes
Application note
Details
Reference
SanDisk and NT cards
See DLP 102 in the

Procedures
MAC filters
when replacing a defective NT due to hardware

failure, the SanDisk in the new NT should be replaced
with the SanDisk from the defective NT
reset the system when a SanDisk is replaced
When both specific and generic MAC filter counters are

enabled for the same port and VLAN, only the specific
counter is incrimented.
See chapter 12
(3 of 3)
3-6

4.1 Overview
4-2
4.2 7342 ISAM FTTU system architecture

4.3 P-OLT functional blocks
4-2
4.4 V-OLT functional blocks
4-8

4-2
4-1
4.1
Overview
This chapter provides a functional description of the 7342 intelligent services access
manager fiber to the user (7342 ISAM FTTU) P-OLT and V-OLT system
components, which are typically installed at the CO or CEV.
4.2
7342 ISAM FTTU system architecture

The 7342 ISAM FTTU provides a gigabit passive optical network (GPON)-based
access network and has three main components:
the packet optical line termination (P-OLT) unit that provides the central
switching, processing, and control functions
the video optical line termination (V-OLT) unit that provides the processing and
distribution of video services
the optical network terminal (ONT) unit that provides local switching,
processing, and control functions.
See the 7342 ISAM FTTU ONT Product Information Manual for functional
descriptions of the ONTs, which terminate services from the GPON at the
subscribers premise.
4.3
P-OLT functional blocks

The P-OLT consists of two main functional blocks:
network termination (NT)

line termination (LT)
Figures 4-1 and 4-2 shows the functional blocks of the P-OLT.
4-2

Figure 4-1 P-OLT functional blocks with an EHNT
Management/craft interface
Network interface
Network termination
Line termination
NT I/O module
ACU
NT card A
LT cards (1-16)
Software
OBC
OBC
48-GE
layer 2
switch
Software
EHNM
Local
switch
eHCL
Software
Software
OBC
48-GE
layer 2
switch
OBC
GPON
EHLM
FPGA
10-GE
XAUI
Software
GLOB
eHCL
EHNM
NT card B
18404
Figure 4-2 P-OLT functional blocks with an EXNT

Management/craft interface
Network interface
Network termination
ACU
NT I/O module
NT card A
OBC
Line termination
LT cards (1-16)
Software
OBC
Software
200-GE
layer 2
switch
Local
switch
eHCL 2
OBC
Software
OBC
200-GE
layer 2
switch
GPON
FPGA
Software
40-GE
XAUI
Software
GLOB
eHCL 2
NT card B
19498
The functional blocks are built on the platform with tiers of software applications,
including communication and management protocols, core service and management
applications, and transport applications.

4-3
Network termination
The NT functional block contains a pair of NT cards and ACU cards that provide the
following key functions:
layer 2 switching
NT redundancy
control and management
network synchronization
connections
Layer 2 switching
The NT and LT cards work together to provide the layer 2 switching function. The
NT cards provide the layer 2 virtual local area network (VLAN) bridging
management function. This function controls port mappings, including
user-to-network interface (UNI)-to-bridge port and GPON encapsulated module
(GEM) port-to-VLAN mapping. The LT cards provide layer 2 switching in either
cross-connect or residential bridge mode.
Physical UNIs that do not have a direct association with a bridge port, such as the
plain old telephone service (POTS) UNIs, are not included in the UNI-to-bridge port
mapping.
NT redundancy
The two layer 2 switches are provisioned for load sharing. Under normal
circumstances when both NT cards are operational, the on-board controller (OBC)
on the primary layer 2 switch functions as the master that controls the operation of
both switches.
Control and management
The layer 2 switch has an OBC that is dedicated to controlling the Internet protocol
(IP) routing functions. The switch is managed separately from the NT card. The
switch has its own management information base (MIB) that can be accessed directly
using simple network management protocol (SNMP) via a supported network
management system, or indirectly using transaction language 1 (TL1) or command
line interface (CLI).
The OBC on the primary NT cards controls the functioning of the entire P-OLT shelf.
The NT OBC has a fast Ethernet (FE) link that connects to the peer OBC on the layer
2 switch to synchronize the databases. The NT OBC has its own MIB that can be
accessed directly using SNMP via a supported network management system or
indirectly using TL1 or CLI. The MIB controls the applications that are related to the
P-OLT shelf.
The NT OBC determines which layer 2 switch is active or functions as the master,
based on the link failure indication from the layer 2 switch or other board fault
conditions.
4-4

Network synchronization
The 7342 ISAM FTTU system must be synchronized to a network timing reference
to support synchronization-sensitive services, such as voice, video and circuit
emulation service (CES). The system can be configured for network synchronization
using either the building integrated timing supply (BITS) interface or the IEEE
1588v2 capabilities of the EXNT network interface. Both timing configurations
support clock redundancy with redundant NT cards in the system.
The P-OLT system clock on the NT card is synchronized to the configured network
timing reference. The system clock is distributed to the LT interface, which
synchronizes the PON output clock with the timing reference. The ONTs derive the
timing for voice, video and CES traffic from the PON clock, which is traceable to the
network timing reference.
Note For P-OLTs deployed remotely from a central office (CO),
the service provider should plan to use the IEEE 1588v2 network
timing reference at the remote location to ensure proper
synchronization of the P-OLT and its ONTs.
Connections
The EHNT card uses a point-to-point Ethernet-based high capacity link (eHCL)
track on the P-OLT backplane to carry up to 2 Gb/s of unicast, multicast, and in-band
management traffic to each LT (up to 4 Gb/s from both NT cards). A 10 gigabit
Ethernet (GE) attachment unit interface (XAUI) is provided between the two NTs.
The layer 2 switch provides 48 GE ports and two 10-GE ports. The ports provide the
following functions:
Upstream or network interfaces: four 1-GE ports and one 10-GE port terminate
on the front panel to provide an interface to the Ethernet metropolitan area

network (E-MAN).
Downstream or user interfaces with two-port LT cards: a maximum of 32 ports
terminate at the back panel to provide interfaces for the LT cards. Each LT card
requires two GE ports.
Downstream or user interfaces with four-port LT cards on an OLTS-M shelf: a
maximum of 56 ports terminate at the back panel to provide interfaces for the LT
cards. Each LT card requires four GE ports.
NT redundancy connection: one 10-GE port provides an interface to the
redundant NT card for load sharing and communication associated with the
forwarding database.
NT OBC and layer 2 switch OBC connection: one GE port of the switch matrix
provides an interface between the OBC on the NT card and the OBC on the layer
2 switch.
NT I/O: four ports are available in ETSI shelves for expansion.
The EXNT card uses a point-to-point Ethernet-based extreme capacity link (XAUI)
on the P-OLT backplane to carry up to 10 Gb/s of unicast, multicast, and in-band
management traffic to each LT (up to 20 Gb/s from both NT cards). A 10 gigabit
Ethernet (GE) interface (XAUI) is provided in the shelf backplane between the two
NTs.

4-5
The layer 2 switch provides 1-GE ports and 10-GE ports. The ports provide the
following functions:
Upstream or network interfaces: two 1-GE ports and two 10-GE ports terminate
on the front panel to provide an interface to the Ethernet metropolitan area

network (E-MAN).
Downstream or user interfaces with two-port LT cards: a maximum of 28 ports
terminate at the back panel to provide interfaces for the LT cards. Each LT card
requires two GE ports.
Downstream or user interfaces with four-port LT cards on an OLTS-M shelf: a
maximum of 56 ports terminate at the back panel to provide interfaces for the LT
cards. Each LT card requires four GE ports.
NT redundancy connection: one 10-GE backplane connection provides an
interface to the redundant NT card for load sharing and communication
associated with the forwarding database.
NT OBC and layer 2 switch OBC connection: one GE port of the switch matrix
provides an interface between the OBC on the NT card and the OBC on the layer
2 switch.
NT I/O: four ports are available in ETSI shelves for expansion.
Management console
The management console provides the operations, administration, and maintenance

(OAM) functions. The management console for the P-OLT system can use a local
craft port or remote network (in-band) connection. A local management console uses
the local craft port that is located on the faceplate of the alarm control unit (ACU)
card. A remote management console uses the network connection to the NT cards.
See chapter 6 for more information.
Line termination
The P-OLT provides the LT function using the LT cards. The LT card provides the
following main functions:
interfaces to the GPON

interfaces to the NT cards
layer 2 switching
card control and management
Interfaces to GPON
Each LT card provides interfaces to the GPON. The GPON interface supports
forward error correction (FEC) and Raman reduction.
FEC data encoding provides data redundancy, which allows the LT card to detect and
correct transmission errors from the ONT, and enhances the reliability of upstream
data. Upstream FEC support is enabled or disabled using TL1 commands. For more
information about the TL1 commands, see the 7342 ISAM FTTU Operations and
Maintenance Procedures Guide using TL1 and CLI.
4-6

Occasionally, when fiber and equipment in the GPON network are shared, Raman
effect can occur where signals cross over from downstream digital signals in the
lower spectrum and cause visible lines on overlaid broadcast radio frequency (RF)
video signals. The effect is usually more prominent in the low end video channels
that are in the 1550 to 1560 nm range.
You can enable Raman crosstalk reduction for each optical GPON link on the LT
card that is installed in the P-OLT using the TL1 interface. Raman crosstalk
reduction is disabled by default. For more information about enabling or disabling
Raman crosstalk reduction, see the 7342 ISAM FTTU Operations and Maintenance
Procedures Guide using TL1 and CLI.
Interfaces to NT cards
Each LT card interconnects with the NT cards through redundant communication

links. The type of communication link is dependant upon the NT card type in the
shelf.
With the EHNT installed the eHCL link is used. An eHCL is an Ethernet
packet-based interface that provides point-to-point transmission to and from the NT
cards for network access. The eHCL links supports a throughput capacity of 4 Gb/s
in receive (Rx) and transmit (Tx) to the NT cards.
With the EXNT installed the XAUI link is used. An XAUI is an Ethernet
packet-based interface that provides point-to-point transmission to and from the NT
cards for network access. The XAUI links, on the two port LT cards, supports a
throughput capacity of 5 Gb/s in receive (Rx) and transmit (Tx) to the NT cards. The
XAUI links, on the four port LT cards, supports a throughput capacity of 20 Gb/s in
receive (Rx) and transmit (Tx) to the NT cards.
Layer 2 switching
The LT functional block provides the layer 2 switching specific to the access
environment by supporting cross-connect mode and residential bridge modes. The
LT block serves as a layer 2 switch that is independent of the NT block, which serves
as a standard bridge. Both the LT and NT learn and age independently on media
access control (MAC) addresses.
The LT block also provides multicast traffic duplication. Multicast duplication on the
LT card can increase the efficiency of the bandwidth on the eHCL links between the
NT cards and LT cards. Each PON can simultaneously support up to 2.4 Gb/s of
multicast with this approach, although the NT to LT capacity is 4 Gb/s.
The LT functional block provides the GPON management function that controls the
transport functions, such as setting up the GEM flows on the PON. The GPON
management function establishes association between slots, ports, or services and
UNIs. The LT card conveys transmission container (T-CONT) to allocation
identification (ID), port ID and priority-bit mapping and quality of service (QoS)
information to individual ONTs. T-CONTs are used to manage the upstream
bandwidth allocation in the PON section of the transmission convergence layer. The
ONTs use the T-CONTs and the dynamic bandwidth assignment to request upstream
bandwidth. T-CONT type 5 accommodates QoS. Fixed bandwidth is derived from
the sum of all provisioned bandwidth for the port IDs within the T-CONT.

4-7
Control and management
The LT OBC sends ONT management information through the OAM VLAN to the
NT cards. The information includes alarm and state change events that occur on the
ONTs supported by the LT card.
When 802.1x sessions are set up at the LT card, authentication is requested via the
NT, using input/output channel manager (IOCM) internal communication. The LT
initiates and controls the IOCM communication.
Even though the aging timer is independent on the NT and the LT card, for proper
operation, it should be configured the same. The aging timer on the LT card is
common for all line interface modules (LIMs).
4.4
V-OLT functional blocks

The 7342 ISAM FTTU uses the V-OLT to distribute video signal from service
providers across the PON to the ONTs. The V-OLT uses erbium doped fiber
amplifiers (EDFA). The distribution requires wavelength division multiplexer
(WDM) to be overlaid into the fiber path. The WDM function is provided through
the video coupler.
RF video signal distribution

The distribution of the optical video signal is described as follows:
The V-OLT receives an incoming wavelength optical signal with embedded

video channels through a fiber path from the cable TV head-end equipment.
The V-OLT amplifies and splits the optical signal into multiple optical feeds to
the video coupler.
The video coupler merges the video signal over the fiber paths.
The fiber paths carry the optical signals between the P-OLT and PON and the
ONTs that are associated with the PON.
RF video services
The V-OLT supports the full cable television (CATV) spectrum from 47 MHz to 862
MHz.
The V-OLT supports most of the CATV service options, such as video on demand
(VOD), interactive video for games, and standard or premium analog and digital
channels. Access to video services may require a set-top box (STB) between the
video output of the ONT equipment and customer premises equipment (CPE).
The 7342 ISAM FTTU provides Raman crosstalk reduction if distortion, caused by
downstream digital data signals on the GPON network, is visible on the lower
spectrum video channels. See the 7342 ISAM FTTU Operations and Maintenance
Procedures Guide using TL1 and CLI for more information about enabling and
disabling Raman reduction. See section 4.3 for a description of Raman reduction.
4-8

Upstream signal and data channels

An Ethernet connection between the set-top box and the local area network (LAN)
port is required to provide a upstream signaling channel. This channel carries service
requests through a separate virtual channel between the ONT and the P-OLT. The
upstream data channel uses one of LANs available at the ONT.
RF video service management

The V-OLT requires a separate element management system (EMS) to control video
output signals from the V-OLT equipment.
For subscribers to access video services, the ONTs can be provisioned remotely
using a supported network management system.

4-9
4-10

Equipment layout
5.1 Overview
5-2
5.2 P-OLT equipment layout
5-2
5.3 V-OLT equipment layout
5-9
5.4 Video coupler equipment layout

5.5 ONT equipment layout
5-9
5-12

5-1
5 Equipment layout
5.1
Overview
This chapter describes the layout of the 7342 ISAM FTTU physical equipment.
The 7342 ISAM FTTU system provides an access network based on the gigabit
passive optical network (GPON) technology, using the following equipment:
central office (CO) equipment:

packet optical line termination (P-OLT) equipment
video optical line termination (V-OLT) equipment (required when radio frequency
(RF) video service is supported)
video coupler (required when V-OLT is supported)
customer premises equipment: optical network terminals (ONTs)
5.2
P-OLT equipment layout

The P-OLT equipment is typically located in a CO or in a controlled environment
vault (CEV). Each P-OLT consists of one optical line termination (OLT) shelf,
mounted in an equipment rack. The OLT equipment rack contains:
top rack unit (TRU)

one or more OLT shelves
one fan unit per shelf
rack power cable
rack alarm cable
OLT rack
The OLT rack can accommodate a maximum of two P-OLT shelves and one TRU,
which distributes power and collects alarms.
The following TRUs are supported:
ATRU-M
ATRU-N
ATRU-U
GTRU-B
Figure 5-1 shows a P-OLT (ALTS-N) and ATRU-M installed in an equipment rack.
Figure 5-2 shows two P-OLT shelves (OLTS-M) and ATRU-U installed in an
equipment rack.
5-2

5 Equipment layout
Figure 5-1 Rack mounted ATRU-M and P-OLT (ALTS-N) with cover attached
ATRU-M
IR
C
JA
M
NI
M
EG SU
F
UR ATL
TA OV
-R
W
P
1R
S
2R
S
RB
TS
LB
ET
RA
SAU
01
02
02
LA
03
A1/4
A
A2L
SAU
/30A
01
A2R
/30A
02
A3/4
A
02
03
A1/4
A
A2L
/30A
A2R
/30A
A3/4
A
P-OLT with
cover installed
18834

5-3
5 Equipment layout
Figure 5-2 Rack mounted ATRU-U and P-OLT (OLTS-M)
SAU
01
02
FAN1
FAN2
CB\A
A01/35
A02/35
A04/6
AO5/6
SAU
01
02
FAN1
FAN2
CB\B
B01/35
B02/35
B04/6
BO5/6
CRI
MAJ
MIN
FUS
VOLTAGE
PWR-ATRU
UNUSED
ESD
PWRB1
PWRB2
ARTH
UNUSED
TEST
BON
INT
PWRB2
PWRB1
IN G P
FAN UNIT STATUS
BLINKING
GREEN - INITIALIZING
SOLID
GREEN - ACTIVE
RED
- FAN FAILURE
AMBER - OVER TEMPERATURE
FAN UNIT STATUS

BLINKING
GREEN - INITIALIZING
SOLID
GREEN - ACTIVE
RED
- FAN FAILURE
AMBER - OVER TEMPERATURE
19345
OLT ALTS-N shelf

The ALTS-N optical line termination (OLT) shelf is the frame in which the cards and
other units that comprise the P-OLT are installed. The shelf is mounted in a rack.
Figure 5-3 shows a P-OLT (ALTS-N).
5-4

5 Equipment layout
Figure 5-3 OLT shelf with cards, fan tray, and fiber routing tray installed
Energy Hazard
AACU-C
CRI
MAJ
MIN
ALM
ACO
EHNT
EHNT
ALM PWR ACT
ALM PWR ACT
ALM
ALM PWR ACT
ACT
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
PWR
PWR
PWR
PWR
PWR
PWR
PWR
PWR
PWR
PWR
PWR
PWR
PWR
PWR
PWR
PWR
ALM
ALM
ALM
ALM
ALM
ALM
ALM
ALM
ALM
ALM
ALM
ALM
ALM
ALM
ALM
ALM
CRAFT
ETHERNET
623.75 mm
247.2 mm
284.5 mm
497.4 mm
515 mm
529.4 mm
18835
The ALTS-N shelf has three main areas:
cable routing and shelf connector area

card cage
fan tray
The card cage is the large central area of the shelf that accommodates plug-in cards,
including, from left to right, 1 ACU slot, 2 NT slots (NTA and NTB), and 16 LT
slots. Blank filler plates are installed in any empty slots in the card cage area. The
MAC address for the shelf is located on a label that is affixed on the left side of the
shelf, beside the ACU slot.
The topmost area of the shelf is the cable routing and shelf connector area, and a fan
unit is installed in the horizontal fan tray area along the bottom of the shelf.
The top rack unit (TRU) is a separate unit located above the shelf in the equipment
rack that distributes power and telco alarms to the shelf. The shelf distributes the
power to the fan unit and other components via the shelf backplane. A circuit breaker
for the fan unit is located in the TRU. As well, a GMT fuse in the TRU protects the
fan units power circuit.

5-5
5 Equipment layout
Individual fans in the fan unit have a non-field replaceable fuse to protect a short in
one fan from causing all fans to fail. If a single fan fails, the other fans automatically
compensate by adjusting their speed so that the proper air flow is maintained. Fan
speed also automatically adjusts according to the ambient temperature to save power
and minimize acoustic noise.
P-OLT OLTS-M shelf

The OLTS-M optical line termination (OLT) shelf is the frame in which the cards
and other units that comprise the P-OLT are installed. The shelf is mounted in a rack.
Figure 5-4 shows a P-OLT (OLTS-M).
Figure 5-4 OLTS-M shelf with cards installed
19.0158
18.3110
17.2334
11.1181
GLT4-A
EHNT-B
2
3
2
3
2
3
2
3
PON SF
PON SF
PON SF
PON SF
PON SF
PON SF
ALM
PON SF
PWR
ALM
PON SF
PWR
ALM
PON SF
PWR
ALM
GE-2
GE-3
GE-4
10G
CRI
MAJ
MIN
ALM
ACO
10G
DANGER
DANGER
DANGER
DANGER
DANGER
DANGER
GLT4-A
GLT4-A
GLT4-A
GLT4-A
PWR
PWR
PWR
PWR
PWR
ALM
ALM
ALM
ALM
ALM
2
3
2
3
2
3
2
3
2
3
O&M
Tx
Tx
Rx
Rx
GE-1
DANGER
DANGER
DANGER
DANGER
DANGER
DANGER
PON1
PON3
PON3
PON3
PON3
PON3
PON4
PON4
PON4
PON4
PON4
PON2
PON3
PON4
PON2
PON3
PON4
PON2
PON2
CRAFT
PON2
PON3
PON4
PON2
PON3
PON4
PON2
PON3
PON4
PON2
PON3
PON4
PON2
PON3
10G
PON4
GE-4
10G
PON3
GE-4
PON3
PON2
GE-3
PON4
PON2
GE-2
PON4
PON2
GE-3
PON2
GE-2
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
ETHERNET
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON2
24.4646
DANGER
GE-2
GE-4
GE-1
DANGER
ALM PWR ACT
LNK TX RX
GE-1
GE-3
O&M
GLT4-A
EHNT-B
AACU-C
ALM PWR ACT
LNK TX RX
GE-1
PON SF
GLT4-A
PWR
ALM
PON SF
GLT4-A
PWR
ALM
PON SF
GLT4-A
PWR
ALM
PON SF
GLT4-A
PWR
ALM
PON SF
GLT4-A
PWR
ALM
UNIT
GLT4-A
PWR
NETWORK
GLT4-A
BAT B
UNIT
GLT4-A
BAT A
NETWORK
BATRET
19321
The OLTS-M shelf has three main areas:
shelf power and connector area

card cage
cable routing tray
5-6

5 Equipment layout
The card cage is the large central area of the shelf that accommodates plug-in cards,
including, from left to right, 9 LT slots (LT1 through LT9), 1 NT slot (NTA), 1 ACU
slot, 1 NT slot (NTB), and 5 LT slots (LT10 through LT14). Blank filler plates are
installed in any empty slots in the card cage area. The MAC address for the shelf is
located on a label that is affixed on the left side of the shelf, beside the LT1 slot.
The topmost area of the shelf is the power and connector area. Redundant -48 V dc
power feeds from the TRU supply the shelf with power. The BITS-B card is mounted
here and provides RJ-45 connectors for the BITS interface (primary and secondary)
and the LAN interface (out of band management). A DB-9 connector for the Craft 2
Interface, the Fan Alarm connector and a 50 pin D connector for the ACU alarm
cable is located in this area.
The top rack unit (ATRU-U or GTRU-B) is a separate unit installed at the top of the
equipment rack that distributes power and telco alarms to the shelf. The shelf
distributes the power to shelf components via the shelf backplane.
A separate fan unit (AFAN-S) is located below the OLT shelf and provides forced
air cooling to the shelf components. If a single fan fails, the other fans automatically
compensate by adjusting their speed so that the proper air flow is maintained. Fan
speed also automatically adjusts according to the ambient temperature to save power
and minimize acoustic noise.
OLT shelf backplane

The backplane of the OLT shelf is a printed circuit board that provides connectivity
between the units used in the shelf. The backplane is preinstalled and is not field
replaceable.
The backplane provides two types of buses: the IQ buses and the HCL buses. The IQ
buses are used for timing distribution. The HCL buses are used for the eHCL signals
for all the data and control traffic.
For more information, see the 7342 ISAM FTTU Hardware Installation and
Maintenance Practices.
Cards in the OLT shelf

The OLT shelf contains NT, LT, and ACU cards.
NT cards
The NT cards support the layer 2 switching function and management function for
the P-OLT shelf where both the NT and LT cards reside. The P-OLT can be
configured to have a primary and secondary NT card for load sharing: NT card A and
NT card B.
The 7342 ISAM FTTU system supports two NT card types, which provide GE
optical connectivity to a high-bandwidth IP services network and support either
Ethernet high-capacity links (eHCL) or XAUI links to LT cards, dependant on NT
card type:
EHNT-A and EHNT-B

EXNT-A

5-7
5 Equipment layout
For details on each NT card type, see the appropriate unit data sheets.
Optical modules
Table 5-1 provides information about the supported 1 GE and 10 GE pluggable

modules for the NT cards.
Table 5-1 Optical modules
Module Type
Rate
Wavelength (nm)
Reach
SFP
1 GE
Electrical
100 m
850
550 m
1310
10 km
1310
40 km
1550
80 km
Electrical
300 m
850
10k m
1310
40 km
1550
80 km
XFP
10 GE
The NT cards are not shipped with the optical modules installed. The optical modules
are orderable items. See 7342 ISAM FTTU P-OLT Planning and Ordering Guide for
ordering information.
LT cards
The LT card provides connection between the NT card and the ONT at the customer
premises.
For the connection to the ONTs, the LT card provides GPON interfaces. Each
GPON interface can support 32 or 64 ONTs, dependant on LT card type.
For the connection to the NTs, the LT card provides either eHCL or XAUI
interfaces to the NTs, dependant on NT card type.
For the connection to EHNT card types, the LT provides redundant eHCL busses.
The eHCL connections support a maximum of 4 Gb/s bidirectional bandwidth.
For the connection to EXNT card types, the LT provides redundant XAUI busses.
The XAUI connections support a maximum of 10 Gb/s bidirectional bandwidth.
The optical implementation of the GPON can be optimized for different performance
and reach levels. The GLT2 card has two versions: GLT2-A and GLT2-B. The
GLT2-B version has increased size for both the GPON interface and the eHCLs to
support functions such as forward error correction (FEC). The GLT2-B also supports
the multicast duplication.
For details on each LT card type, see the appropriate unit data sheet.
5-8

5 Equipment layout
ACU card
The ACU card performs alarm control function for each shelf. The ACU card
provides alarm indication for CO alarms, telemetry alarms, and rack-level alarms.
The alarm indication are visual as well as audible.
The ACU card provides two RS-232 local craft ports and two Ethernet ports for
operations and maintenance activities. One craft port and one Ethernet port are
located at the ACU front panel. The other craft port and Ethernet port are located on
the backplane of the OLT shelf.
SANC-D unit
The SANC-D unit provides the building integrated timing supply (BITS) and local
network connection function for the ALTS-N shelf. In an NT card, the system clock
can be locked on one pair of BITS signals. The SANC-D unit receives two pairs of
BITS input signals through the front panel. These signals are routed through the
backplane to the associated NT unit. The primary NT unit received primary BITS
and the secondary NT unit receives secondary BITS.
BITS-B unit
The BITS-B card is mounted on the OLTS-M backplane at J67 and provides an
RJ-45 connector to connect the primary (PRI) BITS and secondary (SEC) BITS
timing references to the NT cards. A second RJ-45 connector on the cards provides
a 10/100 Mbps Ethernet interface.
The BITS-B card provides protection and attenuation for the BITS signals and also
provides termination for unused Ethernet signals.
FILT-A installation kit or FILT-B
The FILT-A installation kit is installed on the ALTS-N shelf and provides power
filtering. The power filtering is for the 48 V dc that is fed from the TRU. The
FILT-B comes pre-installed in the OLTS-M shelf.
5.3
V-OLT equipment layout

The V-OLT equipment is supplied by Scientific Atlanta. See documentation
provided by the supplier for more information.
5.4
Video coupler equipment layout

The video coupler equipment consists of a video coupler fiber rack, video coupler
shelves (VCSs), and video coupler WDM trays for 4 PONs (VCW4) or video coupler
WDM trays with splitters for 8 PONs (VCS8).

5-9
5 Equipment layout
Video coupler fiber rack

The video coupler fiber rack is provided by Tyco. The rack can hold a maximum of
15 video coupler subracks, including one subrack for sparing. For more information
about the rack, refer to related Tyco documentation.
Video coupler shelf

The video coupler shelf is provided by Tyco or LGX. The shelf can hold a maximum
of three VCW4 trays. The subrack also provides cable routing management from the
VCW4 trays to the sides of the subrack.
Video coupler WDM tray

There are the following types of video coupler trays:
VCW4
VCS8
VCSL
VCW2
The VCW4 is provided by Tyco. The VCW4 tray is provided in pairs of left and right
trays. Each tray supports 4 PONs. A pair of trays supports 8 PONs. A video coupler
system using VCW4 trays requires a separate splitter rack to hold the splitters.
The VCS8 is provided by Tyco. The VCS8 tray is provided in pairs of left and right
trays. Each tray support 8 PONs. A pair of trays supports 16 PONs. The VCS8 tray
integrates the splitter into the tray and eliminates the need for a splitter rack.
The VCSL and VCW2 are provided by LGX.
Figure 5-5 shows the Tyco video coupler rack loaded with 14 shelves.
5-10

5 Equipment layout
Figure 5-5 Tyco video coupler fiber rack

5-11
5 Equipment layout
5.5
ONT equipment layout

In the 7342 ISAM FTTU system, multiple ONTs connect to LT units installed in the
P-OLT shelf over the GPON network. The ONT installs at the subscribers premises
and the P-OLT installs at the CO or CEV. ONT units provide a single entry point for
services at the subscribers premises. ONTs can provide multiple services to
single-family residences, small office, home office, and business users.
Note The maximum number of ONT units that can be connected
to the PON is determined by the bandwidth utilization of each ONT
and the types of ONT units that are connected.
See the 7342 ISAM FTTU ONT Product Information Manual for more information
about ONT units, including the equipment layout.
ONT connection capacity

See the deployment planning chapter of the 7342 ISAM FTTU ONT Product
Information Manual for more information.
5-12

Operations, administration, and

maintenance
6.1 Overview
6-2
6.2 Management interfaces

6.3 EMS functions
6-2
6-6
6.4 Operations, administration and maintenance

6.5 Troubleshooting
6-7
6-8
6.6 OSMINE certification
6-8

6-1
6.1
Overview
This chapter provides information about the OAM functions of the
7342 ISAM FTTU.
The 7342 ISAM FTTU system is operated, administered, and maintained through an
interface provided by an element management system or by manually manipulating
the hardware components.
The operations and maintenance procedures you can perform with the
7342 ISAM FTTU system are documented in the 7342 ISAM FTTU Operations and
Maintenance Procedures Guide using TL1 and CLI.
6.2
Management interfaces
A management interface allows the performance of management activities, such as
configuration, provisioning, alarm monitoring, and troubleshooting. The
7342 ISAM FTTU supports the following management interfaces for local and
remote management:
the craft port or the Ethernet port on the AACU card for a locally connected craft
terminal; see Figure 6-1
the craft 2 port on the P-OLT backplane for a remotely connected craft terminal,
as shown in Figures 6-2 and 6-3
the Ethernet port on the P-OLT backplane for out-of-band connectivity to a
remotely connected craft terminal via a network management system through an
IP network
a gigabit Ethernet (GE) port on the NT card for in-band connectivity to a remotely
connected craft terminal via a network management system through the IP
network
Figure 6-1 AACU-C craft and Ethernet connections
ETHERNET
CRI
MAJ
MIN
ALM
ACO
CRAFT
AACU-C
Craft terminal
port
Ethernet port
18911
6-2


Figure 6-2 ALTS-N backplane craft and Ethernet connections
Remote Craft Port
(RCFT)
Lan connector
Energy Hazard
AACU-C
EHNT
EHNT
ALM PWR ACT
ALM PWR ACT
ALM
ALM PWR ACT
ACT
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
PWR
PWR
PWR
PWR
PWR
PWR
PWR
PWR
PWR
PWR
PWR
PWR
PWR
PWR
PWR
PWR
ALM
ALM
ALM
ALM
ALM
ALM
ALM
ALM
ALM
ALM
ALM
ALM
ALM
ALM
ALM
ALM
Local Craft
Interface
CRAFT
ETHERNET
CRI
MAJ
MIN
ALM
ACO
19680

6-3

Figure 6-3 OLTS-M backplane craft and Ethernet connections
Lan connector
BATRET
BAT A
BAT B
Craft 2
Interface
EHNT-B
2
3
PON SF
PON SF
PON SF
PON SF
PON SF
PON SF
PON SF
PON SF
ALM
PON SF
PWR
ALM
GE-2
GE-3
GE-4
10G
CRI
MAJ
MIN
ALM
ACO
10G
DANGER
DANGER
DANGER
DANGER
DANGER
DANGER
GLT4-A
GLT4-A
GLT4-A
PWR
PWR
PWR
PWR
ALM
ALM
ALM
ALM
ALM
2
3
2
3
2
3
2
3
2
3
O&M
Tx
Tx
Rx
Rx
GE-1
DANGER
DANGER
DANGER
DANGER
DANGER
DANGER
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON3
PON3
PON3
PON3
PON4
PON4
PON4
PON4
PON2
PON3
PON4
PON2
PON3
PON4
PON2
PON2
CRAFT
PON2
PON3
PON4
PON2
PON3
PON4
PON2
PON3
PON4
PON2
PON3
PON4
PON2
PON3
PON4
PON2
PON3
PON4
10G
PON3
GE-4
10G
PON3
GE-4
PON4
PON2
GE-3
PON4
PON2
GE-2
PON2
GE-2
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
ETHERNET
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
GE-3
PON2
GLT4-A
PWR
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
PON1
DANGER
GE-2
GE-4
GE-1
DANGER
ALM PWR ACT
LNK TX RX
GE-1
GE-3
O&M
GLT4-A
EHNT-B
AACU-C
ALM PWR ACT
LNK TX RX
GE-1
PON SF
GLT4-A
PWR
ALM
PON SF
GLT4-A
PWR
ALM
PON SF
GLT4-A
PWR
ALM
PON SF
GLT4-A
PWR
ALM
PON SF
GLT4-A
PWR
ALM
UNIT
GLT4-A
PWR
ALM
NETWORK
GLT4-A
PWR
ALM
UNIT
GLT4-A
PWR
NETWORK
GLT4-A
Local Craft
Interface
19679
Craft terminal
Management tasks for the 7342 ISAM FTTU can be performed using the CLI and
TL1 commands through local or remote connections to the craft terminal. The
P-OLT provides two craft interface options.
A craft interface is located on the AACU card in the shelf; see Figure 6-1. The craft
interface is an RS-232 interface with a DB-9 connector. The terminal end of the cable
can use either a DB-9 or DB-25 connector depending on the type of craft terminal
used. The craft interface on the AACU card is typically used for local access.
A remote craft interface is located in the connector area of the P-OLT shelf. This is
a DB-9 connector which is labeled RCFT (remote craft) on the ALTS-N shelf and is
labeled CRAFT 2 INTERFACE on the OLTS-M shelf. The other end of the cable
can use a DB-9 or DB-25 connector depending on the type of craft terminal, or
modem used. The craft 2 interface is typically connected to a modem that can be
remotely accessed.
Maintenance Practices and the 7342 ISAM FTTU Operations and Maintenance
6-4

TL1 and CLI access protocol options

The 7342 ISAM FTTU supports the following TL1 and CLI access protocol options:
CLI via Telnet and SSH

TL1 via Telnet, SSH, and UDP
Note 1 The TL1 via Telnet option uses a non standard port. Contact
your local support representative to obtain the port number.

Note 2 For information on enabling or disabling protocol access
for CLI or TL1, see the DLP for configuring SSH in the
7342 ISAM FTTU Operations and Maintenance Procedures Guide
using TL1 and CLI.
Ethernet ports on the AACU and the P-OLT backplane

The P-OLT provides two Ethernet ports that can be used for management tasks. One
Ethernet port is on the AACU and the other is on the P-OLT backplane. They can be
used as an Ethernet craft port or for out-of-band IP network connectivity to an EMS.
Only one Ethernet port can be used at a time.
The Ethernet port can be configured in the following ways:
as a craft terminal when the inband management channel is through the GE ports
on the NT card
for out-of-band management when the GE ports are used for data traffic only
not used
Maintenance Practices and the 7342 ISAM FTTU Operations and Maintenance
5520 AMS connection options

Management tasks for the 7342 ISAM FTTU can be performed through the GUI
provided by the 5520 AMS. The 5520 AMS is remotely connected to the
7342 ISAM FTTU system through network connectivity to the GE ports on the NT,
or to the Ethernet port on the P-OLT backplane.
For more information, see the 5520 AMS operations and maintenance guide.
5528 WAM connection options

Management tasks for the 7342 ISAM FTTU can be performed through the
web-based 5528 WAM. Operating personnel can log in to the 5528 WAM through a
web browser to perform management tasks. The 5528 WAM is remotely connected
to the 7342 ISAM FTTU system through network connectivity to the GE ports on the
NT, or to the Ethernet port on the AACU or the P-OLT backplane.
The 5528 WAM supports Microsoft Internet Explorer and Mozilla Firefox.

6-5
6.3
EMS functions
The 7342 ISAM FTTU provides element management system (EMS) functions
through the following network management systems.
5520 AMS
The 5520 AMS is an element manager that delivers a complete management solution
for the 7342 ISAM FTTU platform.
The 5520 AMS supports the following management functions:
configuration and productivity management, such as provisioning, software
download for network element equipment, backup and restore, and management
operations
performance monitoring management, such as history data collection, storage,
and retrieval for the line units
alarms and fault management, such as surveillance, notification control, and
alarm history for network elements
security manager for network element access control, network management
system security control, and management privilege control
database management, such as system data, software version, and database
backup
GUI with high-level system, equipment, and table views
advanced management for inventory, large-scale release updates, and
service-oriented troubleshooting
advanced OSS integration capabilities
scalability up to one million lines and 100 operator positions
The 5520 AMS allows the 7342 ISAM FTTU components that are far from the CO
to be managed from one location. After the component is installed, the 5520 AMS
remote functionality allows all of the local functionality to be accessible remotely.
5528 WAM
The 5528 WAM is a PC- and Solaris-based management tool for configuring,
maintaining, and troubleshooting the 7342 ISAM FTTU. Operating personnel can
use a web browser. Supported web browsers include Microsoft Internet Explorer and
Mozilla Firefox.
The 5528 WAM is suited to small networks. It can also provide a supplemental
maintenance and troubleshooting capability for major networks. It increases the
number of user sessions available to operators and enables local central office
operating personnel to turn up initial hardware and to provide on-site hardware
maintenance.
The 5528 WAM uses web-based open architecture that is highly scalable. It provides
a graphical equipment view, CLI, and TL1 access.
6-6

The 5528 WAM management system supports the following general management
functions:
6.4
full element management operation

element drilling and quick graphical view
network alarm monitoring and statistics
equipment software management
full equipment data collection (configuration, alarm, performance management,
operational state, inventory) with scheduling and data export in formats similar to
SVC and TL1
migration support
element pre-provisioning operation
non-service affecting plug-n-play customization user operation
scalable element management domain
network operation partitioning
skill-based user security control
network element searching engine
provisioning script generation and execution
management task scheduling
graphical local or remote craft direct access
enhanced craft with NE turn-up wizard
network database backup
field deployment and troubleshooting tool
complete TL1/CLI interface support with cut-through window and command
template
programmable TL1/CLI scripting environment with execution flow control
Operations, administration and maintenance

You can perform operation, administration, and maintenance tasks for the
7342 ISAM FTTU.
Hardware operation, administration, and maintenance tasks

Hardware operation, administration, and maintenance tasks for the
7342 ISAM FTTU include:
powering up 7342 ISAM FTTU

responding to LED indications
replacing or adding cards
troubleshooting physical symptoms
For more information about hardware operation, administration, and maintenance

tasks, see the 7342 ISAM FTTU Hardware Installation and Maintenance Practices.

6-7
ONT repair and return information

Repair and return information that is stored in volatile RAM at the ONT can be
retrieved from FLASH memory using an EMS management session with the P-OLT.
A push button on the ONT can also be used to collect the latest information. Once
initiated, the ONT information that is stored in RAM is saved to FLASH memory,
from which the information can be retrieved for viewing using the 5528 WAM.
6.5
Troubleshooting
The 7342 ISAM FTTU provides methods to collect information for troubleshooting,
including:
local and remote CES loopbacks

optical power level monitoring
ping support on the GPON
remote monitoring (RMON) Ethernet statistics
statistics reports and performance monitoring counters
system-generated alarms
VoIP call statistics collection
See chapter 10 for more information about troubleshooting and fault isolation.
6.6
OSMINE certification
The 7342 ISAM FTTU is certified for operations systems modification for the
integration of network elements (OSMINE).
6-8

7.1 Overview
7-2
7.2 P-OLT equipment
7-2
7.3 Video coupler equipment
7-3
7.4 System and service capacity specifications

7.5 GPON optical and RF line rates
7.6 P-OLT optical budgets
7-8
7-8
7.7 Video coupler optical budget
7-9
7.8 Environmental requirements
7-9
7.9 Power specifications
7-4
7-9

7-1
7.1
Overview
This chapter provides information about the technical specifications for the central
office equipment, including the packet optical line termination (P-OLT) and the
video coupler equipment.
Note The video optical line termination (V-OLT) equipment is an
erdium-doped fiber amplifier (EDFA). For information about the
V-OLT equipment, see the EDFA customer documentation.
7.2
P-OLT equipment
Table 7-1 provides information about the P-OLT components.
Table 7-1 P-OLT components
Component
Mnemonic
Description
Shelf
ALTS-N
A standard shelf with an integrated fan unit
OLTS-M
XAUI shelf without fan unit
Fan Unit
AFAN-S
Variable speed, redundant fans for OLTS-M shelf

cooling
Network termination
(NT) cards
EHNT-A
48 Gb/s NT card
EHNT-B
48 Gb/s NT card (OLTS-M only)
EXNT-A
200 Gb/s NT card (OLTS-M only)
1-GE SFP
1-GE pluggable optical module for the NT card
1-GE SFP electrical
1-GE pluggable electrical module for the NT

card
10-GE XFP
10-GE pluggable optical module for the NT card
Line termination (LT)

cards
GLT2-A, GLT2-B
GPON LT with two GPON interfaces
GLT4-x
GPON LT with four GPON interfaces
ATRU-M
Top rack unit, version M, version N, or version U
TRU
ATRU-N
ATRU-U
GTRU-B
Alarm control unit
AACU-C
Alarm control unit, version C
Table 7-2 lists the field-installable or field-replaceable units and the quantity
supported for the P-OLT.
7-2

Table 7-2 Installable and field-replaceable cards
Cards
Quantity
Alarm control unit
Fan unit
NT unit
LT unit with two GPON interfaces
16 for ALTS-N
LT unit with four GPON interfaces
14 for OLTS-M
Filler plate
As required
Note Filler plates must be installed in all unused NT or LT slots.

For information about ordering a filler plate, see the
7342 ISAM FTTU P-OLT Planning and Ordering Guide.
Table 7-3 lists the weight specifications of the P-OLT units.

Table 7-3 P-OLT unit weight specifications
7.3
Unit
Weight
AACU-C
1.5 lb (0.68 kg)
AFAN-H
11.02 - 12.35 lb (5 - 5.6 kg)
AFAN-S
11.0 lb (5.0 kg)
ATRU-M
13.23 lb (6 kg)
ATRU-N
12.35 lb (5.6 kg)
ATRU-U
13.23 lb (6 kg)
GTRU-B
13.23 lb (6 kg)
NT
3.5 lb (1.59 kg)
GLT2
2.0 lb (0.91 kg)
GLT4
2.5 lb (1.13 kg)
ALTS-N
62.61 lb (28.4 kg)
OLTS-M
37 lb (16.8 kg)
Rack
340 - 379 lb (154-172 kg)
Video coupler equipment

Table 7-4 describes the components of the video coupler equipment.

7-3
Table 7-4 Video coupler equipment
7.4
Component
Mnemonic
Description
Rack
Rack for video coupler
Shelf
VCS
Video coupler shelf
Video coupler
VCW4-A
Video coupler WDM tray supporting 4 PONs (VCW4)
Video coupler
with splitters
VCS8-A
Video coupler WDM tray with splitters supporting 8 PONs

(VCW8)
System and service capacity specifications

This section provides information about the 7342 ISAM FTTU services and system
capacity specifications.
Service and system capacity

Table 7-5 lists the service and system capacity of the P-OLT.
Table 7-5 Service and system capacity
Description
Maximum
Notes
VLANs per system
4094
VLAN ID 1 to 4094. 4095 is reserved by standard.
residential bridge or
cross-connect VLANs per system
4089
VLAN IDs 1 and 4094 are reserved.
Maximum CVLANs per LT card
256 for
GLT2-x
Three other VLANs ID are required by the system for internal use.
System limit is the maximum number of CVLANs per LT card multiplied
by the number of LT slots on the OLT shelf.
512 for
GLT4-x
Static media access control
(MAC) addresses per VLAN
16 000
Dynamic MAC addresses per

VLAN
16 000
MAC addresses per VLAN
16 000
Static and dynamic MAC addresses combined. All subscribers must be in

the same VLAN.
MAC addresses per system
16 000
This number combines static and dynamic MAC addresses.
MAC addresses that can be

learned per PON (GLT2-A) based
on the number of PQ profiles
Varies
Depending on the number of priority queues mapped:
8
7
6
5
4
3
2
1
p-bits = 256
p-bits = 293
p-bits = 341
p-bits = 410
p-bits = 512
p-bits = 683
p-bits = 1024
p-bit = 1024
(1 of 4)
7-4

Description
Maximum
Notes
MAC addresses that can be

learned per pairs of PONs
(GLT2-B, GLT2-C, GLT4-x)
based on the number of PQ
profiles
Varies
MAC addresses per GLT2
2304
MAC addresses per GLT4
4608
MAC address that can be

learned per single UNI Ethernet
port
2048
Address resolution protocol

(ARP) entries per system
16 000
This number combines static and dynamic MAC addresses.
ARP entries per GLT2
2304
Same as maximum MAC entries.
ARP entries per GLT4
4608
Same as maximum MAC entries.
802.1x sessions per GLT2
256
802.1x sessions per GLT4
512
802.1x sessions per system
4096 or 3584
ALTS-N is 4096= 256 x 16, OLTS-M is 3584= 256 x 14
802.1x simultaneous setup per

LT
32
802.1x simultaneous setup per

system
100
POTS lines per PON
192
VoIP clients per PON
64
One VoIP client per ONU = 64 VoIP clients per PON.
Services per GLT2
880
Services per GLT4
1760
Maximum Ethernet frame size

(GLT4-x)
2000 byte
The exception is the GLT2-A, which supports an 1800 byte maximum

Ethernet frame size.
User-to-network interfaces per

EHNT card
240
User-to-network interfaces per

EXNT card
288
GEM ports per PON
800 or 864
The limit of 800 GEM ports is for Release 04.05.xx and earlier. The limit
of 864 Gemports is for Release 04.06.00 and later.
8
7
6
5
4
3
2
1
p-bits = 512
p-bits = 585
p-bits = 683
p-bits = 819
p-bits = 1024
p-bits = 1365
p-bits = 2048
p-bit = 4096
Each queue in a PQ profile uses a GEM port. For example, when the limit
is 800, if you create PQ profiles that use 8 queues per service, then only
100 services using those profiles can be created on that PON.
Further, there is a limit of 22 GEM ports per ONT. Three of those GEM
ports are reserved and cannot be used for priority queues. For example,
if there are 2 HSI services on an ONT UNI with 8 priority queues defined
per service, then those 16 priority queues use 16 GEM ports. Another
service using another 8 priority queues cannot be created, as that
would exceed the maximum allowed number of GEM ports.
(2 of 4)

7-5
Description
Maximum
T-CONTs per PON
440
Notes
440 = 512 total T-CONTs - 64 used for OMCI - 8 reserved.
In configurations using the maximum number of services per PON,
upstream packet loss may occur when DT values less than three are
used for all services.
More than one service per T-CONT is possible in FLEX mode
Maximum bridge ports per

residential bridge
See Notes
The maximum number of bridge ports is determined by LT card type,

NT card type, and ONT type.
For GLT2-x cards, 576 or 480 bridge ports per residential bridge:
8.064 on an OLTS-M using EXNT-A NTs with 14 LT cards (576 per LT)
6,720 on an OLTS-M using EXNT-A NTs with 14 LT cards (480 per LT)
For GLT4-x cards, 1152 or 960 bridge ports per residential bridge:
Maximum bridge ports per

system
See Notes
16,128 on an OLTS-M using EXNT-A NTs with 14 LT cards (1152 per

LT)
13,440 on an OLTS-M using EXNT-A NTs with 14 LT cards (960 per LT)

The total bridge ports per system is the number per residential bridge
plus 32 more reserved bridgeports.
Maximum bridge ports per LT

card
See Notes

For GLT2-x and EXNT-x systems, the limit is 576 bridgeports (288 UNIs
per PON x 2 PONs)
For GLT2-x and EHNT-x systems, the limit is 480 bridgeports (240 UNIs
per PON x 2 PONs)
For GLT4-x and EXNT-x systems, the limit is 1152 bridgeports (288 UNIs
per PON x 4 PONs)
For GLT4-x and EHNT-x systems, the limit is 960 bridgeports (240 UNIs
per PON x 4 PONs)
Maximum service flows per LT

card
See Notes
The maximum number of service flow is determined by LT card type and

NT card type.
For GLT2-x and EXNT-x systems, the limit is 1728 flows
For GLT2-x and EHNT-x systems, the limit is 1440 flows
For GLT4-x and EXNT-x systems, the limit is 3456 flows
For GLT4-x and EHNT-x systems, the limit is 2880 flows
Maximum service flows per

system
See Notes
The maximum number of service flow is determined by LT card NT card

type and number of LT slots.
For GLT4-x and EXNT-x systems, the limit is 48,384 flows (3456 flows
per LT x 14 slots).
For GLT4-x and EHNT-x systems, the limit is 40,320 flows (2880 flows
per LT x 18 slots).
Maximum service portals per LT

PON
880 for
GLT2-x
1760 per
GLT4-x
Maximum service portals per
system
24640
Services per system GLT2
14 080
ALTS-N is 14 080 = 880 x 16
Services per system GLT4
24 640
OLTS-M is 24 640 = 1760 x 14
(3 of 4)
7-6

Description
Maximum
Notes
VDSL2 subscribers per PON
ports x
ONTs/MDUs
per PON
Depends on the ONT/MDU.
ports x
ONTs/MDUs
per PON x
number of
PONs on a
GLT4
Depends on the ONT/MDU.
IGMP signaling channels per

PON
288

GLT2
576

GLT4
1152
VDSL2 subscribers per PON per

GLT4
For example, O-00240V-A MDU supports 24 ports.

VDSL2 subscribers per PON would be 24 ports x 12 MDUs per PON = 288
VDSL2 ports per PON.
For example, O-00240V-A MDU supports 24 ports.
VDSL2 subscribers per GLT4 would be 24 ports x 12 MDUs per PON x 4
PONs per GLT4 = 1152 VDSL2 ports per GLT4.
(4 of 4)
P-OLT performance and distance

The P-OLT provides performance and distance capacity of 2.488 Gb/s downstream
and 1.244 Gb/s upstream, within a 18.6 mile (30 km) span, for all GLT cards. The
optical link budget is defined by both loss and bandwidth characteristics. The loss
characteristic is determined by the difference between the optical transmitter and
optical receiver for each direction, and is typically 28 dB. The bandwidth
characteristic is determined by the maximum link distance parameter of each OLT
and ONT transmitter specification, and is limited by the smaller of the upstream and
downstream values.
PON bandwidth
The number of optical network terminals (ONTs) on the PON affects the bandwidth
available to each subscriber. See the 7342 ISAM FTTU ONT Product Information
Manual deployment planning chapter for more information.
P-OLT connection capacities

The P-OLT can accommodate a maximum of 16 on the ALTS-N or 14 on the
OLTS-M LT units. Each LT unit provides two or four ports. Only four port LT cards
are supported on the OLTS-M.
Video coupler connection capacity

The video coupler rack can accommodate a maximum of 15 video coupler shelves,
including a spare video coupler. Each shelf can hold a maximum of three pairs of
video coupler trays. One left and one right tray are connected as a pair. There are two
types of WDM trays. The VCW4 tray contains four WDMs with a total of 12 port
connections. The VCS8 tray contains eight WDMs with a total of 18 port
connections.

7-7
7.5
GPON optical and RF line rates

The 7342 ISAM FTTU system supports the GPON line rate of 2.488 Gbp/s
downstream and 1.244 Gbp/s upstream between the P-OLT and the ONTs, based on
the ITU-T G.984 protocol.
Alcatel-Lucent recommends using FEC to reduce the impact of BER events on
downstream IP video traffic. With FEC applied, the 28 dB optical budget of the
GPON connection can reach up to 29.5 dB performance. Actual performance will
vary, depending on the specific equipment and deployment conditions.
Consider the following when planning video deployments:
ONTs supporting video overlays only support a 1:4 split ratio

The maximum supported length of RG9 or RG59 coax cable is 100 ft (30.48 m)
See the RF video service DLP in the 7342 ISAM FTTU Operations and Maintenance
Procedures Guide using TL1 and CLI for more information about video deployment
configurations.
Note Video performance varies according to the unique
characteristics of the customer-specific setup, such as channel

loading, video backbone, and delivery service quality. Due to high
variations in customer requirements, contact your Alcatel-Lucent
sales representative to determine the guaranteed video performance
for your specific network and video application.
The V-OLT supports the full radio frequency (RF) spectrum of 47 MHz to 862 MHz.
7.6
P-OLT optical budgets

The optical budgets for NT and LT cards are described in the unit data sheet (UDS)
of the NT and LT cards. Table 7-6 describes the information provided in the NT and
LT UDSs.
Table 7-6 P-OLT optical budgets
7-8
Chapter
Title
Content
37
EHNT and pluggable optical modules

unit data sheet
Summary of optical modules and optical

budgets
38
EXNT-A and pluggable optical modules

unit data sheet
Summary of optical modules and optical

budgets
40
GLT2 unit data sheet
Optical budgets
41
GLT4 unit data sheet
Optical budgets

7.7
Video coupler optical budget

See chapter 52 LGX VCW2 unit data sheet for information about the optical
budget of the VCW2 connectors and the WDM.
7.8
Environmental requirements
Table 7-7 describes the environmental requirements of the P-OLT.
Table 7-7 P-OLT environmental requirements
Location
Temperature
Relative
humidity
Minimum
Normal
Maximum
Central office
23F (5C)
32F (0C) to 104F (40C)
122F (50C)
5 to 95%
Remote (temperature
hardened)
40F (40C)
23F (-5C) to 122F (50C)
149F (65C)
5 to 100%
Storage
40F (40C)
158F (70C)
5 to 95%
Table 7-8 describes the environmental requirements of the video coupler.

Table 7-8 Video coupler environmental requirements
Mode
Temperature
Relative humidity
(non-condensing)
Storage or shipping
40F (40C) to 185F (85C)
5% to 85%
Operating
40F (40C) to 185F (85C)
5% to 85%
(1)
Note
(1)
7.9
Under normal operating and storage conditions, 90% short term.
Power specifications
This section provides the following information about the 7342 ISAM FTTU:
input voltage
power consumption
See the 7342 ISAM FTTU ONT Product Information Manual deployment planning
chapter for ONT power information.
P-OLT input voltage

Table 7-9 describes the input voltage for the P-OLT.
7-9
Table 7-9 P-OLT input voltage
Operating condition
Power input
Operating range
72 V dc to 40 V dc
Nominal input voltage
48 V dc
No damage to equipment
0 V dc to 72 V dc
P-OLT power consumption

Table 7-10 describes the power consumption for components of the P-OLT shelf.
Table 7-10 P-OLT power consumption
Unit
Typical
Maximum
Quantity range
ACCU-C
5W
7.5 W
1/shelf
AFAN-H
48 W
130 W
1/shelf
AFAN-S
48 W
216 W
1/shelf
EHNT-A or EHNT-B
67 W
81 W
2/shelf
EXNT-A with GLT2-x cards
87 W
90 W at -5/+50 W unit power

draw
2/shelf

draw
EXNT-A with GLT4-x cards
92.2 W at -5/+50 W unit power

draw

draw
2/shelf
96.8 W at -40/+65 W unit

power draw
97.3 W at -40/+65 W unit

power draw
GLT2-A
35 W
40 W
16/shelf
GLT2-B
39 W
45 W
16/shelf
GLT4-x with EHNT-B
62 W

draw
14/shelf

draw
GLT4-x with EXNT-A

draw

draw
14/shelf
70.6 W at -40/+65 W unit

power draw

draw
1-GE SFP
1W
1W
4 to 8
10-GE XFP
2.5 W
2.5 W
1 to 2
ATRU-M ,
5W
10 W
1/rack
ATRU-N
ATRU-U
GTRU-B
7-10

To calculate the total typical power consumption of a component per shelf, multiply
the typical consumption of the component times the quantity per shelf. To calculate
the total maximum power consumption of a component per shelf, multiply the
maximum consumption of the component times the quantity per shelf.

7-11
7-12

Detailed system description
8 Alarms and troubleshooting

9 DHCP and PPPoE relay agents
10 Fault isolation
13 NT redundancy
14 Proxy ARP
15 QoS
17 Security
18 VLANs


Alarms and troubleshooting
8.1 Overview
8-2
8.2 Isolating faults indicated by alarms

8-3
8-1
8.1
Overview
This chapter provides information on how to:
view the P-OLT alarms that can be raised

determine the problem indicated by a P-OLT alarm
See the alarms chapter in the 7342 ISAM FTTU P-OLT and ONT Fault Isolation and
Troubleshooting for more information about ONT alarms.
General
Resolve P-OLT alarms that affect service before the alarms that do not affect service.
Use local procedures to correct problems associated with customized alarms.
Contact Alcatel-Lucent customer technical assistance at 1-888-252-2832
(1-888-ALCATEC) when a problem cannot be corrected. Many of the UNIX
troubleshooting protocols and most of the UNIX commands require root access. If
this is the case, Alcatel-Lucent recommends that a UNIX system administrator
perform the troubleshooting.
P-OLT alarms are grouped by alarm type, as shown in the 7342 ISAM FTTU P-OLT
and ONT Fault Isolation and Troubleshooting.
Except where otherwise specified, the report and logging modes for each alarm are
enabled.
Note 1 See the alarms chapter in the 7342 ISAM FTTU P-OLT and
ONT Fault Isolation and Troubleshooting for more information about
ONT alarms.
Note 2 To avoid excessing loading on the P-OLT, clear all
extraneous ONT alarms by making inactive ONTs out-of-service.
Alarm storm prevention

The following conditions may generate alarm storms.
1
Weather or other natural phenomenon in a given geographic area.
During software migration.
When a PONLOS alarm is declared due to multiple INACT alarms issued from
connected ONTs
You can suppress alarms due to weather or INACT alarms, as shown in Figure 8-1.
8-2


Figure 8-1 Alarm storm prevention
INACT
alarms
suppressed
ONT
X
PONLOS alarm triggered
LT
7342
X
Fiber cut or
other outage
PON
ONT
ONT
Configure suppression
of alarm storms
18998
When weather causes geographically concentrated alarm storms, you can lower
alarm reporting thresholds from NEs in that area.
When a fiber cut generates multiple INACT alarms on all affected ONTs connected
to the PON, the alarm storm prevention function uses a timing mechanism to buffer
all the INACT alarms. When the higher level PONLOS alarm is raised, all the
INACT alarms are discarded.
You can use the alarm filtering feature to remove reporting of the base alarms and
show the derived alarms. See the 7342 ISAM FTTU P-OLT and ONT Fault Isolation
and Troubleshooting for more information.
8.2
Isolating faults indicated by alarms

See the 7342 ISAM FTTU P-OLT and ONT Fault Isolation and Troubleshooting for
more information about listing, isolating, and fixing alarm issues.

8-3
8-4

DHCP and PPPoE relay agents
9.1 Overview
9-2
9.2 DHCP relay agent
9-2
9.3 DHCP relay configuration parameters

9.4 PPPoE relay agent
9-3
9-4
9.5 PPPoE relay agent configuration parameters

9-5
9-1
9.1
Overview
This chapter provides a detailed description of the Dynamic Host Configuration
Protocol (DHCP) or Point-to-Point Protocol over Ethernet (PPPoE) relay agent
functions that are used by the 7342 ISAM FTTU.
Note 1 The 7342 ISAM FTTU supports both DHCP and PPPoE
relay agents on the same ONT user-to-network interface (UNI).

However, the 7342 ISAM FTTU does not support both DHCP and
PPPoE relay on the same VLAN. These two services must be on
different S-VLANs.
Note 2 For instruction on how to configure DHCP and PPPoE, see
the 7342 ISAM FTTU Operations and Maintenance Procedures

Guide using TL1 and CLI.
9.2
DHCP relay agent

The DHCP is an enhanced version of the BOOTP. The DHCP enables a host at the
subscriber residence to obtain configuration information from a DHCP server over a
specified period of lease time after the host starts up. The configuration information
includes the IP address, subnet mask, DNS server address, and default router address.
The DHCP relay agent function is required when the LAN does not have BOOTP or
a DHCP server. In a LAN, a host on the LAN broadcasts a DHCP request message
on the network. Every DHCP server that receives the message replies with a DHCP
offer message, which allows the client to choose a server based on the host client
configuration. A server on the LAN can be configured to relay the requests to the
DHCP server that may be located elsewhere on the network. The DHCP relay agent
function also passes the responses from the server to the client that initiated the
request.
The 7342 ISAM FTTU uses the LT card to provide the DHCP relay agent function.
The LT card supports only the Layer 2 relay agent function.
DHCP Option 82
The DHCP Option 82 is an optional parameter that is inserted in the DHCP request
messages to identify the circuit that the requesting host is connected to.
The LT card can be configured to add or remove the Option 82 parameter as part of
the layer 2 forwarding and bridging function. In the response, the DHCP server
returns the Option 82 parameter so that the relay agent can relay it only to the circuit
from which the DHCP request originates.
When another device is configured as the DHCP server, and the 7342 ISAM FTTU
is configured as a DHCP relay agent, the Option 82 parameter should be enabled on
both devices, to ensure traffic passes correctly between the devices.
9-2

The 7342 ISAM FTTU supports multiple instances of the DHCP relay agent
function. Generally, one DHCP relay agent is configured for each VLAN. Each
VLAN can be connected to its own edge routers and DHCP servers. The service
providers can allocate private addresses to the CPE.
Note 1 If private IP addresses are used, the service provider must
provide the NAT function in the edge router.

Note 2 The proxy ARP function is activated on an residential
bridge VLAN when the DHCP relay is enabled on the residential

bridge VLAN. For information about proxy ARP, see Chapter 14.
DHCP Option 60
When there are multiple service providers on the VLAN and each service provider
has a DHCP server, the residential gateway must be configured with DHCP Option
60, which specifies the Vendor Class ID.
The DHCP Option 60 provides information about the service requested by the host
from a subscriber residence so that the host can receive the appropriate service from
the server.
9.3
DHCP relay configuration parameters

The DHCP relay agent function requires the configuration of the DHCP relay agent
and virtual router DCHP parameters.
DHCP relay agent configuration parameters

Table 9-1 describes the parameters used to configure the DHCP relay agent function.
To view the current DHCP relay parameter settings, see the 7342 ISAM FTTU
Operations and Maintenance Procedures Guide using TL1 and CLI.
Table 9-1 DHCP relay agent parameters
Parameter
Description
Relaying
When enabled, the relay agent is active.
Server
When enabled, the relay agent forwards the packets to a specific

DHCP server.
Server IP
IP address of the DHCP server to which the packets are to be

forwarded
secs-threshold/hops-threshol
d
Thresholds for Option 82
Agent circuit ID
For each VLAN, use one of the following formats:
do not add
physical line ID
customer ID (1)
(1 of 2)

9-3
Parameter
Description
Remote node ID
For each VLAN, use one of the following formats:
do not add
customer ID
(1)
(2 of 2)
Note
(1)
The format of the customer ID is an ASCII string that is configurable for each UNI and for each
service.
Restrictions
The following restrictions apply when configuring DHCP relay:
Before you enable the DHCP relay agent, you must configure the static routes to
the DHCP servers on a virtual routing and forwarding (VRF) IP interface.
Up to four DHCP servers can be configured on a VRF.
The S-VLAN ID of the HSI service that is configured for DHCP relay at the LT
card (layer 2) must match the VLAN ID that is entered in the VRF routing table
for layer 3.
Virtual router DHCP relay configuration parameters

The 7342 ISAM FTTU supports up to 128 virtual routers. Each virtual router
represents a dedicated IP routing space. Individual virtual routers cannot exchange
traffic between them. Each virtual router has a DHCP agent that is used exclusively
within its dedicated IP routing space.
You can configure the following DHCP relay parameters for each virtual router:
DHCP relay agent: The agent can be enabled or disabled.

Option 82 insertion: The option can be enabled or disabled. This is configured
independent of the DHCP relay agent status. When another device is configured
as the DHCP server, and the 7342 ISAM FTTU is configured as a DHCP relay
agent, the Option 82 parameter should be enabled on both devices, to ensure
traffic passes correctly between the devices.
Relay agent IP address: This parameter is the IP address of one of the VRF IP
interfaces.
9.4
PPPoE relay agent

Service providers can use PPPoE to provide high-speed Internet (HSI) services.
When a service provider chooses to use PPPoE, the PPPoE relay agent provides
information to the broadband remote access server (BRAS) about which subscriber
is setting up a PPPoE session. The PPPoE relay agent is used to provide the
information to BRAS. The BRAS returns the parameter so that the relay agent can
relay it only to the circuit from which the PPPoE request originates.
The PPPoE relay agent is an optional parameter. The value is inserted in the PPPoE
session establishment messages to identify the circuit that the requesting client is
connected to.
9-4

The P-OLT can be configured to enable or disable the PPPoE relay agent for each
S-VLAN as part of the layer 2 forwarding and bridging function. The P-OLT
supports PPPoE relay agents for stacked and unstacked residential bridge mode.
The P-OLT supports both PPPoE and DHCP relay on the same UNI. For example,
one service may use PPPoE and another service may use DHCP. However, PPPoE
service and DHCP service must be on different S-VLANs.
The P-OLT does not support both PPPoE and DHCP relay agent functions on the
same VLAN. Only one relay agent function can be enabled enabling on a first come,
first served basis.
9.5
PPPoE relay agent configuration parameters

When a PPPoE relay agent is enabled on a VLAN, the P-OLT must be configured
with a vendor-specific tag that can be added to the PPPoE discovery protocol
messages (PADI, PADR, PADT) in the upstream direction.
Note The packet is dropped if the packet exceeds the maximum
Ethernet frame size of 2000 bytes after the vendor-specific tag is
added. (The GLT2-A does not support 2000 byte frames and will drop
packets larger than 1800 bytes.)
Table 9-2 lists the format and specifications of the vendor-specific tag.
Table 9-2 Vendor-specific tag
Format
Specifications
Tag type
0 x 0105
Tag value
Enterprise code
Suboption 1
Circuit ID configurable for each VLAN in one of the following

formats:
Suboption 2
physical line ID
customer ID (2)
(1)
Remote ID configurable for each VLAN in one of the following

formats:
not add
customer ID
(2)
Notes
(1)
The physical line ID must use the same access node identifier as the DHCP Option 82 value. The
format of the physical line ID is:
<access-node-identifier>PON<rack>/<shelf>/<slot>/<PON>:<ONT>.<ONT-slot>.<UNI>. Slot
numbering for PPPoE Option 82 begins at 1. The physical line ID can be toggled to start with 01 or
03 depending whether the PONIDSYNTAX parameter is set to Legacy or Logical.
(2)
The format of the customer ID is an ASCII string that is configurable for each UNI and for each
service.

9-5
9-6

10 Fault isolation
10.1 Overview
10-2
10.2 Monitoring OLT and ONT optics

10.3 Ping
10-2
10-3
10.4 RMON Ethernet statistics
10-3
10.5 Statistics and performance monitoring

10.6 TCA counters and alarms
10.7 DS1 and E1 loopbacks
10.8 Ethernet OAM
10-3
10-3
10-4
10-5

10-1
10 Fault isolation
10.1
Overview
This chapter provides a detailed description of the 7342 ISAM FTTU fault isolation
features.
10.2
Monitoring OLT and ONT optics

The 7342 ISAM FTTU supports monitoring of the downstream and upstream optics
operating status for each ONT GPON connection using a TL1 or an element
management system (EMS) management session with the P-OLT.
Optical power levels

A report summary of the current OLT and ONT optical power levels can be viewed.
ONT receive optical signal level (1490 nm)

ONT transmit optical signal level (1310 nm)
OLT receive optical signal level from a specific ONT (1310 nm)
OLT transmit optical signal level (1490 nm)
Optics module status

The status of the optics modules in the GLT4 card and the ONT units are monitored.
The report summary will display the current:
temperature of the optics module

laser bias voltage level
laser bias current
Downstream threshold monitor
In addition to monitoring optical power levels, you can set high and low optical
power level thresholds for the downstream signals. An alarm is raised in the system
if either the upper or the lower power level threshold is crossed. Use TL1 to
configure optical power level thresholds.
The following wavelengths are used for downstream traffic between the P-OLT and
the ONTs across the GPON:
1490 nm downstream signals for data, VoIP, and packetized CES DS1/E1
1550 nm downstream signals for overlaid RF video
See the 7342 ISAM FTTU Operations and Maintenance Procedures Guide using
TL1 and CLI and the 7342 ISAM FTTU Fault Isolation and Troubleshooting Guide
documents for details about monitoring ONT optical GPON line power levels and
setting the high and low thresholds.
10-2

10 Fault isolation
10.3
Ping
The ping feature is available for troubleshooting layer 3 network connections
between an ONT device and voice gateways or servers on the GPON. From a TL1
management session with the P-OLT, you can initiate a ping from the ONT to any
host device or server on the GPON. For the ping feature to work, the device on the
GPON must be on the same VoIP VLAN as the ONT and VoIP must be provisioned
on the ONT. Only after VoIP is provisioned is the ONT assigned an IP address.
To ping a server on the network, enter the IP address of the server using standard
dotted decimal notation. As a security measure, you can disable the ONT from
responding to ping requests received from devices on the GPON to avoid flooding.
The ONT ping feature is disabled by default. For configuration information, see the
7342 ISAM FTTU Fault Isolation and Troubleshooting Guide.
10.4
RMON Ethernet statistics

The RMON Ethernet statistics (RFC 2819) can be used to track P-OLT Ethernet port
statistics on the NT using any RMON SNMP manager. The statistics can be used to
determine network performance. For example, frame throughput rates, as well as
bandwidth transmit and receive averages and peaks, can be measured by the type of
frame (unicast, multicast, or broadcast), and by the size of the frame.
10.5
Statistics and performance monitoring

Statistics counters and reports are useful for data collection, monitoring system
performance, and for troubleshooting performance on targeted segments of your
network. You can view statistics from a management session with the P-OLT using
TL1 or the EMS interface. Use the TL1 interface to configure performance
monitoring counters. For more information about statistics and performance
monitoring counters, see chapter 16.
VoIP call statistics

VoIP call statistics are useful for troubleshooting voice-related issues and for
information gathering. Statistics are gathered for the last incoming or outgoing call
on each POTS port configured for VoIP on the ONT. You can view VoIP call
statistics from a management session with the P-OLT using TL1 or the EMS
interface. For more information about VoIP call statistics, see chapter 16.
10.6
TCA counters and alarms

The following performance monitoring counters can generate TCA alarms:
errored or lost Tx and Rx fragments for upstream traffic across all GEM ports on
the GLT2 card on the outdoor ONTs
lost fragments or bad GEM headers received downstream on aggregate GEM

ports on the outdoor ONTs

10-3
10 Fault isolation
dropped frames (upstream and downstream) for Ethernet traffic on all MoCA,
and Ethernet ports on the outdoor ONT
Rx errored frames for ports on the ONT configured for MoCA

Rx errored, severely errored, and unavailable seconds for a VDSL2 transmission
TCA alarms
TCA thresholds are applied to 15-min counters. An alarm is raised if the number of
events occurring within a 15-min period exceeds the specified threshold. The
following alarms are raised:
PONOLTTC alarms
PONOLTTCONT alarms
PONONTTC alarms
ONTL2UNI alarms
ONTMOCA alarms
xDSL (VDSL2) alarms
TCA provisioning
Performance monitoring counters are provisioned using either a TL1 or an EMS
management session with the P-OLT. TCA is disabled by default. To enable TCA,
you must do the following.
Set the threshold value using the appropriate TL1 set TCA threshold command or
an EMS.
After the threshold is set, enable TCA using the appropriate TL1 set performance
monitoring mode command or set the appropriate fields in the EMS.
For configuration information, see 7342 ISAM FTTU Operations and Maintenance
10.7
DS1 and E1 loopbacks

You can perform remote loopbacks on DS1 and E1 TDM links at the business ONT
using a TL1 or an element management system (EMS) management session with the
P-OLT. See the 7342 ISAM FTTU P-OLT and ONT Fault Isolation and
Troubleshooting for instructions on how to perform DS1 and E1 loopback tests on
the business ONT.
Note You must put the link in the out-of-service (OOS) state
before you can perform a loopback test on that link.
Caution Service disruptions will occur on any link that has a

loopback test applied. Services on that link are disrupted for as long
as the loopback test is applied to that link. You must manually
deactivate an active loopback test.
10-4

10 Fault isolation
Figure 10-1 shows an active remote loopback at the business ONT. A remote
loopback loops TDM traffic back towards the subscriber on the connected DS1 or E1
links at the ONT. No MEF-8 packetization is applied to the TDM traffic that is
looped back towards the subscriber.
Figure 10-1 Remote loopback
CES line
Tx
Layer 2
de-packetizer
Layer 2
Rx
Subscriber
side
GPON
side
CES line
Rx
Layer 2
packetizer
Layer 2
Tx
18879
10.8
Ethernet OAM
The transition to Ethernet-based aggregation networks requires new operations and
maintenance fault management tools. The 802.1ag standard defines OAM
mechanisms for Ethernet. See the 7342 ISAM FTTU Fault Isolation and
Troubleshooting Guide for procedural information.
Figure 10-2 shows the components of 802.1ag-compliant Ethernet OAM.

10-5
10 Fault isolation
Figure 10-2 Ethernet OAM components
GPON access scope
Link trace
messages
Customer MP
Access link MEP
MP
MP
Link trace
replies
Trusted
Edge
router
Ethernet
edge switch
7342 ISAM FTTU

NT
ONT
RGW
LT
Customer MID level

Operator MD level
Access link MEP
Untrusted
Loopback
messages
Intra-carrier MEP
MP
Customer MEP
Customer MEP
MEP
Maintenance association
Ports
MIPs
Continuity checks
Loopback
replies
No
message
x
x
x
MP
No
Source reply
of fault
19054
Table 10-1 lists details of the OAM components.

Table 10-1 Ethernet OAM components
Component
Details
Configuration
Maintenance domain (MD)
MD levels divide the network into multiple administrative

OAM domains.
Create domains using

TL1
Maintenance association
(MA)
MA is an OAM maintenance entity per service instance in the

MD, such as a VLAN. An MA associates maintenance end points
or maintenance intermediate points into one OAM
maintenance entity, for example, the endpoints and
intermediate points of a VLAN.
Create MAs using TL1
MPs are configured on ports, services such as a VLAN, or MD.
Create MIPs and MPs

using TL1
Maintenance points (MPs)
Maintenance end points (MPs) either start or terminate an

OAM test, such as a loopback.
Maintenance intermediation points (MIPs) passively process
and allow the transit of an OAM packet to or from a MP.
Table 10-2 lists the supported OAM Ethernet tools.
10-6

10 Fault isolation
Table 10-2 Ethernet OAM supported tools
OAM tool
Details
See
Continuity check (CC)
Use CCs to have MPs send multicast connectivity check

messages periodically. All MPs and MIPs in the MD receive the
messages, and update its database to know the status
between itself and the MP sending the CC message.
Continuity check tests
Link trace
Use link traces to trace the path between MPs in a single MD.
All intermediate MIPs between the MPs respond with a link
trace reply until the MP at the end of the domain is reached.
The link trace results are used to determine the path for a
loopback by providing MAC addresses of all MIP and MP
devices.
Link trace tests
Loopback
Use loopbacks to determine the source of a fault along an MA.

The MP issues a loopback message to MIPs.
Loopback tests
The MIP just before the fault point will issue a loopback reply.
The MIP just after the fault will not issue a loopback reply.
Continuity check tests

Figure 10-3 shows the sequence for a continuity check (CC) test. All peer MPs in the
same MA exchange CC messages. All MIPs and MPs along the same MA build a
database of their peers. Only one MIP on the 7342 ISAM FTTU processes CC
messages.
Figure 10-3 Continuity check process for the NE
7342 ISAM FTTU
WMS/
CLI/
TL1
Router or
Switch
NT
LT
ONT
RG
An upstream NE sends a CCM to NT

The 7342 ISAM FTTU checks if the
MD and MA match the configured
values. It updates the MP database
with MEP ID and MAC address
of the originator.
19055
When a peer MP or MIP does not receive a specified number of CC reply messages
in a given time, a fault is raised.
CC messages can be sent from the ONT, as shown in Figure 10-4.

10-7
10 Fault isolation
Figure 10-4 CC messages on ONTs
Trusted and untrusted
7342 ISAM FTTU
WMS/
CLI/
TL1
Router or
Switch
NT
LT
ONT
RG
ONT sensor passes the

CCMs transparently to OLT.
LT forwards CCM
packet to NT
The 7342 ISAM FTTU
updates the MP ID and
MAC address of RG or ONT
19059
Link trace tests

A link trace acts like an ICMP traceroute command. Multicast link trace messages
(LTMs) are sent from the originating OAM MP. 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
MIP, and a response in the form of a link trace reply (LTR) message is sent back to
the MP. A 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.
Figure 10-5 shows the sequence for an link trace. In a link trace, the MP is on the
ONT.
10-8

10 Fault isolation
Figure 10-5 Link trace test sequence
7342 ISAM FTTU
NMS
CLI/
TL1
Router or
Switch
NT
LT
ONT
RG
Perform link test

(access-level, S-VLAN,
C-VLAN, MEP ID, p-bit)
The 7342 ISAM FTTU checks VLAN and
port membership. It obtains the MAC
address from MP ID internally. It forms
a link trace message packet with given
destination MAC address and p-bit and
forwards to LT ports only.
LT checks if MAC address exists in
forwarding database. If yes, LT
forwards it on GEM PORT
corresponding to service and p-bits
ONT extracts the packet based

on MAC address and Ethertype.
It sends a link trace message
reply with same p-bit and C-VLAN.
Response (LT success/failure;
ONT success/failure
LT forwards LTM
reply to NT
(no processing)
19057
Loopback tests
A loopback acts like an ICMP ping command. Multicast or unicast loopback
messages (LBMs) are sent from the originating OAM MP with the MAC address of
the destination MP. Each MIP along the loopback forwards the LBM to the next
MIP. When the target MP receives the LBM with the matching MAC address, the
destination MP sends back a unicast or multicast loopback response (LBR) message
to the originating MP. When the originating MP receives the LBR, the loopback is
complete.
Figure 10-6 shows the sequence for an loopback. In this loopback, the MP is on the
ONT.

10-9
10 Fault isolation
Figure 10-6 Loopback test sequence
7342 ISAM FTTU
WMS/
CLI/
TL1
Router or
Switch
NT
LT
ONT
RG
Perform loop back (based on access-level,

S VLAN, C VLAN, including MEP ID, p-bit)
NT checks V LAN and
port membership. It obtains the MAC
address from MEP ID internally. It forms
a loopback message packet with given
destination MAC address and p-bit and
forwards to LT ports only.
LT forwards the loopback message
like any other packet based on
S-VLAN, C VLAN, MAC address
and p-bits.
ONT extracts the packet based

on MAC address and Ethertype.
It sends a link trace message
reply with same p-bit and C-VLAN.
Response (success or failure)
LT forwards loopback
message reply to NT
19060
10-10

11.1 Overview
11-2
11.2 IP multicast stream flow

11.3 IGMP infrastructure
11-2
11-3
11.4 Join and leave messages
11-7
11.5 IGMP configuration requirements
11-11
11.6 Subscriber and video management

11.7 IP multicast service networks
11-17
11.8 Dynamic and static multicast streams

11.9 P-OLT IP multicast features
11.10 ONT IP multicast features
11-12
11-19
11-20
11-20

11-1
11.1
Overview
The 7342 ISAM FTTU delivers video streams on demand to IPTV video subscribers
using the IP multicast technology.
IP multicast is a technology that can send a single copy of data using a single address
for a group of recipients.
IP multicast is delivered to a group of subscribers that request a particular data
stream. The membership of the group is not restricted by the locations. These
members are hosts on the IP network. The group is identified by a single destination
IP address that must be within the Class D range.
Hosts that need to receive a data stream delivered to a particular group must join the
group through the Internet Group Management Protocol (IGMP). IGMP is a protocol
used by hosts and multicast routers in a single physical network to establish hosts
memberships in particular multicast groups. The 7342 ISAM FTTU supports two
versions of IGMP:
IGMP version 2 (IGMPv2) is described in RFC 2236. IGMPv2 provides support

for low leave latency by reducing the amount of time that it takes for a multicast
router to learn that there are no longer any members of a particular group present
on an attached network.
IGMP version 3 (IGMPv3) is described in RFC 3376. IGMPv3 provides support
for multiple group records in a single report.
TL1 and CLI for multicast and IGMP configuration procedures.
11.2
IP multicast stream flow

The content of IP multicast streams can include various types of information, such
as video, audio, data carousel, and electronic multicast guides. An IP multicast
stream flows from the network to the subscriber as follows:
1
Network equipment
Provides source of the IP multicast stream

Delivers the requested IP multicast stream to the NT card through external ports that
connect the network equipment to the NT card
NT card
Replicates the IP multicast stream for each requesting LT card

Forwards the requested stream to the LT card through internal ports over the
multicast VLAN associated with the IPTV service provider
LT card
Replicates the IP multicast stream for each requesting GPON

Forwards the IP multicast stream to a single GEM port ID on the requesting GPON
using its interworking function
GPON
Allows the IP multicast stream to be distributed to multiple subscribers on the

GPON because of its broadcast nature
11-2

ONT
Replicates the IP multicast stream for each requesting UNI port

Forwards the requested stream from the multicast GEM port ID on the GPON to the
user-to-network (UNI) port that connects the subscriber equipment to the ONT
Subscriber equipment
Receives and plays the requested IP multicast stream to the subscriber through a
11.3
host on the UNI port

Sends IGMP join and leave messages requested from the subscriber to the ONT
through the UNI port
IGMP infrastructure
Figure 11-1 is a high-level view of the IGMP infrastructure that is implemented on
the 7342 ISAM FTTU system to support multicast forwarding of a stream from the
network equipment to the subscriber equipment.
Figure 11-1 IGMP infrastructure
P-OLT NT
P-OLT LT
ONT
IGMP
Proxy
IGMP
Proxy
IGMP
Snoop
IGMP Joins, Leaves
and Reports
IGMP GMQs, GSQs
and GSSQs
Network
Equipment
Subscriber
Equipment
Multicast Forwarding
upstream
downstream
19241
The elements of the IGMP infrastructure include the following:
IGMP signaling
between each network interface port on the NT and the NT
between the NT and LT cards
between the LT and each user-to-network interface (UNI) port on the ONT
IGMP proxy
at the NT card
at the LT card
IGMP snoop on the ONT

11-3
IGMP signaling
IGMP signaling is a protocol used to add and remove IP multicast streams. IGMP
signaling consists of a set of IGMP messages that communicate the requirements for
delivery of IP multicast streams. Table 11-1 lists the IGMP message types.
Table 11-1 IGMP message types
IGMP message type
Description
Join
A request to send an IP multicast stream
Leave
A request to stop an IP multicast stream
Query
A request about the usage status of an IP multicast

stream, which includes the following two queries:
Report
general membership query (GMQ)

group specific query (GSQ)
A status report on the usage of an IP multicast stream
IGMP signaling between the network and NT
The NT receives query messages from the network, and responds to the network with
report messages. The NT sends to the network a first join message to start the
delivery of an IP multicast stream, and a last leave message to stop the delivery of
an IP multicast stream when the stream is no longer in use.
IGMP signaling between the NT and the LT card
The LT card receives query messages from the NT and forwards join, leave, and
report messages to the NT over the multicast VLAN associated with the IPTV
service provider.
IGMP signaling between the LT card and the ONT UNI port
An ONT can support one or more UNI ports. The port is either a 10/100 Base-T or a
10/100/1000 Base-T Ethernet, or a VDSL2 port. Each Ethernet/VDSL2 port is
associated with a single subscriber and is supported by eight subscriber GEM port
IDs on the GPON side. Each subscriber GEM port ID maps to a different priority
level and carries join, leave, and report messages upstream from the ONT to the LT
card, and query messages downstream from the LT card to the ONT.
Note For ONTs that have SoC technology on-board, only one UNI
port at a time can be configured for multicast streams. For more
information about ONTs and multicast support, see the
7342 ISAM FTTU ONT Product Information Manual.
11-4

IGMP proxy
IGMP proxy is a facility that acts on behalf of hosts. IGMP proxy manages a
multicast forwarding database that lets routers know which IP multicast streams are
to be delivered to subscribers, by performing the following functions:
Sends query messages to determine the usage status of IP multicast streams

Receives join, leave, and report messages
Adds or removes an entry in the multicast forwarding database in response to
join, leave, and report messages
Sends a first join message to start the delivery of an IP multicast stream
Sends a last leave message to stop the delivery of an IP multicast stream
Responds to incoming query messages on the usage status of IP multicast streams
IGMP proxy is implemented at both the NT and the LT card, which optimizes the
utilization of bandwidth by allowing the IP multicast streams to be delivered
on-demand to the subscribers without replicating them.
IGMP proxy at the NT
In the downstream direction, the IGMP proxy at the NT sends query messages to the
LT card to determine the status of active IP multicast streams. The IGMP proxy also
adds and removes entries in the multicast forwarding database in response to join,
leave, and report messages received from the LT card.
In the upstream direction, the IGMP proxy at the NT responds to query messages
received from the network by sending report messages that indicate the IP multicast
streams that are still required. The IGMP proxy also sends to the network a first
join message to start the delivery of an IP multicast stream and a last leave message
to stop the delivery of an IP multicast stream.
Querier election is used when more than one network-side router will send
IGMP GMQ and IGMP GSQ messages. The router with the lowest source IP address
in its IGMP GMQ and IGMP GSQ messages is elected the querier. The other routers
move to a passive state until queries from the elected router are no longer seen, at
which point the querier election process resumes. For more information, see RFC
3376 (IGMPv3), section 6.6.2 Querier Election.
The 7342 ISAM FTTU enables querier election when a VLAN has more than one
static router port. When an IGMP GMQ or IGMP GSQ message is received on one
of the static router ports, the IGMP proxy facility at the NT floods the message to all
the other static router ports for the VLAN. The IGMP proxy uses the elected router
port to send its network-side IGMP join, leave and report messages. If a router port
has not been elected, the IGMP proxy sends its messages on all router ports.
IGMP proxy at the LT card
In the downstream direction, the IGMP proxy at the LT card sends query messages
to the subscribers to maintain the status of active multicast streams on the GPON.
The IGMP proxy at the LT card receives and responds to join, leave, and report
messages received from the subscribers.
In the upstream direction, the IGMP proxy at the LT card responds to query messages
received from the NT, and sends join, leave, and report messages to the NT
requesting the addition or removal of an IP multicast stream.
11-5
IGMP snoop
The ONT supports an IGMP snoop facility. The IGMP snoop facility snoops (looks
into) upstream join and leave messages, and maintains the multicast forwarding
database supported by the ONT hardware, which keeps track of the IP multicast
streams that subscribers are currently viewing.
IGMP snoop versus IGMP proxy

Subscribers (hosts) send IGMP directly to IGMP proxy, which can regenerate IGMP
if required; IGMP snoop can only look into IGMP. Figure 11-2 illustrates this
difference.
Figure 11-2 IGMP snoop versus IGMP proxy
IGMP snoop (to snoop = to dig into, to look into)
A Subscribers (hosts) directly address IGMP proxy at the LT card.
B IGMP snoop at the ONT only monitors.
IGMP proxy (to proxy = to delegate, to authorize someone else to do)
C IGMP proxy at the LT card regenerates IGMP if required, and directs it to IGMP Proxy at the NT.
D IGMP proxy at the NT regenerates IGMP if required, and directs it to the multicast router.
NT
IGMP
proxy
LT card
IGMP
proxy
ONT
IGMP
snoop
D
R
IGMP H
IGMP
Hosts
IGMP
IGMP
H Host
R Router
Multicast forwarding database
19336
The IGMP messages sent by the subscribers terminate at the router interface of the
IGMP proxy at the LT card.
If a message represents a first join to an IP multicast stream or a last leave of an IP
multicast stream, the IGMP proxy at the LT card generates and sends, on its host
interface, an IGMP message to the IGMP proxy at the NT to start or stop the delivery
of the IP multicast stream.
If required, the IGMP proxy at the NT generates and sends, on its host interface, a
first join or last leave IGMP message to the multicast router.
11-6

11.4
Join and leave messages

Subscribers send IGMP join and leave messages from a host on the UNI port. More
than one host can be on the same UNI port and can be simultaneously receiving the
same stream.
An UNI port can be provisioned for LT-to-ONT signaling. When LT-to-ONT
signaling is enabled, the ONT forwards the join and leave messages to the LT card
for processing; when the LT-to-ONT signaling is disabled, the ONT processes the
messages.
LT-to-ONT signaling mode enabled

LT-to-ONT signaling is typical for deployments where the 7342 ISAM FTTU
system is not integrated with a third-party IPTV middleware application. In such
cases, 7342 ISAM FTTU system is required to control access to IP multicast streams
and to provide facilities to collect and report viewer statistics.
In LT-to-ONT signaling mode enabled, the ONT forwards join and leave messages
from the subscriber to the LT card. When a join request is received from the ONT,
the LT card validates the request for the following:
maximum bandwidth of IGMP signaling channel is not exceeded

maximum stream count of IGMP signaling channel is not exceeded
subscriber has full-view or pre-view rights to the multicast stream
message is valid
For validated join messages, if no other host on the UNI port is receiving the stream,
the LT card signals the ONT to forward the IP multicast stream from the GPON to
the UNI port.
When the LT card receives a leave request from the ONT, the LT card validates that
the message is valid. If no other host on the UNI port is receiving the stream, the LT
card signals the ONT to stop sending the stream to the UNI port.
LT-to-ONT signaling mode disabled (default)

In LT-to-ONT signaling mode disabled, join and leave messages are processed by
the ONT. This mode is typical for deployments where the 7342 ISAM FTTU system
is integrated with a third-party IPTV middleware application, such as MSTV, and the
access control and viewer statistics provided by the 7342 ISAM FTTU system is not
required.
Join messages
When the ONT receives a join message, the following events take place, as
numbered in Figure 11-3.

11-7

Figure 11-3 Processing of IGMP messages at the ONT
IGMP signaling
channel
2
IGMP snoop
3
GPON
UNI
Multicast GEM port ID
Priority=0 GEM port ID
Ethernet/VDSL port
4
6
ONT bridge
Multicast forwarding
database
Downstream
Upstream
Traffic flow
Data retrieval or updates
19253
The ONT forwards a copy of the request to the IGMP snoop facility.
The IGMP snoop facility determines that the maximum number of IP multicast
streams allowed on the UNI port is not exceeded.
The ONT snoop facility adds the MAC multicast address (first 23 bits of the IP
multicast address) to its forwarding database and associates the MAC multicast
address with the UNI port.
The ONT forwards the original join message to one of the eight GEM port IDs
associated with the UNI port based on p-bit. The join message is carried
upstream to the LT card.
When the IP multicast stream is available on the GPON, the ONT validates the
destination IP multicast address in the multicast frames. Non-validated frames
are dropped; validated frames are forwarded from the GPON to the UNI port of
the subscriber.
The LT card sends periodic queries to the subscriber to audit the stream usage
using the multicast GEM port ID.
When the original join message is forwarded upstream from the ONT, the message
is carried across the GPON using the subscriber GEM port ID and is terminated at
the GPON-side router interface of the IGMP proxy at the LT card. If the requested
IP multicast stream is already on the GPON, no further action is required.
If the requested IP multicast stream is not on the GPON, the following events take
place, as numbered in Figure 11-4.
11-8


Figure 11-4 Processing of join messages at the LT card
Multicast Source
Table
2
IGMP proxy
3
GigE
GPON
Multicast VLAN ID
Multicast GEM port ID

database
LT bridge
Downstream
Upstream
Traffic flow
Data retrieval or updates
19254
The LT card extracts the join message from the traffic flow and forwards it to
IGMP proxy.
The IGMP proxy performs a lookup on the IP multicast address in the Multicast
Source Table.
The IGMP proxy adds the IP multicast address and the source VLAN ID of the
requested IP multicast stream to its forwarding database and associates it with the
multicast GEM port ID.
If the request is a first join, the IGMP proxy sends a first join message to the
NT using the multicast VLAN.
When the IP multicast stream arrives from the NT card over the multicast VLAN,
the LT forwards it to the GPON using the multicast GEM port ID.
Leave messages
When the ONT receives a request from a subscriber to leave an IP multicast stream,
the ONT IGMP snoop facility snoops the message and stops forwarding the stream
from the multicast GEM port ID to the subscriber if no other host on the UNI port is
receiving the stream. If the ONT supports more than one subscriber, the ONT stops
forwarding the IP multicast stream only if there is no other subscriber using the
stream.
The IGMP proxy at the LT card determines if other subscribers are interested in the
IP multicast stream. If no other interested subscribers are found, the IGMP proxy at
the LT card stops forwarding the IP multicast stream to the GPON, sends a last
leave message to the NT card to stop the delivery of the IP multicast stream, and
removes it from its multicast forwarding database.

11-9
The IGMP proxy at the NT determines if other LT cards require the IP multicast
stream. If no other LT card is found, the IGMP proxy at the NT sends a last leave
message to the network to stop the delivery of the IP multicast stream, and removes
the stream from its multicast forwarding database.
Processing limits
The maximum number of IGMP messages that are allowed within a one second
interval is configurable by UNI port. The IGMP message rate per second is also
affected by the collection of CDR records. Enabling CDR record generations lowers
IGMP message rates. CDR records are configurable system wide. When the message
rate exceeds the threshold value, the IGMP message processing is suspended for the
current and the next one-second time intervals.
The following threshold values are configurable by both GPON and UNI port:
the maximum bandwidth that can be consumed

the maximum number of streams that are allowed
Note If required for vendor-specific applications, the multicast
bitrate can be set to zero for IGMP signaling channels, in which case
the LT will not monitor bandwidth consumption by the ONT UNI.
The PON multicast bandwidth monitoring will still be applicable.
When threshold values are exceeded, requests to join the IP multicast groups are
denied. Table 11-2 identifies the division of tasks between the LT card and the ONT
in tracking and enforcing these limits.
Table 11-2 Processing limits
Network element
Item
LT tracks and limits
The amount of bandwidth consumed across the GPON

The number of streams that are allowed to be transported
across the GPON
LT tracks
The amount of bandwidth consumed across an ONT UNI port.

Note that the maximum multicast bitrate can be set to zero
for IGMP signaling channels, in which case the LT will not
monitor bandwidth consumption by the ONT UNI.
The number of streams that are being transported across
each UNI port
The number of hosts on each UNI port that are
simultaneously receiving the same stream
ONT tracks and limits
The number of streams that are allowed to be transported

across each UNI port
The number of hosts on each port that can simultaneously be
receiving the same stream
11-10

IGMP expedited leave

When a subscriber changes from one channel to another channel, the expedited
IGMP leave function immediately causes the removal of a stream. This quick
reaction allows for the recovery of the bandwidth used by the old channel before the
new channel is delivered.
The IGMP expedited leave is supported by both the P-OLT and the ONTs as follows.
When there are no subscribers accessing the stream on the GPON, the stream is
removed by the LT card from the GPON.
When there are no subscribers accessing the stream on the ONT UNI port, the
stream is removed by the ONT from the port.
11.5
IGMP configuration requirements

The steps to configure the IGMP system are as follows:
1
Provision the IGMP system.
Provision a video subscriber.
Table 11-3 identifies the data configuration requirements for multicast forwarding by
configuration step.
Table 11-3 Multicast data configuration requirements
Configuration step
Data configuration
requirement
Description
Provision the IGMP

system
Multicast VLAN per IPTV service

provider
Specifies the unstacked VLAN over

which the IP multicast streams from
an IPTV service provider are to be
carried to the LT card
Multicast Source Table
Specifies the IP multicast groups that

a subscriber can join, and associates
the IP multicast stream with the
multicast VLAN
Multicast bandwidth for the

GPON
Specifies the maximum multicast

bandwidth for the GPON.
When a join message is received at
the LT card, if the requested IP
multicast stream is not already on the
GPON, the bit-rate for the requested
IP multicast stream is added to the
multicast bandwidth that is in use. If
the total exceeds the maximum
multicast bandwidth for the GPON,
the request to join is denied.
LT IGMP proxy facility
Specifies the operational parameters

for the IGMP proxy facility at the LT
(1 of 2)

11-11
Configuration step
Data configuration
requirement
Description
Provision a video
subscriber
Subscriber VLAN at the SHub
Specifies the subscriber VLAN through

the NT Ethernet switch
DHCP relay and IP address
Provisions DHCP relay and IP address
DHCP server
Specifies the address of the DHCP

server
Subscriber VLAN
Specifies the VLAN for the subscriber.

The VLAN can be stacked or
unstacked.
HSI service for the subscriber
Specifies the HSI service for the

subscriber
IGMP signaling channel
Specifies the IGMP signaling channel

for a subscriber and associates the
channel with the subscribers HSI
service.
The IGMP signaling channel includes
the multicast attributes of the UNI
port, which are used to validate IGMP
join messages.
(2 of 2)
TL1 and CLI for multicast and IGMP configuration procedures.
11.6
Subscriber and video management

Tasks for the management of subscribers and video services include authentication,
authorization, and accounting. For these functions, the 7342 ISAM FTTU supports
middleware applications, such as Alcatel-Lucent FSD-ICE Open Media suite or
Microsoft TV2.
The 7342 ISAM FTTU system supports a package feature that allows each multicast
source to be associated to one or more multicast packages that are offered to the
subscribers. The subscriber can choose to subscribe to a package for a pre-view
session or for a full-view session. The package feature is typical for deployments
where operators have developed their own IPTV middleware application.
Terminology
Multicast source, multicast stream, and channel share the same IP multicast address
and are used in this section as follows:
multicast source refers to a multicast group that a subscriber can join

multicast stream refers to an IP data stream that is sent out into the network and
is organized into multicast packages
channel refers to the means by which a subscriber accesses a multicast stream in
a multicast package
Figure 11-5 illustrates the relationship among the terms multicast source, multicast
stream, and channel.
11-12


Figure 11-5 Multicast source, multicast stream, and channel
Video server
Multicast
source
Package 1
Package 2
Multicast stream
Package n
Channel
19140
Package
A package is a group of multicast streams that share a common access permission.
The service provider can deliver different levels of services to subscribers by
grouping multicast streams into one or more multicast packages. Up to 1024
multicast packages are supported. The service provider can assign names to the
available package numbers. Figure 11-6 shows an example of a package with sample
subscribers.
Figure 11-6 Package example with sample subscribers
BBC
NBC
Weather channel
...
Basic
CNN
BBC World
...
News
Eurosport
Sky sports
...
Sports
Subscriber 1
Basic
Subscriber 2
Basic
News
Subscriber 3
Basic
News
Sports
News
Sports
Subscriber 4
19131
Access control
The steps for creating multicast packages and providing subscriber access to them
are shown in Figure 11-7.

11-13

Figure 11-7 Steps for creating multicast packages and providing access to subscribers
Multicast sources
Packages
Multicast
source
data
2
Configure
multicast
sources
IGMP channel
Number and
name packages
Configure
IGMP channel
Package
data
IP multicast address
Pre-view limits
4
Set pre-view
limits
Pre-view
Multicast
data
source
table
IGMP
package
table
IGMP
channel ID
Signaling
requirement
IGMP
channel
data
7
IGMP
channel
table
Enable LT-to-ONT
signaling
Full-view packages
Pre-view packages
3
Categorize
multicast sources
into packages
Package
bitmap
6
Package
number
Package
number
Provide access
rights to
subscribers
IGMP
channel ID
Subscriptions
19138
The implementation steps are as follows:

1
Number and name the multicast packages.
Configure the multicast sources.
Categorize the multicast sources into multicast packages.
Set pre-view limits for multicast stream.
Configure an IGMP channel for a subscriber and associate the IGMP channel
with the subscriber HSI service.
Provide access rights to the subscriber by indicating the multicast packages the
subscriber is entitled to request (according to subscriptions).
Enable or disable LT-to-ONT signaling.

Note The following steps can be done concurrently:
steps 2, 3, and 4
steps 5, 6, and 7
See the Multicast IGMP service configuration section of the
using TL1 and CLI.
11-14

Access modes
For a particular multicast package, the following access modes are offered:
Full-view: The subscriber can join the multicast stream at any time with unlimited
view duration.
Pre-view: The subscriber can join the multicast stream with a limited pre-view
frequency and view duration.
No-view: The subscriber cannot join the multicast stream, neither in pre-view nor
in full-view mode.
The access mode applies to all hosts on the same service.
With pre-view rights for a multicast group, the subscriber can subsequently access
the channel up to some predefined period. The frequency of subsequent pre-views
and the duration between consecutive pre-views are limited per multicast stream to
avoid service theft. All hosts on the same service share the same pre-view counts, so
that the pre-view expires at the same time for all of them.
If the LT-to-ONT signaling is enabled, the LT notifies the ONT to stop forwarding
the multicast stream from the PON to the subscriber when the pre-view time expires.
Control Data Records

The 7342 ISAM FTTU supports Call Data Records (CDRs). CDRs are audit trail
records that reflect the viewing behavior of subscribers. CDRs support the operator
with an overview of the multicast join and leave activities on the UNI. They can be
used by an operator for marketing or monitoring purposes as follows:
For marketing: allows the operator to collect statistics regarding the popularity of
a multicast stream
For monitoring: allows the operator to ensure that subscribers are successfully
accessing the channels within their subscription range
The generation of CDR records is configurable at the system level.When the operator
explicitly enables this feature, the NE generates autonomous CDR records. A CDR
record can be generated for one or more of the following events:
a join of a pre-view session

a join and leave of a full-view session
a join outside the access rights of the subscriber
a join of a pre-view session when the maximum number threshold has been
exceeded
a join of a pre-view session during the black-out period
an interim viewing of a full-view or pre-view session

11-15
The generated CDR records are temporarily stored in volatile memory buffers on the
LT cards. At predefined time intervals, the NT retrieves these memory buffers and
stores the records in one of two ways for later retrieval by the operator:
local file storage: the NT stores the records as a local file on the
Alcatel-Lucent-approved flash storage device; the file can be retrieved using
TFTP
remote logging storage: the NT forwards the CDR records to the syslog system
for local logging to the syslog RAM disk or remote logging to a network server
A CDR record contains the following information:
a sequence number to uniquely identify a CDR record by LT card

the multicast stream being subscribed
the multicast source sending the multicast stream
source address of the subscriber
the service interface
the multicast mode
the reason for which the CDR record was generated
the type of CDR record that has been generated
the session number
the view duration
the date and time of CDR record
Wholesale video through residential-bridging

Table 11-4 describes the steps required to provide wholesale video through
residential-bridging.
Table 11-4 Wholesale video through residential-bridging
Data configuration
requirement
Description
SHub
Create a residential-bridge service VLAN on the SHub and enable

downstream multicast flooding over the S-VLAN (ENT-LANXVLAN).
Associate the service VLAN to a network-side port and one or more
LT-side ports (SET-LANXVLANPORT).
LT
Create a service VLAN on the PON with the following characteristics

(ENT-PONVLAN):
C-VLAN learning mode

Stacked VLAN tagging mode
enabling of downstream multicast traffic in the C-VLAN
Create a C-VLAN based static bridge port that links the C-VLAN to the
service VLAN on the PON (ENT-PONCFDBSTATIC).
ONT
Create three services with an upstream tagging mode of VLAN translation

using ENT-SERVICE-HSI, and associate the UNI-side VLAN (C-VLAN) with
the same network-side VLAN (S-VLAN).
Create an IGMP signaling channel and associate the channel with one of
the services.
11-16

11.7
IP multicast service networks

The 7342 ISAM FTTU supports two types of subscriber access network for IP
multicast services: IP and PPPoE.
IP subscriber access network

The IP subscriber access network is an IP-based end-to-end architecture that
integrates network routers and switches, such as Alcatel-Lucent 7750 Service Router
and the 7450 Ethernet Service Switch, with the access network provided by the
7342 ISAM FTTU and a residential gateway at customer premises.
Figure 11-8 shows the IP subscriber access network architecture and the signaling
flow.
Figure 11-8 IP subscriber access network architecture and signaling flow
Video server
7750/7450
7342 OLT-NT
7342 OLTLT
IGMP proxy
IGMP proxy
IP termination
IP termination
7342 ONT
RGW
IGMP
snooping
IGMP proxy
IP termination
IGMP termination
IPoE (IGMP
Report/Leave)
IPoE (IGMP
GSQ/GMQ/GSSQ)
Set-top box
IGMP
termination
IPoE (IGMP Report/Leave)
IPoE
IPoE (IGMP GSQ/GMQ/GSSQ)
IPoE
IPoE (UDP/RTP multicast stream)

19242
The 7342 ISAM FTTU supports layer 2 QoS based on the ITU-T 802.1q
prioritization and frame scheduling. The network routers, switches, and residential
gateway support layer 3 QoS requirements that are using differentiated services and
rate shaping.
IGMP messages across the access network are encapsulated in IP packets.
Time-critical IP multicast streams such as video on demand and broadcast video are
rate shaped at the video source, the video server, network routers, and switches, and
forwarded to subscribers encapsulated in IP packets.
The IP multicast service supports a VLAN for each subscriber or a VLAN for each
service deployment model. IP multicast streams are sourced from one or more
VLANs.
The residential gateway and the LT card support an IGMP proxy and encapsulate
IGMP signaling messages using IP. The LT cards also support IGMP statistics and
expedited leave. Expedited leave is an enhancement to the fast leave facility
introduced in IGMP v.2 (RFP 2236) and quickly removes unused multicast streams
to recover transport resources.
The 7342 ISAM FTTU controls multicast forwarding by supporting IGMP proxy on
NT cards and IGMP snoop on the ONTs.

11-17
PPPoE subscriber access network

The PPPoE subscriber access network is a legacy access network as specified in
TR-025 and TR-059. This access network supports PPPoE subscriber protocols as
described in TR-043.
Figure 11-9 shows the PPPoE subscriber access network architecture and signaling
flow.
Figure 11-9 PPPoE subscriber access network architecture and signaling flow
BRAS
7342 OLT-NT
PPPoE
termination
IGMP
proxy
IGMP
termination
7342 OLTGLT2
IGMP
snooping/proxy
7342 ONT
RG
Set-top box
IGMP
snooping
PPPoE
termination
IP termination
IGMP proxy
IGMP
termination
PPPoE (IGMP Report/Leave)
IPoE
PPPoE (IGMP GSQ/GMQ/GSSQ)
IPoE
Video server
IPoE (IGMP GSQ/GMQ/GSSQ)
IP termination
IPoE (IGMP Report/Leave)
IPoE (UDP/RTP multicast stream)
18192
The PPPoE subscriber access network can be upgraded to support an Ethernet-based

architecture using the WT-101 migration guidelines while preserving the existing
PPPoE-based subscriber management infrastructure.
The 7342 ISAM FTTU IP multicast service supports half proxy mode.
Half proxy mode
IGMP messages between the BRAS and the RG are encapsulated in subscriber
PPPoE sessions. IP multicast streams originate separately at an edge multicast router
and are forwarded to subscribers encapsulated in IP packets. IGMP messages
between the edge multicast router and the NT card are encapsulated in IPoE.
To support this architecture, the 7342 ISAM FTTU IP multicast service supports the
following:
IGMP proxy facility at the NT cards and IGMP snoop facility at the ONTs
a half IGMP proxy facility at the LT card. This is a half proxy because it does not
send IGMP queries to the RG on behalf of network-side equipment. It does,
however, aggregate IGMP reports and leaves from the RGW to network-side
equipment.
11-18

The PPPoE session flow between the subscriber RG and network BRAS is not
interrupted. The IGMP snoop and proxy facilities look for IGMP report and leave
messages in upstream PPPoE subscriber sessions. When the IGMP snoop and proxy
facilities see an RG IGMP report, they set up and maintain an entry in the associated
downstream multicast forwarding table. When an IGMP leave is detected, they
remove the entry from the associated multicast forwarding table if there is no other
subscriber requesting the stream.
The RG supports an IGMP proxy and encapsulates IGMP signaling messages using
PPPoE. The RG only responds to PPPoE encapsulated IGMP queries from the
BRAS.
11.8
Dynamic and static multicast streams

The 7342 ISAM FTTU supports both dynamic and static multicast routing to provide
reliable transport of multicast stream content between the network and CPE. The
type of multicast stream is provisioned by setting a command attribute to either
dynamic or static. The attribute setting is stored as an entry in the Multicast Source
Table with other multicast configuration data (see Table 11-5).
Note 1 See the ENT-PONMCSRC command in the

using TL1 and CLI for LT provisioning information.
Note 2 See the SHub Multicast Filtering Database Configuration
command and the SHub Multicast Filtering Port List Configuration
Command in the 7342 ISAM FTTU CLI Commands Guide for NT
provisioning information.
Dynamic multicast stream

In the 7342 ISAM FTTU, a dynamic multicast stream is provisioned in the Multicast
Source Table and is activated or deactivated using IGMP signaling. The IGMP
signaling is used to add or remove an entry in the multicast forwarding databases
supported at the NT, LT, and ONT.
Static multicast stream

A static multicast stream is provisioned in the Multicast Source Table, but is not
activated using IGMP signaling. When a provisioned static multicast stream is found
during system startup, the stream is immediately activated by adding an entry to the
multicast forwarding databases supported at the NT, LT, and ONT.
Static multicast streams are usually very low bit rate streams that are carrying
background system information, such as router table and network time updates. A
maximum of eight static multicast entries are supported. Static multicast streams can
be associated with a PON to ensure availability of bandwidth.
Note Static multicast channels support RIPv2 on both the NT and
the LT.

11-19
11.9
P-OLT IP multicast features

The P-OLT can be configured to support the IGMP proxy and snoop facility with
P-OLT IP multicast features. Table 11-5 summarizes the P-OLT IP multicast
features.
Table 11-5 P-OLT IP multicast features
Features
Description
IGMP message
encapsulation
The IP multicast supports both IPoE and PPPoE encapsulated IGMP

messages.
IP multicast stream
processing
The IP multicast supports replication and forwarding from the NT

cards to LT cards over point-to-point eHCL links. The LT can receive
multicast traffic at the full 4 Gb/s throughput capacity on the eHCL
links if required. The individual link between the NT and LT is
selected using a source IP address plus destination IP address based
hashing method.
On the LT card, the multicast data stream is replicated so that each
GPON can share the same IP multicast stream if there are subscribers
requesting the same stream on each GPON. For example, if an IP
multicast stream is sent to one GPON on the LT at 1.5 Gb/s, the LT
replicates the stream so that the other GPON can receive the same
IP multicast stream. Multicast replication on the LT can increase the
efficiency of bandwidth utilization on the eHCL links between the NT
and the LT. Each GPON can simultaneously support up to 2.4 Gb/s of
multicast traffic with this approach, although the NT to LT capacity
is 4 Gb/s.
11.10
IGMP versions
The IP multicast supports IGMP version 2 as defined in RFC 2236 and

IGMP version 3 (without source-specific multicast) as defined in RFC
3376.
Configured IP multicast
streams (Multicast Source
Table)
Configured IP multicast streams are treated as members of the IPTV

domain. The configured stream has the following attributes:
Bandwidth and streams

control
The IGMP proxy at the LT card can control the amount of bandwidth
used across the GPON for support of the IP multicast service. It can
also control the number of streams allowed to be delivered to a
subscriber.
source VLAN identifier
transport bit rate
source identifier, such as CNN, ESPN, ABC
service identifier, such as Time Warner, Verizon, or AT&T
type of multicast stream, dynamic or static
multicast packages
pre-view duration
maximum number of pre-views allowed
black-out duration between consecutive pre-views
ONT IP multicast features

The ONTs support the IGMP snoop facility. Table 11-6 provides information about
the ONT IP multicast features.
11-20


Table 11-6 ONT IP multicast features
Features
Description
IGMP message
encapsulation
The IP multicast supports both IPoE and PPPoE encapsulated IGMP

messages.
IP multicast stream
processing
The IP multicast supports a multicast forwarding database that is

managed by the IGMP snoop facility to control forwarding of IP
multicast streams from the multicast GEM port ID to requesting UNI
ports.
Configurable attributes
For the ONT, the configurable attribute is the maximum age of a

multicast stream.
For the ONT UNI port, the configurable attributes include:
the maximum number of multicast stream allowed on a UNI port

the maximum number of hosts allowed
the maximum number of IGMP messages allowed within a 1 s
interval
the IGMP version (specify IGMP v2 or IGMP v3, otherwise accept
the system default)
the C-VLAN associated with the subscriber
the packages to which the subscriber has full-view access rights
the packages to which the subscriber has pre-view access rights
the LT-to-ONT signaling mode
For ONTs that have SoC technology on-board, only one UNI port at a
time can be configured for multicast streams. For more information
about ONTs and multicast support, see the 7342 ISAM FTTU ONT
Product Information Manual.

11-21
11-22

12.1 Overview
12-2
12.2 Layer 2 forwarding rules

12.3 Layer 2 forwarding modes
12-2
12-4
12.4 Residential bridge mode configuration requirements
12-8
12.5 Residential bridge with VLAN pass-through mode configuration

requirements
12-10
12.6 Residential bridge with C-VLAN forwarding mode configuration
requirements
12-10
12.7 VLAN cross-connect mode configuration requirements
12.8 Forwarding unicast traffic in the LT card
12.9 MAC filters
12.10 Pause frames
12-11
12-12
12-13
12-13
12.11 Subscriber scalability
12-13

12-1
12.1
Overview
This chapter describes the layer 2 forwarding function used by the
7342 ISAM FTTU. The 7342 ISAM FTTU uses the layer 2 forwarding protocol to
create a secure tunnel for data and video traffic across the IP network.
The 7342 ISAM FTTU uses the NT and the LT cards to provide the layer 2
forwarding function. The NT and LT cards are two independent layer 2 systems.
They both learn and age independently on MAC addresses. Where C-VLAN
forwarding is used in residential bridge mode, the LT card also learns and ages on
C-VLAN.
Note 1 Although the aging timer is independent in the NT and LT
cards, the configured values must be as identical for proper operation.

The aging timer value in the LT should be the same for all LIMs.
Note 2 The maximum Ethernet frame size supported at the OLT
and ONT interface is 2000 bytes. However, the GLT2-A does not
support 2000 byte frames and will drop packets larger than 1800
bytes.
12.2
Layer 2 forwarding rules

The NT card provides the following layer 2 forwarding features:
classifying of interfaces
switching flood traffic
learning MAC addresses
Classifying of interfaces
For layer 2 forwarding, the 7342 ISAM FTTU classifies the interfaces into the
following categories:
network interface
access interface
control interface
Table 12-1 describes the layer 2 forwarding rules for the unicast frames between the
interfaces.
Table 12-1 Unicast frame forwarding rules
Interface
Network interface
Frames received on a network interface can be forwarded to another

network interface and the control interface.
Access interface
Frames received on an access interface can be forwarded to the

network interface.
(1 of 2)
12-2

Interface
Control interface
Frames received on the control interface can be forwarded to the

network and access interface.
(2 of 2)
These rules can be forced or further restricted by VLAN port configuration. For
example, only one access interface can belong to a VLAN in cross-connect mode.
Switching flood traffic

Flooding in the Ethernet switch is limited to 500 packets/s per type per port for
security. The types of flooding are:
broadcast
unknown destination
unknown multicast
The forwarding of broadcast frames or frames with unknown (unicast or multicast)
destination MAC address uses the rule to flood to all allowed interfaces.
Learning MAC addresses

Duplicate MAC addresses cannot be learned by an NT card. Table 12-2 describes the
priority information about the learning interfaces.
Table 12-2 Rules for learning MAC addresses
Learning interface
Priority
Control interface
This interface has priority over a network or an access interface

regardless of the order of learning.
Network interface
This interface has priority over an access interface regardless of the

order of learning.
Two network interfaces
The last network interface takes priority. MAC movement is

performed.
Two access interfaces
The first access interface takes priority. MAC movement is not

performed.
Duplicate MAC address handling
To handle duplicate MAC addresses, the GLT4 card reserves 64 filters and the GLT2
card reserves 32 filters. If the LT card receives a duplicate MAC address, the LT
card:
discards the frame

notifies the NT card, which generates a duplicate MAC alarm to the EMS

12-3
blocks traffic as follows:

if the LT card has an unused reserved filter, installs a reserved filter on the LT card
to discard subsequent frames from the BridgePort with the same source MAC
address. Frames with different source MAC addresses will not be discarded; frames
destined to the duplicate MAC address will be forwarded to the first BridgePort
where the duplicate MAC address was learned
if all reserved filters are installed, blocks the BridgePort
provides a mechanism to automatically remove the filter and to clear the alarm as
follows:
The filter is removed after the MAC address ages on the first BridgePort where the
MAC address was learned.
The BridgePort is unblocked after a minimum time period.

The duplicate MAC alarm is cleared from the moment the MAC address ages.
The alarm timer is re-started if the duplicate MAC re-occurs after the filter is
removed and before the duplicate MAC alarm is cleared.
If the NT card receives a frame with a MAC address that was learned on a different
LT card, the frame is returned to the LT card with a destination MAC address of the
LT card itself. The LT card performs the usual duplicate MAC address handling.
MAC address flushing
Learned MAC addresses are flushed from the VLAN forwarding database as
follows:
Aged-out MAC address entries are flushed.

After an Ethernet connection is disconnected on the UNI of an ONT, the learned
MAC address entries for the ONT UNI port are flushed.
After the maximum MAC value on a port is changed to a lower number by an

operator, the learned MAC address entries for the ONT UNI port are flushed.
After a port is authenticated, the learned MAC address entries for the ONT UNI
port are flushed.
12.3
Layer 2 forwarding modes

The 7342 ISAM FTTU supports the following types of layer 2 forwarding modes:
residential bridge mode

residential bridge with VLAN pass-through mode
residential bridge with C-VLAN forwarding mode
VLAN cross-connect mode
Residential bridge mode

The residential bridge function is required when multiple network service providers
(NSPs) are connected to the 7342 ISAM FTTU using a VLAN.
12-4

In the multiple NSP scenario, the subscriber ports are connected to the VLAN of their
corresponding NSP. Multiple subscriber ports can be associated with a single
VLAN. When a subscriber generates a frame or a frame is received from the
upstream NT card, the P-OLT performs a MAC address lookup in the forwarding
table identified by the VLAN. Each VLAN has a forwarding table in the P-OLT.
Residential bridge VLANs support the snooping features DHCP Option 82.
The ONT supports two VLAN classification modes in residential bridge mode:
port-based VLAN
port/protocol based VLAN
Features
The residential bridge mode has the following features compared to standard
bridging:
distinguishes network and subscriber ports. Frames received from a subscriber

will always be sent towards the network and never to another subscriber. The only
exception is the traffic destined for the P-OLT.
avoids flooding by not sending broadcast to all nodes on the network.
avoids the use of the same MAC address over multiple ports. This prevents a
MAC address learned on one port from receiving service on another port and
prevents DoS and spoofing attacks.
It is important to note that the VLAN must be unique between the P-OLT and the
NSP IP router in the Ethernet network to support the residential bridge feature. If the
network configuration uses a single VLAN for two P-OLTs and an NSP router, there
could be direct subscriber-to-subscriber communication and the consequence of
broadcast and flooding.
Network and user ports
The residential bridge mode makes a distinction between network ports and user
ports, in contrast with standard bridging where all ports are treated equally. Frames
received from a user will always be sent towards the network and never to another
user.
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) will be
sent to all ports in a particular VLAN. In residential bridge mode, broadcast from the
user only goes to the network. Broadcast from the network is either passed to all ports
or blocked on the user ports. This behavior can be configured per VLAN.
Also broadcast as a consequence of flooding, which happens in case of standard
bridging when the MAC DA is unknown or in case of multicast, is avoided in
residential bridge mode.

12-5
MAC address learning
In residential bridge mode, the MAC addresses are learned in a different way than in
standard bridging. A protection is built in to prevent the use of one specific MAC
address by multiple ports in one particular VLAN.
Frame types
In residential bridge mode, only the following frame types are accepted from the user
ports:
IP over Ethernet (IPoE) (IPv4)/ARP/Reverse Address Resolution Protocol
(RARP)
PPPoE (discovery & session)
IPoE (IPv4)/ARP/RARP/PPPoE (discovery & session)
all ethernet types
Extensible Authentication Protocol Over LAN (EAPOL)
EAPOL frames are dedicated packets that are never forwarded but are processed
by the ONT.
Other frames, including multicast data frames, will be discarded.
Residential bridge with VLAN pass-through mode

This mode of residential bridging passes the VLAN tag to the residential gateway.
This mode is only supported for unstacked VLANs. This mode can also be used for
multicast.
In this mode, an ONT uses a unique C-VLAN tag to allow multiple services to be
offered to the same ONT. The residential gateway tags the services with the
appropriate C-VLAN tags and p-bits. In the downstream direction, the P-OLT sends
the S-VLAN tag received from the network to the ONT as a C-VLAN tag. The ONT
passes downstream traffic with tags unchanged to the residential gateway.
For multicast, the P-OLT can be set up to configure the multicast sources on a VLAN
to a type that allows pass-through for multicast. With this setup, the IGMP joins and
leaves are sent from the residential gateway with a specific C-VLAN tag. The P-OLT
sends downstream video streams to the residential gateway with the same C-VLAN
tag. MAC learning and unicast forwarding do not occur.
For VLAN translation in combination with EtherType classification in pass-through
mode, you can provision the EtherType, UNI C-VLAN, and NW C-VLAN
combination, as required. For information about unstacked VLANs using VLAN
translation and EtherType classification, see VLAN translation mode with
EtherType classification in section 18.3.
Residential bridge with C-VLAN forwarding mode

The residential bridge with C-VLAN forwarding mode applies to stacked VLANs
where each subscriber is identified by a combination of S-VLAN and C-VLAN.
Forwarding of downstream traffic is based on C-VLAN; the MAC destination
address is not used. In the upstream direction, the LT learns the S-VLAN, C-VLAN,
and p-bit of the packets. In the downstream direction, the S-VLAN, C-VLAN, and
p-bit identify the GEM port ID.
12-6

C-VLAN learning
A protection is built in to prevent the use of one specific C-VLAN by multiple ports
in one particular VLAN. If a duplicate C-VLAN is detected on the LT across bridge
ports, an alarm is raised.
Table 12-3 describes the layer 2 forwarding process in the LT card when using
residential bridge with C-VLAN forwarding mode.
Table 12-3 Upstream layer 2 in residential bridge with C-VLAN forwarding mode
Interface
Description
LIM
When a frame is received from the GEM port ID, the LT card checks whether there
is memory to learn the new C-VLAN. When there is memory, the LT card learns the
C-VLAN, adds the S-VLAN tag, and forwards the frame to the NT card.
LT card
The LT card verifies the uniqueness of the learned C-VLAN. If the address is unique
within its S-VLAN, there are no more actions on the LIM. If the address is not unique,
the LT card removes the C-VLAN, blocks the Bridge port, generates a notification to
the NT card, and unblocks the Bridge port when the C-VLAN ages on the first
BridgePort.
NT card
The NT card reflects the disabled state of the Bridge port in its managed data and
generates a duplicate C-VLAN alarm to the element management system (EMS). The
alarm contains the C-VLAN and the identification of the two Bridge ports involved.
VLAN cross-connect mode

The VLAN in cross-connect mode provides a connection-oriented model across the
connectionless Ethernet access network through VLANs. One VLAN contains only
one user port in VLAN cross-connect mode. A subscriber is identified across the
entire network by a VLAN ID in VLAN cross-connect mode.
In the upstream direction, the incoming subscriber port without the MAC destination
address is sufficient to identify the outgoing upstream port and the VLAN tag. This
VLAN is the port-based default VLAN configured for this subscriber port. To
identify the outgoing upstream port, the MAC destination address is required. If the
MAC DA is not yet learned, the frame will be flooded.
In the downstream direction, the C-VLAN only identifies the outgoing subscriber
port without a MAC destination address in the downstream direction.
The limitation of the VLAN in cross-connect mode is scalability. A particular VLAN
ID can be configured only once on any of the subscriber ports in the P-OLT. The
same VLAN ID can configured only once over all P-OLTs in the complete Ethernet
network to which the P-OLT is connected. If VLAN stacking is not used, the VLAN
cross-connections should only be used in small networks where the P-OLT is directly
connected to the IP router of an NSP, or for business customers.
A VLAN in cross-connect mode shares two common features with VLAN in
residential bridge mode: there will be no subscriber-to-subscriber communication
and no broadcast storms.
VLAN stacking introduces an additional VLAN layer. In VLAN stacking, an outer
layer can bundle a number of inner VLANs. The outer VLAN is the S-VLAN. The
inner VLAN is the C-VLAN.
12-7
Usage
A particular VLAN ID can be configured only once:
on any of the user ports in the ONT

over all ONTs in the complete Ethernet network to which the ONT is connected
Note VLAN stacking allows the user to use the same ID for
multiple VLANs. See chapter 18 for more information about VLAN
stacking.
Properties
Because there is only one single user, a VLAN in cross-connect mode also has the
two basic properties that differentiate iBridging from standard bridging:
no user-to-user communication is possible in the ONT

prevention of broadcast storms.
Supported models
There are several VLAN cross-connect models supported:
basic VLAN cross-connect: C-VLAN cross-connect

VLAN stacking for business users: S-VLAN cross-connect
For information about VLANs and VLAN stacking, see chapter 18.
VLAN translation and customer service flow

Formerly, incoming C-VLANs were overwritten by the S-VLAN towards the
network when unstacked mode was used. Now, when a C-VLAN is sent upstream
(using either stacked mode or unstacked mode), the same C-VLAN tag is returned.
VLAN swapping is allowed as well, and the customer can configure a mapping table
between C-VLANs and S-VLANs to accommodate C-VLAN/S-VLAN translation
according to WT-101.
For information about unstacked VLANs using VLAN translation and EtherType
classification, see VLAN translation mode with EtherType classification in
section 18.3.
12.4
Residential bridge mode configuration requirements

The residential bridge mode requires the following:
a VLAN configured in the NT card

all access links or interfaces added to the VLAN
12-8

Upstream frame forwarding

Upstream frames are bridged by the NT card in the VLAN to one of the network
interfaces. The forwarding is based on the MAC addresses learned at the network
interface. If the destination MAC address is unknown, the frame is flooded to all of
the network ports in the system.
Downstream frame forwarding

Downstream frames are bridged by the NT card in the VLAN to the access interface
based on the learned information. If the destination MAC address is unknown, the
frames are flooded to all of the access interfaces in the LAN.
Frames that are forwarded contain the VLAN tag and p-bits. The VLAN tag is the
same one as received over the interface or is the port-based default in case an
untagged or priority-tagged frame is received. The p-bits are passed transparently or
are passed with the port-based default.
Configuration requirements
Residential bridge mode provides bridging that is suitable for residential subscribers.
Different bridge ports that belong to their own ONT can be members of the same
residential bridge VLAN. Residential bridge supports voice, data, and video
services.
Table 12-4 describes the residential bridge configuration parameters on the LT card.
Table 12-4 Residential bridge LT card configuration parameters
Parameter
Description
VLAN ID
The VLAN IDs can be used for residential bridge configuration. The range is 2 to
4094; 1 and 4095 are reserved by standards. VLAN Id 4095 is reserved for
internal use.
Member bridge
port
Multiple bridge ports can be configured as member bridge ports of the

residential bridge. The GE ports on the LT card must be added as member
bridge ports by default.
Frame mixture
The member bridge ports of the residential bridge can be configured to receive
a mixture of priority and C-VLAN tagged frames. Untagged frames are
discarded.
S-VLAN
A default S-VLAN can be configured for a bridge port.
Bandwidth and
number of
queues
Sustained bandwidth, peak bandwidth, and number of queues (GEM port IDs)
can be configured for T-CONTs of the residential bridge. There can be multiple
T-CONTs associated with a bridge port (M:1). Upstream granting is based on
T-CONTs, and not on bridge ports.
Table 12-5 describes the system configuration parameters for residential bridge.

12-9
Table 12-5 Residential bridge system configuration parameters
Parameter
Description
Multiple VLANs
The 7342 ISAM FTTU allows the configuration of multiple VLANs that are used
for residential bridge. There is a limit to the maximum number of residential
bridge VLANs for each system.
Removal of
residential
bridge member
bridge port
When a bridge port is deleted as a member of the residential bridge, all MAC
entries associated with the port are automatically deleted.
Aging timer
An aging timer can be configured for aging out the dynamic entries that are
learned in a VLAN forwarding table. The aging timer applies globally to all
VLANs in the system that support MAC learning.
To minimize mis-sequenced or dropped packets when a blocked link is removed
and reconnected, ensure that the aging timer for dynamic MAC entries on the
SHub matches the root bridge forward delay timer for the SHub. For more
information, see 7342 ISAM FTTU Operations and Maintenance Procedures
Guide using TL1 and CLI.
12.5
DSCP to 802.1p
marking
The P-OLT can be configured in the QoS profile to indicate that DSCP to 802.1p
marking is enabled on a bridge port. The marking occurs at the ONTs.
DSCP to 802.1p
mapping table
The DSCP to 802.1p mapping table is configurable.
Stacked or
unstacked VLAN
VLANs can be configured as stacked or unstacked VLANs.
Residential bridge with VLAN pass-through mode

configuration requirements
For upstream traffic, the ONT must be configured to the Trusted mode so that the
C-VLAN tags are passed to the P-OLT. The P-OLT must be set up to configure the
S-VLAN to the same VLAN ID as the C-VLAN ID that the residential gateway
inserted. The same VLAN ID is used between the network and the residential
gateway.
For downstream traffic, the ONT must be configured to the Transmit Tag mode so
that the VLAN tag is passed to the residential gateway.
12.6
Residential bridge with C-VLAN forwarding mode

configuration requirements
In residential bridge with C-VLAN forwarding mode, the S-VLAN must be unique
for each PON on an LT card. The S-VLAN cannot span multiple users across
multiple PONS or LT cards. For upstream traffic, packets are tagged with their
C-VLAN ID as follows.
In trusted mode, the residential gateway tags the packets.

In untrusted mode, the ONT tags the packets.
12-10

The C-VLAN ID must be unique for each subscriber within a S-VLAN. Two
subscribers within the same S-VLAN cannot have the same C-VLAN. An alarm is
raised if a duplicate C-VLAN occurs.
12.7
VLAN cross-connect mode configuration requirements

The purpose of the VLAN cross-connect mode is to create a bit pipe between a
VLAN configured at a network interface and a subscriber interface.
The VLAN cross-connect mode requires the NT card to be configured with a VLAN
and only one access interface can be associated with this VLAN. The unicast frames
pass transparently.
In a cross-connect VLAN, a single bridge port is associated with a single VLAN.
Only one bridge port can be configured in a cross-connect VLAN. Table 12-6
describes the cross-connect configuration parameters.
Table 12-6 Cross-connect configuration parameters
Parameter
Description
Cross-connect
VLAN
The P-OLT supports the configuration of a VLAN as a cross-connect VLAN.
MAC learning
The LT card performs MAC learning in a cross-connect VLAN. There are no rules
for MAC movement within the cross-connect VLAN.
Limit of
cross-connect
VLAN
The P-OLT supports a limit on the maximum number of cross-connect VLANs

allowed in each LT card.
Stacked S-VLAN
The cross-connect VLAN supports configuration of the stacked S-VLAN.
Forwarding
When the frames sent through the bit pipe are IPoE frames, various protocol
messages such as DHCP or IGMP can be snooped. These functions are disabled so
that these frames are handled as data traffic.
Due to this handling, there can be downstream multicast frames, but there is no
corresponding multicast tree. When there is no multicast tree, the frames are flooded
to all access interfaces. In VLAN cross-connect mode, since there is only one access
interface, all frames flood this access interface. The multicast frames pass
transparently.
The broadcast frames are forwarded in the same way as multicast frames.
In this configuration, the layer 2 control protocol frames are discarded. The layer 2
frames are link related and are not handled within the scope of a VLAN.

12-11
12.8
Forwarding unicast traffic in the LT card

This section provides information about the layer 2 forwarding process taking place
in the LT card when using either residential bridge or cross-connect mode.
Residential bridge mode upstream

Table 12-7 describes the layer 2 forwarding process in the LT card when using
residential bridge mode.
Table 12-7 Upstream layer 2 forwarding in residential bridge mode
Interface
Description
LIM
When a frame is received from the GEM port ID, the LT card checks whether there
is room to learn new MAC addresses. When there is room, the LT card learns the
MAC address, adds the S-VLAN tag, and forwards the frame to the NT card.
LT card
The LT card verifies the uniqueness of the learned MAC address. If the address is
unique within its VLAN, there are no more actions on the LIM. If the address is not
unique, it removes the MAC address, installs a filter to discard further packets from
the BridgePort with the same source MAC address, generates a notification to the
NT card, and removes the filter when the MAC address ages on the first BridgePort
where the source MAC address was learned.
NT card
The NT card reflects the disabled state of the BridgePort in its managed data and
generates a duplicate MAC alarm to the element management system (EMS). The
alarm contains the MAC address and the identification of the two BridgePorts
involved.
Residential bridge mode downstream

When traffic is going downstream in residential bridge mode, the LT card uses the
VLAN tag and the destination MAC address to decide on the forwarding. The LT
card determines the appropriate GEM port ID to forward the traffic to. The
forwarding is based on the S-VLAN tag, destination MAC address, and priority.
Cross-connect unicast upstream traffic

In cross-connect mode, the number of MAC addresses are limited and duplicate
MAC addresses are not allowed. A MAC address must be unique for each VLAN. It
is verified at configuration time that only one BridgePort belongs to the VLAN.
Cross-connect unicast downstream traffic

In cross-connect mode, the LT card forwards all downstream traffic within the
VLAN to the BridgePort, including unicast frames, broadcast frames, and multicast
frames.
12-12

12.9
MAC filters
The 7342 ISAM FTTU uses global MAC filters. The filters are applied to the
BridgePort to accept or deny preconfigured MAC source and destination addresses.
The NT card supports the filter function.
When both specific and generic MAC filters are enabled for the same port and
VLAN, only the specific filter counter is incremented.
12.10
Pause frames
Pause frames are used for flow control as specified in IEEE 802.3x standard. The LT
card does not generate pause frames when it cannot process all of the data frames
from the NT card. The LT card discards the data frames it cannot process without
sending a pause frame. This applies to both upstream and downstream traffic.
Although there is no pause frame to indicate the discard of the unprocessed frames,
the 7342 ISAM FTTU performance monitoring function collects information about
the events.
The NT card normally does not send pause frames to the LT card. If the LT card
receives a pause frame, the pause frame is automatically processed.
The NT card can receive and process pause frames. In response to a pause frame, the
NT card stops generating upstream traffic on the interface that sends the pause frame
for the time indicated in the pause frame. Traffic is buffered and QoS-aware
scheduling is performed at due time.
12.11
Subscriber scalability
To enable subscriber scalability, the PON must be able to support up to 288 UNIs.
This implies learning of a large number of MAC addresses will be required. To
address the MAC learning limitations of the LANX (up to 16k MACs), a capability
has been introduced to support disabling of MAC learning. The subscriber scalability
implementation also makes use of T-CONT sharing across multiple UNIs.
Implementation considerations
MAC learning must be disabled on a range of VLANs on the SHub, in order to
support subscriber scalability. In this mode, the SHub can forward downstream
packets based on the VLAN ID, without reference to a destination MAC address.

12-13
Disabling of MAC learning on a range of VLANs places the following limitations on

the VLANs:
For cross-connect (CC) VLANs, MAC learning can be disabled on both network
and user ports. For residential bridge (RB) VLANs, subscriber scalability is
supported by disabling MAC learning on user ports only (ports towards the LT).
Because the network ports continue to learn, the number of network ports or
trunks in these VLANs is unlimited.
Each VLAN must be restricted to a single LT. This limitation is required to avoid
flooding of unicast traffic to multiple LTs.
In the case of CC VLANs, it is recommended to limit the VLAN to a single
network port (or trunk). This will avoid flooding of unicast traffic to multiple
network ports. If multiple network ports are configured, they should be
configured either as a link aggregation group (trunk), or using STP protocol. If a
link aggregation group is used, unicast traffic will be forwarded on a single link
of the group. If STP is used, the 7342 ISAM FTTU should be configured as
non-root, so that redundant links will be placed in blocking state. Then unicast
traffic will be forwarded on the single link in forwarding state
Note Packet processing behavior is inherited from the VLAN
mode (RB or CC) specified for the VLANs in the range.
The downstream forwarding for a VLAN range that has MAC learning disabled can
be configured in one of two modes:
Flood to the LTwhen user and network ports are disabled, DLF traffic is Layer
2 forwarded to user and network member ports without learning the SMAC.
When user ports only are disabled, traffic is forwarded after SMAC learning.
Redirect to the LTwhen user and network ports are disabled, DLF traffic is
Layer 2 forwarded to user but not to other network member ports, without SMAC
learning. When user ports only are disabled, traffic is forwarded after SMAC
learning.
These two modes provide different handling towards the LT links, which are
configured as a link aggregation, with redundant links to both NTs.
The redirect mode has the advantage that the selection of the egress LT port is
decided in the ingress chip. Flooding results in packets being sent to both NTs, which
then use hashing on trunk block masks to determine whether to forward or not.
Note 1 All residential features such as anti-spoofing and
authentication are fully functional when subscriber scalability is

implemented.
Note 2 The GLT4 can manage 1024 IGMP packets per second with
a 40% processor loading. Assuming 288 UNIs on all 4 PONs (1152

UNIs), this corresponds to a maximum of approximately 0.9 IGMP
packets per subscriber per second, on average.
12-14

For subscriber scalability, the Ethernet services configuration that supports T-CONT
sharing across multiple UNIs on an ONT for a single service must also be
implemented, to enable subscribers of the same service to share a T-CONT.
Figure 12-1 illustrates this configuration model. See chapter 25 for additional
information about Ethernet services.
Figure 12-1 Subscriber scaling using T-CONT per Service with GEM port per subscriber
PON
OLT
Tag
GEM
Tag
Tag
Tag
ONT
GEM
GEM
Tag
GEM
T-CONT
T-CONT
WRR
GEM
Tag
GEM
GEM
Tag
GEM
Tag
GEM
Tag
UNI
UNI
Tag
Tag
Tag
Tag
Uplink
Tag
Tag
Tag
Tag
GEM
GEM
T-CONT
T-CONT
GEM
WRR
GEM
Tag
GEM
GEM
Tag
GEM
Tag
UNI
UNI
Tag
Tag
Tag
Tag
20070
Table 12-8 lists subscriber scaling that can be implemented based on T-CONT per
service and GEM port per subscriber usage and bridging table limits.
Table 12-8 Subscriber scaling based on T-CONT and GEM usage
Subscribers
per ONT
Services
MAC
address
Maximum
subscribers
per PON
T-CONT
determined
limit
GEM
determined
limit (1)
Bridging
table
determined
limit
24
288
3520
288
318
24
239
3520
288
239
24
216
2640
216
239
Note
(1)
Assumes worst case with each priority in a separate GEM port.

12-15
Restrictions and limitations

Certain restrictions and limitations should be considered when disabling MAC
learning to implement subscriber scalability.
Due to a shortage of packet processing hardware filters, subscriber scalability

configuration is permitted on a VLAN Range only, and not individual VLANs.
The VLANs in the range and the VLAN ports must be configured on the SHub,
12-16
with all other parameters specified, and all the VLANs in the range must use the
same LT port.
The VLAN mode must be the same (RB or CC) for all VLANs in the range.
For VLANs in the range, user-to-user communication must be disabled because
MAC learning will be disabled on user ports.
Layer 3 functionality is not supported when MAC learning is disabled on user
ports. The outgoing port information of Layer 3 Nexthop MAC cannot be
determined, so you cannot configure VLANs in the range with a Layer 3
interface.
The upstream traffic intended for a specific network port will be duplicated on
other network ports in forwarding state, resulting in bandwidth wastage on those
network ports. Therefore, it is strongly recommended that the network ports be
configured with a single port (or trunk) in forwarding state.

13 NT redundancy
13.1 Overview
13-2
13.2 Single bridge port configuration
13-2
13.3 Multiple bridge port configuration
13-3
13.4 Multiple upstream switches configuration

13.5 Redundancy between NT and LT cards
13.6 Dynamic data synchronization

13-3
13-4
13-4
13-1
13 NT redundancy
13.1
Overview
This chapter provides information about the redundancy of the NT cards that use a
load-balancing scheme. The information includes the architectural aspects of the LT
cards that are required to support the NT redundancy.
Note The P-OLT provides a fast switch-over in case of link or
equipment failures. The operator must ensure that other upstream
devices such as switches and routers do provide a similar fast
switch-over to ensure end-to-end fast switch-over in case of link or
equipment failures. Such a fast switch-over capability will be critical
for voice, video, and CES services.
TL1 and CLI for more information.
13.2
Single bridge port configuration

7342 ISAM FTTU can be configured as a single bridge port connected to an
upstream switch. Figure 13-1 shows the network topology of the single bridge port
connected to an upstream switch.
Figure 13-1 Single bridge port network topology
Upstream switch
NT-A
NT-B
18196
The links as a whole are configured as a single 802.3ad link aggregation group so
that there is one single bridge port connecting 7342 ISAM FTTU and the upstream
switch. The links are terminated on NT-A and NT-B.
The links work in a load-balancing mode. In this mode, a flow is always assigned to
the same link. There are no sequencing issues. If one of the links fails, the other links
will share the remaining load. The bridge port is kept active.
If an NT card fails, two of the network links in the group will fail. The network bridge
port is still active because the other NT card will share the remaining load.
The time to detect the link failures and reconfigure the link group is less than a
second. There is no need to relearn any of the network MAC addresses after a link
failure or recovery since the state of the bridge port does not change.
In this mode, there is a single bridge port running the STP. When there is a failure of
a link of an NT card, the STP state is not affected. There is no need to recompute a
new spanning tree. The 7342 ISAM FTTU platform implements a distributed STP
algorithm that runs on NT-A and NT-B at the same time.
13-2

13 NT redundancy
13.3
Multiple bridge port configuration

7342 ISAM FTTU can be configured as multiple bridge ports connected to one
upstream switch. Figure 13-2 shows the network architecture of the multiple bridge
port configuration.
Figure 13-2 Multiple bridge port network topology
Upstream switch
NT-A
NT-B
18197
The links are grouped into separate 802.3ad link aggregation groups. One group is
terminated on NT-A and the other is terminated on NT-B. Each link aggregation
group runs RSTP. When forwarding NT-A fails, RSTP reconverges.
Both bridge ports run RSTP, but only one of the bridge ports is in the forwarding
state. This is the way used by the RSTP algorithm to prevent a loop between the
7342 ISAM FTTU and the upstream switch.
Note RSTP must be disabled between the upstream switch (such
as 7450 Ethernet Service Switch) and the G6 gateway.
When a link fails on the primary NT card, the bridge port is kept active by the other
links in the group.
When one of the NT cards fails, there is a need to recompute a new spanning tree
since the STP state is affected. The recomputing stops the traffic flow for a few
seconds when the STP algorithm converges. Use of the RSTP algorithm can speed
up the convergence.
The failure of an NT card also requires the network addresses to be relearned after
the switch-over, since no traffic has passed through the secondary NT card. If link
aggregation is used on the LTs, subscriber MAC addresses do not need to be
relearned by NT-B.
The disadvantage of this connection topology is that only half of the network links
are used at any given time. There is also a short service interruption when there is a
card failure.
13.4
Multiple upstream switches configuration

7342 ISAM FTTU can be configured into multiple link aggregation groups
connecting to multiple upstream switches. Figure 13-3 shows the multiple upstream
switches.

13-3
13 NT redundancy
Figure 13-3 Multiple upstream switches
Upstream
switch 1
NT-A
Upstream
switch 2
NT-B
18247
In this configuration, each link aggregation group functions as a bridge port. Each
link aggregation group runs RSTP.
When the forwarding NT-A fails, RSTP reconverges.
Note RSTP must be disabled between the upstream switch (such
as 7450 Ethernet Service Switch) and the G6 gateway.
13.5
Redundancy between NT and LT cards

The 7342 ISAM FTTU supports redundancy between the NT and LT cards.
The redundancy is supported through static link aggregation. Since each LT card
supports several ONTs and subscribers on each ONT may have different MAC
addresses, flow assignment is based on source MAC and destination MAC.
If one of the NT cards fails, the subscriber MAC and multicast membership is
automatically available on the secondary NT card.
RIPv2 supports redundant NT cards. When that standby NT card comes up, the
RIPv2 module can be restarted and no reprovisioning is required on the standby NT.
13.6
Dynamic data synchronization

Dynamic data is synchronized between the two NT cards to minimize service
interruption if one of the NT cards fails.
Dynamic data includes the following:
MAC addresses in the FDB tables that have been learned on a port
IGMP multicast membership data
unsaved configuration data
authentication data
When link aggregation is used with one link from each NT card, all MAC addresses
are learned on both links.
13-4

13 NT redundancy
The NT cards synchronize the AAA server and RADIUS client information. With
the synchronization, the operator-initiated disconnections and subscriber-initiated
disconnections can work normally after a switch-over.
If the operator performs provisioning tasks on the layer 2 switch, there is a window
of time when the two NT cards are out of synchronization until the data is copied to
the standby NT card. During this window, the standby NT card is in cold-standby
state and the SWCAP alarm is raised. However, it is possible that this alarm is not
visible if the amount of provisioning is small and the synchronization can therefore
be very quick.
With RIPv2, there is no need to dynamically synchronize the RIPv2 database when
the standby NT comes up.

13-5
13 NT redundancy
13-6

14 Proxy ARP
14.1 Overview
14-2
14.2 Functional description

14.3 Proxy ARP process flow
14.4 ARP table persistence
14.5 Static ARP IP address
14-2
14-2
14-3
14-3

14-1
14 Proxy ARP
14.1
Overview
This chapter provides a detailed description of the proxy address resolution protocol
(ARP) used in the 7342 ISAM FTTU.
14.2
Proxy ARP provides a proxy that answers ARP requests intended for another host
and routes packets to the destination host. This function helps hosts on a subnet reach
remote subnet hosts without configuring routing or a default gateway.
In the 7342 ISAM FTTU, a host on a customer premises equipment (CPE) from a
subscriber residence sends an ARP request as a broadcast frame. After verifying that
the host IP address and MAC address are valid, the LT forwards the request upstream
to the gigabit Ethernet (GE) port. The upstream edge router responds to the ARP
request with a unicast message that is forwarded to the designated host based on
MAC lookup. No special ARP handling is required to forward a unicast message
downstream to the host.
However, when the edge router sends an ARP request for a host on a CPE, special
ARP handling is required on the LT card because broadcast frames are not forwarded
downstream in residential bridge VLANs. This special ARP handling is the proxy
ARP function.
14.3
Proxy ARP process flow

The proxy ARP function is activated on a residential bridge VLAN when the DHCP
relay is enabled on the residential bridge VLAN. The proxy ARP function does not
work if DHCP relay is not enabled. The proxy ARP process works as follows:
14-2
After snooping the DHCP ACK packages, the LT adds the IP address to the lease
table and creates an ARP entry with the corresponding MAC address.
After the ARP entry ages out, the LT periodically sends ARP requests to the
allocated IP address on the bridge port that sent out the DHCP request message.
If an ARP response is received, the corresponding ARP entry is refreshed in the

ARP table for the ARP aging period. The forwarding table of the VLAN is also
updated with the MAC address of the client (host) for the same period.
If there is no response to an ARP request, the ARP entry and FDB entries are
de-activated. However, the IP address in the lease table is not deleted. The IP
address is deleted only when the lease period expires.
If the client resumes sending traffic after being inactive, the LT activates the
ARP and FDB entries for the client. The client does not need to initiate a new
DHCP request.
If the edge router sends an ARP request for a client, the LT sends an ARP
response to the edge router with the MAC address of the CPE, after verifying that
there is an entry corresponding to the IP address in the ARP table.

14 Proxy ARP
14.4
After snooping DHCP release packages, the LT deletes the MAC entry in the
ARP table after verifying that an entry corresponding to the client IP address is
in the lease table.
After the lease expires, the IP address in the lease table and the MAC entry in the
ARP table are deleted.
ARP table persistence

The DHCP force renew mechanism described in the preceding process is not
supported by all residential gateways and hosts. This can be resolved by making the
ARP tables persistent on the network termination (NT) card.
Persistent ARP tables are stored in the file system on the NT cards. Persistent ARP
tables are available to the line termination (LT) cards after an LT restart or LT
replacement. Because the file system is replicated across the two NT cards, the ARP
table can also survive an NT switch-over or NT replacement.
If operating personnel want to replace both of the NT cards, they must back up the
database and restore it after installing the new NT cards. When the ARP file is
restored from the element management system (EMS), the NT card downloads the
ARP tables to the LT cards.
After an NT switch-over, the newly activated NT performs an audit of the ARP table
by retrieving the tables from the LTs and updating any entries that are missing in its
database.
The LT cards need to download the ARP tables from the active NT after a restart.
The LT cards need to check if any entries have aged out and flush the aged-out
entries from the table.
14.5
Static ARP IP address

The 7342 ISAM FTTU supports the addition and deletion of a static IP address in a
residential bridge VLAN that is enabled for the DHCP relay agent function. A static
entry can be added to the ARP table either manually by an operator using a TL1
command, or dynamically by the system using ARP snooping (see ARP snooping).
When the proxy ARP and static IP are used on the VLAN, the DHCP packets are
relayed in the VLAN without adding Option 82 parameters to the packets.
Static IP addresses can be created in the ARP table for a specific bridge port. Periodic
ARP requests can be sent for static IP addresses to learn the MAC addresses of the
hosts.
If the DHCP server snoops an IP address that is a static IP address in the VLAN, the
static IP address takes precedent over dynamic IP addresses. If the DHCP server
assigns the same IP address as a static IP address, the static IP address overwrites the
dynamic IP address.
TL1 and CLI for static ARP configuration procedures.

14-3
14 Proxy ARP
ARP snooping
The ARP snooping function on the LT snoops the ARP response to an ARP request
from a host on the subscriber side. The 7342 ISAM FTTU uses this function to learn
the IP address and MAC address of a host, and dynamically adds an entry for the host
in the ARP table. To avoid service theft, the entry is made static so that the IP address
is fixed to the ONT UNI.
The ARP snooping function can snoop multiple IP addresses on the same ONT UNI.
The 7342 ISAM FTTU limits the number to the maximum number of MAC
addresses allowed on the ONT UNI. To refresh the ARP table, the Proxy ARP
function periodically sends an ARP request to a snooped IP address. After a response
is not received to three consecutive ARP requests, the Proxy ARP function removes
the entry from the ARP table.
The ARP snooping function is enabled on the LT on a per VLAN basis, and is useful
for handling deployments of subscriber services, such as Video-on-Demand, where
IP addresses that are statically assigned to hosts cannot be entered manually in the
system.
14-4

15 QoS
15.1 Overview
15-2
15.2 QoS infrastructure
15-2
15.3 Traffic classification and marking elements

15.4 Traffic policing elements
15-8
15.5 Congestion management elements

15.6 Traffic shaping elements
15.7 QoS configuration
15-4
15-9
15-20
15-25
15.8 Downstream queuing and scheduling

15.9 Upstream queuing and scheduling
15-26
15-29
15.10 Recommended DSCP to p-bit mapping

15-32
15-1
15 QoS
15.1
Overview
This chapter describes the QoS functions used by the 7342 ISAM FTTU.
The 7342 ISAM FTTU ONT and OLT uses the 802.1p bits QoS model, which relies
on traffic segregation into classes of service (CoS) by p-bit. Each traffic class can be
configured with different QoS characteristics, insuring preferential treatment for
higher priority traffic on the network, such as video and voice traffic.
TL1 and CLI for QoS configuration procedures.
15.2
QoS infrastructure
QoS provides the ability to differentiate levels of service priority by CoS. A service
level is typically described in terms of network delay, bandwidth, and jitter. For
example, much data traffic is tolerant of delays and packet drops. However, voice
and video are intolerant of jitter. Video can also be bursty at times.
To ensure that traffic is serviced according to its behavior and to service level
requirements, QoS provides support to the following functions:
classifying and marking traffic according to type and importance based on

policies and the behavior of traffic
policing traffic by limiting the egress and ingress traffic
managing congestion by prioritizing traffic based on marking and by configuring
queuing and scheduling that respond to traffic classes
traffic shaping by specifying guaranteed and non-guaranteed traffic rates to
maximize the use of bandwidth
Figure 15-1 shows the high-level view of the QoS infrastructure that is implemented
on the 7342 ISAM FTTU.
15-2

15 QoS
Figure 15-1 QoS infrastructure
Upstream scheduling
OLT
ONT
Guaranteed BW
Extra BW
GEM port
Network
port
NT SP/
WRR
GEM port
T-CONT
eHCL LT SP/
WRR
GEM port
DBA
GPON
scheduler
GEM port
GEM port
SP/
WRR
Classifier
Service
port
T-CONT GEM port
Grants
Downstream scheduling
OLT
ONT
GEM port
Network
port
NT SP/
WRR
eHCL
LT SP/
WRR
GEM port
GPON
SP
Service
port
GEM port
19084
Elements of the QoS infrastructure are hardware, software, and data-related, and are
listed by function in Table 15-1.
Table 15-1 QoS infrastructure elements
Function
Element
Traffic classification and marking
CoS
P-bit
DSCP
P-bit to CoS mapping
QoS marker and session profiles
Traffic policing
Traffic meter
Ingress rate
Maximum burst size
Traffic flow
Egress rate
(1 of 2)

15-3
15 QoS
Function
Element
Congestion management
Switch
Ports
Scheduler and queues
P-bit to queue mapping
Traffic scheduler
Downstream rate limiting to ONT
Priority queue profile
T-CONTs and GEM ports
Traffic shaping
Bandwidth profile
Reserved bandwidth
Dynamic bandwidth allocation (DBA)
(2 of 2)
15.3
Traffic classification and marking elements

Traffic classification and marking elements described in this section are:
CoS
P-bit
DSCP
CoS
A CoS is a grouping of similar traffic types that has its own level of service priority.
The 7342 ISAM FTTU recognizes up to eight CoS.
P-bit
The system uses the priority-bit (p-bit) to differentiate traffic into CoS. The p-bit is
an integer value from 0 to 7 that is either encoded in the tag header of a
priority-tagged and VLAN-tagged frame, or derived from the DSCP number in the
IP header of an untagged frame.
Traffic is marked with a p-bit according to its type and importance. Time-critical,
delay-sensitive, and jitter-sensitive traffic, such as network control data, voice, and
video, receive the higher value p-bits. Less time-sensitive traffic, such as data,
receive the lower value p-bits.
15-4

15 QoS
Traffic types include ethernet data, IGMP, multicast, voice signaling, voice bearer,
CES, and OMCI.
Note The following definitions apply.
An untagged frame is a frame that does not carry a tag header

following the source MAC address.
A priority-tagged frame is a frame that carries a tag header with
priority information, but with no VLAN ID.
A VLAN-tagged frame is a frame that carries a tag header with
both priority information and VLAN ID.
DSCP
The DSCP is an integer value from 0 to 63 that is encoded in a six-bit field in the IP
header. The six-bit field allows for 64 (26 = 64) possible forwarding behaviors. Each
forwarding behavior maps to one of eight p-bit values.

A DSCP to p-bit mapping maps blocks of DSCP numbers to p-bits. The mapping is
used to mark untagged frames with their p-bit. When an upstream untagged IP frame
from a trusted subscriber is received, the mapping is used to convert the DSCP
number in the IP header of the frame to a p-bit.
You can configure DSCP to p-bit mappings at the following two levels:
system-wide level
ONT UNI port level
See Table 15-14 for the Alcatel-Lucent recommended mapping of DSCP numbers to
p-bits.
System default DSCP to p-bit mapping
Blocks of DSCP numbers are mapped to p-bits to serve as system defaults for ONT
UNI ports.
Customized DSCP to p-bit mapping
Customized mappings of DSCP numbers to p-bits can be configured for an ONT

UNI port.

The P-bits 0 to 6 are system mapped to one of eight CoS (or queues). P-bit 7 is
reserved for management traffic, such as OMCI. The mapping is used for upstream
traffic at the NT.

15-5
15 QoS
C-VLAN to S-VLAN p-bit translation

An optional p-bit translation profile can be configured and associated with a stacked
S-VLAN, to map C-VLAN p-bit values (0 to 7) to S-VLAN p-bit values (0 to 7). The
LT uses the translation profile to perform priority marking of upstream traffic.
The LT adds an outer S-VLAN tag to the frame, and uses the associated translation
profile to derive the corresponding S-VLAN p-bit. An S-VLAN that is configured in
this mode could be used by either an EVC flow or an HSI service.
Figure 15-2 shows an example of a C-VLAN to S-VLAN p-bit translation that is
performed at the LT.
Figure 15-2 C-VLAN to S-VLAN p-bit translation at the LT
7342 OLT/LT
7750
ONT
LiveBox
HSI Traffic
SVLAN = 1035/pbit = 0
HSI Traffic
HSI Traffic
CVLAN = 835/pbit = 0
VoD Traffic
VoD Traffic
VoD Traffic
TVNum Traffic
TVNum Traffic
TVNum Traffic
VoIP Traffic
VoIP Traffic
VoIP Traffic
20056
UNI-side to network-side p-bit translation profile

When configuring Ethernet services flows, a p-bit translation profile can be applied
to a flow for the ONT, to translate priority marked traffic from the UNI-side
(subscriber) to network-side (network service provider) p-bit values.
Traffic is directed toward a GEM port, based on the specified p-bit mapping, the
outer VLAN key, and the priority queue profile. After the VLAN tagging and
translation process is complete, the specified p-bit value is used to map to a specific
GEM port.
The application of p-bit translation depends on the type of flow. For a default flow
using p-bit translation, all UNI-side p-bits must translate to only one network-side
p-bit in the p-bit translation profile.
A wildcard flow accepts any outer-tag VLAN-ID entering the UNI and requires a
p-bit mapping profile to translate UNI-side to network-side p-bits. If multiple
wildcard flows are configured on the same ONT UNI port, the flows cannot have
overlapping UNI-side p-bits in the p-bit translation profile.
See chapter 25 for additional information about Ethernet services. For flow and p-bit
configuration details see the 7342 ISAM FTTU Operations and Maintenance
Figure 15-3 shows an example of one-to-one p-bit translation at the ONT with
VLAN translation also supported.
15-6

15 QoS
Figure 15-3 One-to-one p-bit translation, single-tagged frames
Upstream single-tagged with VID translation and P-bit translation
From UNI
C-VLAN ID C-P-bit
C-VLAN ID C-P-bit
To GEM Port
(C-VID), C-P-bit)
Translate 1:1
Downstream single-tagged with VID translation and P-bit translation
To UNI
C-VLAN ID C-P-bit
C-VLAN ID C-P-bit
From GEM port
Translate 1:1
20079
Figure 15-4 shows a many-to-one p-bit translation that uses a many-to-one mapping
of UNI-side to network-side p-bit values. For example, you might use this when a
flow is configured as the default flow for the UNI.
Figure 15-4 Many-to-one p-bit translation, single-tagged frames
Upstream single-tagged with 1:1 translation and N:1P-bit translation
From UNI
Default
C-VLAN ID C-P-bit
C-VLAN ID C-P-bit
Translate 1:1
Overwrite
Downstream single-tagged with VID translation and P-bit pass through
From UNI
C-VLAN ID C-P-bit
C-VLAN
C-VID ID C-P-bit
From GEM port
Translate 1:1
Pass through
20080

The QoS marker profile establishes policies for marking and tagging downstream
and upstream frames at the ONT to guarantee various levels of service.

15-7
15 QoS
A QoS marker profile is configurable for an ONT UNI port, and includes information
such as:
default p-bit for untagged upstream traffic

downstream tagging behavior
upstream tagging behavior
The QoS session profile associates a QoS marker profile with an ONT UNI port. The
same marking and tagging rules are applied to all services across an ONT UNI port.
15.4
Traffic policing elements

Traffic policing is a process that measures the transmission rate of traffic across a
port and compares the rate to acceptable threshold levels. Traffic policing can be
implemented at a network port to monitor ingress traffic for ingress rate and
maximum burst size, and egress traffic for egress rate.
Traffic policing elements described in this section are:
Traffic meter
Ingress rate
Maximum burst size
Traffic flow
Egress rate
Traffic meter
Traffic meters specify both the maximum rate of traffic that can ingress a SHub port,
and the maximum burst size allowed. Traffic meters are applied to network ports.
Ingress rate
Ingress rate is the maximum rate of traffic that can ingress a port. Ingress rate is
configurable for a network port, and can be monitored for different traffic flow types.
Maximum burst size

Maximum burst size is the maximum number of bytes that can travel through a port
without causing packet loss, and is configurable for a network port.
Traffic flow
Ingress traffic can be monitored for the following traffic flow types:
15-8
portall traffic on a port

VLANall traffic associated with a VLAN
VLAN and p-bitall traffic associated with a VLAN and having the same p-bit
VLAN and DSCPall traffic associated with a VLAN and having the same
DSCP number
15 QoS
Egress rate
Egress rate is the maximum rate of traffic that can leave a port. A network port can
be configured for egress rate, and can be enabled or disabled to receive pause frames.
15.5
Congestion management elements

The p-bit value directs the assignment of traffic to queues. Queues can be sized and
scheduled to meet the service needs of traffic classes. Traffic schedulers are
configurable by port.
Congestion management elements described in this section are:
Switch
Ports
Traffic scheduler
Switch
The switch is a device with ports that directs incoming data from multiple input ports
to the output port that will take it to its final destination. The switch performs the
following tasks:
schedulingdeciding which packet to send when packets from multiple input

ports are intended for the same output port
data forwardingforwarding the packet to the intended output port, under the
control of the scheduler
queue managementmanaging queues to minimize packet loss rates and to
optimize throughput
The P-OLT hardware has two switch devices: a large switch located on the NT card,
which is called the SHub, and a small switch located on the LT card. Queuing and
scheduling functions can be performed by both switches if required. The size of the
switch varies based on card type. For switch sizes, see Chapter 4.
The switch on the LT card operates at electrical speeds in both upstream and
downstream directions, although congestion may occur on individual ports.

15-9
15 QoS
Ports
The 7342 ISAM FTTU receives and transmits data through external ports, internal
ports, and virtual ports.
External ports include SHub ports on the NT and ONT UNI ports.
SHub ports include 1 Gb/s and 10 Gb/s ports located on the NT.
ONT UNI ports include Ethernet ports (RJ-45), VDSL2 ports, MoCA ports, DS1/E1
ports, POTS port (RJ-11), and RF video ports.
Internal ports include GE and OBC ports, which are implemented by the Ethernet
switch.
Virtual ports are GEM ports that are used to carry traffic across the GPON from
the LT card to the ONT and from the ONT to the LT card.

A port is equipped with a scheduler, which has up to eight queues. The queue is
where the data is held while it awaits forwarding; the scheduler is what decides
which queues to process and in what order. Each queue is provided with a size and a
weight.

A mapping of p-bits to queues directs traffic of a specified CoS to one of eight
queues.
Mappings of p-bit to queues are configured at the LT, ONT, and service levels.
P-bit to queue mapping at the LT
A single p-bit to queue mapping directs the queuing of downstream and upstream
traffic at the LT:
from the LT to the GPON

from the LT to the NT
The mapping of p-bits 0 through 6 to queues 1 through 7 is configurable. Queue 0 is
reserved for internal VLAN (4095) traffic; p-bit 7 is automatically mapped to the
same queue as p-bit 6.
P-bit to queue mapping at the ONT
At the ONT, a mapping of p-bit to queues is included in the downstream rate limiting
scheduler for the ONT.
P-bit to queue mapping at the service level
At the service level, a mapping of p-bit to queues is included in the priority queue
profile associated with the service, and applies to upstream traffic on the service.
15-10

15 QoS
Traffic scheduler
A customized traffic scheduler provides more flexible scheduling capabilities over
the system default traffic scheduler. Traffic schedulers regulate the depth and
scheduling of queues of a port, and can be configured for interface ports at the NT
and at the LT. Interface ports include:
at the NT
from the NT to the LT
from the NT to the network
at the LT
The traffic scheduler specifies:
weight of a queue
internal buffer size in bytes of a queue
size of buffer to be shared dynamically among the queues
The internal buffer size affects latency, as latency increases with size of queue.
The weighted priority of a queue determines how the queue is scheduled. A queue
can be scheduled in one of two ways:
strict priority (SP)

weighted round robin (WRR)
SP scheduling ensures that highly critical or sensitive traffic is forwarded with
minimal delay. WRR scheduling gives precedence to higher priority traffic and
ensures that lower priority traffic is serviced satisfactorily. When the port is not
congested, all weighted queues are treated equally. When congestion occurs, the
weight is used to give weighted priority to higher priority traffic.
Traffic scheduler at the NT
Table 15-2 identifies scheduling of queues at the NT by weighting factor.

Table 15-2 Scheduling of queues at the NT by weighting factor
Weight
Scheduling
Queue 0
SP
Queue with a weight of 0

Queue with a weight of 1 to 15
WRR
Not used
Traffic scheduler at the LT
Table 15-3 identifies scheduling of queues at the LT by weighting factor.

15-11
15 QoS
Table 15-3 Scheduling of queues at the LT by weighting factor
Weight
Queue 0
Scheduling
(1)
SP

Queue with a weight of 1 to 15
WRR
Not used
Note
(1)
Queue 0 is always SP and is reserved for internal VLAN traffic.
Where a traffic scheduler is not configured for a port at the LT, the system default
traffic scheduler is assumed. Table 15-4 identifies the parameter values in the system
default traffic scheduler at the LT and default p-bit mapping.
Table 15-4 Default traffic scheduler at the LT
Queue
Weight
Size
P-bit mapping
11648
11648
6, 7
11648
4, 5
11648
2, 3
11648
0, 1
16 (not used)
(2)
16 (not used)
(2)
16 (not used)
(2)
Dynamic area
58240
(1)
Notes
(1)
Queue 0 is reserved for internal VLAN traffic.
(2)
P-bits are not assigned to unused queues.

Downstream rate limiting controls the rate of traffic sent to the ONT, to insure that
the ONT does not receive more traffic than its ONT UNI ports can support.
Figure 15-5 illustrates downstream rate limiting as implemented on the LT card.
15-12

15 QoS
Figure 15-5 Downstream rate limiting
OMCI
Voice
Multicast
traffic
spacer
SP
SP
WFQ
WFQ
Queue 0
ONU1
...
Queue 7
SP/
WFQ
ONT 1 rate shaper

Packet
dispacher
GPON
SP/WFQ
scheduler
Queue 0
ONU2
...
Queue 7
SP/
WFQ
WFQ
SP/
WFQ
WFQ
GPON
ONT 2 rate shaper

...
Queue 0
ONU64
...
Queue 7
ONT 64 rate shaper
18982
Elements of downstream rate limiting include:
multicast traffic spacer

OMCI queue
per-ONT rate shaper
GPON SP/WFQ scheduler
Multicast traffic spacer
The multicast traffic spacer consists of a single queue. Because a guaranteed portion
of the PON bandwidth is provisionally reserved for multicast service (see Reserved
bandwidth), and the number of IP multicast streams is provisioned by ONT, the need
to rate limit multicast on an ONT basis is not required. Therefore, multicast is rate
limited on a PON basis.
OMCI queue
The OMCI queue consists of a single queue; the queue contains all downstream
communication from the P-OLT to the ONT. The input to the queue originates solely
from the LT card processor.

15-13
15 QoS
Per ONT rate shaper
The traffic management module on the LT card provides 64 shaper blocks per GPON
interface, one for each ONT. Within each shaper block are eight queues, with a
flexible scheduling mechanism (SP or WRR) for each queue. Each queue is
configurable for scheduler weight, and for maximum and guaranteed buffer sizes to
limit the depth of the queue.
A queue operates with a tail drop discard mechanism. If the queue size reaches the
configured maximum buffer size, or if the buffer pool has no remaining buffer space,
arriving packets are dropped until the queue has room to accept the packets.
Downstream rate limiting is configured on an ONT to operate in one of two ways:
rate limit on a per-ONT basis

rate limit on a per-service basis
Downstream rate limiting on a per-ONT basis limits the total of all downstream
traffic to an ONT to a certain rate for service level agreement purposes; multicast
traffic is excluded. The rate limit is the sum of the EIRs of all services on the ONT.
Downstream traffic is mapped to the queues based on p-bits. A per-ONT
downstream rate limiting scheduler specifies the individual scheduler weight and
sizes of the queues in the per ONT rate shaper, and the mapping of p-bits to queues,
which provides a more efficient use of scarce edge and access network bandwidth
resources. Figure 15-6 illustrates downstream rate limiting on a per-ONT basis.
Figure 15-6 Per-ONT downstream rate limiting
LT
ONT
Packets are queued by p-bit.

0
MAC 1 1 256
MAC 1 2 257
VLANx MAC 1 1
MAC 2 2 258
VLANx MAC 1 2
VLANy MAC 2 2
VLANx
2
3
VLANy
VLANy MAC 2 3
VLANz MAC 3 6
VLANz MAC 3 7
MAC 3 6 260
p-bit
MAC 2 3 259
X
GEM
port
VLANz
256
257
258
259
260
261
ENET1
MAC 1
ENET2
MAC 2
VOIP
MAC 3
7
MAC 3 7 261
The per-ONT downstream rate limiting scheduler profile

includes a configurable p-bit to queue mapping.
Per-ONT downstream rate-limiting

scheduler specifies queue sizes
and scheduler weights.
19960
15-14

15 QoS
Downstream rate limiting on a per-service basis limits the downstream traffic to each
service on an ONT to the EIR of the service. There is a single queue in the ONT rate
shaper for each service; p-bits are ignored in the queuing process. A per-service
downstream rate limiting scheduler specifies the scheduler weight and size of the
service queue. Figure 15-7 illustrates downstream rate-limiting on a per-service
basis.
Figure 15-7 Per-service downstream rate limiting
LT
MAC 1 1 256
MAC 1 2 257
MAC 2 2 258
MAC 3 6 260
VLANx MAC 1 2
VLANy MAC 2 2
GEM
port
VLANx
2
MAC 3 7 261
X
VLANy MAC 2 3
VLANz MAC 3 6
VLANy
VLANz MAC 3 7
p-bit
MAC 2 3 259
VLANx MAC 1 1
ONT
VLANz
256
257
258
259
260
261
ENET1
MAC 1
ENET2
MAC 2
VOIP
MAC 3
7
Packets are directed
to queues by service.
Per-service downstream rate-limiting

scheduler specifies individual queue size
and scheduler weight.
19961
Note 1 A per-service downstream rate limiting scheduler can also
disable rate limiting for the service, while enabling queuing and
scheduling for the same service.
Note 2 Per-service downstream rate limiting scheduler is
supported by the GLT4 but not by GLT2 cards.
GPON SPWFQ scheduler
The GPON SPWFQ scheduler operates in a combination of SP and weighted fair

queuing (WFQ).
The OMCI queue and the multicast traffic spacer are treated as SP with the OMCI
queue having a higher priority than the multicast traffic spacer.
A weight is software calculated for each input from the individual 64 per-ONT
rate shapers. The weight calculation is based on the aggregated CIR bandwidth
from the downstream bandwidth profiles assigned to each service flow that is
activated on the ONT.

15-15
15 QoS

A priority queue profile defines up to eight priority queues; each queue represents a
GEM port in a T-CONT that carries traffic across the GPON from the ONT to the
LT. After tagging is complete, traffic is directed to one of the GEM ports.
The number of available GEM ports per ONT UNI (22, with 3 reserved for internal
use for a maximum of 19) limits the number of priority queues that can be used for
each service on the ONT UNI. For example, if 8 priority queues are used per HSI
service, there are not enough GEM ports available to have a third HSI service with 8
queues.
The priority queue profile includes the scheduling weight of each priority queue, and
the distribution of p-bits to the priority queues. The weight directs the scheduling of
queues at the ONT as described in Table 15-5; the p-bit mapping directs
priority-marked service traffic to a priority queue.
Table 15-5 Upstream scheduling of queues at the ONT by weighting factor
Weight
Scheduling
SP
Queue with a weight of 1 to 255 with 255 being lowest

priority
WRR
Not used
Priority queue profiles are applied to flows and traditional services on an ONT UNI
port.

T-CONTs are traffic containers for GEM ports. A GEM port is a virtual port that is
used to transport data across the PON from the LT to the ONT and from the ONT to
the LT. Each GEM port has an identifier (GEM port ID) that is unique to a PON port.
Up to 512 T-CONTs can be supported per PON port. Each T-CONT can support up
to eight GEM ports.
After tagging frames, the 7342 ISAM FTTU segregates frames into GEM ports, and
GEM ports into T-CONTS depending on how the services are configured.
Table 15-6 identifies the T-CONT models supported by the 7342 ISAM FTTU and
the service configurations to which they apply.
Table 15-6 T-CONT models
T-CONT model
EVC and Ethernet service

configuration
T-CONT per EVC model
T-CONT per CoS model
T-CONT per service model
Traditional service
configuration (HSI,
CES PW, VoIP, DSL2)
(1 of 2)
15-16

15 QoS
T-CONT model
EVC and Ethernet service

configuration
Traditional service
configuration (HSI,
CES PW, VoIP, DSL2)
T-CONT per subscriber/per service

model
(2 of 2)
The T-CONT models are described in the following sections. For more information
about tagging, see Chapter 18 on VLANs.
T-CONT per EVC model
The T-CONT per EVC model allows multiple services for a single subscriber to
share the same T-CONT. In this model, a T-CONT is dedicated to an EVC, and an
EVC is dedicated to a subscriber. A T-CONT is represented by a portal, and can be
shared across multiple services for a subscriber. Each GEM port is associated with a
service bound to the T-CONT.
On an ONT UNI port, a flow can be defined by any combination of VLAN ID, p-bits,
and number of tags. The service is allocated a set of GEM ports. After tagging is
performed, upstream frames having the specified number of tags, and the same p-bit
and VLAN ID in their outer tag are directed to the same GEM port. GEM ports
having the same VLAN ID are grouped together with the same T-CONT.
T-CONT per CoS model
The T-CONT per CoS model allows multiple services for different subscribers to
share the same T-CONT. In this model, a T-CONT can be shared across multiple
ONT UNIs on the same ONT; a GEM port is uniquely identified by an ONT UNI
port, VLAN ID, and p-bit.
After tagging is performed, upstream frames having the same ONT UNI, and p-bit
and VLAN ID in their outer tag, are directed to the same GEM port. GEM ports
having the same p-bit are grouped together with the same T-CONT.
T-CONT per service model
The T-CONT per service model allows multiple subscribers of the same service to
share the same T-CONT. In this model, a T-CONT maps to one service on the PON;
each GEM port maps to a single subscriber of the service. In this model, the T-CONT
can be shared across multiple ONT UNIs on the same ONT. The model obtains
maximum subscriber scalability on the PON and allows efficient use of the GPON
TC layer.
After tagging is performed, upstream frames are directed to a GEM port based on the
ONT UNI, p-bit, and C-VLAN ID. GEM ports having the same C-VLAN ID are
grouped together with the same T-CONT.
Figure 15-8 illustrates the T-CONT per service model.

15-17
15 QoS
Figure 15-8 T-CONT per service model
PON
OLT
Tag
GEM
Tag
Tag
ONT
GEM
GEM
GEM
T-CONT
T-CONT
GEM
WRR
GEM
Tag
Tag
Tag
Tag
GEM
GEM
Tag
Tag
GEM
GEM
Tag
UNI
UNI
Tag
Tag
Tag
Tag
Uplink
Tag
Tag
Tag
GEM
GEM
T-CONT
T-CONT
WRR
GEM
GEM
GEM
GEM
Tag
Tag
Tag
UNI
UNI
Tag
Tag
Tag
Tag
20070
T-CONT per subscriber/per service model
In the T-CONT per subscriber/per service model, a T-CONT is reserved for a single
service on a single ONT UNI, with a GEM port for each priority queue within the
service.
When a service is created, the 7342 ISAM FTTU creates autonomous instances of a
T-CONT and GEM ports, and associates them as follows:
the T-CONT is associated with the priority queue profile of the service
each queue in the priority queue profile is associated with a unique GEM port; the
GEM port inherits the same p-bits as the queue
Where more than one service is configured on the same ONT UNI port, multiple
T-CONTs support traffic from the ONT UNI port. However, because the number of
GEM ports across the ONT UNI port cannot exceed eight, the operator must ensure
that each priority queue profile uses fewer than eight queues.
After frames are tagged, frames are directed to GEM ports based on their p-bit.
Figure 15-9 shows the relationships among the elements.
15-18

15 QoS
Figure 15-9 T-CONTs and GEM ports
Where more than one service is configured,
multiple T-CONTs can support traffic
across an ONT UNI port.
ONT
ONT UNI
port
Priority
queue
profile
Service
T-CONT
A priority queue
profile has one to
eight queues.
An ONT UNI port can

have a maximum of
eight GEM ports.
P-bit
mapping
A T-CONT
contains
one to eight
GEM ports.
A p-bit maps
to one queue.
Queue
Each queue has its own
GEM port; the GEM port
takes on the same p-bit
as its queue.
GEM
port
One-to-one mapping
One-to-many or many-to-one mapping
19473
Figure 15-10 illustrates the T-CONT per subscriber/per service model.

Figure 15-10 T-CONT per subscriber/per service model
PON
OLT
Tag
GEM
Tag
GEM
ONT
GEM
T-CONT
T-CONT
GEM
UNI
Uplink
Tag
Tag
GEM
T-CONT
T-CONT
GEM
GEM
GEM
20071

15-19
15 QoS
15.6
Traffic shaping elements

An integral part of traffic shaping is the optimization of bandwidth to reduce the
burstiness of traffic.
Traffic shaping elements described in this section are:
PON bandwidth
Bandwidth profile
Reserved bandwidth
PON bandwidth
The bandwidth available on the PON can be considered when configuring the system
for maximum performance. The following information is available for a specific
PON:
aggregate upstream provisioned CIR

aggregate upstream provisioned AIR
guaranteed upstream bandwidth that remains for further provisioning
aggregate downstream provisioned CIR
guaranteed downstream bandwidth that remains for further provisioning
maximum downstream multicast bandwidth allowed
The operator can use this information to determine how much bandwidth is left to
allot in the upstream or downstream direction.
Bandwidth profile
A bandwidth profile specifies the bandwidth characteristics of ONT services.
Bandwidth profiles allow you to:
engineer your network resources to provide performance assurances

offer bandwidth to subscribers in increments less than the UNI speed
offer multiple service instances per UNI and each service can have its own
bandwidth profile
Bandwidth characteristics include the following traffic parameters:
15-20
CIR
AIR
EIR
DT

15 QoS
The CIR guarantees a committed bandwidth under peak demand conditions, and the
EIR guarantees superior service when network utilization is low. The DT specifies
the longest delay between two upstream grants for the service. The upstream
granting rate may be more frequent than what the DT specifies if the bandwidth
requires it.
Bandwidth profiles can be applied to a portal, a flow, or a service. When the
bandwidth is applied to a portal or a service, the bandwidth profile provides the
bandwidth requirements for the T-CONT. When the bandwidth profile is applied to
a flow, the bandwidth requirements for the T-CONT are calculated by adding the
bandwidth of the individual flows in the portal.
The bandwidth characteristics provide input to the following processes:
DBA requires CIR, AIR, and EIR to allocate upstream bandwidth.

CAC requires CIR, AIR, and EIR to check for the availability of bandwidth when
a new service is added to a GPON or S-VLAN.
You must consider the EIR of the services to set threshold levels for queues when
configuring downstream rate-limiting schedulers.
The delay tolerance parameter determines the upstream grant frequency to
achieve provisioned maximum delay variation (DT).
The AIR and DT have no significance in the downstream direction.
Reserved bandwidth
Multicast traffic is forwarded downstream to a single GEM port ID and is not
replicated on the GPON. The bandwidth required for multicast traffic is reserved at
the GPON level to ensure that multicast traffic is accounted for in the CAC check.

DBA is the process by which ONTs and their associated T-CONTs request upstream
bandwidth and whereby the P-OLT re-assigns bandwidth accordingly. The P-OLT
allocates upstream bandwidth on a T-CONT basis, and not on a GEM port, queue, or
VLAN priority basis. The characteristics of the T-CONT determine the quality of
upstream traffic. VLAN priority affects traffic quality only indirectly.
The 7342 Dynamic Bandwidth Allocation (DBA) mechanism grants upstream
bandwidth to ONUs in increments of 32bytes. The guaranteed minimum bandwidth
assigned to an ONU by the DBA mechanism is derived from the CIR, AIR, and
Delay Tolerance (DT) values provisioned in the Bandwidth Profile for an HSI
service. The minimum bandwidth value is determined by comparing the BW profile's
provisioned CIR value to a calculated minimum bandwidth based on the BW
profile's provisioned DT value. The formula for calculating the minimum bandwidth
based on the BW profile's provisioned DT value is: DT_MinBW =[(8000
transmission time slots per second/Provisioned DT)*32 bytes]. Refer to Table 15-7.
If the upstream CIR and/or AIR bandwidth parameters defined in the HSI's BW
profile are configured less than the calculated DT_MinBW value, the
RTRV-PONBW command will display the calculated DT_MinBW value for the
UPCIR and UPAIR parameters. Otherwise the configured CIR and AIR values will
be displayed.

15-21
15 QoS
Table 15-7 MinBW for Delay Tolerance
MinBW
Delay Tolerance Number
2048 Kbps
1024 Kbps
512 Kbps
256 kbps
128 Kbps
16
64 Kbps
32
32 Kbps
64
The 7342 ISAM FTTU supports DBA according to the ITU-T G.984.3
recommendation, which specifies four types of bandwidth and classifies T-CONTs
into five types of containers. A T-CONT is allocated one or more types of bandwidth
based on its container type.
Table 15-8 describes the bandwidth types and the order in which they are reserved.
Table 15-8 Bandwidth types
Bandwidth type
Description
Reservation
Priority
Fixed bandwidth
Fixed bandwidth has the following characteristics:
is entirely reserved and is cyclically allocated to achieve

a low cell transfer delay
guarantees cell transfer delay, delay variation, and
transmission rate
Fixed bandwidth is treated as guaranteed bandwidth in the

CAC check.
Assured
bandwidth
Assured bandwidth has the following characteristics:
means fixed average bandwidth over some specified time

interval. While fixed bandwidth guarantees cell transfer
delay, delay variation, and transmission rate, assured
bandwidth guarantees the average transmission rate
only.
is always available to a T-CONT if the T-CONT has data to
transmit
is available to other T-CONTs if the T-CONT does not
have data to transmit
Assured bandwidth is treated as guaranteed bandwidth in the

CAC check.
15-22
Non-assured
bandwidth
Non-assured bandwidth is surplus bandwidth that a T-CONT

can use, which is not committed to fixed bandwidth or
assured bandwidth.
Best effort
bandwidth
Best effort bandwidth is surplus bandwidth that a T-CONT

can use after all other bandwidth types have been assigned.

15 QoS
Fixed bandwidth is reserved first, including slot location to minimize delay and delay
variation. Assured bandwidth is reserved next with the remaining bandwidth.
Bandwidth that is still not reserved is released to the pool of surplus bandwidth for
non-assured bandwidth and best effort bandwidth, with non-assured bandwidth
having higher priority over best effort bandwidth.
The DBA does not allocate assured bandwidth until the P-OLT receives a bandwidth
request from the ONT. Therefore, assured bandwidth is available for best effort
traffic.
The DBA allocates assured bandwidth explicitly through idle-cell monitoring.
A part of AIR is always allocated to observe bandwidth demands.

When bandwidth is granted, the T-CONT sends an idle cell to the P-OLT, if the
T-CONT has no upstream data to transport. The DBA reduces the bandwidth to
a minimum and re-assigns it to other T-CONTs that do not send idle cells.
The 7342 ISAM FTTU categorizes a T-CONT by container type based on the CIR,
AIR, and EIR requirements of the T-CONT, and allocates bandwidth to a T-CONT
according to its type. Table 15-9 describes the allocation of bandwidth by T-CONT
type and the corresponding bandwidth settings, and identifies the services to which
the T-CONT types are best suited.
Table 15-9 Allocation of bandwidth by T-CONT type
T-CONT type
Type 1
Bandwidth
Allocation
Bandwidth settings
Suited to
CIR
AIR
EIR
Fixed bandwidth only
>0
AIR = CIR
EIR = CIR
VoIP service and

CES
>0
EIR = AIR
VoIP service and

other services
with a constant
bit rate and some
tolerance to
delay (1)
>0
EIR > AIR
VoIP service and

other services
with a constant
bit rate and some
tolerance to
delay (1)
T-CONT type 1 guarantees cell transfer

delay, delay variation, and transmission
rate. Upstream bandwidth is reserved and is
cyclically allocated with a fixed rate and
controlled cell transfer delay.
Type 2
Assured bandwidth only

T-CONT Type 2 guarantees the average
transmission rate only.
Type 3
Assured bandwidth and non-assured

bandwidth
T-CONT type 3 has both assured bandwidth
and non-assured bandwidth, and is allocated
bandwidth up to its EIR amount as follows:
Assured bandwidth is fully allocated if

there is data waiting for assured
bandwidth.
Non-assured bandwidth is allocated up
to the EIR amount in a WRR manner
across all T-CONTs that have assured
bandwidth and are requesting additional
bandwidth. The assured bandwidth
determines the weight.
(1 of 2)

15-23
15 QoS
T-CONT type
Type 4
Bandwidth
Allocation
Bandwidth settings
Suited to
CIR
AIR
EIR
Best effort bandwidth only
>0
HSI service
>0
AIR CIR
EIR AIR
Premium HSI
service (with
fixed, assured,
non-assured, and
best effort
bandwidth)
T-CONT type 4 uses surplus bandwidth that is

not allocated to fixed, assured, and
non-assured bandwidth types. Each T-CONT
type 4 is allocated bandwidth equally up to
the maximum peak attainable bandwidth
(EIR) without any guaranteed bandwidth in a
round robin fashion.
Type 5
Maximum bandwidth
T-CONT type 5 is a mix of all service
categories. The maximum amount of
bandwidth that can be granted is allocated
to the T-CONT up to the EIR amount for all
services contained in the T-CONT.
If assured bandwidth is not provisioned, that
is AIR is equal to CIR, then the difference
between EIR and CIR is treated as best effort
bandwidth and is allocated in a round robin
fashion up to the EIR amount.
(2 of 2)
Note
(1)
T-CONT types 2 and 3 are suitable for VoIP and other services that have a constant bit rate and can tolerate some delay;
T-CONT types 2 and 3 are not suitable for CES.
When a service of T-CONT type 2, 3, 4, or 5 is configured, the system must allocate

a minimum bandwidth to observe bandwidth demands. For assured bandwidth, the
system performs the following:
system allocates 128 kb/s in addition to any fixed bandwidth (CIR)

if the amount of the idle cell is less than 128 kb/s, then the AIR bandwidth is
granted
system deallocates assured bandwidth if the AIR bandwidth is not used after a
certain period of time
For a service of type T-CONT type 4, the system internally allocates a minimum
bandwidth to observe idle cells.
Table 15-10 describes how the DBA issues grants to T-CONTs based on a system of
prioritization:
Table 15-10 T-CONT prioritization
Priority
Bandwidth
High
Fixed bandwidth, which is represented by:
CIR of T-CONT type 1

CIR of T-CONT type 5
(1 of 2)
15-24

15 QoS
Priority
Bandwidth
Medium high
Assured bandwidth, which is represented by:
Medium low
Non-assured bandwidth, which is represented by:
Low
AIR minus CIR of T-CONT type 2

EIR minus AIR of T-CONT type 3
EIR minus AIR of T-CONT type 5
Best effort, which is represented by:
EIR of T-CONT type 4

EIR minus AIR of T-CONT type 5 if CIR equals AIR
(2 of 2)
The proper selection of grant size and delay tolerance are critical per service to meet
service level agreements, such as bandwidth guarantees, bounded latency, and
reduced packet loss.
15.7
QoS configuration
The following represents the workflow to implement QoS.
1
Configure traffic policing at network ports
Configure QoS at the NT
Configure QoS at the LT
Reserve bandwidth for multicast traffic
Configure QoS at the ONT
Configure QoS for the ONT UNI
Configure QoS for ONT services
Table 15-11 identifies the QoS elements by configuration task.

Table 15-11 QoS elements by configuration task
Task
Element
Configure traffic policing at network ports
Egress rate
Traffic meter
Traffic flow
Configure QoS at the NT

Traffic scheduler at the NT
Configure QoS at the LT

Traffic scheduler at the LT
Reserve bandwidth for multicast
Reserved bandwidth
(1 of 2)

15-25
15 QoS
Task
Element
Configure QoS for the ONT
Configure QoS for the ONT UNI

Configure QoS for ONT services
Bandwidth profile
UNI-side to network-side p-bit translation profile
(2 of 2)
VLAN configurations are required so that the 7342 ISAM FTTU can tag frames with
their VLAN ID and p-bit for QoS purposes. Table 15-12 identifies where VLAN
configuration information can be found in Chapter 18 on VLANs.
Table 15-12 VLAN configurations
15.8
VLAN configuration
See
VLAN types
Section 18.3
VLAN models
Section 18.4
VLAN tagging
Section 18.5
Frame processing at the LT
Section 18.6
Frame processing at the ONT
Section 18.7
Downstream queuing and scheduling

The 7342 ISAM FTTU processes downstream traffic as follows:
from the network (EMAN) to the NT

from the LT across the GPON to the ONT
from the ONT to the subscriber
Figure 15-11 illustrates downstream queuing from the EMAN to the subscriber.
15-26

15 QoS
Figure 15-11 Downstream queuing from EMAN to subscriber
ONT
NT A
LT 1
10-Gb/s
GPON 1
eHCL
Subscriber
1-Gb/s
1-Gb/s
NT B
IP network
GPON 2
10-Gb/s
SHub ports
eHCL
Queues for
service ports
Queues for
PON interface ports
1-Gb/s
1-Gb/s
Queues for
LT interface ports
19337
From the network (EMAN) to the NT

When a traffic meter is associated with a SHub port and traffic flow type, the flow of
traffic through the SHub port is monitored. The traffic meter controls the burst and
maximum transmission rate of network traffic entering the port on a per-flow basis.
When the traffic flow reaches the configured maximum ingress rate, excess traffic is
dropped.
From the NT to the LT

As packets are received from the network, they are differentiated by traffic class and
directed to their queue for forwarding to the LT. An LT interface port on the NT has
the following downstream queueing and scheduling characteristics.
Each switch port on the NT features a hierarchical scheduler with up to eight

queues.
SP and WRR scheduling are available.
A customized traffic scheduler can be applied to the LT interface port to specify
the size and scheduling priorities of the queues. See Traffic scheduler at the NT
If a traffic scheduler is not configured for the LT interface port, the system default
traffic scheduler is applied.

15-27
15 QoS
From the LT across the GPON to the ONT

The LT supports eight queues in the downstream direction towards each GPON
interface.
The system mapping of p-bits to queues at the LT directs the queuing of traffic to the
GPON, where queue 0 is reserved for internal VLAN (4095) traffic, and p-bit 7 is
automatically mapped to the same queue as p-bit 6.
A system default traffic scheduler is available. A customized traffic scheduler can be
associated with the GPON interface port to specify the buffer size, scheduling
method, and priorities of the queues. See Traffic scheduler at the LT for more
information.
Traffic backlog handling
In general, the LT is configured not to send a pause frame to any port, when it can
not process all the data frames received from the NT card. When a queue reaches its
maximum capacity as defined by its internal buffer size, the LT card uses the queue
management algorithm tail drop to drop arriving packets until the queue is free to
accept traffic. The 7342 ISAM FTTU performance monitoring function collects
information about the events.
The NT card does not normally send a pause frame to the LT. If the LT card receives
a pause frame, the pause frame is automatically generated.
Downstream rate limiting
Downstream traffic to the ONT is rate limited either on a per-ONT or per-service

basis, because the ONT tends to receive more traffic from the GPON than its ONT
UNI ports can support.
Per-ONT downstream rate limiting ensures that the ONT does not receive more
downstream traffic than the sum of the EIRs (Excess Information Rate) of all
services or flows configured on the ONT.
Per-service downstream rate limiting rate limits the traffic to the EIR of the
service or portal.
Multicast traffic is not included in the per ONT rate limiting. Multicast traffic is
scheduled on its own, and only unicast traffic is accounted for in the per ONT rate
limiter.
See Downstream rate limiting to ONT for more information.
From the ONT to the subscriber

In the downstream direction, the ONT terminates the GEM layer, extracts the
Ethernet packets, performs any VLAN and p-bit translation that is required (see
Chapter 18 for information about VLAN tagging), and forwards them into the right
downstream priority queue based on their p-bit. Figure 15-12 illustrates the queuing
and scheduling of downstream traffic at the ONT.
15-28

15 QoS
Figure 15-12 Downstream queuing and scheduling at the ONT
ONT
Queue 0
C
Trusted/Untrusted
Residential gateway
Queue 1
SP
F
Ethernet
Queue 7
P-OLT
A
GPON
CES
D
Ethernet/VDSL2 port
DS1/E1 port
Signaling
POTS phone
SP
Bearer
OMCI
POTS port
E
OBC
A Downstream traffic
B Ethernet traffic is C CES traffic has
is shaped at the
queued based on
its own queue.
P-OLT/Aggregation Switch priority tags p-bit.
and marked with p-bit.
D POTS traffic is
E OMCi has its
queued based
own queue.
on whether it is
signaling or bearer.
F Only strict
priority
scheduling
is done.
19323
The ONT may be receiving more data than its egress ports can support. A substantial
amount of data buffering is provided to absorb any data bursts until they can be
transported towards the subscriber. The ONTs must support a SP scheduling
mechanism in the downstream direction, as all traffic types contend for the same
Ethernet UNI port.
Each ONT UNI port is equipped with up to eight queues. Ethernet traffic is assigned
to queues based on p-bit only, whereby the highest priority p-bit is allocated to the
highest priority queue. CES and OMCI traffic each have their own queue. Voice
traffic is segregated into two priority queues: one for signaling and the other for
bearer traffic. All queues are serviced in a SP manner.
15.9
Upstream queuing and scheduling

The 7342 ISAM FTTU processes upstream traffic as follows:
from the ONT to the LT

from the NT to the network (E-MAN)
Figure 15-13 illustrates upstream queuing from the subscriber to the EMAN.

15-29
15 QoS
Figure 15-13 Upstream queuing from subscriber to EMAN
ONT
NT A
LT 1
10-Gb/s
GPON 1
eHCL
Subscriber
1-Gb/s
GPON 2
1-Gb/s
NT B
IP network
10-Gb/s
eHCL
Queues for
NT interface ports
1-Gb/s
1-Gb/s
Queues for
SHub ports
19343
From the ONT to the LT

The ONT receives untagged, priority-tagged, single-tagged, and double-tagged
packets from a subscriber. On a packet basis, the ONT tags and marks the received
frames with their p-bit and C-VLAN ID based on the tagging requirements of the
ONT UNI port and the service or flow. See Upstream tagging at the ONT in
Chapter 18 for more information.
The ONT uses the Priority queue profile of the service or flow to map the p-bit to a
queue.
The ONT UNI port can support multiple priority queue profiles (traffic schedulers)
in the upstream direction, where each priority queue profile is allocated to an
individual service or flow on the UNI. The priority queue profile attached to a service
determines:
how queues are scheduled

how priority-marked service traffic is mapped to queues
An ONT UNI port is associated with an eight-queue scheduler. The scheduler can
perform SP or WRR scheduling on an individual queue. The relative weights of the
queues are configurable; SP is achieved by allocating a zero weight to the queues,
whereas a value between 1 and 255 will trigger WRR handling. See Priority queue
profile for more information.
15-30

15 QoS
Each queue is associated with a GEM port. Packets are carried across the GPON in
the GEM port associated with the queue. The GEM port is contained in a T-CONT
(see T-CONTs and GEM ports). CES, voice, and OMCI are carried across the
GPON, each in their own T-CONT, separate from subscriber traffic.
Figure 15-14 illustrates upstream scheduling at the ONT.
Figure 15-14 Upstream scheduling at the ONT
Bandwidth
Allocation
Based on
Services
Provisioned
ONT
Priority 6, 5, 4
T-CONT
Priority 3
A
T-CONT
OLT
SP/
WRR
GPON
Trusted/Untrusted
Residential gateway
E
Ethernet/VDSL2 port
Priority 0
CES
T-CONT
DS1/E1 port
Signaling
T-CONT
SP/
WRR
B
Bearer
POTS phone
POTS port
C
OMCI
T-CONT
A T-CONTs are assigned

guaranteed and
dynamic BW by DBA.
B Traffic schedulers
C
for a service
can be provisioned
to prioritize traffic
based on strict priority
(SP) or weighted round
robin (WRR) or combination
of the two.
D CES traffic has

POTS traffic has a
dedicated T-CONT
its own T-CONT.
and is separated
into two queues
for signaling and bearer.
E Ethernet traffic can

have one or more
T-CONTs and each
T-CONT can support
up to 8 queues.
19324
The LT card is equipped with a granting engine called a DBA scheduler. The DBA
is associated with only one GPON and allocates bandwidth to specific T-CONTs
based on their type. For information on the allocation of bandwidth by T-CONT
type, see Table 15-9.
From the LT to the NT

In the upstream direction, the P-OLT performs a concentration function. The
network bandwidth of network links (GEM ports) is less than the bandwidth of LT
ports. Some statistical multiplexing is occurring based on the assumption that not all
subscribers are sending traffic at the same time.

15-31
15 QoS
On a packet basis, the LT tags and marks the received frames with their p-bit and
S-VLAN ID based on the tagging requirements of the service VLAN on the PON.
See Upstream tagging at the LT in Chapter 18 for more information.
The LT supports eight queues in the upstream direction towards each NT interface
port. The system-wide mapping of p-bits to queues, which is configured for the LT,
directs the queuing of traffic, where queue 0 is reserved for internal VLAN (4095)
traffic and p-bit 7 is automatically mapped to the same queue as p-bit 6.
A customized traffic scheduler can be applied to individual NT interface ports to
specify the buffer size, scheduling method, and priorities of their queues. A system
default traffic scheduler is automatically generated. See Traffic scheduler at the LT
From the NT to the network (E-MAN)

The NT supports up to eight queues in the upstream direction towards each SHub
port. SP and WRR scheduling are available.
A customized traffic scheduler can be attached to a SHub port to specify the size and
scheduling priorities of its queues. See Traffic scheduler at the NT for more
information. If a traffic scheduler is not configured for a port, the system default
traffic scheduler is automatically used.
The system monitors a SHub port for egress rate. When the traffic flow rate reaches
the configured maximum egress rate, excess traffic is dropped.
15.10
Recommended DSCP to p-bit mapping

Although the DSCP allows for 64 possible forwarding behaviors, the DiffServ model
aggregates traffic into four standard per-hop behaviors, which provide eight
forwarding classes; see Table 15-13.
Table 15-13 Forwarding classes
Per-hop behavior
Forwarding class
Best effort
BE
Assured forwarding
AF-1
AF-2
AF-3
AF-4
Expedited forwarding
EF
Class selector
CS-1
CS-2
Table 15-14 lists the Alcatel-Lucent recommended DSCP and p-bit mapping for the
optimal CoS treatment in a triple play network.
15-32

15 QoS
Table 15-14 Recommended CoS mapping
DSCP Binary
DSCP
Number
P-bit
Forwarding
Class
Traffic type
Scheduling
type
000000-000111
0 to 7
BE
Ethernet data
WRR
001000-001111
8 to 15
AF-1
010000-010111
16 to 23
AF-2
011000-011111
24 to 31
AF-3
ICMP
100000-100111
32 to 39
AF-4
Multicast data
101000-101111
40 to 47
Voice signaling,
IGMP, DHCP, and
other control
101110
46
EF
Voice-bearer
101110
46
EF
CES
110000-110111
48 to 55
111000-111111
56 to 63
110000
48
CS-1
111000
56
CS-2
OMCI

SP
15-33
15 QoS
15-34

16 Statistics and performance

monitoring
16.1 Overview
16-2
16.2 Statistics, counters, and performance monitoring

16.3 P-OLT performance monitoring
16-5
16.4 RMON Ethernet statistics support for the P-OLT

16-2
16-5
16-1
16.1
Overview
This chapter provides a detailed description of the 7342 ISAM FTTU statistics and
performance monitoring features.
TL1 and CLI for statistics and performance monitoring related procedures.
16.2
Statistics, counters, and performance monitoring

Statistics counters and reports are available for collecting operational statistics for
the 7342 ISAM FTTU. The statistics counters and reports are useful for monitoring
and for troubleshooting the performance of 7342 ISAM FTTU components and
network connections. Status reports display information in a static format, whereas
counters track the number of occurrences of statistics parameters dynamically.
Performance monitoring is performed at the P-OLT and at ONT units. See the
7342 ISAM FTTU ONT Product Information Manual for information about statistics
supported on ONT units.
Operators can view system statistics and monitor performance using a TL1, CLI, or
an element management system (EMS) management session with the P-OLT. Use
the TL1 interface to enable counters and to set filters. You must use a remote
monitoring (RMON) SNMP manager to access RMON statistics. See section 16.4
for information about RMON statistics support on the 7342 ISAM FTTU.
The 7342 ISAM FTTU has two types of statistics collecting counters:
15-min counters
rolling counters
Note 1 Threshold crossing alarm (TCA) is not supported on rolling
counters. See chapter 10 for information about TCA-related alarms
and performance statistics.
Note 2 When the system date changes; for example, due to the
move to daylight savings time, performance statistics collection is

affected and an interval is either repeated or lost.
Statistics collection for voice over IP (VoIP) calls at the ONT is also available. See
the 7342 ISAM FTTU Operations and Maintenance Procedures Guide using TL1
and CLI for VoIP call statistics information.
16-2

15-min counters
The 7342 ISAM FTTU uses 15-min counters to collect statistics continuously in
15-min intervals. When a counter is enabled using TL1, the system starts counting
statistics occurring over a 15-min period and records the number as an integer in a
log file. A total of 32 15-min intervals occurring over an 8-hr period are logged. After
the 8 hr has elapsed, new 15-min intervals overwrite the oldest entry recorded in the
log file. If a command to retrieve performance statistics includes the current 15-min
interval, a snapshot of the count at the time of the retrieval request is provided. The
15-min counters are disabled by default.
Note 1 During an LT unit initialization, the current count of the
first 15-min interval may be forced to restart due to the

synchronization procedure between the LT unit on the P-OLT and the
ONT.
Note 2 Alcatel-Lucent recommends that users should wait for 30
seconds after the expiration of an interval before retrieving last

interval counts. This ensure reliable results as synchronization is then
correct between the P-OLT and the ONTs.
Note 3 A maximum of 31 counters can be active at the same time
on each GPON, or for each service type configured on the same

GPON interface port on the LT card. An alarm is raised when the
number of simultaneous counters exceeds the limit.
Table 16-1 lists the 15-min counters the 7342 ISAM FTTU uses to collect
performance monitoring statistics.
Table 16-1 15-min counters
Counter description
P-OLT
ONT
TC-layer of the gigabit passive optical network (GPON) connection
ONTENET counters
ONTL2UNI counters
ONTMOCA counters
VLAN-based traffic
QoS at the LT
See the 7342 ISAM FTTU ONT Product Information Manual for information about
15-min counters supported on ONT units.
When you retrieve performance statistics, you can use filters to define the scope of
statistics that are collected for viewing. All statistics within the specified range are
retrieved from the log file.
Depending upon the type of statistic you are retrieving, you can set filters to define
any combination of the following:
selected group of statistical parameters

date range
time range
16-3
direction (Tx or Rx)

location (near-end or far-end)
count thresholds
See the 7342 ISAM FTTU TL1 Commands and Messages Reference document for
the command syntax of filters and which filters are supported for the different types
of 15-min counters.
You can set TCA thresholds for 15-min counters using TL1. If the number of events
occurring within a 15-min period exceeds the specified threshold, a TCA alarm event
is raised in the system. See chapter 10 for information about TCA-related alarms and
performance statistics. See the 7342 ISAM FTTU TL1 Commands and Messages
Reference for details about restrictions for the use of statistics collecting counters and
TCA support.
Rolling counters
Rolling counters start at zero and count up to a maximum value. When the maximum
value is reached, the counter restarts at zero. No logs are maintained for rolling
counters and TCA is not supported.
You can enable and disable rolling counters using TL1. When a counter is enabled,
you can retrieve the current count using a TL1 or an EMS management session with
the P-OLT. A snapshot of the current value in the rolling counter is displayed as an
integer.
Table 16-2 lists the rolling counters the 7342 ISAM FTTU uses to collect
performance monitoring statistics.
Table 16-2 Rolling counters
Counter description
P-OLT
IGMP per user channel
IGMP per LT card
IGMP multicast sources
VLAN-based traffic
There are restrictions as to how many rolling counters you can enable
simultaneously. Also, some rolling counters can be set to automatically reset to zero
after being retrieved. See the 7342 ISAM FTTU TL1 Commands and Messages
Reference document for restrictions, maximum count ranges, and the resetting of
rolling counters. See the 7342 ISAM FTTU ONT Product Information Manual for
information about rolling counters supported on ONT units.
16-4

Status reports
Status reports are available for the following:
802.1 end-user authentication

802.1 operator authentication
residential bridges
See the 7342 ISAM FTTU TL1 Commands and Messages Reference document for
statistical parameters that are displayed in status reports.
16.3
P-OLT performance monitoring

The 7342 ISAM FTTU supports the following performance monitoring statistics
counters for the P-OLT:
GPON TC-layer
GPON errored fragments
IGMP per user channel
IGMP per LT card
IGMP multicast sources
VLANs
You can view statistics collected for the P-OLT using a TL1, CLI, or an EMS
management session with the P-OLT. To enable and disable counters, use TL1.
Counters are disabled by default unless indicated otherwise.
For 15-min counters, you can use filters to define the scope of statistical data
retrieved from the log file. Some counters have restrictions for the total number that
you can activate at the same time. See the 7342 ISAM FTTU TL1 Commands and
Messages Reference document for information about filters and any restrictions that
apply to each performance statistic type.
16.4
RMON Ethernet statistics support for the P-OLT

The P-OLT supports the collection of remote monitoring (RMON) Ethernet statistics
as defined in RFC 2819. The RMON Ethernet statistics can be gathered from the NT
Ethernet ports of the P-OLT using any RMON SNMP manager.
The RMON implementation does not count packets larger than 1526 bytes. The only
oversized packets that are counted are those that fall between 1518 and 1526 bytes.
Larger packets are discarded.
The RMON manager must set the SNMP packets that it sends with a community
string defined for the P-OLT that it is monitoring.
Table 16-3 describes the RMON Ethernet statistics.

16-5

Table 16-3 RMON Ethernet statistics and definitions
Statistic
Description
EtherStatsEntry
A collection of RMON Ethernet statistics for a specific Ethernet interface. For

example, an instance of the etherStatsPkts object may be named etherStatsPkts.1.
etherStatsIndex
The value of this object uniquely identifies the etherStats entry.
etherStatsDataSource
This object identifies the source of the data that this etherStats entry is configured
to analyze. This source can be any ethernet interface on this device.
etherStatsDropEvents
The total number of events in which packets were dropped by the probe because of
a lack of resources. This number is not necessarily the number of packets dropped;
but is the number of times that this condition was been detected.
On NT network ports, packet discards are not incremented.
etherStatsOctets
The total number of data octets that was received on the network including those in
bad packets and FCS octets, and excluding framing bits.
etherStatsPkts
The total number of packets that were received including bad packets, broadcast
packets, and multicast packets.
etherStatsBroadcastPkts
The total number of good packets received that were directed to the broadcast
address excluding multicast packets.
etherStatsMulticastPkts
The total number of good packets received that were directed to a multicast address
excluding packets directed to the broadcast address.
etherStatsCRCAlignErrors
The total number of packets received that were between 64 and 1518 octets
excluding framing bits, but including FCS octets inclusive, but had either a bad Frame
Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with
a non-integral number of octets (Alignment Error).
etherStatsUndersizePkts
The total number of packets received that were less than 64 octets including FCS
octets, but were otherwise well formed and excluding framing bits.
etherStatsOversizePkts
The total number of packets received that were greater than 1518 octets including
FCS octets and were otherwise well formed but excluding framing bits.
etherStatsFragments
(1)
The total number of packets received that were less than 64 octets including FCS
octets but excluding framing bits, and had either a bad FCS with an integral number
of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment
Error).
etherStatsJabbers
The total number of packets received that were greater than 1518 octets including
FCS octets excluding framing bits, and had either a bad FCS with an integral number
of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment
Error).
etherStatsCollisions
An estimate of the total number of collisions on this Ethernet segment.
etherStatsPkts64Octets
The total number of packets including bad packets received that were 64 octets and
including FCS octets but excluding framing bits.
etherStatsPkts65to127Octets
The total number of packets including bad packets received that were between 65
and 127 octets excluding framing bits but including FCS octets.
The total number of packets including bad packets received and FCS octets that were
between 128 and 255 octets excluding framing bits.
(1 of 2)
16-6

Statistic
Description
etherStatsOwner
The entity that configured this entry and is therefore using the resources assigned to
it.
etherStatsStatus
The status of this etherStats entry.
(2 of 2)
Note
(1)
It is normal for the etherStatsFragments statistic to increment because it counts both runts, which are normal
occurrences due to collisions, and noise hits.

16-7
16-8

17 Security
17.1 Overview
17-2
17.2 Secured MAC learning

17.3 Access control lists
17-3
17-3
17.4 RADIUS proxy and server

17.5 SNMP encryption
17.6 SSH
17-4
17-6
17-7
17.7 802.1x authentication
17-11
17.8 System log for security and NE actions

17.9 User account management
17.10 IPSec
17-15
17-17
17-17
17.11 Anti-spoofing mechanism
17-19

17-1
17 Security
17.1
Overview
This chapter describes the security features supported by the 7342 ISAM FTTU:
secured MAC learning

RADIUS proxy and server
SNMP encryption
SSH
802.1x authentication
system logs
user account management
IPSec
anti-spoofing mechanism
Figure 17-1 shows the possible security features in the network.

Figure 17-1 7342 ISAM FTTU and network security features
OSS application
Telnet
user ID/password
Firewall
Firewall
IPSec
NMS
client GUI
User ID/
password
NMS
server
HTTP/RMI
Local
security
data
SNMPv3 USM/VACM
SSHv2 or telnet
user ID/password
FTP/SCP user ID/password
Managed
network
(G6+ 7342
ISAM FTTU)
User authorization and

authentication
requests
NMS
display terminal
RADIUS
18969
TL1 and CLI for security configuration procedures.
17-2

17 Security
17.2
Secured MAC learning

When a frame is received with an unknown media access control (MAC) source
address or the MAC source address is received on a different port than previously
learned, the 7342 ISAM FTTU learns this MAC address with the following
restrictions. These restrictions are valid in both residential bridge mode and virtual
local area network (VLAN) cross-connect mode.
If the MAC address is learned on a user port and the number of MAC addresses
already learned on that user port has reached the maximum set in the
MAXMANUM parameter, the MAC address is not learned and the frame is
dropped. If the user sends more than 300 packets with the unlearned MAC
address in 15 s., the OLT will shut down the user port for 15 s.
If the MAC address is learned on a user port and the same MAC address has
already been learned on an Ethernet network interface in the same VLAN as the
user port, then the MAC address is not learned and the frame is dropped.
If the MAC address is learned on a user port and the same MAC address is already
on another user port and both user ports are in the same VLAN, then the new
MAC address is not learned and the frame is dropped.
If the MAC address is first learned on a user port and then on an Ethernet network
interface, then this movement is accepted and the MAC address will be learned.
This means that the MAC address is removed on the user port.
Well-known MAC addresses, such as multicast MAC addresses, and MAC
addresses allocated for IEEE protocols, will not be learned.
Only independent VLAN learning is supported; that is, 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.
17.3
Access control lists

Filter policies, also referred to as Access Control Lists (ACLs), are applied to
VLANs, protocols, NT cards, or LT cards to control traffic into or out of the system.
The filters can be based on MAC matching criteria, or on EtherType only.
You can configure the following 7342 ISAM FTTU MAC-based filters, to enable or
prevent the forwarding to or the distribution from specific MAC addresses:
source MAC address

destination MAC address
source and destination MAC address
any source and destination MAC address, used for EtherType only filtering

17-3
17 Security
17.4
RADIUS proxy and server

The remote authentication dial-in user service (RADIUS) is a standardized method
of information exchange between the RADIUS client, a device that provides network
access to users, and the RADIUS server, a device that contains authentication and
profile information about the users. The 7342 ISAM FTTU supports RADIUS for
both layer 2 and layer 3 forwarding. The 7342 ISAM FTTU supports the RADIUS
protocol, as defined by RFC 2865. Compatible RADIUS servers include, but are not
limited to, SteelBeltedRADIUS server Release 5.03 for Solaris 2.8. Refer to the
appropriate RADIUS server user documentation for more information about
configuring RADIUS server dictionary information
The NT card can contact RADIUS servers over the internal VLAN and the external
VLAN. When the internal VLAN is used, the RADIUS proxy on the NT card is used
as the destination. The RADIUS proxy contacts the RADIUS servers of the ISPs.
When the external VLAN is used, the destination is the external RADIUS server or
proxy. The RADIUS proxy in the NT card selects the RADIUS server based on the
domain name. This domain name maps to a specific Internet service provider (ISP).
The IP addresses of the RADIUS servers are in the ISP profile.
Applications such as 802.1x that need RADIUS server access for authentication use
the internal VLAN to contact the RADIUS client on the NT card. The RADIUS
client on the NT card contacts a RADIUS server outside of the 7342 ISAM FTTU
system. When a response is received from the RADIUS server, the client on the NT
card sends the success or failure indication to the 802.1x application on the LT card
using the internal VLAN.
To route the RADIUS packets towards the RADIUS servers, the system performs an
IP lookup in the context of the Internet service provider (ISP). The ISP profile
contains configuration for the virtual routing and forwarding (VRF) application. The
VRF configuration provides a route for each of the RADIUS servers used by the ISP.
If multiple RADIUS servers are configured for redundancy, the RADIUS client on
the NT card selects the appropriate RADIUS server.
Caution If a higher priority RADIUS server is not responding,
authentication is retried until the dead-interval expiration value is
reached. The 7342 ISAM FTTU then tries to authenticate using a
lower priority RADIUS server. This may lead to authentication and
service outages.
The following features are supported:
User authentication via an external RADIUS authentication server.

The RADIUS Authentication client encrypts all password fields in the messages.
Multiple RADIUS Authentication servers.
A flexible authentication mechanism: that supports Password Authentication
Protocol (PAP) and Challenge-Handshake Authentication Protocol (CHAP)
authentication, as well as support of Extensible Authentication Protocol (EAP)
RADIUS authentication for CLI and TL1 users
User authentication via external RADIUS servers
Fall back to local authentication when no RADIUS server is available. "Fallback
to a configurable default operator profile when the RADIUS server does not
support vendor specific attribute.
17-4

17 Security
Figure 17-2 shows RADIUS on the NT and SHub.

Figure 17-2 RADIUS on the NT and SHub
Applications like 802.1x
and PPP server talk via
the internal OAM VLAN
to NT control to perform
authentication
A RADIUS packet from NT control on the Internal OAM

VLAN is handled by the RADIUS proxy.
A RADIUS packet from NT control on the External OAM
VLAN is bridged
7342 ISAM
FTTU
Ethernet
RADIUS
ONT
ER
NT
control
RADIUS
server
When an application requests for authentication, NT control will

perform authentication using the local authentication database,
or it will use RADIUS.
In case of RADIUS, the external OAM VLAN is used to contact an
external RADIUS server, or the internal OAM VLAN is used
towards the SHub, which will perform RADIUS proxy.
18971
CLI and TL1 operators can be authenticated either locally on each

7342 ISAM FTTU or remotely centralized at a RADIUS server. There is one
restriction: if CLI or TL1 over SSH with key authentication is used, the
authentication has to be done locally as RADIUS does not support keys.
This functionality is only supported for CLI and TL1. It does not apply for SNMP
operators as SNMP does not work with the concept of a session. That would mean
that, for each SNMP request, communication with a RADIUS server would have to
be setup to authenticate the originator. In case of CLI and TL1, the authentication
occurs once for a complete session.
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 NE). In
addition, the NE will fallback to local authentication in case the communication with
the RADIUS server fails.
As an operator will either choose for local or centralized authentication, typically the
local database will only contain the administrator account in case RADIUS is used.
To prevent isolation, the operator can configure one default local operator profile
that applies when RADIUS is not reachable and the operator is not configured in the
local database.
Figure 17-3 shows RADIUS operator authentication.

17-5
17 Security
Figure 17-3 RADIUS operator authentication
NMS
7342 ISAM
FTTU
Ethernet
RADIUS
ONT
ER
NT
control
RADIUS
server
When a CLI or TL1 operator requests for authentication, NT control will perform
authentication using the local authentication database, or it will use RADIUS.
In case of RADIUS, the external OAM VLAN is used to contact an external
RADIUS server, or the internal OAM VLAN is used towards the SHub,
which will perform RADIUS proxy.
18972
TL1 and CLI for configuration information.
17.5
SNMP encryption
The 7342 ISAM FTTU provides the simple network management protocol (SNMP)
version 3 privacy and authentication features of the user-based security model
(USM). The privacy feature uses DES-56 to encrypt SNMP version 1 and SNMP
version 2 packets. Authentication is provided by keyed-hash message authentication
code (HMAC) signatures (HMAC-SHA-96 or HMAC-SHA-96). Access control lists
for managers and community string can also be provisioned in addition to USM or
used without USM.
The security mechanisms defined in SNMPv3 protect against threats as masquerade,
modification of information, message stream modification, and disclosure and
provide:
data origin authentication

data integrity checks
timeliness indicator
encryption
SNMPv3 allows for different security levels. Messages between agent and manager
can be:
unauthenticated and unencrypted

authenticated but unencrypted
both authenticated and encrypted
17-6

17 Security
SNMPv3 defines two security-related capabilities: the User-based Security Model

(USM) and View-based Access Control Model (VACM)
The USM provides authentication and privacy (encryption) functions and operates at
the message level. In addition, it 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 allowable access via an
internal table of user/secrets/access entries. Both authentication and encryption
utilize symmetric keys, which can be generated from a password. Localization of the
authentication and encryption keys by hashing the generated key with the ID of each
agent entity is strongly recommended.
The VACM verifies that 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
SNMPv3 implements security by adding a security header to a standard SNMP PDU,

allowing entities to support non-SNMPv3-aware agents and managers.
See DLP for SNMPv3 configuration in the 7342 ISAM FTTU Operations and
Maintenance Using the 5526 AMS or the 7342 ISAM FTTU Operations and
Maintenance Procedures Guide using TL1 and CLI for more information.
During creation, modification, or deletion of a 7342 ISAM FTTU, you can configure
the security level of communication between the network manager and the
7342 ISAM FTTU. See security DLP 7342 ISAM FTTU Operations and
Maintenance Using the 5526 AMS or the 7342 ISAM FTTU Operations and
Maintenance Procedures Guide using TL1 and CLI for more information.
The available supported security levels are NoAuthNoPriv, AuthNoPriv, and
AuthPriv:
NoAuthNoPriv: Indicates that messages between the agent and the manager are
unauthenticated and unencrypted
authNoPriv: Indicates that messages between the agent and the manager are
authenticated by unencrypted
authPriv: Indicates that messages between the agent and the manager are both
authenticated and encrypted
17.6
SSH
The secure shell (SSH) provides a secure and authenticated stream over the transport
control protocol (TCP) layer. The 7342 ISAM FTTU implements SSH version 2. On
top of this protocol, SSH implementations offer secure replacements for rsh, rlogin,
rcp, ftp, and telnet.

17-7
17 Security
The main capabilities of SSH are:
Secure Command shell is the secure version of the typical shell. It enables
commands and applications to be executed from the command line.
Secure file transfer (SFTP) handles secure file transfers by encrypting usernames,
passwords, and data while using the same port as the SSH server, which prevents
the opening of another port.
Note For the SSH server and SFTP client feature, the
7342 ISAM FTTU supports a single SFTP transfer at a time. Do not

perform concurrent transfers to the P-OLT. See the 7342 ISAM FTTU
Operations and Maintenance Procedures Guide using TL1 and CLI
for configuration information.
Figure 17-4 shows how SSHv2 secures communications.
Figure 17-4 SSHv2 security
SSH CLI
client appl
ssh client
SSH Appl. protocol

SSH transport
authentic, conn.
NMS
ssh server
7342 ISAM FTTU
SSH
client
Secure link for CLI/TL1
SSH
Server
SFTP
client
Secure link for SFTP
InterPeak
SFTP
Client
File
Secure link
for SW&DB
SSH CLI
server appl
SFTP
Server
DB of client pubKeys
or passwords
SFTP
Server
ISAM pubKey
ISAM privkey
supported algos
SFTP client
uname/pwd
Secure link for the transfer

from file server to 7342 ISAM FTTU (SW&dDB)
18968
The SSH transport layer provides authentication, encryption, and integrity.

Encryption is provided by a negotiated Diffie-Hellman or public-private key
exchange to negotiate a shared session secret: the symmetric key for 3DES. The
connection layer provides multiplexing of different streams over the transport layer.
User authentication provides authentication of client to server. Secure FTP is the
FTP client. It is used to download or upload files to or from the platform.
Table 17-1 shows the 7342 ISAM FTTU platform SSH and SNMP authentication
and authorization configurations.
17-8

17 Security
Table 17-1 SSH and SNMPv3 security combinations
Security
protocol
Encryption
algorithm
Authentication
algorithm
Authentication
mechanism
Combinations
SSH
Hmac-sha-1
Hmac-sha-1-96
Nothing
Encryption only
Authentication only
Encryption and authentication
Hmac-sha-1
Hmac-md5
Username and
password. A
different
username and
password are
required for each
SNMP engine
Nothing
Authentication only
Encryption and authentication
SFTP
SNMPv3
3DES
blowfish
AES
DES-56
DES-56
Username and
password
Username and
Public/Private
key
The SSH authentication algorithm manages password and public key login attempts
as follows:
When a user attempts to connect via telnet, the system verifies whether the IP
address is locked and responds as follows:
If the IP address is locked, the system closes the connection.

If the IP address is not locked, the user can make up to three connection attempts.
The number of connection attempts permitted depends on the value configured for
the SSH server connection parameter.
If a login attempt fails (because a username and password are mismatched, a timeout
occurs, or a connection breaks), the system logs a login failure event.
If a login attempt succeeds, the system logs a login success event.
When a login failure occurs, the system begins monitoring failed login attempts
as follows:
If the system is monitoring individual IP addresses, it increases the IP address login

failure counter by one, and adjusts the global last fail time to the current time.
If the system assumes an attack is occurring, it monitors login failures globally.

Each time a failure occurs, the system increases the global login failure counter by
one, and updates the global last fail time to the current time.
If the system is monitoring less than five IP addresses globally when a connection
failure occurs for another IP address, it starts monitoring the new login failure, sets
the login failure counter to one, and adjusts the global last fail time to the current
time.
If the system is monitoring five IP addresses globally when a login failure occurs for
another IP address, it sets the global login failure counter to the sum of the failed
login counters for the five IP addresses plus one, adjusts the global last fail time to
the current time, and stops monitoring individual IP addresses.
If a successful login occurs, the system responds as follows:

If the system is monitoring login failures globally, it stops global monitoring and
resets the count of all previous failures.
If the system is monitoring login failures for an IP address, it stops monitoring the
IP address and resets the login failure counter for that IP address.

17-9
17 Security
The system monitors the failed login times and counters as follows:
The system decreases the failed login counter (global or IP address) by one when the
current time is greater than the value determined by the following calculation:
current time > last failed login time + 15 minutes
The system stops monitoring failed login attempts when the applicable failed login
counter (global or IP address) is zero.
A login attempt is permitted as follows:

When the applicable login failure counter (global or IP address) is less than three.
When the current time is greater than the value determined by the following
calculation (the applicable global or IP address login failures are used):
current time > last fail time + max(15, (login failures - 3) * 2)
Table 17-2 shows lockout times that the SSH authentication algorithm enforces for
assumed password attacks.
Table 17-2 Lockout times for failed login attempts
Number of IP
addresses
Lockout time(2)
1st failed login group
1-5
no effect
1st failed login group (IP address a)
2nd failed login group
1-5
2nd failed login group (IP address b)
3rd failed login group
2 minutes
2-5
no effect
Failed login attempts
(1)
no effect
3rd failed login group (IP address c)
4th failed login group
1-2
4 minutes
3-5
no effect
4th failed login group (IP address d)
1-3
6 minutes
4-5
no effect
5th failed login group (IP address e)
1-4
8 minutes
no effect
6th failed login group (IP address f)
1-5
7th failed login for any group
10 minutes
(1 of 2)
17-10

17 Security
Number of IP
addresses
Lockout time(2)
1-5
12 minutes
1-5
1-5
1-5
Failed login attempts
(1)
14 minutes
15 minutes
15 minutes
(2 of 2)
Notes
(1)
If the user attempts to log in from another IP, there is no delay.
(2)
The system returns to normal 2.5 hours (10 x 15 minutes) after the attack stops.
17.7
802.1x authentication
The 7342 ISAM FTTU implements the authenticator part of the IEEE 802.1x
protocol to authenticate ONT LAN user ports for IPoE traffic. The 802.1x protocol
is only applicable to residential bridge mode. In residential bridge mode,
VLAN-tagged frames are not supported for 802.1x.
The P-OLT maintains the 802.1x authentication state by terminating the 802.1x
protocol and authenticates the user using the RADIUS server. Authentication is only
performed by the RADIUS server. Local authentication is not supported. The optical
network terminal (ONT) provides the filters for blocking and unblocking a local area
network (LAN) port.
There is no interaction between 802.1x and dynamic host configuration protocol
(DHCP) or Point-to-Point Protocol (PPP). After the system authenticates a port using
802.1x, the user can use DHCP or PPP.
802.1x support assumptions

The 7342 ISAM FTTU supports 802.1x authentication based on the following
assumptions:
Authentication is supported only on LAN ports at the ONT and not for the plain
old telephone system (POTS) lines.
Authentication is performed on an ONT UNI basis. The highest priority GPON
encapsulation module (GEM) port ID that is configured on the user network
interface (UNI) is used for authentication.
17-11
17 Security
The user does not send user IDs and the domain name during authentication. The
system uses the default domain.

The disconnection of servers is not required.
Support for non-EAP RADIUS servers is not required.
The assignment of VLANs by the RADIUS server is not required.
There is no local authentication for 802.1x when the RADIUS server fails.
Authentication protocols
The 7342 ISAM FTTU supports extensible authentication protocol (EAP) over
RADIUS between the P-OLT and the RADIUS server for 802.1x authentication. The
following authentication protocols are supported when the EAP is used:
MD5-Challenge, as defined in RFC 2284

OTP, as defined in RFC 2284
generic token card, as defined in RFC 2284
TLS, as defined in RFC 2716
The 7342 ISAM FTTU system is not required to support VLAN selection based on
RADIUS response.
The 802.1x protocol can be enabled or disabled for each 7342 ISAM FTTU system
or for each ONT UNI.
Port-based authentication
The 7342 ISAM FTTU supports port-based authentication. The port is the ONT
UNI. MAC-based authentication is not required. Accounting is based on each port,
not on the MAC. The accounting session is linked to the session of the first
authenticated user. Interim accounting is supported and is based on a configurable
time interval.
There are two MAC configuration scenarios for authentication:
When MAXMAC is 1, the first MAC address to be authenticated is learned on the

bridge port for the duration of session timeout (not the FDB aging timeout). The
MAC address is learned on all VLANs configured on the bridge port. No other
MAC addresses are learned.
When MAXMAC is greater than 1, MAC learning occurs after authentication is
successful. All MAC addresses are learned dynamically and age out using the
FDB aging timer. The system responds with EAP-Success message if other users
on the port try to authenticate after the port is authorized for traffic.
When the authenticated user logs out, the system performs the following actions:
closes the port for traffic

stops accounting for the port
sends an identity request as multicast over the port to invite any potential users of
the port for authentication
opens the port for traffic again only after a successful authentication
17-12

17 Security
sends new identity requests only after the held period expires if the authentication
fails
sends periodic identity request messages until the port is authenticated

does not require re-authentication
flushes the FDB entries that correspond to the port
When the maximum MAC value on a bridge port is changed by the operator to a
lower value, the system performs the following actions:
flushes all the forward database (FDB) entries on the port

closes the associated ONT UNI for data traffic
sends identity request as multicast over the port in order to invite any potential
users of the port for authentication
opens the port for traffic after successful authentication
User session disconnection by system

The 7342 ISAM FTTU supports the following three types of user disconnections:
When the RADIUS requests disconnection, the system does not send an
accounting stop message. The system sends a failure message to the first
authenticated user on the port and initiates the authentication of other users on the
port.
When the maximum session duration is expired. The system sends a failure
message to the first authenticated user on the port and initiates other users on the
port to start authentication.
When there is a request to disable or delete a user port, the system gracefully
terminates the user sessions on the port before the port is disabled or deleted. User
session accounting data is sent to the RADIUS accounting servers when the
session is terminated.
Statistics and operational data

The 7342 ISAM FTTU provides statistics and operational data for the authenticator,
as described in the IEEE 802.1x MIB requirement document.
The system provides visibility to the intermediate 802.1x states during the
authentication phase of a user session.
Restart scenarios
If the NT card restarts or is removed, all 802.1x sessions are terminated gracefully.
After the restart, an accounting-on message (if enabled) is sent to each potential
RADIUS server. An EAP Request Identity is sent to all 802.1x-enabled ports in the
system to re-initiate the authentication of users.
If the NT card switches over, the existing 802.1x sessions are retained. However, the
sessions that are being authenticated are lost.

17-13
17 Security
If the LT card restarts or is removed, all 802.1x sessions are terminated and a logout
message is not sent. An accounting-stop message is sent to RADIUS server for each
session. An EAP Request Identity is sent to all 802.1x-enabled ports on the LT to
re-initiate the authentication of users.
If the operator requests reboot on the LT card, the 802.1x sessions that were created
on the LT card are terminated and a logout message is not sent. An accounting-stop
message is sent to the RADIUS server for each session. An EAP Request Identity is
sent to the 802.1x enabled ports on the LT to re-initiate the authentication of users.
If all RADIUS servers of a VRF are unreachable, such as during an NT restart or
network problems, the OLT provides two options: accept or reject all authentication
requests. The default is to reject all authentication requests, which means there is no
local authentication. When Accept All is configured, an EAP success message is
returned to the ports that are trying to authenticate with a lease time of 30 min.
Re-authentication
To ensure that there is no service interruption during re-authentication, it is required
re-authentication of the supplicant must occur before the session expires. The
supplicant does not cause any service interruption during re-authentication. New
accounting-stop or accounting-start messages are not sent due to re-authentication.
The P-OLT supports the re-authentication state. The configuration of the
re-authentication function is made on a port basis and includes enabling or disabling
re-authentication and setting the re-authentication period.
The RADIUS Termination Action attribute is supported. If a Termination Action is
received, re-authentication is performed only at the request of the RADIUS server.
The RADIUS server overrides local configuration of re-authentication in the P-OLT.
If re-authentication is enabled on a port, the Session Timeout value returned by
RADIUS service is used as the re-authentication period. If the RADIUS server does
not return a Session Timeout value, the re-authentication timer for the port that is
configured by the management system is used.
If there is no response from an RADIUS server for re-authentication due to an NT
card switchover, the P-OLT treats the re-authentication as a successful one for 30
min.
If re-authentication is disabled for a port, the Session Timeout value returned by
RADIUS server is used to terminate the sessions. Re-authentication initiated by the
management system is not required.
During re-authentication, traffic to and from the user is not interrupted. The port
forwards bidirectional traffic until re-authentication is completed. If
re-authentication fails, the port is changed to unauthorized state.
An EAP Request Identity message is sent to the port when the re-authentication timer
expires.
17-14

17 Security
17.8
System log for security and NE actions

The NE supports system logs, also known as syslog. This system log contains actions
performed on the NE, behavior of the NE that may provide troubleshooting
information, even after a reset, and security-related information for administrators.
Based on information contained in the syslog, the administrator can:
trace and audit the behavior of the NE

review operator actions
change the security settings
Figure 17-5 shows the syslog system.
Figure 17-5 Syslog system
Syslog record
storage
Configuration
query results
SHub logs
Authentication
CLI configurations
Syslog
system
Local file system
TL1 configurations
View management
from stations
Send syslogs to
remote servers
18901
All syslog messages include a timestamp, based on the NE system clock, to identify
the time the logged action or event occurred. System log messages also provide a
description of the action that is being logged, and identifies the remote host terminal
of the user performing the logged action.
Users with root, administrator, or security access control can view the syslog files.
Logged message or information types

The following types of messages are logged:
unauthorized login attempts or security attacks

when a login identifier is changed, added, or deleted
when an ACL is created, modified, or deleted
when software is modified
when a login password is changed, added, or deleted

17-15
17 Security
when a login password aging threshold is changed, added, or deleted

when an authorized login or logout occurs
For NE system logging, the following information on the state of the NE is logged:
BCM counters
resource failure statistics
memory error counters
port link status
CPU packet counter
protocol packet counters
event triggered logging for application resets and watchdog timer resets
LT card resets and LT card transitions to the operational state
protection switch events
Message filtering
Security administrators can control what is seen in the syslog. Syslog entries can be
filtered based on the severity level of the message. Severity levels ranked highest to
lowest, showing the parameter filter name in parentheses, are:
emergency (EM)
alert (AL)
critical (CR)
error (ER)
warning (WN)
notice (NO)
info (IN)
debug (DBG)
Syslog format
Consider the following format information when viewing system log information.
The message length can be up to 1024 bytes; longer messages that have been
truncated are indicated in the TRUNCATE field.
The message type is indicated in the FACILITY field.

The message severity is indicated in the SEVERITY field.
The HOSTNAME indicates the static IP address, system name, or dynamic IP
address, in that order.
The application generating the message is indicated in the APP-NAME field.
Only ASCII characters are used in the MSG field.
17-16

17 Security
Syslog file destinations

Security administrators can specify the destination for logging. When the system log
data is configured to be sent to a file, and the file is configured to be uploaded, the
syslog file is uploaded to the remote server based on the IP address and directory path
specified. Possible syslog destinations include:
17.9
all CLI terminals

all TL1 terminals
local file
remote syslog server, to house system logs
User account management

The NE supports user account management, which allows administrators to:
disable the threshold for the maximum number of login attempts before a user is
locked out
set login identifier length
age passwords
restore a locked out session
disable user IDs that have not been used for a specified period of time
17.10
IPSec
Internet protocol security (IPSec) is a suite of protocols and support components that
provide security at the network or IP packet processing layer of network
communication. The 7342 ISAM FTTU implements IP version 4 and supports only
transport mode.
Table 17-3 lists the protocols and components that make up the IPSec protocol suite.
Table 17-3 IPSec protocol suite
IPSec core protocols
IPSec support components
IPSec authentication header (AH)
Encryption/hashing algorithms
Encapsulating security payload (ESP)
Security policies/security associations
Internet key exchange (IKE)/key management

17-17
17 Security
The combination of these core protocols and support components provide varying
levels of security. IPSec provides two different types of security at the IP layer:
Authentication which protects the integrity of the message and ensures that the
data has not been changed during transmission. Authentication also protects
against certain types of attacks, such as replay attacks. Both IPSec core protocols,
AH and ESP, support authentication.
Privacy which encrypts the contents of the message using hashing algorithms
such as message digest 5 (MD5) or secure hash algorithm (SHA-1). These
hashing algorithms require that an initial key be set up. This key can be created
manually using configuration or automatically assigned using the IKE protocol.
Of the two IPSec core protocols, ESP supports payload encryption while AH does
not.
When IPSec is enabled, all inbound and outbound packets must pass through a filter
called the security policy database (SPD) to determine if each packet maps to a
security association (SA). The SPD checks its rule table to determine whether a
packet maps to an SA and, if so, how IPSec should process this packet.
Figure 17-6 shows the internal structure of the IPSec protocol suite.
Figure 17-6 IPSec internal protocol suite
Application
process
Error logs to system audit file

IKE
Application
protocol
Negotiates, modifies, and deletes SAs

System manager
API
Configures
IPSec
policies
SAD
Points to
SPD
Consults
Consults
Asks for
SA creation
Socket layer
Transport protocol (TCP/UDP)
Security protocol
AH, ESP
IP
Link layer protocol
19066
Each SA describes a secure connection for data traffic traveling in one direction only
between devices. Bidirectional protection between two devices requires that
individual SAs be set up for traffic traveling in each direction.
Setting up a SA between devices requires that initial keys be exchanged between the
devices. Key exchange is performed either statically, by provisioning both devices
manually, or dynamically using the IKE protocol. The dynamic provisioning option
provides application programming interfaces (APIs) that allow IPSec core protocols
to request dynamic setup of a SA. Dynamic provisioning is more commonly used
than static provisioning.
17-18

17 Security
A set of three parameters containing the security parameter index (SPI), IP

destination address, and security protocol identifier is used to identify individual
SAs. These parameters are added to AH or ESP packet headers by the transmitting
device to link each secure packet with an SA. The receiving device can then use the
parameter information to return an index to the security association database (SAD)
action table to determine what type of IPSec action must be applied to the incoming
packet. SAD index entries are made either manually, by provisioning a static SA
entry into the database, or dynamically by the IKE protocol after the completion of
a SA negotiation.
See the procedures for configuring IPSec and IKE in the 7342 ISAM FTTU
Operations and Maintenance Procedures Guide using TL1 and CLI.
Sun Solaris and OLT interworking

The following issues should be noted while configuring your IPSec service:
When setting up a SA between a device running Sun Microsystems Solaris 10 and

the optical line termination (OLT), it is recommended that the duration of the SA
on the OLT be provisioned to last for a shorter time than the duration provisioned
using Solaris. When the SA is provisioned in this way, the OLT initiates the
re-keying process and the SA is renewed at the end of phase 1 without any error.
If the SA duration is provisioned using Solaris to be shorter than the duration for
OLT, then Solaris initiates the re-keying process. In addition to the usual handling
of this situation according to a protocol, Solaris 10 sends an initial contact
message. Rather than allow the SA to pass on to phase 2, Solaris treats the SA as
if it is complete and causes the protocol to request the establishment of a new
session.
When retrieving ESP keys using Sun Microsystems Solaris 10, the characters in
the string will differ from those you saved. The discrepancy in ESP key values is
due to Solaris performing error detection by inserting an odd parity bit following
seven bits of key data. For example, 4E/01001110 changes to 4F/01001111
because Solaris inserts an additional 1 at the end of the string in order to prevent
there being an even number of 1s in the string.
17.11
Anti-spoofing mechanism
The 7342 ISAM FTTU supports two features to protect against spoofing:
gratuitous ARP discard

source address anti-spoofing
Gratuitous ARP discard
A gratuitous ARP request is an ARP packet where the sender IP address and the
target IP address are the same. Attackers can use gratuitous ARP requests to corrupt
the ARP cache of a router by sending out a gratuitous ARP request that claims to be
the default router.
The 7342 ISAM FTTU supports a discard mechanism that filters incoming traffic for
gratuitous ARP requests. When gratuitous ARP discard is enabled, incoming
gratuitous ARP requests are discarded.
17-19
17 Security
Gratuitous ARP discard is implemented on a per ONT UNI port basis. See
7342 ISAM FTTU Operations and Maintenance Procedures Guide using TL1 and
CLI for configuration information.
Note Gratuitous ARP discard only applies for residential bridge
VLANs; in VLAN cross-connect mode, gratuitous ARP requests are
always forwarded.
Source address anti-spoofing

Source address spoofing is an attempt to gain entry to a system by posing as a trusted
source. Although the packet cannot be routed back to the initial source, source
address spoofing can lead to unnecessary network congestion and to possible denial
of service.
To block unauthorized traffic, the 7342 ISAM FTTU supports an anti-spoofing
mechanism that limits source address spoofing. Upstream traffic arriving at the ONT
is validated for source address. Authorized packets are forwarded and non-validated
packets are discarded, as illustrated in Figure 17-7.
Figure 17-7 ONT packet authorization
ONT
Forward authorized packets
Upstream packets
Authorize
packets
Discard
unauthorized
packets
Authorized
source addresses
19075
Source address anti-spoofing is implemented in either static or dynamic mode.
Static mode enables the table of authorized source addresses to be provisioned

statically by an operator for one of the following anti-spoofing control types:
MAC only
IP only
MAC and IP
Dynamic mode enables the table of authorized source addresses to be provisioned
both statically by an operator and dynamically through DHCP, and supports the
anti-spoofing control type IP-only.
Source address anti-spoofing filters are applied as follows:
For IP-only anti-spoofing, packets that match a configured IP source address are
forwarded, and non matching packets are dropped.
For MAC and IP anti-spoofing, packets that match a configured pair of MAC
source address and IP source address are forwarded, and non-matching packets
are dropped.
17-20

17 Security
MAC-only anti-spoofing can be implemented in one of two modes:

Inclusive mode forwards packets that match a configured MAC source address, and
drops non matching packets.
Exclusive mode forwards packets that do not match a configured MAC source
address, and drops matching packets.
Exclusive mode is used when you want to protect the 7342 ISAM FTTU against
virus-infected computers that send traffic using the MAC address of the default
router, which is in the computers ARP cache table.
Not all anti-spoofing control types apply to all traffic. Table 17-4 identifies the
anti-spoofing control types and any traffic exemptions by source address
anti-spoofing mode.
Table 17-4 Anti-spoofing control types and traffic exemptions
Source address
anti-spoofing mode
Anti-spoofing control type
Traffic exemptions
Static
MAC-only anti-spoofing
Is applied to all data traffic
IP-only anti-spoofing
Is not applied to non-IP traffic,

such as:
MAC and IP anti-spoofing

Dynamic
IP-only anti-spoofing
PPPoE
ARP
EAPOL, EAP
Is not applied to DHCP packets to

allow a subscriber to obtain a
DHCP lease.
The anti-spoofing control type limits the number of authorized source address
entries.
When static or dynamic source address anti-spoofing is enabled, the LT card
downloads the static entries provisioned for an ONT UNI port to the ONT by way of
OMCI. When a static entry is removed or anti-spoofing is disabled, the LT card
notifies the ONT to remove the corresponding anti-spoofing filter(s).
When dynamic anti-spoofing is enabled, the LT card forwards the currently leased
IP addresses to the ONT by way of OMCI after an IP address is leased, or a DHCP
lease expires or is released. When a UNI port has reached its maximum allowed
number of IP source addresses, the LT card drops any subsequent DHCP ACKs with
a leased IP address that is not in the lease table. IP source addresses that are added
dynamically through DHCP survive ONT restarts, LT restarts, and NT switchovers.
See 7342 ISAM FTTU Operations and Maintenance Procedures Guide using TL1
and CLI for configuration information.
Per-service anti-spoofing
This feature allows the operator to set up dynamic or static IP anti-spoofing on a
per-service basis, for example, the HSI service. The dynamic IP anti-spoofing allows
up to eight IP addresses to be learned. The static IP anti-spoofing allows up to eight
IP addresses to be specified by the operator.

17-21
17 Security
17-22

18 VLANs
18.1 Overview
18-2
18.2 General description

18.3 VLAN types
18-2
18-4
18.4 VLAN models
18-8
18.5 VLAN tagging
18-12
18.6 Frame processing at the LT
18-20
18.7 Frame processing at the ONT
18-25
18.8 Network interface CAC bandwidth check

18.9 VLAN bridging scalability
18-35
18-37

18-1
18 VLANs
18.1
Overview
This chapter provides information about the virtual local area network (VLAN)
strategy for the 7342 ISAM FTTU.
The P-OLT and the ONT uses Ethernet layer 2 for services and data transport, which
supports VLANs as defined in the IEEE 802.1q.
Traffic from the Ethernet network is always tagged with a VLAN membership and
uses residential bridge or a cross-connect mode. Traffic from the subscriber side can
be tagged or untagged.
Each VLAN on the LT and each UNI port on an ONT are configurable for upstream
and downstream traffic. The tagging options of traffic are shown in Table 18-1. For
additional tag handling information, see:
VLAN tagging
Table 18-1 Tagging options for upstream and downstream VLAN traffic
Traffic direction
Tagging options
See
Upstream and
downstream at the
LT
Stacked VLAN
Section 18.5
Unstacked VLAN
VLAN pass-through mode
Upstream at the
ONT
Untrusted
Section 18.5
VLAN pass-through
VLAN translation
EtherType/VLAN translation
EtherType classification
Flexible
Downstream at the
ONT
Transmit tagged traffic
Section 18.5
Transmit untagged traffic
TL1 and CLI for VLAN configuration procedures.
18.2
General description
The following sections define the purpose of VLANs in the 7342 ISAM FTTU.
18-2

18 VLANs
Definition
A LAN is a local area network and is defined as all devices in the same broadcast
domain. A VLAN divides a physical LAN into multiple virtual LANs whose
membership is not necessarily based on location. Each VLAN represents a different
broadcast domain.
VLAN specifications are contained in the Institute of Electrical and Electronics
Engineers (IEEE) 802.1q standards.
Purpose
A VLAN is typically used to group physically dispersed end-stations into a single
broadcast domain. Even though end-stations may be physically attached to different
LAN segments in different physical locations, they can communicate as if they were
on a common LAN when the end-stations are associated to a VLAN.
You can create broadcast domains by putting switch ports in VLANs. All ports in a
single VLAN are in a single broadcast domain. Figure 18-1 shows an example of
three VLANs: VLAN A, VLAN B, and VLAN C, where:
ports 1, 7, and 8 on switch A and ports 4 and 7 on switch B are in VLAN A and
are therefore in the same broadcast domain
ports 2, 4, 6, and 9 on switch A and ports 3 and 6 on switch B are in VLAN B,

and therefore are in the same broadcast domain
ports 3 and 5 on switch A and ports 1, 2, 5, and 8, and 9 on switch B are in
VLAN C, and therefore are in the same broadcast domain
Figure 18-1 Example of VLAN
Network
Switch
1 2 3456 7 89
Switch
123456 7 8 9
VLAN
A
VLAN
B
VLAN
C
17877

18-3
18 VLANs
The 7342 ISAM FTTU uses VLANs to facilitate the communication between
network service providers (NSPs) and subscribers and to deliver services over the
GPON. Subscriber-to-subscriber communication is not how VLANs are intended to
be used with the 7342 ISAM FTTU.
Services from NSPs are delivered to the 77342 ISAM FTTU over the Ethernet
metropolitan area network (EMAN) connection using VLANs. You can associate
multiple VLANs from NSPs to a network port on the NT card installed in the P-OLT,
and then associate those VLANs to an LT-interface port on the NT card, and a GPON
port on the LT card for GPON access. Depending on the VLAN mode, a VLAN from
the NSP can be attached to multiple LT cards and GPON ports. Management,
subscriber, HSI, and multicast traffic are carried between the NSP and the
subscribers connected to the GPON through these VLANs.
VLANs are manually configured using a management session with the P-OLT.
Alternately, a VLAN may be configured automatically under 802.1x control, which
you can then associate to an ONT GEM port. An ONT GEM port must be manually
removed from a VLAN.
The 7342 ISAM FTTU supports two forwarding modes: VLAN cross-connect mode
and residential bridge VLAN mode. Both of these forwarding modes can be used
when planning your network configuration. In addition, the 7342 ISAM FTTU
supports two VLAN configuration models: the VLAN per subscriber model and the
VLAN per service model.
18.3
VLAN types
The 7342 ISAM FTTU supports three VLAN types:
Residential bridge VLAN

Cross-connect VLAN
Flow mirroring VLAN
A residential bridge VLAN can be configured at the LT card to operate in either
MAC learning mode or C-VLAN learning mode for downstream forwarding of
traffic to the subscriber. See Chapter 12 for more details.
The VLAN types are described in the following sections.
Residential bridge VLAN

In the residential bridge VLAN mode, multiple subscribers can be associated to a
single VLAN from an NSP to allow those subscribers to access the services of the
NSP using a single VLAN ID. User-to-user communication is not supported in
residential bridge mode. Upstream traffic from subscribers is always sent towards the
NSP.
Caution You cannot have the same VLAN between the NSP and
multiple P-OLTs on the same EMAN. The VLAN between the
P-OLT and NSP in the Ethernet network must have a unique ID. The
risk of flooding caused by broadcast frames from other P-OLTs on the
network could cause performance degradation.
Figure 18-2 shows a basic residential bridge VLAN.

18-4

18 VLANs
Figure 18-2 Residential bridge VLAN model
NSP IP
network
NSP 1
User A
User B
User C
User D
User E
User F
User G
NSP 1
NSP 2
NSP 3
EMAN
NSP IP
network
NSP 2
7342 FTTU
NSP IP
network
NSP 3
= NSP 1-VLAN
= NSP 2-VLAN
= NSP 3-VLAN
18917
In Figure 18-2, users A through C can access NSP 1-VLAN, users D and E can
access NSP 2-VLAN, and users F and G can access NSP 3-VLAN. Each NSP has its
own forwarding table in the P-OLT that is associated with its VLAN ID. When a
subscriber generates a frame, or a frame is received from the NSP, a MAC address
lookup is performed in the forwarding table identified by the VLAN ID.
The residential bridge VLAN supports unidirectional multicast downstream traffic
where broadcasting towards all subscribers on the GPON is not desired. You can
configure precisely which subscribers have access to a VLAN. This type of VLAN
is also used for IGMP signaling.
Note Separate multicast VLANs between the ONT and the P-OLT
must be configured to carry multicast data traffic and IGMP signaling
traffic for IPTV services. At least one multicast VLAN must be
configured between the edge equipment and the P-OLT. Multicast
VLANs are unidirectional in the downstream direction only.
Cross-connect VLAN
In VLAN cross-connect mode, there is a one-to-one mapping between the VLAN
from the NSP and the subscriber. Only one cross-connect VLAN from the NSP can
be associated with only one user port on the LT card installed in the P-OLT. A single
subscriber at the ONT side of the GPON connection is associated with that
cross-connect VLAN. Each cross-connect VLAN on the network requires a unique
VLAN ID. Any traffic issued by the subscriber is passed transparently towards the
network using the selected cross-connect VLAN.
Only one cross-connect VLAN from the NSP can be associated with a user port on
the LT card installed in the P-OLT. A single subscriber at the ONT side of the GPON
connection is associated with that C-VLAN.

18-5
18 VLANs
Figure 18-3 shows the basic VLAN cross connect with three C-VLANs from an NSP
on the EMAN side. Each C-VLAN connects to different GPON ports on the
7342 ISAM FTTU P-OLT, and each C-VLAN is associated with a single subscriber
connected to the GPON through an ONT. Every subscriber requires a unique
C-VLAN for bidirectional communication with the NSP.
Figure 18-3 C-VLAN cross-connection model
C-VLAN to GPON port
cross-connects
EMAN
GPON
P-OLT
GPON ports
C-VLANs
to NSPs
C-VLANs
to ONTs
18924
The incoming C-VLAN from the NSP on the EMAN has a unique VLAN ID. This
VLAN ID is mapped to a specific GPON port on one of the LT cards installed in the
P-OLT, which is connected to the GPON. Traffic from the NSP is broadcast over the
GPON to all ONTs connected to the GPON. Any subscriber UNI port on an ONT
that is configured with HSI services associated to the VLAN ID that is being
broadcast can accept the traffic. Consequently, traffic issued by the subscriber is
transparently forwarded to the network-side using that VLAN ID.
Each subscriber requires their own unique C-VLAN. When configuring an Ethernet
UNI port at the ONT, you must enter the unique VLAN ID from the NSP. This
associates the NSP C-VLAN to the subscriber.
The subscribers C-VLAN is used for HSI services and carries all bidirectional
traffic, including: HSI, VoIP, VOD, MS TV unicast streams, and instant channel
change transactions.
Flow mirroring VLAN

The 7342 ISAM FTTU supports mirroring of subscriber traffic. Mirroring is the
process of duplicating packets. The original packets are forwarded to their
destination and a copy is sent to a mirror VLAN. The mirror packets can be viewed
using a packet sniffer device that is attached to the destination mirror port.
Mirroring can be used to:
troubleshoot problems with subscriber packet delivery and content

help service providers meet regulations by providing itemized call records and
wiretaps, as authorized by investigative authorities
18-6

18 VLANs
The 7342 ISAM FTTU supports up to 16 flow mirroring VLANs. Each flow
mirroring VLAN can be associated with one or more bridge ports, including:
ONT Ethernet port

MoCA port
VoIP client
VDSL2 port
Mirroring is available for upstream and downstream unicast traffic; multicast traffic
is not mirrored.
Tagging of mirror packets
Mirroring of traffic occurs on the LT card. The mirror packet inherits the source and
destination MAC addresses, and the priority level of the original packet; the outer
VLAN ID is replaced with the VLAN ID of the flow mirroring VLAN. Table 18-2
lists the field specifications for tagging of mirror packets.
Table 18-2 Tagging specifications for mirror packets
Field
Value
MAC source address
MAC source address of original packet
MAC destination address
MAC destination address of original packet
VLAN ID
VLAN ID of flow mirroring VLAN
p-bit
p-bit of original packet
The original downstream packets are forwarded to the subscriber, the original
upstream packets are forwarded to the network, and the mirror packets are forwarded
to their new VLAN. No learning of MAC or C-VLAN addresses is performed for
these VLANs.
Summary of features
Table 18-3 summarizes the 7342 ISAM FTTU features of the flow mirroring
VLANs.
Table 18-3 Features of flow mirroring VLANs
Feature
Support
Support for up to 16 flow mirroring VLANs
Mirroring of multiple bridge ports to the same flow mirroring VLAN
Mirroring of downstream traffic from the network side
Mirroring of upstream traffic originating from a subscriber port
No learning of MAC or C-VLAN addresses

18-7
18 VLANs
18.4
VLAN models
The 7342 ISAM FTTU supports two VLAN configuration models:
VLAN per subscriber model

VLAN per service model
Each model is described in the following sections.
VLAN per subscriber model

In the VLAN per subscriber model, each ONT has a unique residential bridge or
cross-connect VLAN. Figure 18-4 shows the network topology of the VLAN per
subscriber model for two subscribers. One subscriber is connected using a modular
ONT (M-series) and the other is shown connected using either an indoor ONT
(I-series) or an outdoor ONT (O-series).
Figure 18-4 Network topology of the VLAN per subscriber model for two subscribers
NT
VLAN
(subscriber)
VLAN
(IPTV)
LT
Ethernet
O-series ONT
I-series ONT
RG
10/100/1000 Base T
10/100
Base T
Computer
IPTV
Phone
Voice
Phone
Set-top box
M-series
ONT
VLAN
(subscriber)
Ethernet
VDSL
VDSL
modem
RG
10/100/
1000
Base T
IPTV
10/100
Base T
Computer
Voice
Phone
Voice
Set-top box
Phone
Phone
18194
Figure 18-5 shows the connection of a subscriber using the business ONT.
18-8

18 VLANs
Figure 18-5 VLAN per business ONT subscriber connection
NT
VLAN
(subscriber)
VLAN
(IPTV)
LT
Ethernet
Business
ONT
RG
10/100/1000 Base T
10/100/1000
Base T
Computer
IPTV
Phone
Voice
Phone
VLAN
(CES DS1/E1)
MEF-8
DS1/E1
Set-top box
18959
There can be a maximum of eight GPON encapsulated module (GEM) port

identifications (IDs) for each Ethernet UNI port at the ONT. This means that each
service must use less than eight priority bits and less than eight port IDs if there is
more than one service on a UNI.
A VLAN per subscriber carries traffic with all levels of priority to the network. Each
LAN port may have one or more GEM port IDs on the GPON interface, but the port
IDs are all attached to the same VLAN as a single bridge port.
At startup, the residential gateway (RGW) or router sends a dynamic host
configuration protocol (DHCP) request to get the IP address allocated. The gateway
can set the priority bits for each service in the Ethernet frames that it sends upstream.
Alternatively, the ONT can perform differentiated service code point (DSCP) to
priority bit (p-bit) marking.
The voice GEM port ID must be a separate bridge port in this model, but is attached
to the same VLAN for the subscriber as the other port ID of the subscriber.
Alternatively, the voice bridge port from all subscribers are attached to a dedicated
voice VLAN.
For the business ONT, a separate VLAN and bridge port are used for CES DS1 and
E1 traffic across the GPON using MEF-8 layer 2 Ethernet packetization.
The VLAN per subscriber model supports configuration for stacked VLANs or
unstacked VLANs. In unstacked VLANs, the service VLAN (S-VLAN) is unique to
a subscriber; in stacked VLANs, the combination of (S-VLAN, C-VLAN) is unique
to a subscriber.
VLAN per service model

In the VLAN per service model, every service is assigned a residential bridge VLAN.
All subscriber bridge ports associated with a service are attached to the
corresponding VLAN.
Figure 18-6 shows the network topology of the VLAN per service model where
subscribers have three different services: voice, IPTV, and data. Each of these
services is provided through a separate bridge port and a separate VLAN.

18-9
18 VLANs
Figure 18-6 VLAN per service model
NT
LT
VLAN
(Data)
Ethernet
VLAN
(IPTV)
IPTV
O-series ONT
I-series ONT
RG
10/100/1000 Base T
10/100
Base T
Computer
Phone
Voice
Phone
Set-top box
M-series
ONT
VLAN
(Voice)
Ethernet
VDSL
VDSL
modem
RG
10/100/
1000
Base T
IPTV
10/100
Base T
Computer
Voice
Phone
Voice
Set-top box
Phone
Phone
18227
Figure 18-7 shows the network topology of the VLAN per service model where
subscribers have three different services: voice, IPTV, and data. In this case, the
shared S-VLAN for VoIP services allows ONT to ONT communication via the LT
card. Each of these services is provided through a separate bridge port and a separate
VLAN.
18-10

18 VLANs
Figure 18-7 VLAN per service model with shared S-VLAN for VoIP
NT
LT
VLAN
(Data)
Ethernet
VLAN
(IPTV)
IPTV
O-series ONT
I-series ONT
RG
10/100/1000 Base T
10/100
Base T
Computer
Phone
Voice
Phone
Shared
S-VLAN
Set-top box
M-series
ONT
VLAN
(Voice)
Ethernet
VDSL
VDSL
modem
RG
10/100/
1000
Base T
IPTV
10/100
Base T
Computer
Voice
Phone
Voice
Set-top box
Phone
Phone
20049
Figure 18-8 shows the VLAN per service model for a business ONT that has four
services: voice, IPTV, data, and CES DS1 or E1. The DS1 or E1 traffic is
encapsulated as layer 2 Ethernet using MEF-8 for transport across the GPON.
Figure 18-8 VLAN per service model for the business ONT
NT
VLAN
(data)
LT
Ethernet
Business
ONT
RG
10/100/1000 Base T
VLAN
(IPTV)
IPTV
VLAN
(voice)
Voice
10/100/1000
Base T
Computer
Phone
Phone
VLAN
(CES DS1/E1)
MEF-8
DS1/E1
Set-top box
18958

18-11
18 VLANs
18.5
VLAN tagging
VLAN tag support affects service frame delivery and performance. Tagging of an
Ethernet frame consists in adding a IEEE.802.1q tag of four bytes that specifies the
VLAN ID and the p-bit (from 0 to 7). Figure 18-9 shows tagging of an untagged
frame. Because a VLAN tag is added, the trunking device recalculates the frame
check sequence (FCS) on the modified Ethernet frame.
Figure 18-9 Tagging of an Ethernet frame
DA
SA TYPE/LEN DATA FCS

X
DA
SA
Untagged Frame
TAG TYPE/LEN DATA FCS Tagged Frame

20035
Frames coming from the network side are generally tagged with a VLAN used in
either residential bridge or cross-connect mode. Untagged frames might also be
received, for example, when a network port is attached to a VLAN-unaware device.
In this special case, a port-based default VLAN is normally required on the network
port. Where a port-based default VLAN is not specified, untagged frames are
discarded.
Frames coming from the subscriber side can be tagged or untagged.
Each S-VLAN and ONT UNI are configurable for tagging:
An S-VLAN on the PON is configurable for tagging in one of three VLAN

tagging modes, and in one of three upstream p-bit marking modes.
An ONT UNI is configurable for tagging in one of two downstream tagging

modes, and in one of six upstream tagging modes.
The 7342 ISAM FTTU alters the frame at the LT based on the tagging configuration
of the S-VLAN, and at the ONT based on the upstream and downstream tagging
configuration of the ONT UNI. The 7342 ISAM FTTU applies the same VLAN
tagging configuration to all traffic in the same S-VLAN, and the same upstream and
downstream ONT UNI tagging configuration to all services and flows on the same
port.
The following sections describe:
18-12
VLAN tagging modes at the LT

P-bit marking modes at the LT
Downstream tagging modes at the ONT UNI
Upstream tagging modes at the ONT UNI
Compatible tagging modes

18 VLANs
VLAN tagging modes at the LT

The 7342 ISAM FTTU supports the following S-VLAN tagging modes:
Stacked VLAN mode

Unstacked VLAN mode
The VLAN tagging modes are described in the following sections.
Stacked VLAN mode
VLAN stacking is a technique that allows the VLAN space in a network to be

scalable beyond the traditional 4000-VLAN space. 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. One service-VLAN (S-VLAN)
bundles multiple smaller customer-VLANs (C-VLANs).
VLAN stacking supports an aggregation model such that you can assign multiple
subscribers to the same S-VLAN. Each subscriber is assigned a unique C-VLAN.
In VLAN stacking, the NSP can specify subscriber end-to-end connectivity while
remaining transparent to the EMAN. The S-VLAN at the EMAN side is associated
with a GPON port at the LT card. In the downstream direction, the LT strips the
frames of their outer tag, and C-VLANs, which were carried within the S-VLAN, are
then passed through to the subscribers that are associated with the GPON port.
In the upstream direction, the P-OLT receives frames from the ONTs that are either
priority-tagged or C-VLAN tagged. The P-OLT adds the S-VLAN tag and sends the
frames to the network with both tags attached. In some cases, such as for internal
EVCs with all-to-one bundling, triple-tagged frames are sent and received from the
network. All traffic in the S-VLAN is forwarded to the NSP.
In a frame, the S-VLAN is distinguished from the C-VLAN through EtherType:
EtherType of the S-VLAN is provisionable at the system level using the CLI
command configure system with a default value of 8100 hexadecimal
EtherType of the C-VLAN is always 8100 hexadecimal

A stacked VLAN can also be enabled for single-tagged frames. In this case,
single-tagged frames are passed through downstream to the subscribers as untagged
frames, and upstream to the network as singled-tagged frames.
Figure 18-10 shows a cross-connect VLAN in stacked VLAN mode.

18-13
18 VLANs
Figure 18-10 Cross-connect VLAN in stacked VLAN mode
C-VLAN to GPON port
cross-connects
EMAN
P-OLT
S-VLAN
GPON
GPON ports
C-VLANs
to ONTs
C-VLANs
to NSPs
18925
Note In stacked VLAN mode, a single C-VLAN per ONT can be

configured for all voice traffic originating from the ONT. In this
provisioning scenario, both bearer and signaling traffic use the same
C-VLAN. This feature is not applicable for the M-300 series modular
ONTs.
Unstacked VLAN mode
Unstacked VLANs carry frames that are singled-tagged. When VLANs are
configured as unstacked, the P-OLT sends frames to the network with a single
S-VLAN tag, and frames to the ONT as priority-tagged.
VLAN pass-through mode allows single- and double-tagged frames to be

transparently passed through unchanged from the network to the RGW, and from the
RGW to the network. In the VLAN pass-through mode, the RGW is responsible for
tagging the frames with their C-VLAN ID and p-bit.
P-bit marking modes at the LT

An S-VLAN is configurable for p-bit marking in one of three modes. The LT sets the
p-bit in the outer tag of an upstream frame based on the p-bit marking mode of the
S-VLAN that is carrying the frame, as described in Table 18-4. The LT does not
change the p-bit in a downstream frame.
Table 18-4 P-bit marking mode
P-bit marking mode
Description
copy
The LT sets the p-bit in the S-VLAN tag to the p-bit in the C-VLAN tag of
the frame.
set
The LT sets the p-bit in the S-VLAN tag to the default p-bit specified for
the S-VLAN.
(1 of 2)
18-14

18 VLANs
P-bit marking mode
Description
map
The LT translates the p-bit in the C-VLAN tag to an S-VLAN p-bit using the
C-VLAN to S-VLAN mapping profile, and sets the p-bit in the S-VLAN tag
to the translated value.
(2 of 2)
The option copy applies to all VLAN tagging modes. The options set and map apply
only to an S-VLAN in stacked VLAN mode, to enable a network provider to bundle
a number of C-VLANs in an S-VLAN for a NSP while retaining the subscriber p-bit.
For a VLAN in either unstacked VLAN mode or pass-through mode, the C-VLAN
p-bit inserted by the CPE must be preserved in the S-VLAN tag.
A check mark in Table 18-5 shows compatible configurations.
Table 18-5 Compatible configurations for p-bit marking mode
VLAN mode
Residential
bridge
Cross-connect
CVLAN-learning
VLAN tagging
mode
P-bit marking mode

Copy
Map
Set
Stacked
Unstacked
Passthrough
Stacked
Unstacked
Passthrough
Stacked

The 7342 ISAM FTTU supports the following downstream ONT UNI tagging
modes:
Transmit to port with a tag

Transmit to port without a tag
The transmit to port with a tag allows the frames to pass through from the ONT to
the CPE as tagged frames.
The transmit to port without a tag strips the frames of their outer tag. Therefore,
double-tagged frames received at the ONT UNI are passed through as singled-tagged
frames; all others are passed through as untagged frames.
18-15
18 VLANs

The 7342 ISAM FTTU supports the following upstream ONT UNI tagging modes:
Untrusted mode
VLAN translation mode
VLAN translation mode with EtherType classification
EtherType classification mode
Flexible mode
Whereas all downstream traffic is considered trusted, upstream traffic can be either
trusted or untrusted. When the CPE is not a trusted device, the ONT UNI is
configured for upstream tagging in untrusted mode. All other tagging modes are
reserved for traffic from a trusted device.
The upstream tagging modes are described in the following sections.
Untrusted mode
The untrusted mode supports traffic from an untrusted CPE. The ONT does not trust
the markings in the frame. The ONT will overwrite the p-bit and C-VLAN ID of the
frames with the values configured for that particular ONT UNI.
In the VLAN pass-through mode, the ONT accepts the markings inserted by the
CPE, and processes the frames, based on the tags received from the subscriber. If an
IP frame is not tagged by the subscriber, the ONT can optionally derive the p-bit
from the DSCP in the IP header of the frame or use the port-based default.
VLAN translation mode provides flexibility in managing VLANs; it supports VLAN

swapping. It allows the customer to map a C-VLAN on the subscriber side to a
C-VLAN on the network side, so that when a VLAN is sent upstream, the same
VLAN is returned. The network provider can configure a mapping table between
C-VLANs and S-VLANs to accommodate C-VLAN to S-VLAN translation
according to WT-101
The network-side VLAN is typically configured in VLAN pass-through mode,
although VLAN translation mode can also operate in both the stacked and unstacked
VLAN modes. In both the stacked and unstacked VLAN modes, when a subscriber
sends a C-VLAN upstream, the same C-VLAN tag is returned.
Figure 18-11 provides a VLAN translation mode example.
18-16

18 VLANs
Figure 18-11 VLAN translation mode example
ONT translates
C-VLAN 200 to C-VLAN 500
C-VLAN 300 to C-VLAN 600
C-VLAN400 to C-VLAN 700
Default C-VLAN to C-VLAN 800
or drop
OLT passes C-VLANs thru

as S-VLANS (do not
overwrite VID or P-bits)
Service-1
RGW adds C-VLANs.

Any service can
use any p-bit
1
4
Service-2
RG
2
ONT
OLT
3
HSI Service-1
PORTID 101,
102: pbits 0-7
Service-3
PC
5
6
Trusted
Mode
Phone
STB
HSI Service-2
PORTID 103,
104: pbits 0-7
HSI Service-3
PORTID 105,
106: pbits 0-7
1 S-VLAN = 500
4 C-VLAN = 200
2 S-VLAN = 600
5 C-VLAN = 300
3 S-VLAN = 700
6 C-VLAN = 400
19046
In this example, HSI services one, two, and three are configured in VLAN translation
mode on the same ONT. Table 18-6 shows the VLAN mapping of UNI-side
C-VLANs to network-side C-VLANs for each HSI service. The S-VLANs to which
the HSI services are bound are configured in the VLAN pass through mode.
Table 18-6 VLAN translation configuration example
Service
UNI-side C-VLAN
Network-side C-VLAN
200
500
300
600
400
700
VLAN translation mode with EtherType classification
The VLAN translation with EtherType classification mode allows a VLAN on the
subscriber side to be mapped to a VLAN on the network side base. The ONT uses
the C-VLAN ID, EtherType field, and p-bit in the frame to locate the corresponding
service.

18-17
18 VLANs
For VLAN translation in combination with EtherType classification in unstacked,

pass-through mode, you can provision the EtherType, UNI C-VLAN, and network
C-VLAN combination, as required. This allows PPPoE and IPoE data paths that are
identified using the same p-bit and the same C-VLAN to be mapped to different
network VLANs. The p-bit and EtherType values are preserved during VLAN
translation. The combination of EtherType, p-bit, and C-VLAN values are used to
identify the network-side VLAN in the upstream direction. Downstream, the
network-side VLAN is translated into the appropriate C-VLAN.
By configuring the UNI with the correct EtherType and VLAN translation
combination, you can map the correct upstream and downstream forwarding
combinations. Table 18-7 shows the upstream forwarding configurations.
Table 18-7 VLAN translation and EtherType classification for upstream forwarding
Incoming
C-VID
Incoming
p-bit
Incoming
EtherType
Outgoing
C-VID
Outgoing
p-bit
Outgoing
EtherType
Outgoing
port ID
200
IPoE
600
IPoE
2000
200
IPoE
600
IPoE
2000
200
PPPoE
700
PPPoE
2005
300
IPoE
800
IPoE
2006
300
IPoE
800
IPoE
2007
Table 18-8 shows the downstream forwarding configurations.

Table 18-8 VLAN translation and EtherType classification for downstream forwarding
Incoming
port ID
Incoming
C-VID
Incoming
p-bit
Incoming
EtherType
Outgoing
C-VID
Outgoing
p-bit
Outgoing
EtherType
2000
600
IPoE
200
IPoE
2000
600
IPoE
200
IPoE
2005
700
PPPoE
200
PPPoE
2006
800
IPoE
300
IPoE
2007
800
IPoE
300
IPoE
EtherType classification mode
EtherType classification mode classifies traffic by EtherType. When a frame is

received, the corresponding EtherType service is selected based on the EtherType
and p-bit in the outer tag of the frame. The frame is sent unchanged to the LT on the
corresponding PPPoE or IPoE service.
Figure 18-12 provides an example of two HSI services on the same ONT UNI in
EtherType classification mode; the S-VLANs to which the HSI services are bound
are configured in unstacked VLAN mode.
18-18

18 VLANs
Figure 18-12 EtherType classification mode
ONT classifies upstream traffic
PPPoE traffic to GEM PORTS 101, 102
IPoE traffic to GEM PORTS 103, 104
S-VLAN = 500
Service-2
OLT overwrites the S-VLAN

tag and sends its as a single
tagged frame.
RGW sends both

PPPoE and IPoE
traffic on the same
Ethernet Port
to ONT.
PC
IPoE
RG
ONT
OLT
Service-1
S-VLAN = 700
HSI Service-1
PORTID 101, P-bits 0-3
Trusted
Mode
PPPoE
STB
HSI Service-2
20034
Flexible mode
The flexible mode provides different configuration options that allow a network
provider to control how frames are processed at the ONT. In flexible mode, the
following processing options are available:
ability to discard or process untagged frames received upstream at the ONT

ability to discard or process priority-tagged frames received upstream at the ONT
ability to priority-mark untagged IP frames from a trusted CPE using either the
DSCP in the IP header or the port-based default p-bit

ability to forward priority-tagged frames received upstream at the ONT as either
priority-tagged frames or as C-VLAN tagged frames
ability to simultaneously pass-through singled-tagged and double-tagged frames
from the CPE to the LT
ability to screen singled-tagged and double-tagged frames in upstream direction
using the tag protocol identifier (TPID); non-matching frames are processed as
untagged frames
ability to tag single and double-tagged frames with their TPID in the downstream
direction
ability to translate a subscriber VLAN on the UNI side to its equivalent subscriber
VLAN on the network side in both the upstream and downstream directions
ability to translate a subscriber p-bit on the UNI side to the subscriber p-bit on the
network side in both the upstream and downstream directions
Different configuration options can be combined, to meet a specific configuration

requirement. The flexible mode is principally used with Ethernet services for
business and residential applications that are configured in the two-level hierarchy of
portal and flow; see Chapter 25 for more information on these services.

18-19
18 VLANs
Compatible tagging modes

The LT and the ONT process frames independently. The operator must ensure that
the tagging configuration of the S-VLAN is compatible with both the downstream
and the upstream tagging configuration of the ONT UNI.
See the VLAN tagging training section in the 7342 ISAM FTTU Operations and
Maintenance Procedures Guide using TL1 and CLI for a list of compatible tagging
modes.
18.6

The LT processes a frame in the downstream direction based on the VLAN tagging
mode of the S-VLAN, and in the upstream direction based on the VLAN tagging
mode and p-bit marking of the S-VLAN. Each VLAN tagging mode and p-bit
marking mode have their own set of tagging rules, which instruct the LT how to
process the frames before sending them to the ONT or to the NT.
In the downstream direction, the LT can receive a single-tagged, double-tagged,

or triple-tagged frame from the NT, and can send a double-tagged,
singled-tagged, priority-tagged, or untagged frame to the ONT.
In the upstream direction, the LT can receive a priority-tagged, single-tagged, or
double-tagged frame from the ONT, and can send a single-tagged, double-tagged,
or triple-tagged frame to the network
The following sections describe VLAN tagging at the LT:
Downstream tagging at the LT

Upstream tagging at the LT
Downstream tagging at the LT
In the downstream, the LT either overwrites the outer tag of the frame, strips the
frame of its outer tag, or leaves the outer tag of the frame unchanged based on the
VLAN tagging mode of the S-VLAN. Table 18-9 lists the possible combinations of
VLAN modes, tagging modes, and the corresponding downstream tagging operation
at the LT.
Table 18-9 Downstream tagging at the LT
VLAN mode
Residential
bridge
VLAN tagging
mode
Stacked
Overwrites outer
tag
(1)
Unstacked
passthrough
LT
Strips outer tag
Leaves outer tag

unchanged
(1 of 2)
18-20

18 VLANs
VLAN mode
Crossconnect
VLAN tagging
mode
Stacked
LT
Overwrites outer
tag
(1)
Strips outer tag
Unstacked
passthrough
CVLANlearning
Stacked
Leaves outer tag

unchanged
(1)
(2 of 2)
Note
(1)
A VLAN in stacked mode can be enabled for single-tagged frames. In this special case, the LT sends
an untagged frame on the PON to the ONT.
The downstream tagging operations at the LT are described in detail in the following
sections
Downstream tagging in stacked VLAN mode
Table 18-10 describes the tagging of downstream frames at the LT in stacked VLAN
mode, and the resulting frames sent by the LT to the ONT.
Table 18-10 Downstream tagging at the LT in stacked VLAN mode
NT to LT
LT
LT to ONT
The NT sends a single-tagged

frame to the LT. (S-VLAN
tag)
If the S-VLAN is not enabled for

single-tagged frame, the LT discards
the frame.
If the S-VLAN is enabled for singletagged frames, the LT strips the

frame of its outer tag.
The LT sends an untagged

frame to the ONT.
The NT sends a
double-tagged frame to the
LT. (S-VLAN and C-VLAN tag)
The LT strips the frame of its outer

tag.
The LT sends a
single-tagged frame to the
ONT. (C-VLAN tag)
The NT sends a triple-tagged

and C-VLAN tag)
The LT strips the frame of its outer

tag.
The LT sends a
ONT. (C-VLAN tag)
Downstream tagging in unstacked VLAN mode
Table 18-11 describes the tagging of downstream frames at the LT in unstacked

VLAN mode, and the resulting frames sent by the LT to the ONT.

18-21
18 VLANs
Table 18-11 Downstream tagging at the LT in unstacked VLAN mode
NT to LT
LT
LT to ONT

tag)
The LT sets the VLAN ID in the tag to

0.
The LT sends a
priority-tagged frame to the
ONT.
The NT sends a
The LT discards the frame.

and C-VLAN tag)
Downstream tagging in VLAN pass-through mode
Table 18-12 describes the tagging of downstream frames at the LT in VLAN

pass-through mode, and the resulting frames sent by the LT to the ONT.
Table 18-12 Downstream tagging at the LT in VLAN pass-through mode
NT to LT
LT
LT to ONT

tag)
The LT leaves the frame

unchanged. (1)
The LT sends a
single-tagged frame to the
ONT. (S-VLAN tag)
The NT sends a
The LT leaves the frame

unchanged. (1)
The LT sends a
ONT. (S-VLAN and C-VLAN
tag)

and C-VLAN tag)
Note
(1)
Where a VLAN is configured in pass-through mode, the ONT UNI port is configured as a tagged port
to allow the VLAN ID to pass through to the CPE.
Upstream tagging at the LT

Table 18-13 lists the possible combinations of VLAN modes, tagging modes, and
p-bit marking modes, and the corresponding upstream tagging operation at the LT.
18-22

18 VLANs
Table 18-13 Upstream tagging at the LT
VLAN mode
Residential
bridge
VLAN
tagging
mode
P-bit
marking
mode (1)
Stacked
copy
LT
Overwrites
outer tag
Checks for
allowance
of singledtagged
frames
(4095) (2)
Unstacked
copy
Passthrough
copy
Stacked
copy
map
Unstacked
copy
Passthrough
copy
Stacked
copy
map
set
Inserts
translated
p-bit in
outer tag
map
set
CVLANlearning
Inserts
C-VLAN
p-bit in
outer tag
set
Crossconnect
Inserts
S-VLAN
p-bit in
outer tag
Notes
(1)
The p-bit marking mode applies in the upstream direction only.
(2)
When singled-tagged frames are allowed in a stacked VLAN, the LT overwrites the C-VLAN tag with the S-VLAN tag if the
C-VLAN ID has the special value of 4095.
The upstream tagging operations at the LT are described in the following sections
Upstream tagging in stacked VLAN mode
As a general rule, in stacked VLAN mode, the LT adds the S-VLAN tag before
sending the frame to the network. However, if the S-VLAN is enabled for
single-tagged frames, the LT strips the C-VLAN tag before adding the S-VLAN tag
if the C-VLAN ID has a special value, and sends a single-tagged frame to the
network.
The LT sets the VLAN ID in the outer tag to the VLAN ID of the S-VLAN, and sets
the p-bit in the outer tag based on the p-bit marking mode of the S-VLAN, as
described in Table 18-4.
Table 18-14 describes the tagging of upstream frames at the LT in stacked VLAN
mode, and the resulting frames sent by the LT to the NT.

18-23
18 VLANs
Table 18-14 Upstream tagging at the LT in stacked VLAN mode
ONT to LT
LT
LT to NT
The ONT sends a

priority-tagged frame
to the LT.
The LT adds the S-VLAN tag to the

priority-tagged frame.
The LT sends a
NT.
The ONT sends a tagged

frame to the LT.
(C-VLAN tag)
If the S-VLAN is not enabled for

single-tagged frames, the LT adds the
S-VLAN tag to the tagged frame.
The LT sends a
NT.
If the S-VLAN is enabled for

single-tagged frames, and the C-VLAN ID
has the value 4095, the LT strips the
C-VLAN tag, and adds the S-VLAN tag. (1)
The LT sends either a single

or double S-VLAN tagged
frame.
If the S-VLAN is enabled for

single-tagged frames, and the C-VLAN ID
does not have the value 4095, the LT
adds the S-VLAN tag.
The LT sends a
NT.
The LT adds the S-VLAN tag to the

double-tagged frame.
The LT sends a triple-tagged

frame to the NT.
The ONT sends a

double-tagged frame to
the LT. (S-VLAN and
C-VLAN tagged frame)
Note
(1)
See the 7342 ISAM FTTU Operations and Maintenance Procedures Guide using TL1 and CLI for
configuration requirements in stacked VLAN mode.
Upstream tagging at the LT in unstacked VLAN mode
Table 18-15 describes tagging of upstream frames at the LT in unstacked VLAN

mode, and the resulting frames sent by the LT to the NT.
Table 18-15 Upstream tagging at the LT in unstacked VLAN mode
ONT to LT
LT
LT to NT
The ONT sends a

to the LT.
The LT overwrites the C-VLAN tag with

the S-VLAN tag, using the S-VLAN ID and
the p-bit in the C-VLAN tag. (1)
The LT sends an S-VLAN

tagged frame to the NT.
The ONT sends a

single-tagged frame to
the LT. (C-VLAN tag)
The ONT sends a
the LT. (S-VLAN and
Note
(1)
18-24
For an S-VLAN in unstacked VLAN mode, the p-bit marking mode must be copy, to ensure that the
customer p-bit is preserved as inserted by the CPE.

18 VLANs
Upstream tagging in VLAN pass-through mode
Table 18-16 describes the tagging of upstream frames at the LT in VLAN

pass-through mode, and the resulting frames sent by the LT to the NT.
Table 18-16 Upstream tagging at the LT in VLAN pass-through mode
ONT to LT
LT
LT to NT
The ONT sends a

to the LT.
The LT overwrites the C-VLAN tag with

the S-VLAN tag, using the S-VLAN ID (1)
and the p-bit in the C-VLAN tag. (2)
The LT sends an S-VLAN

tagged frame to the NT.
The LT passes the frame through as is.
The LT sends a
NT.
The ONT sends a

the LT. (C-VLAN tag)
The ONT sends a
the LT. (S-VLAN and
Notes
(1)
To achieve the VLAN pass-through mode, so that the frame is sent to the network with the same
C-VLAN ID inserted by the CPE, the S-VLAN must be configured with the same C-VLAN ID.
(2)
For an S-VLAN in VLAN pass-through mode, copy must be the p-bit marking mode so that the
customer p-bit, as inserted by the CPE, is preserved.
18.7

An ONT UNI is configurable for tagging in one of two downstream tagging modes,
and in one of six upstream tagging modes. Each tagging mode has its own tagging
rules, which instruct the ONT how to process frames before sending them to the CPE
or to the LT.
In the downstream direction, the ONT can receive a double-tagged,

single-tagged, priority-tagged, or untagged frame from the LT, and can send a
double-tagged, single-tagged, priority-tagged, or untagged frame to the CPE.
In the upstream direction, the ONT can receive an untagged, priority-tagged,
single-tagged, or double-tagged frame from the CPE, and can send a
priority-tagged, single-tagged, or double-tagged frame to the LT.
The following sections describe tagging at the ONT:

Downstream tagging at the ONT
Upstream tagging at the ONT
Note VLAN translation tagging behavior may differ depending on
the type of ONT or MDU. See the 7342 ISAM FTTU Operations and
Maintenance Procedures Guide using TL1 and CLI for more
information.

18-25
18 VLANs
Downstream tagging at the ONT

Table 18-17 describes the downstream tagging operations at the ONT, based on the
downstream and upstream tagging modes of the forwarding ONT UNI port.
Table 18-17 Downstream tagging at the ONT
Upstream tagging mode of ONT UNI
port
Downstream tagging at ONT

Untrusted mode
The ONT leaves the frame as is.
The ONT swaps the network-side customer VLAN ID

with the UNI-side customer VLAN ID.
VLAN translation mode with EtherType

classification
The ONT swaps the network-side customer VLAN ID

with the UNI-side customer VLAN ID.
EtherType classification
Flexible mode
If the flow is configured for VLAN or p-bit

translation:
the ONT swaps the network-side C-VLAN ID with

the UNI-side C-VLAN ID, if applicable
the ONT swaps the network-side customer p-bit
with the UNI-side customer p-bit, if
applicable. (1)
In the flexible mode, an ONT UNI has a configured

TPID value:
for a single-tagged frame, the ONT inserts the

configured TPID value in the outer tag
for a double-tagged frame, the ONT inserts the
configured TPID value in the outer tag and the
TPID value 0x8100 in the inner tag is
transparently passed through

All upstream tagging modes
(2)
The ONT strips the downstream frame of its outer

tag.
Notes
(1)
Downstream p-bit translation is not performed if more than one UNI-side p-bit is mapped to the
same network-side p-bit. The p-bit is passed through as is.
(2)
When the CPE associated with an ONT UNI port can only generate, or accept untagged frames, data
frames transmitted towards the subscriber should be untagged frames.
18-26

18 VLANs
Upstream tagging at the ONT

In the upstream direction, the ONT can receive an untagged, priority-tagged,
single-tagged, or double-tagged frame from a CPE. The ONT processes the frame in
four stages as follows, before sending it to the LT as a single-tagged or double-tagged
frame:
1
The ONT uses the QoS marker profile to process frames in the first stage. The
ONT performs an initial screening of frames using the screening criteria in the
QoS marker profile. If a frame is accepted, the ONT either tags the frame (if the
frame is untagged), overwrites the VLAN ID in the outer tag, or leaves the frame
as is.
The ONT matches the incoming frame to a service or flow on the ONT UNI. If
a match is not found, the frame is dropped.
Where VLAN and p-bit translation are required, the ONT performs the
translation in the outer tag of the frame.
The ONT determines the frames GEM port, by matching the p-bit in the outer
tag to the p-bit mapping of queues in the priority queue profile of the service or
flow. A non-matching frame is dropped; a matching frame is directed to the
GEM port.
The ONT forwards the frame to the LT on the corresponding service or flow.
Table 18-18 describes the p-bit marking rules for marking untagged frames by frame
type. These p-bit marking rules apply to all tagging modes. See the
7342 ISAM FTTU Operations and Maintenance Procedures Guide using TL1 and
CLI for configuration details.
Table 18-18 P-bit marking rules for untagged frames
Frame type
P-bit marking rule
Untagged IP frame
In untrusted mode, the ONT uses the default p-bit of the ONT UNI
port to mark an untagged IP frame. In all other tagging modes, the
ONT marks the frame with a p-bit in one of two ways:
Untagged Non-IP frame
using the default p-bit for the ONT UNI port

deriving the p-bit from the DSCP in the IP header using the DSCP
to p-bit mapping profile
The ONT marks an untagged non-IP frame with its p-bit using the
default p-bit of the ONT UNI port.
The following sections describe the upstream tagging operations at the ONT by
upstream tagging mode.
Upstream tagging in untrusted mode
Table 18-19 describes the tagging of upstream frames at the ONT in untrusted mode,
and the resulting frames sent by the ONT to the LT.

18-27
18 VLANs
Table 18-19 Upstream tagging at the ONT in the untrusted mode
Upstream ONT UNI
tagging mode
CPE to ONT
ONT
ONT to LT
Untrusted mode
The CPE sends an

untagged frame to the
ONT.
The ONT adds the C-VLAN tag using

the port-based default p-bit and
C-VLAN ID.
The ONT sends a

tagged frame to
the LT.
The CPE sends a

priority-tagged frame to
the ONT.
The ONT overwrites the C-VLAN tag

using the port-based default C-VLAN
ID and p-bit.
The CPE sends a tagged

frame to the ONT.
Upstream tagging in VLAN pass-through mode
Table 18-20 describes the tagging of upstream frames at the ONT in the VLAN
pass-through mode, and the resulting frames sent by the ONT to the LT.
Table 18-20 Upstream tagging at the ONT in the VLAN pass-through mode
Upstream ONT UNI
tagging mode
CPE to ONT
ONT
ONT to LT
VLAN pass-through
mode
The CPE sends an

ONT.
The ONT tags the frame using the port-based

default C-VLAN ID, and sets the p-bit as
The ONT sends a

tagged frame to the
LT.
The CPE sends a

the ONT.
The ONT leaves the frame unchanged.
The ONT sends a

priority-tagged
frame to the LT.

frame to the ONT.
The ONT sends a

tagged frame to the
LT.
The CPE sends a

the ONT.
The ONT discards the frame.
Upstream tagging in VLAN translation mode
Figure 18-13 shows the algorithm used by the ONT to translate a UNI-side C-VLAN
to a network-side C-VLAN in VLAN translation mode.
18-28

18 VLANs
Figure 18-13 Translation algorithm in VLAN translation mode
Untagged frame
Add C-VLAN tag with
C-VLAN ID set to
port-based default
VLAN ID and p-bit set
to DSCP mapping value.
VLAN-tagged frame
Priority-tagged frame
Search for a service on the
ONT UNI port with matching
C-VLAN ID.
Was a
matching
C-VLAN ID
found?
Service match
is not found
Search for a default service
on the ONT UNI port.
Default service
is not found
Was a default
service found?
Frame is dropped
Default service
is found
Service match
is found
Does the
default service have
a provisioned networkside VLAN ID?
Network-side VLAN ID
is provisioned for service
Overwrite the C-VLAN ID with
the network-side VLAN ID
and retain p-bit.
Overwrite the C-VLAN ID with

the network-side VLAN ID
and retain p-bit.
is not provisioned
for service
Retain originalRetain
C-VLAN
original
ID
and p-bit.
C-VLAN ID
and p-bit
19456
Table 18-17 describes the tagging of upstream frames at the ONT in VLAN
translation mode, and the resulting frames sent by the ONT to the LT.

18-29
18 VLANs
Table 18-21 Upstream tagging at the ONT in VLAN translation mode
Upstream ONT UNI
tagging mode
CPE to ONT
ONT
ONT to LT
VLAN translation
mode
The CPE sends an

ONT.

The ONT sends a

priority-tagged
frame (1), or tagged
frame to the LT.
The ONT then uses the algorithm in

Figure 18-13 to overwrite the UNI-side C-VLAN
ID with the network-side C-VLAN ID.
(2)
The CPE sends a

the ONT.

frame to the ONT.
The ONT uses the algorithm in Figure 18-13 to

overwrite the UNI-side C-VLAN ID with the
network-side C-VLAN ID.
The ONT sends a

priority-tagged
frame (1), or tagged
frame to the LT.
The CPE sends a

the ONT.
Notes
(1)
If the network-side VLAN ID has the value of zero, the ONT sends a priority-tagged frame, otherwise, the ONT sends a
tagged-frame.
(2)
The ETSI MDUs can translate from a zero VLAN ID to a non-zero VLAN ID, but it cannot translate from a non-zero VLAN ID
to a zero VLAN ID. Therefore, for the ETSI MDU, upstream VLAN translation is possible, but downstream is not. As a result,
priority-tagged frames are not allowed from the CPE.
Upstream tagging in VLAN translation mode with EtherType classification
Figure 18-14 shows the algorithm used by the ONT to translate a UNI-side C-VLAN
to a network-side C-VLAN in VLAN translation mode with EtherType classification
mode.
18-30

18 VLANs
Figure 18-14 Tagging of upstream traffic in VLAN translation mode with EtherType classification
Untagged frame
Add C-VLAN tag with:
C-VLAN ID set to
port-based default
V-LAN ID
p-bit set to DSCP
mapping value for an
IP packet
p-bit set to port-based
default p-bit for a
non-IP packet
Tagged frame
Priority-tagged frame
Search for a service on the
ONT UNI port matching both
C-VLAN ID and Ether Type.
Was a
matching
C-VLAN ID
found?
Service match
is not found
Search for a default service
on the ONT UNI port.
Was a default
service found?
Default service
is not found
Frame is dropped
Service match
is found
Default service
is found
Does the
default service have
a provisioned networkside VLAN ID?
is provisioned for service
is not provisioned
for service
Overwrite theOverwrite
C-VLAN the
ID with
C-VLAN ID withOverwrite theOverwrite
C-VLAN the
ID with
C-VLAN ID
Retain
with originalRetain
C-VLAN
original
ID
the network-side
the network
VLAN IDside VLAN ID
the network-side
the network
VLAN IDside VLAN and
ID p-bit.
C-VLAN ID
and retain p-bit.
and retain p-bit.
and retain p-bit.
and retain p-bit.
and p-bit
19457
Table 18-22 describes tagging of upstream frames at the ONT in VLAN translation
mode with EtherType classification, and the resulting frames sent by the ONT to the
LT.

18-31
18 VLANs
Table 18-22 Upstream tagging at the ONT in VLAN translation mode with EtherType classification
Upstream ONT UNI
tagging mode
CPE to ONT
ONT
ONT to LT
VLAN translation
with EtherType
classification mode
The CPE sends an

ONT.

The ONT sends a

priority-tagged (1)
or tagged frame to
the LT.
The ONT then uses the algorithm in

Figure 18-14 to overwrite the UNI-side C-VLAN
ID with the network-side C-VLAN ID.
The CPE sends a
the ONT.
The ONT discards frame.

frame to the ONT.
The ONT uses the algorithm in Figure 18-14 to

overwrite the UNI -side C-VLAN ID with the
network-side C-VLAN ID.
The ONT sends a

priority-tagged (1)
or tagged frame to
the LT.
The CPE sends a

the ONT.
Note
(1)
The ONT sends a priority-tagged frame, if the network-side VLAN ID has the value of zero. Otherwise, the ONT sends a
tagged-frame.
Upstream tagging in EtherType classification mode
Table 18-23 describes tagging of upstream frames at the ONT in the EtherType
classification mode, and the resulting frames sent by the ONT to the LT.
Table 18-23 Upstream tagging at the ONT in EtherType classification mode
EtherType
classification of
frame
CPE to ONT
ONT
ONT to LT
PPPoE
The CPE sends an untagged

frame to the ONT.

default C-VLAN ID, and sets the p-bits as
The ONT sends a

tagged frame on the
PPPoE service.
The CPE sends a

ONT.
The ONT sends a

priority-tagged
frame on the PPPoE
service.

frame to the ONT.
The ONT sends a

tagged frame on the
PPPoE service.
The CPE sends a

ONT.
(1 of 2)
18-32

18 VLANs
EtherType
classification of
frame
CPE to ONT
ONT
ONT to LT
IPoE or anything
else
The CPE sends an untagged

frame to the ONT.

The ONT sends a

tagged frame on the
IPoE service.
The CPE sends a

ONT.
The ONT sends a

priority-tagged
frame on the IPoE
service.

frame to the ONT.
The ONT sends a

tagged frame on the
IPoE service.
The CPE sends a

ONT.
(2 of 2)
Upstream tagging in flexible mode
Table 18-24 describes the tagging of upstream frames at the ONT in flexible mode,
and the resulting frames sent by the ONT to the LT.

18-33
18 VLANs
Table 18-24 Upstream tagging at the ONT in flexible mode
Upstream ONT UNI
tagging mode
CPE to ONT
ONT
ONT to LT
Flexible mode
The CPE sends an

ONT.
If the ONT UNI is configured to drop untagged

frames, the ONT discards the frame.
If the ONT UNI is configured to receive

untagged frames, the ONT tags the untagged
frame using the port-based default C-VLAN ID
and sets the p-bit as described in Table 18-18.
The ONT sends a

single-tagged frame
to the LT.
If the flow is configured for VLAN translation,

the ONT swaps the C-VLAN ID in the outer tag
for the network-side C-VLAN ID.
If the flow is configured for p-bit translation,
the ONT swaps the p-bit in the outer tag for the
network-side customer p-bit.
The CPE sends a
the ONT.
The ONT screens the frame for the TPID value

configured for the ONT UNI port. For a
non-matching frame, the ONT processes the
frame as an untagged frame.
If the ONT UNI is configured to drop

priority-tagged frames, the ONT discards the
frame.
If the ONT UNI is configured to pass-through

priority-tagged frames, the ONT passes the
frame through as is.
The ONT sends a

priority-tagged
frame to the LT.
If the ONT UNI is configured to overwrite VLAN

ID with the port-based C-VLAN ID, the ONT
overwrites the VLAN ID.
The ONT sends a

single-tagged frame
to the LT.
If the flow is configured for VLAN translation,

the ONT swaps the C-VLAN ID in the outer tag
for the network-side C-VLAN ID.
If the flow is configured for p-bit translation,
the ONT swaps the p-bit in the outer tag for the
network-side customer p-bit.
The CPE sends a
the ONT.

configured for the ONT UNI port.
The CPE sends a

the ONT.

configured for the ONT UNI port.
18-34
For a non-matching frame, the ONT

processes the frame as an untagged frame.
For a matching frame:
If the flow is configured for VLAN
translation, the ONT swaps the C-VLAN
ID in the outer tag for the network-side
C-VLAN ID.
If the flow is configured for p-bit
translation, the ONT swaps the p-bit in
the outer tag for the network-side
customer p-bit.
For a non-matching frame, the ONT

processes the frame as an untagged frame.
For a matching frame, if the flow is
configured for VLAN translation, the ONT
swaps the C-VLAN ID in the outer tag for
the network-side C-VLAN ID; the p-bit is
preserved.
The ONT sends a

single-tagged frame
to the LT.
The ONT sends a

double-tagged
frame to the LT.

18 VLANs
18.8
Network interface CAC bandwidth check

A CAC check ensures available bandwidth on a network interface to support
requested services. Figure 18-15 illustrates the different levels in the network system
where a CAC bandwidth check is performed:
at the SHub network port or link aggregation group (LAG) of network ports,
whenever a VLAN is added to the SHub network port or LAG
for a S-VLAN, whenever a subscriber service, is added to an S-VLAN, or a flow
or portal is added to an S-VLAN with a bandwidth profile
at the GPON at the LT card, whenever a subscriber service is added to the GPON,
or a flow or portal is added to the GPON with a bandwidth profile
Figure 18-15 CAC bandwidth check
Services, flows, or
portals configured
Service
Traffic Flows with CIR/AIR/EIR
7342 OLT
GPON
S-VLAN
GE
CAC at
NT port
or LAG
S-VLAN
CAC for
S-VLAN
Capacity
S-VLAN
GPON
CAC
at the
LT
ONT
GPON
ONT
19239
For more information on bandwidth profiles, see Chapter 15 on QoS.
CAC at NT port or LAG

Whenever a SHub VLAN is created, the guaranteed downstream and upstream
bandwidths, as defined by the committed information rates (CIR), are specified.
When the SHub VLAN is associated with a 1-GE or 10-GE port, or a LAG on the
network SHub, a CAC check is performed on the port or LAG to determine if it has
sufficient bandwidth to support the new VLAN. Overbooking is not supported on the
SHub ports or LAGs.
Note The default CIR for VLANs configured on the SHub is 100
kb/s.

18-35
18 VLANs
Use the SHub Interface Port Control Status CLI command (show interface shub port)
to determine available upstream and downstream bandwidth on an SHub network
port before creating a VLAN on an network port or LAG. The SHub VLAN
Configuration CLI command (configure vlan shub) is used to configure upstream
and downstream bandwidth parameters on the SHub VLAN.
For information about CLI command syntax, refer to the 7342 ISAM FTTU CLI
Commands Guide.
CAC for S-VLAN capacity

Each S-VLAN is configured with the following bandwidth characteristics:
downstream and upstream guaranteed bandwidths

downstream and upstream overbooking factors to improve network efficiency
A CAC check is performed on an S-VLAN when a new service is provisioned, or
when a flow or portal is provisioned with a bandwidth profile. The CAC check
determines if the S-VLAN has available bandwidth to support the required EIR for
the service, flow, or portal. The CAC check ensures that the sum of the EIRs of all
services, flows, and portals on the S-VLAN is less than the S-VLAN guaranteed
bandwidth times the S-VLAN overbooking factor.
There are separate CAC checks for upstream and downstream directions.
PON CAC at the LT

The GPON performs limited upstream and downstream CAC checks to assure that
new service, flow, or portal provisioning does not exceed the available PON
bandwidth. The following calculations are performed when a new service is
provisioned, or when a flow or portal is provisioned with a bandwidth profile:
The CIR identified in the bandwidth profile is added to the sum of all other CIR
of services, flows, and portals. The CIR sum is compared against the available
downstream PON bandwidth.
The AIR identified in the bandwidth profile is added to the sum of all other AIR
of services, flows, and portals. The AIR sum is compared against the available
upstream PON bandwidth.
If the sum of all CIRs is less than the available downstream PON bandwidth, and the
sum of all AIRs is less than the available upstream PON bandwidth, then the
provisioning request is allowed.
The available downstream PON bandwidth is 2.488 Gb/s less the reserved bandwidth
for multicast less some reserved bandwidth for OMCI. The available upstream PON
bandwidth is 1.244 Gb/s less some bandwidth reserved for OMCI.
18-36

18 VLANs
PON bandwidth
The bandwidth available on the PON can be considered when configuring the system
for maximum performance. The following information is available for a specific
PON:
aggregate upstream provisioned CIR

aggregate upstream provisioned AIR
guaranteed upstream bandwidth that remains for further provisioning
aggregate downstream provisioned CIR
guaranteed downstream bandwidth that remains for further provisioning
maximum downstream multicast bandwidth allowed
The operator can use this information to determine how much bandwidth is left to
allot in the upstream or downstream direction.
GPON and SHub VLAN bandwidth synchronization

The operator is responsible for ensuring that the bandwidth configured for a VLAN
on the NT is the same as the bandwidth configured for the corresponding VLAN on
the SHub.
18.9
VLAN bridging scalability

The 7342 ISAM FTTU supports two types of VLAN bridging: residential bridge and
cross-connect bridging. Table 18-25 describes the scalability of VLAN bridges. See
Table 7-5 for more information about service capacity.
Table 18-25 VLAN bridging scalability
Description
Maximum
Notes
MAC addresses per bridge

port
1 to 128
This number is configurable from 1 to 128.
Bridge ports per GLT2
384
384 = 3 per user x 128 users per GLT2. The

assumption is 2 UNIs per ONT.
Bridge ports per GLT4
768
768 = 3 per user x 256 users per GLT4. The

assumption is 2 UNIs per ONT.
Bridge ports per residential

bridge
6176
6176 = 384 bridge ports per GLT2 x 16 GLT2 + 32

reserved
Bridge ports per system
6176
6176 = 384 bridge ports per GLT2 x 16 GLT2 + 32

reserved

18-37
18 VLANs
18-38

Services descriptions
19 VoIP overview
20 HSI service
22 Triple play service delivery architecture in access network
25 Ethernet services for business and residential applications


19 VoIP overview
19.1 Overview
19-2
19.2 Voice gateway mode
19-4
19.3 H.248 softswitch mode

19.4 SIP modes
19-6
19-8
19.5 VoIP service configuration

19.6 Security
19-12
19-38
19.7 VoIP call statistics
19-39
19.8 XML file configuration data for package C ONTs

19-40
19-1
19 VoIP overview
19.1
Overview
This chapter provides information about the implementation of the Voice over IP
(VoIP) service in the 7342 ISAM FTTU.
VoIP service operation modes

The 7342 ISAM FTTU provides different modes of operation for VoIP services.
These include voice gateway, H.248 softswitch, and session initiation protocol (SIP)
modes.
Voice gateway mode
When the service provider uses existing Class 5 switch for voice services, the
7342 ISAM FTTU uses the G6 voice gateway to interact with the switch and perform
loop emulation. The G6 voice gateway performs both the signaling and the bearer
path end-point functions.
H.248 softswitch mode
When the service provider uses the broadband data network for voice services, the
7342 ISAM FTTU interacts with the network through the ITU-defined H.248
protocol or the IETF-defined Megaco protocol to an H.248-based softswitch. In this
mode, the voice traffic and signaling may follow different paths through the network.
SIP modes
When the service provider uses SIP for VoIP services, the 7342 ISAM FTTU
interoperates in two SIP modes: SIP mode 1 or thin client mode, and SIP mode 2
or thick client mode.
In these modes of operation, the ONT performs user agent functionality. The two
modes of operation are to allow for different signaling behavior, especially for
advanced call features, to be handled correctly for the two very different signaling
characteristics.
The ONT provides special functionality for emergency calls (911) originating at the
ONT including blocking ONT software upgrades when a 911 call is in progress.
TISPAN support
Building upon the work already done by 3GPP in creating the SIP-based IMS (IP
Multimedia Subsystem), TISPAN and 3GPP are now working together to define a
harmonized IMS-centric core for both wireless and wireline networks.
This harmonized ALL IP network has the potential to provide a completely new
telecom business model for both fixed and mobile network operators. Access
independent IMS will be a key enabler for fixed/mobile convergence, reducing
network installation and maintenance costs, and allowing new services to be rapidly
developed and deployed to satisfy new market demands.
19-2

19 VoIP overview
The Alcatel-Lucent Feature Server 5000 is more than 80% compliant with all
TISPAN Release 1 features, with the exception of TS 183 023 (XCAP over the Ut
interface).
7342 ISAM FTTU access product line interoperates with Alcatel-Lucent TISPAN
compliant FS5000 from Release 04.04.16 and later.
Contact your Alcatel-Lucent support representative for a complete listing of all
TISPAN compliance details.
Common service operation mode features

Table 19-1 describes features that the VoIP service operation modes have in
common.
Table 19-1 Common features of VoIP service operation modes
Feature
Description
802.1p
The upstream VoIP traffic is marked with an 802.1p priority value according to the priority queue
profile and the following rules:
Exactly two priority queues must be used.

The priority queue with the highest mapped value is used for VoIP signaling, dynamic host
configuration protocol (DHCP), and file transfer protocol (FTP).
The other priority queue is used for bearer traffic.
For each traffic type, the traffic is tagged with the highest value mapped to its priority queue.
In the downstream direction, other values mapped to the two priority queues are used to map
frames to the appropriate GPON encapsulated module (GEM) port ID.
911
The ONTs do not have special requirements for 911 calls, except for SIP mode 2.
Bandwidth
profile
Bandwidth profiles are provisioned for both upstream and downstream traffic flows. These profiles
are for both signaling and bearer traffic. Bandwidth and priority queue profiles are defined at the
packet optical line termination (P-OLT) unit. The same set of profiles can be used for all VoIP traffic.
DSCP
The upstream signaling and bearer VoIP traffic is marked with differentiated services code point
(DSCP) values according to VoIP service and POTS port provisioning.
For non-SoC-based ONTs, signaling and bearer in the downstream direction must be marked with the
priority bits in the priority queue (PQ) profile for VoIP services. Otherwise, signaling is not directed
to the VoIP stack and the bearer is not directed to the voice path.
File download
The configuration profile can be downloaded from a file server. The file server IP address is manually
provisioned or learned through the DHCP server. The name of the file is provisioned. The configuration
profile contains a set of characteristic data for the analog phone and the VoIP service. The data
includes:
impedance settings
gain settings
ringing cadences
tone frequencies and cadences
For the SIP modes, the profile data is expanded to include additional service configuration
parameters.
IP addressing
Provisioning options are available to manually provision IP addresses through TL1, simple network
management protocol (SNMP), or learned through the DHCP or BRAS server.
MLT diagnostics
The same mechanized loop test (MLT) diagnostics are available in both modes of operation.
(1 of 2)

19-3
19 VoIP overview
Feature
Description
Option 82
identifier (1)
A provisionable string used by the DHCP relay is enabled on the service virtual local area network
(S-VLAN) with the configuration (CONF) option. The string allows a configurable identifier to be
associated with the VoIP service that is inserted by the DHCP relay agent at the P-OLT toward the
DHCP server.
Ping
The ONTs support ping responses.
(2 of 2)
Note
(1)
When another device is configured as the DHCP server and the 7342 ISAM FTTU is configured as a DHCP relay agent, the
Option 82 parameter should be enabled on both devices. This is to ensure that traffic passes correctly between the
devices.
19.2
Voice gateway mode

In the G6 voice gateway mode, the H.248/Megaco protocol is used for call control
signaling between the voice gateway and the ONT. The OLT interfaces with the
voice gateway through a layer 2 Ethernet network. Using the H.248 protocol, the
voice gateway controls voice calls, including the bearer channel to carry voice data
between the voice gateway and ONT. The signaling and bearer end-points are
identical.
Figure 19-1 shows the network topology when the voice service is delivered in a
voice gateway mode.
Figure 19-1 Voice gateway network topology
AMS
L2
Ethernet
cloud
GR303/
TR008
Phone
Class 5 PSTN
switch
Voice gateway
(G6)
OLT
ONT
Phone
Signaling and bearer channel end-points are same

18188
The G6 voice gateway mode supports two submodes as follows:
GR-303/TR008 mode for ANSI H.248 support

V5 mode for ETSI H.248 support
19-4

19 VoIP overview
GR-303/TR008 mode
The G6 voice gateway supports both GR-303 and TR008 interfaces with the Class 5
switch. In this mode, two types of message flows typically occur between the voice
gateway and the ONT: H.248/Megaco signaling and ABCD-bit loop-start signaling.
H.248/Megaco message-based signaling is used to set up and tear down calls. It sets
up the bearer path and DS0 connection.
ABCD-bit loop-start signaling controls the analog interface and is passed in the
bearer channel using RFC 2833 protocol. The G6 voice gateway converts the 2-bit
AB signaling used by the TR008 interface to the 4-bit ABCD loop-start signaling
used by the ONT.
GR-303/TR008 call flow
The following is a high-level description of the flow for the GR-303/TR008 type call
that is initiated by the PSTN side through a Class 5 switch.
1
After the voice gateway receives a GR-303 setup request, it sends an equivalent
H.248/Megaco connect message to the ONT. This establishes the bearer path
between the Class 5 switch and the ONT. After the bearer path is established, the
voice gateway acknowledges the GR-303 setup request to the Class 5 switch.
The Class 5 switch sends ABCD codes to ring the phone. The codes alternate
between ring-on and ring-off. The voice gateway forwards the codes to the ONT
transparently. During ringing, the Class 5 switch sends frequency-shift-keying
(FSK) tones along the bearer path between the first and second ring to deliver the
caller identifier information.
When the phone goes off-hook, the ONT reports the off-hook status using ABCD
signaling. The voice gateway forwards the signaling to the Class 5 switch. The
Class 5 switch stops sending ringing ABCD codes when it receives the off-hook
signaling, then allows the voice data to flow through the bearer path.
When the phone goes on-hook, the ONT reports the on-hook status using the
ABCD signaling to the voice gateway. The voice gateway forwards the signaling
to the Class 5 switch.
When the Class 5 switch receives the on-hook signaling, it sends a GR-303
release message to the voice gateway and disconnects the voice path. The voice
gateway in turn sends the H.248/Megaco message to the ONT to disconnect the
bearer path.
V5 mode
The G6 voice gateway supports V5.2 interfaces with the Class 5 switch. In this mode,
the voice gateway translates the V5.2 PSTN signaling messages into H.248 messages
to the ONT. These messages are used for all aspects of call control, including call
setup, call teardown, and analog interface control for ringing or off-hook/on-hook
notifications. The H.248 messages are also used to set up the bearer path and voice
connection with the ONT.

19-5
19 VoIP overview
V5 call flow
The following is a high-level description of the flow for a V5 type call that is initiated
from the PSTN side through a Class 5 switch.
19.3
After the voice gateway receives a V5 channel allocation request, it sends an

equivalent H.248/Megaco connect message to the ONT. This establishes the
bearer path between the Class 5 switch and the ONT. After the bearer path is
established, the voice gateway acknowledges the channel allocation request to
the switch.
The Class 5 switch sends Establish and Signal messages to ring the phone. These
messages indicate the ringing cadence number to use. The voice gateway
translates the messages to H.248 signaling and passes the cadence number on.
The ONT then rings the phone according to the profile data in the current
configuration profile for that cadence.
When the phone goes off-hook, the ONT reports the off-hook status using the
H.248 signaling. The voice gateway translates the H.248 signaling into a Signal
message to the Class 5 switch. The Class 5 switch connects the voice call to the
voice gateway. The ONT automatically stops the ringing and allows the voice
data to flow through the bearer path to the voice gateway.
When the phone goes on-hook, the ONT reports the on-hook status using the
H.248 signaling. The voice gateway translates the H.248 signaling into a Signal
message to the Class 5 switch.
When the Class 5 switch receives the Signal message for on-hook, it sends
Disconnect and channel de-allocation messages to the voice gateway and
disconnects the voice channel. The voice gateway in turn sends the H.248
signaling message to the ONT to tear down the bearer path.
H.248 softswitch mode

The H.248 softswitch application uses a full set of H.248/Megaco signaling
messages to support voice services. Most call features require some type of signaling
interaction with the softswitch.The softswitch supports features such as caller ID,
call waiting, and 3-way calling. See the appropriate ONT Customer Release Notes for
information about supported softswitches.
The ONT performs various functions under the direction of the softswitch.
notify the softswitch of off-hook and on-hook events

provide dial tone locally
collect dialed digits and send the digits to the softswitch
play ringback tone and busy tone
provide caller ID FSK transmission with data provided by the Softswitch
establish or disconnect real-time protocol (RTP) bearer path and RTP control
protocol (RTCP) to another VoIP media gateway
Figure 19-2 shows the softswitch network topology.
19-6

19 VoIP overview
Figure 19-2 Softswitch network topology
Management channel
Server (s) DHCP,

application, FTP etc.,
Softswitch
IP phone
PSTN
gateway
IP cloud
Signaling
channel
PSTN
cloud
BRAS
RJ11
L2
Ethernet
cloud
POTS
phone
RJ45
OLT
Class 5 PSTN
switch
ONT
POTS
phone
IP
phone
18189
The ONT supports redundant softswitch servers. When operating in a redundant

configuration, the ONT contacts the secondary server if the primary server is lost.
Note To implement redundant softswitch servers, you must use the
DHCP option 120 for a second softswitch IP address.
Softswitch call flow

The call flow associated with a conventional softswitch for traffic originating from
the ONT is generally the same as specified in the IETF/ITU-T H.248/Megaco call
flow.
One fundamental difference between the gateway mode and the softswitch mode is
that, in the softswitch mode, the Megaco signaling protocol instructs the ONT in
terms of playing tones, and on-hook and off-hook event through out-of-band
signaling messages.

19-7
19 VoIP overview
19.4
SIP modes
The 7342 ISAM FTTU supports two SIP modes:
SIP mode 1: thin client interworking with softswitches, such as Broadsoft

Broadworks
SIP mode 2: thick client interworking with softswitches, such as Nortel CS2000
In the two SIP modes, the SIP switches provide the SIP server functions, while the
ONT provides the SIP user agent functions, including the following.
controls the analog states of the POTS line to locally invoke call setup and call
tear-down
generates dial tone locally
collects dialed digits and send the dialed string to the SIP switch
plays ringback tone and busy tone
derives caller ID FSK from headers in signaling messages
supports NTP date and time for caller ID
establishes or disconnects an RTP bearer path and RTCP to another VoIP media
gateway
call statistics with call history
Redundancy in SIP mode 1 or SIP mode 2 is supported if a domain name is

configured for the registrar_route and outbound_proxy parameters in the SIP
provisioning data and a DNS server address is provided through DHCP; see
Table 19-7. The ONT automatically contacts the domain name server (DNS) and
obtain a list of A records or SRV records. The ONT uses the records to contact
possible SIP servers according to the methodology outlined in RFC 3268.
SIP service features

Table 19-2 lists the service features supported by the two SIP modes.
Table 19-2 SIP service features
Service
Description
SIP
mode 1
SIP
mode 2
Emergency number (911)
Basic 911 support
Enhanced 911 support
Denial of feature use
Emergency ringback
Forced hold
Call forwarding status

indications
Splash ring when a call is actually forwarded
Stutter dial tone while call forwarding is active
Call hold
Basic hold (flash hook supported)
Call transfer,
Blind and consultative call transfer
Call park
(1 of 2)
19-8

19 VoIP overview
Service
Description
SIP
mode 1
SIP
mode 2
Call waiting
Basic call waiting
Delivery of calling number and name
Cancel call waiting
Activate/deactivate/interrogate call waiting

(ETSI)
Calling party ID
Delivery of calling number and name
Conference calling
Call parties are joined together at a softswitch

server
Call parties in a 3-way conference are joined

together at an ONT
6-way conference
Direct connect (Hot Line)
Configurable directory number is called

automatically when a subscriber goes off hook
Direct connect (Warm

Line)
Configurable directory number is called

automatically when a subscriber goes off hook
and does not dial before the initial digit timeout
period.
Distinctive ringing
Outside call alerting
Priority call
Screening list
Teen line
Home intercom
Allows conversation between two phones on the

same physical POTS line as though in a normal
call, but without establishing a network
connection
Message waiting
indication (MWI)
Audible and visual MWI when a subscriber has

voice mail message waiting, including:
Y
Reminder ring
Stutter dial tone
Visual MWI
Outbound call dialing
Part of basic call
Bridged lines
Two or more lines sharing the same directory

number
Call pickup with Barge-in
Allows a third party to join a 2-way call
Suppressed ringing
Supports specialized telemetry devices used in

place of standard phone sets
Multiple SIP accounts
As many as 10 registrations are allowed for each

POTS line
(2 of 2)
Subscriber service codes for SIP mode 2
In SIP mode 2, the ONT supports service-feature related codes that are configurable
in the ONT, including the following:
*70 or 1170 to cancel call waiting for the duration of the current call
*52 or 1152 after a flash hook to place the remote party on hold
*54 or 1154, or *53 or 1153 to activate home intercom
19-9
19 VoIP overview
*41 or 1141 to initiate a 6-way conference call, or cause a consultation call to be

joined to an active 6-way conference
*43 or 1143 to release a consultation call instead of joining it to a 6-way

conference
*43# to activate call waiting service (ETSI)
#43# to deactivate call waiting service (ETSI)
*#43# to interrogate call waiting service activation status (ETSI)
By default, the subscriber invokes features such as 3-way calling or call waiting
using the methods described in the Bellcore GRs. However, the ONTs supporting
SIP voice service also support ETSI market-based methods of invoking calling
features when the enable_etsi SIP parameter in Table 19-7 is set to yes. Enabling this
parameter allows for different subscriber call feature controls, as shown in
Table 19-3.
Table 19-3 ETSI call feature configuration
Call feature
SIP provisioning
parameter
Example
Release active call, reduce to 2-way call
etsi_cw_release
R1
(1)
Toggle calls
etsi_cw_toggle
R2
(1) (2)
Merge calls, begin 3-way call
etsi_cw_merge
R3
(1)
Release held or new call, reduce to 2-way call
etsi_cw_release_held_
call
R0
Release active call, reduce to 2-way call
etsi_ch_release
R1
(1)
Toggle calls
etsi_ch_toggle
R2
(1)
Merge calls, begin 3-way call
etsi_ch_merge
R3
(1)
Release held call, reduce to 2-way call
etsi_cw_release_held_
call
R0
Split call, return to call hold (3-way call ends)
etsi_3wc_split
R2
(1)
Split call, return to call hold (3-way call ends, previous

call hold state entered
etsi_3wc_split_precon
f
R2
(1)
Call waiting
Call hold and call consultation
3-way call
Notes
(1)
R in the example column refers to register recall and the numbers are dialed digits.
(2)
R2 for the etsi_cw_toggle parameter indicates that using register recall (or flash hook) then dialing
2 causes the ONT to toggle between two calls during call waiting.
SIP call flow

Figure 19-3 shows the call flow for a SIP call that originates from the ONT.
19-10

19 VoIP overview
Figure 19-3 Call flow of a SIP call originating from the ONT
Phone
ONT
Softswitch
Off hook
Send dial tone or stutter tone
First digital dialed
Stop dial tone/stutter tone
Remaining digits dialed
INVITE (collected digits)
100 TRYING
180 RINGING
Send ring back tone
PRACK
200 OK (PRACK)
200 OK (INVITE)
Stop ring back tone
ACK
Speech path established
18585
Figure 19-4 shows the call flow for a SIP call that is terminated at the ONT.

19-11
19 VoIP overview
Figure 19-4 Call flow of a SIP call terminated at the ONT
Phone
ONT
Softswitch
INVITE
100 TRYING
Send ringing with caller ID
180 RINGING
PRACK
200 OK (PRACK)
Off hook
Stop ringing
200 OK (INVITE)
ACK
Speech path established
18586
19.5
VoIP service configuration

The VoIP framework consisting of signaling protocols like SIP does not specify any
standard way or mechanism of implementing a configuration interface. As
implemented in the 7342 ISAM FTTU, there are four possible sources of
configuration information for SIP. See Table 19-4 for the sources of SIP
configuration data.
Table 19-4 Sources of SIP configuration data
Source
Description
OMCI
OMCI communication is used to conduct service and protocol provisioning. OMCI data
is used to configure the overall VOIP service and individual POTS lines from the OLT.
A limited set of provisioning options for SIP are also provided using OMCI. OMCI data
is established using TL1 or SNMP commands at the OLT.
DHCP
IP addresses that are used for the voice service can be manually selected and
entered or automatically obtained. As an option to manual IP address provisioning,
a DHCP server can be used to automatically obtain IP addresses.
Configuration
profile file
Country-specific parameters are stored in a configuration profile file (XML file) to

allow the VoIP services to be configured for individual countries. Configuration
profile files can be embedded in the software load or obtained by FTP download.
When the configuration profile is downloaded using FTP, it may contain SIP-specific
provisioning parameters.
(1 of 2)
19-12

19 VoIP overview
Source
Description
iConfig
iConfig is an alternative to the configuration profile method of provisioning

SIP-specific parameters at the ONT. The iConfig external server communicates SIP
Provisioning data to ONTs. This process is intended to allow centralized control and
dissemination of provisioning data to multiple SIP devices, such as ONTs.
(2 of 2)
7342 ISAM FTTU VoIP service configuration is described in subsequent sections as

follows:
process for country-specific POTS configuration files

service and protocol configuration
configuration profile (embedded in the software load or FTP download)
iConfig (Sipping) configuration for SIP
VoIP service provisioning parameters
Process for country-specific POTS configuration files

In order for SIP configuration to work correctly in different countries, XML
download files are used. These XML files contain:
CDE data, related to hardware settings specific to a country, such as tone values
and ringing cadences.
SIP provisioning data, related to SIP-specific configuration parameters, allowing

for per-ONT and per-POTS line configurations.
The CDE data is gathered by Alcatel-Lucent and used to generate the XML
download files. The XML download files are shipped with the ONT software. The
XML download files are downloaded to the ONTs, and when the ONT initializes and
the VoIP client is activated, the XML content containing SIP configurations is
loaded into system.
XML files for package C ONTs

Some ONTs, such as those from package C, contain XML files already embedded.
These XML files contain pre-configured SIP and H.248 data, which defines how the
voice protocols run. See section 19.8 for more information.
Service and protocol configuration

Service and protocol configuration requirements are different between the voice
gateway mode and the softswitch mode.
Voice gateway mode
In the voice gateway mode, the service and protocol configuration must be manually
performed using the element management system (EMS). Voice gateway
deployments require some unique considerations during service and protocol
configuration; see Table 19-5.

19-13
19 VoIP overview
Table 19-5 Voice gateway mode considerations
Type
Consideration
ONT configuration
The static IP addresses must be derived and configured

along with termination identifiers on the ONT during the
POTS provisioning time. No DHCP function is expected.
Voice gateway configuration
The ONT IP addresses and the termination identifiers must

be configured on the voice gateway.
File download
The ONT is expected to use an embedded configuration for

voice gateway applications. File download is not necessary.
The embedded configuration profile is stored on the ONT
flash. ONTs are shipped from the factory with the
embedded profiles already installed. New configuration
files can be downloaded to the ONT flash via FTP.
ONT and voice gateway MAC

configuration
The ONT and voice gateway MAC addresses are fixed at the
ONT and the voice gateway. The MAC addresses are
exchanged as part of the ARP.
Softswitch modes
There are two softswitch modes: H.248/Megaco and SIP softswitch modes. In these
modes, some configuration elements associated with VoIP provisioning can be
derived automatically from the DHCP/BRAS servers on the network.
The ONT and the softswitch trigger the ARP proxy function for individual MAC
address learning.
Table 19-6 describes the use of different DHCP options in the different VoIP modes.
Table 19-6 DHCP options and VoIP modes
DHCP option
Function
Voice gateway
mode
H.248 Softswitch
mode
SIP mode 1
(for IP0E)
SIP mode 2
(for IPoE)
IP subnet mask
Not recommended
Supported
Supported
Supported
Default IP router
Not recommended
Supported
Supported
Supported
DNS server address
Not supported
Not supported
Supported
Supported
50
IP address of VoIP
service on the ONT
Not recommended
Supported
Supported
Supported
61
ONT client ID
Not recommended
Supported
Supported
Supported
66
FTP servers IP address

(used if FTP download
is needed)
Not recommended
Supported
Supported
Supported
90
DHCP authentication
Not recommended
Supported
Supported
Supported
(1)
(1 of 2)
19-14

19 VoIP overview
DHCP option
Function
Voice gateway
mode
H.248 Softswitch
mode
SIP mode 1
(for IP0E)
SIP mode 2
(for IPoE)
120
IP softswitch IP
addresses or domain
name
Not recommended
The first IP address

is the primary
server. The second
IP address is the
address of the
secondary server.
If a second IP
address is present,
it enables
redundancy.
Supported
Supported
(2 of 2)
Note
(1)
The clientid parameter is used as the H.248 message identifier (MID) field for H.248 signaling messages when DHCP is
disabled.
Configuration profile
The 7342 ISAM FTTU uses embedded or downloaded configuration profiles for
both the voice gateway and Megaco softswitch modes. This is also supported for SIP
and includes additional SIP-specific parameters.
Configuration profile in voice gateway and softswitch modes
The ONT supports configuration profiles related to different countries. The profile
settings for analog and digital data are specific to each country. Embedded or
downloaded configuration profiles have the same content and format, and are used
for both voice gateway and H.248 Softswitch modes.
The ONT software load contains embedded configuration profiles with the specified
file names. Embedded configuration profiles are needed when a file download is not
desirable. See the appropriate 7342 ISAM FTTU ONT CRN for information about the
countries that are supported in the embedded profiles.
The ONT can download the appropriate configuration profile using the FTP when
the ONT does not have the specified file name among its embedded configuration
profiles. The downloaded configuration profile is stored in flash memory and can
survive ONT restarts, software downloads, and software activation. Because the
ONT does not re-download a file automatically, any change to the contents of an
existing file on the file server has no impact on in-service ONTs.
To activate a new profile, you must use a different file name on the FTP server. VoIP
service on each ONT must be provisioned with the new file name. The ONT
automatically deletes a previously downloaded file with a name that is no longer
provisioned.
Configuration profile in SIP modes
In the SIP modes, additional data in the configuration profile may be used to
provision SIP services as part of the FTP download data. Table 19-7 summarizes this
additional provisioning data. The use of a configuration profile to provision SIP
services is a provisioning option at the ONT.

19-15
19 VoIP overview
iConfig
The ONT can communicate with a specialized server intended to allow centralized
control and dissemination of provisioning data to SIP devices, such as ONTs. The
protocol used for this communication is based on draft IETF standard
draft-ietf-sipping-config-framework, and is more simply referred to as iConfig or
Sipping.
This is an optional feature at the ONT as an alternative to the configuration profile
method of provisioning SIP-specific parameters at the ONT. The same parameters
summarized in Table 19-7 are supported with both methods.
When iConfig is enabled, the ONT contacts the specialized configuration server for
a root certificate to be used for subsequent access to provisioning data using TLS.
The configuration server notifies the ONT of provisioning data by supplying an
indirect HTTPS reference. The ONT then reads the provisioning data using HTTP
over TLS (HTTPS), and with HTTP Digest authentication.
Direct communication to the configuration server uses SIP protocol over UDP with
HTTP Digest (also known as MD5) authentication. The ONT is provisioned with the
IP addressees of the Configuration server and the HTTP Digest authentication
credentials as part of the VoIP client turn-up.
If the iConfig method is selected, there is no configuration profile selection. Default
data for U.S. applications will be used for all analog settings.
SIP-specific provisioning parameters

Additional SIP parameters can be provisioned. See Table 19-7 for a description of
SIP parameters and SIP mode in which they are supported.
Table 19-7 SIP-specific provisioning parameters
Parameter
Description
SIP mode 1
SIP mode 2
SIP user agent provisioning (There is only one set of data for the ONT.)
permanent_timer
The duration, in seconds, of the permanent timer

(sometimes known as the start dial timer). This timer
starts when an off-hook condition is detected on the POTS
line, and if it expires before any digits are received from the
POTS line, permanent treatment is applied to the line. This
is an optional parameter. This is a non-negative integer and
the value is expressed in seconds. The default value is 16.
Supported
Supported
interdigit_timer
The duration, in seconds, of the standard interdigital timer.

This timer starts after a digit is received from the analog line
interface, and if it expires before another digit is received,
dialing is assumed to be completed. This is an optional
parameter. This is a non-negative integer and the value is
expressed in seconds. The default value is 16.
Supported
Supported
critical_timer
The duration, in seconds, of the critical interdigital timer.

This timer starts at a point in digit collection specified by the
dialing pattern, and if it expires before another digit is
received, dialing is assumed to be completed. This is an
optional parameter. This is a non-negative integer and the
value is expressed in seconds. The default value is 4.
Supported
Supported
(1 of 17)
19-16

19 VoIP overview
Parameter
Description
SIP mode 1
SIP mode 2
timed_release
The duration, in seconds, of the Timed Release timer. To end

a conversation, the local or remote subscriber hangs up. If
the local subscriber hangs up, BYE is sent to the softswitch
immediately unless this was a termination end of the call. If
the local call was the termination call, BYE is not sent and
the idle state is entered until the re-answer timer expires or
BYE is received. The re-answer timer is configured using the
timed_release parameter.
Supported
Supported
This is an optional parameter. This is a non-negative integer

and the value is expressed in seconds. The default value is 10
seconds.
reanswer_timer
ON a terminating call, if the POTS line goes on-hook, the ONT

or MDU maintains the dialog and starts the reanswer_timer
value If the POTS line goes off-ook before the timer expires,
the POTS line will resume the dialog. If a BYE is received
before the timer expires, the ONT idles the POTS linke and
cancels the timer.
Supported
Supported
error_tone_timer
When an error response is received for a new INVITE request,

the parameter specifies the time the error tone is output
before starting signal treatment when the user stays
off-hook.
Supported
Supported
auto_connect_timer
The parameter specifies how long the ONT waits before

resuming a held remote call after an active remote call goes
on-hook during call features such as call waiting and
consultation call.
Supported
Supported
enter_key
The digit that is to be treated as an indication that dialing is

complete, when received at a point in digit collection where
it does not match the dialing pattern at that point. This is
typically used to signal the completion of dialing a speed
dialing number or an international number. This is an
optional parameter. The hash mark symbol # is the default
value.
Supported
Supported
codec
An audio format name, chosen from among the audio MIME

types registered with the IANA (many of which are listed in
RFC 3555). More than one codec setting may appear in the
provisioning data; the sequence of all such codec setting
values, in descending order of q value, is used by the user
agent to create an ordered list of codec formats sent in an
initial offer and is used to define the order of formats sent in
an answer. The audio/telephone-event format specified by
RFC 2833 is implicitly included by the user agent in all offers,
and in all answers to an offer that includes that format, and
thus a setting including that format is never required. The
following codec values are supported:
Supported
Supported
Supported
Supported
audio/PCMA (for G.711 A-law)

audio/PCMU (for G.711 Mu-law)
audio/G729 (for G.729)
Other values are silently ignored. These values are case
insensitive. The default value is audio/pcmu.
qos-dscp
The differentiated services code point (DSCP) value that

should populate the DS field of RTP packets sent by the user
agent. It is an integer value in the range of zero (0) to 63. The
default value is the value configured via SNMP/TL1.
(2 of 17)

19-17
19 VoIP overview
Parameter
Description
SIP mode 1
SIP mode 2
local-ports
A range of port numbers specifying the minimum and

maximum ports numbers to be used by the user agent for RTP
media. NOTE: Only one value is set for this parameter across
all ports in the system. This is a string. The range is specified
as a lower bound and an upper bound, separated by a dash.
These bounds are decimal integer values between 0 and
65535. The default range is 5004-6003.
Supported
Supported
enable_t38
Indicates whether T.38 support is enabled. This is a string

containing a value of yes or no. The default value is
yes.
Supported
Supported
enable_rfc2833
Indicates whether voice activity detection is enabled for

voice encoding. In order for DTMF tones to be encoded in RFC
2833 packets, there must be SDP negotiation and agreement
at both ends of the bearer channel. The ONT or MDU will
offer RFC 2833 or include it in an SDP response only if the
enable_rfc2833 is set to yes. This is a string containing a
value of yes or no.. The default value is yes.
Supported
Supported
When set to far_end_symmetry, during SDP negotiations of

the RFC 2833 payload type, the ONT offers the configured
dynamic_codec_payload_map_entry value for RFC 2833.
However, if the ONT receives an answer to an offer with a
different payload type, the ONT uses that payload type for
both the sending and receiving of RFC 2833 packets.
ONTs will explicitly include the SDP direction attribute of
sendrcv when the current call connection is in a 2-way
conversation.
enable_vad
Indicates whether voice activity detection is enabled for

voice encoding. This is a string containing a value of yes or
no. The default value is no.
Supported
Supported
packetization_interval
This parameter controls the packetization rate which each

line of the voice client (ONT or MDU) will use in the
offer/answer SDP messages for the RTP packet rate it
requests to receive. The units are milliseconds between
successive frames. The voice client can offer a subset of the
range of values of 10 to 30 (10, 20, 30 are supported). The
value actually used will be rounded to the nearest supported
value. The default value is 10 when using FTP download and
20 when using iConfig to configure SIP.
Supported
Supported
enable_info_based_dtmf
This parameter specifies whether the voice client transmits

DTMF digits in INFO method SIP messages rather than inband
or via RFC 2833 signaling. When enabled, this parameter
takes precedence over the enable_rfc2833 parameter. The
content type for the INFO messages is controlled by the
content_type_for_info parameter. The default value is no
(disabled).
Supported
Not
supported
content_type_for_info
This parameter specifies the content type to be sent in INFO

messages that carry DTMF tones and flash hook events. The
two supported values for this parameter are
audio/telephone-event and application/broadsoft. If an
unrecognized value is specified, the default value is used.
The default value is application/broadsoft.
Supported
Not
supported
default_packetization_in
terval
This parameter specifies the rate at which the ONT generates

RTP frames if the far end does not request a specific rate
during the SDP offer/answer phase of establishing a call. The
default is 10 milliseconds when using FTP download and 20
milliseconds when using iConfig to configure SIP.
Supported
Supported
(3 of 17)
19-18

19 VoIP overview
Parameter
ptime_symmetric
Description
SIP mode 1
SIP mode 2
This parameter specifies the packetization interval method.
Supported
Supported
Supported
Supported
The name (UDP, TCP, TLS) of the transport protocol and the
port number to be used for signaling. This is an optional
parameter, the default protocol value is UDP and the default
port number is 5060. UDP is the only allowed value for
transport protocol. (This parameter does not apply to iConfig
message transport.)
Supported
Supported
The uniform resource identifier (URI) is used as the request

URI for all REGISTER requests. This is a string of up to 99
characters and is a required parameter. The FTP XML name
of this parameter is shown as RegistrarURI.
Supported
Supported
The address of the server or proxy to which REGISTER

requests are sent. It is a numeric IP address or a fully
qualified domain name. This is a string of up to 99 characters
and is a required parameter. The FTP XML name of this
parameter is shown as RegistrarRoute.
Supported
Supported
Supported
Supported
When set to no_symmetry, the packetization interval is

used by the ONT in any offer or answer. When the parameter
is set to this option, the default_packetization_interval value
is used when generating packets when no ptime value is
specified in offers or answers received by the ONT.
When set to far_end_symmetry, the ONT sends or receives
packets with the same ptime interval value that appears in
offers or answers received by the ONT. When the parameter
is set to this option, the default_packetization_interval
parameter is used for both sending and receiving packets,
assuming that there was no ptime value in the initial offer. If
the SDP with the missing ptime value was an answer to an
initial offer, the ONT uses the
default_packetization_interval value for both send and
receive packets.
annexb_in_sdp
This parameter specifies whether to add an annexb

statement into the SDP offers and answers from the ONT
when G.729 is a listed codec.
The options are yes and no. When set to yes and when
the enable_vad parameter is set to yes and the G.729 codec
is listed in the SDP media line, then annexb support
information is added to the SDP.
When set to no and the enable_vad parameter is set to no,
a line indicating no annexb support information is added to
the SDP.
Annex B information is ignored in received SDP messages.
POTS line provisioning (There is a set of data for each subscriber interface.)
transport_protocol (1)
registrar_uri
(1)
registrar_route
(1)
When the string dhcp is used, this keyword substitutes the IP

address or domain name returned from DHCP option 120
instead of the registrar_route parameter value. If the DHCP
server does not provide an option 120 value, a 0.0.0.0
address is substituted and a registration failure alarm is
raised for each configured POTS line.
When the string port is used, an optional UDP port number
can be specified to use in conjunction with the DHCP
address.
register_period
(1)
The registration expiration time that the client will propose

by including it in an Expires header of a REGISTER request.
This is a non-negative integer and the value is expressed in
seconds. The default value is 3600.
(4 of 17)

19-19
19 VoIP overview
Parameter
register_head_start
(1)
register_retry_interval
outbound_proxy
(1)
(1)
Description
SIP mode 1
SIP mode 2
The number of seconds prior to expiration of a registration at

which the client sends a REGISTER request to refresh the
registration. This is a non-negative integer and the value is
expressed in seconds. The default value is 60.
Supported
Supported
The interval between successive registration retries after a

failed registration retry. The value is expressed in seconds.
The range is zero (0) to 65535 and zero (0) disables
registration. The default value is 60.
Supported
Supported
The address of a server or proxy to which all SIP requests are

to be sent, except for those for which a server of proxy is not
otherwise specified. It is either a numeric IP address or a
fully qualified domain name. This is a string of up to 99
characters and is a required parameter. The FTP XML name
of this parameter is shown as OutboundProxy.
Supported
Supported
The differentiated services code point (DSCP) value that

should populate the DS field of SIP packets sent by the user
agent. It is an integer value in the range of zero (0) to 63. The
default value is the value configured via SNMP/TL1.
Supported
Supported
The subscription expiration time that the client will propose

by including it in an Expires header of a SUBSCRIBE request.
seconds.The default value is 86400 (one day). (This
parameter does not apply to iConfig requests.)
Not supported
Supported
The number of seconds prior to expiration of a subscription

at which the client sends a SUBSCRIBE request to refresh the
subscription.This is a non-negative integer and the value is
expressed in seconds. The default value is 3600 (one hour).
Not supported
Supported
When the string dhcp is used, this keyword substitutes the IP

address or domain name returned from DHCP option 120
instead of the registrar_route parameter value. If the DHCP
server does not provide an option 120 value, a 0.0.0.0
address is substituted and invite failure and subscribe failure
alarms are raised for each configured POTS line.
address.
The outbound_proxy value is superseded for INVITE requests
if the outbound_uri_suffix value is configured.
outbound_uri_prefix + dialed number + @ +

outbound_proxy when the oubound_uri_suffix value is
not configured
outbound_uri_prefix + dialed number +
outbound_uri_suffix when the oubound_uri_suffix value
is configured
A port number will be appended to the request URI if the

outbound_proxy or outbound_uri_suffix was specified with a
port number, unless the port number equals 5060.
sip_dscp
(1)
subscribe_period
(1)
subscribe_head_start
(1)
The ONT or MDU will cancel subscriptions when registration

fails. No attempt to subscribe occurs after registration fails.
sip_timer_t1
(1)
The value of the SIP T1 timer (the round-trip time estimate).

milliseconds. The range is 1 to 65535. The default value is
500.
Supported
Supported
sip_timer_t2
(1)
The value of the SIP T2 timer (the maximum retry interval for
a non-INVITE request). This is an integer and the value is
expressed in seconds. The range is 1 to 65535. The default is
4.
Supported
Supported
(5 of 17)
19-20

19 VoIP overview
Parameter
sip_invite_timeout
(1)
sip_noninvite_timeout
address_of_record
(1)
Description
SIP mode 1
SIP mode 2
The INVITE transaction timeout, designated as Timer B in RFC

3261. This is an integer. The value is expressed in seconds.
The range is 1 to 65535. The default value is 32 (64*T1).
Supported
Supported
The non-INVITE transaction timeout, designated as Timer F in

RFC 3261. This is an integer and the value is expressed in
seconds. The range is 1 to 65535. The default value is 32
(64*T1).
Supported
Supported
The SIP address of record (AOR) for the POTS line. This is a
string of up to 99 characters and is a required parameter. The
FTP XML name of this parameter is shown as
AddressOfRecord.
Supported
Supported
When the string autofill is used, this keyword substitutes a

new address of record, taking the form:
sip:CLIENTID + PORT#@registrar_host,
where
CLIENTID is the TL1 and OMCI configured value for CLIENTID
PORT# is the numeric port value, from 1 to n, where n is the
numeric port number for the POTS line
registrar_host is the filled value of the registrar_uri
parameter.
The CLIENTID and PORT# values are concatenated, with no
white space or other delimiters between them.
realm
A realm identifier that corresponds to the service provider

domain in which the POTS line is registered. The realm
identifier is used in the authentication of the user agent. This
is a string of up to 99 characters and is an optional
parameter. The default is to use the realm parameter from
the 401/407 authentication challenge.
Supported
Supported
username
The user name to be used for authentication for all SIP

requests made on behalf of the SIP AOR. This data element
affects the behavior of both the voice software and the
iConfig client. This is a string of up to 99 characters. The
default value is the user portion of the AOR.
Supported
Supported
password
A password that is associated with the AOR in the service

provider domain that is identified by the realm identifier and
is used in the authentication of the user agent. This is a string
of up to 99 characters and is an optional parameter.
Supported
Supported
contact_uri_user
The user name portion of the contact URI that represents the
port on behalf of which the user agent acts. The user name
of the contact URI is the value of the contact_uri_user
property. The host value portion of the contact URI is the
numeric IP address of the user agent. The contact URI is
registered against the AOR. This is a string of up to 99
characters and a required parameter. The FTP XML name of
this parameter is shown as ContactURIUser.
Supported
Supported

new contact_uri_user value, taking the form:
CLIENTID + PORT#
where
CLIENTID is the TL1 and OMCI configured value for CLIENTID
PORT# is the numeric port value, from 1 to n, where n is the
numeric port number for the POTS line
The CLIENTID and PORT# values are concatenated, with no
white space or other delimiters between them.
(6 of 17)

19-21
19 VoIP overview
Parameter
Description
SIP mode 1
SIP mode 2
primary_identify
Up to ten identity data sets may be associated with a single

POTS line. If more than one is specified then one and only
one should be specified as the primary identity. The primary
identity parameter, if set to yes, indicates which identity
data set is the one to be used in outgoing calls and
subscriptions from the line with which it is associated. If
more than one identity data set has this property set to yes
for a POTS line or if none does, the Voice Client may use any
of the configured identities. The default is no.
Not supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
An identity data set is comprised of these parameters:

address_of_record, realm, username, password,
contact_uri_user, and primary_identity. Note: The
address_of_record parameter in each identity data set
should be unique.
digit_map
A pattern that guides digit collection and allows the user

agent to determine when dialing is complete. One digit_map
setting is supported for each POTS port. See Table 19-8 for a
description of the digit map contents. This is a string of up to
1093 characters and is a required parameter with no default
value. A digit map must be customized for each SIP
implementation based on the features of the SIP server in the
network.
White space in the digit map string is not significant.
Characters are case insensitive.
outbound_uri_prefix
A string added as a prefix to the dialed digits to form the

Request URI and the To URI when sending an INVITE request
to the softswitch. This is a sting of up to 99 characters and is
an optional parameter. The default value is sip. The FTP
XML name of this parameter is shown as OutboundURIPrefix
outbound_uri_suffix

not configured
is configured
A string that is added as a suffix to the dialed digits to form

the Request URI and the To URI when sending an INVITE
request to the softswitch. The specified string is added as is
if the string contains an @ character. If an @ character is not
present, then @ is prefixed to the specified value. This string
of up to 99 characters is an optional parameter. The default
value is @ + outbound_proxy. The FTP XML name of this
parameter is shown as OutboundURISuffix.

not configured
is configured
(7 of 17)
19-22

19 VoIP overview
Parameter
Description
SIP mode 1
SIP mode 2
service_code_ccw
A set of one or more service codes, such as *70, that the user
agent recognizes as the Cancel Call Waiting service code.
This reflects that fact that in typical dial plans there are two
equivalent ways to dial a given service code. This is a string.
The value of this property may include up to two service
codes, each up to 6 characters long, separated by white
space. The default is *70 1170. The same service code
values must be present in the digit map with an S modifier
and no R modifier.
Not supported
Supported
Not supported
Supported
Not supported
Supported
Not supported
Supported
If a configured value also appears in the digit map with an S

modifier then they will be processed during dialing for the
associated feature. If the value is not in the digit map with
an S modifier, then the digits will be treated as normally
dialed digits and not be specially processed.
Use the appropriate enable_XXX parameter to enable the
service code.
service_code_6wc
A set of one or more service codes that the user agent

recognizes as a request to initiate a six-way conference. This
reflects that fact that in typical dial plans there are two
The value of this property may include two service codes,
each up to 6 characters long, separated by white space. The
default is *41 1141.
service code.
service_code_rls

recognizes as a request to release a consultation call that
was initiated as part of six-way conference procedures. This
reflects the fact that in typical dial plans there are two
The value of this property may include two service codes,
each up to 6 characters long, separated by white space. The
default is *43 1143.
service code.
service_code_hold

recognizes as a request to place the active call on hold. This
codes, each up to 6 character long, separated by white
space. The default is *52 1152.
service code.
(8 of 17)

19-23
19 VoIP overview
Parameter
Description
SIP mode 1
SIP mode 2
intercom_code_1
A set of one or more home intercom service codes for

alerting pattern 1. This reflects that fact that in typical dial
plans there are two equivalent ways to dial a given service
code. This is a string. The value of this property may include
up to two service codes, each up to 6 characters long,
separated by white space. The default is *53 1153.
Not supported
Supported
intercom _code_2
A set of one or more home intercom service codes for

alerting pattern 2. This reflects that fact that in typical dial
plans there are two equivalent ways to dial a given service
code. This is a string. The value of this property may include
up to two service codes, each up to 6 characters long,
separated by white space. The default is *54 1154.
Not supported
Supported
enable_cw
Indicates whether the call waiting service is enabled. This is

a string containing a value of yes or no. The default
value is yes.
Supported
Supported
etsi_activate_call_waitin
g
A set of one or more service codes that the user agent will
recognize as a request to activate call waiting in ETSI mode.
codes of six characters each, separated by white space. This
equivalent ways to dial a given service code. The default is
*43#.
Not supported
Supported
etsi_deactivate_call_wai
ting
recognize as a request to de-activate call waiting in ETSI
mode. The value of this property may include up to two
service codes of six characters each, separated by white
space. This reflects that fact that in typical dial plans there
are two equivalent ways to dial a given service code. The
default is #43#.
Not supported
Supported
etsi_interrogate_call_wa
iting
recognize as a request to interrogate call waiting active
status in ETSI mode. The value of this property may include
up to two service codes of six characters each, separated by
white space. This reflects that fact that in typical dial plans
there are two equivalent ways to dial a given service code.
The default is *#43#.
Not supported
Supported
enable_3wc
Indicates whether 3-way conference service is enabled. This

is a string containing a value of yes or no. The default
value is no.
Not supported
Supported
enable_6wc
Indicates whether 6-way conference service is enabled. This

is a string containing a value of yes or no. The default
value is no.
Not supported
Supported
enable_transfer
Indicates whether the call transfer service is enabled. This is

a string containing a value of yes or no. The default
value is no.
Not supported
Supported
enable_hold
Indicates whether the call hold service is enabled. This is a

string containing a value of yes or no. The default value
is no.
Not supported
Supported
enable_supp_ring
Indicates whether the suppressed ringing service is enabled.

This is a string containing a value of yes or no. The
default value is no.
Not supported
Supported
enable_forced_hold
Indicates whether the forced hold behavior is enabled for an

emergency call. This is a string containing a value of yes or
no. This is an optional parameter. The default value is
no.
Not supported
Supported
(9 of 17)
19-24

19 VoIP overview
Parameter
Description
SIP mode 1
SIP mode 2
supp_ring_offhook_timer
The time interval within which the device must go offhook

for a suppressed ringing call. This is a non-negative integer.
The value is expressed in seconds. The default value is 5.
Not supported
Supported
supp_ring_interrupt_tim
er
The time interval within which the device must go onhook if

a suppressed ringing call is interrupted. This is a
non-negative integer. The value is expressed in seconds. The
default value is 2.
Not supported
Supported
conference_uri
The URI of the conference server to be used for the 6-way

conference service.
Not supported
Supported
direct_connect_uri
The URI to be inserted as the To address of an INVITE sent in

response to the device going off-hook. If this property is set,
an off-hook event triggers an immediate INVITE with the
value of this property as the To address. If this property is not
set, an off-hook event provides the dial tone to the port,
allowing the user to dial a call in the usual manner. This is a
string of up to 99 characters and is an optional parameter.
The default value is a null string, which indicates no direct
connect. Set the enable_warmline parameter to yes to use
the direct_connect_uri parameter.
Supported
Supported
message_event_uri
The URI to which a subscription for message-waiting events

is sent. If this property is not set, the user agent shall not
subscribe for message waiting events. This value is a URI The
default is no URI, which disables subscribe. When the
parameter is set to URI, you can configure the
allow_unmatched_notify parameter.
Not supported
Supported
Supported
Supported
Supported
Supported

new message_event_uri value based on the filled value, after
any derived value, of the address_of_record parameter.
A port number will be appended to the request URI if the
message_event_uri, cfwd_event_uri, or registrar_uri was
specified with a port number, unless the port number equals
5060.
address.
allow_unmatched_notify
This parameter governs behavior to allow a NOTIFY with full

dialog headers (indicating that they are part of a dialog) to
be accepted by the ONT that does not match a known
SUBSCRIBE dialog. The contents of such an unmatched
NOTIFY will be ignored. The default is no, meaning that a
NOTIFY with full dialog headers must match a known
SUBSCRIBE dialog or a 481 error will result. If the parameter
is set to yes, the contents of such an unmatched NOTIFY will
be ignored.
This parameter should not be set to yes if implicit NOTIFY
messages are expected from the softswitch (for example, no
SUBSCRIBE is performed).
message_waiting_mode
The mode for presenting a message-waiting indication to the

user. This is a sequence of up to three values: dial-tone to
enable stutter dial tone, visual to enable visual MWI, and
reminder-ring to enable a reminder ring. Any combination
of the three may be specified. This is an optional parameter.
The default value is dial-tone.
You can specify more than one value at a time in the XML file.
Separate the values using spaces.
(10 of 17)

19-25
19 VoIP overview
Parameter
Description
SIP mode 1
SIP mode 2
vmwi_refresh_interval
The duration, in minutes, of the interval between successive

refresh transmissions of the message-waiting status to the
analog line, if visual is specified in
message_waiting_mode. If the value of this property is zero,
refresh transmissions will not be performed. This is an
optional parameter. This is a non-negative integer expressed
in minutes. The default value is 30.
Supported
Supported
vmwi_abbreviated_ring
Indicates whether the abbreviated ring option is enabled.

This is a string containing a value of yes or no. This is an
optional parameter. The default value is no.
Supported
Supported
mwi_reminder_burst
The duration of the message-waiting reminder ring burst.

This is an optional parameter. This is an integer expressed in
milliseconds. The default value is 500.
Supported
Supported
mwi_reminder_interval
The duration of the interval between message-waiting

reminder ring bursts. This is an optional parameter. This is a
non-negative integer expressed in minutes. The default value
is 15.
Supported
Supported
bridged_line_uri
The bridged line agent URI if the bridged line service is

enabled. If this property is not set, the user agent does not
enable the POTS line to act as one of a set of bridged lines.
Not supported
Supported
bridged_line_dialog_uri
The bridged line dialog URI used by the bridged line service.
If this property is not set, the user agent uses the
bridged_line_uri setting as the bridged line dialog URI.
Not supported
Supported
cfwd_state
Indicates whether the state of the network-based call

forwarding service is to be rendered to the user.This is a
string containing a value of yes or no. The default value
is no.
Supported
Supported
cfwd_reminder
Indicates whether a reminder alert is to be provided to the

user when the network-based call forwarding service
redirects a call. This is a string containing a value of yes or
no. The default value is no.
Supported
Supported
cfwd_event_uri
The URI to which a call forwarding event subscription is sent.

If this property is not set, but either cfwd_state or
cfwd_reminder is set to yes, the call forwarding event
subscription is sent to the URI specified in the
address_of_record property. This value is a URI.
Supported
Supported
obsolete_hold
Indicates whether the user agent must use the obsolete hold
convention (a connection address of 0.0.0.0) when placing a
media stream on hold. This is a string containing a value of
yes or no. The default value is yes.
Not supported
Supported
session_timer_min
The minimum acceptable value for the RFC 4028 session

timer interval. This is a non-negative integer. The value is
expressed in seconds. The default value is 90, which is the
RFC 4028 absolute minimum.
Supported
Supported
session_timer_max
The RFC 4028 session timer interval to be proposed by the

user agent. This is a non-negative integer. The value is
expressed in seconds. The default value is 1800, which is the
RFC 4028 recommended value.
Supported
Supported
session_timer_refresher
Specifies the refresher to be specified by the user agent

when it has a choice. A value of none specifies that the
user agent will not request session expiration. Any other
value specifies that the user agent will request session
expiration. This is a string containing either none, uas,
or uac. The default value is uas.
Supported
Supported
(11 of 17)
19-26

19 VoIP overview
Parameter
Description
SIP mode 1
SIP mode 2
cid_allows_fromhdr
A value specifying whether information from the FROM

header may be used in providing caller ID to the phone set.
Information from P-Asserted-Identity header is always used
in preference to the FROM header. This value only has effect
when no P-Asserted-Identity information is available. A yes
means that the FROM header will be used for the caller ID if
the P-Asserted-Identity header is not present in the INVITE
message. A no means that, if the P-Asserted-Identity
header is not present, then no caller ID is provided to the
phone set. The default value is no.
Supported
Supported
rfc2833_symmetric
This parameter governs the SDP offer/answer processing

related to the payload type to use with RFC2833. If this
parameter is set to yes, then it means that the same
payload types will be used for both send and receive RFC2833
packets. The payload type to be used will be based on the
SDP offer or answer from the ONT. If this parameter is set to
no then the payload types to be used for send and receive
RFC2833 packets are set according to the rules in RFC3264
section 5.
Supported
Supported
Supported
Supported
Supported
Supported
If this parameter is set to far_end_symmetry, the same

payload type will be sent for both send and receive RFC2833
packets. The payload type to be used will be based on the
SDP offer or answer received from the far end of the call. The
default is no
dynamic_codec_payload
_map_entry
This is a list of ordered pairs that specify the dynamic

payload numbers to be used by the ONT for specific payload
types, identified by IANA MIME type. The values specified will
be used by the voice client as part of its offer-answer SDP
negotiation. Each ordered pair consists of a mimetype entry
and a payload_number entry. More than one such ordered
pair may be present. Two mimetype values are supported
(not case-sensitive): audio/G726-32 and
audio/telephone-event.
Any other mimetype value along with its associated
payload_number will be ignored. The payload_number entry
is an integer in the range of 96 to 127 inclusive. It is an error
to specify two mimetypes that map to the same payload
number. Such errors will cause the profile not to be used.
The default for audio/G726-32 is 98. The default for
audio/telephone-event is 97.
obsolete_stale
This value controls the behavior of the ONT with respect to

nonce expiration and re-registration or dialog refreshes.
If this value is set to true then if the ONT receives an
authentication reject (401 or 407 error) that contains a new
nonce value, but no stale-flag, the ONT should behave as if a
stale=true was present and send the refresh with the new
nonce value
Note that the ONT will still properly handle the stale-flag, if
present. If the obsolete_stale value is set to false, then if
the stale-flag is not present in the 401/407 message,
RFC2716 compliant behavior will be followed, and the
registration or dialog that was being refreshed will be
terminated. The default value is false when using FTP
download and true when using iConfig to configure SIP.
(12 of 17)

19-27
19 VoIP overview
Parameter
Description
SIP mode 1
SIP mode 2
thin_client_HF_method
If the voice client is in thin mode (SIP mode 1), the hook flash
processing behavior is controlled by this value.
Supported
Not
supported
If the value is set to info, the hook flash indication is sent

using an INFO message to the softswitch. If the value is set to
invite, the ONT passes the HF event to the softswitch using
an INVITE message with the request-URI set to the value of
the thin_client_HF_request_URI value.
thin_client_HF_request_
URI
This value contains the string value to be used as the user

portion of the INVITE request when the ONT is in thin client
(SIP mode 1) and the thin_client_HF_method is set to
invite. The default is LucentTISPAN-FlashRequest.
Supported
Not
supported
cfwd_implicit
This value controls whether the voice client will SUBSCRIBE

to call forwarding status NOTIFY messages or whether the
voice client will expect to receive NOTIFY messages without
a subscription.
Supported
Supported
If the value is set to no, the voice client subscribes if either

of the cfwd_state or cfwd_reminder values are set to yes.
If the value is set to yes, the voice client will process
NOTIFY messages without having performed a SUBSCRIBE.
The default value is no.
session_timer_method
This value controls which SIP method is used for session timer
functionality. The options are update, invite, or
explicit_invite. The default is invite.
Supported
Supported
add_route_header
This value enables or disables the route header in new SIP

requests generated at the ONT or MDU. This does not apply
to responses or requests within an established dialog.
Supported
Supported
enable_warmline
This value controls whether the warm line feature is

enabled.
Supported
Supported
If the value is set to yes, warm line is enabled. When warm

line is enabled, if the permanent_timer expires before a
caller who has picked up the phone (gone off hook) dials any
digit, the CPE device sends an INVITE request using the value
specified in the direct_connect_uri property as the
requested URI.
The default is no, warm line is disabled.
enable_etsi
This parameter controls whether the ONT acts in accordance

with ETSI or GR requirements for offering services. A value of
yes enables ETSI behavior. The default is no.
Not supported
Supported
etsi_ch_release
This parameter contains the value of the consult call service

option code which is used to drop the active session and
resume held session as a two-way call ending the consult
state. If this parameter is not configured or is configured to
contain the empty string, the ONT disables the functionality.
Not supported
Supported
Valid values are in the form Rd, where d represents '0'-'9' or

'*' or '#'. An invalid value causes the ONT to act as if this
parameter was not configured. This parameter only has
meaning if the enable_esti parameter is set to yes. The
default is an empty string.
(13 of 17)
19-28

19 VoIP overview
Parameter
Description
SIP mode 1
SIP mode 2
ets_ch_release_held_call
This parameter contains the service code to be used to

release the held session during a consultation call. If this
parameter is not configured or is configured to contain the
empty string, the ONT disables the functionality. Valid values
shall be of the form Rd, where d represents '0'-'9' or '*' or
'#'. An invalid value will cause the ONT to act as if this
Not supported
Supported
etsi_ch_toggle

option code used to toggle between two sessions. If this
property is not configured or is configured to contain the
empty string, the ONT disables this functionality.
Not supported
Supported
Not supported
Supported

etsi_ch_merge

option code which is used to merge two sessions to a 3-way
call with mixing in the ONT. If this property is not configured
or is configured to contain the empty string, the ONT disables
this functionality.
etsi_ch_release_earliest
This parameter contains the value used t orelease a call and

return to a 2-way call state by releasing the call leg added
first. The other dialog continues as active, and the call is
reduced to a 2-way call. Valid values are in the form Rd,
where d is 0-9 or * or #. An invalid value does not result in
any ONT behavior. You cannot configure this parameter
unless the enable_etsi pararmeter is set to true. The
default value is an empty string.
Not supported
Supported
etsi_ch_release_latest
This parameter contains the value used t orelease a call and

return to a 2-way call state by releasing the call leg added
most recently. The other dialog continues as active, and the
call is reduced to a 2-way call. Valid values are in the form
Rd, where d is 0-9 or * or #. An invalid value does not result
in any ONT behavior. You cannot configure this parameter
Not supported
Supported
etsi_3wc_split
This parameter contains the service code that takes a 3wc to

a consult call state in the ETSI mode. If this parameter is not
configured or is configured to contain the empty string, the
ONT disables the split call operation for the line in question.
Not supported
Supported

(14 of 17)

19-29
19 VoIP overview
Parameter
Description
SIP mode 1
SIP mode 2
etsi_3wc_split_preconf
This parameter contains the service code to be used to split

a 3-way call and return to the pre-conference state. If this
empty string, the ONT shall disable this functionality. Valid
values shall be of the form Rd, where d represents '0'-'9' or
'*' or '#'. An invalid value will cause the ONT to act as if this
Not supported
Supported
etsi_3wc_release_earlies
t
This parameter contains the value used to release a 3-way

call to a 2-way call state by releasing the call leg added first.
The other dialog continues as active, and the call is reduced
to a 2-way call. Valid values are in the form Rd, where d is
0-9 or * or #. An invalid value does not result in any ONT
behavior. You cannot configure this parameter unless the
enable_etsi pararmeter is set to true. The default value is
an empty string.
Not supported
Supported
etsi_3wc_release_latest
This parameter contains the value used to release a 3-way

call to a 2-way call state by releasing the call leg added most
recently. The other dialog continues as active, and the call is
reduced to a 2-way call. Valid values are in the form Rd,
where d is 0-9 or * or #. An invalid value does not result in
any ONT behavior. You cannot configure this parameter
Not supported
Supported
enable_3wc_focus
This parameter controls whether the ONT or MDU will append

3WC to the contact name and add the isfocus header to the
INVITE message when establishing a second dialog for the
consultation call feature.
Not supported
Supported
etsi_cw_release
This parameter contains the service code used to release the

active session and resume the held call as a two way call
ending the call waiting state. If this parameter is not
ONT disables the release active session operation for the line
in question.
Not supported
Supported

etsi_ch_release_held_cal
l
This parameter contains the service code to be used to

release the held session during a consultation call. If this
empty string, the ONT shall disable this functionality. Valid
values shall be of the form Rd, where d represents '0'-'9' or
'*' or '#'. An invalid value will cause the ONT to act as if this
Not supported
Supported
etsi_cw_toggle
This parameter contains the service code to be used to toggle

between sessions during call waiting. If this parameter is not
ONT disables the toggle session operation for the line in
question.
Not supported
Supported

(15 of 17)
19-30

19 VoIP overview
Parameter
Description
SIP mode 1
SIP mode 2
etsi_cw_release_held_ca
ll
This parameter specifies the service code to use to release

the new call waiting call (prior to toggling) or the held
session during toggling. If this parameter is not configured,
or is configured to contain an empty string, the ONT disables
this functionality.
Not supported
Supported
Not supported
Supported
Valid values shall be of the form Rd, where d represents

'0'-'9' or '*' or '#'. An invalid value will cause the ONT to act as
if this parameter was not configured. This parameter only
applies when the enable_esti parameter is set to yes. The
etsi_cw_merge
This parameter contains the service code to be used to merge

the 2-call waiting sessions and transition into a 3-way call
with mixing in the ONT. If this property is not configured or
is configured to contain the empty string, the ONT disables
the merge sessions operation for the line in question.
cw_alert_timer
This parameter specifies the value, in seconds, of the

duration for which the user is allowed to answer a call
waiting call. The default is 120 seconds.
Not supported
Supported
enable_dead_line_tone
This parameter controls ONT behavior with respect to

playing a dead line tone when the user goes off-hook and
either:
Supported
Supported
Not supported
Supported
Supported
Supported
the line is unregistered

the PON is unavailable
The default is no, indicating that no tone is output in

either case.
enable_reverse_polarity
This parameter controls whether reverse polarity is used.

This parameter can be configured only when the enable_etsi
parameter is set to yes. It must be configured for each line.
When enabled:
For the originator of a call, polarity is reversed when the call
is answered (200 OK received). For the terminator of a call,
polarity is reversed prior to the start of ringing.
For either the originator or terminator, when the call ends
because BYE received, normal polarity is resumed. For the
originator, if the user goes on-hook, normal polarity is
resumed. For the terminator, if the user goes on-hook,
reverse polarity continues until the re-answer timer expires,
then normal polarity is resumed.
The default is no. Set to yes to enable reverse polarity.
enable_calling_name_id
This parameter determines whether a display name is output

to the phone set.
When the parameter is set to yes (default), the display name
is included as part of the caller ID output data. When the
parameter is set to no, the display name is not included as
part of the caller ID output data.
(16 of 17)

19-31
19 VoIP overview
Parameter
Description
SIP mode 1
SIP mode 2
callerid_uri_preference
This parameter specifies whether to set tel-uri as a higher

priority than sip-uri, when there is more than one p-assert
header present.
Supported
Supported
Supported parameters are sip, tel, or first. Unsupported

values are mapped to first. If an incoming call contains
more than one p-assert header, this parameter controls
which header is used to populate the caller ID data output on
the phone set.
When the parameter is set to sip, the p-assert header that
is formed with a sip-uri will be used. When the parameter is
set to tel, the p-assert header that is formed with a tel-uri
will be used. When the parameter is set to first (default),
it indicates the p-assert header that occurs earlier in the
incoming INVITE will be used for the caller ID data. The
default is first
enable_call_hold_tone
This parameter controls whether or not the ONT will play the
call hold tone to the user when the associated RTP session is
inactive or sendonly. This parameter only applies when the
enable_esti parameter is set to yes. The default is no
Not supported
Supported
etsi_recall_dial_tone_na
me
This parameter contains the name of the tone to be played

to indicate to the user that mid-call dialing is allowed.
Possible values are DialTone or RecallDialTone. This
parameter only applies when the enable_esti parameter is
set to true. The default is RecallDialTone.
Not supported
Supported
etsi_held_party_ringback
This parameter shall control whether or not ringing shall be

applied when a user goes on hook with an RTP session on
hold. This parameter only applies when the enable_esti
parameter is set to true. The default is no.
Not supported
Supported
add_media_level_cline
This parameter controls the presence of the second c-line,

or contact address, in the SDP for obsolete hold. This
parameter is ignored when the obsolete_hold parameter is
not enabled. The options are yes (default) meaning the
second c-line will be added as part of the media description,
and no, meaning only a single session-level c=line is
present in the SDP, and it is set to 0.0.0.0.
Not supported
Supported
direction_in_hold_req
This parameter controls the value of direction attribute

inserted into the hold SDP when standard hold behavior is
enabled. This parameter is ignored when the obsolete_hold
parameter is enabled. The options are sendonly (default)
and inactive, which correspond to the direction attribute
that is used in SDP for the hold request.
Not supported
Supported
dtmf_volume_level
This parameter specifies a numeric value used to overwrite

the volume field with a fixed value in the RFC 2833 packet
that the ONT generates for each DTMF digit detected at the
POTS line.
Not supported
Supported
(17 of 17)
Note
(1)
This parameter can only be set on an ONT-wide basis when the parameter is configured as part of the configuration profile
(FTP download).
Digit map digit collection
A digit map is used to control how the ONT or MDU processes dialed digits for a
voice service.
19-32

19 VoIP overview
Besides simple collection of the digits of a phone number, it allows for ONT or MDU
internal handling of special dialed sequences like 911 and service codes. The ONT
utilizes the configured digit map at call origination, or in some cases after flash-hook.
In SIP mode 1, there is no digit collection by the ONT after flash-hook. In SIP mode
2, digit collection is usually started after a mid-call flash-hook. In all other cases
digits are simply passed in-band in the voice path, either as tones or as RFC 2833
packets. The digit map also allows for these subscriber interaction functions:
timeout of digit collection

termination of digit collection
output of recall dial tone or normal dial tone
When digit collection is started the ONT digit map library (DML) software is
initialized with timers and the configured digit map string. The DML builds a tree
with branches for each possible matching path possible in the digit map string from
left to right. As each digit is input:
1
The tree is traversed using the digits entered so far until a matching pattern is
found.
If the matching point also satisfies all conditions of the pattern (such as the
number of repetitions allowed), then digit collection is ended.
If no matching pattern is found, then digit collection is ended.
Digit collection begins when the device goes off-hook. Digit map processing occurs
until one of the following events occurs:
The permanent timer expires when no digit has been received.

The interdigit timer expires after at least one digit has been received.
no more patterns are matched, and the base of the digit map tree is reached
a digit is entered for which there is no matching pattern
the enter key is used, but it is processed as an enter key only if there is not a
pattern match for the defined enter key at that point in the tree
The call attempt is made (INVITE sent) with digits collected at the point the digit
collection ends.
Digit collection is influenced by the following SIP configuration parameters (see
Table 19-7 for details on these parameters):
permanent timer
interdigit timer
critical timer
use of the Enter key

19-33
19 VoIP overview
There are three types of service codes (also called feature codes) to consider in a digit
map:
The service code is handled locally at the ONT or MDU, for example *70 in SIP
mode 2. Such service codes are not supported in SIP mode 1. These service codes
are not included in INVITE messages.
The service code triggers a service at the softswitch, but does not have a set of
digits which must then be collected by the ONT or MDU. In this case, the
INVITE contains just the feature code, and is dependent on the softswitch.
The service code triggers a service at the softswitch, and does have a set of digits
which must then be collected by the ONT or MDU. In this case, both the service
code and the phone number are included in the INVITE message. For example,
*67 followed by 1234567 would invoke called ID blocking on a call to phone
number 123-4567. In most cases, the digit map would include the I (insertion
character) modifier and #, so the INVITE would contain *67#1234567.
Digit map syntax, collection elements, and samples
The ONT digit map is a pattern that guides digit collection and allows the user agent
to determine when dialing is complete. The digit_map SIP parameter is used to set
this pattern. One digit map is supported for each POTS port.
White space in the digit map string is not significant. Characters are not case
sensitive. Parenthesis can be used to create patterns with following operators and
modifiers and to group sets of patterns together. An enter key on the phone is used
during digit collection to end the collection and cause the call attempt to be made
(INVITE sent). The enter key detected by the ONT is configurable with the SIP
provisioning enter_key parameter. The default is #.
Vertical bar characters are used to create alternate patterns in the digit map. For
example 1 | 2| 3 means 1 or 2 or 3. Care must be taken to make alternative patterns
unambiguous when constructing a digit map.
Table 19-8 lists and describes the elements, symbols, and modifiers used in the ONT
digit map.
19-34

19 VoIP overview
Table 19-8 ONT digit map elements, symbols, and modifiers
Pattern elements, symbol, or
modifier
Representation
0-9, A-D, *, and #
Dialed digits
A digit in the range 0-9
[]
A set of digits enclosed in brackets [ ] represents the occurrence of any of the

enclosed digits. If a ^ appears immediately after the opening bracket, it represents
the occurrence of any digit other than the enclosed digits.
A pattern element followed by a dot signifies zero of more occurrences of the

element.
A pattern element followed by a question mark signifies zero or one occurrence of the
element.
In the sequence (( * | 11 ) ( 88| 90 )) R I# ? means the user can enter:
nothing
*88
*90
However, the user cannot enter:
*88 and *90
A pattern element followed by a plus sign signifies one or more occurrences of the
element.
{m}
A pattern element followed by { m } signifies exactly m occurrences of the element.
{m,}
A pattern element followed by { m, n } signifies at least m occurrences.
{m,n}
A pattern element followed by { m, n } signifies at least m occurrences, but not more

than n occurrences of the element.
For example, {0,2} means that the pattern proceeding it can be used 0, 1, or 2 times.
In the sequence (( * | 11 ) ( 67 | 82 )) SRI# {0,2} means the user can enter:
nothing
*67 and *82
*82 and *67
*82
*67
However, the user cannot enter:
*67, *82, and *67
()
A sequence of pattern elements enclosed in parenthesis matches the concatenation

of the elements.
A sequence of pattern elements separated by | matches the any one of the elements
in the sequence.
The T modifier represents the application of the critical timer (4 s). A pattern element
followed by the T modifier matches if an only if the critical timer expires at that
point.
The P modifier represents the application of dial tone when a partial match reaches
that point.
The I modifier represents the insertion of a special digit character (such as #) into the
collected digit string immediately following the substring that matches the pattern
element that is followed by the I modifier. The inserted character is specified
immediately following the I in the pattern.
(1 of 2)

19-35
19 VoIP overview
Pattern elements, symbol, or

modifier
Representation
The E modifier specifies the substring that matches the pattern element before it as
an emergency call. The pattern element generally is a sequence of pattern elements
enclosed in parentheses. This use of this symbol is not supported in SIP mode 1.
The R modifier specifies that a recall dial tone should be output after a particular
pattern is performed.
The S modifier specifies the substring that matches the pattern element before it as
service code that may be of interest to the user agent. The pattern element generally
is a sequence of pattern elements enclosed in parentheses. This use of this symbol is
not supported in SIP mode 1.
(2 of 2)
Note 1 Alphabetic symbols in the ONT digit map are not case
sensitive.
Note 2 The digit_map SIP parameter is a required parameter; it has
no default value. A digit map must be customized for each SIP

implementation based on the features of the SIP server in the network.
The following is an example of a digit map used with SIP mode 1:
*x{20} | #x{20} | 411 | 911 | [01235678]x{20} | [49] ( [^1]x{19} |
1[^1]x{19} )
This example:
Allows for up to 20 digits to be entered following * or # for service codes

411 or 911 can be entered and digit map collection will stop immediately.
Allows a dialed number (without a service code) of up to 20 digits, with
exclusions to make sure the different patterns are unique for 411 and 911.
This example forces the subscriber to use the enter key or wait for timeout to dial
a simple service code or phone number (except for 411 or 911).
The interdigit timeout with this Digit Map should be configured to 4 seconds
(normally it is 16 seconds).
The following is an example of a digit map used with SIP mode 2:
( ( * | 11 ) ( 67 | 82 ) ) SRI# {0,2} ( ( * | 11 ) ( 70 ) ) S I# ? (
101xxxx ) ? ( ( * | 11 ) 52 ) S I# ? ( ( * | 11 ) ( 88 | 90 ) ) R I#
? ( ( ( * | 11 ) ( [23]xx | [014]x | 5[^2] | 6[^7] | 7[^0] | 8[01345679]
| 9[^0] ) ) S I# | ( 0T | 00 | 011?[2-9]x{0,14}T | [01] ( [2-8] 11 |
(911)E | [2-9] ( [^1]x{8} | 1[^1] x{7}) ) | [2-8] 11 | (911)E | [2-9]
( [^1]x{5} | 1[^1] x{4}) | [2-9] [^1]?T ) )
This example:
The example allows these type 1 service codes: *70/1170 and *52/1152. The
cancel call waiting and call hold service code parameters in the XML download
data must also be configured with these features codes for the features to work
properly.
Allows these type 3 service codes: *67/1167, *82/1182, *88/1188, and *90/1190.
*67/1167 and *82/1182 can be entered together in any order and can be followed
by *88/1188 or *90/1190. This ordering may be important in some cases.
19-36

19 VoIP overview
All other service codes are type 2.

S and R modifiers are used with most codes; however, the S modifier is not
required except for the type 1 codes.
R modifiers are not necessary on the *70/1170 and *52/1152 codes, the ONT will
output correct tones as part of Type 1 processing.
The E modifier in the example will cause special emergency call behavior in the
ONT if 911, 0911 or 1911 is dialed.
RFC2833 DTMF digit transmission
Inband transmission of DTMF tones only occurs when digit collection is not being
performed. This inband transmission provides a way for a server to independently
collect dialed digits, allowing the ONT to pass them transparently. By comparison,
RFC2833 transmission of DTMF is an alternative method of transmitting DTMF
digits.
In VoIP processing, the use of RFC2833 is a negotiated item in the Session
Description Protocol (SDP). The SDP Offer/Answer negotiation is used to determine
if the two endpoints should actually use RFC2833 transmission or not.
When using the RFC2833 transmission method, digits are encoded in
RFC2833-defined packets so the server does not have to decode RTP packets in
order to process DTMF tones. When RFC2833 packets are used for DTMF
transmission, the DTMF tones are not sent in the encoded RTP data.
The 7342 ISAM FTTU provides a provisioning option to enable or disable this
feature so the ONT knows whether or not to initiate offers with RFC2833 or not. See
the SIP provisioning parameter enable_rfc2833 in Table 19-7.
Note This feature does not change how pulse dialing is handled,
and applies to DTMF only.
INFO-based DTMF digit transmission
As an alternative to RFC2833 DTMF transmission, the ONT supports sending and

receiving DTMF digits in SIP INFO messages. The digit is represented in the body
of the INFO messages following a content type header of
application/telephone-event as follows:
Content-Type: audio/telephone-event
Content Length: 4
xxyyyyyy
Where xxyyyyyy is a 32-bit value. xx is the top-most 8 bits, and yyyyyy is the next 24
bits. xx represents one of the 16 possible DTMF event values specified in RFC2833
(0 through 15). yyyyyy is not used, it will be ignored in INFO messages received, and
set to 0 for INFO messages generated by the ONT.

19-37
19 VoIP overview
As with RFC2833 DTMF transmission, a digit sent with this method will not be sent
in the encoded RTP voice data. INFO based DTMF transmission is enabled with the
enable_info_based_dtmf parameter from Table 19-7.
Note This feature does not change how pulse dialing is handled,
and applies to DTMF only.
19.6
Security
For network and ONT security, the ONT supports the following mechanisms:
DHCP option 90: supported in any VoIP mode of operation that uses DHCP
HTTP Digest/MD5 authentication: supported in SIP modes in response to an
authorization challenge from the softswitch, or iConfig server
configuration of an FTP server username and password, when downloading XML
configuration profile files
DHCP Option 90
DHCP Option 90 provides a signature in a DHCP message for the authentication and
integrity of the message. DHCP Option 90 does not provide privacy. The signature
allows a DHCP client or server to know a responding client or server is valid or a
spoof. It also prevents replay and eavesdropping attacks that can cause a denial of
service.
VoIP clients are programmed with a username secret ID and a shared secret K (Key).
To sign a DHCP message, the invariant parts of the message are used to compute a
hash value with the secret K based on RFC 2104. If the receiver of the message has
the same secret K, the receiver can re-calculate the hash value and determine whether
the sender knows the shared secret K. If the hash value calculated by receiver does
not match the hash value in the Option 90 HMAC-MD5 field, the sender does not
know the correct secret K value or the message was altered during the transmission.
Using the RDM, a receiver can determine whether this message has already been
received and is a replay attack.
HTTP digest
HTTP digest provides a method for client authentication and message integrity to the
server, and optional authentication of server and server messages. HTTP digest does
not provide privacy. HTTP digest may be used within Transport Layer Security
(TLS) to perform client authentication. Server authentication is mandatory in TLS.
Each VoIP client is provisioned with at least one set that includes a realm identifier,
username, and password (shared secret). The information is also stored on the
network servers.
19-38

19 VoIP overview
19.7
VoIP call statistics

VoIP call statistics are gathered for the last incoming or outgoing call on each POTS
port configured for VoIP on the ONT. Up to 32 previous call statistics are supported
individually.
An RTCP failure alarm is raised at the P-OLT if RTCP packets are not received
during a VoIP call.
Statistics collection
VoIP call statistics for the last incoming or outgoing call are retained at the ONT.
You can view the statistics from a management session with the P-OLT using TL1
or the EMS interface.
Collection of call statistics occurs when a bearer channel is established. If multiple
bearer channels are established during the course of a single call, such as if call
waiting occurs, then only the data from the last disconnected bearer channel is
retained in the ONT.
Table 19-9 lists the VoIP call statistics that are collected.
Table 19-9 Collected VoIP call statistics
Type
Description
Statistic
Format/unit
(1)
The date when the call was initiated. This is determined at

the start of ringing when terminating a call (incoming), or
when going off-hook for the originating call (outgoing).
DATE
YY-MM-DD
Example: 06-01-16
Time (1)
The time when the call was initiated. This is determined at

the start of ringing when terminating a call (incoming), or
when going off-hook for the originating call (outgoing).
TIME
HH-MM-SS
Duration
The duration of the call is recorded as an integer in seconds.

For a call origination, the duration starts at the initial
off-hook and stops when the call ends with on-hook. For call
termination, the duration starts when ringing is applied to
the line, continues when the line goes off-hook, and stops
when the call ends with on-hook.
DURATION
seconds
Called number (2)
For outgoing calls, the called number is the digits dialed by

the subscriber.
CALLEDNO
a string of up to 25
alphanumeric
characters
CALLINGNO
a string of up to 25
alphanumeric
characters
Date
Example: 13-30-02
For incoming calls, the called number is the identity of the

subscriber line terminated at the ONT that is receiving the
call.
Calling
number (2)
For outgoing calls, the calling number is the identity of the

subscriber line terminated at the ONT that is initiating the
call.
For incoming calls, the calling number is the phone number
or identity of the external party that is calling a subscriber
line terminated at the ONT.
RTP packets
transmitted
The total number of RTP packets transmitted during of the

call.
TXPKTS
integer
RTP packets
received
The total number of RTP packets received during the call.
RXPKTS
integer
(1 of 2)

19-39
19 VoIP overview
Type
Description
Statistic
Format/unit
RTP packets lost
The total number of RTP packets lost during the call.
PKTSLOST
integer
RTP packets
discarded
The total number of RTP packets discarded due to errors.
PKTSDISC
integer
Jitter buffer
overruns
The total number of jitter buffer overruns.
OVERRUNS
integer
Jitter buffer
underruns
The total number of jitter buffer underruns.
UNDERRUNS
integer
Average jitter
The average jitter for received packets is recorded as an

integer in milliseconds.
AVGJTR
milliseconds
RTCP
participation
The far end RTCP participation with valid values of

participated or not participated.
RTCP
Peak jitter
The peak jitter.
PJTR
milliseconds
Average jitter
buffer depth
The average jitter buffer depth.
AVGJTRBD
milliseconds
RTCP-XR
participation
The far end RTCP-XR participation with valid values of

participated or not participated.
RTCPXR
RTCP-XR peak
round-trip delay
The peak round-trip delay for a call. (Only available if

far-end participated in RTCP-XR.)
PRTDEL
integer
RTCP-XR average
round-trip delay
The average round-trip delay for the call. (Only available if

far-end participated in RTCP-XR.)
AVGRTDEL
integer
RTCP-XR average
mean opinion
score
The average mean opinion score (MOS) with valid values of 0

to 500 in hundredths. (Only available if far-end participated
in RTCP-XR.)
AVGMOS
integer
(2 of 2)
Notes
(1)
(2)
The time and date data is from the local GMT time kept at the ONT.
Not supported for voice gateway and H.248 softswitch modes.
RTCP failure alarm

When a bearer channel is established on a VoIP POTS port on the ONT, the
7342 ISAM FTTU monitors RTCP activity. The alarm management software raises
an RTCP failure alarm when no RTCP packets are detected on the established bearer
channel within a configured duration of time. By default, the system waits 3 min
before raising an RTCP failure alarm.
The RTCP alarm is associated with a specific POTS port on the ONT. You can view
system-generated alarms at the P-OLT using TL1 or the EMS interface. An active
RTCP failure alarm is cleared at the P-OLT when either the VoIP call is terminated
or RTCP packets are detected on the bearer channel.
19.8
XML file configuration data for package C ONTs

For ONTs that are shipped with an XML file already configured, the data that defines
SIP and H.248 behavaior is pre-configured with default values. Use an XML file
editor to update the file to meet network voice requirements. Table 19-10 lists the
XML file configuration options, sample XML, and parameter ranges.
19-40

19 VoIP overview
Table 19-10 XML file configuration data for package C ONTs
XML parameter
Parameter values
Sample XML
Information
Signaling protocol and country codes configuration

SignalingProtocol
country
Specifies the VoIP signaling protocol.
<onuDeviceConfig>
Options are:
<VoipGlobal>
<Basicconfig
SignalingProtocol=SIP
country=DK/></BasicConfig
>
SIP
H248
Applicable country code, as outlined in ISO

3166. Can be the country code (for
example, DK for Denmark) or the numeric
code (208 for Denmark)
SG Singapore 702
AU UAE United Arab Emirates 784
DE Germany 276
GB UK United Kingdom 826
CN China 156
US USA United States of America 840
BR Brazil 076
IP configuration
ipgetmode
IP configuration mode. Options are:
<Ipconfig>
<Ipmode ipgetmode="static"
address="172.19.113.253"
gateway="172.20.115.250"
mask="255.255.255.0"
username="" passwd=""
DNSServer1="0.0.0.0"
DNSServer2="0.0.0.0"/>
dhcp
static
pppoe
DNS
configuration
can be used
when set to
static
address
Static IP address when ipgetmode is set to

static. The value is null when ipgetmode is
set to dhcp or pppoe
gateway
IP gateway address when ipgetmode is set to

mask
IP netmask when ipge mode is set to static.

The value is null when ipgetmode is set to
dhcp or pppoe
DNSSer ver1
First DNS server when ipgetmode is set to

DNSServer2
Second DNS server when ipgetmode is set to

username
PPPoE user name an alphanumeric string of

1 to 64 characters. There is no default.
passwd
PPPoE user name password is an

alphanumeric string of 1 to 31 characters.
There is no default.
</Ipconfig>
Telnet configuration
TELNET
Specifies whether to enable or disable

Telnet service access from the VoIP IP
address. The options are:
<VoipServiceACL
TELNET="disable"/></VoipGlo
bal
enable
disable (default)
SIP voice server configuration

(1 of 9)

19-41
19 VoIP overview
XML parameter
Parameter values
Sample XML
Information
InstanceID
Specifies the SIP server instance. This is set

to 1 and cannot be changed.
<voice>
expire-time
Expiration time, in seconds. The range is

3600 (default) to 31 536 000 seconds (1 hour
to 365 days)
sipServerIP
Specifes the SIP server IP address in v4

format or domain name.
sipDomain
Host URI value.
<sipServer MaxNumber="4"
NumberOfInstance="1">
<sipServerInstance
InstanceID="1"
expire-time="120"
sipServerIP="172.20.135.250"
sipServerPort="5060"
sipDomain=""
sipKeepAlive="0"/>
</sipServer>
If not
configured, the
sipServerIP
value is used.
sipServerPort
Specifies the SIP server port value. The

range is an integer from 1 to 65534. The
default is 5060.
obServer
Outbound SIP server IP address in v4 format

or domain name.
A null address or
not configured
indicates no
outbound server
is used.
sipKeepAlive
Specifies the keepalive value used by the SIP

protocol. The options are:
Not currently
supported.
support100rel
Specifies whether 100rel is included in the

support header of the INVITE request. The
options are:
require100rel
0 (default) for no keepalive

1 for UDP
2 for Update
enable
disable (default)
Specifies whether 100rel is included in the

require header of the provisioning response
following the INVITE request request. The
options are:
enable
disable (default)
SIP voice server port configuration

InstanceID
Specifies the SIP server port instance. This is

set to 1 and cannot be changed.
<sipPort MaxNumber="2"
primarySip
Specifies the primary SIP proxy for the SIP

server instanceID. Only one SIP server is
supported.
<sipPortInstance
InstanceID="1" primarySip="1"
secondarySip="3" vmailSrv="1"
serviceCfg ="1"/>
secondarySip
Specifies the secondary SIP proxy for the SIP

server instanceID. Only one SIP server is
supported. A value of 0 indicates no
secondary server is supported.
<sipPortInstance
InstanceID="2" primarySip="1"
secondarySip="4" vmailSrv="1"
serviceCfg ="1"/>
Not currently
supported
vmailSrv
Specifies the SIP voice mail instanceID. A

value of 0 indicates no voice mail server is
supported.
</sipPort>
serviceCfg
Specifies the service configuration profile

instanceID. A value of 0 indicates no service
configuration profile is supported.
(2 of 9)
19-42

19 VoIP overview
XML parameter
Parameter values
Sample XML
Information
<sipVoiceMail MaxNumber="3"
Not currently
supported
SIP voice mail configuration

InstanceID
Specifies the SIP voice mail instance. This is

set to 1 and cannot be changed.
sipVoiceMailEn
Specifies whether to enable or disable MWI.

The options are:
open (enable)
close (disable)
sipVoiceMailServerI
P
Specifes the SIP voice mail server IP address

in v4 format or domain name.
expire-time
Expiration time, in seconds. The range is

300 (default) to 31 536 000 seconds (5
minutes to 365 days)
<sipVoiceMailSvrInstance
InstanceID="1"
sipVoiceMailEn="Open"
sipVoiceMailSrvIP="172.20.135
.250" expire-time="120" />
</sipVoiceMail>
Not currently
supported
Not currently
supported
Not currently
supported
SIP basic phone service configuration

Multiple instances of <sipBasic> are supported
(3 of 9)

19-43
19 VoIP overview
XML parameter
Parameter values
Sample XML
Information
InstanceID
Specifies the SIP basic phone service

instance, as represented by a POTS port.
<sipBasic MaxNumber="2"
POTS port index
name
Specifies the SIP basic phone instance,

typically, a telephone number. Supports a
string of up to 63 characters.
sipUserName
User name an alphanumeric string of 1 to 31

characters. There is no default.
sipUserPasswd
User name password is an alphanumeric

string of 1 to 31 characters. There is no
default.
ReleaseTimer
Specifies the call release timer value. To

end a conversation, the local or remote
subscriber hangs up. If the local subscriber
hangs up, BYE is sent to the softswitch
immediately unless this was a termination
end of the call. If the local call was the
termination call, BYE is not sent and the idle
state is entered until the re-answer timer
expires or BYE is received.The range is 0 to
4294967295 milliseconds. The default is
10000 milliseconds.
<sipBasicInstance
InstanceID="1" name="2001"
sipUserName="2001"
sipUserPasswd="2001"
portAdmin="open" RxGain="10"
TxGain="-120"/>
<sipBasicInstance
InstanceID="2" name="2002"
sipUserName="2002"
sipUserPasswd="2002"
TxGain="-120"/>
</sipBasic>
A value of 0
indicates to use
the ONT value.
BusyTimer
Specifies the busy timer value. The range is

0 to 4294967295 milliseconds. The default is
15000 milliseconds.
A value of 0
indicates to use
the ONT value.
RohTimer
Specifies the ROH timer value. The range is

0 to 4294967295 milliseconds. The default is
15000 milliseconds.
A value of 0
disables the ROH
timer.
RingingTimer
Specifies the ringing timer value, which

determines how long the ringback tone is
played. The range is 0 to 4294967295
milliseconds. The default is 60000
milliseconds.
A value of 0
indicates to use
the ONT value.
WaitDialingTimer
Specifies the wait dialing timer value, which

determines how long to wait for the first
digit to be dialed. The range is 0 to
4294967295 milliseconds. The default is
16000 milliseconds.
A value of 0
indicates to use
the ONT value.
criticaltimer
Specifies the critical timer value. The range

is 0 to 4294967295 milliseconds. The default
is 4000 milliseconds.
partialtimer
Specifies the partial timer value. The range

is 0 to 4294967295 milliseconds. The default
is 16000 milliseconds.
SIP protocol local port configuration

sipportsipLocalPort
Specifies the SIP protocol port value. The

range is an integer from 1 to 65534. The
default is 5072.
<sipport sipLocalPort="5072"/>
Value cannot be
changed from
default.
SIP digit map dial plan configuration

Multiple instances of <sipAdvanced> digit map dial plans are supported
(4 of 9)
19-44

19 VoIP overview
XML parameter
Parameter values
Sample XML
Information
InstanceID
Specifies the instance of the digit map dial

plan. The value is an integer from 1 to 64.
<sipAdvanced MaxNumber="64"
A maximum of
64 instances are
supported.
digitmap
Specifies the digit map dial plan. The value

is a digit map. Contact your Alcatel-Lucent
support representative for more
information about digit map formats that
are supported in the XML file configuration.
<sipAdvInstance InstanceID="1"
digitmap="[xABCD*#].T"/>
digitmap="[xABCD*#].T"/></si
pAdvanced>
H.248 system timer configuration

StartTimer
Specifies the digit map start timer value.

The range 1 to 99 seconds. The default is 20
seconds.
LongTimer
Specifies the digit map long timer value.

seconds.
ShortTimer
Specifies the digit map short timer value.

seconds.
<H248MGSysPara
StartTimer="20"
LongTimer="10"
ShortTimer="5"/>
H.248 media gateway protocol configuration

InstanceID
Specifies the H.248 protocol instance. This

is set to 1 and cannot be changed.
MgDomainName
Specifies the media gateway domain name

or the device name. The value is a string of
1 to 64 characters.
mgPort
Specifes the media gateway UDP port. The

range is a port number in the range 1 to
65535. The default is 2944.
Heartbeattimer
Specifies the heartbeat timer. The value is

a range of 5 to 655 seconds. The default is
60 seconds.
<H248MG
NumberOfInstance="1"
MaxNumber="1">
<H248MGInstance
InstanceID="1"
MgDomainName="website.com
" MgPort="2944"
heartbeattimer="60" format="
Long " Topversion="2"
MIDFormat="0" auth="disable"
authInitKey="securitykey"
authmgid="websiterg.com"/>
</H248MG>
format
Specifies the H.248 protocol message

format. The options are short (default) and
long
Topversion
Specifies the H.248 protocol top version.

The range is an integer from 1 to 4. The
default is 2
MIDFormat
Specifies the message sender identification

value of the media gateway. The options
are:
0 (default) for IP address

1 for domain name
2 for device name
H.248 MGC configuration

(5 of 9)

19-45
19 VoIP overview
XML parameter
Parameter values
Sample XML
Information
InstanceID
Specifies the MGC instance. This is set to 1

and cannot be changed.
caAddr
Specifes the MGC server IP address in v4

format or domain name.
<H248MGC
MaxNumber="2">
caPort
Specifies the MGC port value. The range is

an integer from 1 to 65535. The default is
2944.
MgDomainName
Specifies the media gateway domain name

or the device name. The value is a string of
1 to 64 characters.
<H248MGCInstance
InstanceID="1"
caAddr="192.168.1.111"
caPort="2944"
MGCDomainName="MGC.com"
/>
</H248MGC>
<H248User
MaxNumber="4">
The maximum
value is the
number of POTS
ports available.
H.248 user configuration

InstanceID
Specifies the H.248 user instance.
TID
Specifies the termination ID value. The

range is a string of 1 to 64 alphanumeric
characters. The defualt is A0
phonenumber
<H248UserInstance
InstanceID="1" TID="A0"
phonenumber="61921930"/>
</H248User>
Specifies the phone number.
VoIP POTS configuration (for SIP and H.248

Multiple instances of <voipPotsCfg> s are supported
InstanceID
portAdmin
Specifies the VoIP POTS instance. This is set

to 1 and cannot be changed.
Specifies the administrative state of the
POTS port. The options are:
open (enabled)
close (disabled)
RxGain
Specifies the gain for the POTS port on the

receiving side. The range is an integer from
-120 to + 60, in 0.1 dB increments.
TxGain
Specifies the gain for the POTS port on the

transmitting side. The range is an integer
from -120 to + 60, in 0.1 dB increments.
<voipPotsCfg>
<potsBasic MaxNumber="2"
<potsBasicInstance
InstanceID="1"
TxGain="-120" />
<potsBasicInstance
InstanceID="2"
TxGain="-120" />
</potsBasic>
Applies to SIP or
H.248
Applies to SIP or
H.248
Applies to SIP or
H.248
VoIP CODEC configuration (for SIP and H.248)

Multiple instances of <voipCodecCfg> are supported
(6 of 9)
19-46

19 VoIP overview
XML parameter
Parameter values
Sample XML
Information
InstanceID
Specifies the VoIP CODEC instance, as

represented by a POTS port.
<voipCodecCfg MaxNumber="2"
POTS port index
CodecControl
An audio format name, chosen from among

the audio MIME types registered with the
IANA (many of which are listed in RFC 3555).
The audio/telephone-event format
specified by RFC 2833 is implicitly included
by the user agent in all offers, and in all
answers to an offer that includes that
format, and thus a setting including that
format is never required.Specifies the
supported CODECs. Multiple codecs can be
supported, separated by commas. The
options are G.711u, G.711a, G.729a,
G.723.1.
silenceSuppress
<voipCodec InstanceID="1"
codecControl="G.711u,G.711a"
silenceSuppress="open,open"
packetPeriod="10,15" />
<voipCodec InstanceID="2"
codecControl="G.711u,G.729a
,G.711a"
silenceSuppress="open,open,cl
ose" packetPeriod="10,5,15" />
</voipCodecCfg>
Specifies the silence suppress value. A

silence suppress value is required for each
CODEC type supported, separated by
commas. The options are:
Applies to SIP
and optionally
for H.248
Applies to SIP
and optionally
for H.248
open (enabled) (default value)

close (disabled)
packetPeriod
Specifies the packetization rate which each

line of the voice client (ONT or MDU) will use
in the offer/answer SDP messages for the
RTP packet rate it requests to receive. The
units are milliseconds between successive
frames. A packet period value is required
for each CODEC type supported, separated
by commas. The options are 5, 10, 20
(default), or 30 milliseconds.
Applies to SIP
and optionally
for H.248
min
A range of port numbers specifying the

minimum and maximum ports numbers to be
used by the user agent for RTP media.
Specifies the minimum RTP port number.
default is 50000.
Applies to SIP
and optionally
for H.248
max
A range of port numbers specifying the

minimum and maximum ports numbers to be
used by the user agent for RTP media.
Specifies the maximum RTP port number.
default is 50010.
Applies to SIP
and optionally
for H.248
VoIP media configuration (for SIP and H.248)

Multiple instances of <voipMedia> are supported
(7 of 9)

19-47
19 VoIP overview
XML parameter
Parameter values
Sample XML
Information
InstanceID
Specifies the VoIP media instance, as

represented by a POTS port.
<voipMedia MaxNumber="2"
POTS port index
fax-mode
Specifies the fax mode. The options are t38

and pass (for G.711 pass through mode)
DTMF
Specifies the DTMF mode. This parameter

specifies whether the voice client transmits
DTMF digits in INFO method SIP messages
rather than inband or via RFC 2833
signaling. The ONT or MDU will offer RFC
2833 or include it in an SDP response only if
the RFC2833 is set to open. The options are
Oob (out of band) and Inb (in-band)
Rfc2833
Specifies whether RFC 2833 is enabled or

disabled. In order for DTMF tones to be
encoded in RFC 2833 packets, there must be
SDP negotiation and agreement at both ends
of the bearer channel.
<voipMedia InstanceID="1"
fax-mode="t38" DTMF="oob"
jitter-mode="dyn"
max-jitter="60"
target-jitter="20" ec="open" />
<voipMedia InstanceID="2"
fax-mode="t38" DTMF="oob"
jitter-mode="dyn"
max-jitter="60"
target-jitter="20" ec="open" />
</voipMedia>
</voipPotsCfg>
Supported when
DTMF is set to
Oob
open (RFC 2833 is enabled)

close (RFC 2833 is disabled and SIP
information is used)
Jitter-mode
Specifies the jitter buffer mode. The

options are Dyn (dynamic) or Sta (static)
Max-jitter
Specifies the maximum jitter buffer. The

value is 0 to 65535 milliseconds. The default
is 100 milliseconds
Supported when
jitter-mode is
set to Dyn
Target-jitter
Specifies the target jitter buffer value. The

value is 0 to 65535 milliseconds. The default
is 20 milliseconds
Supported when
jitter-mode is
set to Dyn
ec
Specifies whether echo cancellation is used.

The options are:
open (enabled)
close (disabled)
VoIP service configuration (for SIP and H.248)

Multiple instances of <sipServiceCfg> are supported
(8 of 9)
19-48

19 VoIP overview
XML parameter
Parameter values
Sample XML
Information
InstanceID
Specifies the service instance. This is set to

1 and cannot be changed.
<sipServiceCfg MaxNumber="2"
cid
Specifies whether caller ID is supported.

The options are:
call-wait
Specifies whether call waiting is supported.

The options are:
call-hold
open (enabled)
close (disabled)
Not currently
supported
ring (splash ring)

tone (special dial tone)
visual (visual indicator)
Not currently
supported
open (enabled)
close (disabled)
Specifies the direct call mode. The options

are:
direct-number
Enabling any of
call-hold,
call-transfer, or
confcall enables
all three.
open (enabled)
close (disabled)
Specifies whether call forwarding is

supported. The options are:
direct-call
</onuDeviceConfig>
Specifies the message waiting indicator

type, for each supported call service option,
separated by commas. The mode for
presenting a message-waiting indication to
the user. This is a sequence of up to three
values: tone to enable stutter dial tone,
visual to enable visual MWI, and ring to
enable a reminder ring. The options are:
call-forward
</Voice>
Specifies whether conference calling is

supported. The options are:
mwi-present
open (enabled)
close (disabled)
</sipServiceCfg>
Specifies whether call transfer is supported.

The options are:
confcall
open (enabled)
close (disabled)
Specifies whether call hold is supported.

The options are:
call-transfer
open (enabled)
close (disabled)
<sipServiceInstance
InstanceID="1" cid="open"
call-wait="open"
call-hold="open"
call-transfer="open"
confcall="open"
mwi-present="ring,tone,visual
" call-forward="open"
direct-call="hot"
direct-number="911" />
Not currently
supported
hot (hotline enabled)

warm (warm line enabled)
close (direct call disabled)
Specifies the direct call number, typically, a

telephone number. Supports a string of up
to 31 characters.
Not currently
supported
(9 of 9)

19-49
19 VoIP overview
19-50

20 HSI service
20.1 Overview
20-2
20.2 Network example
20-2
20.3 HSI service configuration elements

20.4 QoS characteristics
20-3
20-6
20.5 HSI service configuration example

20-9
20-1
20 HSI service
20.1
Overview
This chapter provides high level information about the implementation of the
HSI service in the 7342 ISAM FTTU. Although the HSI service can carry different
types of traffic, such as IPTV traffic, this chapter focuses on the delivery of IP data
services to subscribers.
TL1 and CLI for HSI related procedures.
20.2
Network example
The HSI service enables the delivery of IP data services to business and residential
subscribers. Figure 20-1 provides an overview of the delivery of IP data services to
a subscriber across the triple play service delivery architecture (TPSDA).
Figure 20-1 Delivery of data services across the TPSDA
Services and
servers
Edge Routing
Aggregation
Access network
Home/Business/MTU
VPLS/
HVPLS
HSI
Internet
ONT
Internet
7450 ESS
7750 SR
7342 ISAM
FTTU
19464
Following is a description of the flow of IP data traffic across the 7342 ISAM FTTU
access network. For a description of the flow of traffic between the internet and the
7342 ISAM FTTU, see Section 22.3, 7342 ISAM FTTU service delivery across the
TPSDA.
Downstream flow across the 7342 ISAM FTTU access network

IP data traffic flows from the 7450 ESS to the subscriber as follows.
20-2
At the 7450 ESS, when the switch determines that the packet is destined for a
subscriber port, the packet is mapped to the appropriate VLAN for a particular
subscriber.
The 7450 ESS forwards the packet on the access GE port with the appropriate
p-bit.
The 7342 ISAM FTTU access node receives the packets as single- or
double-tagged frames, and manipulates the tag based on the tagging mode of the
VLAN.
The frames are directed to a GEM port based on the value of their p-bit and
VLAN ID, and carried downstream over the GPON as untagged, priority-tagged,
or tagged frames.

20 HSI service
The ONT receives the frames on the GEM ports. If the ONT UNI port associated
with a GEM port is configured as an untagged port, the ONT strips the frames of
their tag header. For tagged ONT UNI ports, the ONT leaves the frames intact.
The switch at the ONT forwards the frames to the ONT UNI port as untagged or
tagged frames.
Upstream flow across the 7342 ISAM FTTU access network

IP data traffic flows from the subscriber to the 7450 ESS as follows.
1
In the upstream direction, the IP data traffic enters the 7342 ISAM FTTU access
network through an Ethernet, VDSL2, or MoCA port on the ONT as untagged,
priority-tagged, or tagged frames
On a packet basis, the ONT tags and marks the received frames with their p-bit
and C-VLAN ID based on the upstream tagging mode of the port.
The ONT directs the frame to one of eight GEM ports according to its priority
queue.
The frame is carried across the GPON on the GEM port contained within a
T-CONT to the LT as either a priority-tagged or tagged frame. The DBA at the
LT card grants upstream bandwidth to the frame on a T-CONT basis.
The LT receives priority-tagged and tagged frames on the GEM port. The LT
priority marks the frame with the p-bit received from the ONT, and tags the
frame with its S-VLAN ID in one of two ways.
In VLAN stacked mode, the LT adds an outer S-VLAN tag, and sends the frame
upstream to the network as a double-tagged frame.
In VLAN unstacked mode, the LT overwrites the C-VLAN ID with the

S-VLAN ID, and sends the frame upstream to the network as a single-tagged frame.
20.3
The switches direct the frame from the LT to the NT, and from the NT to the
SHub. The S-VLAN ID determines the outgoing ports along the way, and the
p-bit determines the queues.
The 7450 ESS receives the packet on the subscriber VLAN.
HSI service configuration elements

The following configuration elements are required to configure an HSI service:
S-VLAN
ONT
Port-related elements
ONT UNI port including Ethernet, VDSL2, or MoCA port
QoS marker and session profile
HSI service
HSI service
bandwidth profile
priority queue profile

20-3
20 HSI service
Figure 20-2 shows the configuration elements in a networking topology where two
HSI services are configured a single ONT UNI port.
Figure 20-2 HSI service configuration elements in a networking topology
A priority queue profile governs queuing and scheduling
of different traffic flows by service.
ONT
Scheduler
(A)
ANI
(GPON)
ONT UNI port
Pri=0 GEM port ID=i

Pri=1 GEM port ID=j
SP+
WRR
T-CONT
(A)
ONT-IWF
HSI service (1)
Pri=2 GEM port ID=k

Pri=3 GEM port ID=l
LT
Pri=4 GEM port ID=m

Pri=5 GEM port ID=n
SP+
WRR
T-CONT
(B)
Ethernet/VDSL/MoCA port
HSI service (2)
Pri=6 GEM port ID=o

Pri=7 GEM port ID=p
Scheduler
(B)
Queues
Downstream
Upstream
A DSCP to p-bit mapping is used to

priority-mark untagged frames from a
trusted customer.
A QoS marker and session profile
directs marking and tagging of traffic
flows on a port.
19460
HSI elements
Table 20-1 shows where to locate a detailed description of each configuration
element.
Table 20-1 HSI service configuration elements
HSI element
See
S-VLAN
Chapter 18
ONT
7342 ISAM FTTU ONT Product Information Manual
ONT UNI port
7342 ISAM FTTU ONT Product Information Manual
Section 15.3
Section 15.3
HSI service
7342 ISAM FTTU Operations and Maintenance

Procedures Guide using TL1 and CLI
Bandwidth profile
Section 15.6
20-4
Section 15.5

20 HSI service
Relationship among the HSI elements

The relationships among the HSI elements are shown and labelled in Figure 20-3 and
are described in Table 20-2.
Figure 20-3 Relationships among HSI elements
GEM
port
I
A
ONT
ONT UNI
port
HSI
service
Priority queue
profile
J
G
T-CONT
D
E
DSCP to p-bit
mapping
Port provisioning
data
QoS session
profile
QoS marker
profile
Bandwidth
profile
HSI service provisioning data
One-to-one mapping
One-to-many or many-to-one mapping
19461

20-5
20 HSI service
Table 20-2 Relationships among HSI elements
Key
Relationship description
Based on the model of ONT, an ONT can support multiple Ethernet/VDSL2/MoCA

ports. Each port supports a single subscriber.
An ONT UNI port can carry one or more HSI services to the subscriber. Typically this
configuration occurs when more than one service provider is supplying services to
the subscriber.
A DSCP to p-bit mapping is used to priority mark untagged frames from a trusted
customer. If a DSCP to p-bit mapping is not configured for the port, the ONT uses
the system-wide DSCP to p-bit mapping.
The QoS marker profile specifies the tagging mode of a port in the upstream and
downstream directions. All services provisioned on the ONT UNI port inherit the
same tagging mode. Because each port can have its own QoS marker profile,
multiple tagging modes can be supported simultaneously across different ONT UNI
ports.
An upstream and a downstream bandwidth profile specify the bandwidth

requirements of a service. Services can share the same bandwidth profiles.
Each HSI service is configured with one priority queue profile that directs the
queuing and scheduling of its traffic by p-bit. HSI services can share the same
priority queue profile on the same port or across ports.
The 7342 ISAM FTTU assigns a single T-CONT to a priority queue profile to carry
service traffic across the GPON.
For each priority queue that is specified in a priority queue profile, a GEM port is
assigned. Traffic is directed to a GEM port based on p-bit as follows:
the p-bit to queue mapping in the priority queue profile maps the p-bit in the
frame to a queue in the profile
the queue determines the GEM port
There is a maxium of 19 GEM ports available per ONT. This is turn limits the number
of priority queues per ONT to 19. When multiple priority queues are used per
service, this limits the number of services available per ONT UNI.
I
Because a port can have up to eight priority queues, an Ethernet/VDSL2/MoCA port

can have one to eight GEM ports. Where more than one service is configured for a
port, each priority queue profile must use fewer than eight priority queues.
There is a maxium of 19 GEM ports available per ONT. This is turn limits the number
of priority queues per ONT to 19. When multiple priority queues are used per
service, this limits the number of services available per ONT UNI.
Traffic is carried across the GPON in GEM ports that are contained in the T-CONT.
A T-CONT is limited to a maximum of eight GEM ports.
Note See the 7342 ISAM FTTU Operations and Maintenance

Procedures Guide using TL1 and CLI for configuration details of
each element.
20.4
QoS characteristics
This section describes QoS characteristics that are specific to HSI. For a detailed
overview of QoS, see chapter 15.
20-6

20 HSI service
Data traffic
An HSI service carries the following types of data traffic:
IP enscapsulated data traffic

IP enscapsulated data traffic in PPPoE
The ONT transparently passes data traffic between an ONT UNI port and a GEM
port in both the upstream and downstream directions.
Upstream direction
In the upstream direction, the following path shows how traffic from an ONT UNI
port is directed to a GEM port:
ONT UNI port HSI service p-bit in the frame p-bit to queue mapping
priority queue GEM port
A flow of traffic from an HSI service on an ONT UNI port is directed upstream to
one of eight GEM ports. The GEM port is selected based on the priority queue to
which the p-bit encoded in the tag header of the frame is mapped.
Downstream traffic
Downstream traffic is switched directly to the ONT UNI port that is associated with
the GEM port.
P-bit
Unlike video and voice data, HSI data is tolerant of jitter, delays, and packet loss, and
does not require preferential treatment over other traffic types. Because the p-bit
differentiates traffic into CoS, the lower p-bit values of 0 through 2 are normally
reserved for data traffic. These p-bits correspond to the following CoS:
best effort
advanced forwarding
Note P-bit 7 is reserved for management traffic, such as OMCI.
For more information on the assignment of p-bits to traffic classes,
see Table 15-14, Recommended CoS mapping.
Traffic queuing and scheduling

Because priority queue profiles are associated on a per service basis, multiple
priority queue profiles can be supported simultaneously across an ONT UNI port in
the upstream direction.
Figure 20-4 shows how a single priority queue profile can support all traffic across
an ONT UNI port. This configuration normally occurs when a single provider
supplies all services to a subscriber across the ONT UNI port.

20-7
20 HSI service
Figure 20-4 Upstream traffic queuing for single priority queue profile
Traffic tagging and prioritization in both the
upstream and downstream directions
ONT
ANI
(GPON)
ONT-IWF
ONT UNI port
Pri=0 GEM port ID=i

Pri=1 GEM port ID=j
Pri=2 GEM port ID=k
Pri=3 GEM port ID=l
LT
T-CONT
(A)
SP+
WRR
Pri=4 GEM port ID=m
Pri=5 GEM port ID=n

Pri=6 GEM port ID=o
Pri=7 GEM port ID=p
Scheduler
(A)
Queues
Downstream
Upstream
19458
Figure 20-5 shows how multiple priority queue profiles can support traffic across an
ONT UNI port. This configuration occurs when more than one provider supplies
services to a subscriber across the ONT UNI port.
There is a maxium of 19 GEM ports available per ONT. This is turn limits the
number of priority queues per ONT to 19. When multiple priority queues are used
per service, this limits the number of services available per ONT UNI.
Figure 20-5 Upstream traffic queuing with two priority queue profiles
Traffic tagging and prioritization in both the
upstream and downstream directions
ONT
Scheduler
(A)
T-CONT
(A)
ANI
(GPON)
ONT-IWF
Pri=1 GEM port ID=j
SP+
WRR
Pri=2 GEM port ID=k
HSI service (1)
Pri=3 GEM port ID=l
LT
Pri=4 GEM port ID=m
T-CONT
(B)
ONT UNI port
Pri=0 GEM port ID=i
Pri=5 GEM port ID=n
SP+
WRR
HSI service (2)
Pri=6 GEM port ID=o

Pri=7 GEM port ID=p
Scheduler
(B)
Queues
Downstream
Upstream
19459
20-8

20 HSI service
Tagging
Each VLAN at the NT is configurable for tagging, and each ONT UNI port on the
ONT is configurable for upstream and downstream tagging.
The P-OLT follows the tagging mode of the VLAN.

The ONT follows the tagging mode of the ONT UNI port, as specified in the QoS
marker profile.
The operator is responsible for ensuring that the VLAN and ONT UNI port tagging
options are compatible.
Table 20-3 lists the tagging modes and where a detailed description of each tagging
mode can be found. The ONT applies the same tagging mode to all services across
an ONT UNI port in both the downstream and upstream directions.
Table 20-3 Tagging modes
Tagging mode
Options
See
VLAN tagging modes
Stacked VLANs
Section 18.5
Unstacked VLANs
Unstacked VLANs in VLAN pass-through
mode
ONT UNI port downstream
tagging modes
Transmit tagged traffic
ONT UNI port upstream

tagging modes
Untrusted mode
Section 18.5
Transmit untagged traffic

Section 18.5
VLAN pass through mode

VLAN/Ethertype translation mode
Ethertype classification mode
20.5
HSI service configuration example

See the training section of the 7342 ISAM FTTU Operations and Maintenance
Procedures Guide using TL1 and CLI for a configuration example.

20-9
20 HSI service
20-10

21.1 Overview
21-2
21-3

21-1
21.1
Overview
The 7342 ISAM FTTU can provide RF video service through the video overlay
function. The function operates downstream in the 1550 nm optical band. Signals
sent over the overlay network are presented to the subscriber as RF signals from a
video F-type connector in the ONT.
Note For information on IP multicasting and IGMP, see
chapter 11.
The RF video service in the downstream 1550 nm optical band supports most
available cable television (CATV) services, including standard analog broadcast
channels, as well as standard and high definition digital broadcast channels. On
MoCA-supporting ONTs operating in the downstream 1490 nm optical band.
additional services can be delivered, including video-on-demand (VOD) and
data-based services, such as interactive video (games). In the upstream direction, the
1310 nm return channel is carried over an HSI service. For access to these services,
a set-top box may be required between the video output of the ONT equipment and
the customers television set.
The MoCA data channel transmits in the 800 MHz to 1500 MHz frequency range,
while the RF video channel transmits in the 54 MHz to 850 MHz or 47 to 862 MHz
frequency range, depending on ONT. The video channel is 6 MHz wide.
Within the ONT functional blocks, the RF subsystem is an RF amplifier that
produces the required RF output for the subscriber video equipment. The RF
subsystem monitors the levels of optical and RF signals in support of the
performance management functions. The RF video service is optional and
independent of the SoC functions.
Note For more information about ONT RF video interface
specifications, see the 7342 ISAM FTTU ONT Product Information
Manual.
Breakdown of the RF 1550 nm and 1490 nm overlay

Figure 21-1 shows the RF 1550 nm and 1490 nm frequency spectrum overlay.
21-2

Figure 21-1 1550 nm and 1490 nm RF overlay on the 7342 ISAM FTTU
<optional>
Switched Digital Broadcast
200/n1000
channels
Analog
Broadcast
50 MHz
100/n1000
channels
Digital
Broadcast
(SD)
1550 nm
(HD)
350 MHz
860 MHz
New services
SD VoD
HD VoD
Non-Video
1490 nm
19443
When MoCA is used as the Ethernet over coaxial technology, how the spectrum is
used becomes an issue. For example, both RF and MoCA could use the 800 MHz to
860 MHz frequency range, but typically MoCA channels start above 860 MHz.
Table 21-1 shows the breakdown of the data channels.
Table 21-1 RF and MoCA channel breakdown
21.2
Feature
RF
MoCA
Data channel width
6 MHz
25 MHz
Downstream frequency range
54 to 860 MHz
800 to 1500 MHz
Data throughput
n/a
above 100 Mb/s
Network example
Figure 21-2 shows the network topology.

21-3
Figure 21-2 RF video service in 7342 ISAM FTTU
Video head end
Core transport
Central office
Fiber (PON)
Distribution
Broadcast
video
ONT
Home network
Analog
channels
Digital
channels
1550 nm
(downstream RF video)
Video RF mux
Video optical
transmitter
EDFA
Coax
1310 nm
(upstream)
B
Private
network
Power
Major Alarm
Processor
Minor Alarm
WDM
VoD
server
VoD
Ethernet
Router
IP
Network
1490 nm
(downstream data)
Coax
7342 OLT
Ethernet
Coax
A Analog broadcast No STB needed

B Digital broadcast STB needed
C Broadcast and VoD STB needed
19442
21-4

22 Triple play service delivery

architecture in access network
22.1 Triple play services

22.2 TPSDA
22-2
22-2
22.3 7342 ISAM FTTU service delivery across the TPSDA

22.4 Configuring the 7342 ISAM FTTU for triple play
22.5 Triple play configuration example

22-9
22-10
22-22
22-1
22.1
Triple play services

Triple play services refer to the delivery of data using high-speed Internet (HSI),
voice, and video services to residential subscribers over a single broadband network.
Each service is a discrete product, as shown in Figure 22-1. The video component
includes linear programming (broadcast television), and optionally a non-linear
Video on Demand (VoD) component.
Figure 22-1 Triple play services
Data
(high-speed Internet)
Voice
Video
Residential gateway
19383
22.2
TPSDA
Triple Play Service Delivery Architecture (TPSDA) allows network operators to
progressively integrate their data (HSI), voice, and video services in a unified and
homogenous ethernet-based aggregation network environment. TPSDA can be
deployed and adapted to the network of a provider.
The 7342 ISAM FTTU TPSDA is based on three major components, as shown in
Figure 22-2:
IP/MPLS network
IP edge aggregation and routing
7342 ISAM FTTU access network
22-2


Figure 22-2 7342 ISAM FTTU TPSDA
IP network
7342 ISAM FTTU

access network
IP edge aggregation
and routing
BSR - broadband service router

BSA - broadband service aggregator
5620 SAM
5526 AMS/
5523 AWS
5750 SSC
7342
ISAM
FTTU
access
BSA
VLAN (8)
NGN
7450 ESS
7342
ISAM
BSA FTTU
access
Secure VPLS
infrastructure
Video
BSR
DHCP
server
7450 ESS
IP/MPLS
7750 SR
BSA
7342
ISAM
FTTU
access
7450 ESS
Internet
19392
IP/MPLS network
The IP/MPLS network is the core network and includes core routers that are
interconnected using access links, such as fiber. A router consists of line cards,
switching fabric, and a control processor card, as shown in Figure 22-3.
Figure 22-3 Architectural elements of a router
Router
Interfaces
Forwarding
line card
Forwarding
Control plane
line card
Control processor card
Forwarding
line card
Switching fabric
19418

22-3
The switching fabric performs packet switching between line cards.
Incoming packets from external interfaces are received and forwarded to the
switching fabric by the line cards.
The switching fabric switches the packets to other line cards for forwarding to
outgoing interfaces.
The control plane, which resides in the control processor card, calculates forwarding
paths between routers and exchanges routing information.
IP edge aggregation and routing component

The IP edge aggregation and routing component is based on two major network
elements, which are optimized for their respective roles:
the BSA, an aggregation device that performs the subscriber-specific functions

the BSR, a multi-edge service router that provides the routing intelligence
The 7450 Ethernet Service Switch (ESS) provides the BSA functionality; the
7750 Service Router (SR) provide the BSR functionality.
Relationship among elements
Ethernet access ports on the BSA connect the BSA and the 7342 ISAM FTTU access
network.
The 5750 Subscriber Services Controller (SSC) and 5620 Service Aware Manager
(SAM) manage the BSA and BSR as a single virtual node. A secure VPLS
infrastructure interconnects the BSA and BSR.
The BSR routes traffic to and from multiple service providers to the IP/MPLS
network, as shown in Figure 22-4.
22-4


Figure 22-4 IP/MPLS network
IP/MPLS network
Service
provider
Core router
BSR
BSR
Service
provider
Service
provider
Service
provider
Service
provider
Service
provider
Service
provider
Service
provider
Access
link
19419
Architectural elements
Table 22-1 describes the architectural elements of the IP edge aggregation and
routing component.
Table 22-1 IP edge aggregation and routing architectural elements
Component
Description
BSA
The BSA Is a high-capacity Ethernet-centric aggregation device

that:
BSR
aggregates traffic from an 7342 ISAM FTTU that is connected to

subscriber residential gateways
performs per-subscriber queueing, scheduling, accounting, and
filtering
supports hundreds of GE ports, tens of thousands of filter
policies, and tens of thousands of queues
The BSR Is a multi-service edge router that is connected to the

IP/MPLS network. The BSR:
terminates the layer 2 access and routes over IP/MPLS with

support for all IP and MPLS routing protocols
supports per-service and per-content type differentiation of
QoS levels
supports the distribution of multicast traffic
supports hundreds of ports
(1 of 2)

22-5
Component
Description
5750 SSC
The 5750 SSC is a management system that provides a customer

self-service web portal to manage services for a subscriber.The
5750 SSC:
5620 SAM
supports centralized management of customer and service

profiles and policies
works with the 5620 SAM to enable per-user QoS and bandwidth
changes in the network
The 5620 SAM is a management system that provides a unified

interface for activating services and policies across the distributed
elements of the TPSDA, including VPLS, QoS, multicasting, security,
filtering, and accounting.
The 5620 SAM supports the following functions:
secure VPLS infrastructure
installing, creating, configuring, and managing end-user

services
configuring and managing policies related to quality of service,
routing protocols, schedules, ACLs, services, files, accounting,
and statistics
setting polling, deployment, and alarm policies
VPLS Is a provider service that:
emulates the functionality of a Local Area network

interconnects 7342 ISAM FTTUs that are located in different
geographic areas as though they are in the same local area
network
provides multipoint connectivity over an IP network
VPLS instances can be automatically established using

hub-and-spoke and ring topologies. The instance starts in the BSA
and terminates at the BSR, which is connected to the IP-routed
network.
(2 of 2)
7342 ISAM FTTU access network

The 7342 ISAM FTTU access network extends optical access across the last mile of
the communications network to the subscriber using fiber cabling. One single fiber
cable provides triple play services to residential or business subscribers.
Relationship among elements
Figure 22-5 shows a composite view of the 7342 ISAM FTTU access network.
22-6


Figure 22-5 7342 ISAM FTTU access network
P-OLT
GPON
ONT
Optical link length 1
5526 AMS/
5523 AWS
BSA
Splitters
1490 nm
2.4 Gb/s
1310 nm
1.2 Gb/s
7342 P-OLT
1 The maximum optical link length depends on the specific equipment and deployment conditions.
19417
The 7342 ISAM FTTU access node is connected to Ethernet access ports on the
BSA. Typically, a single VLAN per subscriber is configured between the access
node and the BSA. This configuration enables the BSA to apply consistent
per-subscriber policies, such as QoS, filtering, and accounting.
The 5526 Access Management System (AMS) in ANSI markets and 5523 ADSL
Work Station (AWS) in ETSI markets provide both element management and
network management functions for the 7342 ISAM FTTU access network.
All services and traffic are transported between the P-OLT and an ONT over a
GPON network. The primary transport mechanism over the GPON is Ethernet over
GEM, with differentiated levels of service to ensure equitable and efficient
utilization of the shared bandwidth on the GPON.
The P-OLT resides at the office of the service provider and performs a
network-to-GPON interface.
The ONT resides in the customer premise or curb and performs a

subscriber-to-GPON interface function.
Architectural elements
Table 22-2 describes the individual architectural elements of the 7342 ISAM FTTU
access network component.

22-7

Table 22-2 7342 ISAM FTTU access network architectural elements
Component
Description
P-OLT
The P-OLT equipment performs a network-to-GPON interface. The

equipment comprises three main elements:
GPON
NT card: The NT (Ethernet High Capacity Network Termination)

card connects the P-OLT to the BSA.
ACU card: The ACU (Alarm Control Unit) card provides a
centralized collection point for alarms and common alarm
displays for the central office.
LT card: The LT (GPON Line Termination) is an asymmetrical
GPON line interface providing 2.4 Gb/s downstream through a
1490 nm optical wavelength and 1.2 Gb/s upstream through a
1310 nm optical wavelength. The LT card is made up of a
Motherboard (ULTM) and a Daughter card (GLTD). The GLTD
provides the interfaces between the OLT and the ONTs through
the Optical Data Network (ODN), where the PON interface is
terminated and the optical signal is converted to an electrical
signal and vice versa.
The GPON brings optical fiber cabling and signals to the subscriber.
The optical transmission has no power requirements or active
electronic parts after the signal goes through the network.
The GPON employs a point-to-multi-point topology. A single strand
of fiber extends from the P-OLT at the central office to a passive
optical splitter. The splitter multiplies the signal to up to 32
different lines, with each line terminating at an ONT. Anything
transmitted from the P-OLT is then transmitted to the 32 different
lines.The fiber line can typically be extended to a maximum of 18.6
miles (30 km) and can be shared by up to 64 subscribers.
The optical link budget is defined by both loss and bandwidth
characteristics. The loss characteristic is determined by the
difference between the optical transmitter and optical receiver for
each direction. Typically this is 28dB. The bandwidth characteristic
is reflected by the maximum link distance parameter of each OLT
and ONT transmitter specification, and is limited by the smaller of
the upstream and downstream values.
ONT
The ONT is an edge device that terminates the GPON and provides
service interfaces to the subscriber. The ONT receives all
transmissions from the P-OLT, determines what data packets are
for the subscriber, and discards all other packets.
The ONTs are available in various models. They can be used
interchangeably on the GPON network so that service providers can
mix ONT models to meet the unique needs of their client base.
5526 AMS and 5523 AWS
The 5526 AMS and 5523 AWS are EMS that provide a user-friendly
alternative to the TL1 and CLI. The systems allow for full remote
support of network elements, including:
22-8
provisioning
software downloads
database backup and restore
fault management
disaster recovery
performance monitoring

22.3
7342 ISAM FTTU service delivery across the TPSDA

Figure 22-6 shows a high-level view of the delivery of triple play services to a
subscriber across the TPSDA. Typically, the TPSDA uses a VLAN per subscriber
model.
Figure 22-6 7342 ISAM FTTU access network within TPSDA
Services and
Servers
HSIA
DHCP
policy
RADIUS AAA
Edge Routing
IP-service termination
per-service QoS
IPTV multicast routing
DHCP and PPPoE
for HSIA
Soft
switch
DHCP
server
IPTV
SIP
Aggregation
Ethernet aggregation
per-sub, per-service
QoS
subscriber profile
IGMP proxy for IPTV
security
layer 2
forwarding model
Access
GPON
IGMP, security,
QoS
No electronics
(splitters)
IPTV
VPLS/
HVPLS
DHCP
Phone
Internet
IPTV
ONT
7450 ESS
PPPoE
BRAS
Home/Business/MTU
RGs
TR-069
voice
data
video
7750 SR
7342 ISAM FTTU

PON fiber
distribution
HSI
VLAN per subscriber (HSI, VoD)
Priority-tagged packet
Multicast VLAN
Internet
Management VLAN
19382
Downstream
The following describes the flow of traffic from the IP/MPLS network to the
subscriber.
1
Traffic flows in the downstream direction from various sources into the 7750 SR.
The service router examines the IP destination and DSCP value for QoS
treatment and forwards the message to the appropriate VPLS/HVPLS path to the
7450 ESS.
The packet is received by the 7450 ESS and delivered, based on the MAC
address, to the appropriate outgoing port. For a multicast packet, the packet may
also be forwarded to the next 7450 ESS using the HVPLS functionality that
allows drop-and-continue capability for multicast traffic. When the switch
determines that the packet is destined for a subscriber port, the traffic is mapped
to the appropriate VLAN for the subscriber. At this point, subscriber policies are
applied, such as shaping and DSCP examination, and the packet is forwarded on
the access GE port with the appropriate p-bit.

22-9
The 7342 ISAM FTTU access node receives the packet, applies the appropriate
queuing based on the p-bit, combines any multicast traffic destined to that
subscriber based on p-bit, and forwards the packet to the appropriate ONT UNI
port
The packet is sent to the customer premises equipment (CPE). The CPE
examines the IP address, TCP port, and the DSCP values, and forwards the
packet using the NAT function to the appropriate port on the RG.
Upstream
The following describes the flow of traffic from the subscriber to the IP/MPLS
network.
22.4
Upstream traffic originates from a port on the RG and is assigned appropriate

QoS-based settings based on various parameters. The NAT function is applied to
replace the local IP address with the RG network IP address. The traffic is then
marked or tagged with the appropriate DSCP, p-bit, and/or C-VLAN ID, and sent
to the 7342 ISAM FTTU access node as an untagged, priority-tagged, or
C-CLAN tagged message.
The 7342 ISAM FTTU access node examines the message to determine whether
any special actions are required, such as for IGMP, DHCP, 802.1x, adding the
appropriate VLAN ID and forwarding the message to the WAN port. The
appropriate queuing is used based on the destination MAC address, and any
protocol-aware processing and p-bit.
The 7450 ESS receives the packet on the subscriber VLAN and applies, for
example, the subscriber policies, filters. The packet is forwarded using the MAC
address to the appropriate HVPLS path.
At the edge router, the 7750 SR is the first point in the network where traffic that
originates from one subscriber can be sent to another subscriber. Until this point,
all traffic has been directed upstream using the VLAN and VPLS functions.
Traffic can not be switched from one subscriber to another at layer 2 of the
network. For security and traffic management, all traffic must pass through a
router to be sent to a subscriber.
Configuring the 7342 ISAM FTTU for triple play

Figure 22-7 is a top-level view of the functions required to configure and provision
the 7342 ISAM FTTU system for triple play. Each box represents a function that
comprises one or more procedures, and the arrows represent the flow of information
from one function to another function.
22-10


Figure 22-7 Triple play workflow
NT card, ACU card,

LT card, PON, ONT,
Service card, power
shedding profile ID
Management VLAN,
Multicast VLAN,
Subscriber VLAN
1
Configure
equipment
Rack, shelf, LT slot,

PON, ONT, slot
Subscriber
VLAN ID
3
Configure
VLANs
Multicast
VLAN ID
Subscriber
VLAN ID
Downstream scheduler ID
QoS profiles. Power

shedding profile
2
Configure QoS
and shedding
profile
Configure
services
Configure VLAN
for DHCP relay
Configure
IGMP
Bandwidth profile ID,

QoS session profile ID,
Priority queue profile ID
Data service,
Voice service,
Video service
Multicast sources,
IGMP system parameters,
Bandwidth per PON
19429
Configure the equipment

The equipment must be configured at the P-OLT level and at the ONT level.
P-OLT equipment
The equipment at the P-OLT includes NT cards, ACU cards, LT cards, and the PON
facility.
ONT equipment
The equipment at the ONT level includes the ONT and service interface cards.
An optional power shedding profile can be configured for an ONT to establish the
length of time that a class of service is to remain operational when the power source
for the ONT transitions to battery power during an outage.
Configure QoS
The 7342 ISAM FTTU TPSDA supports a QoS model to ensure that:
bandwidth is available on a network interface to support requested services

per-subscriber bandwidth controls on HS1 meet service level agreements for a
subscriber
there is minimum delay, jitter, and packet loss for critically sensitive traffic, such
as voice and video

22-11
Configuring QoS on the 7342 ISAM FTTU access network
The QoS model on the 7342 ISAM FTTU access network is implemented by
creating different types of QoS profiles and assigning them to network elements.
A profile has settings that are applicable to individual network elements. The profile
can be used by more than one network element at the same time. The types of QoS
profiles are:
p-bit to CoSto map p-bits to classes of service for upstream traffic at the NT
p-bit to queue mappingsto implement class-based queuing for upstream and
downstream traffic
policer profilesto enforce predetermined limits on upstream and downstream
subscriber traffic
traffic schedulersto prioritize and to size downstream queues to control delay,
jitter, and packet loss
downstream schedulerto limit the rate of traffic sent to an ONT to avoid packet
loss
QoS marker and session profileto convey upstream marking settings to the
ONT and downstream marking settings to the P-OLT
DSCP to p-bit mappingto priority mark upstream untagged frames from a
trusted source
bandwidth profilesto specify bandwidth requirements for a provisioned service
to meet service level agreements
priority queue profilesto assign relative weights to queues and to implement
class-based queuing for upstream traffic at the ONT
Figure 22-8 shows the profiles and the network elements of the 7342 ISAM FTTU
access network that use them.
Figure 22-8 Assignment of profiles to network elements
P-OLT
NT A
BSA
Subscriber Port
VLAN ID 10 1
Multicast
VLAN ID 40 Port
2
Multicast
VLAN ID 41
LT B
IGMP
proxy
IGMP half
proxy
SP/
WRR
SP/
WRR
A NT:
Per service and per-port egress rate limiting
Service ingress QoS policy
Self-generated traffic policy
D ONT UNI port:
ONT 1 C
IGMP
snoop
GPON 2
SP
D
Port
1
B LT:
C ONT:
Per-ONT shedding profile
p-bit to queue mapping
downstream rate limiting scheduler
traffic scheduler
C-VLAN to S-VLAN translation profile
E Service, flow, or portal:

bandwidth profile
Per-service downstream rate limiting scheduler
UNI-side to network-side translation profile
19430
22-12

Table 22-3 lists the profiles and their network elements.

Table 22-3 QoS profiles and their network elements
Profile
Network element
Bandwidth profile
Service
Downstream scheduler
ONT
ONT UNI port
NT
LT
ONT(1)
Service
Power shedding profile
ONT
Service
UNI ONT
Traffic policer
Network interface port on the Shub
Traffic scheduler
Network interface port on the SHub

LT interface port on the NT
PON interface port on the LT
NT interface port on the LT
Note
(1)
The p-bit to queue mapping is configured in the downstream scheduler profile.
QoS across the TPSDA
The TPSDA provides the following QoS functions for the BSR and BSA:
call admission for video and VoIP to guarantee delay, jitter, and packet loss
characteristics after the service connection is accepted

per-subscriber bandwidth controls, including shaping and policing functions
content differentiation
distribution of QoS policy and enforcement across the BSA and BSR to
implement meaningful per-subscriber service level controls
sophisticated and granular QoS in the BSA to deliver differentiated IP services
based on the subscriber and the content
In the BSR-to-BSA downstream direction, the BSR performs service distribution

routing based on guarantees that are required to deliver the service and associated
content, rather than on individual subscribers. The BSR only needs to classify
content to a CoS for a BSA to ensure that traffic for each service receives the
appropriate treatment towards the BSA.
The BSR relies on the IP layer classification of traffic from the network to queue
traffic appropriately towards the BSA. Under extreme loading, lower priority data
services and/or HSI traffic are compromised to protect video and voice traffic.
22-13
HSI traffic is classified based on the source network address or the IEEE 802.1p
(p-bit) marking to one of eight CoS, with each CoS associated with a queue. This
classification allows the QoS information to be propagated to downstream or
upstream nodes by network elements. Figure 22-9 shows the downstream QoS
configuration.
Figure 22-9 BSR-to-BSA downstream QoS configuration
5750 SSC
5620 SAM
Per-subscriber rate limited HSI
Per-subscriber QoS policy
Per-service priority/delay/loss
content differentiation in HSI
VoIP VLAN
VoIP
Video
Video VLAN
Gigabit
Ethernet
IP
7750 SR
HSI
Gold
HSI
VLAN
Silver
BSA
Bronze
Trusted IP network ingress
points, with prefferred
content marked in DSCP.
For HSI content differentiation,
queuing for Gold/Silver/Bronze
based on DSCP classification.
Optional overall subscriber rate
limiting on VLAN.
VLAN
per
subscriber
Gigabit
Ethernet
FTTU
access
node
7450 ESS
VoIP and video queued and prioritized
as per VLAN QoS policy.
Per-subscriber queuing and PIR/OR

policing/shaping for HSI.
HSI content differentiation based on

DSCP. Each queue may have individual
CIR/PIR and shaping.
Per-service prioritization for VoIP and

video with VoIP prioritized over video.
802.1p marking for prioritization
in the access and home.
Optional overall subscriber rate limiting

on VLAN (HQoS).
19455
In the BSA-to-BSR upstream direction, traffic levels are substantially lower than
downstream. Class-based queuing is used on the BSA network interface to ensure
that video control traffic is transmitted with a minimal and consistent delay, and that
preferred data/HSI services receive better treatment for upstream/peering service
traffic than the best effort Internet class of service. Therefore, the BSR does not need
to enforce per-subscriber policies. This function is distributed to the BSAs, and the
per-subscriber policies can be implemented on the downstream interfaces facing the
7342 ISAM FTTU access nodes.
The BSA can perform scheduling and queuing functions on a per-service,
per-subscriber basis, in addition to performing wire-speed packet classification and
filtering based on both L2 and L3 interfaces. In addition to per-service rate limiting
for Internet services, service traffic for each subscriber can be rate-limited as an
aggregate using a bundled service policy. These functions allow different subscribers
to receive different service levels independently and simultaneously. Figure 22-10
shows the upstream QoS configurations.
22-14


Figure 22-10 BSA-to-BSR upstream QoS configuration
Access egress
policies
5750 SSC
Access ingress
policies
5620 SAM
Per-subscriber rate-limited HSI
Per-subscriber QoS policy
content differentiation in HSI
7450 ESS
Aggregation
VoIP VLAN
Real-time
HSI
Video VLAN
Gigabit
Ethernet
IP
VLAN
per
subscriber
Gigabit
Ethernet
Gold
7750 SR
HSI
VLAN
Silver
FTTU
access
node
BSA
Bronze
Video/VoIP: policy defines

priority aggregate CIR/PIR.
HSI: QoS policy defines
priority and aggregate
CIR/PIR. Content differentiation
based on ingress classification.
DSCP marked.
Per-subscriber QoS/
content classification
for content differentiation.
VoIP/video: shared
queuing for prioritization
of real-time traffic over
HSI. Upstream video
traffic is negligible.
HSI: Per-subscriber
queuing with PIR/CIR
policing/shaping.
19454
Traffic is monitored for ingress and egress rate as it enters and exits the
7342 ISAM FTTU access node.
In the downstream direction, the 7342 ISAM FTTU access node receives incoming
packets from the BSA, and queues packets based on the value of the received p-bit.
Traffic schedulers regulate the buffering and scheduling of traffic in a strict priority
or weighted round robin fashion. Excess traffic is dropped using the tail drop
algorithm.
Depending on the deployment model, the CPE connected to the 7342 ISAM FTTU
access node can be trusted or not trusted.
In the trusted case, the marking and shaping of the upstream traffic can be handled
by the CPE. The CPE can be trusted to enforce traffic, which is shaped and marked
as specified in the service provider SLA. As a result, the 7342 ISAM FTTU access
node can honor the markings in the forwarding path.
In the untrusted case, the 7342 ISAM FTTU access node marks and shapes upstream
traffic.

22-15
Configure VLANs
VLANs are used to limit the boundaries of a broadcast. A VLAN groups nodes (or
devices) in a single broadcast domain. Only nodes within the same broadcast domain
can receive broadcast frames that originate from any node within the same domain.
Categories of VLANs
Typically, the following categories of VLANS are configured in a triple play

network:
management VLANto establish an IP connection to the switch from a

workstation connected to a port in the VLAN
multicast VLANto carry one more IP multicast streams from one or more IPTV
service providers from the IP/MPLS network to the PON
service or subscriber VLANto carry a service to a subscriber
customer VLANto bundle a number of subscribers in a service VLAN
VLAN across the TPSDA
VLANs are configured between the BSA and the 7342 ISAM FTTU access node,
using the 5620 SAM.
The same VLANs are configured on the 7342 ISAM FTTU. The VLANs are
associated with NT ports and subscriber services, which specifies the route that
traffic follows to reach its final destination.
NT ports include:
a network interface port on the NT (SHub port)

an LT interface port on the NT
Subscriber services, in turn, associate the VLAN with the following ports:
the PON interface port on the LT

the ONT UNI port
Figure 22-11 shows the downstream traffic for VLAN 10. The arrows indicate the
path that it follows as it makes its way:
22-16
from the BSA to the NT

from the GPON to the ONT
from the ONT to the port


Figure 22-11 Downstream traffic for VLAN 10
P-OLT
NT
BSA
VLAN
Port ID 10
1
Port
1
Port
2
LT
IGMP
proxy
SP/
WRR
ONT 1
IGMP
snoop
IGMP half
proxy
VLAN
ID 10
SP/
WRR
VLAN
ID 10
GPON 2
SP
Port
1
VLAN
ID 10
19432
Configure VLAN for DHCP relay

DHCP is a network protocol that allows a host to obtain its IP address and other
network configuration information from a server when the host powers up. The
configuration information includes the following:
IP address that the DHCP server dynamically assigns to the host

subnet mask
default router address
IP address for the media gateway controller (Softswitch or gateway)
IP address of the FTP service where VoIP configuration data is stored
DNS server address for the HSI service
To enable the relay of configuration information from the DHCP server to a host on
a VLAN, the VLAN must be configured for DHCP relay.
Option 82
Typically, all hosts on the same VLAN receive the configuration information. To
limit the broadcast range, the relay Option 82 is used.
Option 82 allows the relay agent function on the LT to append some information to
the DHCP request that identifies where the DHCP request originated. When Option
82 is configured for the VLAN, the configuration information is relayed only on the
circuit that the host is connected to.
Operation of DHCP across TPSDA
The operation of DHCP is shown in Figure 22-12.

22-17

Figure 22-12 IP address assignment with DHCP
VPLS
BSR
BSA
DHCP
server
7342 ISAM
FTTU
Residential
gateway
Client
device
Access node
inserts Option 82
DHCP
relay
DHCP discover
Option 82 = Subscriber port
DHCP discover
Initial lease
request:
DHCP
relay
DHCP
relay
DHCP
relay
DHCP offer
DHCP request
Option 82 = Subscriber port
DHCP ack
DHCP
snoop
Confirm offer
or renew lease
DHCP lease table populated

from snooped DHCP Ack
19431
The sequence of events for DHCP is as follows.

1
During boot-up, the host sends a DHCP discover message to get an IP address
from the DHCP server. The discover message contains the destination MAC
address, the source MAC address, and the MAC address of the host device.
If Option 82 is configured, the relay agent function on the LT card adds the relay
option field that indicates the physical location, such as shelf, slot, and port, of
the host.
22-18
The DHCP server looks up the host MAC address and optionally Option 82
information in the database. If the host is recognized and authorized to access the
network, an IP address is assigned and a DHCP offer message is returned. The
BSR and the BSA relays the offer message to the host.
The discover message may reach more than one DCHP server, and therefore
more than one offer may be returned. The host chooses one of the offered IP
addresses and confirms the choice in a DHCP request message to the originating
DHCP server.
The DHCP server confirms that the IP address is available, updates the database
to indicate that the server is now in use, and replies with a DHCP ACK message
to the host.

Configure IGMP and multicast

To configure the 7342 ISAM FTTU for IGMP and multicast, the following must be
configured:
IGMP system parameters

multicast sources
maximum bandwidth on a GPON
The 7342 ISAM FTTU delivers IP multicast streams on demand to IPTV video
subscribers using the IP multicast technology. This technology sends a single copy
of an IP multicast stream using a single IP address for the entire group of subscribers.
The routers between the IP/MPLS network and the subscribers route the IP multicast
stream using the multicast group address route.
Figure 22-13 shows the implementation of IGMP across the TPSDA.
Figure 22-13 Implementation of IGMP across the TPSDA
BSR
BSA
P-OLT NT
P-OLT LT
ONT
IGMP
proxy
IGMP
proxy
IGMP
proxy
IGMP
snoop
IGMP joins, leaves,
and reports
IGMP GMQs
and GSQs
Network
equipment
Subscriber
equipment
upstream
downstream
19433
IGMP
Routers and layer 3 switches use IGMP to manage membership for a multicast
session. The 7342 ISAM FTTU access network stores the multicast groups that a
subscriber can join in the multicast source table.
When an host needs to receive an IP multicast stream, the host sends an IGMP
message to join the multicast group.
When an host needs to stop receiving an IP multicast stream, the host sends an
IGMP message to leave the multicast group.

22-19
Bandwidth on GPON
The 7342 ISAM FTTU ensures the availability of bandwidth on a GPON.
When the maximum rate is reached, subsequent join requests are denied.
When an IP multicast stream is no longer active, the stream is removed quickly
from the 7342 ISAM FTTU access network.
IGMP proxy
The IGMP proxy is a facility that sets up and tears down the delivery of IP multicast
streams to hosts by listening to IGMP messages and periodically sending out queries
to discover which IP multicast groups are active or inactive.
The IGMP proxy is located between hosts and an router, and is implemented on the
BSA, the NT, and the LT; see Figure 22-13.
The IGMP proxy acts as a router towards downstream hosts by forwarding the
requested streams.
The IGMP proxy acts as a host towards upstream routers by communicating with
the router on behalf of all downstream hosts.
IGMP snoop
An IGMP snoop function is implemented on the ONT; see Figure 22-13. The IGMP
snoop function silently examines all IGMP messages:
to track the IP multicast streams that a host is receiving

to regulate and monitor the number of active streams on the UNI port
Forwarding tables
Although IGMP message processing is considered a layer 3 function, the actual

multicast forwarding function is performed at layer 2. Across the TPSDA,
forwarding tables track the IP multicast streams that are in use:
BSAtracks the IP multicast streams that are forwarded to the NT

NTtracks the IP multicast streams that are forwarded to the LT
LTtracks the IP multicast streams that are on the GPON
ONTtracks the IP multicast streams that are active on the ONT UNI port
Configure services
The configuration requirements are unique for each service. Table 22-4 lists the
requirements for data, video, and VoIP services.
22-20


Table 22-4 Configuration requirements by service
Service
Configuration by service
Data
Ethernet port or VDSL2 port

HSI service (1)
Video
Ethernet port or VDSL2 port

HSI service (1)
VoIP
VoIP service
POTS line
Note
(1)
High-speed Internet and video can either have their own HSI service, or share the same HSI service.
If the HSI service is shared, only an IGMP signaling channel is required for video.
Table 22-5 lists the pre-service configuration requirements for an HSI service.
Table 22-5 Pre-service configuration requirements for HSI service
Requirement type
Requirement
Notes
Equipment
Rack, shelf, LT slot, PON
ONT
Ethernet or VDSL2 port
Qos and other profiles
VLAN
Upstream bandwidth profile
Applies to upstream side of this

service
Downstream bandwidth profile
Applies to downstream side of

this service

service
service or subscriber VLAN
When the port is configured for

VLAN translation mode, a unique
S-VLAN is required for each
service on the port.
customer VLAN
Only applies when the port is

configured for VLAN translation
mode
Table 22-6 lists the pre-service configuration requirements for a VoIP service.
Table 22-6 Pre-service configuration requirements for a VoIP service
Requirement type
Requirement
Notes
Equipment
Rack, shelf, LT slot, PON
ONT
(1 of 2)

22-21
Requirement type
Requirement
Notes
QoS and other profiles
Upstream bandwidth profile

service
Downstream bandwidth profile
Applies to downstream side of

this service

service
service or subscriber VLAN
When the port is configured for

VLAN translation mode, a unique
S-VLAN is required for each
service on the port.
customer VLAN
Only applies when the port is

configured for VLAN translation
mode
VLAN
(2 of 2)
22.5
Triple play configuration example

The configuration example is illustrated in Figure 22-14 and is based on the
following scenario:
one subscriber has with three services: data, video (IPTV), voice
data and video share the same HSI service
VLAN per subscriber model is used
two IPTV service providers each have their own multicast VLAN
VoIP service is in SIP mode 2
Figure 22-14 Triple play provisioning example
NT
VLAN
(subscriber)
VLAN
(multicast)
VLAN
(multicast)
LT
Ethernet
IPTV 1
RG
ONT
10/100/1000 Base T
10/100
Base T
Computer
IPTV 2
Phone
Voice
Phone
Set-top box
19434
Configuration exclusions
The configuration of the following is excluded from the example in Figure 22-14:
NT card
policer profiles
power shedding profile
22-22


management VLANs
Configuration details
The configuration details are shown in Figure 22-15.
Figure 22-15 Provisioning details
P-bit classification
Ethernet 0
IGMP signaling 6
voice signaling 5
voice bearer 6
Ethernet port 1
ONTNET-1-1-4-2-1-1-1
QoS session profile ID 4
QoS marker profile ID 4
HSI data,
IGMP signaling,
IP multicast stream
Subscriber VLAN 10
172.22.178.123
P-OLT
NT
Subscriber
VLAN ID 10 Port
1
Management
VLAN ID 4003
Multicast
VLAN ID 40
Multicast
VLAN ID 41
Port
2
ONT 1
LT 1-1-4
IGMP
proxy
SP/
WRR
IP multicast groups Multicast VLANs

IPTV provider 1
VLAN 40 for IPTV provider 1
239.192.0.1
172.22.40.11
293.192.0.2
VLAN 41 for IPTV provider 2
IPTV provider 2
172.22.41.11
239.192.1.1
293.192.1.2
IGMP
snoop
IGMP half
proxy
SP/
WRR
HSI service
priority queue
profile ID 1
bandwidth
profile ID 1
IGMP signaling
channel
SP
Port
1
SP
POTS
D
1
GPON 2
Bandwidth on PON
Maximum bandwidth
of 300000 kb/s
HSI-1-1-4-2-1-1-1-1
VOIP-1-1-4-2-1-1
Voice signaling
Voice bearer
POTS port 1
ONTPOTS-1-1-4-2-1-2-1
QoS marker profile ID 4
VoIP service
priority queue
profile ID 2
bandwidth
profile ID 1
Ethernet data, IGMP signaling, Voice signaling, Voice bearer

IP multicast streams
19428
Table 22-7 describes the configuration details where they are organized by function.
Table 22-7 Configuration details
Configuration
Description
Configure equipment
(1 of 7)

22-23
Configuration
Description
P-OLT equipment
ACU card on rack 1, shelf 1 with the following characteristics:
aid ID ACU-1-1
equipment type of AACU-C
power up
in service
LT card on rack 1, shelf, 1, slot 4 with the following characteristics:
aid ID LT-1-1-4
equipment type of GLT2-A
power up
in service
GPON 2 on LT card in rack 1, shelf 1, slot 4 with the following

characteristics:
ONT equipment
aid ID PON-1-1-4-2
FEC enabled
in service
ONT 1 on GPON 2 on LT card in rack 1, shelf 1, slot 4 with the

following characteristics:
aid ID ONT-1-1-4-2-1
battery backup NO
accumulation interval of 1000 frames
ONT description 1 and 2 of null
provisioned version number of *
serial number of ALCL00001824
SLID of wildcard (not used)
planned software version of 3FE50645AAAA07
FEC disabled
in service
Ethernet service card 1 on ONT 1 of GPON 2 of LT card in rack 1,

shelf 1, slot 4 with the following characteristics:
aid ID ONTCARD-1-1-4-2-1-1
type of 10/100 Base-T
in service
POTS service card 2 on ONT 1 of GPON 2 of LT card in rack 1, shelf 1,

slot 2 with the following characteristics:
aid ID ONTCARD-1-1-4-2-1-2
type of POTS
in service
Configure QoS
(2 of 7)
22-24

Configuration
Description
Traffic scheduler
Traffic scheduler for downstream traffic from the NT to the LT

(LT interface port 1) with the following characteristics:
profile ID 1
profile name LT_port_1
size of 8832 bytes for queues 0, 1, 2, and 3
size of 128 bytes for queues 4, 5, and 6
weight of 1 and 2 for queues 0 and 1 respectively
weight of 0 for queues 2, 3, 4, 5, and 6 (strict priority)
dynamic size of 26880 bytes for buffer
Traffic scheduler for upstream traffic from the NT to the network

(network interface port) 1 with the following characteristics:
profile ID 2
profile name SHub_port_1
size of 8832 bytes for queues 0, 1, 2, and 3
size of 128 bytes for queues 4, 5, and 6
weight of 1 and 2 for queues 0 and 1 respectively
weight of 0 for queues 2, 3, 4, 5, and 6 (strict priority)
dynamic size of 26880 bytes for buffer
Traffic scheduler for downstream traffic from the LT to the PON

(PON interface port 1) for with the following characteristics:
profile ID 3
profile name LT-4-2
size of 11648 for queues 0, 1, 2, 3, and 4
size of 0 for queues 5, 6, and 7(unused)
weight of 0 for queues 0, 1, and 2 (strict priority)
weight of 2 for queues 3
weight of 1 for queue 4
weight of 16 for queues 5, 6, and 7 (unused)
dynamic size of 58240 for shared buffer
Traffic scheduler for upstream traffic from the LT to the NT

(NT interface port 1) with the following characteristics:
Downstream scheduler
profile
profile ID 4
profile name LTLANX-4
size of 11648 for queues 0, 1, 2, 3, and 4
size of 0 for queues 5, 6, and 7(unused)
weight of 0 for queues 0, 1, and 2 (strict priority)
weight of 2 for queues 3
weight of 1 for queue 4
weight of 16 for queues 5, 6, and 7 (unused)
dynamic size of 58240 for shared buffer
Downstream scheduler to be assigned to the ONT with the following

characteristics:
profile ID 2
weight of 0 for queues 1 to 4 (strict priority)
weight of 256 for queues 5, 6, 7, and 8 (unused)
maximum size of 32, 256, 256, 256 for queues 1, 2, 3, and 4
respectively
maximum size of 0 for queues 5, 6, 7. and 8 (unused)
guaranteed size of 8 for queues 1, 2, 3, and 4
guaranteed size of 0 for queues 5, 6, 7, and 8
p-bit mapping of 0 to queue 1, 5 to queue 2, 6 and 7 to queue 3
(3 of 7)

22-25
Configuration
Description
Bandwidth profile
Bandwidth profile to be assigned to all services for both upstream

and downstream traffic with the following characteristics:
profile ID 1
profile name 2M_CIR_10M_EIR
CIR of 2000 kb/s
EIR of 10000 kb/s
delay tolerance of 80 (default)
Priority queue profile for HSI service that applies to both data
(p-bit 0) and IGMP (p-bit 6 and 7) with the following characteristics:
profile ID 1
weight 50 for queue 1
weight 256 (unused) for all others
p-bit 0 assigned to queue 2
p-bits 2 to 5 assigned to no queues
p-bits 6 and 7 assigned to queue 1
Control traffic, which has the p-bits of 6 or 7, is mapped to the

higher priority queue. Control traffic includes IGMP.
Priority queue profile for VoIP service where voice signaling traffic
has p-bit 5 and voice bearer traffic has p-bit 6 with the following
characteristics:
QoS marker profile
QoS marker profile for Ethernet port with the following

characteristics:
QoS session profile
profile ID 2
weight 256 (unused) for all others
p-bit 0 to 4 is assigned to no queues
p-bit 5 assigned to queue 2
p-bits 6 and 7 assigned to queue 1
profile ID 4
profile name marker_HSI_profile
marking type VLAN pass-through
Ethernet priority 0
downstream tagging behavior of transmit traffic without a tag
QoS session ID 4 mapped to QoS marker profile 4
Configure VLANs
Subscriber VLAN
VLAN ID 10 with the following characteristics:
on network interface port 1

on LT interface port shelf 1, rack 1, slot 4
mode of residential bridge
IP address of 172.22.178.123
prefix length of 24
unstacked
(4 of 7)
22-26

Configuration
Multicast VLAN
Description

on LT interface port shelf 1, rack 1, and slot 4
name of multicast_1
IP address of 172.22.40.11
prefix length of 24
unstacked

on LT interface port shelf 1, rack 1, and slot 4
name of multicast_2
prefix length of 24
unstacked
Configure DHCP relay for subscriber VLAN 10

DHCP relay
DHCP relay for VLAN 10 with the following characteristics:
DHCP server ID 2
server IP address 143.209.14.50
server name vrf2_DHCP
Configure IGMP
IGMP system parameters
System defaults with mode of half proxy
IP multicast source
IP multicast group 239.192.0.1 from IPTV service provider 1 with the

peak rate of 2500 kb/s

sustained rate of 2500 kb/s
multicast VLAN ID 40





Maximum multicast
bandwidth on PON

Maximum multicast bandwidth on PON with the following

characteristics:
aid ID PON-1-1-4-2
maximum bandwidth of 300000 kb/s
Configure services
(5 of 7)

22-27
Configuration
Description
Ethernet port
Ethernet port 1 on Ethernet interface card in slot 1 on ONT 1 of

GPON 2 of LT card in rack 1, shelf 1, slot 4 with the following
characteristics:
HSI service
HSI service 1 on UNI port 1 of UNI interface card 1 on ONT 1 of GPON

2 of LT card in rack 1, shelf 1, and slot 4 with the following
characteristics:
aid ID HSI-1-1-4-2-1-1-1-1
priority queue profile id 1
AES encryption enabled
service label subscriber_1_HSI
subscriber VLAN ID 10
in service
IGMP signaling channel for HSI service 1 on UNI port 1 on service

interface card 1 on ONT 1 of PON 2 of LT card in rack 1, shelf 1, and
VoIP service
aid ID ONTENET-1-1-4-2-1-1-1
upstream and downstream bandwidth profile ID 1
auto-detection sensing of AUTO
C-VLAN ID 0
session profile ID 4
maximum number of MAC addresses of 10
power shedding override of false
DSCP to p-bit mapping profile ID 1
in service
aid ID HSI-1-1-4-2-1-1-1-1
maximum bandwidth consumption of 24000 kb/s
number of multicast streams allowed on the port of 10
rate of 16 IGMP messages per second
maximum number of hosts per stream of 4
VoIP service 1 on ONT 1 of GPON 2 of LT card in rack 1, shelf 1, and

aid ID VOIP-1-1-4-2-1-1
upstream and downstream bandwidth profile ID 1
priority queue profile id 2
AES encryption enabled
service label of subscriber_1_VoIP
S-VLAN ID 10
network mask IP address of 0.0.0.0
IP address of default router of 0.0.0.0
IP address of the media gateway controller of 0.0.0.0
IP address of FTP server of 0.0.0.0
DHCP disabled
UDP port of the media gateway controller 2944
DSCP value for outgoing signaling and management packets of
48
VoIP mode of SIP mode 2 (SSSIP2)
planned configuration file of test
client ID of ABCD.*
circuit ID of null
in service
(6 of 7)
22-28

Configuration
Description
POTS lines
POTS port 1 on service interface card in slot 2 on ONT 1 of GPON 2

of LT card in rack 1, shelf 1, slot 4 with the following
characteristics:
aid ID ONTPOTS-1-1-4-2-1-2-1
customer information of provisioning sample
VoIP service ID of 1
termination ID of
DSCP value for outgoing bearer traffic of 46
POTS power of 0
call history enabled
in service
(7 of 7)
Prerequisites
The prerequisites for the example in Figure 22-14 are:
The management VLAN 4093 is configured and associated with network

interface port 1.
The network interface port 1 is up.
Workflow
Following is the workflow for the example in Figure 22-14.

1
Configure the equipment.
Configure the equipment on the P-OLT.

Configure the equipment on the ONT.
2
Configure the QoS profiles.
Configure the VLANs.
Configure the traffic scheduler.

Configure the downstream scheduler profile.
Configure the QoS marker profile.
Configure the QoS session profile.
Configure the priority queue profile.
Configure the upstream bandwidth profile.
Configure the multicast VLANs on the NT.
Specify the IP addresses for multicast VLANs.
Add the multicast VLANs to the static table on the NT.
Configure the subscriber VLAN on the NT.
Specify the IP address for the subscriber VLAN.
Configure the subscriber VLAN for DHCP relay.
Set up virtual routing and forwarding for subscriber VLAN.

Add the subscriber VLAN to static table on the NT with DHCP enabled.

22-29
Configure the IGMP and multicast system.
Set IGMP system parameters.

Configure multicast sources.
Set the maximum multicast bandwidth on GPON 2.
6
Configure the services.
Configure the Ethernet port.

Configure the HSI service.
Configure the IGMP signaling channel.
Configure the VoIP service.
Configure the POTS line.
Verify the provisioning data.
Configuring the equipment

The equipment includes the ACU card, LT card, GPON facility on the LT card,
ONT, and the service interface card.
Configure the equipment on the P-OLT
The equipment on the P-OLT is configured to allow the ONT to be attached to GPON
2 of the LT card in rack 1, shelf 1, and slot 4 on the P-OLT.
The following procedure configures the ACU card, LT card, and GPON facility.
1
Configure the ACU card on rack 1, shelf 1 using the TL1 command ENT-EQPT
with the configuration details in Table 22-7.
Configure the LT card in rack 1, shelf 1, and slot 4 using the TL1 command
ENT-EQPT with the configuration details in Table 22-7.
Configure GPON 2 of the LT card in rack 1, shelf 1, slot 4 using the

TL1 command ED-PON with the configuration details in Table 22-7.
Configure the equipment on the ONT
The equipment on the ONT includes the ONT, the Ethernet service interface card,
and the POTS service interface card.
The following procedure configures the ONT and the service interface cards.
22-30
Configure ONT 1 on GPON 2 of the LT card in rack 1, shelf 1, and slot 4 using
the TL1 command ENT-ONT with the configuration details in Table 22-7.
Configure the Ethernet service card in slot 1 on ONT 1 on GPON 2 of the LT

card in rack 1, shelf 1, and slot 4 using the TL1 command ENT-ONTCARD with
the configuration details in Table 22-7.
Configure the POTS service card in slot 2 on ONT 1 of GPON 2 on the LT card
in rack 1, shelf 1, and slot 4 using the TL1 command ENT-ONTCARD with the
configuration details in Table 22-7.

Configuring QoS profiles for ONT UNI port and HSI service
The following procedure configures the QoS profiles that the ONT UNI port and HSI
service require. Table 22-8 lists the profiles.
Table 22-8 QoS profiles
QoS profile
Associated with
Traffic scheduler
NT
LT
Downstream scheduler profile
ONT
QoS marker profile
ONT UNI port
QoS session profile

HSI service
Bandwidth profile
Configure the traffic scheduler for downstream traffic from the NT to the LT
using the CLI command configure qos shub port-profile with the configuration
details in Table 22-7.
Associate the traffic scheduler LT_Port_1 with the LT port in rack 1, shelf 1, and
slot 4 using the CLI command configure qos shub shub-qos-port with the
Configure the traffic scheduler for upstream traffic from the NT to the SHub port
using the CLI command configure qos shub port-profile with the configuration
Associate the traffic scheduler SHub_Port_1 with SHub port 1 using the CLI
command configure qos shub shub-qos-port with the configuration details in
Table 22-7.
Configure the traffic scheduler for downstream traffic from the LT to the GPON
using the TL1 command ENT-PROFILE-SCHED with the configuration details
in Table 22-7.
Associate the traffic scheduler LT-4-2 with GPON interface port for GPON 2 in
slot 4 using the TL1 command SET-SCHED-PORTMAP with the configuration
Configure the traffic scheduler for upstream traffic from the LT to the NT using
the TL1 command ENT-PROFILE-SCHED with the configuration details in
Table 22-7.
Associate traffic scheduler LTLANX-4 to slot 4 NT interface port using the TL1
command SET-SCHED-PORTMAP with the configuration details in
Table 22-7.
Configure a downstream scheduler profile for the ONT using the TL1 command
ENT-PROFILE-SCHEDONT with the configuration details in Table 22-7.
10 Associate the downstream scheduler profile ID 2 with ONT 1 using the TL1
command ED-ONT with the configuration details in Table 22-7.

22-31
11 Configure a QoS marker profile for the HSI service port using the TL1 command
ENT-QOS-MARKPROF with the configuration details in Table 22-7.
12 Configure a QoS session profile using the TL1 command
ENT-QOS-SESSPROF with the configuration details in Table 22-7.
13 Configure a priority queue profile to direct the queueing and scheduling of
upstream HSI service traffic using the TL1 command ENT-PROFILE-PQ with
14 Configure a priority queue profile to direct the queueing and scheduling of
upstream voice service traffic using the TL1 command ENT-PROFILE-PQ with
15 Create an upstream bandwidth profile for the HSI service traffic using the TL1
command ENT-PROFILE-BW with the configuration details in Table 22-7.
Configuring VLANs
The multicast VLANs 40 and 41 carry the IP multicast streams to the GPON. The
subscriber VLAN 10 will be used to carry data, IGMP signaling, voice signaling and
bearer traffic to and from the subscriber.
Configure the multicast VLANS on the NT
The multicast VLANs 40 and 41 are used to carry the IP multicast streams from the
BSA to the NT, from the NT to the LT, and from the LT to the GPON. The following
procedure configures VLANs 40 and 41, and associate them with ports on the SHub
and NT.
1
Configure the multicast VLANs 40 and 41 on the NT using the CL1 command
configure vlan shub with the configuration details in Table 22-7.
Associate the multicast VLANs 40 and 41 with egress network port 2 using the
CLI command configure vlan shub.
Associate the multicast VLANs 40 and 41 with LT interface port on rack 1, shelf
1, and slot 4.
Save the VLAN configuration.
Specify the IP addresses for the multicast VLANs
The following procedure configures VLAN 40 with an IP address of 172.22.40.11

and VLAN 41 with an IP address of 172.22.31.11.
22-32
Set multicast VLAN 40 to an administrative state of down using the CLI

command configure interface shub vland-id.
Specify the IP address of VLAN 40 using the CLI command configure interface
shub ip with the configuration details in Table 22-7.
Set the multicast VLAN 40 to an administrative state of up using the CLI

command configure interface shub vlan-id.



Add the multicast VLANs to the static table on the NT
The following procedure configures the multicast VLANs as unstacked VLANs. A

stacked multicast VLAN is not supported.
1
Configure the multicast VLAN 40 using the TL1 command ENT-PONVLAN

Configure the multicast VLAN 41 using the TL1 command ENT-PONVLAN

Configure the subscriber VLAN on the NT
Configure the subscriber VLAN, and associate the subscriber VLAN with a SHub
and LT interface port as follows:
1
Configure the subscriber VLAN using the CLI command configure vlan shub
Associate the subscriber VLAN 10 with the outgoing network interface port 1
using the CLI command configure vlan shub.
Associate the subscriber VLAN 10 with the LT interface port on rack 1, shelf 1,
and slot 4 using the CLI command configure vlan shub.
Save the subscriber VLAN configuration.
Specify the IP address for the subscriber VLAN
The following procedure configures VLAN 10 with an IP address of 172.22.178.123.

1


Configuring the subscriber VLAN for DHCP relay.

To enable the relay of the IP address and other configuration information from the
DHCP server to the subscribers devices that are on VLAN 10, VLAN 10 must be
configured for DHCP relay.

22-33
Set up routing and forwarding for subscriber VLAN 10
The following procedure sets up virtual routing and forwarding for subscriber
VLAN 10.
1
Configure a VRF using the CLI command configure ip shub; see Table 22-7 for
configuration details.
Set the subscriber VLAN 10 to an administrative state of down using the CLI
command configure interface shub.
Associate subscriber VLAN 10 with VRF 2 using the CLI command configure
interface shub ip.
Set subscriber VLAN 10 to an administrative state of up using the CLI command

configure interface shub.
Enable the SHub with the DHCP relay function using the CLI command
configure dhcp-relay shub.
Specify the IP address for the DSCP server that is associated with VRF 2 using
the CLI command configure dhcp-relay shub server; see Table 22-7 for
configuration details.
Specify the IP address for VRF 2 using the CLI command configure dhcp-relay
shub agent with the configuration details in Table 22-7.
Enable relaying for VRF 2 using the CLI command configure dhcp-relay shub
agent.
Configure routing information for VRF 2 using the CLI command configure ip
shub vrf with the configuration details in Table 22-7.
10 Save the configuration.

Add the subscriber VLAN to the static table on the NT with DHCP enabled
The following procedure adds the subscriber VLAN to the static table on the NT with
DHCP enabled.
Add the subscriber VLAN to the static table on the NT using the TL1 command
ENT-PONVLAN with the configuration details in Table 22-7.
Configuring IGMP and multicast system

Configure the IGMP and multicast system, which includes specifying the IGMP
system parameters, populating the table of multicast sources, and setting the
bandwidth threshold value for a PON.
Set IGMP system parameters
The IGMP proxy facility on the LT is always active. You can modify the IGMP
system default values for your multicast environment using the TL1 command
SET-PONIGMPSYS. The following procedure sets the IGMP system parameters.
1
22-34
Modify the system default values, as required, using the TL1 command
SET-PONIGMPSYS

To snoop PPPoE encapsulated IGMP, set the value of mode to half proxy mode
using the TL1 command SET-PONIGMPSYS.
Activate half proxy mode on the LT card in rack 1, shelf 1, and slot 4 using the
TL1 command INIT-SYSwith an initialization mode of 2 (no self-test).
Configure multicast sources
Each multicast source represents a multicast group that a subscriber can join to
receive the associated IP multicast stream. The multicast source is uniquely
identified in the system by an IP multicast address. The following procedure
configures multicast sources for IPTV service providers 1 and 2.
1
Create the following two entries in the multicast source table for the IPTV
service provider 1 using the TL1 command ENT-PONMCSRC with the
configuration details in Table 22-7:
239.192.0.1 with a peak rate and sustained rate of 2500 kb/s, and associated with
VLAN ID 40
239.192.0.2 with a peak rate and a sustained rate of 230 kb/s, and associated with
VLAN ID 40
Create the following two entries in the multicast source table for the IPTV
service provider 2 using the TL1 command ENT-PONMCSRC with the
configuration details in Table 22-7:
239.192.1.1 with a peak rate and sustained rate of 2500 kb/s, and associated with
VLAN ID 41
239.192.1.2 with a peak rate and a sustained rate of 230 kb/s, and associated with
VLAN ID 41
Set the maximum multicast bandwidth on GPON 2.
The system tracks the amount of bandwidth consumed on a GPON. When a

subscriber requests an IP multicast stream that is not already on the GPON, the
system adds the bit rate to the current rate in use. If the total exceeds the allowable
bandwidth amount, the request is denied.
Set the maximum multicast bandwidth for GPON 2 using the TL1 command
SET-PONMCBW with the configuration details in Table 22-7.
Configuring services
The following procedure configures the Ethernet port, the HSI service, the IGMP
signaling channel for the video service, the VoIP service, and the POTS line for the
subscriber.
1
Configure Ethernet port 1 on Ethernet service card 1 using the TL1 command
ONT-ONTENET with the configuration details in Table 22-7.
Create an HSI service on ONT 1 of GPON 2 for the subscriber using the TL1
command ENT-SERVICE-HSI with the configuration details in Table 22-7.
Create an IGMP signaling channel for the HSI service using the TL1 command
ENT-PONIGMPCHN with the configuration details in Table 22-7.

22-35
Create a VoIP service on ONT 1 of GPON 2 for the subscriber using the TL1
command ENT-SERVICE-VOIP with the configuration details in Table 22-7.
Configure the POTS line using the TL1 command ENT-ONTPOTS with the
Verifying the configuration data

The following procedure verifies the configuration data.
1
Verify the configuration data for the equipment using the following TL1
commands:
Verify QoS profiles using the following TL1 commands:
RTRV-EQPT for the ACU card and LT card

RTRV-PON for the PON
RTRV-ONT for the ONT
RTRV-ONTCARD for the service cards
RTRV-PROFILE-SCHEDONT for the downstream scheduler profile
RTRV-PROFILE-BW for the bandwidth profile
RTRV-PROFILE-PQ for the priority queue profile
RTRV-QOS-MARKPROF for the QoS marker profile
RTRV-QOS-SESSPROF for the QoS session profile
Verify the configuration data for VLANs using the following TL1 commands:
RTRV-LANXVLAN for VLANs on the SHub

RTRV-LANXVLANPORT for VLAN associations with ports on the NT
RTRV-PONVLAN for VLANs on the NT
4
Verify the status of the IGMP VLAN router ports for VLAN 40 and 41 using the
CLI command show igmp shub vlan-router-port
Verify the configuration data for IGMP and multicast system using the following
TL1 commands:
RTRV-PONIGMPSYS for the IGMP system parameters

RTRV-PONMCSRC for the multicast sources
RTRV-PONMCBW for the reservation of multicast bandwidth on a PON
6
Verify the configuration data for the services using the following TL1
commands:
22-36
RTRV-ONTENET for the Ethernet port

RTRV-SERVICE-HSI for the HSI service
RTRV-PONIGMPCHN for the IGMP signaling channel
RTRV-SERVICE-VOIP for the VOIP service
RTRV-ONTPOTS for the POTS line

23.1 Overview
23-2
23-2
23.3 Structured and unstructured DS1 and E1 services handling for

CES
23-4
23.4 Jitter buffering, congestion handling, and alarms
23.5 CES clocking and synchronization
23-7
23.6 Configuring DS1 and E1 port parameters

23.7 Configuring CES PW services

23-6
23-8
23-10
23-1
23.1
Overview
This chapter provides information about how the 7342 ISAM FTTU performs circuit
emulation services (CES) encapsulation on DS1 and E1 TDM traffic for transport as
Ethernet layer 2 over the GPON using the Metro Ethernet Forum standard MEF-8
payload structure and pseudo-wire (PW) technology.
You can provision CES and the DS1 or E1 ports on the business ONT using a TL1
or an EMS management session with the P-OLT. See the 7342 ISAM FTTU
Operations and Maintenance Procedures Guide using TL1 and CLI or the
appropriate network management operations and maintenance guide for
configuration procedures.
23.2
Network example
The business ONT supports two DS1 and E1 service connections at the subscriber
premises. The following TDM link types are supported:
structured (fractional) DS1 or E1

unstructured DS1 or E1
At the subscriber premises, the business ONT terminates DS1 or E1 links from the
subscriber. The TDM traffic is adapted and packetized using MEF-8 pseudo-wire
technology before being transported across the GPON. MEF-8 is the payload option
that is used. The MEF-8 packets are multiplexed with the Ethernet layer 2 data traffic
at the business ONT GPON port.
When the MEF-8 packets are received at the 7342 ISAM FTTU P-OLT that is
installed at the CO, the P-OLT forwards the packets to the destination PSTN,
typically via a G6 voice gateway that is connected to the IP network.
Figure 23-1 shows the network topology of DS1 or E1 CES encapsulated traffic from
the PSTN traversing the GPON via a voice gateway and 7342 ISAM FTTU P-OLT
on the CO side, and the business ONT at the customer premise. The
7342 ISAM FTTU and business ONT model can also support CES DS1 and E1
traffic from a 7250 Service Access Switch.
23-2


Figure 23-1 CES DS1 or E1 traffic between the ONT and PSTN over the GPON via the P-OLT
EMS
DS1 or E1
Class 5 PSTN
switch
GE
L2
Ethernet
cloud
GE
GPON
P-OLT
Voice gateway
(G6)
DS1 or E1
Business
ONT
DHCP server
18953
In the downstream direction, DS1 or E1 traffic from the PSTN is sent to the G6 voice
gateway, which performs Ethernet layer 2 encapsulation using the MEF-8 payload
format and sends the traffic out on to the Ethernet network to the 7342 ISAM FTTU
P-OLT. The LT card installed in the 7342 ISAM FTTU P-OLT forwards the packets
to the business ONT over the GPON. At the subscriber premises, the business ONT
de-encapsulates the packets and forwards the DS1 or E1 payload to the DS1 or E1
port, which is terminating the DS1 or E1 lines at the subscriber premises.
Service options
Table 23-1 describes the options supported for voice, data, and video services.
Table 23-1 Voice, data, and video service options
Service
Options
Voice
H.248/Megaco and session initiation protocol (SIP) between the ONT and
voice gateway or softswitch
Real-time transport protocol (RTP), user datagram protocol (UDP), Internet
protocol (IP), Ethernet, and expedited forwarding
Unbundling support using a G6 gateway
Data
Point-to-point (PPP) and dynamic host configuration protocol (DHCP)

802.1X, remote authentication dial-in user service (RADIUS) for DHCP
Residential bridge and virtual local area network (VLAN) cross-connect modes
DHCP relay (Option 82), proxy address resolution protocol (ARP)
Video
Internet protocol over Ethernet (IPoE) and PPP over Ethernet (PPPoE)
Internet group management protocol (IGMP) v2 and v3, proxy and snoop
IPoE, class of service (CoS), assured forwarding
Expedited leave, fault isolation, performance management, cross-VLAN
multicast, Connection admittance control (CAC) on PON, and customer
channel limits

23-3
Table 23-2 describes the CES DS1/E1 features supported on the business ONT. The
business ONT supports the voice, data, and video service options described in
Table 23-1.
Table 23-2 Business ONT features
Item
Specification
GPON interfaces
Two IEEE 802.3 compliant, RJ-45 10/100/1000BASE-T Gigabit

Ethernet ports, half or full duplex, supporting multi-mode and
single-mode fiber.
For configurable modes, see 7342 ISAM FTTU P-OLT and ONT
Operations and Maintenance Procedures.
DS1/E1 WAN interfaces
Two RJ-48C ports configured for 100 DS1, 120 balanced E1,
or 75 unbalanced E1.
DS1/E1 CES over PSN
IETF PWE3 pseudo-wire

MEF-8
DS1 standards
AT&T TR-6421; ITU-T Rec. G.703, G.704

Structured, unstructured, and fractional DS1 support
E1 standards
ITU-T Rec. G.703, G.704, G.706, G.732, G.823

Structured, unstructured, and fractional E1 support
Synchronization
CES DS1/E1
Upstream: A 16.384 MHz local oscillator or a derived clock from

the GPON that is provided by the P-OLT (1).
Downstream: A 16.384 MHz adaptive clock received from the
PWE3 packet stream, and a differential clock recovered from the
PWE3 packet stream.
Gigabit
Ethernet
Management
A Gigabit Ethernet transmit reference clock of 125 MHz as per

IEEE 802.3.
Local DB-9 serial craft port
Remote in-band management using TL1 or an EMS management
session with the P-OLT
SNMP MIB 1 and MIB 2 support
Quality
QoS aware layer 2 switch per VLAN
Loopbacks and diagnostic tests
Local, remote and packet loopbacks

Trace route and PING support
Note
(1)
23.3
The downstream derived clock provided by the P-OLT is tied to the BITS clock and is traceable to
a network timing reference. The derived clock is used for differential clock recovery and for timing
the upstream PWE3 packet streams in the absence of a valid TDM recovery clock.
Structured and unstructured DS1 and E1 services handling

for CES
Structured DS1 or E1 services emulate fractional services where the 1.544 Mb/s
DS1, or 2.048 Mb/s E1, bandwidth is subdivided in to DS0 64 kb/s channels.
Framing is used to group together multiple DS0s when the service is structured or
fractional. Unstructured services treat the full bandwidth of a DS1 or E1 link as
though it were one large channel, ignoring any framing.
23-4

CES encapsulation is a method of carrying TDM traffic in an Ethernet frame so that

there is minimal loss of quality. The 7342 ISAM FTTU performs CES on the TDM
traffic received at the ONT DS1 or E1 port using the MEF-8 payload structure for
transport as Ethernet layer 2 packets over pseudo-wires (PW). The TDM payload
within the MEF-8 packet, whether it is structured or unstructured, is treated as a bit
stream. The MEF-8 packets are multiplexed along with other Ethernet layer 2 data
packets at the ONT before being transported across the GPON.
Structured DS1/E1
Structured emulation takes the DS0 timeslots that are in a TDM frame and places
them in sequence into the MEF-8 payload structure of the packet. The existing
framing structure, such as the F bit for DS1, is removed.
Figure 23-2 shows how the CES interworking function (IWF) of the business ONT
converts structured TDM frames into MEF-8 packets.
Figure 23-2 Structured TDM frames encapsulated into CES MEF-8 packets
Packet 2
Packet 1
Frame 1
Frame 2
DS0 Timeslot 1 DS0 Timeslot 1

DS0 Timeslot N DS0 Timeslot N
Frame M
DS0 Timeslot 1
DS0 Timeslot 2
DS0 Timeslot 3
Packet L

DS0 Timeslot 1
DS0 Timeslot 2

DS0 Timeslot N
DS0 Timeslot 1
DS0 Timeslot N
DS0 Timeslot 1
DS0 Timeslot N
IWF
Frame 1
in Packet L
Frame 2
in Packet L
DS0 Timeslot N
Incoming TDM Frames
Frame M
in Packet L
Outgoing Packets
18954
Unstructured DS1/E1
Unstructured emulation, which is also called structure-agnostic transport, disregards
any TDM framing structure and treats the TDM data as a stream of consecutive
octets. The number of octets that comprise each MEF-8 payload is independent of
the number of timeslots in each TDM frame. As such, any alignment of these octets
with the underlying timeslots is coincidental and is not guaranteed. The payload size
is typically chosen to make a packet formation time of approximately 1 msec. For a
DS1 circuit, this payload size is 192 octets, where an octet is an eight bit byte. For
E1, the payload size is 256 octets.
Figure 23-3 shows how the CES interworking function (IWF) converts unstructured
TDM octets in to CES MEF-8 packets.

23-5

Figure 23-3 Unstructured TDM traffic encapsulated into CES MEF-8 packets
Octet 1
Octet 2
Octet N
Incoming TDM Octets
IWF
Packet 1
Packet 2
Packet L
Octet 1
Octet 2
Octet 1
Octet 2
Octet 1
Octet 2
Octet N
Octet N
Octet N
Outgoing Packets
18955
Payload size
In unstructured mode, the payload size is fixed at eight DS0 frames per MEF-8
packet. For DS1, the payload length is fixed at 192 bytes per frame. For E1, the
payload length is fixed at 256 bytes per frame. In structured mode, the payload length
is determined from the encapsulation delay setting, see section 23.7.
Note The payload length for each DS0 frame in a MEF-8 packet is
0.125 ms.
23.4
Jitter buffering, congestion handling, and alarms

Jitter occurs when packets arriving from the network experience delays caused by
network congestion, packet routing, or timing drifts. A jitter buffer is used to manage
jitter. You configure the jitter buffer for the business ONT CES PW service using a
TL1 management session with the P-OLT.
The jitter buffer is configured in the CES maintenance profile and is set in frame
units, where one frame unit equals 0.125 ms. Calculate the maximum jitter buffer
size to use as follows:
1.5 payload length (in frames) 0.125 ms = maximum jitter buffer (ms)
The minimum value for the jitter buffer is 1 ms. The maximum value is 200 ms. See
and CLI for configuration command descriptions.
Stray packets are discarded by the CE bound IWF. Malformed packets are detected
by a mismatch between the expected packet size, taking the value of the l bit in to
account, and the actual packet size inferred from the PSN and multiplexing layers.
The 7342 ISAM FTTU monitors the TDM streams for alarm conditions. An alarm is
raised in the system when an alarm condition persists for 2.5 seconds. The alarm is
cleared after the alarm condition is no longer detected for a period of 10 s. The
following CES pseudo wire (PW) alarms can be raised:
23-6
PWE Link Loss

PWE LOSSREORDER
PWE Malformed packets
PWE Late Frames
PWE Jitter Buffer Over-run

PWE Jitter Buffer Under-run
The following CES port alarms are raised in the system:
23.5
CES Loss Of Signal (LOS)

CES AIS Received
CES Loss Of Frame (LOF)
CES RAI Received
CES clocking and synchronization

The same clocking reference at both ends of the DS1 or E1 link is required to meet
the wander requirements of TDM traffic.
The business ONT can use one of two clocking sources for CES: a derived GPON
clock at 16.384 MHz or a 6.384 MHz local oscillator. When the system clock for
CES is derived from the GPON, the upstream P-OLT locks to the BIT clock and
supplies the ONT with an Ethernet clock that is traceable to a network timing
reference. The supplied Ethernet clock is used for differential clock recovery and for
timing the upstream pseudo-wire MEF-8 packet streams in the absence of a valid
TDM recovery clock. The local oscillator is only used if adaptive mode is selected.
The downstream TDM streams may be timed from one of two clocking sources: a
16.384 MHz adaptive clock received from the MEF-8 packet stream or a differential
clock recovered from the MEF-8 packet stream via the GPON. When the clock is
received from the GPON, you must configure the GPON to send RTP packets.
In adaptive timing, a local, free-running 25 MHz clock is used. The generated bit rate
is determined by the long-term average data rate. The DS1/E1 equipment that is
attached must be loop timed. In differential timing, a 16.384 MHz reference clock is
synchronized to the PON. Both ends of the DS1/E1 CES PW must use the same
reference clock frequency and be synchronized to a common source. RTP is used to
transport the transmit bit rate information. The DS1 or E1 equipment that is attached
to the terminating CES PW devices must be loop timed. In loop timing, the receive
clock rate is used for the transmit clock rate. The DS1/E1 equipment that is attached
must be source timed, not loop timed.
Timestamps within the MEF-8 packets are used for carrying timing information
across the network. Timestamp values are generated in differential format when the
interface is operating in differential timing reference mode. Otherwise, the
timestamp values represent absolute time.
You can add an RTP header to each MEF-8 packet for timing purposes and
determine whether or not to include the 4 byte control word immediately preceding
the RTP header. Configure RTP header parameters using a TL1 or an EMS
management session with the P-OLT. See the 7342 ISAM FTTU Operations and
Maintenance Procedures Guide using TL1 and CLI for configuration command
descriptions.

23-7
23.6
Configuring DS1 and E1 port parameters

You can configure the following business ONT DS1 and E1 port parameters:
framing mode
framing type
line encoding
line length (DS1)
line impedance (E1)
Configure the DS1 or E1 port at the business ONT to be compatible with the
connected TDM link.
Note You must configure both ports on the business ONT for the
same type of service, either DS1 or E1. Do not combine different
TDM services on the same business ONT.
Structured and unstructured framing mode

For each DS1 or E1 port, you can configure the framing mode as either structured or
as unstructured. Structured framing mode uses framing, whereas the unstructured
mode is without any framing. The default framing mode is unstructured. Make sure
that the type of framing used matches the framing mode you have configured for the
port.
Framing type
Framing is used to synchronize and extract individual channels from a structured
DS1 or E1 link. The framing you configure for the DS1 or E1 port at the business
ONT must be consistent with the framing mode that you configured for the port.
If the framing mode for the port is configured as unstructured, then you must
configure the framing type as unframed. When unframed is selected, all incoming
TDM data is treated like a bit stream.
Table 23-3 lists the framing types the business ONT supports. The available framing
types are only applicable if the business ONT DS1 or E1 port is configured as
structured.
Table 23-3 DS1 and E1 framing
Link type
Framing
DS1
superframes
extended superframes
unframed (default)
E1
PCM 30
PCM 31
unframed (default)
23-8

For DS1 links, superframes consist of 12 DS0 64 kb/s timeslots that are combined in
to one superframe. An extended superframe consists of 24 DS0 64 kb/s timeslots
combined in to one extended superframe.
For E1 links using PCM 30 transmission, multiFrame alignment signal (MFAS) and
frame alignment signal (FAS) framing are used. Timeslots 1 through 15 correspond
to channels 1 through 15, and timeslots 17 through 31 correspond to channels 16
through 30. Timeslot 0 of every even frame is reserved for FAS and timeslot 16 is
reserved for MFAS and channel associated signaling (CAS).
For E1 links using PCM 31 transmission, only FAS framing is used. Timeslots 1
through 31 correspond to channels 1 through 31. Timeslot 0 of every even frame is
reserved for FAS.
Line encoding
Table 23-4 lists the line encoding types supported for DS1 and E1 links.
Table 23-4 DS1 and E1 line encoding
Link type
Encoding
DS1
B8ZS
AMI (default)
E1
HDB3
AMI (default)
Binary 8 zero code suppression (B8ZS) prevents too many consecutive zeros from
being transmitted over the DS1 link. If an 8 bit sequence of zeros is detected, they
are replaced with a pre-determined sequence before being transmitted. When that
sequence is detected at the receiving end, it is replaced with 8 bits of all zeros.
Alternate mark inversion (AMI) line encoding is used to accommodate the ones
density requirements of DS1 and E1 lines. One bit out of eight is reserved as a control
bit. As such, AMI operates at 56 Kb/s rather than the full 64 kb/s for each DS0.
High-density bipolar-3 zeros (HDB3) is based on AMI and is similar to B8ZS. When
a sequence of four zeros in a row is detected, a substituted value is inserted that is
determined by the number of occurrences since the previous sequence was detected.
Line length and line impedance

The business ONT supports DS1, DSX-1, and E1 connections. Table 23-5 lists the
line lengths that are supported for DS1 and DSX-1 connections.

23-9

Table 23-5 Line lengths supported for DS1 and DSX-1
Link type
Line length
DS1
7.5 dB
15 dB
22.5 dB
DSX-1
0-133 ft (default)
133-266 ft
266-399 ft
399-533 ft
533-655 ft
For E1 links, you can set the impedance for either 75 or 120 .
Note An RJ-48C connector at the business ONT is used for DS1
and E1 connections. You may require a cable adapter to connect your
TDM line to the business ONT. Adapters are not supplied.
23.7
Configuring CES PW services

For each DS1 or E1 port you configure at the business ONT, you must create a CES
pseudo-wire (PW) service. Table 23-6 lists the CES PW service parameters to
configure when you create the service. Make sure that the CES pseudo-wire service
settings made here match those of the G6 voice gateway or other remote end device.
TL1 and CLI for configuration command descriptions.
Table 23-6 CES PW parameters
Item
Parameters
AES encryption
Enabled
Disabled (default)
Label to identify the CES PW service
Up to 20 alphanumeric characters
S-VLAN to associate with the CES PW service
S-VLAN ID value of 2 to 4093
Source VLAN
(1)
to associate with the CES PW service
VLAN ID value of 0 or 2 to 4093

Default is 0
Signaling mode
CAS
(2)
No signaling (default)
(3)
Timeslot mapping (structured mode only) to determine the

number of DS0 timeslots to transport.
4 byte octet
Payload size (unstructured mode only)
192 bytes (DS1)
string, hexadecimal
256 bytes (E1)

Encapsulation delay for each 0.125 ms frame in the MEF-8
packet (structured mode only)
1 ms, 2ms, 3 ms, 4 ms, or 8 ms
(1 of 2)
23-10

Item
Parameters
CES PW service timing mode
(4)
Network
Differential
Adaptive (default)
Loop
Transmit MEF-8 ECID value
8 byte octet string, hexadecimal

Default is all zeros
Expected MEF-8 ECID value
8 byte octet string, hexadecimal

Destination MAC address of the business ONT
Hexadecimal value
RTP header
Enabled
Disabled (default)
(2 of 2)
Notes
(1)
All services on a user-to-network interface (UNI) must have the same setting for this parameter
when in VLAN translation mode.
(2)
Channel associated signaling (CAS) is carried in a separate signaling channel.
(3)
For DS1, the fourth octet must be set to 00 (hexadecimal).
(4)
The timing mode must be the same for all CES PW services configured on the business ONT.
In addition to the parameters listed in Table 23-6, the following profiles are
referenced when you create a CES PW service:
upstream and downstream bandwidth profiles

a priority queue profile
a CES maintenance profile
Note Before creating the CES PW service, you must have
provisioned the business ONT and configured all referenced profiles.

23-11
23-12

24.1 Overview
24-2
24-2

24-1
24.1
Overview
This chapter provides information about how the 7342 ISAM FTTU interacts with
the micro span component of Litespan circuit emulation service solution.
micro span is a product used to provide wideband services over an Ethernet link.
These service are carried across the Ethernet network. The network aggregates the
traffic, both Ethernet and PON. There are two elements in the solution:
The MS-C configured in a Litespan slot in the central office

the MS-R remote terminal, connected to an ONT at the subscriber site
To confine the traffic between the central office and the remote terminal, a VLAN is
used. The transport network between the MS-C and the MS-R uses Ethernet
switching based on the VLAN ID and the MAC addresses of the devices. See the
7342 ISAM FTTU ONT Product Information Manual CES interfaces chapter for
more information.
24.2
Network example
Figure 24-1 shows a micro span solution using a 7342 ISAM FTTU to transport CES
traffic across an Ethernet network.
24-2


Figure 24-1 Network example of micro span collocated with 7342 ISAM FTTU
Central Office
Litespan-2000/2012
Switched TDM
Special Services
GR-57, GR-303
Class 5
DS1
D4,
DACS
MS-C
DS1,
DC3,
OC-x
Ethernet
ONT
Ethernet
7450 ESS
7342 ISAM
FTTU
Ethernet
MS-R
Central Office B
Data Video
POTS/VoIP
PON
ALARM, DDS
COIN, ISDN
DS1
NMS Management for

Litespan and
7342 ISAM FTTU and ONTs
18933
In order to ensure the CES traffic is transmitted to and from the MS-C and MS-R, a
CES VLAN must be created that confines the traffic as it traverses the network. A
management VLAN is also used for communication between the MS-C and the
5526 AMS. Figure 24-2 shows a sample VLAN configuration.

24-3

Figure 24-2 CES VLAN example using micro span, 7342 ISAM FTTU, and ONTs
Litespan-2000/2012
VLAN 20
MS-C
VLAN 10
W
T
MS-C
7450 ESS
L
T
ONT
7342 ISAM FTTU
Pre-provisioned with port-based

VLAN residential bridge for
each MC-C
VLAN ID
MS-R
MS-Rs added
to VLAN 10
18935
High-level workflow
The following is a high-level description of the workflow required to create a CES
network configuration that includes the 7342 ISAM FTTU and ONTs.
24-4
Provision and configure the MS-C and MS-R according to the appropriate
Litespan user documentation. The default management VLAN ID is 4093.
Connect an Ethernet cable from the ONT to the MS-R. The traffic is then
segregated. See the appropriate Litespan user documentation.
When using ONTs without Ethernet physical PLL, the network timing settings
on both ends of the CES should be set to adaptive.
Ensure the P-OLT and the ONT is configured to carry pbits for priority traffic
tagging. See the 7342 ISAM FTTU Operations and Maintenance Procedures
Guide using TL1 and CLI or the 5526 AMS Operations and Maintenance guide
for the 7342 ISAM FTTU.
Configure the ONT to support transparent bridging. See the 7342 ISAM FTTU
Operations and Maintenance Procedures Guide using TL1 and CLI or the
5526 AMS Operations and Maintenance guide for the 7342 ISAM FTTU.
Configure a CES VLAN across the Ethernet network for the micro span traffic;
for example, on the 7342 ISAM FTTU and the 7450 ESS. See the appropriate
equipment user documentation for VLAN configuration information.
When the CES VLAN is configured, the MS-C and MS-R create a CES
automatically.

25 Ethernet services for business and

residential applications
25.1 Overview
25-2
25.2 Metro Ethernet services infrastructure

25.3 Ethernet virtual connection
25.4 EVC models
25-11
25.5 Constraints
25-17

25-4
25-6
25-1
25.1
Overview
This chapter provides high-level information about the implementation of Ethernet
services for business and residential applications in the 7342 ISAM FTTU.
Table 25-1 describes the functionality that is supported by the Ethernet services, and
optionally by traditional services such as standard HSI, VoIP, CES, and VDLS2. See
and CLI for configuration information.
Table 25-1 Functionality supported by Ethernet services
Functionality
Description
Ethernet
services
Single-tagged frames in a stacked VLAN
This functionality applies to internal EVCs

with all-to-one bundling; see Internal EVC
models for more information.
Transparent pass-through of untagged

frames from the CPE
Transparent pass-through of double-tagged

frames across the 7342 ISAM FTTU access
network
Traditional
services
To implement, the ONT UNI must be

configured with the default value VLAN ID of
4095, and the S-VLAN configured in stacked
mode with single-tagged frames enabled.
This functionality supports wholesaling
services on the PON, and mixed business
services such as point-to-point and xDSL.
This functionality applies to external EVCs;

see External EVC models for more
information.
VLAN pass-through mode at the LT and
flexible mode at the ONT allow both
single-tagged and double-tagged frames to
pass through simultaneously from the
network to the CPE and from the CPE to the
network. See Chapter 18 on VLANs for more
information.
GEM port per service
The External EVC with T-CONT per CoS model

supports multiple services for a single
subscriber, with a dedicated GEM port for
each service. In this model, traffic is directed
to a GEM port based on VLAN ID and p-bit.
Setting of p-bit in the outer S-VLAN tag to

a defined value while retaining the
subscriber p-bit
This functionality supports bundling of a

number of C-VLANS in a single S-VLAN for a
service provider.
You can specify the p-bit marking mode for a

stacked S-VLAN on the PON; see Chapter
Chapter 18 on VLANs for more information.
Translation of the customer p-bit on the

UNI side to its equivalent customer p-bit on
the network side at the ONT
You can apply a Uni-side to network-side

p-bit translation profile to a flow; see
Chapter 15 on QoS and Chapter 18 on VLANs
Translation of the customer VLAN on the

UNI-side to its equivalent customer VLAN
on the network side at the ONT
You can map the UNI-side C-VLAN to the

network-side C-VLAN for a flow or service;
see Chapter 18 on VLANs for more
information.
Mapping of business traffic at the LT to the

CoS in the aggregation network, while
retaining the subscriber p-bit
(1 of 2)
25-2

Functionality
Description
Ethernet
services
Multiple cross-connect VLANs on the same

ONT UNI
This functionality applies to external EVCs;

see External EVC models for more
information.
T-CONT sharing across multiple ONT UNIs

on the same ONT for a single service
This functionality obtains maximum

subscriber scalability on the PON, and limits
MAC learning at the LT.
Traditional
services
The T-CONT per service model allows

multiple subscribers of the same service to
share the same T-CONT; see Chapter 15
on QoS for more information. You can disable
MAC learning at the LT for S-VLANs that are
used in this scenario.
T-CONT sharing across multiple services on
the same ONT UNI
The T-CONT per EVC model allows multiple

services for a single subscriber to share the
same T-CONT; see Chapter 15 on QoS for
more information.
T-CONT sharing across multiple services

across multiple ONT UNIs on the same ONT
This functionality identifies different CoSs

between the P-OLT and the ONT in
cross-connect mode.
The T-CONT per CoS model allows multiple

services for different subscribers to share the
same T-CONT; see Chapter 15 on QoS for
more information.
Upstream segregation of single and
double-tagged frames to GEM ports based
on the VLAN ID and p-bit in their outer tag
A flow may be defined by any combination of

VLAN ID, p-bits, and number of tags.
The T-CONT per EVC model supports the
segregation of traffic into GEM ports by VLAN
ID, p-bit, and number of tags; see Chapter 15
on QoS for more information.
GEM port sharing across an UNI
Multiple services on the same ONT UNI can

share the same GEM port.
VLAN translation on incoming frame from

CPE
The customer VLAN on the UNI-side can be

swapped for the customer VLAN on the
network-side, to support multiple EVCs on
the same ONT UNI; see Chapter 18 on VLANs
Bundling
Bundling allows two or more C-VLANs on the

same ONT UNI to be associated with a single
EVC (or S-VLAN).
Service-multiplexing can also be used with

bundling, and allows an ONT UNI to support
multiple EVCs (or S-VLANs).
See Internal EVC models for more
information.
All-to-one bundling
All-to-one bundling occurs when every

C-VLAN on the ONT UNI maps to a single EVC
(or S-VLAN).
See Internal EVC models for more

information.
(2 of 2)
These features are subject to constraints. For information about system and hardware
related constraints, see Section 25.5.
TL1 and CLI for business service related procedures.
25-3
25.2
Metro Ethernet services infrastructure

Figure 25-1 shows the model for Metro Ethernet services.
Figure 25-1 Metro Ethernet services model
CPE
UNI
Metro
ethernet
network (MEN)
UNI
CPE
UNI
CPE
20028
A MEN is a computer network that is based on the Ethernet standard and covers a
metropolitan area. MEN is commonly used as a metropolitan access network to
connect subscribers and businesses to a WAN, such as the Internet. Large businesses
can also use Metro Ethernet to connect branch offices to their intranet.
The MEN contains one or more 7342 ISAM FTTUs that connect to a bridging device
such as 7450 Ethernet Service Switch, as shown in Figure 25-2.
25-4


Figure 25-2 Example of MEN
7750 SR
7750 SR
7450 ESS
7450 ESS
MEN
7342 GPON
7342 GPON
CPE
CPE
UNI
UNI
ONT
ONT
20029
The CPE and MEN exchange Ethernet frames across the UNI. A UNI is a standard
Ethernet interface that is the demarcation point between the CPE and the
7342 ISAM FTTU access network. In the 7342 ISAM FTTU, a UNI is equivalent to
an ONT UNI port.
An Ethernet frame is a frame transmitted across the UNI to the network service
provider, or an Ethernet frame transmitted across the UNI to the subscriber. The
Ethernet frame consists of the first bit of the destination MAC address through the
last bit of the frame check sequence. Ethernet frames can be divided into two groups:
data Ethernet frames

L2 control protocol frames
A data Ethernet frame is one of the following:
unicast Ethernet frame, which has a unicast destination MAC address

multicast Ethernet frame, which has a multicast destination MAC address
broadcast Ethernet frame, which has a broadcast destination MAC address

25-5
25.3
Ethernet virtual connection

The connectivity between the UNIs is specified by the Ethernet virtual connection
(EVC). An EVC is a logical association of two or more UNIs, and performs two
functions:
connects two or more subscriber sites to enable the transfer of Ethernet service
frames between them, such as Internet data, business critical data, video, VoIP,
video conferences
prevents the transfer of data between subscriber sites that are not part of the same
EVC. This capability enables an EVC to provide data security and privacy similar
to frame relay or ATM permanent virtual circuit (PCV).
Two rules govern the delivery of Ethernet frames over an EVC:
the service frame should never be delivered back to the originating UNI
the service frame must be delivered with the Ethernet MAC address and frame
content unchanged
Based on these characteristics, an EVC can be used to construct a L2 private line or
virtual private network (VPN).
EVC types
In Metro Ethernet services, there are three types of EVCs:
point-to-point
multipoint-to-multipoint
rooted-multipoint
The EVC types are described in the following sections.
Point-to-point EVC
In a point-to-point EVC, exactly two UNIs must be associated with one another as
shown in Figure 25-2 and in Figure 25-3. A service frame from one UNI in the EVC
must only be delivered to the second UNI in the EVC. This type of EVC operates
similarly to a virtual circuit. It is an essential component of a service type known as
E-line.
25-6


Figure 25-3 Point-to-point EVC
CPE
UNI
20077
Multipoint-to-multipoint EVC
In a multipoint-to-multipoint EVC, two or more UNIs must be associated with one

another, as shown in Figure 25-4. Typically, a broadcast or multicast service frame
from one UNI in the EVC would be replicated in the MEN, and a single copy would
be delivered to each of the other UNIs in the EVC. This EVC creates a service that
behaves like a switched Ethernet environment. It is an essential component of a
service type known as E-LAN.
Figure 25-4 Multipoint-to-multipoint EVC
CPE
UNI
20078
Rooted-multipoint EVC
In a rooted-multipoint EVC, UNIs are designated as either a root or a leaf UNI.

Transmissions from a root UNI may be delivered to one or more of the other root and
leaf UNIs, and transmissions from a leaf UNI are delivered to only one or more of
the root UNIs. No communication can occur between leaf UNIs. Figure 25-5 shows
a rooted-multipoint EVC. This EVC can be used in environments that need a
hub-and-spoke communication arrangement without needing to configure multiple
point-to-point EVCs. It is an essential component of a service type known as E-tree.

25-7

Figure 25-5 Rooted-multipoint EVC
Root
UNI
Leaf UNI
Rooted-Multipoint EVC
20084
Implementation of EVC on the 7342 ISAM FTTU

Individual links of the EVC are implemented on one or more 7342 ISAM FTTUs as
separate S-VLANs. The upstream function to which the 7342 ISAM FTTUs are
connected, such as the 7450 Ethernet Service Switch, bridges the links together
using, for example, VPLS. The upstream configuration determines the EVC type.
In the 7342 ISAM FTTU, a link of the EVC is generally configured in stacked
VLAN mode. However, the outer tag is added either internally or externally
depending on whether the EVC is an internal or external EVC:
An EVC is an internal EVC when the EVC UNI originates on the

7342 ISAM FTTU, and is equivalent to an ONT UNI. In such cases, the S-VLAN
originates inside the 7342 ISAM FTTU, and the 7342 ISAM FTTU adds the
outer tag at the LT.
An EVC is an external EVC when the EVC UNI is not equivalent to an ONT UNI
port, and the S-VLAN originates outside the 7342 ISAM FTTU at the CPE. For
an external EVC, the outer tag is added externally to the 7342 ISAM FTTU so
that the 7342 ISAM FTTU receives and transmits double-tagged frames.
In an EVC. the Ethernet services are configured in a two-level hierarchy: the portal
is the higher-level and the flow is the lower level. The two-level hierarchy supports
T-CONT sharing across multiple services and subscribers, which allows subscriber
scalability on the PON.
An EVC can be a single service that is carried to one or more subscribers, such as in
the case of multicast and broadcast, or an EVC can carry multiple services to a single
subscriber. The EVC is configured as an S-VLAN on the PON.
A portal is the equivalent of a T-CONT on a PON. Multiple EVCs can be aggregated
in a single portal, or an EVC can have a dedicated portal. The portal aggregates the
traffic from one or more flows on the same ONT, and specifies bandwidth
requirements on an aggregate basis.
The flow is the equivalent of a service or C-VLAN on the ONT UNI; each flow is
bound to one portal and one EVC. When bundling is used for an EVC, multiple
C-VLANs can be bundled in a single portal.
Figure 25-6 shows the relationships among the Ethernet service elements.
25-8


Figure 25-6 Ethernet service element relationships
PON
ONT
ONT CARD
ONT UNI
PORTAL
FLOW
FLOW
PORTAL
FLOW
FLOW
20030
Configuration elements
The following configuration elements are needed to configure a link of an EVC and
its Ethernet services on the 7342 ISAM FTTU:
EVC
S-VLAN
optional C-VLAN to S-VLAN p-bit translation profile
portal
optional bandwidth profile
optional per-service downstream rate-limiting scheduler
flow
optional bandwidth profile
optional UNI-side to network-side p-bit translation profile
ONT UNI, such as an Ethernet, VDSL2, or MoCA port
Figure 25-7 shows the configuration of EVC and Ethernet services configuration.

25-9

Figure 25-7 EVC and Ethernet services configuration
EVC
S-VLAN
(C-VLAN to S-VLAN p-bit
translation profile
Portal
(Bandwidth profile)
(Per-service downstream
rate-limiting scheduler)
GEM
S-VLAN
Flow
(Bandwidth profile)
Uni-side to network-side
p-bit translation profile
GEM
Mapper
T-CONT
GEM
Tagging
GEM
Tagging
UNI
Scheduler
GEM
S-VLAN
GEM
ONT UNI
QoS marker and
session profile
DSCP to p-bit
mapping profile
DSRL
GEM
Mapper
Tagging
GEM
20054
Table 25-2 describes each configuration element and the chapter in the
7342 ISAM FTTU Product Information Manual where the configuration element is
described in more detail.
25-10


Table 25-2 EVC and Ethernet service configuration elements
Configuration element
Description
See
EVC
S-VLAN
The S-VLAN is a VLAN on the PON.
Chapter 18 VLANs
C-VLAN to S-VLAN p-bit

translation
The S-VLAN has a C-VLAN to S-VLAN p-bit

translation profile if the LT must translate
customer p-bits to NSP p-bits before
sending frames to the network.
Chapter 15 QoS
Bandwidth profile
The bandwidth profile specifies the

bandwidth requirements for the services in
a portal. The bandwidth is profiled either
for a portal or for the individual flows in a
portal, but not for both.
Per-service downstream
rate-limiting scheduler
If the ONT is configured for downstream

rate-limiting on a per-service basis, a
per-service downstream rate-limiting
scheduler may be specified for the portal;
see Downstream rate limiting to ONT.
Bandwidth profile
The bandwidth profile specifies the

bandwidth requirements of the flow. The
bandwidth is profiled either for the portal
or for the individual flows in a portal, but
not for both.
UNI-side to network-side p-bit

translation profile
A flow can specify a UNI-side to

network-side p-bit translation profile to
translate the customer p-bit on the UNI side
to its equivalent customer p-bit on the
network side.
The priority queue profile defines the

mapping of p-bits to queues, and the weight
of each queue in the upstream. Each
priority queue is a GEM port.
The ONT uses a DSCP to p-bit mapping to

priority-mark untagged IP traffic received
at an ONT UNI port from a trusted source.
The QoS session and marker profiles define

the tagging of traffic at the ONT UNI port.
Portal
Flow
ONT UNI port
25.4
EVC models
The 7342 ISAM FTTU supports four ways to configure a link of an internal EVC,
and two ways to configure a link of an external EVC. The configuration models are
described in the following sections.
TL1 and CLI for more configuration information.

25-11
Internal EVC models

An internal EVC has four configuration models:
bundling and one CoS

bundling and multiple CoSs
all-to-one bundling and one CoS
all-to-one bundling and multiple CoSs
The following definitions apply:
Bundling allows two or more C-VLANs on the same ONT UNI to be associated
with a single EVC (or S-VLAN). With bundling, the provider and subscriber
must agree on the C-VLAN IDs used at the ONT UNI and the mapping between
each C-VLAN ID and a specific S-VLAN.
Service multiplexing can also be used with bundling, and allows an ONT UNI to
support multiple EVCs (or S-VLANs). Service multiplexing can only be used
with bundling.
All-to-one bundling occurs when every C-VLAN on the ONT UNI maps to a
single EVC (or S-VLAN).
A single CoS provides one portal per EVC (or S-VLAN). All traffic in the same
EVC is directed to the same portal.
Multiple CoSs provide two or more portals per EVC (or S-VLAN). Traffic in the
same EVC is directed to one of the portals based on p-bits.
Internal EVC configuration considerations
The four internal EVC configuration models are described in the next sections, and
are based on the following considerations:
An internal EVC with bundling and service multiplexing supports multiple EVCs
per UNI. An internal EVC with all-to one bundling supports a single EVC per
UNI.
For internal EVCs, the LT must add the outer tag in the upstream direction, and
remove the outer tag in the downstream direction. The tagging behavior at the LT
corresponds to the VLAN tagging mode of stacked; see Chapter VLANs for
more information about VLAN tagging modes.
All-to-one bundling requires special consideration. At the subscriber side, the
all-to-one bundling models receive from and send to the CPE a mixture of
untagged, single-tagged, and double-tagged frames. At the network side, the
all-to-one bundling models receive from and send to the network a mixture of
single-tagged, double-tagged, and triple-tagged frames. As a result, the following
configurations are also required to support all-to-one bundling:
Because of hardware limitations in handling triple-tagged frames, the all-to-one
25-12
bundling models must be configured in cross-connect VLAN mode; see

Chapter VLANs for more information about cross-connect VLANs.
To allow a single-tagged frame in a stacked VLAN, special configuration is required
to instruct the LT to allow an untagged frame across the PON in the downstream
direction, and to remove the outer C-VLAN tag before adding the S-VLAN tag in
the upstream direction, so that a singled-tagged frame is sent to the network;
see Configuration constraints for more information.

Internal EVC with bundling and single CoS
This configuration model, as shown in Figure 25-8, enables more than one C-VLAN
to be bundled in a single EVC under one CoS. All service flows in the EVC are
directed to the same portal.
Figure 25-8 Internal EVC with bundling and single CoS
Flow
Portal
GEM
S-VLAN
Tagging
GEM
Mapper
T-CONT
GEM
Tagging
GEM
Scheduler
UNI
GEM
DSPL
Mapper
Tagging
GEM
20032
The EVC is configured as a stacked S-VLAN in C-VLAN learning mode, and is

enabled for forwarding of broadcast and multicast frames. The EVC has a single
portal. For each C-VLAN that is bundled in the EVC, a flow is configured on the
ONT UNI port with a priority queue profile, and is attached to the portal.
Table 25-3 shows the basic steps that are required to configure an internal EVC with
bundling and single CoS. See the 7342 ISAM FTTU Operations and Maintenance
Procedures Guide using TL1 and CLI for more configuration information.
Table 25-3 Configuration for internal EVCs with bundling and single CoS
Network element
EVC
Create a PON S-VLAN with
Portal
Flow
VLAN mode of C-VLAN learning

tagging mode of stacked VLAN mode
forwarding of broadcast and multicast frames
Create one portal.

For each C-VLAN to be bundled in the S-VLAN:
Create a priority queue profile.

Create a flow specifying a priority queue profile, and
associate the flow to a portal.
Internal EVC with bundling and multiple CoSs
This configuration model allows more than one C-VLAN to be bundled in a single
EVC under two or more CoSs. In this model, an EVC has a portal per CoS, and flows
are directed to a portal by p-bit.

25-13
The EVC is configured as a stacked S-VLAN in C-VLAN learning mode, and is

enabled for forwarding of broadcast and multicast frames. For each CoS, a portal is
created.
For each C-VLAN that is bundled in the EVC, a flow for each portal is created on
the UNI port with non-overlapping p-bits in the priority queue profile, and is
associated to the portal.
bundling and multiple CoSs. See the 7342 ISAM FTTU Operations and
Maintenance Procedures Guide using TL1 and CLI for more configuration
information.
Table 25-4 Configuration for internal EVCs with bundling and multiple CoSs
Network element
EVC
Create a PON S-VLAN with:

forwarding of broadcast and multicast frames
Portal
For each CoS:
Flow
Create a portal.
Create a priority queue profile with p-bits unique to the
CoS.
For each C-VLAN to be bundled in the S-VLAN:
Create a flow specifying the priority queue profile, and
associate the flow to the portal.
Internal EVC with all-to-one bundling and single CoS
This configuration model, as shown in Figure 25-9, allows all C-VLANs on the same
ONT UNI to be bundled in a single EVC under one CoS.
Figure 25-9 Internal EVC with all-to-one bundling and single CoS
Portal
Flow
T-CONT
GEM
S-VLAN
GEM
Tagging
Mapper
Scheduler
GEM
Tagging
UNI
GEM
DSPL
20031
The EVC is configured as a stacked S-VLAN in cross-connect mode. The EVC has
a single portal. A single flow, which specifies a default behavior for all C-VLANs,
is created on the ONT UNI, and is attached to the portal.
25-14

all-to-one bundling and single CoS. See the 7342 ISAM FTTU Operations and
information.
Table 25-5 Configuration for internal EVCs with all-to-one bundling and single CoS
Network element
EVC
VLAN mode of cross-connect mode

Portal
Create one portal.
Single flow
Create a single flow, and associate the single flow to the

portal.
Internal EVC with all-to-one bundling and multiple CoSs
This configuration model enables all C-VLANs to be bundled in a single EVC under
two or more CoSs.
The EVC is configured as a stacked S-VLAN in cross-connect mode. The EVC has
one portal for each CoS.
For each portal, a flow is created on the UNI port with a priority queue profile with
non-overlapping p-bits, and is attached to the portal. Each flow defines a default
behavior for all C-VLANs.
all-to-one bundling and multiple CoSs. See the 7342 ISAM FTTU Operations and
information.
Table 25-6 Configuration for internal EVCs with all-to-one bundling and multiple CoSs
Network element
EVC
VLAN mode of cross-connect

Portal
For each CoS:
Flow
Create a portal.
Create a priority queue profile with p-bits unique to the
CoS.
associate the flow to a portal.

25-15
External EVC models

An external EVC provides two configuration models:
T-CONT per EVC

T-CONT per CoS
An external EVC can simultaneously receive single and double-tagged frames from
CPE. The ONT is typically configured to process both, and to drop untagged and
priority-tagged frames.
External EVC with T-CONT per EVC
This configuration model provides a separate T-CONT for each EVC.

An EVC is configured as a cross-connect S-VLAN in VLAN pass-through mode. An
EVC has a single portal. A single flow is created on the ONT UNI with a priority
queue profile, and is attached to the portal.
Table 25-7 shows the basic steps that are required to configure an external EVC with
one T-CONT per EVC. See the 7342 ISAM FTTU Operations and Maintenance
Table 25-7 Configuration for external EVCs with one T-CONT per EVC
Network element
EVC

VLAN tagging mode of VLAN pass-through mode
Portal
Create a single portal, and associate the portal to S-VLAN.
Flow
Create a priority queue profile for the flow.

Create a single flow specifying the priority queue profile, and
associate the single flow to the portal.
External EVC with T-CONT per CoS
This configuration model allows multiple EVCs to share the same portal by CoS.
Flows in the EVCs are grouped together in the same portal by p-bit.
Each EVC is configured as a cross-connect S-VLAN in VLAN pass-through mode.
For each CoS, there is a single portal that the EVCs share. For each EVC within a
CoS, a single flow is created on the ONT UNI with a priority queue profile, and is
attached to the portal.
Table 25-8 shows the basic steps that are required to configure an external EVC with
one T-CONT per CoS. See the 7342 ISAM FTTU Operations and Maintenance
25-16


Table 25-8 Configuration for external EVCs with one T-CONT per COS
Network element
EVC
For each EVC that will share the T-CONT, create a PON S-VLAN
with:
Portal
For each CoS:
Flow
25.5

tagging mode of VLAN pass-through mode
Create a single portal.
Create a priority queue profile with p-bits unique to this
CoS.
For each EVC within this CoS:
attach the flow to the portal.
Constraints
The following sections describe the system, hardware, and configuration constraints
for EVCs and Ethernet services.
System constraints
The following system constraints apply:
An external EVC cannot have an IGMP signaling channel. An IGMP signaling
channel can only be associated with a flow that does not use double-tagged
frames at the UNI.
An external EVC cannot use an ONT UNI that is configured for anti-spoofing.
Anti-spoofing can only be implemented on a port that does not use double-tagged
frames.
An internal and external EVC can only be implemented on an ONT UNI that is
configured in the flexible mode.
The flexible mode does not support per-service anti-spoofing.
The flexible mode does not support Ethertype classification.
Hardware constraints
GLT cards support Ethernet services for business and residential applications as
follows:
The GLT4-A supports all functionality for Ethernet services for business and
residential applications.
The GLT2 does not support EVC models that require the C-VLAN learning
mode. These are EVC models that use bundling and service multiplexing (see
Section 25.4).

25-17
The GLT2-A does not support internal EVCs (see Section 25.4), including the
following functionality:
all-to-one tagging
single-tagged frames in a stacked VLAN
p-bit marking of upstream frames with a p-bit value specified for the S-VLAN
p-bit translation of C-VLAN p-bit to S-VLAN p-bit
The GLT2-A supports only the following functionality:

double-tagged frame support from customers
cross-connect without VLAN translation
mapping of customer p-bits to provider p-bits
control to pass or drop untagged non-BPDU frames
control to pass or drop customer BPDUs
Table 25-9 lists the maximum number of portals that can be configured for a GLT2
or GLT4 card and the overall maximum for the 7342 FTTU system.
Table 25-9 Maximum number of portals per GLT card and system
Description
GLT2
GLT4
Maximum portals
per GLT card
880 (440 * 2)
1760 (440 * 4)
Maximum portals
per system
31680 (1760 * 18)
Table 25-10 lists the ONT types that support Ethernet services implementations.
Table 25-10 Ethernet services support for ONT types
ONT type
Ethernet services support
Standard services support
GSFU (SOCv2.x)
GSFU (SOCv1.x):
Current Generation ONTs (I-24x, I-040,

B-0404-A) (1)
MDU (O-00240V-A, O-0881V-A)

MDU (O-2412x)
MDU (O-2412x)
M300 MDU
Next Generation ONTs (I-x4xG-B)
(1)
Note
(1)
The Current Generation ONTs (I-24x, I-040, B-0404-A) must be enabled for port-to-port communication to support the
flexible mode; in this communication mode, a business service can only be configured on port 1, and the service is
replicated on the other enabled ONT UNI ports.
The Next Generation ONTs (I-x4xG-B) do not have to be in port-to-port communication to support the flexible mode, and
support business services separately on each of their 4 ONT UNI ports.
25-18

The Current Generation ONTs (I-24x, I-040, B-0404-A) do not support the
following:
VLAN translation and VLAN pass-through on traffic that uses the same p-bit
across the same UNI
downstream p-bit translation when the service is configured for VLAN

pass-through
The ONT UNI supports a VLAN tagging operation data table that is populated by an
EVC flow configuration command, based on the number of UNI-side p-bits
(multiplied by two if both single- and double-tagged frames are enabled for the flow
operation). An ONT UNI supports 16 entries and an MDU supports 32 entries.
Configuration constraints
Table 25-11 describes how to configure the 7342 ISAM FTTU to meet the specific
requirements of a particular EVC model.
Table 25-11 EVC configuration constraints
EVC configuration model
Requirement
Configuration
Internal EVC with bundling,

and one or more EVCs per
UNI (service-multiplexing)
Simultaneous pass-through of
singled-tagged, and optionally untagged
and priority-tagged frames from the CPE
in upstream direction
The PON S-VLAN must be configured with:
Simultaneous pass-through of untagged

and single-tagged frames in downstream
direction

forwarding of broadcast and multicast
frames
A service flow is configured for each C-VLAN

that is bundled in the EVC.
The QoS marker profile must be configured in
flexible mode and to:
transmit untagged frames using default

p-bit for the port; the ONT will by default
tag the frame with the default C-VLAN ID
for the port
overwrite priority-tagged frames with the
default C-VLAN ID for the port
The downstream tagging mode in the QoS

marker profile can be transmit to port with or
without a tag.
The default p-bit in the QoS marker profile
can be any value.
(1 of 2)

25-19
EVC configuration model
Requirement
Configuration
Internal EVC with all-to-one

bundling, and a single EVC
per UNI
Simultaneous pass-through of untagged,

priority-tagged, singled-tagged, and
double-tagged frames in upstream
direction
Simultaneous pass-through of untagged,

priority-tagged, singled-tagged, and
double-tagged frames in downstream
direction
VLAN mode of cross-connect mode

enabling of single-tagged frames in a
stacked VLAN
The ONT UNI port must be configured with

the default C-VLAN ID of 4095.
The QoS marker profile for the ONT UNI must
be configured with flexible mode as the
upstream tagging mode, and transmit to port
with a tag as the downstream tagging mode,
and to:
transmit untagged frames using default

p-bit for the port
allow priority-tagged frames to pass
through
The default p-bit in the QoS marker profile

can be any value.
External EVC
singled-tagged and double-tagged frames
from CPE in upstream direction
singled-tagged and double-tagged frames
to CPE

tagging mode of VLAN pass-through mode
The QoS marker profile for the ONT UNI must

be configured with flexible mode as the
upstream tagging mode, and transmit to port
with a tag as the downstream tagging mode,
and to drop untagged and priority-tagged
frames.
(2 of 2)
25-20

Unit data sheets




26.1 Overview
26-2
26.2 Unit data sheet overview
26-2
26.3 Index list of unit data sheets for 7342 ISAM FTTU

26-2
26-1
26.1
Overview
Table 26-1 lists the sections in this chapter that provide overview information about
unit data sheets for the 7342 ISAM FTTU.
Table 26-1 Overview of unit data sheets for the 7342 ISAM FTTU
26.2
Description
Section
Unit data sheet overview
26.2
Index list of the unit data sheets for the 7342 ISAM FTTU
26.3
Unit data sheet overview

Unit data sheets provide detailed information about the major hardware units of the
7342 ISAM FTTU. The unit data sheets supplement the information provided
elsewhere in the documentation.
Unit data sheets typically provide the following types of information:
identification
features and application notes
general description
physical description, including an illustration and dimensions
alarm LEDs
interfaces and connections
power supply
Many of the units used in the 7342 ISAM FTTU are used in more than one Alcatel
product. The unit data sheets in this document describe the units as they are used in
the 7342 ISAM FTTU. For information about the units as they are used in other
products, see the unit data sheets that have been provided as part of the
documentation for the product.
26.3
Index list of unit data sheets for 7342 ISAM FTTU

Table 26-2 lists the unit data sheets according to part description.
Note The shelf is referred to within these manuals by the term
Optical Line Terminal Shelf (OLTS), but ALTS-N or OLTS-M is the
name used for ordering.
26-2


Table 26-2 Alphabetical list of unit data sheets by description
Description
Mnemonic
Part number
Chapter
Alarm control unit
AACU-C
3EC 16687 AC
27
Battery filter adapter card
FILT-A
3EM 17820 AA
39
Battery filter adapter card
FILT-B
3FE 51428 AA
39
3FE 51428 AB
BITS access for optical NT
BITS-B
3FE 51426 AA
34
Fan unit with filter
AFAN-H
3EC 37533 AB
28
Fan unit with filter
AFAN-S
3FE 51461 AA
29
GPON line termination with 2 PONs card 1
GLT2-A
3FE 50385 AA
40
GLT2-B
3FE 51039 AA
40
GLT4-A
3FE 51034 AA, AC, AD variants
41
Ethernet high-capacity network termination

card
EHNT-A
3FE 50479 AA
37
Ethernet high-capacity network termination

card
EHNT-B
3FE 51196 AA
37
Ethernet XAUI based network termination

card
EXNT-A
3FE 51230 AA
38
OLT shelf, version N
ALTS-N
3EC 17542 AB
30
OLT shelf, version M
OLTS-M
3FE 51410 AA
45
OLT rack
3AP 60332 EB
44
3FE 50479 AB
3AP 60432 EB
3AP 60332 CB
3AP 60432 CB
3FE 51459 AA
3FE 51459 AB
Rack for video coupler, Tyco and LGX
1AD 04674 0001
47
Synchronous ATM network combiner,

version D, BITS and LAN access for optical
NT
SANC-D
3EC 17919 AA
46
Top rack unit, version M
ATRU-M
3EC 17422 AA
31
Top rack unit, version N
ATRU-N
3EC 17422 CD
32
Top rack unit, version U
ATRU-U
3FE 51460 AA
33
Top rack unit, version B
GTRU-B
3FE 51460 AB
33
Video coupler subrac, Tyco
VCS
1AD 04675 0001
48
Video coupler WDM tray for 4 PONs, Tyco
VCW4-A
3EM 15711 AA (tray pair)
50
3EM 15711 AB (left tray)

3EM 15711 AC (right tray)
Video coupler WDM with splitters tray for 8
PONs, Tyco
VCS8-A
3EM 15711 AD (tray pair)
49
3EM 15711 AE (left tray)

3EM 15711 AF (right tray)
Video coupler shelf, LGX compatible
VCSL-A
3EM 11047 AA
51
(1 of 2)

26-3
Description
Mnemonic
Part number
Chapter
Video coupler LGX WDM cassette, 2 PONs
VCW2-C
3EM 11046 AC
52
(2 of 2)
26-4

27.1 Identification
27-2
27.2 Features and application notes

27.4 Alarm control function
27.5 Alarm LEDs
27-2
27-2
27-4
27-5
27.6 Interfaces and connections

27.7 Physical description
27-6
27-8

27-1
27.1
Identification
Table 27-1 provides identification information about the AACU-C.
Table 27-1 Identification of ACCU-C
Part number
Mnemonic
Description
CLEI
CPR
ECI/Bar
code
3EC 16687 AB
AACU-C
Alarm control unit,

version C
VAUCABNKAA
W73150
134652
3EC 16687 AC
AACU-C
Alarm control unit,

version C
BVC1AAYFAA
O7OLTJ
154790
27.2
Features and application notes

The AACU-C card provides:
alarm control functions for the P-OLT shelf that support CO alarm system,
27.3
telemetry alarm system, and rack alarms

alarm cut-off (ACO) and LED lamp test button
alarm LEDs
audible alarm signals to the TRU (HTRU-F or AMP)
connection to the TRU (HTRU-F or AMP)
local craft interface
one Ethernet port on the AACU
one Ethernet port on the P-OLT backplane
response to remote inventory request by the NT card
General description
The AACU-C is a card that is installed in each P-OLT shelf. The AACU-C card
provides alarm control functions for the P-OLT shelf. The AACU-C card:
collects up to two rack fan alarms, one TRU fuse alarm, and five miscellaneous
external alarms
reports conditions of locally detected alarms

reports of NT alarm conditions as set by the NT card, including NT loss of signal,
NT failure, and LT failure
handles input and output alarm information

generates alarm status indicators via relay contacts or Opto switches
generates audible and visual telemetry signals
27-2

If any of the P-OLT components experience a fault, the AACU-C generates visual
and audible alarm signals and forwards the signals to the TRU. When the alarms are
generated, the LEDs on the AACU front panel displays the alarms according to the
level of severity, including critical, major, and minor. The AACU also generates
audible alarm signals to telemetry devices.
In addition to the audible alarm indicators and alarm LEDs, the AACU front panel
contains an ACO (audible cut-off) button, a local craft port, and an Ethernet port. The
ACO button can be used to extinguish the audible alarm. If the ACO button is
pressed for longer than 3 s., a lamp test starts. The local craft port is for OAM access.
The Ethernet port is for remote out-of-band OAM access or can also be used as an
Ethernet craft port.
The AACU-C connects to the TRU through a cable that connects the J64 connector
at the backplane of the P-OLT shelf and the J3 connector on the TRU.
The AACU-C responds to request from the NT card about its identification and
operating status for remote inventory. The information provided for remote
inventory includes product identification, manufacturer identification, and inventory
information.
Figure 27-1 shows the front and side views of the AACU.

27-3

Figure 27-1 AACU front and side views
27.4
Alarm control function

The AACU generates alarm signals related to the operation of the P-OLT shelf for:
the CO alarm system

the telemetry alarm system
rack-level alarms
CO alarm system
The AACU supports a local CO alarm interface that provide visual and audible
minor, major, and critical alarms to the CO alarm system.
27-4

The AACU supports six discrete isolated alarm outputs: two for critical, two for
major, and two for minor alarms.
The critical alarm outputs are normally closed (power off) contact mechanical relays
that are held open during normal operation. If there is a loss of power, the relay is
released to notify the CO.
The AACU accepts an external ACO input that resets the audible alarm contact sets
to the non-alarmed state. The visual alarms remain on until the alarms are cleared.
Telemetry alarm system

The AACU provides a discrete telemetry alarm interface that provides visual and
audible minor, major, and critical alarms to the telemetry alarm system. The
telemetry alarm system consists of two contact sets for minor and major alarms and
one contact set for critical alarms.
The critical alarm outputs are normally closed (power off) contact mechanical relays
that are held open during normal operation. If there is a loss of power, the relay is
released to notify the CO.
The AACU accepts an external ACO input that resets the audible alarm contact sets
to the non-alarmed state. The visual alarms remain on until the alarms are cleared.
After activation, the telemetry alarms remain activated for a minimum of 20 s. to
ensure that the telemetry scanner has the time to detect the alarm.
Rack-level alarms
The AACU-C generates the following rack-level alarm inputs:
2 alarm inputs for the state of each fan unit

a fuse alarm input for the fuse alarm from the TRU
up to 5 miscellaneous alarm input
When any of the alarms described above occur, the AACU updates its alarm status
table. The ACCU-C reports the alarm status when polled by the NT.
27.5
Alarm LEDs
By default, the AACU-C generates a critical alarm output to the CO and telemetry
alarm systems when a poll by the NT fails for 12 s., which leads to an NT Poll Failure
event.
The AACU-C front panel has five LEDs. The CRI, MAJ, and MIN LEDs indicate
alarms associated with the P-OLT shelf. The ALM LED indicates the local alarms
associated with the AACU-C card. The ACO LED activates whenever the ACO
switch is pressed. The ACO switch serves two functions: one is to extinguish the
audible alarms and the other is to test the LED lamps. When the switch is pressed for
more than 3 s., the AACU-C lamps are lit until the ACO switch is released.
Table 27-2 describes the alarm LEDs.

27-5

Table 27-2 Alarm LEDs
27.6
LEDs
Description
Color display
CRI
Critical
Red
MAJ
Major
Red
MIN
Minor
Yellow
ALM
Alarm local
Red
ACO
ACO active
Green
Interfaces and connections

The AACU provides the following interfaces:
TRU (HTRU-F or AMP)

alarm input and output
AACU OAM
Ethernet OS port
NT cards
Interface to the TRU

The connection to the TRU transmits alarm signals from the AACU to the TRU. The
connection is accomplished through the telephony connector that is located on the
backplane of the P-OLT shelf. This connector (J64) is linked via the alarm cable to
the alarms connector (J3) on the back of the TRU. Both connectors use the 50-pin
connector. For more information about the pin assignment of the connectors, see
7342 ISAM FTTU Hardware Installation and Maintenance Practices.
Interface for alarm input/output

The AACU has a top connector that connects the AACU with the P-OLT backplane.
The top connector provides an interface for the alarm input and output.
Interface for AACU OAM

The AACU provides one local craft interface on the front panel for OAM access. In
addition, the AACU provides one Ethernet port located on the front panel, and an
Ethernet port connected to the AACU on the P-OLT backplane.
Local craft port
The local craft interface uses a DB-9 connector that provides female pins with a male
shell. It is configured as DCE to communicate with a local DTE craft terminal.
Table 27-3 describes the pin assignments for the DB-9 connector.
27-6


Table 27-3 DB-9 connector pin assignment
Pin
Signal
Direction
Description
DCD
Out
Data carrier detect
RXD
Out
Received data
TXD
In
Transmit data
DTR
In
Data terminal ready
EG
Signal ground (EG)
DSR
Out
Data set ready
RTS
In
Request to send
CTS
Out
Clear to send
RI
In
Ring indicator (used in DTE

configurations only)
Cable connectors
Use a cable to connect the DB-9 craft port on the AACU-C to the craft terminal. For
the craft port, the cable end must be a male 9-pin connector. For the craft terminal,
the cable end can be either a 9-pin or 25-pin connector. For more information about
the pin assignment for the craft cable connectors, see 7342 ISAM FTTU Hardware
Installation and Maintenance Practices.
Interface for Ethernet OS port

The AACU provides a 10/100 BaseT Ethernet interface that connects to the CO
LAN. The interface uses the RJ-45 Ethernet port on the front panel of the AACU.
The Ethernet interface is paralleled via a backplane connection to a second RJ-45
jack mounted on the backplane to support rear access cabling.
Caution The two Ethernet ports must not be used simultaneously.
If you plug Ethernet cables into both front and back RJ45 connectors,
neither interface will work because of interference between the
signals causing continuous errors.
Interface to the NT cards

The AACU has an interface to the NT card for alarm collection and control functions.
Table 27-4 describes the NT interface signal and the associated direction.
Table 27-4 NT interface
Signal
Direction
Description
ACU_TXD
In
Serial receive line from the NT
ACU_RXD
Out
Serial transmit line to the NT
ACU_IRQ
Out
AACU interrupt request to the NT

27-7
27.7
Physical description
Table 27-5 describes the physical specification of the AACU card.
Table 27-5 AACU physical specifications
27-8
Description
Specification
Height
16.53 in. (41.99 cm)
Width
0.77 in. (1.96 cm)
Depth
8.66 in. (22 cm)
Weight
1.5 lb. (0.68 kg)

28.1 Identification
28-2

28.4 Front panel
28.5 Back panel
28-2
28-2
28-3
28-3
28.6 Fan and cable assembly

28.7 Filter assembly
28-4
28-4
28.8 Electrical specifications

28-4
28-4

28-1
28.1
Identification
Table 28-1 provides identification information about AFAN-H.
Table 28-1 Identification of AFAN-H
Part number
Mnemonic
Description
CLEI
CPR
ECI/Bar code
3EC 37533 AA 3EC

37533 AB
AFAN-H
Fan unit with filter. Two

variants: AA does not have a
filter bracket, while AB does.
28.2

The AFAN-H fan unit provides:
forced air cooling through eight wide-range fans integrated with the ALTS-N
shelf
nominal voltages of 48 V dc to 60 V dc
alarm interface board that provides alarm indication to the ATRU and the office
alarm system
alarm (for a failing fan, for example) that closes the relay contacts
replaceable and hot-insertable fans
locking mechanism that prevents the unit from being disconnected from the frame
28.3
when fully extended

power and alarm connections to the backplane using two DB-15 connectors
dust filter
L-10 lifetime at ambient temperatures of 104F (40C): 75000 h
L-10 lifetime at ambient temperatures of 158F (70C): 70000 h
noise level: 57 dBA
temperature range: 14F to 158F (10C to +70C)
flammability according to UL94V-0
General description
The AFAN-H provides forced air cooling to an ALTS-N shelf as well as alarm
generation in case of fan failure. It is protected through circuit breakers in the TRU
or CO power distribution frame. Air is drawn through the AFAN from bottom to top.
Figure 28-1 shows the front, top, and side views of the AFAN-H fan unit.
28-2


Figure 28-1 Front, top, and side views of the AFAN-H fan unit
Airflow
Alarm LED
18402
28.4
Front panel
The front panel has a single alarm LED, which lights in case of fan failure; see
Figure 28-2.
Figure 28-2 AFAN-H front panel
18343
28.5
Back panel
The back panel contains the connectors that plug into the shelf back panel; see
Figure 28-3.
Figure 28-3 AFAN-H back panel
BK
CATHODE (-)
BD
ANODE (*)
LED 1
FAN 1
FAN 1
FAN 3
FAN 4
FAN 5
FAN 6
FAN 7
FAN 8
18344

28-3
28.6
Fan and cable assembly

The cable assembly transfers the alarm signal to the ATRU or any other alarm
collection device and the power connection; see Figure 28-4.
Figure 28-4 Fan and cable assembly
Fan
Pin 1
18178
28.7
Filter assembly
This AFAN-H version is provided with a dust filter. The dust filter has the following
characteristics:
made from nonwoven synthetic material with a minimum dust arrestance of 80%
initial pressure <35 Pa
EN779 Classification E3
dimensions: 0.30 in. x 18.35 in. x 9.49 in. (7.6mm x 466 mm x 241 mm)
filter life depends on the physical surroundings, typical 3 to 6 months (inspection
every 2 months)
complies with UL Class2/UL94 HF-1
slides into a dedicated slot on the shelf
28.8
Electrical specifications
The fan unit has the following electrical specifications:
maximum free airflow: 330 ft3/h (9.3 m3/h) (36 V dc) to 405 ft3/h (11.5 m3/h)
(72 V dc)
air velocity: 1.5 m/s

voltage: 36 V dc to 72 V dc
28.9
Table 28-2 describes the physical specifications of the AFAN-H fan unit.
28-4


Table 28-2 AFAN-H physical specifications
Description
Specifications
3EC 37533 AA
Height
23.62 in. (60 cm)
Width
13.39 in. (34 cm)
Depth
5.71 in. (14.50 cm)
Weight
11.02 lb (5 kg)

28-5
28-6

29.1 Identification
29-2

29.4 Front panel
29-2
29-2
29-3
29.5 Filter assembly
29-3
29.6 Electrical specifications

29-3
29-3

29-1
29.1
Identification
Table 29-1 provides identification information about AFAN-S.
Table 29-1 Identification of AFAN-S
Part number
Mnemonic
Description
CLEI
CPR
ECI/Bar code
3FE 51461 AA
AFAN-S
Fan unit with filter.
BVPQAEFKAA
070MEX
155523
3FE 51462 AA
Rack mount chassis for fan unit
3FE 51527 AA
Replacement air filter
29.2

The AFAN-S fan unit provides:
29.3
forced air cooling through six wide-range fans mounted below the OLTS-M shelf
redundant power feeds, nominal voltage range of -48 V dc to -60 V dc
LED on the unit front panel to indicate status
fan presence detected by the ACU card, alarm generated if fan is not installed
variable speed fan to match airflow to thermal requirements
fan filter replacement without service interruption
General description
The AFAN-S provides forced air cooling to an OLTS-M shelf as well as alarm
generation in case of fan failure. It is protected through circuit breakers in the TRU.
Power must be supplied to the A and B power source at startup (boot time) or the
system will not initialize. This is because a FANALM alarm for fan 1 will be raised
if the fan unit is missing A- or B-side power. An alarm for this reason puts the system
in thermal shutdown mode. This is to ensure proper powering of the equipment to
protect the system from a potential thermal event. Air is drawn through the AFAN
from bottom to top.
The AFAN-S utilizes thermal sensors and a single control board to regulate the
variable speed fans. The fan unit consumes less power and is quieter by running at
low speed in normal CO operating conditions. If the fan exhaust temperature rises,
the controller board will increase the fan speed. If a fan fails, the remaining fans will
increase their speed to compensate for the loss and a fan failure alarm will be raised.
The fan unit is removable for servicing, allowing easy access to the six internal fans.
The fan chassis mounts directly below the OLTS-M shelf and the AFAN-S unit and
filter assembly slide into the chassis.
Figure 29-1 shows the front of the AFAN-S fan unit with the air filter installed.
29-2


Figure 29-1 Front view of the AFAN-S fan unit
AFAN-S
FAN UNIT STATUS
BLINKING
GREEN - INTIALIZING
SOLID
GREEN - ACTIVE
RED
- FAN FAILURE
AMBER - OVER-TEMPERATURE
CAUTION
MOVING PARTS INSIDE OF FAN
19372
29.4
Front panel
The front panel has a single, three element, status LED. Table 29-2 defines the status
LED states.
Table 29-2 Status LED indications
29.5
LED color
LED state
Fan status
Green
Blinking
Initializing
On
Active
Yellow
On
Over temperature
Red
On
Fan failure
Filter assembly
This AFAN-S version is provided with a dust filter. The dust filter has the following
characteristics:
made from nonwoven synthetic material with a minimum dust arrestance of 80%
filter life depends on the physical surroundings, typical 3 to 6 months (inspection
every month)
slides into a dedicated slot on the shelf
replacement without affecting service
29.6
Electrical specifications
The fan unit has the following electrical specifications:
voltage: 36 V dc to 75 V dc
dual input power feed (48 V dc A and B power feeds)
29.7
Table 29-3 describes the physical specifications of the AFAN-S fan unit.

29-3

Table 29-3 AFAN-S physical specifications
29-4
Description
Specifications
Height
3.38 in. (85.85 mm)
Width
17.23 in. (437.64 mm)
Depth
10.88 in. (276.35 mm)
Weight
11.0 lbs. (5.0 kg)

30.1 Identification
30-2

30-2
30.4 Backplane connectors and cables

30.5 Physical location identification
30.6 Power distribution
30-6
30.7 Thermal limitation
30-7
30-2
30-4
30-6
30-7

30-1
30.1
Identification
Table 30-1 provides identification information about ALTS-N.
Table 30-1 Identification of ALTS-N
Part number
Mnemonic
Description
CLEI
CPR
ECI/Bar
code
3EC 17542 AB
ALTS-N
Line termination
shelf, version N
30.2

The ALTS-N shelf provides:
a shelf frame in which the P-OLT components install that is rack mountable in a
UT-9 rack for deployment in a CO or CEV
slots for 2 NT cards (NTA and NTB) and 1 ACU card

slots for up to 16 LT cards; for example, up to 16 GLT2 cards terminating a
maximum of 2048 subscribers per P-OLT shelf
connection for a FILT card with three battery filter caps that mount in the shelf
power input area for CE Mark, EN55022, and EN300386 EMC compliance
connection for a SANC-D backplane adapter
terminals for connecting a 48 V dc or 60 V dc power supply
support for the installation of a fiber routing tray
30.3
General description
The ALTS-N optical line termination (OLT) shelf is the rack mountable frame in
which the cards and other units that comprise the P-OLT are installed. The shelf
mounts in the OLT rack for CO or CEV installations. The OLT rack is a UT-9 rack,
600 mm wide and 2200 mm high, with 25 mm spaced holes for mounting equipment.
See the OLT rack unit data sheet for more information.
Note Due to thermal limitations, you can install a maximum of two
P-OLT shelves plus one TRU unit in a rack, even though three shelves
plus the TRU unit can physically fit in to the same rack.
The ALTS-N shelf has three main areas:
card cage
cable routing and shelf connector area
fan tray
30-2

The ALTS-N shelf supports the following NT and LT cards:
EHNT-A
GLT2-A
GLT2-B
Figure 30-1 shows an ALTS-N shelf populated with P-OLT components.
Figure 30-1 ALTS-N shelf with P-OLT cards and components
Energy Hazard
AACU-C
CRI
MAJ
MIN
ALM
ACO
EHNT
EHNT
ALM PWR ACT
ALM PWR ACT
ALM
ALM PWR ACT
ACT
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
GLT2-A
PWR
PWR
PWR
PWR
PWR
PWR
PWR
PWR
PWR
PWR
PWR
PWR
PWR
PWR
PWR
PWR
ALM
ALM
ALM
ALM
ALM
ALM
ALM
ALM
ALM
ALM
ALM
ALM
ALM
ALM
ALM
ALM
CRAFT
ETHERNET
623.75 mm
247.2 mm
284.5 mm
497.4 mm
515 mm
529.4 mm
18835
The card cage is the large central area of the shelf that accommodates plug-in cards
that are 16.53 in. (42 cm) in height and 8.66 in. (22 cm) in depth. From left to right,
there is 1 ACU slot, 2 NT slots (NTA and NTB), and 16 LT slots. Blank filler plates
must be installed in any empty slots in the card cage area.
The topmost area of the shelf is the cable routing and shelf connector area, which
provides the following:
attachments for the fiber mounting kit

line interface connectors, such as the I/O unit for the GLT2 card that provides an
Ethernet connection between the GLT2 and Ethernet equipment outside the
P-OLT
slot for the optional SANC-D unit
30-3
shelf power connections from the TRU

fan unit power connections from the TRU
TRU and remote craft interface connectors
IQ-bus extension and XDSL line connectors
Note The IQ-bus extension and XDSL line connectors are not used
for the 7342 ISAM FTTU application.
The fan tray area contains the fan unit.

For a detailed description of the fan unit and the plug-in cards, refer to the
corresponding unit data sheets.
30.4
Backplane connectors and cables

The backplane interconnects the cards, the fan unit, the eHCL bus interface, external
interfaces, and other rack equipment. Input power terminals are located on the
externally accessible section of the backplane, which is the topmost section; see
Figure 30-1 and Figure 30-2. The physical location identification jumpers are also
located on the backplane.
Power is distributed to the fan unit and to the active units in the shelf over the
backplane. Cards installed in the card cage are supplied with redundant (A, B) power
feeds from the TRU over the shelf backplane. Shelf and fan unit power circuit
breakers are located on the TRU.
Figure 30-2 shows the backplane of the ALTS-N. The connectors that appear in the
topmost section are externally accessible from the front of the shelf. This is also
where fiber cable management is performed.
30-4


Figure 30-2 ALTS-N backplane
M5 nuts for
powering Subrack
(from TRU)
Fast-on terminals
for powering Fan unit
(from TRU)
Fast-ons for
Two-Wire
configuration
(LT area)
Fast-ons for
Two-Wire configuration
(Fan area)
FGE026
Table 30-2 provides information about the backplane connectors and related cables.
Table 30-2 Backplane connectors and related cables
Connector
Function
Type
Related cables
PWR I/O
Shelf power (BATA, BATB, BATRET)
Cable Lug M5
6 mm2 (3x)
FAN PWR I/O
Fan power (BATA, BATB, BATRET)
Female Faston 6.3
0.75 mm2 (3x)
(1 of 2)

30-5
Connector
Function
Type
Related cables
FAN 1, FAN 2
Fan interface
DSUB 15 pins
None
LT01 to LT16 NTA,

NTB, ACU
Connectors for plug-in units in line

termination area
Metral
CON-PB*MAL*XX
LINE 01 to 16
Line interface connectors
CHAMP 50 pins
UTP CAT5-type or better
ACU-TRU
Top Rack interface
DSUB 50 pins
3EC 16844 xx AA
CRTF
Remote Craft Interface
DSUB 9 pins
3EC 16028 xx AA
PLID
PLID jumper setting
Jumper connectors
1AB 00270 00 12
(jumper)
BATRET, FG
Two-wire power configuration
Fastons
(Faston bridge)
(1)
None
(2 of 2)
Note
(1)
Press-fit connectors with five row pinning and with 2 mm pitch.
30.5
Physical location identification

The ALTS-N shelf provides the physical location identification (PLID) setting. This
requires 21 PLID bits for ultra-density equipment.
Nine bits (SLOT_ID, BP_TYP) are fixed in the backplane layout, the other twelve
(SR_ID, R_ID, R_TYP, ACU_EN) can be altered at the installation with PLID
jumpers.
As described in Table 30-2, the jumpers are placed on the backplane in two columns
between the ACU and the NTA slots.
30.6
Power distribution
The shelf and the fan unit receive redundant power from the TRU. The TRU provides
redundant power, A and B, to the shelf and frame ground for the rack. In the
three-wire configuration, there are three power cables (BATA, BATB, and
BATRET) and a separate frame ground wire. In the two-wire configuration, frame
ground is provided via the BATRET cable. Figure 30-2 shows the Faston bridges
used to connect the three-wire and the two-wire power configurations.
The power signals BATA, BATB and BATRET is distributed via the backplane and
feed the plug-in units and fan units installed.
In the shelf power input area, a small board (FILT-A) is bolted onto the power
connectors of the ALTS-N shelf. The FILT-A (3EM 17820 AA) filters the dc mains
on the shelf to achieve CE Mark, EN55022, and EN300386 EMC compliance.
Three battery filter caps are provided on the board, one each for BAT_A-FG,
BAT_B-FG, and BAT_RET-FG.
Table 30-3 lists the power and grounding signals used.
30-6


Table 30-3 Power and grounding signals
30.7
Signal name
Description
BATA
Battery supply voltage branch A
BATB
Battery supply voltage branch B
BATRET
Common return voltage
EG
Electrical ground
FG
Shelf frame ground
Thermal limitation
Due to the high data rates and large number of subscribers, failure of the P-OLT
equipment can cause massive service outages and revenue loss for service providers.
Some P-OLT cards are not expected to operate more than a few minutes without
forced air cooling.
To prevent failure, the P-OLT uses a redundant fan design. With this design, the
failure of one fan does not cause a cooling system degradation that is severe enough
for the NT and LT units to fail. However, there are constraints that must be observed
for the design to work as specified.
Observe the following when working with the P-OLT equipment:
Keep the front cover on during normal operation to maintain proper thermal
30.8
operation.
Use only the AFAN-H as the P-OLT cooling system. The AFAN-H is
fault-tolerant and highly reliable.
Do not stack P-OLT shelves directly over each other, unless the air space between
the shelves are 300 mm and more.
Do Not place the shelf above a heat source without redirecting the hot air away
from the inlet of the shelf. For example, you can use an air baffle to redirect hot
air.
Never allow an in-service P-OLT be left without forced-air cooling for more than
5 minutes.
Replace the failed fan within the MTTR period. A single-fan failure in the P-OLT
cooling system does not cause the NT or LT cards to fail during the MTTR period.
MTTR is a maximum of 4 hours for remote locations, including CEVs.
Figure 30-3 shows the ALTS-N shelf with a front cover and a fan unit inserted at the
bottom.

30-7

Figure 30-3 ALTS-N shelf
FGE032
Front cover
The front cover provides EMC enclosure of the line termination area.
The front cover is supported by hanging it on the hooks on top of the shelf and closed
by locking the clips at the bottom.
Rear cover
The rear cover provides electrical insulation between the backplane of the shelf and
the rack or cabinet. To assure EMC enclosure, it is mounted to the backplane with
screws and to the shelf frame with spring contacts.
Fiber management kit

The fiber management kit is used to route fiber cables that are coming from the LT
cards installed in the ALTS-N shelf, and consists of a fiber routing tray and mounting
brackets. The fiber routing tray mounts inside the cable routing and shelf connector
area, which is located directly above the card cage. Fiber cables are routed out the
cable exit areas located on the left and right sides of the shelf.
Specifications
Table 30-4 describes the physical specifications of the ALTS-N.
30-8


Table 30-4 Physical specifications of the ALTS-N
Description
Specification
Height
24.56 in. (62.4 cm)
Width
20.27 in. (51.5 cm)
Depth
11.22 in. (28.5 cm)
Weight
62.61 lb (28.4 kg)

30-9
30-10

31.1 Identification
31-2

31.4 Front panel
31-2
31-2
31-3
31.5 PBA-ATRU-G board

31-4
31-6

31-1
31.1
Identification
Table 31-1 provides identification information about ATRU-M.
Table 31-1 Identification of ATRU-M
Part number
Mnemonic
Name
CLEI
CPR
ECI/bar
code
3EC 17422 AA
ATRU-M
Top rack unit, version M, for P-OLT rack

configurations
31.2

The ATRU-M unit provides:
rack powering to a maximum of two P-OLT shelves

termination of the office power and service battery cabling
termination of redundant office power cabling
termination point for connection to the CO alarm system and telemetry alarm
system
circuit breaker options for the AA variant:
6 x 30 A circuit breakers: 3 x A/3 x B (labeled 01, 02, and 03), for board protection
6 x 4 A circuit breakers: 3 x A/3 x B (labeled FAN1, FAN2, and FAN3), for fan
protection
three fuses, 5 A each, one for the service battery, 2 for the power cabling to the
31.3
top rack unit (TRU) control board

summary alarm display of minor, major, and critical alarms
circuit breaker alarm
power available indicators (A and B)
earth bonding point
General description
The ATRU includes the front panel and the connector blocks. For a description of
the connector blocks and their cabling, refer to the 7342 ISAM FTTU Hardware
Installation and Maintenance Practices.
The top rack unit contains a small board, the ATRU-G, located on the left. For a brief
description of this board, see the corresponding section.
31-2

31.4
Front panel
Figure 31-1 shows the following parts from left to right:
indicator LEDs and Test button

circuit breaker block for branch A
earth bonding point
circuit breaker block for branch B
warning labels
Figure 31-1 ATRU-M AA variant front panel
Indicator LEDs and test button

The test button is used to activate a lamp test. The lamp test tests the LEDs on the
PBAs and the rack lamps. Above the test button, a number of LED indicators are
located. Table 31-2 provides information about the LEDs.
Table 31-2 Front panel LED indicators
LED
Name
Description
CRI
Critical
Indicates a critical error
MAJ
Major
Indicates a major error
MIN
Minor
Indicates a minor error
FUS
Fuse
Indicates the condition of the fuse
VOLTAGE
Voltage
Indicates a voltage error
PWR-ATRU
Power
Power Indicator
PWRA1
Power 1, branch A
Power indicator 1 of the A branch of the power

distribution
PWRA2
Power 2, branch A

distribution
PWRA3
Power 3, branch A

distribution
PWRB1
Power 1, branch B
Power indicator 1 of the B branch of the power

distribution
PWRB2
Power 2, branch B

distribution
(1 of 2)

31-3
LED
Name
Description
PWRB3
Power 3, branch B

distribution
(2 of 2)
Circuit breakers
Circuit breakers are used for power feed branch A and B. The ATRU-M uses the AA
variant of the branch A circuit breaker.
The AA variant provides six circuit breakers each for the branch A and B. When
looking at the front panel, the circuit breakers for the branch A are located at the left
and those for the branch B are located at the right. Of the six circuit breakers for each
branch, the first three, labeled 01, 02, and 03, are the circuit breakers for the line of
the power distribution. These are 30 A circuit breakers and used for board protection.
The other three, labeled FAN1, FAN2, and FAN3, are 4 A circuit breakers, used for
fan protection.
Earth bonding point

This is the bonding point to which the protective earth is connected.
31.5
PBA-ATRU-G board
The PBA-ATRU-G board is located to the left, inside the ATRU-M. This board
performs a number of controls and functions of the ATRU-M. It contains a number
of connectors for different signals and a number of jumpers (straps) to set board
parameters.
Figure 31-2 shows the location of the connectors and jumpers on the PBA-ATRU-G
board.
31-4


Figure 31-2 PBA-ATRU-G connector and jumper locations
The pin layout of the 37-pin SUB-D CO interface connector is described in

Table 31-3. This interfaces to the central office local and telemetry alarm systems.
Table 31-3 CO connector pin layout
Pin
Signal name
I/O
Description
ACO_TEL_RET
In
BATRET on ACU
ACO_AUD_RET
In
BATRET on ACU
Not used
Not used
MISC1RET
In
BATRET on ACU
MISC2RET
In
BATRET on ACU
MISC3RET
In
BATRET on ACU
VOLTAGE_ALM
Out
Voltage alarm (low/high)
FUSEFAIL
Out
Fuse failure alarm
10
AUD_MIN-
Out
Audible minor alarm
11
AUDMAJ-
Out
Audible major alarm
12
AUD_CRI-
Out
Audible critical alarm
13
VIS_MIN-
Out
Visual minor alarm
14
VIS_MAJ-
Out
Visual major alarm
15
VIS_CRI-
Out
Visual critical alarm
16
TEL_MIN-
Out
Telemetry minor alarm
17
TEL_MAJ-
Out
Telemetry major alarm
(1 of 2)

31-5
Pin
Signal name
I/O
Description
18
TEL_CRI-
Out
Telemetry critical alarm
19
SYS_ID-
Out
System identity
20
ACO_TEL
In (From CO)
Alarm cutoff telemetry
21
ACO_AUD
In
Alarm cutoff audible
22
Not used
23
MISC1
In
Spare alarm 1
24
MISC2
In
Spare alarm 2
25
MISC3
In
Spare alarm 3
26
VOLTAGE_ALM_RET
Out (To CO)
BATR on ATRU
27
FUSEFAIL_RET
Out
BATR on ATRU
28
AUD_MIN+
Out
BATRET ON CO
29
AUDMAJ+
Out
BATRET ON CO
30
AUD_CRI+
Out
BATRET ON CO
31
VIS_MIN+
Out
BATRET on ATRU
32
VIS_MAJ+
Out
BATRET on ATRU
33
VIS_CRI+
Out
BATRET on ATRU
34
TEL_MIN+
Out
BATRET on CO
35
TEL_MAJ+
Out
BATRET on CO
36
TEL_CRI+
Out
BATRET on CO
37
SYS_ID+
Out
BATRET on CO
(2 of 2)
31.6
Table 31-4 describes the ATRU-M physical specifications.
Table 31-4 ATRU-M physical specifications
31-6
Description
Specification
Height
3.37 in. (86 mm)
Width
20.08 in. (51 cm)
Depth
7.87 in. (20 cm)
Weight
13.23 lb (6 kg)

32.1 Identification
32-2

32-2
32-4

32-2
32-1
32.1
Identification
Table 32-1 provides identification information about ATRU-N.
Table 32-1 Identification of ATRU-N
Part number
Mnemonic
Name
CLEI
CPR
ECI/Bar
code
3EC 17422 CD
ATRU-N
Top rack unit, Version N
32.2

The ATRU-N unit provides:
rack configurations with one or two ALTS-N shelves

fixed power distribution to ALTS-N shelves
connection of the central office (CO) power branches (feeders A1, A2, A3, B1,
B2, and B3)
distribution for branches A (feeders A1, A2) and B (feeders B1, B2) to two
ALTS-N shelves (redundant shelf powering)
distribution for branch A (feeder A3) to the first fan unit and branch B (feeder B3)
to the second fan unit
BATRET connection towards the CO power distribution frame (PDF) and to the
shelves and associated fan units
Note The ATRU-N contains no switches or circuit breakers for
equipment protection. The customer has to provide the protection
devices at the power source or at the PDF.
wires required for shelf and fan unit powering

fused powering connections for the PBA-ATRU-G unit (six 5 A fuses)
alarm control unit (ACU) interconnection between the shelves
connection to the CO alarm system and telemetry alarm system
alarm collecting, input voltage supervision, alarm routing and displaying alarm
conditions on the front panel (PBA-ATRU-G unit)
jumper setting for alarm selection
earth bonding point on the front panel
installation into a standard ETSI rack at an 87.5 mm pitch
32.3
General description
The ATRU-N is used for a rack configuration with up to two ALTS-N shelves, so
two power feeders are sufficient. However, a third power feeder is used for powering
a single fan unit. The first fan unit is powered by the third feeder from branch A and
the second fan unit is powered by the third feeder from branch B. Redundant
powering of the fan units is not offered; see Figure 32-1.
32-2

The ATRU-N provides the following functions:
connection of the external input power feeders (maximum three branch A and
three branch B feeders) and distribution of these to the two shelves and to the fan
unit in each shelf
Note Because the shelves and fan units in the rack are not
protected by switches nor circuit breakers, the customer has to
provide for the protection devices at the power source or power
distribution frame.
ACU (alarm control unit) interconnections between the shelves

voltage alarm at input voltages outside the tolerated limits
alarm selection
The ATRU-N contains the PBA-ATRU-G unit that performs the following
functions:
alarm collection
input voltage supervision
alarm routing
displays of the alarm conditions
It contains the cables for the power connections to the shelves and the fan units.
The TRU fits into a 87.5 mm pitch and according to the standard ETSI rack
dimensions.

32-3
BAT B2
BAT B1
BAT B3
BAT B2
BAT B1
BAT A3
BAT A2
BAT A1
to Power Distribution Frame
BAT B3
(for Two Wire
configuration)
Figure 32-1 Diagram of ATRU-N for fixed shelf powering (up to two ALTS-N shelves)
BATRET
PBA ATRU G
F A1
5A
F A1
5A
F A1
5A
I PWR A1
I PWR A2
I PWR A3
BATRET
F B1
5A
F B1
5A
F B1
5A
I PWR B1
I PWR B2
I PWR B3
BATRET
BAT A
BAT B
Fan2
SR 2
SR1
Fan1
SR 2
SR1
A TRU N
BAT RET
to shelf and fan units
32.4
The ATRU-N has three main parts: the front panel, the power-input terminal blocks,
and the PBA-ATRU-G board; see Figure 32-2.
32-4


Figure 32-2 Parts of the ATRU-N
Front panel
The front panel contains the following items from left to right:
LEDs for status indication and test button

Earth bonding point
Label with current rating
Warning label Energy Hazard
Figure 32-3 shows the front panel.

Figure 32-3 ATRU-N front panel
Front panel LEDs
Figure 32-4 shows the twelve front panel LEDs. Table 32-2 describes the LEDs.

32-5

Figure 32-4 ATRU-N front panel LEDs
CRI
MAJ
MIN
FUS
VOLTAGE
PWRATRU
PWRA1
PWRB1
PWRA2
PWRB2
PWRA3
PWRB3
TEST
FGE106
Table 32-2 Front panel LEDs
LED
Color
Name
Description
CRI
Red
Critical
MAJ
Red
Major
MIN
Yellow
Minor
FUS
Red
Fuse
Indicates the condition of the fuse
VOLTAGE
Red
Voltage
Indicates a voltage error
PWR_ATRU
White
Power
Power Indicator
PWRA1
Green
Power 1, branch A
Power indicator 1 of power branch A
PWRA2
Green
Power 2, branch A
PWRA3
Green
Power 3, branch A
PWRB1
Green
Power 1, branch B
Power indicator 1 of power branch B
PWRB2
Green
Power 2, branch B
PWRB3
Green
Power 3, branch B
Test button
The test button is used to activate a lamp-test. This test allows to check the operation
of the front panel LEDs (on the PBA-ATRU-G) and the rack lamps above the TRU.
Earth bonding point
The earth bonding point is connected to the protective earth. It provides a connection
point for an ESD wrist strap required when handling ESD susceptible cards.
32-6

Power input terminal blocks

The ATRU-N provides terminal and fuse blocks premounted on a symmetrical
DIN-rail. The two fabrication variants, shown in Figure 32-5, are available from
different sources. Although they have different terminal block types, they have the
same performance characteristics.
Figure 32-5 Power-input terminal blocks (two fabrication variants)
Fabrication variant 1
(1)
(2)
(3)
interconnected
BATRET terminals
Fabrication variant 2
(1)
(2)
(3)
interconnected
BATRET terminals
Notes
(1) Frame Ground is connected to this BATRET terminal to obtain the Two Wire power configuration
(2) These fuses and terminals are reserved for powering the PBA ATRU G unit.
(3) This terminal is reserved for BATRET connection of the PBA ATRU G unit.

32-7
Power and grounding provisions
The power input connections are the powering feeds coming from the CO PDF and
terminated on the terminal blocks inside the TRU (Figure 32-5).
Power input connections must be made by service personnel only. Table 32-3 gives
an overview of the possible connections.
Table 32-3 Power input connection and grounding provisions
Power connection type
Provisions
Labeling
Wire section
Battery input feed A1
max. 16
mm2
P-A1
16 mm2
max. 16 mm2
P-A2
16 mm2
Battery input feed B1
max. 16 mm2
P-B1
16 mm2
max. 16 mm2
P-B2
16 mm2
max. 2.5 mm2
P-A3
2.5 mm2
max. 2.5 mm2
P-B3
2.5 mm2
Battery return inputs max.
max. 16 mm2
BRET
16 mm2
Optional two-wire system connection

point (1)
max. 16 mm2
BRET
16 mm2
Note
(1)
Allows connecting the rack frame ground to BATRET to obtain a two-wire power supply instead of
the standard delivered three-wire power architecture. This connection is to be made on site.
Each variant contains six terminal blocks for BATRET connection; these are
interconnected.
Only two blocks of 16 mm2 are required for the battery return connections to the
power plant (BATRET A, BATRET B). The third block of 16 mm2 is reserved for
the optional frame ground to BATRET connection to obtain a two-wire
configuration.
Miniature fuses for PBA-TRU-G
The input terminal block contains six identical miniature fuses to protect the
PBA-ATRU-G board. Because this board is powered from all the branches (A1, A2,
A3, B1, B2, and B3) there is protection on each branch:
F-A1, F-A2, F-A3, F-B1, F-B2, and F-B3 are rated 250 V/5 A/medium blow.
External circuit breaker rating and cable sections
A P-OLT system equipped with the ATRU-N for fixed shelf powering is
permanently connected equipment. This type of TRU does not provide switches or
circuit breakers for powering on or off the system. The power switching function has
to be done externally by circuit breakers at the PDF.
Figure 32-6 shows how the P-OLT rack with an ATRU for fixed power distribution
has to be connected to the PDF.
32-8


Figure 32-6 Power connection of P-OLT rack to PDF
Power input terminals

ATRU N
B1
Circuit Breakers
A1
PDF B
Shelf 1
Fan unit 1
Battery B
A3
Circuit Breakers
B2 A2
PDF A
Shelf 2
Battery A
Fan unit 2
B3
Power Distribution Frame

Note The power distribution to the shelves provides for
redundancy, meaning that if one of the two breakers supplying a
specific shelf is turned off (for example, A1 is turned off, but B1 is
left on), the remaining single feed can support the full current
requirements of that shelf. Under normal conditions (A and B on), the
power/current is shared between the A and B feeds.
The power distribution to the fan units does not provide for
redundancy. Each fan unit is supplied by only one feed (feed A3 for
the first fan unit and feed B3 for the second).
The circuit breakers at the power distribution frame must have the following current
rating to protect the power cables feeding a P-OLT rack equipped with two ALTS-N
shelves; see Table 32-4.

32-9

Table 32-4 PDF circuit breaker rating and power cable sections
Branch
Powering
Max. CB
rating at PDF
Power cable
section
Branch A1
Shelf 1
32 A
16 mm2
Branch A2
Shelf 2
32 A
16 mm2
Branch A3
Fan unit 1
10 A
2.5 mm2
Branch B1
Shelf 1
32 A
16 mm2
Branch B2
Shelf 2
32 A
16 mm2
Branch B3
Fan unit 2
10 A
2.5 mm2
Warning If an inappropriate circuit breaker or cable section is

applied, a dangerous situation may occur.
Using circuit breakers with a rating too high or using power cables
with a section too small can cause death or serious physical harm to
persons, or damage to equipment.
Incorrect connection can cause serious physical harm to persons or
damage to equipment (for example, when powering the fan units with
power cables that are protected with 32 A breakers instead of 10 A
breakers).
Remove and replace circuit breakers with appropriately rated circuit
breakers.
Check for correct power cable connections between the power
distribution frame and the P-OLT before powering the equipment.
PBA-ATRU-G board
The ATRU-N contains the PBA-ATRU-G board. This board provides an interface
for alarm collection, alarm routing, and display of the alarm conditions in the rack.
As shown in Figure 32-2, the ATRU-G board is mounted inside the left-hand side the
TRU.
Figure 32-7 describes the board layout and shows the following items:
32-10
LEDS (Figure 32-4 shows the LEDs on the front panel)

one test button (Figure 32-4 shows the test button on the front panel)
three ACU/FAN alarm interface connectors
one central office interface connector
twenty jumpers.


Figure 32-7 Layout of the ATRU-G board (jumpers factory set)
ACU3
2
ACU2
20
1
18
34
50
17
ACU1
18
34
50
17
18
34
3 2 1
X1
LEDS
13 5
2 4 6
(LR)
(CA)
3
17
19
33
33
33
50
37
(CB)
3 X20
(CO)
Test button
FGE108
Rack lamp connector

ACU/FAN Alarm
Interface Connectors
ATRU G Jumpers
Pin number
Jumper
number
3 21
X1
Central Office
Interface Connector
X19
X20
Jumper
CO interface connector
Table 32-5 describes the pin connector layout for a D-SUB 37-pin connector used
with the CO interface connector on the ATRU G. Figure 32-8 shows the D-SUB
37-pin connector layout.

32-11

Figure 32-8 D-SUB 37-pin connector
19
20
37
FGE109
Table 32-5 Pin layout of CO interface connector

Pin
Signal name
Type
Description
ACO_TEL_RET
In
BATRET on ACU
ACO_AUD_RET
In
BATRET on ACU
3, 4, 22
Not used
MISC1_RET
In
BATRET on ACU
MISC2_RET
In
BATRET on ACU
MISC3_RET
In
BATRET on ACU
VOLTAGE_ALM
Out
Voltage_alarm (low/high)
FUSEFAIL
Out
Fuse failure alarm
10
AUD_MIN-
Out
Audible minor alarm
11
AUD_MAJ-
Out
Audible major alarm
(1 of 2)
32-12

Pin
Signal name
Type
Description
12
AUD_CRI-
Out
Audible critical alarm
13
VIS_MIN-
Out
Visual minor alarm
14
VIS_MAJ-
Out
Visual major alarm
15
VIS_CRI-
Out
Visual critical alarm
16
TEL_MIN-
Out
Telemetry minor alarm
17
TEL_MAJ-
Out
Telemetry major alarm
18
TEL_CRI-
Out
Telemetry critical alarm
19
SYS_ID-
Out
System identity
20
ACO_AUD
In
Alarm cutoff audible
21
ACO_TEL
In
Alarm cutoff telemetry
23
MISC1
In
Spare alarm 1
24
MISC2
In
Spare alarm 2
25
MISC3
In
Spare alarm 3
26
VOLTAGE_ALM_RET
Out
BATR on ATRU-G
27
FUSEFAIL_RET
Out
BATRET on ATRU-G
28
AUD_MIN+
Out
BATRET on CO
29
AUD_MAJ+
Out
BATRET on CO
30
AUD_CRI+
Out
BATRET on CO
31
VIS_MIN+
Out
BATRET on ATRU-G
33
VIS_CRI+
Out
BATRET on ATRU-G
34
TEL_MIN+
Out
BATRET on CO
35
VIS_MAJ+
Out
BATRET on ATRU-G
35
TEL_MAJ+
Out
BATRET on CO
36
TEL_CRI+
Out
BATRET on CO
37
SYS_ID+
Out
BATRET on CO
(2 of 2)
ACU/FAN alarm interface connectors

Table 32-6 describes the pin connector layout for a D-SUB 50-pin connector used
with the ACU and FAN interface connectors on the ATRU-G. Figure 32-9 shows the
D-SUB 50-pin connector layout.

32-13

Figure 32-9 D-SUB 50-pin connector
1
18
17
34
50
FGE110
Table 32-6 Pin layout of ACU/FAN alarm connectors

Pin
Signal name
Type
Description
ACO-TEL-A
Out
Telemetry alarm cutoff (A-wire)
ACO-AU-A
Out
Audible alarm cutoff (A-wire)
FAN-ALM0-A
Out
Fan unit 0 alarm (A-wire)
FAN-ALM1-A
Out
DOOR-ALM-A
Out
Door alarm (A-wire)
FUSE-ALM-A
Out
Fuse alarm (A-wire)
SP-ALM0-A
Out
Spare alarm 0 (A-wire)
SP-ALM1-A
Out
SP-ALM2-A
Out
10
SP-ALM3-A
Out
(1 of 3)
32-14

Pin
Signal name
Type
Description
11
SP-ALM4-A
Out
12
AU-MIN-A
In
Minor audible alarm (A-wire)
13
AU-MAJ-A
In
Major audible alarm (A-wire)
14
AU-CRIT-A
In
Critical audible alarm (A-wire)
15
VIS-MIN-A
In
Minor visible alarm (A-wire)
16
VIS-MAJ-A
In
Major visible alarm (A-wire)
17
VIS-CRIT-A
In
Critical visible alarm (A-wire)
18
TEL-MIN-A
In
Minor tel. alarm (A-wire)
18
TEL-MIN-B
In
Minor tel. alarm (B-wire)
20
TEL-MAJ-A
In
Major tel. alarm (A-wire)
21
TEL-MAJ-B
In
Major tel. alarm (B-wire)
22
TEL-CRIT-A
In
Critical tel. alarm (A-wire)
23
TEL-CRIT-B
In
Critical tel. alarm (B-wire)
24
SID-A
In
System ID (A-wire)
25
SID-B
In
System ID (B-wire)
26
FAN-ALM2-A
In
27
FAN-ALM2-B
In
Fan unit 2 alarm (B-wire)
28
FAN-ALM3-A
In
29
FAN-ALM3-B
In
30
TRU-SP0
In
Spare alarm 0
31
TRU-SP1
In
Spare alarm 1
32
TRU-SP2
In
Spare alarm 2
33
TRU-SP3
In
Spare alarm 3
34
ACO-TEL-B
Out
Telemetry. alarm cutoff (B-wire)
35
ACO-AU-B
Out
Audible alarm cutoff (B-wire)
36
FAN-ALM0-B
Out
37
FAN-ALM1-B
Out
38
DOOR-ALM-B
Out
Door alarm (B-wire)
39
FUSE-ALM-B
Out
Fuse alarm (B-wire)
40
SP-ALM0-B
Out
Spare alarm 0 (B-wire)
41
SP-ALM1-B
Out
42
SP-ALM2-B
Out
43
SP-ALM3-B
Out
44
SP-ALM4-B
Out
45
AU-MIN-B
In
Minor audible alarm (B-wire)
46
AU-MAJ-B
In
Major audible alarm (B-wire)
47
AU-CRIT-B
In
Critical audible alarm (B-wire)
(2 of 3)

32-15
Pin
Signal name
Type
Description
48
VIS-MIN-B
In
Minor visible alarm (B-wire)
49
VIS-MAJ-B
In
Major visible alarm (B-wire)
50
VIS-CRIT-B
In
Critical visible alarm (B-wire)
(3 of 3)
Jumpers
The PBA-ATRU-G is equipped with 20 jumpers. Jumpers X1 to X19 allow different
parameter settings and jumper X20 is a spare.
At delivery, the jumpers are factory set. Each jumper is in the left-hand position and
connects pin 2 and 3. Table 32-7 gives the function of the jumpers when factory set.
Jumper setting is performed on site and as required by the application; see
Table 32-8.
Table 32-7 Factory jumper settings
Jumper
Function (application-dependent)
X5
Fuse fail indication at CO
X3+X6
Power OFF command to ACU
X11
Power OFF setting for 48 V power system
X4
LVA_HVA signal to ACU
X7+X8+X9+X10
LVA_HVA setting for 48 V rack supply voltage selection system
X14
Rack lamp ON when one power branch is present
X15+X16
ALARM FAN3 assigned to ACU alarm input of FAN2
X12+X13
ATRU-G fed by power branches A and B
X2+X18+X17+x19
Door alarm contacts connected to ACU alarm inputs SP_ALM2
(1)
(2)
Notes
(1)
X3 and X6 are removed for 3 P-OLT racks (future).
(2)
X15 and X16 are removed for 2 and (future) 3 P-OLT racks.
Table 32-8 Application-dependent jumper setting

Jumper
X17+X19
MISC3 of CO connected to SP_ALM2 of ACU
X4
MISC4 of ACU connected toSP_ALM3 of ACU
X1+X6+X5+X3
MISC5 of ACU connected to SP_ALM4 of ACU
X7+X8+X9+X10
LVA_HVA setting for 60 V rack supply voltage selection system
X11
Power OFF setting for 60 V power system
(1)
(1 of 2)
32-16

Jumper
X12+X13
ATRU-G is fed by the service battery
X14
POWER ON rack lamp is illuminated when both the power input branches
are present
X15+X16
ALARM FAN3 assigned to ACU alarm input of FAN1
X2+X18
Door alarm contacts connected to ACU alarm inputs DOOR_ALM
(2)
(2 of 2)
Notes
(1)
X3 and X6 are removed for 3 P-OLT racks (future).
(2)
X15 and X16 are removed for 2 and (future) 3 P-OLT racks.
Dimensions
The ATRU-N unit complies with the ETSI rack dimensions.
Table 32-9 gives the dimensions of the ATRU-N.
Table 32-9 ATRU-N dimensions
Dimension
Comment
Value
Height
85.7mm
Width
Excluding mounting support
500 mm
Including mounting support
530 mm
For mounting
515 mm
Excluding hinged front
258.5 mm
Including hinged front
262 mm
Pitch of mounting holes
12.5 or 25 mm
Weight
3.5 kg
Depth
Safety requirements
When equipped in a OLT rack, the ATRU-N meets the requirements of:
EN 60950/EC 60950, third edition 1999-04Safety of information technology

equipment.
AS3260
The following characteristics are valid:
permanently connected equipment

installation in restricted access location
Class I equipment (for protection against electric shock)

32-17
TNV dc supply voltage (Telecommunication Network Voltage)

The dc-return conductor is insulated (three-wire power configuration) with
arrangements to connect the dc-return conductor to the frame (two-wire power
configuration).
Specifications
Table 32-10 describes the physical specifications of the ATRU-N.
Table 32-10 Physical specifications of the ATRU-N
32-18
Description
Specification
Height
3.37 in. (85.7 mm)
Width
15.75 in. (40 cm)
Depth
11.81 in. (30 cm)
Weight
12.35 lb (5.6 kg)

33.1 Identification
33-2

33.4 Front panel
33-2
33-2
33-3
33.5 PBA-ATRU-G board

33-4
33-6

33-1
33.1
Identification
Table 33-1 provides identification information about ATRU-U and GTRU-B.
Table 33-1 Identification of ATRU-M
Part number
Mnemonic
Name
CLEI
CPR
ECI/bar code
3FE 51460 AA
ATRU-U
Top rack unit, version U, for OLTS-M

P-OLT rack configurations
BVM5Y00CRA
211350
454739
3FE 51460 AB
GTRU-B
Top rack unit, version B, for OLTS-M

P-OLT rack configurations
BVM8F00BRA
213064
459585
33.2

The ATRU-U and GTRU-B units provide:
termination of redundant office power

termination of the service battery cabling
circuit breakers for rack equipment for the ATRU-U:
4 x 35 A circuit breakers: 2 x A/2 x B (labeled 01,and 02), for P-OLT shelf
protection
4 x 6 A circuit breakers: 2 x A/2 x B (labeled FAN1 and FAN2), for fan protection
circuit breakers for rack equipment for the GTRU-B:
4 x 50A circuit breakers: 2 x A/2 x B (labeled 01,and 02), for P-OLT shelf protection
4 x 6 A circuit breakers: 2 x A/2 x B (labeled FAN1 and FAN2), for fan protection
rack power wiring to a maximum of two P-OLT shelves
rack power wiring to a maximum of two fan shelves
termination point for connection to the CO alarm system and telemetry alarm
33.3
system
three internal fuses, 5 A each, one for the service battery, 2 for the power cabling
to the top rack unit (TRU) control board (PBA-ATRU-G)
summary alarm display of minor, major, and critical alarms
circuit breaker alarm indicator
power available indicators (A and B)
earth bonding point
General description
The ATRU and GTRU includes the front panel, redundant power connector blocks
and rack equipment power harness. For a description of the connector blocks and
their cabling, refer to the 7342 ISAM FTTU Hardware Installation and Maintenance
Practices.
The top rack unit contains a small board, the ATRU-G, located on the left. For a brief
description of this board, see the corresponding section.
33-2

33.4
Front panel
Figures 33-1 and 33-2 show the following parts from left to right:
indicator LEDs and Test button

circuit breaker block for branch A
earth bonding point
circuit breaker block for branch B
warning labels
Figure 33-1 ATRU-U front panel
CAUT
ION
TWO Bra
nch Pow
er Supply
Switch off
the fuses
F........and
F...
rack or PD .....in
B.....
to clear
the equipm
ent
ENERGY
HAZARD
19335
Figure 33-2 GTRU-B front panel
SAU
CRI
C1
MAJ
C2
FAN1
MIN
FAN2
FUS
VOLTAGE
PWRA1
PWRA2
UNUSED
PWR-ATR
SAU
D1
D2
PWRB1
FAN1
PWRB2
FAN2
UNUSED
TEST
ESD
50A
EA
BON
A05/6
IN
A04/6
RTH
6A
A02/50
6A
A01/50
IN
50A
CB/A
PO
50A
CB/B
50A
6A
B01/50
6A
B02/50
B04/6
B05/6
20364
Indicator LEDs and test button

The test button is used to activate a lamp test. The lamp test tests the LEDs on the
TRU and the rack lamps. Above the test button, a number of LED indicators are
located. Table 33-2 provides information about the LEDs.

33-3

Table 33-2 Front panel LED indicators
LED
Name
Description
CRI (red)
Critical
MAJ (red)
Major
MIN (yellow)
Minor
FUS (red)
Fuse fail
Indicates the tripped or off condition of a circuit breaker
VOLTAGE (red)
Voltage
Indicates a branch voltage error high or low
PWR-ATRU
(green)
ATRU Power
Power present Indicator
PWRA1 (green)
Power 1, branch A

distribution
PWRA2 (green)
Power 2, branch A

distribution
UNUSED
PWRB1 (green)
Power 1, branch B

distribution
PWRB2 (green)
Power 2, branch B

distribution
UNUSED
Circuit breakers
Circuit breakers are used for power feed branch A and B for two OLTS-M shelves
and two AFAN-S fan units.
There are four circuit breakers each for the branch A and B. When looking at the
front panel, the circuit breakers for the branch A are located at the left and those for
the branch B are located at the right. Of the four circuit breakers for each branch, the
first two, labeled 01,and 02, are the circuit breakers for the shelf power distribution.
These are 35 A circuit breakers (ATRU-U) and 50 A circuit breakers (GTRU-B) and
used for board protection. The other two, labeled FAN1,and FAN2, are 6 A circuit
breakers, used for the fan unit protection.
Earth bonding point

This is the bonding point to which the ESD wrist strap is connected.
33.5
PBA-ATRU-G board
The PBA-ATRU-G board is located to the left, inside the ATRU-U and GTRU-B.
This board performs a number of controls and functions of the TRU. It contains a
number of connectors for different signals and a number of jumpers (straps) to set
board parameters.
Figure 33-3 shows the location of the connectors and jumpers on the PBA-ATRU-G
board.
33-4


Figure 33-3 PBA-ATRU-G connector and jumper locations
X312 (DA)
2
1
X201 (PA)
4 5 6
1 2 3
X202 (PB)
4 5 6
X301 (CO)
ACU3
1 2 3
k319
ACU2
ACU1
X311 (LR)
1 3 5
2 4 6
X2401 (CA)
1 2 3
X2402 (CB)
1 2 3
k366 k382 X304

3
X303
X302
X1
X19
18839
The three ACU connectors interface through the P-OLT back panel to the ACU card.
Connector ACU1 is for P-OLT shelf 1, connector ACU2 is for P-OLT shelf 2 and
connector ACU3 is not used.
The pin layout of the 6-pin RJ45 rack lamp connector is described in Table 33-3.
Table 33-3 Lamp rack connector (X311)
Pin
Signal name
I/O
Description
CRI_RK_LMP
Out
Critical alarm rack lamp (Red lamp,

left side, +)
MAJ_RK_LMP
Out
Major alarm rack lamp (Red lamp,

right side, +)
MIN_RK_LMP
Out
Minor alarm rack lamp (Yellow lamp,+)
BATD
Out
48 V (all lamps, )
LMP_ON
Out
Power ON (Green lamp, +)
The pin layout of the 2-pin door alarm connector is described in Table 33-4. This
interfaces to the equipment cabinet door sensor.

33-5

Table 33-4 Door alarm connector (X312)
Pin
Signal name
I/O
Description
DOOR ALM A
In
Door alarm A-wire (BATRET of ACU)
DOOR ALM B
In
Door alarm B-wire (OPTO ACU)
Note Jumper X20 is a spare jumper.
33.6
Table 33-5 describes the ATRU-U and GTRU-B physical specifications.
Table 33-5 ATRU-U and GTRU-B physical specifications
33-6
Description
Specification
Height
3.37 in. (8.57 cm)
Width
17.23 in. (47.76 cm)
Depth
10.18 in. (25.85 cm)
Weight
13.2 lb. (6.0 kg)

34.1 Identification
34-2

34.4 Location
34-2
34-2
34-3

34-1
34.1
Identification
Table 34-1 provides identification information about the BITS-B.
Table 34-1 Identification of BITS-B
Part number
Mnemonic
Description
CLEI
CPR
ECI/Bar code
3FE 51426 AA
BITS-B
BITS and LAN interface board
BVL3AC2BAA
099999
155524
34.2

The BITS-B unit provides:
34.3
signal attenuation of the BITS clock signal to the NT

signal attenuation of the reflection back to the BITS clock generator
electromagnetic interference attenuation
ethernet LAN connector
General description
The BITS-B card is mounted on the OLTS-M backplane at J67 and provides an
RJ-45 connector to connect the primary (PRI) BITS and secondary (SEC) BITS
timing references to the NT cards. A second RJ-45 connector on the cards provides
a 10/100 Mbps Ethernet interface.
The BITS-B card provides protection and attenuation for the BITS signals and also
provides termination for unused Ethernet signals.
The BITS-B is a passive unit. No power interface is required.
Figure 34-1 shows the BITS-B card. See 7342 ISAM FTTU Hardware Installation
and Maintenance Practices for the pinouts for the BITS interface.
Figure 34-1 BITS-B card
LAN
BITS
19338
34-2

34.4
Location
The BITS-B unit is mounted on the backplane of the OLTS-M shelf in the power and
connector section at the top of the shelf.

34-3
34-4

35.1 Identification
35-2

35-2
35-2

35-2
35-1
35.1
Identification
Table 35-1 provides identification information about the blank LT filler plates.
Table 35-1 Identification of the blank LT filler plate
Part number
Mnemonic
Description
CLEI
CPR
ECI/Bar code
3FE 24573 AB
LT filler plate
3FE 51178 AA
4 Port LT filler plate
BVPQAEEKAA
154157
35.2

The blank LT filler plate:
provides an ESD/EMI seal for unused LT slots in shelves supporting two-port

LTs
provides a thermal seal for unused LT slots in shelves supporting two-port LTs
contains mechanical parts only
The four-port LT filler plate:
provides an ESD/EMI seal for unused LT slots in shelves supporting four-port

LTs
provides a thermal seal for unused LT slots in shelves supporting four-port LTs
provides non-functional fiber connectors to park fiber optic cable
Warning The blank LT filler plate or LT cards must be placed in
unused LT slots to maintain proper operation.
35.3
General description
To meet EMC and thermal requirements, blank LT filler plates or LT cards must be
inserted in any unused LT slots.
Note The ANSI OLTS-K shelf does not need the front and rear
covers installed to meet EMC and thermal requirements as in previous
versions.
35.4
Table 35-2 describes the dimensions of the blank LT filler plate.
35-2


Table 35-2 Dimensions of the LT filler plate
Description
Measurement
Height
16.53 in. (41.9862 cm)
Width
0.98 in. (2.49 cm)
Depth
7.36 in. (18.69 cm)

35-3
35-4

36.1 Identification
36-2

36-2
36-2

36-2
36-1
36.1
Identification
Table 36-1 provides identification information about the blank NT filler plate.
Table 36-1 Identification of the blank NT filler plate
Part Number
Mnemonic
Description
CLEI
CPR
ECI / Bar code
3FE 24574 AA
Blank NT filler plate
36.2

The blank NT filler plate:
provides an ESD/EMI seal for unused NT slots in shelves

provides a thermal seal for unused NT slots in shelves
contains mechanical parts only
Warning The blank NT filler plate or NT cards must be placed in
unused NT slots to maintain proper operation.
36.3
General description
To meet EMC and thermal requirements, blank NT filler plates or NT cards must be
inserted in any unused NT slots in any shelf.
Note The ANSI OLTS-K shelf does not need the front and rear
covers installed to meet EMC and thermal requirements as in previous
versions.
36.4
Table 36-2 describes the dimensions of the blank NT filler plate.
Table 36-2 Dimensions of the NT filler plate
36-2
Description
Measurement
Height
16.53 in. (41.9862 cm)
Width
0.98 in. (2.95 cm)
Depth
7.36 in. (18.69 cm)

37 EHNT and pluggable optical modules

unit data sheet
37.1 Identification
37-2

37-6
37.4 Network interface modules

37.5 Interfaces and connectors
37.6 Status LEDs
37.7 Power
37-5
37-7
37-7
37-7
37-9
37-10

37-1
37.1
Identification
Table 37-1 provides identification information about EHNT-A and the associated
pluggable optical modules while Table 37-2 provides specific information for 1AB
3566300XX modules.
Table 37-1 Identification of EHNT-A and the associated optical modules
Part number
Mnemonic
Description
CLEI
CPR
ECI/Bar
code
Application
3FE 50479 AA
EHNT-A
Ethernet high capacity

network termination card,
version A
BVNIPR0EAB
070BHM
147927
BVNIPU0EAA
070BHM
149239
BVL3ABHBAA
070JMJ
151820
3FE 50479 AB
3FE 51196 AA
EHNT-B
Ethernet high capacity

version B
(for OLTS-M shelf)
3FE 51026 AA
1-GE SFP, electrical, 100 m

(328 ft), not temperature
hardened (Commercial
range -5C to +50C (23F to
122F)) (1) (2) (3)
BVL3AA5BAA
U73174
146295
3FE 25772 AA
1-GE SFP (upstream), 1310

nm transmit, 1490 nm
receive, SMF, 10 km,
temperature hardened
(Industrial range -40C to
+65C (-40F to 149F)) (1)
VAUIAGUAAA
U72812
137841
3FE 25772 AB
1-GE SFP (downstream),

1490 nm transmit, 1310 nm
+65C (-40F to 149F)) (1)
VAUIAGVAAA
U72813
137842
3FE 25773 CA
1-GE SFP, 850 nm,

multimode fiber (MMF),
0.85 m (850 nm), 550 m
(1804 ft) (4), not
(Commercial range -5C to
+50C (23F to 122F)) (1) (3)
BVLIJ0TFAA
U72534
136282
SX
VAUIAEYAAA
U72496
135567
LX10
3FE 25774 AA
compliant with 802.3z

1000BASE-SX PMD
275 m with 62.5 uM
MMF (200 MHz * km @
850nm fiber)
550 m with 50 uM MMF
(500 MHz * km @ 850nm
fiber)
1-GE SFP, 1310 nm, single

mode fiber (SMF), 6.21 mi
(10 km), temperature
hardened (Industrial range
-40C to +65C (-40F to
149F)) (1) (3)
(1 of 2)
37-2

Part number
Mnemonic
Description
CLEI
CPR
ECI/Bar
code
Application
3FE 25775 AA
1-GE SFP, 1310 nm, SMF,

24.85 mi (40 km),
+65C (-40F to 149F)) (1) (3)
VAUIAE0AAA
U72498
135569
EX
3FE 25776 AA

49.71 mi (80 km),
+65C (-40F to 149F)) (1) (3)
VAUIAF2AAA
U72742
136958
ZXU
3FE 25776 BA

49.71 mi (80 km), not
+50C (23F to 122F)) (1) (3)
VAUIAEZAAA
U72497
135568
ZXU
3FE 50712 AA
10-GE XFP, 850 nm, MMF,

984 ft (300 m) (5), not
+50C (23F to 122F)) (1) (3)
BVLIJ0UFAA
U72906
139338
SR
3FE 50712 BA
10-GE XFP, 1310 nm, SMF,

6.21 mi (10 km), not
+50C (23F to 122F)) (1)
BVL3AALBAA
U73047
142249
LR
3FE 50712 BB

6.21 mi (10 km),
+65C (-40F to 149F)) (1) (3)
VAUIAMHAAA
U73591
154615
LR
3FE 50712 CA

24.85 mi (40 km), not
+50C (23F to 122F)) (1) (3)
BVL3AAMBAA
U73048
142250
ER
3FE 50712 CB

24.85 mi (40 km),
+65C (-40F to 149F)) (1) (3)
BLV3AA9BAA
U73263
148225
ER
3FE 50712 DA

49.71 mi (80 km), not
+50C (23F to 122F)) (1) (3)
3EM 19465 AA
10-GE XFP, electrical, 0.3

m, temperature hardened
(for EHNT-A only)
+65C (-40F to 149F)) (1)
1AB 35663 00XX

(Refer to
Table 37-2)
10-GE XFP, 100GHz DWDM,

SMF, 49.71 mi (80 km), not
+50C (23F to 122F)) (1) (3)
(Refer to
Table 37-2)
(Refer to
Table 37
-2)
(Refer to
Table 37
-2)
(2 of 2)

37-3

Notes
(1)
Do not use unauthorized SFPs or XFPs. Using unauthorized SFPs and XFPs adversely affects the P-OLT, may cause an
unexpected NT reset, and requires operator intervention to fix.
(2)
Use shielded CAT5e-grade or better Ethernet cables with electrical SFPs or XFPs.
(3)
The EXNT-A AA variant does not support these SFPs or XFPs.
(4)
The reach assumes 50 m MMF.
(5)
The reach assumes 50 m MMF, 2000 MHz/km.
Table 37-2 Specific information for 1AB 3566300XX modules

Part number
Channel
Wavelength
CLEI
CPR
ECI/Bar code
1AB356630001
60
1529.55
WOTRAP5GAA
U73480
152783
1AB356630002
59
1530.33
WOTRAP6GAA
U73480
152827
1AB356630003
58
1531.12
WOTRAP7GAA
U73480
152828
1AB356630004
57
1531.90
WOTRAP8GAA
U73480
152829
1AB356630005
56
1532.68
WOTRAP9GAA
U73480
152830
1AB356630006
55
1533.47
WOTRARAGAA
U73480
152831
1AB356630007
54
1534.25
WOTRARBGAA
U73480
152832
1AB356630008
53
1535.04
WOTRARCGAA
U73480
152833
1AB356630009
52
1535.82
WOTRARDGAA
U73480
152834
1AB356630010
51
1536.61
WOTRAREGAA
U73480
152835
1AB356630011
50
1537.40
WOTRARFGAA
U73480
152836
1AB356630012
49
1538.19
WOTRARGGAA
U73480
152837
1AB356630013
48
1538.98
WOTRARHGAA
U73480
152838
1AB356630014
47
1539.76
WOTRARJGAA
U73480
152839
1AB356630015
46
1540.56
WOTRARKGAA
U73480
152840
1AB356630016
45
1541.35
WOTRARLGAA
U73480
152841
1AB356630017
44
1542.14
WOTRARMGAA
U73480
152842
1AB356630018
43
1542.94
WOTRARNGAA
U73480
152843
1AB356630019
42
1543.73
WOTRARPGAA
U73480
152844
1AB356630020
41
1544.53
WOTRARRGAA
U73480
152845
1AB356630021
40
1545.32
WOTRARSGAA
U73480
152846
1AB356630022
39
1546.12
WOTRARTGAA
U73480
152847
1AB356630023
38
1546.92
WOTRARUGAA
U73480
152848
1AB356630024
37
1547.72
WOTRARVGAA
U73480
152849
1AB356630025
36
1548.51
WOTRARWGAA
U73480
152850
1AB356630026
35
1549.32
WOTRARXGAA
U73480
152851
1AB356630027
34
1550.12
WOTRARYGAA
U73480
152852
1AB356630028
33
1550.92
WOTRARZGAA
U73480
152853
1AB356630029
32
1551.72
WOTRAR0GAA
U73480
152854
1AB356630030
31
1552.52
WOTRAR1GAA
U73480
152855
(1 of 2)
37-4

Part number
Channel
Wavelength
CLEI
CPR
ECI/Bar code
1AB356630031
30
1553.33
WOTRAR2GAA
U73480
152856
1AB356630032
29
1554.13
WOTRAR3GAA
U73480
152857
1AB356630033
28
1554.94
WOTRAR4GAA
U73480
152858
1AB356630034
27
1555.75
WOTRAR5GAA
U73480
152859
1AB356630035
26
1556.55
WOTRAR6GAA
U73480
152860
1AB356630036
25
1557.36
WOTRAR7GAA
U73480
152861
1AB356630037
24
1558.17
WOTRAR8GAA
U73480
152862
1AB356630038
23
1558.98
WOTRAR9GAA
U73480
152863
1AB356630039
22
1559.79
WOTRASAGAA
U73480
152864
1AB356630040
21
1560.61
WOTRASBGAA
U73480
152865
1AB356630041
20
1561.42
WOTRASCGAA
U73480
152866
(2 of 2)
37.2

The EHNT card mounts in the network termination slots (NT-A and NT-B) of the
optical line termination (OLT) shelf.
The EHNT card supports:
up to 16000 media access control (MAC) address entries with hardware assisted
aging
up to 8000 IP address entries; hashing may limit the number of IP address entries
to 5000
up to 12257 routes
IEEE 802.3x flow control at full duplex
network timing requirements for BITS I/F logic
The EHNT card provides:
gigabit Ethernet (GE) optical connectivity to a high-bandwidth Internet protocol
(IP) services network

pluggable SFP and XFP modules for GE optical connectivity
management and control interfaces for the 7342 ISAM FTTU
a 48 Gb/s switch matrix that supports two GE interfaces per line termination (LT)
card (36 in total)
four fixed 1-GE 1000Base-X using SFP network ports
one 10-GE network XFP port

37-5
one HiGig (10-GE) NT-to-NT XFP port for EHNT-A

diagnostic light emitting diodes (LEDs) per port
Note The EHNT card is not pre-equipped with optical ports. The
base unit has an operating temperature of 40F to 149F (40C to
65C). Different versions of optical pluggable modules are available
for each port, some of which provide extended temperature operation.
37.3
General description
The EHNT card is an NT subsystem that provides GE optical connectivity to a
high-bandwidth IP services network.
The EHNT-A card has four 1-GE SFP ports for connectivity to a high-bandwidth IP
services network and two 10-GE XFP ports. One 10-GE XFP port connects to the IP
services network and the remaining 10-GE port connects to the other NT card in a
redundant system. Any one or a combination of the network connections can be used,
depending on expected capacity.
The EHNT-B card has four 1-GE SFP ports for connectivity to a high-bandwidth IP
services network and one 10-GE XFP port for connection to the IP services network.
Any one or a combination of the network connections can be used, depending on
expected capacity. Connectivity to the other NT card in a redundant system is
accomplished through the backplane of the OLTS-M shelf.
In addition to providing network termination, the EHNT card performs Ethernet
switching and provides the control and management functions of the
7342 ISAM FTTU. The EHNT card manages the P-OLT, the shelf, and the
switching data path.
The EHNT card manages high-bandwidth IP services for subscribers by providing a
48 Gb/s Ethernet switching matrix. In the downstream direction, high-bandwidth IP
services enter the network termination side of the 7342 ISAM FTTU over optical
connectivity at the EHNT card. The EHNT card switches the IP traffic. The
appropriate packets for each connected subscriber are then forwarded over the
backplane to an LT unit. In the upstream direction, the EHNT card receives Ethernet
packets from the LT units over the backplane. The EHNT card switches the packets
to the high-bandwidth IP services network.
The EHNT card supports inband management traffic received through its
connectors. Local management through a craft terminal is supported by the EHNT
card through craft connections on the alarm control unit (ACU).
The EHNT card can be managed by either a NMS or a local command line interface
(CLI and TL1) on the AACU.
The AB variant of the EHNT-A card replaced the previously available AA variant.
The AB variant is a direct replacement of the AA variant but does not contain the
wire straps. The AA variant is no longer an orderable item.
The EHNT-A and EHNT-B are not interchangeable. The EHNT-A is the NT card for
the OLTS-K shelf configuration and the EHNT-B is the NT card for the OLTS-M
configuration.
37-6

37.4
Network interface modules

See Section 43.4 of the NT card unit data sheet for information on network interface
modules.
37.5
Interfaces and connectors

The EHNT supports the LC/UPC connector for connection to the external optical
network.
The EHNT supports the following connectors for the required optical modules that
are Alcatel-Lucent-approved:
four 1000Base-X SFP connectors for gigabit Ethernet optical connectivity

one 10-GE network XFP connector
one HiGig (10-GE) NT-to-NT XFP connector (EHNT-A only)
These connectors are located on the faceplate of the EHNT card. For detailed
backplane pin information, see the 7342 ISAM FTTU Hardware Installation and
37.6
Status LEDs
The front panel contains light emitting diodes (LEDs) for port status, diagnostics of
power, the SFP ports, and the XFP ports. Figure 37-1 shows the front view of the
EHNT-A and Figure 37-2 shows the front view of the EHNT-B.

37-7
UNIT
Figure 37-1 Front view of EHNT-A

ALM PWR ACT
UNIT
EHNT
ALM PWR ACT
1 Gb E
LNK TX RX
1
2
3
4
10 GbE
1 Gb E
LNK TX RX
1
1
2
1 GbE-1
10 GbE
4
1
1 GbE-2
1 GbE-3
1 GbE-4
10 GbE-1
10 GbE-2
(XO)
18153
ALM PWR ACT
LNK TX RX
GE-1
UNIT
EHNT-B
ALM PWR ACT
LNK TX RX
GE-1
GE-2
GE-3
GE-4
10G
GE-3
GE-4
NETWORK
GE-2
10G
NETWORK
UNIT
Figure 37-2 Front view of EHNT-B
O&M
Tx
Rx
GE-1
GE-2
O&M
GE-3
GE-4
10G
19043
37-8

The port LEDs show the status of the 1-GE and 10-GE ports. The O&M port LEDs
on the EHNT-B card, indicate the out-of-band management traffic activity on the
ACU card (indicated by RX LED). Differing ports are labeled to the left of the LEDs,
but the LEDs show the same information for each. Table 37-3 provides information
about port LEDs.
Table 37-3 EHNT port LEDs
LED
Color
Display
Status
LNK
Green
OFF
No link detected at this port
ON
Link detected at this port
OFF
No data activity detected on this TX port
ON
Data activity detected on this TX port
OFF
No data activity detected on this RX port
ON
Data activity detected on this RX port
TX
Green
RX
Green
Table 37-4 provides information about diagnostic LEDs on the EHNT card.
Table 37-4 EHNT diagnostic LEDs
LED
Color
Display
Status
ALM
Red
ON
Card failure
PWR
Green
OFF
Power off
ON
Power on
1 s ON, 1 s OFF
Alive (boot SW)
Flashing at received packet

rate
Loading software
3.5 s ON, 0.5 s OFF
Software is running
OFF
Standby
ACT
Green
ON
One pulse
Active
(1)
Synchronizing
Note
(1)
37.7
One pulse is equal to 125 ms ON, 125 ms OFF, and exhibits a repetition rate of 2/s.
Power
The EHNT card is fed by two power branches (BATA and BATB) with a nominal
voltage of 48 V or 60 V and an operating range of 36 V dc to 72 V dc through
its backplane connector.
A fuse is provided to avoid damage to the PBA in case of short circuits. The fuse
rating is 4 A, slow blow.

37-9
A hot insertion circuit limits the in-rush current. An electromagnetic compatibility

(EMC) filter is provided to limit the noise coupled onto the battery (BAT) wires.
37.8
Table 37-5 lists the physical specifications of the EHNT card.
Table 37-5 EHNT physical specifications
37-10
Description
Specification (Vertical orientation)
Height
16.5 in. (42 cm)
Width
1.2 in. (3 cm)
Depth
8.7 in. (22 cm)
Weight
3.5 lb (1.59 kg)

38 EXNT-A and pluggable optical

modules unit data sheet
38.1 Identification
38-2

38-5

38.6 Status LEDs
38.7 Power
38-4
38-5
38-6
38-6
38-7
38-8

38-1
38.1
Identification
Table 38-1 provides identification information about EXNT-A and the associated
pluggable optical modules.
Table 38-1 Identification of EXNT-A and the associated optical modules
Part number
Mnemonic
Description
CLEI
CPR
ECI/Bar
code
Application
3FE 51230 AA
EXNT-A
Ethernet XAUI based

(extreme-capacity)
version A
BVL3ADHBAA
070MXD
156646
BVL3ADXBAA
070PCT
161636
(for OLTS-M shelf only)

3FE 51230 AB
EXNT-A
Ethernet XAUI based

(extreme-capacity)
version A, temperature
hardened
(for OLTS-M shelf only)
3FE 51026 AA
1-GE SFP, electrical, 100 m

(328 ft), not temperature
hardened (Commercial
range -5C to +50C (23F to
122F)) (1) (2) (3)
BVL3AA5BAA
U73174
146295
3FE 25772 AA
1-GE SFP (upstream), 1310

nm transmit, 1490 nm
+65C (-40F to 149F)) (1)
VAUIAGUAAA
U72812
137841
3FE 25772 AB
1-GE SFP (downstream),

1490 nm transmit, 1310 nm
+65C (-40F to 149F)) (1)
VAUIAGVAAA
U72813
137842
3FE 25773 CA
1-GE SFP, 850 nm,

multimode fiber (MMF),
0.85 m (850 nm), 550 m
(1804 ft) (4), not
+50C (23F to 122F)) (1) (3)
BVLIJ0TFAA
U72534
136282
SX
compliant with 802.3z

1000BASE-SX PMD
275 m with 62.5 uM
MMF (200 MHz * km @
850nm fiber)
550 m with 50 uM MMF
(500 MHz * km @ 850nm
fiber)
(1 of 3)
38-2

Part number
Mnemonic
Description
CLEI
CPR
ECI/Bar
code
Application
3FE 25774 AA
1-GE SFP, 1310 nm, single

mode fiber (SMF), 6.21 mi
(10 km), temperature
hardened (Industrial range
-40C to +65C (-40F to
149F)) (1) (3)
VAUIAEYAAA
U72496
135567
LX10
3FE 25775 AA

24.85 mi (40 km),
+65C (-40F to 149F)) (1) (3)
VAUIAE0AAA
U72498
135569
EX
3FE 25776 AA

49.71 mi (80 km),
+65C (-40F to 149F)) (1) (3)
VAUIAF2AAA
U72742
136958
ZXU
3FE 25776 BA

49.71 mi (80 km), not
+50C (23F to 122F)) (1) (3)
VAUIAEZAAA
U72497
135568
ZXU
3FE 25772 AB
1-G SFP, 1490 nm Tx, 1310

nm Rx, SMF, 6.2 mi (10 km),
temperature hardened (1) (3)
VAUIAGUAB
U72813
137842
3FE 50712 AA
10-GE XFP, 850 nm, MMF,

984 ft (300 m) (5), not
+50C (23F to 122F)) (1) (3)
BVLIJ0UFAA
U72906
139338
SR
3FE 50712 BA

6.21 mi (10 km), not
+50C (23F to 122F)) (1)
BVL3AALBAA
U73047
142249
LR
3FE 50712 BB

6.21 mi (10 km),
+65C (-40F to 149F)) (1) (3)
VAUIAMHAAA
U73591
154615
LR
3FE 50712 CA

24.85 mi (40 km), not
+50C (23F to 122F)) (1) (3)
BVL3AAMBAA
U73048
142250
ER
3FE 50712 CB

24.85 mi (40 km),
+65C (-40F to 149F)) (1) (3)
BLV3AA9BAA
U73263
148225
ER
3FE 50712 DA

49.71 mi (80 km), not
+50C (23F to 122F)) (1) (3)
(2 of 3)

38-3
Part number
Mnemonic
Description
CLEI
CPR
ECI/Bar
code
Application
3EM 19465 AA
10-GE XFP, electrical, 0.3

m, temperature hardened
(for EHNT-A only)
+65C (-40F to 149F)) (1)
1AB 35663 00XX

(Refer to
Table 37-2)
10-GE XFP, 100GHz DWDM,

SMF, 49.71 mi (80 km), not
+50C (23F to 122F)) (1) (3)
(Refer to
Table 37-2)
(Refer to
Table 37
-2)
(Refer to
Table 37
-2)
(3 of 3)
Notes
(1)
Do not use unauthorized SFPs or XFPs. Using unauthorized SFPs and XFPs adversely affects the P-OLT, may cause an
unexpected NT reset, and requires operator intervention to fix.
(2)
Use shielded CAT5e-grade or better Ethernet cables with electrical SFPs or XFPs.
(3)
The EXNT-A AA variant does not support these SFPs or XFPs.
(4)
The reach assumes 50 m MMF.
(5)
The reach assumes 50 m MMF, 2000 MHz/km.
38.2

The EXNT-A card mounts in the network termination slots (NT-A and NT-B) of the
optical line termination (OLTS-M) shelf.
The EXNT-A card supports:
up to 16000 media access control (MAC) address entries with hardware assisted
aging
up to 2000 IP address entries on the EXNT-A card
up to 993 routes on the EXNT-A card
IEEE 802.3x flow control at full duplex
network timing requirements for BITS I/F logic
IEEE 1588v2 Precision Timing Protocol (PTP)
The card provides:
gigabit Ethernet (GE) optical connectivity to a high-bandwidth Internet protocol
(IP) services network

pluggable SFP and XFP modules for GE optical connectivity
management and control interfaces for the 7342 ISAM FTTU
200 Gb switch matrix
XAUI and eHCL interfaces per line termination (LT) card
10 GE XAUI link to each GLT4-x card

2.5 GE eHCL link to each GLT2-C card
38-4
four XAUI links with the peer NT card

one XAUI link to the ACU card
two 1-GE SFP network ports
two 10-GE XFP network ports
network synchronization of the NT system clock

BITS/SETS
1588v2 PTP
diagnostic light emitting diodes (LEDs) per port
Note The EXNT-A card is not pre-equipped with optical ports.
The base unit has an operating temperature of 40F to 149F (40C
to 65C). Different versions of optical pluggable modules are
available for each port, some of which provide extended temperature
operation.
38.3
General description
The EXNT-A card is an NT subsystem that provides GE optical connectivity to a
high-bandwidth IP services network.
The EXNT-A card has two 1-GE SFP ports and two 10-GE XFP ports for
connectivity to a high-bandwidth IP services network. Any one or a combination of
the network connections can be used, depending on expected capacity. Connectivity
to the other NT card in a redundant system is accomplished through a XAUI interface
in the backplane of the OLTS-M shelf.
In addition to providing network termination, the EXNT-A card performs Ethernet
switching and provides the control and management functions of the
7342 ISAM FTTU. The EXNT-A card manages the P-OLT, the shelf, and the
switching data path.
The EXNT-A card manages high-bandwidth IP services for subscribers by providing
a 200 Gb/s Ethernet switching matrix. In the downstream direction, high-bandwidth
IP services enter the network termination side of the 7342 ISAM FTTU over optical
connectivity at the EXNT-A card. The EXNT-A card switches the IP traffic. The
appropriate packets for each connected subscriber are then forwarded over the
backplane to an LT unit. In the upstream direction, the EXNT-A card receives
Ethernet packets from the LT units over the backplane. The EXNT-A card switches
the packets to the high-bandwidth IP services network.
The EXNT-A card supports inband management traffic received through its
connectors. Local management through a craft terminal is supported by the EXNT-A
card through craft connections on the alarm control unit (ACU).
The EXNT-A card can be managed by three types of user network element
management interfaces:
5526 AMS
5528 WAM
local command line interface (CLI and TL1) on the ACU
38.4

See Section 43.4 of the NT card unit data sheet for information on network interface
modules.

38-5
38.5

The EXNT-A supports the LC/UPC connector for connection to the external optical
network.
The EXNT-A supports the following connectors for the required optical modules
that are Alcatel-Lucent-approved:
two 1000Base-X SFP connectors for gigabit Ethernet optical connectivity

two 10-GE network XFP connector
These connectors are located on the faceplate of the EXNT-A card. For detailed
backplane pin information, see the 7342 ISAM FTTU Hardware Installation and
38.6
Status LEDs
The front panel contains light emitting diodes (LEDs) for the individual 1 GE and 10
GE port status, ACU LAN port status, card alarm indication, and NT operational
state. Figure 38-1 shows the front view of the EXNT-A.
ALM PWR ACT
LNK TX RX
GE-1
10G1
10G2
UNIT
NETWORK
GE-2
EXNT-A
ALM PWR ACT
LNK TX RX
GE-1
GE-2
10G1
10G2
NETWORK
UNIT
Figure 38-1 Front view of EXNT-A
O&M
Tx
Rx
GE-1
O&M
GE-2
10G-1
GE-4
10G-2
19445
Table 38-2 defines the UNIT LEDs on the EXNT-A card.
38-6


Table 38-2 EXNT-A UNIT LEDs
LED
Color
Display
Status
ALM
Red
ON
Card failure
PWR
Green
OFF
Power off (no power on board)
ON
Power on
1 s ON, 1 s OFF
Alive (boot SW)
Flashing at received packet

rate
Loading software
3.5 s ON, 0.5 s OFF
Software is running
OFF
Standby NT
ON
Active NT
One pulse (1)
Synchronizing
ACT
Green
Note
(1)
One pulse is equal to 125 ms ON, 125 ms OFF, and exhibits a repetition rate of 2/s.
The NETWORK LEDs indicate the status and traffic flow of the 1-GE (GE-1 and
GE-2) and the 10-GE (10G1 and 10G2) ports. The O&M LEDs indicate the
out-of-band management traffic activity at the LAN connector on the ACU card.
Differing ports are labeled to the left of the LED group, but the LEDs show the same
information for each. Table 38-3 provides information about the NETWORK and
O&M LEDs.
Table 38-3 NETWORK and O&M LEDs
LED
Color
Display
Status
LNK
Green
OFF
No link detected at this port
ON
Link detected at this port
OFF
No data activity detected on this TX port
ON
Data activity detected on this TX port
OFF
No data activity detected on this RX port
ON
Data activity detected on this RX port
TX
RX
38.7
Green
Green
Power
The EXNT-A card is fed by two power branches (BATA and BATB) with a nominal
voltage of 48 V or 60 V and an operating range of 40.5 V dc to 72 V dc through
its backplane connector.
A hot insertion circuit limits the in-rush current. An electromagnetic compatibility
(EMC) filter is provided to limit the noise coupled onto the battery (BAT) wires.

38-7
38.8
Table 38-4 lists the physical specifications of the EXNT-A card.
Table 38-4 EXNT-A physical specifications
38-8
Description
Specification (Vertical orientation)
Height
16.5 in. (42 cm)
Width
1.2 in. (3 cm)
Depth
8.7 in. (22 cm)
Weight
3.5 lb. (1.59 kg)

39.1 Identification
39-2

39-2
39-4

39-2
39-1
39.1
Identification
Table 39-1 provides identification information about FILT-A and FILT-B.
Table 39-1 Identification of FILT-A and FILT-B
Part number
Mnemonic
Description
CLEI
CPR
ECI/Bar
code
3EM 17820 AA
FILT-A
Battery filter adapter

card
3FE 51428 AA
FILT-B

card
3FE 51428 AB
FILT-B

card
39.2

The FILT-A and FILT-B provide:
filtering for the dc mains, bolted onto the power connectors of the ALTS-N and
OLTS-M shelf in the shelf power input area
three battery filter caps, one each for BAT_A-FG, BAT_B-FG, and
BAT_RET-FG or BAT_RET-EG
CE Mark, EN55022, and EN300386 EMC compliance
39.3
General description
In the shelf power input area, the FILT-A or FILT-B are installed on the Battery A,
Battery B, and Battery Return power connectors of the ALTS-N or OLTS-M shelf.
The FILT-A or FILT-B filters the dc mains on the shelf. Figure 39-1 shows the
FILT-A on the backplane of the shelf. The FILT-B is not shown, since the FILT-B
is always part of the backplane assembly of the OLTS-M shelf.
39-2


Figure 39-1 FILT-A on the ALTS-N backplane
Short male/female
External tooth
standoff
lockwasher
External tooth
lockwasher
M5 locknuts
Long male/female
standoff
FILT PBA
Split
lockwasher
Hex nut
M3 flat
washer
Hex nut
Split
lockwasher
M3X10 MM
captive screw
Power
connection
Split
lockwasher
Hex nut
Protective cover
18177
Shelf power distribution

The shelf and the integrated fan are powered from the TRU using two redundant
branches A and B in a 2-wire or 3-wire configuration.
Power and grounding signals

Table 39-2 describes information about signal identification.
Table 39-2 Signal identification
Signal name
Description
BATA
BATB
BATRET
EG
Electrical ground
FG
Shelf frame ground
A 2-wire configuration has the same three power cables, but no separate grounding.
Grounding is provided through the BATRET cable, when the two Faston bridges are
equipped on the backplane, one in the LT area and one in the fan area.
A 3-wire configuration has three power cables (BATA, BATB, and BATRET) and a
separate grounding (frame ground) provided by the mechanical connection with the
rack.

39-3
The power signals BATA, BATB, and BATRET are distributed through the
backplane and feed the cards and the fan unit.
Three battery filter caps are provided on the FILT-A and FILT-B, one each for
BAT_A-FG, BAT_B-FG, and BAT_RET-FG or BAT_RET-EG.
39.4
The FILT-A or FILT-B kit contains male/female standoffs, lock washers, nuts, and
other hardware needed to install the FILT-A or FILT-B on the backplane power
connectors. See the 7342 ISAM FTTU Hardware Installation and Maintenance
Practices for installation instructions.
Figure 39-2 shows the caution label on the backplane of the shelf.
Figure 39-2 Caution label on the shelf backplane
Ene
rgy
Haz
ard
18176
Tables 39-3 and 39-4describes the physical specifications of the FILT-A or FILT-B
card.
Table 39-3 FILT-A physical specifications
Description
Specification
Height
1 in. (2.5 cm)
Width
4.8 in. (12.2 cm)
Depth
1.4 in. (3.5 cm)
Table 39-4 FILT-B physical specifications
39-4
Description
Specification
Height
1.49 in. (3.78 cm)
Width
5.91 in. (15.01 cm)
Depth
1.4 in. (3.5 cm)

40.1 Identification
40-2

40.4 Optical budgets
40.5 Status LEDs
40-2
40-4
40-4

40.7 Power
40-2
40-4
40-7
40-7

40-1
40.1
Identification
Table 40-1 provides identification information about the GLT2.
Table 40-1 Identification of GLT2
Part Number
Mnemonic
Description
CLEI
CPR
ECI/Bar
code
3FE 50385 AA
GLT2-A
GPON line termination with 2 PONS

asymmetric, eHCL, temperature hardened,
version A
BVNIRS0EAB
070BMU
145814
3FE 51039 AA
GLT2-B

asymmetric, eHCL, temperature hardened,
version B
BVNIRT0EAA
070EGZ
146791
3FE 51305 AA
GLT2-C

asymmetric, eHCL/XAUI, temperature
hardened, version C
BVNISV0EAA
070KAM
152707
40.2

Features and application notes specific to the GLT2 card include:
two PON interfaces that supports a maximum of 128 indoor or outdoor ONTs per
GLT2 card
two eHCL interfaces between the NT cards and each LT card with a throughput
capacity of 4 Gb/s (GLT2-A and GLT2-B)
LT communication interface to NT is determined by NT type (GLT2-C):
EXNT-A one XAUI lane (2.5 Gb/s) to NTA and NTB with a 5 Gb/s throughput
capacity
EHNT-B one eHCL lane (2 Gb/s) to NTA and NTB with a 4 Gb/s throughput
capacity
For features and application notes common to all LT cards, see Section 42.2 of
the LT card unit data sheet.
40.3
General description
The GLT2 is a line termination (LT) card that provides connectivity between the
network termination (NT) cards and the optical network terminals (ONTs). The LT
card is plugged in the P-OLT shelf, together with the two NT cards and an alarm
control unit (ACU). The LT cards and the NT cards perform the optical line
termination (OLT) function as specified in ITU G.984.1. The OLT is connected
through a single fiber to the ONTs.
40-2

The NT cards are central shelf controllers that provide two Ethernet switches. Each
NT is connected to an LT card by a communication link. Each LT card has redundant
communication links to the active and standby NT cards. GLT2-A and GLT2-B
cards support 2 Gb/s eHCL links. The GLT2-C can operate in one of two
communication modes, either 2 Gb/s eHCL or 2.5 Gb/s XAUI. The communication
mode is determined by the active NT card type. With EHNT cards the eHCL link
mode is used and with EXNT cards the XAUI link mode is used.
The eHCL/XAUI interface provides a point-to-point transmission to and from the
NT cards for network access, implementing an Ethernet packet-based interface. The
communication links support load sharing over the two redundant links. The eHCL
links support a throughput capacity of 4 Gb/s RX and TX and the XAUI links support
a throughput of 5 Gb/s RX and TX to the NTs to handle subscriber traffic.
The GLT2 card contains a media access controller (MAC) that provide the interfaces
towards the PON. The MAC transport channel is asymmetric with a 2.488 Gb/s line
rate downstream and a 1.244 Gb/s line rate upstream on the PON interface.
The GLT2 card contains a 12 Gb/s packet switch that supports Ethernet adaptation
for VLAN functions such as priority mapping, bridging and crossconnect,
processing, and destination port selection. The switch supports the processing of
voice, data, and IPTV video services.
There are three versions of the GLT2 cards: version A, version B and version C.
Table 40-2 describes the differences.
Table 40-2 GLT2-A, GLT2-B and GLT2-C differences
GLT2
features
GLT2-A
GLT2-B
GLT2-C
FEC
Downstream FEC
support. Upstream
FEC is not
supported.
Downstream and upstream

FEC support
Downstream and upstream

FEC support
Multicast
traffic rate
Multicast
capability which
limits the GLT2-A
to 2 Gb/s traffic
per GPON
interface.
Multicast capability which

allows the GLT2-B to
duplicate multicast streams
between both GPON
interfaces. This allows the
GLT2-B to surpass 4 Gb/s
towards both GPON
interfaces and achieve
maximum downstream line
rates (2.4 Gb/s).
Multicast capability which

allows the GLT2-C to
duplicate multicast streams
between both GPON
interfaces. This allows the
GLT2-C to surpass 4 Gb/s
towards both GPON
interfaces and achieve
maximum downstream line
rates (2.4 Gb/s)
Downstream
rate limiting
per ONT
Supported
Supported
Flow
mirroring
Supported
Supported
CVLAN
bridging
mode
Supported
Supported
PON
interface
connector
orientation
Up
Up
Down
(1 of 2)

40-3
GLT2
features
GLT2-A
GLT2-B
GLT2-C
LT to NT link
interface
eHCL
eHCL
eHCL and XAUI
(2 of 2)
40.4
Optical budgets
See Section 42.4 of LT card unit data sheet for information on optical budgets.
40.5
Status LEDs
The GLT2 front panel contains five LEDs indicating power and alarm status.
Table 40-3 describes the LEDs.
Table 40-3 GLT2 LEDs
LED
Description
Color
Display
Status
PWR
This LED indicates that

normal power is being
provided to the card.
Green
ON
Power on
OFF
Power off
1 s ON, 1 s OFF
Alive (booting software)
Flashing
Loading software
2.5 s ON, 1.5 s

OFF
Software is running
ON
Alarm is present on board
OFF
No alarm is present on
board
ON
Alarm is present on PON

facility. Indicates loss of
signal on PON.
OFF
No alarm present on PON

facility.
ALM
SF1
SF2
40.6

the card has a local
hardware failure present.
Red

the PON facility is in
Signal Fail mode.
Yellow

The GLT2 front panel has two SC/UPC connectors for interfaces to the PON. The
connecting fiber cable can be 1.6-mm, 2.0-mm or 3.0-mm single mode fiber cable.
Figure 40-1 shows the front view of the GLT2-A card.
40-4


Figure 40-1 Front view of the GLT2-A card
18146
Figure 40-2 shows the side view of the GLT2-A card and the card ejection handles.

40-5

Figure 40-2 Side view of the GLT2-A card
18147
The front panel contains status LEDs described in Section 40.5.
40-6

For additional information on interfaces and connections common to all LT cards,

see Section 42.6 of LT card unit data sheet.
40.7
Power
See Section 42.7 of LT card unit data sheet for information on power.
40.8
Table 40-4 describes the physical specifications of the GLT2 card.
Table 40-4 GLT2 physical specifications
Description
Specification
Height
16.5 in. (42 cm)
Width
0.98 in. (2.5 cm)
Depth
8.7 in. (22 cm)
Weight
2.0 lb (0.91 kg)

40-7
40-8

41.1 Identification
41-2

41.5 Status LEDs
41-2
41-3
41-3

41.7 Power
41-2
41-4
41-5
41-5

41-1
41.1
Identification
Table 41-1 provides identification information about the GLT4.
Table 41-1 Identification of GLT4
Part Number
Mnemonic
Description
CLEI
CPR
ECI/Bar
code
3FE 51034 AA
GLT4-A
GPON line termination with 4 PONs

hardened, fiber routing down
BVL3ACMBAA
070KCN
152823
3FE 51034 AC
GLT4-A

hardened, fiber routing down, RSSI
optics
BVL3AD7BAA
070KCN
162833
3FE 51034 AG
GLT4-A

hardened, fiber routing down, RSSI
optics
BVL3AGSBAA
070XBW
172867
41.2

The GLT4 card provides:
four PON interfaces that supports a maximum of 256 indoor or outdoor ONTs per
GLT4 card
RSSI capable optics on the AC and AG variants of the GLT4-A card and all later
generation LT cards
LT communication interface to NT is determined by NT type:
EXNT-A four XAUI lanes (10 Gb/s) to NTA and NTB with a 20 Gb/s throughput
capacity
EHNT-B one eHCL lane (2 Gb/s) to NTA and NTB with a 4 Gb/s throughput
capacity
For features and application notes common to all LT cards, see Section 42.2 of
the LT card unit data sheet.
41.3
General description
The GLT4 is a line termination (LT) card that provides connectivity between the
network termination (NT) cards and the optical network terminals (ONTs). The LT
card is plugged in the P-OLT shelf, together with the two NT cards and an alarm
control unit (ACU). The LT cards and the NT cards perform the optical line
termination (OLT) function as specified in ITU G.984.1. The OLT is connected
through a single fiber to the ONTs.
41-2

The NT cards are central shelf controllers that provide two Ethernet switches. Each
NT is connected to an LT card by a communication link. Each LT card has redundant
communication links to the active and standby NT cards. The LT card can operate in
one of two modes of communication, either the 2 Gb/s (eHCL) or the 10Gb/s (XAUI)
mode. The communication mode is determined by the active NT card type. When the
EHNT-B card type is detected, the 2 Gb/s operating mode is configured. When the
EXNT-A card type is detected, the 10 Gb/s operating mode is configured.
The communication interface provides a point-to-point transmission to and from the
NT cards for network access, implementing an Ethernet packet-based interface. The
communication links support load sharing over the two redundant links. The eHCL
links support a throughput capacity of 4 Gb/s RX and TX and the XAUI links support
a throughput capacity of 20 Gb/s RX and TX to the NTs to handle subscriber traffic.
The GLT4 card contains a media access controller (MAC) that provide the interfaces
towards the PON. The MAC transport channel is asymmetric with a 2.488 Gb/s line
rate downstream and a 1.244 Gb/s line rate upstream on the PON interface.
The GLT4 card contains a 12 Gb/s packet switch that supports Ethernet adaptation
for VLAN functions such as priority mapping, bridging and crossconnect,
processing, and destination port selection. The switch supports the processing of
voice, data, and IPTV video services.
The RSSI capable optics on the GLT4-A, AC and AG variants, provides the ability
to view a summary of the operational status of PON port optics. Using a TL1
command, the user can view a report of the receive and transmit optical power levels,
laser bias voltage and current, and the temperature of the optics module.
41.4
Optical budgets
See Section 42.4 of LT card unit data sheet for information on optical budgets.
41.5
Status LEDs
The GLT4 front panel contains six LEDs indicating power and alarm status.
Table 41-2 describes the LEDs.
Table 41-2 GLT4 LEDs
LED
Description
Color
Display
Status
PWR

normal power is being
provided to the card.
Green
ON
Power on
OFF
Power off
Blinking
Initialization
ON
Alarm is present on board
OFF
No alarm is present on
board
ALM

the card has a local
hardware failure present.
Red
(1 of 2)

41-3
LED
Description
Color
Display
Status
SF1

the PON facility is in
Signal Fail mode.
Yellow
ON
Alarm is present on PON

facility. Indicates loss of
signal on PON.
OFF
No alarm present on PON

facility.
SF2
SF3
SF4
(2 of 2)
41.6

The GLT4 front panel has four SC/UPC connectors for interfaces to the PON. The
connecting fiber cable can be 1.6-mm, 2.0-mm or 3.0-mm single mode fiber cable.
Figure 41-1 shows the front view of the card.
Figure 41-1 Front view of the GLT4 card
GLT4-A
PWR
ALM
2
3
PON SF
DANGER
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
PON4
PON3
PON2
PON1
AVOIDE DIRECT
EXPOSURE TO BEAM
19073
Figure 41-2 shows the side view of the card and the card ejection handles.
41-4


Figure 41-2 Side view of the GLT4 card
13760 13754
19074
The front panel contains status LEDs described in Section 41.5.

For additional information on interfaces and connections common to all LT cards,
see Section 42.6 of LT card unit data sheet.
41.7
Power
See Section 42.7 of LT card unit data sheet for information on power.
41.8
Table 41-3 describes the physical specifications of the GLT4 card.
Table 41-3 GLT4 physical specifications
Description
Specification
Height
16.5 in. (42 cm)
(1 of 2)

41-5
Description
Specification
Width
0.98 in. (2.5 cm)
Depth
8.7 in. (22 cm)
Weight
2.5 lb. (1.13 kg)
(2 of 2)
41-6

42.1 Identification
42-2

42.5 Status LEDs
42-2
42-3
42-4

42.7 Power
42-2
42-4
42-5
42-5

42-1
42.1
Identification
Table 42-1 identifies the sections that provide identification information specific to
each LT card type.
Table 42-1 LT card identification information
42.2
LT card
See
Identification of GLT2
Section 40.1
Identification of GLT4
Section 41.1

The LT card provides:
SC/UPC PON interface connector orientation either up or down for fiber routing
preference
a line rate of 2.488 Gb/s downstream and 1.244 Gb/s upstream
a 12 Gb/s packet switch
Ethernet adaptation that supports VLAN functions
reference clocks that generate PON clocks
an on-board controller (OBC) for control and status
the ability to be hot inserted or extracted
an operating temperature range of 40F to 149F (40C to 65C)
reach capacity of 18.6 miles (30 km)
For features and application notes specific to each LT card type, use Table 42-2 to
locate information.
Table 42-2 LT card features and application notes
42.3
LT card
See
GLT2
Section 40.2
GLT4
Section 41.2
General description
Table 42-3 identifies the sections that describe each LT card type.
42-2


Table 42-3 LT card general description
42.4
LT card
See
GLT2
Section 40.3
GLT4
Section 41.3
Optical budgets
Table 42-4 provides the optical budgets of the LT card.
Warning Operating equipment outside of its tested and
documented performance characteristics and causing an optical
overload may cause damage to equipment components, such as APD
receivers, affect service delivery, and void any component or system
warranties.
Table 42-4 Optical budgets of the LT card
Description
Minimum
Typical
Maximum
2488.32 Mbit/s
Transmitting budgets
TX nominal bit rate
2.488 Gb/s
TX central wavelength single fibre
1480 nm
1500 nm
Line code = Scrambled NRZ
Mask of TX eye diagram
Per G.984.2
Minimum ORL of ODN at Olu and Old
more than 32
At CO temperature, TX extinction ratio

(0C to +50C system inlet air
temperature)
8.2 dB
13.0 dB
At industrial temperature, TX extinction

ratio (40C to +65C system inlet air
temperature) (1)
6.0 dB
13.0 dB
At CO temperature, TX output power (0C

to +50C system inlet air temperature)
2.5 dBm
5.0 dBm
At industrial temperature, TX output

power (40C to +65C system inlet air
temperature) (1)
2.0 dBm
5.0 dBm
TX spectral width
< 1 nm
TX side mode suppression
30 dB
1244.16 Mbit/s
Receiving budgets
RX nominal bit rate
1.244 Gb/s
RX wavelength single and dual fibre
1260 nm
1360 nm
(1 of 2)

42-3
Description
Minimum
Typical
Maximum
Line code = Scrambled NRZ
Maximum reflectance of equipment,

measured at transmitter wavelength
less than -6 dB
less than -6 dB
less than -6 dB
Minimum ORL of ODN at Oru and Ord
more than 32
RX BER
1E10-10
RX optical sensitivity
28.0 dB
RX optical overload
8.0 dBm
Link distance
18.6 miles
(30 km)(2)
(2 of 2)
Notes
(1)
The operating temperature is restricted to the CO temperature range, unless FEC is enabled.
(2)
The optical link budget is defined by both loss and bandwidth characteristics. The loss
characteristic is determined by the difference between the optical transmitter and optical
receiver for each direction. Typically this is 28dB. The bandwidth characteristic is reflected by the
maximum link distance parameter of each OLT and ONT transmitter specification, and is limited
by the smaller of the upstream and downstream values. Typically the limiting link distance is
30 km.
42.5
Status LEDs
The front panel of an LT card contains LEDs indicating power and alarm status.
Table 42-5 identifies the sections that describe the LEDs specific to each LT card
type.
Table 42-5 LT card LEDs
42.6
LT card
See
GLT2 LEDs
Section 40.5
GLT4 LEDs
Section 41.5

Table 42-6 identifies the sections that describe the interfaces and connections
specific to each LT card type. The information that follows Table 42-6 is common to
all LT cards.
Table 42-6 LT card interfaces and connections
42-4
LT card
See
GLT2
Section 40.6
GLT4
Section 41.6

The front panel contains card ejection handles that can remove the LT card from the
OLT shelf. The LT cards provide hot insertion and removal capability. The LT cards
can be plugged in and removed from a live shelf without affecting the operation of
any other cards.
The LT card connections with external CO equipment are provided on the P-OLT
backplane. The connections include:
point-to-point eHCL and XAUI interfaces

special lines:
LT identification address lines
LT control/status lines
P-OLT related interfaces
The backplane connectors are female compliant press-fit connectors with 5-row
pinning and 2-mm pitch.
42.7
Power
The LT card is powered through the backplane of the P-OLT shelf at 48 V dc or
60 V dc.
42.8
Table 42-7 identifies the sections that describe the physical specifications of each LT
card type.
Table 42-7 LT card physical specifications
LT card
Specification
GLT2 physical specifications
Section 40.8
GLT4 physical specifications
Section 41.8

42-5
42-6

43.1 Identification
43-2

43-2

43.6 Status LEDs
43.7 Power
43-2
43-2
43-9
43-10
43-10
43-10

43-1
43.1
Identification
Table 43-1 identifies the sections that provide identification information specific to
each NT card type.
Table 43-1 NT card identification information
43.2
NT card
See
Identification of EHNT
Section 37.1
Identification of EXNT-A
Section 38.1

Table 43-2 identifies the sections that provide feature and application information
specific to each NT card type.
Table 43-2 NT card features and application notes
43.3
NT card
See
EHNT
Section 43.2
EXNT-A
Section 38.2
General description
Table 43-3 identifies the sections that describe each NT card type.
Table 43-3 NT card general description
43.4
NT card
See
EHNT
Section 37.3
EXNT-A
Section 38.3

Figure 43-1 shows the physical differences between an optical and electrical SFP.
43-2


Figure 43-1 Optical and electrical SFP module components
Optical SFP
Electrical SFP
Case temperature
probe point
Release clasp
Receiver (Rx)
Transmitter (Tx)
18389
Figure 43-2 shows an electrical SFP installed in an NT card port.

Figure 43-2 Electrical SFP in an NT card
UNIT
EHNT-B
ALM PWR ACT
LNK TX RX
GE-1
GE-2
GE-3
GE-4
10G
NETWORK
Electrical
SFP
O&M
Tx
Rx
GE-1
GE-2
GE-3
GE-4
10G
19251
Optical module power and modulation frequencies

Table 43-4 describes the power propagation and modulation frequencies of the
optical modules.
43-3

Table 43-4 Optical module specifications
Part number
Power propagation at optical port
Maximum modulation frequency
3FE 25773 CA
0.4 mW
1250 MHz
3FE 25774 AA
0.5 mW
1250 MHz
3FE 25775 AA
1.0 mW
1250 MHz
3FE 25776 AA
3.2 mW
1250 MHz
3FE 25776 BA
3.2 mW
1250 MHz
3FE 50712 AA
0.8 mW
10.31 GHz
3FE 50712 BA
1.1 mW
10.31 GHz
3FE 50712 BB
1.1 mW
10.31 GHz
3FE 50712 CA
2.5 mW
10.31 GHz
3FE 50712 CB
2.5 mW
10.31 GHz
Optical budgets
Table 43-5 describes the optical budgets for the 1-GE 850 nm SFP with a reach of
1804 ft (550 m).
Warning Operating equipment outside of its tested and
documented performance characteristics and causing an optical
overload may cause damage to equipment components, such as APD
receivers, affect service delivery, and void any component or system
warranties.
The 1-GE 850 nm SPF with MMF:
compliant with 802.3z 1000BASE-SX PMD

275 m with 62.5 uM MMF (200 MHz * km @ 850nm fiber)
550 m with 50 uM MMF (500 MHz * km @ 850nm fiber)
Table 43-5 Optical budgets for the 1-GE 850 nm 550 m SFP
Description
Minimum
Typical
Maximum
Tx nominal bit rate
1250 Mb/s
Tx central wavelength
820 nm
860 nm
Mask of Tx eye diagram
802.3
Tx mean launched optical power
9.5 dBm
4.0 dBm
Tx extinction ratio
9 dB
Tx spectral width (rms)
0.85 nm
Receiving budgets
(1 of 2)
43-4

Description
Minimum
Typical
Maximum
Rx nominal bit rate
1250 Mb/s
Rx wavelength
820 nm
860 nm
Rx BER
Less than 1E-12
Rx optical sensitivity
17 dBm
Rx optical overload
0 dBm
Link distance (50 um MMF)
0.31 mi (550 m)
(2 of 2)
6.21 mi (10 km).
Table 43-6 Optical budgets for the 1-GE 1310 nm 10 km SFP
Description
Minimum
Typical
Maximum
Tx nominal bit rate
1250 Mb/s
Tx central wavelength
1274 nm
1360 nm
Mask of Tx eye diagram
802.3
Tx mean launched optical power
9.5 dBm
3.0 dBm
Tx extinction ratio
9 dB
Tx spectral width (SMSR)
30 dB
Rx nominal bit rate
1250 Mb/s
Rx wavelength
1274 nm
1360 nm
Rx BER
Less than 1E-12
Rx optical sensitivity
20 dBm
Rx optical overload
3.0 dBm
Link distance (50 um MMF)
6.21 mi (10 km)
Receiving budgets
24.86 mi (40 km).
Description
Minimum
Typical
Maximum
TX nominal bit rate
1250 Mb/s
TX central wavelength
1280 nm
1335 nm
802.3
(1 of 2)

43-5
Description
Minimum
Typical
Maximum
TX mean launched optical power
4.5 dBm
0 dBm
TX extinction ratio
9 dB
TX spectral width (SMSR)
30.0 dB
RX nominal bit rate
1250 Mb/s
RX wavelength
1280 nm
1335 nm
RX BER
Less than 1E-12
22 dBm
RX optical overload
3.0 dBm
Link distance (G.652 SMF)
24.86 mi
(40 km)
Receiving budgets
(2 of 2)
49.71 mi (80 km), temperature hardened.
Description
Minimum
Typical
Maximum
TX nominal bit rate
1250 Mb/s
1500 nm
1580 nm
802.3
0 dBm
+5 dBm
TX extinction ratio
9 dB
30.0 dB
RX nominal bit rate
1250 Mb/s
RX wavelength
1500 nm
1580 nm
RX BER
Less than 1E-12
24 dBm
RX optical overload
3.0 dBm
49.71 mi
(80 km)
Receiving budgets
Table 43-9 describes the optical budgets for the 1-GE 1550 nm SFP and a reach of
49.71 mi (80 km), not temperature hardened.
43-6


Description
Minimum
Typical
Maximum
TX nominal bit rate
1250 Mb/s
1540 nm
1570 nm
802.3
0 dBm
+5 dBm
TX extinction ratio
9 dB
30.0 dB
RX nominal bit rate
1250 Mb/s
RX wavelength
1540 nm
1570 nm
RX BER
Less than 1E-12
24 dBm
RX optical overload
0 dBm
49.71 mi
(80 km)
Receiving budgets
Table 43-10 describes the optical budgets for the 10-GE 850 nm XFP with a reach of
984 ft (300 m).
Table 43-10 Optical budgets for the 10-GE 850 nm 300 m XFP
Description
Minimum
Typical
Maximum
TX nominal bit rate
10 Gb/s
840 nm
860 nm
802.3
4.0 dBm
1.1 dBm
TX extinction ratio
3 dB
TX spectral width (rms)
0.45 nm
RX nominal bit rate
10 Gb/s
RX wavelength
840 nm
860 nm
RX BER
Less than 1E-12
9.9 dBm
RX optical overload
1.0 dBm
Link distance (50 um 2 GHz)
984 ft (300 m)
Receiving budgets

43-7
Table 43-11 describes the optical budgets for the 10-GE 1310 nm XFP with a reach
of 6.21 mi (10 km).
Table 43-11 Optical budgets for the 10-GE 1310 nm 10 km XFP
Description
Minimum
Typical
Maximum
TX nominal bit rate
10 Gb/s
1290 nm
1330 nm
802.3
8.2 dBm
0.5 dBm
TX extinction ratio
3.5 dB
30 dB
RX nominal bit rate
10 Gb/s
RX wavelength
1290 nm
1330 nm
RX BER
Less than 1E-12
14.4 dBm
RX optical overload
0.5 dBm
6.21mi (10 km)
Receiving budgets
of 24.86 mi (40 km).
Description
Minimum
Typical
Maximum
TX nominal bit rate
10 Gb/s
1530 nm
1565 nm
802.3
4.7 dBm
4.0 dBm
TX extinction ratio
3 dB
30 dB
RX nominal bit rate
10 Gb/s
RX wavelength
1530 nm
1565 nm
RX BER
Less than 1E-12
15.8 dBm
RX optical overload
1.0 dBm
Receiving budgets
(1 of 2)
43-8

Description
Minimum
Typical
Maximum
24.86 mi
(40 km)
(2 of 2)
of 49.71 mi (80 km).
Description
Minimum
Typical
Maximum
TX nominal bit rate
10 Gb/s
1530 nm
1550 nm
1565 nm
802.3
0 dBm
+ 4.0 dBm
TX extinction ratio
9 dB
30 dB
RX nominal bit rate
10 Gb/s
RX wavelength
1270 nm
1600 nm
RX BER
Less than 1E-12
24 dBm
RX optical overload
7.0 dBm
49.71 mi
(80 km)
Receiving budgets
43.5

Table 43-14 identifies the sections that describe the interfaces and connections
specific to each NT card type.
Table 43-14 NT card interfaces and connections
NT card
See
EHNT
Section 37.5
EXNT-A
Section 38.5

43-9
43.6
Status LEDs
The front panel of an NT card contains LEDs indicating power and alarm status.
Table 43-15 identifies the sections that describe the LEDs specific to each NT card
type.
Table 43-15 NT card LEDs
43.7
NT card
See
EHNT
Section 37.6
EXNT-A
Section 38.6
Power
Table 43-16 identifies the sections that describe the power information specific to
each NT card type.
Table 43-16 NT card power information
43.8
NT card
See
EHNT
Section 37.7
EXNT-A
Section 38.7
Table 43-17 identifies the sections that describe the physical specifications of each
NT card type.
Table 43-17 EHNT physical specifications
43-10
NT card
See
EHNT
Section 37.8
EXNT-A
Section 38.8

44.1 Identification
44-2

44-3
44-5

44-2
44-1
44.1
Identification
Table 44-1 provides identification information about the OLT rack assembly.
Table 44-1 Identification of the OLT rack assembly
Part number
Mnemonic
Description
CLEI
CPR
ECI/bar code
3AP 60332 CB
prewired OLT rack assembly with one

ALTS-N shelf, one ATRU-N TRU, and
one AFAN-H fan unit with fan filter
3AP 60432 CB
prewired OLT rack assembly with two

ALTS-N shelves, one ATRU-N TRU, and
two AFAN-H fan units with fan filters
3AP 60332 EB
prewired OLT rack assembly with one

ALTS-N shelf, one ATRU-M TRU, and
one AFAN-H fan unit with fan filter
3AP 60432 EB
prewired OLT rack assembly with two

ALTS-N shelves, one ATRU-M TRU, and
two AFAN-H fan units with fan filters
3FE 51459 AA
2200 mm rack with one OLTS-M shelf
The pre-assembled rack is equipped

with one OLTS-M shelf, the TRU, the
AFAN, and cable harnesses.
3FE 51459 AB
2200 mm rack with two OLTS-M shelves

with two OLTS-M shelves, the TRU, the
AFAN, and cable harnesses.
3FE 51459 AG
Customer specific 2200 mm rack with

one OLTS-M shelf
with one OLTS-M shelf, the TRU, the
AFAN, a rack door for the shelf (3FE
51520 AA), and cable harnesses.
44.2

The OLT rack assembly:
is preinstalled with either one or two P-OLT ALTS-N or OLTS-M shelves that
have an AFAN-H or AFAN-S fan unit installed with filters
is preinstalled with either an ATRU-M, ATRU-N, ATRU-U, or GTRU-B top
rack unit (TRU) providing redundant power distribution for up to two shelves,
power circuit breakers, fan failure fuses, and telco alarm distribution
support for 48 V dc or 60 V dc
supports alarm connection to the shelves
44-2

44.3
General description
The OLT rack is:
UT-9 rack, 600 mm wide and 2200 mm high, that has 25 mm drill holes for
mounting equipment to install a maximum of two ALTS-N or OLTS-M shelves.
Each rack accomodates one TRU.
19-in. rack, used in the Asia-Pacific (APAC) market, 482.6 mm wide and 1800
mm high to install a maximum of two OLT-M shelves, that has 36U vertical
equipment aperture per IEC 60297-1 or 1550 mm vertical equipment aperture per
IEC 917-2. Each rack accomodates one TRU.
Note 1 One P-OLT system consists of a single ALTS-N or
OLTS-M shelf that is populated with the plug-in units and

components that comprise a P-OLT. See the ALTS-N or OLTS-M
unit data sheet for more information.
Note 2 The TRU distributes redundant power for the shelves, as
well as provides circuit breakers, fan fuse, and telco alarm
connections. See the unit data sheets for the ATRU-N, OLTS-M,
ATRU-M, ATRU-U, or GTRU-B for more information.
Table 44-2 describes the various OLT rack configurations.

Table 44-2 OLT rack assembly components list
OLT rack assembly
part number
Components list
Quantity
Description
Part number
3AP 60332 EB
UT-9 rack, 600 mm wide and 2200 mm

high, with 25 mm drill holes for
mounting equipment
3FE 20145 AA
ATRU-M TRU
3EC 17422 AA
AFAN-H fan unit with fan filter
3EC 37533 AB

mounting equipment
3FE 20145 AA
ATRU-M TRU
3EC 17422 AA
3EC 37533 AB

mounting equipment
3FE 20145 AA
ATRU-N TRU
3EC 17422 CD
3EC 37533 AB
3AP 60432 EB
3AP 60332 CB
(1 of 3)

44-3
OLT rack assembly

part number
Components list
Quantity
Description
Part number
3AP 60432 CB

mounting equipment
3FE 20145 AA
ATRU-N TRU
3EC 17422 CD
3EC 37533 AB

mounting equipment
3FE 20145 AA
One OLTS-M shelf
3FE 51459 AA
ATRU-U TRU
3FE 51410 AA
AFAN-S fan unit with fan filter
3FE 51461 AA

mounting equipment
3FE 20145 AA
Two OLTS-M shelves
3FE 51459 AA
ATRU-U TRU
3FE 51410 AA
3FE 51461 AA

mounting equipment
3FE 20145 AA
One OLTS-M shelf
3FE 51459 AA
ATRU-U TRU
3FE 51410 AA
3FE 51461 AA
Rack door
3FE 51520 AA

mounting equipment
3FE 20145 AA
Two OLTS-M shelves
3FE 51459 AA
ATRU-U TRU
3FE 51410 AA
3FE 51461 AA
Rack door
3FE 51520 AA

mounting equipment
3FE 20145 AA
One OLTS-M shelf
3FE 51459 AA
GTRU-B TRU
3FE 51410 AB
3FE 51461 AA
3FE 51459 AA
3FE 51459 AB
3FE 51459 AG
3FE 51459 AH
3FE 51459 BA
(2 of 3)
44-4

OLT rack assembly

part number
Components list
Quantity
Description
Part number
3FE 51459 BB

mounting equipment
3FE 20145 AA
Two OLTS-M shelves
3FE 51459 AA
GTRU-B TRU
3FE 51410 AB
3FE 51461 AA

mounting equipment
3FE 20145 AA
One OLTS-M shelf
3FE 51459 AA
GTRU-B TRU
3FE 51410 AB
3FE 51461 AA
Rack door
3FE 51520 AA

mounting equipment
3FE 20145 AA
Two OLTS-M shelves
3FE 51459 AA
GTRU-B TRU
3FE 51410 AB
3FE 51461 AA
Rack door
3FE 51520 AA
3FE 51459 BG
3FE 51459 BH
(3 of 3)
44.4
Table 44-3 describes the physical specifications of the ETSI racks.
Table 44-3 Physical specifications of ETSI racks
Description
Specification
3AP 60332 CB
Height
90.95 in. (231 cm)
Width
29.13 in. (74 cm)
Depth
22.05 in. (56 cm)
Weight
339.51 lb (154 kg)
3AP 60432 CB, 3FE 51459 AA, 3FE 51459 AB, 3FE 51459 AG, 3FE 51459 AH, 3FE 51459 BA, 3FE
51459 BB, 3FE 51459 BG, 3FE 51459 BH
Height
90.95 in. (231 cm)
Width
29.13 in. (74 cm)
Depth
22.05 in. (56 cm)
(1 of 2)

44-5
Description
Specification
Weight
379.20 lb (172 kg)
3AP 60332 EB
Height
86.61 in. (220 cm)
Width
26.77 in. (68 cm)
Depth
16.93 in. (43 cm)
Weight
235.9 lb (107 kg)
3AP 60432 EB
Height
90.95 in. (231 cm)
Width
29.13 in. (74 cm)
Depth
22.05 in. (56 cm)
Weight
379.42 lb (172.1kg)
(2 of 2)
44-6

45.1 Identification
45-2

45-3
45.4 Backplane connectors and cables

45.5 Physical location identification
45.6 Power distribution
45-6
45.7 Thermal limitation
45-7
45-2
45-5
45-6
45-12

45-1
45.1
Identification
Table 45-1 provides identification information about OLTS-M.
Table 45-1 Identification of OLTS-M
Part number
Mnemonic
Description
CLEI
CPR
ECI/Bar code
3FE 51410 AA
OLTS-M
19 inch line termination shelf,

version M
BVM5X00CRA
211349
454738
3FE 51488 AA
19 in. mounting ear - left
3FE 51489 AA
19 in. mounting ear - right
3FE 51490 AA
ETSI mounting ear - left
3FE 51491 AA
ETSI mounting ear - right
45.2

The OLTS-M shelf provides:
front access shelf in which the P-OLT components install

mounting locations for NT, LT and AACU cards:
2 NT cards
1 AACU card
14 LT cards
terminals for connecting 48 V dc or 60 V dc Battery A and Battery B power
feeds
FILT card installed with battery filter caps that mount on the shelf power input
terminals for CE Mark, EN55022, and EN300386 EMC compliance
SMAC card to provide MAC ID addresses for the NE
BITS-B card that provides:
BITS clock termination

LAN interface
10 Gbps XAUI links between NTs and LTs, as well as between NTs and the ACU
for future use
HighGig backplane interconnection between NT cards

integrated fiber management tray at the bottom of the shelf
shelf is rack mountable in either a 19 in. rack or a UT-9 rack for deployment in a
CO or CEV
45-2

45.3
General description
The OLTS-M optical line termination (OLT) shelf is the 19 in. rack mountable frame
in which the cards and other units that comprise the P-OLT are installed. The shelf
mounts in the OLT rack for CO or CEV installations. Depending on the mounting
ears that are ordered, the OLT rack can be either a 19 in. wide, 300 mm or UT-9 rack,
600 mm wide for mounting equipment. See the OLT rack unit data sheet for more
information.
Note Due to thermal limitations, you can install a maximum of two
P-OLT shelves plus one TRU unit in a UT-9 rack, even though three
shelves plus the TRU unit can physically fit in to the same rack.
The OLTS-M shelf has three main areas:
power and shelf connector area (upper area)

card cage (center area)
cable routing tray (lower area)
The OLTS-M shelf supports the following NT and LT cards:
EHNT-B
EXNT-A
GLT4-A
Figure 45-1 shows an OLTS-M shelf, with 19 in. mounting ears, populated with
P-OLT components.

45-3

Figure 45-1 OLTS-M shelf with P-OLT cards and 19in. mounting ears
19.0158
18.3110
17.2334
11.1181
GLT4-A
EHNT-B
2
3
PON SF
PON SF
PON SF
PON SF
PON SF
PON SF
ALM
PON SF
PWR
ALM
PON SF
PWR
ALM
PON SF
PWR
ALM
LNK TX RX
GE-1
GE-2
GE-3
GE-4
10G
CRI
MAJ
MIN
ALM
ACO
ALM PWR ACT
LNK TX RX
GE-1
GE-2
GE-3
GE-4
10G
O&M
Rx
DANGER
DANGER
DANGER
DANGER
DANGER
GLT4-A
PWR
PWR
ALM
ALM
ALM
2
3
2
3
2
3
2
3
2
3
Rx
GE-1
DANGER
DANGER
DANGER
DANGER
DANGER
DANGER
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON3
PON3
PON3
PON3
PON4
PON4
PON4
PON4
PON2
PON3
PON4
PON2
PON3
PON4
PON2
PON2
CRAFT
PON2
PON3
PON4
PON2
PON3
PON4
PON2
PON3
PON4
PON2
PON3
PON4
PON2
PON3
PON4
PON2
PON3
PON4
10G
PON3
GE-4
10G
PON3
GE-4
PON4
PON2
GE-3
PON4
PON2
GE-2
PON2
GE-2
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
ETHERNET
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
INVISIBLE LASER
RADIATION WHEN
DISCONNECTED
GE-3
PON2
GLT4-A
PWR
ALM
AVOIDE DIRECT
EXPOSURE TO BEAM
PON1
PON1
24.4646
DANGER
GLT4-A
PWR
ALM
Tx
GE-1
DANGER
GLT4-A
PWR
O&M
Tx
DANGER
GLT4-A
EHNT-B
AACU-C
ALM PWR ACT
PON SF
GLT4-A
PWR
ALM
PON SF
GLT4-A
PWR
ALM
PON SF
GLT4-A
PWR
ALM
PON SF
GLT4-A
PWR
ALM
PON SF
GLT4-A
PWR
ALM
UNIT
GLT4-A
PWR
NETWORK
GLT4-A
BAT B
UNIT
GLT4-A
BAT A
NETWORK
BATRET
19321
The card cage is the large central area of the shelf that accommodates plug-in cards
that are 16.53 in. (42 cm) in height and 8.66 in. (22 cm) in depth. From left to right,
there are 9 LT card slots (LT 1 through LT 9), 1 NT slot (NTA), 1 ACU slot, 1 NT
slot (NTB), and 5 LT slots (LT 10 through LT 14). To maintain air flow and EMI
integrity, blank filler panels must be installed in any empty slot in the card cage area.
The topmost area of the shelf is the power and shelf connector area, which provides
the following:
45-4
shelf power connections from the TRU

BITS interface and remote Ethernet connectors
craft 2 interface connector
shelf alarm connection to TRU
fan alarm connector
SMAC card

45.4
Backplane connectors and cables

The backplane interconnects the cards, the eHCL bus interface, the XAUI bus
interfaces, external interfaces, and other rack equipment. Input power terminals are
located on the externally accessible section of the backplane, which is the topmost
section; see Figure 45-1.
The shelf identification jumpers are located on the backplane in the area of the NTA
connectors. The jumpers can only be accessed when there are no cards installed in
the shelf.
Power is distributed to the installed units in the shelf over the backplane. Cards
installed in the card cage are supplied with redundant (A and B) power feeds from
the TRU over the shelf backplane. Shelf power circuit breakers are located on the
TRU at the top of the rack.
Figure 45-2 shows the backplane of the OLTS-M. The connectors that appear in the
topmost section are externally accessible from the front of the shelf.
Figure 45-2 OLTS-M backplane
Shelf Power
Terminals
BITS
LAN
Craft 2 Alarm
Interface
Fan
Alarm
BATRET
BAT A
BAT B
SMAC
Shelf ID
19339
Table 45-2 provides information about the backplane connectors and related cables.

45-5

Table 45-2 Backplane connectors and related cables
Connector
Function
Type
Related cables
FILT-B terminals
Shelf power (BATA, BATB, BATRET)
Cable Lug M5
6 mm2 (3x)
LAN (on BITS-B

card)
10/100 Mbps Ethernet port
RJ45
BITS (on BITS-B

card)
BITS primary and BITS secondary signal input
RJ45
ALARMS (J64)
Alarm interface cable to TRU
DSUB 50 pins
3FE 51529 AA
3FE 51529 AB
CRAFT 2
INTERFACE (J23)
Remote Craft Interface
DSUB 9 pins
3EC 16028 xx AA
FAN_ALM (J25)
Fan shelf alarm interface
2x5 ribbon connector
Part of power harness
SMAC (J22)
SMAC card connector
Shelf ID (J63)
Physical location identification jumper

settings
Jumper connectors
45.5
Physical location identification

The OLTS-M shelf provides the physical location identification (PLID) setting. This
requires 21 PLID bits for ultra-density equipment.
The jumpers are placed on the backplane in two columns between the LT-9 and the
NTA slots.
45.6
Power distribution
The shelf receives redundant power from the TRU. The TRU provides redundant
power, A and B, to the shelf and frame ground for the rack. In the three-wire
configuration, there are three power cables (BATA, BATB, and BATRET) and a
separate frame ground wire. In the two-wire configuration, frame ground is provided
via the BATRET cable.
The power signals BATA, BATB and BATRET is distributed via the backplane and
feed the plug-in units. Power must be supplied to the A and B power source at startup
(boot time) or the system will not initialize. This is because a FANALM alarm for
fan 1 will be raised if the fan unit is missing A- or B-side power. An alarm for this
reason puts the system in thermal shutdown mode. This is to ensure proper powering
of the equipment to protect the system from a potential thermal event.
In the shelf power input area, a small board (FILT-B) is bolted onto the power
connectors of the OLTS-M shelf. The FILT-B filters the dc mains on the shelf to
achieve CE Mark, EN55022, and EN300386 EMC compliance.
Three battery filter caps are provided on the board, one each for BAT_A-FG,
BAT_B-FG, and BAT_RET-FG.
Table 45-3 lists the power and grounding signals used.
45-6


Table 45-3 Power and grounding signals
45.7
Signal name
Description
BATA
BATB
BATRET
EG
Electrical ground
FG
Shelf frame ground
Thermal limitation
Due to the high data rates and large number of subscribers, failures of the P-OLT
equipment can cause massive service outages and revenue loss for service providers.
Some P-OLT cards are not expected to operate more than a few minutes without
forced air cooling.
In the current system, there exist multiple thermal sensors on the NT and LT cards.
This allows for 2 thermal defense methods on the P-OLT.
Individual thermal readings on the LT and NT cards. This allows for shutdown of
individual cards, but not for shutdown of a group of LT cards or all LT cards on
the shelf.
FGU 4.6 and later introduced a more comprehensive, system wide thermal
defense that correlated information from alarms and the fans to ensure
system-wide protection.
To prevent failures, the P-OLT uses a redundant fan design. With this design, the
failure of one fan does not cause a cooling system degradation that is severe enough
for the NT and LT units to fail. However, there are constraints that must be observed
for the design to work as specified.
Observe the following when working with the P-OLT equipment:
Install filler panels in any unused slot position to maintain proper thermal
operation.
Use only the AFAN-S as the OLTS-M shelf cooling system. The AFAN-S is
fault-tolerant and highly reliable.
system will not initialize. This is because a FANALM alarm for fan 1 will be
raised if the fan unit is missing A- or B-side power. An alarm for this reason puts
the system in thermal shutdown mode. This is to ensure proper powering of the
equipment to protect the system from a potential thermal event.
Do not stack P-OLT shelves directly over each other, a 50 mm air gap between
the lower P-OLT shelf and the fan unit for the upper P-OLT should exist.
Do Not place the shelf above a heat source without redirecting the hot air away
from the inlet of the shelf. For example, you can use an air baffle to redirect hot
air.

45-7
Never allow an in-service P-OLT be left without forced-air cooling for more than
5 minutes.
Replace the failed fan within the MTTR period. A single-fan failure in the P-OLT
cooling system does not cause the NT or LT cards to fail during the MTTR period.
MTTR is a maximum of 4 hours for remote locations, including CEVs.
P-OLT thermal defense for individual card protection

There are threshold values defined for such sensors where the hardware and software
react to the sensor readings once a threshold is exceeded.
LT cards
The LT cards have thermal sensors mounted in close proximity to the boards FPGAs
(two on the GLT2 and four on the GLT4 cards). Each sensor takes two separate
readings:
Internal reading - the ambient temperature for the area around the sensor.
External reading - the core (junction) temperature of the FPGA device.
The LT card software reads the sensors periodically (once per second) and will
maintain a history of the last ten readings. If the average of the readings exceed a
pre-defined threshold, the software reacts to it.
The LT thresholds for internal readings are:
Major Thermal Alarm Raise Threshold - LT notifies NT of monitored

temperature threshold reached or exceeded and NT raises system alarm
(HITEMP). The temperature exceeded threshold for this alarm is 70C (158F).
Major Thermal Alarm Clear Threshold - LT notifies NT of monitored
temperature falling below threshold for clearing of system alarm (HITEMP). The
temperature clear threshold for this alarm is 67C (152.6F).
Critical Thermal Alarm Raise Threshold - LT notifies the NT that the card is
dangerously hot. The NT raises a system alarm (SHUTDOWN) (85 C/185 F)
and turns off the power to the reporting LT card. The operator is expected to
resolve the cause of the high temperature and re-activate the LT using TL1
commands.
Critical Thermal Alarm Clear Threshold - LT notifies NT of monitored
temperature falling below threshold for clearing of system alarm (HITEMP). The
temperature clear threshold for this alarm is 102C (215.6F).
45-8

The LT thresholds for junction readings are:
Major Thermal Alarm Raise Threshold - LT notifies NT of monitored

temperature threshold reached or exceeded and NT raises system alarm
(HITEMP). The temperature exceeded threshold for this alarm is 105C (221F).
Major Thermal Alarm Clear Threshold - LT notifies NT of monitored
temperature falling below threshold for clearing of system alarm (HITEMP).
Critical Thermal Alarm Raise Threshold - LT notifies the NT that the card is
dangerously hot. The NT raises a system alarm (SHUTDOWN) (110 C/230 F)
and turns off the power to the reporting LT card. The operator is expected to
resolve the cause of the high temperature and re-activate the LT using TL1
commands.
NT card
Each NT card has two thermal sensors that are read by the on-board computers. The
sensors are located at the hottest locations on the board and monitor the ambient
temperature of the card. The software reads the sensors and raises major and critical
alarms when the pre-defined thresholds are exceeded. The NT thresholds are:
Major Thermal Alarm Raise Threshold - monitored temperature threshold

reached or exceeded (70 C/158 F), NT raises system alarm (HITEMP).
Major Thermal Alarm Clear Threshold - monitored temperature falls below

threshold (68 C/154 F) for clearing of system alarm (HITEMP).
Critical Thermal Alarm Raise Threshold - monitored temperature threshold
reached or exceeded (85 C/185 F), raises critical system alarm (SHUTDOWN).
Critical Thermal Alarm Clear Threshold - monitored temperature falls below
threshold (82 C/179.6 F) for clearing of critical system alarm (SHUTDOWN).
Unlike the LT, the software cannot power down the NT in the case of a critical
thermal event. There is a thermal switch located next to the boards power supply that
will power down the NT board if a very high temperature is reached (95 C/203 F).
If the ambient temperature falls below 85 C (185 F), the board will be powered up
again.
Fan unit (AFAN-S)
The fan unit is essential to the proper operation of the 7342 ISAM FTTU. If a fan
fails, the fan unit controller will increase the speed of the operating fan and raise a
system alarm (FANALM). Other reasons for a FANALM include:
power feed missing (A or B)

on-board fan unit controller fails (causes system to increase the speed of the fans
to maximum)
on-board fan unit power converters fail
bad power to the controller
fan switch is in the off position

45-9
If the fan unit is removed from the system, a system alarm is raised (FANMISSING).
The 7342 ISAM FTTU should not be operated without the fan unit for more than a
few minutes.
P-OLT thermal defense in FGU 4.6 and later systems

New command(s) allow the user to gather individual ambient and junction
temperature readings of every board in the system. The rtrv-opstat-lt command is to
added to the TL1 management system for thermal sensor retrievals from the LTs.
The rtrv-opstat-nt command is modified to include the data retrieval for thermal
sensors of the NT. See the 7342 ISAM FTTU Operations and Maintenance
Procedures Guide using TL1 and CLI guide for more information about performing
the commands.
LT cards and NT cards
Similar to the current implementation, in FGU 4.6 and later, the LT and NT software
reads the multiple thermal sensors in a periodic way. The readings are categorized
into 2 types:
Local ambient temperature readings: These readings are showing the ambient
thermal readings around a specific sensor # of such readings/sensors will be
equivalent to the number of sensors on the board (for example, if the board has 4
sensors, the expected number of such readings are 4). These values are physically
read from the sensors and are representing the sensor temperature. These readings
measure the temperature (PCB) around the sensor.
FPGA/ASIC/CPLD junction temperature readings: The critical board
components (for example, FPGA) are also read periodically. The total number of
readings may be less than the total number of sensors on board, however all the
FPGAs on board are recommended to be covered with such readings. For current
GLT2-x and GLT4-x or NT cards, these readings are read from the same sensors.
There are 2 critical conditions defined:
Critical Condition 1 (CC1): This is a trigger where the system shows a thermal
breakdown and is independent of thermal mode. It is dangerous to continue
operation if such a trigger happens. The trigger is a certain number of LTs stating
SHUTDOWN alarms within a certain timeframe.
Critical Condition 2: This is a trigger which states that the system will get hot
quickly. And this condition is detected only by early detection algorithm. System
reacts to this trigger.
For a system that has 9 or more active LTs, the following conditions are considered
as Critical Condition 1:
The system gets THERMALSHUTDOWN alarms from C 4 or more LTs within

4 minutes.
At any time if at least 80% of the LTs in the system report either HITEMP alarm
or THERMALSHUTDOWN alarm
45-10

For a system that has less than 9 active LTs, the following conditions are considered
as Critical Condition 1:
The system gets THERMALSHUTDOWN alarms from 3 or more LTs within 4

minutes.
At any time if at least 90% of the LTs in the system report either HITEMP or
THERMALSHUTDOWN alarms.
The detection of no air flow is the basis for critical fan problems. Once the system
detects air-flow problems in the LTs, it starts to count the number of such warnings
and makes a decision depending on the received number of warnings and the total
number of active LTs in the system. The critical condition 2 is a clear indicator for
the shelf early detection algorithm to take an action. The system takes action to
critical condition 2 only while detecting FAN1 or unreliable ACU issues.
For a system that has 9 or more active LT cards, one of the following conditions are
considered as Critical Condition 2:
The system gets/calculates suspected air flow problem warnings from at least
70% of the LTs within any minute interval
For 4 or more LTs, the system calculates a suspected air flow problem for 3
consecutive minutes. 3 consecutive minute-long suspected air flow issues from an
LT are called 3 consecutive warnings.
For 3 consecutive minutes, if the system calculates 9 or more 3 consecutive
warnings for the LTs
For a system that has less than 9 active LT cards, one of the following conditions are
considered as Critical Condition 2:
The system gets/calculates suspected air flow problem warnings from at least
80% of the LTs within any minute interval
For 3 or more LTs, the system calculates a suspected air flow problem for 3
consecutive minutes. 3 consecutive minute-long suspected air flow issues from an
LT are called 3 consecutive warnings.
For 3 consecutive minutes, if the system calculates 6 or more 3 consecutive
warnings for the LTs
Fan unit
The fan unit is essential to the proper operation of the 7342 ISAM FTTU. There are
eight fans in the fan unit and they are configured as four redundant pairs. If a fan fails,
the fan unit controller will increase the speed of the operating fan and raise a system
alarm (FANALM). Other reasons for a FANALM include:
power feed missing (A or B)

on-board fan unit controller fails (causes system to increase the speed of the fans
to maximum)
on-board fan unit power converters fail
45-11
bad power to the controller

fan switch is in the off position
If the fan unit is removed from the system, a system alarm is raised (FANMISSING).
The 7342 ISAM FTTU should not be operated without the fan unit for more than a
few minutes.
To avoid damage to hardware due to thermal events, early detection of thermal
problems was added to FGU 4.6 and later releases. The early detection mechanism
senses a problem with the fans that are critical for the operation of the shelf, thus the
system reacts to the condition. The key controller in a system is the NT card, and
keeping it alive during a thermal event is the main intent of early detection logic. If
the NT is kept alive, it can maintain the control of the LTs, however to be alive, the
NT is required to detect a thermal problem at its early phases and react to it before it
gets out of control.
For this purpose, the NT board is sent all the thermal sensor data from all LTs. If a
Fan1 condition (or missing/malfunctioning ACU) is detected, the NT software
determines if a thermally critical condition present and puts the shelf into an
absolute low-power mode, in which all LTs are turned off and the NTs are put in
low-power mode. This is based both on the presence of Fan1/ACU problem and the
number of LTs reporting thermal issues. This way, the NTs survive a fatal fan failure
with protecting the equipment, however all the services are taken down. In the case
of a Fan2 condition, the NT goes into ignorant mode, where the NT expects the fan
unit to be put back in a short time, for example, when fan filters are being replaced.
45.8
The following sections describe the OLTS-M shelf.
Front cover
The front cover is supported by hanging it on the notched cutouts on the side rails of
the shelf and secured by tightening the two captive screws at the bottom.
Fiber management shelf

The fiber management shelf located at the bottom of the OLTS-M shelf is used to
route fiber cables that are coming from the LT and NT cards. It consists of a fiber
tray and fiber routing clips. Fiber cables are routed out the cable exit areas located on
the left and right sides of the shelf. To assist in routing the cables, the front lip of the
tray can be removed by loosening the two captive screws on the bottom edge.
Specifications
Table 45-4 describes the physical specifications of the OLTS-M.
Table 45-4 Physical specifications of the OLTS-M
Description
Specification
Height
24.46 in. (62.13 cm)
(1 of 2)
45-12

Description
Specification
Width
17.23 in. (43.76 cm)
Depth
11.12 in. (28.24 cm)
Weight
37.0 lb. (16.8 kg)
(2 of 2)

45-13
45-14

46.1 Identification
46-2

46-2
46-2

46-2
46-1
46.1
Identification
Table 46-1 provides identification information about the SANC-D.
Table 46-1 Identification of the SANC-D
Part number
Mnemonic
Description
CLEI
CPR
ECI/Bar
code
3EC 17919 AA
SANC-D
Synchronous ATM network combiner,

version D, BITS and LAN access for optical
NT
46.2

The SANC-D provides:
46.3
BITS and LAN interface connection in an ALTS-N shelf

synchronization signal connection to the optical NT units
front panel BITS and LAN connection using two RJ-45 connectors
backplane connection to the optical NT units
General description
The SANC-D provides BITS and LAN physical interface access to the optical NT
units installed in the shelf. The SANC-D is located in the connector area of the
ALTS-N shelf.
The SANC-D provides the following functions:
BITS/SETS interface physical access

LAN physical access
RIMW interface
A SANC-D can be used in an ALTS-N shelf deployed with either one or two SDH
optical NT units.
The SANC-D backplane connectors are female pressfit connectors with 5-row
pinning and 2 mm pitch.
The SANC-D is provided with a LAN interface to allow outband management.
46.4
The external interfaces are:
BITS/SETS interface physical access

LAN physical access
46-2

remote inventory interface

presence interface
The front panel is equipped with the following parts:
one RJ-45 8-pin female connector for BITS/SETS interface

one RJ-45 8-pin female connector for LAN interface
two contacts for ESD prevention
two tabs for insertion and extraction

46-3
46-4

47 Racks for video coupler unit data

sheet
47.1 Identification
47-2

47-2
47-6

47-2
47-1
47.1
Identification
Table 47-1 provides identification information about the Tyco and LGX racks for the
video coupler.
Table 47-1 Identification of the rack for the video coupler
Part number
Mnemonic
Description
CLEI
CPR
ECI/Bar
code
1AD 04674 0001
Tyco 2200 mm
video coupler
fiber rack
1AD 01412 0044
LGX rack for

video coupler
47.2

The Tyco rack for the video coupler:
houses a maximum of 15 Tyco video coupler subracks (VCSs), including one for
sparing
includes fiber-handling raceways
is generally located in a CO or CEV
The LGX rack for the video coupler:
houses a maximum of nine video coupler shelves (VCSL-As)

supports two full packet optical line termination (P-OLT) systems (one and a half
VCSL shelves are required for each P-OLT)
is generally located in the central office (CO) or controlled environment vault

(CEV)
47.3
General description
The following provides a general description of the video coupler racks.
Tyco
The 2200 mm video coupler fiber rack is used to hold the VCSs separately from the
packet optical line termination (P-OLT) rack.
The VCSs are storage shelves for video coupler trays. The trays contain wavelength
division multiplexers (WDMs).
The WDMs provide video signal overlay onto the passive optical network (PON) and
distribute the video signal from the video optical line termination (V-OLT) to the
optical network terminal (ONT).
47-2

When fully equipped, a video coupler fiber rack provides video overlay capacity for
a maximum of five P-OLT racks, or 10 P-OLT shelves.
Figure 47-1 shows the video coupler fiber rack.

47-3

Figure 47-1 Video coupler fiber rack
47-4

LGX
The rack for the video coupler is a standard 23 in (54.82 cm). closed unequal-flange
equipment rack. A fiber slack storage tray (FSST) is optional for each three VCSL-A
shelves.
The rack holds the video coupler shelves that provide wavelength division
multiplexers (WDMs) for merging the optical traffic from the P-OLT and the video
optical line termination (V-OLT).
For each full P-OLT, 1-1/2 VCSL shelves are required. A single video coupler rack
can support a maximum of six P-OLTs.
Figure 47-2 shows the rack for video coupler and the recommended video coupler
layout.

47-5

Figure 47-2 Rack for video coupler and recommended layout
VCW2 12
VCW2 1
VCSL 1
VCSL 2
VCSL 3
P-OLT 1
P-OLT 4
FSST
VCSL 4
VCSL 5
P-OLT 2
VCSL 6
P-OLT 5
FSST
VCSL 7
VCSL 8
P-OLT 6
P-OLT 3
VCSL 9
FSST
no310
47.4
Table 47-2 provides information about the physical dimensions of the Tyco video
coupler fiber rack.
47-6


Table 47-2 Physical dimensions of the Tyco video coupler fiber rack
Description
Measurement
Height
86.61 in. (2200 mm)
Width
47.24 in. (1200 mm)
Depth
11.81 in. (300 mm)
Table 47-3 provides information about the dimensions of the LGX 58.42 cm (23-in.)
rack, including the front and back aisles.
Table 47-3 54.82 cm (23 in) rack dimensions
Description
Pitch
Depth
Floor area
Wiring aisle (rear)
26 in. (66 cm)
11.2 in. (28.4 cm)
2.17 ft2 (0.202 m2)
Equipment
26 in. (66 cm)
12.8 in. (32.5 cm)
2.17 ft2 (0.202 m2)
Maintenance aisle (front)
26 in. (66 cm)
15 in. (38.1 cm)
2.71 ft2 (0.252 m2)
Total
26 in. (66 cm)
39 in. (99 cm)
7.05 ft2 (0.655 m2)

47-7
47-8

48 Tyco video coupler subrack unit data

sheet
48.1 Identification
48-2

48-2
48-2

48-1
48.1
Identification
Table 48-1 provides identification information about the Tyco subrack for video
coupler.
Table 48-1 Identification of the subrack for video coupler
Part number
Mnemonic
Description
CLEI
CPR
ECI/Bar
code
1AD 04675 0001
Subrack for video

coupler provided
by Tyco
48.2

The Tyco subrack for video coupler:
holds a maximum of three pairs of Tyco video coupler WDM (VCW4-A) trays
that include three left trays and three right trays
is housed in the 2200-mm Tyco video coupler fiber rack

provides fiber routing management for the VCW4-A trays to the sides of the
subrack
allows independent removal and addition of video coupler trays for maintenance
or replacement
allows independent connection or disconnection of fiber jumpers for maintenance
and replacement
is generally located in a CO, CEV, or remote terminal
48.3
General description
The Tyco video coupler subrack (VCS) supports a maximum of three pairs of video
coupler WDM (VCW4-A) trays. The VCS modularity allows system expansion on
an as-needed basis. It also provides fiber routing management into and out of the
shelf while maintaining fiber bend radius control.
Figure 48-1 shows the front view of the VCS.
Figure 48-1 Video coupler subrack, front view
48-2

The WDM is used to overlay video signals through the PON to individual ONTs. A
VCS supports a maximum of 24 PONs.
For more information about the Tyco video coupler subrack, see related Tyco
customer documents.
Figure 48-2 shows an open VCS with five WDM trays.
Figure 48-2 Open VCS with 5 trays

48-3
48-4

49.1 Identification
49-2

49.4 Optical safety
49-3
49-3
49.5 Environment requirements

49.6 Connections
49-2
49-3
49-4

49-1
49.1
Identification
Table 49-1 provides identification information about Tyco VCS8-A.
Table 49-1 Identification of VCS8-A
Part number
Mnemonic
Description
CLEI
CPR
ECI/Bar
code
3EM 15711 AD
VCS8-A
Tyco video
coupler WDM
trays with
splitters, 16
PONs, version A
3EM 15711 AE
Left tray with 8

WDMs with LC
connectors on
the splitters
3EM 15711 AF
Right tray with 8

WDMs with LC
connectors on
the splitters
49.2

The Tyco VCS8-A tray provides:
overlay video signal inserted into downstream traffic to the optical network
terminals (ONTs)
modular trays designed for scalability that matches the passive optical networks
(PONs) on the line termination (LT) cards
installation based on LT cards with one tray supporting four LT cards
eight wavelength division multiplexers (WDMs) per tray that can serve eight
PONs
18 port connections per tray with front access, including PON and video optical
line termination (V-OLT) ports equipped with SC/APC connectors, and packet
optical line termination (P-OLT) ports equipped with SC/UPC connectors
easy snap-in installation of a maximum of two pairs of VCS8 trays into the video
coupler subrack (VCS)
easy connection or disconnection of jumpers without tools
The VCS8-A is located in the central office (CO), controlled environment vault
(CEV), or remote terminal. It is compliant with GR-1209 and GR-1221
requirements. The connectors are compliant with GR-326 requirements.
49-2

49.3
General description
The VCS8-A tray is used for applications that support all digital radio frequency
(RF) lineup. The VCS8 provides overlay of video signals from the V-OLT onto the
PON.
The VCS8 tray supports the integration of the splitters into the VCS8 tray. The
integration eliminates the need for a splitter rack and simplifies fiber management.
The VCS8 allows a one-to-one relationship between the P-OLT subracks and VCSs.
The VCS8 is scalable to accommodate the increase of LT cards in the P-OLT. The
VCS8 tray contains two trays, a left and a right tray, that are connected together.
Each VCS contains two pairs of VCS8 trays that can provide video overlay to a
maximum of 16 LT cards.
There are 18 LC type connectors in each tray, grouped into three sets:
eight LC/UPC connectors for signals to and from the P-OLTs

two LC/APC connectors for signals to the V-OLT
eight LC/APC connectors for signals to and from the ONTs, including the overlay
video signal
Each V-OLT port is attached to an optical amplifier. The V-OLT input passes
through a 1:4 planar splitter that splits the V-OLT input into four outputs to feed four
WDM video couplers. Each video coupler connects to the P-OLT, V-OLT, and the
PON that connects to the ONTs.
The function of the VCS8-A is to merge the optical traffic from P-OLT and V-OLT
ports into a multiwavelength signal. The merge is accomplished through a coarse
WDM. The VCS8-A injects the 1550 nm video traffic from the V-OLT onto the 1490
nm traffic from the P-OLT. The resulting multiwavelength traffic is then passed
through the PON to the ONT at the subscriber site. The 1310 nm upstream traffic
from the ONT is routed through the VCS8-A to the P-OLT port.
49.4
Optical safety
Observe the following warnings when working with the optical components in the
VCS8-A.
Warning 1 Possibility of personal injury. Laser radiation when
open. Avoid eye or skin exposure to direct or scattered radiations.
Warning 2 Possibility of personal injury. Fiber cables transmit
invisible laser light. To avoid eye damage or blindness, never look
directly into fibers, connectors, or adapters.
49.5
Environment requirements
The VCS8-A contains optical components that must be placed in a controlled
environment. The conditions in the environment must not exceed the extreme ratings
provided in Table 49-2.

49-3

Table 49-2 Extreme rating for optical components
Parameter
Minimum
Maximum
Storage and shipping temperature
40F (40C)
185F (85C)
Operating temperature
40F (40C)
185F (85C)
Optical input power capability
+24 dBm
5% RH
85% RH
Operating and storage humidity range
(1)
Note
(1)
49.6
The actual operating environment may reach a maximum of 90% for short-term operation.
Short-term operation is defined as a maximum of 72 h and for a total of no more than 15 days per
year.
Connections
There are 18 LC type connectors in a VCS8 tray, grouped into three sets. Each group
of three connectors handles two inputs, one from the P-OLT and one from the
V-OLT, and one output to the ONT through the PON. The functions of the
connectors are described as follows:
P-OLT connector: receives input from the P-OLT

V-OLT connector: receives input from the V-OLT
PON connector: provides output to an ONT through the PON
Figure 49-1 shows the VCS8 tray.
Figure 49-1 VCS8 tray
49-4

50.1 Identification
50-2

50.4 Optical safety
50-2
50-3

50.6 Connections
50-2
50-3
50-3

50-1
50.1
Identification
Table 50-1 provides identification information about Tyco VCW4-A.
Table 50-1 Identification of VCW4-A
Part number
Mnemonic
Description
CLEI
CPR
ECI/Bar
code
3EM 15711 AA
VCW4-A
Tyco video
coupler WDM tray
for 8 PONs,
version A
3EM 15711 AB
Left tray: Tyco

video coupler
WDM tray for 4
PONs (4 SC
without splitters)
3EM 15711 AC
Right tray: Tyco

video coupler
WDM tray for 4
PONs (4 SC
without splitters)
50.2

The Tyco VCW4-A tray provides:
overlay video signal inserted into downstream traffic to the optical network
terminal (ONT)
modular trays designed for scalability that matches the passive optical networks
(PONs) on the line termination (LT) cards
installation based on LT cards with one tray supporting two LT cards
four wavelength division multiplexers (WDMs) per tray that can serve four PONs
12 port connections per tray with front access, including PON and video optical
line termination (V-OLT) ports equipped with SC/APC connectors, and packet
optical line termination (P-OLT) ports equipped with SC/UPC connectors
The VCW4-A is located in the central office (CO), controlled environment vault
(CEV), or remote terminal. It is compliant with GR-1209 and GR-1221
requirements. The connectors are compliant with GR-326 requirements.
50.3
General description
The VCW4-A tray is installed in a Tyco video coupler subrack. Left and right trays
are paired for space efficiency. Each tray contains four WDMs that can connect a
maximum of four PONs.
50-2

The function of the VCW4-A is to merge the optical traffic from P-OLT and V-OLT
WDM. The VCW4-A injects the 1550 nm video traffic from the V-OLT onto the
1490 nm traffic from the P-OLT. The resulting multiwavelength traffic is then
passed through the PON to the ONT at the subscriber site. The 1310 nm upstream
traffic from the ONT is routed through the VCW4-A to the P-OLT port.
50.4
Optical safety
VCW2-C.
50.5
The VCW4-A contains optical components that must be placed in a controlled
Parameter
Minimum
Maximum
40F (40C)
185F (85C)
40F (40C)
185F (85C)
+24 dBm
5% RH
85% RH
(1)
Note
(1)
50.6
year.
Connections
There are 12 SC type connectors in a VCW4 tray, grouped into four sets of three.
Each group of three connectors handles two inputs, one from the P-OLT and one
from the V-OLT, and one output to the ONT through the PON.

50-3
The functions of the connectors are described as follows:

Figure 50-1shows the VCW4 tray.
Figure 50-1 VCW4 tray and connectors
50-4

51.1 Identification
51-2

51.4 Alarms
51-2
51-2
51-3
51.5 Connections
51-3
51-3

51-1
51.1
Identification
Table 51-1 provides identification information about the LGX VCSL-A.
Table 51-1 Identification of VCSL-A
Part number
Mnemonic
Description
CLEI
CPR
ECI/Bar
code
3EM 11047 AA
Video coupler
shelf LGX
51.2

The VCSL-A shelf:
holds a maximum of 12 video coupler WDM casettes (VCW2-C)

mounts in either a 19-in. or 23-in. LGX-compatible rack with a removable front
51.3
door
provides fiber routing management
enables independent removal and addition of video coupler cassettes for
maintenance
provides blank plates for unoccupied cassette slots
is generally located in CO or CEV
General description
Figure 51-1 shows the VCSL-A shelf.
51-2


Figure 51-1 VCSL-A shelf
No270
The VCSL-A shelf houses and protects the video coupler WDM cassettes. The
VCSL modularity allows system expansion on an as-needed basis. It also provides
fiber routing management into and out of the shelf while maintaining fiber bend
radius control.
The VCSL-A supports a maximum of 12 WDM cassettes per shelf. Each WDM
cassette (VCW2-C) supports two PONs. The WDM is used to distribute video
signals through the PON to individual ONTs.
51.4
Alarms
This is a passive shelf. There are no alarms present.
51.5
Connections
Figure 51-1 shows the output connectors.
51.6
Table 51-2 lists the physical specifications of the VCSL-A shelf.
Table 51-2 Physical specifications
Description
Specification
Height
7 in. (17.78 cm)
Width
17 in. (43.18 cm)
(1 of 2)

51-3
Description
Specification
Depth
11 in. (27.94 cm)
Weight
8 lb (3.36 kg)
(2 of 2)
51-4

52.1 Identification
52-2

52.4 Optical budget
52.5 Optical safety
52-2
52-3
52-4

52.7 Connections
52-2
52-4
52-5
52-5

52-1
52.1
Identification
Table 52-1 provides identification information about LGX VCW2-C.
Table 52-1 Identification of VCW2-C
Part number
Mnemonic
Description
CLEI
CPR
ECI/Bar
code
3EM 11046 AC
VCW2-C
Video coupler
WDM cassette, 2
PON, version C
BVPMBEABAA
W73067
134412
52.2

The LGX VCW2-C cassette provides:
overlay video signal inserted into downstream traffic to the ONT

modular cassettes designed for scalability that matches the PONs on the LT cards
2 wavelength division multiplexers (WDMs) that support a maximum of two
PONs
6 port connections with front access, including PON and V-OLT ports equipped
with SC/APC and P-OLT ports equipped with SC/UPC connectors
adapters for PON connections equipped with shutters for safety
industry standard vertical LGX cassette
easy installation into the VCSL-A or any LGX-compatible shelves
The VCW2-C is located in a CO, CEV, or remote terminal. It is compliant with

GR-1209 and GR-1221 requirements. The connectors are compliant with GR-326
requirements.
52.3
General description
A VCW2-C is installed in the VCSL-A shelf. Each VCW2-C contains two WDM
units. Each WDM unit is connected to a PON in the P-OLT system.
The function of the VCW2-C is to merge the optical traffic from P-OLT and V-OLT
WDM. The VCW2-C injects the 1550 nm video traffic from the V-OLT onto the
1490 nm traffic from the P-OLT. The resulting multiwavelength traffic is then
passed through the PON to the ONT at the subscriber site. The 1310 nm upstream
traffic from the ONT is routed through the VCW2-C to the P-OLT port.
Figure 52-1 shows an illustration of the VCW2-C.
52-2


Figure 52-1 VCW2-C
52.4
Optical budget
The video coupler optical budget information is divided into two sections: one for
VCW2 connectors and the other for the WDM.
Table 52-2 provides the optical budget of VCW2 connectors.
Table 52-2 Optical budget of VCW2 connectors
Parameter
Condition
Minimum
Maximum
Insertion loss
Mated pair
0.3 dB
Return loss
UPC
50 dB
Return loss
APC
60 dB
Return loss
UPC
50 dB
Table 52-3 provides the optical budget of WDM.

Table 52-3 Optical budget of WDM
Parameter
Minimum
Maximum
Notes
Video band
1539 nm
1565 nm
Data bands
1260 nm
1360 nm
1480 nm
1500 nm
20 dB
Worst point over data

bands
Data isolation
(1 of 2)

52-3
Parameter
Minimum
Maximum
Notes
Video isolation
20 dB
Worst point over

video bands
Insertion loss
0.8 dB
Port-to-port
(connectorized
pigtail)
Polarization mode
dispersion (PMD)
0.1 ps
All ports, over data

and video bands
Polarization dependent
loss (PDL)
0.1 dB

and video bands
Chromatic dispersion
(CD)
1 ps/nm
+1 ps/nm

and video bands
Directivity
55 dB

and video bands
Return loss
55 dB

and video bands
(2 of 2)
52.5
Optical safety
VCW2-C.
52.6
The VCW2-C contains optical components that must be placed in a controlled
Parameter
Minimum
Maximum
40F (40C)
185F (85C)
40F (40C)
185F (85C)
+24 dBm
5% RH
85% RH

52-4
(1)


Note
(1)
52.7
year.
Connections
There are six SC type connectors at the front of the VCW2-C. There are two sets of
three connectors. The functions of the connectors are described as follows:

Figure 52-2 shows the input and output connectors.
Figure 52-2 VCW2-C input and output connectors
SC/APC
PON
P-OLT
SC/UPC
SC/APC
V-OLT
SC/APC
PON
SC/UPC
P-OLT
SC/APC
V-OLT
VCW2-x
FGU051
52.8
Table 52-5 lists the physical specifications of the VCW2.
Table 52-5 VCW2 physical specifications
Description
Specification
Height
5.10 in. (12.95 cm)
Width
1.15 in. (2.92 cm)
Depth
6.36 in. (16.15 cm)
(1 of 2)

52-5
Description
Specification
Weight
1.125 lb (0.51 kg)
(2 of 2)
52-6

Glossary
1000Base-LX
An IEEE 802.3 LAN transmission standard for 1000 Mb/s gigabit Ethernet
(GE) using Long Wavelength (LX) laser transmitters over fiber-optic cable.
1000Base-SX
An IEEE 802.3 LAN transmission standard for 1000 Mb/s gigabit Ethernet
(GE) using Short Wavelength (SX) laser transmitters over fiber-optic cable.
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 cabling.
5523 AWS
The Alcatel-Lucent 5523 Access Workstation

The Alcatel-Lucent client-server architecture controller for
7342 ISAM FTTU systems.
5526 AMS
The Alcatel-Lucent 5526 Access Management System

The Alcatel-Lucent UNIX-based, client-server architecture controller for
7342 ISAM FTTU systems.
5528 WAM
5528 Web-based Access Manager

The Alcatel-Lucent 5528 Web-based Access Manager is a web server-based
network manager software. The 5528 WAM allows registered users to
connect to the NE through the Internet or craft port, providing a uniform and
simplified method of monitoring, provisioning, and configuring NEs.
AAA server
Authentication, Authorization, Accounting server

GL-1
Glossary
AACU-C
Alarm Control Unit, Version C

A card that performs alarm control functions and provides connectivity for
a craft terminal and Ethernet 10Base-T connectivity for maintenance access.
AAI
Access-to-Access Interface
The interface that the line termination (LT) card uses to subtend to the
passive optical network (PON).
ACK
Acknowledgement
ACL
Access Control List
ACO
Alarm Cut Off

ACO is a push button that allows the 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 component located on the optical line termination (OLT) shelf that
collects rack alarms, controls top rack unit alarm displays, and provides an
alarm interface to the central office alarm system
AFAN
Fan
A fan unit installed at the bottom of each optical line termination (OLT)
shelf.
AFAN-H
Fan, version H
A fan unit installed at the bottom of each optical line termination (ALTS-N)
shelf. AFAN-H is only used in the ETSI market.
AFAN-P
Fan, version P
A fan unit installed at the bottom of each optical line termination (OLTS-K)
shelf. AFAN-P is only used in the ANSI market.
AFAN-R
Fan, version R
A fan unit installed at the bottom of each optical line termination (OLTS-L)
shelf. AFAN-R is only used in the ANSI market.
AFAN-S
Fan, version S
A fan unit installed at the bottom of each optical line termination (OLTS-M)
shelf. AFAN-S is only used in the ETSI market.
AFE
Analog Front End
AGC
Automatic Gain Control

An electronic device that controls the gain of a signal to ensure some level
of performance over changing conditions.
AID
GL-2
Access Identifier
Glossary
AIS
Alarm Indication Signal
ALM
Alarm
ALTS-N
ADSL Line Termination Shelf, version N

The ASAM shelf that provides mounting locations and slide-in rails for unit
insertion into backplane-mounted connectors. The ALTS-N is only used in
the ETSI market.
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.
APC
American Power Conversion
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 availability
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
ASCII
American Standard Code for Information Interchange

Coding method used to convert letters, numbers, punctuation, and control
codes into digital form
AU
Automatically Out-of-Service
An alarm signal that indicates that the unit failed and is automatically taken
out-of-service
AUMA
Automatically and Manually Out-of-Service

An alarm signal that indicates that the unit failed and the user has manually
(administratively) taken it out of service.
AWG
American Wire Gauge

AWG is a standard measuring gauge for non-ferrous conductors.
BAC
Buffer Acceptance Control
BATA
Battery A
BATB
Battery B
BATRET
Battery Return

GL-3
Glossary
BER
Bit Error Rate

Measure of transmission quality expressed as the percentage of received bits
in error compared to the total number of bits received.
BITS
Building Integrated Timing Supply
BITS-A
BITS backplane adapter, version A

BITS-A is only used in the ANSI market.
BITS-B
BITS backplane adapter, version B

BITS-B is only used in the ETSI market.
BMLD
Burst Mode Laser Driver
BOOTP
Bootstrap Protocol
Application layer configuration protocol that allows a host to configure itself
dynamically at boot time. This protocol provides 3 services:
IP address assignment
Detection of the IP address for a serving machine
The name of a file to be loaded and executed by the client machine
BRAS
Broadband Remote Access Server
BW
Bandwidth
CAC
Connection Admission Control

CAC is an algorithm that evaluates whether a new service can be added to a
VLAN on a PON, and whether a new VLAN can be added to a gigabit
Ethernet port or LAG on the NT.
CB
Circuit Breaker
CBN
Common Bonding Network
CDE
Component Development Environment

Development discipline based on the reuse of components to ease rapid
time-to-market.
CDR
Clock Data Recovery
CDRH
Center for Devices and Radiological Health (U.S.)
CEMT
Cable Entry Management Tray
CES
Circuit Emulation Service
CEV
Controlled Environment Vault
CFR
Code of Federal Regulation (U.S.)
GL-4

Glossary
CRoHS
China Restriction of Hazardous Substances

The CRoHS regulations provide information about the installation and
operation of ONT systems with regards to the use of hazardous substances
in products and subassemblies.
CID
Channel Identifier or Consecutive Identical Digit
CLEC
Competitive Local Exchange Carrier
CLEI
Common Language Equipment Identifier
CLI
Command Line Interface

A workstation access method interface that uses CLI commands to
communicate to any network element in the 7342 ISAM FTTU network.
CO
Central Office
Telephone switching center that connects subscribers within a telephone
network.
CODEC
Coder Decoder
CoS
Class of Service
a method of managing traffic in a network by grouping similar types of
traffic together and treating each type as a class with its own level of service
priority.
CPE
Customer Premises Equipment

Customer-owned telecommunications equipment at customer premises used
to terminate or process information from the public network
CPLD
Complex Programmable Logic Device
CPU
Central Processing Unit

The part of a computer that performs the logic computational and
decision-making functions
CSA
Carrier Serving Area

A type of trunk-loop architecture that typically includes a T1 carrier, a
cluster of subscribers, and a serving area
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
CTAG
Correlation Tag
C-VLAN
Customer VLAN

GL-5
Glossary
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
dBm
Decibel referenced to one millivolt across 75 ohms
DCE
Data Circuit Terminating Equipment
DHCP
Dynamic Host Configuration Protocol

DHCP is 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.
DLP
Detailed Level Procedure
DPE
Drum Plate Enlarger
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 DSL is a single twisted-pair that supports full-duplex transmission at a bit
rate of 160 kb/s (144 kb/s for 2B+D data, 12 kb/s for framing and error
correction, and 4 kb/s for the embedded operations channel).
DSP
Digital Signaling Processing
DSRL
Downstream rate limiting can be configured on the 7342 ISAM FTTU on a

per-ONT basis or on a per-service basis
DTE
Data Terminal Equipment

A definition of hardware specifications provided for data communications.
EAP
Extensible Authentication Protocol
EC
Echo Cancellation
A technique to stop a received signal from being transmitted back to its
origin by constructing a signal closely approximating the echo component
and subtracting this from the locally transmitted signal
GL-6

Glossary
ECT
Enhanced Craft Terminal
EDFA
Erdium-Doped Fiber Amplifier

A form of fiber optical amplification in which the transmittal light signal
passes through a section of erbium-doped fiber and is amplified by means of
a laser pump diode. EDFA is used in transmitter booster amplifiers, in-line
repeating amplifiers, and receiver preamplifiers.
EE
Equipment Engineering
EFT
Electrical Fast Transient
eHCL
Ethernet-based High Capacity Link
EHNT
Ethernet-based High-capacity Network Termination
EIA
Electronic Industries Association

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.
EM
Element Manager
E-MAN
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].
These two abilities are collectively named EMC.
EMI
Electromagnetic Interference
EMS
Element Management System
EPC
Ethernet Power Connection
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 availability.
ES
Error Second
ESD
Electrostatic discharge
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.

GL-7
Glossary
EVC
Ethernet Virtual Connection

Logical association of UNIs that connects subscriber sites to enable transfer
of Ethernet service frames (such as Internet data, business critical data,
video, and video conferences) between them, and prevents transfer of data
between subscriber sites that are not part of the EVC
EXNT
Ethernet XAUI based (extreme-capacity) Network Termination
FAP
Fuse Alarm Panel
FCC
Federal Communications Commission (U.S.)
FCS
Frame Check Sequence
FDA
Food and Drug Agency (U.S.)
FDB
Forwarding Database
FEC
Forward Error Correction
FGND
Frame Ground
FGU
Feature Group Fiber to the User
FPGA
Field Programmable Gate Array

An integrated chip with functions that can be programmed by software
FSST
Fiber Slack Storage Tray

A tray used in the Video Coupler shelf for excess PON fiber storage
FTP
File Transfer Protocol

A protocol by which clients can transfer files to a server. Commonly used to
transfer files to a web server for websites or to download files from the web
to install.
FTTU
Fiber To The User

A high-speed fiber-optic cable technology for delivery of broadband
services to home or office over and Ethernet passive optical network (PON).
GBE
Gigabit Ethernet
GE
Gigabit Ethernet
Ethernet interface that runs at 1000 Mb/s
GEM
GPON encapsulated module
GLOB
GPON Line-termination Optical Block
GLT2
GPON Line Termination with 2 PONs
GLT4
GPON Line Termination with 4 PONs
GMII
Gigabit Ethernet Media Independent Interface
GL-8

Glossary
GMQ
General Membership Query
GND
Ground
GNDF
Ground Frame
GPON
Gigabit Passive Optical Network
GUI
Graphical User Interface

A user screen that includes menus, tables, or icons to query or change data;
usually distinguished from the command line interface.
HD
High Density
HS
Hazardous Substance
HSI
High Speed Internet
HST
Hazardous Substance Table

The HST lists the hazardous substances present in products and
subassemblies, as required by CRoHS legislation.
HTRU
High-density Top Rack Unit

An FTTU component that provides redundant power distribution, as well as
fuse and alarm functions, for an equipment rack housing OLTS units.
ICMP
Internet Control Message Protocol
IDC
Insulation Displacement Connector
IDC
Insulation Displacement Connector
IEEE
Institute of Electrical and Electronics Engineers

The IEEE is 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.
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
ILEC
Incumbent Local Exchange Carrier
IOCM
Input-Output Channel Manager
IP
Internet Protocol
Connectionless packet-switching protocol that works together with TCP.
IPoE
Internet Protocol over Ethernet

GL-9
Glossary
IPTV
IP Television
The delivery of video services over an end-to-end IP infrastructure. IPTV
can include various classes of video services, such as video on demand,
broadcast TV, video conferencing, and mobile video.
IS
In Service
ISAM
Intelligent Services Access Manager

The Intelligent Service Access Manager is a DSL access multiplexer that
operates in a packet aggregation network. The ISAM enables deployment of
triple-play services, such as video on demand, high-definition TV and
broadcast TV services for all subscribers simultaneously.
ISDN
Integrated Services Digital Network

An internationally accepted standard for voice, data, and signaling. There
are two basic types of ISDN service: Basic Rate Interface (BRI) and Primary
Rate Interface (PRI).
ISP
Internet Service Provider

A regional network-providing Internet service
ITU
International Telecommunication Union

Standards organization that develops international telecommunications
recommendations.
IXL
Index List
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.
LAN
Local Area Network

Type of network that sends and receives communications over a small area,
such as within an office or group of buildings.
LED
Light Emitting Diode

A semiconductor diode that emits light when a current is passed through it.
LGX
LightGuide Cross-connect
LIM
Line Interface Module
LLC
Logical Link Control

The common data link protocol in Layer 2 of the OSI model that multiplexes
one or more data links to and from separate service access points.
LLID
Loopback Location IDentifier

During a fault investigation by a network operator, the point to which
loopback cells return from a central location in the network.
GL-10

Glossary
LOP
Loss of Pointer
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.
LT
Line Termination
MAC
Media Access Control

The IEEE sublayer in a local area network that controls access to the shared
medium by local area network attached devices.
MAU
Media Attachment Unit

Ethernet connector.
MBS
Maximum Burst Size
MCR
Minimum Cell Rate

An available bit-rate service traffic descriptor in cells/sec. The rate at which
the source is always allowed to send.
MD
MD is expanded in two ways:
Mixed Density
Monitor Diode
MD5
Message Digit algorithm 5
MDF
Main Distribution Frame
MDI
Medium Dependent Interface

MDI is a type of Ethernet port for use with twisted-pair cabling.
MDU
Multi Dwelling Unit
MDIX
Medium Dependent Interface Crossover

The MDIX version of MDI 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.
MEN
Metro Ethernet network
MIB
Management Information Base

A database of network performance information that is stored on a network
agent for access by a network management station.
MII
Media Independent Interface
MLT
Mechanized Loop Test

GL-11
Glossary
MMF
Multimode Fiber
An optical fiber with a core diameter from 50 to 100 microns. 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.
MoCA
Multimedia over Coax Alliance
MOS
Mean Opinion Scores
MPI
Message Passing Interface
MPOE
Minimum Point of Entry
MTTR
Mean Time To Repair
NAT
Network Address Translation
NB
Narrow Band
NE
Network Element
Hardware or combined hardware-software that is designed to perform within
a telecommunications system.
NEBS
Network Equipment Building Standards

Performance, quality, environmental, and safety standards set by Bellcore
for telecommunications equipment.
NEC
U.S. National Electrical Code
Nm
One billionth (10-9) of a meter
NNI
Network-to-Node Interface
NR
Normal
NSP
Network Service Provider
NT
Network Termination
A card that provides a link to an Ethernet-based network. The
7342 ISAM FTTU uses the EHNT-A, EHNT-B or EXNT-A.
NTA, or NT-A
Network Termination-A
NTB, or NT-B
Network Termination-B
NTB
Network Timing BUS
NTP
Non-Trouble Procedure
NTP
Network Time Protocol
NTR
Network Timing Reference
GL-12

Glossary
OAM
Operations, Administration, and Maintenance

Broad categories of functions found in a communications network and/or the
business processes found in network service provider companies.
OATD
Optical Access Termination Daughterboard
OBC
On-Board Controller
ODN
Optical Distribution Network
OFDF
Optical Fiber Distribution Frame

The interface between optical fiber and the optical transmission equipment.
OLT
Optical Line Termination
OLTS
Optical Line Termination Shelf

The FTTU shelf (also called FTTU Line Termination Shelf) that provides
mounting locations and slide-in rails for unit insertion into
backplane-mounted connectors.
OLTS-K
Optical Line Termination Shelf, version K

backplane-mounted connectors. The OLTS-K is only used in the ANSI
market.
OLTS-L
Optical Line Termination Shelf, version L

backplane-mounted connectors. The OLTS-L is only used in the ANSI
market.
OLTS-M
Optical Line Termination Shelf, version M

backplane-mounted connectors. The OLTS-M is only used in the ETSI
market.
OMCI
ONT Management Control Interface
ONT
Optical Network Terminal

Equipment that provides voice, data, and video services and terminates the
7342 ISAM FTTU 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.

GL-13
Glossary
ONU
Optical Network Unit

Equipment that provides voice, data, and video services and terminates the
7342 ISAM FTTU 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.
OOS-MA
Out of ServiceMaintenance
OS
Operations System
Standalone software system that supports network-related operations
functions.
OSI
Open Systems Interconnection

The only internationally accepted framework of standards for
communication between different systems made by various vendors.
OSMINE
Operation Systems Modification for the Integration of Network Elements
OSP
Outside Plant
OSPF
Open Shortest Path First

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
PBA
Printed Board Assembly
PBIT
Priority bit
PC
Personal Computer
PCI
Peripheral Component Interconnect
PCM
Pulse Code Modulation

A form or modulation used to sample a voice signal and convert the sample
into a digital code. A digital modulation method that converts a pulse
amplitude modulated signal into a digital signal.
PCR
Peak Cell Rate

The Peak Cell Rate in cells/sec; the cell rate that the source may never
exceed.
GL-14

Glossary
PDF
Power Distribution Frame
PE
Protective Earth
PHY
Physical (Medium independent)
PID
Protocol Identifier
A part of the SNAP header that identifies the protocol to be encapsulated.
PLID
Physical Location Identification
PLOAM
Physical Layer Operation Administration and Maintenance
PM
Performance Monitoring
A type of transport measurement that provides the continuous collection of
performance data.
PoE
Power over Ethernet

A technology that enables the transmission of electrical power, along with
data, to remote devices over unshielded twisted-pair wiring in an Ethernet
network.
P-OLT
Packet Optical Line Termination

The fully assembled shelf in the 7342 ISAM FTTU system. The P-OLT
consists of two NT cards (for redundancy), one AACU card, and 18 LT
cards.
PON
Passive Optical Network

A fiber-based network that uses passive splitters to deliver signals to
multiple users.
POTS
Plain Old Telephone Service

Term used to describe 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
PPPoE
Point-to-Point Protocol over Ethernet

A specification for connecting multiple computer users on an Ethernet local
area network to a remote site through common customer premises
equipment. PPPoE allows users to share a common xDSL, cable modem, or
wireless connection to the Internet. PPPoE combines the PPP protocol,
commonly used in dialup connections, with the Ethernet protocol, which
supports multiple users in a local area network. The PPP protocol
information is encapsulated within an Ethernet frame.
PPTP
Point-to-Point Tunneling Protocol
PQ
Priority Queue

GL-15
Glossary
PRI
Primary Rate Interface

One type of interface for the ISDN product. The equivalent of a T-1 circuit.
The PRI delivered to the customer premises provides a 23B+D channel
running at 1.544 Mbit/s.
PST
Primary State; PON Section Trace
PSTN
Public Switched Telephone Network

Telephone network based on normal telephone signaling and ordinary
switched long distance telephone circuits.
PVC
Permanent Virtual Circuit

A connection set up by service order instead of on-demand signaling.
PW
pseudo-wire
QoS
Quality of Service
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).
RAL
Restricted Access Location
RAM
Remote Access Multiplexer
RDI
Remote Defect Indication
RDM
Relay Detection Mechanism
RED
Random Early Detection
REN
Ring Equivalency Number
RF
Radio Frequency
RG
Routing Gateway
RGW
Residential Gateway
RH
Relative Humidity
RIP
Routing Information Protocol

An interior gateway protocol defined by the IETF (RIPv1 - RFC 1058 and
RIPv2 - 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.
GL-16

Glossary
RJ-45
The RJ-45 is a single-line jack for digital transmission over ordinary phone
wire, either untwisted or twisted. It is the interface for Ethernet standards
10Base-T and 100Base-T.
RMON
Remote Monitoring
RSSI
Receive Signal Strength Indication
RSTP
Rapid Spanning Tree Protocol

RSTP is specified in IEEE802.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
Real Time
RTCP
Real-Time Control Protocol
RTL
Routine Task List
RTP
Real-time Transport Protocol
RTU
Remote Test Unit
RU
Rack Unit
A rack unit is a unit of vertical space in a standard 19-inch equipment rack.
One RU is 1.75 in.
Rx
Receive (Rx) is the downstream direction on the ONT side. Receive (Rx) is
the upstream direction on the LT side.
SC
Subscriber Connector or Standard Connector or Siemon Connector
SCR
Sustainable Cell Rate
SDH
Synchronous Digital Hierarchy
SEC
Secondary
SELV
Safety Extra Low Voltage

A circuit which has no direct connection to a primary power source, but
derives its power from either a transformer, converter or equivalent isolation
device, or from a battery. It is designed and protected so that under normal
and single fault conditions, its voltages do not exceed a safe value.
SES
Severely Errored Second
SFF
Small Form Factor

A physically compact connector design that has been developed for use in
fiber optic systems. These connectors are about half the size of conventional
connectors.

GL-17
Glossary
SFP
Small Form-factor Pluggable

SFP is 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.
SFU
Single family unit
SFTP
SSH File Transfer Protocol
SHub
Service Hub
SID
System Identifier
A string up to 20 characters in length specifies a unique name for each NE
in a system.
SIP
Session Initiation Protocol

SIP is an application-layer control (signaling) protocol for creating,
modifying, and terminating sessions with one or more participants. These
sessions include Internet telephone calls, multimedia distribution and
multimedia conferences.
SLC
Subscriber Line Cardholder
SLIC
Subscribers Line Interface Circuit

A component in the optical network terminal (ONT) that confers operating
states and other functionality.
SLID
Subscriber Location Identification

A 10-character string set in the network element manager on a GSFU to
allow Enhanced Automated Service Turn-Up.
SMF
Single Mode Fiber

Optical fiber with a core diameter of less than 10 microns that is used for
high-bandwidth transmission over long distances.
SMII
Serial Media Independent Interface
SNMP
Simple Network Management Protocol

Protocol used by network management to retrieve information about
connection status, configuration, and performance.
SNR
Signal-to-Noise Ratio
The ratio of the value of the signal to that of the noise; often expressed in
decibels (dB).
SNTP
Simple Network Time Protocol

A method of synchronizing network nodes. An SNTP server can be used by
multiple nodes to synchronize themselves.
SoC
GL-18
System-on-a-Chip
Glossary
SOHO
Small Office Home Office
SP
Strict Priority
SPI
Serial Peripheral Interface
SSH
Secure Shell
STB
Set-Top Box
The electronic box connected to a television set. This STB receives the
incoming CATV signal and is connected to the televisions coaxial cable.
STP
Spanning Tree Protocol

STP is 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.
S-VLAN
Service VLAN
SWRD
Single Wire Return Device

A unit that provides the ONTs with an Ethernet connection for upstream
connectivity. The SWRD unit functions as a data conversion device with two
10/100 Ethernet ports and 2 RF ports.
TAP
Test Access Port

or
Trouble Analysis Procedure
TB
Terminal Block
T-CONT
Transmission Container, Traffic Container
TCP
Transmission Control Protocol

Protocol for establishing a duplex connection between end systems for the
reliable delivery of data.
TCP/IP
Transmission Control Protocol/Internet Protocol

A networking protocol that provides communication across interconnected
networks, between computers with different hardware architectures and
various operating companies
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
TFTP
Trivial File Transfer Protocol

GL-19
Glossary
TIA
Telecommunications Industries Association

The group responsible for setting telecommunications standards in the
United States.
TID
Target Identifier
The parameter in a TL1 command that identifies the NE which is the target
for the execution of the command.
TL1
Transaction Language 1
Human-machine language standard for controlling network elements.
TLS
Transport Layer Security
TNG
Training Document
TNV
Telecom Network Voltage
TOS
Type of Service
TPID
Tag Protocol Identifier
TRU
Top Rack Unit
TWP
Twisted Pair
Tx
Transmit
Tx is in the upstream direction on the optical network terminal (ONT) side
and in the downstream direction on the line termination (LT) side.
UAI
User-to-Access Interface
The link between the subscriber and the FTTU.
UART
Universal Synchronous Receiver Transmitter
UAS
UAS is expanded in two ways:
Unavailable seconds
A calculation derived by counting the number of seconds that the
interface is unavailable.
Universal Access Server
UDP
User Datagram Protocol
UDS
Unit data sheet
UID
User Identifier
UL
Underwriters Laboratories, Inc.
UNI
User-to-Network Interface
UPC
Usage Parameter Control
GL-20

Glossary
UPS
Uninterruptible Power Supply

An FTTU component that provides emergency backup power for lifeline
POTS at a subscribers location.
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.
UTC
Coordinated Universal Time

A time scale that couples Greenwich Mean Time, which is based solely on
the Earth's inconsistent rotation rate, with highly accurate atomic time.
V ac
Volts alternating current
VCL
Virtual Channel Link
VCSL
Video Coupler Shelf, LGX compatible
VCW2
Video Coupler WDM Cassette, 2 PON

A unit that is installed into the Video Coupler Shelf-LGX (VCSL) of an
FTTU system. Each VCW2 contains two WDM units, which allows each
line termination (LT) card installed in the packet optical line termination
(P-OLT) to connect to a single VCW2.
V dc
Volts direct current
VDSL
Very-high-bit-rate Digital Subscriber Line

A technology that enables very high speed asymmetric data transmission
rates over a single twisted-pair copper telephone wire, but at shorter ranges
than other xDSL types. VDSL consists of two versions: VDSL1, which is the
original VDSL, and VDSL2. The 7342 ISAM FTTU supports VDSL2.
VDSL1 is converted to VDSL2 on migration to release FGU 04.05.05 and
higher.
VLAN
Virtual Local Area Network

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
A service that allows many users to request the same videos at the same time.
Requires a high-end video server with hundreds of gigabytes of storage.
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. VoIP avoids the tolls charged
for POTS.
V-OLT
Video Optical Line Termination

GL-21
Glossary
VP/VC
Virtual Path/Virtual Channel
VRF
Virtual Routing and Forwarding

A logical or virtual routing function with associated routing table that can be
instantiated in a router capable of supporting IP VPN services.
Watt
WAN
Wide Area Network

A type of network that sends and receives communications over a national
area.
WDM
Wavelength Division Multiplexing

A means of increasing the data-carrying capacity of an optical fiber by
simultaneously operating at more than one wavelength.
WRR
Weighted Round Robin
XAUI
10 GE Attachment Unit Interface

A standard for connecting 10 Gigabit Ethernet ports to each other and to
other electronic devices on a printed circuit board.
xDSL
x Digital Subscriber Line

A general term that is used to refer to more than one type of unspecified DSL
(for example, ADSL, ADSL2, READSL, SHDSL, VDSL2).
XFP
GL-22
10-gigabit Ethernet (GE) small form-factor pluggable

Index
Numbers
1490 nm, 21-2
15 min counters, 16-3
15-min counters, 16-3
1550 nm, 21-2
7342 ISAM FTTU
access network, 22-6
configuring for triple play, 22-10
functional blocks, 4-2
GPON features, 1-4
OAM tests, 10-5
service delivery with TPSDA, 22-9
service features, 1-4
triple play, 22-1, 22-2
unit data sheet, 26-2
7342 ISAM FTTU EVC implementation, 25-8
7342 ISAM FTTU VLAN usage, 18-3
802.1ag, 10-5
A
AACU, 27-1
alarm LEDs, 27-5
dimensions, 27-8
physical description, 27-8
weight, 27-8
AACU-A, 5-9
AACU-C, 27-1
alarm control functions, 27-4
alarm input/output, 27-6
CO alarm system, 27-4
features and descriptions, 27-2
functions, 27-2
HTRU, 27-2
identification, 27-2
interface to HTRU, 27-6
interfaces and connections, 27-6
OAM interface, 27-6
rack-level alarms, 27-4
telemetry alarm system, 27-4
account login management, 17-17
AFAN-H, 28-1
back panel, 28-3
cable assembly, 28-4
electrical specifications, 28-4
filter assembly, 28-4
front panel, 28-3
functions, 28-2
physical specifications, 28-4
AFAN-S, 29-1
electrical specifications, 29-3
filter assembly, 29-3
front panel, 29-3

IN-1
Index
AFAN-S (continued) business services
functions, 29-2
physical specifications, 29-3
alarms
CES, 23-6
fault isolation, 8-1
monitoring, 6-8
RTCP failure, 19-40
troubleshooting, 8-1
VoIP, 19-39, 19-40
allocating
bandwidth, 15-21
ALTS-N, 5-4, 30-1, 45-1
backplane connectors and cables, 30-4,
45-5
features and application notes, 30-2, 45-2
general description, 30-2, 45-3
identification, 30-2, 45-2
MAC address label, 5-4
physical description, 30-7, 45-12
physical location identification, 30-6, 45-6
power distribution, 30-6, 45-6
AMI, 23-9
anti-spoofing
gratuitous ARP anti-spoofing, 17-19
source address anti-spoofing, 17-20, 17-21
application notes, 3-1
FGU 04.04.xx, 3-2
FGU 4.2, 3-4
FGU 4.3.0, 3-3
FGU 4.3.5, 3-3
architecture
See triple play
ATRU-M, 31-1
front panel, 31-3, 33-3
indicator LEDs and test button, 31-3, 33-3
PBA-ATRU-G board, 31-4, 33-4
ATRU-N, 32-1
features and application notes, 32-2
functional description, 32-2
IN-2
ATRU-U, 33-1
B
B8ZS, 23-9
bandwidth
allocating, 15-21
CAC check, 18-35
CAC check for S-VLAN, 18-36
DBA, 15-21
profile, 15-20
reserved, 15-21
SHub VLAN capacity check, 18-35
BITS, 23-7, 23-10
BITS-B, 34-1
features, 34-2
general description, 34-2
location, 34-3
Blank LT filter plate, 35-1
Blank NT filler plate, 36-1
bridge ports
associating with flow mirroring VLANs,
18-6
bridging
VLAN scalability, 18-37
broadcast domains
creating for VLANs, 18-3
burst size, 15-8
business ONT
CES, 23-2
connection capacity, 5-12
DS1/E1 ports, 23-2
business services; See Ethernet services

Index
C DHCP relay agent
C
C-VLAN learning mode, 18-4
CAC
bandwidth check, 18-35
bandwidth check for S-VLAN, 18-36
LAG bandwidth check, 18-35
LT, 18-36
NT bandwidth check, 18-35
PON, 18-36
SHub VLAN bandwidth capacity check,
18-35
Capacity
technical specifications, 7-4
CAS, 23-10
CES, 1-5
AES encryption, 23-10
alarms, 23-6
clocking, 23-7, 23-10
configuration, 23-10
congestion handling, 23-6
DS1/E1 port parameters, 23-8
expected ECID, 23-10
frames per packet, 23-10
interworking function, 23-5, 23-5
IWF, 23-5, 23-5
jitter buffer, 23-6
MAC address, 23-10
MEF-8 packets, 23-2, 23-5, 23-5
micro span, 24-2
overview, 23-2
payload length, 23-6
payload size, 23-10
QoS, 23-6
RTP header, 23-7, 23-10
services handling, 23-4
signaling mode, 23-10
timeslot mapping, 23-10
timing, 23-7, 23-10
Tx ECID, 23-10
CLI access protocols, 6-5
clocking
adaptive clock, 23-7, 23-10
BITS, 23-7, 23-10
differential clock, 23-7, 23-10

local oscillator, 23-7, 23-10
configuring
example of triple play, 22-22
IGMP, 11-11, 11-16
QoS, 15-25
triple play, 22-10
VLANs, 18-3
congestion management elements, 15-9
downstream rate limiting, 15-12
p-bit to queue mapping, 15-10
ports, 15-10
priority queue profile, 15-16
scheduler and queues, 15-10
switch, 15-9
T-CONT and GEM ports, 15-16
traffic scheduler, 15-11
constraints
Ethernet services configuration, 25-17
Ethernet services hardware, 25-17
Ethernet services system, 25-17
continuity check, 10-5
control data records, 11-15
counters
15-min counters, 16-2, 16-3
filters, 16-3
restrictions, 16-4
rolling counters, 16-2, 16-4
TCA thresholds, 16-3
cross-connect VLANs, 18-5
features, 18-5
D
data and IPTV service, 1-4
DBA, 15-21
DHCP
Option 60, 9-3
Option 82, 9-2
DHCP Option 90, 19-38
DHCP relay agent, 9-1
configuration, 9-3
function, 9-2
parameters, 9-3
virtual router configuration, 9-4

IN-3
Index
downstream forwarding equipment
downstream forwarding
VLAN translation with EtherType
classification, 18-18
downstream rate limiting, 15-12, 15-28
per ONT, 15-14
per service, 15-14
downstream tagging
at LT, 18-20
at ONT, 18-26
modes, 18-15
options, 18-2
pass-through VLANs, 18-22
stacked VLANs, 18-21
transmit to port with tag, 18-15
transmit to port without tag, 18-15
unstacked VLANs, 18-21
DS1
AMI, 23-9
B8ZS, 23-9
CES encapsulation, 23-4
encoding, 23-9
extended superframes, 23-8
framing, 23-8
jitter buffer, 23-6
line length, 23-9
modes, 23-8
port configuration, 23-8
structured mode, 23-8
superframes, 23-8
synchronization, 23-7, 23-10
unstructured mode, 23-8
DS1/E1
CES, 23-4
jitter buffer, 23-6
DS1/E1 CES, 1-5
DSCP, 15-5
p-bit mapping, 15-5, 15-32
DSX-1
line length, 23-9
dynamic multicast stream, 11-19, 11-19
IN-4
E
E1
AMI, 23-9
CES encapsulation, 23-4
encoding, 23-9
framing, 23-8
HDB3, 23-9
impedance, 23-9
jitter buffer, 23-6
modes, 23-8
PCM 30, 23-8
PCM 31, 23-8
port configuration, 23-8
structured mode, 23-8
unstructured mode, 23-8
egress rate, 15-9
eHCL, 40-2, 41-2, 42-2
redundancy, 40-2, 41-2, 42-2
EHNT
alarm LEDs, 37-7
interfaces and connectors, 37-7, 43-9
optical budgets, 43-4
optical module power and modulation
frequency, 43-3
power supply, 37-9, 43-10
supported optical modules, 43-2
EHNT-A, 37-1, 43-1
EMS
5520 AMS, 1-6
5523 AWS, 1-6
5528 WAM, 1-7
encoding, 23-9
Environmental conditions
equipment
configuring triple play example, 22-30

Index
equipment layout EVC models
equipment layout, 5-1

ONT equipment, 5-12
P-OLT equipment, 5-2
V-OLT equipment, 5-9
Ethernet frames
broadcast, 25-4
downstream tagging at ONT, 18-26
downstream tagging stacked VLANs,
18-21
L2 control protocol, 25-4
MEN to CPE, 25-4
multicast, 25-4
p-bit marking untagged frames, 18-27
pass-through tagging mode, 18-14
processing at the LT, 18-20
processing at the ONT, 18-25
stacked tagging mode, 18-13
tagging downstream at LT, 18-20
tagging options, 18-2
transmission over EVCs, 25-6
unicast, 25-4
unstacked tagging mode, 18-14
upstream tagging at LT, 18-22
upstream tagging at ONT, 18-27
VLAN tagging, 18-12
VLAN tagging modes, 18-13
Ethernet services, 25-2
configuration constraints, 25-19
configuration elements, 25-9
configuration models, 25-11
element relationships, 25-8
EVC flows, 25-11
EVC models, 25-8
EVC portals, 25-11
external EVC models, 25-16
hardware constraints, 25-17
internal EVC models, 25-12
maximum configurable EVC portals, 25-18
supported functionality, 25-2
supported ONTs, 25-18
system constraints, 25-17
Ethernet switch, 15-9
Ethernet virtual connections, 25-6
configuration elements, 25-9
element relationships, 25-8

Ethernet frame transmission, 25-6
EVC flows, 25-11
EVC portals, 25-11
external models, 25-16
implementation on 7342 ISAM FTTU,
25-8
internal models, 25-12
models, 25-8
multipoint-to-multipoint, 25-7
point-to-point, 25-6
rooted multipoint, 25-7
supported ONTs, 25-18
types, 25-6
EtherType classification, 18-18
upstream tagging, 18-32
EVC configuration
external, 25-16
internal, 25-12
ONT support, 25-18
EVC constraints
hardware, 25-17
maximum EVC portals, 25-18
system, 25-17
EVC elements
bandwidth, 25-11
EVC flows, 25-11
EVC portals, 25-11
p-bit translation profiles, 25-11
per service DSRL, 25-11
priority queue profiles, 25-11
QoS marker and session profiles, 25-11
S-VLAN, 25-11
EVC flows
EVC models, 25-11
external, 25-16
internal, 25-12

IN-5
Index
EVC portals GLT2
EVC portals
maximum configurable, 25-18
EVC types
multipoint-to-multipoint, 25-7
point-to-point, 25-6
rooted-multipoint, 25-7
EVC; See EVC types, EVC flows, EVC portals,
EVC configuration, EVC models
EXNT
alarm LEDs, 38-6
interfaces and connectors, 38-6
power supply, 38-7
EXNT-A, 38-1
extended superframes, 23-8
external EVC models, 25-8
T-CONT per CoS, 25-16
T-CONT per EVC, 25-16
types, 25-16
F
fan unit, 28-2, 29-2
fault isolation
alarms, 8-1
loopbacks, 10-4
Feature description, 2-1
FGU 04.04.00 features, 2-9
FGU 4.1 features, 2-13
FGU4.0 features, 2-14
FEC
upstream support, 4-6
FGU 04.04.00 release
features, 2-9
FGU 04.04.01 release
features, 2-9
IN-6
FGU 04.04.xx release

FGU 4.0 release
features, 2-14
FGU 4.1 release
features, 2-13
FGU 4.2 release
features, 2-12
FGU 4.3 release
features, 2-11
FGU 4.3.0 release
FGU 4.3.5 release
features, 2-11
FILT-A, 5-9
flexible mode
configuration options, 18-19
flow mirroring VLANs
associating with bridge ports, 18-6
features, 18-7
mode, 18-6
fractional TDM, 23-4
5523 AWS, 6-6
5528 WAM, 6-6
EMS functions, 6-6
functional description, 4-1
7342 ISAM FTTU functional blocks, 4-2
P-OLT functional blocks, 4-2
V-OLT functional blocks, 4-8
G
GEM
performance monitoring, 16-5
GEM port, 15-16
GLT2, 40-1, 41-1, 42-1
alarm LEDs, 40-4, 41-3, 42-4
dimensions, 40-7, 41-5, 42-5
features and application notes, 40-2, 41-2,
42-2
front panel, 40-4, 41-4, 42-4

Index
GLT2 (continued) IP edge aggregation and routing
identification, 40-2, 41-2, 42-2

interfaces and connections, 40-4, 41-4,
42-4
OBC, 40-2, 41-2, 42-2
physical description, 40-7, 41-5, 42-5
power, 40-7, 41-5, 42-5
version A and B difference, 42-3
GLT2-A, 5-8
GPON
optical line rate, 1-2, 7-8, 10-2
GPON 15 min counters
P-OLT, 16-3
gratuitous ARP requests
anti-spoofing, 17-19
GTRU-B, 33-1
front panel, 33-3
H
half proxy mode, 11-18
hardware constraints
hardware support
GLT cards for Ethernet services, 25-18
ONTs for Ethernet services, 25-18
HDB3, 23-9
header and tag manipulation, 18-12
HSI
HTTP digest, 19-38
I
iBridge
configuration, 12-8
iBridge mode
about, 12-4
ibridge VLANs, 18-4
features, 18-4
iBridge with VLAN pass-through
IGMP
configuration, 11-11, 11-16
provisioning IGMP system, 11-11,
11-16
provisioning video subscriber, 11-11,
11-16
requirements, 11-11, 11-16
expedited leave, 11-11
join and leave messages, 11-7
LT-to-ONT signaling, 11-7
disabled, 11-7
enabled, 11-7
processing limits, 11-10
proxy, 11-5, 11-6
signaling, 11-4
snoop, 11-6, 11-6
IGMP and multicast
IGMP expedited leave, 11-11
IGMP messages, 11-7
IGMP proxy, 11-5
IGMP signaling, 11-4
IGMP snoop, 11-6
indoor ONT
infrastructure
IP multicast and IGMP, 11-3
QoS, 15-2
ingress rate, 15-8
internal EVC models, 25-8
all-to-one bundling and multiple CoSs,
25-15
all-to-one bundling and single CoS, 25-14
bundling and CoS definitions, 25-12
bundling and multiple CoSs, 25-13
bundling and single CoS, 25-13
types, 25-12
IP edge aggregation and routing, 22-4

IN-7
Index
IP multicast MAC filters
IP multicast
control data records, 11-15
IGMP signaling, 11-4
ONT features, 11-20
P-OLT features, 11-20
packages, 11-12
access control, 11-13
creating, 11-13
generating CDR, 11-15
pre-view, 11-15
service networks, 11-17
IP subscriber, 11-17
PPPoE subscriber, 11-18
streams
dynamic, 11-19, 11-19
flow, 11-2
static, 11-19, 11-19
video management, 11-12
infrastructure, 11-3
IP multicast stream
dynamic, 11-19, 11-19
flow, 11-2
static, 11-19, 11-19
IP/MPLS network, 22-3
IWF, 23-5, 23-5
J
jitter buffer, 23-6
jitter buffer statistics, 19-39
L
LAG
CAC bandwidth check, 18-35
layer 2 forwarding, 12-2
forwarding unicast traffic in LT, 12-12
iBridge mode configuration, 12-8
downstream frame forwarding, 12-9
requirements, 12-9
upstream frame forwarding, 12-9
iBridge with VLAN pass-through
IN-8
MAC filters, 12-13

modes, 12-4
iBridge, 12-4
iBridge with VLAN pass-through,
12-6
VLAN cross-connect, 12-7, 12-8
pause frames, 12-13
rules, 12-2
classification of interfaces, 12-2
learning MAC addresses, 12-3
switching flood traffic, 12-3
subscriber scalability, 12-13
VLAN cross-connect configuration, 12-11
line length, 23-9
link trace, 10-5
Litespan
micro span, 24-2
loopbacks, 10-4, 10-5
LT
CAC, 18-36
downstream tagging, 18-20
downstream tagging for pass-through
VLANs, 18-22
downstream tagging for unstacked
VLANs, 18-21
18-21
Ethernet frames processing, 18-20
upstream tagging for stacked VLANs,
18-23
upstream tagging for unstacked VLANs,
18-24
upstream tagging pass-through VLANs,
18-25
LT-to-ONT signaling, 11-7
disabled, 11-7
enabled, 11-7
M
MAC, 40-2, 41-2, 42-2
MAC address, 23-10
MAC filters, 12-13

Index
MEF-8 OSMINE certification
MEF-8, 1-5
expected ECID, 23-10
overview, 23-2
packets, 23-4
payload size, 23-10
timestamps, 23-7, 23-10
Tx ECID, 23-10
MEN services; See Metro Ethernet services
Metro Ethernet services
7342 FTTU implementation, 25-4
Ethernet frames transmission, 25-4
EVC types supported, 25-6
micro span, 24-2
network example, 24-2
Microspan
workflow, 24-4
mirror packet VLAN tagging, 18-7
MoCA
RF video interaction, 21-2
modes
VLANs, 18-4
Modular ONT
TCA, 10-3
VDSL performance monitoring, 10-3
VoIP statistics, 19-39
modular ONT
modulation frequency, 43-3
multicast packages, 11-12, 11-13
multipoint-to-multipoint EVC, 25-7
N
NT
CAC bandwidth check for SHub VLAN,
18-35
NT redundancy
data synchronization, 13-4
multiple bridge port configuration, 13-3
multiple upstream switches, 13-3
single bridge port configuration, 13-2
O
OAM, 6-1
5523 AWS, 6-5
5528 WAM, 6-5
CLI access protocol option, 6-5
craft terminal, 6-4
management interfaces, 6-2
manual tasks, 6-7
ONT FLASH repair information, 6-8
OSMINE certification, 6-8
TL1 access protocol option, 6-5
OAM tests, 10-5
OLT rack, 44-1
OLTS-M, 5-6
MAC address label, 5-6
ONT
downstream tagging modes, 18-26
Ethernet services support, 25-18
RF video network example, 21-3
ONT equipment, 5-12
loopbacks, 10-4
ONT safety
electrostatic discharge, xvi
ONT UNI
Ethernet services configuration, 25-11
upstream tagging modes, 18-16
ONTs
Ethernet frames processing, 18-25
upstream tagging modes, 18-27
optical budgets, 43-4
optical module power, 43-3
optical module power and modulation
frequency, 43-3
Optical modules
Option 60, 9-3
Option 82, 9-2
OSMINE certification, 6-8

IN-9
Index
Outdoor ONT Power specifications
Outdoor ONT
outdoor ONT
Overview
5520 AMS, 1-6
7342 ISAM FTTU, 1-2
EMS
5523 AWS, 1-6
5528 WAM, 1-7
network ONT interfaces, 1-6
network P-OLT interfaces, 1-5
network V-OLT interfaces, 1-6
overview
element management system, 1-6
network interfaces, 1-5
P
P-bit, 15-4
profile, 15-6
CoS mapping, 15-5
DSCP mapping, 15-5
queue mapping, 15-10
UNI-side to network-side p-bit translation
profile, 15-6
p-bit marking
compatible configurations, 18-15
copy mode, 18-14
LT, 18-14
map mode, 18-14
S-VLAN, 18-14
set mode, 18-14
untagged frames, 18-27
P-OLT
AACU-A, 5-9
Backplane, 5-7
cards, 5-7
FILT-A, 5-9
GLT2-A, 5-8
loopbacks, 10-4
performance monitoring, 16-4, 16-5
Rack (ETSI), 5-2
IN-10
SANC-D, 5-9
technical specification, 7-2
P-OLT equipment
ALTS-N shelf, 5-4, 5-6
P-OLT equipment layout, 5-2
P-OLT functional blocks
line termination, 4-6
network termination, 4-4
P-OLT rack, 44-2
pass-through tagging, 18-14, 18-14
pass-through tagging upstream, 18-16, 18-28
pass-through VLANs
PAUSE frames, 12-13
PCM 30, 23-8
PCM 31, 23-8
counters, 10-3, 16-2
GEM ports, 16-5
GLT2, 16-5
GPON, 16-5
GPON optical line levels, 10-2
HSI, 16-5
IGMPI, 16-5
ONT, 16-4
P-OLT, 16-4, 16-5
RMON Ethernet statistics, 16-5
TCA, 10-3
VDSL, 10-3
VLAN, 16-5
PING, 6-8, 10-3
Pluggable units, 5-7
point-to-point EVC, 25-6
PON
CAC, 18-36
subscriber scalability maximum, 12-15
PON interfaces, 40-2, 41-2, 42-2
ports, 15-10
Power specifications, 7-9
input voltage, 7-9
power consumption, 7-10

Index
PPPoE relay agent RTP
PPPoE relay agent, 9-1

configuration, 9-5
function, 9-4
pre-view subscription, 11-15
processing limits
IGMP messages, 11-10
profile
bandwidth, 15-20
priority queue, 15-16
QoS marker, 15-7
Proxy ARP, 14-2
functions, 14-2
proxy ARP
persistence, 14-3
process flow, 14-2
static IP, 14-3
pseudo-wire, 23-4
Q
QoS, 23-6
bandwidth profile, 15-20
configuring, 15-25
configuring VLAN, 15-25
congestion management, 15-9
DBA, 15-21
downstream queueing and scheduling,
15-26
downstream rate limiting, 15-12, 15-28
DSCP to p-bit mapping, 15-32
Ethernet switch, 15-9
GEM port, 15-16
marker profile, 15-7
p-bit to queue mapping, 15-10
ports, 15-10
queues, 15-10
reserved bandwidth, 15-21
scheduler, 15-10
T-CONT, 15-16
traffic classification, 15-4
traffic policing, 15-8

traffic shaping, 15-20
upstream queuing and scheduling, 15-29
VLAN configurations, 15-25
queues, 15-10
p-bit mapping, 15-10
queuing and scheduling
downstream, 15-26
downstream at the LT, 15-28
downstream at the network, 15-27
downstream at the NT, 15-27
downstream at the ONT, 15-28
upstream, 15-29
upstream at the LT, 15-31
upstream at the NT, 15-32
upstream at the ONT, 15-30
R
Rack, 5-2
Backplane, 5-7
Raman reduction, 4-6
Redundancy
NT and LT, 13-4
relay agent, 9-1
DHCP, 9-2
DHCP configuration, 9-3
PPPoE, 9-4
PPPoE configuration, 9-5
remote loopbacks, 10-4
RF line rate, 1-2, 7-8
RF overlay breakdown, 21-2
RF video
about, 21-2
network example, 21-3
RF video service, 1-5
RMON Ethernet statistics, 16-5
rolling counters, 16-4
rooted-multipoint EVC, 25-7
RTCP
alarm, 19-40
statistics, 19-39
RTP, 23-7, 23-10

IN-11
Index
rules syslog
rules
S
S-VLAN, 23-10
CAC bandwidth check, 18-36
p-bit marking compatible configurations,
18-15
p-bit marking modes, 18-14
Safety guidelines
safety standard compliance
resistibility compliance, xii
SANC-D, 5-9, 46-1
scalability
VLAN bridging, 18-37
scalability of subscribers per PON, 12-15
scheduler, 15-10
secured MAC learning, 17-3
security
802.1X authentication, 17-11
8021.x authentication
assumptions, 17-11
port-based authentication, 17-12
protocols, 17-12
reauthentication, 17-14
restart scenario, 17-13
statistics and operating data, 17-13
user-session disconnection, 17-13
access control lists, 17-3
anti-spoofing, 17-19
DHCP Option 90, 19-38
HTTP digest, 19-38
RADIUS, 17-4
secured MAC learning, 17-3
SNMP, 17-6
SSH, 17-7
system log, 17-15
user accounts, 17-17
service capacity specifications, 7-4
IN-12
service networks
IP multicast, 11-17
services
delivery with TPSDA, 22-9
RF video, 21-2
SHub VLAN
CAC bandwidth capacity check, 18-35
signaling, 23-10
softswitch
5020, 19-6
source address anti-spoofing, 17-20, 17-21
source VLAN, 23-10
stacked tagging, 18-13
stacked VLANs
static multicast stream, 11-19, 11-19
statistics
AVGJTRBUFF, 19-39
CALLEDNO, 19-39
CALLINGNO, 19-39
DURATION, 19-39
OVERRUNS, 19-39
performance monitoring counters, 10-3,
16-2
PKTSDISC, 19-39
RTCP, 19-39
RXPKTS, 19-39
status reports, 10-3, 16-2, 16-5
TIME, 19-39
TXPKTS, 19-39
UNDERRUNS, 19-39
VoIP, 10-3, 19-39, 19-39
status reports, 16-5
structured TDM, 23-4
subscriber scalability
bridging table limitations, 12-15
implementation considerations, 12-13
limitations and restrictions, 12-16
maximum subscribers per PON, 12-15
superframes, 23-8
syslog, 17-15

Index
system constraints traffic scheduler
system constraints
system log, 17-15
T
T-CONT, 15-16
per CoS model, 15-17
per EVC model, 15-17
per service model, 15-17
per subscriber/per service model, 15-18
T1/E1
loopbacks, 10-4
tagging
downstream at LT, 18-20
downstream at ONT, 18-26
downstream for pass-through VLANs,
18-22
downstream for unstacked VLANs, 18-21
downstream stacked VLANs, 18-21
Ethernet frames, 18-12
options, 18-2
p-bit marking untagged frames, 18-27
pass-through mode, 18-14
stacked mode, 18-13
unstacked mode, 18-14
upstream at LT, 18-22
upstream at ONT, 18-27
upstream for stacked VLANs, 18-23
upstream for unstacked VLANs, 18-24
upstream in untrusted mode, 18-27
upstream pass-through VLANs, 18-25
VLAN mirror packets, 18-7
tagging mode, 18-18
EtherType classification, 18-18
tagging modes
compatible, 18-20
downstream, 18-15
Ethernet frames, 18-13
transmit to port with a tag, 18-15
transmit to port without a tag, 18-15
upstream, 18-16
upstream EtherType classification, 18-32
upstream flexible mode, 18-33
upstream flexible tagging, 18-19

upstream in VLAN translation, 18-28
upstream pass-through mode, 18-16, 18-28
upstream untrusted, 18-16
upstream VLAN translation tagging, 18-16
upstream VLAN translation with
EtherType classification, 18-17, 18-30
TCA, 10-3
TDM
line length, 23-9
capacity specifications, 7-4
distance and performance, 7-7
environmental conditions, 7-9
ONT connection capacity, 5-12
optical modules, 7-8, 43-2
P-OLT, 7-2
P-OLT connection capacity, 7-7
PON bandwidth, 7-7
power consumption, 7-9
service capacity specifications, 7-4
video coupler, 7-3
video coupler optical budget, 7-9, 52-3
timeslots, 23-4, 23-10
timing, 23-7, 23-10
TISPAN
VoIP support, 19-2
TL1 access protocols, 6-5
TPSDA
See triple play
traffic classification, 15-4
traffic meter, 15-8, 15-8
traffic policing
egress rate, 15-9
traffic flow types, 15-8
traffic policing elements, 15-8
burst size, 15-8
ingress rate, 15-8
meter, 15-8
downstream rate limiting, 15-14
LT, 15-11
NT, 15-11

IN-13
Index
traffic shaping elements upstream tagging
traffic shaping elements, 15-20

bandwidth profile, 15-20
DBA, 15-21
reserved bandwidth, 15-21
translation profile
C-VLAN p-bit to S-VLAN p-bit, 15-6
UNI-side p-bit to network-side p-bit, 15-6
transmit to port with tag, 18-15
transmit to port without a tag, 18-15
triple play, 22-1
architecture, 22-2
configuring, 22-10
configuring equipment, 22-11
configuring example, 22-22
configuring IGMP and multicast, 22-19
configuring QoS, 22-11
configuring services, 22-20
configuring VLAN for DHCP relay, 22-17
configuring VLANs, 22-16
delivery services with TPSDA, 22-9
example workflow, 22-29
FTTU access network, 22-6
IP edge aggregation and routing, 22-4
IP/MPLS network, 22-3
verifying example, 22-36
troubleshooting
alarms, 8-1
U
unicast traffic
forwarding, 12-12
cross-connect unicast downstream
traffic, 12-12
cross-connect unicast upstream traffic,
12-12
iBridge mode downstream, 12-12
iBridge mode upstream, 12-12
Unit data sheet
ALTS-N, 30-1, 45-1
ATRU-M, 31-1
ATRU-N, 32-1
ATRU-U, 33-1
BITS-B, 34-1
blank LT filter plate, 35-1
IN-14
blank NT filler plate, 36-1

GTRU-B, 33-1
SANC-D, 46-1
VCW2, 52-1
VCW4, 49-1, 50-1
connections, 49-4, 50-3
environmental requirements, 49-3,
50-3
features and application notes, 49-2,
50-2
optical safety, 49-3, 50-3
video coupler shelf, 48-1, 51-1
unit data sheet
EHNT-A, 37-1, 43-1
EXNT-A, 38-1
OLT rack, 44-1
overview, 26-2
unstacked tagging, 18-14
unstacked VLANs
unstructured TDM, 23-4
untagged frames p-bit marking, 18-27
untrusted tagging, 18-16
untrusted tagging mode, 18-27
upstream forwarding
classification, 18-18
upstream tagging
at ONT, 18-27
flexible mode, 18-19, 18-33
LT, 18-22
modes, 18-16
options, 18-2
pass-through mode, 18-16, 18-28
pass-through VLANs, 18-25
stacked VLANs, 18-23
unstacked VLANs, 18-24
untrusted, 18-16
VLAN translation mode, 18-16, 18-28
classification, 18-17, 18-30

Index
user accounts VLANs
user accounts, 17-17
V
V-OLT equipment layout, 5-9
V-OLT functional blocks
RF video service management, 4-9
RF video services, 4-8
RF video signal distribution, 4-8
upstream signal and data channels, 4-9
VCSL, 48-1, 51-1
VCW2, 52-1
connections, 52-5
environmental requirements, 52-4
optical safety, 52-4
VCW4, 49-1, 50-1
connections, 49-2, 49-4, 50-2, 50-3
environmental requirements, 49-3, 50-3
optical safety, 49-3, 50-3
VDSL
video
Raman reduction, 4-6
Video coupler
optical budget, 7-9, 52-3
video coupler equipment layout, 5-10
Video coupler rack, 47-1
Video coupler shelf, 48-1, 51-1
alarms, 51-3
connections, 51-3
video coupler subrack, 5-10

video coupler WDM tray, 5-10
video management, 11-12
VLAN
bridging, 12-13
configuring for QoS, 15-25
configuring for triple play for DHCP relay,
22-17
configuring triple play for DHCP relay
example, 22-33
VLAN cross-connect
VLAN for service model, 18-9
VLAN for subscriber model, 18-8
VLAN forwarding
cross-connect mode, 12-7
iBridge mode, 12-4
VLAN translation tagging mode, 18-16
VLAN translation upstream tagging, 18-28
classification, 18-17, 18-30
downstream forwarding, 18-18
upstream forwarding, 18-18
VLANs
7342 ISAM FTTU usage, 18-3
associating flow mirroring VLANs with
bridge ports, 18-6
bridging scalability, 18-37
broadcast domains, 18-3
C-VLAN learning mode, 18-4
CAC check, 18-35
CAC S-VLAN bandwidth check, 18-36
compatible tagging modes, 18-20
configuration method, 18-3
cross-connect, 18-5
definition, 18-3
downstream tagging at LT, 18-20
downstream tagging at ONTs, 18-26
downstream tagging for pass-through
VLANs, 18-22
downstream tagging for unstacked
VLANs, 18-21

IN-15
Index
VLANs (continued) VoIP

downstream tagging options, 18-2
18-21
Ethernet frame tagging modes, 18-13
Ethernet frames processing at the LT,
18-20
Ethernet frames processing at the ONT,
18-25
EtherType classification tagging, 18-18
flow mirroring features, 18-7
flow mirroring mode, 18-6
frame header manipulation, 18-12
frame tagging, 18-12
ibridge mode, 18-4
ibridge VLAN features, 18-4
mirror packet tagging, 18-7
models, 18-8
modes, 18-4
pass-through tagging mode, 18-14
purpose, 18-3
SHub VLAN CAC bandwidth check,
18-35
stacked tagging mode, 18-13
stacking, 18-20
transmit to port without a tag, 18-15, 18-15
unstacked tagging mode, 18-14
untagged frames p-bit marking, 18-27
upstream EtherType classification, 18-32
upstream flexible tagging mode, 18-19,
18-33
upstream pass-through tagging mode,
18-16
upstream tagging at LT, 18-22
upstream tagging at ONTs, 18-27
upstream tagging for stacked VLANs,
18-23
upstream tagging for unstacked VLANs,
18-24
upstream tagging in untrusted mode, 18-27
upstream tagging in VLAN translation
mode, 18-28
upstream tagging options, 18-2
IN-16
upstream tagging pass-through mode,

18-28
upstream tagging pass-through VLANs,
18-25
upstream untrusted tagging, 18-16
upstream VLAN translation tagging mode,
18-16
upstream VLAN translation with
voice gateway
G6, 19-4
voice service, 1-4
VoIP
5020 Softswitch mode, 19-2, 20-2
alarms, 19-39, 19-40
common features, 19-3
H.248-based softswitch, 19-6
modes of operation, 19-2, 20-2
service and protocol configuration, 19-13
SIP softswitch mode, 19-2, 20-2
SIP softswitch modes, 19-8
statistics, 6-8, 19-39, 19-39
TISPAN support, 19-2
voice gateway, 19-4
voice gateway mode, 19-2, 20-2

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
2010 Alcatel-Lucent. All rights reserved.

3FE 53568 AAAA TCZZA Edition 01

7342 ISAM FTTU OLT ETSI R04.06.11 Product Information 3FE 53568 AAAA TCZZA PDF

Uploaded by

Document Information

Original Description:

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

7342 ISAM FTTU OLT ETSI R04.06.11 Product Information 3FE 53568 AAAA TCZZA PDF

Uploaded by

Copyright:

Available Formats

Alcatel-Lucent 7342

INTELLIGENT SERVICES ACCESS MANAGER FIBER TO THE USER

3FE 53568 AAAA TCZZA Edition 01

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

Assistance and ordering phone numbers

Alcatel-Lucent 7342 ISAM FTTU P-OLT R04.06.11 May 2010

Alcatel-Lucent quality processes

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

may, or will, cause equipment damage or serious performance

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

May 2010 Alcatel-Lucent 7342 ISAM FTTU P-OLT R04.06.11

Procedures with options or substeps

Procedure 1 Example of options in a procedure

This is one option.

This is another option.

You must perform this step.

Procedure 2 Example of required substeps in a procedure

This is the first substep.

This is the second substep.

This is the third substep.

You must perform this step.

Multiple PDF document search

Alcatel-Lucent 7342 ISAM FTTU P-OLT R04.06.11 May 2010

Procedure 3 To search multiple PDF files for a common term

Open Adobe Acrobat Reader.

Enter the search criteria.

Click on the All PDF Documents In radio button.

Select the folder in which to search using the drop-down menu.

Click on the Search button.

May 2010 Alcatel-Lucent 7342 ISAM FTTU P-OLT R04.06.11

ETSI P-OLT safety guidelines

Safety instruction boxes

Alcatel-Lucent 7342 ISAM FTTU P-OLT R04.06.11 May 2010

ETSI P-OLT safety guidelines

The following is an example of the Warning box.

Safety related labels

May 2010 Alcatel-Lucent 7342 ISAM FTTU P-OLT R04.06.11

ETSI P-OLT safety guidelines

Hazardous voltage warning label

Laser warning labels

Figure 4 shows a laser classification label. Laser classification labels may be

Alcatel-Lucent 7342 ISAM FTTU P-OLT R04.06.11 May 2010

ETSI P-OLT safety guidelines

CLASS 1 LASER PRODUCT

a warning that calls attention to the invisible laser radiation

May 2010 Alcatel-Lucent 7342 ISAM FTTU P-OLT R04.06.11

ETSI P-OLT safety guidelines

INVISIBLE LASER RADIATION

Laser Warning Label

CLASS 1 LASER PRODUCT

RAYONNEMENT LASER CLASSE 1

CLASE 1 DEL LASER

Protective grounding terminal

Figure 7 shows the symbol for an earth terminal.

Alcatel-Lucent 7342 ISAM FTTU P-OLT R04.06.11 May 2010

ETSI P-OLT safety guidelines

Safety standards compliance

EMC, EMI, and ESD standards compliance

EN 300-386 V1.3.2 (2003-05): Electromagnetic Compatibility and Radio

Spectrum Matters (ERM): Telecommunications Network Equipment;

Environmental standards compliance

Equipment safety standards compliance