XPON Configuration Commands

855 views
Skip to first unread message

Balaji Purushothaman

unread,
Jan 20, 2018, 7:33:38 AM1/20/18
to VOLTHA Discuss
Greetings,

Could someone share the working XPON Configuration commands to setup datapath for Edgecore OLT/Broadcom ONU.

Thanks & Regards,
Balaji

Girish GC

unread,
Jan 22, 2018, 12:26:06 AM1/22/18
to Balaji Purushothaman, VOLTHA Discuss
Hi Balaji,

Please find the xPON commands to provision a Broadcom ONU on Edgecore OLT. The datapath is setup after the subscriber on Broadcom ONU is successfully authenticated. ONOS pushes the DHCP and Unicast flows once the subscriber is successfully authenticated.

(voltha) preprovision_olt -t asfvolt16_olt -H 192.168.140.71:50060
success (device id = 0001ddee729d51e3)
(voltha) enable
enabling 0001ddee729d51e3
waiting for device to be enabled...
success (logical device id = 0001000000000001)
(voltha) xpon
(voltha-xpon ) channel_group create -n "Manhattan" -d "Channel Group for Manhattan" -a up -p 100 -s 000000 -r raman_none
(voltha-xpon ) channel_partition create -n "WTC" -d "Channel Partition for World Trace Center in Manhattan" -a up -r 20 -o 0 -f false -m false -u serial_number -c "Manhattan"
(voltha-xpon ) channel_pair create -n "PON port" -d "Channel Pair for Freedom Tower in WTC" -a up -r down_10_up_10 -t channelpair -g "Manhattan" -p "WTC" -i 0 -o class_a
(voltha-xpon ) traffic_descriptor_profile create -n "TDP 1" -f 100000 -a 500000 -m 1000000 -p 1 -w 1 -e additional_bw_eligibility_indicator_none
(voltha-xpon ) channel_termination create -i 0001ddee729d51e3 -n "PON port" -d "Channel Termination for Freedom Tower" -a up -r "PON port" -c "AT&T WTC OLT"
(voltha-xpon ) vont_ani create -n "ATT Golden User" -d "ATT Golden User in Freedom Tower" -a up -p "WTC" -s "BRCM02106930" -r "PON port" -o 1
(voltha-xpon ) 
(voltha-xpon ) ont_ani create -n "ATT Golden User" -d "ATT Golden User in Freedom Tower" -a up -u true -m false
(voltha-xpon ) tcont create -n "TCont 1" -r "ATT Golden User" -t "TDP 1"
(voltha-xpon ) 
(voltha-xpon ) v_enet create -n "uni-1" -d "Ethernet port - 1" -a up -r "ATT Golden User"
(voltha-xpon ) gem_port create -n "Gemport 1" -r "uni-1" -c 2 -a true -t "TCont 1" 


Regards,
Girish

--
You received this message because you are subscribed to the Google Groups "VOLTHA Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to voltha-discuss+unsubscribe@opencord.org.
To post to this group, send email to voltha-...@opencord.org.
Visit this group at https://groups.google.com/a/opencord.org/group/voltha-discuss/.
To view this discussion on the web visit https://groups.google.com/a/opencord.org/d/msgid/voltha-discuss/CAAfR3dTjEHojtzGpaScW2fLCtK%2BbN8w4PXMbwTUE7cM2-Y4YNw%40mail.gmail.com.
For more options, visit https://groups.google.com/a/opencord.org/d/optout.

Balaji Purushothaman

unread,
Jan 23, 2018, 12:55:54 PM1/23/18
to VOLTHA Discuss


Girish,

Thank you very much, That really helps.

when you run this XPON configuration, Could you please capture and send me the output of commands listed below, 

From Voltha CLI:
Devices, Ports for OLT and ONT, Flows for OLT and ONT.
Logical Device and its Ports, Flows

From ONOS CLI:
Flows, Devices, netcfg 

Thanks & Regards,
Balaji

 

Girish GC

unread,
Jan 24, 2018, 12:24:07 AM1/24/18
to Balaji Purushothaman, VOLTHA Discuss
Hi Balaji,
Attached the device, ports, flows information from the voltha cli.
You may refer ONOS Apps documentation for ONOS apps related configuration. The configuration is dependent on your custom topology.
Please refer below links for ONOS app related config.



Regards,
Girish

--
You received this message because you are subscribed to the Google Groups "VOLTHA Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to voltha-discuss+unsubscribe@opencord.org.
To post to this group, send email to voltha-...@opencord.org.
Visit this group at https://groups.google.com/a/opencord.org/group/voltha-discuss/.
device_ports_flows.txt

Sriram Iyyappan Mamandoor Pandurangan

unread,
Sep 28, 2018, 12:52:27 PM9/28/18
to VOLTHA Discuss
Hi Girish, Balaji,

I have an EdgeCore OLT running with the OpenOLT adapter connected with a Broadcom ONU as per the below shared diagram.


I have followed this link https://guide.opencord.org/cord-5.0/profiles/rcord/voltha_install.html and provisioned the OLT & ONU via XPON configuration commands.

 

Downstream traffic is reaching ONU gpondef interface from OLT. But we are unable to see the traffic on ONU ethernet interfaces. Also, we are unable to push traffic in upstream from ONU to OLT.

 

Can anyone share the traffic tested configuration commands to program OLT & ONU using OpenOLT?

 

  +---------------------------------+

  |             ONOS 1.13.1         |

  |                                 |

  +---------------------------------+

                   |

                   |

  +---------------------------------+

  |             VOLTHA 1.4          |

  |                                 |

  |       +------------------+      |

  |       | OpenOLT adapter  |      |

  +-------+--------+---------+------+

                   |

  OpenOLT gRPC API |

                   |

+--------------------- ---------------+

|                  |                  |

|         +------------------+        |

|         | OpenOLT driver   |        |

|         +--------+---------+        |

|                  |                  |

| Broadcom BAL2.6  |                  |

|                  |                  |

|         +------------------+        |

|         | Maple/Qumran SDK |        |

|         +------------------+        |

|                                     |

|       Edgecore White box OLT        |

+-------------------------------------+

                   |

  +---------------------------------+

  |             BRCM ONU            |

  |                                 |

  +---------------------------------+



regards,
Sriram I

Shad Ansari

unread,
Sep 28, 2018, 1:22:25 PM9/28/18
to srirami...@gmail.com, VOLTHA Discuss
Hi Sriram,

xpon configuration is not required with OpenOLT. Let me summarize the steps:

1) Use OpenOLT agent (aka driver) or your own agent on the device

2) Start Voltha/ONOS as you would normally do. Load the proper netcfg for the OLT and ONUS (sadis).

3) Pre-provision the olt using "-t openolt" in voltha CLI and enable it:

4) do a add-subscriber in ONOS

You should have data connectivity at this point.


--
You received this message because you are subscribed to the Google Groups "VOLTHA Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to voltha-discus...@opencord.org.

To post to this group, send email to voltha-...@opencord.org.
Visit this group at https://groups.google.com/a/opencord.org/group/voltha-discuss/.

Sriram Iyyappan Mamandoor Pandurangan

unread,
Sep 29, 2018, 12:44:53 PM9/29/18
to VOLTHA Discuss, srirami...@gmail.com
Hi Shad,

Thanks for your email.

Tried out traffic verification without the XPON commands as suggested, the following is the observation

 

  1. Data is reaching PON interface on ONU from OLT on the downstream.
  2. Data is reaching Bridge interface on ONU from host on the upstream.
  3. In both cases, Data is not crossing from Bridge to PON interface on the ONU.

 

  1. Packets sent downstream towards the ONU via the OLT are reaching the ONU gpondef interface:

    • ONU gpondef interface counters (I am sending bursts of 1000 packets every second):

# ifconfig gpondef

gpondef   Link encap:Ethernet  HWaddr 64:6E:EA:E8:11:13

          inet6 addr: fe80::666e:eaff:fee8:1113/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:14679651 multicast:0 unicast:14679651 broadcast:0

          RX errors:0 dropped:0 overruns:0 frame:0

          TX packets:184 multicast:0 unicast:184 broadcast:0

          TX errors:0 dropped:0 overruns:0 carrier:0 collisions:0

          txqueuelen:1000

          RX bytes:1820262740 (1.6 GiB) TX bytes:9568 (9.3 KiB)

          RX multicast bytes:0 (0.0 B) TX multicast bytes:0 (0.0 B)

 

# ifconfig gpondef

gpondef   Link encap:Ethernet  HWaddr 64:6E:EA:E8:11:13

          inet6 addr: fe80::666e:eaff:fee8:1113/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:14680651 multicast:0 unicast:14680651 broadcast:0

          RX errors:0 dropped:0 overruns:0 frame:0

          TX packets:184 multicast:0 unicast:184 broadcast:0

          TX errors:0 dropped:0 overruns:0 carrier:0 collisions:0

          txqueuelen:1000

          RX bytes:1820386740 (1.6 GiB) TX bytes:9568 (9.3 KiB)

          RX multicast bytes:0 (0.0 B) TX multicast bytes:0 (0.0 B)

  • ONU eth0 and eth0.0 do not get the 1000 packets:

# ifconfig eth0

eth0      Link encap:Ethernet  HWaddr 64:6E:EA:E8:11:10

          inet6 addr: fe80::666e:eaff:fee8:1110/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:31722 multicast:3576 unicast:28140 broadcast:6

          RX errors:0 dropped:0 overruns:0 frame:0

          TX packets:29606 multicast:1898 unicast:27690 broadcast:18

          TX errors:0 dropped:0 overruns:0 carrier:0 collisions:0

          txqueuelen:1000

          RX bytes:2851580 (2.7 MiB) TX bytes:11195509 (10.6 MiB)

          RX multicast bytes:0 (0.0 B) TX multicast bytes:0 (0.0 B)

 

# ifconfig eth0

eth0      Link encap:Ethernet  HWaddr 64:6E:EA:E8:11:10

          inet6 addr: fe80::666e:eaff:fee8:1110/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:31729 multicast:3576 unicast:28147 broadcast:6

          RX errors:0 dropped:0 overruns:0 frame:0

          TX packets:29611 multicast:1898 unicast:27695 broadcast:18

          TX errors:0 dropped:0 overruns:0 carrier:0 collisions:0

          txqueuelen:1000

          RX bytes:2852075 (2.7 MiB) TX bytes:11196489 (10.6 MiB)

          RX multicast bytes:0 (0.0 B) TX multicast bytes:0 (0.0 B)

 

# ifconfig eth0.0

eth0.0    Link encap:Ethernet  HWaddr 64:6E:EA:E8:11:10

          inet6 addr: fe80::666e:eaff:fee8:1110/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:31756 multicast:3577 unicast:28173 broadcast:6

          RX errors:0 dropped:2847 overruns:0 frame:0

          TX packets:29617 multicast:0 unicast:29617 broadcast:0

          TX errors:0 dropped:0 overruns:0 carrier:0 collisions:0

          txqueuelen:0

          RX bytes:2282762 (2.1 MiB) TX bytes:11070965 (10.5 MiB)

          RX multicast bytes:201042 (196.3 KiB) TX multicast bytes:0 (0.0 B)

 

# ifconfig eth0.0

eth0.0    Link encap:Ethernet  HWaddr 64:6E:EA:E8:11:10

          inet6 addr: fe80::666e:eaff:fee8:1110/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:31763 multicast:3577 unicast:28180 broadcast:6

          RX errors:0 dropped:2847 overruns:0 frame:0

          TX packets:29622 multicast:0 unicast:29622 broadcast:0

          TX errors:0 dropped:0 overruns:0 carrier:0 collisions:0

          txqueuelen:0

          RX bytes:2283131 (2.1 MiB) TX bytes:11071932 (10.5 MiB)

          RX multicast bytes:201042 (196.3 KiB) TX multicast bytes:0 (0.0 B)

 

 

  1. Packets sent Upstream from host connected on LAN1 of the ONU:
    1. I am starting wpa_supplicant on host connected to ONU (on eth4):

[root@localhost ~]# wpa_supplicant -Dwired -ieth4 -c/root/wpa_supplicant.conf

Associated with 01:80:c2:00:00:03

 

    1. I am able to get EAPOL packets till “eth0.0” interface on the ONU.

# tcpdump -i eth0.0 -vv | grep -i "EAP"

tcpdump: listening on eth0.0, link-type EN10MB (Ethernet), capture size 262144 bytes

22:45:28.173172 EAPOL start (1) v1, len 0

22:45:58.200407 EAPOL start (1) v1, len 0

 

    1. But I can see no packets going out from the “gpondef” port on the ONU itself:

# tcpdump -i gpondef -vv | grep -i "EAP"

tcpdump: listening on gpondef, link-type EN10MB (Ethernet), capture size 262144 bytes

 

On the ONU I have the following:

 

# pspctl dump WanRate

1010

# pspctl dump RdpWanType

XGS

# pspctl dump IpClassMethod

NONE

# cat /sys/class/net/bronu513/bridge/group_fwd_mask

0x8

# exit

> wan show

VCC     Service         Interface       Proto.  IGMP    Src?    MLD     Src?    IPv4Status      IPv4            IPv6Status      IPv6

        Name            Name                                                                    address                         address

N/A     br_veip0        veip0.1         Bridged Disable Disable Disable Disable Unconfigured    Unconfigured

> 

 

Tried some gemport commands:

# gponif -n 1024

# gponif -n 1024

gem id: 1024, if name:

# gponif -c

ioctl command return error!

# gpon -s gpon0

sh: gpon: not found

# gpon -s veip0/veip0

sh: gpon: not found

# gponif -s veip0/veip0

i/f name: veip0/veip0

gem ids:

# gponif -a veip0/veip0 -g 1024

The gem id 1024 is not valid#

# gponif -a veip0/veip0 -g 1023

The gem id 1023 is not valid#

#

# gponif -a veip0/veip0 -g 1

# gpon -s veip0/veip0

sh: gpon: not found

# gponif -s veip0/veip0

i/f name: veip0/veip0

gem ids:

# gponif -a veip0/veip0 -g 2

# gponif -n 1024

gem id: 1024, if name:

# gponif -n 1

gem id: 1, if name:

# gponif -a veip0/veip0 -g 1 2 1024

The gem id 1024 is not valid#

#

 

regards,
Sriram I
pon-sep29.zip

GS Ying

unread,
Oct 1, 2018, 7:58:00 PM10/1/18
to srirami...@gmail.com, voltha-discuss
I assume that the ONU is setup as the bridge, not as a home gateway, correct?

Shawn


Sriram Iyyappan Mamandoor Pandurangan

unread,
Oct 2, 2018, 2:53:29 AM10/2/18
to VOLTHA Discuss, srirami...@gmail.com
Hi Shawn,

Yes the ONU is setup as the bridge.

regards,
Sriram I

Shaun Missett

unread,
Oct 2, 2018, 12:04:23 PM10/2/18
to srirami...@gmail.com, VOLTHA Discuss
Also assume the UNI Port used matches the OMCI ME provisioning -  the 10G port?

Shaun Missett

unread,
Oct 2, 2018, 1:04:00 PM10/2/18
to Sriram Iyyappan Mamandoor Pandurangan, VOLTHA Discuss
I have not used that device - I dont think the ONU adapter will support it.

On Tue, Oct 2, 2018 at 1:01 PM Sriram Iyyappan Mamandoor Pandurangan <srirami...@gmail.com> wrote:
Hi Shaun,

As recommended in the link https://guide.opencord.org/prereqs/hardware.html, we are using Iskratel Innbox G108.

regards,
Sriram I

On Tue, Oct 2, 2018 at 10:20 PM Shaun Missett <shaunm...@gmail.com> wrote:
What ONU are you using?

On Tue, Oct 2, 2018 at 12:20 PM Sriram Iyyappan Mamandoor Pandurangan <srirami...@gmail.com> wrote:
Hi Shaun,

How to check this? Do you have any commands to check? I can share the output.

Or please share the complete configuration procedure. I will try and share the results. Below is the actual connectivity diagram.

  +---------------------------------+

  |             ONOS 1.13.1         |

  |                                 |

  +---------------------------------+

                   |

                   |

  +---------------------------------+

  |             VOLTHA 1.4          |

  |                                 |

  |       +------------------+      |

  |       | OpenOLT adapter  |      |

  +-------+--------+---------+------+

                   |

  OpenOLT gRPC API |

                   |

+--------------------- ---------------+

|                  |                  |

|         +------------------+        |

|         | OpenOLT driver   |        |

|         +--------+---------+        |

|                  |                  |

| Broadcom BAL2.6  |                  |

|                  |                  |

|         +------------------+        |

|         | Maple/Qumran SDK |        |

|         +------------------+        |

|                                     |

|       Edgecore White box OLT        |

+-------------------------------------+

                   |

  +---------------------------------+

  |             BRCM ONU            |

  |                                 |

  +---------------------------------+


regards,
Sriram I

Shaun Missett

unread,
Oct 2, 2018, 1:05:49 PM10/2/18
to Sriram Iyyappan Mamandoor Pandurangan, VOLTHA Discuss
Brcm should work as long as the UNI is the one configured by the OMCI - last I looked it is the 10G uni port.

On Tue, Oct 2, 2018 at 1:03 PM Sriram Iyyappan Mamandoor Pandurangan <srirami...@gmail.com> wrote:
Hi Shaun,

Yes. Its BRCM ONU. Let me check and get back to you.

regards,
Sriram I

On Tue, Oct 2, 2018 at 10:31 PM Shaun Missett <shaunm...@gmail.com> wrote:
Ok - looking back  in thread I see u r using the BRCM ONU - it used to be that the default UNI was the 10G port - u should connect to that uni and try it.
Shaun

On Tue, Oct 2, 2018 at 12:50 PM Shaun Missett <shaunm...@gmail.com> wrote:
What ONU are you using?

On Tue, Oct 2, 2018 at 12:20 PM Sriram Iyyappan Mamandoor Pandurangan <srirami...@gmail.com> wrote:
Hi Shaun,

How to check this? Do you have any commands to check? I can share the output.

Or please share the complete configuration procedure. I will try and share the results. Below is the actual connectivity diagram.

  +---------------------------------+

  |             ONOS 1.13.1         |

  |                                 |

  +---------------------------------+

                   |

                   |

  +---------------------------------+

  |             VOLTHA 1.4          |

  |                                 |

  |       +------------------+      |

  |       | OpenOLT adapter  |      |

  +-------+--------+---------+------+

                   |

  OpenOLT gRPC API |

                   |

+--------------------- ---------------+

|                  |                  |

|         +------------------+        |

|         | OpenOLT driver   |        |

|         +--------+---------+        |

|                  |                  |

| Broadcom BAL2.6  |                  |

|                  |                  |

|         +------------------+        |

|         | Maple/Qumran SDK |        |

|         +------------------+        |

|                                     |

|       Edgecore White box OLT        |

+-------------------------------------+

                   |

  +---------------------------------+

  |             BRCM ONU            |

  |                                 |

  +---------------------------------+


regards,
Sriram I
On Tue, Oct 2, 2018 at 9:34 PM Shaun Missett <shaunm...@gmail.com> wrote:

Matt Jeanneret

unread,
Oct 2, 2018, 1:57:50 PM10/2/18
to Shaun Missett, Sriram Iyyappan Mamandoor Pandurangan, VOLTHA Discuss
Current brcm openomci adapter (which does not exist in 1.4)  uses the first port (uni me) reported back via omci discovery.  On the alpha and broadcom dev onu thats lan port 1, which is gigabit only.  Im fairly sure its me id 257.

In 1.4 code the old adapter bridged all uni into the omci bridge and presented them as a single uni northbound 


-matt




Sriram Iyyappan Mamandoor Pandurangan

unread,
Oct 3, 2018, 3:23:41 AM10/3/18
to VOLTHA Discuss, shaunm...@gmail.com, srirami...@gmail.com
Hi Matt,

We pulled latest VOLTHA version and tried. Same issue is seen. Please let me know if you need any more logs. We will capture and share to you.

brcm_openomci_onu version is 0.5

(voltha) adapters
Adapters:
+-------------------+---------------------------+---------+
|                id |                    vendor | version |
+-------------------+---------------------------+---------+
|        adtran_olt |               Adtran Inc. |    0.19 |
|        adtran_onu |               Adtran Inc. |    0.13 |
|     asfvolt16_olt |                  Edgecore |    0.98 |
| brcm_openomci_onu |            Voltha project |    0.50 |
|      broadcom_onu |            Voltha project |    0.46 |
|          dpoe_onu |   Sumitomo Electric, Inc. |     0.1 |
|         maple_olt |            Voltha project |     0.4 |
|     microsemi_olt |     Microsemi / Celestica |     0.2 |
|           openolt |      OLT white box vendor |     0.1 |
|          pmcs_onu |                      PMCS |     0.1 |
+-------------------+---------------------------+---------+
|        ponsim_olt |            Voltha project |     0.4 |
|        ponsim_onu |            Voltha project |     0.4 |
|     simulated_olt |            Voltha project |     0.1 |
|     simulated_onu |            Voltha project |     0.1 |
|         tibit_olt | Tibit Communications Inc. |     0.1 |
|         tibit_onu | Tibit Communications Inc. |     0.1 |
|          tlgs_onu |                      TLGS |     0.1 |
+-------------------+---------------------------+---------+
(voltha) version
2.0.0-dev
(voltha)


regards,
Sriram I

Matt Jeanneret

unread,
Oct 3, 2018, 6:59:44 AM10/3/18
to Sriram Iyyappan Mamandoor Pandurangan, VOLTHA Discuss, Shaun Missett
Hi Siram,

Can you grab the output of the "devices" command from the voltha cli and also the voltha log?  I apologize i have not been following this thread closely up till now but i suspect this is a "all in one" combined gateway/onu that uses VEIP UNI rather than PPTP UNI.   Based on your output already:

br_veip0        veip0.1

All the ONU we have tested with use PPTP where each physical lan port is a discrete UNI.   With the VEIP kind of ONU the physical LAN ports on the device are not UNI.  There is a virtual UNI created between the regular ethernet ports and the omci bridge/gem port.

When running the devices command there is a reason column that shows the state of mib synchronization and discovery.   If there are any elements missing in the discovery the adapter does not push/download the omci to assign alloc id or build the omci bridge.   It should say "onu-missing-required-elements", which in this case means it did not find any PPTP.

I have a task to update the adapter to work with both types of UNI but haven't gotten around to it yet.    I recently received one of these types of ONU so ill try a few things and see if i can come up with something.


-matt



Sriram Iyyappan Mamandoor Pandurangan

unread,
Oct 4, 2018, 4:04:27 PM10/4/18
to VOLTHA Discuss, srirami...@gmail.com, shaunm...@gmail.com
Hi Matt,

Sorry. .We got stuck due to mismatch with openolt adapter and driver. Please find the requested logs.

I am able to get OLT and ONU to be discovered. ONU is not getting activated. Need your help to make ONU to activate.

(voltha) devices

Devices:

+------------------+-------------------+------+------------------+------------------+-------------+-------------+----------------+----------------+------------------+-------------------------------+--------------+-------------------------+--------------------------+----------------------+------------------------------+

|               id |              type | root |        parent_id |    serial_number | admin_state | oper_status | connect_status | parent_port_no |    host_and_port |                        reason |   extra_args | proxy_address.device_id | proxy_address.channel_id | proxy_address.onu_id | proxy_address.onu_session_id |

+------------------+-------------------+------+------------------+------------------+-------------+-------------+----------------+----------------+------------------+-------------------------------+--------------+-------------------------+--------------------------+----------------------+------------------------------+

| 000152aaf526aea5 |           openolt | True | 00010000c0a80002 | 192.168.0.2:9191 |     ENABLED |      ACTIVE |      REACHABLE |                | 192.168.0.2:9191 |                               | -o asfvolt16 |                         |                          |                      |                              |

| 00019aacf22c46d2 | brcm_openomci_onu | True | 000152aaf526aea5 |     ISKT71e81110 |     ENABLED |  DISCOVERED |      REACHABLE |      536870912 |                  | onu-missing-required-elements |              |        000152aaf526aea5 |                          |                    1 |                            1 |

| 0001d854c19dbeaa | brcm_openomci_onu | True | 000152aaf526aea5 |     ISKT71e81100 |     ENABLED |  DISCOVERED |      REACHABLE |      536870913 |                  | onu-missing-required-elements |              |        000152aaf526aea5 |                        1 |                    1 |                            1 |

+------------------+-------------------+------+------------------+------------------+-------------+-------------+----------------+----------------+------------------+-------------------------------+--------------+-------------------------+--------------------------+----------------------+------------------------------+

(voltha)

 

Voltha core Logs:

 

20181004T195333.646 INFO     MainThread brcm_openomci_onu_handler._mib_in_sync {device_id: 0001d854c19dbeaa, already_loaded: False, in_sync: True, event: loading-device-data-from-mib, instance_id: compose_voltha_1_1538680765, vcore_id: 0001}

20181004T195333.646 DEBUG    MainThread onu_device_entry.query_mib {device_id: 0001d854c19dbeaa, class_id: 11, instance_id: compose_voltha_1_1538680765, attributes: None, event: query, vcore_id: 0001}

type: "brcm_openomci_onu"

adapter: "brcm_openomci_onu"

  onu_id: 1

  onu_session_id: 1

reason: "onu-missing-required-elements"

type: "brcm_openomci_onu"

adapter: "brcm_openomci_onu"

  onu_id: 1

  onu_session_id: 1

reason: "onu-missing-required-elements"

20181004T195333.649 ERROR    MainThread brcm_openomci_onu_handler._mib_in_sync {device_id: 0001d854c19dbeaa, e: onu-missing-required-elements, event: device-info-load, exception: Traceback (most recent call last):

  File "/voltha/voltha/adapters/brcm_openomci_onu/brcm_openomci_onu_handler.py", line 735, in _mib_in_sync

    raise Exception("onu-missing-required-elements")

Exception: onu-missing-required-elements, instance_id: compose_voltha_1_1538680765, vcore_id: 0001}


At this Point, we can’t see UNI ports at ONOS. Earlier we had it visible.. but I suspect that the behavior earlier was assuming a PPTP type ONU and hence incorrect.

 

onos> devices

id=of:00000000c0a80002, available=true, local-status=connected 27m11s ago, role=MASTER, type=SWITCH, mfr=VOLTHA Project, hw=, sw=, serial=192.168.0.2:9191, chassis=c0a80002, driver=voltha, channelId=172.27.0.1:46656, managementAddress=172.27.0.1, protocol=OF_13

onos>

onos>

onos> ports

id=of:00000000c0a80002, available=true, local-status=connected 27m13s ago, role=MASTER, type=SWITCH, mfr=VOLTHA Project, hw=, sw=, serial=192.168.0.2:9191, chassis=c0a80002, driver=voltha, channelId=172.27.0.1:46656, managementAddress=172.27.0.1, protocol=OF_13

  port=65536, state=enabled, type=fiber, speed=0 , adminState=enabled, portMac=00:00:00:01:00:00, portName=nni-65536

onos>



regards,
Sriram I
5th-Oct-logs.zip

Matt Jeanneret

unread,
Oct 4, 2018, 5:20:15 PM10/4/18
to Sriram Iyyappan Mamandoor Pandurangan, VOLTHA Discuss, Shaun Missett

Thaer Alem

unread,
Apr 3, 2023, 8:03:48 AM4/3/23
to VOLTHA Discuss, Matt Jeanneret, VOLTHA Discuss, Shaun Missett, Sriram Iyyappan Mamandoor Pandurangan
Hi, Where i can get cheat sheet for OpenOLT Usages?
Reply all
Reply to author
Forward
0 new messages