Network layout showoff

[ionbasa]

11 hours ago, System Error Message said:

Some of you seem to have fancy equipment but supermicro isnt everything. 1st gen iseries xeons can be overclocked if used with consumer boards and they do overclock very well requiring only a small bump in voltage for a huge increase. for dual socket overclocking you would need the evga board which is a rarity nowadays. Nothing more satisfying than to bring something back from the dead and overclocking it far for practical use.

 

You can click here about my modified router. Thick lines indicate LACP or 10Gb/s

 

GPGPU cluster performs all sorts of tasks such as file server, cluster compilations, etc.

 

Trying to keep my network as efficient as possible. I do have other switches and routers on standby but they arent used. This means using only 1 switch for efficient switching, having standby/hibernate and remote wake up and shut downs, lots of other things too. Still in the works but this is what i have at the moment. I wire everything i can.

 

For a bit more detail my GPGPU cluster consists of various architectures. I try to get my hand on the best of every architecture. Even some of the laptops use eGPUs sometimes.

 

Not many desktops as i've crammed them into 2U rack cases. KVM handled by one of the laptops.

Out of curiosity, what are are you using to manage your GPGPU cluster? Have you looked into using infiniband to increase throughput between slaves and the host? I've heard infiniband with DMA to the GPUs can offer an nifty speed increase when compared to traditional 10Gbps Ethernet (in some use cases).

[System Error Message]

11 hours ago, ionbasa said:

Out of curiosity, what are are you using to manage your GPGPU cluster? Have you looked into using infiniband to increase throughput between slaves and the host? I've heard infiniband with DMA to the GPUs can offer an nifty speed increase when compared to traditional 10Gbps Ethernet (in some use cases).

I use SFP+ direct. Most wired things are close to the switch. As for DMA to the GPUs depends on the linux drivers, software and if the GPUs themselves support it as i use consumer GPUs. Windows doesnt support the NICs used not even windows server and LACP is an important feature for me. Some of them use SFP+ and some use quad port intel server NICs. They consist of unequal systems so the faster ones get SFP+ and slower ones get intel server NICs.

 

As for speed its not an issue but using ssh eats a significant amount of a CPU when you start hitting 1Gb/s.

 

 

[divito]

Not really following the rules, but I felt like mapping out the basic of basic that is my network at home.

 

[krowhill]

Some notes.

All NICs are 1000/100/10 unless otherwise noted, all lines are CAT 5e, all switches are unmanaged TPLink 1000/100/10.

[brwainer]

8 hours ago, krowhill said:

Some notes.

All NICs are 1000/100/10 unless otherwise noted, all lines are CAT 5e, all switches are unmanaged TPLink 1000/100/10.

What thin client are you using? Every result I've found for Vcenter shows it was something from back in the ESXi 3 days

[krowhill]

I just got a L300 by NComputing, I haven't set it up yet, so I am not entirely sure, I believe it just means I have to install a software package on the VM itself.  The price was good so I picked it up.

[krowhill]

On 9/30/2016 at 1:46 AM, brwainer said:

What thin client are you using? Every result I've found for Vcenter shows it was something from back in the ESXi 3 days

I just picked up a NComputing L300 for $40USD, I haven't actually set it up, from what I understand all that it requires is installing a client program on the VM itself.

[Guest]

On 07/09/2016 at 9:58 AM, Teshy09 said:

so are these virtualised labs using gns3 / or has anyone purchased the equipment and deployed physically ?

They're all meant to be environments that users are running at home.

 

I should also probably get around to posting mine once it's completed

[Acolyte_of_PC]

This is it, finally got around to making one of these thanks to it being a requirement for my networking class. We are currently thinking of building a NAS out of old computer parts and new HDD to add to our massive home network.

[MacA]

So this is my home network. Not best, I only did it because I was extremely sick of consumer hardware. Although, that's another story.

 

Basically the network cable comes in from Telstra, Which from who I buy a 100/2mbit connection. I only really get about 40/0.8mbit. Its better than ADSL here though.

Then It goes in to the Telstra provided router. Then into my new Edgerouter POE. From there it's going into my home network wireless, and my 24 port EdgeSwitch.

I also have 2 Synology NAS's. One at my house and the backup at the neighbours. The EdgeSwitch also connects to about 10 computers. The router also connects to a backbone ubiquiti dish link (Linus showed it here). I have a receiver on the other side as well as a another consumer grade router, of which the owner of the second house chose. I also provided them a Ubnt UAP-AC-LR, which I manage from a PC In my rack which runs UBNT Controller.

 

Future Plans:

• Run a wired cable from my house to the neighbours.
• Include them home phone.

Notes

• The neighbours are family relatives and don't pay.
• There QOSed to 5mbit/0.1mbit

 

 

 

 

 

 

Thanks for any suggestions. This was all done on a budget.

 

 

 

Note: I put in a rackmount NAS on accident. (I Actually have 2 DS412+'s), One in the current spot and one backup connected to the receiver at the neighbours house for backups.

 

. 

[Ezzy-525]

On ‎17‎/‎08‎/‎2014 at 0:42 PM, TheRoss0411 said:

I can't even bridge my two routers

My Virgin Media Superhub has absolutely pants WiFi...took me a good 15mins to get the damn thing to recognise a second router to handle WiFi with the Superhubs radio turned off.

 

And, I've done it before. Unfortunately, networking usually decides to do whatever the hell it wants and only rewards persistence. If you think it will work straight off...you're gonna have a bad time mkay ?

[dr_sepheroth]

Now all we need is a network diagram of an ISP internal network setup and we will all be home free, till next term, studying.

 

Complex stuff....

[Lurick]

1 hour ago, dr_sepheroth said:

Now all we need is a network diagram of an ISP internal network setup and we will all be home free, till next term, studying.

 

Complex stuff....

 

Don't even need an ISP internal network setup diagram for complex. Just a good size enterprise company should do the trick. Heck, for a testbed we have setup in our lab if you take a basic Vizio diagram size, with about 35 devices in the standard block. Imagine that multiplied by 30.

[brwainer]

1 hour ago, dr_sepheroth said:

Now all we need is a network diagram of an ISP internal network setup and we will all be home free, till next term, studying.

 

Complex stuff....

The rules from the first post say you shouldn't post your work networks. But a standard ISP network is going to be pretty bland - a CMTS or DSLAM for connections to residents, this connected by fiber or coax (even DSL uses coax for backhauls, or did before fiber) to routers (true routers, as in devices that only route). And that's everything if you are talking about what it takes to get people to the internet.

 

Things can get more complex when you talk about MPLS or MetroE products, because then you typically start talking about routing tags (as in, the route through the network is decided at the edge, not at each riuter) and extra VLAN tags to seperate customers.

 

A WISP network would be interesting to see for me, because they typically have lots of PtMP APs with various methods of connecting them together, like PtP wireless, and every type of wired connection imaginable.

[dr_sepheroth]

I may be a computer geek but I know when I have been out done/ what is;

• MPLS
• MetroE
• PtMP
• WISP
• CMTS
• DSLAM 

[brwainer]

7 minutes ago, dr_sepheroth said:

I may be a computer geek but I know when I have been out done/ what is;

• MPLS
• MetroE
• PtMP
• WISP
• CMTS
• DSLAM 

• MPLS - Multiprotocal Lable Switching: A label is made for each endpoint, and the path through the network for each label is predetermined and known by all the devices. A bandwidth limit is typically applied for each label as well. Usually each label is only for communication between two endpoints, I'm not sure if that's how the protocol is required to work, or if that's just how it is always used. Data on the network is handled purely by its label, meaning that the data being carried can be any other type of communication. This makes it more flexible and efficient than ethernet switching and IP routing.
• MetroE - Metro Ethernet: an ethernet network that is across a metro area (a city and some of its surrounding area). This is also called a MAN or Metro Area Network. It can be used to connect seperate offices in a city. Simple implementations just use QinQ VLAN tagging to seperate customers. 
• PtMP - Point to MultiPoint: basically the same as your home router/ap, which is a single point and talks to multiple client endpoints. But a PtMP typically uses a sector antenna, which is an antenna that only broadcasts in a 30 degree wide direction. Often a WISP will use one of these on a tower or tall building and point it towards multiple customers' houses, if they are all in the same direction.
• WISP - Wireless ISP: an ISP that connects to their customers using wireless technologies. See the video Linus made about the Ubiquiti product that does wifi over several miles - that was two PtP antennas, but a WISP can use much more complex setups.
• CMTS - Cable Modem Termination System: The device that talks to all the DOCSIS modems connected in a specific geographic area, like part of a neighborhood. This is where the bandwidth limitations of DOCSIS take place, because the single coax connection between the CMTS and a bunch of modems can only carry a specific amount, which is limited by the DOCSIS version of the CMTS (and if there is a few old modems, they do cause the other modems to slow down because the CMTS has to take more time to talk to the old ones)
• DSLAM - Digital Subscriber Line Access Multiplexor: The device that talks to all the DSL modems in a given geographic region. Because there is a dedicated phone line to each customer, the bottleneck is not  the bandwidth to all the customers, but what version of DSL the DSLAM uses, and what its upstream bandwidth to the rest of the ISP's network is. The distance to a specific customer matters much more than with DOCSIS because amplifiers cannot be used, but one customer does not slow down other customers as it does with DOCSIS.

[dr_sepheroth]

Thank you very much this helps me quite a bit with another issue I have been having for a few years. I think I just worked out why my ISP cuts out once a month.

 

At least once a month we have very stormy weather (including lightning and thunder) that would set up a signal block in the atmosphere between a PtMP network.

[Kovi]

This is my network. The items in red are planned, I just don't know if they will work. The idea is to have my pc, and only my pc, be able to access the cameras, while still having access to the main network. 

[Guest]

 

20 minutes ago, Kovi said:

This is my network. The items in red are planned, I just don't know if they will work. The idea is to have my pc, and only my pc, be able to access the cameras, while still having access to the main network. 

You'd want to look at VLAN tagging specific ports in that case. Have the cameras as well as your PC with untagged VLAN traffic meaning they are segregated from the rest of the network. Note you'll need a smart/managed switch that supports VLAN tagging.

[Zoravar]

On 11/27/2016 at 5:10 PM, Windspeed36 said:

 

You'd want to look at VLAN tagging specific ports in that case. Have the cameras as well as your PC with untagged VLAN traffic meaning they are segregated from the rest of the network. Note you'll need a smart/managed switch that supports VLAN tagging.

 

 

Is it possible to have a single VLAN supporting NIC connect to two VLAN networks at once?  Such as a private VLAN network with no internet (for cameras) and a second VLAN network for internet and other devices?

[jagdtigger]

This will sound a little bit silly but im planning on making a cabinet for my networking stuff and i need advice on how much airflow it will need. Networking stuff:

Spoiler

Netegear fvs336g

TP-Link TL-SG3216

NSA325

NAS540

Arris modem

 

[Zoravar]

On 12/12/2016 at 7:15 AM, jagdtigger said:

This will sound a little bit silly but im planning on making a cabinet for my networking stuff and i need advice on how much airflow it will need. Networking stuff:

  Hide contents

Netegear fvs336g

TP-Link TL-SG3216

NSA325

NAS540

Arris modem

 

1

 

 

 

 

3

 

 

 

You might want to consider making this its own topic.  But regardless, here is my opinion:  With the higher end switches and two NAS units going in the cabinet, you'll probably need active cooling (a fan).  There are a lot of pre-made cabinet fans to choose from.  Here are a couple things to consider: 

1. Get one with an AC (wall) plug on it, so you don't have to power it off of a USB port on one of you NAS units.  (But a USB one would still work). 
2. Get one with some kind of speed control.  You can adjust it to find the right balance between noise and heat. 
3. Get one with fan grills on it to give the fans some protection against wires and other foreign objects.

Here is an example:  http://a.co/9SmMOlh  This exact unit would not work for you in Hungary because of the plug type and voltage.  However, it gives you an example to go off of. 

 

A cheaper (do it yourself) alternative:  You can get an old computer fan and attach an old USB plug to it.  Then buy a fan grill and screw it all to the side of the case (after cutting a hole).  

[jagdtigger]

1 hour ago, Zoravar said:

You might want to consider making this its own topic.  But regardless, here is my opinion:  With the higher end switches and two NAS units going in the cabinet, you'll probably need active cooling (a fan).  There are a lot of pre-made cabinet fans to choose from.  Here are a couple things to consider: 

1. Get one with an AC (wall) plug on it, so you don't have to power it off of a USB port on one of you NAS units.  (But a USB one would still work). 
2. Get one with some kind of speed control.  You can adjust it to find the right balance between noise and heat. 
3. Get one with fan grills on it to give the fans some protection against wires and other foreign objects.

Here is an example:  http://a.co/9SmMOlh  This exact unit would not work for you in Hungary because of the plug type and voltage.  However, it gives you an example to go off of. 

 

A cheaper (do it yourself) alternative:  You can get an old computer fan and attach an old USB plug to it.  Then buy a fan grill and screw it all to the side of the case (after cutting a hole).  

I already solved the PSU problem(link its maybe a little bit overkill but better to be safe than sorry ), i just do not know how much airflow is needed. Im planning on using 140mm high static pressure fans(with dust filters on the intake fans).

[pbx2]

This is my current one after the upgrade i will be doing soon, it's a lan network so no internet

[yamileon]

my simple home network 

everything not connected by lines is wireless