cancel
Showing results for 
Search instead for 
Did you mean: 
cancel

VLAN DESIGN BEST PRACTICE ?

unleashed333
Beginner
Beginner

Dear All

I have two sites which are connected via ISP MPLS link,currently total network is flat .I have to implement VLAN design,what should be th best practice for it.,user of SITE A  authenticates from server of SITE B.

we have altogether of 200-250 user

Large VLAN contains 50 user

small VLAN contains 5-10 user

any iP schemening will work...Please have alook at attachment and kindly share your experience

5 REPLIES 5

Bilal Nawaz
Engager
Engager

You could consider the following:

Group devices by traffic patterns - Devices that communicate extensively between each other are good candidates to be grouped into a common VLAN.

Group devices for security - It is often a good practice to put servers and key infrastructure in their own VLAN, isolating them from the general broadcast traffic and enabling greater protection.

Group devices by traffic types - VoIP quality is improved by isolating VoIP devices to their own VLAN. Other traffic types may also warrant their own VLAN. Traffic types include network management traffic, IP multicast traffic such as video, file and print services, email, Internet browsing, database access, shared network applications, and traffic generated by peer-to-peer applications.

Group devices geographically - In a network with limited trunking, it may be beneficial to combine the devices in each location into their own VLAN.

It all depends on what the requirements are.

Routing can take care for users in Site A authenticating from a server in Site B if theyre on another subnet/vlan if needed.

hth

Bilal

Please rate useful posts & remember to mark any solved questions as answered. Thank you.

Leo Laohoo
VIP Community Legend VIP Community Legend
VIP Community Legend

250 users and you want to segment them?  My question is WHY?

The size is enough to fit neatly in a /24 subnet.

If you have to, then subnet them per "department":  Finance, marketing, engineering, etc.

Remember 250 Users + Network devices + Servers (if any) in that /24 Will that be enough? Is it following best practice? Is the company likely to expand?...

I agree, many instances have been segregated based on dept. too

Please rate useful posts & remember to mark any solved questions as answered. Thank you.

Sakun Sharma
Beginner
Beginner

You can divide traffic based on departments, servers and voice.

For example you can have one set of VLAN's for Departments, One for Servers, One for Management - Managing Devices, And one Dedicated to Voice for  using QoS service.

Authentication etc can be handled by Inter-VLan routing.

So it would be like this:

VLAN xx - Accounts

VLAN xx - other Departments

VLAN xx - Voice

VLAN xx - Management

VLAN xx - Servers

For futher expandability I suggest to use bigger subnet, because soon or later your network will grow, and changing complete IP addressing at that time will be big headache, so better is to keep margin now only by using /16 network.

--

Regards

Sakun Sharma