<div>
<div class="content wysiwyg-content">
I manage a network with about 400 IP devices plugged into to our LAN. I know how to use VLAN's and I have a test environment in place with routing and everything working great. <br />
<br />
My final questions before I start breaking our production network down are:<br />
<br />
1) At what point is using VLAN's required on a LAN when security isn't a concern on the LAN?<br />
<br />
2) Is there a certain number of devices the we should try to stay under per VLAN?<br />
<br />
3) Is it possible for the VLAN routing on our backbone to cause noticeable latency?<br />
<br />
I'm trying to avoid causing administration overhead where it isn't needed.<br />
&nbsp;
</div>
</div>


I manage a network with about 400 IP devices plugged into to our LAN. I know how to use VLAN's and I have a test environment in place with routing and everything working great. 

My final questions before I start breaking our production network down are:

1) At what point is using VLAN's required on a LAN when security isn't a concern on the LAN?

2) Is there a certain number of devices the we should try to stay under per VLAN?

3) Is it possible for the VLAN routing on our backbone to cause noticeable latency?

I'm trying to avoid causing administration overhead where it isn't needed.
 

VLAN / Subnet Project

Networking software modules are interfaced with a framework implemented on the machine's operating system that implements the networking functionality of the operating system. The best known frameworks are the TCP/IP model and the OSI model. Systems typically do not use a single protocol to handle a transmission. Instead they use a set of cooperating protocols, sometimes called a protocol family or protocol suite.[9] Some of the best known protocol suites include: IPX/SPX, X.25, AX.25, AppleTalk and TCP/IP. Other protocols indirectly related to networking include the hypertext transfer protocol (HTTP) and its related technologies, Dynamic Host Configuration Protocol (DHCP), Domain Name Server (DNS) and other Internet protocols.

Networking Protocols

Networking hardware includes the physical devices facilitating the use of a computer network. Typically, networking hardware includes gateways, routers, network bridges, modems, wireless access points, networking cables, line drivers, switches, hubs, and repeaters. But it also includes hybrid network devices such as multilayer switches, protocol converters, bridge routers, proxy servers, firewalls, network address translators, multiplexers, network interface controllers, wireless network interface controllers, ISDN terminal adapters and other related hardware.

Networking Hardware-Other

The Windows operating systems have distinct methodologies for designing and implementing networks, and have specific systems to accomplish various networking processes, such as Exchange for email, Sharepoint for shared files and programs, and IIS for delivery of web pages. Microsoft also produces server technologies for networked database use, security and virtualization.