Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

path monitoring exhancements #202

Merged
merged 3 commits into from
Jul 31, 2020

Conversation

RoadRunnr
Copy link
Member

alternate version of #191

* Move set of active context from state to data. Keeping them in there
  was not the best idea. Matching on set changes is better done by
  just keeping the count in there.
* Convert active context set to map. This allos us to stroe the monitoring
  key and demonitor them properly.
* Rework to Restart Counter change logic. now a restart counter change
  changes the state immediatly and processes all further GTP requests
  (incl. the one that triggered the RC change) in the new state.
For an active path, the echo request interval is adjusted depending on
wether the path as active contexts (busy), no contexts (idle) or is
down.
For idle and down paths a maximum time to keep their state, monitor
them or try to reconntact them is introduced.

A path is considered active when we have initiated it (e.g. SGSN/SGW or
proxy use).
@coveralls
Copy link

coveralls commented Jul 31, 2020

Coverage Status

Coverage increased (+0.3%) to 79.066% when pulling ff71648 on feature/monitor_down_pgw_peer_path-alternate into b6ed415 on master.

Copy link
Contributor

@vijay-hirani vijay-hirani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gone through the changes, Look okay

@mgumz mgumz merged commit 6f63a3b into master Jul 31, 2020
@mgumz mgumz deleted the feature/monitor_down_pgw_peer_path-alternate branch July 31, 2020 14:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants