Abend during BorderManager 3.8 Installation While creating filters

I just tried configuring the filters using brdcfg.nlm, and it STILL abended. It seems something is corrupt, but what?

Looks like I got it. I applied the latest BorderManager support pack & ran bdrcfg.nlm. It put all the filters in place.

Since you solved it yourself, don't forget to post a (free) Question in the Community Support TA (https://www.experts-exchange.com/Community_Support/) and request that this Question be PAQed and the points refunded. Be sure to include a link to this Question.

In order to help people searching the EE database, I would suggest posting the exact ABEND message here.

And one bit of advice - there is a Post-SP2 eDirectory patch that is critically important if this server hosts an NDS replica. It is available from --> http://support.novell.com/cgi-bin/search/searchtid.cgi?/2968987.htm

Well, I'm ALMOST there...

When BorderManager attempts to load AUTHGW.NLM the followiong message appears on the logger screen:
"Loader cannot find public symbol: VPN_ACLCheck for module AUTHGW.NLM. Error processing External Records. Module AUTHGW.NLM NOT loaded."

Novell TID number 10092411 describes the problem. The TID states that a search path is missing. However, the one referenced is already there. It may be a missing search path, but where?

Novell TID 10092411
----------------------------------
NW51SP6
Novell BorderManager 3.8
VPN Client to Site
 
 symptom
Error: "VPN authentication gateway not found"
Error: "Failed to connect to authentication gateway."
AUTHGW.NLM is not loaded

When stopping VPN and BorderManager and the attempting to load AUTHGW.NLM the following error occured: "Loader cannot find public symbol: VPN_ACLCheck for module AUTHGW.NLM. Error processing External Records. Module AUTHGW.NLM NOT loaded."
 
  cause
  A JAVA search driver was missing
 
  fix
 Add the following search drive: sys:\java\njclv2\bin
 

In your AUTOEXEC.NCF - near the top. Put that SEARCH drive in - the syntax would be

SEARCH ADD SYS:JAVA\NJCLV2\BIN

Yes, as I mentioned in my posting, that search is already there. The TID I referenced describes the problem perfectly, but the solution is not that particular search. I am wondering if there is some other search that must be added (as in where does the search need to point to, not where does it go in the autoexec.ncf).

I've verified the search statement several times, and verified that it was active.  I do not see an overlay for BM like there is for NW (I wish there was!).

Anyhoo.... I am suspecting that there are some installation issues at work. I was finally able to get authgw to load this morning, but only by manually loading other nlms which should be loading automatically (vptunnel, ike, etc.). I am going to remove BM, remove the BMsp2, and remove the filters, reboot, and try reinstalling (again). Prior to reinstalling I'll also go and remove the config in iManager for the vpn server and c2s vpn.

I'll update here after all that.

Sounds like a plan. I look forward to hearing your progress.

rule number one when installing any Novell product on a NetWare 6.5 server:  MAKE SURE YOU HAVE ALL NECCESSARY PATCHES FOR IT THAT MAY BE REQUIRED TO ENSURE COMPATIBILITY WITH NETWARE 6.5!

sometimes, one has to shout ;)

<PLUGGING MY EARS FROM THE NOISE>
I'm not sure why that was necessary, since I certainly DID have all patches! We aren't talking about a compatibility issue here... we are talking about an installation that didn't complete properly in the first place.

I was refering to the original abend issue.

You should apply the latest IP patch for NetWare 6.5, and make sure you take the DOMESTIC stack, and not the NULL stack.  The NULL stack will not work with BorderManager VPN.

Always do this whenever you apply a service pack and you should avoid future problems with having the wrong IP stack.

Which is exactly what I did!

We can close out this question now anyway. I think I'm going to open a Novell incident on Monday. This is down to the wire.

If I need to, I'll start a new thread with the current issues.

It has been my experience with installing BorderManager, that you need to use the NetWare base install as a starting point, install the BorderManager base install, then apply the NetWare SP/patches, and then the BorderManager SP/patches.  Did you start with a NetWare SP2 overlay?

Also, does this server have any eDirectory replicas on it?  For proper VPN function, I have found that you should have replicas of ROOT and the authentication context partition.

Yes, to all of those. That is exactly what I did.

What I mean is, you should start with a base 6.5 install, not an overlay...  apply the 6.5 SP2 after the BM install.

Ok, this problem is solved. I ended up working with Novell Support, which then bumped it over to the BorderManager developers in India!  The core issue was that when BorderManager was installing (even with a fresh installation on a fresh server), the installation was putting the scmservice object in the wrong container! It needed to be placed in the server container. Per Novell, this should happen automatically. In fact, there is not even a way to create the object manually.

Novell was not able to determine WHY this happened, but they were able to MOVE the object to the correct container, reassign rights, and get it to work.

Thanks for your help on this though. It was a wierd one! I am still having trouble getting something to work as needed, but it is unrelated to the installation so I'll open a new thread on it.
Ted

bereanbs,

I appreciate the points, but if I didn't answer your Question, I would have preferred that you had a Moderator PAQ it and refund your points, rather than giving me a grade of C.

When I saw the C, I said "ouch."

bearanbs, you should go to the "help" link at the top of the page, and read up on how EE grading works.