OSPF prefer learned route over local

Hey
I am deploying a new VPLS between 8 offices. The plan in to have all the offices get internet access through the main office. So basically all the satellite offices will only have access to the VPLS WAN link. The main office will advertize a default route to the rest of satellite offices over OSPF.
Each office currently has its own internet connection. I would like to maintain each office's internet connection until we have completed deployment of the VPLS and have thoroughly tested it.
So my question is this. How to i configure OSPF to prefer the learned default route, over the default route it has statically configured?
thanks for your help
Dan

Dan
Without knowing the full topology it's difficult to say for sure but as a general answer you can't really.
Even if you tried to set the AD of OSPF to be the same as the static route, which I'm not sure would be a good idea, the locally configured static would have a better metric.
I think you are basically going to have to test by advertising out the default route via OSPF, making sure it is in the OSPF database at each site and then remove the locally configured default to test internet connectivity via your main branch.
Or you could try using PBR to bypass the routing table which would allow you to test central internet connectivity but it doesn't confirm your OSPF routing is working properly.
Jon

Similar Messages

  • Issue with OSPF Point-to-Multipoint over CES Cloud

    I'm having an issue running ospf point-to-multipoint over a CES cloud.  The reason I want to do this is that not every site has the same bandwidth and this way I can use neighbor statements to specify the cost to each neighbor.
    To make this work I have to shut down the cloud facing interface on each node and bring them up one at a time.  Everything runs fine until I then shut one of them down and bring it up again, I'm only able to form adjanceis with 2-3 nodes - the other nodes get stuck in either INIT or EXSTART until OSPF give up do to too many retires.  If I then repeat the process of shutting down the interface on each node and bringing them back up it works again.
    I've tried both " ip ospf network point-to-multipoint" and " ip ospf network point-to-multipoint non-broadcast" with the same results.
    Here are the router types involved and the firmware they are running:
    1. asr1006 asr1000rp1-adventerprisek9.03.10.00.S.153-3.S-ext.bin
    2. asr1006 asr1000rp1-adventerprisek9.03.10.00.S.153-3.S-ext.bin
    3. 2821 c2800nm-ipbasek9-mz.151-3.T4.bin
    4. 2821 c2800nm-ipbasek9-mz.151-3.T4.bin
    5. 2921 c2900-universalk9-mz.SPA.150-1.M1.bin (ipbasek9 license)
    6. 2921  c2900-universalk9-mz.SPA.153-2.T.bin (ipbasek9 license)
    7. 2821 c2800nm-ipbasek9-mz.151-3.T4.bin
    Here is the relevant config from one of the routers:
    interface GigabitEthernet1/0/6
     description CES
     bandwidth 50000
     ip address 10.226.126.30 255.255.255.224
     no ip redirects
     ip flow ingress
     ip flow egress
     ip ospf authentication message-digest
     ip ospf message-digest-key 1 md5 blahblahblah
     ip ospf network point-to-multipoint non-broadcast
     ip ospf dead-interval 3
     ip ospf hello-interval 1
     load-interval 30
    router ospf 1
    router-id 10.226.1.9
    ispf
    auto-cost reference-bandwidth 10000
    timers throttle spf 10 100 5000
    timers throttle lsa 10 100 5000
    timers lsa arrival 80
    passive-interface default  
    no passive-interface GigabitEthernet1/0/6
    network 10.226.126.0 0.0.0.31 area 0
    neighbor 10.226.126.6 cost 1000
    neighbor 10.226.126.5 cost 3333
    neighbor 10.226.126.4 cost 3333
    neighbor 10.226.126.3 cost 3333
    neighbor 10.226.126.2 cost 3333
    neighbor 10.226.126.1 cost 200
    All the routers have at least one other interface running OSPF point-topoint with no issues.  The ASRs also have some stub areas in addition to area 0.  I've tried taking the ASRs out of the loop and testing, but the results are the same.
    Please let me know if you have any ideas or need more details.
    Thanks.

    Hi Peter,
    believe me: I was perplexed as well and it took me some time to understand what was going on.
    I've created a simple gns3 lab (topology attached) with handy IP- and MAC addresses:
    R1: 192.168.0.1; 02:00:00:00:11:11
    R3: 192.168.0.3; 02:00:00:00:33:33
    R4: 192.168.0.4; 02:00:00:00:44:44
    The host routes for the point-to-multipoint interfaces play an important role:
    R3#show ip route 192.168.0.0
    C 192.168.0.0/24 is directly connected, FastEthernet1/0
    O 192.168.0.1/32 [110/1] via 192.168.0.1, 00:02:44, FastEthernet1/0
    O 192.168.0.4/32 [110/64] via 172.16.34.4, 00:02:44, Serial0/1
    Now, with a debug arp enabled on R1 we can see what happens when we shutdown and re-enable Fa1/0.
    R1(config-if)#do show ip int brief f1/0
    Interface IP-Address OK? Method Status Protocol
    FastEthernet1/0 192.168.0.1 YES NVRAM administratively down down
    R1(config-if)#do show ip arp
    <no output>
    R1(config-if)#no shut
    IP ARP: sent rep src 192.168.0.1 0200.0000.1111,
    dst 192.168.0.1 ffff.ffff.ffff FastEthernet1/0
    IP ARP: sent rep src 192.168.0.1 0200.0000.1111,
    dst 192.168.0.1 ffff.ffff.ffff FastEthernet1/0
    IP ARP: creating incomplete entry for IP address: 192.168.0.4 interface FastEthernet1/0
    IP ARP: sent req src 192.168.0.1 0200.0000.1111,
    dst 192.168.0.4 0000.0000.0000 FastEthernet1/0
    IP ARP: creating incomplete entry for IP address: 192.168.0.3 interface FastEthernet1/0
    IP ARP: sent req src 192.168.0.1 0200.0000.1111,
    dst 192.168.0.3 0000.0000.0000 FastEthernet1/0
    IP ARP: rcvd rep src 192.168.0.4 0200.0000.4444, dst 192.168.0.1 FastEthernet1/0
    IP ARP: rcvd rep src 192.168.0.3 0200.0000.4444, dst 192.168.0.1 FastEthernet1/0
    IP ARP: rcvd rep src 192.168.0.4 0200.0000.3333, dst 192.168.0.1 FastEthernet1/0
    IP ARP: rcvd rep src 192.168.0.3 0200.0000.3333, dst 192.168.0.1 FastEthernet1/0
    R1(config-if)#do show ip arp
    Protocol Address Age (min) Hardware Addr Type Interface
    Internet 192.168.0.1 - 0200.0000.1111 ARPA FastEthernet1/0
    Internet 192.168.0.3 0 0200.0000.3333 ARPA FastEthernet1/0
    Internet 192.168.0.4 0 0200.0000.3333 ARPA FastEthernet1/0
    R1(config-if)#do show ip ospf neighbor
    Neighbor ID Pri State Dead Time Address Interface
    4.4.4.4 0 INIT/ - 00:00:16 192.168.0.4 FastEthernet1/0
    3.3.3.3 0 FULL/ - 00:00:16 192.168.0.3 FastEthernet1/0
    OSPF: Rcv hello from 4.4.4.4 area 0 from FastEthernet1/0 192.168.0.4
    OSPF: Send immediate hello to nbr 4.4.4.4, src address 192.168.0.4, on FastEthernet1/0
    OSPF: Send hello to 192.168.0.4 area 0 on FastEthernet1/0 from 192.168.0.1
    OSPF: End of hello processing
    Because of the hostroute to R4, R3's proxy ARP answeres an ARP request for R4 (the same happens on R4)! At this point we have IP connectivity to R4 (via R3) but this doesn't work for OSPF's link local traffic.
    So just for the fun of it, we could configure a static ARP entry to verify if that will fix the problem:
    R1(config)#arp 192.168.0.4 0200.0000.4444 arpa
    %OSPF-5-ADJCHG: Process 1, Nbr 4.4.4.4 on FastEthernet1/0 from LOADING to FULL, Loading Done
    R1(config)#no arp 192.168.0.4 0200.0000.4444 arpa
    IP ARP: creating incomplete entry for IP address: 192.168.0.4 interface FastEthernet1/0
    IP ARP: sent req src 192.168.0.1 0200.0000.1111,
    dst 192.168.0.4 0000.0000.0000 FastEthernet1/0
    IP ARP: rcvd rep src 192.168.0.4 0200.0000.4444, dst 192.168.0.1 FastEthernet1/0
    IP ARP: rcvd rep src 192.168.0.4 0200.0000.3333, dst 192.168.0.1 FastEthernet1/0
    Or we could avoid that R3 installs an OSPF hostroute to 192.168.0.4.
    R3(config)#ip prefix-list NO-HOSTROUTES deny 192.168.0.0/24 ge 32
    R3(config)#ip prefix-list NO-HOSTROUTES permit 0.0.0.0/0 le 32
    R3(config)#router ospf 1
    R3(config-router)#distribute-list prefix NO-HOSTROUTES in
    R3(config-router)#do show ip route 192.168.0.4
    Routing entry for 192.168.0.0/24
    Known via "connected", distance 0, metric 0 (connected, via interface)
    R1(config)#do clear ip arp 192.168.0.4
    IP ARP: sent req src 192.168.0.1 0200.0000.1111,
    dst 192.168.0.4 0200.0000.3333 FastEthernet1/0
    IP ARP: creating incomplete entry for IP address: 192.168.0.4 interface FastEthernet1/0
    IP ARP: sent req src 192.168.0.1 0200.0000.1111,
    dst 192.168.0.4 0000.0000.0000 FastEthernet1/0
    IP ARP: rcvd rep src 192.168.0.4 0200.0000.4444, dst 192.168.0.1 FastEthernet1/0
    %OSPF-5-ADJCHG: Process 1, Nbr 4.4.4.4 on FastEthernet1/0 from LOADING to FULL, Loading Done
    An interesting detail is the destination MAC address in the first request. Seems like the MAC address of the former ARP entry was still cached somewhere.
    The adequate solution to solve the problem is of course disabling proxy-ARP.
    I was quite surprised to see that that the protocol logic obviously ignores the fact of being in the same subnet but rather simply check if there is another entry for the requested host in the routing table.
    The sanity checks section of RFC 1027 says
    "An ARP subnet gateway implementation must not reply if the physical networks of the source and target of an ARP request are the same."
    and it seems to me that IOS has not implemented this check. I'm looking forward to hear your opinion!
    Thanks for joining,
    best regards
    Rolf

  • Any way to move old prefs etc. back over after clean install?

    So I have a few partitions and a few options here. I'm currently running 10.5.1 off of my internal HD and it seems fast and stable so far. I have another partition with my Tiger system cloned and yet another partition I could use. So I could do another Leopard install onto the Tiger partition, do an archive and install, so that I get back all my prefs and bookmarks etc., not have to reinstall certain apps. But can I manually copy prefs, mail etc. over from my Tiger partition or is that a mistake?

    Looks like maybe Migration Assistant may be what I need. Will it copy over my mail, bookmarks and prefs from my Tiger partition? What essentially would be the difference between having done an archive and install over my Tiger system and doing a clean install and using Migration Assistant to move stuff over? Will it essentially give me the same results?

  • Finding a rogue WiFi router on local network

    This is likely a very odd and possibly complicated question, but I figure I'd throw it out there anyways.
    At my office, we have a couple wireless routers throughout the building. However, one in particular has started to act up. It used to work perfectly, but in the last month or so, it has stopped working. Connecting to it via the password that was set no longer works. Laptops can SEE the network in a list of wireless connections, but we can't log into anymore.
    Now, normally a easy solution would be to find the physical router and reset it manually. But here's the problem.
    We don't know where it actually is. It was installed before myself or the current IT specialist were hired. We were able to use a Macbook and iStumbler to detect its general location by walking around the building and guaging signal strength. But we still can't find it. It's likely up in the ceiling somewhere. Don't ask me why.
    So, I'm wondering if there's a way, be it through an app, Terminal, etc, to detect the router over the network. If we're able to get the IP of the device, maybe we can log into it and possibly fix the problem.
    If not, perhaps people know of a good device we could purchase to further locate the physical device it self? I've seen a handful of WiFi detectors, but they usually only show 1-5 bars - nothing more.
    Any insight?

    I assume you mean that you have several wireless access points, not wireless routers.
    Have your IT Dept disconnect the ethernet cable that connects the Access Point to the main switch or router, and then "tone" the wire to trace it.
    Use one of these:
    http://www.iautomate.com/kp100.html
    Another option is to flash the firwmare over the LAN, BUT that will probably default the Access Point to an address already in use and that may create a bigger problem.
    Peter

  • How to access Time Capsule drives behind DSL Router over WAN

    Hello everyone,
    I have an older Time capsule(with USB Drive) connected to my Hitron CGN3 DSL wireless router over ethernet. 
    I have turned off the wireless functionality of the TC since the router seems to be much faster on Speedtest.net. 
    I have my TC and attached USB drive setup to share over WAN but am getting a Double NAT error.
    It doesn't seem like I can turn off NAT on my Router.
    I can't run the TC in bridge mode because it will remove the Share over WAN option for the TC and Drive.
    Is it possible to setup the TC and attached USB drive to the router, without wireless on, so that I can access the TC and drive over the internet?
    Any help would be soooooo apreciated!!!
    Thanks!
    Ian

    Does anyone know why my Time Capsule drive sharing needs to be set to disk password?
    You can set the TC disks to user accounts.. at least you can on older TC with older airport utility.. but there are consequences which you discovered.
    If you set accounts.. you will have major issue with the existing files.. they will all disappear.
    The old v5 utility gives you this warning.. which somehow Apple forgot on new version.
    It actually makes all the present files disappear for all users. The warning just doesn't go far enough. You do this on a blank TC.. and of course the USB drive is just the same.. you cannot use different settings on that to the TC internal drive. So offload all your files.. create accounts on a bare TC.. load the files back into the correct user profiles.
    In the end you probably want more flexibility than a TC is designed for.. buy something designed for remote access.. WD MyCloud.. it is hugely superior.
    Also. . .  I am trying some File manager apps for my iPhone in hopes that i can connect to the same drive with it.  So far no luck with the free versions of FileBrowser Lite or File Explorer Free.
    Most are SMB based.. not AFP.. Apple offer only two protocols.. SMB and AFP. But no responsible ISP allows SMB over the internet. The flood of files from hacked windows machines would bring the internet to a grinding halt.
    People do get around it.. you can use filebrowser for instance by opening SMB to the outside world on a non-standard port.
    See http://www.stratospherix.com/support/gsw_timecapsule.php?page=6remote
    But this is incredibly risky.. there is very poor security and it is not a great idea. The AFP security is much better than SMB.
    If you want security use something other than TC.. any real NAS that offers VPN access for instance. The cost of a WD MyCloud is very reasonable when you look at the flexibility of the design. But any decent NAS will offer real remote access.. not Apple's limited pretend version.

  • What is the preferred dynamic routing over l2l/ipsec?

    what is the preferred dynamic routing over l2l/ipsec?
    Sent from Cisco Technical Support iPhone App

    Disclaimer
    The  Author of this posting offers the information contained within this  posting without consideration and with the reader's understanding that  there's no implied or expressed suitability or fitness for any purpose.  Information provided is for informational purposes only and should not  be construed as rendering professional advice of any kind. Usage of this  posting's information is solely at reader's own risk.
    Liability Disclaimer
    In  no event shall Author be liable for any damages whatsoever (including,  without limitation, damages for loss of use, data or profit) arising out  of the use or inability to use the posting's information even if Author  has been advised of the possibility of such damage.
    Posting
    Pretty much what you might use if not IPSec.
    Do you have some reason why IPSec should have a preferred routing protocol or are you just wondering if there is a preferred routing protocol for IPSec?

  • Discover Switch and router over VPN

    i am in contact with a company having many branches connecting over VPN tunnel and with different IP range in each branch
    how can i configure the LMs to discover my switch and my router over VPN

    LMS 3.0.1 and higher can use non-CDP discovery methods which should be able to find your remotely connected VPN devices.  You could use the Ping Sweep or Route Table modules to accomplish what you want.
    See https://supportforums.cisco.com/docs/DOC-9005 for more details.

  • BGP Community | Route-Map | Local Pref

    While labbing today I've ran into some strange behavior with BGP communities/route-map processing. Basically the objective was from R9, send a community for the 172.30.79.0/27 route out to R7 to 65100:90 AND send a community for the 172.30.89.0/27 route out to R8 to 65100:110. Then on R9 match community 65100:90 and set the local-pref to 90 and 65100:110 to local-pref of 110. Should be easy enough but the behavior that i'm seeing is that all is working on R7 but not on R8. The R8 inbound route-map is watching the community but not setting the local-pref for some reason... Any ideas? See below.
    Topology
    ##R9’s BGP/Route-map config setting communities for the two routes out to R7 & R8##
    R9#sh run  | s bgp|route-map
    router bgp 65100
     network 172.30.79.0 mask 255.255.255.224
     network 172.30.89.0 mask 255.255.255.224
     network 192.122.3.9 mask 255.255.255.255
     neighbor 172.30.79.7 remote-as 65006
     neighbor 172.30.79.7 send-community both
     neighbor 172.30.79.7 route-map R7-OUT out
     neighbor 172.30.89.8 remote-as 65006
     neighbor 172.30.89.8 send-community both
     neighbor 172.30.89.8 route-map R8-OUT out
    ip bgp-community new-format
    route-map R7-OUT permit 10
     match ip address prefix-list 172.30.79.0/27
     set community 65100:90
    route-map R7-OUT permit 20
    route-map R8-OUT permit 10
     match ip address prefix-list 172.30.89.0/27
     set community 65100:110
    route-map R8-OUT permit 20
    ##R7’s config##
    R7#sh run | s bgp|route-map
    router bgp 65006
     address-family ipv4 vrf VPN
      neighbor 172.30.79.9 remote-as 65100
      neighbor 172.30.79.9 activate
      neighbor 172.30.79.9 send-community both
      neighbor 172.30.79.9 as-override
      neighbor 172.30.79.9 route-map R9-IN in
    route-map R9-IN permit 10
     match community 65100:90
     set local-preference 90
    route-map R9-IN permit 20
    ##R7’s ‘show bgp’##
    R7#sh ip bgp vpnv4 vrf VPN | b Network
         Network          Next Hop            Metric LocPrf Weight Path
    Route Distinguisher: 65066:700 (default for vrf VPN)
     r>  172.30.79.0/27   172.30.79.9           90              0 65100 i
     *>  172.30.89.0/27   172.30.79.9              0             0 65100 i
     *>  192.122.3.9/32   172.30.79.9              0             0 65100 i
    ##R8’s config##
    router bgp 65006
     address-family ipv4 vrf VPN
      neighbor 172.30.89.9 remote-as 65100
      neighbor 172.30.89.9 activate
      neighbor 172.30.89.9 send-community both
      neighbor 172.30.89.9 as-override
      neighbor 172.30.89.9 route-map R9-INv2 in
    route-map R9-INv2 permit 10
     match community 65100:110
     set local-preference 110
    route-map R9-INv2 permit 20
    ##R8’s ‘show bgp’##
    R8#sh ip bgp vpnv4 vrf VPN | b Network
         Network          Next Hop            Metric LocPrf Weight Path
    Route Distinguisher: 65006:800 (default for vrf VPN)
     *>  172.30.79.0/27   172.30.89.9              0             0 65100 i
     r>  172.30.89.0/27   172.30.89.9              0             0 65100 i
     *>  192.122.3.9/32   172.30.89.9              0             0 65100 i
    R8#sh ip bgp vpnv4 vrf VPN community | b Network
         Network          Next Hop            Metric LocPrf Weight Path
    Route Distinguisher: 65006:800 (default for vrf VPN)
     r>  172.30.89.0/27   172.30.89.9              0             0 65100 i
    R8#sh ip bgp vpnv4 vrf VPN 172.30.89.0/27         
    BGP routing table entry for 65006:800:172.30.89.0/27, version 77
    Paths: (1 available, best #1, table VPN, RIB-failure(17))
      Not advertised to any peer
      Refresh Epoch 2
      65100
        172.30.89.9 from 172.30.89.9 (192.122.3.9)
          Origin IGP, metric 0, localpref 100, valid, external, best
          Community: 65100:110
          Extended Community: RT:910:910
          mpls labels in/out 45/nolabel
          rx pathid: 0, tx pathid: 0x0

    While labbing today I've ran into some strange behavior with BGP communities/route-map processing. Basically the objective was from R9, send a community for the 172.30.79.0/27 route out to R7 to 65100:90 AND send a community for the 172.30.89.0/27 route out to R8 to 65100:110. Then on R9 match community 65100:90 and set the local-pref to 90 and 65100:110 to local-pref of 110. Should be easy enough but the behavior that i'm seeing is that all is working on R7 but not on R8. The R8 inbound route-map is watching the community but not setting the local-pref for some reason... Any ideas? See below.
    Topology
    ##R9’s BGP/Route-map config setting communities for the two routes out to R7 & R8##
    R9#sh run  | s bgp|route-map
    router bgp 65100
     network 172.30.79.0 mask 255.255.255.224
     network 172.30.89.0 mask 255.255.255.224
     network 192.122.3.9 mask 255.255.255.255
     neighbor 172.30.79.7 remote-as 65006
     neighbor 172.30.79.7 send-community both
     neighbor 172.30.79.7 route-map R7-OUT out
     neighbor 172.30.89.8 remote-as 65006
     neighbor 172.30.89.8 send-community both
     neighbor 172.30.89.8 route-map R8-OUT out
    ip bgp-community new-format
    route-map R7-OUT permit 10
     match ip address prefix-list 172.30.79.0/27
     set community 65100:90
    route-map R7-OUT permit 20
    route-map R8-OUT permit 10
     match ip address prefix-list 172.30.89.0/27
     set community 65100:110
    route-map R8-OUT permit 20
    ##R7’s config##
    R7#sh run | s bgp|route-map
    router bgp 65006
     address-family ipv4 vrf VPN
      neighbor 172.30.79.9 remote-as 65100
      neighbor 172.30.79.9 activate
      neighbor 172.30.79.9 send-community both
      neighbor 172.30.79.9 as-override
      neighbor 172.30.79.9 route-map R9-IN in
    route-map R9-IN permit 10
     match community 65100:90
     set local-preference 90
    route-map R9-IN permit 20
    ##R7’s ‘show bgp’##
    R7#sh ip bgp vpnv4 vrf VPN | b Network
         Network          Next Hop            Metric LocPrf Weight Path
    Route Distinguisher: 65066:700 (default for vrf VPN)
     r>  172.30.79.0/27   172.30.79.9           90              0 65100 i
     *>  172.30.89.0/27   172.30.79.9              0             0 65100 i
     *>  192.122.3.9/32   172.30.79.9              0             0 65100 i
    ##R8’s config##
    router bgp 65006
     address-family ipv4 vrf VPN
      neighbor 172.30.89.9 remote-as 65100
      neighbor 172.30.89.9 activate
      neighbor 172.30.89.9 send-community both
      neighbor 172.30.89.9 as-override
      neighbor 172.30.89.9 route-map R9-INv2 in
    route-map R9-INv2 permit 10
     match community 65100:110
     set local-preference 110
    route-map R9-INv2 permit 20
    ##R8’s ‘show bgp’##
    R8#sh ip bgp vpnv4 vrf VPN | b Network
         Network          Next Hop            Metric LocPrf Weight Path
    Route Distinguisher: 65006:800 (default for vrf VPN)
     *>  172.30.79.0/27   172.30.89.9              0             0 65100 i
     r>  172.30.89.0/27   172.30.89.9              0             0 65100 i
     *>  192.122.3.9/32   172.30.89.9              0             0 65100 i
    R8#sh ip bgp vpnv4 vrf VPN community | b Network
         Network          Next Hop            Metric LocPrf Weight Path
    Route Distinguisher: 65006:800 (default for vrf VPN)
     r>  172.30.89.0/27   172.30.89.9              0             0 65100 i
    R8#sh ip bgp vpnv4 vrf VPN 172.30.89.0/27         
    BGP routing table entry for 65006:800:172.30.89.0/27, version 77
    Paths: (1 available, best #1, table VPN, RIB-failure(17))
      Not advertised to any peer
      Refresh Epoch 2
      65100
        172.30.89.9 from 172.30.89.9 (192.122.3.9)
          Origin IGP, metric 0, localpref 100, valid, external, best
          Community: 65100:110
          Extended Community: RT:910:910
          mpls labels in/out 45/nolabel
          rx pathid: 0, tx pathid: 0x0

  • Routing over a trunk

    I have a packet tracer lab that i am using to learn my CCNA on. 
    I have 2 sites connected together by layer 3 switches and i cannot ping between the sites. 
    The trunk is vlan10 with addresses on each side of 1.1.1.1/30 and 1.1.1.2/30
    From each switch i can ping the other side.  
    I have some machines on 192.168.100.0/24 in Vlan 20
    and machines on the other switch on 10.0.10.0/25 Vlan 30
    From Vlan20 i can ping the local side of Vlan 10 and the same from Vlan 30 but i cant ping over the trunk. 
    Can anyone give me a hint as to why not?
    SWITCH 1
    version 12.2
    no service timestamps log datetime msec
    no service timestamps debug datetime msec
    no service password-encryption
    hostname ScunthorpeSwitch
    enable secret 5 *****
    ip routing
    interface FastEthernet0/1
    interface FastEthernet0/2
     switchport access vlan 20
     switchport mode access
    interface FastEthernet0/3
     switchport access vlan 30
     switchport mode access
    interface FastEthernet0/24
     switchport access vlan 10
     switchport trunk encapsulation dot1q
     switchport mode trunk
    interface Vlan1
     no ip address
    interface Vlan10
     ip address 1.1.1.2 255.255.255.252
    interface Vlan30
     ip address 10.0.10.253 255.255.255.0
    ip classless
    ip route 0.0.0.0 0.0.0.0 FastEthernet0/24 
    VLAN Name                             Status    Ports
    1    default                          active    Fa0/1, Fa0/4, Fa0/5, Fa0/6
                                                    Fa0/7, Fa0/8, Fa0/9, Fa0/10
                                                    Fa0/11, Fa0/12, Fa0/13, Fa0/14
                                                    Fa0/15, Fa0/16, Fa0/17, Fa0/18
                                                    Fa0/19, Fa0/20, Fa0/21, Fa0/22
                                                    Fa0/23, Gig0/1, Gig0/2
    10   FIRBELINK                        active    
    20   SHEFFIELD                        active    Fa0/2
    30   SCUNTHORPE                       active    Fa0/3
    40   SERVERS                          active    
    1002 fddi-default                     act/unsup 
    ScunthorpeSwitch#sho interfaces trunk 
    Port        Mode         Encapsulation  Status        Native vlan
    Fa0/24      on           802.1q         trunking      1
    Port        Vlans allowed on trunk
    Fa0/24      1-1005
    Port        Vlans allowed and active in management domain
    Fa0/24      1,10,20,30,40
    Port        Vlans in spanning tree forwarding state and not pruned
    Fa0/24      1,10,20,30,40
    SWITCH 2
    version 12.2
    no service timestamps log datetime msec
    no service timestamps debug datetime msec
    no service password-encryption
    hostname "Sheffield Switch"
    enable secret 5 **************
    ip routing
    username ***** password 0 ********
    no ip domain-lookup
    interface FastEthernet0/1
     switchport access vlan 20
     switchport mode access
    interface FastEthernet0/2
     switchport access vlan 20
     switchport mode access
    interface FastEthernet0/3
     switchport mode access
     shutdown
    interface FastEthernet0/24
     description FIBER BETWEEN SITES
     no switchport
     no ip address
     duplex auto
     speed auto
    interface Vlan1
     no ip address
    interface Vlan10
     ip address 1.1.1.1 255.255.255.252
    interface Vlan20
     ip address 192.168.100.250 255.255.255.0
    ip classless
    ip route 0.0.0.0 0.0.0.0 FastEthernet0/24 
    banner motd ^C
    ******* , Do Not Enter ******   ^C
    VLAN Name                             Status    Ports
    1    default                          active    Fa0/3, Fa0/4, Fa0/5, Fa0/6
                                                    Fa0/7, Fa0/8, Fa0/9, Fa0/10
                                                    Fa0/11, Fa0/12, Fa0/13, Fa0/14
                                                    Fa0/15, Fa0/16, Fa0/17, Fa0/18
                                                    Fa0/19, Fa0/20, Fa0/21, Fa0/22
                                                    Fa0/23, Gig0/1, Gig0/2
    10   FIRBELINK                        active    
    20   SHEFFIELD                        active    Fa0/1, Fa0/2
    30   SCUNTHORPE                       active    
    40   SERVERS                          active    
    Sheffield Switch#sho interfaces trunk 
    Port        Mode         Encapsulation  Status        Native vlan
    Fa0/24      on           802.1q         trunking      1
    Port        Vlans allowed on trunk
    Fa0/24      1-1005
    Port        Vlans allowed and active in management domain
    Fa0/24      1,10,20,30,40
    Port        Vlans in spanning tree forwarding state and not pruned
    Fa0/24      1

    You have no routing protocol running so the L3 switches only know about connected and static routes. The only static route you have is the default:
         ip route 0.0.0.0 0.0.0.0 FastEthernet0/24
    The interface you tell it to use is a L2 interface, so you're effectively not routing with that default. If you create an SVI (Layer 3 switched virtual interface) for each VLAN on all the switches (i.e. add interfaces for VLAN 20 on switch 1 and VLAN 30 on switch 2), it will work. also if you made the default route on each switch be the other switch's VLAN 10 L3 interface, that would also work.
    You could also setup actual routing like OSPF or EIGRP but that's outside the scope for CCNA practice.

  • RV042 not annoucing vpn routes over rip v2

    Problem: RV042 is not announcing a class C VPN route via RIP to other routers. It announces the gateway public address via rip, but not the VPN route.
    I am attempting to use a pair of RV042 as a redundant links between our home office and a branch. The home office and branch is already connected via a T1. Each location also has an additional cable internet connection with public IP address and a cisco 1921 router controlling the traffic.
    The 1921 routers are using OSPF to route traffic over the T1 and have RIPv2 enabled to talk to their local respective RV042s. Here is a description of how the network is set up.
    MainRouter - cisco 1921
       Eth0 - Network is 192.168.41.0/24
                 IP address is 192.168.41.20
       Eth0/1 - Network 10.1.1.1 255.255.255.254
                T1 connection to branch router
    MainRV - RV042 v3 with fw 4.2.1.02
       Wan1 - Public IP A X.X.X.X
        LAN- Network 192.168.41.0/24
                  IP 192.168.41.11 255.255.255.0
    BranchRouter - cisco 1921
      Eth0/0 - Network is 192.168.46.0/24
                   IP address is 192.168.46.10
      Eth0/1 - Network 10.1.1.2 255.255.255.254
                T1 connection to main router
    BranchRV - RV042 v3 with fw 4.2.1.02
      Wan1 - Public IP B Y.Y.Y.Y
        LAN - Network 192.168.46.0/24
                  IP 192.168.46.11 255.255.255.0
    I have established a VPN from BranchRV to MainRV and it passes traffic correctly. My "MainRouter "
    rip database looks like this....
    192.168.41.0/24    auto-summary
    192.168.41.0/24    directly connected, GigabitEthernet0/0
    X.X.X.X/24    auto-summary
    X.X.X.Z/30
        [1] via 192.168.46.11, 00:00:01, GigabitEthernet0/0
    Notice that there is no route to 192.168.46.0/24 in there....
    Now here is the kicker, just messing around, I changed the VPN settings to use subnets 10.0.10.0/24 on MainRV and 10.0.11.0/24 on BranchRV instead of 192.168.41.0/24 and 192.168.46.0/24 respectivly. After I tried that the routes for the 10.0.3.0 were announced via RIP
    Here is what the MainRouter's rip database looked like after I tried that
    10.0.0.0/8    auto-summary
    10.0.11.0/24
        [2] via 192.168.41.11, 00:00:18, GigabitEthernet0/0
    192.168.41.0/24    auto-summary
    192.168.41.0/24    directly connected, GigabitEthernet0/0
    X.X.X.X/24    auto-summary
    X.X.X.Y/30
        [1] via 192.168.41.11, 00:00:18, GigabitEthernet0/0
    What gives? This really looks like a bug to me...
    Anyhow I'm thinking a workaround might be to set up a GRE tunnel across those 10.0.X.X subnets to the other side so I can at least dynamically route traffic accross.... Without the RIP routes being announced I don't have automatic failover!
    Thanks for your help,
       Curtis

    Yes as was explained to me previously.... by Jason Nickle multicast does not cross a site-to-site tunnel.
    That is not what I want to have happen. What I want is for my RV042 to announce it's VPN routes to other routers on the same physical network. Which it currently is not doing.
    Site 1
        Cisco IOS Router X - main router, local network traffic runs across this
         RVO42 X - has VPN link to RVO42 Y at Site 2
    Site 2
      Cisco IOS Router Y - main router, local newtok traffic runs acress this
       RVO42 Y - has VPN link to RVO42 X at Site 1
    The problem is that RV042 Y doesn't tell Router Y that it has a route to Site 1. And RV042 X doesn't tell Router X that it has a route to Site 2. So they are not locally announcing via RIP, the routes they have TO the respective remote sites.
    What I was trying to say in my original post, is that the router will announce VPN routes if the vpn subnets are a class A 10.X.X.X subnet, but it doesn't announce them if they are a class C 192.168.X.X subnet. So what I am doing should be working, however it is not.

  • Leaking MPLS VPN learned routes from VRF to Global

    I'm trying to leak routes from a VRF to global. I can get the routes leaked from directly connected CE to the global, however I can't get the routes from remote CE's to leak in to the global routing table. Below are my configurations
    RP/0/0/CPU0:B25BR1#sh run vrf TR
    Wed Dec 17 22:40:33.772 UTC
    vrf TR
     address-family ipv4 unicast
      import route-target
       65000:7020
      export to default-vrf route-policy TR-2-GLOBAL
      export route-target
       65000:7020
    RP/0/0/CPU0:B25BR1#sh rpl route-policy TR-2-GLOBAL
    Wed Dec 17 22:40:50.851 UTC
    route-policy TR-2-GLOBAL
      if destination in TR-2-GLOBAL then
        pass
      endif
    end-policy
    RP/0/0/CPU0:B25BR1#sh rpl prefix-set TR-2-GLOBAL
    Wed Dec 17 22:40:57.861 UTC
    prefix-set TR-2-GLOBAL
      192.168.0.17/32,
      192.168.0.18/32,
      192.168.0.19/32,
      192.168.0.20/32
    end-set
    !Routes that I want to see also are  192.168.0.19/32 and 192.168.0.20/32 which are there in the VRF routing table
    RP/0/0/CPU0:B25BR1#sh route vrf TR
    Wed Dec 17 22:41:45.767 UTC
    Codes: C - connected, S - static, R - RIP, B - BGP, (>) - Diversion path
           D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
           N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
           E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
           i - ISIS, L1 - IS-IS level-1, L2 - IS-IS level-2
           ia - IS-IS inter area, su - IS-IS summary null, * - candidate default
           U - per-user static route, o - ODR, L - local, G  - DAGR
           A - access/subscriber, a - Application route, (!) - FRR Backup path
    Gateway of last resort is not set
    B    10.1.0.0/30 [20/0] via 10.1.0.5, 00:14:32
    C    10.1.0.4/30 is directly connected, 06:57:19, GigabitEthernet0/0/0/2
    L    10.1.0.6/32 is directly connected, 06:57:19, GigabitEthernet0/0/0/2
    B    10.1.128.0/30 [20/0] via 10.1.0.5, 00:14:32
    B    192.168.0.17/32 [20/0] via 10.1.0.5, 00:13:56
    B    192.168.0.18/32 [20/0] via 10.1.0.5, 00:13:56
    B    192.168.0.19/32 [200/0] via 192.168.0.4 (nexthop in vrf default), 00:13:31
    B    192.168.0.20/32 [200/0] via 192.168.0.4 (nexthop in vrf default), 00:13:31
    RP/0/0/CPU0:B25BR1#sh ip rou
    Wed Dec 17 22:41:50.097 UTC
    Codes: C - connected, S - static, R - RIP, B - BGP, (>) - Diversion path
           D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
           N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
           E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
           i - ISIS, L1 - IS-IS level-1, L2 - IS-IS level-2
           ia - IS-IS inter area, su - IS-IS summary null, * - candidate default
           U - per-user static route, o - ODR, L - local, G  - DAGR
           A - access/subscriber, a - Application route, (!) - FRR Backup path
    Gateway of last resort is not set
    S    10.0.0.0/27 is directly connected, 08:04:01, Null0
    O    10.0.0.4/30 [110/2] via 10.0.0.9, 08:03:10, GigabitEthernet0/0/0/0
    C    10.0.0.8/30 is directly connected, 08:04:00, GigabitEthernet0/0/0/0
    L    10.0.0.10/32 is directly connected, 08:04:00, GigabitEthernet0/0/0/0
    O    10.0.0.12/30 [110/3] via 10.0.0.9, 08:03:10, GigabitEthernet0/0/0/0
                      [110/3] via 10.0.128.9, 08:03:10, GigabitEthernet0/0/0/1
    O    10.0.0.16/30 [110/2] via 10.0.128.9, 08:03:51, GigabitEthernet0/0/0/1
    O    10.0.0.24/30 [110/3] via 10.0.128.9, 06:29:14, GigabitEthernet0/0/0/1
    O    10.0.0.28/30 [110/2] via 10.0.128.9, 08:03:51, GigabitEthernet0/0/0/1
    S    10.0.128.0/29 is directly connected, 08:04:01, Null0
    O    10.0.128.0/30 [110/3] via 10.0.0.9, 08:03:10, GigabitEthernet0/0/0/0
                       [110/3] via 10.0.128.9, 08:03:10, GigabitEthernet0/0/0/1
    O    10.0.128.4/30 [110/2] via 10.0.128.9, 08:03:51, GigabitEthernet0/0/0/1
    C    10.0.128.8/30 is directly connected, 08:04:00, GigabitEthernet0/0/0/1
    L    10.0.128.10/32 is directly connected, 08:04:00, GigabitEthernet0/0/0/1
    S    10.1.0.4/30 is directly connected, 06:57:23, Null0
    S    10.1.128.4/30 is directly connected, 08:04:01, Null0
    C    10.18.0.0/16 is directly connected, 08:04:00, MgmtEth0/0/CPU0/0
    L    10.18.0.9/32 is directly connected, 08:04:00, MgmtEth0/0/CPU0/0
    L    127.0.0.0/8 [0/0] via 0.0.0.0, 08:04:04
    O    192.168.0.1/32 [110/2] via 10.0.0.9, 08:03:10, GigabitEthernet0/0/0/0
    O    192.168.0.2/32 [110/4] via 10.0.0.9, 08:03:10, GigabitEthernet0/0/0/0
                        [110/4] via 10.0.128.9, 08:03:10, GigabitEthernet0/0/0/1
    O    192.168.0.3/32 [110/3] via 10.0.128.9, 08:03:40, GigabitEthernet0/0/0/1
    O    192.168.0.4/32 [110/3] via 10.0.128.9, 08:03:51, GigabitEthernet0/0/0/1
    O    192.168.0.5/32 [110/4] via 10.0.0.9, 08:03:10, GigabitEthernet0/0/0/0
                        [110/4] via 10.0.128.9, 08:03:10, GigabitEthernet0/0/0/1
    O    192.168.0.6/32 [110/2] via 10.0.128.9, 08:03:51, GigabitEthernet0/0/0/1
    O    192.168.0.7/32 [110/3] via 10.0.0.9, 08:03:10, GigabitEthernet0/0/0/0
                        [110/3] via 10.0.128.9, 08:03:10, GigabitEthernet0/0/0/1
    L    192.168.0.8/32 is directly connected, 08:04:00, Loopback0
    B    192.168.0.17/32 [20/0] via 10.1.0.5 (nexthop in vrf TR), 00:05:37
    B    192.168.0.18/32 [20/0] via 10.1.0.5 (nexthop in vrf TR), 00:05:37
    I'm only seeing the routes from the directly connected CE, but not the routes received from RR. What am I missing here?
    Thanks!
    -Sajith

    I'm trying to leak routes from a VRF to global. I can get the routes leaked from directly connected CE to the global, however I can't get the routes from remote CE's to leak in to the global routing table. Below are my configurations
    RP/0/0/CPU0:B25BR1#sh run vrf TR
    Wed Dec 17 22:40:33.772 UTC
    vrf TR
     address-family ipv4 unicast
      import route-target
       65000:7020
      export to default-vrf route-policy TR-2-GLOBAL
      export route-target
       65000:7020
    RP/0/0/CPU0:B25BR1#sh rpl route-policy TR-2-GLOBAL
    Wed Dec 17 22:40:50.851 UTC
    route-policy TR-2-GLOBAL
      if destination in TR-2-GLOBAL then
        pass
      endif
    end-policy
    RP/0/0/CPU0:B25BR1#sh rpl prefix-set TR-2-GLOBAL
    Wed Dec 17 22:40:57.861 UTC
    prefix-set TR-2-GLOBAL
      192.168.0.17/32,
      192.168.0.18/32,
      192.168.0.19/32,
      192.168.0.20/32
    end-set
    !Routes that I want to see also are  192.168.0.19/32 and 192.168.0.20/32 which are there in the VRF routing table
    RP/0/0/CPU0:B25BR1#sh route vrf TR
    Wed Dec 17 22:41:45.767 UTC
    Codes: C - connected, S - static, R - RIP, B - BGP, (>) - Diversion path
           D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
           N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
           E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
           i - ISIS, L1 - IS-IS level-1, L2 - IS-IS level-2
           ia - IS-IS inter area, su - IS-IS summary null, * - candidate default
           U - per-user static route, o - ODR, L - local, G  - DAGR
           A - access/subscriber, a - Application route, (!) - FRR Backup path
    Gateway of last resort is not set
    B    10.1.0.0/30 [20/0] via 10.1.0.5, 00:14:32
    C    10.1.0.4/30 is directly connected, 06:57:19, GigabitEthernet0/0/0/2
    L    10.1.0.6/32 is directly connected, 06:57:19, GigabitEthernet0/0/0/2
    B    10.1.128.0/30 [20/0] via 10.1.0.5, 00:14:32
    B    192.168.0.17/32 [20/0] via 10.1.0.5, 00:13:56
    B    192.168.0.18/32 [20/0] via 10.1.0.5, 00:13:56
    B    192.168.0.19/32 [200/0] via 192.168.0.4 (nexthop in vrf default), 00:13:31
    B    192.168.0.20/32 [200/0] via 192.168.0.4 (nexthop in vrf default), 00:13:31
    RP/0/0/CPU0:B25BR1#sh ip rou
    Wed Dec 17 22:41:50.097 UTC
    Codes: C - connected, S - static, R - RIP, B - BGP, (>) - Diversion path
           D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
           N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
           E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
           i - ISIS, L1 - IS-IS level-1, L2 - IS-IS level-2
           ia - IS-IS inter area, su - IS-IS summary null, * - candidate default
           U - per-user static route, o - ODR, L - local, G  - DAGR
           A - access/subscriber, a - Application route, (!) - FRR Backup path
    Gateway of last resort is not set
    S    10.0.0.0/27 is directly connected, 08:04:01, Null0
    O    10.0.0.4/30 [110/2] via 10.0.0.9, 08:03:10, GigabitEthernet0/0/0/0
    C    10.0.0.8/30 is directly connected, 08:04:00, GigabitEthernet0/0/0/0
    L    10.0.0.10/32 is directly connected, 08:04:00, GigabitEthernet0/0/0/0
    O    10.0.0.12/30 [110/3] via 10.0.0.9, 08:03:10, GigabitEthernet0/0/0/0
                      [110/3] via 10.0.128.9, 08:03:10, GigabitEthernet0/0/0/1
    O    10.0.0.16/30 [110/2] via 10.0.128.9, 08:03:51, GigabitEthernet0/0/0/1
    O    10.0.0.24/30 [110/3] via 10.0.128.9, 06:29:14, GigabitEthernet0/0/0/1
    O    10.0.0.28/30 [110/2] via 10.0.128.9, 08:03:51, GigabitEthernet0/0/0/1
    S    10.0.128.0/29 is directly connected, 08:04:01, Null0
    O    10.0.128.0/30 [110/3] via 10.0.0.9, 08:03:10, GigabitEthernet0/0/0/0
                       [110/3] via 10.0.128.9, 08:03:10, GigabitEthernet0/0/0/1
    O    10.0.128.4/30 [110/2] via 10.0.128.9, 08:03:51, GigabitEthernet0/0/0/1
    C    10.0.128.8/30 is directly connected, 08:04:00, GigabitEthernet0/0/0/1
    L    10.0.128.10/32 is directly connected, 08:04:00, GigabitEthernet0/0/0/1
    S    10.1.0.4/30 is directly connected, 06:57:23, Null0
    S    10.1.128.4/30 is directly connected, 08:04:01, Null0
    C    10.18.0.0/16 is directly connected, 08:04:00, MgmtEth0/0/CPU0/0
    L    10.18.0.9/32 is directly connected, 08:04:00, MgmtEth0/0/CPU0/0
    L    127.0.0.0/8 [0/0] via 0.0.0.0, 08:04:04
    O    192.168.0.1/32 [110/2] via 10.0.0.9, 08:03:10, GigabitEthernet0/0/0/0
    O    192.168.0.2/32 [110/4] via 10.0.0.9, 08:03:10, GigabitEthernet0/0/0/0
                        [110/4] via 10.0.128.9, 08:03:10, GigabitEthernet0/0/0/1
    O    192.168.0.3/32 [110/3] via 10.0.128.9, 08:03:40, GigabitEthernet0/0/0/1
    O    192.168.0.4/32 [110/3] via 10.0.128.9, 08:03:51, GigabitEthernet0/0/0/1
    O    192.168.0.5/32 [110/4] via 10.0.0.9, 08:03:10, GigabitEthernet0/0/0/0
                        [110/4] via 10.0.128.9, 08:03:10, GigabitEthernet0/0/0/1
    O    192.168.0.6/32 [110/2] via 10.0.128.9, 08:03:51, GigabitEthernet0/0/0/1
    O    192.168.0.7/32 [110/3] via 10.0.0.9, 08:03:10, GigabitEthernet0/0/0/0
                        [110/3] via 10.0.128.9, 08:03:10, GigabitEthernet0/0/0/1
    L    192.168.0.8/32 is directly connected, 08:04:00, Loopback0
    B    192.168.0.17/32 [20/0] via 10.1.0.5 (nexthop in vrf TR), 00:05:37
    B    192.168.0.18/32 [20/0] via 10.1.0.5 (nexthop in vrf TR), 00:05:37
    I'm only seeing the routes from the directly connected CE, but not the routes received from RR. What am I missing here?
    Thanks!
    -Sajith

  • "Show ip route" L - Local

    I have just issued the 'sh ip route' command and the router output is showing some of the routes as 'L'
    I have the expected Connected 'C' and OSPF 'O'  routes but I have not seen the 'L' indicator before. I have done a search but can't find anything that explains why the /32 interface addresses have been marked as Local
    ROUTER#sh ip route
    Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
           D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
    <OUTPUT OMITTED>
    C        XX.YYY.1.64/30 is directly connected, GigabitEthernet0/0
    L        XX.YYY.1.66/32 is directly connected, GigabitEthernet0/0
    C        XX.YYY.1.68/30 is directly connected, GigabitEthernet0/1
    L        XX.YYY.1.70/32 is directly connected, GigabitEthernet0/1
    These connections are configured as point to point OSPF connections for connecting the router to core switches, and the routers themselves are used as BGP Route Reflectors. Can anyone shed any light on the meaning of 'Local' and why it is needed as well as  'Connected'. I can do a 'sh ip route connected' but it doesn't allow 'sh ip route local'
    These are c7301 routers running IOS 12.2(33)SRD
    Regards
    Mel

    Probably no one will read this 4 years after, but just for thread comletion's sake (and since gougle returns this page in its results) I cut-paste the following passage form the CCNA 100-101 cert guide(Chapter 16 after Example 16-1).
    "Note that the router also automatically produces a different kind of route, called a local route. The local routes defines a route for the one specific IP address configured on the router interface. Each local route has a /32 prefix length, defining a host route, which defines a route just for that one IP address. For example, the last local route, for 172.16.5.1/32, defines a route that matches only the IP address of 172.16.5.1. Routers use these local routes that list their own local IP addresses to more efficiently forward packets sent to the router itself."

  • Force Routing Over second link?

    We have a MPLS WAN connecting our offices from our Service Provider. Our Head Office has a larger 50Mbps pipe and a remote office has 2 separate 2Mbps links (lets call them link1 and link2). Right now all traffic only goes over Link1 at the remote office as per all the BGP routing. I can make a static route at the remote office for specific traffic to go over link2 and it will successfully send over that link. My question is, is there a way to get traffic from Head Office to go to Link2 instead of Link1?

    It primary depends on BGP routing. You can try to change the way ISP send traffic to you branch using different BGP path attribute  in advertisement on the two links but you have to negotiated with ISP because they can also "force" their netwrok to use on path instead of the other for example using BGP local preference. I suggest you to read here to understand BGP algorithm:
    http://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/13753-25.html
    Bye,
    enrico

  • 2900 Series Router - Over 700 failed login attempts - How do I find the source IP?

    There is a 2900 series router  Version 15.0(1)M1, in our company, recently the logs show that there were over 700 failed login attempts to try and gain privelege level 15 access. Is there a way to see the source IP from the host that is attempting the logins?

    There is a 2900 series router  Version 15.0(1)M1, in our company, recently the logs show that there were over 700 failed login attempts to try and gain privelege level 15 access. Is there a way to see the source IP from the host that is attempting the logins?

  • AirPort Extreme 802.11n as a wireless router and local network switch?

    Good afternoon,
    I'm curious if its possible to have the APE in wireless network mode and connect systems via hard line as well?
    I have an AirPort Extreme 802.11n set to "Create a Wireless Network" mode that is attached directly to a cable modem for internet connectevity. My issue is that while all wireless devices (several iPods, two iPhones and three laptop computers) connect to the APE without issue (and have internet access), when I try to plug in a Windows 7 desktop computer via one of the ethernet jacks, Windows is unable to connect and shows the network as "unidentified," spitting back a private IP address as opposed to a local LAN (this behavior repeats for an Ubuntu Linux box as well).
    Not sure if the APE is misconfigured, this is a Windows 7 issue or if its improper use on my part (though this also precludes me from connecting a gigabit switch to the APE).
    Thank you,
    Nathan

    Properly configured, the AirPort should provide both wired and wireless network client with Internet access.
    At this point, I would recommend that you do the following as a minimum:
    Power-down the modem, AirPort base station, and computer(s).
    Power-up the modem; wait at least 10-15 minutes to allow it adequate time to initialize.
    Power-up the AirPort base station; wait at least 5-10 minutes. Note: The AirPort's status light may continue to flash amber after it has intialized. That is because, there may be some additional configuration items necessary, like setting up wireless security, before the overall setup is completed to get a green status.
    Power-up your computer(s).
    If the above steps do not solve the problem, start over with step 1 above, but then perform the next steps between steps 1 & 2. above.
    Disconnect the AirPort base station from the Internet broadband modem.
    While all of the devices are powered-down, perform a "factory default" reset on the base station. This will get it back to its "out-of-the-box" configuration and make setting it up much easier, especially if you use the "Assist me" process within the AirPort Utility. (ref: Resetting an AirPort Base Station or Time Capsule)
    After the base station resets, go ahead and power it back down.
    Reconnect the AirPort base station to the Internet broadband modem. For the Extreme and Time Capsule, be sure to connect the cable to the base station's WAN (circle-of-dots) port.
    Continue with step 2 in the first set of steps.
    In this basic configuration, the AirPort base station will broadcast an unsecured wireless network with a Network Name (SSID) of Apple Network NNNNNN. Network clients, connected to the base station either by wire or wireless, should now be able to access the Internet through the ISP's modem. Once Internet connectivity has been verified, you can use the AirPort Utility to configure the base station for wireless security and any other desired options. Please post back your results.

Maybe you are looking for