Overview

When using a Layer 4 Classification, i.e., TCP or UDP, there are various internal classifications that ensure that the engine classifies correctly. The module for the Layer 4 Classification is a separate module from other classifications. Ocassionally, this module can fail to load and the following error message will be generated in main logs:

Oct 2 16:28:27 LR-Exinda mgmtd[3659]: [mgmtd.ERR]: apply_setapp(), md_monitor.c:736, build 1: Error code 1 returned
Oct 2 16:28:27 LR-Exinda mgmtd[3659]: [mgmtd.ERR]: md_monitor_commit_apply(), md_monitor.c:2482, build 1: Error code 1 returned
Oct 2 16:28:27 LR-Exinda mgmtd[3659]: [mgmtd.ERR]: Error 1 (ERROR-NO-MAP) returned from apply function for module: monitor_module

The internal file /proc/net/exinda/set_app will be empty.

Root Cause

The Layer 4 Classification depends on a module called set_app, and it handles all the port-based application definitions. If a custom application has been created based on a network-object that is subsequently deleted or renamed, this module fails to load, resulting in no Layer 4 Classification.

Resolution

Identify the failing application with the deleted or renamed network-object, and either re-select the correct network-object or delete the application. The set_app module will re-populate, and Layer 4 Classification will work.