ONT activation and Troubleshooting based on service model

Content:+ ONT activation method with detail PLOAM message description follwed ITUT G988 standard+ OMCI Key components and detail explanation which detail describe in wireshark packets + GPON Service troubleshooting followed Viettel service model. So that find the issue come from GR part or OMCI part

ONT activation and Troubleshooting based

on service model

© 2017 DASAN Zhone Solutions – Proprietary and

1 ONT activation method

© 2017 DASAN Zhone Solutions – Proprietary and Confidential

GPON Element communication

OMCC-OMCI channel establishmnet

© 2017 DASAN Zhone Solutions – Proprietary and Confidential

© 2017 DASAN Zhone Solutions – Proprietary and Confidential

6

10.2.5.1 Downstream PLOAM Message

1 Upstream_Overhead Pre-assigned delay, the number of preamble bytes, ONU optical power

2 Assign_ONU-ID Link a free ONU-ID with the serial number

4 Deactivate_ONU-ID instruct to stop sending upstream traffic and reset itself

5 Disable_Serial_Number Disable / enable with this serial number

6 Encrypted_Port-ID Indicate to ONUs which channels are encrypted or not

7 Request_Password Request the password from an ONU in order to verify it

8 Assign_Alloc-ID Instruct an ONU that the specified allocation ID is assigned to it

9 No Message No message available when a PLOAM field is transmitted

10 POPUP POPUP state  Ranging State (O4) or Operation state (O5)

11 Request_Key Trigger ONU to generate a new encryption key and send it upstream

12 Configure_Port-ID Configure GEM Port for OMCI channel

13 Physical_Equipment_Error(PEE) Indicate to the ONUs that the OLT is unable to send both GEM frames and OMCC frames

14 Change_Power_Level The OLT triggers the ONU to either increase or decrease its transmitted power level

15 PST message To check the ONU-OLT connectivity in a survivable PON configuration, and to perform APS

16 BER Interval Accumulation interval per ONU for collecting bit errors

17 Key_Switching_Time The OLT indicates to the ONU when to begin using the new encryption key

18 Extended_Burst_Length Instruct the ONU the number of type 3 preamble bytes to use in the upstream direction

© 2017 DASAN Zhone Solutions – Proprietary and

The “activation process” is performed under the control of the OLT by means of exchange of upstream

and downstream PLOAM messages

© 2017 DASAN Zhone Solutions – Proprietary and

10.2.3 ONU state diagram

I.1.4.1 Old ONU bring-up

Once the ONU enters operation state O5 after activation, the OLT creates the OMCC as described in clause B.1 As described in clause I.1.3.1, the OLT then retrieves the ONU MIB data sync value by sending a get (ONU data (MIB data sync)) message to the ONU The OLT compares the received MIB data sync attribute value to the OLT's own MIB data sync value for that ONU The result of the comparison leads to three possible ONU bring-up scenarios:

 If the ONU's MIB data sync value matches the OLT's value, and is not zero, the OLT may assume that their MIBs are in alignment The ONU bring-up process is complete.

NOTE – The OLT ultimately makes the choice between trusting MIB sync match – which is not a guarantee – and resynchronizing the MIBs in detail The OLT also has the choice to reset the MIB and rebuild it from scratch or to audit and repair it incrementally

 If the ONU's MIB data sync value equals zero, possibly the result of an ONU software upgrade or because the ONU considers its MIB to be invalid, the OLT follows the bring-up sequence described for a new ONU

 If the ONU's MIB data sync value does not match the OLT's value, the OLT executes the MIB synchronization process, as described in clause I.1.3.2 Once the OLT has provisioned the ONU's MIB, it must align MIB data sync values The OLT completes the bring-up process by sending a set (ONU data (MIB data sync)) command

I.1.4.2 New ONU bring-up

© 2017 DASAN Zhone Solutions – Proprietary and Confidential

 OLT sets the ONU MIB to its default state by sending a MIB reset to the ONU The ONU re- initializes its MIB to the default and resets the MIB data sync attribute to zero.

 Next, the OLT uploads the ONU's MIB to retrieve all ME instances and capabilities The OLT then issues create, delete and set

commands to bring the ONU's MIB into sync with the OLT's MIB.

 When an ONU changes an attribute value autonomously, it sends an attribute value change message (AVC) to the OLT The ONU can send AVCs during the MIB

synchronization or MIB download processes AVCs should be viewed as a partial method of ONU state discovery Not all managed Rec ITU-T G.988 (10/2012) 521 entities or attributes issue AVCs, and an AVC message can

be lost in transmission without an error being detected Therefore, the OLT should audit the ONU state immediately after a reset has been completed

New ONU bring-up (Cont)

Apply traffic profile

© 2017 DASAN Zhone Solutions – Proprietary and

Apply traffic profile

2 OMCI Key Components

© 2017 DASAN Zhone Solutions – Proprietary and Confidential

1 Transaction correlation identifier

 Associate a request message with its response message

 The transaction identifier of event messages is 0x0000

 Most significant bit of TID indicates the priority

 Normally almost message’s priority is high

2 Message type

 DB always 0 (reserved)

 AR indicates whether or not the message requires an acknowledgment

 AK indicates whether or not this message is an acknowledgement to an action request

 MT indicate the message type (0 ~ 31): Table 11.2.2-1

‒ 4 : create

‒ 6 : delete

‒ 8 : set

© 2017 DASAN Zhone Solutions – Proprietary and

• First 2 bytes are set to 0x0000

• Next 2 bytes are 0x0028

• Last 4 bytes are 32-bit CRC

© 2017 DASAN Zhone Solutions – Proprietary and

© 2017 DASAN Zhone Solutions – Proprietary and

Management Entity

Relationships Attributes

Actions Notifications

© 2017 DASAN Zhone Solutions – Proprietary and

Relationships

© 2017 DASAN Zhone Solutions – Proprietary and

© 2017 DASAN Zhone Solutions – Proprietary and

© 2017 DASAN Zhone Solutions – Proprietary and

Layer2 functions

N:1 bridging, where a bridge is used to serve

multiple UNI ports from a single ANI service

© 2017 DASAN Zhone Solutions – Proprietary and

Layer2 functions

1:M mapping, where a mapper is used

to serve a single UNI with multiple

ANI connections, based on IEEE

802.1p priorities

© 2017 DASAN Zhone Solutions – Proprietary and

Layer2 functions

1:P filtering, where a bridge with filters

is used to serve a single UNI with

multiple ANI connections, based on

some VLAN information other than

IEEE 802.1p priorities

Futher more: N:M, 1:MP, N:P, N:MP

© 2017 DASAN Zhone Solutions – Proprietary and

ZTE OLT Traffic profile

© 2017 DASAN Zhone Solutions – Proprietary and

DASAN OLT Traffic profile

© 2017 DASAN Zhone Solutions – Proprietary and

ALU OLT Traffic profile

© 2017 DASAN Zhone Solutions – Proprietary and

HUAWEI OLT Traffic profile

© 2017 DASAN Zhone Solutions – Proprietary and

T-CONT

9.2.2 T-CONT

 A T-CONT can accommodate GEM packets in

priority queues or traffic schedulers that exist in

the GEM layer

 The ONU autonomously creates instances of this

ME The OLT can discover the number of

T-CONT instances via the ANI-G ME When the

ONU's MIB is reset or created for the first time,

all supported T-CONTs are created The OLT

provisions alloc-IDs to the ONU via the

PLOAM channel Via the OMCI, the OLT must

then set the alloc-ID attributes in the T-CONTs

that it wants to activate for user traffic, to create

the appropriate association with the allocation

ID in the PLOAM channel

 The allocation ID that matches the ONU-ID

itself is defined to be the default alloc-ID This

alloc-ID is used to carry the OMCC

 Alloc-ID: This attribute links the T-CONT with

the alloc-ID assigned by the OLT in the

assign_alloc-ID PLOAM message In [ITU-T

G.984.3], legal values range from 0 to 0x0FFF,

with some values having special meaning

© 2017 DASAN Zhone Solutions – Proprietary and

GEM port network CTP

9.2.3 GEM port network CTP

 This managed entity represents the termination of

a GEM port on an ONU

 Instances of the GEM port network CTP managed

entity are created and deleted by the OLT

 In ITU-T G.984 systems, when a GEM port

network CTP is created, its encryption state is by

default not encrypted If the OLT wishes to

configure the GEM port to use encryption, it must

send the appropriate PLOAM message This

applies equally to new CTPs and to CTPs that are

re-created after a MIB reset

 Relationships: An instance of the GEM port

network CTP managed entity may be associated

with an instance of the T-CONT and GEM

interworking termination point managed entities

 Direction: This attribute specifies whether the

GEM port is used for UNI-to-ANI (1),

ANI-to-UNI (2), or bidirectional (3) connection

© 2017 DASAN Zhone Solutions – Proprietary and

GEM interworking termination point

9.2.4 GEM interworking termination point

 An instance of this managed entity represents a

point in the ONU where the interworking of a bearer

service (usually Ethernet) to the GEM layer takes

place At this point, GEM packets are generated

from the bearer bit stream (e.g., Ethernet) or the

bearer bit stream is reconstructed from GEM

packets

 Interworking option: This attribute identifies the

type of non-GEM function that is being

interworked The options are:

© 2017 DASAN Zhone Solutions – Proprietary and

Multicast GEM interworking termination point

9.2.5 Multicast GEM interworking termination

point

 An instance of this managed entity represents a point in

a G-PON ONU where a multicast service interworks

with the GEM layer At this point, a multicast bit stream

is reconstructed from GEM packets

 The default multicast operation of the PON is where all

the multicast content streams are carried in one PON

layer connection (GEM port) This connection is then

specified in the first entry of the IPv4 or IPv6 multicast

address table, as the case may be

 The OLT uses the multicast GEM IW TP entity as the

means to discover the ONU's multicast capability This

entity is mandatory if multicast is supported by the

ONU If the OLT attempts to create this entity on an

ONU that does not support multicast, the create

command fails

 IPv4 multicast address table: This attribute maps IP

multicast addresses to PON layer addresses Each entry

contains:

GEM port-ID

Secondary key

IP multicast destination address range start

IP multicast destination address range stop

2 bytes

2 bytes

4 bytes

4 bytes

© 2017 DASAN Zhone Solutions – Proprietary and

MAC bridge port configuration data

9.3.4 MAC bridge port configuration data

 TP type: This attribute identifies the type of termination point

associated with this MAC bridge port Valid value are:

1 Physical path termination point Ethernet UNI

2 Interworking VCC termination point

3 IEEE 802.1p mapper service profile

4 IP host config data or IPv6 host config data

5 GEM interworking termination point

6 Multicast GEM interworking termination point

7 Physical path termination point xDSL UNI part 1

8 Physical path termination point VDSL UNI

9 Ethernet flow termination point

10 Reserved

11 Virtual Ethernet interface point

12 Physical path termination point MoCA UNI

 Bridge ID pointer: This attribute points to an instance of the MAC

bridge service profile

 Port num: This attribute is the bridge port number It must be unique

among all ports associated with a particular MAC bridge service profile

 TP pointer: This attribute points to the termination point associated

with this MAC bridge port The TP type attribute indicates the type of the termination point; this attribute contains its instance identifier

 Port priority: This attribute denotes the priority of the port for use in

(rapid) spanning tree algorithms

 Port path cost: This attribute specifies the contribution of the port to

the path cost towards the spanning tree root bridge The range is 1 65535

 Port spanning tree ind: The Boolean value true enables (R)STP

LAN topology change detection at this port The value false disables topology change detection

© 2017 DASAN Zhone Solutions – Proprietary and

VLAN tagging filter data

 VLAN filter list: This attribute is a list of provisioned

TCI values for the bridge port A TCI, comprising user priority, CFI and VID, is represented by 2 bytes This attribute supports up to 12 VLAN entries The first N are valid, where N is given by the number of entries attribute

 Forward operation: When a frame passes through the

MAC bridge port, it is processed according to the operation specified by this attribute, in accordance withTable 9.3.11-1 Figure 9.3.11-3 illustrates the treatment

of frames according to the provisioned action possibilities Tagged and untagged frames aretreated separately, but both in accordance with the figure While all forwarding operations are plausible, only actions 0x10 and 0x12 are necessary to construct a VLAN mapper and an 802.1p mapper, respectively

 h) Bidirectional positive filtering by TCI: Both

ingress and egress frames are filtered on investigation of the TCI fields If and only if the specified fields in the TCI of a candidate ingress frame match an entry in the VLAN filter list, the frame is admitted into the bridge

If, and only if the specified fields in the TCI of a candidate egress frame match an entry in the VLAN filter list, the frame is forwarded based on the destination MAC address, according to action (a)

© 2017 DASAN Zhone Solutions – Proprietary and

Extended VLAN tagging operation configuration data

extended-vlan-tagging-operation 35_HSI_H646 create downstream-mode enable

single-tagged-frame 1 filter inner vid 35 cos any tpid 0x8100 treat remove single

treat inner vid copy-inner cos copy-inner tpid copy-inner apply

 Association type: This attribute identifies the type of the

ME associated with this extended

VLAN tagging ME Values are assigned as follows:

0 MAC bridge port configuration data

1 IEEE 802.1p mapper service profile

2 Physical path termination point Ethernet UNI

3 IP host config data or IPv6 host config data

4 Physical path termination point xDSL UNI

5 GEM interworking termination point

6 Multicast GEM interworking termination point

7 Physical path termination point MoCA UNI

8 Reserved

9 Ethernet flow termination point

10 Virtual Ethernet interface point

11 MPLS pseudowire termination point

Downstream mode: Regardless of its association, the rules of the received

frame VLAN tagging operation table attribute pertain to upstream traffic The downstream mode attribute defines the tagging action to be applied to

downstream frames:

 0 The operation performed in the downstream direction is the inverse

of that performed in the upstream direction Which treatment and filter fields are used for downstream filtering and the handling of unmatched frames are left to the implementation of the ONU

 1 Regardless of the filter rules, no operation is performed in the downstream direction All downstream frames are forwarded unmodified

 2 Filter on VID and P-bit value On a match, perform the inverse operation

on both the VID and P-bit value If no match is found, forward the frame unmodified

 3 Filter on VID only On a match, perform the inverse VID operationonly; pass the P bits through If no match is found, forward the frameunmodified