Network Design

I'm designing a network that should be able to support both dedicated servers and also offer colocation (full rack and half rack). Things will be relatively small at start but the design must be able to scale. The colo area will be secured from the dedicated server area.

Right now, this is what I'm thinking:

CORE/DISTRIBUTION combined:
- Two cisco 6509's running HSRP
- Each 6509 is connected to the same two upstream ISP's via BGP (so that means 4 links in total)
- Each 6509 is connected to the access switches (described below)
- The 6509's will have a single gigabit crossconnect between them so that they can talk to each other for HSRP, iBGP, etc.

ACCESS
- Each of our racks will have an L3 switch at the top of the rack for all the servers in the rack to plug into
- there will be ~30 servers per rack
- these switches will use 4 x 1 gbit ports for trunking to the core. They will be configured in two 802.3ad link aggregation groups (ie 2 x 1gbit links per LAG group). One LAG group will connect to the first 6509, the second LAG group will connect to the second 6509.
- The default gateway on these L3 switches will be configured with the HSRP virtual IP address of the 6509's.
-spanning tree will have to be enabled to avoid loops since the two 6509's are connected directly also

QUESTIONS:
1) Each dedicated server will get 5 usable IP addresses, so I'd have to subnet my IP address space accordingly (into a bunch of /29's). This also means that I'd have to setup 1 VLAN per subnet (wich means 1 VLAN per server!). Is this a scalable design? If I have 1000 servers I'd need 1000 VLAN's! Isn't there a limit to the number of VLANS that can be created/handled by my core switches? How do larger providers do it that have thousands of servers?

2) Is this design scalable/redundant? The only single point of failure that I see is my access switch (if it dies, it could take out a rack's worth of servers). I guess I would have to live with this and would have spares on hand.

3) I'm a little confused with the interaction of BGP and HSRP. What happens, for example, if one of the links to one of the ISP's goes down on the active HSRP router? I dont want it to fail over to the inactive HSRP router, because the router is still good, its just a link that went down. Would the active HSRP router be smart enough to realize (maybe via iBGP) that the inactive HSRP router can still route to that ISP and thus just ROUTE the traffic to that inactive 6509 and then have that router send it out to the ISP? I'm assuming this traffic would travel across the 1gbit xconnect between the two 6509's so I may have to consider increasing that capacity using link aggregation aswell?

4) Which cisco switch would be good as my L3 access switch? It would have to support ~30 servers in the rack plus have at least 4x1gbit ports that I can config into two lag groups to uplink to the core.