[b]Routing Information Protocol (RIP)[/b]
http://ccnahelpguides.blogspot.com/2008/08/routing-information-protocol-rip.html

[b] Interior Gateway Routing Protocol (IGRP)[/b]
http://ccnahelpguides.blogspot.com/2008/08/interior-gateway-routing-protocol-igrp...

Glad to hear it.

I did an in-place upgrade today to a 3.8sp5 server, and it was probably
the smoothest upgrade I've ever seen. Nothing was a problem, and
everything came through.

Personally though, I advise not putting two BM servers in the same ou,
as it is easier to deal with both filtering and licensing issues when
they are in their own OU's.

Have a look in the BM CD, in the documents/craig johnson directory, for
a Lite version of my BM 3.9 book. It will give some useful guidance on
upgrades and tuning of the server. (It's also not hard to set up a new
OU and drag almost all the 3.9 server-related objects to the new OU. A
couple, like filter exceptions, you just recreate in the new OU.)

Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***

I have installed Border Manager 3.9 sp1 running on OES Netware 6.5 sp7.

The server is a read/write replica.

I have installed plugins into Mobile iManager 3.7 running from Windows
XP sp1. I cannot confirm which version of plugins I have.

I am experiencing the following error while attempting to manage the proxy.

This configuration cannot be edited because it is currently being edited
by cn=user,ou=userou,o=org (127.0.0.1) Since 7/25/08 4:35:28 pm.

Any changes you will make will be discarded.

This is being seen through iManager. Can someone please explain how I
can get out of this situation.

Cheers,

Depends on just what is happening (where the failure occurs). Have you
watched the logger screen at the point of failure?

Is this just an sp1 update to 3.9? Or are you trying an overlay
upgrade? I haven't tried it yet, but you may be able to just copy the
sp1 files manually over the old ones. I'm not sure if there is some
change happening to some NDS attributes or other changes that are done
with some java process in the sp1 install.

Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***

I wouldn't bother to upgrade them. Just set up another new virtual
server and install 3.9 there. Use different IP addresses to avoid
address duplication and test. When ready, unload proxy on the old
server and unload the IP address as needed. Then reconfigure the new
server to use the old addresses for reverse proxy, and you should be
good to go.

If you are doing filtering on the new server(s), you will need to be
sure you put in filter exceptions to allow the reverse proxy traffic to
the old IP addresses.

Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***

Have a look in the documents\craig johnson folder on the BM 3.9 CD. I
have some upgrade ideas for you in there.

Basically, the new server can simply be installed over the old one, and
worst case is you have to re-enter some of your settings. The filters
should be automatically re-used. The access rules can be saved to a
file in clipboard viewer, and through careful use of the FILLATTR.NCF
file can be upgraded into 3.9. (Though SurfControl/LinkWall/N2H2 would
have to be redone manually, I think).

Proxy settings might also be upgradable, but it's usually easy enough
to just re-enter them.

I have successfully upgraded older servers in place by manually
modifying the products.dat file to tell it that a BM3 3.8 sp5
installation is in place. Haven't done that with a 3.5 server, but I
think it would still work. Definitely an untested upgrade scenario not
supported by Novell.

Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***

mmeeks wrote:

I recently posted a similar question in the thread "3.8 on old server to
3.9 on new - Tips?" I never found a useful solution. I had to document
all of my rules from the old server, take screenshots of settings, then
manually re-enter everything on the new server. My only consolation is
that I will never again have to migrate a BorderManager server because
this will be our last BorderManager server.

Jim Wagner

You have to point a default route to a router that can actually get to
the Internet. That is, if you hand off a packet to some other router
(your internal Cisco), then it has to have a default route to some
other device. As long as the traffic doesn't have to go through your
BMgr server from the internal router, you should be fine.

I often set up new BM servers pointing to internal address of old BM
servers to get started, if there isn't a free public IP address
available for the new server. Also, when I work on proxy-only BM
servers, it's natural for them to have only one nic and point to some
other router (firewall) for internet access.

In your case, perhaps your internal networks are advertised via RIP or
OSPF, and you could just have routing protocols add your internal
routes for you.

Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***

HI

I have a Bm 3.8 sp5 on NetWare 6 sp5. I want to update to Gwava 4 which
needs to be at least on NetWare 6.5 sp5. I am concerned about the legacy
vpn I have that talks to a NetWare 6 sp5 BM 3.7 sp3 slave.

Is this an update I can make? The gwava indicates I might be able to run
on NetWare 6 sp5 but its not tested much.

Thanks,

Ok, so I opened Pandora's box. Whom among the group has the connections
with the powers that be to correct this situation?
Gus