iManager Error: NDS Error -610
Erik
This morning I installed the bm39_iman27 plugins into iManager 2.7.3. There were no errors during installation.
Under Roles and tasks-Bordermanager there are only 4 items (Access Rules, Legacy Filter Configuration, Proxy Services and VPN Services). In the test there were a few more items
(Access Rules, Easy Filter Configuration, Filter Maintenance, Legacy Filter Configuration, List All Firewall Policies, Proxy Services, VPN Services).
While opening for example Proxy Services in production, there are a lot of lines on the logger screen with count and a number. At last there is the Error: NDS Error -610
Any suggestions?
Thanks,
Erik
Craig Johnson
> This morning I installed the bm39_iman27 plugins into iManager 2.7.3. There were no errors during
installation.
> Under Roles and tasks-Bordermanager there are only 4 items (Access Rules, Legacy Filter
Configuration, Proxy Services and VPN Services). In the test there were a few more items
> (Access Rules, Easy Filter Configuration, Filter Maintenance, Legacy Filter Configuration, List All
Firewall Policies, Proxy Services, VPN Services).
>
filtering. I just use FILTCFG to manage filters instead of iManager.
Have you checked the Roles and Tasks in the iManager config menu? You might have to update RBS.
> While opening for example Proxy Services in production, there are a lot of lines on the logger screen
with count and a number. At last there is the Error: NDS Error -610
OK, there's an issue with DS perhaps. The 610 error is illegal DS name. Could be some sort of problem
in iManager, or perhaps an issue in DS. Do you have a replica on the server? Have you run DSREPAIR on
the server? Do you have this error just when trying to select the proxy option, or do you get to the
server name search field prompt? Do you have a long server name for the BM server?
You can manage BM 3.9 from any iMan 2.7.x that has the plugins installed, including a Windows version
running on your PC. Or an iMan 2.7.x installed in another tree.
Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***
Craig Johnson
> Is there anyone with a clue? We are unable to manage our BM-server at
> the moment.
>
Sorry for the slow response. Please check my reply to the first
message in this thread.
Mysterious
>
> I have read this thread about a BM3.9 remove configuration utility.
>
> http://forums.novell.com/novell-product-support-forums/bordermanager/bm-install-setup/390618-bm-3-9-remove-configuration.html
>
> Could this be a solution to our problem? I know we have to enter the
> configuration ( do we?).
>
> Erik
>
>
1. -610 is an illegal name. If you enable dstrace and dup the issue,
you'll be able to see what object gives the error. Also duplicating the
issue and postign the logger screen will help
2. If you do not have all bm menus in imanager, install the plugins
properly or update the collection if you use one.
Mysterious
>
> Hi,
> on NBM logger screen I only see this
>
> ......
> count -->21396
> count -->21397
> count -->21398
> count -->21399
> count -->21400
> count -->21401
> count -->21402
> .....
just ignore that, it is informative
> When I try to manage NBM from another non NBM server, it�s functional
> without any problem.
>
>
you do not have a problem with bm, you have a problem with your edir on
the bm box. Take the dstrace and you'll be able to see it and fix it.
Make sure that your bm server holds a partition containing the server
object.
Craig Johnson
wrote:
> It looks like, that without local replica isn�t iManager able in timely
> fashion find all Border Manager servers, even when I have local replica
> takes it 20 - 30 seconds from clicking on Proxy Services and showing
> dialog, where I can choose right server
>
Replicas are needed on the server for other purposed. IManager's initial
link to proxy services is pretty slow, regardless of having a replica on
there. Some trees more than others.
Craig Johnson
Novell Knowledge Partner
Mysterious
Mysterious
>
> Thanks Mysterious,
>
> Those TID's are about not been able to start iManager on the BM-server.
i did not see that. tid3660131 shows your problem when trying to log in
into imanager, nothing to do if it is a bm server or not
> I tried TID 3660131 en 7001244, but I am still not able to login to
> iMaganer on the BM-server.
Did you do all mentioned steps on the bm server itself?
> We are able to set filters through iManager on other servers, but the
> items Access Rules and Proxy Services still don not work.
>
> Erik
>
>
I think you have to clarify your issue because each post is a
contradiction of your last one. For example, you said:
"We can not manage BM from any server nor the workstation version of
iManager.
If we try to start iManager off of the BM server, there is a message;"
But you just said that filters works thru imanager.
Also
Access Rules and Proxy Services still don not work.
Can you elaborate? Go step by step and explain what is happening, not
what you think is happening, so when you use imanager from another
server, you've got on the left side the bm menu, correct? Under the bm
menu you've got 7 entries, correct? if not, your plugins are not
correctly installed or your collection has not been updated. Start
fixing this.
if you've got all 7 entries, what happen when you click on the proxy
services. Do you get the option to select the bm server object? if not
what error is displayed on the browser. A screenshot will help.
if you're able to select it, do you get then the proxy configuration
tab? bla bla bla bla, so steps by step we'll be able to see where it fails
Mysterious
>
> My answers are in RED!
> Sorry for my bad formulation, my dutch is better ;-)
i could not see the colors :-)
you have to install the plugins on the tomcat directory where the
imanager is running. So if you run imanager from server A, you have to
install the plugins on server A, not on the bm server.
Mysterious
>
> and the iManager screen...
>
>
> +----------------------------------------------------------------------+
> |Filename: iManager2.JPG |
> |Download: http://forums.novell.com/attachment.php?attachmentid=3822 |
> +----------------------------------------------------------------------+
>
what is the full name of your bm server?
Mysterious
>
>
> This shows the screens when I click Proxy Services in iManager
> connected to a server(not the BM-server).
>
> First the loggerscreen of the server.
>
>
> +----------------------------------------------------------------------+
> |Filename: iManager.JPG |
> |Download: http://forums.novell.com/attachment.php?attachmentid=3821 |
> +----------------------------------------------------------------------+
>
OK, you do not have any issue with the snapins but with your ds. If you
take a dstrace as i mentioned previously, you'll see which object and
why it gives the -610 error.
Mysterious
>
> I took a dstrace on both the BM-server and the server running iManager,
> but I could not see -610 errors. Do I have to set special options during
> the trace are do I have to ask this in the eDirectory section of this
> forum?
>
> Erik
>
>
the dstrace should be taken on the server running imanager, hence the
one giving the -610 error. if you did not set any option on the capture
filter then probably nothing was capture so or enable schema option or
enable all options to be sure. As you will enable the dstrace just
before hit imanager button to force the -610 error, trace should not be
very big and will show the object causing it but i asked you about the
complete name of your server as that may be the culprit.
At server console running imanager type:
1. load dstrace
2. dstrace screen on
3. dstrace +all
4. dstrace file on
Now go to imanager and click on the button to force the -610 error
When done at server console type unload dstrace.
now on the sys:system\dstrace.log should be the -601 error
Mysterious
>
> I hope you meen the -610 I have to look for? There are some -601 and
> -603 errors on a few user objects.
>
yes i meant 610
> Here is yust a small piece of the iMonitor trace history. The
> servername is SVZDL0002
the whole name, cn=blabla.ou=blabla.o=blabla.T=blabla
> 14:46:45 94AFF500 NCPCli: request DSASearch by context 087b1110
> succeeded
> 14:46:45 94AFF500 NCPCli: SearchFromPartition: Retrieved 333 entries
> 14:46:45 94AFF500 NCPCli: SearchFromPartition: Processed 71 values, err
> = failed, illegal ds name (-610)
>
there is your error, if you have taken the dstrace as i told you, you
will see what reply is that, to what request.
Craig Johnson
> iManager workstation 2.7.0 and updated it to 2.7.2 and we were still
> able to manage BorderManager. After updating to 2.7.3 it stopped
> functioning.
>
Odd - I don't see that on a single one of (quite a few) BM 3.9 servers
I work on.
This one will need a trace. Sounds like something unique in your tree
is interacting with a particular 2.7.3 call. I'm guessing it is rare,
so Novell may never have seen something like it.