PE-CE OSPF problem

CE1-CE2-PE1-P-P-PE2-CE3-CE3
For OSPF superbackbone:
From CE2 perspective, PE1 is a ABR
From provider network perspective, PE1 and PE2 is a ASBR.
But for Provider network, how they see CE2?
and Do CE1(in other area) still see PE1 as a ABR?

In this scenario, the CE routers are ABR routers and the PE routers are ABR and ASBR routers for the CE1 and CE2 routers.
http://www.cisco.com/warp/public/121/mpls_ospf2.html

Similar Messages

  • OSPF problem: Neighbor Down 1-2 times per day

    Hi
    We have 4 devices are running OSPF (3 cisco routers and 1 Juniper firewall as show in attachment file). In last few months, we got Neighbot Down message almost 1-2 times per day. Network between them interrupt for a short time and even monitoring mechanism does not aware the interruption(down time is too short). Could I have your advice of any possible root cause to this problem?
    Timer intervals configured to all devices are same: Hello 10, Dead 40, Wait 40, Retransmit 5
    Neighbor A
    Neighbor A#sh ip ospf neighbor 
    Neighbor ID     Pri   State           Dead Time   Address         Interface
    172.16.255.128    1   FULL/DROTHER    00:00:34    172.16.108.11   GigabitEthernet0/11
    172.16.255.130    1   FULL/DR         00:00:33    172.16.108.2    GigabitEthernet0/11
    172.16.255.64     1   FULL/DROTHER    00:00:34    172.16.107.1    GigabitEthernet0/12
    172.16.255.128    1   FULL/DROTHER    00:00:38    172.16.107.11   GigabitEthernet0/12
    172.16.255.130    1   FULL/DR         00:00:38    172.16.107.7    GigabitEthernet0/12
    Neighbor A#show log
    Mar 16 06:03:33.159: %OSPF-5-ADJCHG: Process 1, Nbr 172.16.255.128 on GigabitEthernet0/12 from FULL to DOWN, Neighbor Down: Dead timer expired
    Mar 16 06:03:50.137: %OSPF-5-ADJCHG: Process 1, Nbr 172.16.255.128 on GigabitEthernet0/12 from LOADING to FULL, Loading Done
    Mar 16 21:15:05.509: %OSPF-5-ADJCHG: Process 1, Nbr 172.16.255.64 on GigabitEthernet0/12 from LOADING to FULL, Loading Done
    Neighbor B
    Neighbor B#sh ip ospf neighbor 
    Neighbor ID     Pri   State           Dead Time   Address         Interface
    172.16.255.128    1   FULL/DROTHER    00:00:36    172.16.108.11   GigabitEthernet0/11
    172.16.255.129    1   FULL/BDR        00:00:35    172.16.108.1    GigabitEthernet0/11
    172.16.255.64     1   FULL/DROTHER    00:00:39    172.16.107.1    GigabitEthernet0/12
    172.16.255.128    1   FULL/DROTHER    00:00:30    172.16.107.11   GigabitEthernet0/12
    172.16.255.129    1   FULL/BDR        00:00:35    172.16.107.6    GigabitEthernet0/12
    Neighbor B#show log
    Mar 16 06:03:33.143: %OSPF-5-ADJCHG: Process 1, Nbr 172.16.255.128 on GigabitEthernet0/12 from FULL to DOWN, Neighbor Down: Dead timer expired
    Mar 16 06:03:50.122: %OSPF-5-ADJCHG: Process 1, Nbr 172.16.255.128 on GigabitEthernet0/12 from LOADING to FULL, Loading Done
    Mar 16 21:14:58.054: %OSPF-5-ADJCHG: Process 1, Nbr 172.16.255.64 on GigabitEthernet0/12 from LOADING to FULL, Loading Done
    Mar 16 21:15:03.800: %OSPF-5-ADJCHG: Process 1, Nbr 172.16.255.128 on GigabitEthernet0/12 from LOADING to FULL, Loading Done
    Neighbor C
    Neighbor C#sh ip ospf neighbor 
    Neighbor ID     Pri   State           Dead Time   Address         Interface
    172.16.255.129    1   FULL/BDR        00:00:35    172.16.108.1    FastEthernet0/1/0
    172.16.255.130    1   FULL/DR         00:00:38    172.16.108.2    FastEthernet0/1/0
    172.16.255.64     1   2WAY/DROTHER    00:00:30    172.16.107.1    FastEthernet0/0/1
    172.16.255.129    1   FULL/BDR        00:00:35    172.16.107.6    FastEthernet0/0/1
    172.16.255.130    1   FULL/DR         00:00:33    172.16.107.7    FastEthernet0/0/1
    Neighbor C#show log
    Mar 16 06:03:23.571: %OSPF-5-ADJCHG: Process 1, Nbr 172.16.255.130 on FastEthernet0/0/1 from FULL to DOWN, Neighbor Down: Dead timer expired
    Mar 16 06:03:25.479: %OSPF-5-ADJCHG: Process 1, Nbr 172.16.255.129 on FastEthernet0/0/1 from FULL to DOWN, Neighbor Down: Dead timer expired
    Mar 16 06:03:29.415: %OSPF-5-ADJCHG: Process 1, Nbr 172.16.255.64 on FastEthernet0/0/1 from EXSTART to DOWN, Neighbor Down: Dead timer expired
    Mar 16 06:03:50.112: %OSPF-5-ADJCHG: Process 1, Nbr 172.16.255.129 on FastEthernet0/0/1 from LOADING to FULL, Loading Done
    Mar 16 06:03:50.112: %OSPF-5-ADJCHG: Process 1, Nbr 172.16.255.130 on FastEthernet0/0/1 from LOADING to FULL, Loading Done
    Mar 16 21:14:53.740: %OSPF-5-ADJCHG: Process 1, Nbr 172.16.255.130 on FastEthernet0/0/1 from FULL to DOWN, Neighbor Down: Dead timer expired
    Mar 16 21:15:03.793: %OSPF-5-ADJCHG: Process 1, Nbr 172.16.255.130 on FastEthernet0/0/1 from LOADING to FULL, Loading Done

    I think no L2 loops in the network. We have spanning tree configured on switches connecting to router A & B.
    VLAN0108
      Spanning tree enabled protocol ieee
      Root ID    Priority    32876
                 Address     5c50.15a3.8480
                 This bridge is the root
                 Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec
      Bridge ID  Priority    32876  (priority 32768 sys-id-ext 108)
                 Address     5c50.15a3.8480
                 Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec
                 Aging Time  300 sec
    Interface           Role Sts Cost      Prio.Nbr Type
    Gi1/0/45            Desg FWD 4         128.45   P2p Edge
    Gi1/0/47            Desg FWD 19        128.47   P2p Edge
    Gi1/0/48            Desg FWD 4         128.48   P2p Edge
    VLAN0107
      Spanning tree enabled protocol ieee
      Root ID    Priority    32875
                 Address     5c50.15ec.f000
                 This bridge is the root
                 Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec
      Bridge ID  Priority    32875  (priority 32768 sys-id-ext 107)
                 Address     5c50.15ec.f000
                 Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec
                 Aging Time  300 sec
    Interface           Role Sts Cost      Prio.Nbr Type
    Gi1/0/45            Desg FWD 4         128.45   P2p Edge
    Gi1/0/47            Desg FWD 19        128.47   P2p Edge
    Gi1/0/48            Desg FWD 4         128.48   P2p Edge

  • OSPF problem in a GSR12000 with MPLS interfaces

    Hi,
    I am using an MPLS interface connected to other vendor routers.
    OSPF is set on the MPLS interface.
    The OSPF did not synched with the other vendor OSPF due to the following :
    00:45:55: OSPF: Rcv DBD from 10.10.55.113 on GigabitEthernet4/0 seq 0x178476E opt 0x42 flag 0x7 len 32 mtu 1500 state EXSTART
    00:45:55: OSPF: First DBD and we are not SLAVE
    00:46:00: OSPF: Retransmitting DBD to 10.10.55.113 on GigabitEthernet4/0
    00:46:00: OSPF: Up DBD Retransmit cnt to 1 for 10.10.55.113 on GigabitEthernet4/0
    00:46:00: OSPF: Send DBD to 10.10.55.113 on GigabitEthernet4/0 seq 0x745 opt 0x52 flag 0x7 len 32
    00:46:00: OSPF: Rcv DBD from 10.10.55.113 on GigabitEthernet4/0 seq 0x178476E opt 0x42 flag 0x7 len 32 mtu 1500 state EXSTART
    00:46:00: OSPF: First DBD and we are not SLAVE
    After diagnosing the problem we found out that if the loopback router-id address value is bigger then the neighbores IP address then you will get this problem.
    If you will change the router-id ip address for 1.1.1.1 and the MTU is set ok (to be 1500 on the MPLs i/fs) then it will work well !
    Regards,
    Simhon Doctori.

    Hi,
    Sorry for barging in on this. Can you please tell me how this Master/Slave relationship comes into play in conjunction with DR. DR is a focal point for distributing LSD and propagating all the updates on broadcast or NBMA networks.
    a. What if DR has a RID of 1.1.1.1 which is lower
    than any other RID on a segment?
    b. Will it be chosen as Master anyhow?
    c. What if a topology change occurs on a Slave
    router, it is allowed to update the Master?
    Is there the same Master/Slave notion in other routing protocols, specifically ISIS, EIGRP and BGP?
    Thank you very much.
    David

  • OSPF Problem

    Hi All,
    I have a customer which has the following setup.
    R1
    R2 R3
    R4
    R1 is at the central site and has the data center hosted. The link between R1 and R2, R2 and R4 are in Area0. The links between R1 and R3, R3 and R4 are in Area1.
    Users at R4 wants to access some SAP servers which are hosted at R1. The link between R4 and R2 is a slow speed link and the link between R4 and R3 is a 2 MBPS LL.
    The problem is that the R4 is learing the routes to the SAP servers segment Via R2 with slow speed links (a backup link) and hence users are facing a problem to access the SAP application.
    We have tried changing the cost on the R2 and R4 interfaces from default 48 to 1000 and more but still it learns the route Via R2. When we shut the interface down at R4, the router learns the route via R3 (which it should be and what we want) everything works fine.
    Let me know your thoughts on this and how can we fine tune that.
    Regards,
    -amit singh

    Hello,
    OSPF will always - independant of metric - prefer INTRA area routes over INTER area routes.
    The way you described the setup I would assume, that R4 has the network of the SAP servers learned through LSA type 1 in area 0 and through LSA type 3 in area 1.
    If this is the case then there is little to do, other than setting up a virtual link through area 1 between R1 and R4 or converting everything to area 0.
    I would recommend to look for a solution without virtual links.
    Hope this helps! Please rate all posts.
    Regards, Martin

  • MPLS OSPF Problem

    Hi,
    Anyone know the cause of the problem below ? This log appeared after ospf establish.
    %OCE-SP-3-UNEXPECTED_SW_OBJ_TYPE: SW_OBJ handle/type mismatch; expecting oce type label, found 1
    Thanks,
    Gilang.

    Hi
    This seems to be a bug. Please check the below URL and search for SW_OBJ handle/type mismatch
    http://www.cisco.com/en/US/docs/ios/system/messages/guide/sm_cn07.html
    regards
    shivlu jain
    http://www.mplsvpn.info

  • [OSPF/LDP/PW Fast convergence] ASR9k/ME3800/ME3600

    Hello, Netpro:
    I'm having a bit of a problem with OSPF/LDP Pseudowire fast convergence.
    I have a test lab scenario with 2 ASR9000, 1 ME3800X and 1 ME3600X.
    They are connected in an L3 MPLS ring, like this:
    ME3800X---[a]---ASR1--[b]--ASR2---[c]---ME3600X
      |                                                                      |
      |--------------------------------[d]-----------------------|   
    The MEs are connected back to back closing the loop.
    The ring is configured for: OSPF fast convergence timers, LDP session protection, MPLS LDP  sync and BFP for OSPF on all interfaces.
    For testing purposes I've configured a pseudowire between the MEs and forced the path via OSPF to go through the ASRs.
    My problem is that I do not get the same responses when breaking the ring in different places. For example: if I break the ring in (b) or (d) i get ~100ms loss (when breaking the d connection, I change OSPF so that the PW takes the direct route between MEs). If I break the ring in (a) or ( c ) I get ~ 500ms loss.
    Also for testing purposes, I ran a similar test but with regular L3 interfaces ( NO pseudowire) between MEs and for all scenarios i get 60-100ms. So, basically I'm assuming OSPF is converging like it's supposed to and the issue is within LDP.
    Any ideas?
    Regards,
    c.

    Yes, I did test traffic engineering, but there's a bug (on 3600/3800) that when a PW changes paths, it will stop passing traffic, so that part is stuck.
    Is there an OSPF problem with ASR? I didn't understand very well your comment
    My description of my scenario is just for simplicity purposes. The real question here is, what is going on between an IOS box and an XR box that when you cause a fault in between those 2, LDP recovers in 500ms and when you cause a fault in same-OS boxes, recovery is 100ms.

  • Problem reset Nexus 5596

    Hello,
    Some equipments Nexus 5596 from a customer have reinitiated and it seems to have been provoked by an OSPF problem although I am not sure.
    The logs from the equipment show:
    2013 Jan  9 07:29:42 ROISBPRE2CN %BTCM-5-BTCM_LOG_L3_READY: system becomes L3 Ready
    2013 Jan  9 07:29:44 ROISBPRE2CN %VSHD-5-VSHD_SYSLOG_CONFIG_I: Configured from vty by  on ppm.3726
    2013 Jan  9 07:29:45 ROISBPRE2CN %OSPF-5-ADJCHANGE:  ospf-1 [3236]  Nbr 180.101.250.26 on Vlan902 went TWOWAY
    2013 Jan  9 07:29:48 ROISBPRE2CN %OSPF-5-ADJCHANGE:  ospf-1 [3236]  Nbr 180.101.250.29 on Vlan902 went TWOWAY
    2013 Jan  9 07:29:49 ROISBPRE2CN %OSPF-5-ADJCHANGE:  ospf-1 [3236]  Nbr 180.101.250.28 on Vlan902 went TWOWAY
    2013 Jan  9 07:29:52 ROISBPRE2CN %OSPF-5-ADJCHANGE:  ospf-1 [3236]  Nbr 180.101.250.17 on Vlan902 went TWOWAY
    2013 Jan  9 07:29:52 ROISBPRE2CN %OSPF-5-ADJCHANGE:  ospf-1 [3236]  Nbr 180.101.250.29 on Vlan902 went FULL
    2013 Jan  9 07:29:52 ROISBPRE2CN %OSPF-5-ADJCHANGE:  ospf-1 [3236]  Nbr 180.101.250.26 on Vlan902 went FULL
    2013 Jan  9 07:30:41 ROISBPRE2CN %ETHPORT-5-IF_DOWN_INITIALIZING: Interface port-channel902 is down (Initializing)
    2013 Jan  9 07:30:41 ROISBPRE2CN %ETHPORT-5-IF_DOWN_INITIALIZING: Interface port-channel100 is down (Initializing)
    2013 Jan  9 07:30:41 ROISBPRE2CN %ETHPORT-5-IF_DOWN_INITIALIZING: Interface Ethernet1/31 is down (Initializing)
    2013 Jan  9 07:30:41 ROISBPRE2CN %ETHPORT-5-IF_DOWN_INITIALIZING: Interface Ethernet1/32 is down (Initializing)
    2013 Jan  9 07:30:41 ROISBPRE2CN %ETHPORT-5-IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN: Interface port-channel112 is down (No operational mem
    bers)
    2013 Jan  9 07:30:41 ROISBPRE2CN %ETHPORT-5-IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN: Interface port-channel111 is down (No operational mem
    bers)
    I wanted to know if you know something about a problem with OSPF in next version:
      cisco Nexus5596 Chassis ("O2 48X10GE/Modular Supervisor")
      Intel(R) Xeon(R) CPU         with 8263880 kB of memory.
       bootflash:    2007040 kB
    Kernel uptime is 0 day(s), 2 hour(s), 25 minute(s), 35 second(s)
    System version: 5.1(3)N1(1a)
    Thank you very much.

    OSPF logs say that your switch is fully adjacent with 180.101.250.26 and .29, this means normal operation.
    Bi-directional communication has been established between the Nexus and 180.101.250.17 and .28. They are in the middle of the OSPF neighboring process.
    Some interfaces are initializing, and Po111 and 112 have no member ports (the channel-group <111|112> command hasn't been issued on any physical interfaces).
    More information about OSPF neighbor states can be found here.

  • Trying to understand problems that occur when redistributing between two OSPF processes

    Hi all, I'm currently brushing up on my OSPF and trying to understand the problems that can occur when redistributing between two OSPF processes. I have read and understand (I think!) the issues caused by the fact that the same route submitted by two different OSPF processes may not necessarily follow the OSPF rules that one would expect - for example, OSPF preferring intra-area routes to inter-area routes to external routes, but only within the same process. So, if the same route is submitted from two different processes, that rule goes out the window.
    But I'm having some difficulty getting my head around the idea of setting the administrative distance lower in one OSPF process to prefer one domain over the other. I just can't quite follow the example described in this document:
    http://www.cisco.com/c/en/us/support/docs/ip/open-shortest-path-first-ospf/4170-ospfprocesses.html#twored
    Specifically, in figure 4 where two external networks - external network "N" originating in OSPF domain 1, and external network "M" originating in OSPF domain 2 - are redistributed via two ASBRs. The explanation states:
    This sequence of events could occur occur:
    Router A (Router B) redistributes M into Domain 1, and external M will reach Router B (Router A).
    Because the administrative distance of Domain 1 is lower than Domain 2, Router A (Router B) will install M through Domain 1 and will set to maxage its previous originated LSA (event 1) into Domain 1.
    Because M has been set to maxage in Domain 2, Router A (Router B) will install M though Domain 2 and, therefore, will redistribute M into Domain 2.
    Same as event 1.
    I can't quite work my way through this. I guess it must have something to do with the redistribution of "M" from domain 2 into domain 1 being learned by both ASBRs due to the lower administrative distance assigned to external routes in domain 1, and the original routes through domain 2 being deleted, but then I can't follow the rest of the description. And I can't understand why this would be a problem for network "M" in OSPF domain 2, but NOT for network "N" in OSPF domain 1.
    Any explanation gratefully received!
    Thanks, Graham

    Hello.
    You are right - whenever A and B learns about "M" from Domain 2, they craft LSA for domain 1 and inject it simultaneously. They learn each other's LSAs simultaneously and withdraw (set timer to 3600) for previous LSAs. And it might flap infinitely.
    If they don't learn LSA simultaneously (let's say that A is much faster then B), then there will be no flaps, but B would learn all Domain 2 routes (not just redistributed) via Domain 1.
    And later you will observe routing loop (when you stop advertising M from D): A knows "M" from Domain 2 and injects into Domain 1, B knows from A via Domain 1 and injects into Domain 2... so "M" stays in the routing tables due to mutual redistribution.
    You don't have similar (flap) issue with network "N", because admin distance is lower for Domain 1, so both routers would never prefer OSPF via Domain 2! But having no issue with route flaps, you still will observe routing loop if you stop advertising "N" from C.

  • OSPF external route selection problem

    Hello. I have a situation where I got two paths to get to a destination. Router A can get to subnet C either through my Telco's onsite router (Router A->telco router->Router C)or through a secondary link that travels from Router A-> Router B->diffenent Telco router->Router C.
    The link between Router A and the telco router is area 0. The link between Router A->B->Telco router is also area 0.
    Normally I want traffic to go directly through the onsite telco router...and only go through the longer route if the onsite router goes down.
    For some reason I'm going through the suboptimal path. Here's what the OSPF database is telling me:
    Routing Bit Set on this LSA
    LS age: 1267
    Options: (No TOS-capability, DC)
    LS Type: AS External Link
    Link State ID: 192.168.33.0 (External Network Number )
    Advertising Router: 192.168.50.14
    LS Seq Number: 80000084
    Checksum: 0x4B8B
    Length: 36
    Network Mask: /24
    Metric Type: 1 (Comparable directly to link state metric)
    TOS: 0
    Metric: 100
    Forward Address: 0.0.0.0
    External Route Tag: 66
    LS age: 262
    Options: (No TOS-capability, DC)
    LS Type: AS External Link
    Link State ID: 192.168.33.0 (External Network Number )
    Advertising Router: 192.168.50.94
    LS Seq Number: 800003B8
    Checksum: 0xF757
    Length: 36
    Network Mask: /24
    Metric Type: 1 (Comparable directly to link state metric)
    TOS: 0
    Metric: 100
    Forward Address: 0.0.0.0
    External Route Tag: 66
    Both telco routers advertise this route as an extern type 1 with a metric of 100. Can anyone shed some light as to why my router is picking the path via 50.14 instead of 50.94? 50.94 is a locally connected network. 50.14 is a couple of hops away.
    Thanks,
    Mike

    No problem.
    Here's the output...
    show ip ospf border-routers
    OSPF Process 2 internal Routing Table
    Codes: i - Intra-area route, I - Inter-area route
    OSPF Process 1 internal Routing Table
    Codes: i - Intra-area route, I - Inter-area route
    i 10.0.22.3 [2] via 192.168.19.14, Vlan168, ABR/ASBR, Area 0, SPF 42
    i 10.0.22.2 [2] via 192.168.19.2, Vlan168, ABR/ASBR, Area 0, SPF 42
    i 192.168.30.5 [501] via 192.168.19.15, Vlan168, ASBR, Area 0, SPF 42
    i 192.168.30.5 [501] via 192.168.19.14, Vlan168, ASBR, Area 0, SPF 42
    i 172.29.50.1 [1] via 192.168.19.11, Vlan168, ASBR, Area 0, SPF 42
    i 172.18.1.2 [3] via 192.168.19.15, Vlan168, ABR/ASBR, Area 0, SPF 42
    i 172.18.1.3 [2] via 192.168.19.15, Vlan168, ABR/ASBR, Area 0, SPF 42
    i 192.168.1.5 [1] via 192.168.19.8, Vlan168, ASBR, Area 0, SPF 42
    i 10.0.32.2 [2] via 192.168.19.15, Vlan168, ABR/ASBR, Area 0, SPF 42
    i 10.0.32.3 [2] via 192.168.19.3, Vlan168, ABR/ASBR, Area 0, SPF 42
    i 172.27.95.1 [2] via 192.168.19.16, Vlan168, ABR/ASBR, Area 0, SPF 42
    i 172.19.1.3 [1] via 192.168.19.15, Vlan168, ABR/ASBR, Area 0, SPF 42
    i 172.19.1.2 [1] via 192.168.19.14, Vlan168, ABR/ASBR, Area 0, SPF 42
    i 10.0.24.2 [1] via 192.168.19.22, Vlan168, ABR/ASBR, Area 0, SPF 42
    i 10.0.24.3 [1] via 192.168.19.23, Vlan168, ABR/ASBR, Area 0, SPF 42
    i 192.168.19.4 [1] via 192.168.19.4, Vlan168, ASBR, Area 0, SPF 42
    i 172.27.87.1 [1] via 192.168.19.12, Vlan168, ASBR, Area 0, SPF 42
    i 192.168.19.19 [1] via 192.168.19.19, Vlan168, ASBR, Area 0, SPF 42
    i 172.20.1.2 [3] via 192.168.19.3, Vlan168, ASBR, Area 0, SPF 42
    i 172.20.1.3 [2] via 192.168.19.3, Vlan168, ASBR, Area 0, SPF 42
    I 10.0.16.11 [2] via 192.168.19.3, Vlan168, ASBR, Area 0, SPF 42
    I 10.0.16.11 [3] via 192.168.19.2, Vlan168, ASBR, Area 0, SPF 42
    I 10.0.16.10 [2] via 192.168.19.2, Vlan168, ASBR, Area 0, SPF 42
    I 192.168.50.14 [2] via 192.168.19.14, Vlan168, ASBR, Area 0, SPF 42
    i 192.168.50.94 [100] via 192.168.50.94, Vlan162, ASBR, Area 0, SPF 42
    i 172.21.1.2 [1] via 192.168.19.16, Vlan168, ASBR, Area 0, SPF 42
    i 10.0.229.2 [1] via 192.168.19.24, Vlan168, ABR/ASBR, Area 0, SPF 42
    i 10.0.17.2 [2] via 192.168.19.2, Vlan168, ABR/ASBR, Area 0, SPF 42
    i 10.0.17.3 [2] via 192.168.19.3, Vlan168, ABR/ASBR, Area 0, SPF 42
    i 192.168.8.1 [1] via 192.168.19.28, Vlan168, ASBR, Area 0, SPF 42
    i 192.168.16.173 [565] via 192.168.19.14, Vlan168, ABR/ASBR, Area 0, SPF 42
    i 192.168.16.173 [565] via 192.168.19.15, Vlan168, ABR/ASBR, Area 0, SPF 42
    i 172.27.193.2 [1] via 192.168.19.20, Vlan168, ASBR, Area 0, SPF 42
    i 172.16.1.2 [1] via 192.168.19.2, Vlan168, ABR/ASBR, Area 0, SPF 42
    i 172.16.1.3 [1] via 192.168.19.3, Vlan168, ABR/ASBR, Area 0, SPF 42

  • OSPF setup problem

    Hello everyone!
    Im trying to configure a simple example of OSPF between three routers (R1, R2, R3),
    which are interconnected via serial ports, using DCE cables.
    Each router is connected to a switch via an Ethernet port.
    Each switch has PCs attached to it.
    Im using Cisco Packet Tracer.
    R1 serial 1/0 interface is connected to R2 serial 1/0, using a network 192.168.10.0/30.
    R1 serial 1/1 interface is connected to R3 serial 1/0, using a network 192.168.10.6/30.
    R2 serial 1/1 interface is connected to R3 serial 1/1, using a network 192.168.10.8/30.
    R1 fa 0/0 interface is connected to switch S1 using 172.16.1.16/28 network, and in the
    meantime I configured this router as a DHCP server (with the network 172.16.1.16/28)
    and the router fa 0/0 as a default gateway with IP address 172.16.1.17/28.
    R2 fa 0/0 interface is connected to switch S2 using 10.10.10.0/24 network, and similarly,
    it is configured as a DHCP server with a default gateway 10.10.10.1/24 (fa0/0 IP).
    R3 fa 0/0 interface is connected to switch S3 using 172.16.1.32/29 network, and again,
    it is configured as a DHCP server with default gateway 172.16.1.33 (fa 0/0 IP).
    The clock rate is configured for R1 interfaces se 1/0 and 1/1 (I tried 64000 and
    other values).
    When I try the show ip ospf neighbor command on each of the routers,
    R2 and R3 can see each other, however they do not recognize R1 as a neighbor.
    Also, R1 cannot see any neighbor at all...
    First I tried to check if the OSPF is set up correctly at each router (the loopback
    interfaces, router IDs, netwok connection types).
    R2's serial interface can ping R1's directly connected serial interface. But it cannot ping
    any other interface of R1.
    Similarly, R3's serial interface can ping only R1's directly connected serial interface.
    But R2 and R3 can ping each other's any interface (serial, fa).
    When I try to ping a PC connected to R1 from any device that is connected to the R2 or
    R3 fa interfaces, I get "Destination host unreachable."
    I checked the default gateway of R1, checked that the fa 0/0 of R1 and the DHCP are
    configured properly.
    What could it be? Am I missing something here with respect to the OSPF configurations?
    But if it was the case, why other routers see each other?
    It seems that the problem comes from R1, whose serial interfaces are the ones who set up
    the clock rate. Could the clock rate be the reason?
    Ping 224.0.0.5 from any of the routers does not show anything.
    Tracert works only for the routers R2 and R3 (from R1 I cannot see any routes)
    For example when I make traceroute from R2 to a serial interface of R2, it works:
    R2#traceroute 192.168.10.6
    Type escape sequence to abort.
    Tracing the route to 192.168.10.6
    1   192.168.10.10   5 msec    5 msec    6 msec
    Also, the ping and traceroute from R1's se 1/1 to R2's se 1/0 for example works too:
    R1#ping 192.168.10.6
    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 192.168.10.6, timeout is 2 seconds:
    Success rate is 100 percent (5/5), round-trip min/avg/max = 4/6/8 ms
    R1#traceroute 192.168.10.6
    Type escape sequence to abort.
    Tracing the route to 192.168.10.6
      1   192.168.10.9    7 msec    7 msec    7 msec   
      2   192.168.10.10   7 msec    5 msec    4 msec
    Thanks a lot for reading all this, and thanks for any suggestions!
    Anna

    duplicate post, try avoiding posting duplicate posts for same problem.
    Regards
    Alain
    Don't forget to rate helpful posts.

  • Problem ospf ip route...

    Hello, i've i little problem with my PT.
    i'm gonna configure ospf on my router (a basic ospf), just to see how ospf work 
    I want all pc communicate !
    But after insert all of network connected to the network, all of my router do not create the ip route 
    password for all equipement : tech
    The networks connected to the Router2 are:
    172.18.0.0 0.0.63.255
    172.18.64.64 0.0.0.63
    172.18.64.128 0.0.0.63
    172.18.64.192 0.0.0.63
    3.0.0.0 0.255.255.255
    192.168.0.0 0.0.0.255
    The network connected to the Router0 are :
    172.16.0.0 0.0.31.255
    172.16.32.0 0.0.31.255
    172.16.64.32 0.0.0.31
    172.16.64.64 0.0.0.31
    172.16.64.96 0.0.0.31
    172.16.64.128 0.0.0.31
    172.16.64.160 0.0.0.31
    2.0.0.0 0.255.255.255
    1.0.0.0 0.255.255.255
    3.0.0.0 0.255.255.255
    192.168.0.0 0.0.0.255
    The network connected to the Router3 are :
    172.17.0.0 0.0.63.255
    172.17.64.64 0.0.0.63
      172.17.64.128 0.0.0.63
    172.17.64.192 0.0.0.63
      2.0.0.0 0.255.255.255
    192.168.0.0 0.0.0.255
    The network connected to the Router 4 are :
    172.19.0.0 0.0.63.255
    172.19.64.64 0.0.0.63
    172.19.64.128 0.0.0.63
    172.19.64.192 0.0.0.63
    1.0.0.0 0.255.255.255
    192.168.0.0 0.0.0.255
    PT in attachment
    Thanks or u help

    Hello,
    omg, work perfectly :D
    So i've another question but it's not about ospf but about the stp (i know i'm on the wan section but, i ask my question anyway :D)
    on my PT, on my switch0, "spanning-tree vlan 1-8 priority 61440" and "spanning-tree vlan 1-8 root primary" with this all of pc port in portfast, it's sufficient for a correct spannin-tree ? (beginner)
    Thanks a lot Kirill !

  • How do I correct the problem of two routers with the same OSPF Router IDs?

    How do I correct the problem of two routers with the same OSPF Router IDs?

    Hi,
    The answer above is correct, though you don't really need to reload, you can just simply clear the OSPF process with the following command:
    clear ip ospf 1 process
    HTH

  • MPLS + OSPF default rote weird problem (cat6509)

    I have two cat6509.
    Switch A is connected to the internet and receive an OSPF default-route.
    Switch A an B is connect trough a MPLS Tunnel with traffic eng..
    When I setup an notebook connected to the Switch B I canno't reach the internet. But If I change in the switch B the default-route learned trough ospf to static one pointing to the lo0 of SwA it works fine.
    And another thing weird.
    If I let the original config, SwB learning the default-route via Tunnel171 OSPF, I can reach the internet from the notebook If I change the SwB to process switch the packets.
    Someone can help?

    Hi,
    this sounds somewhat wierd, I agree. Did you configure "mpls ip default-route" on both 6509? This allows for label switching of the default route.
    It would lso be interesting to get an output from "show mpls ldp discovery", "show mpls forward" and "show ip cef 0.0.0.0 detail" in both cases default through ospf or through static (in case there are any differences).
    Regards, Martin

  • Problem of routing between inside and outside on ASA5505

    I have a ASA5505 with mostly factory default configuration. Its license allows only two vlan interfaces (vlan 1 and vlan 2). The default config has interface vlan 1 as inside (security level 100), and interface vlan 2 as outside (security level 0 and using DHCP).
    I only changed interface vlan 1 to IP 10.10.10.1/24. After I plugged in a few hosts to vlan 1 ports and connect port Ethernet0/0 (default in vlan 2) to a live network, here are a couple of issues I found:
    a) One host I plugged in is a PC, and another host is a WAAS WAE device. Both are in vlan 1 ports. I hard coded their IP to 10.10.10.250 and 10.10.10.101, /24 subnet mask, and gateway of 10.10.10.1. I can ping from the PC to WAE but not from WAE to the PC, although the WAE has 10.10.10.250 in its ARP table. They are in the same vlan and same subnet, how could it be? Here are the ping and WAE ARP table.
    WAE#ping 10.10.10.250
    PING 10.10.10.250 (10.10.10.250) from 10.10.10.101 : 56(84) bytes of data.
    --- 10.10.10.250 ping statistics ---
    5 packets transmitted, 0 packets received, 100% packet loss
    WAE#sh arp
    Protocol Address Flags Hardware Addr Type Interface
    Internet 10.10.10.250 Adj 00:1E:37:84:C9:CE ARPA GigabitEthernet1/0
    Internet 10.10.10.10 Adj 00:14:5E:85:50:01 ARPA GigabitEthernet1/0
    Internet 10.10.10.1 Adj 00:1E:F7:7F:6E:7E ARPA GigabitEthernet1/0
    b) None of the hosts in vlan 1 in 10.10.10.0/24 can ping interface vlan 2 (address in 172.26.18.0/24 obtained via DHCP). But on ASA routing table, it has both 10.10.10.0/24 and 172.26.18.0/24, and also a default route learned via DHCP. Is ASA able to route between vlan 1 and vlan 2? (inside and outside). Any changes I can try?
    Here are ASA routing table and config of vlan 1 and vlan 2 (mostly its default).
    ASA# sh route
    Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
    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 - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
    * - candidate default, U - per-user static route, o - ODR
    P - periodic downloaded static route
    Gateway of last resort is 172.26.18.1 to network 0.0.0.0
    C 172.26.18.0 255.255.255.0 is directly connected, outside
    C 127.1.0.0 255.255.0.0 is directly connected, _internal_loopback
    C 10.10.10.0 255.255.255.0 is directly connected, inside
    d* 0.0.0.0 0.0.0.0 [1/0] via 172.26.18.1, outside
    interface Vlan1
    nameif inside
    security-level 100
    ip address 10.10.10.1 255.255.255.0
    interface Vlan2
    nameif outside
    security-level 0
    ip address dhcp setroute
    interface Ethernet0/0
    switchport access vlan 2
    All other ports are in vlan 1 by default.

    I should have made the config easier to read. So here is what's on the ASA and the problems I have. The ASA only allows two VLAN interfaces configured (default to Int VLAN 1 - nameif inside, and Int VLAN 2 - nameif outside)
    port 0: in VLAN 2 (outside). DHCP configured. VLAN 2 pulled IP in 172.26.18.0/24, default gateway 172.26.18.1
    port 1-7: in VLAN 1 (inside). VLAN 1 IP is 10.10.10.1. I set all devices IP in VLAN 1 to 10.10.10.0/24, default gateway 10.10.10.1
    I have one PC in port 1 and one WAE device in port 2. PC IP set to 10.10.10.250 and WAE set to 10.10.10.101. PC can ping WAE but WAE can't ping PC. Both can ping default gateway.
    If I can't ping from inside interface to outside interface on ASA, how can I verify inside hosts can get to outside addresses and vise versa? I looked at ASA docs, but didn't find out how to set the routing between inside and outside. They are both connected interfaces, should they route between each other already?
    Thanks a lot

  • Problem with FWSM and L3 interface in same switch

    I have two 6513s with an 802.1q trunk connecting them. Each switch has redundant Sup720s running in Native mode, IOS ver 12.2(18)SXF (they were initially running SXD3). A FWSM (ver 2.3(3), routed mode, single context) is in each switch, setup in failover mode.
    I can not get a PC, in a vlan that has the layer 3 interface defined on the switch with the active FWSM in it, to communicate with devices "behind" the FWSM. If I move the layer 3 configuration for that vlan to the other 6513, everything works fine.
    The MSFCs are on the inside of the firewall, they have a layer 3 interface configured in the same vlan as the FWSM "inside" interface. Several "same security level" interfaces are defined on the FWSM and used to protect server farms. I am using OSPF on the MSFCs and FWSM and the routing table is correct.
    The FWSM builds connections for attempts made by the PC with the layer 3 interface defined on the same switch as the active FWSM just fine, so this is not a FWSM ACL problem.
    A ping of the FWSM "inside" interface from a PC with the layer 3 interface defined on the same switch as the active FWSM fails, even though debug icmp trace on the FWSM shows the request and the response. A packet capture, using the NAM-2, shows only the request packets. I have captured on the common vlan and the FWSM backplane port channel interface.
    Just to add to the confusion, if I capture in the same places, but do the ping from a PC that is in a vlan with the layer 3 interface defined in the 6513 that does not contain the active FWSM, which works fine, I see the request and reply on the common vlan capture, but only the request on the port channel capture.
    This problem has been there from the beginning of this implementation and has not changed with IOS and FWSM software upgrades. I have experienced this with any and all vlans that I tried to define the layer 3 interface for on the switch with the active FWSM. I have MLS turned on.
    If anyone else has experienced this and solved it, or knows what is going on, I would appreciate any insight.
    Thanks.
    Keith

    I will have to get setup to record more data, but I do know the FWSM showed a ping request and a ping reply at the "inside" interface.
    I believe my problem is related to the IOS command "firewall multiple-vlan-interfaces" which I put in place to allow IPX traffic to be brought around the FWSM. The little documentation that there is for this command, states that policy routing may need to be implemented to prevent ip packets from going around the firewall. I do not have any policy routing in place.
    I also do not have any active layer three interfaces defined for any of the vlans assigned to the firewall except the "inside" interface. So my resoning was that I did not need to be concerned about ip packets having a way around the FWSM. My suspicion is that this command and the fact that I have mls on is causing some type of a problem which results in the packet being "lost" when it needs to be going through the MSFC in the switch with the active FWSM to get to the PC. Hopefully that makes some sense.
    Do you have any idea where better documention on using the "firewall multiple-vlan-interfaces" may be, or a better explanation of all that is happening inside the switch when that command is used?
    Thanks.

Maybe you are looking for

  • ISA credit memos and down payment does not display data  R/3 E-commerce 5.0

    Dear guru's The Billing doc search in the ISA searches Credit Memos and down payments. However, system don´t found documents, but business partner have credit memos and down payments. Some idea?

  • Does 2 firewire audio and video interface can work together  on FCP ?

    hello, My audio interface is a TC Electronic Konnekt 24D my video interface is a Canopus ADVC 110 my hard drives are plugged in firewire too and I use Final Cut Pro 5.0.4 So, the konnekt is recognized by FCP only when the Canopus is not plugged. And

  • How can I transfer a Playlist to my mp3 player?

    i have a cheap little mp3 player (Jensen), and i want to transfer an iTunes playlist (all my iTunes songs are already in mp3 format, btw) to the player. however, i can't click and drag a playlist to the mp3 player directly. the mp3 player instruction

  • HOW DO I REDUCE QT FILE SIZE

    OK, l'm certainly a lost newbie on this one! I want to reduce a short QT.dv movie, about 816mb, to a smaller window size (320 x240) using much less memory. Is for example MPEG1 ("muxed") the answer? If so, how do I do that? Or any other suggestions..

  • Going through all the nodes children (JTree)

    Hello all, I'm detecting clicks on a JTree, and I want a method that goes from that node to the end of the tree (all the leaves). The method will be invoked if the node has children of course, I want to do this recursively but I don't know how. Can a