I saw this Cisco IOS hidden command show ip ospf route for OSPF in this post. I tried to create a running example for myself so I can learn more about this hidden command.
Do you like this site? Remember to share it to all your friends on Facebook and Twitter!
Showing posts with label OSPF. Show all posts
Showing posts with label OSPF. Show all posts
Wednesday, October 14, 2015
Saturday, September 29, 2012
Tuesday, April 28, 2009
Observe and solve Classful addressing problem, using OSPF (CNA-02-007)
CCNA Exploration 4.0, Semester 2, "Observe and solve Classful addressing problem, using OSPF" Packet Tracer 5.0 practice file (CNA-02-007).
I like to use OSPF because I do not have to worry about any "Classful" problem at all: there is no "Classful" function in its design and no backward compatibility burdens. No "no auto-summary" command in OSPF!
As long as OSPF is running fine, all routes would also be fine!
I like to use OSPF because I do not have to worry about any "Classful" problem at all: there is no "Classful" function in its design and no backward compatibility burdens. No "no auto-summary" command in OSPF!
As long as OSPF is running fine, all routes would also be fine!
R2>sh ip 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 not set
10.0.0.0/24 is subnetted, 2 subnets
O 10.1.1.0 [110/65] via 172.30.2.1, 00:00:24, Serial0/0/0
O 10.2.2.0 [110/65] via 192.168.4.1, 00:00:24, Serial0/0/1
172.30.0.0/24 is subnetted, 3 subnets
O 172.30.1.0 [110/65] via 172.30.2.1, 00:00:24, Serial0/0/0
C 172.30.2.0 is directly connected, Serial0/0/0
C 172.30.3.0 is directly connected, FastEthernet0/0
C 192.168.4.0/24 is directly connected, Serial0/0/1
O 192.168.5.0/24 [110/65] via 192.168.4.1, 00:00:24, Serial0/0/1
R2>
Related Posts:
CCNA,
CCNA Exploration 4.0,
Cisco Network Academy,
OSPF,
Packet Tracer
Location:
Wanhua District, Taipei City, Taiwan
Sunday, April 12, 2009
How to "Resign" your Router role as DR/BDR in OSPF without clearing OSPF process?
In Cisco IOS, just change that interface priority to zero (0), then it quits the role of DR/BDR immediately.
interface FastEthernet0/0
ip ospf priority 0
Related Posts:
CCNP,
Maintenance Tips,
OSPF,
Quick Reference
Saturday, December 20, 2008
IOS OSPF Multi-VRF support: remember to add "capability vrf-lite" statement
IOS "Multi-VRF" to me is a solution to one of my headache. Since I failed to persuade my colleagues buying new switches, I have to make one hardware acting as two.
(The following story is really demonstrating a bad habit. You should avoid the same mistakes by prepare well before you do anything!)
Without study further at the beginning, I jumped right into configuring and enabling the Multi-VRF feature. I decided to use OSPF, so my first configuration looked like this:
Looks not too wrong, isn't it?
In fact, I immediately saw a lot of routing entries coming in. That's why I thought I was right at the first moment.
Then something strange came out. I checked more carefully about the routing table entries and found some routes are just missing. All OSPF externals and "intra-area"s are there, but not those "inter-area"s.
I googled a while and found this page on Cisco.com. The missing statement is "capability vrf-lite". So the correct configuration should be like this:
A good lessen for myself!
(The following story is really demonstrating a bad habit. You should avoid the same mistakes by prepare well before you do anything!)
Without study further at the beginning, I jumped right into configuring and enabling the Multi-VRF feature. I decided to use OSPF, so my first configuration looked like this:
router ospf 1 vrf XXXXX router-id 1.2.3.4 area 1.2.3.0 authentication message-digest network 1.2.3.0 0.0.0.255 area 1.2.3.0
Looks not too wrong, isn't it?
In fact, I immediately saw a lot of routing entries coming in. That's why I thought I was right at the first moment.
Then something strange came out. I checked more carefully about the routing table entries and found some routes are just missing. All OSPF externals and "intra-area"s are there, but not those "inter-area"s.
I googled a while and found this page on Cisco.com. The missing statement is "capability vrf-lite". So the correct configuration should be like this:
router ospf 1 vrf XXXXX
router-id 1.2.3.4
capability vrf-lite
area 1.2.3.0 authentication message-digest
network 1.2.3.0 0.0.0.255 area 1.2.3.0
A good lessen for myself!
Tuesday, June 17, 2008
OSPF LSA Types (2), LSA Type 1: Router LSA
(Continued from previous post)
Type 1 LSA is a Router LSA. Each LSA defines one OSPF speaking router, and all its direct connections to network objects.
Network objects are (1) OSPF routers, and (2) OSPF defined networks.
Look at the diagram. The router R1 is in fact connected to 3 objects: router R2, network 10.12.12.0/24, and network 10.1.1.0/24.
No, the network 100.100.100.1/24 is not defined in this OSPF configuration, that's why it is not a connected object.
We use the command show ip ospf database router 0.0.0.1 to list the exact Type 1 Router LSAs defining R1, where 0.0.0.1 is the OSPF name (the router ID) of R1. Here is the result on R1.
Similarly, we can also list the Type 1 Router LSA of R2. Here is the result on R1, using command "show ip ospf database router 0.0.0.2"
(To be continued)
Type 1 LSA is a Router LSA. Each LSA defines one OSPF speaking router, and all its direct connections to network objects.
Network objects are (1) OSPF routers, and (2) OSPF defined networks.
Look at the diagram. The router R1 is in fact connected to 3 objects: router R2, network 10.12.12.0/24, and network 10.1.1.0/24.
No, the network 100.100.100.1/24 is not defined in this OSPF configuration, that's why it is not a connected object.
We use the command show ip ospf database router 0.0.0.1 to list the exact Type 1 Router LSAs defining R1, where 0.0.0.1 is the OSPF name (the router ID) of R1. Here is the result on R1.
R1>show ip ospf database router 0.0.0.1
OSPF Router with ID (0.0.0.1) (Process ID 1)
Router Link States (Area 0)
LS age: 1724
Options: (No TOS-capability, DC)
LS Type: Router Links
Link State ID: 0.0.0.1
Advertising Router: 0.0.0.1
LS Seq Number: 80000003
Checksum: 0x54DC
Length: 60
AS Boundary Router
Number of Links: 3
Link connected to: another Router (point-to-point)
(Link ID) Neighboring Router ID: 0.0.0.2
(Link Data) Router Interface address: 10.12.12.1
Number of TOS metrics: 0
TOS 0 Metrics: 64
Link connected to: a Stub Network
(Link ID) Network/subnet number: 10.12.12.0
(Link Data) Network Mask: 255.255.255.0
Number of TOS metrics: 0
TOS 0 Metrics: 64
Link connected to: a Stub Network
(Link ID) Network/subnet number: 10.1.1.0
(Link Data) Network Mask: 255.255.255.0
Number of TOS metrics: 0
TOS 0 Metrics: 10
R1>
Similarly, we can also list the Type 1 Router LSA of R2. Here is the result on R1, using command "show ip ospf database router 0.0.0.2"
You may have noticed, that R2 indeed is connected to more than 3 objects, how come only 3 are listed? This is because each OSPF area has its own link state database. The above 3 objects are the only objects within Area 0, the one covering both R1 and R2.
R1>show ip ospf database router 0.0.0.2
OSPF Router with ID (0.0.0.1) (Process ID 1)
Router Link States (Area 0)
Routing Bit Set on this LSA
LS age: 1508
Options: (No TOS-capability, DC)
LS Type: Router Links
Link State ID: 0.0.0.2
Advertising Router: 0.0.0.2
LS Seq Number: 80000004
Checksum: 0x84A8
Length: 60
Area Border Router
Number of Links: 3
Link connected to: another Router (point-to-point)
(Link ID) Neighboring Router ID: 0.0.0.1
(Link Data) Router Interface address: 10.12.12.2
Number of TOS metrics: 0
TOS 0 Metrics: 64
Link connected to: a Stub Network
(Link ID) Network/subnet number: 10.12.12.0
(Link Data) Network Mask: 255.255.255.0
Number of TOS metrics: 0
TOS 0 Metrics: 64
Link connected to: a Stub Network
(Link ID) Network/subnet number: 10.2.2.0
(Link Data) Network Mask: 255.255.255.0
Number of TOS metrics: 0
TOS 0 Metrics: 10
R1>
(To be continued)
Sunday, June 1, 2008
OSPF LSA Types (1)
For a quick reference about OSPF LSA types, I designed this case study to demonstrate them together.I use 4 routers, talking to each other using OSPF protocol. R1 is belonging to Area 0. R3 and R4 are belonging to Area 1. R2 is a border router, where some interfaces are in Area 0, and others in Area 1.
(To be continued)
Network Diagram
R1 Configuration
R2 Configuration
R3 Configuration
R4 Configuration
Related Posts:
CCNP,
OSPF,
Quick Reference
Location:
Wanhua District, Taipei City, Taiwan
Subscribe to:
Posts (Atom)
Popular Posts
-
CCNA Exploration 4.0, Semester 4, "Dual Stack IPv6 and IPv4 configuration " Packet Tracer 5.0 practice file (CNA-04-006). ...
-
I created this practice to test the Packet Tracer 5.3 features of BGP.
-
Fire-like Kapok blossoms in Taipei City, Taiwan To show the reserved VLAN numbers on both IOS and NX-OS, the common command is: sho...
-
We hear a lot of directions when we are talking about Data Center technologies: Northbound, Southbound, and even Eastbound/Westbound. What d...
-
One working switch port on my Cisco Catalyst 2950 suddenly went down by itself! Of course, my phone rang when I was having dinner, and the...
