systemd,manual: set LimitNOFILE=65536

A typical OS imposed limit is 1024 open FD, which is too low when there
are thousands of HNB.

In systemd service file, set a super high limit of 65536.

In osmo-hnbgw's user manual, add section 'Configure limits' describing
this in detail.

Related: OS#6256
Related: osmo-bsc I26c4058484b11ff1d035a919bf88824c3af14e71
Change-Id: I5333765199cf9e3e5a570f85b85d2b7423d34a4d
This commit is contained in:
Neels Hofmeyr 2023-11-30 18:13:06 +01:00 committed by laforge
parent fadc67b8fb
commit 90928fb246
2 changed files with 18 additions and 0 deletions

View File

@ -6,6 +6,7 @@
ExecStart=/usr/bin/osmo-hnbgw -c /etc/osmocom/osmo-hnbgw.cfg

View File

@ -76,6 +76,23 @@ To run multiple OsmoHNBGW instances on the same SCCP routing, each HNBGW has to
configure a distinct point-code, see <<configure_iucs_iups>>.
=== Configure limits
When connecting hundreds of HNB to OsmoHNBGW, it may be necessary to adjust the
operating system's limit on open file descriptors for the osmo-hnbgw process. A
typical default limit imposed by operating systems is 1024; this would be
exceeded by, for example, about 1024 HNB on Iuh, sockets for other interfaces
not considered yet.
It should be ok to set an OS limit on open file descriptors as high as 65536
for osmo-hnbgw, which practically rules out failure from running out of file
descriptors anywhere (<50,000 HNB).
When using systemd, the file descriptor limit may be adjusted in the service
file by the `LimitNOFILE` setting ("Number of Open FILE descriptors").
OsmoHNBGW ships a systemd service file with a high LimitNOFILE setting.
=== Configuring Primary Links