Volumes of secondry novell server is not showing in iManager

We have a primary novell server. I have created another novell server (new physical server) as a secondary server under the same Tree/Context. Now I created a new nss volume in 2nd server.
But when I open the iManager windows client to the 1st server and go to Files and Folder->Object Selector and open volumes under 2nd server, in this window I see all the old volumes in 2nd server but not the new volume I created. Looks like some problem with refreshing the volume list. How to make nss refresh its volume list? I expect to see LFA2_VOL3, but it is not there. See attached picture.
https://drive.google.com/open?id=1tg_SH6yYF5IT5QShoSAISDEdy3GX1wMr
  • Which OS are we talking about? NetWare, OES11, OES2015, OES2018?
  • In article <srinivaskv.8qcm7b@no-mx.forums.microfocus.com>, Srinivaskv
    wrote:
    > Looks like some problem with refreshing the volume
    > list. How to make nss refresh its volume list


    That would likely be at the eDir level hitting a snag. I bet that you
    would see that missing volume on iManager of the second server.
    On either/both SLES base servers, run the following commands to see
    what is going on that also triggers some of the resync of things
    ndsrepair -T
    ndsrepair -E
    ndsrepair -C -Ad -A
    If errors show, we will need to dig into them in the appropriate forum
    as this is very much NOT a client issue.


    Andy of
    http://KonecnyConsulting.ca in Toronto
    Knowledge Partner
    https://forums.novell.com/member.php/75037-konecnya
    If you find a post helpful and are logged in the Web interface, please
    show your appreciation by clicking on the star below. Thanks!

  • Hi Andy,

    Yes I am able to see the missing volume in Imanager on the second server. Also If I open Imanager on first server and go to Files and Folders menu and in the properties after I selecting a volume of first server, then instead of first server name I type in second server name and volume, iManager shows the properties correctly. It could be problem with the eDir having to be rebuild. I will try those repair cmds and let you know. Could we do this even if there are no problems. Is ndsrepair a harmless command if there isn't anything to do?

    Thanks very much for your suggestions.

    Srinivas.
    Grace Infrastructure Pvt Ltd
    Pondicherry India.
  • In article <srinivaskv.8qgybb@no-mx.forums.microfocus.com>, Srinivaskv
    wrote:
    > Is ndsrepair a
    > harmless command if there isn't anything to do?


    Ndsrepair is the full range, from basic diagnostics to blowing away
    parts of eDir. It is all in the options selected that ARE case
    sensitive.

    Those three I gave (in that order) are basic diagnostic ones that can
    be run any time. If the first shows errors, deal with those before
    bothering with the other tests and so on. I.e. If a server can't see
    an other server, we need to dig into that first. Example I recently
    dealt with was a flaky switch kept bouncing connections. Until that was
    fixed, there just wasn't any point in pushing the ndsrepairs other than
    as a monitor as to our status and to find the boxes where eDir got hung
    up because of the wire level corruptions.
    If you do have errors on that level, take them over to the OES Admin
    section rather than this client section.


    Andy of
    http://KonecnyConsulting.ca in Toronto
    Knowledge Partner
    https://forums.novell.com/member.php/75037-konecnya
    If you find a post helpful and are logged in the Web interface, please
    show your appreciation by clicking on the star below. Thanks!

  • Hi Andy,

    I ran the nsdrepair commands one by one. Only ndsrepair -E gave message about 1 error . But no details. After the commands were run, now iManager is showing volumes from the secondary.
    So thanks a lot for your help.


    --Srinivas.
  • In article <srinivaskv.8qpzrz@no-mx.forums.microfocus.com>, Srinivaskv
    wrote:
    > I ran the nsdrepair commands one by one. Only ndsrepair -E gave
    > message about 1 error . But no details. After the commands were run, now

    the details are typically embedded above and in the form of -### detail
    added at the end of a line
    example:
    Replica: .serv1.org.Domain a time
    Server: CN=serv2.org.Domain a time -625 Remote
    Object: {Root]
    which in this case indicates that serv1 can't talk with serv2.

    > IManager is showing volumes from the secondary.

    Sometimes those diagnostic ndsrepairs do kick things clear and let normal
    processing happen

    > So thanks a lot for your help.

    Your welcome. It is a pleasure to help here, though as you can see from
    the delay, other things (work