Connecting two network switch over fibre

Hewlett-packard Probook 4530s silver not...
April 17, 2014 at 08:27:18
Specs: Windows 8.1, I3/8GB
OK I have two network switches. first switch is connected to the router and works fine,how can i connect the second the switch over fibre

See More: Connecting two network switch over fibre

Report •


#1
April 17, 2014 at 08:29:20
You would need switches that support fiber modules or get a fiber to Ethernet converter for both ends of the fiber.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#2
April 17, 2014 at 08:50:12
Yes thes two switches support fibre connection using SFP

Report •

#3
April 17, 2014 at 09:39:27
When you say "support fibre connection using SFP" do you mean they have the GBIC's already built into the switch?

If so, then all you'll need is a preterminated (sfp) fiber optic cable of the correct length to run between them.

My switches just come with a slot for a GBIC and I have to buy those as well. So if yours are the same, you'll require two GBIC's as well as the cable.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

Related Solutions

#4
April 17, 2014 at 10:25:03
Curt, I have done that and I see an activity on the status light. but when i connect a device i don't get IP

Report •

#5
April 17, 2014 at 10:44:47
thedzaho in your opening post you asked how. Why, when it appears your question now is why doesn't it work?

How about posting the specs of the switches as well as the specs of the cable you are using.

Also tell us if you are using vlans, if you know.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#6
April 17, 2014 at 11:28:37
wanderer the switch is Dlink DES 3828P with vlan which is connected to the router and the second switch Dlink DGS 1210 no vlan is linked with ULC to ULC Fiber Optic Cables coming from the fibre splice box

Report •

#7
April 17, 2014 at 12:09:54
I have yet to work with any managed D-Link switches so am unfamiliar with those models.

If your trunk ports aren't configured correctly, then clients will not be able to talk to the DHCP server. When you set the fiber link up, did you confirm connectivity between switches? If not, this is step one after making the physical connection.

You state the second switch has no VLAN. By this I'm assuming you mean, you've left it setup with the factory defaults which in every switch I've worked on is, VLAN 1 (the default VLAN) is assigned to every port on the switch. If this is true for your switch, then you need to ensure VLAN 1 is the primary VLAN on the port of the other switch you're connecting to. Again, both ports would have to be configured as "trunk" ports and set to "Tag all"

When working with VLAN's you need to duplicate VLAN's across all switches. For example....

Where I work, VLAN 1 (default) is our management VLAN. All network appliances have IP's on the subnet belonging to this VLAN and no other devices (printers, clients, etc) use this subnet/VLAN. So, if I were to add a switch to my network and leave it with the default configuration (ie: VLAN 1 on all ports) then clients would not be able to communicate as they are on different VLAN's.

So, lets say your client is using VLAN 2 and that's the VLAN your client DHCP server resides on. Now you plug a client computer onto your new switch, even if you have the uplink ports configured correctly, if the client is plugging into a port that's assigned VLAN 1, it will not be able to reach the DHCP server because it's on VLAN 2. VLAN's 1 and 2 are segregated from each other and do not speak to each other. You would therefore have to create VLAN 2 on your new switch, add that VLAN to the uplink (trunk) port and then, it could reach the DHCP server.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***

message edited by Curt R


Report •

#8
April 17, 2014 at 13:50:45
Yep that's why I asked about vlans. It presently doesn't work because of the vlans on the main switch.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#9
April 18, 2014 at 06:35:53
@Curt R I really appreciate your help so much. Yes connectivity between the two switches are active. Now talking of trunk, which switch should be trunked?? Switch 1 has a VLAN of 23, should I configure VLAN 23 on Switch 2 as well ??

Report •

#10
April 18, 2014 at 09:19:13
It does not make sense to have a single vlan unless its just the default vlan. You might want to log into the main switch and document its configuration.

You then need to add all vlans to both ports connected the switches as well as configuring the vlans on the added switch.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#11
April 18, 2014 at 09:58:21
Wanderer, you mean i should configure VLAN 23 for all port on Switch 2

Report •

#12
April 18, 2014 at 10:04:20
Have you spent any time googling vlans so you understand what they are and how they work?
Did you review the configured switches vlans? There can't just be one. If there is just one having vlans is pointless.

But if this is the case, vlan 23 has to exist on every port on both switches as well as the trunk connection between the switches.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's

message edited by wanderer


Report •

#13
April 21, 2014 at 03:01:54
I have been able to solve my issue, thanks to you guys.
What I did was to create a VLAN 23, tagged the uplink port (trunk port) and then untagged all other ports on Switch 2. And voila, there I have clients obtaining IP address

Thanks once more.


Report •

#14
April 21, 2014 at 07:45:27
You're welcome............I suppose.

But you'd do well to follow wanderer's advice and actually do some reading and research on VLAN tagging. Your grasp of it seems to be very poor. If you had even a basic understanding of VLAN tagging, you wouldn't have needed to ask this question.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#15
April 21, 2014 at 08:28:02
Yeah, I have no clear understanding of VLAN.

Thank you.


Report •

Ask Question