neels has uploaded this change for review.

View Change

improve error log for unknown netinst

When a Network Instance name is not known, hint in the error log that an
entry needs to be added to the 'netinst' section of the cfg.

Related: SYS#6192
Change-Id: Ifdc0e7ec0d7b62b0127a5daa76cf48a932fcaf72
---
M src/osmo-upf/up_session.c
1 file changed, 4 insertions(+), 2 deletions(-)

git pull ssh://gerrit.osmocom.org:29418/osmo-upf refs/changes/62/30462/1

diff --git a/src/osmo-upf/up_session.c b/src/osmo-upf/up_session.c
index e17b319..90bb49a 100644
--- a/src/osmo-upf/up_session.c
+++ b/src/osmo-upf/up_session.c
@@ -156,8 +156,10 @@
 	} else {
 		netinst = netinst_find(&g_upf->netinst, netinst_name);
 		if (!netinst) {
-			LOGPFSML(session->fi, LOGL_ERROR, "Network Instance from PFCP request not found: %s\n",
-				 osmo_quote_str_c(OTC_SELECT, netinst_name, -1));
+			LOGPFSML(session->fi, LOGL_ERROR, "Network Instance from PFCP request not found: %s"
+				 " -- ensure there is a 'netinst' / 'add %s <ip-addr>' entry in your config\n",
+				 osmo_quote_str_c(OTC_SELECT, netinst_name, -1),
+				 osmo_escape_str_c(OTC_SELECT, netinst_name, -1));
 			return OSMO_PFCP_CAUSE_RULE_CREATION_MOD_FAILURE;
 		}
 	}

To view, visit change 30462. To unsubscribe, or for help writing mail filters, visit settings.