2.2 Distributed File Services (DFS)

2.2.1 Windows Cannot Access Error

If Windows SMB Share or Windows Server are unavailable, or no trustee rights are available for the Windows SMB Share, permission denied error is displayed.

Figure 2-1 Error Message

2.2.2 CIFS eDirectory User can Access Non-OES Windows Target DFS Junction

If the Active Directory administrator permissions are granted to Windows share, the CIFS eDirectory user can access the DFS junction on the non-OES Windows target DFS junction.

2.2.3 Non-OES Target Validation Errors

By default, dfstool uses anonymous login to validate the non-OES SMB share without prompting the user for any credentials on the command line. The dfstool does not check whether the path exists from the share. If the anonymous login is disabled on the server hosting the target then junction creation or modification might fail.

The i option can be used to establish the non-OES junction without verifying the existence of the target server or share:

  • dfstool -c /media/nss/VOL1/dir1/junc1 -t target_server_or_ip_address/share_name/path_to_target_folder -T non-oes -i

    (or)

    dfstool -c /media/nss/VOL1/dir1/junc1 -t target_server_or_ip_address/share_name/path_to_target_folder -T non-oes --ignore-targetpath-check

  • dfstool -m /media/nss/VOL1/dir1/junc1 -t target_server_or_ip_address/share_name/path_to_target_folder -T non-oes -i

    (or)

    dfstool -m /media/nss/VOL1/dir1/junc1 -t target_server_or_ip_address/share_name/path_to_target_folder -T non-oes --ignore-targetpath-check

2.2.4 NCP Clients Issues

  • NCP client does not list non-OES targets.

  • For a DFS junction, the NCP client is unable to list all multiple targets. In a failover scenario, the NCP client cannot use the other target if one of the targets is unavailable as the NCP clients always points to the first target path.

2.2.5 iManager Issues

  • iManager cannot list more than one target if the DFS junction points to multiple targets.

  • If an NSS volume has both OES and a non-OES junction, iManager junction scan lists only OES junctions. So, to view non-OES junctions, you must use dfstool.

  • When browsing the NSS volume to modify or delete DFS junctions, iManager lists only OES junctions.

  • In OES 24.4 iManager, the move volume and split volume jobs fail when you select an existing volume as the target. To resolve this issue, you can use an earlier version of iManager or create a new volume during the move or split volume operation.

2.2.6 RME must be Configured for DFS Junction Pointing to Multiple Targets

Cluster migrating a resource (which has a first target path) to another server (which has a second target path) followed by "vldb repair" would result in only one active target path until the user configures Resource Mutual Exclusion (RME).

2.2.7 DFSTOOL Command Errors

  • If a DFS junction points to multiple targets, the list junction cannot list more than one target for that DFS junction.

  • dfstool does not validate the special characters ($$, $!) appended to the share name and creates junction successfully.

  • dfstool throws an encryption issue even though the junction is successfully created when creating a junction with Netapp shares using the -A option.

  • When using DFS Namespace to generate a non-OES junction, dfstool incorrectly lists the non-OES junction target path because DFS Namespace is appended before the SMB target share.

    Junction Name

    Source Server

    Source Path

    Target Server

    Target Path

    Management Context

    Status

    junc1

    OESserver

    Vol1:/nonoes/

    Windows_domain

    DFSnamespace:/Winshare1/

    *NA*

    Available

    junc2

    OESserver

    Vol1:/nonoes/

    Windows_domain

    DFSnamespace:/Winshare1/dir1

    *NA*

    Available