https://osmocom.org/https://osmocom.org/favicon.ico?16647414092020-11-16T18:14:53ZOpen Source Mobile Communicationsosmo-gbproxy - Feature #4521: gbproxy: Redundancy between NS-VCs (SGSN Side)https://osmocom.org/issues/4521?journal_id=203452020-11-16T18:14:53Zlaforge
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>Assignee</strong> set to <i>laforge</i></li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li></ul> osmo-gbproxy - Feature #4521: gbproxy: Redundancy between NS-VCs (SGSN Side)https://osmocom.org/issues/4521?journal_id=208562021-01-18T18:52:06Zlaforge
<ul><li><strong>% Done</strong> changed from <i>0</i> to <i>50</i></li></ul><p>IP-SNS allows us to establish NS-VCs to multiple IP endpoints of each SGSN. In theory there is redundancy between those NS-VCs. We just need to test that this actually works.</p>
<p>Also, there are of course link-layer redundancy mechanisms on L2 or L3 such as STP, VRRP, OSPF, RIP, etc. that can be used to facilitate redundancy on the transport level between gbproxy and SGSN.</p>
<p>We'll lleave this ticket to extend our automatic tests to cover situations where some NSVCs are dying and traffic shall continue over other NS-VCs.</p> osmo-gbproxy - Feature #4521: gbproxy: Redundancy between NS-VCs (SGSN Side)https://osmocom.org/issues/4521?journal_id=208582021-01-18T18:53:24Zlaforge
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>New</i></li><li><strong>Priority</strong> changed from <i>High</i> to <i>Normal</i></li></ul> osmo-gbproxy - Feature #4521: gbproxy: Redundancy between NS-VCs (SGSN Side)https://osmocom.org/issues/4521?journal_id=208712021-01-19T17:24:53Zlaforge
<ul></ul><p><a class="external" href="https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/22315">https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/22315</a> introduces the capability to temporarily disable and re-enable NSVSs in TTCN3.</p> osmo-gbproxy - Feature #4521: gbproxy: Redundancy between NS-VCs (SGSN Side)https://osmocom.org/issues/4521?journal_id=208762021-01-19T17:45:33Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-3 priority-3 priority-high3 closed" href="/issues/4959">Bug #4959</a>: Problems on NS-VC recovery</i> added</li></ul>