A Forum reader recently asked:
"We've had the following problem since upgrading BorderManager 3.8.4 to BorderManager 3.8 SP5. Since the update was installed, we lost some of our filters (from looking in filtcfg). Is this a known issue after updating to BorderManager 3.8 SP5, or what could be the problem?"
And here's the response from Craig Johnson ...
It's not, though it can be a known problem when upgrading from NetWare 6.0 to 6.5.
Your filters are stored in the NBMRuleContainer in NDS - usually in the same OU as the server. If something goes wrong there (NDS), you get filtering problems. Filtering problems are generally associated with seeing -6001 errors in the logger screen when trying to edit certain exceptions.
In general, you can delete the contents of the NBMRuleContainer and remigrate the filters from a (good) copy of filters.cfg, using a filtsrv migrate procedure. You want to be sure you copy in a good copy of filters.cfg just before doing the migrate. (For more on the whole issue, in either my BorderManager 3.x book or my BorderManager filtering book, see the URL below).
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.