Bug #5040
closedBlock all BSS-NSVC if no SGSNs are available
0%
Description
When the last SGSN becomes unavailable we should NS-BLOCK all BSS NSVCs.
At that point we can also free all BVCs/cells since the BSS needs to BVC-RESET after NS-UNBLOCK.
As soon as an SGSN is available again we need to unblock the BSS-NSVCs
Related issues
Updated by daniel almost 3 years ago
- Related to Bug #4897: gbproxy2: Re-introduce handling of NS_AFF_CAUSE_FAILURE added
Updated by daniel almost 3 years ago
UN/BLOCK is not used for IP Subnetworks so what should we do there? Changeweight to 0 for data (and signalling)?
That doesn't seem to work as 6.2.8.1 of 40.016 states:
"""
Upon receiving an SNS-CHANGEWEIGHT PDU, if the resulting sum of the signalling weights of all the peer IP endpoints configured for this NSE is equal to zero or if the resulting sum of the data weights of all the peer IP endpoints configured for this NSE is equal to zero, the BSS/SGSN shall send an SNS-ACK PDU with a cause code of "Invalid weights". The whole content of that SNS-CHANGEWEIGHT PDU shall be ignored.
"""
Maybe using SNS-DEL would work? It seems the SGSN-side is also not allowed to initiate the size procedure.
The idea in #4897 was to BVC-block the PTP-BVCs towards the BSS if no SGSN is available, but the un/block procedures on BSSGP can only be initiated by the BSS, not by the SGSN.
Updated by daniel almost 3 years ago
- Status changed from New to Rejected
I think it doesn't make sense to do anything on the NS-layer. Instead we could (periodically) send a BVC-RESET for BVCI0 towards the BSS (and additionally prevent the PtP-BVCs from coming up).
I'll use #4897 for that as that issue is about BVC handling.