Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

WAAS: CIFS Connectivity Configuration

Hello everybody,

I have some questions about CIFS configuration:

Is it possible to configure a File Server, which belongs to two o more Connectivity Directives ?.

Or if a system has two o more Edge devices and one core device, how can we configure the Connectivity Directive if the Wan links have different Bandwith and delay?. How can affect this values in the CIFS performance?

Have these questions sense in Waas 4.1 ?

Thanks in advance

Jose Luis

1 ACCEPTED SOLUTION

Accepted Solutions
Silver

Re: WAAS: CIFS Connectivity Configuration

Totally transparent with no need to configure core and edge services except in instances when file preposition is being used.

5 REPLIES
Silver

Re: WAAS: CIFS Connectivity Configuration

In version 4.0 you had to configure a connectivity directive for each of the WAN characteristics.

In version 4.1 you no longer need to configure core and edge file services. WAAS 4.1 has a Layer 7 CIFS acceleration no longer requiring a 4050 tunnel.

In addition, the WAVE appliances now provide Virtual Blades with windows core services (DNS, DHCP, etc) to allow users to remain authenticated should WAN fail

New Member

Re: WAAS: CIFS Connectivity Configuration

Assuming this topology:

WAFS CORE --wan 1 -- WAFS EDGE 1

--wan 2 -- WAFS EDGE 2

It is possible associate a one Core cluster with two connectivity directives?

If it is possible, the configuration shuld be like this:

Connectivity 1 -- Core cluster 1 --Edge1

Connectivity 2 -- Core cluster 1 --Edge2

Regards.

José Luis

Silver

Re: WAAS: CIFS Connectivity Configuration

yes you can setup multiple connectivity directives from a single core to multiple edges in 4.0.

If using 4.1 there is no longer a need for this for traffic is not tunneled using port 4050. You simply enable the CIFS accelerator

New Member

Re: WAAS: CIFS Connectivity Configuration

In WAAS 4.0, the traffic is tunneled using port 4050, that means the File Server has many MS-DS(445, 139) connection with the WAFS CORE. As a result you can see the IP of the WAE Core in the output of the command "netstat" applied in the File Server. It can affect some account logs, such as, printing report.

As you comment using waas 4.1 the traffic is not tunneled using port 4050, Does the Wae Core still make a MS-DS connection with File Server ? or with this version the CIFS accelerator is totally transparent to the File Server.

Thanks for your comments.

José Luis

Silver

Re: WAAS: CIFS Connectivity Configuration

Totally transparent with no need to configure core and edge services except in instances when file preposition is being used.

310
Views
0
Helpful
5
Replies