|
Question : Procurve 3400 & 2824 bridging
|
|
I currently have two physically separated LAN's in the same building, each with their own gateway (one on T1, one on DSL). They are two separate subnets (192.0.1.n is the primary, 192.168.1.n is the other). I need to connect the two. I recently received several new switches, including an HP Procurve 3400 as my core switch, and a Procurve 2824 for the second LAN's core. I am told that using the functionality of these two switches, I can bridge the two so that the second network can use the T1 & access files, etc. from the first subnet. If this is true, can anyone please point me in the right direction of the settings required to perform this? Thank you.
|
Answer : Procurve 3400 & 2824 bridging
|
|
This should work fine:
Configure 2824 two VLANs different subnets:
This previous EE solution looks perfect for the 2824: [Take a look]
http://www.experts-exchange.com/Networking/Q_21187426.html?query=Procurve+VLAN+routing&clearTAFilter=true
ftp://ftp.hp.com/pub/networking/software/59906023e01-Mgmt-ch16-IProuting.pdf
Configuring a Static IP Route
To configure an IP static route with a destination address of 192.0.0.0 255.0.0.0 and a next-hop router IP address of 195.1.1.1, you would enter the following commands:
HPswitch(config)# ip route 192.0.0.0 255.0.0.0 195.1.1.1
HPswitch(config)# write memory
Syntax: ip route < dest-ip-addr > < dest-mask > < next-hop-ip-addr >
or ip route < dest-ip-addr >/< mask-bits > < next-hop-ip-addr >
The < dest-ip-addr > is the routes destination.
The < dest-mask > parameter specifies the subnet mask for the routes destination
IP address.
Ones are significant bits and zeros allow any value. For example, the mask 255.255.255.0 matches on all hosts within the Class C sub-net address specified by the < dest-ip-addr >.
Alternatively, you can use the CIDR notation and specify the number of bits in the network mask.
For example, you can enter 209.157.22.0/24 instead of 209.157.22.0 255.255.255.0.
The < next-hop-ip-addr > is the IP address of the next router in the path to the destination.
-----------------------
Configuring the Default Route
You can also assign a default route and enter it inthe routing table. The default route is the route assigned to all traffic that has destinations that are not in the local routing table. For example, if 208.45.228.35 is the IP address of your ISP router, all non-local traffic could be directed to that route by entering the commands:
HPswitch(config)# ip route 0.0.0.0 0.0.0.0 208.45.228.35
HPswitch(config)# write memory
----------------------------
"Supposing you have correctly configured the two VLANS (the DEFAULT VLAN and 1 more VLAN, say vlan 2) and assigned the switch two DIFFERENT IP addresses on the two vlans. Let the address of the switch be 10.0.1.10 on vlan 1 and 192.168.150.10 on vlan 2 done using this:
HPSwitch(config)# vlan 1 ip address 10.0.1.10/24
HPSwitch(config)# vlan 2 ip address 192.168.150.10/24
HPSwitch(config)# write memory
Now the router (in the switch) is directly connected to both the subnets and thus has built in static routes and therefore you need not add routes yourself.
Just ensure that nodes on vlan 1 use 10.0.1.10 as the default gateway and like wise for vlan 2."
------------------------
Thanks for the info -- just wanted to determine the simpliest/easiest & most efficient approach. Bridge is usually done within the same network.
And you only need one switch to route the VLANs.
You can use the routing capabilites of you procurves. The 3400 may be a better performer -- more on this later.
|
|
|
|
|
