OSPF Transit Capability

OK, a new feature introduced in OSPFv2 and back to RFC 2328 section 16.3 is the following:

16.3.  Examining transit areas' summary-LSAs

This step is only performed by area border routers attached to one or more non-backbone areas that are capable of carrying

transit traffic (i.e., "transit areas", or those areas whose

TransitCapability parameter has been set to TRUE in Step 2 of

the Dijkstra algorithm (see Section 16.1).

The purpose of the calculation below is to examine the transit

areas to see whether they provide any better (shorter) paths

than the paths previously calculated in Sections 16.1 and 16.2.

Any paths found that are better than or equal to previously

discovered paths are installed in the routing table.

The calculation also determines the actual next hop(s) for those

destinations whose next hop was calculated as a virtual link in

Sections 16.1 and 16.2.  After completion of the calculation

below, any paths calculated in Sections 16.1 and 16.2 that still

have unresolved virtual next hops should be discarded.

so what does it mean in Plain English?!!

OSPF Neighbors at Different Subnets!!

Yesterday we had many challenges at facebook Group about different Cisco IGPs Cases , and one them was about configuring OSPF neighbors but in different subnets, so the only Case i Knew According to RFC2328 was Point-to-Point connection using ip unnumbered and virtual links, that's always works fine .

But what about multi-access interfaces e.g: fastethernet ?!! That was a bit confusing at the beginning but i had to go for a workaround solution which PPPOE + ip unnumbered which worked like a magic :D

So As usual we will use our simple Topology with two routers with R1 as PPPOE server and R2 as PPPOE Client:
R1 ==> fa0/0 ==> IP address should be 10.10.10.1/24
R2 ==> fa0/0 ==> IP address should be 20.20.20.20/24

So I will move These IPs to Loopback 0 in Both Routers and We will Start from There.

R1 (PPPOE Server):

EIGRP "Named Mode" First Thoughts!!

When I started to read about this new operational mode for Cisco which is called EIGRP Mode, I keep telling my self what is the point here Cisco, i don't see any benefits but typing more commands!, but bear with me :)

According to Cisco this mode is available on 15.0(1)M - 12.2(33)SRE - 12.2(33)XNE - Cisco IOS XE Release 2.5 which is pretty new one.

Cisco now called our old EIGRP configuration "Classic Mode" which we used to type AS number, now by this new configuration we won't type AS Number but instead we are going to type "Virtual-Instance Name"!,
Cisco aims by this new config to get what is called "Unified Configuration Solution" to provide ONE place to configure all of EIGRP and to provide ONE common way to define a feature , so let's take a look at our usual Basic topology and I am going to configure R1 with the old Classic Mode and R2 with the new Config Named Mode just to show how differences are but with the same overall final result.

EIGRP AS go figure!

I know it has been a lot of time since i blogged but here I'm again :)

Have you ever faced a situation that you want to peer with a router using EIGRP and you can't even touch or telnet to that device, well you 're gonna tell me so where is the catch here ?!! go with your normal config and in your lovely config mode and type (config)#router eigrp AS-Number and you should be good to go!

and here is the catch you didn't get it, I don't know The EIGRP AS dude!!!!!!!
so again to keep our case pretty simple i will just use two router with their loopbacks, so nothing fancy here: