Connecting two switches using SFP modules
Hi All,
I have two Netgear GS724T v2 devices, 2 SFP modules and a 30m LCLC optical cable which I would like to use to connect two switches together but I am having massive issues - Probably because I am a noob!
I have 3 switches in total (all GS724T) and have 2 connected via Ethernet with vlans trunked and this is working perfectly. However I want to connect the third switch via fibre using the SFP modules but cant seem to figure out to configure this. I am reading up on LAG but I cant see how to trunk and get the two switches communicating.
In the crudest form, Ports 1, 2, 3 and 4 will have different vlans configured on them. The SFP module (port 25 (even though its a 24 port switch)) should be trunked with vlans 1, 2, 3, 4.
Any help?
Thanks in advance
I have two Netgear GS724T v2 devices, 2 SFP modules and a 30m LCLC optical cable which I would like to use to connect two switches together but I am having massive issues - Probably because I am a noob!
I have 3 switches in total (all GS724T) and have 2 connected via Ethernet with vlans trunked and this is working perfectly. However I want to connect the third switch via fibre using the SFP modules but cant seem to figure out to configure this. I am reading up on LAG but I cant see how to trunk and get the two switches communicating.
In the crudest form, Ports 1, 2, 3 and 4 will have different vlans configured on them. The SFP module (port 25 (even though its a 24 port switch)) should be trunked with vlans 1, 2, 3, 4.
Any help?
Thanks in advance
Patrick Bogers
Not a Netgear expert but i would check which mode the fiber ports are, ethernet or stack... if stack for sure you cannot create a trunk.
ASKER
That's half the issue :) Cant seem to find the SFP ports in the port list - I see everything from ge01 to ge24 but not the SFP modules on 25 and 26 :( Not sure what's going on. Firmware is up to date and hasn't resolved it.
Have you tried: show stack-port
ASKER
Unfortunately thee switch doesn't have command line based config, only GUI based - but it's not very intuitive.
Ah thats nice :( Do you have original netgear prosafe GBIC's?
Just because you have GBIC modules doest say they are compatible.
Just because you have GBIC modules doest say they are compatible.
ASKER
They are Cisco GBICs which netgear say are compatible. And when connected it shows a connected link light. So I don't think the issue is related to the cable or the sfps. I've been reading up and I've read that sometimes these ports are paired with copper ports? Looking at the switch it has lines that would suggest 23 and 24 are paired but no idea
Hm ok. I would say if the lights state they are connected (stacked) and you have the same VLANs configured on both switches it should communicate. Did you check if you were able to?
Are the SFP ports not shared with the last two copper 1000-base T ports (23 and 24), in which case you can use either copper or fibre? It looks that way based on a google image search, but as I don't have a netgear I can't verify this.
ASKER
Hi Ralph, this what I've been reading also. Does this mean I need to trunk the clans to the copper ports only?
Patrick, apologies, I had an emergency last night so will be picking this back up today.
Patrick, apologies, I had an emergency last night so will be picking this back up today.
I would expect that if you configure the trunk settings on port 23 for the first fiber connection and 24 for the second, it should work.
Put a bit of tape over the copper ports so they don't get used somewhere down the line by someone who isn't aware of the configuration - I've no idea what happens if you try to use both at the same time, but I can't imagine it would be good. Best case, the device connected to the copper just won't get a connection, worst case: the switch will decide to stop using the fiber interface. Or try it out and let us know what happens!
Put a bit of tape over the copper ports so they don't get used somewhere down the line by someone who isn't aware of the configuration - I've no idea what happens if you try to use both at the same time, but I can't imagine it would be good. Best case, the device connected to the copper just won't get a connection, worst case: the switch will decide to stop using the fiber interface. Or try it out and let us know what happens!
Hi Amarjot,
No apologies needed, i find this a interesting thread.
No apologies needed, i find this a interesting thread.
ASKER
Time for an update!
So I got everything set up as it should be and then re-connected the SFP modules with a cable from vlan 1 to port 1 - For some reason I was dropping packets all over the place and had to unplug the fibre to get things back online again. So this didn't work.
The current config is as follows:
Port 23 and 24 have been added to LAG1. LAG1 has been trunked with VLANs 1, 2, 3 and 4. This is as it is described. Something seems fishy with the new Switch so I may try to get this RMA'd and try again!!
Going to get the RMA process started but if you guys can see any issues in the meantime, please advise!
Thanks
So I got everything set up as it should be and then re-connected the SFP modules with a cable from vlan 1 to port 1 - For some reason I was dropping packets all over the place and had to unplug the fibre to get things back online again. So this didn't work.
The current config is as follows:
Port 23 and 24 have been added to LAG1. LAG1 has been trunked with VLANs 1, 2, 3 and 4. This is as it is described. Something seems fishy with the new Switch so I may try to get this RMA'd and try again!!
Going to get the RMA process started but if you guys can see any issues in the meantime, please advise!
Thanks
If you want to use one SFP port per switch to connect the switches, why exactly do you need a LAG (Link aggregation group)?
Just for the record, the term 'Trunk' has 2 different meaning in networking:
- Cisco: a trunk port carries multiple VLANs, but can be a single port or a LAG (Etherchannel in Cisco),
- Everybody else (HP, Brocade): a trunk is multiple ports used as one, faster logical port, also known as LAG, which might be static or LACP configured.
Just for the record, the term 'Trunk' has 2 different meaning in networking:
- Cisco: a trunk port carries multiple VLANs, but can be a single port or a LAG (Etherchannel in Cisco),
- Everybody else (HP, Brocade): a trunk is multiple ports used as one, faster logical port, also known as LAG, which might be static or LACP configured.
ASKER
Hi TimotiSt,
from the research I've been doing so far, it looks like ports 23 and 24 are indeed shared with the sfp ports. I plan to run one fibre cable plus two copper cables (23+24 and 25(sfp)) for redundancy. I read that, should the fibre be connected, this will take precedence over the copper, the copper will only kick in should the fibre fail.
I'm not familiar with LAG, LACP hence why I'm struggling with the set up - any ideas how to resolve?
Thanks
from the research I've been doing so far, it looks like ports 23 and 24 are indeed shared with the sfp ports. I plan to run one fibre cable plus two copper cables (23+24 and 25(sfp)) for redundancy. I read that, should the fibre be connected, this will take precedence over the copper, the copper will only kick in should the fibre fail.
I'm not familiar with LAG, LACP hence why I'm struggling with the set up - any ideas how to resolve?
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi Ralph, thanks for that breakdown. I will try this first thing tomorrow. Also, I have a rma in place so if this switch continues to give issues, I'll have a known working version by Tuesday!
Thanks again
Thanks again
ASKER
Hey Ralph,
Got the replacement Switch today and the config worked a treat.
Ports 23 and 24 added to LAG1
VLANS 1, 2, 3, 4 Trunked to LAG1
Port 23F (SW1) Connected to Port 23F (SW2)
Patch Lead connected to Port 23T (SW1) to Port 23T (SW2)
Patch Lead connected to Port 24T (SW1) to Port 24T (SW2)
Found the reason for my lost packets also... Like an idiot, I left the patch cable in Port 1 (SW2) to Port 11 (SW1) for configuration which caused a loopback. Yanked her out, tagged by VLANs and everything is working as should!
Thanks for everyone for all of your help
Ajay
Got the replacement Switch today and the config worked a treat.
Ports 23 and 24 added to LAG1
VLANS 1, 2, 3, 4 Trunked to LAG1
Port 23F (SW1) Connected to Port 23F (SW2)
Patch Lead connected to Port 23T (SW1) to Port 23T (SW2)
Patch Lead connected to Port 24T (SW1) to Port 24T (SW2)
Found the reason for my lost packets also... Like an idiot, I left the patch cable in Port 1 (SW2) to Port 11 (SW1) for configuration which caused a loopback. Yanked her out, tagged by VLANs and everything is working as should!
Thanks for everyone for all of your help
Ajay
Awesome. Glad you got it sorted!