Table Of Contents
Cisco WAFS Quick Installation and Configuration Note, Release 3.0
Overview of WAFS
WAFS Network System Parameters
Network Setup Overview
Unpacking the Hardware
Connecting and Powering On the System
Cisco File Engine 511 and Cisco Wide Area Application Engine 511
Cisco Wide Area Application Engine 611
Cisco Wide Area Application Engine 7326
Cisco Network Module NM-CE-BP-80G-K9
Configuring the Network Interface
Configuring the Network Interface on a Cisco Appliance
Configuring the Network Interface on a Network Module
Accessing the Setup Wizard
Configuring the Core FE Using the Setup Wizard
Configuring the Edge FE
Configuring WCCP on the Edge FE (Optional)
Configuring the Edge FE with the Setup Wizard
Launching the WAFS Central Manager
Distributing Licenses
Defining a New Connection
Updating the File Engines
Starting File Engine Components
Client-to-Edge FE Connection
Accessing an Edge FE Through a Mapped Drive (Windows Only)
Accessing an Edge FE Through UNC Pathing (Windows Only)
Mounting a UNIX Shared Directory
Obtaining Technical Assistance
Cisco Technical Support & Documentation Website
Submitting a Service Request
Definitions of Service Request Severity
Documentation Feedback
Cisco WAFS Quick Installation and Configuration Note, Release 3.0
This document provides step-by-step instructions for setting up a Wide Area File Services (WAFS) network. Use this document in either of the following situations:
•
You are installing and configuring your WAFS network for the first time.
•Your network is already installed, but there is a problem (for example, the network does not boot or the software is corrupted). If you have a backup of the configuration, use that to restore your settings. If you do not have a backup, reinstall the WAFS software, which takes about 7 minutes. See the "Accessing the Setup Wizard" section and follow the instructions in this document to reconfigure your WAFS network.
If your WAFS network is already installed and you want to upgrade the WAFS software to a newer release, refer to the Cisco WAFS User Guide, Release 3.0 for upgrade instructions. The user guide also covers how to perform a rollback to a previous software release.
Note Cisco WAFS 3.0 uses both the WAFS Manager GUI and the WAFS CLI to configure the various features. The GUI instructions are in this user guide. Refer to the Cisco WAFS Software Configuration Guide, Release 3.0 for CLI instructions.
This document contains the following sections:
•Overview of WAFS
•WAFS Network System Parameters
•Network Setup Overview
•Unpacking the Hardware
•Connecting and Powering On the System
•Configuring the Network Interface
•Accessing the Setup Wizard
•Configuring the Core FE Using the Setup Wizard
•Configuring the Edge FE
•Launching the WAFS Central Manager
•Client-to-Edge FE Connection
Note The Cisco WAFS 3.0 software can run on dedicated Cisco appliances such as the WAE-511 and on the network module NM-CE-BP-80G-K9 connected to specific Cisco routers. The term File Engine (or FE) is used in textual descriptions and in the example windows to refer to these hardware platforms.
Overview of WAFS
Cisco WAFS facilitates the consolidation of all branch-office data into central file servers that reside at the data center. WAFS overcomes WAN latency and bandwidth limitations so users at branch offices can experience LAN-like speeds when accessing centralized files over the WAN. Figure 1 shows a common deployment scenario for WAFS with the Cisco File Engine components.
Figure 1 Wide-Area File Services Solution with Cisco File Engines
Cisco WAFS includes ready-to-use appliances with the following components:
•The Cisco Edge File Engine resides at each branch office or remote campus, replacing file and print servers and giving local clients fast, LAN-like read and write access to a cached view of the centralized files.
•The Cisco Core File Engine resides at the data center and connects directly to one or more file servers or network attached storage (NAS) gateways, performing WAN-optimized file requests for the remote Edge File Engines.
•The Cisco WAFS Central Manager provides remote management and monitoring of all the File Engines.
The Cisco WAFS software runs on the Cisco FE-511, Cisco WAE-511, Cisco WAE-611, and Cisco WAE-7326 appliance, as well as network module NM-CE-BP-80G-K9. A File Engine can be configured to be an Edge File Engine, a Core File Engine, or a WAFS Central Manager. Each of these File Engine components can also run concurrently on the same appliance if resources and capacity are sized appropriately. For example, a File Engine can be configured both as a Core File Engine and a WAFS Central Manager for smaller deployments. For larger deployments, the various components should be run on separate appliances.
WAFS Network System Parameters
Table 1 specifies the different parameters and data needed to set up and configure the WAFS network. For your convenience, you can enter your values in the table and refer back to it when configuring the WAFS network.
Table 1 WAFS Network System Parameters
Parameter
|
Data Center Values (Core FE)
|
Branch Office Values (Edge FE)
|
Interface speed
|
|
|
Duplex mode
|
|
|
IP address*
|
|
|
Subnet mask*
|
|
|
Default gateway*
|
|
|
DNS server 1
|
|
|
DNS server 2
|
|
|
DNS domain
|
|
|
WINS server
|
|
|
WAFS File Engine
(Host name)
|
|
|
Windows domain controller
|
|
|
Windows file server
|
|
|
UNIX file server
|
|
|
Windows clients
|
|
|
UNIX clients
|
|
|
Windows domain
|
|
|
* When WAFS runs on network module NM-CE-BP-80G-K9, these parameters must be configured from the host router and will appear as read-only in the Setup Wizard.
Network Setup Overview
The following sections describe how to set up a network similar to the one shown in Figure 1. For some hardware details, you may need to refer to the Cisco File Engine 511 Hardware Installation Guide, the Cisco Wide Area Application Engine 511 and 611 Hardware Installation Guide, or the Cisco Wide Area Application Engine 7326 Hardware Installation Guide.
For additional software information, you may need to refer to the Cisco WAFS Software Configuration Guide, Release 3.0 and the Cisco WAFS User Guide, Release 3.0.
To set up a network similar to the one shown in Figure 1, perform the steps in the following sections:
•Unpacking the Hardware
•Connecting and Powering On the System
•Configuring the Network Interface
•Accessing the Setup Wizard
•Configuring the Core FE Using the Setup Wizard
•Configuring WCCP on the Edge FE (Optional)
•Configuring the Edge FE
•Launching the WAFS Central Manager
•Client-to-Edge FE Connection
Unpacking the Hardware
Before you install the WAFS File Engine on your local area network, verify that you have all of the following items:
•CD-ROM containing WAFS application software and the license key file
•Serial console cable
•Power cord
•Rack-mounting kit
•Regulatory Compliance and Safety Information for the Cisco Content Networking Product Series documentation
Note Additional cables and other items may be included in the accessory kit, but they are not required for installing and configuring your WAFS network.
To unpack the hardware, follow these steps:
Step 1 Open the carton and remove the File Engine.
Step 2 Remove the Ethernet serial cable (blue).
Step 3 Follow the mounting instructions in the included pamphlet if you are rack-mounting the File Engine.
Note By default, Cisco WAFS is designed to work with Ethernet networks. If a different network architecture is being used, such as Token Ring, contact Cisco Technical Support for further instructions.
Connecting and Powering On the System
This section contains procedures for connecting the three File Engines that run the WAFS software:
•Cisco File Engine 511 and Cisco Wide Area Application Engine 511
•Cisco Wide Area Application Engine 611
•Cisco Wide Area Application Engine 7326
•Cisco Network Module NM-CE-BP-80G-K9
Cisco File Engine 511 and Cisco Wide Area Application Engine 511
Figure 2 shows the system back-end connectors on the rear panel of a Cisco File Engine 511 or a Cisco Wide Area Application Engine 511.
Figure 2 System Back-End Connectors on a Cisco FE 511 or a Cisco WAE 511
1
|
AC power receptacle
|
5
|
Onboard video port
|
2
|
Keyboard port
|
6
|
Ethernet 1 receptacle (network)
|
3
|
Mouse port
|
7
|
Ethernet 2 receptacle
|
4
|
Serial port
|
|
|
To connect and power on the Cisco FE 511 or Cisco WAE 511, follow these steps referring to Figure 2:
Step 1 Connect the AC power cable to the power socket on the left side of the rear panel of the File Engine (1). Connect the other end of the cable to a grounded power supply.
Step 2 Connect one end of the serial console cable to the serial port (4). Connect the other end of the serial console cable to the serial port on the installation console.
Step 3 Connect one end of the straight-through Ethernet cable to the network port located at the back of the File Engine (6). The other end of this cable should be connected to your local network.
Step 4 Press the On switch on the front panel of the Cisco FE 511 or Cisco WAE 511 to power it up.
Cisco Wide Area Application Engine 611
Figure 3 shows the system back-end connectors on a Cisco Wide Area Application Engine 611.
Figure 3 System Back-End Connectors on a Cisco WAE 611
1
|
AC power receptacle
|
5
|
Onboard video port
|
2
|
Keyboard port
|
6
|
Ethernet 1 receptacle (network)
|
3
|
Mouse port
|
7
|
Ethernet 2 receptacle
|
4
|
Serial port
|
|
|
To connect and power on the Cisco WAE 611, follow these steps referring to Figure 3:
Step 1 Connect the AC power cable to the power socket on the left side of the rear panel of the File Engine (1). Connect the other end of the cable to a grounded power supply.
Step 2 Connect one end of the serial console cable to the serial port (4). Connect the other end of the serial console cable to the serial port on the installation console.
Step 3 Connect one end of the straight-through Ethernet cable to the network port located at the back of the File Engine (6). The other end of this cable should be connected to your local network.
Step 4 Press the On switch on the front panel of the Cisco WAE 611 to power it up.
Cisco Wide Area Application Engine 7326
Figure 4 shows the system back-end connectors on a Cisco Wide Area Application Engine 7326.
Figure 4 System Back-End Connectors on a Cisco WAE 7326
1
|
Serial connector
|
8
|
Ethernet 1 (network)
|
2
|
Mouse connector
|
9
|
Remote Supervisor Adapter II SlimLine Ethernet
|
3
|
Keyboard connector
|
10
|
Advanced System Management (ASM) adapter
|
4
|
Video connector
|
11
|
Advanced System Management (ASM) adapter
|
5
|
USB 1 (not supported)
|
12
|
SCSI1 connector
|
6
|
USB2 2 (not supported)
|
13
|
AC power receptacles
|
7
|
Ethernet 2
|
14
|
AC power receptacles
|
To connect and power on the Cisco WAE 7326, follow these steps referring to Figure 4:
Step 1 Connect the AC power cable to the power socket (13 or 14) on the right side of the rear panel of the File Engine. Connect the other end of the cable to a grounded power supply.
Step 2 Connect one end of the serial console cable to the serial port (3). Connect the other end of the serial console cable to the serial port on the installation console.
Step 3 Connect one end of the straight-through Ethernet cable to the network port located at the back of the File Engine (8). The other end of this cable should be connected to your local network.
Step 4 Press the On button on the front panel of the Cisco WAE 7326 to power it up.
Cisco Network Module NM-CE-BP-80G-K9
For information on how to connect and power on Cisco network module NM-CE-BP-80G-K9 running WAFS, refer to the Cisco Network Modules Hardware Installation Guide.
Configuring the Network Interface
This section described how to configure the network interface of your File Engine. Your File Engine can either run on a Cisco network module or on a Cisco appliance like the Cisco WAE-511. For more information, refer to the following topics:
•Configuring the Network Interface on a Cisco Appliance
•Configuring the Network Interface on a Network Module
Configuring the Network Interface on a Cisco Appliance
To configure the network interface of a File Engine that resides on a Cisco appliance like the WAE 511, you must connect to the File Engine using a console as described in the "Connecting and Powering On the System" section. You then assign the File Engine an IP address and associated information. If the File Engine has already been configured to appear on your network, you can skip to the "Accessing the Setup Wizard" section.
If you are connecting to the File Engine using a PC as the console, the PC must have some type of terminal emulation software installed. The terminal emulation software should be configured with the following parameters:
•9600 baud
•8 data bits
•No parity bits
•1 stop bit
To configure the network interface, follow these steps:
Step 1 When the File Engine boots, you are prompted to run the first-time setup script (enter basic configuration), which you use to configure the File Engine. Enter y when prompted.
Note The configuration prompt waits several seconds before proceeding with the File Engine boot sequence. If you do not enter y in time to enter basic configuration, you will need to log into the File Engine through the terminal console and run the setup CLI command. The username is admin and the password is default.
Step 2 Enter the required information as prompted by the script. Refer to Table 1 for this information.
When finished, you see a summary of the information you entered.
Step 3 Accept the changes when prompted.
Once you accept the changes, the File Engine is visible on the network.
Step 4 Write down the IP address for future reference. You need it to launch the GUI, which takes you through the rest of the configuration.
Note If you are using DHCP, create a reservation record for the File Engine, or contact your network administrator. The WAFS software does not support dynamic address allocation.
Configuring the Network Interface on a Network Module
If you are running WAFS on network module NM-CE-BP-80G-K9, you must configure the network module's internal interface and default gateway on the host router.
To configure the network module IP addresses, use the following commands beginning in global configuration mode on the host router:
Note In the following commands, the term content engine (CE) refers to the network module running the WAFS software.
| |
Command
|
Purpose
|
Step 1
|
Router(config)# interface content-engine slot/unit
|
Enters content-engine interface configuration mode for the specified interface. The arguments are as follows:
•slot—Number of the router chassis slot for the network module.
•unit—Number of the daughter card on the network module. For CE network modules, always use 0.
|
Step 2
|
Router(config-if)# ip address router-side-ipaddr subnet-mask
|
Configures an IP address and subnet mask on the router-side interface to the internal link. The arguments are as follows:
•router-side-ipaddr—IP address for the internal router-side FE interface.
•subnet-mask—Subnet mask to use with the IP address.
|
Step 3
|
Router(config-if)# service-module ip address ce-side-ipaddr subnet-mask
|
Configures an IP address and subnet mask on the CE interface to the internal link. The arguments are as follows:
•ce-side-ipaddr—IP address for the internal interface.
•subnet-mask—Subnet mask to use with the IP address.
|
Step 4 *
|
Router(config-if)# service-module external ip address external-ipaddr subnet-mask
|
Configures an IP address and subnet mask on the Fast Ethernet external interface of the network module. The arguments are as follows:
•external-ipaddr—IP address for the external CE interface.
•subnet-mask—Subnet mask to use with the IP address.
|
Step 5
|
Router(config-if)# service-module ip default-gateway gw-ipaddr
|
Configures an IP address for the default gateway for the network module. The argument is as follows:
•gw-ipaddr—IP address for the default gateway.
|
Step 6
|
Router(config-if)# exit
|
Exits content-engine interface configuration mode.
|
* This step is optional.
Note The Installation chapter in the Cisco WAFS User Guide, Release 3.0 provides an example configuration of a WAFS network module. Refer to this example if you need assistance configuring the network interface on your network module.
Accessing the Setup Wizard
To access the Setup Wizard, follow these steps:
Step 1 Open Microsoft Internet Explorer 6.0 or later.
Step 2 Enter the WAFS Management address for the File Engine into the Address field, using the following format:
http://ip address/mgr
The Login is displayed.
Step 3 Enter the default user name (admin) and password (default) in the fields provided, and click the Login button.
Note When logging in for the first time to an uninitialized File Engine, you see the first page of the Setup Wizard.
Configuring the Core FE Using the Setup Wizard
Follow the windows in the Setup Wizard and provide the required information.
To configure the Core FE, follow these steps:
Step 1 Click Next in the Network Settings window.
You have already set up the network interface in the "Configuring the Network Interface" section. You do not need to fill out the information in this window, because you will perform future management of the network interface using the CLI.
Step 2 Select the correct time zone, date, and time from the pull-down menus in the System Settings window, if they are incorrect.
Click Next.
Step 3 Check the Core FE check box in the Role Selection window.
Step 4 (Optional) Check the WAFS Central Manager check box if this Core FE will be used as the Central Manager.
Note Your WAFS network can have only one Central Manager, so you can only check this box for one Core FE.
Note To configure both a Core FE and an Edge FE on a single File Engine, make sure that the File Engine has at least 1 GB of RAM. If it does not, the performance will be severely affected.
Click Next.
You see the Windows Environment window. If your site uses only NFS, click Next and skip to Step 7.
Step 5 Enter the following information in the Windows Environment window:
a. Provide the Windows workgroup name for the file servers that will be exported by the Edge FE.
b. (Optional) Provide the Windows Internet Naming Service (WINS) server address if WINS is used within the organization.
Click Next.
Step 6 Enter the following information in the Core FE Configuration - CIFS window:
a. Provide a file server access username and password. Use any user account with Read and Directory Browsing privileges. This is required for proper operation of pre-position policies and for browsing the shares when creating coherency policies.
b. Add the windows server from Table 1 in the Server Name box. To add a server, click the Add button, enter the server name in the provided space, and click OK. The CIFS file server name must be 15 characters or less.
Note Be sure to enter the name of the CIFS server. Do not enter the IP address of the CIFS server.
Note If WCCP is enabled on an Edge FE, it is possible that the Windows server you are adding can have multiple names or addresses. If the file server you are adding represents more than one IP address, all of the addresses will be shown in the Server name box. If the file server you are adding represents one IP address but has many names, you can add multiple names to the list in the order in which you want the Edge FEs to access them. The Edge FEs will use the first name in the list that matches the IP address they are using. You only need to add the names that you want the Edge FE to access.
Click Next.
Step 7 Enter the following information in the Core FE Configuration - NFS window:
a. Add the file server access User ID (UID) and Group ID (GID). The default values should work in most cases.
b. Add the UNIX server to the NFS Server Name box. To add a server, click the Add button, enter the server name in the provided space, check the TCP and/or UDP check boxes depending on which method your server is using, and click OK.
Click Next.
Step 8 (Optional) Enter the following information in the Notification Setting window if you want notification capability:
a. Add the intended alert recipient e-mail address.
b. Add the mail-server hostname or IP address.
c. Enter the name or address of the SNMP manager in the SNMP notification host field. The SNMP manager receives traps and notifications (if the enable check boxes are checked) from all the File Engines in the WAFS network.
Click Next.
Step 9 Enter the following information in the Connection to WAFS Central Manager window:
a. Enter the logical name for the Core FE. This name appears in the WAFS Central Manager in the File Engine name field.
b. Enter the IP address or host name of the WAFS Central Manager in the Central host field.
c. Check the Register with central check box to ensure the File Engine registers with the Central Management Console.
Step 10 Click Finish to end the setup process.
The Setup Wizard finishes and, after a few moments, displays a successful registration window. After clicking the Close button, you see the Components tab of the File Engine Control page as shown in Figure 5.
Note If you have changed the time zone or the date and time, you will see a Restart button instead of the Close button. Click the Restart button to restart the WAFS service to make sure it is updated with the latest system time. To verify that your configuration changes have been made, wait 1 to 2 minutes for the service to restart and then log in again. After you log in, you see the Components tab on the File Engine Control window as shown in Figure 5.
The recently configured Core FE is marked as Not Licensed. Once licenses are distributed from the WAFS Central Manager, the Core FE is enabled. See the "Distributing Licenses" section.
Figure 5 Components Tab in the File Engine Control Window for Core FE
Configuring the Edge FE
Now that the WAFS Central Manager is running, you need to set up and configure the remaining File Engine as an Edge FE. Unpack another File Engine and connect it to an installation console, as described in "Unpacking the Hardware" section, and the "Connecting and Powering On the System" section. Then, configure the File Engine as described in the "Configuring the Network Interface" section.
Note If this File Engine is to be set up remotely, ensure that you contact the remote location to verify the setup and configuration after the File Engine has been connected to an installation console.
Configuring WCCP on the Edge FE (Optional)
The Web Cache Communication Protocol (WCCP) allows you to transparently route traffic from clients to servers. Clients can map a drive to the server directly without having to specify the names of the File Engines. WAFS software supports WCCP, but you need a router that supports it also. Transparent routing through WCCP is used only for CIFS clients, not NFS clients.
If you want to enable WCCP on your WAFS network, you must use the WAFS CLI. You configure WCCP on the Edge File Engine and on the router before you configure the rest of the File Engine parameters using the Setup Wizard.
Note If you enable WCCP on your WAFS network when considerable CIFS traffic for non-cached servers is expected to be routed through the router, Cisco recommends that you configure static bypass rules on the router (as opposed to on the FE) that cause traffic to the non-cached file server(s) not to be redirected to the Edge FE.
To configure WCCP on the router, follow these steps:
| |
Command
|
Purpose
|
Step 1
|
router(config)# ip wccp 89
redirect-list [number | name]
|
For CIFS redirection, specifies the redirect access list. Only packets that match this access list are redirected. If you do not configure this command, all packets with destination ports matching those defined for the CIFS service will be redirected.
|
Step 2
|
router(config)# interface interface
|
Configures the interface to the local network. If the File Engine and clients are not on the same subnet, perform this step and then proceed to Step 6.
|
Step 3
|
router(config-if)# ip cef
|
Enables Cisco Express Forwarding (CEF) of redirected packets back through the interface on which they were received. Without this command, the router does not use the high-speed switching cache, and the packets are process-switched, which is a much slower method.
|
Step 4
|
router(config-if)# exit
|
Exits interface configuration mode.
|
Step 5
|
router(config)# interface interface
|
Specifies the LAN interface on the router to configure WCCP interception.
|
Step 6
|
router(config-if)# ip wccp 89 redirect in
|
For CIFS redirection, configures the interface connected to the LAN to redirect CIFS traffic to the Edge File Engine.
|
Step 7
|
router(config-if)# end
|
Exits interface configuration mode.
|
Step 8
|
router # copy running-config
startup-config
|
Saves the running configuration to the startup configuration, which is stored in nonvolatile memory (NVRAM).
|
To configure WCCP on the File Engine, follow these steps beginning in global configuration mode:
| |
Command
|
Purpose
|
Step 1
|
file-engine(config)# wccp version 2
|
Enables WCCP v2 on the Edge File Engine.
|
Step 2
|
file-engine(config)# wccp router-list
list-number lP-address
|
Configures a router list for the WCCP service(s). List-number is the router list number (1-8). You can list more than one IP address by separating each address by a comma.
|
Step 3
|
file-engine(config)# wccp cifs-cache
router-list-num list-number
|
For CIFS redirection, configures the cifs-cache service on the Edge File Engine and associates it with the router list you just created (the list number in this step must match the list number you specified in Step 2). This command also informs the routers in the specified router list that this File Engine is accepting cifs-cache service.
|
Step 4
|
file-engine(config)# exit
|
Exits global configuration mode.
|
Step 5
|
file-engine# write memory
|
Writes the running configurations to nonvolatile memory (NVRAM).
|
You are now ready to access the WAFS Setup Wizard.
Configuring the Edge FE with the Setup Wizard
To continue configuring the Edge FE, follow these steps:
Step 1 Click Next in the Network Settings window.
You have already set up the network interface in the "Configuring the Network Interface" section. You do not need to fill out the information on this window, because you will perform future management of the network interface using the CLI.
Click Next.
Step 2 Select the correct time zone, date, and time from the pull-down menus in the System Settings window, if they are incorrect.
Click Next.
Step 3 Check the Edge FE check box in the Role Selection window.
Click Next.
The Windows Environment window is displayed. If your site uses only NFS, click Next and skip to Step 5.
Step 4 Enter the following information in the Windows Environment window:
a. Provide the Windows workgroup name for the file servers that will be exported by the Edge FE.
b. (Optional) Provide the WINS server address if WINS is used within the organization.
Click Next.
Step 5 Enter the following information in the Edge FE Configuration window:
a. Check the Allow file server name publishing check box if you want file server names to be registered automatically. If WCCP is enabled, this window indicates that and the Allow file server name publishing check box is disabled.
b. Enter the Active Directory site name. Active Directory provides several benefits. For example, if DFS is implemented, this allows for DFS (MS Distributed File System) integration.
Click Next.
Step 6 (Optional) Enter the following information in the Notification Setting window if you want notification capability:
a. Add the intended alert recipient e-mail address.
b. Add the mail-server hostname or IP address.
c. Enter the name or address of the SNMP manager in the SNMP notification host field. Check the enable check boxes to ensure that the SNMP manager receives traps and notifications from the File Engines in the WAFS network.
Click Next.
Step 7 Enter the following information in the Connection to WAFS Central Manager window:
a. Enter the logical name for the Edge FE as you would like it to appear in the WAFS Central Manager in the File Engine name field.
b. Enter the IP address or host name of the WAFS Central Manager in the Central host field.
c. Check the Register with central check box to ensure the File Engine registers with the Central Management Console.
Step 8 Click Finish to end the setup process.
The Setup Wizard finishes and, after a few moments, displays a successful registration window. After clicking the Close button, you see the Components tab of the File Engine Control page as shown in Figure 6.
Note If you have changed the time zone or the date and time, you will see a Restart button instead of the Close button. Click the Restart button to restart the WAFS service to make sure it is updated with the latest system time. To verify that your configuration changes have been made, wait 1 to 2 minutes for the service to restart and then log in again. After you log in, you see the Components tab in the File Engine Control window as shown in Figure 6.
The recently configured Edge FE is marked as Not Licensed. Once licenses are distributed from the WAFS Central Manager, it is enabled. See the "Distributing Licenses" section.
Figure 6 Components Tab in the File Engine Control Window for Edge FE
You have successfully completed setting up two WAFS File Engines—one containing the Central Manager and Core FE components, and one containing the Edge FE component. You now need to establish connectivity between the Core FE and Edge FE, define coherency policies, and test the WAFS network. These tasks are accomplished using the Central Manager.
Launching the WAFS Central Manager
After the File Engine designated as the WAFS Central Manager has been deployed, you can launch the WAFS Central Manager remotely from any location on the WAFS network through Internet Explorer. Refer to the Cisco WAFS 3.0 User Guide for information on central management.
To launch the WAFS Central Manager, follow these steps:
Step 1 Open Internet Explorer 6.0 or later.
Step 2 Enter the WAFS Management address from Table 1:
http://ip address/mgr
The Login page is displayed.
Step 3 Enter the default user name (admin) and password (default) in the fields provided, select the WAFS Central Manager option, and click the Login button.
If this is the first time you are logging in, you will see the license agreement. Click the Accept button. The WAFS Central Manager interface is displayed. The WAFS Central Manager includes three main views: Tasks, Groups, and Users. These views are accessible by clicking their icons at the top left of the window. By default, you see the File Engines window when you first access the WAFS Central Manager, as shown in Figure 7. You can navigate to the different views and management windows using the icons or navigation tabs.
Figure 7 File Engines Window
Distributing Licenses
To distribute licenses, follow these steps:
Step 1 Click the License button (
) in the File Engines window.
The License Installation window is displayed.
Step 2 Use the Browse button to browse the directory tree and select the license key file (for example, *.lic) that is on the CD-ROM included in the accessory kit shipped with the system. You can view the license properties, such as expiration date and licensed components, in this window once a license file is loaded (see Figure 8).
Step 3 Distribute the license by clicking the check box next to the File Engine names and clicking the Install License button.
The Distribution Status window is displayed, which provides you with the status of this operation.
Note If the licensing distribution process fails, refer to the Cisco WAFS 3.0 User Guide for troubleshooting information.
Figure 8 License Installation Screen
Defining a New Connection
After distributing the license to the two File Engines, click the Connectivity menu in the WAFS Central Manager to connect the File Engines to each other according to their assigned roles. For more information on connectivity policies, refer to the Cisco WAFS 3.0 User Guide for information on central management.
To define a new connection, follow these steps:
Step 1 Click Connectivity in the left pane to display the Connectivity window.
Step 2 Click Add to display the Connectivity details window (see Figure 9).
Figure 9 Connectivity Details Window
Step 3 Select the WAFS Core FE host name for the data center in the Core FE tab.
Step 4 Select the WAFS Edge FE host name for the branch office in the Edge FE tab.
Step 5 Specify a prefix (for example, WAFS-) in the Alias tab (CIFS only).
The prefix allows you to give each Edge FE a unique identifier, which will eliminate name conflicts. The prefix is placed before each exported Windows server name.
Step 6 Do the following in the NFS tab:
a. Check the Is root squash enabled on file servers check box.
b. Leave the default values (original) in both the UID and GID fields.
Step 7 Click Save to save the new connection.
The connection details are displayed in the Connectivity window.
Step 8 Click Distribute to distribute the new connections to the File Engines.
Step 9 Close the Connectivity Details window.
Updating the File Engines
To update all File Engines, follow these steps:
Step 1 Update all File Engines by clicking the Distribute button at the bottom of the Connectivity window.
Step 2 Close the update window.
Starting File Engine Components
With the licenses installed on each File Engine, you can start one or all components. Refer to the Cisco WAFS 3.0 User Guide for information on central management.
To start all File Engine components, follow these steps:
Step 1 Click File Engines in the left pane.
A list of all the registered File Engines appears in the display area (right pane).
Step 2 Click the Operations tab to display management options.
Step 3 Click Start All to start all enabled components in both registered File Engines.
A distribution window is displayed that shows the progress of the command.
To start an individual File Engine component, follow these steps:
Step 1 Log into the File Engine Manager.
Step 2 Click Control in the left pane. Make sure the Components tab is active.
A list of all the registered File Engines appears in the display area (right pane).
Step 3 Click the name of the File Engine you want to start.
Step 4 Click Start to start the registered File Engine.
Client-to-Edge FE Connection
The Edge FE behaves simply as another node on your network. Clients can access it using the same methods used to access NFS or Windows file servers, including:
•Drive mapping or UNC (Windows only)
•Share mounting (NFS only)
Note In Windows environments, we recommend that clients map a network drive to the Edge FE.
Accessing an Edge FE Through a Mapped Drive (Windows Only)
To access the Edge FE through a mapped drive, follow these steps:
Step 1 Open Windows Explorer.
Step 2 Select Map Network Drive from the Tools menu.
Step 3 Browse to the desired drive letter in the Drive field and locate the share.
Step 4 In the Folder field, enter the path in the format \\servername\sharename, and click OK.
Note Use the original server name in place of servername if WCCP is enabled. If WCCP is disabled, use a server alias in place of servername. The alias can be the server name with a prefix or suffix, or an explicitly defined alias.
You will see the selected mapped drive in a new window.
Accessing an Edge FE Through UNC Pathing (Windows Only)
To access the Edge FE through UNC, follow these steps:
Step 1 Select Run from the Windows Start menu.
Step 2 Enter the path to the server name in the Open field, in the format \\servername, and click OK.
Note Use the original server name in place of servername if WCCP is enabled. If WCCP is disabled, use a server alias in place of servername. The alias can be the server name with a prefix or suffix, or an explicitly defined alias.
You see a new window open. This window shows the available network shares on the server as they are exported through the local Edge FE.
Mounting a UNIX Shared Directory
To mount a UNIX share, follow these steps:
Step 1 Display the available exported shares on the Edge FE by entering the following command:
showmount -e EdgeFE-name
Step 2 Mount the share by entering the following command:
mount fehost:/CoreFE-name/FileServer-name/Share-name targetdir
Note The File Engine supports only the NFS version 2 mount command. Be sure your system supports
NFS v2, or use the specific NFS v2 mount command options. when using the mount command.
Step 3 Change the directory to the mounted share by entering the following command:
cd targetdir
You have successfully connected a client to the Edge FE. For more information about the installation, setup, and configuration process, refer to the Cisco WAFS 3.0 User Guide.
Obtaining Technical Assistance
Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.
Cisco Technical Support & Documentation Website
The Cisco Technical Support & Documentation website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, at this URL:
http://www.cisco.com/techsupport
Access to all tools on the Cisco Technical Support & Documentation website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Note Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support & Documentation website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.
Submitting a Service Request
Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL:
http://www.cisco.com/techsupport/servicerequest
For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.
To open a service request by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447
For a complete list of Cisco TAC contacts, go to this URL:
http://www.cisco.com/techsupport/contacts
Definitions of Service Request Severity
To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.
Severity 1 (S1)—Your network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Documentation Feedback
You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.
You can send comments about Cisco documentation to bug-doc@cisco.com.
You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
© 2005 Cisco Systems, Inc. All rights reserved.
