Size of VLANS

[SYNACK]

Only the L2 vlan extends past the local switch. This is fine. Design and security suggests you want to avoid broadcast - this does that.

 

If HP is ripping you off in the UK then look to Cisco. First, their gear is superior and their warranty now matches HP's completely. The only hope HP has ever had in the networking space has been on price, and if they aren't doing that for you, tell them to stuff it.

 

Not UK, New Zealand, we easily pay double or more what the UK does for networking gear and the UK lot still get ripped of in comparison to the US. Cisco stuff is new car level of prices for the lowest mid level switches under educational pricing.

[Destinova]

Not UK, New Zealand, we easily pay double or more what the UK does for networking gear and the UK lot still get ripped of in comparison to the US. Cisco stuff is new car level of prices for the lowest mid level switches under educational pricing.

 

That's interesting. The Cisco EDU discount here (Canada) is fairly close to 40% off list price, depending on what gear you're looking at. Comparison on the Cisco/HP side (I sell both as a consultant) Cisco can get very close to HP pricing, but can't offer the 2-for-1 or 3-for-2 deals that they often have on their lower end L2 and L3 switches, which is usually the tipping point for anyone buying bulk.

[Roberto]

Most of the decent switches are L3 anyway, and it does make a good deal of sense. Some would even argue that the uplinks should be OSPF VLAN's of their own (ie a vlan of 2). There isn't any point in polluting uplinks with random traffic that doesn't need to be there. I've got 4 links like this and it works pretty well.

 

This is our approach. It works well but does require a lot of investment, time as well as money, to set up. We've used this approach to connect each edge and each core together with redundant routes.

[SYNACK]

This is our approach. It works well but does require a lot of investment, time as well as money, to set up. We've used this approach to connect each edge and each core together with redundant routes.

 

You can do that with STP also and get rid of the protocol overhead but as always the best solution depends on the requirements.

[nelsons]

The easiest way is to start with addressing the network, making sure you have the right number of hosts that you require on each network or vLAN. Once you have done this you can then look at summarsing the network at the relevant boundaries. If you have some transit networks between two devices use /30's

 

If I can be of any help drop me a PM, happy to run stuff through ;-)

 

Cheers