Actions
Bug #6007
opennetwork -> bts -> gprs nsvc will always create a nsvc node
Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
04/17/2023
Due date:
% Done:
0%
Spec Reference:
Description
When starting with a minimal configuration of the gprs nsvc 1, the osmo-bsc
will generate new configuration for NSVC1.
e.g. initial configuration is
network bts 1 [...] gprs nsvc 0 nsvci 2 gprs nsvc 0 local udp port 23000 gprs nsvc 0 remote ip 192.168.56.1 gprs nsvc 0 remote udp port 23000 # no gprs nsvc 1
The bsc will create such nodes on `show running-config` or when doing a `write`
gprs nsvc 0 nsvci 2 gprs nsvc 0 local udp port 23000 gprs nsvc 0 remote ip 192.168.56.1 gprs nsvc 0 remote udp port 23000 gprs nsvc 1 nsvci 0 gprs nsvc 1 local udp port 0
Please ensure that an non-existent configuration won't generate such elements.
The correct behaviour would be
gprs nsvc 0 nsvci 2 gprs nsvc 0 local udp port 23000 gprs nsvc 0 remote ip 192.168.56.1 gprs nsvc 0 remote udp port 23000
without any node describing nsvc 1.
No data to display
Actions