Re: Network Design

Tech-Archive recommends: Fix windows errors by optimizing your registry

buf wrote:
Thanks.. I thought that was all overkill :) I wanted to keep it a single subnet but was curious on best practice for that... Users are mostly office users (word, excel) We have a drafting department that does CAD but there are only 3 users there and they aren't doing intensive CAD or 3D stuff.. It's mostly file and print.. I'm moving to a SAN because we are doing a lot of scanning documents and image type things and will get more involved with that later.. I'm currently running out of space..

It is currently set up in the 172.22 range... It is a Win2k domain.. I'm moving to a Win2008 domain..

In a VLAN case how do users authenticate if the DC is in Say VLAN1 and you have users in VLAN2 or VLAN3..

I have a watchguard x550e in place that acts as the firewall.. From that goes into a dell powerconnect 5212 which the servers are connected to then to two other dell switches which the users are connected to..

I am pretty much re-doing the entire network so I'm wondering best practice for optimal performance.. I'll probably be playing with the NEW network for a while in the a test environment for learning purposes and then migrate everyone over. Being it isn't that big of a network I kind of have that luxury..

I am getting :

1- Dell PowerEdge 1950 this will be a Windows 2008 64 bit. This will be the DC (AD, DHCP, DNS, printer server)

1 - Dell PowerEdge 2950 (Backup DC, SQL server)

1 - Dell Equalogic PS5000E - ISCSI SAN.

2 - Dell PowerConnect 5424 GB switches to connect the SAN to the servers..


2 older servers from old network that I'll use to do things like (Anti-Virus server, fax server, web server, etc.)


Thanks for your input!


Hi buf, please follow Meinolf's advise: don't mix dc's and exchange/sql servers.

Also: read up on your RAID levels for these servers, as you might want to consider a mix of raid 1 and 5 for example. (on your NAS?)
I'll stop there; this is m.p.w.s.networking after all.

The Dell switches seem to have been designed with iSCSI in mind, I guess that means they support jumbo-frames; this will increase you iSCSI throughput. Make sure your (dedicated) nics support it too.

Since you're on the W2K and iSCSI tour: consider the future; Hyper-V failover clustering requires iSCSI targets (the NAS) to support SCSI-3 persistent reservation. If this might be in your future; check for the NAS to support this.

Have fun!

--

/ ) Regards,
/ /_________
_|__|__) Paul Weterings
/ (O_) http://www.servercare.nl
__/ (O_)
____(O_)
.

Relevant Pages

  • Trinity College, Cambridge-Computer Officer
    ... NETWORK AND SERVERS SUPPORT COMPUTER OFFICER ... and 33 days annual holidays. ...
    (uk.jobs.offered)
  • TRINITY COLLEGE CAMBRIDGE Computer Officer
    ... Servers and Network Support Computer Officer ... and 33 days annual holidays. ...
    (uk.jobs.offered)
  • Re: Event ID 1500, Your Profile can not be loaded
    ... The Service Pack is not supported by our software vendor. ... problems in servers that are lacking basic updates. ... you are connected to the network, or that your network is functioning ... see Help and Support Center at ...
    (microsoft.public.windows.terminal_services)
  • Re: Dcidag errors
    ... Port blockage between servers ... Other sorts of networking issues (lack of connectivity between the points ... These errors are typically a result of a network connectivity issue of some ... > replicating this nc. ...
    (microsoft.public.windows.server.active_directory)
  • Re: I need Job Blobb
    ... > Windows and Network administratation. ... > In a job I would like to administrate servers, ... > Title: ISP Network Administrator ... > o Building, installation, configuration and tuning ...
    (microsoft.public.cert.exam.mcse)