This action might not be possible to undo. Are you sure you want to continue?
This procedure explains how to create a CIFS share on your Celerra® system and map a drive to the share on your host or workstation.
◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆
Overview ............................................................................................... 2 Pre-implementation tasks ................................................................... 4 Implementation worksheets ............................................................... 5 Connect external network cables ....................................................... 8 Configure storage for a Fibre Channel enabled system ............... 10 Configure the network ...................................................................... 20 Create a file system ............................................................................ 21 Delete CIFS share created during startup....................................... 25 Create a new CIFS server .................................................................. 26 Join CIFS server to domain............................................................... 30 Start CIFS service ............................................................................... 31 Add a CIFS share................................................................................ 32 Map a CIFS share ............................................................................... 34 Configure and test standby relationships....................................... 35 Appendix............................................................................................. 42
Creating a CIFS share
Creating a CIFS share
To create a CIFS share, you must perform the following tasks: 1. Verify that you have performed the pre-implementation tasks: • Create a Powerlink® account. • Register your Celerra with EMC® or your service provider. • Install Navisphere® Service Taskbar (NST.) • Add additional disk array enclosures (DAEs) using the NST.
Note: Not available for NX4.
2. Complete the implementation worksheets. 3. Cable additional Celerra ports to your network system. 4. Configure unused or new disks with Navisphere Express. 5. Configure your network by creating a new interface to access the Celerra storage from a host or workstation. 6. Create a file system using a system-defined storage pool. 7. Delete the CIFS share if one was created during startup. 8. Create a new CIFS server. 9. Join the CIFS server to the domain. 10. Start the CIFS service. 11. Add a CIFS share. 12. Configure a Windows client host or workstation to access the CIFS share and map a network drive to the CIFS share. 13. Configure and test blade standby relationships
System requirements for CIFS
The following describes the requirements for configuring CIFS on the Celerra Network Server. Software Celerra Network Server version 5.6 Hardware Celerra Network Server
Creating a CIFS share
Creating a CIFS share
Network Windows 2000, Windows Server 2003, or Windows NT domain. You must configure the domains with the following:
Windows 2000 or Windows Server 2003 domains: • Active Directory • Kerberos or NT LAN Manager support • DNS (Domain Name System) server The DNS server should support dynamic updates (DDNS). If DDNS is unsupported, you must manually update the DNS server. • NTP (Network Time Protocol) server Configuring Celerra Time Services provides instructions on configuring an NTP server.
Note: If using UNIX or SHARE user authentication on the Data Mover, you do not need any of the previous elements. However, it is recommended that you do not use UNIX or SHARE user authentication methods. Instead of SHARE authentication, use NT security mode with a stand-alone CIFS server with local user support enabled.
Windows NT domain: Windows Internet Naming Service (WINS) server If your Windows NT domain spans more than one subnet, the domain must be configured with a Windows Internet Naming Service (WINS) server.
Storage No specific storage requirements
Creating a CIFS share
Creating a CIFS share
Before you begin this CIFS implementation procedure ensure that you have completed the following tasks.
Create a Powerlink account
You can set up a Powerlink account at http://Powerlink.EMC.com. Use this website to access additional EMC resources, including documentation, release notes, software updates, information about EMC products, licensing, and service. If you did not register your Celerra at the completion of the Celerra Startup Assistant (CSA), you can do so now by downloading the Registration wizard from Powerlink. The Registration wizard can also be found on the Applications and Tools CD that was shipped with your system. Registering your Celerra ensures that EMC Customer Support has all pertinent system and site information so they can properly assist you.
Register your system with EMC
Download and install the Navisphere Service Taskbar (NST) Add additional disk array enclosures
The NST is available for download from the CLARiiON® Tools page on Powerlink and on the Applications and Tools CD that was shipped with your system.
Use the NST to add new disk array enclosures (DAEs) to fully implement your Celerra.
Note: Not available for NX4.
When you have finished the “Pre-implementation tasks,” go to “Implementation worksheets” on page 5.
Creating a CIFS share
Creating a CIFS share Implementation worksheets Before you begin this implementation procedure take a moment to fill out the following implementation worksheets with the values of the various devices you will need to create. Creating a CIFS share 5 .255. You will need the following information to fill out Table 1: Does the network use variable-length subnets? ❑ Yes ❑ No Note: If the network uses variable-length subnets. Do not assume 255. This step can be repeated as needed to create additional file systems. Table 1 Create interface worksheet Maximum Transmission Unit (MTU) (optional) Virtual LAN (VLAN) identifier (optional) Data Mover number Device name or virtual device name IP address Netmask Devices (optional) Create file system worksheet The create file system step creates a file system on a Data Mover. It can also create virtual network devices: Link Aggregation.0 or other common values.255. or Ethernet Channel. be sure to provide the correct subnet mask. Create interface worksheet The New Network Interface wizard configures individual network interfaces for the Data Movers. Fail-Safe Network.
Creating a CIFS share Volume Management: ❑ Automatic (recommended) ❑ Manual Storage Pool for Automatic Volume Management: Read/Write Data Mover: ❑ server_2 ❑ server_3 ❑ CLARiiON RAID 1 (Not available for NX4.) ❑ CLARiiON RAID 5 Performance ❑ CLARiiON RAID 5 Economy ❑ CLARiiON RAID 1/0 ❑ CLARiiON RAID 6 File System Name ____________________________________________ File System Size (megabytes) __________________________________ Use Default User and Group Quotas: ❑ Yes ❑ No Hard Limit for User Storage (megabytes) ____________________ Soft Limit for User Storage (megabytes) _____________________ Hard Limit for User Files (files)_____________________________ Soft Limit for User Files (files) _____________________________ Hard Limit for Group Storage (megabytes) __________________ Soft Limit for Group Storage (megabytes) ___________________ Hard Limit for Group Files (files) ___________________________ Soft Limit for Group Files (files) ____________________________ Enforce Hard Limits: ❑ Yes ❑ No Grace Period for Storage (days)_____________________________ Grace Period for Files (days) _______________________________ Create a CIFS server worksheet You can choose to create a CIFS server as part of creating a CIFS share. You will need the following information: Data Mover: ❑ server_2 ❑ server_3 Interfaces Used by CIFS Server: _________________________________________________________ _________________________________________________________ 6 Creating a CIFS share . Make a copy of this worksheet for each CIFS server you create.
Creating a CIFS share 7 .” go to “Connect external network cables” on page 8. You will need the following information: Data Mover: ❑ server_2 ❑ server_3 File System Name ____________________________________________ CIFS Server Names ___________________________________________ CIFS Share Name ____________________________________________ Share Path ___________________________________________________ User Limit ___________________________________________________ Comment____________________________________________________ When you have finished the “Implementation worksheets. optional for Windows 2000/2003)_______________________________________ CIFS Server Names (aliases): _________________________________________________________ _________________________________________________________ Create a CIFS share worksheet The Create a CIFS share step makes a file system available to Windows clients.Creating a CIFS share CIFS Server Type: ❑ Windows NT ❑ Windows 2000/2003 Computer Name (Windows 2000/2003) ______________________ Windows Domain _________________________________________ Join the Domain: ❑ Yes ❑ No Domain Admin Username (Windows 2000/2003) _____________ Domain Admin Password (Windows 2000/2003) ______________ Organizational Unit (Windows 2000/2003) ___________________ NetBIOS Name (Required for Window NT. This step can be repeated as needed to share additional file systems.
Figure 1 shows the 4 copper Ethernet X-blade’s network ports for an NX4. Figure 2 shows the 2 copper Ethernet and 2 10 GB optical X-blade’s network ports for an NX4. and fxg0-fxg1. They are labeled cge0-cge3. and FSNs. such as Ethernet channels. Internal management module cge0 cge1 cge2 cge3 Com 1 Com 2 BE 0 BE 1 AUX 0 AUX 1 CIP-000560 Figure 1 4 copper Ethernet port X-blade Internal management module fxg0 fxg1 cge0 cge1 Com 1 Com 2 BE 0 BE 1 AUX 0 AUX 1 CNS-001256 Figure 2 2 copper Ethernet and 2 10 GB optical port X-blade Any advanced configuration of the external network ports is beyond the scope of this implementation procedure. For more information about the many network configuration options the Celerra system supports. refer to the Configuring and Managing Celerra Networking and 8 Creating a CIFS share . you will need to connect the desired blade network ports to your network system.Creating a CIFS share Connect external network cables If you have not already done so. link aggregation. They are labeled cge0-cge1.
Creating a CIFS share 9 .Creating a CIFS share Configuring and Managing Celerra Network High Availability technical modules for more information.” go to “Configure storage for a Fibre Channel enabled system” on page 10. When you have finished the “Connect external network cables.
This section details how to create additional storage for a Fibre Channel enabled integrated system using Navisphere Express. 10 Creating a CIFS share . 2.Creating a CIFS share Configure storage for a Fibre Channel enabled system There are two ways to configure additional storage in a Fibre Channel enabled system. Note: The default username is nasadmin and the default password is nasadmin. open an internet browser such as Internet Explorer or Mozilla Firefox. as shown in Figure 3 on page 11. Note: This IP address is the one that you assigned when you initialized the storage system. Configure storage with Navisphere Express Configure storage with Navisphere Express by doing the following: 1. Type the user name and password to log in to Navisphere Express. 3. Type the IP address of a storage processor of the storage system into the internet browser address bar. To start Navisphere Express.
Creating a CIFS share 11 .Creating a CIFS share Figure 3 Navisphere Express Login screen 4. To configure unused storage. select Disk Pools in the left navigation panel from the initial screen shown in Figure 4 on page 12.
Creating a CIFS share Figure 4 Manage Virtual Disks screen Note: If you are trying to create a new virtual disk (LUN) for Automatic Volume Management (AVM) to use in a stripe with existing virtual disks. 5. 12 Creating a CIFS share . as shown in Figure 5 on page 13. Click Create New Disk Pool. Find the information on the existing virtual disks by going to the details page for each virtual disk by selecting Manage > Virtual Disks > <Existing_Virtual_Disk_Name>. Record the MB value of the existing virtual disks and use this value as the size for any new virtual disk. the new virtual disk must match the size of the existing virtual disks.
• The RAID Group Type values should be applicable to your system. All virtual disks that you create on a disk pool are automatically assigned to the same SP as the disk pool. as shown in Figure 6 on page 14. 6. Disk Pool 4 to SP B. The software assigns each disk pool that you create to an SP as follows: Disk Pool 1 to SP A. etc. Disk Pool 3 to SP A. Disk Pool 2 to SP B. Creating a CIFS share 13 . If you create only one disk pool on the storage system. all virtual disks on the storage system are assigned to SP A and all data received. or sent. goes through SP A. Select the RAID group type for the new disk pool.Creating a CIFS share Figure 5 Manage Disk Pools screen Note: You should create at least two disk pools.
as shown in Figure 6.com. Select the disk pool just created. Figure 6 Create Disk Pool screen 7. 9. 10. see NAS Support Matrix document on http://Powerlink. Click Apply.EMC. as shown in Figure 6. Note: RAID5 is recommended. Click Create a virtual disk that can be assigned to a server. 8. 14 Creating a CIFS share . Select the disks in the Disk Processor Enclosure to include in the new disk pool.Creating a CIFS share • For more information.
Type the Name for the new virtual disk(s). and select its Capacity and the Number of Virtual Disks to create.Creating a CIFS share 11. Figure 7 Create Virtual Disks screen 12. Note: It is recommended that virtual disk capacity not be larger than 2 TB. as shown in Figure 7. as shown in Figure 7 on page 15. Assign a server to the virtual disk(s) by using the Server list box. Creating a CIFS share 15 .
as shown in Figure 8. 14. Verify the virtual disk server assignment. 13.Creating a CIFS share Note: To send data to or receive data from a virtual disk. by looking under Assigned To on the Manage Virtual Disks page. This may take some time depending on the size of the virtual disks. Select Virtual Disks from the left navigation panel. 16 Creating a CIFS share . Click Apply to create virtual disk(s). 15. to verify the creation of the new virtual disk(s). you must assign a server to the virtual disk. Note: The system now creates the virtual disks.
Celerra Manager must be used. To make the new virtual disks (LUNs) available to the Celerra system. 17. Launch the Celerra Manager by opening Celerra Manager using the following URL: https://<control_station> Where <control_station> is the hostname or IP address of the Control Station. click Yes to proceed. Creating a CIFS share 17 .Creating a CIFS share Figure 8 Verify new virtual disk assignment 16. If a security alert appears about the system’s security certificate.
Creating a CIFS share 18. click Yes to accept the certificate. 19. 20. If a security warning appears about the system’s security certificate being issued by an untrusted source. click Yes. If a warning about a hostname mismatch appears. Figure 9 Rescan Storage System in Celerra Manager 18 Creating a CIFS share . At the login prompt. The default password is nasadmin. as shown in Figure 9 on page 18. On the Celerra > Storage Systems page. log in as user root. click Rescan. 21.
Creating a CIFS share 19 . When you have finished the “Configure storage for a Fibre Channel enabled system. The user virtual disks (LUNs) are now available for the Celerra system.” go to “Configure the network” on page 20. This may cause data loss or unavailability.Creating a CIFS share ! CAUTION Do not change the host LUN (virtual disk) identifier of the Celerra LUNs (virtual disks) after rescanning.
Creating a CIFS share Configure the network Using Celerra Manager. 2. Once you have completed the New Network Interface wizard and successfully created a new network interface and an optional new virtual device. go to “Create a file system” on page 21. you can create interfaces on devices that are not part of a virtual device. if desired. Click New Network Interface wizard to set up a new network interface. 3. configure a new network interface and device by doing the following: 1. Host or workstation access to the Celerra storage is configured by creating a network interface. Log in to Celerra Manager as root. 20 Creating a CIFS share . Note: On the Select/Create a network device page. The new virtual device can be configured with one of the following high-availability features: Ethernet Channel. Link Aggregation. Click Celerras > <Celerra_name> > Wizards. In Celerra Manager. Note: You cannot create a new interface for a Data Mover while the Data Mover is failed over to its standby. or Fail-Safe Network. click Create Device to create a new virtual network device. This wizard can also be used to create a new virtual device.
as shown in Figure 10. Creating a CIFS share 21 . Figure 10 File Systems screen 3. Click New at the bottom of the File Systems screen. do the following steps: 1.Creating a CIFS share Create a file system To create a new file system. Select the Storage Pool radio button to select what the file system will be created from. as shown in Figure 11 on page 22. 2. Go to Celerras > <Celerra_name> > File Systems tab in the left navigation menu.
For more information about system-defined storage pools refer to “Appendix” on page 42. Note: Based on the disks and the RAID types created in the storage system. different system-defined storage pools will appear in the storage pool list. 6. Select the system-defined storage pool from the Storage Pool drop-down menu.Creating a CIFS share Figure 11 Create new file system 4. Designate the Storage Capacity of the file system and select any other desired options. Name the file system. 22 Creating a CIFS share . 5.
File systems can be enabled with FLR capability only at creation time. the file system automatically extends when the high water mark is reached. Creating a CIFS share 23 . as shown in Figure 12 on page 24. • File-level Retention (FLR) Capability: If enabled. The new file system will now appear on the File Systems screen. 7.Creating a CIFS share Other file system options are listed below: • Auto Extend Enabled: If enabled. it is persistently marked as an FLR file system until it is deleted. • Virtual Provisioning Enabled: This option can only be used with automatic file system extension and together they let you grow the file system as needed. Click Create.
24 Creating a CIFS share .” go to “Delete CIFS share created during startup” on page 25.Creating a CIFS share Figure 12 File Systems screen with new file system When you have finished the “Create a file system.
select the desired Data Mover. click OK. and select Unjoin Domain on the CIFS Server Properties page. When you have finished the “Delete CIFS share created during startup. Select Celerras > <Celerra_name> > CIFS. 3. Creating a CIFS share 25 . and click the CIFS Shares tab. To delete the CIFS server: a. and click the CIFS Servers tab. b. Double-click the server. and click the CIFS Servers tab.” go to “Create a new CIFS server” on page 26. b. delete the CIFS share created during startup. To delete the CIFS share created during startup and make the file system unavailable to CIFS users on the network: a. The Confirm Delete page appears. Select the NetBIOS name of the CIFS server to delete and click Delete. c. d. 2. When the Confirm Delete page appears. c. and click Delete. Select one or more shares to remove. then you can begin to use this share as a production share. Click OK. Select Celerras > <Celerra_name> > CIFS. If you have more than five disks. c. In the Show CIFS Servers list. To unjoin the CIFS server from the domain (and hence. Click OK. the CIFS users on the network): a. 1. If you have a minimum configuration of five or less disks. Select Celerras > <Celerra_name> > CIFS. The interfaces configured for any deleted server are automatically assigned to the default CIFS server for that Data Mover. b.Creating a CIFS share Delete CIFS share created during startup You may have optionally created a CIFS share using the Celerra Startup Assistant (CSA).
Using International Character Sets with Celerra technical module on the Celerra Network Server User Information CD. If the Data Mover has those systems mounted. Unicode is enabled if its option is selected and unavailable.Creating a CIFS share Create a new CIFS server Create a new CIFS server on a Data Mover. A Data Mover can host many instances of a CIFS server. To set Unicode support. Unicode support must be enabled on the Data Mover before any Windows 2000 server or Windows Server 2003 can be created on that Data Mover. you cannot disable it. If you are creating a Windows 2000 server or Windows Server 2003. To create a new CIFS server: 1. check that Unicode is enabled on the Data Mover. If Unicode is enabled. However. Note: For Kerberos authentication. Unicode can be enabled using the uc_config command and through the Set Up Celerra wizard on the Celerra Manager. Each instance is referred to as a CIFS server. select Celerras > <Celerra_name> > CIFS. 26 Creating a CIFS share . You cannot disable it. ASCII-based file and directory name encoding is enabled by default. When software is installed in a new Celerra Network Server. you might also need to customize the settings of the translation configuration files before enabling Unicode. Select the Data Mover in the Show CIFS Configuration list box. check that it does not have any non-US-ASCII (7-bit ASCII) file systems mounted on it because these file systems will become unusable. EMC strongly recommends that you enable Unicode character encoding if you have CIFS clients. and click the Configuration tab. Before you enable Unicode on a Data Mover. To do so. you must first perform Unicode conversion on these file systems using the command line interface. proceed with step 2. provides the instructions. select the Enable Unicode option. depending on your environment. ! CAUTION After you enable Unicode on a Data Mover.
In the Set Local Admin Password field. type the domain administrator's username and password and specify the Windows Active Directory Organizational Unit in which the CIFS server is to be registered. you can join the domain later through the CIFS Server Properties page. A Data Mover can have only one default CIFS server. 4. you can create and delete a default CIFS server. it automatically becomes the default CIFS server on the Data Mover and uses all interfaces not assigned to other CIFS servers. The CIFS: New CIFS Server page appears. Select Celerras > <Celerra_name> > CIFS. To enable local user support on the server. select the Join the domain option. To join the domain. type the name of the domain to join. In the Creating a CIFS share 27 . If you do not join the domain upon server creation. On the CIFS Servers page. type a password for the local administrator account. For Windows 2000 or Windows Server 2003 go to step 6. click New. 3. When you create a CIFS server without any interfaces.Creating a CIFS share 2. c. select the Enable local users option. for Windows NT server go to step 7. Online help describes the fields and requested information. Select the server type and complete the tasks for the appropriate server type. b. For Windows 2000 or Windows Server 2003. complete the following: a. At any time. and for stand-alone server go to step 8. type the computer name. In the Domain field. 6. In the Choose Data Mover field. To join the domain immediately. and go to step 9. and click the CIFS Servers tab. You must create all other CIFS servers with one or more interfaces. d. 5. e. Note: You cannot create a default CIFS server on a Data Mover that has a virtual Data Mover (VDM) on it. In the Windows 2000 Computer Name field. select the Data Mover on which you want to create the CIFS server.
type the name of the local workgroup of which the server will be a part. b. 10. In the Workgroup field. the system uses the first 15 characters of the computer name as the NetBIOS name. In the NetBIOS Name field. For a stand-alone server. complete the following: a. b. type a NetBIOS name that is unique within the domain. 7. 8. type a password for the local administrator account on the server. In the NetBIOS Name field. If it is left blank. In the Domain field. Because aliases act as secondary names. type a NetBIOS name for the server. "Understanding local user support" online help provides more information. c.Creating a CIFS share Confirm Admin Password field. In the Set Local Admin Password field. select the Enable local users option and type a password for the local administrator account in the Set Local Admin Password field. complete the following: a. "Understanding local user support" online help provides more information. For a Windows NT server. type the name of the Windows NT domain that the server will join. retype the password. In the Confirm Admin Password field. In the Aliases field. c. select Celerras > <Celerra_name>> Network. type one or more alternative names for the server and separate each with a comma. and click the Interfaces tab. You can assign aliases to NetBIOS names and computer names. 28 Creating a CIFS share . this field is optional. confirm the password by retyping it. Note: For Windows 2000 servers and Windows Server 2003. To enable local user support on the server. Select one or more interfaces for the server. alternate identities for a given resource. Aliases provide multiple. 9. the aliases share the same set of local groups and shares as the primary NetBIOS name or computer name. Confirm the password by retyping it in the Confirm Admin Password field. To create interfaces.
you must specify an interface. For a stand-alone server with VDMs. 11. When you have finished the “Create a new CIFS server.Creating a CIFS share Note: Always specify an interface for a stand-alone server. Creating a CIFS share 29 .” go to “Join CIFS server to domain” on page 30. Click OK.
Select Check to join domain. 2. 3. Online help describes the fields and requested information.” go to “Start CIFS service” on page 31.Creating a CIFS share Join CIFS server to domain To join the CIFS server to the domain: 1. When you have finished the “Join CIFS server to domain. 30 Creating a CIFS share . Select Celerras > <Celerra_name> > CIFS. The CIFS Server Properties page appears. Click the CIFS Servers tab and double-click the NetBIOS name. type the domain’s administrator username and password and the server’s organizational unit within that domain.
” go to “Add a CIFS share” on page 32. 2. This service runs on the Data Mover and presents shares on a network and on Windows-based computers. Select Celerras > <Celerra_name> > CIFS > Configuration page. and click Apply. select the CIFS Service Started option.Creating a CIFS share Start CIFS service To start the CIFS service on the Data Mover: 1. Select the Data Mover or VDM (virtual Data Mover). Creating a CIFS share 31 . When you have finished the “Start CIFS service.
in which case the limit is 80 characters. Select Celerras > <Celerra_name> > CIFS. the actual length of a share name in characters depends on the dialect. 32 Creating a CIFS share . type the name by which the directory will be shared on the network. and click New. You may also delete the contents of this box and type a new.Creating a CIFS share Add a CIFS share To create a CIFS share and make an existing file system available to CIFS clients: 1. The list presents the root paths of all the file systems and checkpoints available on the selected Data Mover. In the Choose Data Mover list box. 4. You can use a share name that is in use on another Data Mover. In the File System list box. Share names are case-sensitive and can only contain ASCII characters. Online help describes the fields and requested information. Some Unicode languages require more than one UTF-8 character for a Unicode character (byte). The CIFS: New CIFS Share page appears. select the file system or checkpoint that contains the directory to be shared. a Japanese character may require three UTF-8 characters. complete path. To share a subdirectory. Share names can contain spaces and other non-alphanumeric characters. For example. E-Lab™ Interoperability Navigator provides additional limitations. 5. The Path field displays the path to the root of the file system by default. A share name cannot include the following characters: /\" Share name length is limited to 12 characters unless Unicode support is enabled. select a Data Mover from which to share the file system. Note: With Unicode enabled. click the CIFS Shares tab. but must be enclosed by quotes if spaces are used. 3. This path must already exist. 2. add the rest of the path to the string in the field. In the CIFS Share Name field.
leave blank. the share becomes available only on the selected servers.” go to “Map a CIFS share” on page 34. or click Apply to create the share and remain on the New CIFS Share page. type the number of users allowed to access the share simultaneously. Select the CIFS servers on which to make the share available. 8. In the User Limit field. If you select one or more servers. Creating a CIFS share 33 . ("File system mounts" online help provides more details on mounting file systems. In the Comment field. 9. When you have finished the “Add a CIFS share. 7. If you do not select any CIFS servers.Creating a CIFS share Any single path on a file system can be shared on two or more Data Movers. Character limit is 256. To allow an unlimited number of users.) 6. the share becomes available on all CIFS servers. Do not type zero. but can be shared only once on the same Data Mover. type an optional description of the share. Click OK to create the share and return to the CIFS Shares page.
Log in to a Windows client computer connected to the same subnet as the NX4 system.com. Some of these steps depend on the network where the system is configured. 4.EMC. 5.Creating a CIFS share Map a CIFS share This step walks you through mapping a network drive to the CIFS share on a Windows client host or workstation that is on the network of the NX4 system. Enter the following command and press Enter: \\<CIFS_NetBios_or_Computer_name>\<CIFS_share_name> A Windows Explorer window opens to the new CIFS share. Click Start > Run on the Windows desktop. For a Windows NT CIFS server. perform the following: 1. 2. For a Windows 2000/2003 CIFS server. 3. you can map a network drive to this share by assigning a drive letter to the share. To map a CIFS share. Using Window management tools. For more information. see the Configuring CIFS on Celerra technical module on http://Powerlink. you must add the computer name to the domain controller under /users and computers/. you must verify that the domain controller can see the computer name for the Data Mover. 34 Creating a CIFS share .
storage identity (controlled file systems). EMC recommends a minimum of one standby blade for up to three Primary blades. To configure a failover blade: 1. 2. Creating a CIFS share 35 . Select <Celerra_name> > Data Movers > <desired_primary_blade> from the left-hand navigation panel. Define the standby configuration using Celerra Manager following the blade standby configuration recommendation: a. On the Data Mover Properties screen. b. This is because the standby blade will assume the faulted primary blade’s network identity (NIC IP and MAC addresses). Configure a standby relationship A blade must first be configured as a standby for one or more primary blades to act as a standby blade. configure the standby blade for the selected primary blade by checking the box of the desired Standby Mover and define the Failover Policy. and service identity (controlled shares and exports). When a primary blade fails over to a standby. the standby blade assumes the identity and functionality of the failed blade and functions as the primary blade until the faulted blade is healthy and manually failed back to functioning as the primary blade. Determine the ideal blade failover configuration for the Celerra system based on site requirements and EMC recommendations. ! CAUTION The standby blade(s) must have the same network capabilities (NICs and cables) as the primary blades with which it will be associated.Creating a CIFS share Configure and test standby relationships EMC recommends that multi-blade Celerra systems be configured with a Primary/Standby blade failover configuration to ensure data availability in the case of a blade (server/Data Mover) fault. Creating a standby blade ensures continuous access to file systems on the Celerra Unified Storage system.
It is recommended that the Failover Policy be set to auto. Click Apply. Note: The blade configured as standby will now reboot. 36 Creating a CIFS share .Creating a CIFS share Figure 13 Configure a standby in Celerra Manager Note: A failover policy is a predetermined action that the Control Station invokes when it detects a blade failure based on the failover policy type specified. c.
Fail Safe Network. Also. do the following: 1. Open a SSH session to the Control Station with an SSH client like PuTTY using the CS. Creating a CIFS share 37 . Change to the root user by entering the following command: su root Note: The default password for root is nasadmin. etc). To test the failover configuration. If configured network ports are left un-cabled when a failover occurs. and switch configuration (VLAN configuration. High Availability. access to files systems will be disrupted. the names of the blades. Log in to the CS as nasadmin. network configurations (EtherChannel. ! CAUTION You must cable the failover blade identically to its primary blade. the type column designates the blade type as 1 (primary) and 4 (standby). the blades must have the same network connections (Ethernet and Fibre Cables). the Celerra is able to transfer functionality from the primary blade to the standby blade without disrupting file system availability For a standby blade to successfully stand-in as a primary blade. When a failover condition occurs. Collect the current names and types of the system blades: # nas_server -l Sample output: id type 1 1 2 4 acl slot groupID state name 1000 2 0 server_2 1000 3 0 server_3 Note: In the command output above provides the state name. 3. Repeat for each primary blade in the Primary/Standby configuration. Test the standby configuration It is recommended that the functionality of the blade failover configuration be tested prior to the system going into production.Creating a CIFS share d. 2. and so forth).
Creating a CIFS share 4. In the example above.server_3 server_3 : renamed as server_2 Note: This command will rename the primary and standby blades. server_2..done failover activity complete commit in progress (not interruptible). was rebooted and renamed server_2.. the primary blade.. monitor this traffic by entering: # server_netstat <server_name> -i Example: [nasadmin@rtpplat11cs0 ~]$ server_netstat server_2 -i Name Mtu Ibytes Ierror Obytes Oerror PhysAddr **************************************************************************** fxg0 fxg1 mge0 mge1 cge0 cge1 9000 9000 9000 9000 9000 9000 0 0 851321 28714095 614247 0 0 0 0 0 0 0 0 0 812531 1267209 2022 0 0 0 0 0 0 0 0:60:16:32:4a:30 0:60:16:32:4a:31 0:60:16:2c:43:2 0:60:16:2c:43:1 0:60:16:2b:49:12 0:60:16:2b:49:13 5. Manually force a graceful failover of the primary blade to the standby blade by using the following command: # server_standby <primary_blade> -activate mover Example: [nasadmin@rtpplat11cs0 ~]$ server_standby server_2 -activate mover server_2 : server_2 : going offline server_3 : going active replace in progress . After I/O traffic is running on the primary blade’s network port(s).server_3 and server_3 was renamed as server_2. 38 Creating a CIFS share .faulted..faulter.done server_2 : renamed as server_2.
Verify that the blades appear with reason code 5 by typing. retains the initial name. Checking that the blades have changed names and types: # nas_server -l Sample output: id type 1 1 2 1 acl slot groupID state name 1000 2 0 server_2. thus reflecting that the failover completed successfully.Creating a CIFS share 6. 7. Sample output: [nasadmin@rtpplat11cs0 ~]$ server_netstat server_2 -i Name Mtu Ibytes Ierror Obytes Oerror PhysAddr **************************************************************************** fxg0 9000 0 0 0 0 0:60:16:32:4b:18 fxg1 9000 0 0 0 0 0:60:16:32:4b:19 mge0 9000 14390362 0 786537 0 0:60:16:2c:43:30 mge1 9000 16946 0 3256 0 0:60:16:2c:43:31 cge0 9000 415447 0 3251 0 0:60:16:2b:49:12 cge1 9000 0 0 0 0 0:60:16:2b:48:ad Note: The WWNs in the PhysAddr column have changed. Verify that the failover has completed successfully by: a. b.faulted.server_3 1000 3 0 server_2 Note: In the command output above each blade’s state name has changed and the type column designates both blades as type 1 (primary). though physically a different blade. Checking I/O traffic is flowing to the primary blade by entering: # server_netstat <server_name> -i Note: The primary blade. # /nas/sbin/getreason Creating a CIFS share 39 .
faulter. server_2.server_3 : renamed as server_2 Note: This command will rename the primary and standby blades. After the blades appear with reason code 5. Checking that the blades have changed back to the original name and type: # nas_server -l Sample output: id type 1 1 2 4 acl slot groupID state name 1000 2 0 server_2 1000 3 0 server_3 40 Creating a CIFS share . 9.. In the example above.Creating a CIFS share 8. was rebooted and renamed server_3 and server_2.faulted.done server_2 : renamed as server_3 server_2.faulted..server_3 was renamed as server_2.server_3 : going active replace in progress . Verify that the failback has completed successfully by: a.done failover activity complete commit in progress (not interruptible).. the standing primary blade.. manually restore the failed over blade to its primary status by typing the following command: # server_standby <primary_blade> -restore mover Example: server_standby server_2 -restore mover server_2 : server_2 : going standby server_2.
com for more information about determining and defining blade standby configurations. Checking I/O traffic flowing to the primary blade by entering: # server_netstat <server_name> -i Sample output: [nasadmin@rtpplat11cs0 ~]$ server_netstat server_2 -i Name Mtu Ibytes Ierror Obytes Oerror PhysAddr **************************************************************************** fxg0 fxg1 mge0 mge1 cge0 cge1 9000 9000 9000 9000 9000 9000 0 0 851321 28714095 314427 0 0 0 0 0 0 0 0 0 812531 1267209 1324 0 0 0 0 0 0 0 0:60:16:32:4a:30 0:60:16:32:4a:31 0:60:16:2c:43:2 0:60:16:2c:43:1 0:60:16:2b:49:12 0:60:16:2b:49:13 Note: The WWNs in the PhysAddr column have reverted to their original values. Refer to the Configuring Standbys on EMC Celerra technical module http://Powerlink.EMC. Creating a CIFS share 41 .Creating a CIFS share b. thus reflecting that the failback completed successfully.
Disk group and disk volume configurations Disk group type RAID 5 8+1 Attach type Fibre Channel Storage profile clar r5 economy (8+1) clar_r5_performance (4+1) clar_r5_performance clar_r1 clar_r5_performance clar_r1 clar_r6 Table 2 RAID 5 4+1 RAID 1 RAID 5 4+1 RAID 1 RAID 6 4+2 RAID 6 12+2 RAID 5 6+1 RAID 5 4+1 (CX3 only) RAID 3 4+1 RAID 3 8+1 RAID 6 4+2 RAID 6 12+2 RAID 5 6+1 (CX3 only) RAID 5 4+1 (CX3 only) RAID 3 4+1 RAID 3 8+1 Fibre Channel Fibre Channel Fibre Channel Fibre Channel ATA ATA clarata_archive clarata_archive ATA clarata_r3 ATA clarata_r6 LCFC clarata_archive LCFC clarata_archive LCFC clarata_r3 42 Creating a CIFS share .Creating a CIFS share Appendix This appendix describes the disk group and disk volume configurations. Disk group and disk volume configurations Table 2 maps a disk group type to a storage profile. The storage profile name is a set of rules used by AVM to determine what type of disk volumes to use to provide storage for the pool. associating the RAID type and the storage space that results in the automatic volume management (AVM) pool.
Creating a CIFS share Disk group type RAID 6 4+2 RAID 6 12+2 RAID 5 2+1 RAID 5 3+1 RAID 5 4+1 RAID 5 5+1 RAID 1/0 (2 disks) RAID 6 4+2 RAID 5 2+1 RAID 5 3+1 RAID 5 4+1 RAID 5 5+1 RAID 1/0 (2 disks) RAID 6 4+2 Attach type LCFC Storage profile clarata_r6 SATA SATA SATA SATA SATA SATA SAS SAS SAS SAS SAS SAS clarata_archive clarata_archive clarata_archive clarata_archive clarata_r10 clarata_r6 clarsas_archive clarsas_archive clarsas_archive clarsas_archive clarsas_r10 clarsas_r6 Creating a CIFS share 43 .
Creating a CIFS share 44 Creating a CIFS share .
This action might not be possible to undo. Are you sure you want to continue?