Network Backplane

MadMax wrote: What the heck...



Let's see if we can get some more activity in here...



My current switch is an HP ProCurve 2824 with cat5e and Cat6 in a direct hope run configuration.



Cat5e in the lounge and Cat6 for all the audio and servers.



Just curious as to what everyone else is using for switching and cabling.



Anyone using P.O.E. for VOIP phone systems?

Never heard of hope run maybe home run? Inquiring minds want to know.

I use Cat5 and Cat5e with a very basic (and now OLD) store-bought LyncSys hub, with home runs to each computer, doing peer to peer networking with six machines here. Files can be moved pretty quickly from one machine to another, although I don't network from machine to machine for production work per se. With Vista on three of the six machines, most of my networking problems (and slowdowns) have dropped dramatically, moreso than any hardware changes.



What kind of speed/throughput do you get with the HP ProCurve? Enough to run one machine paired with another, as if it were just another drive?

Hi,

Home setup here. Cat5 to 1 very old D-Link DSH-5. That goes out to 2 comps, one desktop type server in the basement, and my laptop. These are only used for dedicated VST and VSTi processing using Nuendo's networking feature and FX Teleport.



The laptop will also run wireless and is usually used as a remote. I know that's not "storage" but what the hell... it's sort of on topic right? :)

For archiving, I simply setup an iSCSI SAN on cat 6. Workstations are isolated from DMZ for security reasons. Computers with DMZ access are on a physically seperate LAN segment. (I don't like to take chances with data security), but the linux (ubuntu, specifically) based iSCSI san has worked out quite nicely. The HBA's were worth the investment, in my opinion.

Interesting thread. I'm learning PC world as we go here. For those who are too, I did a search for more on this and found this link

http://discountcablesusa.com/ethernet-cables100.html



here is an excerpt from the page:

Ethernet Cables

Comparison between CAT5, CAT5e, CAT6, CAT7 Cables



In the context of the 100-ohm UTP (Unshielded Twisted Pair) type of cable used for Ethernet wiring the only categories of interest are Cat3, Cat4, Cat5, Cat5e, Cat6, and Cat7. CATx is an abbreviation for the category number that defines the performance of building telecommunications cabling as outlined by the Electronic Industries Association (EIA) standards. Some specifications for these categories are shown further down.



Up until the late 1980s thick or thin coaxial cable was typically used for 10-Mbps Ethernet networks, but around that time, UTP cabling became more commonly used because it was easier to install and less expensive. UTP CAT3 and CAT4 were used for a quite limited time since the emergence of 100Base-TX networks meant a quick shift to CAT5. By the year 2000, moves to gigabit (1000Base-TX) Ethernet LANs created a need for another specification, CAT5e. CAT5e is now being superseded by CAT6 cable and there is a developing standard for CAT7.

then I searched for iSCSI SAN on cat 6 and found this link: here



Forgive my ignorance.. Is this how you are connecting multiple computers together to save all data onto one main storage device? here

audiokid,



Yes, what we were talking about is network-based central data storage for the studio. a SAN (Storage Area Network) is typically a network dedicated to linking multiple workstations or servers to one central data storage archive. In an enterprise environment, many times this will use very expensive specialized equipment (fiber channel adapters, SAN switches, etc..) that is quite cost prohibitive for most studios. iSCSI is a protocol that allows one to create a SAN using standard networking hardware one would use for a regular LAN. It also allows you to mix and match platforms between your initiators (that would be the workstations or servers) and your target (that would be the system you have designated as your central archive). For instance, if you have a windows based DAW and want to use a linux based SAN target, it's much easier than it was before (SAMBA can be quite glitchy) and it allows you to set up a dedicated network just for audio data traffic.

MadMax,



I use Win workstations primarily, however, the SAN is a closed network with no DMZ access, so not worried about intrusion issues. The key is keeping the SAN isolated from the DMZ (especially the target node) and using dedicated interface and backplane equipment, whether it be investing in HBA's or using standard gigabit NIC's and switches. For most studio uses, I think iSCSI is a reliable and cost-effective platform to use for data archiving. In an enterprise level IT environment is where I think it falls short and a more robust solution involving fiber channel is needed (such as EMC).

My hope run is really just a business network that is 10 years old. 100kbps with standard 3 com 8 port switches on each floor running on cat 5. I have 5 workstations attached by wire and 1 by wireless through a Linksys access point. The only thing we do here in true multiuser fashion is UPS and accounting. Otherwise, the network is used mostly for transferring files, backup, testing, etc. etc.

Cisco 2950 series switching. VLAN'd out with access lists to isolate DAWS from the net while allowing access to the files servers. Cat5e cabling. Linux file servers. Want to upgrade to gig speed but the Cisco gear for that is pretty pricey still on the used market

MadMax wrote:



Anyone using P.O.E. for VOIP phone systems?

Not in the studio but I installed a cisco voip system for the day job. Working on the higher level functionality it offers now like wireless phones, video teleconferencing etc