NEP Updates & Upgrades¶
Breaking Change: Tenant Custom Variable Migration¶
Starting with the current NetEye and NEP upgrade path, the legacy NEP tenant
custom variable nx_neteye_tenant is deprecated and replaced with a new variable.
The supported tenant information is now stored in the host custom variable neteye_tenant.
Before upgrading NEP components, verify every host where nx_neteye_tenant is defined
and ensure that neteye_tenant exists and contains the correct tenant value.
Note that this variable applies to host objects only and has no meaning on service objects.
This is a breaking change: features that depend on tenant information may not work correctly
after the upgrade if required host objects still rely solely on nx_neteye_tenant,
or if neteye_tenant is missing or configured with an incorrect value.
After verifying that the new variable is working as expected in the upgraded environment,
you can remove the legacy nx_neteye_tenant variable from your host objects. This cleanup
is strongly recommended, though the upgrade will complete successfully even if the variable remains.
Warning
The deprecated variable cleanup operation is irreversible. While it is not strictly mandatory, it is strongly recommended once you have verified that everything operates correctly after the upgrade.
To remove the variable nx_neteye_tenant and wipe its contents follow the next steps:
Log into NetEye.
In the main menu, select Director.
Scroll down the list of tiles and, under the section “Do more with custom data”, click on Define Data Fields.
Search for
nx_neteye_tenantand click on it (refer to the Field Name column).
Click on the Delete button.
In the confirmation dialog, set Wipe related vars to
Yes, then click Delete again to confirm.If there are additional instances of the
nx_neteye_tenantfield, repeat steps 4–6 until all instances have been removed.