WAAS and Symantec Vertitas Volume Replicator

Unanswered Question
Aug 19th, 2007


We are forwarding Symantec replication traffic via our WAAS infrastructure over a 20Mb WAN link. The CM appears to register the traffic but does not optimize it at all. Has anyone had any experience with WAAS and Symantec Veritas Volume Replicator (VVR) 4.3?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Zach Seils Mon, 08/20/2007 - 22:42


What TCP port(s) does the application use? When the application is active, do the connection appear as optimized in the output of 'sh tfo conn summ'?



frosty074 Mon, 08/20/2007 - 23:28

We've configured custom TCP ports 58600 58999.

Yes the tfo connections appear to be optimizing the traffic, although the CM gui indicates 1X optimization.

When we test FTP on those ports it works OK, but the CM still shows 1X optimization.

WAE config:

classifier Symantec58600-58999

match dst port range 58600 58999

name CustomReplication classifier Symantec58600-58999 action optimize full

tblancha Tue, 08/21/2007 - 09:06

I tested with VVR in the lab. VVR default uses UDP and using the nerd knob in the GUI did not force VVR to start using TCP. To get VVR to use TCP, I had to input these commands:

vrport data 1999-1999

vrport heartbeat 2000-2000

or use what ever ports you want to use. The previous answer was asking if you were seeing TCP sessions in the WAE's. This can be seen by telneting to the WAE and issueing a "show tfo connection summary". Can you post the output of that command?

frosty074 Wed, 08/22/2007 - 18:00

Hi, tfo stats attached. = one of the replication servers.

'CustomReplication' is the name we've given the application.

Zach Seils Fri, 08/24/2007 - 05:55

What classifier(s) do you have associated with this application? What position are the policy-maps in? The output you provided shows a single connection on port 3389, which is Microsoft RDP.



This Discussion