3FE-77621-AACA-FMZZA-01-ISAM R6 - 5 - 02 Customer Release Note

7360 ISAM FX
7362 ISAM DF/SF
R6.5.02
CUSTOMER RELEASE NOTE
3FE-77621-AACA-FMZZA
Edition: 01
September 30, 2021
Released
© 2021 Nokia. Nokia Confidential Information

Use subject to agreed restrictions on disclosure and use.
Nokia is committed to diversity and inclusion. We are continuously reviewing our customer documentation
and consulting with standards bodies to ensure that terminology is inclusive and aligned with the industry.
Our future customer documentation will be updated accordingly.
-------------------------------------------------
This document includes Nokia proprietary and confidential information, which may not be distributed or
disclosed to any third parties without the prior written consent of Nokia.
This document is intended for use by Nokia’s customers (“You”/”Your”) in connection with a product
purchased or licensed from any company within Nokia Group of Companies. You agree to notify Nokia of
any errors you may find in this document; however, should you elect to use this document for any purpose(s)
for which it is not intended, You understand and warrant that any determinations You may make or actions
You may take will be based upon Your independent judgment and analysis of the content of this document.
Nokia reserves the right to make changes to this document without notice. At all times, the controlling
version is the one available on Nokia's site.
No part of this document may be modified.
NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED
TO ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-
INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN
RELATION TO THE CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA BE LIABLE
FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT,
INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF
PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT
MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE
CASE OF ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.
Copyright and trademark: Nokia is a registered trademark of Nokia Corporation. Other product names
mentioned in this document may be trademarks of their respective owners.
© 2021 Nokia.
2/72 Edition 01 - RL 30-Sept-2021
Contents
1 About this Document ....................................................................................... 5
2 Release Content ............................................................................................... 6
2.1 Introduction ............................................................................... 6
2.2 New Features............................................................................. 6
2.3 Feature Change ........................................................................16
2.4 R6.5.02 Corrections/Improvements ...........................................17
2.5 R6.5.01 Corrections/Improvements ...........................................21
2.6 R6.5 Corrections/Improvements ...............................................25
3 Delivery Information ..................................................................................... 31
3.1 Delivered Software ..................................................................31
3.2 Delivered XDSL Proxies ..........................................................31
3.3 Delivered Documentation .........................................................32
3.3.1 Documentation Restrictions/Inconsistencies .................32
4 Supported Hardware ..................................................................................... 33
5 Compatibility ................................................................................................ 36
5.1 AMS-ISAM Compatibility .......................................................36
5.2 TL1 and CLI ...........................................................................36
5.2.1 CLI/TL1 commands & parameters phased out ..............36
6 Known Restrictions ....................................................................................... 38
6.1 Generic Restrictions .................................................................38
6.2 R6.5.02 Restrictions .................................................................57
6.3 Known Restrictions from Previous Releases ..............................59
7 Migration ...................................................................................................... 61
8 Installation Manual ....................................................................................... 62
9 Validated Voice Supplementary Services........................................................ 63
9.1 H.248 POTS Supplementary Services .......................................63
9.2 SIP POTS Supplementary Service ............................................63
10 Voice Package Performance ........................................................................... 65
10.1 H.248 POTS Performance ........................................................65
10.2 SIP Performance ......................................................................65
11 Premium Packages ........................................................................................ 66
Edition 01 - RL 30-Sept-2021 3/72
11.1 Premium Packages Equipment..................................................66
11.2 Premium Packages Connectivity ...............................................68
11.3 Premium Package Video Applications ......................................69
11.4 Premium Packages Transport ...................................................70
11.4.1 Premium Package Reference Timing Source ................70
11.4.2 Premium Package Type-B PON Protection ..................70
11.4.3 Premium Package 40 km Differential Distance PON
Operation 71
11.4.4 Premium Package NGPON2 Multi-Lambda .................71
11.4.5 Premium Package XGS-PON and NGPON2 Enhanced
10Gbps Upstream ....................................................................72
11.4.6 Premium Package Ethernet OAM ................................72
11.4.7 VULA Uplink SW Package .........................................72
4/72 Edition 01 – RL 30-Sept-2021
1 About this Document
This document for products 7360 ISAM FX and 7362 ISAM DF/SF provides
information for following software release:
ISAM R6.5.4.8.1
ISAM OFLMT R6.5.4.8.1
ISAM Push-button Migration Tool V3.4.42
Edition 01 - RL 30-Sept-2021 5/72
2 Release Content
2.1 Introduction
This document provides delivery information of the ISAM software release 6.5.02.
This delivery includes support for 7360 ISAM FX and 7362 ISAM SF/DF for all markets.
This delivery includes support for FX, SF and DF equipment practices. There is no support for
FD, MX, SX and DX equipment practices in this release and the XD equipment practice was
discontinued since release 4.0.
2.2 New Features

A general description of the ISAM (Intelligent Service Access Manager) and its features is given
in the "System Description" which is part of the ISAM Customer Documentation package.
Following table gives an overview of the new features supported in R6.5, R6.5.01 and R6.5.02.
Platform Domain
7360 ISAM FX: BFD functionality improvements for routed
networks - IES support (R6.5)
Feature Content:
 Support of BFD over IPv6 for IES/Base router. The BFD can be used for BGP6 Next-Hop
tracking or static route next-hop tracking. The BGP or static routes can be used for RPF
check for PIM-SSM IPv6 multicast source and can be used to switch to alternate path
available in a short span of time (within 1 sec).
 Supported NTs: FANT-F, FANT-G and FANT-H.
Value or Application:
 Service providers can use the BFDv6 to detect IPv6 multicast reverse path connectivity
failure to IPv6 multicast source. Using BFDv6, the reverse-path failure to IPv6 multicast
source is detected and PIM-SSM is used to switchover the multicast streams via alternate
path with maximum of 1 second outage for all IPv6 multicast streams using the failed path.
7360 ISAM FX: Support of IPDR streaming protocol versioning support (R6.5)
Feature Content:
 Some service providers need to interoperate with IPDR collector which supports IPDR
version message passing the transport protocol and the port number to be used for IPDR
export from 7360 ISAM FX IPDR exporter.
On the 7360 ISAM FX the corresponding filters must be supported to allow such IPDR
version messages to be forwarded to internal NT CPU cores and DPoE system.
 IHUB should facilitate IPDR version message exchange from external IPDR collector to
IPDE exporter at DPoE subsystem.
6/72 Edition 01 – RL 30-Sept-2021
 Supported NTs: FANT-F, FANT-G, FANT-H.
 IPDR streaming protocol version number are useful for IPDR streaming records for Cable
MSOs.
7360 ISAM FX: Intra-shelf Type-B protection with FGLT-D/FWLT-C/FGUT-A (R6.5)
Feature Content:
 Type-B protection on following LTs:
o FWLT-C/FGUT-A pure GPON mode with GPON-managed profile
o FWLT-C/FGUT-A pure XGS-PON mode with GPON-managed profile
o FWLT-C/FGUT-A pure XGS-PON mode with NGPON-managed profile
o FWLT-C/FGUT-A with MPM mode
o FGLT-D; FGLT-D can work with FGLT-B in protection pairs.
 Dimensioning & Scalability:
o The maximum number of protection groups in the same 7360 ISAM FX shelf = 126
o The maximum number of simultaneous switch-overs (LT failure case with full
protection) = 16 protection groups for FWLT-C/FGUT-A/FGLT-D.
o The maximum number of ONTs connected to each protection group = 64 ONTs per
protection group (for MPM mode, 64 ONTs with a mixture of GPON & XGS
ONTs).
Restrictions:
 Board replacement scenarios (other than the FGLT-D replacing FGLT-B scenario)
 FWLT-C/FGUT-A Type-B protection is not supported when the cage mode is GPON &
optical module is MPM.
 PON protection on FGLT-D/FWLT-C/FGUT-A.
7360 ISAM FX: Intra-shelf Type-B protection with FGLT-E (R6.5)
Feature Content:
 Support intra-shelf Type-B protection with FGLT-E.
 Dimensioning & scalability:
o The maximum number of protection groups in the same 7360 ISAM FX shelf =
126.
o The maximum number of simultaneous switch-overs (SWO) = 16 Protection
Groups (PGs), i. e. half of the PON ports protected on each FGLT-E.
o The maximum number of ONTs connected to each protection group = 64 ONTs per
protection group
 PON protection on FGLT-E (32 port GPON board).
Edition 01 - RL 30-Sept-2021 7/72
7362 ISAM DF/SF: Internal clock failure detection and alarm reporting
for DF-16GW, DF-8G & SF-8GW (R6.5)
Feature Content:
 Support auto monitoring of the internal clock status and if abnormal; raise an alarm based
on the alarm configuration (the default is no alarm and if the timing sync is enabled an
alarm is required to be enabled manually).
 These alarms are useful in troubleshooting and for fault isolation of the internal clock
source.
7360 ISAM FX: IPv6 management extensions: RADIUS & TACACS (R6.5)
Feature Content:
 Support a RADIUS client for IPv6 for the following use cases;
o Operator authentication
o 802.1X authentication
 Support authentication even if the RADIUS server is on VPRN.
 Support a TACACS+ client for IPv6 for the following use case;
o Operator authentication
 Supported NTs: FANT-G and FANT-H.
7360 ISAM FX: Enhancements for dual-stack Access Network

(Scaling of ARP) (R6.5)
Feature Content:
 7360 ISAM FX in l3host mode, apart from the current 16K ARP + 32K ND scale, also
supports up to 64ARP + 64K DHCPv4 entries with ND routes.
Additionally; IPv4 & IPv6 route entries to be reduced to a minimum of 2K. This ensures
OLTs serving in high customer density area, should be deployable with reasonable reduced
number of routes to connect to uplink networks.
 Support additional IPv4 host devices behind the ONT.
 Increase in splitting ratio of PON lines.
7360 ISAM FX: OSPF with IPv6 on VPRNs (R6.5)
Feature content:
 OSPFv3 for the IPv6 router is now also supported in Virtual Private Router (VPRN)
instances for exchanging IPV6 routes.
 In Nokia OLT the service architecture was implemented using VPRN instances for every
service.
 This feature is useful for service providers deploying IPv6 based networks employing
OSPFv3 in core network for faster convergence times compared to BGP this feature is very
useful.
8/72 Edition 01 – RL 30-Sept-2021
 Faster convergence time as compared to BGP for VPRN.
7360 ISAM FX: New FANT-H BC variant to support FX-4/8 in

cabinet application (R6.5.01)
Feature Content:
 The FANT-H BB variant supports application in Class 1 environment (Central office). For
cabinet application which are with no temperature control environment (outdoor class 2
environment) a new variant (BC) was required which can cater to outdoor extreme
variations.
 Complies to GR 63 and GR 3108 Class 2.
 Full feature parity with FANT-H BB (ANSI) in FX-8/4 shelf.
 ANSI variant (FANT-H BC) conforming to ANSI standards
 Supports two additional SFP/SFP+ cages which can support 1Gig or 10Gig SFP/SFP+
optics.
 Migration support from legacy NTs based on type of optics plugged into the standby
FANT-H BC NT.
Restrictions:
 Supported only on FX-4 & FX-8 shelfs. Not supported on the FX-16 shelf.
 FANT-H BC variant ANSI compliance for cabinet applications.
 FANT-H BC Supported Temperature ranges in the following operational conditions:
o Central Office (CO) environment:
5oC to 40oC (41oF to 104oF) for normal operating range, or
-5oC to 50oC (23oF to 122oF)
o Class2 outside plant (OSP) environment:
-20oC to 40oC (-4oF to 104oF) for normal operating range, or
-40oC to 65oC (-40oF to 149oF)
 FANT-H BC NT is suitable for outdoor class 2 cabinet environments. Lower power
consumption and improved thermals than FANT-H BB variant for extended temperature
ranges.
7360 ISAM FX: New FANT-F AF (ETSI) and FANT-F BF (ANSI) variants (R6.5.01)
Feature Content:
 New FANT-F AF (ETSI) and FANT-F BF (ANSI) variants were required to be introduced
because of parts obsolescence on legacy FANT-F NT’s (FANT-F AE & FANT-F BD).
 These NT’s can be interchanged with previous version of the FANT-F’s once 7360 ISAM
FX is upgraded to R6501 or higher.
 These new FANT-F’s bear the same form, fit or function in comparison to previous version
of FANT-F for both ETSI & ANSI market.
Edition 01 - RL 30-Sept-2021 9/72
Value of Application:
 Addresses parts obsolescence on FANT-F AE and FANT-F BD variant.
 FANT-F AF can be used in the following operations conditions:
o in a Central Office (CO) environment with multiple 7360 ISAM FX subracks (as
described in the 7360 ISAM FX Hardware Installation Manual), the ambient
temperature can be between -5°C to +45°C
o in a single 7360 ISAM FX subrack, the ambient temperature can be between -40°C
to +65°C
 FANT-F BF can be used in the following operational conditions:
o 5°C to 40°C (41°F to 104°F) normal operating range, or -5°C to 50°C (23°F to
122°F), in a central office (CO) environment
o -20°C to 40°C (-4°F to 104°F) normal operating range, or -40°C to 65°C (-40°F to
149°F), in a Class 2 outside plant (OSP) environment
7360 ISAM FX: Retrieval of actual power consumption (R6.5.01)
Feature content:
 Ability to retrieve the actual power consumption of a 7360 ISAM FX shelf.
 Monitoring the actual power consumption of an OLT can be useful in the context of
managing expenses (for energy).
 Monitoring the actual power consumption of an OLT can be useful to verify whether the
power plant has been correctly dimensioned.
 Higher than expected power consumption can be an indication of an imminent failure.
Applicable Standards
 IETF RFC 7326: “Energy Management Framework”
7360 ISAM FX: Retrieval of power related metric (R6.5.02)
Feature content:
 Ability to retrieve power consumption, energy measurement data and configuration of
energy measurement parameters by introducing additional CLI configuration and retrieval
commands.
 Store history of energy measurement data on ISAM.
 Information retrieval via CLI and SNMP management interface.
 Monitoring the actual power consumption of an OLT can be useful in the context of
managing expenses (for energy).
 Monitoring the actual power consumption of an OLT can be useful to verify whether the
power plant has been correctly dimensioned.
 Higher than expected power consumption can be an indication of an imminent failure.
 Historic information can help in identifying variations in power consumption over time.
7362 ISAM DF: LLDP support on uplink ports (R6.5.01)
10/72 Edition 01 – RL 30-Sept-2021
Feature Content:
 This feature implements LLDP support on the uplink ports of 7362 ISAM DF-16GW.
 LLDP support on the DF-16GW uplink ports for network topology discovery and device
inventory reporting based on IEEE 802.1AB.
 Support LLDP port-id-subtype configuration such that “Port info” if-index can be
translated to meaningful information about that port (e.g. if-index 69238784 is mapped to
“2/1/1” shown as “Port info” in the CLI command “show lldp neighbors”).
 LLDP must be supported on top of physical Ethernet ports only (not on top of a LAG port)
 Support the standard LLDP-V2-MIB but convert it to SMIv1 (IACM does not support
SMIv2).
Value or application:
 Targeted for operators who use Passive Optical LAN and are used to building network
maps.
7360 ISAM FX: Antitheft Protection for FWLT-C, FGUT-A, FGLT-D and FGLT-E
(R6.5.01)
Feature Content:
 Anti-theft protection on FWLT-C, FGUT-A, FGLT-D and FGLT-E.
 The license counter counts the number of boards (LT and NT) in the system that are
plugged in & receive the anti-theft protection
 Discourage unauthorized removal and stealing of boards from shelves.
7360 ISAM FX: Antitheft Protection for FANT-H

(R6.5.02)
Feature Content:
 Extending Anti-theft protection to FANT-H NT card.
 Protect FANT-H against unauthorized removal from the network
 Discourage unauthorized removal and stealing of NT and other LT boards from shelves.
 Operators deploying cards in a remote location can be safeguarded against theft.
7362 ISAM DF: UNI loopback and GPON functionality (R6.5.01)
Feature Description:
 New OLT command to initiate/stop a loopback at ONU UNI with an optional time-out on
7362 ISAM DF-16GW
 Scope limited to ONU UNI loopback only with G-010G-Q and G-040G-B
 Troubleshooting at ONT UNI level.
Edition 01 - RL 30-Sept-2021 11/72
7360 ISAM FX: FELT-B: Cross-LT LAG with load sharing (R6.5.02)
 Extend the cross-LT LAG with a load sharing option (next to the existing Active/Standby);
o Maximum 8 links (ideally 4+4 to balance the load equally)
o Maximum 80 Gb/s worth of traffic per LAG
o On all interface types (UNI, NNI and uplink)
 Any combination of single port, intra-LAG and cross-LT LAGs (A/S and A/A) can be
supported on the card, provided we stay with the resources available of the card (resource
management is performed at provisioning time)
 Cross-LT LAGs allow to combine board and link protection.
 The cross-LT LAG load sharing option allows a better link utilization in normal conditions
(all links are active) than the active/standby option (max 50% of the links can be used). In
case of bard failure, the offered LAG load might be reduced by 50%.
7360 ISAM FX: Autoboot feature and Linux based IMAT Tool support
for FANT-G and FANT-H (R6.5.02)
Feature Content:
 Linux-based IMAT tool to allow loading configuration on the Compact Flash card which
can then be read by FANT-G and FANT-H NT. The primary use case for this tool is to
allow ZTP configuration.
 Autoboot feature is now extended to FANT-G and FANT-H which allows the
configuration file loaded on the CF via IMAT tool to be read & applied during boot-up
phase of the NT. Once the configuration is applied ISAM reboots again is activated with
the updated configuration.
 The primary use case for IMAT tool & Autoboot feature is to allow ZTP configuration
using configure to order process.
 The feature was already available on FANT-F and is now extended to FANT-G and
FANT-H.
7360 ISAM FX: GPRS Tunnel Protocol based hashing for

LAG load balancing (R6.5.02)
Feature Content:
 GTP (GPRS Tunnel Protocol) protocol-based hashing to support load balancing of 5G
traffic on 7360 ISAM FX.
 Load balancing of traffic on 7360 for high bandwidth use case of 5G.
7360 ISAM FX: Pluggable passive CEx cassette enabling coexistence
12/72 Edition 01 – RL 30-Sept-2021
of 25G PON with GPON/XGS/MPM (R6.5.02)
 A new pluggable passive module, called WDM1-M, is introduced to enable wavelength
co-existence of 25G PON (www.25gspon-msa.org) with existing GPON and/or XGS-PON
technologies on a common ODN.
 This new cassette provides the same density and interfaces as the existing WDM1r-H
cassette and is compatible with the existing 1RU CEx enclosure.
 This new cassette enables the following scenario’s :
o XGS-PON and 25G PON,
o MPM (XGS-PON+GPON) and 25G PON,
o GPON and 25G PON.
 The lambdas used for 25G PON that make the above wavelength co-existence scenario’s
possible are : upstream 1286+/-2nm, downstream 1358+/-2nm.
 Combine multiple PON technologies on the same PON, enabling 25G PON overlay on
ODNs where GPON and/or XGS are already deployed.
 For loss budget considerations, please check the Unit Data Sheet of the cassette and of the
optics, or contact your Nokia representatives.
7360 ISAM FX: Management of external amplifier using GE i/f

on 7362 ISAM DF/SF (R6.5.02)
Feature Content:
 EDFA (Erbium Doped Fiber Amplifier) is a device for optical amplification, typically
used by cable providers to amplify CATV 1550nm and combine it with GPON on the
same ODN/ONT.
 EDFA can support untag mgt traffic(alarm) only with UTP interface.
 This feature requires to transfer untagged management traffic from the 3rd party device
called EDFA via 7362 ISAM DF/SF to the upstream AN switch.
 Applicable to cable operators to manage the management traffic of EDFA via the 7362
ISAM DF/SF.
7360 ISAM FX: 25G PON enablement on ISAM FX equipped with

Quillion-based FWLT-C and FGUT-A (R6.5.02)
Feature Content:
 This feature introduces the SW support of 25G PON on the 7360 ISAM FX platform
equipped with FWLT-C and/or FGUT-A.
 On a 7360 ISAM FX system loaded with this new release, individual FWLT-C and/or
FGUT-A line cards can be upgraded to 25G PON via a board-level license, necessitating
AMS for its management. This license is strictly enforced, i.e. by default (without license)
the system will reject any 25G PON related configuration attempt.
 Each LT supports up to 8 ports configured for 25G PON operation, but the operator is free
Edition 01 - RL 30-Sept-2021 13/72
to only use a subset of the LT PON ports in 25G PON mode and use other modes (e.g.
GPON, XGS-PON, MPM) on different ports.
 It is possible to configure 25G PON homogeneously at LT-level during slot planning, or
later at individual port-level. Note that for an (even-numbered) port to be configured in
25G PON mode, its neighbouring (odd-numbered) port must not be used for other
purposes. The 25G PON operational-mode is supported in combination with new 25G
PON capable OLT optics.
 The 25G PON technology necessitates the FANT-H, with a 100Gbps backplane link
speed.
 In the present release the solution is asymmetric, meaning that the downstream line rate is
25Gbps while the upstream line rate is 10Gbps.
 The 25G PON enablement on 7360 ISAM FX, enabled by the latest generation Quillion-
based LT cards, provides operators the means to extract even more value from their fiber
investments and existing infrastructure. 25G PON is built-in the new FWLT-C and FGUT-
A cards, meaning that any operator deploying FWLT-C or FGUT-A is by definition "25G
PON ready" today.
 This technology enables new kinds of high-end use cases for PON, like Mobile Anyhaul
and Business/Enterprise services, that can’t be offered by existing technologies. 25G PON
can easily co-exist with GPON and XGS-PON technologies, on the same ODN (even in
case of MPM deployments with GPON+XGS), thanks to the fact it uses a dedicated, non-
overlapping pair of downstream and upstream wavelengths.
 Applicable Standard: 25GS-PON MSA (www.25gs-pon-msa.org)
Transport Domain
7360 ISAM FX: SLID-only authentication (R6.5)
Feature Content:
 A new SLID-pre authentication mode is introduced.
o In this mode and with SN-bundling disabled, only the SLID is used for
authentication
o When an activating ONU’s SLID matches the configured SLID; it is authenticated,
regardless of the SN matching or not (unbundled case).
o When an activating ONU’s SLID doesn’t match the configured SLID;
authentication fails, regardless of the SN matching or not.
o When SN and SLID are bundled, both the SN and SLID of an activating ONU must
match the configured SN and SLID for authentication to succeed. If any of these
does not match authentication fails.
 Applicable to all GPON and U-NGPON boards and all cage modes:
o GPON (GPON management model)
o XGS-PON (GPON and NGPON2 management model)
o MPM (GPON management model)
o NGPON2 (NGPON2 management model)
7360 ISAM FX/7362 ISAM DF/SF: Improve ONU dying gasp alarm behavior (R6.5)
14/72 Edition 01 – RL 30-Sept-2021
Feature Content:
 The dying gasp raise criteria is as follows: If an ONU goes off the PON (i.e. missing burst)
preceded by a DGi indication (PLOAM for GPON or bit in burst header for
NGPON2/XG(S)PON) a dying gasp alarm should be raised. Not in any other case. E.g. a
dying gasp indication alone should not trigger any action from the OLT or an alarm. The
PON MAC needs to make sure the DGi behavior complies with this for both GPON and
the NGPON technologies.
 Supported on the following platforms:
o 7360 ISAM FX: all GPON and XGS-PON/TWDM-PON/MPM LTs,
o 7362 ISAM DF-16GW, 7362 ISAM SF-8GW and 7362 ISAM DF-8G.
7360 ISAM FX: Support of OLT-ONT lock feature (R6.5)
Feature Content:
 Allow (an authorized operator) to lock and unlock an ONT to an OLT by sending an OLT
specific unique key.
 Allow to unlock (a) previously locked ONT(s).
The OLT will provide the option so that an authorized/normal operator can
update the existing key on an ONT or range of ONTs with a new key.
 Supported on;
o NT: FANT-F, FANT-G and FANT-H,
o LT: FGLT-B and
o ONT: G-2425G-A & G-140-WG.
7360 ISAM FX: Upstream AES encryption and bi-directional OMCI encryption
for MPM and XGS oper-modes (R6.5.01)
Feature Content:
 AES encryption on FWLT-C/FGUT-A for XGS-PON dual-rate in 7360 ISAM FX for both
pure XGS-PON mode (including NGPON2-managed) and MPM modes:
o configurable upstream AES encryption of the XGEM payload on a per ONU basis
(for all non-default XGEM ports). This is allowed by the new AES decryption
capability of FWLT-C and FGUT-A.
o bi-directional AES encryption of the default XGEM port (carrying OMCI traffic) on
a per ONU basis. Per ITU-T standard (G.9807.1 C.15.5.1), the encryption of the
default XGEM port is always bi-directional: as soon as the OLT encrypts it
downstream, the ONU is expected to automatically encrypt in the upstream. Since
Quillion-based XGS-capable LTs can support upstream decryption capabilities (see
above), it is now possible to enable bi-directional encryption of the OMCI XGEM
port.
 Security enhancement for bi-directional encryption of the OMCI XGEM port.
7360 ISAM FX: Default range mode for GPON changed

from ‘normal mode’ to ‘alien tolerant mode’ (R6.5.01)
Edition 01 - RL 30-Sept-2021 15/72
Feature content:
 Alien mode becomes the default range mode for GPON, instead of ‘normal mode’.
 Offers improved performance in ranging and stability of ONT with various OLT optics.
 The default ranging-mode changed to ‘alien-tolerant’ for the GPON channel of ALL the
optics that have GPON channel or GPON channel inside. This feature covers all versions
of GPON, XG(S) MPM and SFP-DD dual GPON optics for newer generation line cards
(FWLT-C, FGUT-A, FGLT-D, FGLT-E).
7360 ISAM FX: Support of 64 bit ethernet PM rolling counters using

standard OMCI (R6.5.01)
 Support of 64 bit ethernet PM rolling counters using standard OMCI will become possible
by using the “Ethernet frame extended PM 64 bit” ME that is now included in ITU G.988.
 Target HW:
o NT: FANT-F/FANT-G
o LT: NGLT-C/FGLT-B (as main install base) and
o new LTs based on our own ASIC (FGLT-D, FWLT-C).
o ONT: XS-0525X-P
7360 ISAM FX: Flat scheduling combined with CoS based trTCM (R6.5.02)
 Flat scheduling combined with CoS based trTCM (8 CoS level)
 Applicable on:
o NT: FANT-F, FANT-G, FANT-H
o LT: FGLT-D, FWLT-C, FGUT-A
o Applicable for GPON, XGS and MPM modes.
 Flat scheduling improvement on FGLT-D, FWLT-C, FGUT-A
2.3 Feature Change

Change of the System Vendor ID; from R5.8 on, the System Vendor ID has been changed from
"ALCB" into "NOKB" on xDSL cards for ISAM FX.
16/72 Edition 01 – RL 30-Sept-2021
2.4 R6.5.02 Corrections/Improvements
Nr Id Rel. note entry
Equipment
1 BBN-25153 Title: Major Alarm LED is active, but no major alarms are observed in FX-8
(1906732) Problem: Major Alarm LED is active on the NGFC faceplate, but no major alarms are
observed in CLI.
2 BBN-14338 Title: "Lag Subgroup Switchover Failed" alarms were not correctly cleared in
(1799634) some scenarios.
Problem: Wrong "Lag Subgroup Switchover Failed" alarms were raised and remained
outstanding, on some scenarios, though the subgroup got switched over successfully.
3 BBN-12586 Title: 7362 ISAM DF-8G - power-oper-mode is always dc-local

(1698142) Problem: The output of "show equipment power", power-oper-mode is always shown
as dc-local, no matter actual input is dc or ac.
GPON OLT
4 BBN-12684 Title: ONT discard omci message because of omic mic error
Problem: GponMgnt send the wrong onuid to glob
5 BBN-14386 Title: Few ONTs down after OLT restart
(1987393, Problem: A number of ONTs stay down after migration. ONT provisioning failure and
2062681) ONT OMCI failure alarms are raised due to AES encryption status mismatch between
OLT and ONT. Issue only occurs if AES encryption is enabled. It is applicable on all
GPON boards, XGSPON is not impacted.
6 BBN-20257 Title: PONLOS wrongly reported after all ONUs under this PON power outage
(1926871) Problem: 512 ONT in the same LT go offline at the same time due to power outage and
no DGi alarm is not reported. State change requires more than 5s.
7 BBN-24228 Title: FWLT-C fails to initialize after LT slot conversion from FGLT-B
(2121357) Problem: Two cases of FWLT-C failing to initialize after performing slot conversion
from FGLT-B were reported during production deployment. LT enters a continuous
reboot loop and may enter service but will not be operationally active. For example, no
ONT's will range. It was also reported that system performance was sluggish during LT
reboot cycle, CPU loading did not identify any high running task.
8 BBN-12620 Title: After a huge storm of DG alarms (due to a power outage ), it took 30+
(1755820) minutes to restore all traffic due to slow GLOB provisioning.
Problem: After a huge storm of DG alarms (due to a power outage ), it took 30+
minutes to restore all traffic due to slow GLOB provisioning due to an internal mailbox
issue.
9 BBN-23575 Title: TYPE-B behavior issue on FGLT-B
Problem: A post glob reset in a TYPE-B setup, can leave the ONT status in inactive
state.
10 BBN-18629 Title: "ont-olt" distance is not accurate
(1801250) Problem: The "ont-olt" ranging distance value is not correctly calculated for ISAM
7362 DF-16GW & DF-8G.
11 BBN-20316 Title: ONTs WIFI password configured via TL1 HGUTR069 is changed after an
(2086983) OLT reset.
Problem: ONTs WIFI password configured via TL1 HGUTR069 is changed after an
OLT reset. It seems they are cut to only 8 characters
12 BBN-20536 Title: FANT-H – Undersized packets dropped when NT-B is unlocked
Edition 01 - RL 30-Sept-2021 17/72
(1906594) Problem: When downstream frames are sent across the NT-NT backplane links they
may be dropped if undersized (<64 byte). This can happen when NT-B is unlocked and
TCP traffic is hashed to NT-B, and the minimum packet size is being violated and
dropped at HiGig link
13 BBN-23290 Title: ONT displayed on two different PONs
(2115834) Problem: One specific ONT is displayed on two different PONs due to incomplete
information being referenced in the software to identify ONT's logical address
information.
14 BBN-19669 Title: GLXF traces improvement
Problem: GLXF traces improvement for ALEXX script for NGPON2 ONT.
15 BBN-14375 Title: For 7362 OLT create RF ontcard slot fails with third party ONT.
(1883695) Problem: For 7362 OLT while creating RF ontcard slot via CLI failure message is
encountered for third party ONT
16 BBN-12564 Title: Snmpwalk on bponLanEtherPortOpstatLinkStatus returning error
(1824168) Problem: Snmpwalk on bponLanEtherPortOpstatLinkStatus return error due to issues
with the mapper.
GPON ONT
17 BBN-18077 Title: Modifying the planned-us-rate leads to issues with new XGS-ONT creation.
(2072727)
Problem: After provisioning 2 XGS-ONTs with 1G profile (CIR=EIR=AIR=1G,
DT=1), the avail-us-bw is changed to 4942974, subsequently XGS-ONT is planned
which results in the following error message on the CLI "Error : GPON MGT error 340
: No enough bandwidth for this configuration"
H248
18 BBN-23891 Title: No dial tone due to high temperature ports
(1348937) Problem: Issue observed on NPOT-B with port reporting high temperature alarm
frequently, which will impact the NPOT-B performance causing no dial tone problem
for other ports.
L2 Forwarding
19 BBN-25274 Title: IPv6 Forwarding issue
Problem: Dhcpv6 sessions not getting established and unable to debug as continuous
error records are flowing in the LT
20 BBN-12583 Title: No traffic through FELT-B uplink
Problem: During migration, NNI mode configuration for upstream-facing FELT not
properly configured in NT switching matrix. As a consequence no traffic through the
whole system
21 BBN-14373 Title: The PPP cross-connect client-port statistics do NOT work as expected.
(1981119) Problem: After the system reboot, the PPP cross-connect client-port statistics do not
work as expected.
22 BBN-18303 Title: LAG-64 MANAGEMENT PROBLEM
(2077864) Problem: When both lag interfaces are down at the same time. Standby port is restored
and LAG switchover to make port active will not occur.
When an active port is restored, the switchover will occur. Failure scenario will recover
when the second interface is restored or “sub-group-force” command is initiated on the
standby port.
23 BBN-14552 Title: LLDP system description wrong
(1911032) Problem: The LLDP system description is being changed whenever the system id is
changed.
Migration
24 BBN-16711 Title: Title: Migration does not maintain QoS session profile configuration
(2060545) Problem: After migration when ONTs reboot, the ONTs bridge port session profile no
18/72 Edition 01 – RL 30-Sept-2021
longer references rem-up/down policies
Workaround: Once the session profiles are re-configured to have the proper rem-
up/down policies, IPDR records resume from the ONTs.
25 BBN-12710 Title: System reboots when show transaction set-log-table is executed
Problem: After migration, In some rare scenarios stale entries that have corrupted or
uninitialized values seem to persist in transaction table. In such case, if show transaction
set-log-table is executed CLI task experiences unexpected exception due to the invalid
OID lengths that are present in the table.
MPLS
26 BBN-12665 Title: Alarm LDPSESSIONDOWN not cleared after LDP peer config removal
(1875069) Problem: LDPSESSIONDOWN alarm is not cleared when LDP peer configuration is
removed
Multicast
27 BBN-12635 Title: Configure multicast channel ranges with overlapped multicast MACs, one
(1932345) range would be lost after LT reset.
Problem: Configure multicast channel ranges with conflicting multicast MACs is not
allowed on ISAM. MAC overlap check is not working as expected on both NT and LT,
It is possible to configure ranges with overlapped MACs, however, some multicast
functions will not work.
NT
28 BBN-21670 Title: TX Optical value is not correctly reported in the XFP port on NT I/O (NO-
(2104211) Power) but RX value is correctly reported
Problem: For XFP module 10G : 3FE-50712-BB 1310nm (10km) and 3FE-50712-CB
1550nm (40km), on the XFP port on NT I/O the optical value TX is not correctly
reported (NO-Power) but the xfp is transmitting and RX value is correctly reported.
OAM
29 BBN-12765 Title: BFMU file uploads can cause NT restart
(1807764) Problem: BFMU file uploads, using sftp functionality of the NT, can induce a race
condition, that will end up in a NT board reset.
30 BBN-12595 Title: Multiple 7362 ISAM SF are Stuck with PSU-CRIT alarm TRD=05/08/2021
(908338)
Problem: Multiple 7362 ISAM SF are Stuck with PSU-CRIT alarm TRD=05/08/2021.
Unknown reason casing OV (over-voltage) alarm
31 BBN-12568 Title: OID 1.3.6.1.4.1.637.61.1.35.11.22.1.3 times out issue
(1753483) Problem: When trying to find a service index the system has to go through various
elements of an array. When there are many ont's, there are many elements in the above
array. So it will take a long time to find a service index. This may lead to a timeout
issue.
32 BBN-19987 Title: The current bandwidth in the output of the command 'show interface port x-
(2092163) pon detail' for FGUT-A/FWLT-C is not correct.
Problem: The current bandwidth in the output of the command 'show interface port x-
pon detail' for FGUT-A/FWLT-C is not correct. This issue was caused due to an
internal requirement change.
QoS
33 BBN-12720 Title: DS UNI weights accuracy decreases as weight values increase on FWLT-C
(1672312)
Problem: With smaller values of UNI weights, traffic is accurate. However for larger
values of UNI weights the accuracy is decreasing
34 BBN-12722 Title: Inaccurate weights applied on downstream QoS
Edition 01 - RL 30-Sept-2021 19/72
(1674470) Problem: When same user uses multiple queues, and both queues have different
weights and same priority. In particular in the extremes e.g. weight 1 versus weight 99,
there can be a 20% deviation
35 BBN-12668 Title: Possible QoS unaware drop when congested in downstream
(1922912) Problem: When using multiple queues in the downstream traffic manager with
overload/congestion, it is possible to use all available addresses/pointers in the external
LPDDR memory. A protection is in place to drop packets QoS aware when nearing this
filling level, to avoid QoS unaware drop when completely filled. The threshold for this
was configured the same for all boards, even though some boards have less memory
capacity. For these boards, QoS unaware drop was possible. Affected boards: FGLT-D,
FGLT-E, LGLT-D, LGLT-E
36 BBN-12728 Title: Subflow policing could fail on Quillion-based boards in upstream and
(1919458) downstream direction.
Problem: Subflow policing was failing when next policies (lower precedence/priority)
with no policer action are present.
37 BBN-16524 Title: Downstream VoIP frames (pbit5) drop in 128 ONU test when ds-dedicated-
q=enable
Problem: When 128 ONUs are configured in a PON port on FGLT-D and a high traffic
load is applied, VOIP frames drop at a high rate of (>20%) continuously. The issue was
observed after ensuring that all traffic goes through the VoIP special queue with
sufficiently large frames at a high rate.
Security
38 BBN-18616 Title: RADIUS authentication for SSH using a PIN is not working.
(1782115) Problem: When logging in for the first time using RADIUS authentication via SSH, the
MSAN replies to the first query with the one-time password from the token which is not
handled causing an authentication failure.
39 BBN-12714 Title: Changing SuperUserAuth causes illegal value 0 at the first NT startup after
(653827) OSW switch on redundant NT
Problem: After OSW switchover on NT Redundant setup, changing SuperUserAuth
causes illegal value 0 at the first NT startup.
SIP
40 BBN-23892 Title: No calls could be made although subscribers registered were active
(683234) Problem: On 7302 ISAM with NANT-D & NPOT-B card, no calls could be made
although subscribers were registered and active on the system due to memory leak
problem.
41 BBN-23893 Title: No calls could be made on random NPOT-B boards
(1225365) Problem: Due to memory leak for a specific CW (call waiting) and CH (Call Hold)
scenario, no calls could be made anymore after memory exhausted.
42 BBN-23887 Title: DTMF RTP EVENTs not played if payload type 120 used
(678350) Problem: DTMF events received as pure RFC2833 RTPEVENT are not played to the
phone when payload type 120 is being used.
43 BBN-23884 Title: NPOT-B resets with unknown reset reason
(1-7937126) Problem: NPOT-B board resets in a specific SIP scenario when making an outgoing
call, in which 6 dialogs received.
44 BBN-23883 Title: No UA-profile Re-Subscribe is sent when NOTIFY has encrypted Contact
(1-7974687) header
20/72 Edition 01 – RL 30-Sept-2021
Problem: Issue observed in an exceptional scenario with a SIP server that uses an
encrypted CONTACT header including proprietary parameters which are change in
each SIP server response, and where already a first NOTIFY is being received from the
SIP server prior to receiving the SIP 202 response on the Re-Subscribe.
45 BBN-23890 Title: NT trace debug error records flooding during daily inventory collection
(1374112) Problem: For SIP DHCP mode, trace debug error records are flooding on NT board
during daily inventory collection.
46 BBN-17978 Title: No line reversal when line-reversal configured
Problem: When linesig-remanswer configured as line-reversal, after call setup, no line
reversal sent out from caller.
VoiceServices
47 BBN-16593 Title: Voice subscribers down with physical failure. NPOT-C board is up
(2058600) Problem: VCP chipset problem. SW workaround to re-initialize VCP did not work as
expected
2.5 R6.5.01 Corrections/Improvements

GPON OLT
1 ALU02732492 Title: ONT inactive after cage mode downgrade from MPM to GPON with GPON
optics
Problem: When cage mode downgrade is done from an SFP mismatch condition, more
specific MPM cage mode with GPON optic, GPON ONT remains inactive after
configuration. Only in case PON is put admin up before configuration of ONT's.
2 ALU02742917 Title: FGLT-B reset caused by the TM crash event CorrECCErr

(1391674) Problem: FGLT-B board reset caused by LT's Traffic Manager crash event
CorrECCErr. When the auto-reset function is disabled and if the CorrECCErr event is
reported, the TM does not crash. In the normal mode of operation, LT should not auto-
reset if CorrECCErr error event is detected.
3 ALU02736910 Title: OMCI errors in TL1 HGUTR069 PPPoE parameters when they arent
(1017098, applied correctly
1351339, Problem: ONT keeps the default password of the preconfig file even it receives the
1387862, correct password from the TL1 and sends the default password to the BRAS
1774077,
1814357,
1840974)
4 ALU02737933 Title: FGLT-D - BER errors when disconnecting ONTs
(886458) Problem: Under certain conditions, disconnecting ONTs can cause BER traffic loss on
other ONTs of that same PON. This only occurs in GPON-mode with FEC enabled.
5 ALU02738340 Title: FGLT-D - Startup and Link Issues

Problem: Link issues can surface as boards not coming up, boards not coming up in
certain slots (especially slots 1 and 2), or boards coming up with half link capacity (10G
iso 20G)
6 ALU02741581 Title: FWLT-C - With VMAC enabled, max-unicast-mac is only half of what is
configured
Problem: Only half of VMAC are learned and only traffic of those half is forwarded.
The rest is dropped.
Edition 01 - RL 30-Sept-2021 21/72
7 ALU02744511 Title: Multicast forwarding in stacked CC broken for HC-UNI ports
(1775774) Problem: Multicast forwarding in stacked CC configuration is not working for HC-
UNI mode. In normal UNI mode, the mulitcast forwarding was still working.
8 ALU02751846 Title: Mailbox issue between LT and GLOB
(1755820) Problem: When the mailbox restarts, it should not read the msg in the pool.
9 ALU02732018 Title: OLT CLI and SNMP slow after using remote-debug
(1221109) Problem: OMCI consumed too much CPU thus load control took effect and PONA
could not get scheduled in time. Likely system ran into a corner case
10 ALU02737526 Title: Speed display issue for FWLT-C
(870974) Problem: After waking up the FWLT-C from a power down mode, CLI reports 10G
operational speed for LT.
11 ALU02737927 Title: Some ONTs in invalid/inactive state after shut/noshut PON
(1-8042984) Problem: When toggling the PON administrative state down and up a couple of times,
some ONTs on the PON get stuck in Invalid state.
12 ALU02737963 Title: All PONs of a FGLT-B card went out of order
(1-7427531) Problem: FGLT-B reset due to missing board parameter
13 ALU02738455 Title: ISAM FX: SNMPwalk with incorrect ifindex led to NT SWWD reset
(1692362) Problem: ISAM FX: SNMPwalk with incorrect ifindex led to NT SWWD reset.
Ideally, the NT should not reset even if wrong snmp message received.
14 ALU02738519 Title: NGFC-F card displays status "unknown" in CLI
(1019039) Problem: The NGFC-F card of 7360 ISAM FX displays status "unknown" in CLI and
no "unknown-error" alarm is triggered. Instead for ACU group, if it is planned and the
actual type is unknown, then a board mismatch alarm will be triggered.
15 ALU02738632 Title: 7362 ISAM DF management traffic corrupted for specific destination MAC
(1669934) addresses
Problem: IP TCP SYN packet/frames replies from OLT are corrupted. It is not possible
to use SSH or any TCP connection to OLT mgnt IP
16 ALU02739595 Title: System should not read the smas file in case it is a POWERON reset
(1390777) Problem: System should not read the smas file in case it is a POWERON reset. Instead,
system should go to hang mode, then the HW issue will be exposed immediately, then
customer could take action to replace the HW.
17 ALU02739864 Title: All GPON ONTs under same PON of FWLT-P have equal olt-rx-sig-level
(884609)
Problem: All GPON ONTs under same PON of FWLT-P have equal olt-rx-sig-level,
XGS ONTs are ok.
18 ALU02740163 Title: PBMT rollback timeout when NE reset before rollback using snmpv3
(1642895) Problem: PBMT rollback timeout after activate NE with old release when using
snmpv3 and there is NE reset before rollback.
19 ALU02740172 Title: 7360 ISAM FX third party ONU LOID web registration failed initially when
(1692186) connected to OLT
Problem: If planned-us-rate configuration of ONT is set to auto-match, when opening
the ONU's registration web page and enter the LOID and about 1-2min later, the web
displayed registration fails for third party ONUs. After a while the ONU registration
with the OLT is successful.
20 ALU02740234 Title: Downstream MPLS forwarding (Network to User) will not work in FANT-H
(652756) with S+C Cross-Connect VLAN
Problem: MPLS traffic on a PW with only c-tag in the payload is not treated as
untagged when PW is configured in ETHER VC-type. As a result of this, the customer
VLAN is not retained while forwarding towards user SAP.
21 ALU02740559 Title: ONT last tate change date is not Updated
22/72 Edition 01 – RL 30-Sept-2021
(1734668) Problem: The ONT last change date is not updated in 7362 ISAM DF.
22 ALU02740846 Title: GLOB cannot auto recover after 25 reset
(841597) Problem: GLOB will not recover automatically after more than 25 GLOB reset on a LT
as message buffer has been exhausted on OBC side.
23 ALU02740947 Title: SNMPwalk on iphost name for the ONTs results in a timeout
(1674905) Problem: For large system with high number of ONTs connected to a PON, an index
value determination is happening that can take a long time resulting in timeout.
24 ALU02741367 Title: FWLT-C - Queue weights inaccurate

(1642444) Problem: When the shaper is set close to the PON limit (e.g. a shaper which allows 1G
is too much for GPON), conversion of SW weights to HW weights is not accurate
(rounding may cause a deviation)
25 ALU02745104 Title: FWLT-C / FGLT-D - Stability improvements
(1755774) Problem: Unexpected occasional LT hot resets were observed in rare cases.
26 ALU02746282 Title: Fake external alarm after upgrade
(1812747) Problem: Fake external alarm appears after upgrade
27 ALU02746477 Title: ONT LOS not reported when fiber disconnected
(1782170, Problem: When there are multiple ONTs on a PON port and if fiber is removed from a
1799674) single ONT then the ONT is reported inactive but LOS alarm is not reported in OLT for
that ONT.
28 ALU02747404 Title: RIP check fail causing DOA
(1390777) Problem: RIP data with some probability of returning fail
29 ALU02747774 Title: FANT-G Poweron Error after SWO
(1692997) Problem: The task SFP exited when it was traced by the app callstack_svr. But the
callstack_svr didn't reclaim the tracee's task_struct in such a critical case.
30 ALU02748782 Title: ONT cannot be ranged to OLT and results in a PONLOS alarm
(1299311) Problem: ONT connected to FGLT-B cannot be ranged resulting in a PONLOS alarm,
issue seen only on one PON
31 ALU02748785 Title: OMCI & ONT provisioning fail alarms seen on all ONTs of a LT
(1669906) Problem: Enabling AES in ONT interface results in OMCICOM alarm whereas
disabling AES clears the alarm on a single pon
32 ALU02748786 Title: OMCI messages are dropped in FPGA in upstream due to MIC error on a
(1222920) PON
Problem: OMCICOMM and CFG alarm observed on a specific PON on a LT and these
alarm are generated due to MIC error
33 ALU02753128 Title: Downstream VoIP frames (pbit5) drop seen during 128 ONU test
(1922912) Problem: When 128 ONUs are configured in a PON port on FGLT-D and high traffic
load is applied, VOIP frames drops in high rate (>20%) continuously.
34 ALU02753350 Title: FGLT-D subflow policing fails when other QOS policies are present
(1918349) Problem: Combining the 2 policies, the one with the policer attached is misbehaving
35 ALU02741034 Title: Incorrect CDE feature pre-R35PPPQoSHandling bitmap position

(1746469) Problem: The pre-R35PPPQoSHandling CDE feature bitmap position wrongly
changed from 17 to 18.
36 ALU02743010 Title: FWLT-C - XPON: untilization with FEC enabled under-estimated
(1738758) Problem: The downstream utilization as well as peak-utilization counters return values
< 90% when the PON is fully loaded (load close to theoretical maximum, FEC enabled
in both directions as per xgs-pon standards)
37 ALU02744976 Title: QoS Profile Configuration Errors on FWLT-C with VLAN MGT error 441
(1797882)
Edition 01 - RL 30-Sept-2021 23/72
Problem: FWLT-C min EBS is 1024 not 64, need new CLI promot to hint.
38 ALU02746093 Title: Ds-schedule-tag (x-pon parameter) can not be modified if there is gpon vlan
(1816997) port existed
Problem: HKBN reported a fwlt-c issue when migrate from gpon to xgs pon. Customer
plan to install MPM SFP and install xgs ont, and need to change x-pon parameter ds-
schedule-tag from default value egressoutertag to svlantag for particular deplolyment
(align with gpon deployment). Then error is seen, system refuse the modification.
39 ALU02746952 Title: AGC mode display issue on NGLT-C card

(891328) Problem: OLT sends the correct AGC mode to ONU but display in OLT is incorrect
40 ALU02750925 Title: Display error for show-power-mode in CLI for 7362 ISAM DF-8G
(1698142) Problem: From HW view, DF-8G supports power-mode of ac and dc, which will be
displayed as "ac" and "dc-loc" in CLI command "show equipment power-oper-mode" in
CLI. But SW didn't implement this feature until this FR.
GPON ONT
41 ALU02737319 Title: ONT goes operationally down when enabling PM collection
Problem: ONT goes operationally down when enabling PM collection for CPU or
memory utilization, or when configuring a threshold crossing alarm for l2uni ont
dropped-frames up/down. The ONT comes back operationally up after a while. The
issue is seen with XS-020X-A type ONTs and is related to the ONT version: older
versions do not support such configuration.
42 ALU02744945 Title: FWLT-C/FGLT-D - Wrong OLT-ONT distance reporting for Freescale
(1738635) ONT
Problem: Freescale ONT's on a near 0 loop are reported on a distance of 0.1 or 0.2 km
(OK) when using diff reach of 20 km. However when switching to diff-reach 34 km
they are reported on a distance of over 8 km.
43 ALU02750108 Title: OMCI messages are dropped on ONT due to CRC error in downstream
(1690937,
1837511) Problem: OMCI messages are dropped on ONT due to CRC check, after disable the
CRC check on ONT, OMCICOM alarm was not visible.
L2 Forwarding
44 ALU02748692 Title: FWLT-C - VLAN Counters don' t work when PPP CC is configured
(1220739) Problem: DS forward/discard bytes not reported in VLAN counters
Migration
45 ALU02745100 Title: 7360 ISAM FX Migration - Isolation and HOT reset after 1 hour - Manual
(1228566) intervention required for 802.1X authentication
Problem: When migrating OLT with more than 3500 subscribers, only 1000 ports got
802.1X authenticated after 1 hour, and then OLT got isolated. During this period,
802.1X CLI command might cause a NT reset due to no response from AAA task.
46 ALU02749439 Title: Some 3rd party ONT does not complete DHCP cycle
(1643645) Problem: After migation to R6.2.04d, some 3rd party ONT's were out of service
because these ONT's did not complete the DHCP cycle
OAM
47 ALU02748266 Title: Snmpwalk on bponLanEtherPortOpstatLinkStatus returns an error
(1824168) Problem: Snmpwalk on single ONT returns an error whereas snmpwalk for all ONTs
returns correct result
QoS
48 ALU02737377 Title: DS UNI weights accuracy decreases as weight values increase on FWLT-C
(1642242)
24/72 Edition 01 – RL 30-Sept-2021
Problem: With smaller values of UNI weights, traffic is accurate. However for larger
values of UNI weights the accuracy is decreasing
49 ALU02748555 Title: FWLT-C / FGLT-D - ONT weights derived from UNI weights are capped at
(1737753) 127
Problem: If no scheduler-node on the ONT, the sum of the weights of the UNIs of the
ONT is taken, but when this sum exceeds the valid range of weights the weights are
capped at 127. This could lead to wrong ONT weights.
Redundancy
50 ALU02739444 Title: Cold reset ISAM and then manual SWO results in different ONU alarms
(GPON)
Problem: Cold reset and then Manual SWO, ONT alarms are observed on GPON
interface
51 ALU02736857 Title: Unexpected protection group state observed after DB restore
Problem: We can see the swo-reason for a specific protection group is board-failure.
This is not expected. It should be "no-switch-over". And the status of another protection
group is also not correct. It should be "act-up inact-up".
Synchronisation
52 ALU02735753 Title: FANT-F AE and FELT-B AB got a sine wave with paragon without external
reference
Problem: With FANT-F AE and FELT-B end to end test, using a paragon-x with
external reference, the output of FELT-B and 1pps shows like a sine wave
2.6 R6.5 Corrections/Improvements

Equipment
1 ALU02725867 Title: RX power level of SFP+ optics are not displayed on the STBY FANT-F card
(666482)
Problem: SFP+ optics are not showing RX power level on the Hot STBY FANT-F card
(alarm reported rx-power-tca : low-alarm-th) but is correct on the FANT-F that provide
service
2 ALU02733477 Title: ANSI 7360 ISAM FX-8 shelf: LED control for BAT-A and BAT-B is
(1017789) swapped
Problem: When DC Power from the BAT-A position is removed, the LED on the front
panel for BAT-A remains green while the LED for BAT-B goes dark. The alarm is
reported correctly in the CLI. Although the software has been corrected however in the
Unit Data Sheet, the figure of NGFC-H, BAT-A and BAT-B are swapped. The correct
position should be: Position 2 is BAT-A, Position 3 is BAT-B.
GPON OLT
3 ALU02726004 Title: NELT-B ingress qos profile not taken into account with PPP CC
(1-7979563) Problem: When VLAN is attached to PPP CC and ingress qos profile pbit 0/1 traffic is
mapped to NELT-B Q4, pbit 1 traffic over PPP session wrongly goes to Q1. No such
issue when VLAN is directly attached to bridge port.
4 ALU02728020 Title: After swapping FGLT-B with FWLT-C, it might be impossible to set up PPP
(682104) sessions
Problem: When the issue is present a continuous flow of PPP CC related error record
are noticed on the LT. After a (warm) reset of the LT, the issue seems to get resolved
and no error records are observed anymore.
Edition 01 - RL 30-Sept-2021 25/72
5 ALU02731518 Title: PPP session issue on FWLT-C
(919732) Problem: After some time that FGLT-B boards are replaced with FWLT-C, users are
not able to setup the PPP sessions anymore.
6 ALU02736985 Title: FGLT-D - BER errors when disconnecting ONTs
(886458) Problem: Under certain conditions, disconnecting ONTs can cause BER traffic loss on
other ONTs of that same PON. This only occurs in GPON-mode with FEC enabled.
7 ALU02738339 Title: FGLT-D - Startup and Link Issues

Problem: Link issues can surface as boards not coming up, boards not coming up in
certain slots (especially slots 1 and 2), or boards coming up with half link capacity (10G
iso 20G)
8 ALU02718763 Title: Alarm time stamp issues
(510184) Problem: When there is a system time change, the alarm module will receive a callback
and based on current time will adjust timestamps in alarm tables. However, sometimes
the callbacks are received with some delay, as a result, the alarm timestamps are
wrongly adjusted. Software change was implemented to send the current time with a
time diff from the internal module while calling the alarm callback.
9 ALU02719790 Title: Network port on the standby NT fails to come up

(1-8029558) Problem: Under some corner conditions, the network port on the standby NT, i.e. nt-
b:xfp:1, failed to come up
10 ALU02721971 Title: Copying coredump file (180k) from FWLT-C to NT (FANT-G) results in NT
(650056) or LT reset
Problem: Copying coredump file (180k) from FWLT-C to NT (FANT-G) results in NT
or LT reset. The same tests under FGLT-B are ok, no NT or LT reset happened.
11 ALU02723253 Title: ISAM wrongly reboots while using TL1

(663965) Problem: In rare cases, under load condition, the System will reboot while executing
TL1 commands due to the scheduler unable to service the responder task when the timer
has sent a message for processing.
12 ALU02723526 Title: Wrong syntax for NEWONT TL1 message
(1-8024609) Problem: The NEWONT TL1 message doesn't have the same syntax as the other
alarms; it requires one additional coma behind the ':'.
13 ALU02724709 Title: High risk of power failure due to frequent power on/off
(387976) Problem: High risk of power failure on FANT-G/DF-16GW due to frequent power
on/off because unnecessary ROM updates.
14 ALU02724843 Title: High usage of memory on two nodes
(1-8014738) Problem: Customer has two nodes with NANT-A having high memory usage. Values
are always constant and they are 85 and 89 percentage.
15 ALU02725816 Title: Signal degrade Alarm is observed after ONT reset of the Huawei SFP ONT
(590793) on the FWLT-C
Problem: Signal degrade Alarm is observed after reset of the Huawei SFP ONT
connected to the FWLT-C. GPON frame length was adjusted from 19424 to 19370 to
cope with Huawei SFP ONT.
16 ALU02725871 Title: FWLT-C - vmac not correct after cage mode transition
(1-8035879) Problem: Incorrect VMAC generated by the FWLT-C board after changing the cage
mode
17 ALU02726157 Title: FGLT-D not booting after full NE power cycle
(680910) Problem: Depending on the number of SFPs deployed, FGLT-D may not come into
service after NE powercycle (showing as empty in CLI).
26/72 Edition 01 – RL 30-Sept-2021
18 ALU02726685 Title: Internal error seen during the new ONT provisioning if parameter
(754601) "planned-us-rate" is not set. NT trace prints ERR log
'SnmpConfigValue::getValue before specified!!!!'
Problem: The issue arises when creating an ONT using anything other than CLI or
TL1. And creating ONT without setting planned-us-rate. In this case, the value of the
ONT's planned-us-rate is the initial value, and an error prompt appears when used.
19 ALU02727329 Title: Abnormal Tx power observed on NT board uplink port after

(1-8037481) "LINKDOWN" alarm on OEM XFPs
Problem: TXPWLO/TXBIASCURLO/RXPWLO alarm continuously fluctuated on the
NT board's uplink port after LINKDOWN alarm.
20 ALU02729481 Title: Stacked vlan tag - pbit problem
(1-8035874) Problem: Stacked vlan tag pbits in inner vlan tag overwitten
21 ALU02730606 Title: Policer not taking effect when applied to PPP CC client-port fro FWLT-C
(909770)
Problem: Upstream policer on the PPP CC client-port to police the HSI US traffic does
not work properly for FWLT-C card.
22 ALU02730823 Title: SNTP is not syncing to the high priority server after applying IP filter on
(1098943) lower priority server
Problem: Configure two SNTP servers with priority 1 and 2. 1 being higher is
preferred choice. Apply filters such that, first the server with priority 2 is blocked, then
1 and then block both 1 and 2. Now apply filter for priority 2 server. SNTP stops
syncing to the higher priority server.
23 ALU02730960 Title: NELT-B poweron reset
(667554/ Problem: In rare case, NELT-B in slot 2 will have poweron reset when MSTP is
1219826) enabled on Port 25.
24 ALU02731215 Title: Static MAC configuration causes the traffic to be dropped
(1038136) Problem: Static MAC configuration causes the traffic to be dropped. The issue is due
to the same QinQ VLAN bound to different vlan port belonging to different types of
boards.
25 ALU02731609 Title: Error records during LT boot and during PPP CC client-port config
(1217543) Problem: Many error records are seen during FWLT-C reboot. Similar error records
are also seen during normal operations, like for example when the PPP CC client-ports
are configured
26 ALU02732057 Title: XGS ONT needs long time to register to OLT
(1219262) Problem: If planned-us-rate configuration of ONT is set to auto-match, the ONT needs
a long time to register to the OLT
27 ALU02732149 Title: Possible QoS congestion issue on for 1 port of FELT-B
(667543) Problem: As a result of incorrect application of backpressure mechanism, congestion
could occur on one of the FELT-B ports.
28 ALU02732365 Title: UP-CRC-ERROR counter wrong for PON 9 to PON 16
(1022286) Problem: Troubleshooting counter UP-CRC-ERROR is calculated wrongly for PON 9
to PON 16 on FGLT-B
29 ALU02733441 Title: Downstream MPLS forwarding (Network to User) will not work in FANT-H
(652756) with S+C Cross-Connect VLAN
Problem: MPLS traffic on a PW with only c-tag in the payload is not treated as
untagged when PW is configured in ETHER VC-type. As a result of this, the customer
VLAN is not retained while forwarding towards user SAP.
30 ALU02733469 Title: NGFC-F card of ISAM FX displays the status as "unknown" on the CLI
(1019039)
Edition 01 - RL 30-Sept-2021 27/72
Problem: NGFC-F card of ISAM FX displays the status as "unknown" on the CLI.
There no "unknown-error" alarm triggered. Instead for ACU group, if it is planned and
the actual type is unknown, then a board mismatch alarm will be triggered.
31 ALU02733585 Title: ONT Inactive reported instead of PON LOS

(1-7914122) Problem: When SFP cage is empty in MPM cage operational mode, the ONT Inactive
alarm is raised for each pre-provisioned ONT instead of just one PON LOS alarm for
the GPON PON port.
32 ALU02734310 Title: GLOB cannot auto recover after 25 reset
(841597) Problem: GLOB will not recover automatically after more than 25 GLOB reset on a LT
as message buffer has been exhausted on OBC side.
33 ALU02734371 Title: FGLT-D hot resets
(1163562) Problem: Some FGLT-D board may reset under temperature conditions
34 ALU02734393 Title: Adding Alarm into alarm-list got failed
(1348756) Problem: Adding Alarm into alarm-list failed. This issue was caused due to alarm-list
previous pointer in software was pointing to NULL. Trying to dereference the previous
pointer(NULL) is causing the issue.
35 ALU02734409 Title: System (7360 ISAM FX) should not read the smas file in case it is a
(1390777) POWERON reset
Problem: The System (ISAM FX) should not read the smas file in case it is a
POWERON reset. Instead, the system should go to enter into hang mode, which will
make the HW issue evident and prompt a shelf replacement.
36 ALU02736670 Title: Erratic PONSFPMISMATCH alarms across several ports
(1221247) Problem: In some corner cases, a timing issue when reading out the SFP status can
result in an erratic PONSFPMISMATCH alarms and consequently shut-down of the
laser
37 ALU02737040 Title: VLAN Counters don't work when PPP CC is configured
(1220739) Problem: When a PPP CC client-port is configured, the vlan counters are not correctly
reported on the underlying bridge port. For upstream, forward frames/bytes and discard
frames/bytes are reported. For downstream, forward and discard frames are reported,
but forward and discard bytes will be always zero.
38 ALU02737163 Title: Diff_reach 34km not supported for FWLT-C/FGLT-D

(667545) Problem: PON setting diff_reach 34km causes BIP errors on FGLT-D and FWLT-C
with some 3rd party ONTs. Resetting the differential reach to 20KM(default) results in
no BIP errors. workaround: None
39 ALU02737238 Title: NT reset caused by BM_POOL_FillBufs error
(1411321) Problem: In rare case, NT may wrongly reboot with error info "BM_POOL_FillBufs
err=0xe005a, freeNbr=0".This is due to the improper handling of a particular error
message.
40 ALU02738204 Title: ISAM FX: snmpwalk with incorrect ifindex led to NT SWWD reset
(1692362) Problem: ISAM FX: snmpwalk with incorrect ifindex led to NT SWWD reset. Ideally,
the NT should not reset even if wrong snmp message received.
41 ALU02739862 Title: All GPON ONTs under same PON of FWLT-P have equal olt-rx-sig-level
(884609)
Problem: All GPON ONTs under same PON of FWLT-P have equal olt-rx-sig-level,
XGS ONTs are ok.
42 ALU02740162 Title: PBMT rollback timeout when using snmpv3 and there is NE reset before
(1642895) rollback
28/72 Edition 01 – RL 30-Sept-2021
Problem: PBMT rollback timeout is observed after activating NE with old release
when snmpv3 is used and there is NE reset before the rollback. Establishing a new
SNMP session during rollback restart overcomes the issue.
43 ALU02740168 Title: 7360 ISAM FX - Huawei and ZTE XGS ONU LOID web registration failed
(1692186) initially when connected to OLT
Problem: Open the ONU's registration web page and enter the LOID and about 1-2min
later, the web displayed registration fails for Huawei and ZTE ONU. After a while the
ONU registration with the OLT is successful.
44 ALU02740557 Title: ONT Last State Change Date is Not Updating
(1734668) Problem: The ONT last change date is not updated in 7362 ISAM DF.
45 ALU02728194 Title: PON QoS interface ds-schedule-tag migrated value is ctag expect
(754003) egressoutertag
Problem: During the SW migration process, all LTs are NGLT-A so QoS schedule-
mode can not be service-flat.
46 ALU02729741 Title: Mcast monitor does not work on mcast sources defined by large ranging
(892915)
Problem: The mcast monitor does not work for a mcast channel configured with a large
IP address range
47 ALU02736742 Title: IOP issue with 3rd party ONT for "Admin State" attribute within the
(670208) "Dot1ag MEP" ME support
Problem: Under some specific conditions when 3rd party ONT does not support private
ME "ONT generic V2" the admin state attribute of "dot1ag MEP" ME does not support
the "set by create" operation
48 ALU02740440 Title: LXFWD Bulk Sync Failure alarms raised unknown cause
(1-7952687) Problem: Several intermittent alarms of type LXFWD Bulk Sync Failure on LT10-
PON3 in redundant configuration.
49 ALU02741032 Title: Incorrect CDE feature pre-R35PPPQoSHandling bitmap position for
(1746469) OpenFiber
Problem: The pre-R35PPPQoSHandling CDE feature bitmap position wrongly
changed from 17 to 18.
L2 Forwarding
50 ALU02731115 Title: ARP relay issue in case of VMAC-translation
(662936) Problem: When activating secure forwarding and VMAC-translation, ARP protocol
has an endian issue
L3 Forwarding
51 ALU02737161 Title: OLTs have lost BFD session with vRR
(869381) Problem: OLTs have lost BFD session over multihop BGP session after migration.This
is observed with third party routers.
Migration
52 ALU02723112 Title: Migration to R6.2.04x fails
(1-7974956) Problem: For some specific large configurations the migration could fail due to a
dimensioning problem.
53 ALU02726021 Title: After 7360 ISAM FX upgrade, many ONTs keep on the old software
(1-8022826) Problem: After the 7360 ISAM FX upgrade, many ONT's still had old software load.
ONT in problem state will display as if its planned software is the target software but
still keep on running previous software build.
54 ALU02727654 Title: "Invalid reg_address!!!" Error On LT Board Post NE Software Migration
(1-754624) Activity
Problem: While connected to T&D interface post software migration activity
"zynq_gltd_running: invalid reg_address !!!" errors are observed on the FGLT-B LT
board via T&D interface.
Edition 01 - RL 30-Sept-2021 29/72
55 ALU02733115 Title: PPPoE authentication fails after migration due to NzOnuSN
(1219296) Problem: After migration the authentication string is not correct due to wrong string
NzonuSN (used in Radius authentication). As a consequence the service is down.
56 ALU02733554 Title: FGLT-B taking too long to become operational after migration
(754542) Problem: In a very specific and rare situation, it can take more than 1 hour before the
FGLT-B becomes operational after migration
57 ALU02737159 Title: 7360 ISAM FX - Cages are not properly created in migrated nodes
Problem: When migrating an OLT, "Cage Operational Mode" cannot be retrieved
through CLI or SNMP
58 ALU02737296 Title: 7302 ISAM FD - Cages are not properly created in migrated nodes
(1671796) Problem: When migrating an OLT, "Cage Operational Mode" cannot be retrieved
through CLI or SNMP
Multicast
59 ALU02729788 Title: 7363 ISAM MX stops sending Multicast stream to users after 2 minutes
(747656/
Problem: In ISAM running with 7363 ISAM MX during post-migration, multicast
840397/
issues can be observed in some nodes. Multicast streaming may stop after some time in
886313/ a Multicast VLAN. The issue is typically not directly seen after migration to R6201 (or
891064/ later SW stream that has the issue) but after some time. Multicast Stream will stop
892962/
sometimes in a Multicast VLAN, when during the IGMP leave report retransmission for
893009)
the last group, there is a new Join message in the same Multicast VLAN, then the issue
will occur. GMQ (General Membership Query) message will not be processed by IGMP
proxy (lift to OBC - On Board Controller) that leads to GMQ fail and end up with
stopping Multicast traffic feeding.
30/72 Edition 01 – RL 30-Sept-2021
3 Delivery Information
3.1 Delivered Software
Delivery Note = BBN-29234
Item Number Description
SWPA 3FE 78026 CAAA SWPA-ISAM R65.4.8.1
Tar file: L6GQAA65.481.tar
SWPA 3FE 25412 AAAA OFLMT (ISAM)
tar file: MLXAAA65.481.tgz
SWPA 3FE 61499 AAAA OFLMT (xVPS)
tar file: NBTTAA65.481.tgz
SWPA 3FE 28567 AAAA Push-button Migration Tool (PBMT)
Operational code: migrateIsam.3.4.42.tar.gz
DOCP 3HH 90991 CAAA DOCP- ISAM R6.5.02 CD-ROM
Customer Software Delivery Package
Note Boards with software preinstalled in EPROMs are released as

Functional PBAs (FPBA). An FPBA groups a certain HW release with
a certain software release. The FPBA is only meaningful for the non-
downloadable software. It is the operator's responsibility to download
the correct operational software version.
Note The version of the PBMT SW mentioned above, is the latest version
available at the moment of the ISAM release. However it is highly
recommended to perform the migration with the latest version of the
PBMT available. The latest version of the PBMT SW can be
downloaded from the server ‘networks.nokia.com‘.
Note FOSS (Free and Open Source SW) is part of the ISAM product. A
license note containing a list of all used FOSS and all relevant licenses
is part of the SW-package.
3.2 Delivered XDSL Proxies

Below list of XDSL proxies is part of this release:
 Broadcom 65246/65300: V19.00.41
Edition 01 - RL 30-Sept-2021 31/72
Below list of firmware (FW) is part of this release:
 Broadcom 65300: VE_11_04_32
3.3 Delivered Documentation

DOCP 3HH 15511 NAAA DOCP-7360 ISAM FX R6.5.02 CD-Package (ETSI/MII)
Customer Documentation
DOCP 3HH-91161-NAAA DOCP-7360 ISAM FX R6.5.02 CD-Package (ANSI)
DOCP 3HH 15512 NAAA DOCP-7362 ISAM SF/DF R6.5.02 CD-Package
3.3.1 Documentation Restrictions/Inconsistencies

 For the ANSI-market, intelligent fan trays (BFANs) have been documented since previous
releases in the 7360 ISAM FX ANSI documentation set, but they have not been fully
tested for horizontal mounting options.
 ANCP/L2CP is not supported anymore, and any remaining text on ANCP/L2CP
descriptions, CLI commands, TL1 commands, etc) in the customer documentation should
be considered as obsolete or mistake.
 Whereas EPON/DPoE is mentioned in the customer documentation, the support for
EPON/DPoE has been discontinued since R5.7.
32/72 Edition 01 – RL 30-Sept-2021
4 Supported Hardware
Below list gives an overview of the supported ISAM Network Termination (NT) and Line
Termination (LT) boards in the 7360 ISAM FX systems. It doesn't pretend to be an exhaustive list
of all existing HW boards (please refer to the product information manual(s) for that).
For the 7362 ISAM SF/DF systems, the supported shelf HW-items are listed at the bottom of this
list.
Note Product information manuals (and this chapter) reflect recent as well as
older hardware items that are all supported in this product release.
However, several of these hardware items are no longer offered for
sale. Please consult Nokia's contractual price list for information on
what hardware items are actually orderable.

NTs
3FE-53701-AA FANT-F AA
FX 480Gbps Network Termination (ETSI/MII)
3FE-53701-AC FANT-F AC
FX 480Gbps Network Termination with BITS & SyncE interfaces
(ETSI/MII)
3FE-53701-AD/AE FANT-F (ETSI/MII)
3FE-53701-BD FANT-F (ANSI)
3FE-71256-AA/AB FANT-G (ETSI/MII)
FX 1.2Tbps Network Termination with BITS & SyncE interfaces
3FE-71256-BA FANT-G (ANSI)
3FE-74828-AA FANT-H (ETSI/MII)
3FE-74828-BB FANT-H (ANSI)
LTs/Service boards
3FE-64279-AA NGLT-A
8 port GPON LT
3FE-67301-AA NGLT-C
8 port GPON LT
3FE-62543-AA/AB NELT-B
Ethernet LT, 36lines
3FE-69486-AA/AB FELT-B
High-speed Ethernet LT
3FE-75669-AA FELT-C
High-speed Ethernet LT
Edition 01 - RL 30-Sept-2021 33/72
3FE-66721-AB FGLT-A
16p GPON LT
3FE-68954-AB FGLT-B AB
16 p GPON LT
3FE-75833-AA FGLT-D
16 p GPON LT
3FE-76835-AA FGLT-E
32 p GPON LT
3FE-56399-AB FWLT-A
4p NG-PON2 TWDM LT
3FE-72955-AA/AB FWLT-B
8p U-NGPON LT
3FE-76571-AA FWLT-C
16p XGS/GPON/MPM LT
3FE-76986-AA FGUT-A
16p GPON LT Upgradable
3FE-68135-AA NVPS-C
Universal Voice packet server version C
3FE-65455-BA NPOT-C
48p POTS Line Board (ANSI)
3FE-65728-AA NDLS-E
48 lines VDSL2 over POTS LT with integrated splitter and SLV
(ETSI/MII)
3FE-65728-AB/BA/AC NDLS-E
48 lines VDSL2 over POTS LT with integrated splitter and SLV (ANSI)
Sealed boxes
7362 ISAM DF-16GW
3FE-45632-AA CFXR-A AA
7362 ISAM DF-16GW shelf - AC-powered with fan unit
3FE-45632-BA CFXR-A BA
7362 ISAM DF-16GW shelf - DC-powered with fan unit
3FE-45999-AA CFAN-A
7362 ISAM DF-16GW Fan Unit
7362 ISAM DF-8G
3FE-73857-AA CFXR-C AA
7362 ISAM DF-8G shelf - AC-powered
3FE-73857-BA CFXR-C BA
7362 ISAM DF-8G shelf - DC-powered
7362 ISAM SF-8GW
3FE-73517-AA/BA CFXS-C
7362 ISAM SF-8GW shelf
Wavelength Mux (WM)
3FE-71568-AA RWMS-I
WM shelf
3FE-45015-AA FWLC-A
34/72 Edition 01 – RL 30-Sept-2021
WM line card
3FE-45022-AA FWCC-A
WM Alarm/Controller board
3FE-45026-AA FWPC-A
WM Power board
Passive Wavelength Mux (PWM)
3FE-73554-AA PWMS-A
Passive WM (PWM) shelf
3FE-73553-AA/AB PWM4-A
Dual 4-channel PWM module
Edition 01 - RL 30-Sept-2021 35/72
5 Compatibility
5.1 AMS-ISAM Compatibility
ISAM R6.5.02 will be supported by 7360/7362 ISAM R6.5 v3.0 plug on AMS R9.7.08.
5.2 TL1 and CLI

All TL1 commands can be found in the R6.5.02 TL1 Command and Messages Manuals.
A dedicated document exists depending on the NT in use in the system, i.e.
 3HH 11977 BAAA TCZZA for the 7360 ISAM FX NT
All CLI Commands can be found in the ISAM R6.5.02 CLI Command Reference Guides.
A dedicated document exists depending on the NT in use in the system, i.e.
 3HH-08079-FFCA-TCZZA for the 7360 ISAM FX NT and
 3HH-13842-FFCA-TCZZA for the 7362 ISAM DF/SF.
The CLI Command Reference Guide for the FX NTs will refer you to one of the 6 IHUB
Command Guides for details on the CLI IHUB commands, i.e.
Document Number Description

1 3HH 11982 AAAA TQZZA IHUB System Basics, Management and OAM Guide
2 3HH 11983 AAAA TQZZA IHUB Interface Guide
3 3HH 11984 AAAA TQZZA IHUB QoS Guide
4 3HH 11985 AAAA TQZZA IHUB Services Guide
5 3HH 11986 AAAA TQZZA IHUB Router Configurations and Routing Protocols Guide
6 3HH 11987 AAAA TQZZA IHUB MPLS Guide
Each of these documents are part of one or more of the 7360 ISAM FX and 7362 ISAM DF/SF
R6.5.02 documentation sets.
It should be noted that a number of commands for future features are already part of the SW load
but not yet documented in the command reference guides and/or operations guides. These
commands should not be used.
5.2.1 CLI/TL1 commands & parameters phased out

For a full list of all CLI/TL1 commands and parameters that have been phased-out or are bound to
be removed in a next ISAM release, please carefully check the ISAM CLI Command Guide and
36/72 Edition 01 – RL 30-Sept-2021
ISAM TL1 Commands & Messages Manual documents. Note the CLI/TL1 commands &
parameters phase-out is additional to the feature phase-out.
Note CLI and TL1 commands are not always backwards compatible. It can
be that old commands are still accepted, but will not be executed.
Edition 01 - RL 30-Sept-2021 37/72
6 Known Restrictions
6.1 Generic Restrictions
Following security restriction applies:
 The ISAM system may have TCP/UDP ports open by default when the functionality that
used that port is not enabled. These ports will be visible in a port scan. IP Access control
lists shall be configured to limit access to such ports.
Following restrictions apply to the functionality of NELT-B in 7360 ISAM FX:

 Deployment:
 18xFE or 18xGE ports with SFP in 7302/7330/7356/7360 ISAM.
 36xFE or 36xGE ports with cSFP in 7302/7330/7360 ISAM.
 No cSFP in 7356 REM for thermal reasons: The mechanical class of the 7356 ISAM
FTTB REM is limited to class 3M3 according to ETSI standard ETS 300 019. For
further information, please contact your Nokia representative.
 See Hardware Installation Manual for more information.
 QoS:
 QoS session profile can be configured at the BP and VP Level, and not at the PPP
client port (Default priority and session QoS profile cannot be attached to PPP client
port).
 The pbit/DSCP match conditions for a policy action are compared with the received
pbit/DSCP values. On the NELT-A card, the pbit/DSCP match conditions for a
policy action are compared with the remarked pbit/DSCP values.
 DSCP to P-bit alignment table can be configured on a SAP Bridge port only (not a
SAP vlan port).
 Upstream Layer 3 filters are not supported for PPPoE packets.
 The system level and the VLAN level Pbit to TC mappings must be simultaneously
used for NELT-B UNI operations. For NELT-B HC-UNI and NNI operations, it is
only required to configure the system level Pbit to TC mappings though it might be
safer to create a VLAN level Pbit to TC mapping identical to the system level
mapping to be ready for a potential future introduction of that feature on HC-UNI
and NNI.
 On HC-UNI and NNI port types, QoS treatement is at parity with UNI with
following exceptions:
o Downstream VLAN based policing is only supported for VLAN-CC
forwarders.
o L2 / L3 filters are supported for upstream traffic only (and consequently also
policing and marking based on sub-flows).
o Weigths are internally normalized against of scale of 32 (i.e. sum of internal
weights <= 32), leading to a minimum weight granularity of 3%.
 L2 Forwarding:
 The amount of VP per BP per interface type is as follows: 8/UNI, 32/HC-UNI,
256/NNI (more details can be found in the Product Information)
38/72 Edition 01 – RL 30-Sept-2021
The HC-UNI mode only supports a subset of the UNI features as indicated in the
Product Information
 Enabling VLAN translation on more than 2K VLAN per NELT-B is subject to
licensing.
 The NNI mode is defined to support an S-ISAM (Subtended ISAM) for residential
services. As such the following subscriber management functions are expected to be
performed on the S-ISAM (see Product Information for more details):
o vMAC
o Enhanced i-bridge (DHCP snooping, ARP relay, IP anti-spoofing)
o PPPoE relay with MAC@ concentration
o PPPoE Relay
o L2 DHCP relay / Lightweight DHCPv6 relay
o IEEE802.3ah
o IEEE 802.1x
 Video:
 When using NELT-B for subtending applications, via NNI ports, one needs to take
into account that the NELT-B card supports up to 55…60 zap/second (i.e. a zap =
join + leave) depending on the NT card type and whether the scenario involves a
root (joining a multicast channel not present yet in the system or leaving the last
branch of multicast tree) or branch (adding/remove a branch of a multicast tree).
 LAG:
 All port members of a given LAG must belong to either one of the two Port Id
ranges: 1...18 or 19...36.
 Counters:
 NELT-B HC-UNI and NNI counters are subject to constraints and restrictions.
Following restrictions apply to the functionality of FANT-F in 7360 ISAM FX:

 Video:
 IGMP Resource Admission Control (or CAC) on the uplink not supported on FANT-
F
 The ISAM does not support Performance Monitoring counters for multicast traffic
on a v-VPLS service. When configuring a v-VPLS service instance and attaching
SAPs to that service, it is not possible to count the egress L2 switched or L3 routed
multicast traffic on that SAP. This is a hardware limitation. The ISAM is only able
to count egress multicast traffic on SAPs attached to a true VPLS service instance.
 In an Ethernet Ring Protection Switch (ERPS), with a Nokia 7750 SR as Ring Protection
Link (RPL) owner, the ERPS switchover time increases in function of the number of SAPs
configured on the Nokia 7750 SR.
 Y.1731:
 L2 ACL's cannot be combined with Y.1731 on same VPLS/V-VPLS service.
 When Y.1731 is enabled on LAG with ports from active & standby NT's, loss
measurement with LMM may contain inaccuracies when adding/removing standby
NT ports to LAG while measurement is in progress. The inaccuracy of packet
counters is only for duration when ports are being added or removed from LAG.
 IES and VPRN IP interface supports a maximum value of 16384 for DHCP lease-
populate. When value of dhcp lease-populate is greater than 16384, then it is required to
change to 16384 or less before migrating to release R5.3 or higher. For customers using
Edition 01 - RL 30-Sept-2021 39/72
PBMT tool this conversion will be taken care by the PBMT script. When not using PBMT
for migration, below steps should be executed:
 Execute "admin display-config" CLI command. This will provide the IP interface
related configuration.
 Find the lease-populate command under IP interface “lease-populate <value>”.
 If value is greater than 16384 then needs to be changed to 16384 or less.
 Repeat this for all IP interfaces for which lease-populate is greater than 16384.
 Do admin save.
 Following Alarm Types/Numbers are not supported with TL1: 3/31, 78/1, 84/22, 84/23,
112/2, 194/9, 194/10, 194/11.
Following restrictions apply to the functionality of FANT-F redundancy in 7360 ISAM FX:
 Forwarding:
 The following L3 forwarding functionality is not supported (and so should not be
configured) in a duplex FANT-F system:
o RIP and BFD
 Spanning Tree:
 Fully supported when the uplinks are connected to the NT I/O.
 Suffers from the following limitation when the uplinks are directly connected to the
two NTs (e.g. first uplink connected to NT-A and second uplink connected to NT-
B):
o MAC address conflicts (duplicate MAC addresses) will temporarily occur
during switchover.
Following restrictions apply to the functionality of the 7360 ISAM FX:

 The feature ISSU is supported from R5802a . Starting from R5802a, customer can do
ISSU upgrade from low SW release to high SW release.
 The ISSU feature is supported in following releases: R5.8.02x, R6.0.01, R6.0.02, R6.1,
R6.1.02k&higher, R6.2.02, R6.2.04, R6.4.
 ISSU starting from R6.2.04m or higher in R6.2.04 stream to R6.5.01 with FANT-F NT's
traffic drop may be observed during ISSU lasting few seconds.
 The ISSU feature is excluded from some releases : R6.0，R6.0.02c,R6.1.01, R6.1.02
(except for R6102k & later), R6.2.00x, R6.2.01x, R6.5. Check with support team when
this feature is required.
 Before performing software upgrade with ISSU, please make sure NT-A is active to avoid
unexpected traffice outage.
 7360 ISAM FX in some exceptional cases remains in forced switchover ring protection
state after clearing a forced switchover. When performing a forced switchover in an ERPS
ring and then clearing the forced switchover, it may happen that a 7360 ISAM FX node in
the ring will remain in Forced Switchover state. Specifically, this happens when there is a
link failure after the forced switchover was issued. In this case the ISAM will ignore R-
APS Signal Fail (SF) messages, which is correct. However, when the forced switchover is
cleared, the ISAM will also ignore R-APS No Request (NR) messages. As a result, the
ISAM will remain in Forced Switchover state. Other nodes in the ring (e.g. 7362 ISAM
DF-16GW or 7367 SX) will process the NR messages and will move to Pending state. As
a consequence, when a link failure happens after a forced switchover was issued, not all
nodes in the ring will be in the same state, and the operator will not be aware that one of
40/72 Edition 01 – RL 30-Sept-2021
the links in the ring is broken. However, there will be no loss of data traffic. To work
around the issue: the failure in the ring needs to be restored in order for all nodes to move
to Pending state, and then to Idle state.
 EPIPE is not supported on LSP protected by MPLS-FRR. Such configuration can lead to
unpredictable behavior. This restriction applies only for FANT-F
 Equipment:
 NVPS-C, NDLS-E and NPOT-C are supported with FANT-H, but these cards need
to be explicitly planned to get detected and startup.
 FWLT-C, FGUT-A and FGLT-D are ETSI/MII qualified for deployment in weather-
protected and temperature-controlled environments (i.e. Class 3.1E) as of R6.2.03,
ANSI Qualification will follow in a later release.
 In FANT-H, it is strongly recommended not to use front-panel 10/100/1000Base-T
(eth1) interface for management (or) for any other purpose. Using this interface can
result in link down failures which cannot be recovered
 Management:
 When an ISAM shelf is replaced (i.e) the cards in an existing shelf are directly
moved to the new shelf that is replacing an existing shelf, the SNMPv3 configured
user(s) are deleted silently.
This is due to changed SNMP Engine ID which is based on the ISAM MAC address.
 TL1 displays tr069 service as in service when ONT interface and VEIP is oper down
 7360 ISAM FX SDC Collection recomendation:
Do not collect more than 75k output rows from an SDC collection per OLT. The
limit is dictated by the number of Parameters in the input file, and the number of
rows in the output file, and is dependent on the scale of provisioning in the system.
In order to minimize CPU loading and prevent missing or erroneous results, it is
recommended to avoid any parameter that would require the OLT to get (via OMCI)
any “on demand” data from any ONT. At a minimum this applies to any parameter
which contains the following types of ONT data:
All RSSI Optical measurements immediately available at the ONT side
All “Call History” data associated with a POTS UNI
All interface index parameters
All Current PM parameters that contain immediate data from an ONT (including all
ONT UNIs, Services, GEM Ports)
For the above parameters it is recomended to collect the historical daily data instead.
 ONT CPU and memory utilization Threshold Crossing Alarms (TCA): the TCA are
automatically enabled once the CPU utilization monitoring / memory utilization
monitoring is enabled using the existing CLI commands. This feature is not
generally available in this release.
 LAG port removal taking long time in FANT-H compared to FANT-F/FANT-G
 In a Ethring, Outage is greater 100ms when LACP Lag shutdown that connected
between FANTH and FANTG on a
lag with two or more ports where as the expected outage is 10ms to 60ms when
compared to all FANT-G/FANT-F topology.
 When MAC movement is configured across PON ports in FWLT-C, it is recommended
that the MAC move feature is also enabled across the residential ports on the NT. This is
to avoid traffic loss at the NT during ONT/station movement across PON ports connected
to the FWLT-C with MAC movement enabled.
Edition 01 - RL 30-Sept-2021 41/72
 When using the "force-vlan-vc" option at VPLS SDP binding to enforce a service-
delimiter VLAN for tranmission via Pseudo-wire-tunnel, ensure the MPLS network
interface is a tagged interface. For un-tagged network MPLS interface, the Service-
delimiting VLAN tagging will not happen causing MPLS traffic loss at remote end
 Following restrictions apply to the Timing sync functionality:
 For xPON network, OLT with timing capable ONT works as A ‘distributed T-BC’
node that actually is 2 consecutive T-BC nodes in one system OLT+ access medium
IWF+ONT following G.8271.1.
l OLT with FANT-F/FANT-G/7362 + xPON ONT: Reaches Class A for a pair of
media convertors.
l OLT with FANT-H + xPON ONT: Reaches Class B for a pair of media convertors.
l Noise transfer and transient response (Annex B) over xPON is for further study in
the G.8273.2 standard / adaptation in xPON standard.
 For Ethernet card, OLT with FELT-B works as a single T-BC node;
o OLT with FANT-F/FANT-G + FELT-B: Exhausts 3 single T-BC’s Class A
budget.
o OLT with FANT-H + FELT-B: Reaches Class A of Single T-BC with 5%
failure rate.
o OLT with FANT-F AE (and above)/FANT-G/FANT-H + FELT-B AB: Noise
transfer exceeds mask at cut-off frequency by 1-2 ns in 10-20% probability.
o OLT with FANT-F AE (and above)/FANT-G/FANT-H + FELT-B AB:
Support transient response (Annex B) with marginal glitch and auto-recover
for G.8273 method1.
o No Noise transfer and transient response (Annex B with G.8273 method1)
supported on FANT-F AD and FELT-B AA cards.
 Due to HW limitation, there are a few of functions impact, including:
o FANT-F AD works on IEEE1588-2008 BMCA mode with Limitation on port
number comparation, against G.8275.1 Alternative BMCA.
o FANT-F AD’s announce rate is max 1 pps or less, as opposed the G.8275.1
profile defined default message rate of 8 pps.
o FANT-F AD can only receive PTP packets from remote port via non-
forwardable mode if configured as non-forwardable MAC.
o When deviation compensation per port on FELT-B VULA mode with FANT-F
AD, Phase sync will loss and resync soon.
o FANT-F has performance impact a little in case higher traffic load on the
uplink with the PTP sync source.
o FELT-B MAC address/step mode is same for all ports in one board.
 For Master clock PTP packets over 10G interfaces, ~300ns phase deviation on
FANT-F for L2 untag Multicast PTP mode has been compensated automatically
without manual operator configuration required from R5.8.01. But Any previous
manual compensation done before R5.8.01 release need be removed after migration
to R5.8.01 and later.
 Occasionally, oscillator output is abnormal on FANT-G. Once occurred, common
traffic can be recovered automatically without impact, however, timing function
would not be back to normal. The alarm report is based on alarm attribute
configuration.
42/72 Edition 01 – RL 30-Sept-2021
 FANT-F/FANT-G is service based PTP Arch, not port level. Only 1 PTP master is
visible from OLT and 1 slave port on LAG will be active to communicate with
Master when LAG. PTP protection depends on LAG.
 Since the superframe count field of the time of day information attribute in OMCI is
changed from 30 LSB to 32 LSB of the actual counter in R6.2.04. From R6.2.04 and
latter release, U-050X-A ONT has to be upgraded to HDR6204 and above together.
 LT backplane load sharing towards NT; no support for 80Gbps per LT slot (FANT-F) on
FX16, although supported on FX-4, FX-8.
 User-port level commands for PPPoE L2 Statistics do not report actual data in this release.
 For NGLT-A, packets discarded by the Traffic Manager (QOS processor) are not taken
into account for the trouble-shooting counters.
 A (GPON) Rogue ONT may not be detected when the signal level on corresponding ONT
is too low. However, in many cases a rogue ONT with such low level signals may not
cause disturbance for other ONTs on the PON.
 An unprovisioned (GPON) rogue ONT with an optical signal level lower than that of other
ONTs on the PON may result in disruption on some ONTs without being automatically
detected as rogue as the disruption level is low. Such ONTs are detected by on-demand
tests.
 NG-PON2 is an ITU-T standard (G.989) name which includes two flavors: TWDM-PON
and PtP WDM PON. The 7360 ISAM FX currently only supports the TWDM-PON flavor.
Please review all TWDM-PON plans upfront and in detail with Product Management.
 The 4*10G KR backplane links between NT and LT in the 7360 ISAM FX mean that
configurations must be done carefully to avoid Upstream and Downstream bottlenecks and
instead make maximal usage of the available back-plane link capacity. This is influenced
by the way in which the iHub (core1) in DS and the LT network processor in US spread
the traffic over the back-plane links. This applies to e.g. NGLT, FGLT and FELT cards
and to FWLT, but it will more likely be encountered as a potential issue with the FWLT.
The FWLT has fewer ONUs, carrying larger throughput traffic, which will increase the
probability of traffic passing through the same single backplane link (which would then
become a bottleneck). Contact your Nokia representative for assistance.
 SNMP set of nt:mc properties will lead to unwanted configuration. This will lead to
configuration loss in the next reboot. Ideally nt:mc port should be treated as Internal Port
and does not need any port properties. This is blocked in CLI but allowed in SNMP
 When a software activation of a new software package is started on FANT-F or FANT-G
it is advised to not to do new configuration via CLI until the activation either completed or
rolled back. The restriction does not apply to configuration done via SNMP since the
system can block those during the software activation.
 QoS:
 Remote downstream queues schedule may be invalid if remote downstream queues
in different UNIs have different scheduling modes on mutiple-slots ONU
o If remote downstream queues in UNIs have different scheduling modes, then
OLT may calculate the same Priority queue instance ID for these UNIs and the
remote downstream queues schedule may be invalid
 Workaround: Use WRR scheduling modes for remote downstream queues.
 Clock:
 On FANT-G; NT 1pps Time Error is more than 100ns in case of TC disabled on
FANT-G
 Following restriction exists on PON LOS alarm reporting on FGLT-B an other fiber LTs:
Edition 01 - RL 30-Sept-2021 43/72
 PON LED is still green after fiber is plugged out from the port under specific
scenario when three ONTs are connected under the PON port 4, and one ONT
provision online, the other two status is detected. Then power off the online ONT,
then plugout the fiber from the PON port. The PON LED still green, it should be red
 Video:
 When IGMP channel created on vlan 4096, and if ONT support attribute "Multicast
service package table" in ME "Multicast subscriber config info", OLT would not set
correct value in "Multicast service package table". It will affect the Multicast
Downstream traffic on the vlan 4096. it is recomended to avoide configuring IGMP
channel on vlan 4096 in such a scenario.
 For IGMPv3, the feature to control the load generated by the IGMP proxy itself
(generated traffic rate control) is not generally available.
 For IP ACL filter (IPv4 or IPv6 ACL) configuration, it should be ensured that the total
number of IP ACLs configured (with MAC filters included) is less than the total possible
supported system limit (i.e less than or equal to 512). Any IP ACL configured after having
already configuring supported limit (i.e 512) can cause removal of some of existing IP
ACL filter configuration in hardware on NT switchover
 For LAG configuration with ports spanning across NTs, with number of ports greater than
4, during NT switchover, the LAG recovery can take more time (but less than 1sec). For
such LAG configuration, when BFD is configured over IP interface over V-VPLS having
such LAG SAP, it is recommended to have timeout of BFD session failure [receive-
interval x multiplier] to greater than 500ms so that BFD session does not flap during NT
switchover. Avoiding BFD flaps prevents further delay in recovery at IP routing layer
during LAG recovery. Similar configuration should be made in BFD peer.
 Restriction and remarks specific to FANT-H and FWLT-B AB Variant:
 For FANT-H, FWLT-B(AA), FWLT-B(AB); DS packet loss rate is 1.24 * 10 e-10
 The FWLT-B AB variant is not generally available.
 Restrictions specific to FWLT-C, FGUT-A ,FGLT-D, FGLT-E and FELT-C versus legacy
PON LTs:
 FWLT-C and FGUT-A have the following restrictions:
o NG-PON2 (TWDM-PON) is not supported in the present release
o ISSU is not supported in the present release
o When both a single-tag S-iBridge VLAN and a dual-tag S+C-iBridge VLAN
sharing the same S-VID are configured on the FWLT-C or FGUT-A, a packet
matching that S-VID will be processed by only one of the two configured
forwarders, with the following precedency:
 first, if the S-VID and C-VID of the packet both match the configured
S+C forwarder, it will be processed within the S+C iBridge instance
only;
 second, if only the S-VID matches the configured S forwarder, it will be
processed within the S iBridge instance only.
In summary, a packet matching the S-VID will not be processed by both
forwarders. This is a different behaviour compared to legacy PON
linecards.
o CFM on backplane and vUNI (CFM on ONT UNI is supported) is not
supported in the present release
o eOTDR optics are not supported.
o TEC certification is not available at the moment
44/72 Edition 01 – RL 30-Sept-2021
o MEF certification is not available at the moment
o FWLT-C and FGUT-A packet processing is optimized to sustain wire rate for
an IMIX ethernet traffic profile. Though this has always been the requirement
for Nokia PON linecards, please note that some legacy cards could handle
higher packet rates.
o Modification of the operational-mode of individual FWLT-C/FGUT-A cages
is only allowed between following modes: “gpon”, “mpm-gpon-xgs”, “xgs”,
“twenty-five-g” and “not-set”. Only the transition from “gpon” to “mpm-gpon-
xgs” is supported without losing the configuration on top of the corresponding
interface. All other transitions require cage mode “not-set” as intermediate
step.
o When cage mode downgrade is done from an SFP mismatch condition, more
specific MPM cage mode with GPON optic, GPON ONT remains inactive
after configuration.
The workaround for failure condition, put the PON admin down, unconfigure
and reconfigure the ONTs and put the PON admin up.
o When a cage is configured as a dual-channel cage with two PON interfaces,
i.e. "mpm-gpon-xgs" or "dual-gpon" but a single-channel optical module is
inserted, the first PON interface will raise the "host-sfp-mismatch" alarm and
the second PON interface will raise the "host-sfp-not-prst" alarm.
o Automatic slot re-planning towards FWLT-C/FGUT-A is supported in the
OLT (when enabled by operator and for a limited number of scenarios, see
Detailed Level Procedures), however in the present release an SNMP trap is
missing to proactively notify the AMS (or any other SNMP client) about the
new planned slot type.
o The new 'auto-match' planned-upstream-rate on FWLT-C/FGUT-A to enable
the automatic detection of the ONT's line-rate on MPM ports cannot be used in
combination with dynamic CAC, i.e. max-ranging-onts = 0.
 FGLT-E, FWLT-C and FGUT-A have the following restrictions:
o FGLT-E,FWLT-C and FGUT-A cards can not be planned when the link-speed
is set to 10G or 25G. Reversely, the link-speed can not be re-configured to
10G or 25G when any of these boards is already planned in a slot.
 FELT-C has the following restrictions:
o FELT-C can only be planned with a link-speed set to 100G. Reversely, the
link-speed can not be re-configured to a different value than 100G when a
FELT-C is already planned in the system.
 FGLT-D has the following restrictions:
o It is not supported in ISAM FD shelves (Only supported in 7360 ISAM FX)
o When both a single-tag S-iBridge VLAN and a dual-tag S+C-iBridge VLAN
sharing the same S-VID are configured on the FGLT-D, a packet matching that
S-VID will be processed by only one of the two configured forwarders, with
the following precedency:
- first, if the S-VID and C-VID of the packet both match the configured S+C
forwarder, it will be processed within the S+C iBridge instance only;
- second, if only the S-VID matches the configured S forwarder, it will be
processed within the S iBridge instance only.
Edition 01 - RL 30-Sept-2021 45/72
In summary, a packet matching the S-VID will not be processed by both
forwarders. This is a different behaviour compared to legacy PON linecards.
o Lawful Intercept on the line card is not supported in the present release (LI on
the NT could be considered as an alternative)
o CFM on backplane and vUNI are not supported in the present release (CFM on
ONT UNI is supported)
o eOTDR optics are not supported.
o TEC certification is not available at the moment
o MEF certification is not available at the moment
o FGLT-D packet processing is optimized to sustain wire rate for an IMIX
ethernet traffic profile. Though this has always been the requirement for Nokia
PON linecards, please note that some legacy cards could handle higher packet
rates.
o In the present release, the FGLT-D is limited to 20G backplane capacity in
simplex (and 2 x 20G capacity in duplex) even when the max-lt-link-speed at
system level is configured for 40G.
o Automatic slot re-planning towards FGLT-D is supported in the OLT (when
enabled by operator and for a limited number of scenarios, see Detailed Level
Procedures), however in the present release an SNMP trap is missing to
proactively notify the AMS (or any other SNMP client) about the new planned
slot type.
Following restrictions apply to the functionality of GPON in 7360 ISAM FX and 7362 ISAM
DF/SF:
 If the Dynamic Upstream CAC functionality of the system is not enabled (which is the
case by default), the CIR+AIR upstream bandwidth is limited to a maximum of 836 Mbps
(aggregated) per GPON port.
 Virtual Noise and E-side/DPBO on VDSL2 ONT MDUs is covered in the customer
documentation, but not supported in this release.
 Sharing of a QoS BW profile is not supported at the ONT level when the ONT queues are
configured in strict priority or with a mix of strict priority and weighted fair queuing
scheduling.
 The following functionality cannot be activated at the same time: "Downstream UNI rate
shaping including multicast" and "UNI shaping based on queue parameters".
 When configuring E1 Circuit Emulation Services the Delay Tolerance value must be
carefully set; In addition, as the system default may internally be adjusted on a case by
case basis, the operator is strongly advised not to rely on this value but apply careful
network planning to determine the appropriate DT value for specific services on the PONs.
 Background Rogue ONT tests are disabled by default on the PON interfaces and need to
be turned on explicitly if the operator chooses to do so. For systems migrating to this
release from an older release where this functionality was enabled previously, the prior
setting is preserved on the PONs that already existed in the previous release. For newly
created PONs however, the default disabling will be set.
 For GPON the Rogue ONT detection and isolation feature is not generally available.
 Specific restrictions and remarks regarding Type-B protection on GPON&XGS PON
(applicable to 7360 ISAM):
 When MAC learning is enabled on the IHUB NT, the Type-B PON switchover
requires that forwarding tables are adapted on the NT switch, which takes a minimal
46/72 Edition 01 – RL 30-Sept-2021
time for each Protection Group (PG) that is being switched. Part of the downstream
traffic switchover time remains thus a linear function of the number of PGs
(typically ~20 msec per PG when measured over the OLT) affected by a single
failure event. Although the total amount of PGs that can be configured in the system
is 62, the customers should take care - for their provisioning as well as physical
wiring in the ODN - that no more than 16 simultaneous PON switchovers have to be
initiated as a result of an equipment failure (linecard) or accidental cut in the outside
plant. To guarantee a rapid re-computation of the ONUs’ respective EqD after
switchover, and thus to reduce the upstream outage, it is also recommended to limit
the number of ONUs to 64 on the GPON protected by a Type-B arrangement. These
practices will help guarantee a minimum traffic outage upon switchover, considering
the outage time requirements of the specific services that have to be protected. Note
that the actual upstream traffic loss upon switchover will also be influenced by the
buffering capacity of the protected ONTs.
 When SFP rssi-state is enabled, in very rare case, if SFP rssi is ongoing, and OLT
sends some PLOAM message to ONT exactly before SWO, ONT is in transition
period and can't reply the message to OLT, it will be deactivated and recover after
several seconds.
 Following specific provisioning actions performed by the operator on ONUs that are
connected to PON links protected in a Type-B arrangement, the OLT may need a
few seconds to synchronize the Mib Data Sync (MDS) counter of those ONUs from
the active PON port to the standby PON port. If a switchover was to happen during
that very short period of time, it could be that the ONU(s) affected by the
aforementioned action have to be automatically re-provisioned by the OLT (by
means of an OMCI MIB upload) once they have switched to their new active PON.
This unlikely event could affect the services but only briefly; traffic will restore after
a few seconds. Only the ONUs whose respective MDS counter increased (due to a
provisioning action) and is not yet synchronized since the last switchover or since
the creation of the PG, may be subject to an OLT-triggered MIB upload after
switchover. The actions that could lead to such situation are typically: creation of the
Type-B protection group (i.e. association between a primary-port and a paired-port),
followed by the creation of services or activation of PM counters on ONU(s) already
connected to the redundant PONs, or other configuration actions resulting in OMCI
provisioning messages being exchanged between the active PON and the ONU.
These symptoms won’t appear when the system is in steady-state.
 This functionality is not compatible with the feature "PPPoE relay with MAC
address concentration". Also, PM counters are not yet dynamically synchronized
between active and standby PONs in current release. The current implementation of
the Type-B protection does not provide protocol coverage for IPv6/DHCPv6,
802.1x/RADIUS for dynamic configurations, or network-side router (Layer-3)
functions.
 When LoidPre auth mode is used, rebooting all ONTs to trigger a TypeB SWO will
result in ONT inactivation.
 When TypeB protection is configured & change auth mode of some ONTs to
LoidPre, then trigger a typeB SWO, this will result in ONT inactivation.
 There's a read-only attribute NumberOfSwitchovers for each protection group. This
counter increments each time a switchover occurs within the protection group. But,
Edition 01 - RL 30-Sept-2021 47/72
the counter is reset to 0 when an NT goes through any restart different from hot
reset. This is the case in simplex as well as redundant NT configuration.
 When TypeB protection is configured on FWLT-C/FGUT-A/FGLT-D/FGLT-E, cold
resetting LT to trigger TypeB switchover will result in PON LOS.
 Use predefined script to perform multiple times of simulateous forced swithcover on
more than 10 MPM protetion groups, there's possibility of PON LOS occurrs on
individual protection group.
 When TypeB protection in configured on FWLT-C MPM mode, when there's a
protection group configured without any ONT connected on any of both PON’s, SFP
show commands might fail on other PON’s on the same board.
 Cold reset ISAM, and then do manual SWO immediately after protection-not-
available alarm clears, this may result in different ONU alarms due to system is still
finishing dynamic data synchronization.
 For a Type-B PG, the primary and paired OLT ports must belong to two different
linecards of the same board type. This is enforced to offer equipment (linecard)
protection along with feeder protection.
 In a Type-B configuration, if the OLT loses contact with the last remaining ONU on
the active PON for any reason - including as a result of an ONU power-off event - a
'PON loss of signal' may be detected by the OLT, which will trigger an automatic
PON switchover. This event has no impact on the services as no ONUs are present
on the PON anymore at that moment.
 Not all ONUs will receive dying gasp alarm if the switchover is triggered by
poweroff.
 When configuring the linecard to its maximum capacity, i.e. 8k static IP address +
16k dynamic IP addresses, the system will not synchronize correctly between the
active linecard and the paired linecard. Type-B protection will not operate correctly
in this case. To avoid this, the maximum configuration needs to be reduced to either
8k static IP addresses per linecard, 16k dynamic IP addresses per linecard or a
combination that is lower than 24k addresses per linecard.
 When creating protection group on very loaded LT board, the synchronization
between two proteted PONs will be delayed, PG not available alarm may be
temperarily reported and cleared after bulk synchronization finishes.
 Restoring database with TypeB protection configured, if there's misalignment
between two databases for TypeB protection group configuration, audit may fail and
ONTs will not be able to connect. Reset LT is needed to restore service in such case.
 Active ressources that are in use in association with facilities in a Protection Group
arrangement are still governed by the per line or per board scaling applicable to each
member (primary and paired member port).
 In case of deployments based on FGLT-A only, Type-B protection switchover may
result in a traffic interruption period of around 1 minute for a small subset of ONTs
on the PON
 If legacy XML download mechanism using SW image download channel is used on
ONT, upon TypeB SWO, new active LT board will download the XML again. There
will be “ONT SWDL In Progress” alarm reported & cleared during the process. No
service impact.
 In case of Type-B swichover triggered by LT plug out, there will be additional
outage caused by backplane link processing.
48/72 Edition 01 – RL 30-Sept-2021
 The cross shelf type-B feature is not generally available.
 In-service SW upgrade on the 7360 ISAM FX, in combination with type-B protected
lines, is not generally available.
 TC-Layer PM counters are intended to be used in pairs, with one instance at the OLT and
one instance at the ONT, in order to detect impairments of the TC layer connectivity. This
determination is made based on significant discrepancies between blocks/fragments
reported as transmitted from one end and reported as received from the other in the same
timeframe. However, OLT and ONT may report small differences between these counts
even in the absence of a noteworthy problem.
 Downstream p-bit remarking as a result of policing is not supported on NGLT-C and
FGLT-A. However, upstream remarking as a policer action is supported on all GPON line
cards.
 Queue mode can only be configured per pair of PONs on FGLT-A/NGLT-C.
 Colour aware policer counters is supported only on FELT-B and FWLT-C/FGUT-
A/FGLT-D/FGLT-E. On xPON LTs, for the same interface (vlan port), pbit traffic counter
and colour aware policer counter can not be enabled at the same time.
 Protocol tracing is not supported for downstream ARP messages.
 Protocol tracing is supported for upstream ARP messages, provided that either Secure
Forwarding or MAC address translation is enabled on that VLAN (applies to both iBridge
and VLAN cross-connect).
 DHCP protocol tracing is not supported on a cross-connect VLAN in case Secure
Forwarding is disabled on that VLAN.
 In cases where the VoIP IP-Host service is already created and the associated POTS line is
made ISNR, if the Operator deletes the related Bridgeport, ISAM proceeds to auto-
deletion of higher layer entities. As part of this, the VoIP IP-Host service is also
automatically deleted. No additional service mismatch alarm is raised.
 The following S-tunnel mode restrictions and behavior differences apply in the upstream:
 For RB S-tunnels, the ONT will add an S-VLAN tag in the upstream for all GPON
& Universal NG-PON cards and 7362 ISAM DF.
 For CC S-tunnels via NGLT-A, NGLT-C and FGLT-A cards, the LT will add an S-
VLAN tag in the upstream.
 For CC S-tunnels via FGLT-B and FWLT cards and 7362 ISAM DF, the ONT will
add an S-VLAN tag in the upstream.
 In case of several S+C iBridges sharing the same S-VLAN on same bridge port, CFM
(Ethernet OAM) can only be enabled on one of the S+C iBridges, otherwise, CFM
function will fail due to CFM MAC addresses duplicate as the FDB is shared at S-VLAN
level .
 When enabling 802.1X port-based Network Access Control, the source MAC address of
the incoming EAP packet will be learned, even when the authentication fails afterwards.
The system does not remove the learned MAC address upon authentication failure.
Following restrictions apply to the functionality of universal NG-PON in 7360 ISAM FX and
7362 ISAM DF/SF:
 Generic Functional Restrictions:
 The following (non-exhaustive) list gives an overview of features that are not yet
supported on Universal NG-PON:
o Type-B PON protection
o vMAC
Edition 01 - RL 30-Sept-2021 49/72
o Downstream remote queues
o Traffic limiting per GEM port
o Downstream dedicated VoIP queue
o Support of single-rate policer (CIR, CBS) at VLAN-port level at ONU
o ToD
o SyncE (incl. SSM)
o Embedded OTDR
 FWLT-A tests were passed with 128 physically connected ONUs on 1 Channel Pair.
Tests were also larger dimensions with a mix of configured and emulated ONUs
resulting in the following maximums for the current release:
o 432 Vlan ports per Channel Pair, or
o 1728 Vlan ports per LT, or
o 27648 Vlan ports at ISAM system level;
o with 8000 ONUs and 40000 UNIs at the system level.
 In the current release with multiple ONUs on a Channel Pair, upstream throughput
measurements may vary considerably from one snapshot to the next, depending on
how well services and OMCI traffic fit with the dynamic bandwidth assignment
possibilities. This variability is visible at all packet sizes and size mixes to some
extent, but it is particularly noticeable when more than 64 ONUs are present on the
Channel Pair where it can reach 1-2 Gbps levels.
 Restrictions and remarks specific to XGS-PON:
 XGS-PON can only be supported for 10/10 Gbps symmetrical services when XGS-
PON PR30 optics are used; XGS-PON dual-rate (mix of 10/10 Gbps capable ONUs
and 10/2.5 Gbps capable ONUs on the same OLT port via TDMA co-existence) can
be supported only when XGS-PON dual-rate OLT optics are used.
 In a dual-rate configuration, if the exact same bandwidth profile is assigned to ONUs
of a different type (i.e. XGS-PON ONU working at 10Gbps in upstream and XG-
PON1 ONU working at 2.5Gbps in upstream), it is possible that there are slight
variations between the bandwidth effectively granted by the OLT to the XGS-PON
ONU(s) and to the XG-PON1 ONU(s). This will only happen when the XGS-PON
Channel Pair is not congested, and for specific combinations of bandwidth profile
parameters. This will be corrected in a next release.
 In a dual-rate configuration, the semantics of the “ont-polling-period” parameter
changes because the OLT will alternate the ranging windows for 10/10 Gbps capable
ONUs & 10/2.5 Gbps capable ONUs, at the configured period. E.g. if the
provisioned period is 10s, the 10/10 Gbps capable ONUs be able to range every 20s;
same for the 10/2.5 Gbps capable ONUs respectively, but shifted with 10s.
 While this is still configurable by the operator in the system, it is recommended that
the downstream FEC is always enabled on XGS-PON (as per G.9807.1).
 In order for the Dynamic Bandwith Allocation to be performed in an optimal
manner, in cases where provisioned Delay Tolerance level could not be met due to
the provisioned Bandwidth for the service, this latter is automatically adjusted up in
a way to give precedence to the latency requirement of that service. Retrived
provisioning data in such cases represents the adjusted values.
 In a 10/10 Gbps symmetrical only configuration, there is no consistency check
between the ONU’s planned upstream rate and the channel speed of the ONU’s
preferred Channel Pair. In this case it is recommended to always keep the ONU’s
50/72 Edition 01 – RL 30-Sept-2021
planned upstream rate on the default value, so that the ONU will be provisioned
using the Channel Pair’s nominal speed.
 Bulk reading of RSSI values for multiple ONT's may result in incoherent results.
Workaround is to individually read RSSI for every ONT, with some time in between
 Support for a MoCA interface on the FWLT-B and FWLT-C is not generally
available.
 Loop detection and alarm function for XGS-PON is not generally available.
Following restrictions apply to the 25G PON functionality in 7360 ISAM FX:
 Generic remarks
 To enable 25G PON, the system requires FANT-H and the 100Gbps backplane link
speed.
 25G PON is a capability that is available on the even cages of the FWLT-C and
FGUT-A cards, but which is restricted by default. To configure 25G PON on any
capable port on one of these linecards, the system requires a free board-level 25G
PON enablement license (3EC17929WM). That license must be preliminarily
assigned through AMS.
 Though the system is designed for a large logical ONU split ratio (typically ≥1:32
for the targeted use cases), in the present release the end-to-end system validation
was focused on two ONUs per OLT port (1:2). The scale will gradually increase
with the next OLT SW releases.
 Restrictions associated to the ONU
 The Nokia 25G PON optics are designed for an N1 ODN class (i.e. min loss 14dB,
max loss 29dB) following the 25GS-PON MSAv2 specification. However, in
combination with the first generation of 25G PON ONU (Y-010Y-B), the effective
maximum ODN loss budget will be limited to 27dB. This 2dB penalty will be lifted
upon availability of the second generation of 25G PON ONUs.
 Restrictions associated to the optics
 The current 25G PON solution is asymmetric, meaning the downstream linerate is
25Gbps but the upstream linerate is still 10Gbps. While the Ethernet L2 throughput
achievable in the downstream direction is ~20Gbps, the Ethernet L2 throughput in
the upstream direction will be similar to what is achievable with XGS-PON.
 The RSSI of the first generation asymmetric 25G PON OLT optics (3FE-48259-AA)
may report inaccurate information once the received power signal approaches -
20dBm. This is a design constraint of that specific optics that has no impact on the
receiver's performance itself. It will be lifted on the second generation of 25G PON
OLT optics.
 The first generation asymmetric 25G PON OLT optics (3FE-48259-AA) is not GR-
468 certified. This certification will be obtained for the second generation.
Following restrictions apply to the functionality of universal NG-PON in 7360 ISAM FX:
 In GPON management model operation mode of XGS-PON, a board plug-out / plug-in
action would result in LT rebooting twice.
 Restrictions and remarks specific to TWDM-PON:
 In current release, the TWDM-PON Wavelength Mobility features are supported in a
single-chassis context (i.e. Channel Pairs of the same Channel Group cannot be
spread across different OLTs).
Edition 01 - RL 30-Sept-2021 51/72
When an alternative-preferred channel-pair or a protection channel-pair is configured
on a TWDM-PON ONU, the bandwidth-profile configuration of that ONU shall not
be modified on-the-fly, at the risk of inaccuracies in the QoS CAC calculations. If
the TWDM-PON ONU has only a preferred channel-pair configured, changing the
bandwidth-profile configuration on-the-fly is perfectly allowed. Note that this
restriction is only applicable to TWDM-PON, not to XGS-PON nor GPON.
 When an NG-PON2 ONU connected to FWLT-B is ranged on its preferred channel-
pair but is configured with a second channel-pair (i.e. an alternative preferred
channel-pair or a protecting channel-pair), it can in exceptional cases occur that the
state of that second channel-pair remains reported 'not ready' for that particular ONU
after ISAM reboot. If this happens, please reboot this ONU via the ISAM
management interface (admin equipment ont interface <ont-aid> reboot-with-active-
image).
 In case of ONU connected to 3 channel pairs of which two are connected to the same
FWLT-B, when doing manual ONT switchovers between pref-channel-pair and alt-
pref-channel-pair/prot-channel-pair, it can happen exceptionally that switchover
fails, and from then onwards subsequent switchover attempts also fail. As
workaround, when the ONT is ranged on the pref-channel-pair, remove the prot-
channel-pair/alt-pref-channel-pair and reconfigure it again. As workaround when the
ONT is ranged on the prot-channel-pair/alt-pref-channel-pair, first do a chpair-role-
exch command so that the channel pair the ONT is ranged and becomes the pref-
channel-pair, then remove the prot-channel-pair/alt-pref-channel-pair and
reconfigure it again.
 The following restrictions apply to the Equipment Protection via autonomous ONU
retuning feature (feature specific to TWDM-PON on 7360 ISAM FX):
o Once configured, the protection Channel Pair of the ONU is not editable. In
order to change the configuration, the protection Channel Pair must be deleted
and a new protection Channel Pair must be selected for the ONU of interest.
o The protection is currently not revertive. Once an automatic re-tuning
occurred, the ONU will remain on its new active Channel Pair until another
failure event forces it to switch back to its original Channel Pair; until its
active Channel Pair is made admin-down; or, until a manual ONU re-tuning
from its active Channel Pair to its standby Channel Pair by administrative
action.
o So far, this feature was validated for a total of 4 protected ONUs in the
TWDM PON system. The scale and the dimensioning will be extended in
future releases.
o To avoid an ONU re-activation after re-tuning, and thus limit the traffic outage
following a protection switching event, the channel-attachment fibers (fiber
connecting each OLT TWDM-PON port to their respective Wavelength
Multiplexer port) of the Channel Pairs involved in the same Subchannel Group
must be of equal length.
o The traffic that can survive an ONU re-tuning must follow a cross-connect
model in the current release. If another model is used, the system will not
guarantee the recovery of the service.
 HW restrictions:
 TWDM-PON optics:
52/72 Edition 01 – RL 30-Sept-2021
o The OLT optics have a SOA embedded which results in a high output power
level. If insufficient attenuation is used the ONU optics will be destroyed.
Therefore, it is recommended to have a minimum attenuation of 15dB.
o Also, the proper Optical jumpers to use are UPC (blue connectors). Using APC
(green) can cause bit errors which are sometimes uncorrectable.
 Active Wavelength Multiplexer (WM) restrictions:
o The Active WM has an SOA integrated for upstream optical signal. To avoid
that the amplified upstream optical signal damages the OLT optical module,
the path loss of the ODN shall be at least about 20 dB. For details please
contact your Nokia representative.
Following restrictions apply to the functionality of the 7362 ISAM DF-16GW, 7362 ISAM DF-
8G and 7362 ISAM SF-8GW:
 Functional restrictions:
 Management via TL1 is not supported. Only SNMP and CLI management are
supported.
 Under specific scenarios, it may take considerably longer for ONTs to range when
using the Dual-GPON XFP. In particular, this issue was observed when connecting
four ONTs on the same PON port of a 7362 ISAM DF-16GW, and then
disconnecting and reconnecting the drop fiber of three ONTs while keeping the
fourth ONT connected. This scenario shows instabilities during the re-ranging
process, impacting the behavior of the other ONTs. This issue can be avoided by
configuring the DF-16GW to use "alientolerant" ranging mode. This can be done
using the command 'configure pon range-mode'. This ensures the DF-16GW uses a
more robust ranging mechanism.
 The 7362 ISAM DF/SF does not support "S+C VLAN ports" on the UNI interfaces.
As a result, the 7362 ISAM DF/SF does not support a combination of S+C VLAN
iBridge and S-VLAN tunnel iBridge having the same S-VLAN ID.
 The S-VLAN tunnel iBridge and S-VLAN tunnel cross-connect cannot be used to
transport the VLAN for R-APS packets for ERPS, i.e. these forwarders are fully
transparent to data plane and control plane traffic.
 The 7362 ISAM DF/SF does not yet provide software support for the following
synchronization features:
o 1pps + Time of Day input for phase synchronization
 MAC address translation (vMAC) is not supported
 The SFP+ ports can be used as downlink ports in NNI mode, including some
additional functions (i.e. avoiding user-to-user communication between an NNI port
and PON downlink ports and supporting traffic policing ) but has not been validated
to support IGMP-based multicast services
 Type-B protection is not supported
 It is not possible to support a configuration with some ports in GPON mode and
some ports in XGS-PON/TWDM-PON mode. At installation time, operator needs to
define the "shelf mode", which is either GPON only, or XGS-PON/TWDM-PON
only
 The out-of-band management interface has a throughput restriction of maximum
3000 ingress packets per second. Similarly, the in-band traffic on the OAM VLAN
has a throughput restriction of maximum 3000 pps of ingress traffic.
Edition 01 - RL 30-Sept-2021 53/72
 When changing the shelf mode, the configuration of the Ethernet uplinks will be
cleared, including the configured Ethernet MAU type. As a result, the node will fall
back to the default MAU type for the Ethernet ports. This may lead to a MAU type
conflict with the actual connected link type, leading to the link going down and
therefore loss of remote management.
 CFM OAM support on the uplink ports is restricted to one “Fast CCM” (i.e. 10
CCM messages per second) instance on each bridge port, or two Fast CCM instances
per system. This enables fast failure detection using CCM messages in an Ethernet
ring. For this, a Down MEP must be configured on the uplink bridge port.
LTM/LBM are not supported on the Down MEPs on the uplinks. Also, “Normal
CCM”, using long transmission intervals, are not supported.
 The uplink interfaces support load sharing based on hashing of the Ethernet MAC
header and IP header, the so-called “L2/L3 hybrid” hashing. Other hashing
algorithms are not supported. If an operator configures hashing based on the IP
header (and not the MAC header), the configuration command will not be rejected,
but a warning will be prompted for forward compatibility purposes.
 When performing a MAC flush operation during an ERPS switchover event, the
system does not learn MAC addresses of newly received Ethernet frames on any of
its user interfaces or network interfaces. Once the MAC flush has been completed
(typically within 100 milliseconds) traffic will be relearned.
 When enabling 802.1X port-based Network Access Control, the source MAC
address of the incoming EAP packet will be learned, even when the authentication
fails afterwards. The system does not remove the learned MAC address upon
authentication failure.
 When a UNI port enabled with MAB authentication, it is still allowed connecting
802.1x EAP devices under this UNI port to execute 802.1x EAP authentication
instead of MAB. However under heavy traffic conditions the related protocol
packets may not be processed temporarily.
 There is no command to manually force a backup of the current system
configuration on the internal storage. Instead, the system automatically backs up its
configuration every minute. As a result, a power cycle may result in the loss of
configuration performed during the last minute prior to the power cycle.
 In a ring topology, care is needed when performing a node restart with a default
database. Under such condition, all uplink ports of the node will be enabled and as a
result, the ring topology will contain a loop. This will lead to flooding of Ethernet
management traffic and eventually to a node reset. To avoid this, all Ethernet ports
of a link path should be administratively disabled before performing a node restart.
This configuration is persistently stored, and will take effect once the node has
restarted, therefby avoiding the loop in the ring.
 User to User communication on using "Basic Bridge" for IPv4 can only be used for
specific unicast services. User-to-user communication of non-IPv4 or IPv4 multicast
traffic is not supported
 The 7362 ISAM SF-8GW triple power variant is not qualifiied for ETSI customers
and not generally available for ANSI customers.
 7362 ISAM DF-16GW is not at full feature parity with 7360 ISAM FX as some
rather specific QoS functionality is pending. For further clarification please contact
your Nokia representative.
54/72 Edition 01 – RL 30-Sept-2021
 Restrictions relate to network management:
 Prior to R5.6.01, the 7362 ISAM DF-16GW did not create an OAM forwarder, nor
attach the OAM VLAN port to this forwarder, since the system only supported one
logical uplink port. In addition, the configuration of the LAGs and bridge ports was
not stored in the protected database (i.e. data survives a system restart plus survives a
restart of the system with "default database"). Instead, it was assumed there is a
default LAG interface containing all physical interfaces. OAM connectivity was by
default allowed on this default LAG.
 R5.6.01 adds support for storage of the OAM VLAN port, bridge port and LAG
ports in the protected database. In addition, the DF-16GW supports a migration
process where the unit stores all LAGs and bridge ports from the existing DF-16GW
database into the R5.6.01 protected database.
 In order to be backward compatible, the DF-16GW supports the legacy and new
behavior in R5.6.01. In case there is only one logical uplink port created, the system
allows OAM traffic to pass through without explicit configuration as before. Next,
when the operator creates another logical uplink port, he must create the OAM
forwarder and create VLAN ports over both uplink ports in order to properly support
OAM traffic.
 Consequences:
o Prior to R5.6.01, since all active ports are put in the default LAG, we can NOT
control which physical link is used to send out the OAM packets. Thus, OAM
packets may be distributed across all physical links. Hence, after a system
restart the operator may lose management connectivity (packets sent by
management may not be received on the correct physical link).
o After migrating to R5.6.01, the operator MUST explicitly create the OAM
forwarder and VLAN ports, irrespective of the number of logical uplink ports.
If not, OAM connectivity will be lost after a system restart with "default
database" lateron.
 Further background: in R5.6.01, in case no OAM forwarder is created and there are
multiple logical uplink ports, the system will automatically allow the OAM channel
over the over the lowest physical port id (*). When the operator creates the OAM
forwarder lateron and attaches the first VLAN port into this forwarder, the system
switches the OAM channel to the configured OAM forwarder and VLAN port. If on
the other hand the operator does not create the OAM forwarder and VLAN port
explicitly, and then creates a new uplink port with a smaller port id, then the system
will directly switch the OAM channel to this new port (see *). This will result in a
loss of OAM connectivity. This behavior remains the same, regardless of
system/linecard restart.
 HW Restrictions:
 The 7362 ISAM DF/SF is designed to operate in an Ethernet forwarding network
model. Consequently, it does not support IP forwarding, IP routing or MPLS
functionality.
 When configuring Ethernet Ring Protection Switching (ERPS), path A and path B
should have the same R-APS level value within a ring instance and this for each
node in the ring. Otherwise the the ERPS ring may not work properly.
 The 7362 ISAM DF-8G low capacity mini OLT is not generally available.
Edition 01 - RL 30-Sept-2021 55/72
Following restriction applies to 7362 ISAM DF/SF, 7360 ISAM FX (NELT-B and FELT-B):
 The Automatic Laser Shutdown (ALS) state machine, upon receiving light from the peer,
is declaring the link operationally up too quickly, i.e. not leaving enough time to close the
feedback loop between the two peers (i.e. potentially allowing the peer to shut down its
laser again if it has not received light).
 This can lead to link state toggling in specific conditions, i.e. whenever the actual
link state cannot be made known to the peer by other means than the ALS feedback
loop.
 It applies only in case auto-negotiation on GE optional connections is switched off,
whereas, in principle, the standard mandates to have it switched on.
Link state toggling can be observed in exceptional cases when all following
conditions are met;
o Peers are connected over an GE optical connection made of two uni-directional
fibers.
o One of the fibres is broken.
o Auto-negotiation is not enabled on that line.
o An SFP with 2 fibres (1 per direction) is used and only one is broken.
 This line toggling has following undesired consequences;
o False operational state changes are reported and
o static LAG (i.e. LACP is disabled and cannot verify the link sanity for both
directions) suffers from periodic undesired switch-over leading to period
packet losses.
 Workaround:
o Enable auto-negotiation on GE optical connections made of two uni-
directional fibres, especially when they are member of a static LAG, so there is
a hardware hand-shake mechanisms making the state of both fibres known by
the 2 peers at any time, i.e. much faster than what is needed by the ALS
feedback loop. Mind that 10G links do not suffer from this issue because 10G
standards mandate RDI support (not optional like the GE auto-negotiation).
Following restrictions apply to rings hosted by FELT-B.

 ERPS ring on FELT-B is only supported with v-vpls at the iHub, and NNI port on FELT-
B.
 The ERPS over NNI Feature is not generally available.
 The maximum number of VLANs shared across multiple rings (and therefore with MAC
learning enabled) is limited to 128.
 The MEG and MA identifiers associated with fast CCM used to monitor the ring
connectivity can only be specified by programming the last 8 bytes of the identifier field.
 Multicast recovery in case of ring switch-over is fully driven by the IGMP protocols,
potentially taking a few seconds depending on the number of active multicast streams and
the IGMP configuration parameters.
 Duplicate MAC alarm may happen in case of ring switch-over for traffic exchanged in the
ERPS control VLANs. This can be avoided by disabling MAC learning in the associated
iHub v-vpls.
 A fast CCM session on the control VLAN(s) associated with the VLANs shared by the
OLTs on a ring must be configured between each FELT-B and its adjacent OLT on that
ring to recover from all failure cases.
56/72 Edition 01 – RL 30-Sept-2021
Following restrictions apply to cross-LT LAG with load sharing hosted by FELT-B
 The total number of cross-LT LAG with load sharing link members cannot exceed 12 links
over all cross-LT LAGs with load sharing hosted by the FELT-B redundant pair (assuming
the LAG members are equally distributed over the 2 redundant FELT-B, i.e. 6+6)
Following restrictions apply to migration:

 When migrating from a release prior to R6.2.03 and if OSPFv3 is being used, the operator
recommended to disable the lsa-generate configuration prior to migration activity. Once
the migration is successful lsa-generate value need to be re-applied manually. This
restriction does not apply to migration starting from R6.2.03 or later to a higher release.
 Only offline migration is supported when migrating to R6.5.02 from any previous release.
Also upgrade via linked DB to R6.5.02 is not supported. This exception is only applicable
for R6.5.02.
 Migration of DF-16GW node from R6.5.01 or R6.5.01a to R6.5.02 is not supported.
FGLT-D support for the ANSI market:

 FGLT-D although included in ANSI documentation is no longer supported for ANSI
market.
6.2 R6.5.02 Restrictions

GPON OLT
1 BBN-24987 Title: 87 packets lost at the 30th hour during 86 hours soak on 8 * ( 1 ONT per
PON) scenario
Problem: 87 packets lost at the 30th hour are observed during 86 hours soak on 8 * ( 1
ONT per PON) scenario. Occasional packet drops are observed. Two instances where
the issue occurred when the Packet drop rate is 3.4e-8 and 4.4e-8.
2 BBN-28852 Title: Data Traffic is not successful with PON Port 9-12 on FGLT-B
Problem: In one of the OLT installed, they have an issue with FGLT-B board on slot 1
on FX-4, where IP@ are assigned to the users connected with PON Port 9-11, but data
browsing is not successful. when the Fiber was moved to other free PON port in same
OLT, then the Browsing was successful.
3 BBN-28884 Title: SYSTEM MAC confliction between OLTs
(2122530) Problem: Since FANT-H requires extra 32 MACs to support other functions, two
adjacent OLTs have conflicted system MAC and cause L3 communication failed (ARP,
OSPF, etc.)
GPON ONT
4 BBN-28842 Title: ONTs are going into an invalid state after rebooting the OLT
(1955789) Problem: When some 3rd party ONTs are configured on a different PON and are made
operational UP, subsequently "admin equipment reboot-isam with-self-test" is executed.
After the OLT is UP, check the status of the ONTs, all are operational down but we can
see the light levels for some ONT's which are in service but shows as inactive and some
ONTs where we do not see the light levels they are not passing the service.
5 BBN-28844 Title: ONTs under four PONs suffer OMCICOMM due to increasing upstream
(1326227, errors on one XFI link
Edition 01 - RL 30-Sept-2021 57/72
1743113, Problem: ONTs under four PONs suffer OMCICOMM failure. Trouble shooting
2108510, scripts detect this is to increasing upstream errors on one XFI link.
2114589)
L3 Forwarding
6 BBN-29195 Title: BFD packets are dropped on outgoing LAG interface
(2163610) Problem: L3 (ex.IPv4) traffic was sent such a way that it ingresses via IP interface on
top of uplink LAG interface and egress back into same uplink LAG interface after IP
lookup/routing. Such traffic is dropped at Uplink LAG due to recent fix done to prevent
spurious flooding between uplink LAG ports during port operations. This causes
protocols like 1-arm BFD packets to be lost and loss of connectivity to BNG via uplink
LAG interface. The issue can prevent any L3 packet from routed back via same uplink
LAG interface.
7 BBN-28882 Title: IP/IPv6 filter not working fine, in mirror interface
Problem: Egress filtering is not working in the mirror interface. i.e. the L2 or protocol
filtering is not working in egress.
Migration
8 BBN-28840 Title: FWLT-C x2 failed to boot during field trial on ISR6204r
(1918128) Problem: During the conversion of FWLT-B to an FWLT-C. The conversion was
successful and the FWLT-C was inserted. The LT failed to boot, however. It stayed
unknown for a long period of time, but after successfully being detected by the shelf,
went missing multiple times. Alarms indicate plugged out/in three times before they
manually re-seated it. It continued to behave this way. The customer removed it and
installed another FWLT-C, but that card behaved the same. Eventually, they re-installed
the FWLT-B and restored a database from before the conversion.
9 BBN-28887 Title: LT Board SWP Files Missing Post Migration (waiting-for-sw)

(2122594) Problem: When upgrade, the Upgrade failed one time . we use script to test serveral
days, not reproduce this issue. Analyzed it is a randomly HIPC communication error.
Workaround: Just upgrade once more, the issue not seen anymore.
10 BBN-28838 Title: Upgrade of standby NT-B fails, Software Replacement Phase 0 for NT-B
(2103525) failed
Problem: When upgrade of standby NT-B, NTB failed to upgrade to new Software.
Since Active NT-A works, no traffic impact.
Workaround: Just use upgrade command once more, will overcome this problem.
11 BBN-28845 Title: NT does not always reply to SNMP SET for database activation
(1788095) Problem: From production deployment of SF-8GW with R5802s reports of occasional
but consistent error messages from AMS on database activation are received. Lab
reproduction of the issue has been unsuccessful. The reason for the AMS error
message is due to no response from the NE on an SNMP set operation to activate
OSWP. After which AMS experiences timeout (2 retry, 8 and 16 seconds apart).
NT
12 BBN-28843 Title: Standby NT-B fails to boot up due to core1 error
(1930754) Problem: For a particular deployment scenario CF cards are loaded with a generic
configuration using R6.4.00a and then installed on redundant NTs . The following boot-
up the NT will load the configuration from the CF.
Synchronisation
13 BBN-20635 Title: Performance can't recover after plug out the active NT
58/72 Edition 01 – RL 30-Sept-2021
Problem: When FANT-G board SOOC working in active NT, plug out this board,
make NT switch over, after SOOC switch to new active NT, NT ToD can't be
distributed to LT board.
Workaround: Before plug out NT board, make sure it become standby status
XGPON
14 BBN-28831 Title: Post conversion FWLT-B to FWLT-C, on some PON ports select ONTs, do
(2113320) not range
Problem: Post conversion FWWLT-B to FWLT-C, on some PON ports, select ONTs
do not range. When the optics are changed to a different variant the issue clears.
15 BBN-28880 Title: XGS N2 I-Temp XFP optic is not detected on FWLT-B LT card
(2108196) Problem: Two early samples of XFP N2 I-Temp optics with PN 3FE46232BC were
being tested with 7360 on FWLT-B, ONTs connected to the channel pair do not get
discovered. The likely cause is a firmware programming issue with the early samples.
16 BBN-28885 Title: FWLT-C - SFP mismatch alarm with SFP when the burst-overhead setting
is configured
Problem: Following configuration of channel pair with burst-overhead set to "reduced"
with Gen 2 SFP, ONTs range. Once the SFP is replaced by Gen1 SFP we observe SFP
mismatch alarm.
6.3 Known Restrictions from Previous Releases

Nr Id Rel.note entry
GPON OLT
1 BBN-29107 Title: Cagemode not-set taking very long time when more ONT's configured
Problem: The time took to cage mode not-set all cages is given below.
With 128 ONT in all cage it took 5 minutes 5 sec. 64 ONT took 3 minutes 11 second.
While we unplan a FWLT-C with same configuration the time is much lower. With 128
ONT in all cage it took 1 minute 52 sec. 64 ONT took 1 minute 2 second.
L2 Forwarding
2 BBN-13533 Title: DHCP discover msg from DPU discarded by FX due to invalid option82
Problem: The DHCP packet length depends on several parameters including, whether or
not option 82 circuit-id and/or remote-id are to be added and the length of the value that
added to the circuit-id and remote-id. If the length of these parameters is too long or
invalid the messages will get discarded.
Migration
3 BBN-13510 Title: All traffic broken in case of ISSU upgrade from R6.4.00b to R6.5.01
Problem: A traffic outage of 90s happens in case of an ISSU upgrade from R6.4.00b to
R6.5.01 when NT-B is the active NT.
Workaround: Start ISSU upgrade with NTA as active NT
MPLS
4 BBN-13609 Title: Alarm LDPSESSIONDOWN not cleared after LDP peer config removal
Problem: LDPSESSIONDOWN alarm is not cleared when LDP peer configuration is
removed
Workaround: The alarm can be cleared using CLI (or) LDP flap
Impact customer: Less impact. The alarm will be stale and invalid in the system.
QoS
Edition 01 - RL 30-Sept-2021 59/72
5 BBN-29080 Title: trTCM policer issue
Problem: When EIR=64K. The traffic Pbit0 can only pass around 150M. The Pbit7 can
only pass around 300M, Send 8 Pbit DS traffic, there is no SP scheduling.
Redundancy
6 BBN-29104 Title: Reboot issue with FWLT-C
Problem: In an FWLT-C 16pg*8 ONT setup; after a reboot of the ISAM, all paired ports
are act-up on mimic-mode
7 BBN-13740 Title: FWLT-B after force swo then reboot LT swo occur Channel Pair Loss of
Signal
Problem: When RSSI in enabled on FWLT-B, do force SWO , then reboot LT to trigger
another TypeB SWO , there's possibility of PON LOS.
Synchronisation
8 BBN-13591 Title: Dynamic time error (40ns) on FELT-B with stable NT 1pps
Problem: In an end to end environment with FELT-B (with the NT 1pps and FELT-B
CTE stable), there is always an additional dynamic time error that varies from 0 to 40ns
that causes a risk of G.8273.2 noise generation MTIE failure and transient response
failure.
60/72 Edition 01 – RL 30-Sept-2021
7 Migration
Migration to R6.5.02 is supported from:
 R5.5 releases
 R5.6 releases
 R5.7 releases
 R5.8 releases
 R6.0 releases
 R6.1 releases
 R6.2 releases
 R6.4 releases
Edition 01 - RL 30-Sept-2021 61/72
8 Installation Manual
Detailed SW Installation Guidelines for the ISAM Software are described in the ISAM SW
Installation Guide: 3HH-07196-AAAA-RJZZA.
62/72 Edition 01 – RL 30-Sept-2021
9 Validated Voice Supplementary Services
The following is a list of representative POTS supplementary services that are available via the
ISAM Voice working in conjunction with the Nokia MGC/IMS iAGCF products for H248 and
IMS/5420 CTS products for SIP. More extensive treatment of the supplementary services
supported is available in the associated Nokia IMS documentation.
Interoperability of the ISAM Voice with the 3rd party MGC or IMS cores is also possible
through commercial agreement.
The following relates to Voice on Voice LTs inside the ISAM shelves, not to voice on ONTs.
9.1 H.248 POTS Supplementary Services

Supplementary Service 5020MGC12 5020AGCF
Hold For Enquiry [HFE] / Call Hold [CH] Y Y
Call Forwarding Unconditional (CFU) Y Y
Call Forwarding Busy (CFB) Y Y
Call Forwarding No Reply (CFNR) Y Y
Hot Line/Delay Hot Line Y Y
Calling Line Identification Restriction Y Y
Malicious Call Identification Y Not tested
Calling Line Identification Presentation Y Y
Outgoing Call Barring (OCB) Y Y
Do not disturb Y Y
Anonymous Call Rejection Y Y
Abbreviated Address (AA) Y Not tested
Incoming Call Barring (ICB) Y Y
Inhibition of Incoming Forwarded Calls (IIFC) Y Y
Administrative Call Barring Y Not tested
Alarm call Y Not tested
Call Waiting Y Y
Call Return Y Y
Explicit Call Transfer Y Y
Three Party Service Y Y
CWID service Y Not tested
Distinctive Ring Y Not tested
Special Dialtone Y Not tested
VMWI via H248.3 ind package Y Not tested
9.2 SIP POTS Supplementary Service

Supplementary service CTS 5420
Call Hold(CH) Y
Call Forwarding Unconditional(CFU) Y
Call Forwarding Busy(CFB) Y
Call Forwarding No Reply(CFNR) Y
Edition 01 - RL 30-Sept-2021 63/72
Calling Line Identification Restriction(CLIR) Y
Calling Line Identification Presentation(CLIP) Y
Call Waiting(CW) Y
Explicit Call Transfer Y
Three Party Service Y
Call Barring (outgoing) Y
Call Blocking (incoming) Y
Hot Line Y
Anonymous Call rejection Y
Inhibit Call Forwarding Y
64/72 Edition 01 – RL 30-Sept-2021
10 Voice Package Performance
10.1 H.248 POTS Performance
Note: The performance figures heavily depend on H.248 signaling call flows. The data below is
tested with Nokia 5020 MGC12 as reference. The performance could be different while IOT-ing
with other softswitches according to the signaling processing and behavior of different
softswitches.
POTS Performance NVPS-C :
Standard Call Hold Load Model Suppo Performance(B Call Loss

Times rted HCA)
Users
ETSI 90 sec Load A 20k 5000 40k 1.00E-04
Load B 27k
10.2 SIP Performance

ISAM-V SIP POTS Performance(SIP over UDP)
Call Hold Performance
Call Mode Call Loss
Time (BHCA)
24 call 24(NPOT-A) 90 sec 5K 1.00E-04
Edition 01 - RL 30-Sept-2021 65/72
11 Premium Packages
Premium Package concept:
 Premium Packages are bundles of features allowing operators to extend the ability to
deliver premium services to the subscribers.
 Premium packages require separate licenses (refer to PPP), which give the customer the
right to use the features in the contained packages for the corresponding amount of
lines. Therefor the features of these packages are not part of the current Release SW-
update specified in the roadmap.
 The features of the Premium Packages are defined in the specific roadmap for each
customer.
 The number of customer “Right to Use” is limited to a contractually committed
number.
 Premium Package features may be checked (audit) at the customer site. If the number of
“Right to Use” is exceeded the customer is obliged to purchase additional SW licences.
 These additional features within the Premium Packages will only receive technical
support if the “Right to Use” is not above the contractually committed numbers.
 The Premium Packages desribed here are applicable for:
o 7360 ISAM FX
o 7362 ISAM DF
Depending on specific platform characteristics or applications (GPON, equipment

resiliency, …) a specific package might not apply.
Note: The features as described in the below sub-sections are subject to the OLT. With
respect to features supported on a specific ONT type and especially for the ONT-
based DSL and Voice Services; please refer to the ONT Customer documentation if
the respective feature is being supported by the ONT.
11.1 Premium Packages Equipment

NT Load Sharing
 NT Load Sharing license for high capacity NTs on 7360 ISAM FX
 The features enabled with this licence cover:
o NT redundancy, active-active
o sub-1s switching capability
o NT load sharing
o LT load sharing
2.5 G per LT
 Increase the data-rate per line or per user
 Between a high capacity NT (FANT-F/G) and a high capacity LT (e.g. NGLT-A/B) the
internal link speed can be increased from 1 Gbps to 2.5 Gbps.
66/72 Edition 01 – RL 30-Sept-2021
 To effectively increase this internal link speed, this “2.5 Gbps per LT” license is
required. Else it will be limited to 1 Gbps for even these high capacity boards.
 This capability is enabled per ISAM system or shelf and can not be enabled per LT or
slot.
10 G per LT
 Between a high capacity NT (e.g. FANT-F/FANT-G) and a high capacity LT, the
internal link speed can be increased from 1 Gbps to 10 Gbps.
 To effectively increase this internal link speed, this “10 Gbps per LT” license is
slot.
20 G per LT
 Between redundant high capacity NTs (e.g. FANT-F) and a high capacity LT, the
internal link speed can be increased from 1 Gbps to 20 Gbps.
slot.
40 G per LT
 Increase the data-rate per line or per user by synchronising the LTs with NTs (either
simplex or duplex) at 40 Gbps
 Between a high capacity 480 Gbps NT (FANT-F) and a high capacity LT, the internal
link speed can be increased from 1 Gbps to 40 Gbps
required. Else it will be limited to 1 Gbps for even these high capacity boards
slot
100 G per LT
 Increase the data-rate per line or per user by synchronising the LTs with NTs (either
simplex or duplex) at 100 Gbps
 Between a NT and a high capacity LT, the internal link speed can be increased from 1
Gbps to 100 Gbps
required. Else it will be limited to 1 Gbps for even these high capacity boards
 This capability is enabled per ISAM system or shelf and cannot be enabled per LT or
slot
Anti-theft protection
 Protection against the unauthorized removal of NT and LT cards from the ISAM 7360
FX.
Edition 01 - RL 30-Sept-2021 67/72
 Protection against the unauthorized movement of the complete FX shelf.
 When this feature is enabled, unauthorized removal of the cards & unauthorized
movement of the shelf will render them non-operational.
 This capability is enabled per ISAM 7360 system or shelf, but not at board level.
However, protection can be disabled at board level for operational
reasons.
 The capability is supported in FGLT-B, FWLT-A, FWLT-B, FELT-B and all Quillion
LT cards in an ISAM 7360 FX with FANT-F or FANT-G as the NT card.
11.2 Premium Packages Connectivity

Connectivity includes next licenses:
 PPPoX Relay, license per subscriber: enabling either PPPoA to PPPoE relay or PPPoX
relay with MAC@ concentration
 Subscriber Authentication, license per subscriber: Authentication of subscribers based
on 802.1x and Radius server
 IPv4 Security, license per subscriber: all mechanisms enforcing IPv4 security: vMAC,
IPv4 address anti-spoofing, ARP relay proxy and IP filters (ACL)
 IPv6 Security, license per subscriber: IPv6 antispoofing, ICMPv6 filtering
 IPoA encapsulation, license per subscriber: Enabling IPoA encapsulation for either
VLAN-CC or IP routing, IP Routing Re-factoring (IPoA)
 IPv4 Forwarding, license per subscriber: enabling basic routing at ISAM level,
including IGP protocols (RIP, OSPF, IS-IS); practically, this means enabling IPv4
routing at NT
 IPv6 Forwarding, license per subscriber: Enabling IPv6 routing at ISAM level,
including IGP protocols (OSPFv3); Practically, this means enabling IP routing at NT
 BFD, license per node, for IHUB NTs only: used for IP routing and MPLS resiliency
schemes to get a faster detection of the broken link
 MPLS, license per node, for IHUB NTs only: MPLS for residential & business users
 MPLS+, license per node, for IHUB NTs only: DOD, LDP support for Inter-area LSPs
 MPLS OAM, license per node, for IHUB NTs only: MPLS ping, MPLS traceroute, etc
 MPLS Advanced Resiliency, license per node, for IHUB NTs only: MPLS LSR, MPLS
FRR
 PIM-SSM, license per node, for IHUB NTs only: this is a specific routing protocol for
multicast traffic.
 Enhanced Subscriber Management Lawfull Intercept, license per node: this license is
part of the Enhanced Subscriber Management Package. When enabled, it allows for
monitoring a limited set of lines.
 User-to-User Communication, license per node: allows for user to user communication
via the ISAM only
 BGPv4 routing protocol
o Content: BGP allows to integrate the ISAM in a network where route
advertisements are performed through an IGP (e.g. IS-IS or OSFP) and an
EGP (BGP), typically in a Multi-VRF environment
o Applicable Standards: RFC4271, RFC1997
Available (optional) licenses per network model:
68/72 Edition 01 – RL 30-Sept-2021
PPP Subscriber
IP
Network model concen- authentica- IPoA IP routing Comment
security
tration tion
PPP Concentration only
PPP based HSI  - - - - required if PPPoA or PPPoX
concentration is used
Subscriber Authentication
DHCP HSI/Multi-Media untypical
-   - -
VLAN-CC IP Security untypical
(potentially vMAC)
Subscriber Authentication not
DHCP HSI/Multi-Media deployed today
-   - -
i-bridge IP Secure Forwarding
advised (E-i-Bridge)
IP Secure Forwarding IP
DHCP HSI/Multi-Media Routing required
- -  - 
IP routing IPoA untypical
Optional BGP
Business L2VPN - - - - - Transparency required
Two approaches:
 PPP based with
potential PPPoA relay or
Business L3VPN  - -  -
MAC@ concentration
 IP based with
potential IPoA encap
11.3 Premium Package Video Applications

Video License, including IGMPv3
 Video License; license per subscriber;
 Supports IGMPv3, DoS protection for IGMPv3, increased multicast source table, IGMP
echo client/IGMP msg forking
Video Statistics
 Video Statistics; license per subscriber;
 Call Data Records (CDR), accessible via FTP, record all zapping actions of the end
user, by tracking user-id, channel-id and timing information. The CDR generation can
be customized (minimum viewing time before a CDR is generated, use of intermediate
CDRs, etc.).
 Call Data Records available via Syslog, in near real-time.
Video Wholesale
 Video Wholesale; license per subscriber;
 Cross-VLAN multicast: infeed of channels from multiple VLANs. Service from
different providers is segregated in the network.
Edition 01 - RL 30-Sept-2021 69/72
 Channel package policing. Allows offering end-users restricted access to a specific set
of channels from a selected subset of content providers.
 Bundles of channels, BW management and SLA per provider. This supports the BW
management for wholesale environments, both in a L2 and in a L3 aggregation
network.
 Statistics on service fulfilment per channel and per bundle. Feedback on SLA and
service fulfilment per provider.
 IGMP Source Specific Multicast:
o Distinguishes multicast channels by group IP-address and source IP-address,
the client (STB) sends IGMP messages that not only specify the group IP-
address but also the source IP-address of the video server.
o Video service wholesale (L2), different service providers can choose group IP-
address for their channels independently. Group IP-address from different
providers may overlap.
11.4 Premium Packages Transport
11.4.1 Premium Package Reference Timing Source

SyncE Reference Timing Source
 License per NT port on which SyncE is activated
 ISAM can accept synchronization input not only via E1/T1 BITS, but also via
Synchronous Ethernet, for which this license is required
 Synchronization input via synchronous Ethernet (as opposed to BITS) is also possible
in places where there is no BITS network (e.g. in cabinets).
 Applicable standards ITU-T G.8261/Y.1361 (formerly G.pactiming) "Timing and
Synchronization Aspects in Packet Network
 Use of BITS or SyncE external clock at the NT is required for GPON applications
ToD (Time of Day) Reference Timing Source

 License per ToD external input source configured as ToD reference
 ToD reference source as input is used for phase/ToD synchronization, mainly applied
on Mobile Backhaul application for base-station sync.
11.4.2 Premium Package Type-B PON Protection

ISAM Type-B PON Protection Package
 Large bundles of feeders in a cable or duct increase the risk of intolerable repair times
in case of a breach or an accident. Furthermore, the increasing number of split ratios
and deployment of business-critical services highlight the importance of implementing
PON protection schemes.
70/72 Edition 01 – RL 30-Sept-2021
 ITU-T G984.1 (section 14.2.1) and ITU-T G.sup51 (section 5) specifications describe
multiple PON protection schemes. The ISAM OLT implements the Type-B protection
architecture for GPON access, which addresses route diversity to the first splitter in a
1:1 arrangement (active-standby). This configuration doubles the OLTs and the optical
fibres between the OLTs and the optical splitter, and the splitter has two input/output
ports on the OLT side. Hence, this functionality is also known as PON feeder
protection.
 The PON links of the ISAM can be configured in Protection Groups (PGs) on the
GPON linecards (inter-card protection among linecards of the same type, within the
same OLT chassis). In case of an active PON link failure (e.g. fibre cut on the active
PON feeder), all traffic is switched to the associated standby protection link without
service loss and without necessitating a full reactivation of the ONUs on their new
active PON.
 ISAM Type-B PON Protection Package is a license per configured GPON Protection
Group.
11.4.3 Premium Package 40 km Differential Distance PON

Operation
40 km Differential Distance PON Operation
 The differential distance refers to the relative position of the closest and farthest ONTs
on a PON with respect to the Central Office. Standard PON operations are supported
for ONTs placed on the PON across this range. In normal operations a differential
distance of 20 km is expected to be deployed. In this scheme, the closest ONT distance
is a provisioned parameter.
 The present premium feature allows to extend PON deployments to a 40 km differential
range where the closest ONT distance is still a provisionable parameter between 0 and
20 km. So, in essence, the most far ONT on a PON can be placed at a 60 km distance
from the CO.
 This behavior is defined on a per PON basis
 The actual performance may depend on the power and sensitivity characteristics of the
ONTs that are deployed. Please check related ONT documentation.
11.4.4 Premium Package NGPON2 Multi-Lambda

 Required in case multiple TWDM wavelengths are stacked on the PON. This will allow
the operator to move ONTs from one wavelength to another
 This requires ONUs that support tunable optics so if they range on a non-preferred
channel pair and then the system can request they retune to the preferred channel pair
within the same Channel Group.
 Scope: ISAM 7360 system and requires the use of the FANT-F and the FWLT-A
Edition 01 - RL 30-Sept-2021 71/72
11.4.5 Premium Package XGS-PON and NGPON2 Enhanced
10Gbps Upstream
 10Gbps symmetrical NGPON2 or 10Gbps symmetrical + 10Gbps/2.5Gbps dual-rate
XGS-PON service over fiber, high bandwidth for business customers
o Ultra broadband service enabler for fixed-wireless full service operators.
o Next generation backhaul solution
 Full range of fault management, configuration, accounting, performance, and security
(FCAPS) functions
 Licensed per PON port
 Scope: 7360 ISAM FX
11.4.6 Premium Package Ethernet OAM

ISAM Ethernet OAM Package
 Ethernet Connectivity Fault Management provides capabilities for connectivity
verification, as well as detection, verification & isolation of connectivity failures, using
specific maintenance points on LT user ports & NT uplinks.
 Applicable Standards: IEE802.1ag and ITU-T Y.1731
 ISAM Ethernet OAM Package is a license per MEP
 Scope: all IHUB-based 7360 ISAM FX NT’s; e.g. FANT-F
 This license does not apply to xPON LT’s
11.4.7 VULA Uplink SW Package

 Virtual Unbundled Local Access (VULA) ISAM as handover point between Access
Provide and Servie Provider
 Downstream SLA enforcement features that one would expect on edge switches
 It ensures fairness between subscribers, across multiple Service Providers, via its
advanced QoS/VLAN features
 Scope: P2P Fiber FELT-B
72/72 Edition 01 – RL 30-Sept-2021

3FE-77621-AACA-FMZZA-01-ISAM R6 - 5 - 02 Customer Release Note

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3FE-77621-AACA-FMZZA-01-ISAM R6 - 5 - 02 Customer Release Note

Uploaded by

Copyright:

Available Formats

7360 ISAM FX

7362 ISAM DF/SF

September 30, 2021

© 2021 Nokia. Nokia Confidential Information

2.2 New Features

7360 ISAM FX: Intra-shelf Type-B protection with FGLT-D/FWLT-C/FGUT-A (R6.5)

7360 ISAM FX: Intra-shelf Type-B protection with FGLT-E (R6.5)

7360 ISAM FX: Enhancements for dual-stack Access Network

7360 ISAM FX: OSPF with IPv6 on VPRNs (R6.5)

7360 ISAM FX: New FANT-H BC variant to support FX-4/8 in

7360 ISAM FX: Retrieval of actual power consumption (R6.5.01)

7360 ISAM FX: Retrieval of power related metric (R6.5.02)

7362 ISAM DF: LLDP support on uplink ports (R6.5.01)

7360 ISAM FX: Antitheft Protection for FANT-H

7362 ISAM DF: UNI loopback and GPON functionality (R6.5.01)

7360 ISAM FX: GPRS Tunnel Protocol based hashing for

7360 ISAM FX: Pluggable passive CEx cassette enabling coexistence

7360 ISAM FX: Management of external amplifier using GE i/f

7360 ISAM FX: 25G PON enablement on ISAM FX equipped with

7360 ISAM FX: Support of OLT-ONT lock feature (R6.5)

7360 ISAM FX: Default range mode for GPON changed

7360 ISAM FX: Support of 64 bit ethernet PM rolling counters using

2.3 Feature Change

3 BBN-12586 Title: 7362 ISAM DF-8G - power-oper-mode is always dc-local

2.5 R6.5.01 Corrections/Improvements

2 ALU02742917 Title: FGLT-B reset caused by the TM crash event CorrECCErr

5 ALU02738340 Title: FGLT-D - Startup and Link Issues

24 ALU02741367 Title: FWLT-C - Queue weights inaccurate

35 ALU02741034 Title: Incorrect CDE feature pre-R35PPPQoSHandling bitmap position

39 ALU02746952 Title: AGC mode display issue on NGLT-C card

2.6 R6.5 Corrections/Improvements

7 ALU02738339 Title: FGLT-D - Startup and Link Issues

9 ALU02719790 Title: Network port on the standby NT fails to come up

11 ALU02723253 Title: ISAM wrongly reboots while using TL1

19 ALU02727329 Title: Abnormal Tx power observed on NT board uplink port after

31 ALU02733585 Title: ONT Inactive reported instead of PON LOS

38 ALU02737163 Title: Diff_reach 34km not supported for FWLT-C/FGLT-D

Note Boards with software preinstalled in EPROMs are released as

3.2 Delivered XDSL Proxies

3.3 Delivered Documentation

3.3.1 Documentation Restrictions/Inconsistencies

Item Number Description

5.2 TL1 and CLI

Document Number Description

5.2.1 CLI/TL1 commands & parameters phased out

Following restrictions apply to the functionality of NELT-B in 7360 ISAM FX:

Following restrictions apply to the functionality of FANT-F in 7360 ISAM FX:

Following restrictions apply to the functionality of the 7360 ISAM FX:

Following restrictions apply to rings hosted by FELT-B.

Following restrictions apply to migration:

FGLT-D support for the ANSI market:

6.2 R6.5.02 Restrictions

9 BBN-28887 Title: LT Board SWP Files Missing Post Migration (waiting-for-sw)

6.3 Known Restrictions from Previous Releases

9.1 H.248 POTS Supplementary Services

9.2 SIP POTS Supplementary Service

POTS Performance NVPS-C :

Standard Call Hold Load Model Suppo Performance(B Call Loss

ETSI 90 sec Load A 20k 5000 40k 1.00E-04

10.2 SIP Performance

Depending on specific platform characteristics or applications (GPON, equipment

11.1 Premium Packages Equipment

11.2 Premium Packages Connectivity