• Twitter
  • FaceBook

Welcome to ISAserver.org

Forums | Register | Login | My Profile | Inbox | RSS RSS icon | My Subscription | My Forums | Address Book | Member List | Search | FAQ | Ticket List | Log Out

Array members not caching....

Users viewing this topic: none

Logged in as: Guest
  Printable Version
All Forums >> [ISA Server 2004 Cache] >> General >> Array members not caching.... Page: [1]
Message << Older Topic   Newer Topic >>
Array members not caching.... - 15.Jun.2005 11:48:00 AM   


Posts: 6
Joined: 14.Jun.2005
Status: offline
I had this posted in the firewall board so I moved it to cache... Pleas Help...

I have a ISA 2004 EE array with 3 servers. I added 2 servers over the last 2 weeks. The orginial server is acting as the configuration storage server (although I dont know if that is pertinent). I am using these only for reverse proxy of one internal website and all are on the same subnet. They all 3 show up on the monitoring and all 3 say they are synced and happy. However when I am loadtesting against them the only server that handles any load is the main server. the other 2 sit there and do nothing. I am able to watch the perf mon on the other 2 and the dont do a thing.

All the cache drives appear to be set up ok and caching is enabled.

Any help would be appreciated. My first post but have ref'ed the site many a time over the implementation. Feel free to insult my intelligence.

Post #: 1
RE: Array members not caching.... - 16.Jun.2005 9:49:00 AM   


Posts: 16
Joined: 14.Jan.2004
Status: offline
ISA 2004 EE uses NLB doesn't it?

I know it's not quite the same bit my NLB web farm of 3 servers works in a similar pattern.

Try checking the affinity settings for the NLB cluster?

(in reply to dcarley)
Post #: 2
RE: Array members not caching.... - 16.Jun.2005 10:31:00 AM   


Posts: 6
Joined: 14.Jun.2005
Status: offline
Yeah.. I'm a moron... Never even had NLB enabled... Somthing our M$ SE never mentioned. Makes sense that somthing would need to spread load across the array members.

I am stuck now however, I have it running on 2 of the 3 servers. but dont really know where to go from here.

Do I have to format the URL to point to the VIP for the NLB cluster?

Im confused...

(in reply to dcarley)
Post #: 3
RE: Array members not caching.... - 16.Jun.2005 10:52:00 AM   


Posts: 6
Joined: 14.Jun.2005
Status: offline
I seem to be narrowing down some possibilities for this... I was reading some posts from Tristan on ISAuser.com and It looks like I dont need NLB for caching only, which is what we are trying to do... can anyone confirm this?

Can anyone provide some clarification on this?

(in reply to dcarley)
Post #: 4
RE: Array members not caching.... - 20.Jun.2005 8:15:00 PM   


Posts: 50013
Joined: 10.Jan.2001
From: Texas
Status: offline
Hi Dilert,

Configure the clients for client-side CARP.


(in reply to dcarley)
Post #: 5
RE: Array members not caching.... - 21.Jun.2005 10:47:00 AM   


Posts: 6
Joined: 14.Jun.2005
Status: offline
I am at a large company 60 - 80K users... so it seems that it would be difficult to configure all those browsers. (this is for a webcasting app so I potentially hit all browser) this is why I am interested in server side carp. But it doesent seem to be working very well. I.E. I dont see sessions being spawned in the monitoring screen to the other array members.

Am I missing somthing fundamental about how server side carp works?

(in reply to dcarley)
Post #: 6
RE: Array members not caching.... - 23.Jun.2005 2:02:00 PM   


Posts: 1848
Joined: 26.Jan.2001
From: Keller, TX
Status: offline
CARP, when functioning correctly, has both a client side and server side component.

If auto-discovery is working correctly, then the clients will know that Node1 serves a particular range of websites and Node2 servers another, and so on...

The way it works is that when the clients pull down the WPAD file, WPAD contains a hash from each node of the array. This hash is used by the client to determine which node "most likely" has a particular URL cached, and will send the request to it.

If auto-discovery isn't working, or isn't setup, then the clients send the request to the proxy arrays address (which is resolved through a host record that points to all IP's of the nodes). Since you can't guarantee who will receive the request (let's say Node1 receives the request), Node1 will service the request and talk to the other nodes on the intra-array adapter to retrieve the content from whover is supposed to have it.

(in reply to dcarley)
Post #: 7

Page:   [1] << Older Topic    Newer Topic >>
All Forums >> [ISA Server 2004 Cache] >> General >> Array members not caching.... Page: [1]
Jump to:

New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts