Announcement

Collapse
No announcement yet.

Routing between branch office and external vendor branch office

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Routing between branch office and external vendor branch office

    Recently we installed 100MB dedicated line between branch office and main office. The routers Cisco 2600 were provided by vendor and interconnectivity work as planned.

    Main office specs:
    190.50.103.x GW 190.50.103.99
    branch office 1
    192.168.153.x GW 192.168.153.1
    branch office 2
    192.168.101.x GW 192.168.101.1

    Details of L3 equip.
    190.50.103.99 Nortel
    190.50.103.250 Cisco 3000
    190.50.103.98 Cisco 2600 for 100MB line
    192.168.153.98 Cisco 2600 for 100MB line
    192.168.153.1 Cisco 3560
    192.168.101.98 Cisco 2600 for 100MB


    Of all the above equip. the only one we dont have access is the Nortel box. that said we configure the cisco 3000 to act as GW so we can manipulate the routing schema of the main office LAN.

    So from main office setting PC with GW as x.x.x.250 and having the route added in the x.x.x.250 I am able to connect to a node in segment routed by the x.x.x.99 router, ie 159.123.186.x. But from a branch office I am not able to
    find the route to that segment.

    I have added a route in 190.168.153.1 for 159.123.186.x to go to 192.153.168.98 but it stops in the WAN port of the router
    I have added a route in x.x.x.250 for 192.168.153.x to go to 190.50.103.98
    but stills i cannot not connect to a device in the cloud routedby the nortel box.

    Looking for idea on how to setup this series of routers to accomplish this
    thanks
    Attached Files

  • #2
    Re: Routing between branch office and external vendor branch office

    From the branch office, the traffic will be sent to the 3560, which will then pick up the static and send to the 2600. The 2600 does not have a route to the 159.123.186.x so it will just discard the packets.

    You have created static routes on the 3500 and 3560 to point to the relevant 2600s but you havent configured the coresponding routes on the 2600s.

    On the Branch 2600 you will need a static to 159.123.186.x pointing to 10.10.10.2

    On the Main 2600 you will need a route to 192.168.153.0 pointing to 10.10.10.1

    There doesnt seem to be a reason for your 3000 as you can manupulate the routing from the 2600.. Why are you running the 3560 as a L3 switch? If you configure your branch PCs with a GW of 192.168.153.98 (2600) then you can remove the static route from the 3560..
    Last edited by BigDeesDad; 15th September 2009, 12:08.
    Infrastructure Architect
    CCNA, CCNA Security, MCSE, JNCIS

    Comment


    • #3
      Re: Routing between branch office and external vendor branch office

      Please follow the running-config
      main office
      interface GigabitEthernet0/0
      description WAN
      bandwidth 102400
      ip address 10.10.10.2 255.255.255.0
      duplex full
      speed 100
      vlan-id dot1q 378
      exit-vlan-config
      !
      !
      interface GigabitEthernet0/1
      description LAN
      ip address 190.50.103.98 255.255.255.0
      duplex auto
      speed auto
      !
      ip classless
      ip route 159.123.0.0 255.255.0.0 190.50.103.99
      ip route 192.168.101.0 255.255.255.0 10.10.10.3
      ip route 192.168.153.0 255.255.255.0 10.10.10.1

      ------
      7601_4th_ave#ping 159.123.190.17
      Type escape sequence to abort.
      Sending 5, 100-byte ICMP Echos to 159.123.190.17, timeout is 2 seconds:
      !!!!!
      Success rate is 100 percent (5/5), round-trip min/avg/max = 36/58/84 ms


      branch office

      interface GigabitEthernet0/0
      description WAN$ES_LAN$
      bandwidth 102400
      ip address 10.10.10.1 255.255.255.0
      duplex full
      speed 100
      vlan-id dot1q 378
      exit-vlan-config
      !
      !
      interface GigabitEthernet0/1
      description LAN
      ip address 192.168.153.98 255.255.255.0
      duplex auto
      speed auto
      !
      ip classless
      ip route 159.123.0.0 255.255.0.0 10.10.10.2 8 permanent
      ip route 190.50.103.0 255.255.255.0 10.10.10.2
      ip route 192.168.101.0 255.255.255.0 10.10.10.3

      ----
      9920_4th_ave#ping 159.123.190.17
      Type escape sequence to abort.
      Sending 5, 100-byte ICMP Echos to 159.123.190.17, timeout is 2 seconds:
      .....
      Success rate is 0 percent (0/5)

      Comment


      • #4
        Re: Routing between branch office and external vendor branch office

        OK so your static routes are configured and the branch office has a valid route to the 159.123.0.0 subnet.

        If you have no access lists blocking the traffic then I would imagine that it is the return traffic that is getting dropped by the Nortel device. The Nortel device is directly connected to the 159.123.0.0 and 190.50.103.98 subnets but it sounds like it doesn't have a valid route to the branch subnets hence dropping the traffic...

        You will need to add routes to the branch office subnets on the Nortel or look at using a dynamic routing protocol to negate the need for all the statics.
        Infrastructure Architect
        CCNA, CCNA Security, MCSE, JNCIS

        Comment

        Working...
        X