A Forum reader recently asked:
“I having trouble with my BorderManager 3.6 SP2a server after an install of a new NetWare 6.5 SP6 server into the system. Sometimes on restart it will find all the Border Manager licenses, and sometimes it won’t. What could cause this?”
And here’s the response from Craig Johnson …
BorderManager will try to read a license from the master of the replica ring. If there is some NDS issue there, it could be slowing down the license read.
There are some things you should look at. First, you may be able to get all servers up to the same (22.214.171.124) version of eDirectory (at least if the servers are NW 5.1 or later). Check your patch level against tip #1 at this URL.
Next, you should definitely have a replica on the BorderManager server that holds the NBM licenses. It can be desirable to have the BorderManager in its own partition, and the master of its replica ring.
Next, you should realize there is always a delay involved when starting BorderManager and reading licenses. It is a good idea to allow for this by delaying the BMgr startup until licensing is fully initialized. This is most easily done by launching BMgr last in autoexec.ncf and putting a delay command in front of the launch file.
Finally, run SETUPNLS.NLM once on the BMgr server. That will recreate the server licensing object and could result in an update of an older version of the license, depending on the history of the server. It’s easy, and it does no harm if not needed.
Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment. It just worked for at least one person, and perhaps it will be useful for you too. Be sure to test in a non-production environment.