No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

File Access and Protocols Feature Guide 13

OceanStor 18500 V3 and 18800 V3 Mission Critical Storage System V300R003

This document describes the implementation principles and application scenarios of the NAS feature. Also, it explains how to configure and manage NAS.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Accessing NFS Share

Accessing NFS Share

This section describes how a client accesses an NFS shared file system. The operating systems that support the client in accessing NFS shared file systems include SUSE, Red Hat, HP-UX, SUN Solaris, IBM AIX, and Mac OS, etc. Operations used by a client to access an NFS share in an LDAP domain and NIS domain are the same as those used in a non-domain environment.

Accessing an NFS Shared File System by a SUSE or Red Hat Client

  1. Log in to the client as user root.
  2. Run showmount -e ipaddress to view available NFS shared file systems of the storage system.

    ipaddress represents the virtual IP address of the storage system. 172.16.128.10 is used as an example.

    #showmount -e 172.16.128.10
    Export list for 172.16.128.10
    /nfstest *
    #
    

    NOTE:

    /nfstest in the output represents the path of the NFS share created in the storage system.

  3. Run mount -t nfs -o vers=n,proto=m,rsize=o,wsize=p,hard,intr,timeo=q ipaddress:filesystem /mnt to mount the NFS shared file system. Table 2-14 describes the related parameters.

    #mount -t nfs -o vers=3,proto=tcp,rsize=1048576,wsize=1048576,hard,intr,timeo=600 172.16.128.10:/nfstest /mnt
    Table 2-14  SUSE/Red Hat mount NFS shares parameters

    Parameter

    Description

    Example

    o

    Option that nfs mount, including ro, rw and so on.
    • ro: Mount a share that only be read.
    • rw: Mount a share that can be read and write.

    The default value is rw.

    vers

    The NFS version. The value can be 3 or 4.

    In a scenario where the NFS v4 sharing protocol is used, a single-controller switchover may interrupt services. In a environment that requires high reliability, you are advised to use NFS v3.

    proto

    The transfer protocol. The value can be tcp or udp.

    tcp

    rsize

    The number of bytes NFS uses when reading files from an NFS server. The unit is byte.

    Recommended to use 1048576, and recommended to use 16384 for Red Hat 7.

    wsize

    The number of bytes NFS uses when writing files to an NFS server, The unit is byte.

    Recommended to use 1048576

    timeo

    The retransmission interval upon timeout. The unit is one tenths of a second

    Recommended to use 600

    filesystem

    The path of the NFS share created in the storage system.

    -

  4. Run mount to verify that the NFS shared file system has been mounted to the local computer.

    #mount
    172.16.128.10:/nfstest on /mnt type nfs (rw,vers=3,proto=tcp,rsize=1048576,wsize=1048576,hard,intr,timeo=600,addr=172.16.128.10)
    

    When the previous output appears, the NFS shared file system has been successfully mounted to the local computer. If the actual output differs from the previous output, contact technical support engineers.

Accessing an NFS Shared File System by an HP-UX or SUN Solaris Client

  1. Log in to the client as user root.
  2. Run showmount -e ipaddress to view available NFS shared file systems of the storage system.

    ipaddress represents the virtual IP address of the storage system. 172.16.128.10 is used as an example.

    #showmount -e 172.16.128.10
    Export list for 172.16.128.10
    /nfstest *
    #
    
    NOTE:

    /nfstest in the output represents the path of the NFS share created in the storage system.

  3. Run mount [-F nfs|-f nfs] -o vers=n,proto=m ipaddress:filesystem /mnt to mount the NFS shared file system. Table 2-15 describes the related parameters.

    #mount -f nfs -o vers=3,proto=tcp 172.16.128.10:/nfstest /mnt
    Table 2-15  HP-UX or SUN Solaris mount NFS shares parameters

    Parameter

    Description

    Example

    -F nfs or -f nfs

    Optional.

    -F nfs is available to the HP-UX client and -f nfs to the Solaris client.

    vers

    The NFS version. The value can be 3 or 4.

    In a scenario where the NFS v4 sharing protocol is used, a single-controller switchover may interrupt services. In a environment that requires high reliability, you are advised to use NFS v3.

    proto

    The transfer protocol. The value can be tcp or udp.

    tcp

    filesystem

    The path of the NFS share created in the storage system.

    -

  4. Run mount to verify that the NFS shared file system has been mounted to the local computer.

    #mount
    172.16.128.10:/nfstest on /mnt type nfs (rw,vers=3,proto=tcp,addr=172.16.128.10)
    

    When the previous output appears, the NFS shared file system has been successfully mounted to the local computer. If the actual output differs from the previous output, contact technical support engineers.

Accessing an NFS Shared File System by an IBM AIX Client

  1. Log in to the client as user root.
  2. Run showmount -e ipaddress to view available NFS shared file systems of the storage system.

    ipaddress represents the virtual IP address of the storage system. 172.16.128.10 is used as an example.

    #showmount -e 172.16.128.10
    Export list for 172.16.128.10
    /nfstest *
    #
    
    NOTE:

    /nfstest in the output represents the path of the NFS share created in the storage system.

  3. Run mount ipaddress:filesystem /mnt to mount the NFS shared file system.

    NOTE:

    filesystem represents the path of the NFS share created in the storage system.

    #mount 172.16.128.10:/nfstest /mnt
    mount: 1831-008 giving up on:
    172.16.128.10:/nfstest 
    Vmount: Operation not permitted.
    #
    
    NOTE:

    If the AIX client fails to mount the NFS shared file system after the command is executed, this is because the default NFS ports of AIX and Linux are inconsistent. Run the following command to solve this problem.

    #nfso -o nfs_use_reserved_ports=1
    Setting nfs_use_reserved_ports to 1
    

  4. Run mount to verify that the NFS shared file system has been mounted to the local computer.

    #mount
    172.16.128.10:/nfstest on /mnt type nfs (rw,addr=172.16.128.10)
    

    When the previous output appears, the NFS shared file system has been successfully mounted to the local computer. If the actual output differs from the previous output, contact technical support engineers.

Accessing an NFS Shared File System by a Mac OS Client

  1. Run showmount -e ipaddress to view available NFS shared file systems of the storage system.

    ipaddress represents the virtual IP address of the storage system. 172.16.128.10 is used as an example.

    Volumes root# showmount -e 172.16.128.10
    /nfstest *
    
    NOTE:

    /nfstest in the output represents the path of the NFS share created in the storage system.

  2. Run sudo /sbin/mount_nfs -P ipaddress:filesystem /Volumes/mount1 to mount the NFS shared file system.

    NOTE:

    filesystem represents the path of the NFS share created in the storage system.

    Volumes root# sudo /sbin/mount_nfs -P 172.16.128.10:/nfstest /Volumes/mount1

  3. Run mount to verify that the NFS shared file system has been mounted to the local computer.

    Volumes root# mount
    /dev/disk0s2 on / (hfs, local, journaled)
    devfs on /dev (devfs, local)
    fdesc on /dev (fdesc, union)
    map -hosts on /net (autofs, automounted)
    map auto_home on /home (autofs, automounted)
    172.16.128.10:/nfstest on /Volumes/mount1 (nfs)
    

    When the previous output appears, the NFS shared file system has been successfully mounted to the local computer. If the actual output differs from the previous output, contact technical support engineers.

Accessing an NFS Shared File System by a VMware Client

NOTE:

When you want to create virtual machines on the NFS share, The Root Permission Constraint of the NFS share must be no_root_squash.

  1. Log in to VMware vSphere Client.
  2. Choose Localhost > Configuration > Storage > Add Storage.

    The Add Storage wizard is displayed.

  3. In Select Storage Type, select Network File System. Then, click Next.

    The Locate Network File System page is displayed.

  4. Set parameters. Table 2-16 describes related parameters.

    Table 2-16  Parameters for adding an NFS share in VMware

    Parameter

    Description

    Value

    Server

    Logical IP address of the storage system.

    Example

    172.16.128.10

    Folder

    The path of the NFS share created in the storage system.

    Example

    /nfstest

    Datastore Name

    Name of the NFS share in VMware.

    Example

    data

  5. Click Next.
  6. Confirm the information and click Finish.
  7. On the Configuration tab page, view the newly added NFS share.

Postrequisite

If you modify NFS user information when using the client to access NFS shares, new user authentication information cannot take effect immediately. Wait 30 minutes for the modification to take effect.
Translation
Download
Updated: 2019-08-14

Document ID: EDOC1000084098

Views: 32507

Downloads: 72

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next