MCSA exam

[kevin_lane]

im going for my next exam the 70-291 i've done the other 2. their is a question i came across on my prep exam about a "web site hosted on 3 different servers" now how does this work i know it might sound stupid but just somthing i'd like to learn incase i ever need to do it and this would be live on the internet

[apeo]

Clustered Servers?

[ricki]

you can also do it with round robin

 

richard

[kevin_lane]

how would you do it with round robin also i've been told you can add multipule A host records and do it that way as well

[matt40k]

how would you do it with round robin also i've been told you can add multipule A host records and do it that way as well

 

Round robin again really. Cluster is different. I think Microsoft Load Balancing... rings a bell.

[eastb]

Hi kevin,

As Matt40k says, it would most likely be done using NLB but in conjunction with MS ISA server (in a web publishing role) or similar. You may find a stray question, but it is really beyond the scope if the 291 exam so i wouldn't worry about it too much. You would be expected to know if you are in web publishing or a firewall admin for instance, but not for general Windows network support. Hope that helps a bit.

Cheers!

[strawberry]

NLB is your answer. It's because its static content so you set up a nlb ip address which then reads content from whichever computer is available.

 

clustering is your answer for more dynamic content.

[kevin_lane]

i understand about the NLB but i mean though if i had a web site (big company) and servers in different countrys no NLB and i had 1 server in usa 1 in uk and 1 in hong kong

(i know this sounds mad) all part of the same forest but i just wanted to site split over 3 servers how would that work

i know im getting pritty deep but be nice to know

[strawberry]

set 3 dns records for it, i think it'll always goto the one with the lowest ping?.

 

not sure.

[webman]

Load balancing. I have no idea how MS do it but this is how it would be done with Nginx: NginxLoadBalanceExample - Nginx Wiki

[kevin_lane]

hummm you do mean the host A records ? and www records in dns or am i wrong and its just the a record. ping not sure about that either

[kevin_lane]

humm that looks a bit confuzzling lol am i right in saying

that http {

upstream myproject {

server 127.0.0.1:8000 weight=3;

server 127.0.0.1:8001;

server 127.0.0.1:8002;

server 127.0.0.1:8003;

am i right in saying that these would be different servers in my forest around the world (obs) propper ips but why a different port

 

what does this mean

 

server {

listen 80;

server_name http://www.domain.com;

location / {

proxy_pass http://myproject;

}

}

}

 

this dont tell me alot could you please elaborate

[strawberry]

www is an example of an A record. When you request a record you get all the ip address;s assocaited with it (goto cmd, then type nslookip Google)

 

i think your browser goes to the one with the shortest ping. i could be very wrong on this though.

[strawberry]

different ports ebcause you have to address the service using a nuique name, normally a different ip address btu becuse you are only using the one you have to change the port.

 

no idea on the second bt!

[webman]

You have a front server that accepts requests on http://www.kevinlane.com. You can then have this server pass the request on to one of multiple other servers that are configured to handle the specified website.

 

The ports on the wiki are just an example. This might make more sense:

 

http {
 upstream website {
   server uk.kevinlane.com weight=3;
   server us.kevinlane.com;
   server hk.kevinlane.com;
 }

 server {
   listen 80;
   server_name www.kevinlane.com;
   location / {
     proxy_pass http://website;
   }

}

[Marci]

server {

listen 80;

server_name http://www.domain.com;

location / {

proxy_pass http://myproject;

}

}

}

 

S'a vhost definition...

 

server{ = start a new server (vhost)

listen 80; = traffic for this server is expected to arrive on port 80

location / = local path to the content to be served

{proxy_pass...} = reverseproxy I think... effectively makes the URL after proxy_pass appear in the local URL space...

} = end this server (vhost) definition.

} = dunno - one too many!

[kevin_lane]

ttp {

upstream website {

server uk.kevinlane.com weight=3;

server us.kevinlane.com;

server hk.kevinlane.com;

 

 

would all point too server

server uk.kevinlane.com weight=3;

server us.kevinlane.com;

server hk.kevinlane.com;