- Fs 2 6 0 – Note Manager Interview Questions And Answers
- Fs 2 6 0 – Note Manager Interview Questions
- Fs 2 6 0 – Note Manager Interview Question
- Fs 2 6 0 – Note Manager Interview Question And Answer
Verify if the AD FS 3.0 MMC plugin looks like the following screen shot: If it appears different then you have to install AD FS 3.0. Open AD FS 3.0 Service Certificates and then configure Service Communication, Token-Decrypting, and Tokensigning certificates.
DHR Admin Svcs Div will only post approved blank forms to this web site. If you try to open the below word template or PDF file and you are asked for a password, just click on 'cancel.' FSNotes is a plain-text note manager for macOS, and is modern reinvention of notational velocity (nvALT) on steroids. Our application respects the following open formats: plain/text, Markdown, and RTF, and stores data in the file system. You can view, edit, and copy data in your favourite external editor, and see live results in FSNotes.
2 Updated from: Top 10 finance manager interview questions with answers To:` Top 52 finance manager interview questions with answers On: Mar 2017 3. 3 This ebook includes two parts: - Part I: Top 52 finance manager interview questions with answers (pdf, free download) - Part II: Top 12 tips to prepare for finance manager interview. Hadoop fs -put WCFile.txt WCFile.txt. Now to run the jar file by writing the code as shown in the screenshot. After Executing the code, you can see the result in WCOutput file or by writing following command on terminal. Hadoop fs -cat WCOutput/part-00000.
Applicable Products
- Citrix ADC
Objective
This article describes how to set up Security Assertion Markup Language (SAML) Active Directory Federation Services (AD FS) that is configuring NetScaler SAML to work with Microsoft ADFS 3.0 IDP.
Note: This article is not for replacing AD FS Proxy with NetScaler. It is intended to be used when SAML is configured in front of the NetScaler appliance.
Instructions
To set up SAML AD FS, complete the following procedure:
- Open the following links and verify if the AD FS is working:
https://<adfs_fqdn>/adfs/fs/federationserverservice.asmx
https://<adfs_fqdn >/FederationMetadata/2007-06/FederationMetadata.xml - Verify if the AD FS 3.0 MMC plugin looks like the following screen shot:
If it appears different then you have to install AD FS 3.0. - Open AD FS 3.0 > Service > Certificates and then configure Service Communication, Token-Decrypting, and Token_signing certificates.
- Select the appropriate certificates by clicking on 'Certificates' option that can be used for SAML communication. This is the certificate that NetScaler appliance will use when verifying the signed SAML Response from IDP.
- Open AD FS 3.0 > Trust Relation Ships > Relaying party Trusts > Add Relaying Party Trust and then configure Relaying Party Trust.
- Select the Import Dataabout the relaying party published online or local network option.
- Specify the NetScaler Metadata file location as https://vserver_fqdn>/ns_metadata.xml. Note: Metadata file is not created by default. NetScaler administrator has to create the metadata file (ns_metadata.xml) and copy the same at /netscaler/ns_gui/vpn folder by specifying the location as https://<vpnvserver>/ns_metdata.xml.ORInstead of copying to NetScaler and specifying the URL location, the metadata can be copied to a shared location and accessed.
The following screen shot shows a sample metadata file.Update the following text in the metadata file for the corresponding environment:
Note: The following is the metadata file in text - https://citrix.sharefile.com/d/sa0c465afb9142ff9 and here is an example that has been filled out - https://citrix.sharefile.com/d/see1f982434a4a7cb. Some of the screen shots will reflect the configuration from the example.- IDPLoginPage is the Redirect url
- KeyName is the signingCertname
- <lbvs.fqdn.com>/cgi/samlauth is the Login URL or authentication end point
- lbvserver.fqdn.com is the common name for the certificate of the load balancing virtual server on a NetScaler appliance
- Ignore the following error message.
- Select the Authorization rules, as shown in the following screen shot:
- Verify the Relaying Party data before you complete:Encryption and Signature: NetScaler virtual server Server CertificateEnd Points: https://<vserver_fqdn>/cgi/samlauth
- Complete the Relaying Party Trust Wizard.
- Select the new Relaying Party Trust and edit the Properties.
- Select Advanced.
- Select the Secure hash algorithm as SHA-1, as shown in the following screen shot:Note: An Enhancement #440382 raised to support SHA256 hashing algorithm. This is available in version 10.5 build 55.x or above.
- Select the Encryption tab, remove all Certificates, if there are any listed.
Note: Encrypted Assertions are currently not supported. - Select Endpoints and make sure it looks similar to the following screen shot:
- Select Identifiers, and make sure it looks similar to the following screen shot:
- Select Signature and make sure it looks similar to the following screen shot:
- Right-click the Relaying Party trust and select Edit Claim Rules.
- Select Transform Rule > Add Claim Rule > Claim Rule Template> Send LDAP Attributes as Claims.
- Type a name for the rule.
- Select Active Directory for Attribute Store.
- Select the LDAP attribute: <AD parameters>.
- Select the Out Going Claim Rule as Name ID.
Note: Currently only Out Going Claim Rule: Name ID is supported. - For the second rule, select Send claims using a custom rule.
- Specify a URL to redirect the network traffic when the user logs out by creating a custom claim rule which sends an additional logoutURL attribute.
The custom rule is as follows:
Configuration on a NetScaler Appliance
To configure the NetScaler appliance, complete the following procedure:
- Download AD FS signing certificate.
- Run the following command to add a Certificate key:
add ssl certKey adfs-signing -cert adfs-signing.cer - Run the following command to add an SAML action:
add authentication samlAction samladfs -samlIdPCertName <ipd certificate> -samlSigningCertName <sp certificate> -samlRedirectUrl 'https://<adfs_fqdn >/adfs/ls/' -samlUserField 'Name ID' -samlIssuerName <issuername/relaying party identifier>add authentication samlPolicy saml_true ns_true samladfsex: add authentication samlAction samladfs -samlIdPCertName adfs.coolidge.netweb -samlSigningCertName lbiis.coolidge.net -samlRedirectUrl 'https://adfs.coolidge.net/adfs/ls/FormsSignIn.aspx' -samlUserField 'Name ID' -samlIssuerName 'https://lbiis.coolidge.net'- sp certificate is the name of the certificate key pair added as a SAML signing certificate.
- First occurrence of <certname> refers to the certificate name of SAML IDP certificate and second occurrence refers to the SAML signing certificate.
- samlIDPCertname specifies the certificate the NetScaler appliance uses when verifying the signed SAML Response from IDP. It will be a public Signing certificate of IDP.
- samlSigningCert specifies the certificate the NetScaler appliance uses to sign the SAML Request going to IDP. Therefore, the administrator has to configure the same certificate in the NetScaler Metadata file. Most IDPs extract Service Provider information from the metadata file including the certificate. If IDP supports the manual configuration, metadata file is not required. The administrator has to configure this certificate as Service Provider certificate.
- Add a aaa-tm server:
add authentication vserver aaa.coolidge.net SSL 192.168.1.32 443 - Bind the SAML policy:
bind authentication vserver aaa.coolidge.net -policy saml_true -priority 100 - Add a load balancing virtual server:
add lb vserver lbvserver_iis_ssl SSL 192.168.1.31 443 -persistenceType NONE -cltTimeout 180 -AuthenticationHost 'https://aaa.coolidge.net' -Authentication ON -authnVsName aaa.coolidge.net - Add DNS names:
192.168.1.32 > aaa.coolidge.net
192.168.1.31 > lbiis.coolidge.net - The following NetScaler configuration should also be completed:
Add SSL certificates
Add services
Bind services
Additional Resources
To configure AAA virtual server, refer to Citrix Documentation - Configuring the Authentication Virtual Server.
AD FS 3.0 Installation Document: - AD FS 3.0 Installation Document
The following table describes the parameters used to create an SAML action.
add authentication SAMLAction <name> -samlIdPCertName <certname> -samlRedirectUrl <IDP URL> -samlUsernameField –samlSigningCert <certname> -samlIssuerName <issuer_name> -samlRejectUnsignedAssertion <TRUE/FALSE>
add authentication SAMLAction <name> -samlIdPCertName <certname> -samlRedirectUrl <IDP URL> -samlUsernameField –samlSigningCert <certname> -samlIssuerName <issuer_name> -samlRejectUnsignedAssertion <TRUE/FALSE>
Parameter | Description |
certname | It is the public key corresponding to the private key at the Identity Provider (IdP). It is required for decrypting or verifying the SAML assertion. This can come in the assertion as keyInfo, but is not currently used. Add this information to the NetScaler appliance using the add certkey command. |
Redirect url | It is the url of the authentication end point (IdP). Unauthenticated users are redirected to this URL. |
Username field | It can be used to extract the username if the IdP sends the username in other than <NameIdentifier> tag of <Subject> tag. In most scenarios, this need not be configured. Depending on the use cases, this can be removed. |
signingCertname | It is the certificate key of AAA/Gateway virtual server that is used to sign the authentication request to the IdP. If signingCertName is not configured, then assertion is either sent unsigned or authentication is rejected as per the samlRejectUnsignedAssertion parameter. |
samlIssuerName | It is the string to be used in sending the authentication request. Every IdP expects a unique name in the issuer field to signify the authority which sent this assertion. A few IdPs ignore this but a few rely on this field to search the metadata corresponding to this Service Provider. |
samlRejectUnsignedAssertion | It is a knob to accept or reject unsigned assertions from the IdP. This parameter gives flexibility to the administrator or user to verify the connectivity or basic functioning of the Service Provider and IdP. This knob is also used when sending the authentication request out. If signingCert is not configured and if this knob is false, the unsigned authentication request is sent. Otherwise, the SAML authentications are rejected and fall back to forms-based authentication. |
Errors and Debugging
Places to look for information:
NetScaler
Live tracing:
nsconmsg -d current -g saml
cat /tmp/aaad.debug
tail -f /var/log/ns.log
nsconmsg -d current -g saml
cat /tmp/aaad.debug
tail -f /var/log/ns.log
Historical:
nsconmsg -d stats -g saml
cat /var/log/ns.log
nsconmsg -d stats -g saml
cat /var/log/ns.log
Windows
ADFS 3.0 error log:
w3.woodsnetworks.com/index.php/2013/02/adfs-2-0-error-after-successful-login/
Issuername / identifier mismatch:
ID4037: The key needed to verify the signature could not be resolved from the following security key identifier 'SecurityKeyIdentifier
w3.woodsnetworks.com/index.php/2013/02/adfs-2-0-error-after-successful-login/
Issuername / identifier mismatch:
ID4037: The key needed to verify the signature could not be resolved from the following security key identifier 'SecurityKeyIdentifier
Incorrect IDP certificate configured on NetScaler
Browser error:
SAML Assertion verification failed; Please contact your administrator
/var/log/ns.log error:
Feb 12 15:07:07 <local0.err> 192.168.1.65 02/12/2015:14:07:07 GMT ns 0-PPE-0 : AAATM Message 1438 0 : 'Error while trying to verify the signature'
Feb 12 15:07:07 <local0.err> 192.168.1.65 02/12/2015:14:07:07 GMT ns 0-PPE-0 : AAATM Message 1439 0 : 'Verification of SAML assertion resulted in failure 917511'
SAML Assertion verification failed; Please contact your administrator
/var/log/ns.log error:
Feb 12 15:07:07 <local0.err> 192.168.1.65 02/12/2015:14:07:07 GMT ns 0-PPE-0 : AAATM Message 1438 0 : 'Error while trying to verify the signature'
Feb 12 15:07:07 <local0.err> 192.168.1.65 02/12/2015:14:07:07 GMT ns 0-PPE-0 : AAATM Message 1439 0 : 'Verification of SAML assertion resulted in failure 917511'
You can access gluster volumes in multiple ways. You can use GlusterNative Client method for high concurrency, performance and transparentfailover in GNU/Linux clients. You can also use NFS v3 to access glustervolumes. Extensive testing has been done on GNU/Linux clients and NFSimplementation in other operating system, such as FreeBSD, and Mac OS X,as well as Windows 7 (Professional and Up) and Windows Server 2003.Other NFS client implementations may work with gluster NFS server.
You can use CIFS to access volumes when using Microsoft Windows as wellas SAMBA clients. For this access method, Samba packages need to bepresent on the client side.
Gluster Native Client
The Gluster Native Client is a FUSE-based client running in user space.Gluster Native Client is the recommended method for accessing volumeswhen high concurrency and high write performance is required.
This section introduces the Gluster Native Client and explains how toinstall the software on client machines. This section also describes howto mount volumes on clients (both manually and automatically) and how toverify that the volume has mounted successfully.
Installing the Gluster Native Client
Before you begin installing the Gluster Native Client, you need toverify that the FUSE module is loaded on the client and has access tothe required modules as follows:
- Add the FUSE loadable kernel module (LKM) to the Linux kernel:
# modprobe fuse
- Verify that the FUSE module is loaded:
# dmesg | grep -i fuse
fuse init (API version 7.13)
Installing on Red Hat Package Manager (RPM) Distributions
To install Gluster Native Client on RPM distribution-based systems
- Install required prerequisites on the client using the following command:
$ sudo yum -y install openssh-server wget fuse fuse-libs openib libibverbs
- Ensure that TCP and UDP ports 24007 and 24008 are open on all Gluster servers. Apart from these ports, you need to open one port for each brick starting from port 49152 (instead of 24009 onwards as with previous releases). The brick ports assignment scheme is now compliant with IANA guidelines. For example: if you have five bricks, you need to have ports 49152 to 49156 open.You can use the following chains with iptables:
- Download the latest glusterfs, glusterfs-fuse, and glusterfs-rdma RPM files to each client. The glusterfs package contains the Gluster Native Client. The glusterfs-fuse package contains the FUSE translator required for mounting on client systems and the glusterfs-rdma packages contain OpenFabrics verbs RDMA module for Infiniband.You can download the software at GlusterFS download page.
- Install Gluster Native Client on the client.
Note The package versions listed in the example below may not be the latest release. Please refer to the download page to ensure that you have the recently released packages.
Note:The RDMA module is only required when using Infiniband.
Installing on Debian-based Distributions
To install Gluster Native Client on Debian-based distributions
- Install OpenSSH Server on each client using the following command:
$ sudo apt-get install openssh-server vim wget
- Download the latest GlusterFS .deb file and checksum to each client.You can download the software at GlusterFS download page.
- For each .deb file, get the checksum (using the following command) and compare it against the checksum for that file in the md5sum file.
$ md5sum GlusterFS_DEB_file.deb
The md5sum of the packages is available at: GlusterFS download page - Uninstall GlusterFS v3.1 (or an earlier version) from the client using the following command:
$ sudo dpkg -r glusterfs
(Optional) Run$ sudo dpkg -purge glusterfs
to purge theconfiguration files. - Install Gluster Native Client on the client using the following command:
$ sudo dpkg -i GlusterFS_DEB_file
For example:$ sudo dpkg -i glusterfs-3.8.x.deb
- Ensure that TCP and UDP ports 24007 and 24008 are open on all Gluster servers. Apart from these ports, you need to open one port for each brick starting from port 49152 (instead of 24009 onwards as with previous releases). The brick ports assignment scheme is now compliant with IANA guidelines. For example: if you have five bricks, you need to have ports 49152 to 49156 open.You can use the following chains with iptables:
Note
If you already have iptable chains, make sure that the aboveACCEPT rules precede the DROP rules. This can be achieved byproviding a lower rule number than the DROP rule.
Performing a Source Installation
To build and install Gluster Native Client from the source code
- Create a new directory using the following commands:
- Download the source code.You can download the source at link.
- Extract the source code using the following command:
# tar -xvzf SOURCE-FILE
- Run the configuration utility using the following command:
# ./configure
The configuration summary shows the components that will be builtwith Gluster Native Client. - Build the Gluster Native Client software using the following commands:
- Verify that the correct version of Gluster Native Client is installed, using the following command:
# glusterfs --version
Mounting Volumes
After installing the Gluster Native Client, you need to mount Glustervolumes to access data. There are two methods you can choose:
Note
Server names selected during creation of Volumes should be resolvablein the client machine. You can use appropriate /etc/hosts entries orDNS server to resolve server names to IP addresses.
Manually Mounting Volumes
- To mount a volume, use the following command:
# mount -t glusterfs HOSTNAME-OR-IPADDRESS:/VOLNAME MOUNTDIR
For example:# mount -t glusterfs server1:/test-volume /mnt/glusterfs
NoteThe server specified in the mount command is only used to fetchthe gluster configuration volfile describing the volume name.Subsequently, the client will communicate directly with theservers mentioned in the volfile (which might not even include theone used for mount).If you see a usage message like 'Usage: mount.glusterfs', mountusually requires you to create a directory to be used as the mountpoint. Run 'mkdir /mnt/glusterfs' before you attempt to run themount command listed above.
Mounting Options
You can specify the following options when using the
mount -t glusterfs
command. Note that you need to separate all optionswith commas.For example:
# mount -t glusterfs -o backupvolfile-server=volfile_server2,use-readdirp=no,volfile-max-fetch-attempts=2,log-level=WARNING,log-file=/var/log/gluster.log server1:/test-volume /mnt/glusterfs
If
backupvolfile-server
option is added while mounting fuse client,when the first volfile server fails, then the server specified inbackupvolfile-server
option is used as volfile server to mount theclient.In
volfile-max-fetch-attempts=X
Graphicriver project proposal 17770141 download free. option, specify the number ofattempts to fetch volume files while mounting a volume. This option isuseful when you mount a server with multiple IP addresses or whenround-robin DNS is configured for the server-name.If
use-readdirp
is set to ON, it forces the use of readdirpmode in fuse kernel moduleAutomatically Mounting Volumes
You can configure your system to automatically mount the Gluster volumeeach time your system starts.
The server specified in the mount command is only used to fetch thegluster configuration volfile describing the volume name. Subsequently,the client will communicate directly with the servers mentioned in thevolfile (which might not even include the one used for mount).
- To mount a volume, edit the /etc/fstab file and add the following line:
HOSTNAME-OR-IPADDRESS:/VOLNAME MOUNTDIR glusterfs defaults,_netdev 0 0
For example:server1:/test-volume /mnt/glusterfs glusterfs defaults,_netdev 0 0
Mounting Options
You can specify the following options when updating the /etc/fstab file.Note that you need to separate all options with commas.
For example:
HOSTNAME-OR-IPADDRESS:/VOLNAME MOUNTDIR glusterfs defaults,_netdev,log-level=WARNING,log-file=/var/log/gluster.log 0 0
Testing Mounted Volumes
To test mounted volumes
- Use the following command:
# mount
If the gluster volume was successfully mounted, the output of themount command on the client will be similar to this example:server1:/test-volume on /mnt/glusterfs type fuse.glusterfs (rw,allow_other,default_permissions,max_read=131072
- Use the following command:
# df
The output of df command on the client will display the aggregatedstorage space from all the bricks in a volume similar to thisexample: - Change to the directory and list the contents by entering the following:
- For example,
You can use NFS v3 to access to gluster volumes. Extensive testing hasbe done on GNU/Linux clients and NFS implementation in other operatingsystem, such as FreeBSD, and Mac OS X, as well as Windows 7(Professional and Up), Windows Server 2003, and others, may work withgluster NFS server implementation.
GlusterFS now includes network lock manager (NLM) v4. NLM enablesapplications on NFSv3 clients to do record locking on files on NFSserver. It is started automatically whenever the NFS server is run.
You must install nfs-common package on both servers and clients (onlyfor Debian-based) distribution.
This section describes how to use NFS to mount Gluster volumes (bothmanually and automatically) and how to verify that the volume has beenmounted successfully.
Using NFS to Mount Volumes
You can use either of the following methods to mount Gluster volumes:
Prerequisite: Install nfs-common package on both servers and clients(only for Debian-based distribution), using the following command:
$ sudo aptitude install nfs-common
Manually Mounting Volumes Using NFS
To manually mount a Gluster volume using NFS
- To mount a volume, use the following command:
# mount -t nfs -o vers=3 HOSTNAME-OR-IPADDRESS:/VOLNAME MOUNTDIR
For example:# mount -t nfs -o vers=3 server1:/test-volume /mnt/glusterfs
NoteGluster NFS server does not support UDP. If the NFS client you areusing defaults to connecting using UDP, the following messageappears:requested NFS version or transport protocol is not supported
.To connect using TCP - Add the following option to the mount command:
-o mountproto=tcp
For example:# mount -o mountproto=tcp -t nfs server1:/test-volume /mnt/glusterfs
To mount Gluster NFS server from a Solaris client
- Use the following command:
# mount -o proto=tcp,vers=3 nfs://HOSTNAME-OR-IPADDRESS:38467/VOLNAME MOUNTDIR
For example:# mount -o proto=tcp,vers=3 nfs://server1:38467/test-volume /mnt/glusterfs
Automatically Mounting Volumes Using NFS
You can configure your system to automatically mount Gluster volumesusing NFS each time the system starts.
To automatically mount a Gluster volume using NFS
- To mount a volume, edit the /etc/fstab file and add the following line:
HOSTNAME-OR-IPADDRESS:/VOLNAME MOUNTDIR nfs defaults,_netdev,vers=3 0 0
For example,server1:/test-volume /mnt/glusterfs nfs defaults,_netdev,vers=3 0 0
NoteGluster NFS server does not support UDP. If the NFS client you areusing defaults to connecting using UDP, the following messageappears:requested NFS version or transport protocol is not supported.
To connect using TCP - Add the following entry in /etc/fstab file :
HOSTNAME-OR-IPADDRESS:/VOLNAME MOUNTDIR nfs defaults,_netdev,mountproto=tcp 0 0
For example,server1:/test-volume /mnt/glusterfs nfs defaults,_netdev,mountproto=tcp 0 0
To automount NFS mounts
Gluster supports *nix standard method of automounting NFS mounts.Update the /etc/auto.master and /etc/auto.misc and restart the autofsservice. After that, whenever a user or process attempts to access thedirectory it will be mounted in the background.
Testing Volumes Mounted Using NFS
You can confirm that Gluster directories are mounting successfully.
To test mounted volumes
Fs 2 6 0 – Note Manager Interview Questions And Answers
- Use the mount command by entering the following:
# mount
For example, the output of the mount command on the client willdisplay an entry like the following:server1:/test-volume on /mnt/glusterfs type nfs (rw,vers=3,addr=server1)
- Use the df command by entering the following:
# df
For example, the output of df command on the client will display theaggregated storage space from all the bricks in a volume. - Change to the directory and list the contents by entering the following:
# cd MOUNTDIR
# ls
You can use CIFS to access to volumes when using Microsoft Windows aswell as SAMBA clients. For this access method, Samba packages need to bepresent on the client side. You can export glusterfs mount point as thesamba export, and then mount it using CIFS protocol.
This section describes how to mount CIFS shares on MicrosoftWindows-based clients (both manually and automatically) and how toverify that the volume has mounted successfully.
Note
CIFS access using the Mac OS X Finder is not supported, however, youcan use the Mac OS X command line to access Gluster volumes usingCIFS.
Using CIFS to Mount Volumes
You can use either of the following methods to mount Gluster volumes:
You can also use Samba for exporting Gluster Volumes through CIFSprotocol.
Exporting Gluster Volumes Through Samba
We recommend you to use Samba for exporting Gluster volumes through theCIFS protocol.
To export volumes through CIFS protocol
- Mount a Gluster volume.
- Setup Samba configuration to export the mount point of the Gluster volume.For example, if a Gluster volume is mounted on /mnt/gluster, youmust edit smb.conf file to enable exporting this through CIFS. Opensmb.conf file in an editor and add the following lines for a simpleconfiguration:
Save the changes and start the smb service using your systems initscripts (/etc/init.d/smb [re]start). Abhove steps is needed for doingmultiple mount. If you want only samba mount then in your smb.conf you need to add
Note
To be able mount from any server in the trusted storage pool, you mustrepeat these steps on each Gluster node. For more advancedconfigurations, see Samba documentation.
Manually Mounting Volumes Using CIFS
You can manually mount Gluster volumes using CIFS on MicrosoftWindows-based client machines.
To manually mount a Gluster volume using CIFS
- Using Windows Explorer, choose Tools > Map Network Drive… from the menu. The Map Network Drivewindow appears.
- Choose the drive letter using the Drive drop-down list.
- Click Browse, select the volume to map to the network drive, and click OK.
- Click Finish.
The network drive (mapped to the volume) appears in the Computer window.
Alternatively, to manually mount a Gluster volume using CIFS by going toStart > Run and entering Network path manually.
Fs 2 6 0 – Note Manager Interview Questions
Automatically Mounting Volumes Using CIFS
You can configure your system to automatically mount Gluster volumesusing CIFS on Microsoft Windows-based clients each time the systemstarts.
To automatically mount a Gluster volume using CIFS
The network drive (mapped to the volume) appears in the Computer windowand is reconnected each time the system starts.
Fs 2 6 0 – Note Manager Interview Question
- Using Windows Explorer, choose Tools > Map Network Drive… from the menu. The Map Network Drivewindow appears.
- Choose the drive letter using the Drive drop-down list.
- Click Browse, select the volume to map to the network drive, and click OK.
- Click the Reconnect at logon checkbox.
- Click Finish.
Fs 2 6 0 – Note Manager Interview Question And Answer
Testing Volumes Mounted Using CIFS
You can confirm that Gluster directories are mounting successfully bynavigating to the directory using Windows Explorer.