Are VLANs worth the extra work?

[altecsole]

The 2920 has SFP ports not GBIC.

 

 

Can you use compatible SFP transceivers, or is it better to stick with HP?

[FN-GM]

Yep - you're absolutely right. Cause of habit!

 

You won't be the last

 

Reason I wanted to mention it was if he is using SC fibre in his building he will need SC-LC cables as well to work with SFP modules. These are not required for GBIC.

 

- - - Updated - - -

 

Can you use compatible SFP transceivers, or is it better to stick with HP?

 

You can use compatible but I stick with original. I have seen in Cisco switches compatible SFP's stop working when you do a software update.

Edited December 6, 2016 by FN-GM

[altecsole]

 

You can use compatible but I stick with original. I have seen in Cisco switches compatible SFP's stop working when you do a software update.

 

Perfect; thank you.

[AlanD]

I've been thinking about doing more VLANs on our 450 PC network. We already use a VLAN for BYOD (...that seems like a no brainer....would seem pretty irresponsible to allow any potentially infected device onto your domain LAN). The driving force for me - is to be able to isolate networked projectors and printers from both domain and BYOD and selectively allow access by to staff with firewall rules (and to prevent bonjour printing on tablets to the "wrong" printer). The downside - we experienced one morning when domain PCs started picking up DHCP addresses from BYOD VLAN. Took us a while to realise we had an issue, then to figure out what was going on....then how to located the cause of it. All happened after a switch mysteriously rebooted and reset itself...

[Mistert89]

Buy SFP/GBIC via eBay. So much cheaper from equipment refurbishers like Rock Hall .co.uk. Full vat receipt etc. Nothing to lose.....

[FN-GM]

I've been thinking about doing more VLANs on our 450 PC network. We already use a VLAN for BYOD (...that seems like a no brainer....would seem pretty irresponsible to allow any potentially infected device onto your domain LAN). The driving force for me - is to be able to isolate networked projectors and printers from both domain and BYOD and selectively allow access by to staff with firewall rules (and to prevent bonjour printing on tablets to the "wrong" printer). The downside - we experienced one morning when domain PCs started picking up DHCP addresses from BYOD VLAN. Took us a while to realise we had an issue, then to figure out what was going on....then how to located the cause of it. All happened after a switch mysteriously rebooted and reset itself...

 

Sounds like it wasn't setup properly. I bet either you BYOD or main network are on VLAN 1?

[altecsole]

I thought I'd post an update on where I'm up to.

 

I bought a Dell N3048 switch and I've set this up on the bench with a DHCP server and a couple of test workstations. I've got three test VLANs setup and DHCP is working for all of them and routing is working too; which is great.

 

Now comes the problem. I've tried connecting a second switch but I can't get the VLANs to work. The test switches are Netgear and D-Link. I've setup the access ports as Untagged and the uplink to the Dell as Tagged. The uplink port on the Dell is set to Trunk (I've tried General too). Setup in this way I can't ping a test workstation on the Dell switch, even though they are both in the same VLAN. Any advice?

 

Thanks in anticipation.

[mavhc]

I thought I'd post an update on where I'm up to.

 

I bought a Dell N3048 switch and I've set this up on the bench with a DHCP server and a couple of test workstations. I've got three test VLANs setup and DHCP is working for all of them and routing is working too; which is great.

 

Now comes the problem. I've tried connecting a second switch but I can't get the VLANs to work. The test switches are Netgear and D-Link. I've setup the access ports as Untagged and the uplink to the Dell as Tagged. The uplink port on the Dell is set to Trunk (I've tried General too). Setup in this way I can't ping a test workstation on the Dell switch, even though they are both in the same VLAN. Any advice?

 

Thanks in anticipation.

 

Do you want all VLANs to go to the next switch? If so, trunk on both switches

[altecsole]

Do you want all VLANs to go to the next switch? If so, trunk on both switches

 

Thanks. Netgear and D-Link don't use Trunk and Access, they use Tagged and Untagged instead. As I understand it, Untagged is the same as Access and Tagged is the same as Trunk. I've set the connection as Trunk on the Dell and Tagged for the VLAN on the Netgear switch.

[FN-GM]

Thanks. Netgear and D-Link don't use Trunk and Access, they use Tagged and Untagged instead. As I understand it, Untagged is the same as Access and Tagged is the same as Trunk. I've set the connection as Trunk on the Dell and Tagged for the VLAN on the Netgear switch.

 

Its just the wording. If you configure them to use 802.1q on both sides it should work.

 

Make sure the native VLAN is the same on both sides.

[snagrat]

Thanks. Netgear and D-Link don't use Trunk and Access, they use Tagged and Untagged instead. As I understand it, Untagged is the same as Access and Tagged is the same as Trunk. I've set the connection as Trunk on the Dell and Tagged for the VLAN on the Netgear switch.

 

Dlink do use Trunk but it may depend on the switch