Datacom DM984-100B Administration Manual

ADMINISTRATION-MANUAL
GPON - ONU
DM984-100B
DM984 product family CONTENTS
Contents
1 Revision History 8
2 Legal notice 9
4 Acronyms 11
5 About 14
6 DM984-100B at a Glance 15
6.1 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
6.1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 16
6.1.2 Descriptions . . . . . . . . . . . . . . . . . . . . . . . . 16
6.2 Backside Description . . . . . . . . . . . . . . . . . . . . . . . . 17
6.2.1 RESET-Button . . . . . . . . . . . . . . . . . . . . . . . 17
6.2.2 WPS-Button . . . . . . . . . . . . . . . . . . . . . . . . 17
6.3 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
6.3.1 Power supply . . . . . . . . . . . . . . . . . . . . . . . . 18
6.3.2 Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . 18
6.3.3 Management . . . . . . . . . . . . . . . . . . . . . . . . 18
6.3.4 Operating Conditions . . . . . . . . . . . . . . . . . . . 19
6.3.5 Features . . . . . . . . . . . . . . . . . . . . . . . . . . 19
7 Introduction 22
7.1 Physical Specifications . . . . . . . . . . . . . . . . . . . . . . . 22
7.2 T-CONTs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
7.3 GEM-Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
8 Physical Setup 25
8.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
204.4288.00
DATACOM
DM984 product family CONTENTS
8.2 IP Multiservice Access Platform (IPSAN) . . . . . . . . . . . . . 25
9 Operation with OLTs from other vendors 26
9.1 Registration and Configuration . . . . . . . . . . . . . . . . . . 26
9.2 Checking the Firmware version . . . . . . . . . . . . . . . . . . 26
9.3 Upgrading the Firmware . . . . . . . . . . . . . . . . . . . . . . 26
10 First Steps with IPSAN 27
10.1 Initial Connection . . . . . . . . . . . . . . . . . . . . . . . . . 27
10.2 Working with the CLI . . . . . . . . . . . . . . . . . . . . . . . 28
10.3 Saving configurations . . . . . . . . . . . . . . . . . . . . . . . 29
10.4 Marking Configurations for Startup . . . . . . . . . . . . . . . . 30
10.5 Rebooting the Equipment . . . . . . . . . . . . . . . . . . . . . 30
10.6 Setup of Management Access via Telnet . . . . . . . . . . . . . 30
10.7 Setup of Management Access via SSH . . . . . . . . . . . . . . 31
11 IPSAN Configuration 33
11.1 ONU Registration . . . . . . . . . . . . . . . . . . . . . . . . . 33
11.2 ONU status checking . . . . . . . . . . . . . . . . . . . . . . . 35
11.3 Checking the Firmware version of the ONU . . . . . . . . . . . . 36
11.4 Checking allocated bandwidth . . . . . . . . . . . . . . . . . . . 37
11.5 ONU Firmware upgrade . . . . . . . . . . . . . . . . . . . . . . 37
11.6 Profile Management . . . . . . . . . . . . . . . . . . . . . . . . 39
11.6.1 ONU-Profile . . . . . . . . . . . . . . . . . . . . . . . . 39
11.6.2 SLA-Profile . . . . . . . . . . . . . . . . . . . . . . . . . 41
11.6.3 Checking allocated bandwidth in more detail . . . . . . . 42
11.6.4 VP-SVC-Profile . . . . . . . . . . . . . . . . . . . . . . 42
11.6.5 TCONT-VP-BIND-Profile . . . . . . . . . . . . . . . . . 43
11.6.6 FLOW-Profile . . . . . . . . . . . . . . . . . . . . . . . 45
11.7 VLAN Translation Rules . . . . . . . . . . . . . . . . . . . . . . 47
11.7.1 VLAN Rules for Single Tagging Operations . . . . . . . . 47
11.7.2 VLAN Rules for Double Tagging Operations . . . . . . . 50
11.7.3 Setting the VLAN TPID . . . . . . . . . . . . . . . . . . 51
11.8 Additional ONU Configuration . . . . . . . . . . . . . . . . . . . 51
11.8.1 Assigning VLAN rules . . . . . . . . . . . . . . . . . . . 52
11.8.2 Assigning Native VLANs . . . . . . . . . . . . . . . . . . 52
11.8.3 Configuring the IP Whitelist . . . . . . . . . . . . . . . . 54
11.8.4 Configuration of an IP Address . . . . . . . . . . . . . . 55
11.8.5 Configuration of a Default Gateway . . . . . . . . . . . . 55
11.9 Configuring the Uplink Interface . . . . . . . . . . . . . . . . . . 56
11.10Configuring the VLAN Interface . . . . . . . . . . . . . . . . . . 57
DATACOM
204.4288.00
DM984 product family CONTENTS
11.11IGMP-Controlled Multicast . . . . . . . . . . . . . . . . . . . . 58
12 Configuration Guides 61
12.1 Simple Connection with Single Tagged VLAN Setup . . . . . . . 61
12.2 Multiple VLANs and T-CONTs with different Bandwidths Setup . 62
12.3 VLAN Translation Setup . . . . . . . . . . . . . . . . . . . . . . 63
12.4 IGMP Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
13 Examples 65
13.1 Simple Connection with Single Tagged VLAN . . . . . . . . . . . 65
13.2 Multiple VLANs and T-CONTs with different Bandwidths . . . . 66
13.3 VLAN Translation Setup . . . . . . . . . . . . . . . . . . . . . . 67
13.4 IGMP Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
14 Supported MEs 70
14.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
14.2 Managed Entity Description . . . . . . . . . . . . . . . . . . . . 73
14.2.1 802.1p Mapper Service Profile . . . . . . . . . . . . . . . 73
14.2.2 ANI-G . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
14.2.3 Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . 74
14.2.4 Authentication Security Method . . . . . . . . . . . . . . 74
14.2.5 Cardholder . . . . . . . . . . . . . . . . . . . . . . . . . 75
14.2.6 Circuit Pack . . . . . . . . . . . . . . . . . . . . . . . . 75
14.2.7 Dot1 Rate Limiter . . . . . . . . . . . . . . . . . . . . . 76
14.2.8 Dot1X Port Extension Package . . . . . . . . . . . . . . 76
14.2.9 Equipment Extension Package . . . . . . . . . . . . . . . 77
14.2.10 Ethernet Frame Extended Performance Monitoring His-
tory Data . . . . . . . . . . . . . . . . . . . . . . . . . . 77
14.2.11 Ethernet Frame Performance Monitoring History Data Down-
stream . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
14.2.12 Ethernet Frame Performance Monitoring History Data Up-
stream . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
14.2.13 Ethernet Performance Monitoring History Data . . . . . . 79
14.2.14 Ethernet Performance Monitoring History Data 2 . . . . . 80
14.2.15 Ethernet Performance Monitoring History Data 3 . . . . . 80
14.2.16 Extended VLAN Tagging Operation Configuration Data . 81
14.2.17 FEC Performance Monitoring History Data . . . . . . . . 82
14.2.18 GAL Ethernet Performance Monitoring History Data . . . 82
14.2.19 GAL Ethernet Profile . . . . . . . . . . . . . . . . . . . 83
14.2.20 GEM Interworking Termination Point (GEM ITP) . . . . 83
14.2.21 GEM Port Network CTP . . . . . . . . . . . . . . . . . . 84
DATACOM
204.4288.00
DM984 product family CONTENTS
14.2.22 GEM Port Network CTP Performance Monitoring History
Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
14.2.23 GEM Port Performance Monitoring History Data . . . . . 85
14.2.24 IP Host Config Data . . . . . . . . . . . . . . . . . . . . 85
14.2.25 IP Host Performance Monitoring History Data . . . . . . 86
14.2.26 IPv6 Host Config Data . . . . . . . . . . . . . . . . . . . 86
14.2.27 Large String . . . . . . . . . . . . . . . . . . . . . . . . 86
14.2.28 MAC Bridge Configuration Data . . . . . . . . . . . . . 87
14.2.29 MAC Bridge Performance Monitoring History Data . . . . 87
14.2.30 MAC Bridge Port Bridge Table Data . . . . . . . . . . . 88
14.2.31 MAC Bridge Port Configuration Data . . . . . . . . . . . 88
14.2.32 MAC Bridge Port Designation Data . . . . . . . . . . . . 89
14.2.33 MAC Bridge Port Filter Preassign Data . . . . . . . . . . 89
14.2.34 MAC Bridge Port Filter Table Data . . . . . . . . . . . . 89
14.2.35 MAC Bridge Port Performance Monitoring History Data . 90
14.2.36 MAC Bridge Service Profile . . . . . . . . . . . . . . . . 90
14.2.37 Managed Entity . . . . . . . . . . . . . . . . . . . . . . 91
14.2.38 Multicast GEM Interworking Termination Point . . . . . . 91
14.2.39 Multicast Operations Profile . . . . . . . . . . . . . . . . 91
14.2.40 Multicast Subscriber Config Info . . . . . . . . . . . . . . 92
14.2.41 Multicast Subscriber Monitor . . . . . . . . . . . . . . . 93
14.2.42 Network Address . . . . . . . . . . . . . . . . . . . . . . 93
14.2.43 OLT-G . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
14.2.44 OMCI . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
14.2.45 ONU Data . . . . . . . . . . . . . . . . . . . . . . . . . 94
14.2.46 ONU Dynamic Power Management Control . . . . . . . . 94
14.2.47 ONU Power Shedding . . . . . . . . . . . . . . . . . . . 95
14.2.48 ONU Remote Debug . . . . . . . . . . . . . . . . . . . . 96
14.2.49 ONU2-G . . . . . . . . . . . . . . . . . . . . . . . . . . 96
14.2.50 ONU-G . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
14.2.51 Physical Path Termination Point Ethernet UNI (PPTP
Ethernet UNI) . . . . . . . . . . . . . . . . . . . . . . . 97
14.2.52 Port Mapping Package . . . . . . . . . . . . . . . . . . . 98
14.2.53 Priority Queue . . . . . . . . . . . . . . . . . . . . . . . 98
14.2.54 Software Image . . . . . . . . . . . . . . . . . . . . . . . 99
14.2.55 T-CONT . . . . . . . . . . . . . . . . . . . . . . . . . . 99
14.2.56 TCP/UDP Config Data . . . . . . . . . . . . . . . . . . 100
14.2.57 TCP/UDP Performance Monitoring History Data . . . . . 100
14.2.58 Threshold Data 1 . . . . . . . . . . . . . . . . . . . . . 101
14.2.59 Threshold Data 2 . . . . . . . . . . . . . . . . . . . . . 101
14.2.60 Traffic Descriptor . . . . . . . . . . . . . . . . . . . . . 101
DATACOM
204.4288.00
DM984 product family CONTENTS
14.2.61 Traffic Scheduler . . . . . . . . . . . . . . . . . . . . . . 102
14.2.62 UNI-G . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
14.2.63 Virtual Ethernet interface point . . . . . . . . . . . . . . 102
14.2.64 VLAN Tagging Filter Data . . . . . . . . . . . . . . . . . 103
14.2.65 VLAN Tagging Operation Configuration Data . . . . . . 103
DATACOM
204.4288.00
DM984 product family LIST OF FIGURES
List of Figures
6.1 DM984 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.2 Topview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
6.3 View of DM984-100 interfaces . . . . . . . . . . . . . . . . . . . 17
7.1 Possible Topology for GPON . . . . . . . . . . . . . . . . . . . 22
7.2 GPON Architectures . . . . . . . . . . . . . . . . . . . . . . . . 23
11.1 Relations of GPON-Profiles . . . . . . . . . . . . . . . . . . . . 39
DATACOM
204.4288.00
DM984 product family CHAPTER 1. REVISION HISTORY

1. Revision History

Version Comments
v1.1.0 Release version
DATACOM
204.4288.00
DM984 product family CHAPTER 2. LEGAL NOTICE

2. Legal notice

Although every precaution has been taken in the preparation of this document, DATACOM takes no responsibility for possible errors or omissions, and it will accept no obligation for damages resulting from the use of the information con­tained in this manual. The specifications provided in this manual are subject to changes without notice, and they will not be recognized as any kind of contract. Any quotes in this document are property of their respective third party owners and come without warranty.
c
2015 DATACOM - All rights reserved.
DATACOM
204.4288.00
DM984 product family CHAPTER 3. WARRANTY

3. Warranty

This product is warranted against material and workmanship defects for the pe­riod specified in the sales invoice. The warranty only includes the repair and replacement of defective components and parts without any resulting burden to the customer. Defects resulting from the following are not covered: improper use of device, faulty electrical power network, nature-related events (lightning discharges, for instance), failure in devices connected to this product, installa­tions with improper grounding or repairs made by personnel not authorized by DATACOM. This warranty does not cover repairs at the customer’s facilities. Equipment must be forwarded for repairs to DATACOM.
DATACOM
204.4288.00
DM984 product family CHAPTER 4. ACRONYMS
4. Acronyms and declarations
ANI-G (Access Node Interface-GPON)
CLI (Command Line Interface) – User Interface where commands are issued in form of text. In the context of this manual this term is referring to the IPSAN’s Command Line Interface unless specified otherwise.
CTP (Connection Termination Point)
DBA (Dynamic Bandwidth Allocation) - standardized mechanism for bandwidth management
DFB (Distributed Feedback Laser)
DTMF (Dual-tone multi-frequency)
FEC (Forward Error Correction)
FTTB/C (Fiber-to-the-Building/Curb) – Common GPON architecture where the service is provided for one or more buildings
FTTCab (Fiber-to-the-Cabinet) – Common GPON architecture which is simi­lar to FTTB/C but the actual end of the GPON network is considered to be nearer at the service provider
FTTH (Fiber-to-the-Home) – Common GPON architecture where the service is provided for a single customer
GEM-Port (GPON encapsulation method port) – Used to differentiate between data inside of a T-CONT
GPON (Gigabit-capable Passive Optical Network) – refer to Introduction into
204.4288.00
DATACOM
DM984 product family CHAPTER 4. ACRONYMS
GPON for further information
IPSAN (IP Multiservice Access Platform) – DM4600 Product Line including sup­port for GPON and many other Services
ITP (Interworking Termintation Point)
MAC (Media Access Control)
ME (Managed Entity) – Specific part of a configuration that is present on the ONU. A managed entity is configured by one or more OMCI messages.
ODN (Optical Distribution Network) – physical network connecting OLT and ONU
OFE (Optical Fiber Enclosure) - Underside Enclosure where the fiber is stored
OLT (Optical Line Termination) – Formal declaration of a configuring hard­ware/software in a GPON network
OMCI (Optical network unit Management and Control Interface) – Used by the OLT to configure the ONU and watch its behaviour
ONT (Optical Network Termination) – see ONU
1
ONU (Optical Network Unit) – Formal declaration of the user node hardware/­software in a GPON network that will be configured by an OLT
PPTP (Physical Path Termination Point) - for example an Ethernet interface
QoS (Quality of Service) – Queuing protocol for preferential data handling
SFP (Small form-factor pluggable) – Used to enable different types of physi­cal connections depending on the customer needs
SNI (Service Node Interface) – Interfaces at the OLT used by the service provider to deliver the data to a user
1
ONU and ONT is often considered to be the same. This practice is followed in this manual. However, there is a difference between ONU and ONT, as ONT describes only the GPON part of a user device. To avoid confusion between the terms or with the acronym OLT the device is called ONU further on.
DATACOM
204.4288.00
DM984 product family CHAPTER 4. ACRONYMS
T-CONT (Transmission Containers) – Used for assignments of specific services (e.g. different bandwidths)
UNI (User Network Interface) – Interfaces at the ONU used by a user to ac­cess the GPON network
DATACOM
204.4288.00
DM984 product family CHAPTER 5. ABOUT
5. About this Manual
In order to use this manual, fundamental knowledge about network processes is mandatory.
DATACOM
204.4288.00
DM984 product family CHAPTER 6. DM984-100B AT A GLANCE

6. DM984-100B at a Glance

DATACOM
Figure 6.1: DM984
204.4288.00
DM984 product family CHAPTER 6. DM984-100B AT A GLANCE
6.1 LEDs
6.1.1 Overview
Figure 6.2: LED view of DM984
6.1.2 Descriptions
POWER
Behavior Event
Constant green ONU is powered on Constant off ONU is powered off
ALARM
Not in use on this product model.
PON
Behavior Event
Constant green Connection to OLT established Constant off No connection to OLT
ETH1
Behavior Event
Constant green Connected but no Ethernet traffic Constant off No Ethernet connection
DATACOM
204.4288.00
DM984 product family CHAPTER 6. DM984-100B AT A GLANCE
Green blinking Under Ethernet traffic
ETH2
Not in use on this product model.
ETH3
Not in use on this product model.
ETH4
Not in use on this product model.
TEL
Not in use on this product model.
WIFI
Not in use on this product model.
6.2 Backside Description
Figure 6.3: Backside of DM984-100
6.2.1 RESET-Button
Not in use on this product model.
6.2.2 WPS-Button
Not in use on this product model.
DATACOM
204.4288.00
DM984 product family CHAPTER 6. DM984-100B AT A GLANCE
6.3 Specifications
The DM984 GPON ONU is an optical network terminal that offers one Gigabit Ethernet LAN interface and an integrated OFE (optional).
It has the ability to add, remove and modify VLANs, supports multicast traf­fic (e.g. video transport) and has QoS functionality.
6.3.1 Power supply
The DM984 uses an external power source with the following characteristics.
Input: 100Vac to 240Vac Full Range (automatic selection), 50Hz to 60Hz
Output: 12Vdc 500mA
Device consumption: <4W
Attention: Use only the power supply shipped with the DM984-100B. The device may experience severe damage if another power supply is used.
6.3.2 Dimensions
The DM984 GPON ONU is presented in a desktop enclosure
– With integrated OFE, it measures 190mm in width, 160mm in depth
and 46mm in height, including its rubber feet.
– Without integrated OFE, it measures 180mm in width, 160mm in
depth and 36mm in height.
6.3.3 Management
Uses OMCI protocol for management, according to ITU-T G.988[4]
Allows remote firmware upgrade;
Allows storage of two firmware images with software integrity check and
possible rollback
DATACOM
204.4288.00
DM984 product family CHAPTER 6. DM984-100B AT A GLANCE
6.3.4 Operating Conditions
Operating Temperature: 0◦C to 45◦C
Operating Humidity: 5% - 95% non-condensing
6.3.5 Features
GPON Interface (WAN)
Compliant with ITU-T G.984[3]
Connector SC/APC
Supports burst mode of 1.244 Gbit/s Upstream
Supports burst mode of 2.488 Gbit/s Downstream
Performance Monitoring
DFB Laser, according to ITU-T G.984.2[2] AMD1
Average optical transmit power: Between +0.5 dBm and +5 dBm
Receive Sensitivity: At least -27 dBm
Overload reception:-8 dBm
(Signal should not be higher than -8dBm otherwise it will not work properly)
Wavelengths:
Upstream: 1310 nm
Downstream: 1490 nm
Laser Class I
Dying Gasp
Up to 8 T-CONTs and 32 GEM ports possible
VLAN or VLAN plus 802.1p mapping to GEM ports
Upstream SP, WRR, SP+WRR scheduling
Flexible mapping between GEM Ports and T-CONTs
DATACOM
204.4288.00
DM984 product family CHAPTER 6. DM984-100B AT A GLANCE
Activation by automatic discovery of serial number and password as ITU-T G.984.3[5]
AES-128 downstream decryption
DBA (DBRU)
Bidirectional FEC (Forward Error Correction)
VLAN plus 802.1p QoS for dropping un-allowed p-bits
VLAN plus 802.1p Rate limiting
Gigabit Ethernet Interface (LAN)
RJ45 Connectors
10/100/1000 Base-T interfaces
Auto negotiation or manual configuration
MDI / MDIX
Bridging (802.1D)
Virtual Bridge
Adding or removing VLAN tags
VLAN stacking (QinQ) and VLAN translation
Classes of service based on ports, VLAN ID, 802.1p or a combination
Jumbo frames up to 9kB
MAC learning
VLANs 1-4094
Rate limiting per VLAN and 802.1p combination
Broadcast and Multicast
IGMPv2/v3 snooping
Broadcast and multicast rate limit
50 multicast groups
DATACOM
204.4288.00
DM984 product family CHAPTER 6. DM984-100B AT A GLANCE
Management and Configuration
Advanced PLOAM functions
OMCI
Firmware image uploads through OMCI according to G.988[4]
Dual image
Remote reboot
DATACOM
204.4288.00
DM984 product family CHAPTER 7. INTRODUCTION
7. Introduction into GPON
The main characteristics of Passive Optical Networks (PON) is that there are no electrical components in use for signal distribution. This architecture is mainly used as a solution for access to the last mile, leading optical fiber cabling and signals nearest to end user. A PON system has the ability to deliver high speed rates for broadband access.
The first PON was based on ATM (called APON, now renamed to broadband or BPON) and it has evolved to today’s dominants Gigabit PON (GPON) and Ethernet PON (EPON). All of these optical technologies create split multi-site connection paths, they are built using a similar topology, and components like shown by Figure 7.1.
Figure 7.1: Possible Topology for GPON
7.1 Physical Specifications
GPON is a technology used to realize FTTx (e.g. Fiber-to-the-Home) architec­tures (See Figure 7.2). A network that uses GPON technology basically consists
204.4288.00
DATACOM
DM984 product family CHAPTER 7. INTRODUCTION
of two main parts, the OLT and one or more ONUs. In general, all operations to provision a GPON are issued at the OLT and sent via OMCI messages to the ONU. An ODN connects the OLT and the ONUs.
As defined in the ITU-T G.984.1 standard[3] GPON devices are capable of pro­cessing traffic up to 2.488 Gbit/s in downstream and 1.244 Gbit/s in upstream direction.
The physical reach is the maximum physical distance between the ONU/ONT and the OLT. In GPON, two options are defined for the physical reach: 10 km and 20 km. It is assumed that 10 km is the maximum distance over which FP-LD can be used. However, this ONU uses a DFB laser diode, so it is able to operate at a maximum distance of 20 km.
Figure 7.2: GPON Architectures[3]
7.2 Transmission Containers (T-CONTs)
A transmission container or T-CONT is a group of logical connections. For one ONU there are multiple T-CONTs possible. The number of supported T-CONTs depends on the ONU software. One T-CONT has a specific bandwidth allocation. Each T-CONT is supposed to provide different services.
204.4288.00
DATACOM
DM984 product family CHAPTER 7. INTRODUCTION
7.3 GPON encapsulation method port (GEM-Port)
GEM is a data frame transport scheme used in GPON systems which is connection­oriented and supports fragmentation of user data frames into variable-sized trans­mission fragments. One or more GEM-Ports on the other hand are a logical gateways for specific user data flows that are assigned to a specific T-CONT. So it is possible to differentiate between user data within the same service that is represented by a T-CONT.
DATACOM
204.4288.00
DM984 product family CHAPTER 8. PHYSICAL SETUP

8. Physical Setup

8.1 Overview
To achieve any GPON setup described in this manual it is assumed that there is an OLT, which configures the ONU. According to ITU-T G.984.1[3] it is intended to have a passive fiber connection between the OLT and the ONU. It may include optical splitters as well as other passive network components. In a typical FTTH scenario the ONU is connected to the OLT via the ODN and the customer may connect it to his local network. The OLT must also be connected to the service providers’ network. The setup may vary for different scenarios. For an introduction into GPON please refer to the chapter Introduction into GPON. Additionally refer to the manual of the OLT vendor to be sure the ONU is connected correctly.
8.2 IP Multiservice Access Platform (IPSAN)
In case of using the IPSAN as OLT, there is a dedicated GPON card installed which is used to connect the ONU via the ODN to a GPON interface at the GPON card of the IPSAN. Such a GPON interface is also called ponlink in short which will be the convention in this document. In addition to the ONU connections, the IPSAN needs at least one more connection, which acts as uplink to the service providers’ network. Depending on the customers needs, it is also possible to define more than one uplink. Each of the connections to the IPSAN may need a specific SFP to connect the cables to the interfaces. The setup for the scenario with FTTH described above remains the same. Note that the IPSAN is not only an OLT and may be used for other purposes too. For a full guide to all of the supported GPON features, as well as other functionalities please refer to the dedicated IPSAN’s User Manual.[1]
204.4288.00
DATACOM
DM984 product family CHAPTER 9. OPERATION WITH OLTS FROM OTHER VENDORS

9. Operation with OLTs from other vendors

9.1 Registration and Configuration
There are two values that are used by the OLT to identify the ONU. The ONU has a unique serial number and a password. While the password is changeable, the serial number is not. With these two values the ONU can be registered in 3 different ways.
It can be registered using only the serial number, only the password or the two in combination. From now on all the work is done on the OLT’s configuration inter­face. Please refer to the manual of the OLT vendor to ensure proper registration of the ONU.
9.2 Checking the Firmware version
9.3 Upgrading the Firmware
Following the ITU-T G.988[4] the upgrade of the firmware version (also called software download) is only performed by the OLT. Please refer to the manual of the OLT vendor to ensure proper upgrade of the firmware.
For a smooth operation of the ONU, please check for firmware updates on a regular basis and keep the version up to date.
DATACOM
204.4288.00
DM984 product family CHAPTER 10. FIRST STEPS WITH IPSAN

10. First Steps with IPSAN

It is possible to connect to the configuration CLI (command line interface) through serial cables, telnet and SSH. Initially the IPSAN is accessible via the serial interface only. For security reasons it is recommended to use SSH for any configuration. The necessary steps to configure SSH are defined in the section
10.1 Initial Connection
The first connection is possible only through the serial interface of the IPSAN. For this purpose a terminal emulation program, such as Hyperterminal, TeraTerm, PuTTY or similar is needed. The emulation program needs to be configured like this:
Baudrate: 115200 Byterate: 8 Stopbits: 1 Paritybit: None
When accessing the CLI a prompt for username should be visible:
DM4650 login:
After that a prompt for the password is shown:
password:
The default values for these are:
Username: admin Password: admin
After login it is highly recommended to change the password of the admin user. The password can be changed when using the command passwd.
The following example shows the password changing procedure:
DATACOM
204.4288.00
DM984 product family CHAPTER 10. FIRST STEPS WITH IPSAN
DM4650#passwd Type Old Password password: Type New Password password: Confirm Password password:
Password changed sucessfully. DM4650#
For a guide on how to create more users besides the admin user please refer to the IPSAN’s User Manual.[1]
10.2 Working with the CLI
To achieve any configuration on the IPSAN it is necessary to go into the so called configuration menu by typing:
configure
Example:
DM4650#configure DM4650(config)#
The builtin help can be accessed by pressing ’?’ or issuing the command help. This is possible at any time when at the IPSAN’s prompt.
The IPSAN supports auto-completion. Based on the example above it is possible to just type conf and confirm the command with ENTER or complete the com­mand automatically by pressing TAB. This is possible with all commands when at the IPSAN’s prompt.
Example:
DM4650#conf DM4650(config)#
When a menu is active, more information about the menu is available by issuing the following command:
show this
Note:In some menus it isn’t possible to do that, e.g. the configuration menu. Example:
204.4288.00
DATACOM
DM984 product family CHAPTER 10. FIRST STEPS WITH IPSAN
DM4650(unit-gpon-7)#show this Unit: 7 Authentication method: serial-number Key exchange interval: 3600 DM4650(unit-gpon-7)#
To exit a menu this command is given:
exit
Example:
DM4650(config)#exit DM4650#
10.3 Saving configurations
There are two options for saving configurations to the persistent flash storage of the IPSAN. The first option is in combination with marking it as startup­configuration and the second option is without marking it as startup configu­ration. When a configuration is marked as startup-configuration it gets loaded upon the next startup of the IPSAN.
To save a configuration and mark it for the next startup the following command must be issued:
copy running-config startup-config <flash-position>
Description of the used parameters:
Name Format Description
<flash-position> Number (1-10) Position where the configuration is stored
Example:
DM4650#copy running-config startup-config 10 Saving running configuration in flash 10... DM4650#
copy running-config flash-config <flash-position>
Description of the used parameters:
DATACOM
204.4288.00
DM984 product family CHAPTER 10. FIRST STEPS WITH IPSAN
Name Format Description
<flash-position> Number (1-10) Position where the configuration is stored
Example:
DM4650#copy running-config flash-config 10 Saving running configuration in flash 10... DM4650#
10.4 Marking Configurations for Startup
To mark a configuration for loading upon the next startup the following command must be:
select startup-config <flash-position>
Description of the used parameters:
Name Format Description
<flash-position> Number (1-10) Position where the configuration is stored
Example:
DM4650#select startup-config 10 DM4650#
10.5 Rebooting the Equipment
To reboot the IPSAN the following command is issued:
reboot
Example:
DM4650#reboot Please save startup configuration. Are you sure you want to reboot the system? <y/N> y Connection closed by foreign host.
10.6 Setup of Management Access via Telnet
The IPSAN has a dedicated management Ethernet interface, which is used for configuration purposes.
DATACOM
204.4288.00
Loading...
+ 75 hidden pages