+ Post New Thread
Results 1 to 10 of 10
Wired Networks Thread, Connecting two subnets together through procurve switches in Technical; ...
  1. #1

    Join Date
    Sep 2007
    Posts
    160
    Thank Post
    15
    Thanked 3 Times in 3 Posts
    Rep Power
    15

    Connecting two subnets together through procurve switches

    We have had a Virgin Media 1GB Ethernet extension fibre link installed today between both our upper and lower schools which Iím running into our core HP 5406 switches at both ends.

    They are on separate subnets upper school is 10.5.224.0/21 and lower school is 10.11.224.0/21. The domain and active directory are the same and also setup correctly in sites and services (they are currently connected through a 40mb VLAN)

    Fibre end runs to the core switch 10.5.225.102 at the upper school is on port B22
    The other end runs to the core switch 10.11.226.151 at the lower school on port B22

    only thing I did was add an IP of the other subnet in the VLAN 1 of both switches and I also enabled ip rip in the config of both switches

    Upper School Switch 10.5.225.102
    (config) >ip rip
    (config) >vlan 1
    (vlan 1) >ip address 10.11.231.253/21
    (vlan 1) >write mem

    Josephs Switch 10.11.226.151
    (config) >ip rip
    (config) >vlan 1
    (vlan 1) >ip address 10.5.231.253/21
    (vlan 1) >write mem

    From the above CLI commands I can get the switches to communicate with each other, and the switches themselves can communicate with any other device on both subnets however other devices and other switches still cannot communicate cross subnets

    Hope this make sense can anyway help me to let me know what Iím missing or doing wrong please?

  2. #2

    Join Date
    Apr 2012
    Location
    Leeds
    Posts
    302
    Thank Post
    0
    Thanked 67 Times in 53 Posts
    Rep Power
    36
    What does the routing table on both switches show?

  3. #3

    SYNACK's Avatar
    Join Date
    Oct 2007
    Posts
    11,223
    Thank Post
    874
    Thanked 2,717 Times in 2,302 Posts
    Blog Entries
    11
    Rep Power
    780
    They are both in vlan 1 so are not separated in layer 2 leaving all of your broadcasts traversing the link. Your client default gateways need to be the switch on each side so that all traffic checks there for a route and you should have a separate vlan inbetween them (vlan 2 ) for the link, this way you can have each core switch have vlan 1 with ip address 10.11.231.253/21 and vlan2 with 192.168.100.100
    have a static route for the other network
    ip route 10.5.231.253/21 192.168.100.101 (address of the other switch on the link) and a default route on each switch to their local internet connection.

    This should mean that when a packet is received that is addressed to something non-local it will hit the switch, the switch will check and see the route for the other network (if that is where it is headed) and forward it to the vlan2 link, if not it will go out to the net (assuming no silly proxy rubbish in which case you would have no default route)

    It needs to be setup on both ends as IP connectivity is end to end, ie it needs to know where to go at every step of the way to get there and then back.

  4. 2 Thanks to SYNACK:

    chrisjako (24th July 2014), Oaktech (24th July 2014)

  5. #4

    Join Date
    Sep 2007
    Posts
    160
    Thank Post
    15
    Thanked 3 Times in 3 Posts
    Rep Power
    15
    Quote Originally Posted by SYNACK View Post
    They are both in vlan 1 so are not separated in layer 2 leaving all of your broadcasts traversing the link. Your client default gateways need to be the switch on each side so that all traffic checks there for a route and you should have a separate vlan inbetween them (vlan 2 ) for the link, this way you can have each core switch have vlan 1 with ip address 10.11.231.253/21 and vlan2 with 192.168.100.100
    have a static route for the other network
    ip route 10.5.231.253/21 192.168.100.101 (address of the other switch on the link) and a default route on each switch to their local internet connection.

    This should mean that when a packet is received that is addressed to something non-local it will hit the switch, the switch will check and see the route for the other network (if that is where it is headed) and forward it to the vlan2 link, if not it will go out to the net (assuming no silly proxy rubbish in which case you would have no default route)

    It needs to be setup on both ends as IP connectivity is end to end, ie it needs to know where to go at every step of the way to get there and then back.
    how should the vlan 2 be tagged?

    vlan1 untagged on port b22 and vlan2 tagged on port b22?

  6. #5

    SYNACK's Avatar
    Join Date
    Oct 2007
    Posts
    11,223
    Thank Post
    874
    Thanked 2,717 Times in 2,302 Posts
    Blog Entries
    11
    Rep Power
    780
    All vlans untagged, your link ports on each switch are untagged on vlan 2, the rest are all Vlan1, the router engine in the switches takes any packets that actually need to travel across the link and puts them across vlan 2 to be dumped out on the other network by the other switch. This way only packets that need to travel across the link actually do so you don't end up flooding it with rubbish and leaking stuff from one site to the other via broadcasts

  7. Thanks to SYNACK from:

    chrisjako (24th July 2014)

  8. #6

    Join Date
    Sep 2007
    Posts
    160
    Thank Post
    15
    Thanked 3 Times in 3 Posts
    Rep Power
    15
    o.k still not getting it to work

    ive tagged port b22 on vlan 1 (forbidding cuts me off completely), untagged on vlan2 on both switches

    my client machine is on the 10.5.224.0/21 subnet - I've set its default gateway IP address to 10.11.226.151 (which is the VLAN 1 ip address of the switch on the other network)

    on the switches ive set the following:

    switch on the 10.5.224.0/21 network
    VLAN 1 IP = 10.11.226.151
    VLAN 2 IP = 192.168.100.101
    went into config cli and typed in : ip route 10.11.224.0/21 192.168.100.100

    switch on the 10.11.224.0/21 network
    VLAN 1 IP = 10.11.225.102
    VLAN 2 IP = 192.168.100.100
    went into config cli and typed in : ip route 10.5.224.0/21 192.168.100.101

    with all the above in place its still not working, where am i going wrong!!

    Thanks for your help so far btw!

  9. #7
    Trapper's Avatar
    Join Date
    Apr 2007
    Location
    Birmingham
    Posts
    1,209
    Thank Post
    74
    Thanked 147 Times in 119 Posts
    Rep Power
    93
    How far apart are your two sites?

  10. #8

    Join Date
    Sep 2007
    Posts
    160
    Thank Post
    15
    Thanked 3 Times in 3 Posts
    Rep Power
    15
    Quote Originally Posted by Trapper View Post
    How far apart are your two sites?
    they are a mile apart

  11. #9

    SYNACK's Avatar
    Join Date
    Oct 2007
    Posts
    11,223
    Thank Post
    874
    Thanked 2,717 Times in 2,302 Posts
    Blog Entries
    11
    Rep Power
    780
    Default gateway should be the local switch, try ping from a client to the vlan2 address of the local switch, if this works routing is working on that one, next ping vlan 2 remote switch, then remote vlan 1 ip

    you can also do:
    tracert remoteVlan1IP

    and see where it stops
    Last edited by SYNACK; 24th July 2014 at 03:27 PM.

  12. Thanks to SYNACK from:

    chrisjako (24th July 2014)

  13. #10

    Join Date
    Sep 2007
    Posts
    160
    Thank Post
    15
    Thanked 3 Times in 3 Posts
    Rep Power
    15
    SYNACK YOU ARE A LEGEND!!!!

    I could ping the switch perfectly at the other site however couldn't ping the exchange server connected to it, change the default gateway of the exchange server to the local switch and everything started working fine

    BIG BIG thank you for helping me out

SHARE:
+ Post New Thread

Similar Threads

  1. Connecting Two HP Switches through Fiber
    By yaqoob121 in forum Wireless Networks
    Replies: 9
    Last Post: 16th December 2013, 10:07 AM
  2. connecting two switches over a fiber conection
    By marius_wiz in forum Wired Networks
    Replies: 6
    Last Post: 25th July 2012, 10:16 PM
  3. Connecting two subnets with Ipcop ? help ?
    By 2097 in forum Internet Related/Filtering/Firewall
    Replies: 3
    Last Post: 27th February 2012, 02:50 PM
  4. Two domains - Comunication through a firewall prob
    By tarquel in forum Wireless Networks
    Replies: 10
    Last Post: 27th July 2006, 08:42 AM
  5. Changing port vLANs on an HP ProCurve switch
    By MrDylan in forum Hardware
    Replies: 6
    Last Post: 9th March 2006, 03:13 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •