Show ip ospf e

Anyone know what this command does or where it is docuemnted.
Accidently typed it in. It is a non enabled command that appears to display some type of debugging information. If I had to guess it is ospf events but I cannot find anything to confirm that

I had the same experience as you long time ago. here they are. In my opinion, it's kinds of hidden command for highest debbuging command which should not show users.
switch#sh ip ospf e
1 10388 Generic: ospf_build_rtr_lsa 0x0
2 10888 Elect DR: GigabitEthernet0/2 10.0.0.1
3 10888 Elect BDR: GigabitEthernet0/2 10.0.0.2
4 10888 i/f state nbr chg: GigabitEthernet0/2 0x5
5 20488 Generic: ex_delete_old_routes 0x7

Similar Messages

OSPF link update-Basic Query

I am new to OSPF. I have 2 basic querys on OSPF link update.
1. How does one router communicates with every router in the OSPF area. Is it that each router communicates only with its directly connected neighbours? example.
ROUTERA-------ROUTERB-----ROUTERC-----ROUTERD----ROUTERE
Lets say link on RouterB connected to ROUTERA goes down. How does "ROUTERE" get to know about this? Is the communication is from RouterB to ROUTERC then to ROUTERD and then to ROUTERE?
2. How does router handle(forward) multicast packets?
Thanks

Hello Avil,
the way OSPF communicates depends on how your network is set up. In your case, it looks like all routers are connected back-to-back with point-to-point links. OSPF uses the concept of adjacencies: an OSPF router has an adjacency with a connected router, which means that they have the exact same view of the entire network. If you do a 'show ip ospf neighbor' on your RouterA and your RouterE, it tells you the adjacencies these routers have with other connected routers. Now let's say the link between RouterA and RouterB goes down. RouterC notifies RouterD, and RouterD notifies RouterE immediately by exchanging link-state packets.
Keep in mind that on a multiaccess segment (where multiple OSPF routers are directly connected on the same segment), the concept of DR (Designated Router) and BDR (Backup Designated Router) comes into play: on a multiaccess segment, a DR and a BDR are elected, and all other routers have full adjacencies only with the DR and the BDR.
Regarding the multicast traffic: it is handled just as unicast traffic (unless you specifically block it).
Does that make sense ? If you are just starting with OSPF, have a look at the link below, which contains a pretty good introduction of the basic concepts.
OSPF Design Guide
http://www.cisco.com/warp/public/104/2.html#4.0
HTH,
GNT

#sh ip ospf route Command

Hi All,
Kinldy let me know that #sh ip ospf route, which IOS Version support this command...
Regards
Indrapal

Hi Indrapal,
as far as I remember, 'show ip ospf route' is the unsupported version of the 'show ip ospf rib' command, which was introduced with the (Link:) OSPFv2 Local RIB feature in 12.4(15)T.
Perhaps somebody could confirm.
HTH
Rolf

Ospf selection

Hi Experts.
i have some confusion in ospf path selection process. I have a core switch which connects to two router(RA&RB) these are running ospf. Core switch is receving E2 routes for x.x.x.x/24 from both routers. How is it possible to make one router say RA as primary & RB as secondary. I can not manipulate this routes other than E2 so in this case path cost is going to work??
Pls help me here.

Hi,
the main characteristic of E2 routes is that the external part of the metric takes precedence over the internal part.
That means, the cost of the Type-5 LSA's 'metric' fields are always evaluated first, the LSA with the lower cost will be installed in the routing table, regardless of the internal cost, which is the cost of the path to the border router [1].
If, like in your case, the costs of the LSAs are equal, the paths to the ASBRs (in terms of costs) [1] are evaluated. The lower-cost path wins; in case of equality both routes are installed (ECLB).
You can see the two parts of the metric with a "show ip route <prefix>":
R1#show ip route 169.254.0.0
Routing entry for 169.254.0.0/16
Known via "ospf 1", distance 110, metric 20, type extern 2, forward metric 100
R1#show ip ospf border-routers
i 2.2.2.2 [100] via 172.16.12.2, Serial0/0, ASBR, Area 0, SPF 9
i 3.3.3.3 [64] via 172.16.13.3, Serial0/1, ASBR, Area 0, SPF 9
This route has been installed although there is a "cheaper" ASBR, but it obviously injects the LSA for this prefix with a metric greater than 20:
R1#show ip ospf database external 169.254.0.0
LS Type: AS External Link
Link State ID: 169.254.0.0 (External Network Number )
Advertising Router: 3.3.3.3
Network Mask: /16
        Metric Type: 2 (Larger than any link state path)
        TOS: 0
        Metric: 30
So yes, you can achieve a primary/secondary path when both LSAs have the same metrics by changing a interface's cost, but remember that this may affect the whole topology.
HTH
Rolf
EDIT:
[1]: More precisely it's the path to the 'forwarding address', which is another field of external LSAs and used to avoid unnecessary extra-hops. If the FA is 0.0.0.0, the path to the advertising ASBR is used instead.

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 run with TE

i want to know do we get the tunnel update in ospf
shivlu

OSPF use type10 opaque area to carry tunnel information:
show ip ospf database opaque-area

Process show commands with EEM

Hi all,
Im newbie in EEM, but using it in on of my projects in a basic style:
syslog or ip sla tracking events
set actions and some basics if/else...
I dont know how I lived without EEM, its awesome.
I need to do some advanced inspection of show commands output, like taking some strings from "show ip route", "show ip ospf" and so on, compare them and do some actions based on result.
Can anyone show me some simple example, with filtering IP address of the DR from "show ip ospf neighbor", comparing it with router-id from the "show ip ospf interface" and make some action based on the result. It would be very useful for me.
Also documentation for beginners would be appreceated.
Best regards,
Aleksei

Sorry, I missed this one originally. There are a lot of examples in this community that talk about parsing show command output. I don't know of any OSPF-specific ones off the top of my head, but look at examples like:
https://supportforums.cisco.com/thread/2238284?tstart=0
https://supportforums.cisco.com/thread/2241567?tstart=0
You'll need to come up with regular expressions that match what you want from the output of the OSPF commands. I don't have OSPF output handy to show any relevant examples, but hopefully the two I mentioned will be of some help.

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.

RIP redistribution in to OSPF breaks when 1OSPF path goes down

Hi All,
I'm failing to understand why the RIP redistribution is breaking when I shutdown interface 0/0 on the mpls-usa router (mpls is just a naming convention). When 0/0 is up RIP is redistributed by when it is down I get nothing. See diagram below:
The topology:
Show ip route on mpls-2 and mpls-3 when interface 0/0 is down on mpls-usa
show ip route on mpls-2 and mpls-3 with eth 0/0 down
And this is my config on MPLS-USA

Hi,
First of all , please mention interfaces in your topology. Second in all routing table snapshot you cut the router hostname that also creates confusion.
Now in the last output, i am not sure that output is from MPLS-2 or MPLS-3 and where E0/1 is connected to. Regarding your question related to number of routes, i guess you would have only one route in routing table because in OSPF external routes other than route metric, metric to ASBR also comes in to picture.
When you shut one interface, route should not get disappeared. You can shut interface between MPLS-2 and MPLS-USA and share ospf lsa database output from MPLS-USA and MPLS-3. Also "show ip ospf nei" on MPLS-USA router.

Question about OSPF to BGP redistribution

I have some static routes on a router where OSPF and BGP are also running. I have redistributed the static routes into OSPF (showing in OSPF database). I also want to have the static routes into the BGP routing table. Understand this can be done by using a prefix list permiting all the static routes, however I was thinking a simpler way just redistributing whatever is in the OSPF routing tabel into BGP (permit 0.0.0.0/0 le 32).
My question is if OSPF really redistributes those routes. Those routes are shown as "static" in "sh ip route" even though they are also in OSPF database. I have heard that OSPF only redistributes the routes showing as "OSPF routes", not what's in its database.
Thanks for any help.
Gary

Hi Gary,
The thing to understand here is that the use of redistribution does not change anything in the routing table of the router on which you are configuring it.
As you have observed, static routes do not become OSPF routes when you redistribute them into OSPF. This can be generalised to the following: when you redistribute protoclol1 into protocol2, the router will scan the routing table for routes installed by protocol1 and will then do one of the following, depending on the protocol it is being redistributed into:
- if it is a Link state protocol like OSPF, it will originate LSAs appropriate to the route being redistributed. These LSAs will be subsequently flooded to other routers which will install them as routes in their routing table. The only change on the redistributing router is the installation of additional LSAs; the routing table does not change
- if it is a distance vector protocol like IGRP, the router will take the protocol1 routes and advertise them via IGRP update packets every time an update packet is sent. Once again, there is no change on the routing table of the redistributing router.
Note the other important point: when redistributing is carried out, the only routes that are redistributed are those that are in the routing table and installed there by the source protocol, which could be quite different to the contents of link-state databases.
Hope that helps.
Pls remember to rate posts.
Paresh.

Expecting 2 OSPF Type 5 LSA's but only seeing one?

Hi all,
we are dual homing with another AS and we have BGP routes being redistributed in to OSPF...
am I right in thinking that when looking at the type 5 LSA's for a particular prefix, I should see two of them? One type 5 LSA from each ASBR? How can I confirm that OSPF knows about the backup route for a particular prefix?
thanks
Mario

Hi Peter,
from the routing table for prefix 10.0.0.0/14 we get this...
TH_DC_core_01#show ip route 10.4.0.0
Routing entry for 10.4.0.0/14
Known via "ospf 200", distance 110, metric 100000
Tag 5151, type extern 2, forward metric 105
Redistributing via eigrp 208
Last update from 10.129.1.6 on Vlan98, 01:09:03 ago
Routing Descriptor Blocks:
* 10.129.1.6, from 10.129.0.236, 01:09:03 ago, via Vlan98
      Route metric is 100000, traffic share count is 1
      Route tag 5151
TH_DC_core_01#
when looking at the OSPF DB, we get this...
Routing Bit Set on this LSA
LS age: 1968
Options: (No TOS-capability, DC)
LS Type: AS External Link
Link State ID: 10.4.0.0 (External Network Number )
Advertising Router: 10.129.0.236
LS Seq Number: 80000079
Checksum: 0xA53
Length: 36
Network Mask: /14
        Metric Type: 2 (Larger than any link state path)
        TOS: 0
        Metric: 100000
        Forward Address: 0.0.0.0
        External Route Tag: 5151
When i look to see about any type 5 LSA's being advertised by the backup router i see nothing!
TH_DC_core_01#show ip ospf database external adv-router 10.131.0.246
            OSPF Router with ID (10.129.0.252) (Process ID 200)
            OSPF Router with ID (192.168.223.41) (Process ID 700)
            OSPF Router with ID (192.168.0.252) (Process ID 800)
This is telling me that a) either the LSA's are being flushed (as you said) or b) the secondary router is not redistributing for some reason.
Any more advice on this would be very much appreciated.
thanks
Mario

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

FlexVPN and OSPF issue

I have an issue with OSPF rountig on routers configured in hub and spoke topology.
An issue is on a routes which OSPF do not advertise from hub to spokes.
Subnets created on a hub router are not seen on spokes but new added subnet on spoke is seen in hub routing table.
Adding ip ospf network brodcast command on a hub virtual-template interface causes OSPF adjacency to down.
By the way, EIGRP works fine.
Has anyone encountered this issue with OSPF.
Please, look short config below;
-----------------------HUB-------------------------------
crypto ikev2 authorization policy default
route set interface
crypto ikev2 proposal ikev2_prop
encryption aes-cbc-256
integrity sha512
group 16
crypto ikev2 policy ikev2_policy
proposal ikev2_prop
crypto ikev2 keyring Flex_key
peer Spokes
address 192.168.50.197
pre-shared-key local 12345
pre-shared-key remote 12345
peer RTB
address 192.168.50.199
pre-shared-key local 12345
pre-shared-key remote 12345
crypto ikev2 profile Flex_IKEv2
match identity remote address 192.168.50.197 255.255.255.255
match identity remote address 192.168.50.199 255.255.255.255
authentication remote pre-share
authentication local pre-share
keyring local Flex_key
virtual-template 1
no crypto isakmp default policy
crypto ipsec transform-set ipsec_trans esp-aes 256 esp-sha512-hmac
mode tunnel
crypto ipsec profile default
set transform-set ipsec_trans
set ikev2-profile Flex_IKEv2
interface Loopback1
ip address 172.16.10.1 255.255.255.0
ip ospf 10 area 0
interface Loopback10
ip address 10.1.1.1 255.255.255.0
ip ospf 10 area 0
interface Loopback50
ip address 50.1.1.1 255.255.255.0
ip ospf 10 area 50
interface Embedded-Service-Engine0/0
no ip address
interface GigabitEthernet0/1
bandwidth 100000
ip address 192.168.50.198 255.255.255.0
duplex auto
speed auto
interface Virtual-Template1 type tunnel
ip unnumbered Loopback1
ip mtu 1400
ip tcp adjust-mss 1360
tunnel source GigabitEthernet0/1
tunnel mode ipsec ipv4
tunnel path-mtu-discovery
tunnel protection ipsec profile default
router ospf 10
redistribute connected subnets
network 10.1.1.0 0.0.0.255 area 0
sh cryp ike sa
IPv4 Crypto IKEv2 SA
Tunnel-id Local                 Remote                fvrf/ivrf            Status
1         192.168.50.198/500    192.168.50.197/500    none/none            READY
      Encr: AES-CBC, keysize: 256, Hash: SHA512, DH Grp:16, Auth sign: PSK, Auth verify: PSK
      Life/Active Time: 86400/77565 sec
Tunnel-id Local                 Remote                fvrf/ivrf            Status
2         192.168.50.198/500    192.168.50.199/500    none/none            READY
      Encr: AES-CBC, keysize: 256, Hash: SHA512, DH Grp:16, Auth sign: PSK, Auth verify: PSK
      Life/Active Time: 86400/77542 sec
IPv6 Crypto IKEv2 SA
sh ip rou
S*    0.0.0.0/0 [1/0] via 192.168.50.1
      10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C        10.1.1.0/24 is directly connected, Loopback10
L        10.1.1.1/32 is directly connected, Loopback10
      50.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C        50.1.1.0/24 is directly connected, Loopback50
L        50.1.1.1/32 is directly connected, Loopback50
      100.0.0.0/32 is subnetted, 1 subnets
O IA     100.1.1.1 [110/2] via 172.16.10.254, 21:32:58, Virtual-Access1
      172.16.0.0/16 is variably subnetted, 2 subnets, 2 masks
C        172.16.10.0/24 is directly connected, Loopback1
L        172.16.10.1/32 is directly connected, Loopback1
      192.168.50.0/24 is variably subnetted, 2 subnets, 2 masks
C        192.168.50.0/24 is directly connected, GigabitEthernet0/1
L        192.168.50.198/32 is directly connected, GigabitEthernet0/1
      200.1.1.0/32 is subnetted, 1 subnets
O IA     200.1.1.1 [110/2] via 172.16.10.253, 21:32:38, Virtual-Access2
      201.1.1.0/32 is subnetted, 1 subnets
O IA     201.1.1.1 [110/2] via 172.16.10.253, 21:32:38, Virtual-Access2
      220.1.1.0/32 is subnetted, 1 subnets
O IA     220.1.1.1 [110/2] via 172.16.10.253, 00:06:11, Virtual-Access2
---------------------------SPOKE---------------------------------------------
crypto ikev2 proposal ikev2_prop
encryption aes-cbc-256
integrity sha512
group 16
crypto ikev2 policy ikev2_policy
proposal ikev2_prop
crypto ikev2 keyring Flex_key
peer Spokes
address 192.168.50.198
pre-shared-key local 12345
pre-shared-key remote 12345
crypto ikev2 profile Flex_IKEv2
match identity remote address 192.168.50.198 255.255.255.0
authentication remote pre-share
authentication local pre-share
keyring local Flex_key
virtual-template 1
no crypto isakmp default policy
crypto ipsec transform-set ipsec_trans esp-aes 256 esp-sha512-hmac
mode tunnel
crypto ipsec profile default
set transform-set ipsec_trans
set ikev2-profile Flex_IKEv2
interface Loopback200
ip address 200.1.1.1 255.255.255.0
ip ospf 10 area 200
interface Loopback201
ip address 201.1.1.1 255.255.255.0
ip ospf 10 area 201
interface Loopback220
ip address 220.1.1.1 255.255.255.0
ip ospf 10 area 220
interface Tunnel1
ip address 172.16.10.253 255.255.255.0
ip mtu 1400
ip tcp adjust-mss 1360
tunnel source GigabitEthernet0/1
tunnel mode ipsec ipv4
tunnel destination 192.168.50.198
tunnel path-mtu-discovery
tunnel protection ipsec profile default shared
interface GigabitEthernet0/1
ip address 192.168.50.199 255.255.255.0
duplex auto
speed auto
router ospf 10
network 172.16.10.0 0.0.0.255 area 0
sh cryp ike sa
IPv4 Crypto IKEv2 SA
Tunnel-id Local                 Remote                fvrf/ivrf            Status
1         192.168.50.199/500    192.168.50.198/500    none/none            READY
      Encr: AES-CBC, keysize: 256, Hash: SHA512, DH Grp:16, Auth sign: PSK, Auth verify: PSK
      Life/Active Time: 86400/77852 sec
IPv6 Crypto IKEv2 SA
sh ip route
S*    0.0.0.0/0 [1/0] via 192.168.50.1
      172.16.0.0/16 is variably subnetted, 2 subnets, 2 masks
C        172.16.10.0/24 is directly connected, Tunnel1
L        172.16.10.253/32 is directly connected, Tunnel1
      192.168.50.0/24 is variably subnetted, 2 subnets, 2 masks
C        192.168.50.0/24 is directly connected, GigabitEthernet0/1
L        192.168.50.199/32 is directly connected, GigabitEthernet0/1
      200.1.1.0/24 is variably subnetted, 2 subnets, 2 masks
C        200.1.1.0/24 is directly connected, Loopback200
L        200.1.1.1/32 is directly connected, Loopback200
      201.1.1.0/24 is variably subnetted, 2 subnets, 2 masks
C        201.1.1.0/24 is directly connected, Loopback201
L        201.1.1.1/32 is directly connected, Loopback201
      220.1.1.0/24 is variably subnetted, 2 subnets, 2 masks
C        220.1.1.0/24 is directly connected, Loopback220
L        220.1.1.1/32 is directly connected, Loopback220
sh ip ospf database ro 172.16.10.1
            OSPF Router with ID (200.1.1.1) (Process ID 10)
                Router Link States (Area 0)
Adv Router is not-reachable in topology Base with MTID 0
LS age: 336
Options: (No TOS-capability, DC)
LS Type: Router Links
Link State ID: 172.16.10.1
Advertising Router: 172.16.10.1
LS Seq Number: 80000065
Checksum: 0x4B6E
Length: 60
Area Border Router
AS Boundary Router
Number of Links: 3
    Link connected to: a Stub Network
     (Link ID) Network/subnet number: 10.1.1.1
     (Link Data) Network Mask: 255.255.255.255
      Number of MTID metrics: 0
       TOS 0 Metrics: 1
    Link connected to: another Router (point-to-point)
     (Link ID) Neighboring Router ID: 100.1.1.1
     (Link Data) Router Interface address: 0.0.0.18
      Number of MTID metrics: 0
       TOS 0 Metrics: 1
    Link connected to: another Router (point-to-point)
     (Link ID) Neighboring Router ID: 200.1.1.1
     (Link Data) Router Interface address: 0.0.0.17
      Number of MTID metrics: 0
       TOS 0 Metrics: 1

I checked it out in the lab, at least the generic OSPF setup.
A few comments - do not "redistribute connected" not all of them - you can introduce recursive routing (i.e. introduce tunnel endpoint through the tunnel).
Spoke2#show ip ospf interface tu1Tunnel1 is up, line protocol is up Internet Address 10.1.1.177/32, Area 0, Attached via Network Statement Process ID 65001, Router ID 192.168.102.1, Network Type POINT_TO_POINT, Cost: 1000 Topology-MTID    Cost    Disabled    Shutdown      Topology Name        0           1000      no          no            Base Transmit Delay is 1 sec, State POINT_TO_POINT Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5    oob-resync timeout 40    Hello due in 00:00:03 Supports Link-local Signaling (LLS) Cisco NSF helper support enabled IETF NSF helper support enabled Index 1/1, flood queue length 0 Next 0x0(0)/0x0(0) Last flood scan length is 1, maximum is 1 Last flood scan time is 0 msec, maximum is 0 msec Neighbor Count is 1, Adjacent neighbor count is 1     Adjacent with neighbor 172.25.1.1 Suppress hello for 0 neighbor(s)Spoke2#show ip route ospf(...)Gateway of last resort is 172.16.2.1 to network 0.0.0.0      10.0.0.0/32 is subnetted, 3 subnetsO        10.1.1.176 [110/3000] via 10.1.1.1, 00:01:38, Tunnel1O IA 192.168.0.0/24 [110/1010] via 10.1.1.1, 00:01:21, Tunnel1Hub#sh run | s r orouter ospf 65001 network 10.1.1.0 0.0.0.255 area 0 network 192.168.0.0 0.0.0.255 area 10
then I added
route-map CONNECTED_TO_OSPF, permit, sequence 10 Match clauses:    interface Loopback999 Set clauses: Policy routing matches: 0 packets, 0 bytesHub#sh run | s r orouter ospf 65001 redistribute connected subnets route-map CONNECTED_TO_OSPF network 10.1.1.0 0.0.0.255 area 0 network 192.168.0.0 0.0.0.255 area 10
And checked on Spoke
Spoke1#show ip route ospf(...)Gateway of last resort is 172.16.1.1 to network 0.0.0.0      10.0.0.0/8 is variably subnetted, 4 subnets, 2 masksO        10.1.1.177/32 [110/3000] via 10.1.1.1, 00:05:06, Tunnel1O E2     10.255.255.0/24 [110/20] via 10.1.1.1, 00:00:04, Tunnel1O IA 192.168.0.0/24 [110/1010] via 10.1.1.1, 00:04:49, Tunnel1
Final note "shared" is not needed on point to point interfaces.

Distribute List Nexus 7000 / OSPF

I was trying to limit the routes that our ospf should learn, same on 6500 as "distribute-list".
It´s on a VRF.
on http://docwiki.cisco.com/wiki/Cisco_NX-OS/IOS_OSPF_Comparison it says that it isn´t possible.
Any ideas? Is it true? Should I use just redistribute list?
Thanks

########UPDATE########
Since version 6.x Cisco added a feature called table-map.
It works like distributed lists and did what I needed. We are using it already. Info at link above:
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/6_x/nx-os/unicast/configuration/guide/l3_cli_nxos/l3_ospf.html#pgfId-1361896
Maybe it helps.
So to make configuration...
1) I need to make a prefix-list
ip prefix-list Filter_List_in seq 10 permit 10.20.30.40/32
ip prefix-list Filter_List_in seq 20 permit 10.30.20.26/32
ip prefix-list Filter_List_in seq 30 permit 10.40.30.20/32
2) Make a route map and use prefix-list.
route-map Permit_in permit 10
match ip address prefix-list Filter_List_in
3) And apply on ospf (show run).
router ospf 10
vrf VRFOSPF
    router-id 10.0.0.21
    network 10.20.208.21/32 area 0.0.0.0
    redistribute static route-map RM_static
    area 0.0.0.0 authentication message-digest
    area 0.0.0.0 filter-list route-map Permit_in in
    log-adjacency-changesrouter ospf 10
And clear neighbors. (IPs were changed)
When I use the show ip ospf policy... filter in... => no match
route-map Permit_in permit 10
match ip address prefix-list Filter_List_in        C: 0      M: 0
Total accept count for policy: 0
Total reject count for policy: 0
I couldn´t figure why it isnt working.
I also tried to apply the filter list going to (config t --> vrf context VRFOSPF --> router ospf 10 --> and apply the filter list).
Any Ideas?
Edited:
"To filter prefixes advertised in type 3 link-state advertisements (LSAs) between Open Shortest Path First (OSPF) areas of an Area Border Router (ABR),"
"The NX-OS does support inter-area Type-3 LSA/route filtering using the filter-list command configured under the OSPF routing instance."
We will create a ABR on nexus to apply filter-list
Thanks for help.

OSPF - Master/Slave - DR/BDR Election

Routers on the same ethernet segment - during bootup (if running OSPF) does the Master/Slave part happen after the DR/BDR are elected?
Also - If I brought up a new router into that segment (while the other routers are already on and converged) does the master/slave process happen still between this router and the others? I have read a few articles, including the OSPF section in the routing tcp/ip book, but still a bit confused as to when the master/slave happens in relation to the dr/bdr election.
Thanks

Hi,
Yes dr/bdr can also become slave. Election is based on ip address and node with higher ip address becomes Master
ExStart.
In this state, the router and its neighbor establish a master/slave relationship and determine the initial DD sequence number in preparation for the exchange of Database Description packets. The neighbor with the highest interface address becomes the master.
Please see debug outputs below. there is ospf neighborship between R1 (9.0.0.1) and R2(9.0.0.2). Have configured "ip ospf priority 0" on R2 so that it can not become DR/BDR. But still since this router is having higher ip address, it became Master and R1 became Slave.
R2_7606B#show ip ospf nei
Neighbor ID Pri State Dead Time Address Interface
9.0.0.1 1 FULL/DR 00:00:34 9.9.12.1 GigabitEthernet1/17
Aug 29 07:00:07.673: OSPF: 2 Way Communication to 9.0.0.1 on GigabitEthernet1/17, state 2WAY
Aug 29 07:00:07.673: OSPF: Backup seen Event before WAIT timer on GigabitEthernet1/17
Aug 29 07:00:07.673: OSPF: DR/BDR election on GigabitEthernet1/17
Aug 29 07:00:07.673: OSPF: Elect BDR 0.0.0.0
Aug 29 07:00:07.673: OSPF: Elect DR 9.0.0.1
Aug 29 07:00:07.673: DR: 9.0.0.1 (Id) BDR: none
Aug 29 07:00:07.673: OSPF: GigabitEthernet1/17 Nbr 9.0.0.1: Prepare dbase exchange
Aug 29 07:00:07.673: OSPF: Send DBD to 9.0.0.1 on GigabitEthernet1/17 seq 0x2C8 opt 0x52 flag 0x7 len 32
Aug 29 07:00:07.673: OSPF: Rcv DBD from 9.0.0.1 on GigabitEthernet1/17 seq 0xD62 opt 0x52 flag 0x7 len 32 mtu 1500 state EXSTART
Aug 29 07:00:07.673: OSPF: First DBD and we are not SLAVE
Aug 29 07:00:07.673: OSPF: Rcv DBD from 9.0.0.1 on GigabitEthernet1/17 seq 0x2C8 opt 0x52 flag 0x2 len 272 mtu 1500 state EXSTART
Aug 29 07:00:07.673: OSPF: NBR Negotiation Done. We are the MASTER
Aug 29 07:00:07.673: OSPF: GigabitEthernet1/17 Nbr 9.0.0.1: Summary list built, size 12
Aug 29 07:00:07.673: OSPF: Send DBD to 9.0.0.1 on GigabitEthernet1/17 seq 0x2C9 opt 0x52 flag 0x1 len 272
Aug 29 07:00:07.701: OSPF: Rcv DBD from 9.0.0.1 on GigabitEthernet1/17 seq 0x2C9 opt 0x52 flag 0x0 len 32 mtu 1500 state EXCHANGE
Aug 29 07:00:07.701: OSPF: Exchange Done with 9.0.0.1 on GigabitEthernet1/17
Aug 29 07:00:07.701: OSPF: Synchronized with 9.0.0.1 on GigabitEthernet1/17, state FULL
Aug 29 07:00:07.701: %OSPF-5-ADJCHG: Process 100, Nbr 9.0.0.1 on GigabitEthernet1/17 from LOADING to FULL, Loading Done
Aug 29 07:00:07.701: OSPF: Register neighbor 9.9.12.1 on interface GigabitEthernet1/17 with BFD
Aug 29 07:00:07.701: OSPF: GigabitEthernet1/17 Nbr 9.0.0.1: Clean-up dbase exchange
Aug 29 07:00:08.173: OSPF: Build router LSA for area 0, router ID 9.0.0.2, seq 0x80000552, process 100
Aug 29 07:00:08.477: OSPF: BFD Up event intf GigabitEthernet1/17 nbr 9.9.12.1
Aug 29 07:01:34.230: OSPF: We are not DR to build Net LSA for interface GigabitEthernet1/17
Aug 29 07:01:34.230: OSPF: Build network LSA for GigabitEthernet1/17, router ID 9.0.0.2
--Pls dont forget to rate helpful posts--
-Akash

Show ip ospf e

Similar Messages

Maybe you are looking for