BIG IP Design

Need more information.

 

 

Anthony

not sure if i understand your question correctly.

 

 

u mean u wanna use 3900 for load balancing servers for internal users only. is this correct?

 

 

if so, is one-armed deployment acceptable?

 

anyway, if service is not http/s, u cannot use x-forwarded-for header for tracking real client address.

 

 

cheer!

It might be easier to have your F5 SE join you for a whiteboard session.

Thank you guys.I am pretty new to BIGIP so main purpose is we want to move current internal server services in to new 3900 as a first stage and we want to leave internet related services on old BIG IP boxes.

 

 

The internal services is having http,ftp,smtp etc

 

 

I have to configure internal and external interfaces or just internal interface

>I have to configure internal and external interfaces or just internal interface

 

 

either internal/external or internal should work. it depends on what your design is.

If your goal is to never have your new 3900s be the gateway you will want to go with a "one arm" configuration.. Basically anything that can route to your new 3900 you can load balance via SNATs.. One interface should be enough... you can always add another if you'd like to go with a traditional "in line" config..

 

 

As the other posters have mentioned, we need more information..

 

 

When you say 'one arm' I assume you are referring to a trunk config? Single physical? If so, wouldnt he be further ahead to use at least two physicals? I guess Im coming at it from a bandwidth perspective. In many cases out intranet F5's would have issues with just a single 1 gig link. Depends on your design I guess.

one armed configurations are normally in reference to layer 3, in that there is only one subnet defined instead of two (or more). All traffic is snatted (or npath routed) so that you can dump your BIG-IP into a working architecture without making any changes.

I think of any one-armed this way (after all, you can have one armed and routed mode on the same box) - your VIP addresses are on the same subnet as your pool members.

 

--Matt

Thank you guys and If i implement one armed configuration the problem is all the servers,clients are diffrent vlans so which design i have to follow