Bug #5092
Updated by daniel about 3 years ago
The SNS-CONFIG only contain the correct Endpoints as can be seen in VTY. However, all configured binds seem to be used when creating the mesh of NSVCs: <pre> OsmoGbProxy# show ns nsei 34 60 NSEI 00034: UDP, ALIVE FSM Instance Name: 'GPRS-NS2-SNS-SGSN(NSE00034-SNS)[0x5639244dc250]', ID: 'NSE00034-SNS' Log-Level: 'DEBUG', State: 'CONFIGURED' Timer: 4 Maximum number of remote NS-VCs: 8, IPv4 Endpoints: 1, IPv6 Endpoints: 0 Local IPv4 Endpoints: 192.168.0.180:1234, Signalling Weight: 1, Data Weight: 1 Remote IPv4 Endpoints: 192.168.0.240:1234, Signalling Weight: 100, Data Weight: 100 NSVCI none: RECOVERING DYNAMIC data_weight=100 sig_weight=100 udp)[192.168.0.180]:1231<>[192.168.0.240]:1234 NSVCI none: RECOVERING DYNAMIC data_weight=100 sig_weight=100 udp)[192.168.0.180]:1232<>[192.168.0.240]:1234 NSVCI none: RECOVERING DYNAMIC data_weight=100 sig_weight=100 udp)[192.168.0.180]:1233<>[192.168.0.240]:1234 NSVCI none: RECOVERING DYNAMIC data_weight=100 sig_weight=100 udp)[192.168.0.180]:1235<>[192.168.0.240]:1234 NSVCI none: RECOVERING DYNAMIC data_weight=100 sig_weight=100 udp)[192.168.0.180]:1236<>[192.168.0.240]:1234 NSVCI none: RECOVERING DYNAMIC data_weight=100 sig_weight=100 udp)[192.168.0.180]:1237<>[192.168.0.240]:1234 NSVCI none: RECOVERING DYNAMIC data_weight=100 sig_weight=100 udp)[192.168.0.180]:1238<>[192.168.0.240]:1234 NSVCI none: RECOVERING DYNAMIC data_weight=100 sig_weight=100 udp)[192.168.0.180]:1239<>[192.168.0.240]:1234 NSVCI none: UNBLOCKED DYNAMIC data_weight=100 sig_weight=100 udp)[192.168.0.180]:1234<>[192.168.0.240]:1234 </pre> The config looks roughly like this: <pre> ns bind udp foo-1231 listen 192.168.0.180 1231 ip-sns signalling-weight 1 data-weight 1 [...] nse 31 ip-sns-role-sgsn ip-sns-bind foo-1231 [...] </pre>
