Application Acceleration
Application Acceleration

Traffic between Spok

‎02-02-2009 07:51 AM

Dear All,

 

we will install our WXCs (3400 & 1800) in Hub and spoke mode, so the tunnel  will be created between hub (3400 )and spoke(1800) only, but what about traffic will go between two spoke sites?  we need traffic between two spoke sites to be reduced ?.

 

also we can't create tunnel between all Spoks  (it more than 30 spoke and we have wxc 1800 with limited Endpoints), can help me.

 

Also, if the spoke is having the hub as its default decompressor, can we still let the traffic going from the spoke directly to the internet not to be tunnelerd to the hup and be sent to the internet directly from the router where the spoke is connected?

 

                    

 

 

7 REPLIES 7
Application Acceleration

Re: Traffic between Spok

‎02-02-2009 11:39 AM

#1 - By default tunnels are established automatically between hub and spoke sites. If you want spoke to spoke traffic to be reduced you can setup tunnels by manually enabling them between two spokes.

#2 - Don't understand your second point.

#3 - Did you explicity define the hub as the "Default Decompressor" on the Compression/Advanced tab? Normally you would not do so and just select the subnets for compression and let the rest of the traffic flow through untouched.

Kevin Barker
JNCIP-SEC
JNCIS-ENT, FWV, SSL, WLAN
JNCIA-ER, EX, IDP, UAC, WX
Juniper Networks Certified Instructor
Juniper Networks Ambassador

Juniper Elite Reseller
J-Partner Service Specialist - Implementation

If this worked for you please flag my post as an "Accepted Solution" so others can benefit. A kudo would be cool if you think I earned it.
Application Acceleration

Re: Traffic between Spok

‎02-03-2009 12:26 AM

Hi,

 

 

1- For second point, i mean if we will create tunnel manually between each spok, and we have more than 30 spok, WXC 1800 limition will not accept, create all these tunnels. so do you have any method to reduce the traffic between each spok without create tunnels between each spok?

 

 2- We didn't  define the hub as the "Default Decompressor" on the Compression/Advanced tab.

Application Acceleration

Re: Traffic between Spok

‎02-03-2009 07:00 AM

#1 - There is no way to compress traffic without establishing a tunnel between the two units. Perhaps you could leverage your hub and spoke arrangements and reroute traffic from the hubs to your central spoke device and back out. Change your architecture to allow this and only allow spoke to spoke traffic on the heavily used links.

 

#2 - If you are not using default decompressor then traffic that is not flagged for decompression (specific subnets) will pass through the box untouched on it's way to the specific endpoint - Internet or non compressed spoke traffic in your case.

Kevin Barker
JNCIP-SEC
JNCIS-ENT, FWV, SSL, WLAN
JNCIA-ER, EX, IDP, UAC, WX
Juniper Networks Certified Instructor
Juniper Networks Ambassador

Juniper Elite Reseller
J-Partner Service Specialist - Implementation

If this worked for you please flag my post as an "Accepted Solution" so others can benefit. A kudo would be cool if you think I earned it.
Application Acceleration

Re: Traffic between Spok

‎02-04-2009 04:37 AM

The point is, we do not want the spokes to communicate with eachother direct, but they have to go from spoke1 to the hub then back to spoke2. But in the case of the internet traffic, or traffic going to other sites without wx boxes, we want such traffic to go directly from the spoke to them without going to the hub.

 

Now if we set the hub as the defaule decompressor for all the spokes, we are afraid that this may affect the internet traffic, as it may be needed to go from the spoke site to the internet uplink there directly. And still it is not possibe to add exceptions in this case for the internet traffic.

 

 

Application Acceleration

Re: Traffic between Spok

‎02-09-2009 04:33 AM

@muttbarker wrote:

#1 - There is no way to compress traffic without establishing a tunnel between the two units. Perhaps you could leverage your hub and spoke arrangements and reroute traffic from the hubs to your central spoke device and back out. Change your architecture to allow this and only allow spoke to spoke traffic on the heavily used links.

 


I am facing a similar issue as the one mentioned above. How can this spoke-hub-spoke re-routing scenario be done?

 

Thanks

Gr33n Data
JNCIS-FWV, JNCIA-IDP

@gr33ndata

http://gr33ndata.blogspot.com/
Application Acceleration

Re: Traffic between Spok

‎03-18-2009 04:41 AM

gr33ndata,

 

This has more to do with the routing itself.

Let's say you have 2 remote sites: Site1 and Site2 and one central site which is the Hub

The routers on the hub site need to know how to reach subnets in Site1 and Site2.

 

Example:

 

WX1 sits in Site1

WX2 sits in Site2

WX3 is the Hub

 

WX3 is the Default Decompressor for WX1.

Because WX1 has no knowledge about subnets in Site2, traffic will be compressed 

and sent to WX3. WX3 will decompress the packets to the LAN L2/L3 switches. 

These guyz know where to send this traffic. The decision is then made here. 

Whether or not you want to optimize traffic between WX3 and WX2 is totally up to you.

Hair-pinning? 

 

Hope this helps,

A.

 

Application Acceleration

Re: Traffic between Spok

‎03-18-2009 05:50 AM

Antares has the point here. Bear in mind that unless you have direct tunnels to the spokes, sending traffic twice through the hub side WX (and other equipment on the path) is sub-optimal solution, but might work for you if you are not approaching limits of the device.

 

If you have a spoke that has to communicate with many other spokes, and you want this traffic compressed and sent directly, then this spoke site is a candidate for becoming a hub and getting another 3400 for that purpose (more tunnels and capacity).