Wednesday, August 28, 2013

CCNP wireless to CCIE Wireless

Note:

Almost all of the text found on this blog were taken from Cisco.com. This blog post was created to assist me with my CCNP wireless to CCIE wireless journey.


Note: These controller platforms do not require licenses: Cisco 2100 and Cisco 4400 Series Controllers, Cisco WiSMs, Controller Network Modules, and Catalyst 3750G Integrated Wireless LAN Controller Switches.


All features included in a Wireless LAN Controller WPLUS license are now included in the base license; this change is introduced in release 6.0.196.0. These WPlus license features are included in the base license:
OfficeExtend AP
Enterprise Mesh
CAPWAP Data Encryption
The licensing change can affect features on your wireless LAN when you upgrade or downgrade software releases, so you should be aware of these guidelines:
If you have a WPlus license and you upgrade from 6.0.x.x to 7.0.98.0, your license file contains both Basic and WPlus license features. You won’t see any disruption in feature availability and operation.
If you have a WPlus license and you downgrade from 7.0.98.0 to 6.0.196.0 or 6.0.188 or 6.0.182, your license file contains only base license, and you will lose all WPLUS features.
If you have a base license and you downgrade from 6.0.196.0 to 6.0.188 or 6.0.182, when you downgrade, you lose all WPlus features

Base license SKUs for the Cisco 5500 Series Controllers are as follows:
AIR-CT5508-12-K9
AIR-CT5508-25-K9
AIR-CT5508-50-K9
AIR-CT5508-100-K9
AIR-CT5508-250-K9
AIR-CT5508-500-K9
The capacity adder SKUs are as follows:
LIC-CT5508-25A
LIC-CT5508-50A
LIC-CT5508-100A
LIC-CT5508-250A

NoteIf you require a paper certificate for Customs, order it without the “L-” in the SKU (for example, LIC-CT5508-250A) and choose to ship it using U.S. mail.

NoteTypically, you are prompted to accept the EULA for evaluation, extension, and rehost licenses. The EULA is also required for permanent licenses, but it is accepted during license generation.
Ports
A port is a physical entity that is used for connections on the controller platform. Controllers have two types of ports: distribution system ports and a service port.

Cisco 4402 Controllers have two Gigabit Ethernet distribution system ports, each of which is capable of managing up to 48 access points. However, we recommend no more than 25 access points per port due to bandwidth constraints. The 4402-25 and 4402-50 models allow a total of 25 or 50 access points to join the controller.


Cisco 4404 Controllers have four Gigabit Ethernet distribution system ports, each of which is capable of managing up to 48 access points. However, we recommend no more than 25 access points per port due to bandwidth constraints. The 4404-25, 4404-50, and 4404-100 models allow a total of 25, 50, or 100 access points to join the controller.
NoteThe following Cisco Small Form-Factor Pluggable (SFP) options are supported in the Cisco 4400 Series Wireless LAN Controllers: GLC-T (1000BASE-T), GLC-SX-MM (1000BASE-SX), GLC-LH-SM (1000BASE-LX/LH SFP).
NoteThe Gigabit Ethernet ports on the Cisco 4402 and 4404 Controllers accept these SX/LC/T small form-factor plug-in (SFP) modules:- 1000BASE-SX SFP modules, which provide a 1000-Mbps wired connection to a network through an 850nM (SX) fiber-optic link using an LC physical connector- 1000BASE-LX SFP modules, which provide a 1000-Mbps wired connection to a network through a 1300nM (LX/LH) fiber-optic link using an LC physical connector- 1000BASE-T SFP modules, which provide a 1000-Mbps wired connection to a network through a copper link using an RJ-45 physical connector

Cisco 5508 Controllers have eight Gigabit Ethernet distribution system ports, through which the Controller can manage multiple access points. The 5508-12, 5508-25, 5508-50, 5508-100, and 5508-250 models allow a total of 12, 25, 50, 100, or 250 access points to join the controller. Cisco 5508 controllers have no restrictions on the number of access points per port. However, we recommend using link aggregation (LAG) or configuring dynamic AP-manager interfaces on each Gigabit Ethernet port to automatically balance the load. If more than 100 access points are connected to the Cisco 5500 Series Controller, make sure that more than one Gigabit Ethernet interface is connected to the upstream switch.
NoteThe following Cisco Small Form-Factor Pluggable (SFP) options are supported in the Cisco 5500 Series Wireless LAN Controllers: GLC-T (1000BASE-T), GLC-SX-MM (1000BASE-SX), GLC-LH-SM (1000BASE-LX/LH SFP).
NoteThe Gigabit Ethernet ports on the Cisco 5508 Controllers accept these SX/LC/T small form-factor plug-in (SFP) modules:- 1000BASE-SX SFP modules, which provide a 1000-Mbps wired connection to a network through an 850nM (SX) fiber-optic link using an LC physical connector- 1000BASE-LX SFP modules, which provide a 1000-Mbps wired connection to a network through a 1300nM (LX/LH) fiber-optic link using an LC physical connector- 1000BASE-T SFP modules, which provide a 1000-Mbps wired connection to a network through a copper link using an RJ-45 physical connector


Each distribution system port is, by default, an 802.1Q VLAN trunk port. The VLAN trunking characteristics of the port are not configurable.

Cisco 4400 and Cisco 5500 Series Controllers also have a 10/100/1000 copper Ethernet service port. The service port is controlled by the service-port interface and is reserved for out-of-band management of the controller and system recovery and maintenance in the event of a network failure. It is also the only port that is active when the controller is in boot mode. The service port is not capable of carrying 802.1Q tags, so it must be connected to an access port on the neighbor switch. Use of the service port is optional.

NoteThe Cisco WiSM’s controllers use the service port for internal protocol communication between the controllers and the Supervisor 720.
NoteThe Cisco 2100 Series Controller and the controller in the Cisco Integrated Services Router do not have a service port.

NoteThe service port is not autosensing. You must use the correct straight-through or crossover Ethernet cable to communicate with the service port.

CautionDo not configure wired clients in the same VLAN or subnet of the service port on the network.
Interfaces
An interface is a logical entity on the controller. An interface has multiple parameters associated with it, including an IP address, default gateway (for the IP subnet), primary physical port, secondary physical port, VLAN identifier, and DHCP server.

***********************************************************************************
***********************************************************************************

To make APs advertise their channel and tx power level in beacons select DTPC support.

What is DTPC?


When you enable Dynamic Transmit Power Control (DTPC), access points add channel and transmit power information to beacons. (On access points that run Cisco IOS software, this feature is called world mode.)

NOTE: DTPC and world mode are not the same things.

config {802.11a | 802.11bg} dtpc {enable | disable}  

DATA RATES:

Mandatory - clients must support this data rate to be able to associate to the AP

Supported - Clients that support the data rate  can communicate with the AP

Disabled -  Clients specify the data rates for communication

Configure 802.11 bands

Note: The 802.11 band must be disabled in order to configure any settings.

config 802.11a disable network

(wlc1) >config 802.11a rate disabled 6
(wlc1) >config 802.11a rate mandatory 12
(wlc1) >config 802.11a rate supported 54

(wlc1) >show 802.11b

802.11b Network.................................. Enabled
11gSupport....................................... Enabled
11nSupport....................................... Enabled
802.11b/g Operational Rates
    802.11b/g 1M Rate............................ Disabled
    802.11b/g 2M Rate............................ Disabled
    802.11b/g 5.5M Rate.......................... Disabled
    802.11b/g 11M Rate........................... Disabled
    802.11g 6M Rate.............................. Disabled
    802.11g 9M Rate.............................. Disabled
    802.11g 12M Rate............................. Mandatory
    802.11g 18M Rate............................. Supported
    802.11g 24M Rate............................. Supported
    802.11g 36M Rate............................. Supported
    802.11g 48M Rate............................. Supported
    802.11g 54M Rate............................. Supported



How are 802.11n data rates achieved?

High data rates are acheived with the following:

MIMO
Transmit beamforming
Spatial multiplexing
Guard intervals
MCS Index

MIMO - is the use of multiple antennas at both the transmitter and receiver to improve communication performance. It is one of several forms of smart antenna technology



 Transmit beamforming - allows an AP to "focus" it's signal at a client's location. Focusing the signal based on the client's location will increase throughput, SNR and RSSI





Spatial multiplexing - is a  802.11n MIMO technology that allows multiple streams independent streams

Guard interval - is the "space"/ quiet time between symbols in 802.11 transmission that minimizes interference . Symbols are characters that are being transmitted.Guard intervals can be long 800ns or short 400ns. Shorter guard intervals increase throughput but at the risk of higher retries.

MCS index - Are values that allow you to calculate data rates.





MCS index on a Cisco WLC






































802.11h - is used to detect radar interference.

channel announcement can be checked off so that the AP can announce that it is about to change channels and it will also announce the new channel number.

if you want the AP to stop transmitting on the affected 802.11h channel check off the quiet mode box.







Debug from the LAP

If the controller debugs do not indicate a join request, you can debug the process from the LAP as long as the LAP has a console port. You can see the LAP boot up process with these commands, but you must first get into enable mode (default password is Cisco):
  • debug dhcp detail—Shows DHCP option 43 information.
  • debug ip udp—Shows the join/discovery packets to the controller as well as DHCP and DNS queries (all of these are UDP packets. Port 12223 is the controller’s source port).
  • debug lwapp client event—Shows LWAPP events for the AP.
  • undebug all—Disables debugs on the AP.


debug pm pki enable

As a part of the join process, the WLC authenticates each LAP by verifying that its certificate is valid.
When the AP sends the LWAPP Join Request to the WLC, it embeds its X.509 certificate in the LWAPP message. The AP also generates a random session ID that is also included in the LWAPP Join Request. When the WLC receives the LWAPP Join Request, it validates the signature of the X.509 certificate using the AP's public key and checks that the certificate was issued by a trusted certificate authority.
It also looks at the starting date and time for the AP certificate's validity interval and compares that date and time to its own date and time (hence the controller’s clock needs to be set to close to the current date and time). If the X.509 certificate is validated, the WLC generates a random AES encryption key. The WLC plumbs the AES key into its crypto engine so that it can encrypt and decrypt future LWAPP Control Messages exchanged with the AP. Note that data packets are sent in the clear in the LWAPP tunnel between the LAP and the controller.
The debug pm pki enable command shows the certification validation process that occurs during the join phase on the controller. The debug pm pki enable command will also display the AP hash key during the join process if the AP has a self-signed certificate (SSC) created by the LWAPP conversion program. If the AP has a Manufactured Installed Certificate (MIC), you will not see a hash key.
Note: All APs manufactured after June 2006 have a MIC.

 Clientlink
http://www.cisco.com/en/US/prod/collateral/wireless/ps5678/ps10092/white_paper_c11-516389.html
www.youtube.com/watch?v=f2ovVxGeyFo
 
 

Tuesday, January 1, 2013

Cisco's PBR - set ip next-hop verify-availability

Normally set ip next-hop will forward packets when the route-map is matched regardless if the next hop is alive or not. Adding the verify-availability keyword, the router will check the next hop availability via CDP before forwarding the packets, and when next-hop is dead, the packets will be routed through the normal routing table.

http://www.cisco.com/en/US/docs/ios/12_3t/12_3t4/feature/guide/gtpbrtrk.html#wp1057830


Example:

R1#show run | section route-map RPB
 ip policy route-map RPB
route-map RPB permit 10
 match ip address FROM_R3_TO_R4
 set ip next-hop 155.30.0.5
 set ip next-hop verify-availability --> VERIFY VIA CDP
 set ip default next-hop 155.30.146.4
route-map RPB permit 20
 match ip address FROM_R3_TO_R5
 set ip next-hop verify-availability 155.30.146.4 1 track 1
 set ip default next-hop 150.30.0.5

Monday, May 7, 2012

Understanding Cisco Prefix-List

A = 10.0.0.0/8
B = 172.16.0.0/16
C = 192.168.1.0/24

############################################################
0    = 00000000
126    = 01111110

The first bit match


ip prefix-list Incoming seq 5 deny 0.0.0.0/1 ge 8 le 8

############################################################
128 = 10000000
191 = 10111111

The first 2 bits match

ip prefix-list Incoming seq 5 deny 128.0.0.0/2 ge 16 le 16

############################################################
192 = 11000000
223 = 11011111

The first 3 bits match

ip prefix-list Incoing seq 5 deny 192.0.0.0/3 ge 24 le 24
###########################################################

10.0.0.0-10.255.255.255

00001010.00000000.00000000.00000000  = 10.0.0.0    = 10.0.0.0/8
00001010.11111111.11111111.11111111  = 10.255.255.255


172.16.0.0-172.31.255.255
10101100.00010000.00000000.00000000 = 172.16.255.255    = 172.16.0.0/12
10101100.00011111.11111111.11111111 = 172.31.255.255

192.168.0.0-192.168.255.255
11000000.10101000.00000000.00000000 = 192.168.0.0    = 192.168.0.0/16
11000000.10101000.11111111.11111111 = 192.168.255.255


193.0.0.0 – 193.255.255.255 =
11000001.00000000.00000000.00000000 = 193.0.0.0
11000001.11111111.11111111.11111111 = 193.255.255.255

128.0.0.0 – 191.255.255.255 =
10000000.00000000.00000000.00000000

10111111.11111111.11111111.11111111

0.0.0.0 – 63.255.255.255
00000000.00000000.00000000.00000000
00111111.11111111.11111111.11111111


****************************************************************************************************************
•    In address range 193.0.0.0 – 193.255.255.255, do not accept prefixes with subnet masks longer than /20.
•    In address range 128.0.0.0 – 191.255.255.255, do not accept prefixes with subnet masks longer than /18.
•    In address range 0.0.0.0 – 63.255.255.255, do not accept prefixes with subnet masks longer than /12.
•    Never accept prefixes longer than /24.
***************************************************************************************************************


ip prefix-list Incoming seq 5 deny 10.0.0.0/8 le 32
ip prefix-list Incoming seq 10 deny 172.16.0.0/12 le 32
ip prefix-list Incoming seq 15 deny 192.168.0.0/16 le 32
ip prefix-list Incoming seq 20 deny 193.0.0.0/8 ge 21
ip prefix-list Incoming seq 25 deny 128.0.0.0/2 ge 19
ip prefix-list Incoming seq 30 deny 0.0.0.0/2 ge 13
ip prefix-list Incoming seq 35 permit 0.0.0.0/0 le 24

Friday, May 28, 2010

OSPF Virtual Link Configuration, Verification and troubleshooting



Configuration:

R1:

interface Loopback0
 ip address 10.0.0.1 255.224.0.0
 !
!
interface Loopback32
 ip address 10.32.0.1 255.224.0.0
 !
!
interface Loopback64
 ip address 10.64.0.1 255.224.0.0
 !
!
interface Loopback96
 ip address 10.96.0.1 255.224.0.0
 !
interface Serial1/0
 bandwidth 128
 ip address 192.168.1.1 255.255.255.252
 serial restart-delay 0
 clock rate 64000

router ospf 1
 router-id 1.1.1.1
 log-adjacency-changes
 network 10.0.0.0 0.31.255.255 area 0
 network 10.32.0.0 0.31.255.255 area 0
 network 10.64.0.0 0.31.255.255 area 0
 network 10.96.0.0 0.31.255.255 area 0
 network 192.168.1.0 0.0.0.3 area 0

__________________________________________________________________________________

R2:
interface FastEthernet0/0
 ip address 5.5.5.1 255.255.255.0
 ip ospf priority 10
 duplex half
 !
!
interface Serial1/0
 bandwidth 128
 ip address 192.168.1.2 255.255.255.224
 serial restart-delay 0
 !
router ospf 1
 router-id 2.2.2.1
 log-adjacency-changes
 network 5.5.5.0 0.0.0.255 area 1
 network 192.168.1.0 0.0.0.3 area 0

___________________________________________________________________________________

R3:
interface Loopback45
 ip address 45.45.45.1 255.255.255.0
 !
!
interface Loopback46
 ip address 45.45.46.1 255.255.255.0
 !
!
interface Loopback47
 ip address 45.45.47.1 255.255.255.0
 !
!
interface FastEthernet0/0
 ip address 5.5.5.2 255.255.255.0
 ip ospf priority 0
 duplex half
 !
!
!
router ospf 1
 router-id 3.3.3.1
 log-adjacency-changes
 network 5.5.5.0 0.0.0.255 area 1
 network 45.45.45.0 0.0.0.0 area 1
 network 45.45.46.0 0.0.0.0 area 1
 network 45.45.47.0 0.0.0.0 area 1

!
__________________________________________________________________________________

R4:
interface Loopback28
 ip address 28.28.28.1 255.255.255.0
 !
!
interface Loopback29
 ip address 28.28.29.1 255.255.255.0
 !
!
interface Loopback30
 ip address 28.28.30.1 255.255.255.0
 !
!
interface FastEthernet0/0
 ip address 5.5.5.3 255.255.255.0
 ip ospf priority 0
 duplex half
 !
!
interface Serial1/0
 bandwidth 64
 ip address 7.7.7.1 255.255.255.252
 serial restart-delay 0
 clock rate 64000
 !
router ospf 1
 router-id 4.4.4.1
 log-adjacency-changes
 network 5.5.5.0 0.0.0.255 area 1
 network 7.7.7.0 0.0.0.3 area 51

___________________________________________________________________________________
R5:

interface Loopback31
 ip address 31.31.31.1 255.255.255.0
 !
!
interface Loopback32
 ip address 31.31.32.1 255.255.255.0
 !

interface Serial1/0
 ip address 7.7.7.2 255.255.255.252
 serial restart-delay 0
 !

router ospf 1
 router-id 5.5.5.1
 log-adjacency-changes
 network 7.7.7.0 0.0.0.3 area 51
 network 31.31.31.0 0.0.0.255 area 51
 network 31.31.32.0 0.0.0.255 area 51

___________________________________________________________________________________



Negiborship Verification

R1#sh ip ospf neighbor

Neighbor ID     Pri   State           Dead Time   Address         Interface
2.2.2.1           0   FULL/  -        00:00:37    192.168.1.2     Serial1/0
___________________________________________________________________________________

Neighbor ID     Pri   State           Dead Time   Address         Interface
1.1.1.1           0   FULL/  -        00:00:39    192.168.1.1     Serial1/0
3.3.3.1           0   FULL/DROTHER    00:00:36    5.5.5.2         FastEthernet0/0
4.4.4.1           0   FULL/DROTHER    00:00:33    5.5.5.3         FastEthernet0/0
___________________________________________________________________________________

R3#sh ip ospf neighbor

Neighbor ID     Pri   State           Dead Time   Address         Interface
2.2.2.1          10   FULL/DR         00:00:31    5.5.5.1         FastEthernet0/0
4.4.4.1           0   2WAY/DROTHER    00:00:36    5.5.5.3         FastEthernet0/0
___________________________________________________________________________________
R4#sh ip ospf neighbor

Neighbor ID     Pri   State           Dead Time   Address         Interface
2.2.2.1          10   FULL/DR         00:00:31    5.5.5.1         FastEthernet0/0
3.3.3.1           0   2WAY/DROTHER    00:00:37    5.5.5.2         FastEthernet0/0
5.5.5.1           0   FULL/  -        00:00:37    7.7.7.2         Serial1/0
___________________________________________________________________________________

R5#sh ip ospf neighbor

Neighbor ID     Pri   State           Dead Time   Address         Interface
4.4.4.1           0   FULL/  -        00:00:38    7.7.7.1         Serial1/0
____________________________________________________________________________________

Note: Lets take a look at what routers see as they become neighbors: The following output happens between R4 and R5.

R4#
*May 28 10:56:50.735: OSPF: Serial1/0: Route adjust notification: UP/UP
*May 28 10:56:50.735: OSPF: Interface Serial1/0 going Up
*May 28 10:56:50.739: OSPF: Serial1/0: Interface state change to UP, new ospf state P2P
*May 28 10:56:51.235: OSPF: Build router LSA for area 51, router ID 4.4.4.1, seq 0x80000008, process 1
R4#
*May 28 10:57:03.419: OSPF: Rcv DBD from 5.5.5.1 on Serial1/0 seq 0x1653 opt 0x52 flag 0x7 len 32  mtu 1500 state INIT
*May 28 10:57:03.419: OSPF: 2 Way Communication to 5.5.5.1 on Serial1/0, state 2WAY
*May 28 10:57:03.423: OSPF: Serial1/0 Nbr 5.5.5.1: Prepare dbase exchange
*May 28 10:57:03.423: OSPF: Send DBD to 5.5.5.1 on Serial1/0 seq 0x151D opt 0x52 flag 0x7 len 32
*May 28 10:57:03.423: OSPF: NBR Negotiation Done. We are the SLAVE
*May 28 10:57:03.423: OSPF: Serial1/0 Nbr 5.5.5.1: Summary list built, size 2
*May 28 10:57:03.427: OSPF: Send DBD to 5.5.5.1 on Serial1/0 seq 0x1653 opt 0x52 flag 0x2 len 72
*May 28 10:57:03.499: OSPF: Rcv DBD from 5.5.5.1 on Serial1/0 seq 0x1654 opt 0x52 flag 0x1 len 72  mtu 1500 state EXCHANGE
*May 28 10:57:03.503: OSPF: Exchange Done with 5.5.5.1 on Serial1/0
*May 28 10:57:03.503: OSPF: Send LS REQ to 5.5.5.1 length 12 LSA count 1
*May 28 10:57:03.503: OSPF: Send DBD to 5.5.5.1 on Serial1/0 seq 0x1654 opt 0x52 flag 0x0 len 32
*May 28 1
R4#0:57:03.595: OSPF: Rcv LS UPD from 5.5.5.1 on Serial1/0 length 76 LSA count 1
*May 28 10:57:03.595: OSPF: Synchronized with 5.5.5.1 on Serial1/0, state FULL
*May 28 10:57:03.599: %OSPF-5-ADJCHG: Process 1, Nbr 5.5.5.1 on Serial1/0 from LOADING to FULL, Loading Done
*May 28 10:57:03.651: OSPF: Rcv LS REQ from 5.5.5.1 on Serial1/0 length 36 LSA count 1
*May 28 10:57:04.099: OSPF: Build router LSA for area 51, router ID 4.4.4.1, seq 0x80000009, process 1
R4#U ALL
All possible debugging has been turned off
____________________________________________________________________________________

R5#

*May 28 10:58:58.183: OSPF: Serial1/0: Route adjust notification: UP/UP
*May 28 10:58:58.183: OSPF: Interface Serial1/0 going Up
*May 28 10:58:58.187: OSPF: Serial1/0: Interface state change to UP, new ospf state P2P
*May 28 10:58:58.215: OSPF: 2 Way Communication to 4.4.4.1 on Serial1/0, state 2WAY
*May 28 10:58:58.215: OSPF: Serial1/0 Nbr 4.4.4.1: Prepare dbase exchange
*May 28 10:58:58.215: OSPF: Send DBD to 4.4.4.1 on Serial1/0 seq 0x1653 opt 0x52 flag 0x7 len 32
*May 28 10:58:58.491: OSPF: Rcv DBD from 4.4.4.1 on Serial1/0 seq 0x151D opt 0x52 flag 0x7 len 32  mtu 1500 state EXSTART
*May 28 10:58:58.491: OSPF: First DBD and we are not SLAVE
*May 28 10:58:58.495: OSPF: Rcv DBD from 4.4.4.1 on Serial1/0 seq 0x1653 opt 0x52 flag 0x2 len 72  mtu 1500 state EXSTART
*May 28 10:58:58.495: OSPF: NBR Negotiation Done. We are the MASTER
*May 28 10:58:58.495: OSPF: Serial1/0 Nbr
R5#4.4.4.1: Summary list built, size 2
*May 28 10:58:58.495: OSPF: Send DBD to 4.4.4.1 on Serial1/0 seq 0x1654 opt 0x52 flag 0x1 len 72
*May 28 10:58:58.603: OSPF: Rcv LS REQ from 4.4.4.1 on Serial1/0 length 36 LSA count 1
*May 28 10:58:58.607: OSPF: Send UPD to 7.7.7.1 on Serial1/0 length 52 LSA count 1
*May 28 10:58:58.615: OSPF: Rcv DBD from 4.4.4.1 on Serial1/0 seq 0x1654 opt 0x52 flag 0x0 len 32  mtu 1500 state EXCHANGE
*May 28 10:58:58.615: OSPF: Exchange Done with 4.4.4.1 on Serial1/0
*May 28 10:58:58.619: OSPF: Send LS REQ to 4.4.4.1 length 12 LSA count 1
*May 28 10:58:58.683: OSPF: Build router LSA for area 51, router ID 5.5.5.1, seq 0x80000009, process 1
*May 28 10:58:58.747: OSPF: Rcv LS UPD from 4.4.4.1 on Serial1/0 length 64 LSA count 1
*May 28 10:58:58.751: OSPF: Synchronized with 4.4.4.1 on Serial1/0, state FULL
*May 28 10:58:58.751: %OSPF-5-ADJCHG: Process 1, Nbr 4.4.4.1 on Serial1/0 from LOADING to FULL, Loading Done
*May 28 10:58:58.751: OSPF: Serial1/0 Nbr 4
R5#.4.4.1: Clean-up dbase exchange
R5#
*May 28 10:59:03.683: OSPF: Build router LSA for area 51, router ID 5.5.5.1, seq 0x8000000A, process 1
R5#SH IP OSpf NEighbor

Neighbor ID     Pri   State           Dead Time   Address         Interface
4.4.4.1           0   FULL/  -        00:00:38    7.7.7.1         Serial1/0
R5#U ALL
All possible debugging has been turned off
____________________________________________________________________________________

Let's take a look at the Link State Database of R2 and R5:

R2#SH IP OSpf Database

            OSPF Router with ID (2.2.2.1) (Process ID 1)

                Router Link States (Area 0)

Link ID         ADV Router      Age         Seq#       Checksum Link count
1.1.1.1         1.1.1.1         994         0x80000009 0x005099 6
2.2.2.1         2.2.2.1         641         0x80000003 0x0090A7 2

                Summary Net Link States (Area 0)

Link ID         ADV Router      Age         Seq#       Checksum
5.5.5.0         2.2.2.1         641         0x80000002 0x00A67E

                Router Link States (Area 1)

Link ID         ADV Router      Age         Seq#       Checksum Link count
2.2.2.1         2.2.2.1         396         0x80000003 0x00A75A 1
3.3.3.1         3.3.3.1         371         0x80000003 0x007685 1
4.4.4.1         4.4.4.1         91          0x80000003 0x0048AC 1

                Net Link States (Area 1)


Link ID         ADV Router      Age         Seq#       Checksum
5.5.5.1         2.2.2.1         138         0x80000003 0x0036C8

                Summary Net Link States (Area 1)

Link ID         ADV Router      Age         Seq#       Checksum
10.0.0.1        2.2.2.1         644         0x80000002 0x006CAC
10.32.0.1       2.2.2.1         645         0x80000002 0x00EA0E
10.64.0.1       2.2.2.1         645         0x80000002 0x00696F
10.96.0.1       2.2.2.1         646         0x80000002 0x00E7D0
192.168.1.0     2.2.2.1         646         0x80000002 0x007762
192.168.1.3     2.2.2.1         646         0x80000002 0x009F0B
__________________________________________________________________________________


R5#sh ip ospf database

            OSPF Router with ID (5.5.5.1) (Process ID 1)

                Router Link States (Area 51)

Link ID         ADV Router      Age         Seq#       Checksum Link count
4.4.4.1         4.4.4.1         581         0x80000009 0x000882 2
5.5.5.1
____________________________________________________________________________________

Now for the Virtual Link configuration: Before I configure the virtual link let's take a look at the routing table of R1 and R4. Because the network is discontiguous R1 and R4 will not be able to communicate with each other.

R1#SH IP ROUTe ospf
Codes: L - local, C - connected, S - static, 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
       i - IS-IS, su - IS-IS summary, 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, + - replicated route

Gateway of last resort is not set

      5.0.0.0/24 is subnetted, 1 subnets
O IA     5.5.5.0 [110/782] via 192.168.1.2, 00:51:17, Serial1/0
      192.168.1.0/24 is variably subnetted, 3 subnets, 3 masks
O        192.168.1.0/27 [110/1562] via 192.168.1.2, 00:57:56, Serial1/0
R1#ping 31.31.31.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 31.31.31.1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
___________________________________________________________________________________R5#sh R5#sh ip route ospf
Codes: L - local, C - connected, S - static, 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
       i - IS-IS, su - IS-IS summary, 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, + - replicated route

Gateway of last resort is not set
R5#ping 10.0.0.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.0.1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
R5#

Note: As we can see there is no end to end network connectivity. The routing tables of R1 and R5 give proof to this.

Note: Virtual Links are a last resort to a disjointed network, this is only a temporary fix
__________________________________________________________________________________

Virtual Link config

If you take a look at the network diagram you will notice that R2 and R4 are ABR's. Virtual links cannot be configured in area 0. One of the routers in the Virtual Link must be a part of area 0. In the diagram R2 is in area 0. The Virtual Link will be configured on R2 and R4.

R2(config)#router ospf 1
R2(config-router)#area 1 virtual-link 4.4.4.1

*May 28 11:23:10.019: %OSPF-5-ADJCHG: Process 1, Nbr 4.4.4.1 on OSPF_VL1 from LOADING to FULL, Loading Done

__________________________________________________________________________________




R4(config-router)#area 1 virtual-link 2.2.2.1
R4(config-router)#
*May 28 11:23:10.019: %OSPF-5-ADJCHG: Process 1, Nbr 2.2.2.1 on OSPF_VL1 from LOADING to FULL, Loading Done

___________________________________________________________________________________

Note: Let us quickly verify the status of the virtual link on R2 and R4, then I will revisit the routing table of R1 and R5.

R2#SH IP OSpf VIrtual-links
Virtual Link OSPF_VL0 to router 4.4.4.1 is up

  Run as demand circuit
  DoNotAge LSA allowed.
  Transit area 1, via interface FastEthernet0/0
 Topology-MTID    Cost    Disabled     Shutdown      Topology Name
        0           1         no          no            Base
  Transmit Delay is 1 sec, State POINT_TO_POINT,
  Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
    Hello due in 00:00:02
    Adjacency State FULL (Hello suppressed)
    Index 2/4, retransmission queue length 0, number of retransmission 0
    First 0x0(0)/0x0(0) Next 0x0(0)/0x0(0)
    Last retransmission scan length is 0, maximum is 0
    Last retransmission scan time is 0 msec, maximum is 0 msec
_________________________________________________________________________________

R4#SH IP OSpf VIrtual-links
Virtual Link OSPF_VL1 to router 2.2.2.1 is up
  Run as demand circuit
  DoNotAge LSA allowed.
  Transit area 1, via interface FastEthernet0/0
 Topology-MTID    Cost    Disabled     Shutdown      Topology Name
        0           1         no          no            Base
  Transmit Delay is 1 sec, State POINT_TO_POINT,
  Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
    Hello due in 00:00:02
    Adjacency State FULL (Hello suppressed)
    Index 1/3, retransmission queue length 0, number of retransmission 0
    First 0x0(0)/0x0(0) Next 0x0(0)/0x0(0)
    Last retransmission scan length is 0, maximum is 0
    Last retransmission scan time is 0 msec, maximum is 0 msec

R1 and R2 routing table verification:

R1#sh ip route  ospf
Codes: L - local, C - connected, S - static, 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
       i - IS-IS, su - IS-IS summary, 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, + - replicated route

Gateway of last resort is not set

      5.0.0.0/24 is subnetted, 1 subnets
O IA     5.5.5.0 [110/782] via 192.168.1.2, 01:06:15, Serial1/0
      7.0.0.0/30 is subnetted, 1 subnets
O IA     7.7.7.0 [110/2344] via 192.168.1.2, 00:06:32, Serial1/0
      31.0.0.0/32 is subnetted, 2 subnets
O IA     31.31.31.1 [110/2345] via 192.168.1.2, 00:06:32, Serial1/0
O IA     31.31.32.1 [110/2345] via 192.168.1.2, 00:06:32, Serial1/0
      192.168.1.0/24 is variably subnetted, 3 subnets, 3 masks
O        192.168.1.0/27 [110/1562] via 192.168.1.2, 01:12:54, Serial1/0
R1#ping 31.31.31.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 31.31.31.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 108/135/192 ms
___________________________________________________________________________________

R5#sh ip route ospf
Codes: L - local, C - connected, S - static, 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
       i - IS-IS, su - IS-IS summary, 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, + - replicated route

Gateway of last resort is not set

      5.0.0.0/24 is subnetted, 1 subnets
O IA     5.5.5.0 [110/65] via 7.7.7.1, 00:08:19, Serial1/0
      10.0.0.0/32 is subnetted, 4 subnets
O IA     10.0.0.1 [110/847] via 7.7.7.1, 00:08:15, Serial1/0
O IA     10.32.0.1 [110/847] via 7.7.7.1, 00:08:15, Serial1/0
O IA     10.64.0.1 [110/847] via 7.7.7.1, 00:08:15, Serial1/0
O IA     10.96.0.1 [110/847] via 7.7.7.1, 00:08:15, Serial1/0
      192.168.1.0/24 is variably subnetted, 2 subnets, 2 masks
O IA     192.168.1.0/27 [110/846] via 7.7.7.1, 00:08:15, Serial1/0
O IA     192.168.1.0/30 [110/1627] via 7.7.7.1, 00:08:15, Serial1/0

R5#ping 10.0.0.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.0.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 112/151/188 ms
R5#ping 10.32.0.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.32.0.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 112/148/188 ms
R5#ping 10.64.0.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.64.0.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 108/143/176 ms
R5#ping 10.96.0.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.96.0.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 120/142/188 ms
We now have full network reachability

Thursday, May 20, 2010

RIPng Lab

RIPng Lab1:



Configuration

R1:

ipv6 unicast-routing
ipv6 cef


interface Loopback1
 no ip address
 ipv6 address ABCD:1111::1/32
 ipv6 rip lab1 enable
 !
!
interface Loopback2
 no ip address
 ipv6 address ABCD:1112::1/32
 ipv6 rip lab1 enable
 !
!
interface FastEthernet0/0
no ip address
duplex half
ipv6 address A:A:A::1/48
ipv6 rip lab1 enable
 !

ipv6 router rip lab1

__________________________________________________________________________________

R2:

ipv6 unicast-routing
ipv6 cef

interface Loopback1
 no ip address
 ipv6 address 1111::1/16
 ipv6 rip lab1 enable
 !
!
interface Loopback2
 no ip address
 ipv6 address 2222::1/16
 ipv6 rip lab1 enable
 !
!
interface Loopback3
 no ip address
 ipv6 address 3333::1/16
 ipv6 rip lab1 enable
 !
!
interface FastEthernet0/0
 no ip address
 duplex half
 ipv6 address A:A:A::2/48
 ipv6 rip lab1 enable
 !

ipv6 router rip lab1
!
!
________________________________________________________________________________


Verification R1
R1:

R1#SH IPV6 INTerface BRief

FastEthernet0/0            [up/up]
    FE80::C800:17FF:FE84:0
    A:A:A::1
Loopback1                  [up/up]
    FE80::C800:17FF:FE84:0
    ABCD:1111::1
Loopback2                  [up/up]
    FE80::C800:17FF:FE84:0
    ABCD:1112::1
R1#SH IPV6 PROtocols

IPv6 Routing Protocol is "connected"
IPv6 Routing Protocol is "ND"
IPv6 Routing Protocol is "rip lab1"
  Interfaces:
    Loopback2
    Loopback1
    FastEthernet0/0
  Redistribution:
    None

R1#SH IPV6 ROute RIp

IPv6 Routing Table - default - 10 entries
Codes: C - Connected, L - Local, S - Static, U - Per-user Static route
       B - BGP, M - MIPv6, R - RIP, I1 - ISIS L1
       I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary, D - EIGRP
       EX - EIGRP external, ND - Neighbor Discovery
       O - OSPF Intra, OI - OSPF Inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
       ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
R   1111::/16 [120/2]
     via FE80::C801:FFF:FE20:0, FastEthernet0/0
R   2222::/16 [120/2]
     via FE80::C801:FFF:FE20:0, FastEthernet0/0
R   3333::/16 [120/2]
     via FE80::C801:FFF:FE20:0, FastEthernet0/0

R1#SH IPV6 RIp Database

RIP process "lab1", local RIB
 A:A:A::/48, metric 2
     FastEthernet0/0/FE80::C801:FFF:FE20:0, expires in 161 secs
 1111::/16, metric 2, installed
     FastEthernet0/0/FE80::C801:FFF:FE20:0, expires in 161 secs
 2222::/16, metric 2, installed
     FastEthernet0/0/FE80::C801:FFF:FE20:0, expires in 161 secs
 3333::/16, metric 2, installed
     FastEthernet0/0/FE80::C801:FFF:FE20:0, expires in 161 secs

Test end to end connectivity

R1#PING 3333::1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 3333::1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 52/108/216 ms
R1#

__________________________________________________________________________________



Verification R2
R2:
R2#SH IPV6 INTerface BRief

FastEthernet0/0            [up/up]
    FE80::C801:FFF:FE20:0
    A:A:A::2
Loopback1                  [up/up]
    FE80::C801:FFF:FE20:0
    1111::1
Loopback2                  [up/up]
    FE80::C801:FFF:FE20:0
    2222::1
Loopback3                  [up/up]
    FE80::C801:FFF:FE20:0
    3333::1

R2#SH IPV6 PROtocols

IPv6 Routing Protocol is "connected"
IPv6 Routing Protocol is "ND"
IPv6 Routing Protocol is "rip lab1"
  Interfaces:
    Loopback3
    Loopback2
    Loopback1
    FastEthernet0/0
  Redistribution:
    None


R2#SH IPV6 ROute RIp

IPv6 Routing Table - default - 11 entries
Codes: C - Connected, L - Local, S - Static, U - Per-user Static route
       B - BGP, M - MIPv6, R - RIP, I1 - ISIS L1
       I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary, D - EIGRP
       EX - EIGRP external, ND - Neighbor Discovery
       O - OSPF Intra, OI - OSPF Inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
       ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
R   ABCD:1111::/32 [120/2]
     via FE80::C800:17FF:FE84:0, FastEthernet0/0
R   ABCD:1112::/32 [120/2]
     via FE80::C800:17FF:FE84:0, FastEthernet0/0


R2#SH IPV6 RIp Database

RIP process "lab1", local RIB
 A:A:A::/48, metric 2
     FastEthernet0/0/FE80::C800:17FF:FE84:0, expires in 170 secs
 ABCD:1111::/32, metric 2, installed
     FastEthernet0/0/FE80::C800:17FF:FE84:0, expires in 170 secs
 ABCD:1112::/32, metric 2, installed
     FastEthernet0/0/FE80::C800:17FF:FE84:0, expires in 170 secs


Test end to end connectivity

R2#PING abcd:1112::1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to ABCD:1112::1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 40/88/120 ms

OSPF LAB

OSPF: Open Shortest Path First (OSPF) is a dynamic routing protocol for use in Internet Protocol (IP) networks. Specifically, it is a link-state routing protocol and falls into the group of interior gateway protocols, operating within a single autonomous system (AS). It is defined as OSPF Version 2 in RFC 2328 (1998). Source:http://en.wikipedia.org/wiki/Open_Shortest_Path_First




  This lab starts with a basic OSPF configurations and verification.








R1:

interface Loopback45
 ip address 45.45.45.1 255.255.255.0
 !
!
interface Loopback46
 ip address 45.45.46.1 255.255.255.0
 !
!
interface Loopback47
 ip address 45.45.47.1 255.255.255.0
 !
!
interface FastEthernet0/0
 ip address 20.0.0.1 255.224.0.0
 duplex half
 !
!
!
router ospf 1
 router-id 1.1.1.1
 log-adjacency-changes
 network 20.0.0.0 0.31.255.255 area 0
 network 45.45.45.0 0.0.0.255 area 0
 network 45.45.46.0 0.0.0.255 area 0
 network 45.45.47.0 0.0.0.255 area 0

!
______________________________________________________________________________________________


R2:
interface FastEthernet0/0
 ip address 20.0.0.2 255.224.0.0
 duplex half
 !
!
interface Serial1/0
 ip address 1.1.1.1 255.255.255.252
 serial restart-delay 0
 clock rate 64000
 !

router ospf 1
 router-id 2.2.2.1
 log-adjacency-changes
 network 1.1.1.0 0.0.0.3 area 0
 network 20.0.0.0 0.31.255.255 area 0


___________________________________________________________________________________

R3:

interface Loopback20
 ip address 20.20.20.1 255.255.255.0
 !
!
interface Loopback21
 ip address 20.20.21.1 255.255.255.0
 !
!
interface Loopback22
 ip address 20.20.22.1 255.255.255.0
 !
!
interface FastEthernet0/0
 ip address 15.15.15.1 255.255.255.0
 duplex half
 !
!
interface Serial1/0
 ip address 1.1.1.2 255.255.255.252
 serial restart-delay 0
 !
!
interface Serial1/1
 no ip address
 shutdown
 serial restart-delay 0
 !
!
interface Serial1/2
 no ip address
 shutdown
 serial restart-delay 0
 !
!
interface Serial1/3
 no ip address
 shutdown
 serial restart-delay 0
 !
!
!
router ospf 2
 router-id 3.3.3.1
 log-adjacency-changes
 network 1.1.1.0 0.0.0.3 area 0
 network 15.15.15.0 0.0.0.255 area 1
 network 20.20.20.0 0.0.0.255 area 1
 network 20.20.21.0 0.0.0.255 area 1
 network 20.20.22.0 0.0.0.255 area 1
___________________________________________________________________________________

R4:

interface Loopback1
 ip address 192.168.2.1 255.255.255.0
 !
!
interface Loopback2
 ip address 192.168.1.1 255.255.255.0
 !
!
interface Loopback3
 ip address 192.168.3.1 255.255.255.0
 !
!
interface FastEthernet0/0
 ip address 15.15.15.2 255.255.255.0
 duplex half
 !
!
!
router ospf 2
 router-id 4.4.4.1
 log-adjacency-changes
 redistribute rip metric 25 metric-type 1 subnets
 network 15.15.15.0 0.0.0.255 area 1
!
router rip
 version 2
 network 192.168.1.0
 network 192.168.2.0
 network 192.168.3.0
 no auto-summary
!
____________________________________________________________________________________

The next step is to verify neighborship between the routers

R1:
R1#SH IP OSpf NEighbor

Neighbor ID     Pri   State           Dead Time   Address         Interface
2.2.2.1           1   FULL/BDR        00:00:33    20.0.0.2        FastEthernet0/0


____________________________________________________________________________________

R2:

R2#SH IP OSpf NEighbor

Neighbor ID     Pri   State           Dead Time   Address         Interface
3.3.3.1           0   FULL/  -        00:00:34    1.1.1.2         Serial1/0
1.1.1.1           1   FULL/DR         00:00:37    20.0.0.1        FastEthernet0/0
___________________________________________________________________________________


R3:

R3#SH IP OSpf NEighbor

Neighbor ID     Pri   State           Dead Time   Address         Interface
2.2.2.1           0   FULL/  -        00:00:37    1.1.1.1         Serial1/0
4.4.4.1           1   FULL/BDR        00:00:30    15.15.15.2      FastEthernet0/0
___________________________________________________________________________________

R4:

R4#SH IP OSpf NEighbor

Neighbor ID     Pri   State           Dead Time   Address         Interface
3.3.3.1           1   FULL/DR         00:00:34    15.15.15.1      FastEthernet0/0
___________________________________________________________________________________

Note: Pay attention to the state of the neighbor:


  1. R1 identifies R2 as the BDR for the broadcast network: 

Neighbor ID     Pri   State           Dead Time   Address         Interface
2.2.2.1           1   FULL/BDR        00:00:33    20.0.0.2        FastEthernet0/0

  1. R2 identifies R1 as the DR for the broadcast network:
  2. R2 identifies R3 as FULL/-, this happens on Point-to-Point networks where only one router is connected at the other end of the link.


Neighbor ID     Pri   State           Dead Time   Address         Interface
3.3.3.1           0   FULL/  -        00:00:34    1.1.1.2         Serial1/0
1.1.1.1           1   FULL/DR         00:00:37    20.0.0.1        FastEthernet0/0

___________________________________________________________________________________

Let's take a brief look at LSA's and LSA types:

LSA type 1 (Router): Type 1 LSA's are sent by all routers in an area describing their directly connected networks. These LSA's do not leave the area.

LSA type 2 (Network): Type 2 LSA's are sent by the DR in a non-broadcast multiaccess network describing all connected routers on the segment. These LSA's do not leave the area

LSA type 3 (Summary): Type 3 LSA's are sent by the ABR to describe a route to neighbors outside of the area

LSA type 4 (Summary): Type 4 LSA's are sent by the ABR describing the IP address of the ASBR.

LSA type 5 (External): Type 5 LSA's are sent by the ASBR describing routes that are being redistributed into the area.

LSA type 7 Not so Stubby area(NSSA): Are sourced from a router in a NSSA
___________________________________________________________________________________


 Let's take a look at the OSPF database

R1:

R1#sh ip ospf database

            OSPF Router with ID (1.1.1.1) (Process ID 1)

                Router Link States (Area 0)

Link ID         ADV Router      Age         Seq#       Checksum Link count
1.1.1.1         1.1.1.1         1534        0x80000006 0x0077B4 4
2.2.2.1         2.2.2.1         1488        0x80000006 0x0058EF 3
3.3.3.1         3.3.3.1         1284        0x80000003 0x00E898 2

                Net Link States (Area 0)

Link ID         ADV Router      Age         Seq#       Checksum
20.0.0.1        1.1.1.1         1534        0x80000002 0x006CC7

                Summary Net Link States (Area 0)

Link ID         ADV Router      Age         Seq#       Checksum
15.15.15.0      3.3.3.1         1284        0x80000002 0x0025DE
20.20.20.1      3.3.3.1         1284        0x80000002 0x00668D
20.20.21.1      3.3.3.1         1284        0x80000002 0x005B97
20.20.22.1      3.3.3.1         1284        0x80000002 0x0050A1

                Summary ASB Link States (Area 0)

Link ID         ADV Router      Age         Seq#       Checksum
4.4.4.1         3.3.3.1         775         0x80000002 0x009A88

                Type-5 AS External Link States

Link ID         ADV Router      Age         Seq#       Checksum Tag
192.168.1.0     4.4.4.1         715         0x80000002 0x007132 0
192.168.2.0     4.4.4.1         975         0x80000002 0x00663C 0
192.168.3.0     4.4.4.1         975         0x80000002 0x005B46 0


___________________________________________________________________________________

R2:


R2#SH IP OSpf Database

            OSPF Router with ID (2.2.2.1) (Process ID 1)

                Router Link States (Area 0)

Link ID         ADV Router      Age         Seq#       Checksum Link count
1.1.1.1         1.1.1.1         133         0x80000007 0x0075B5 4
2.2.2.1         2.2.2.1         116         0x80000007 0x0056F0 3
3.3.3.1         3.3.3.1         1921        0x80000003 0x00E898 2

                Net Link States (Area 0)

Link ID         ADV Router      Age         Seq#       Checksum
20.0.0.1        1.1.1.1         133         0x80000003 0x006AC8

                Summary Net Link States (Area 0)

Link ID         ADV Router      Age         Seq#       Checksum
15.15.15.0      3.3.3.1         1921        0x80000002 0x0025DE
20.20.20.1      3.3.3.1         1921        0x80000002 0x00668D
20.20.21.1      3.3.3.1         1921        0x80000002 0x005B97
20.20.22.1      3.3.3.1         1921        0x80000002 0x0050A1

                Summary ASB Link States (Area 0)

Link ID         ADV Router      Age         Seq#       Checksum
4.4.4.1         3.3.3.1         1412        0x80000002 0x009A88

                Type-5 AS External Link States

Link ID         ADV Router      Age         Seq#       Checksum Tag
192.168.1.0     4.4.4.1         1352        0x80000002 0x007132 0
192.168.2.0     4.4.4.1         1611        0x80000002 0x00663C 0
192.168.3.0     4.4.4.1         1611        0x80000002 0x005B46 0


___________________________________________________________________________________

R3:

R3#SH IP OSpf DAtabase

            OSPF Router with ID (3.3.3.1) (Process ID 2)

                Router Link States (Area 0)

Link ID         ADV Router      Age         Seq#       Checksum Link count
1.1.1.1         1.1.1.1         271         0x80000007 0x0075B5 4
2.2.2.1         2.2.2.1         254         0x80000007 0x0056F0 3
3.3.3.1         3.3.3.1         31          0x80000004 0x00E699 2

                Net Link States (Area 0)

Link ID         ADV Router      Age         Seq#       Checksum
20.0.0.1        1.1.1.1         271         0x80000003 0x006AC8

                Summary Net Link States (Area 0)

Link ID         ADV Router      Age         Seq#       Checksum
15.15.15.0      3.3.3.1         31          0x80000003 0x0023DF
20.20.20.1      3.3.3.1         31          0x80000003 0x00648E
20.20.21.1      3.3.3.1         31          0x80000003 0x005998
20.20.22.1      3.3.3.1         31          0x80000003 0x004EA2

                Summary ASB Link States (Area 0)

Link ID         ADV Router      Age         Seq#       Checksum
4.4.4.1         3.3.3.1         1548        0x80000002 0x009A88

                Router Link States (Area 1)

Link ID         ADV Router      Age         Seq#       Checksum Link count
3.3.3.1         3.3.3.1         1797        0x80000006 0x008945 4
4.4.4.1         4.4.4.1         1746        0x80000004 0x00981E 1

                Net Link States (Area 1)

Link ID         ADV Router      Age         Seq#       Checksum
15.15.15.1      3.3.3.1         1797        0x80000002 0x0018D1

                Summary Net Link States (Area 1)

Link ID         ADV Router      Age         Seq#       Checksum
1.1.1.0         3.3.3.1         33          0x80000003 0x00836D
20.0.0.0        3.3.3.1         33          0x80000003 0x0042B8
45.45.45.1      3.3.3.1         33          0x80000003 0x0069FC
45.45.46.1      3.3.3.1         33          0x80000003 0x005E07
45.45.47.1      3.3.3.1         33          0x80000003 0x005311

                Type-5 AS External Link States

Link ID         ADV Router      Age         Seq#       Checksum Tag
192.168.1.0     4.4.4.1         1488        0x80000002 0x007132 0
192.168.2.0     4.4.4.1         1748        0x80000002 0x00663C 0
192.168.3.0     4.4.4.1         1748        0x80000002 0x005B46 0
___________________________________________________________________________________

R4:

R4#SH IP ospf database

            OSPF Router with ID (4.4.4.1) (Process ID 2)

                Router Link States (Area 1)

Link ID         ADV Router      Age         Seq#       Checksum Link count
3.3.3.1         3.3.3.1         1952        0x80000006 0x008945 4
4.4.4.1         4.4.4.1         1900        0x80000004 0x00981E 1

                Net Link States (Area 1)

Link ID         ADV Router      Age         Seq#       Checksum
15.15.15.1      3.3.3.1         1952        0x80000002 0x0018D1

                Summary Net Link States (Area 1)

Link ID         ADV Router      Age         Seq#       Checksum
1.1.1.0         3.3.3.1         188         0x80000003 0x00836D
20.0.0.0        3.3.3.1         188         0x80000003 0x0042B8
45.45.45.1      3.3.3.1         188         0x80000003 0x0069FC
45.45.46.1      3.3.3.1         188         0x80000003 0x005E07
45.45.47.1      3.3.3.1         188         0x80000003 0x005311

                Type-5 AS External Link States

Link ID         ADV Router      Age         Seq#       Checksum Tag
192.168.1.0     4.4.4.1         1641        0x80000002 0x007132 0
192.168.2.0     4.4.4.1         1902        0x80000002 0x00663C 0
192.168.3.0     4.4.4.1         1902        0x80000002 0x005B46 0
___________________________________________________________________________________

Let's verify the contents of the routing table across the network

R1:
R1#SH IP ROUTE
Codes: L - local, C - connected, S - static, 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
       i - IS-IS, su - IS-IS summary, 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, + - replicated route

Gateway of last resort is not set

      1.0.0.0/30 is subnetted, 1 subnets
O        1.1.1.0 [110/65] via 20.0.0.2, 01:27:32, FastEthernet0/0
      15.0.0.0/24 is subnetted, 1 subnets
O IA     15.15.15.0 [110/66] via 20.0.0.2, 01:23:14, FastEthernet0/0
      20.0.0.0/8 is variably subnetted, 5 subnets, 2 masks
O IA     20.20.20.1/32 [110/66] via 20.0.0.2, 01:25:49, FastEthernet0/0
O IA     20.20.21.1/32 [110/66] via 20.0.0.2, 01:25:49, FastEthernet0/0
O IA     20.20.22.1/32 [110/66] via 20.0.0.2, 01:25:39, FastEthernet0/0
O E1  192.168.1.0/24 [110/91] via 20.0.0.2, 01:17:27, FastEthernet0/0
O E1  192.168.2.0/24 [110/91] via 20.0.0.2, 01:18:12, FastEthernet0/0
O E1  192.168.3.0/24 [110/91] via 20.0.0.2, 01:18:12, FastEthernet0/0
R1#

__________________________________________________________________________

R2:

Gateway of last resort is not set

      1.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C        1.1.1.0/30 is directly connected, Serial1/0
L        1.1.1.1/32 is directly connected, Serial1/0
      15.0.0.0/24 is subnetted, 1 subnets
O IA     15.15.15.0 [110/65] via 1.1.1.2, 01:14:33, Serial1/0
      20.0.0.0/8 is variably subnetted, 5 subnets, 2 masks
C        20.0.0.0/11 is directly connected, FastEthernet0/0
L        20.0.0.2/32 is directly connected, FastEthernet0/0
O IA     20.20.20.1/32 [110/65] via 1.1.1.2, 01:17:08, Serial1/0
O IA     20.20.21.1/32 [110/65] via 1.1.1.2, 01:17:08, Serial1/0
O IA     20.20.22.1/32 [110/65] via 1.1.1.2, 01:16:58, Serial1/0
      45.0.0.0/32 is subnetted, 3 subnets
O        45.45.45.1 [110/2] via 20.0.0.1, 01:19:01, FastEthernet0/0
O        45.45.46.1 [110/2] via 20.0.0.1, 01:19:03, FastEthernet0/0
O        45.45.47.1 [110/2] via 20.0.0.1, 01:19:03, FastEthernet0/0
O E1  192.168.1.0/24 [110/90] via 1.1.1.2, 01:08:48, Serial1/0
O E1  192.168.2.0/24 [110/90] via 1.1.1.2, 01:09:34, Serial1/0
O E1  192.168.3.0/24 [110/90] via 1.1.1.2, 01:09:34, Serial1/0
R2#
__________________________________________________________________________________


R3:

Gateway of last resort is not set

      1.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C        1.1.1.0/30 is directly connected, Serial1/0
L        1.1.1.2/32 is directly connected, Serial1/0
      15.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C        15.15.15.0/24 is directly connected, FastEthernet0/0
L        15.15.15.1/32 is directly connected, FastEthernet0/0
      20.0.0.0/8 is variably subnetted, 7 subnets, 3 masks
O        20.0.0.0/11 [110/65] via 1.1.1.1, 01:18:08, Serial1/0
C        20.20.20.0/24 is directly connected, Loopback20
L        20.20.20.1/32 is directly connected, Loopback20
C        20.20.21.0/24 is directly connected, Loopback21
L        20.20.21.1/32 is directly connected, Loopback21
C        20.20.22.0/24 is directly connected, Loopback22
L        20.20.22.1/32 is directly connected, Loopback22
      45.0.0.0/32 is subnetted, 3 subnets
O        45.45.45.1 [110/66] via 1.1.1.1, 01:18:10, Serial1/0
O        45.45.46.1 [110/66] via 1.1.1.1, 01:18:10, Serial1/0
O        45.45.47.1 [110/66] via 1.1.1.1, 01:18:10, Serial1/0
O E1  192.168.1.0/24 [110/26] via 15.15.15.2, 01:09:37, FastEthernet0/0
O E1  192.168.2.0/24 [110/26] via 15.15.15.2, 01:10:27, FastEthernet0/0
O E1  192.168.3.0/24 [110/26] via 15.15.15.2, 01:10:28, FastEthernet0/0
R3#
___________________________________________________________________________________

R4:

Gateway of last resort is not set

      1.0.0.0/30 is subnetted, 1 subnets
O IA     1.1.1.0 [110/65] via 15.15.15.1, 01:13:50, FastEthernet0/0
      15.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C        15.15.15.0/24 is directly connected, FastEthernet0/0
L        15.15.15.2/32 is directly connected, FastEthernet0/0
      20.0.0.0/8 is variably subnetted, 4 subnets, 2 masks
O IA     20.0.0.0/11 [110/66] via 15.15.15.1, 01:13:50, FastEthernet0/0
O        20.20.20.1/32 [110/2] via 15.15.15.1, 01:13:50, FastEthernet0/0
O        20.20.21.1/32 [110/2] via 15.15.15.1, 01:13:50, FastEthernet0/0
O        20.20.22.1/32 [110/2] via 15.15.15.1, 01:13:50, FastEthernet0/0
      45.0.0.0/32 is subnetted, 3 subnets
O IA     45.45.45.1 [110/67] via 15.15.15.1, 01:13:50, FastEthernet0/0
O IA     45.45.46.1 [110/67] via 15.15.15.1, 01:13:50, FastEthernet0/0
O IA     45.45.47.1 [110/67] via 15.15.15.1, 01:13:51, FastEthernet0/0
      192.168.1.0/24 is variably subnetted, 2 subnets, 2 masks
C        192.168.1.0/24 is directly connected, Loopback2
L        192.168.1.1/32 is directly connected, Loopback2
      192.168.2.0/24 is variably subnetted, 2 subnets, 2 masks
C        192.168.2.0/24 is directly connected, Loopback1
L        192.168.2.1/32 is directly connected, Loopback1
      192.168.3.0/24 is variably subnetted, 2 subnets, 2 masks
C        192.168.3.0/24 is directly connected, Loopback3
L        192.168.3.1/32 is directly connected, Loopback3
R4#
 _________________________________________________________________________________

Note: I will verify end to end connectivity, if all is well i should be able to ping from R1 to R4 and vice versa.

R1:
R1#PING 192.168.3.1 r 20
Type escape sequence to abort.
Sending 20, 100-byte ICMP Echos to 192.168.3.1, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!
Success rate is 100 percent (20/20), round-trip min/avg/max = 44/64/108 ms
R1#
__________________________________________________________________________________

R4:
R4(config)#do ping 45.45.47.1 r 20

Type escape sequence to abort.
Sending 20, 100-byte ICMP Echos to 45.45.47.1, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!
Success rate is 100 percent (20/20), round-trip min/avg/max = 36/70/112 ms
R4(config)#

Note: Everything looks good, this lab config was simple and straight forward. The difficult part is knowing where to look when there are anomalies on the network. Troubleshooting is a MUST have skill. Later in this lab there will be a lot of issues that must be resolved. Once we have a good baseline understanding of the network, the troubleshooting steps will fall into place, hopefully :-)