Troubleshooting guide

1-6
Cisco Wide Area Application Services Configuration Guide
OL-26579-01
Chapter 1 Planning Your WAAS Network
Site and Network Planning
UNIX Network Integration
Before the initial configuration of a WAAS device, you need to know the following parameters:
• DNS server and DNS domain.
• NIS server parameters (if applicable).
• On the data center WAE side, a browsing UID or GID with file-server directory traversal (read-only)
privileges. This UID or GID, which is usually set up as a domain or service user, is required for
browsing when defining coherency policies.
To successfully integrate Cisco WAAS into the UNIX environment, you need to perform these actions
on both the data center WAE and branch WAE sides of the network:
• You must manually add the name and IP address of both the data center WAE and the branch WAE
to the DNS server.
• When separate domains are used, UNIX users may be defined at the remote (branch) offices or on
the central servers. This situation may result in the same user name being defined in different
domains. A user may be defined differently in the branch and center or may be defined only on one
end and not on the other. You can ensure consistency in such cases by using NIS or by mapping
between the different domains, either manually or automatically. That is, users can be mapped from
the remote server to the central servers by translating their identities from the central office to the
remote offices.
Note To map users using automatic management, you must first configure the NIS server in both the data
center WAE (primary) and branch WAE (secondary).
CIFS-Related Ports in a WAAS Environment
This section describes the CIFS-related ports used between your clients, WAEs that are functioning as
file engines, and CIFS file servers. Most CIFS communication occurs between the branches and the
central office. This communication is encrypted and delivered through the organization’s VPN. No ports
on the firewall need to be opened because all communication is tunneled internally.
You only need to change the firewall setup if administrative or other maintenance work needs to be done
from a location outside the organization.
Ports 139 and 445
If you have only deployed CIFS services in your WAAS network, your WAAS network uses ports 139
and 445 to connect clients to a branch WAE and to connect a data center WAE to the associated file
servers. The port used depends on the configuration of your WAAS network.
If WCCP is enabled or inline mode is used, the branch WAE accepts client connections on ports 139 or
445. If neither WCCP nor inline mode are enabled, the branch WAE accepts connections only over port
139.
Your WAAS network always tries to use the same port to communicate end-to-end. Consequently, if a
client uses port 445 to connect to a branch WAE, the associated data center WAE will try to use the same
port to connect to the file server. If port 445 is unavailable, the data center WAE will try to use port 139.