Allot NetEnforcer with WAE

[robertsoto]

Dear,

My customer want to install a WAAS in six local remote site and a Site Central, but He has a ALLOT NetEnforcer, the Allot is doing Traffic Prioritization now.

I will apreciate some comment about I can install the allot with WAAS.

I am planing to setting with this topology. IT is correct?.

SW --> ALLOT --> WAAS --> Router.

I wait some comment and recomendation.

Thanks,

Regards,

Robert soto.

[Nicolas Fournier]

Hi Robert,

I did some researches on the operability between WAAS and the NetEnforcer products and it seems that there are some problems if the WAAS optimized traffic is going through a NetEnforcer device.

So I would advise you to set this up as you shown in your message and to have the traffic going through the ALOT before passing through the WAAS.

Regards,

Nicolas

[robertsoto]

Hí,

My customer has a six remote branch and each remote branch has a ALLOT,

My topology is:

SW----> WAAS--> ALLOT ---> router,

This topology is becouse the ALLOT is working in Layer 4.

I will apreciate if someone  send me any information about the implentation or experience when implemented ALLOT with WAAS.

Or documentation about a successful case after the implementation.

Thanks,

[Fatoumata Sow]

Hi Soro,

We implement ALLOT with WAAS recently but we have a problem.

When we had the topology:

- SW-->WAAS-->ALLOT-->Router

We get latency on network with or not QoS actived on ALLOT.

- SW-->ALLOT-->WAAS-->Router

Everything work

And I think that ALLOT works in Layer 7 beacause it identify network traffic per application.

hope this is helpful.

Regards

Fatoumata

[finn.poulsen]

I've had almost the same issue at Fatoumata describes :

When an Allot sits withing the optimized path (i.e. after the WAAS box) HTTP traffic is initially delayed :

After 3-way handshake, the WAAS box sends a small packet with spoofed IP-adresses (clients and server) containing :

TCP options x'33' and a payload of e.g. X'12060000040000000000'.

This packet is used as a "handshake" between SO-DRE processes to confirm that resources

can be allocated for the connection.

Unfortunately this packets is delayed by Allot Netenforcer for about 20 seconds or so.

We removed the Netenforcer and everything worked.

Best Regards

Finn Poulsen