Categories

Posts Tagged ‘cisco router’

The OSPF RID | CCNA Exam Tutorial Series

freeware download promo code

OSPF is a major topic on your CCNA exam, as well it should be. OSPF is a widely-used WAN protocol, and you need to learn the fundamentals before moving on to more complicated configurations. One such detail is the OSPF Router ID, or RID.

The RID is the dotted decimal value by which other OSPF routers will identify a given OSPF router. There are some interesting defaults for this value, and a command you should know to hardcode the RID. You had also better know what has to happen for this command to take effect, so let’s take a more detailed look at the OSPF RID.

In this example, R1 has an adjacency with R2 and R3 over the 172.12.123.0/24 frame network. R1 is the hub, with R2 and R3 as the spokes. No other interfaces are OSPF-enabled on any of the routers. Running show ip ospf neighbor on R1, we see some unusual values under “Neighbor ID”, which is another name for the OSPF RID.

R1#show ip ospf neighbor

Neighbor ID Pri State Dead Time Address Interface

3.3.3.3 0 FULL/DROTHER 00:01:57 172.12.123.3 Serial0

2.2.2.2 0 FULL/DROTHER 00:01:57 172.12.123.2 Serial0

Notice the Neighbor ID of each remote address is the loopback address. How can that be if they’re not OSPF-enabled?

When determining the Router ID (RID) of an OSPF-enabled router, OSPF will always use the numerically highest IP address on the router’s loopback interfaces, regardless of whether that loopback is OSPF-enabled.

What if there is no loopback? OSPF will then use the numerically highest IP address of the physical interfaces, regardless of whether that interface is OSPF-enabled.

BOTTOM LINE: An interface does not have to be running OSPF to have its IP address used as the OSPF RID.

The OSPF RID can be changed, but it requires a restart or to reinitialize the OSPF routing process. Use the router-id command to change the default RID of each router as shown, and clear the OSPF process to do so.

R1#conf t

Enter configuration commands, one per line. End with CNTL/Z.

R1(config)#router ospf 1

R1(config-router)#router-id 11.11.11.11

Reload or use “clear ip ospf process” command, for this to take effect

R1#clear ip ospf process

Reset ALL OSPF processes? [no]: yes

1d05h: %OSPF-5-ADJCHG: Process 1, Nbr 3.3.3.3 on Serial0 from 2WAY to DOWN, Neighbor Down: Interface down or detached

1d05h: %OSPF-5-ADJCHG: Process 1, Nbr 2.2.2.2 on Serial0 from 2WAY to DOWN, Neighbor Down: Interface down or detached

After entering the router-id command, the router console informed you that you have to reload the router or reset the OSPF processes for this to take effect. You enter the clear ip ospf process command to do this. Notice that when you’re asked if you really want to do this, the prompt is “no”? That’s because all the OSPF adjacencies on this router will be lost and will have to begin the process again. That’s OK on a practice rack, not good in a production network. Don’t use that one at work.

The OSPF RID is not a complicated concept, but the fact that an interface doesn’t have to be OSPF-enabled in order to have its IP address act as the RID takes some getting used to. And remember – when the router or switch asks you a question and the prompted answer is “no”, take one step back and make sure you really want to do what you’re about to do!

Incoming search terms:

Loopback Interfaces | Cisco CCNA Tutorial

As a CCNA candidate, you most likely have some background in PC hardware and workstation support. If so, you’re already familiar with loopback interfaces, particularly 127.0.0.1, the loopback address assigned to a PC.

When you’re learning all about the different physical interfaces for your CCNA exam – serial, ethernet, and BRI, among others – there’s one logical interface you need to know about, and that is – you guessed it! – the loopback interface.

What isn’t as immediately apparent is why we use loopback interfaces on routers and switches to begin with. Many of the Cisco router features that can use loopbacks are intermediate and advanced features that you’ll learn about in your CCNP and CCIE studies, but these features all come back to one basic concept: If the loopback interface on a router is down, that means the router is unavailable as a whole.

In contrast, a physical interface being down does not mean the router itself is out of commission. A router’s ethernet port can go down, but the other physical interfaces on that router are still operational. Since a loopback interface is logical, there’s nothing physical that can go wrong with it.

As I mentioned, you’ll learn different Cisco router and switch features that utilize loopback interfaces as you climb the Cisco certification ladder. There’s one misconception about Cisco loopback interfaces that you want to get clear on now, though. You’re probably familiar with loopback interfaces on a PC, and may even know that the address range 127.0.0.0 is reserved for loopback addressing.

Note that this reserved address range does not apply to loopbacks on Cisco devices, however. If you attempt to assign an address from this range to a Cisco loopback interface, you get this result:

R1#conf t

Enter configuration commands, one per line. End with CNTL/Z.

R1(config)#interface loopback0

R1(config-if)#ip address 127.0.0.2 255.255.255.0

Not a valid host address – 127.0.0.2

R1(config-if)#ip address 127.1.1.1 255.255.255.0

Not a valid host address – 127.1.1.1

The range 127.0.0.0 is reserved for host loopbacks (such as PCs), not routers or switches. The most commonly used address from this range is 127.0.0.1 – if you can’t ping that on a workstation, that means you can’t ping yourself, which means there’s a problem with the TCP/IP install itself.

Keep these details in mind on the exam and in the workplace, and you’re on your way to CCNA exam success!

Incoming search terms:

Static Routing Tutorial

In studying for your CCNA exam and preparing to earn this valuable certification, you may be tempted to spend little time studying static routing and head right for the more exciting dynamic routing protocols like RIP, EIGRP, and OSPF. This is an understandable mistake, but still a mistake. Static routing is not complicated, but it’s an important topic on the CCNA exam and a valuable skill for real-world networking.

To create static routes on a Cisco router, you use the ip route command followed by the destination network, network mask, and either the next-hop IP address or the local exit interface. It’s vital to keep that last part in mind – you’re either configuring the IP address of the downstream router, or the interface on the local router that will serve as the exit interface.

Let’s say your local router has a serial0 interface with an IP address of 200.1.1.1/30, and the downstream router that will be the next hop will receive packets on its serial1 interface with an IP address of 200.1.1.2/30. The static route will be for packets destined for the 172.10.1.0 network. Either of the following ip route statements would be correct. R1(config)#ip route 172.10.1.0 255.255.255.0 200.1.1.2 (next-hop IP address)

OR

R1(config)#ip route 172.10.1.0 255.255.255.0 serial0 ( local exit interface)

You can also write a static route that matches only one destination. This is a host route, and has 255.255.255.255 for a mask. If the above static routes should only be used to send packets to 172.10.1.1., the following commands would do the job.

R1(config)#ip route 172.10.1.1 255.255.255.255 200.1.1.2 (next-hop IP address)

OR

R1(config)#ip route 172.10.1.1 255.255.255.255 serial0 ( local exit interface)

Finally, a default static route serves as a gateway of last resort. If there are no matches for a destination in the routing table, the default route will be used. Default routes use all zeroes for both the destination and mask, and again a next-hop IP address or local exit interface can be used.

R1(config)#ip route 0.0.0.0 0.0.0.0 200.1.1.2 (next-hop IP address)

OR

R1(config)#ip route 0.0.0.0 0.0.0.0 serial0 ( local exit interface)

IP route statements seem simple enough, but the details regarding the next-hop IP address, the local exit interface, default static routes, and the syntax of the command are vital for success on CCNA exam day and in the real world.

Incoming search terms: