Tag Info

Hot answers tagged

5

If your switch isn't non-blocking then often the uplink ports are non-blocking, so they could have that benefit, otherwise I can't think of any other real differences between types of port.


4

Some switches will have additional benefits when using the SFP uplink ports that are not readily apparent. For example, they could have larger hardware buffers dedicated to than available to normal ports. This is more important on uplink ports as they are more likely to see bursts of traffic that may exceed their capacity.


4

To quote yourself, "The stacking cost just isn't worth it at this scale". Yes, you get some better administrative options with stacking, but it's probably not worth it here. Talking about stacking in general, with just 2 switches, only one stacking cable is necessary. Once you get to 3 switches or more, a ring is best because then any one switch could fail ...


3

I have a GS716T "Smart Switch" and was never able to get this to work. What I ended up doing was using a Python script to send a web request, login, and go to the web page that lists this information. Then I scraped it and stored it as needed. I don't use that switch anymore. I know it's a slightly different model, but same product family. Here is the ...


3

Is there a (significant) signal quality difference between ethernet switches? No. A 1000base-t, do some switches allow longer cable runs than other switches? Nope. If you need longer runs, use fiber. Long runs of copper, even if under spec, put your equipment at high risk of inductive lightning damage, which is another reason to use fiber.


3

The shared secret between a RADIUS server and a NAS (network access server - in your case the switch) serves several purposes: For many RADIUS messages, it provides an assurance that the message is from a NAS/RADIUS that has the same shared secret. It ensures that the RADIUS message has not been changed in transit. It is used to encrypt some RADIUS ...


2

RADIUS secrets authenticate the communication between the RADIUS client (the switch) and the RADIUS server. The intent of the RADIUS protocol is to abstract the authentication (authorization and accounting) away from the endpoint. There still needs to be some kind of authentication between the RADIUS client and server to insure that only authentic RADIUS ...


2

Ethernet VLANs do nothing more than "partition" switches such that they act like multiple switches, with separate broadcast domains for each VLAN. (That is, broadcast traffic from one VLAN doesn't appear in another.) If you're planning on doing port-based VLANs (that is, port X will be a member of VLAN 2, port Y will be a member of VLAN 3, etc) and you're ...


2

Just use a few links between the two switches in a LAG. it'll be cheaper you'll be easily able to increase bandwidth between the two switches by adding a port should that become necessary you can always upgrade to stacking modules later


2

Over the years I've had 10 - 15 small 10/100 Ethernet switches "go crazy" and begin flooding out all ports w/ 100Mbps of "garbage" traffic. In at least 3 cases I was able to reproduce the effect by plugging-in my laptop computer (and nothing else) to the switch. (I say "at least 3" because I finally to the point that I was just throwing the switches in the ...


1

Do the Trunk ports needs to be tagged or untagged on both switches? Tagged. Ports connected to devices that aren't VLAN-aware need to be untagged. Typically this would be your user-facing ports.


1

You havn't actually asked a question, so its difficult to ascertain what you are trying to do. Your design looks reasonably well throught out, but one thing appears to be wrong (it could be OK, and badly represented, but taken with your comment I think you may not have the concept down well), and that is this - VLANS are "virtual switches". They generally ...


1

I've worked with Cisco 3750-X series and it is not required to 'label' the switches, you just have to attach them (correctly!) and they just work. It is possible to tag each switch to indicate which is the "master" but in the end this really means nothing because all of the switches use the same exact running-config file anyway. If you read through the docs ...


1

There is nothing additional to install. On a node you configure /etc/puppet/device.conf with your switch information and then run puppet device on that node.


1

Ahh by now I probably spent more work-hours on it than what this switch cost. It is a Zyxel GS1510-24. I found an interesting forum post about it: "It appears that it only supports dynamic (tagged) if another switch sends it a GVRP message telling it to create a dynamic VLAN. VLAN 1 is static with no way to change it and if you use the web interface to ...



Only top voted, non community-wiki answers of a minimum length are eligible