Tuesday, November 23, 2010

Any #networking and/or #osx #xserve gurus wanna take a look and answer some of my simple Questions?

I'm proposing a a networking over haul for our base of operations here in Salem, Oregon. I have rudimentary Networking knowledge and I've proposed the following design for our network. however, there are a few questions I have.

Networking Structure

We desire to launch a base-wide network with OS-X server to perform the following tasks:

• Managed Traffic Load
• Multi-LAN/WLAN multiple DSL lines
• Prioritized traffic groups (server or router?)
• Throttled guests (server or router?)
• Asset Sharing
• Contacts
• Files
•  Render Nodes (Final Cut)
• DHCP Assignment
• Subnets for Departments or Buildings (server or router?)
• Room for static IP’s
• User groups
• Managed asset access
• Accountability Online per user
• Program access
• Custom desktops
• Time Machine Backups
• Individual node backup over server
• Wireless Access Points / Extenders
• Managed by server group?
• Guest WiFi
• Staff Wifi/LAN


Managed Traffic Load

We propose a balanced multi WAN router (Peplink 310 or 30) to receive input from 3 Qwest DSL lines for approximately 36Mbs throughput to the internet. The Peplink models can manage user groups and throttle accordingly but it is unsure if this can be done through the server better.  Or can the server and router share user-groups to avoid multiple logins?

Asset Sharing

Files and contacts will be shared through access to the server. It is desirable to make the server files structure the default for saved files.

Render Nodes

The server and Intel OS-X Client Nodes should be accessible and configured for Final Cut render sharing through Compressor from the Communications Office.

DHCP Assignment

The Peplink router will have the IP address: 192.168.0.1 (gateway 255.255.255.0) and Assign IP’s in a range from *.*.*.20-254 to allow for static IP’s between the range of *.*.*.2-19

Again, unsure if IP assignment can be done better through the server. Can the main router (or server) manage subnets for departments as well? Should the server act as an interim to between the network and the gateway, or should the server be an offshoot of the network?

Subnets should be for departments over LAN and WLAN (as seen on Networking Map) and double as Guest AP’s / Extenders. 

• ToDo: Map Channel Optimization for WLAN AP’s

User Groups

It is desirable to have custom fetched desktops, program access, and shared asset access based on user-group assignment. Also, tracking and reporting of NSFW web activity. 

Time Machine Backups

A 4TB FAT32 server attached RAID 5 drive for OS-X and Windows system backup. Scheduled and managed by the server for individual nodes.

Wireless Access Points / Extenders

Dedicated AP’s in bridged extender mode can be placed in weak zones to extend range of Subnet Routers. Access and bandwidth are hoped to be controlled by user-group. Sys-Admins and staff have access to internal network. Guests have access to certain printers, and the internet with global and per user throttling.

Networking Structure.pdf (1009 KB)
View this on posterous

Posted via email from Josh Brown

No comments: