The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.
So, my boss has given me the job of re-data cabling a building he owns, and is planning to lease out.
Now, because he doesn't know whether a single, or multiple companies will be inhabiting the building he'd like to keep his options open with regards network infrastructure.
so.
If I bought 2 of these (I need more than 44 ports)
uplinked one to the other, and then set the port VLAN tags appropriately, would I be able to segregate the building into seperate networks as and when required?
Correct. Each VLAN would be its own isolated virtual LAN, which would accomplish your desired goal. The only way to bridge VLANs is to use another router, just as if they were separate physical LANs.
One other thing, are VLAN tags specific to individual switches, or are they um...generic is the best word I guess.
for example, if I had VLAN-1 on one switch, and VLAN-1 on another switch, then uplinked one switch to the other... would both VLAN-1s be, practically speaking, part of the same network?
for example, if I had VLAN-1 on one switch, and VLAN-1 on another switch, then uplinked one switch to the other... would both VLAN-1s be, practically speaking, part of the same network?
If you have a trunk configured between the two switches then vlan-1 on switch 1 would be the same network as vlan-1 on switch 2.
If your switches are trunked correctly then you can put any VLAN on any port on any switch in any combination. Least you can on Cisco switches, so I would hope its a feature on other ones.
Okay, I'm looking at the user guide for the Zyxel GS1548 (Here) and, while there is a section on trunking, that only seems to refer to aggregating ports into single links, not connecting switches together.... is that a different use of the term 'Trunk'?
If this switch doesn't support what I want to do, can anyone recommend a good, cheap switch that will? (ie: support VLAN, web management, stacking / trunking multiple switches)
After creating this link, which I suspect is their term for a trunk, can you then specify which ports can receive traffic from what VLANs? If so, same thing.
Okay, I'm looking at the user guide for the Zyxel GS1548 (Here) and, while there is a section on trunking, that only seems to refer to aggregating ports into single links, not connecting switches together.... is that a different use of the term 'Trunk'?
If this switch doesn't support what I want to do, can anyone recommend a good, cheap switch that will? (ie: support VLAN, web management, stacking / trunking multiple switches)
Cheers!
Yes, a Trunk is where you combine multiple ports into a single data link that has a higher throughput. However, it is not required to just connect the two switches together. You can just plug one port into the other and it will work. You would use trunking if you need more bandwidth between the switches than can be provided by a single port.
SiliconStew on
Just remember that half the people you meet are below average intelligence.
Okay, I'm looking at the user guide for the Zyxel GS1548 (Here) and, while there is a section on trunking, that only seems to refer to aggregating ports into single links, not connecting switches together.... is that a different use of the term 'Trunk'?
If this switch doesn't support what I want to do, can anyone recommend a good, cheap switch that will? (ie: support VLAN, web management, stacking / trunking multiple switches)
Cheers!
Yes, a Trunk is where you combine multiple ports into a single data link that has a higher throughput. However, it is not required to just connect the two switches together. You can just plug one port into the other and it will work. You would use trunking if you need more bandwidth between the switches than can be provided by a single port.
Just pointing out: in typical real world settings you'll be using a switch with line cards (modules/slots), and you'll have a line card with 10 Gig fiber or Ethernet ports to dedicate to trunking. You'll then just configure ranges of ports in the Ethernet line cards to various VLANs.
Okay, I'm looking at the user guide for the Zyxel GS1548 (Here) and, while there is a section on trunking, that only seems to refer to aggregating ports into single links, not connecting switches together.... is that a different use of the term 'Trunk'?
If this switch doesn't support what I want to do, can anyone recommend a good, cheap switch that will? (ie: support VLAN, web management, stacking / trunking multiple switches)
Cheers!
Yes, a Trunk is where you combine multiple ports into a single data link that has a higher throughput. However, it is not required to just connect the two switches together. You can just plug one port into the other and it will work. You would use trunking if you need more bandwidth between the switches than can be provided by a single port.
We're talking about two different meanings of "trunking." What OP needs to do if he wants his VLANs to work across both switches is trunking in the sense that a single uplink is configured to allow multiple VLANs to traverse it -- making it a trunk port instead of an access port. This will allow the scenario asked about where VLAN 2 on Switch1 and VLAN 2 on Switch2 are on the same "isolated" network. If the uplink port is not configured for trunking it will be treated like a normal access port and only permit traffic on its configured VLAN.
In Cisco-land bundling interfaces like that is called port channeling -- allows you to use dual uplinks without having one blocked by STP.
The switch should be able to do VLAN trunking (I think that is a Cisco-born term) because common sense dictates a switch that supports VLANs but can't trunk them is hardly better than a switch that doesn't support VLANs.
The switch should be able to do VLAN trunking (I think that is a Cisco-born term) because common sense dictates a switch that supports VLANs but can't trunk them is hardly better than a switch that doesn't support VLANs.
Posts
NintendoID: Nailbunny 3DS: 3909-8796-4685
One other thing, are VLAN tags specific to individual switches, or are they um...generic is the best word I guess.
for example, if I had VLAN-1 on one switch, and VLAN-1 on another switch, then uplinked one switch to the other... would both VLAN-1s be, practically speaking, part of the same network?
Tall-Paul MIPsDroid
If you have a trunk configured between the two switches then vlan-1 on switch 1 would be the same network as vlan-1 on switch 2.
If this switch doesn't support what I want to do, can anyone recommend a good, cheap switch that will? (ie: support VLAN, web management, stacking / trunking multiple switches)
Cheers!
Tall-Paul MIPsDroid
Yes, a Trunk is where you combine multiple ports into a single data link that has a higher throughput. However, it is not required to just connect the two switches together. You can just plug one port into the other and it will work. You would use trunking if you need more bandwidth between the switches than can be provided by a single port.
Just pointing out: in typical real world settings you'll be using a switch with line cards (modules/slots), and you'll have a line card with 10 Gig fiber or Ethernet ports to dedicate to trunking. You'll then just configure ranges of ports in the Ethernet line cards to various VLANs.
We're talking about two different meanings of "trunking." What OP needs to do if he wants his VLANs to work across both switches is trunking in the sense that a single uplink is configured to allow multiple VLANs to traverse it -- making it a trunk port instead of an access port. This will allow the scenario asked about where VLAN 2 on Switch1 and VLAN 2 on Switch2 are on the same "isolated" network. If the uplink port is not configured for trunking it will be treated like a normal access port and only permit traffic on its configured VLAN.
In Cisco-land bundling interfaces like that is called port channeling -- allows you to use dual uplinks without having one blocked by STP.
This is very true...also, re: the term VLAN trunk(ing), it's actually used in IEE 802.1Q (http://standards.ieee.org/getieee802/download/802.1Q-2005.pdf); you're probably thinking of Cisco's proprietary VTP protocol.