[VOL-2122] Develop debugging mechanism when running openolt as a service - OpenCORD JIRA

XML

Word

Printable

Details

Type: Story
Status: Resolved (View Workflow)
Priority: Medium
Resolution: Done
Affects Version/s: None
Fix Version/s: VOLTHA v2.2
Component/s: bal, openolt-agent
Labels:
None

Story Points:
8
Epic Link:
[Brigade: BAL v3.x migration]

Description

In BAL 2.6, you had to run openolt and bal_core_dist in the forground to have access to the bal cli and be able to check flows, portstats etc.

Not sure if this is still the case with BAL 3.1, and dev_mgmt_daemon. If so, then we need a mechanism to fetch this kind of info while still running openolt as a service

Attachments

Options

Sub-Tasks

1.	Create a BAL application for providing CLI access to BAL	Resolved	Girish Gowdra
2.	Provide a mechanism to dump all BAL objects that were implicitely or explicetly created.	Resolved	Girish Gowdra
3.	Provide a mechanism to dump packet counters on the following BAL objects	Resolved	Girish Gowdra
4.	Provide a mechanism to enable/disable logs of BAL subsystems at run time	Resolved	Girish Gowdra
5.	Provide a mechanism to replay the last N BAL configurations in sequence	Resolved	Unassigned
6.	Provide a mechanism to dump L2 control packets on the PON or NNI interface on the shell	Resolved	Unassigned
7.	Provide a mechanism for packet mirroring from NNI/PON interfaces	Resolved	Unassigned

Options
- Show All Reviews
- Show Open Reviews
- Show All Issues
- Show Open Issues

Gerrit Reviews

No reviews matched the request. Check your Options in the drop-down menu of this sections header.

Activity

People

Assignee:: Girish Gowdra

Reporter:: Saurav Das

Watchers:: 3 Start watching this issue

Dates

Created:: 2019/10/21 6:16 PM

Updated:: 2019/12/12 10:50 AM

Resolved:: 2019/11/28 2:31 AM

Gerrit Reviews

There are no open Gerrit changes