+1 for Don. If your equipment can handle it, it's best to vlan the network for both security and saturation.
What I do is break down the 10.0.0.0 network like this. 10.1.x.0/24 10.2.x.0/24 10.3.x.0/24 Where the second octect is my site. 1 = HQ, 2 = RemoteSite1, 3 = RemoteSite2...etc. Each of the third octect x is my VLAN at my site. I use 10.1.10.0 to start my user vlans off. Then count up from there, 10.1.11.0. None of my remote sites are big enough to have anything other than 1 VLAn so for support purposes they will always be 10.x.10.0...unless they have voip which I vlan off to 10.x.99.0 at all my sites. I leave everything from 10.1.0.0-10.1.9.0 for me to play with for all servers/services/anything for the company. My suggestion is to spend some time to put your thoughts in a spreadsheet before actually implementing it. Just remember you'll need gateways for the VLANs to talk to each other. You'll also need "ip helper-address" (or non-cisco equivalent) for DHCP stuff. Good luck. Jason From: Don Ely [mailto:[email protected]] Sent: Thursday, December 17, 2009 2:51 PM To: NT System Admin Issues Subject: Re: Need more IP addresses Don't add another router... How much do you know about VLAN's? Can you think of any use for them? How many sites do you have? The quick and dirty solution is to change the subnet mask... The more robust solution might include VLAN's... On Thu, Dec 17, 2009 at 12:49 PM, Jeff Johnson <[email protected]<mailto:[email protected]>> wrote: I am in need of more IP addresses on my network. My current network looks like this: 192.168.1.x 255.255.255.0 I am using 248 IP's currently, so I have very little expansion available. I do see the potential to increase in the following year, so I had better get my butt thinking about this soon. Plus I have Christmas and New Year's holidays that I could work with no one on our network for 3 full days. I am thinking about changing my subnet to something like 255.255.254.0 or 255.255.252.0. Would this be a good way, or would I be better adding an additional router and just creating a new 255.255.255.0 network on 192.168.2.x? I guess my question is which is the "correct" way? Jeff Johnson Systems Administrator 714-773-2600 Office 714-773-6351 Fax [cid:[email protected]] ------------------------------------------------------------------------------------------ The pages accompanying this email transmission contain information from MJMC, Inc., which is confidential and/or privileged. The information is to be for the use of the individual or entity named on this cover sheet. If you are not the intended recipient, you are hereby notified that any disclosure, dissemination, distribution, or copying of this communication is strictly prohibited. If you received this transmission in error, please immediately notify us by telephone so that we can arrange for the retrieval of the original document. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
<<inline: image001.jpg>>
