switch to switch different ips
I have two switches, two IP addresses. One switch with IP from first subnet, Second switch with IP from second subnet. I need one port to connect the two.
What do I need to do and how to get these two to talk and be able to access both of them from my machine?
What do I need to do and how to get these two to talk and be able to access both of them from my machine?
Dave Baldwin
You need two network cards.
ASKER
I am not sure I understand. I have two network cards on my server that I will be configuring them on. I just need to know how to configure them to talk to each other through one port. (One is going to be for phones and the other for data)
As far as accessing them I want to remote into them using the IP address. I currently do for the two switches I have here (same subnet) and the two routers I have externally (each with a different subnet different from here)
As far as accessing them I want to remote into them using the IP address. I currently do for the two switches I have here (same subnet) and the two routers I have externally (each with a different subnet different from here)
What kind of switches are you using? Are they managed or unmanged ? Depending on what type of switch you have, you might have to update your server route table and add static routes. This will allow the specific traffic to follow the path you tell it.
ASKER
One is HP Procurve the other is Luxul XMS
They are both managed
They are both managed
The following will make sense mainly if you want to keep your current management IPs for your switches. If not, things are a lot simpler, change the management IP of switch2 to be in the same subnet as switch1 for example. But I don't think you'd ask about that, so here's what I think you need.
You need to use a common subnet between the two, in order for them to talk to each other. You will then need to use routing (don't know if it's supported on your switch models) in order for your machine to connect to the second switch through the first one.
Here's an example for you. SWITCH1 = 172.16.1.1/24, PC = 172.16.1.2/24 , SWITCH2 = 192.168.1.1/24. (I'm only using /24s to keep it a bit simple.)
You need PC to be able to connect to SWITCH2.
a) An easy way out would be to create a second management interface on Switch2 -if it's supported by your model- so that SWITCH2 could be managed through 172.16.1.3 and 192.168.1.1 at the same time.
b) The other way would be to create a second interface with the IP 172.16.1.3 so that 172.16.1.1 and 2 would get that far, and 192.168.1.1 would be accessible through routing. You'd need to configure your default gateway with a command that sets 172.16.1.3 as the next hop for the network 192.168.1.0/24. Then you'd also need SWITCH2 to be able to route between the 2 networks, depends on model.
c) The third way would be to use a completely different subnet to connect the two switches. So what you'd end up with would be something like this:
PC (172.16.1.2) <====> S1 (172.16.1.1)<>S1(172.16.2.
Now, the above will also need routing to be an option, this time on both switches. You'd also need static routes on your default gateway (stating that the next hop for 192.168.1.0/24 is 172.16.1.1), on S1 (stating that next hop for 192.168.1.0/24 is 172.16.2.2) and on S2 (stating that next hop for 172.16.1.0/24 is 172.16.2.1).
You need to use a common subnet between the two, in order for them to talk to each other. You will then need to use routing (don't know if it's supported on your switch models) in order for your machine to connect to the second switch through the first one.
Here's an example for you. SWITCH1 = 172.16.1.1/24, PC = 172.16.1.2/24 , SWITCH2 = 192.168.1.1/24. (I'm only using /24s to keep it a bit simple.)
You need PC to be able to connect to SWITCH2.
a) An easy way out would be to create a second management interface on Switch2 -if it's supported by your model- so that SWITCH2 could be managed through 172.16.1.3 and 192.168.1.1 at the same time.
b) The other way would be to create a second interface with the IP 172.16.1.3 so that 172.16.1.1 and 2 would get that far, and 192.168.1.1 would be accessible through routing. You'd need to configure your default gateway with a command that sets 172.16.1.3 as the next hop for the network 192.168.1.0/24. Then you'd also need SWITCH2 to be able to route between the 2 networks, depends on model.
c) The third way would be to use a completely different subnet to connect the two switches. So what you'd end up with would be something like this:
PC (172.16.1.2) <====> S1 (172.16.1.1)<>S1(172.16.2.
Now, the above will also need routing to be an option, this time on both switches. You'd also need static routes on your default gateway (stating that the next hop for 192.168.1.0/24 is 172.16.1.1), on S1 (stating that next hop for 192.168.1.0/24 is 172.16.2.2) and on S2 (stating that next hop for 172.16.1.0/24 is 172.16.2.1).
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I'm not really objecting to anything, however according to the pdf you linked us to, I did not see routing as a feature anywhere.
Did I miss it?
This question has nothing to do with points or anything.
Did I miss it?
This question has nothing to do with points or anything.
ASKER
I was told that it did. They say yes but I too am not seeing it. I had to contact the manufacturer.
ASKER
Thank you, however I figured out how to configure with the help of outside consultant. Sorry, I did this before reading the post. I will give partial points for both of the post in trying to help me. Also, the post is not completely accurate, not for my setup. The Luxul does support Routing.