🚀 go-pugleaf

Phil Schuman wrote:
> 
> I have a couple of questions on NDS, tree names, and dup ORG names.
> 
> Here is the structure and naming we have to work with...
> 
> This was setup by 2 different groups (duh) and 2 different sources..
> Now we are looking at how to connect the hubs together (in same rack)
> 
> MIS LAN
>         tree name = SYMONS CORP
>         file server name = symons-corp
>         bindery context = o=symons
> 
> MFG LAN
>         tree name = SYMONSPROD
>         file server name = symons_prod
>         bindery context = o=symons
> 
> now the questions
> how can the MIS LAN have a tree name with an embedded space ??
>         however, the SAPs seem to show a 'underscore' ??
> 
> how can we even have both LANs on the same wire - if the ORG is the same ?
>         what should we do about this ???
> 
> any other places or utilities that will clearly show the tree names -
> 
> Phil -There's no problem with 2 trees having the same internal naming structure,
and being on the same net, provided the NDS tree names are different. This
is your case. We have many trees, most with the same internal structure. No
problems, until you try having 2 with the same name - then BIG trouble. Do
NOT do this.
If you don't like the NDS tree names you've got, check out DSMERGE. You may
want this in the end anyway. It merges trees (gosh). But it has a rename
function too.
I can't say about embedded spaces, but if DSMERGE can show it, it can probably
change it to something more reasonable.

Good luck, Richard