In article <4ACB1624.8081.000C.1@almaschools.net>, Scott Owen wrote:
> Reading the manual....it looks like the upgrade from 3.8.5 to BM 3.9sp2 is a very straight forward
procedure.
It can be... With BorderManager, there are a lot of dependencies, and as a minimum you want to be
sure the network (tree) is healthy. Time in sync, no stuck obits in NDS, SLP working properly, servers
up, LDAP working, iManager actually working, etc.
When things go well, it's actually quite a quick and easy upgrade, though you do then have to deal with
iManager.
>
> Then.....I look at the forums....and see references to other fun stuff with minimum requirement
failures, FILLATTR, .....
There are two 'common' issues. One is the eDir 8.8.x problem, where the installation routine thinks
you aren't running a supported eDir version, since it expected 8.7.3.x. There is a TID on manually
modifying the products.dat entry to change 8.8.x to 8.7.3.9 for the install, and then changing it back.
The other is a relatively frequent problem where part of the upgrade doesn't work and tells you to use
fillattr afterwards. I think this is due to an LDAP failure, and it may be as simple as expecting
cleartext when encrypted is used, or vice-versa. The fillattr routine is a java process that converts
old proxy and access rule settings to XML format in eDir, using LDAP. It's a bit of a pain because of
the syntax you have to use, and because of cleartext/non-cleartext issues. I have an example of what
to do in my BMgr 3.x book.
>
> Is there a "how to" or a pre-upgrade checklist somewhere?
My book has a number of things to look for, but in general you want the network to be stable, updated
and healthy before you start.
> Is the issue with 9 SSL Authentication contexts fixed in 3.9sp2?
Yes.
> Should I be good to go with the 3.9 sp2 overlay install? (NBM39SP2.zip)
Yes.
>
Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to
http://www.craigjconsulting.com ***