Lab1 Latest Update

Disclaimer: CCIE SPv3 Lab Exam Workbook is designed to provide extensive practical technical information to
help candidates in the preparation for CISCO Systems' CCIE Service Provider Lab Exam. We do not take liability or
responsibility to any person or entity with respect to loss or damage caused by the information presented in the
workbook.
Cisco, Cisco Systems, and CCIE (Cisco Certified Internetwork Expert) are registered trademarks of Cisco Systems,
Inc. and of its affiliates in the USA and other countries.
The information presented in the workbook is not necessarily related to Cisco Systems, Inc. This workbook is not
affiliated by, endorsed by or sponsored by Cisco Systems, Inc. This workbook provides detailed and comprehensive
practical's for the preparation of CCIE SPv3 Lab Exam but it cannot be used as a replacement of other
supplementary books or prescribed materials.
This workbook is prepared for the individual candidates who have purchase it from us under non-disclosure
agreement. Imitation, copying, editing or posting contents of the workbook over the internet is part of copyright
and non-disclosure agreement violation.
copyright 2014 CcieperfectSolutions.com, All rights reserved.
Rev 3.1 12June14 Copyright CcieperfectSolutions.com Guaranteed pass CCIE SPv3 in next attempt!!! Page 2
Lab A7
Section 1 -
1.1 ISIS for IPv4 Troubleshooting

1.4 OSPF for IPv6 Troubleshooting
1.5 ISIS Levels
1.6 OSPFv3 Hello Timers
1.7 IBGP IPv4 Unicast Troubleshooting
1.9 EBGP IPv4 Unicast
1.11 BGP Path Selection
1.12 MPLS LDP Troubleshooting
1.13 MPLS Traffic Engineering
1.14 MPLS Traffic Engineering Link Protection
1.15 IPv4 PIM SM Troubleshooting
1.16 IPv4 RP
1.17 IPv4 MSDP
1.18 MPLS LDP Authentication
Section 2 -
2.1 PPP Multilink
Section 3 -
3.1 IBGP VPNv4 Troubleshooting

3.3 Intra AS VPNv4
3.4 Intra AS VPNv6
3.5 Inter AS VPNv4
3.6 Inter AS VPNv6
3.7 Carrier Supporting Carrier 1
3.9 Multicast VPN
3.10 BGP IPv4 MDT
Section 4 -
4.1 PPP over MPLS

4.2 Frame-Relay over L2TPv3
4.3 Virtual Private LAN Services
Lab A8
Section 1 -

1.5 ISIS Level
1.6 OSPF Failure Detection
1.11 BGP Path Selection
1.12 MPLS LDP Troubleshooting
1.13 MPLS Traffic Engineering
1.14 MPLS Traffic Engineering Link Protection
1.15 IPv4 PIM SM Troubleshooting
1.16 IPv4 RP
1.17 IPv4 MSDP
1.18 MPLS LDP Authentication
Section 2 -
2.1 PPP Multilink
Section 3 -

3.3 Intra AS VPNv4
3.4 Intra AS VPNv6
3.5 Inter AS VPNv4
3.6 Inter AS VPNv6
3.9 Multicast VPN
Section 4 -
4.1 PPP over MPLS

4.2 Frame-Relay over L2TPv3
4.3 Virtual Private LAN Services
Single Topic Learning Labs Kit
Section 1 -
1.1 Implement ISIS

1.1.0 ISIS Basics
1.1.1 ISIS Configuration
1.1.2 ISIS Level 1
1.1.3 ISIS Level 2
1.1.4 ISIS Multi Level
1.1.5 ISIS Route Leaking
1.1.6 ISIS Passive Interface
1.1.7 ISIS Network Types
1.1.8 ISIS DIS Election
1.1.9 ISIS Metric Types
1.1.10 ISIS Multi Instance
1.1.11 ISIS Path Selection
1.1.12 ISIS Timers
1.1.13 ISIS Optimization
1.1.14 ISIS Route Filtering
1.1.15 ISIS Authentication
1.1.16 ISIS Route Summarization
1.1.17 ISIS BFD
1.1.18 ISIS Single Topology
1.1.19 ISIS Multi Topology
1.1.20 Troubleshooting ISIS Adjacency Issues
1.2 Implement OSPF

1.2.0 OSPF Basics
1.2.1 OSPF Configuration
1.2.2 OSPF DR Election
1.2.3 OSPF Area Types
1.2.3 OSPF Virtual Links
1.2.4 OSPF Network Types
1.2.5 OSPF Timers
1.2.6 OSPF Optimization
1.2.7 OSPF Route Filtering
1.2.8 OSPF Route Summarization
1.2.9 OSPF Path Selection
1.2.10 OSPF BFD
1.2.11 OSPF Authentication
1.2.12 OSPFv3 Basics
1.2.13 OSPFv3 Configuration
1.2.14 OSPFv3 DR Election
1.2.15 OSPFv3 Area Types
1.2.16 OSPFv3 Virtual Links
1.2.17 OSPFv3 Network Types
1.2.18 OSPFv3 Timers
1.2.19 OSPFv3 Optimization
1.2.20 OSPFv3 Route Filtering
1.2.21 OSPFv3 Route Summarization
1.2.22 OSPFv3 Redistribution
1.2.23 OSPFv3 Path Selection
1.2.24 OSPFv3 BFD
1.2.25 OSPFv3 Authentication
1.2.26 Troubleshooting OSPF Adjacency Issues
1.3 Implement BGP
1.3.0 BGP Basics
1.3.1 BGP Configuration
1.3.2 BGP Neighbor Types
1.3.3 BGP Next Hop Processing
1.3.4 BGP Route Reflectors
1.3.5 BGP Attributes Weight
1.3.6 BGP Attributes Local Preference
1.3.7 BGP Attributes AS-PATH
1.3.8 BGP Attributes MED
1.3.9 BGP Attributes Community
1.3.10 BGP Attributes Origin
1.3.11 BGP Route Redistribution
1.3.12 BGP Conditional Advertisements
1.3.13 BGP Route Filtering
1.3.14 BGP Timers
1.3.15 BGP Multipath
1.3.16 BGP Authentication
1.3.17 BGP Features
1.4 Implement MPLS

1.4.0 LDP Basics
1.4.1 LDP Autoconfig
1.4.2 LDP Authentication
1.4.3 LDP Filtering
1.4.4 LDP IGP Synchronization
1.4.5 LDP Session Protection
1.4.6 LDP TTL Propagation
1.5 Implement Traffic Engineering

1.5.0 MPLS Tunneling
1.5.1 Traffic Engineering with OSPF
1.5.2 Traffic Engineering with IS-IS
1.5.3 Traffic Engineering Explicit Paths
1.5.4 Traffic Engineering Bandwidth Reservations
1.5.5 Traffic Engineering Metric Manipulation
1.5.6 Traffic Engineering with Static Routing
1.5.7 Traffic Engineering Targeted LDP
1.5.8 Traffic Engineering Fast Reroute
1.5.9 Inter-Area Traffic Engineering
1.5.10 Inter-AS Traffic Engineering
1.6 Multicast
1.6.0 PIM Configuration
1.6.1 IGMP Configuration
1.6.2 Static RP
1.6.3 Auto RP
1.6.4 BSR
1.6.5 MSDP
1.6.6 Multicast Filtering
1.6.7 MP BGP
1.6.8 SSM
Section 2 -
2.1.1 Ethernet
2.1.2 Frame Relay
Section 3 -
3.1Implement MPLS L3 VPN

3.1.0 MPLS L3 VPN with Static Routing
3.1.1 MPLS L3 VPN with BGP
3.1.2 MPLS L3 VPN with OSPF
3.1.3 MPLS L3 VPN and OSPF Sham-Links
3.1.4 MPLS L3 VPN and OSPF Domain-ID
3.1.5 MPLS L3 VPN with RIPv2
3.1.6 MPLS L3 VPN with EIGRP
3.1.7 MPLS L3 VPN with EIGRP SOO
3.1.8 MPLS L3 VPN with Policy Routing
3.1.9 MPLS L3 VPN VPNv4 Route Reflection
3.1.10 Multi-VRF VRF Lite
3.1.11 Multi-VRF Source Selection
3.1.12 MPLS L3VPN Inter-AS Option A
3.1.13 MPLS L3VPN Inter-AS Option B
3.1.14 MPLS L3VPN Inter-AS Option C
3.1.15 MPLS L3VPN Inter-AS Option C(iBGP Label)
3.1.16 MPLS L3VPN with NAT
3.1.17 MPLS L3VPN with Internet Access
3.1.18 MPLS L3VPN Carrier Supporting Carrier
3.1.19 MPLS L3VPN Multicast VPN
3.1.20 6PE
3.1.21 6VPE
Section 4 -
4.1Implement MPLS L2 VPN

4.1.0 ATOM over Ethernet
4.1.1 ATOM over PPP
4.1.2 ATOM over Frame Relay
4.1.3 ATOM over Interworking
4.1.4 L2TPv3
4.1.5 L2TPv3 Interworking
4.1.6 VPLS
Section 5 -
5.1.1 IOS XR Configuration

5.1.2 To be updated in next release
3.1
Table 1 : Loopback Interface Addresses
R1 Loopback0 9.9.0.1/32 2002:9:9::1/128
Loopback1 172.9.0.1/32 2002:172:9::1/128
R2 Loopback0 9.9.0.2/32 2002:9:9::2/128
Loopback1 172.9.0.2/32 2002:172:9::2/128
Loopback2 9.9.0.22/32
R3 Loopback0 9.9.0.3/32 2002:9:9::3/128
Loopback1 172.9.0.3/32 2002:172:9::3/128
R4 Loopback0 9.9.0.4/32 2002:9:9::4/128
Loopback1 172.9.0.4/32
R5 Loopback0 9.9.0.5/32 2002:9:9::5/128
R6 Loopback0 9.9.0.6/32 2002:9:9::6/128
R7 Loopback0 9.9.0.7/32 2002:9:9::7/128
Loopback1 172.9.0.7/32
R8 Loopback0 9.9.0.8/32 2002:9:9::8/128
Loopback1 172.9.0.8/32 2002:172:9::8/128
Loopback2 9.9.0.88/32
R9 Loopback0 9.9.0.9/32 2002:9:9::9/128
Loopback1 172.9.0.9/32
R10 Loopback0 9.9.0.10/32 2002:9:9::10/128
Loopback1 172.9.0.10/32
R11 Loopback0 172.9.0.11/32 2002:172:9::11/128
Loopback1 192.9.0.11/32
R12 Loopback0 172.9.0.12/32 2002:172:9::12/128
Loopback1 192.9.0.12/32
R13 Loopback0 192.9.0.13/32
R14 Loopback0 172.9.0.14/32 2002:172:9::14/128
Loopback1 192.9.0.14/32
R15 Loopback0 172.9.0.15/32 2002:172:9::15/128
Loopback1 192.9.0.15/32
R16 Loopback0 192.9.0.16/32
R17 Loopback0 172.9.0.17/32 2002:172:9::17/128
Loopback1 192.9.0.17/32
R18 Loopback0 172.9.0.18/32 2002:172:9::18/128
Loopback1 192.9.0.18/32
R19 Loopback0 192.9.0.19/32
R20 Loopback0 172.9.0.20/32
R21 Loopback0 172.9.0.21/32
R22 Loopback0 172.9.0.22/32
R23 Loopback0 172.9.0.23/32
R24 Loopback0 172.9.0.24/32
Table 2 : Loopback Interface Multicast Groups
R1 Loopback0 239.255.0.1
R2 Loopback0 239.255.0.2
R3 Loopback0 239.255.0.3
R4 Loopback0 239.255.0.4
R5 Loopback0 239.255.0.5
R6 Loopback0 239.255.0.6
R7 Loopback0 239.255.0.7
R8 Loopback0 239.255.0.8
R9 Loopback0 239.255.0.9
R10 Loopback0 239.255.0.10
R11 Loopback0 239.255.172.11
R12 Loopback0 239.255.172.12
R13 Loopback0 239.255.172.13
R14 Loopback0 239.255.172.14
R15 Loopback0 239.255.172.15
Section 1
Implement, Optimize and Troubleshooting of Core IP Technologies

ISIS IPv4 routing is pre configured in AS9 as per below table:
Router Area Interface
R2 47.0009 Loopback0
47.0009 GigabiEthernet0/0/0/0.23
47.0009 Ethernet0/0
47.0009 Ethernet0/1
47.0009 Ethernet0/2
47.0009 Ethernet0/0
47.0009 Ethernet0/1
47.0009 Ethernet0/0
47.0009 Ethernet0/1
R2 and R5 are unable to formISIS adjacency, fix the problem so that devices in AS 9 can get each other routes via
ISIS.
R3 and R7 are unable to form ISIS adjacency, fix the problem so that all devices in AS9 can get each other routes
via ISIS.
Pre Configurations :
R2
RP/0/0/CPU0:CPS_R0_R2# show running-config interface loopback 0

Sat Jun 7 17:54:07.273 UTC
interface Loopback0
ipv4 address 9.9.0.2 255.255.255.255
ipv6 address 2002:9:9::2/128
!
RP/0/0/CPU0:CPS_R0_R2# show running-config interface gigabitEthernet 0/0/0/0.23

Sat Jun 7 17:54:38.691 UTC
interface GigabitEthernet0/0/0/0.23
ipv4 address 9.9.23.2 255.255.255.0
ipv6 address 2002:9:9:23::2/64
encapsulation dot1q 12
!
RP/0/0/CPU0:CPS_R0_R2# show running-config interface gigabitEthernet 0/0/0/0.25

Sat Jun 7 18:07:59.926 UTC
ipv4 address 9.9.25.2 255.255.255.0
ipv6 address 2002:9:9:25::2/64
!
RP/0/0/CPU0:CPS_R0_R2# show running-config router isis abc

Sat Jun 7 18:10:37.745 UTC
router isis abc
net 47.0009.0000.0000.2222.00
address-family ipv4 unicast
metric-style wide
!
single-topology
!
interface Loopback0
passive
!
!
!
!
!
!
!
R3
RP/0/0/CPU0:CPS_R0_R3#show running-config interface loopback 0

Sat Jun 7 18:03:21.975 UTC
interface Loopback0
ipv4 address 9.9.0.3 255.255.255.255
ipv6 address 2002:9:9::3/128
!
RP/0/0/CPU0:CPS_R0_R3#show running-config interface gigabitEthernet 0/0/0/0.23

Sat Jun 7 18:03:46.274 UTC
ipv4 address 9.9.23.3 255.255.255.0
ipv6 address 2002:9:9:23::3/64
!

Sat Jun 7 18:03:51.093 UTC
ipv4 address 9.9.34.3 255.255.255.0
ipv6 address 2002:9:9:34::3/64
!

Sat Jun 7 18:03:54.953 UTC
ipv4 address 9.9.35.3 255.255.255.0
ipv6 address 2002:9:9:35::3/64
!

Sat Jun 7 18:03:58.593 UTC
ipv4 address 9.9.37.3 255.255.255.0
ipv6 address 2002:9:9:37::3/64
!
RP/0/0/CPU0:CPS_R0_R3#
RP/0/0/CPU0:CPS_R0_R3#show running-config router isis abc
Sat Jun 7 18:11:55.840 UTC
router isis abc
net 47.0009.0000.0000.3333.00
metric-style wide
!
single-topology
!
interface Loopback0
passive
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
R4

Sat Jun 7 18:14:43.749 UTC
interface Loopback0
ipv4 address 9.9.0.4 255.255.255.255
ipv6 address 2002:9:9::4/128
!

Sat Jun 7 18:15:12.367 UTC
ipv4 address 9.9.34.4 255.255.255.0
ipv6 address 2002:9:9:34::4/64
!

Sat Jun 7 18:15:34.035 UTC
ipv4 address 9.9.45.4 255.255.255.0
ipv6 address 2002:9:9:45::4/64
!

Sat Jun 7 18:15:38.555 UTC
ipv4 address 9.9.48.4 255.255.255.0
ipv6 address 2002:9:9:48::4/64
!
RP/0/0/CPU0:CPS_R0_R4#show running-config router isis abc

Sat Jun 7 18:16:20.082 UTC
router isis abc
net 47.0009.0000.0000.4444.00
metric-style wide
!
single-topology
!
interface Loopback0
passive
!
!
!
!
!
!
!
!
!
!
!
!
!
R5
CPS_R0_R5#show running-config interface loopback 0

Building configuration...
Current configuration : 181 bytes

!
interface Loopback0
ip address 9.9.0.5 255.255.255.255
ip router isis
ip pim sparse-mode
ip igmp join-group 239.255.0.5
ipv6 address 2002:9:9::5/128
ipv6 router isis
end
CPS_R0_R5#show running-config interface ethernet 0/0


!
interface Ethernet0/0
bandwidth 100000
ip address 9.9.45.5 255.255.255.0
ip router isis
ip pim sparse-mode
ipv6 address 2002:9:9:45::5/64
ipv6 router isis
mpls ip
end


!
bandwidth 100000
ip address 9.9.25.5 255.255.255.0
ip router isis
ip pim sparse-mode
ipv6 address 2002:9:9:25::5/64
ipv6 router isis
mpls ip
isis protocol shutdown
end

!
bandwidth 100000
ip address 9.9.35.5 255.255.255.0
ip router isis
ip pim sparse-mode
ipv6 address 2002:9:9:35::5/64
ipv6 router isis
mpls ip
end
CPS_R0_R5#show running-config | section router isis

ip router isis
ipv6 router isis
ip router isis
ipv6 router isis
ip router isis
ipv6 router isis
ip router isis
ipv6 router isis
router isis
net 47.0009.0000.0000.5555.00
metric-style wide
CPS_R0_R5#
R7


!
interface Loopback0
ip address 9.9.0.7 255.255.255.255
ip router isis
ip pim sparse-mode
ipv6 address 2002:9:9::7/128
ipv6 router isis


!
bandwidth 100000
ip address 9.9.37.7 255.255.255.0
ip router isis
ip pim sparse-mode
ipv6 address 2002:9:9:37::7/64
ipv6 router isis
mpls ip
isis network point-to-point


!
bandwidth 100000
ip address 9.9.78.7 255.255.255.0
ip router isis
ip pim sparse-mode
ipv6 address 2002:9:9:78::7/64
mpls ip

ip router isis
ipv6 router isis
ip router isis
ipv6 router isis
ip router isis
router isis
net 47.0009.0000.0000.7777.00
metric-style wide
CPS_R0_R7#
R8


!
interface Loopback0
ip address 9.9.0.8 255.255.255.255
ip router isis
ip pim sparse-mode
ipv6 address 2002:9:9::8/128
ipv6 router isis


!
bandwidth 100000
ip address 9.9.48.8 255.255.255.0
ip router isis
ip pim sparse-mode
ipv6 address 2002:9:9:48::8/64
ipv6 router isis
mpls ip


!
bandwidth 100000
ip address 9.9.78.8 255.255.255.0
ip router isis
ip pim sparse-mode
ipv6 address 2002:9:9:78::8/64
ipv6 router isis
mpls ip

ip router isis
ipv6 router isis
ip router isis
ipv6 router isis
ip router isis
ipv6 router isis
router isis
net 47.0009.0000.0000.8888.00
metric-style wide
CPS_R0_R8#
Pre Configuration Verification:
G0/0/0/0.23 23.2 G0/0/0/0.23 23.3 G0/0/0/0.37 37.7

VLAN 12 VLAN 12 VLAN 15 E0/0 37.7
G0/0/0/0.35 35.3
G0/4/0/0.25 25.2 VLAN 17
VLAN 11 G0/0/0/0.34 34.4
VLAN 14
E0/1 78.7
G0/0/0/0.34 34.3
E0/2 35.5
E0/1 25.5 VLAN 14
VLAN 17 E0/1 78.8
VLAN 11
E0/0 45.5 G0/0/0/0.45 45.4 G0/0/0/0.48 48.4 E0/0 48.8

VLAN 13 VLAN 13 VLAN 16 VLAN 16
There are many IOS and XR commands to verify ISIS, like sh ip protocol (sh protocols on XR), sh clns interface (sh
isis interface on XR), sh clns protocol (sh isis protocol on XR) for checking the ISIS adjacency and for routes sh ip
route isis (sh route isis on XR), sh isis database verbose (same for XR) etc.
Considering the limited time first step should be verifying the ISIS adjacencies, another approach could be verifying
ISIS routing table to find missing networks and then verify adjacencies related to those missing networks
originating device, but better is to verify all the adjacencies first because there are chances to over look when a
route is installed in table from single path which should be installed via multiple paths.
R2
R2 is showing only one neighbor, as per topology it should show two neighbors R3 and R5, let's check quickly for
other devices we'll relook in detailed to fix it.
R3
It looks good, R3 should have 4 neighbors and it has them. R2, R4, R5 and R7 are the neighbors.
R4
It looks good too, R4 should have 3 neighbors and it has those neighbors R3, R5 and R8.
R5
It's not good like we have found for R2. R5 should have 3 neighbors R2, R3 and R8 but R2 is missing.
R7
It looks good, R7 should have 2 neighbors and it has those neighbors R3 and R8.
R8
It looks good too, R8 should have 2 neighbors and it has those neighbors R4 and R7.
All good from ISIS adjacency point of view except for R2 and R5, let's check it in detail:
Is ISIS enabled on R2 interface connecting to R5?
Yes on R2.
Is ISIS enabled on R5 interface connecting to R2?
Amazing, it was really an easy one to catch, if the CLNS processing is disabled nothing will happen from ISIS
prospectives.
Troubleshooting Solutions:


!
bandwidth 100000
ip address 9.9.25.5 255.255.255.0
ip router isis
ip pim sparse-mode
ipv6 address 2002:9:9:25::5/64
ipv6 router isis
mpls ip
isis protocol shutdown
end
CPS_R0_R5#show clns interface e0/1

Ethernet0/1 is up, line protocol is up
CLNS protocol processing disabled
CPS_R0_R5#
Though R5 interface is configured for ISIS routing protocol ISIS protocol operation is in shut down state on the
interface Ethernet0/1, because of the ISIS Protocol operations shut down on interface, nothing is happening.
Lets remove it:
no isis protocol shutdown
Looks good now.
Though it's obvious, let's have look to R2 and R5 ISIS adjacency table:
Now its established.
Looks good.
For the second problem below, lets inject the trouble and check:
R7 is now showing only one neighbor instead of 2.

R3 is missing in table.
No R7 here too.
Let's check in detail on R3:
No DIS election is pointing something related to configuration mismatch, DIS is not elected in ISIS network type
point to point, the output is indicating R3 wants to elect a DIS over the link, it has its priority 64 but unable to
receive remote side priority or response.
R7 has selected itself as DIS because Circuit Id is showing of its own. If you don't wanna checking configuration like
a beginner on interfaces manually, let's do a debug for adjacency packets and see if we can find something:
RP/0/0/CPU0:CPS_R0_R3(config)#logging console debugging

RP/0/0/CPU0:CPS_R0_R3(config)#commit
Sat Jun 7 23:36:20.949 UTC
RP/0/0/CPU0:Jun 7 23:36:21.119 : config[65806]: %MGBL-CONFIG-6-DB_COMMIT : Configuration committed by
user 'cisco'. Use 'show configuration commit changes 1000000010' to view the changes.
RP/0/0/CPU0:CPS_R0_R3(config)#end
RP/0/0/CPU0:CPS_R0_R3# debug isis adjacencies interface gigabitEthernet 0/0/0/0.37
RP/0/0/CPU0:CPS_R0_R3#RP/0/0/CPU0:Jun 7 23:39:50.265 : isis[1006]: SEND L2 LAN IIH on

GigabitEthernet0/0/0/0.37: LAN ID CPS_R0_R3.01, 0 neighbors, Holdtime 30s, Length 68
RP/0/0/CPU0:Jun 7 23:39:50.585 : isis[1006]: SEND L1 LAN IIH on GigabitEthernet0/0/0/0.37: LAN ID
CPS_R0_R3.01, 0 neighbors, Holdtime 30s, Length 68
RP/0/0/CPU0:CPS_R0_R3#undebug all
Looks good, its sending SEND L2 LAN IIH to neighbors.
CPS_R0_R7(config)#logging console
CPS_R0_R7(config)#end
CPS_R0_R7#debug isis adj-packets
IS-IS Adjacency related packets debugging is on for router process null
CPS_R0_R7#
*Jun 7 23:57:12.911: ISIS-Adj: Rec L2 IIH from aabb.cc00.0810 (Ethernet0/1), cir type L1L2, cir id
0000.0000.8888.02, length 74
0000.0000.8888.02, length 74
CPS_R0_R7#
*Jun 7 23:57:13.998: ISIS-Adj: Rec L2 IIH from 000c.2989.3e27 (Ethernet0/0), cir type L1L2, cir id
0000.0000.3333.01, length 68
*Jun 7 23:57:13.998: ISIS-Adj: Multi-point IIH received on point-to-point interface: ignored IIH
*Jun 7 23:57:14.218: ISIS-Adj: Rec L1 IIH from 000c.2989.3e27 (Ethernet0/0), cir type L1L2, cir id
0000.0000.3333.01, length 68
*Jun 7 23:57:14.218: ISIS-Adj: Multi-point IIH received on point-to-point interface: ignored IIH
CPS_R0_R7#un all
We got the issue here too.
Read this quote from Cisco Press article "Integrated IS-IS Routing Protocol Concepts" By Abe Martey:
"IS-IS Adjacencies over Point to Point Media
IS-IS adjacencies on point-to-point links are initialized by receipt of ISHs through the ES-IS protocol. This is
followed by the exchange of point-to-point IIHs. The type of adjacency formed will depend on the parameters
exchanged in the IIHs. The IIHs also are sent periodically over the link to every hello interval to maintain the
adjacency. On Cisco routers, the default hello interval for point-to-point links is 10 seconds.
IS-IS Adjacencies over Multi-access Media
The method specified in ISO 10589 for building adjacencies over broadcast media, such as LANs, differs slightly
from that used on point-to-point links. Some of the significant differences are as follows:
The process is not triggered by receipt of ISHs.

A router sends IIHs on broadcast interfaces as soon as the interface is enabled.
The broadcast medium is modeled as a node, called the pseudonode.

The pseudonode role is played by an elected DIS.
Depending on the configuration, nodes on the LAN broadcast their hellos to well-known Level 1 and Level 2
broadcast MAC addresses.
Two-way communication is confirmed between adjacent nodes by using a three-way handshake procedure made
possible by the presence of an IS Neighbors field in the LAN (Level 1 or Level 2) hello packets. The reliable point-
to-point adjacency formation introduced by TLV Type 240 is similar to this process."

!
bandwidth 100000
ip address 9.9.37.7 255.255.255.0
ip router isis
ip pim sparse-mode
ipv6 address 2002:9:9:37::7/64
ipv6 router isis
mpls ip
end
CPS_R0_R7#show clns interface e0/0

Checksums enabled, MTU 1497, Encapsulation SAP
ERPDUs enabled, min. interval 10 msec.
CLNS fast switching disabled
CLNS SSE switching disabled
DEC compatibility mode OFF for this interface
Next ESH/ISH in 0 seconds
Routing Protocol: IS-IS
Circuit Type: level-1-2
Interface number 0x1, local circuit ID 0x101
Level-1 Metric: 10, Priority: 64, Circuit ID: CPS_R0_R7.01
Level-1 IPv6 Metric: 10
Number of active level-1 adjacencies: 0
Level-2 Metric: 10, Priority: 64, Circuit ID: CPS_R0_R7.01
Level-2 IPv6 Metric: 10
Number of active level-2 adjacencies: 0
Next IS-IS Hello in 2 seconds
if state DOWN
CPS_R0_R7#
Though R7 interface is configured for isis routing protocol, but ISISnetwork type is configured point to point on the
Ethernet0/0, default ISIS network type for Ethernet media (multi-access or broadcast) is network type broadcast.
If the network type is not matching at both ends, ISIS adjacency will not form due to Hello packet type mismatch,
at broadcast network type LAN IIH is sent while for P2P Point to Point IIH is sent.
To short out this problem we need to either change the network type at R3 or simply remove this command on R7.
Lets remove it:
no isis network point-to-point
Looks good, it is showing now both the neighbors.
R3 has also all four adjacencies established.
Web IOU and XRv: If ISIS neighbors are showing in init state or not coming up, add no hello padding at global
router ISIS level for IOS devices. For IOS XR add disable hello-padding at isis interface level.
If still not coming up on IOS device add clns mtu 512 at IOS device interface/sub interface.
If two IOS neighbors are configured to form both IPv4 and IPv6 neighbor ship and one of them is missing ipv6
router isis interface level command IPv4 adjacency will also not form, check it between R7 and R8. Try it by
removing ip router isis for ipv6 adjacency and on IOS XR. {This is based on IOU}.
CPS_R0_R8#debug isis adj

CPS_R0_R8(config-if)#interface ethernet0/1
CPS_R0_R8(config-if)#no shut
CPS_R0_R8(config-if)#end
*Jun 7 21:40:41.225: %LINK-3-UPDOWN: Interface Ethernet0/1, changed state to up
*Jun 7 21:40:42.228: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0/1, changed state to up
*Jun 7 21:40:42.228: ISIS-Adj: Et0/1: Current SYNC state: Normal(1). Event: No SYNC required(1)
*Jun 7 21:40:42.228: ISIS-Adj: Et0/1: New SYNC state: Normal(1)
*Jun 7 21:40:42.228: ISIS-Adj: Et0/1: Current SYNC state: Normal(1). Event: No SYNC required(1)
*Jun 7 21:40:42.228: ISIS-Adj: Et0/1: New SYNC state: Normal(1)
*Jun 7 21:40:42.229: ISIS-Adj: Sending L1 LAN IIH on Ethernet0/1, length 47
0000.0000.7777.02, length 512
*Jun 7 21:40:42.239: ISIS-Adj: New adjacency, level 1 for aabb.cc00.0710
0000.0000.7777.02, length 512
*Jun 7 21:40:42.239: ISIS-Adj: New adjacency, level 1 & 2 for aabb.cc00.0710
0000.0000.8888.02, length 512
*Jun 7 21:40:43.245: ISIS-Adj: No usable IPv6 linklocal addresses in LAN IIH from Ethernet0/1
0000.0000.8888.02, length 512
0000.0000.8888.02, length 512
0000.0000.8888.02, length 512
CPS_R0_R8#un all
Length 512 is clns mtu of interface.
All IPv4 ISIS adjacencies are looking established, lets verify the routing tables followed by a ping test its very
important to check the IGP properly, correct IGP propagation sets the lab:
R2
RP/0/0/CPU0:CPS_R0_R2#sh ip route isis

Sun Jun 8 00:27:00.441 UTC
i L1 9.9.0.3/32 [115/10] via 9.9.23.3, 03:16:06, GigabitEthernet0/0/0/0.23

[115/20] via 9.9.23.3, 01:26:01, GigabitEthernet0/0/0/0.23
R2 has all the loopbacks in AS9 installed in its routing table.
R3

Sun Jun 8 00:29:27.471 UTC

R4

Sun Jun 8 00:30:40.857 UTC

R5
9.0.0.0/8 is variably subnetted, 19 subnets, 2 masks

i L1 9.9.0.2/32 [115/10] via 9.9.25.2, 01:30:47, Ethernet0/1
i L1 9.9.0.3/32 [115/10] via 9.9.35.3, 02:55:58, Ethernet0/2
i L1 9.9.0.4/32 [115/20] via 9.9.35.3, 02:55:48, Ethernet0/2
i L1 9.9.0.7/32 [115/30] via 9.9.35.3, 00:15:09, Ethernet0/2
i L1 9.9.0.8/32 [115/40] via 9.9.35.3, 02:45:57, Ethernet0/2
i L1 9.9.23.0/24 [115/20] via 9.9.35.3, 01:30:47, Ethernet0/2
[115/20] via 9.9.25.2, 01:30:47, Ethernet0/1
i L1 9.9.34.0/24 [115/20] via 9.9.35.3, 02:55:58, Ethernet0/2
i L1 9.9.37.0/24 [115/20] via 9.9.35.3, 00:52:12, Ethernet0/2
i L1 9.9.48.0/24 [115/30] via 9.9.35.3, 02:55:48, Ethernet0/2
i L1 9.9.78.0/24 [115/30] via 9.9.35.3, 00:15:09, Ethernet0/2
CPS_R0_R5#
R7

i L1 9.9.0.2/32 [115/20] via 9.9.37.3, 00:16:48, Ethernet0/0
i L1 9.9.0.3/32 [115/10] via 9.9.37.3, 00:16:48, Ethernet0/0
i L1 9.9.0.4/32 [115/20] via 9.9.78.8, 00:16:48, Ethernet0/1
[115/20] via 9.9.37.3, 00:16:48, Ethernet0/0
i L1 9.9.0.5/32 [115/30] via 9.9.37.3, 00:16:48, Ethernet0/0
i L1 9.9.0.8/32 [115/20] via 9.9.78.8, 02:47:36, Ethernet0/1
i L1 9.9.23.0/24 [115/20] via 9.9.37.3, 00:16:48, Ethernet0/0
i L1 9.9.25.0/24 [115/30] via 9.9.37.3, 00:16:48, Ethernet0/0
i L1 9.9.34.0/24 [115/20] via 9.9.37.3, 00:16:48, Ethernet0/0
i L1 9.9.35.0/24 [115/20] via 9.9.37.3, 00:16:48, Ethernet0/0
i L1 9.9.45.0/24 [115/30] via 9.9.78.8, 00:16:48, Ethernet0/1
[115/30] via 9.9.37.3, 00:16:48, Ethernet0/0
i L1 9.9.48.0/24 [115/20] via 9.9.78.8, 02:47:25, Ethernet0/1
CPS_R0_R7#
R8

i L1 9.9.0.2/32 [115/30] via 9.9.78.7, 00:18:27, Ethernet0/1
[115/30] via 9.9.48.4, 00:18:27, Ethernet0/0
i L1 9.9.0.3/32 [115/20] via 9.9.78.7, 00:18:27, Ethernet0/1
[115/20] via 9.9.48.4, 00:18:27, Ethernet0/0
i L1 9.9.0.4/32 [115/10] via 9.9.48.4, 02:48:54, Ethernet0/0
i L1 9.9.0.5/32 [115/40] via 9.9.78.7, 00:18:27, Ethernet0/1
[115/40] via 9.9.48.4, 00:18:27, Ethernet0/0
i L1 9.9.0.7/32 [115/20] via 9.9.78.7, 02:49:32, Ethernet0/1
i L1 9.9.23.0/24 [115/30] via 9.9.78.7, 00:18:27, Ethernet0/1
[115/30] via 9.9.48.4, 00:18:27, Ethernet0/0
i L1 9.9.25.0/24 [115/40] via 9.9.78.7, 00:18:27, Ethernet0/1
[115/40] via 9.9.48.4, 00:18:27, Ethernet0/0
i L1 9.9.34.0/24 [115/20] via 9.9.48.4, 02:48:54, Ethernet0/0
i L1 9.9.35.0/24 [115/30] via 9.9.78.7, 00:18:27, Ethernet0/1
[115/30] via 9.9.48.4, 00:18:27, Ethernet0/0
i L1 9.9.37.0/24 [115/20] via 9.9.78.7, 01:06:31, Ethernet0/1
i L1 9.9.45.0/24 [115/20] via 9.9.48.4, 02:48:54, Ethernet0/0
CPS_R0_R8#
CPS_R0_R5#tclsh
CPS_R0_R5(tcl)#foreach address {
+>9.9.0.2
+>9.9.0.3
+>9.9.0.4
+>9.9.0.5
+>9.9.0.7
+>9.9.0.8} { ping $address source lo0 repeat 10
+>}
Type escape sequence to abort.
Sending 10, 100-byte ICMP Echos to 9.9.0.2, timeout is 2 seconds:
Packet sent with a source address of 9.9.0.5
!!!!!!!!!!
Success rate is 100 percent (10/10), round-trip min/avg/max = 1/1/1 ms
!!!!!!!!!!
!!!!!!!!!!
!!!!!!!!!!
!!!!!!!!!!
!!!!!!!!!!
CPS_R0_R5(tcl)#
CPS_R0_R5(tcl)#exit
CPS_R0_R5#
Its recommended to perform ping test from all the devices with correct source.
1.2 I SIS for IPv6 Troubleshooting
ISIS IPv6 routing is pre configured in AS 9 as per below table:
47.0009 Ethernet0/0
47.0009 Ethernet0/1
47.0009 Ethernet0/2
47.0009 Ethernet0/0
47.0009 Ethernet0/1
47.0009 Ethernet0/0
47.0009 Ethernet0/1
R5 should have two equal paths installed in ISIS IPv6 routing table for network 2002:9:9:78::/64, currently there is
only one path available, fix the problem to get the desired output.
Pre Configuration:
Refer question 1.1 for configurations.
Let's start verifying from R2:
R2 has its both required interfaces in topology table.
R2 has IPv6 ISIS routes for all required interfaces in AS9.
R3
R3 has its all required neighbors as next-hop in topology table:
R3 has IPv6 ISIS routes for all required interfaces in AS9:
R4
R4 has its all required neighbors as next-hop in topology table:
R5
R5 is receiving IPv6 ISIS routes from its all expected next-hops:
R5 has IPv6 ISIS routes for all required interfaces in AS9:
R7
R7 is receiving IPv6 ISIS routes from its only one next-hop not both, its problem here:
R8
R8 is receiving IPv6 ISIS routes from its only one next-hop not both, its problem here:
Let's check the configurations of R7 and R8 for ISIS IPv6 routing:
Troubleshooting Solution:


!
bandwidth 100000
ip address 9.9.78.7 255.255.255.0
ip router isis
ip pim sparse-mode
ipv6 address 2002:9:9:78::7/64
mpls ip
end
R7 interface Ethernet 0/1 is not advertised in to IPv6 ISIS, we are not seeing ipv6 router isis command applied on
R7 interface connecting to R8, because of it there is no ISIS IPv6 adjacency between R7 and R8.
CPS_R0_R7(config)#interface ethernet 0/1

CPS_R0_R7(config-if)#ipv6 router isis
Note: In Section 1.1 and 1.2, this problem was not injected because removing ipv6 router isis does not allow to
make ISIS IPv4 adjacency between the devices.
Here is what we have asked to achieve:
ISIS IPv4 routing is pre configured in AS 1009 as per below table:
47.0106 Ethernet0/0
47.0106 Ethernet0/1
47.0109 Ethernet0/0
47.0109 Ethernet0/0

47.0110 Ethernet0/0
47.0110 Ethernet0/0
R10 and R9 should form CLNS level-2-only adjacency. Fix the problem in pre configuration to achieve it.
Pre Configurations:
R1

Sun Jun 8 01:53:46.783 UTC
interface Loopback0
ipv4 address 9.9.0.1 255.255.255.255
ipv6 address 2002:9:9::1/128
!

Sun Jun 8 01:53:26.564 UTC
ipv4 address 9.9.16.1 255.255.255.0
ipv6 address 2002:9:9:16::1/64
!

Sun Jun 8 01:53:31.974 UTC
ipv4 address 9.9.19.1 255.255.255.0
ipv6 address 2002:9:9:19::1/64
!
router isis abc

net 47.0101.0000.0000.1111.00
metric-style wide
!
interface Loopback0
passive
!
!
!
!
R6


!
interface Loopback0
ip address 9.9.0.6 255.255.255.255
ip router isis
ip pim sparse-mode
ipv6 address 2002:9:9::6/128
ipv6 ospf 1009 area 0
end


!
ip address 9.9.106.6 255.255.255.0
ip router isis
ip pim sparse-mode
ipv6 address 2002:9:9:106::6/64
mpls ip
end


!
ip address 9.9.16.6 255.255.255.0
ip router isis
ip pim sparse-mode
ipv6 address 2002:9:9:16::6/64
mpls ip
endrouter isis
net 47.0106.0000.0000.6666.00
CPS_R0_R6#
router isis
net 47.0106.0000.0000.6666.00
metric-style wide
R9


!
interface Loopback0
ip address 9.9.0.9 255.255.255.255
ip router isis
ip pim sparse-mode
ipv6 address 2002:9:9::9/128
end


!
ip address 9.9.19.9 255.255.255.0
ip router isis
ip pim sparse-mode
ipv6 address 2002:9:9:19::9/64
mpls ip
end


!
ip address 9.9.109.9 255.255.255.0
ip router isis
ip pim sparse-mode
ipv6 address 2002:9:9:109::9/64
mpls ip
end
CPS_R0_R9#
router isis
net 47.0110.0000.0000.9999.00
metric-style wide
R10


!
interface Loopback0
ip address 9.9.0.10 255.255.255.255
ip router isis
ip pim sparse-mode
ipv6 address 2002:9:9::10/128
end


!
ip address 9.9.106.10 255.255.255.0
ip router isis
ip pim sparse-mode
ipv6 address 2002:9:9:106::10/64
mpls ip
end


!
ip address 9.9.109.10 255.255.255.0
ip router isis
ip pim sparse-mode
ipv6 address 2002:9:9:109::10/64
mpls ip
end
CPS_R0_R10#
router isis
net 47.0110.0000.0000.1010.00
metric-style wide
no hello padding
Let's start checking from R1:
R1 is showing both L2 neighbors as expected.
R6
R9

Apart from L2 adjacency with R10 it has one L1 neighbor ship with R10.
R10

Apart from L2 adjacency with R9 it has L1 neighbor ship with R9 too.
CPS_R0_R9#sh run | i net 47

net 47.0110.0000.0000.9999.00
CPS_R0_R9#
CPS_R0_R10#sh run | i net 47

net 47.0110.0000.0000.1010.00
CPS_R0_R10#
Notice configuration here, as per question R9 should us area Id 47.0109, while that configured with wrong NET ID,
once NET ID is corrected R9 and R10 will have single L2 adjacency.
To form L1 adjacency both devices should be in same Area.
Lets correct it on R9:
router isis
no net 47.0110.0000.0000.9999.00
net 47.0106.0000.0000.9999.00
Problem is solved.
If it is asked to have R9 and R10 in same area, we need to apply is-type level 2 on both R9 and R10.
Apply on any one will result the same output, still its recommended to apply at both ends.
R9
isis circuit-type level-2-only
R10
Let's have a quick look on routes:
R1
R1 is receiving all AS 1009 routes as L2.
R6
i L2 9.9.0.1/32 [115/10] via 9.9.16.1, 00:27:57, Ethernet0/1

i L2 9.9.0.9/32 [115/30] via 9.9.106.10, 00:05:55, Ethernet0/0
[115/30] via 9.9.16.1, 00:05:55, Ethernet0/1
i L2 9.9.0.10/32 [115/20] via 9.9.106.10, 08:23:49, Ethernet0/0
i L2 9.9.19.0/24 [115/20] via 9.9.16.1, 00:27:57, Ethernet0/1
i L2 9.9.109.0/24 [115/20] via 9.9.106.10, 08:23:49, Ethernet0/0
CPS_R0_R6#
R9
i L2 9.9.0.1/32 [115/10] via 9.9.19.1, 00:31:41, Ethernet0/0

i L2 9.9.0.6/32 [115/30] via 9.9.109.10, 00:29:11, Ethernet0/1
[115/30] via 9.9.19.1, 00:29:11, Ethernet0/0
i L2 9.9.0.10/32 [115/20] via 9.9.109.10, 00:07:41, Ethernet0/1
i L2 9.9.16.0/24 [115/20] via 9.9.19.1, 00:31:41, Ethernet0/0
i L2 9.9.106.0/24 [115/20] via 9.9.109.10, 00:07:41, Ethernet0/1
CPS_R0_R9#
R10
i L2 9.9.0.1/32 [115/20] via 9.9.109.9, 00:30:17, Ethernet0/1

[115/20] via 9.9.106.6, 00:30:17, Ethernet0/0
i L2 9.9.0.6/32 [115/20] via 9.9.106.6, 08:26:10, Ethernet0/0
i L2 9.9.0.9/32 [115/20] via 9.9.109.9, 00:08:17, Ethernet0/1
i L2 9.9.16.0/24 [115/20] via 9.9.106.6, 08:26:10, Ethernet0/0
i L2 9.9.19.0/24 [115/20] via 9.9.109.9, 00:08:17, Ethernet0/1
CPS_R0_R10#
OSPFv3 routing is pre configured in AS 1009 as per below table:
R1 0 Loopback0
0 GigabiEthernet0/0/0/0.16
1009 GigabiEthernet0/0/0/0.19
R6 0 Loopback0
1009 Ethernet0/0
0 Ethernet0/1
R9 1009 Loopback0
1009 Ethernet0/0
1009 Ethernet0/1
R10 1009 Loopback0

1009 Ethernet0/0
1009 Ethernet0/1
R10 and R9 are unable to establish OSPF IPv6 adjacency and exchange OSPFv3 updates.
Fix the problem to establish OSPF adjacency between these two.
Pre Configuration:
R1

Sun Jun 8 06:04:33.382 UTC
ipv4 address 9.9.16.1 255.255.255.0
ipv6 address 2002:9:9:16::1/64
!

Sun Jun 8 06:04:42.132 UTC
ipv4 address 9.9.19.1 255.255.255.0
ipv6 address 2002:9:9:19::1/64
!

Sun Jun 8 06:04:54.861 UTC
interface Loopback0
ipv4 address 9.9.0.1 255.255.255.255
ipv6 address 2002:9:9::1/128
!
RP/0/0/CPU0:CPS_R0_R1#sh run router ospfv3

Sun Jun 8 06:05:12.720 UTC
router ospfv3 1009
area 0
interface Loopback0
!
!
!
area 1009
!
!
address-family ipv6
!
R6


!
interface Loopback0
ip address 9.9.0.6 255.255.255.255
ip router isis
ip pim sparse-mode
ipv6 address 2002:9:9::6/128
end


!
ip address 9.9.106.6 255.255.255.0
ip router isis
ip pim sparse-mode
ipv6 address 2002:9:9:106::6/64
mpls ip
end


!
ip address 9.9.16.6 255.255.255.0
ip router isis
ip pim sparse-mode
ipv6 address 2002:9:9:16::6/64
mpls ip
R9


!
interface Loopback0
ip address 9.9.0.9 255.255.255.255
ip router isis
ip pim sparse-mode
ipv6 address 2002:9:9::9/128
end


!
ip address 9.9.19.9 255.255.255.0
ip router isis
ip pim sparse-mode
ipv6 address 2002:9:9:19::9/64
mpls ip
end


!
ip address 9.9.109.9 255.255.255.0
ip router isis
ip pim sparse-mode
ipv6 address 2002:9:9:109::9/64
mpls ip
ipv6 ospf network non-broadcast
end
CPS_R0_R9#
R10


!
interface Loopback0
ip address 9.9.0.10 255.255.255.255
ip router isis
ip pim sparse-mode
ipv6 address 2002:9:9::10/128
end


!
ip address 9.9.106.10 255.255.255.0
ip router isis
ip pim sparse-mode
ipv6 address 2002:9:9:106::10/64
mpls ip
end


!
ip address 9.9.109.10 255.255.255.0
ip router isis
ip pim sparse-mode
ipv6 address 2002:9:9:109::10/64
mpls ip
end
CPS_R0_R10#
Lets verify on R1:
R1 has two OSPFv3 adjacencies established with R9 and R6.

R1 has two interfaces configured in Area 0.
R1 has one interface configured in Area 1009 which is connecting to R9.
R6
R6 has two OSPFv3 adjacencies established with R1 and R10.

R6 has two interfaces configured in Area 0.
R6 has one interface configured in Area 1009 which is connecting to R10.
R9
R9 has two OSPFve3 adjacencies established with R1.

R9 has all interfaces configured in Area 1009.
R9 has not established adjacency with R10.
R10
R10 has two OSPFve3 adjacencies established with R6.

R10 has all interfaces configured in Area 1009.
R10 has not established adjacency with R9.
Let's check why OSPFv3 adjacency is not up between R9 and R10.
CPS_R0_R10#debug ospfv3 adj detail
CPS_R0_R10#conf t
CPS_R0_R10(config-if)#shut
CPS_R0_R10(config-if)#
*Jun 8 06:52:34.672: OSPFv3-1009-IPv6 ADJ Et0/1: IPv6 gonedown
*Jun 8 06:52:34.672: OSPFv3-1009-IPv6 ADJ Et0/1: Interface Ethernet0/1 going Down
*Jun 8 06:52:34.672: OSPFv3-1009-IPv6 ADJ Et0/1: Neighbor change Event
*Jun 8 06:52:34.672: OSPFv3-1009-IPv6 ADJ Et0/1: DR/BDR election on
*Jun 8 06:52:34.672: OSPFv3-1009-IPv6 ADJ Et0/1: Elect BDR 0.0.0.0
*Jun 8 06:52:34.672: OSPFv3-1009-IPv6 ADJ Et0/1: Elect DR 0.0.0.0
*Jun 8 06:52:34.672: OSPFv3-1009-IPv6 ADJ Et0/1: DR: none BDR: none
*Jun 8 06:52:34.672: OSPFv3-1009-IPv6 ADJ Et0/1: Flush network LSA immediately
*Jun 8 06:52:34.672: OSPFv3-1009-IPv6 ADJ Et0/1: Remember old DR 9.9.0.10
*Jun 8 06:52:34.683: %LDP-5-NBRCHG: LDP Neighbor 9.9.0.9:0 (3) is DOWN (Interface not operational)
CPS_R0_R10(config-if)#no sh
*Jun 8 06:52:36.678: %LINK-5-CHANGED: Interface Ethernet0/1, changed state to administratively down
*Jun 8 06:52:37.684: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0/1, changed state to down
CPS_R0_R10(config-if)#no sh
*Jun 8 06:52:38.854: %PIM-5-NBRCHG: neighbor 9.9.109.9 UP on interface Ethernet0/1
*Jun 8 06:52:40.633: %PIM-5-DRCHG: DR change from neighbor 0.0.0.0 to 9.9.109.10 on interface Ethernet0/1
*Jun 8 06:52:40.847: %LINK-3-UPDOWN: Interface Ethernet0/1, changed state to up
*Jun 8 06:52:41.850: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0/1, changed state to up
*Jun 8 06:52:42.856: OSPFv3-1009-IPv6 ADJ Et0/1: IPv6 cameup
*Jun 8 06:52:42.856: OSPFv3-1009-IPv6 ADJ Et0/1: OSPF interface Ethernet0/1 going Up
*Jun 8 06:52:44.087: %LDP-5-NBRCHG: LDP Neighbor 9.9.0.9:0 (2) is UP
*Jun 8 06:53:22.861: OSPFv3-1009-IPv6 ADJ Et0/1: end of Wait
*Jun 8 06:53:22.861: OSPFv3-1009-IPv6 ADJ Et0/1: DR/BDR election on
*Jun 8 06:53:22.861: OSPFv3-1009-IPv6 ADJ Et0/1: DR: 9.9.0.10 (Id) BDR: none
Not a clear clue, adjacency all time getting stuck after DR/BDR election, unable to perform SPF.
Lets verify the configuration:


!
ip address 9.9.109.9 255.255.255.0
ip router isis
ip pim sparse-mode
ipv6 address 2002:9:9:109::9/64
mpls ip
ipv6 ospf network non-broadcast
end
Default OSPF network type over broadcast media Ethernet is Broadcast, In OSPF broadcast networks as well as in
non broadcast networks DR/BDR selection happens.
But broadcast and non broadcast network hello and dead timers are different, for OSPF if timers of both the peers
are not matching adjacency will never form, let's have a look on it:
Let's change the network type on R9 to make the default network type broadcast:
no ipv6 ospf network non-broadcast
CPS_R0_R9#show ospfv3 neighbor
OSPFv3 1009 address-family ipv6 (router-id 9.9.0.9)
Neighbor ID Pri State Dead Time Interface ID Interface

9.9.0.10 1 2WAY/DROTHER 00:00:37 4 Ethernet0/1
9.9.0.1 1 FULL/BDR 00:00:32 13 Ethernet0/0
CPS_R0_R9#
After the changes adjacency got stuck at Two Way state, after a wait of 2-3 minutes:
CPS_R0_R9#clear ipv6 ospf process

Reset selected OSPFv3 processes? [no]: yes
CPS_R0_R9#
*Jun 8 07:28:45.976: %OSPFv3-5-ADJCHG: Process 1009, Nbr 9.9.0.10 on Ethernet0/1 from LOADING to FULL,
Loading Done
CPS_R0_R9#
CPS_R0_R9#show ospfv3 neighbor
OSPFv3 1009 address-family ipv6 (router-id 9.9.0.9)
Neighbor ID Pri State Dead Time Interface ID Interface

9.9.0.10 1 FULL/DR 00:00:37 4 Ethernet0/1
9.9.0.1 1 FULL/BDR 00:00:35 13 Ethernet0/0
CPS_R0_R9#
Its solved now.
Note: R6 and R10 will not be able to make OSPF v3 peering if the OSPF router-id is same on both.
Lets verify the OSPFv3 routes in AS 1009:
R1
R1 has all intra area OSPFv3 routes.

R1 has installed all required AS 1009 routes in routing table.
R6
R6 has all intra area OSPFv3 routes.

R9
R9 has all intra area and inter area both type of OSPFv3 routes.
R10
R10 has all intra area and inter area both type of OSPFv3 routes.
1.5 ISIS IPv4/IPv6 Level
IPv4/IPv6 ISIS in AS 1009 and AS 9 is preconfigured, verify the configuration and make sure below requirements
are achieved:
All devices in AS 9 should be running only ISIS level-1 for both IPv4 and IPv6 interfaces.
Make sure all IPv4/IPv6 subnets are installed in ISIS IPv4/IPv6 routing table of all devices and those ip subnets
are reachable to each other in AS 9 ISIS domain.
All devices in AS1009 should be running only ISIS level-2 for both IPv4 and IPv6 interfaces.
Make sure all IPv4/IPv6 subnets are installed in ISIS IPv4/IPv6 routing table of all devices and those ip subnets are
reachable to each other in AS 1009 ISIS domain.
Solution:
Lets apply it globally at all the devices in AS 9:
R2
RP/0/0/CPU0:CPS_R0_R2#conf t
Sun Jun 8 08:41:32.429 UTC
RP/0/0/CPU0:CPS_R0_R2(config)#router isis abc
RP/0/0/CPU0:CPS_R0_R2(config-isis)#is-type level-1
RP/0/0/CPU0:CPS_R0_R2(config-isis)#commit
Sun Jun 8 08:41:38.978 UTC
RP/0/0/CPU0:CPS_R0_R2(config-isis)#do sh run | b router isis abc
Sun Jun 8 08:42:47.313 UTC
router isis abc
is-type level-1
net 47.0009.0000.0000.2222.00
metric-style wide
R3
Sun Jun 8 08:43:41.200 UTC
Sun Jun 8 08:43:48.529 UTC
RP/0/0/CPU0:CPS_R0_R3(config-isis)#
R4
Sun Jun 8 08:44:44.378 UTC
Sun Jun 8 08:44:50.607 UTC
R5
CPS_R0_R5(config)#router isis
CPS_R0_R5(config-router)#is-type level-1
CPS_R0_R5(config-router)#end
R7
R8
Before proceeding to AS 1009, let's have a quick check:
R2
Looks good.
R3
Confirmed, no L2 IIH any more on the interface.
Let's do a similar check on IOS router.
R5
Good so far.
R1
Sun Jun 8 09:11:03.056 UTC
Sun Jun 8 09:11:08.855 UTC
R6
CPS_R0_R6#conf t
Enter configuration commands, one per line. End with CNTL/Z.
R9
CPS_R0_R9#conf t
R10
CPS_R0_R10#conf t
Let's keep final comprehensive verification for IGP part due for completing the last question related to Core IGP.
3.1
Table 1 : Loopback Interface Addresses
R1 Loopback0 9.9.0.1/32 2002:9:9::1/128

Loopback1 172.9.0.1/32 2002:172:9::1/128
R2 Loopback0 9.9.0.2/32 2002:9:9::2/128
Loopback1 172.9.0.2/32 2002:172:9::2/128
Loopback2 9.9.0.22/32
R3 Loopback0 9.9.0.3/32 2002:9:9::3/128
Loopback1 172.9.0.3/32 2002:172:9::3/128
R4 Loopback0 9.9.0.4/32 2002:9:9::4/128
Loopback1 172.9.0.4/32
R5 Loopback0 9.9.0.5/32 2002:9:9::5/128
R6 Loopback0 9.9.0.6/32 2002:9:9::6/128
R7 Loopback0 9.9.0.7/32 2002:9:9::7/128
Loopback1 172.9.0.7/32
R8 Loopback0 9.9.0.8/32 2002:9:9::8/128
Loopback1 172.9.0.8/32 2002:172:9::8/128
Loopback2 9.9.0.88/32
R9 Loopback0 9.9.0.9/32 2002:9:9::9/128
Loopback1 172.9.0.9/32
R10 Loopback0 9.9.0.10/32 2002:9:9::10/128
Loopback1 172.9.0.10/32
R11 Loopback0 172.9.0.11/32 2002:172:9::11/128
Loopback1 192.9.0.11/32
R12 Loopback0 172.9.0.12/32 2002:172:9::12/128
Loopback1 192.9.0.12/32
R13 Loopback0 192.9.0.13/32
R14 Loopback0 172.9.0.14/32 2002:172:9::14/128
Loopback1 192.9.0.14/32
R15 Loopback0 172.9.0.15/32 2002:172:9::15/128
Loopback1 192.9.0.15/32
R16 Loopback0 192.9.0.16/32
R17 Loopback0 172.9.0.17/32 2002:172:9::17/128
Loopback1 192.9.0.17/32
R18 Loopback0 172.9.0.18/32 2002:172:9::18/128
Loopback1 192.9.0.18/32
R19 Loopback0 192.9.0.19/32
R20 Loopback0 172.9.0.20/32
R21 Loopback0 172.9.0.21/32
R22 Loopback0 172.9.0.22/32
R23 Loopback0 172.9.0.23/32
R24 Loopback0 172.9.0.24/32
Table 2 : Loopback Interface Multicast Groups

R1 Loopback0 239.255.0.1
R2 Loopback0 239.255.0.2
R3 Loopback0 239.255.0.3
R4 Loopback0 239.255.0.4
R5 Loopback0 239.255.0.5
R6 Loopback0 239.255.0.6
R7 Loopback0 239.255.0.7
R8 Loopback0 239.255.0.8
R9 Loopback0 239.255.0.9
R10 Loopback0 239.255.0.10
R11 Loopback0 239.255.172.11
R12 Loopback0 239.255.172.12
R13 Loopback0 239.255.172.13
R14 Loopback0 239.255.172.14
R15 Loopback0 239.255.172.15
Section 1
Implement, Optimize and Troubleshooting of Core IP Technologies
OSPF for IPv4 Troubleshooting
OSPF IPv4 routing is pre configured in AS 9 as per below table:
Router Routing Protocol Interface
R2 OSPF Area 0 Loopback0

OSPF Area 0 GigabiEthernet0/0/0/0.23



OSPF Area 0 Ethernet0/0


Make sure R2 and R6 Loopback 2 interfaces are not advertised in to OSPF.
Make sure POS Link between R1-R2 is not advertised in OSPF.
Check AS 9 devices to make sure their routing tables are in sync as per above table.
Pre Configuration:
RP/0/0/CPU0:CPS_R0_R2#sh run | b router ospf 9

Wed Jun 11 15:54:07.787 UTC
router ospf 9
router-id 9.9.0.2
area 0
interface Loopback0
!
!
!
!
!
router ospfv3 9
router-id 9.9.0.2
area 0
interface Loopback0
!
!

Wed Jun 11 15:55:05.853 UTC
router ospf 9
router-id 9.9.0.3
area 0
interface Loopback0
!
!
hello-interval 20
!
!
!
!
router ospfv3 9
router-id 9.9.0.3
area 0
interface Loopback0
!
!
!
hello-interval 30
R4

Wed Jun 11 15:56:08.428 UTC
router ospf 9
router-id 9.9.0.4
area 0
interface Loopback0
!
!
!
!
area 10
!
!
!
router ospfv3 9
router-id 9.9.0.4
area 0
interface Loopback0
!
hello-interval 120
!
R5
CPS_R0_R5# show running-config | section router ospf

router ospfv3 9
router-id 9.9.0.3
!
exit-address-family
router ospf 9
router-id 9.9.0.5
network 9.9.0.5 0.0.0.0 area 0
network 9.9.35.0 0.0.0.255 area 1
network 9.9.56.0 0.0.0.255 area 10
CPS_R0_R5#


!
interface Loopback0
ip address 9.9.0.5 255.255.255.255
ip pim sparse-mode
ipv6 address 2002:9:9::5/128
ipv6 ospf 9 area 0
end


!
bandwidth 100000
ip address 9.9.35.5 255.255.255.0
ip pim sparse-mode
ipv6 address 2002:9:9:35::5/64
mpls ip
ipv6 ospf 9 area 1
end


!
bandwidth 100000
ip address 9.9.56.5 255.255.255.0
ip pim sparse-mode
ipv6 address 2002:9:9:56::5/64
mpls ip
end
R6
CPS_R0_R6#show running-config | section router ospf

router ospfv3 9
router-id 9.9.0.6
!
exit-address-family
router ospf 9
router-id 9.9.0.6
network 9.9.0.6 0.0.0.0 area 0
network 9.9.46.0 0.0.0.255 area 0
network 9.9.56.0 0.0.0.255 area 1
CPS_R0_R6#


!
interface Loopback0
ip address 9.9.0.6 255.255.255.255
ip pim sparse-mode
ipv6 address 2002:9:9::6/128
ipv6 ospf 9 area 0
end


!
bandwidth 100000
ip address 9.9.46.6 255.255.255.0
ip mtu 1400
ip pim sparse-mode
ipv6 address 2002:9:9:46::6/64
mpls ip
ipv6 ospf 9 area 9
end

bandwidth 100000
ip address 9.9.56.6 255.255.255.0
ip pim sparse-mode
ip ospf network point-to-point
ipv6 address 2002:9:9:56::6/64
mpls ip
ipv6 ospf 9 area 0
end
R7

router ospf 9
router-id 9.9.0.7
network 9.9.0.7 0.0.0.0 area 0
network 9.9.34.0 0.0.0.255 area 0
network 9.9.37.0 0.0.0.255 area 1
ipv6 router ospf 9
CPS_R0_R7#

!
interface Loopback0
ip address 9.9.0.7 255.255.255.255
ip pim sparse-mode
ipv6 address 2002:9:9::7/128
ipv6 ospf 9 area 0
end


!
bandwidth 100000
ip address 9.9.47.7 255.255.255.0
ip pim sparse-mode
ipv6 address 2002:9:9:47::7/64
mpls ip
ipv6 ospf 9 area 9
end


!
bandwidth 100000
ip address 9.9.27.7 255.255.255.0
ip pim sparse-mode
ipv6 address 2002:9:9:27::7/64
mpls ip
ipv6 ospf 9 area 0
end
bandwidth 100000
ip address 9.9.37.7 255.255.255.0
ip pim sparse-mode
ipv6 address 2002:9:9:37::7/64
mpls ip
ipv6 ospf 9 area 0
end
Pre Configuration Verification
R2
RP/0/0/CPU0:CPS_R0_R2#sh protocols
Routing Protocol "BGP 9"

Non-stop routing is not enabled
Graceful restart is not enabled
Current BGP NSR state - None
Address Family IPv4 Unicast:

Distance: external 20 internal 200 local 200
Sourced Networks:
9.9.0.2/32
Routing Information Sources:
Neighbor State/Last update received NSR-State GR-Enabled
9.9.0.3 11:30:25 None No
9.9.0.4 Idle None No
Address Family IPv4 Labeled-unicast:

Sourced Networks:
9.9.0.2/32
Address Family VPNv4 Unicast:

Routing Protocol OSPF 9

Router Id: 9.9.0.2
Distance: 110
Non-Stop Forwarding: Disabled
Redistribution:
None
Area 0
Loopback0
GigabitEthernet0/0/0/0.23
R2 needs to have three interfaces advertised in to OSPF Area 0 - Loopback 0, Gi0/0/0/0.23 and Gi0/0/0/0.27.
As per show protocols output these three interfaces are advertised in to OSPF .
R2 is configured loopback 0 ip address 9.9.0.2 as OSPF router id.
Lets check for OSPF adjacencies:
RP/0/0/CPU0:CPS_R0_R2#show ospf neighbor

Wed Jun 11 16:33:19.806 UTC
* Indicates MADJ interface
Neighbors for OSPF 9
Neighbor ID Pri State Dead Time Address Interface

9.9.0.3 1 FULL/BDR 00:00:37 9.9.23.3 GigabitEthernet0/0/0/0.23
Neighbor is up for 11:38:11
Total neighbor count: 1

R2 has 1 OSPF neighbor, it needs to have two neighbors.

R2 is recieving 2 routes from R3:
RP/0/0/CPU0:CPS_R0_R2#sh route ospf

Wed Jun 11 16:34:35.911 UTC
O 9.9.0.3/32 [110/2] via 9.9.23.3, 11:38:56, GigabitEthernet0/0/0/0.23

R3
RP/0/0/CPU0:CPS_R0_R3#show protocols
Wed Jun 11 16:37:51.857 UTC


9.9.0.2 09:03:19 None No


9.9.0.2 09:03:19 None No

Router Id: 9.9.0.3
Distance: 110
Redistribution:
None
Area 0
Loopback0
R3 needs to have five interfaces advertised in OSPF Area 0 - Loopback 0, Gi0/0/0/0.23 and Gi0/0/0/0.34,
Gi0/0/0/0.35, Gi0/0/0/0.37.
As per show protocols output these four interfaces Loopback 0, Gi0/0/0/0.23 and Gi0/0/0/0.34, Gi0/0/0/0.35
are advertised in to OSPF .
Interface Gi0/0/0/0.37 needs to be advertised in to OSPF.

Wed Jun 11 16:43:11.575 UTC

9.9.0.2 1 FULL/DR 00:00:31 9.9.23.2 GigabitEthernet0/0/0/0.23

R3 has 1 OSPF neighbor, it needs to have four neighbors.

R3 is recieving 2 routes from R2:
RP/0/0/CPU0:CPS_R0_R3#show route ospf

Wed Jun 11 16:44:31.130 UTC

R4
RP/0/0/CPU0:CPS_R0_R4#show protocols
Wed Jun 11 16:51:39.350 UTC


Sourced Networks:
9.9.0.4/32

Sourced Networks:
9.9.0.4/32


Router Id: 9.9.0.4
Distance: 110
Redistribution:
None
Area 0
Loopback0
Area 10
R4 needs to have four interfaces advertised in to OSPF Area 0 - Loopback 0, Gi0/0/0/0.34 and Gi0/0/0/0.46,
Gi0/0/0/0.47.
As per show protocols output these three Loopback 0, Gi0/0/0/0.34 and Gi0/0/0/0.47 interfaces are advertised in
to OSPF Area 0 .
Interface Gi0/0/0/0.46 is advertised in OSPF Area 10.

Wed Jun 11 16:55:37.764 UTC
R4 has 0 OSPF v2 neighbor, it needs to have two neighbors.

R4 is recieving 0 routes:

Wed Jun 11 16:57:22.587 UTC
% No matching routes found
R5
CPS_R0_R5#show ip ospf interface brief

Interface PID Area IP Address/Mask Cost State Nbrs F/C
Lo0 9 0 9.9.0.5/32 1 LOOP 0/0
Et0/0 9 1 9.9.35.5/24 1 DR 0/0
Et0/1 9 10 9.9.56.5/24 1 DR 0/0
CPS_R0_R5#
R5 needs to have three interfaces advertised in OSPF Area 0 - Loopback 0, Ethernet 0/0 and Ethernet 0/1.
As per show protocols output these Loopback 0 is advertised in to OSPF Area 0 .
Interface Ethernet 0/0 is advertised in to OSPF Area 1.
CPS_R0_R5#sh ip ospf database
OSPF Router with ID (9.9.0.5) (Process ID 9)
CPS_R0_R5#show ip ospf neighbor

CPS_R0_R5#

CPS_R0_R5#show 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, H - NHRP, l - LISP
+ - replicated route, % - next hop override
Gateway of last resort is not set
CPS_R0_R5#
R6

Lo0 9 0 9.9.0.6/32 1 LOOP 0/0
Et0/0 9 0 9.9.46.6/24 1 DR 0/0
Et0/1 9 1 9.9.56.6/24 1 P2P 0/0
CPS_R0_R6#
CPS_R0_R6#show ip ospf database

CPS_R0_R6#


CPS_R0_R6#
R7

Lo0 9 0 9.9.0.7/32 1 LOOP 0/0
Et0/2 9 1 9.9.37.7/24 1 DR 0/0
CPS_R0_R7#
Interface Ethernet 0/0, Ethernet 0/1 are not advertised in to OSPF Area 0.
CPS_R0_R7#show ip ospf database
CPS_R0_R7#


CPS_R0_R7#
Troubleshooting Solutions :
G0/0/0/0.23 23.2 G0/0/0/0.23 23.3 G0/0/0/0.35 35.3 E0/0 35.5

VLAN 12 VLAN 12 VLAN 15
G0/0/0/0.37 37.3
VLAN 17 E0/1 56.5
G0/0/0/0.27 27.2 G0/0/0/0.34 34.4
VLAN 11 VLAN 14
E0/2 37.7 G0/0/0/0.34 34.3

E0/1 27.7
VLAN 17 VLAN 14
VLAN 11
E0/1 56.6
E0/0 47.7 G0/0/0/0.47 47.4 G0/0/0/0.46 46.4 E0/0 46.6
VLAN 13 VLAN 13 VLAN 16 VLAN 16
Lets start from R2:
RP/0/0/CPU0:CPS_R0_R2#sh ospf interface brief | b Interface

Wed Jun 11 17:31:27.607 UTC
Interfaces for OSPF 9

Lo0 9 0 9.9.0.2/32 1 LOOP 0/0
Gi0/0/0/0.23 9 0 9.9.23.2/24 1 DR 1/1
Gi0/0/0/0.27 9 0 9.9.25.2/24 1 DR 0/0
All three interfaces are configured correctly on it.
Neighborship with R7 is down on R2, do you know why? Look at output R2 interface connecting to R7 is configured
with wrong IP address, IP between should be 27 in third octect as per rule of 9.9.XX.X. lets correct it:

Wed Jun 11 17:37:42.251 UTC
ipv4 address 9.9.25.2 255.255.255.0
ipv6 address 2002:9:9:27::2/64
!
Wed Jun 11 17:39:01.946 UTC
RP/0/0/CPU0:CPS_R0_R2(config)#interface GigabitEthernet0/0/0/0.27
RP/0/0/CPU0:CPS_R0_R2(config-subif)# ipv4 address 9.9.27.2 255.255.255.0
RP/0/0/CPU0:CPS_R0_R2(config-subif)#commit
Wed Jun 11 17:39:09.405 UTC
RP/0/0/CPU0:CPS_R0_R2(config-subif)#end
RP/0/0/CPU0:CPS_R0_R2#ping 9.9.27.7
Wed Jun 11 17:39:59.972 UTC
!!!!!
Still adjacency did not come up:
RP/0/0/CPU0:CPS_R0_R2#sh ospf neighbor | b State

Wed Jun 11 17:43:04.249 UTC
Before checking at debugging level, lets check weather interface is advertised in to OSPF at R7 correctly:

Lo0 9 0 9.9.0.7/32 1 LOOP 0/0
Et0/2 9 1 9.9.37.7/24 1 DR 0/0
CPS_R0_R7#
Interface Et0/1 is not advertised in to OSPF, lets do that:
CPS_R0_R7#sh run | b router ospf

router ospf 9
router-id 9.9.0.7
network 9.9.0.7 0.0.0.0 area 0
network 9.9.34.0 0.0.0.255 area 0
network 9.9.37.0 0.0.0.255 area 1
CPS_R0_R7#conf t
CPS_R0_R7(config)#router ospf 9
CPS_R0_R7(config-router)#network 9.9.27.0 0.0.0.255 area 0
CPS_R0_R7#
Adjacency has come up:
CPS_R0_R7#sh ip ospf neighbor

9.9.0.2 0 FULL/ - 00:00:38 9.9.27.2 Ethernet0/1
CPS_R0_R7#
Wed Jun 11 18:10:42.195 UTC



Wed Jun 11 18:11:10.634 UTC

Strange no routes from R7.
Lets check further:
RP/0/0/CPU0:CPS_R0_R2#show ospf interface gigabitEthernet 0/0/0/0.27

Wed Jun 11 18:14:14.201 UTC
GigabitEthernet0/0/0/0.27 is up, line protocol is up

Internet Address 9.9.27.2/24, Area 0
Process ID 9, Router ID 9.9.0.2, Network Type BROADCAST, Cost: 1
Transmit Delay is 1 sec, State DR, Priority 1, MTU 1500, MaxPktSz 1500
Designated Router (ID) 9.9.0.2, Interface address 9.9.27.2
Backup Designated router (ID) 9.9.0.7, Interface address 9.9.27.7
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
Hello due in 00:00:03
Index 2/2, flood queue length 0
Next 0(0)/0(0)
Last flood scan length is 1, maximum is 2
Last flood scan time is 0 msec, maximum is 0 msec
LS Ack List: current length 0, high water mark 2
Neighbor Count is 1, Adjacent neighbor count is 1
Adjacent with neighbor 9.9.0.7 (Backup Designated Router)
Suppress hello for 0 neighbor(s)
Multi-area interface Count is 0
CPS_R0_R7#sh ip ospf interface ethernet 0/1
Internet Address 9.9.27.7/24, Area 0, Attached via Network Statement
Process ID 9, Router ID 9.9.0.7, Network Type POINT_TO_POINT, Cost: 1
Topology-MTID Cost Disabled Shutdown Topology Name
0 1 no no Base
Transmit Delay is 1 sec, State POINT_TO_POINT
oob-resync timeout 40
Supports Link-local Signaling (LLS)
Cisco NSF helper support enabled
IETF NSF helper support enabled
Next 0x0(0)/0x0(0)
Adjacent with neighbor 9.9.0.2
CPS_R0_R7#
Its OSPF network type mismatch issue, R2 is using OSPF default network type broadcast for shared media while
R7 is using manually configured OSPF network type point-to-point on a shared media which is default on point to
point WAN links, lets correct network type on R7.
CPS_R0_R7#show running-config interface e0/1


!
bandwidth 100000
ip address 9.9.27.7 255.255.255.0
ip pim sparse-mode
ipv6 address 2002:9:9:27::7/64
mpls ip
ipv6 ospf 9 area 0
end
CPS_R0_R7#conf t
CPS_R0_R7(config)#interface Ethernet0/1
CPS_R0_R7(config-if)#no ip ospf network point-to-point
Wed Jun 11 18:20:33.075 UTC

O IA 9.9.37.0/24 [110/2] via 9.9.27.7, 00:02:55, GigabitEthernet0/0/0/0.27
Looks better now.
Lets head to R3:

Wed Jun 11 18:22:30.237 UTC


R3 needs to have 4 neighbors, R2, R4, R5, R7, here its showing only one.
Checking between R3 and R4 first:
RP/0/0/CPU0:CPS_R0_R3#sh ospf interface brief | i Gi0/0/0/0.34

Wed Jun 11 18:25:14.006 UTC
Gi0/0/0/0.34 9 0 9.9.34.3/24 1 DOWN 0/0

RP/0/0/CPU0:CPS_R0_R4#sh ospf interface brief | i Gi0/0/0/0.34

Wed Jun 11 18:30:19.245 UTC
Gi0/0/0/0.34 9 0 9.9.34.4/24 1 DR 0/0
RP/0/0/CPU0:CPS_R0_R3#debug ospf 9 events gigabitEthernet 0/0/0/0.34
Wed Jun 11 18:53:22.810 UTC
RP/0/0/CPU0:CPS_R0_R3#RP/0/0/CPU0:Jun 11 18:53:32.189 : ospf[1014]: Send hello to 224.0.0.5 area 0 on
GigabitEthernet0/0/0/0.34 from 9.9.34.3 (nbr/if state 3/5)
RP/0/0/CPU0:Jun 11 18:53:32.189 : ospf[1014]: Send hello pkt pri 1 options 0x12 DR 9.9.34.3 BDR 0.0.0.0 hello 20
dead 80 netmask 255.255.255.0, vrf default vrfid 0x60000000
RP/0/0/CPU0:Jun 11 18:53:42.109 : ospf[1014]: Rcv hello from 9.9.0.4 area 0 from GigabitEthernet0/0/0/0.34
9.9.34.4 (nbr/if state 3/5) vrf default vrfid 0x60000000
RP/0/0/CPU0:Jun 11 18:53:42.109 : ospf[1014]: Mismatched hello parameters from 9.9.34.4
RP/0/0/CPU0:Jun 11 18:53:42.109 : ospf[1014]: Trap of type 4 is not enabled
RP/0/0/CPU0:Jun 11 18:53:42.109 : ospf[1014]: Dead R 40 C 80, Hello R 10 C 20 Mask R 255.255.255.0 C
255.255.255.0
RP/0/0/CPU0:Jun 11 18:53:42.109 : ospf[1014]: hello from 9.9.0.4 area 0 failed validation
Looks some mesh with hello timings:
RP/0/0/CPU0:CPS_R0_R3#show ospf interface g0/0/0/0.34 | i Hello

Wed Jun 11 18:56:17.678 UTC
RP/0/0/CPU0:CPS_R0_R4#show ospf interface g0/0/0/0.34 | i Hello

Wed Jun 11 18:57:42.782 UTC
Default hello timer is 10 sec with multiplier 4 on broadcast media for OSPF but R4 is sending hello interval 20 sec
with dead 80 sec (20x4). To form OSPF adjacency hello and dead timers should match.
RP/0/0/CPU0:CPS_R0_R3#show running-config router ospf

Wed Jun 11 19:01:16.287 UTC
router ospf 9
router-id 9.9.0.3
area 0
interface Loopback0
!
!
hello-interval 20
!
Here is the issue, lets correct it:
Wed Jun 11 19:03:58.626 UTC
RP/0/0/CPU0:CPS_R0_R3(config)#router ospf 9
RP/0/0/CPU0:CPS_R0_R3(config-ospf)# router-id 9.9.0.3
RP/0/0/CPU0:CPS_R0_R3(config-ospf)# area 0
RP/0/0/CPU0:CPS_R0_R3(config-ospf-ar-if)# interface GigabitEthernet0/0/0/0.34
RP/0/0/CPU0:CPS_R0_R3(config-ospf-ar-if)# no hello-interval 20
RP/0/0/CPU0:CPS_R0_R3(config-ospf-ar-if)#commit
Wed Jun 11 19:04:18.515 UTC
RP/0/0/CPU0:CPS_R0_R3(config-ospf-ar-if)#end
RP/0/0/CPU0:CPS_R0_R3#sh ospf neighbor | i .34

Wed Jun 11 19:05:53.208 UTC
RP/0/0/CPU0:CPS_R0_R3#sh route ospf | i .34

Wed Jun 11 19:06:02.858 UTC
Lets check for R3 and R5 adjacency:
RP/0/0/CPU0:CPS_R0_R3#sh ospf interface brief | i.35

Wed Jun 11 20:06:50.578 UTC
Gi0/0/0/0.35 9 0 9.9.35.3/24 1 DR 0/0
CPS_R0_R5#sh ip ospf interface brief

Lo0 9 0 9.9.0.5/32 1 LOOP 0/0
Et0/0 9 1 9.9.35.5/24 1 DR 0/0
Et0/1 9 10 9.9.56.5/24 1 DR 0/0
CPS_R0_R5#
We can see R5 interface E0/0 which is connecting to R3 is advertised in wrong area 1, yo form OSPF adjacency
apart from timers area id should also match, lets see in debug what does it show on R3:
RP/0/0/CPU0:CPS_R0_R3#debug ospf 9 adj gigabitEthernet 0/0/0/0.35

Wed Jun 11 20:14:04.088 UTC
RP/0/0/CPU0:CPS_R0_R3#RP/0/0/CPU0:Jun 11 20:14:04.848 : ospf[1014]: Rcv pkt from 9.9.35.5,
GigabitEthernet0/0/0/0.35, area 0.0.0.0 mismatch area 0.0.0.1 in the header
Lets fix it on R5:

router ospfv3 9
router-id 9.9.0.3
!
exit-address-family
router ospf 9
router-id 9.9.0.5
network 9.9.0.5 0.0.0.0 area 0
network 9.9.35.0 0.0.0.255 area 1
network 9.9.56.0 0.0.0.255 area 10
CPS_R0_R5#conf t
RP/0/0/CPU0:CPS_R0_R3#show ospf neighbor | i .35

Wed Jun 11 20:19:48.435 UTC
RP/0/0/CPU0:CPS_R0_R3#show route ospf | i .35

Wed Jun 11 20:19:57.624 UTC
Finally, lets check for R3 and R7 adjacency:
RP/0/0/CPU0:CPS_R0_R3#show ospf interface brief | i .37

Wed Jun 11 20:21:44.787 UTC
CPS_R0_R7#sh ip ospf interface brief | i Et0/2

Et0/2 9 1 9.9.37.7/24 1 DR 0/0
CPS_R0_R7#
R3 has not enabled interface connecting to R7 (Gi0/0/0/0.37) for OSPF routing protocol, lets do it:
Wed Jun 11 20:27:53.341 UTC
router ospf 9
router-id 9.9.0.3
area 0
interface Loopback0
!
!
!
!
!
!
Wed Jun 11 20:28:20.700 UTC
RP/0/0/CPU0:CPS_R0_R3(config-ospf)#area 0
RP/0/0/CPU0:CPS_R0_R3(config-ospf-ar)#interface GigabitEthernet0/0/0/0.37
Wed Jun 11 20:28:43.288 UTC

Wed Jun 11 20:29:46.674 UTC


Its still down, lets check further:
RP/0/0/CPU0:CPS_R0_R3#debug ospf 9 adj GigabitEthernet0/0/0/0.37

Wed Jun 11 20:31:03.918 UTC
RP/0/0/CPU0:CPS_R0_R3#RP/0/0/CPU0:Jun 11 20:31:10.698 : ospf[1014]: Rcv pkt from 9.9.37.7,
GigabitEthernet0/0/0/0.37, area 0.0.0.0 mismatch area 0.0.0.1 in the header
Lets correct area on the R7 interface Eth0/2 which is connecting to R3:

router ospf 9
router-id 9.9.0.7
network 9.9.0.7 0.0.0.0 area 0
network 9.9.27.0 0.0.0.255 area 0
network 9.9.34.0 0.0.0.255 area 0
network 9.9.37.0 0.0.0.255 area 1
ipv6 router ospf 9
CPS_R0_R7#conf t
CPS_R0_R7(config-router)#
CPS_R0_R7(config-router)#
*Jun 11 20:34:37.674: %OSPF-6-AREACHG: 9.9.37.0/24 changed from area 1 to area 0
*Jun 11 20:34:47.177: %OSPF-5-ADJCHG: Process 9, Nbr 9.9.0.3 on Ethernet0/2 from LOADING to FULL, Loading
Done
A final snapshot of R3 OSPF adjacency and routing table:

Wed Jun 11 20:38:15.499 UTC


Wed Jun 11 20:38:22.008 UTC

Lets move to R4:

Wed Jun 11 20:43:57.915 UTC


R4 has only one neighbor up, it needs to have 3 neighbors, lets check first for R4 and R6.

Wed Jun 11 20:45:33.329 UTC
Gi0/0/0/0.46 9 10 9.9.46.4/24 1 DR 0/0
we can see both side interfaces are enabled for OSPF routing protocol with wrong area id on R4, it has configured
area id 10 for interface connecting to R6, lets correct it:

Wed Jun 11 20:49:13.494 UTC
router ospf 9
router-id 9.9.0.4
area 0
interface Loopback0
!
!
!
!
area 10
Wed Jun 11 20:49:55.541 UTC
RP/0/0/CPU0:CPS_R0_R4(config-ospf)#no area 10
RP/0/0/CPU0:CPS_R0_R4(config-ospf)#area 0
RP/0/0/CPU0:CPS_R0_R4(config-ospf-ar)#interface GigabitEthernet0/0/0/0.46
Wed Jun 11 20:50:28.079 UTC
Wed Jun 11 20:51:52.263 UTC

9.9.0.6 1 EXCHANGE/DR 00:00:36 9.9.46.6 GigabitEthernet0/0/0/0.46

Now adjacency is stuck in Exchange state.
"OSPF neighbors that are in exstart or exchange state are trying to exchange DBD packets. The router and its
neighbor form a master and slave relationship. The adjacency should continue past this state. If it does not, there is
a problem with the DBD exchange, such as a maximum transmission unit (MTU) mismatch or the receipt of an
unexpected DBD sequence number." Cisco Documentation
Lets do a adjacency debug on R4 and see if we can get something:
Wed Jun 11 20:56:24.484 UTC
Wed Jun 11 20:56:33.924 UTC
RP/0/0/CPU0:Jun 11 20:57:00.292 : ospf[1014]: 2 Way Communication to 9.9.0.6 on GigabitEthernet0/0/0/0.46,
state 2WAY
RP/0/0/CPU0:Jun 11 20:57:00.292 : ospf[1014]: Neighbor change Event on intf GigabitEthernet0/0/0/0.46
RP/0/0/CPU0:Jun 11 20:57:00.292 : ospf[1014]: DR/BDR election on GigabitEthernet0/0/0/0.46
RP/0/0/CPU0:Jun 11 20:57:00.292 : ospf[1014]: Elect BDR Router ID 0.0.0.0(IP Addr 0.0.0.0)
RP/0/0/CPU0:Jun 11 20:57:00.292 : ospf[1014]: Elect DR Router ID 9.9.0.6(IP Addr 9.9.46.6)
RP/0/0/CPU0:Jun 11 20:57:00.292 : ospf[1014]: Elect BDR Router ID 9.9.0.4(IP Addr 9.9.46.4)
RP/0/0/CPU0:Jun 11 20:57:00.292 : ospf[1014]: Elect DR Router ID 9.9.0.6(IP Addr 9.9.46.6)
RP/0/0/CPU0:Jun 11 20:57:00.292 : ospf[1014]: DR: 9.9.0.6(Id) 9.9.46.6(IP Addr)
RP/0/0/CPU0:Jun 11 20:57:00.292 : ospf[1014]: BDR: 9.9.0.4(Id) 9.9.46.4(IP Addr)
RP/0/0/CPU0:Jun 11 20:57:00.292 : ospf[1014]: Send DBD to 9.9.0.6(9.9.46.6) on GigabitEthernet0/0/0/0.46 seq
0x40dd opt 0x52 flag 0x7 len 32, vrf default vrfid 0x60000000
RP/0/0/CPU0:Jun 11 20:57:00.292 : ospf[1014]: Flush network LSA immediately
RP/0/0/CPU0:Jun 11 20:57:00.292 : ospf[1014]: NBR Negotiation Done. We are the SLAVE for nbr 9.9.0.6 on
GigabitEthernet0/0/0/0.46, area 0
RP/0/0/CPU0:Jun 11 20:57:00.292 : ospf[1014]: build dbd: took 0 ms for nbr 9.9.0.6, count=11, vrf default vrfid
0x60000000
RP/0/0/CPU0:Jun 11 20:57:00.292 : ospf[1014]: Send DBD to 9.9.0.6(9.9.46.6) on GigabitEthernet0/0/0/0.46 seq
0x3ad opt 0x52 flag 0x2 len 252, vrf default vrfid 0x60000000
RP/0/0/CPU0:Jun 11 20:57:04.961 : ospf[1014]: Rcv DBD from 9.9.0.6(9.9.46.6) on GigabitEthernet0/0/0/0.46
seq 0x3ad opt 0x52 flag 0x7 len 32 mtu 1400 state EXCHANGE vrf default vrfid 0x60000000
CPS_R0_R6#show running-config interface Ethernet0/0

!
bandwidth 100000
ip address 9.9.46.6 255.255.255.0
ip mtu 1400
ip pim sparse-mode
ipv6 address 2002:9:9:46::6/64
mpls ip
end
CPS_R0_R6#conf t
CPS_R0_R6(config-if)#no ip mtu 1400

Wed Jun 11 21:02:17.540 UTC

Wed Jun 11 21:02:27.999 UTC
Lets now check for the R4 last OSPF neighbor, R7:

Wed Jun 11 21:05:48.896 UTC
Gi0/0/0/0.47 9 0 9.9.47.4/24 1 DR 0/0

Lo0 9 0 9.9.0.7/32 1 LOOP 0/0
Et0/2 0 9.9.37.7/24 1 BDR 1/1
Et0/1 9 0 9.9.27.7/24 1 BDR 1/1
CPS_R0_R7#
Interface Eth0/0 which connects to R4 is not enabled for OSPF routing, lets do it:

router ospf 9
router-id 9.9.0.7
network 9.9.0.7 0.0.0.0 area 0
network 9.9.27.0 0.0.0.255 area 0
network 9.9.34.0 0.0.0.255 area 0
network 9.9.37.0 0.0.0.255 area 0
ipv6 router ospf 9
CPS_R0_R7#conf t
CPS_R0_R7#
CPS_R0_R7#ping 9.9.47.4
!!!!!
CPS_R0_R7#
Now its showing stuck in EXSTART state:

Wed Jun 11 21:12:22.129 UTC
9.9.0.7 1 EXSTART/DR 00:00:39 9.9.47.7 GigabitEthernet0/0/0/0.47
Wed Jun 11 21:15:32.016 UTC
RP/0/0/CPU0:CPS_R0_R4#RP/0/0/CPU0:Jun 11 21:15:36.655 : ospf[1014]: Rcv DBD from 9.9.0.7(9.9.47.7) on
GigabitEthernet0/0/0/0.47 seq 0x1b45 opt 0x52 flag 0x7 len 32 mtu 1500 state EXSTART vrf default vrfid
0x60000000
RP/0/0/CPU0:Jun 11 21:15:36.655 : ospf[1014]: Nbr 9.9.0.7 has larger interface MTU
It says neighbor has larger MTU size, lets check and fix it:
CPS_R0_R7#show interfaces ethernet 0/0 | i MTU

MTU 1500 bytes, BW 100000 Kbit/sec, DLY 1000 usec,
CPS_R0_R7#
RP/0/0/CPU0:CPS_R0_R4#show interfaces gigabitEthernet 0/0/0/0.47 | i MTU

Wed Jun 11 21:19:07.921 UTC
MTU 1300 bytes, BW 1000000 Kbit (Max: 1000000 Kbit)
R7 has MTU 1500 which is by default for ethernet media, R4 is showing MTU size 1300, lets check and correct it:

Wed Jun 11 21:21:12.882 UTC
mtu 1300
ipv4 address 9.9.47.4 255.255.255.0
ipv6 address 2002:9:9:47::4/64
Wed Jun 11 21:21:48.820 UTC
RP/0/0/CPU0:CPS_R0_R4(config)#interface gigabitEthernet 0/0/0/0.47
RP/0/0/CPU0:CPS_R0_R4(config-subif)#no mtu 1300
RP/0/0/CPU0:CPS_R0_R4(config-subif)#commit
Wed Jun 11 21:22:04.239 UTC
RP/0/0/CPU0:CPS_R0_R4(config-subif)#end

Wed Jun 11 21:23:22.633 UTC
Wed Jun 11 21:23:33.413 UTC
Looks good.
Lets move to R5:

9.9.0.3 1 FULL/DR 00:00:39 9.9.35.3 Ethernet0/0
CPS_R0_R5#
R5 neighbors R3 showing up, lets check for its second neighbor R6:

Lo0 9 0 9.9.0.5/32 1 LOOP 0/0
Et0/0 9 0 9.9.35.5/24 1 BDR 1/1
Et0/1 9 10 9.9.56.5/24 1 DR 0/0
CPS_R0_R5#

Lo0 9 0 9.9.0.6/32 1 LOOP 0/0
Et0/0 9 0 9.9.46.6/24 1 DR 1/1
Et0/1 9 1 9.9.56.6/24 1 P2P 0/0
CPS_R0_R6#ping 9.9.56.5
!!!!!
CPS_R0_R6#
Connectivity and OSPF routing enablement look right. Lets do a debug and check on R5:
CPS_R0_R5#debug ip ospf adj

OSPF adjacency debugging is on
CPS_R0_R5#conf t
CPS_R0_R5#
*Jun 11 21:32:50.666: OSPF-9 ADJ Et0/1: Rcv pkt from 9.9.56.6, area 0.0.0.10, mismatched area 0.0.0.1 in the
header
Wrong area ids are configured at both ends, lets correct them and check:

router ospfv3 9
router-id 9.9.0.3
router ospf 9
router-id 9.9.0.5
network 9.9.0.5 0.0.0.0 area 0
network 9.9.35.0 0.0.0.255 area 0
network 9.9.56.0 0.0.0.255 area 10
CPS_R0_R5#
CPS_R0_R5#conf t
CPS_R0_R5(config-router)# network 9.9.56.0 0.0.0.255 area 0
*Jun 11 21:36:36.479: %OSPF-6-AREACHG: 9.9.56.0/24 changed from area 10 to area 0

router ospfv3 9
router-id 9.9.0.6
!
exit-address-family
router ospf 9
router-id 9.9.0.6
network 9.9.0.6 0.0.0.0 area 0
network 9.9.46.0 0.0.0.255 area 0
network 9.9.56.0 0.0.0.255 area 1
CPS_R0_R6#conf t

9.9.0.6 1 FULL/BDR 00:00:36 9.9.56.6 Ethernet0/1
9.9.0.3 1 FULL/DR 00:00:31 9.9.35.3 Ethernet0/0
CPS_R0_R5#

O 9.9.0.2/32 [110/3] via 9.9.35.3, 00:03:46, Ethernet0/0
O 9.9.0.3/32 [110/2] via 9.9.35.3, 00:03:46, Ethernet0/0
O 9.9.0.4/32 [110/3] via 9.9.35.3, 00:03:46, Ethernet0/0
O 9.9.0.6/32 [110/4] via 9.9.35.3, 00:03:46, Ethernet0/0
O 9.9.0.7/32 [110/3] via 9.9.35.3, 00:03:46, Ethernet0/0
O 9.9.23.0/24 [110/2] via 9.9.35.3, 00:03:46, Ethernet0/0
O 9.9.27.0/24 [110/3] via 9.9.35.3, 00:03:46, Ethernet0/0
O 9.9.34.0/24 [110/2] via 9.9.35.3, 00:03:46, Ethernet0/0
O 9.9.37.0/24 [110/2] via 9.9.35.3, 00:03:46, Ethernet0/0
O 9.9.46.0/24 [110/3] via 9.9.35.3, 00:03:46, Ethernet0/0
O 9.9.47.0/24 [110/3] via 9.9.35.3, 00:03:46, Ethernet0/0
CPS_R0_R5#
No routes from R6, even R6 loopback is coming via R3.
CPS_R0_R5#show ip ospf interface ethernet 0/1
Process ID 9, Router ID 9.9.0.5, Network Type BROADCAST, Cost: 1
0 1 no no Base
Transmit Delay is 1 sec, State DR, Priority 1
Designated Router (ID) 9.9.0.5, Interface address 9.9.56.5
Backup Designated router (ID) 9.9.0.6, Interface address 9.9.56.6
Next 0x0(0)/0x0(0)
Adjacent with neighbor 9.9.0.6 (Backup Designated Router)
CPS_R0_R5#
CPS_R0_R6#show ip ospf interface ethernet 0/1

Process ID 9, Router ID 9.9.0.6, Network Type POINT_TO_POINT, Cost: 1
0 1 no no Base
Transmit Delay is 1 sec, State POINT_TO_POINT
Next 0x0(0)/0x0(0)
Adjacent with neighbor 9.9.0.5
CPS_R0_R6#
Its network type mismatch, lets correct it at R6:


!
bandwidth 100000
ip address 9.9.56.6 255.255.255.0
ip pim sparse-mode
ipv6 address 2002:9:9:56::6/64
mpls ip
ipv6 ospf 9 area 0
end
CPS_R0_R6#conf t
CPS_R0_R6(config)#interface Ethernet0/1
CPS_R0_R6(config-if)#no ip ospf network point-to-point
O 9.9.0.2/32 [110/3] via 9.9.35.3, 00:13:17, Ethernet0/0

O 9.9.0.3/32 [110/2] via 9.9.35.3, 00:13:17, Ethernet0/0
O 9.9.0.4/32 [110/3] via 9.9.56.6, 00:00:21, Ethernet0/1
[110/3] via 9.9.35.3, 00:13:17, Ethernet0/0
O 9.9.0.6/32 [110/2] via 9.9.56.6, 00:00:21, Ethernet0/1
O 9.9.0.7/32 [110/3] via 9.9.35.3, 00:13:17, Ethernet0/0
O 9.9.23.0/24 [110/2] via 9.9.35.3, 00:13:17, Ethernet0/0
O 9.9.27.0/24 [110/3] via 9.9.35.3, 00:13:17, Ethernet0/0
O 9.9.34.0/24 [110/2] via 9.9.35.3, 00:13:17, Ethernet0/0
O 9.9.37.0/24 [110/2] via 9.9.35.3, 00:13:17, Ethernet0/0
O 9.9.46.0/24 [110/2] via 9.9.56.6, 00:00:21, Ethernet0/1
O 9.9.47.0/24 [110/3] via 9.9.56.6, 00:00:21, Ethernet0/1
[110/3] via 9.9.35.3, 00:13:17, Ethernet0/0
CPS_R0_R5#
Perfect.
Now the last one R7, there should not be any problem with that at this stage we have already fixed problems on his
neighbors, lets check on that:

9.9.0.3 1 FULL/DR 00:00:36 9.9.37.3 Ethernet0/2
9.9.0.2 1 FULL/DR 00:00:32 9.9.27.2 Ethernet0/1
CPS_R0_R7#
O 9.9.0.2/32 [110/2] via 9.9.27.2, 01:19:05, Ethernet0/1
O 9.9.0.3/32 [110/2] via 9.9.37.3, 01:18:50, Ethernet0/2
O 9.9.0.4/32 [110/2] via 9.9.47.4, 00:31:31, Ethernet0/0
O 9.9.0.5/32 [110/3] via 9.9.37.3, 01:18:50, Ethernet0/2
O 9.9.0.6/32 [110/3] via 9.9.47.4, 00:31:31, Ethernet0/0
O 9.9.23.0/24 [110/2] via 9.9.37.3, 01:18:50, Ethernet0/2
[110/2] via 9.9.27.2, 01:19:05, Ethernet0/1
O 9.9.34.0/24 [110/2] via 9.9.47.4, 00:31:31, Ethernet0/0
[110/2] via 9.9.37.3, 01:18:50, Ethernet0/2
O 9.9.35.0/24 [110/2] via 9.9.37.3, 01:18:50, Ethernet0/2
O 9.9.46.0/24 [110/2] via 9.9.47.4, 00:31:31, Ethernet0/0
O 9.9.56.0/24 [110/3] via 9.9.47.4, 00:04:10, Ethernet0/0
[110/3] via 9.9.37.3, 00:17:00, Ethernet0/2
CPS_R0_R7#
All set for OSPF IPv4, lets have a final check on all devices:
R2

Wed Jun 11 21:55:28.892 UTC


Wed Jun 11 21:55:33.351 UTC

R2 supposed to have 2 neighbors, all interlink and loopbacks routes in AS 9, which it has.
R3

Wed Jun 11 21:57:55.951 UTC


Wed Jun 11 21:58:01.331 UTC

R4

Wed Jun 11 22:00:33.881 UTC


Wed Jun 11 22:00:42.050 UTC

R5

9.9.0.3 1 FULL/DR 00:00:31 9.9.35.3 Ethernet0/0
CPS_R0_R5#
CPS_R0_R5#sh ip route ospf | b last
O 9.9.0.2/32 [110/3] via 9.9.35.3, 00:28:04, Ethernet0/0
O 9.9.0.3/32 [110/2] via 9.9.35.3, 00:28:04, Ethernet0/0
O 9.9.0.4/32 [110/3] via 9.9.56.6, 00:15:08, Ethernet0/1
[110/3] via 9.9.35.3, 00:28:04, Ethernet0/0
O 9.9.0.6/32 [110/2] via 9.9.56.6, 00:15:08, Ethernet0/1
O 9.9.0.7/32 [110/3] via 9.9.35.3, 00:28:04, Ethernet0/0
O 9.9.23.0/24 [110/2] via 9.9.35.3, 00:28:04, Ethernet0/0
O 9.9.27.0/24 [110/3] via 9.9.35.3, 00:28:04, Ethernet0/0
O 9.9.34.0/24 [110/2] via 9.9.35.3, 00:28:04, Ethernet0/0
O 9.9.37.0/24 [110/2] via 9.9.35.3, 00:28:04, Ethernet0/0
O 9.9.46.0/24 [110/2] via 9.9.56.6, 00:15:08, Ethernet0/1
O 9.9.47.0/24 [110/3] via 9.9.56.6, 00:15:08, Ethernet0/1
[110/3] via 9.9.35.3, 00:28:04, Ethernet0/0
CPS_R0_R5#
R6

9.9.0.5 1 FULL/DR 00:00:34 9.9.56.5 Ethernet0/1

O 9.9.0.2/32 [110/4] via 9.9.56.5, 00:16:18, Ethernet0/1
[110/4] via 9.9.46.4, 00:26:17, Ethernet0/0
O 9.9.0.3/32 [110/3] via 9.9.56.5, 00:16:18, Ethernet0/1
[110/3] via 9.9.46.4, 00:26:17, Ethernet0/0
O 9.9.0.4/32 [110/2] via 9.9.46.4, 00:26:17, Ethernet0/0
O 9.9.0.5/32 [110/2] via 9.9.56.5, 00:16:18, Ethernet0/1
O 9.9.0.7/32 [110/3] via 9.9.46.4, 00:26:17, Ethernet0/0
O 9.9.23.0/24 [110/3] via 9.9.56.5, 00:16:18, Ethernet0/1
[110/3] via 9.9.46.4, 00:26:17, Ethernet0/0
O 9.9.27.0/24 [110/3] via 9.9.46.4, 00:26:17, Ethernet0/0
O 9.9.34.0/24 [110/2] via 9.9.46.4, 00:26:17, Ethernet0/0
O 9.9.35.0/24 [110/2] via 9.9.56.5, 00:16:18, Ethernet0/1
O 9.9.37.0/24 [110/3] via 9.9.56.5, 00:16:18, Ethernet0/1
[110/3] via 9.9.46.4, 00:26:17, Ethernet0/0
O 9.9.47.0/24 [110/2] via 9.9.46.4, 00:26:17, Ethernet0/0
CPS_R0_R6#

9.9.0.3 1 FULL/DR 00:00:36 9.9.37.3 Ethernet0/2
9.9.0.2 1 FULL/DR 00:00:32 9.9.27.2 Ethernet0/1
CPS_R0_R7#sho

O 9.9.0.2/32 [110/2] via 9.9.27.2, 01:19:05, Ethernet0/1
O 9.9.0.3/32 [110/2] via 9.9.37.3, 01:18:50, Ethernet0/2
O 9.9.0.4/32 [110/2] via 9.9.47.4, 00:31:31, Ethernet0/0
O 9.9.0.5/32 [110/3] via 9.9.37.3, 01:18:50, Ethernet0/2
O 9.9.0.6/32 [110/3] via 9.9.47.4, 00:31:31, Ethernet0/0
O 9.9.23.0/24 [110/2] via 9.9.37.3, 01:18:50, Ethernet0/2
[110/2] via 9.9.27.2, 01:19:05, Ethernet0/1
O 9.9.34.0/24 [110/2] via 9.9.47.4, 00:31:31, Ethernet0/0
[110/2] via 9.9.37.3, 01:18:50, Ethernet0/2
O 9.9.35.0/24 [110/2] via 9.9.37.3, 01:18:50, Ethernet0/2
O 9.9.46.0/24 [110/2] via 9.9.47.4, 00:31:31, Ethernet0/0
O 9.9.56.0/24 [110/3] via 9.9.47.4, 00:04:10, Ethernet0/0
[110/3] via 9.9.37.3, 00:17:00, Ethernet0/2
CPS_R0_R7#
We have covered complete pool of the questions till date for this question, in brief those all are here:
R2 and R7 OSPF neighborship is down, fix the problem.

Practice Labs are provided for Troubleshooting OSPF Adjacency Issues cover its in detail.
A good reference document for Troubleshooting OSPF Adajacency Issues:
http://www.cisco.com/c/en/us/support/docs/ip/open-shortest-path-first-ospf/13699-29.html
Single Topic Learning Labs Kit
3.1
GNS3 Simulation Setup for Single Labs
To run GNS net files provided with Single Labs require additional software installation and configuration:
Download below items and keep handy before heading to next step:
Cisco XRv: iosxrv-demo-5.1.2.ova

IOS: c7200-advipservicesk9-mz.122-33.SRE2.bin
IOS: c3660-jsx-mz.123-4.T.bin
GNS3-0.8.6-all-in-one or higher version
Oracle Virtual box
GNS3 Installation
Run the setup and click on next next
Complete install with default options
Install Oracle Virtual box

Run the setup and click on next next
Complete install with default options
Open Virtual box
Click at File Menu and select Import Appliance:
Click on folder icon and bourse to select the file iosxrv-demo-5.1.2.ova:
Click on Next:
Select the Name
Tick the MAC Address Option
Click on import:
It will take a minute or two, if you have downloaded the correct file:
New Machine is imported:
Select machine name
Click on settings:
Click on System
Reduce RAM to 3072 MB (Later you can play for actual size, recommended RAM capacity is 3 GB)
Uncheck Floppy
Uncheck CD/DVD:
Click on Network
Enable Adapter one
Follow settings in screenshot below:
Repeat it for all 4 Adapters one by one.
Click on OK:
VirtualBox Configuration is completed.

If you want to run more than 1 XRv, replicate this host to create multiple hosts one by one.
You can close the Virtual box application, no need to keep it open GNS 3 will take care of that part.
Open GNS3
Click on Edit menu
Select and click on IOS Images and hypervisors:
Click on Image file icon
Browse the 7200 image file
Click on save
Browse the 3600 image file
Click on save
Click on close:
Click on Edit menu
Select and click on Preferences
Select Dynamips
Click on Test Settings
Wait for a minute for the message:
Click on VirtualBox
Click on Test Settings
Wait for a minute for the message:
Click on VirtualBox Guest tab
Type an Identifier name
Click on VM List and select com.cisco.ios.xrv
Increase the number of NICs to 4
Uncheck NAT to Host
Tick the Enable Console
Tick the Headless Mode
Click on save:
If you have created multiple hosts in virtual box, all of them will show here in VM list, you can select and configure
one by one to run multiple XRv routers.
Click on Apply:
If you are familiar with GNS 3,create a topology, drag a virtual host and connect with devices.
Do not use interface e0 to connect any device, thatinterface is reserved for management purpose.
Make sure to select NIC Type as per below screenshots:
If you are not familiar with GNS 3, click on file menu, select open a project import provided net file and check the
NIC type as below:
Double click on Virtual Host Icon to open the Settings to set or check NIC Types:
Click on Virtual host name
Set NIC numbers to 4 if not already
Select the NIC Model to e1000:
Start all devices by a click on Green Indicator; you can start one by one by left click on device icon
Wait for a minute or two, until color gets change to green:
Wait for 1-3 minutes, XR willinitialize and load the factory configurations
Login with cisco/cisco:
Due to bug in GNS3 3.8 to make L2/L3 connectivity through,once all devices in topology up and running delete/add
XR connections one by one, delete it witha device wait for few seconds, connect that back to same interface where
it was connectedbefore deleting, do this for all the XR connections one by one, delete/add only connections from
XR, do not delete/add other connections:
Thank You
1.1.0 ISIS Basics
Content Removed
1.1.1 Implement ISIS
Configure ISIS to make all the hosts reachable to each other.
R1 and R2 should be configured in ISIS Area 49.0012 and R3 and R4 should be in Area 49.0034.
Physical Topology
Logical Topology
Host-2 192.168.2.2
G0/0//0.23 23.3
VLAN 23
F0/0.23 23.1
VLAN 23
F0/0.12 12.2
VLAN 12 SRE-R2
Host-3 192.168.3.3
G0/0//1 13.3
XRV-R3
G0/0//0.34 34.3
VLAN 34
F0/1 13.1
F0/0.12 12.1 F0/0.34 34.4

VLAN 12 VLAN 34
F0/0 14.1 F0/0.14 14.2

VLAN 14 VLAN 14
Host-1 192.168.1.1
SRE-R1 SRE-R4 Host-1 192.168.4.4
Basic Configuration:
SW
Vlan database
!
vlan 12
!
vlan 13
!
vlan 14
!
vlan 23
!
vlan 34
!
apply
!
exit
interface range FastEthernet1/1 -4

switchport mode trunk
switchport trunk encapsulation dot1q
no shut
!
interface FastEthernet1/1
description connects to R1 interface f0/0
switchport trunk allowed vlan 1,2,12,14,1002-1005
!
!
description connects to XR-R3 interface Gi0/0/0/0
switchport trunk allowed vlan 1,2,13,23,34,1002-1005
!
R1
no shut
!
interface FastEthernet0/0.12
ip add 192.168.12.1 255.255.255.252
!
ip add 192.168.14.1 255.255.255.252
!
ip add 192.168.13.1 255.255.255.252
!
interface loopback0
ip add 192.168.1.1 255.255.255.255
R2
no shut
!
ip add 192.168.12.2 255.255.255.252
!
ip add 192.168.23.1 255.255.255.252
!
interface loopback0
ip add 192.168.2.2 255.255.255.255
R3
interface GigabitEthernet0/0/0/0
no shut
!
ip add 192.168.23.2/24
!
ip add 192.168.34.1/24
ip add 192.168.13.2/24
no shut
!
interface loopback0
ip add 192.168.3.3/32
!
R4
no shut
!
ip add 192.168.14.2 255.255.255.252
!
ip add 192.168.34.2 255.255.255.252
!
interface loopback0
ip add 192.168.4.4 255.255.255.255
Verify basic ip connectivity, check all the interfaces are configured correct IP addresses according to the drawing,
vlans are created and correct interfaces assigned to them.
Enable ISIS on R1:
router isis
net 49.0012.0000.0000.0001.00
!
ip router isis
!
ip router isis
!
ip router isis
!
interface loopback0
ip router isis
Enabling ISIS is two step processes on Cisco IOS:
Step 1:Enable it at Global level:
router isis
net 49.0001.0000.0000.0001.00
Step 2:Enable it at Interface level:
ip router isis
We can specify ISIS instance identity, its optional on Cisco IOS but mandatory for Cisco IOS XR.
router isis ABC

net 49.0001.0000.0000.0001.00
Lets verify it:
R1 is showing routing protocol ISIS enabled for 4 interfaces, maximum paths to reach a destination can be 4, route
summarization is not configured and default administrative distance for ISIS is 115.
Once we enable ISIS on an interface, by default it tries to establish adjacencies for both IS Types.
Lets complete ISIS configuration on other routers:
R2
router isis
net
!
ip router isis
!
ip router isis
!
interface loopback0
ip router isis
XRv-R3
router isis 3
net 49.0034.0000.0000.0003.00
!
!
!
!
interface loopback0
!
commit
R4
router isis
net 49.0034.0000.0000.0004.00
!
ip router isis
!
ip router isis
!
interface loopback0
ip router isis
Routers in same area form both Level 1 and Level 2 adjacencies if IS Type is not manually configured.
To form a Level 1 adjacency both routers should be in same area.
ISIS Adjacency between routers in different areas can be only Level 2.
ISIS Circuit Id is known as LAN Id, DR Id, DIS Id too.
To conclude both outputs, R1 is showing two neighbors R3 - R4 and receiving routes of their connected hosts but
where is R2? If we look at drawing, R1 is connected to R2 why that is not showing up in neighbors list of R1? Host
connected to R2 is also missing from R1 Routing Table.
We did enable ISIS on all R2 interface:
Output of showip protocols looks good, desired interfaces are enabled for ISIS routing.
ISIS is enabled on interface but no Circuit ID assigned to it; Circuit ID cannot be assigned unless we have configured
ISIS correctly, its the Id of DIS (DR in OSPF) in ISIS.
Here problem is more obvious; its not showing Area Id something certainly not good with ISIS NET Entity.
CPS-R01-R1#sh run | i net 49

net 49.0012.0000.0000.0001.00
CPS-R01-R1#
CPS-R01-R2#sh run | i net 49

CPS-R01-R2#
Lets reapply ISIS NET ID on R2:
router isis
net 49.0012.0000.0000.0002.00
Now we can see Area Id and System Id both.
R1 is showing both Level 1 and Level 2 neighbor ship with R2 while only Level 2 with R3 and R4. By default ISIS
routers in same area establish both Level 1 and Level 2 adjacencies.
R1 is receiving R2 Host 192.168.2.2 as Level 1 route while R3-R4 hosts as Level-2.

Metric for all routes installed in R1 Routing Table is 20, it has direct link to all the devices in domain.
Important thing here is the route for network 192.168.23.0/30 its between R2 R3, R1 is installing it from R2.
By default ISIS enabled routers prefer Level 1 route over Level 2.
In case of 2 or more routes with unequal metric and same Level Type, the one with lower metric gets installed in
routing table.
If metric is equal along with Level Type from multiple neighbors, up to 4 routes get installed in the routing table.
Network 192.168.34.0/30 between R3 R4 is being installed from both R3 and R4, not from R2. By default a L1 -
L2 ISIS router does not advertise routes received from Level 2 neighbor to a Level 1 neighbor.
Lets try to understand whats going on:
CPS-R01-R1#sh isis database verbose
IS-IS Level-1 Link State Database:

LSPID LSP SeqNum LSP Checksum LSP Holdtime ATT/P/OL
CPS-R01-R1.00-00 * 0x0000000F 0x20CF 675 1/0/0
Area Address: 49.0012
NLPID: 0xCC
Hostname: CPS-R01-R1
IP Address: 192.168.1.1
Metric: 10 IP 192.168.12.0 255.255.255.252
Metric: 10 IP 192.168.14.0 255.255.255.252
Metric: 10 IP 192.168.13.0 255.255.255.252
Metric: 10 IP 192.168.1.1 255.255.255.255
Metric: 10 IS CPS-R01-R2.02
CPS-R01-R2.00-00 0x0000000D 0xEC09 419 0/0/0

NLPID: 0xCC
IP Address: 192.168.2.2
Metric: 10 IP 192.168.2.2 255.255.255.255
Metric: 10 IP 192.168.12.0 255.255.255.252
Metric: 10 IP 192.168.23.0 255.255.255.252
CPS-R01-R2.02-00 0x00000005 0x6FDC 694 0/0/0

CPS-R01-XRv-R3.00-00 0x00000008 0x2432 178 0/0/0

NLPID: 0xCC
Hostname: CPS-R01-XRv-R3
IP Address: 192.168.3.3
Metric: 10 IP 192.168.3.3 255.255.255.255
Metric: 10 IP 192.168.13.0 255.255.255.0
Metric: 10 IP 192.168.23.0 255.255.255.0
Metric: 10 IP 192.168.34.0 255.255.255.252
CPS-R01-R4.00-00 0x00000007 0x6955 410 0/0/0

NLPID: 0xCC
IP Address: 192.168.4.4
Metric: 10 IP 192.168.4.4 255.255.255.255
Metric: 10 IP 192.168.14.0 255.255.255.252
Metric: 10 IP 192.168.34.0 255.255.255.252
CPS-R01-R4.02-00 0x00000003 0x7FCA 499 0/0/0
CPS-R01-R4.03-00 0x00000001 0xAE9A 176 0/0/0

Metric: 0 IS CPS-R01-XRv-R3.00

CPS-R01-R1.00-00 * 0x00000017 0xFD8C 607 0/0/0
NLPID: 0xCC
IP Address: 192.168.1.1
Metric: 10 IP 192.168.1.1 255.255.255.255
Metric: 20 IP 192.168.2.2 255.255.255.255
Metric: 10 IP 192.168.12.0 255.255.255.252
Metric: 10 IP 192.168.13.0 255.255.255.252
Metric: 10 IP 192.168.14.0 255.255.255.252
Metric: 20 IP 192.168.23.0 255.255.255.252
CPS-R01-R1.03-00 * 0x00000006 0x22B0 490 0/0/0

CPS-R01-R2.00-00 0x00000014 0xD248 606 0/0/0

NLPID: 0xCC
IP Address: 192.168.2.2
Metric: 20 IP 192.168.1.1 255.255.255.255
Metric: 10 IP 192.168.2.2 255.255.255.255
Metric: 10 IP 192.168.12.0 255.255.255.252
Metric: 20 IP 192.168.13.0 255.255.255.252
Metric: 20 IP 192.168.14.0 255.255.255.252
Metric: 10 IP 192.168.23.0 255.255.255.252
CPS-R01-R2.02-00 0x00000005 0xFED5 645 0/0/0

CPS-R01-R2.03-00 0x00000007 0x26A9 635 0/0/0

CPS-R01-XRv-R3.00-00 0x00000016 0x8C5C 600 0/0/0
NLPID: 0xCC
IP Address: 192.168.3.3
Metric: 10 IP 192.168.3.3 255.255.255.255
Metric: 20 IP 192.168.4.4 255.255.255.255
Metric: 10 IP 192.168.13.0 255.255.255.0
Metric: 20 IP 192.168.14.0 255.255.255.252
Metric: 10 IP 192.168.23.0 255.255.255.0
Metric: 10 IP 192.168.34.0 255.255.255.252
CPS-R01-R4.00-00 0x0000000D 0x0DC2 605 0/0/0

NLPID: 0xCC
IP Address: 192.168.4.4
Metric: 20 IP 192.168.3.3 255.255.255.255
Metric: 10 IP 192.168.4.4 255.255.255.255
Metric: 20 IP 192.168.13.0 255.255.255.0
Metric: 10 IP 192.168.14.0 255.255.255.252
Metric: 20 IP 192.168.23.0 255.255.255.0
Metric: 10 IP 192.168.34.0 255.255.255.252
CPS-R01-R4.02-00 0x00000004 0x0DC4 598 0/0/0

CPS-R01-R4.03-00 0x00000004 0x3896 598 0/0/0
CPS-R01-R1#
R2 is not advertising network 192.168.34.0 to R1, as Level 1 routers do not advertise routes received from Level 2
neighbors.
A Layer 1/Layer 2 router identifies itself by setting an attach-bit (ATT-bit) in its Layer 1 link-state packet (LSP).
Here Attached bit is set for top two LSPs.
RP/0/0/CPU0:CPS-R01-XRv-R3#sh isis interface brief
Sat May 31 04:22:36.251 UTC
IS-IS 3 Interfaces
Interface All AdjsAdjToposAdvTopos CLNS MTU Prio
OK L1 L2 Run/Cfg Run/Cfg L1 L2
----------------- --- --------- --------- --------- ---- ---- --------
Lo0 Yes 0 0 1/1 1/1 Up 1500 - -
Gi0/0/0/0.23 Yes 0 1 1/1 1/1 Up 1497 64 64
Gi0/0/0/0.34 Yes 1 1 1/1 1/1 Up 1497 64 64
Gi0/0/0/1 Yes 0 1 1/1 1/1 Up 1497 64 64
RP/0/0/CPU0:CPS-R01-XRv-R3#
CPS-R01-R1#tclsh
CPS-R01-R1(tcl)#foreach address {
+>192.168.1.1
+>192.168.2.2
+>192.168.3.3
+>}

!!!!!!!!!!
.!!!!!!!!!
!!!!!!!!!!
!!!!!!!!!!
CPS-R01-R1(tcl)#
CPS-R01-R1#tclsh
+>192.168.1.1
+>192.168.2.2
+>192.168.3.3
+>192.168.4.4} { trace $address source lo0
+>}
Tracing the route to 192.168.1.1
1 192.168.1.1 8 msec 8 msec 8 msec

1 192.168.12.2 36 msec 40 msec 32 msec

1 192.168.13.2 16 msec* 32msec

1 192.168.14.2 40 msec 48 msec 28 msec

CPS-R01-R1(tcl)#
1.1.2 ISIS Level 1
Configure all devices in ISIS area 49.1234.
All devices in network should form only ISIS Level 1 adjacencies.
Host-2 192.168.2.2
G0/0//0.23 23.3
VLA N 23
F0/0.23 23.1
VLA N 23
F0/0.12 12.2
VLA N 12 SRE-R2
Host-3 192.168.3.3
G0/0//1 13.3
XRV-R3
G0/0//0.34 34.3
VLA N 34
ISIS
Level 1
Area 49.1234 Ccieperfectsolutions.com
F0/1 13.1
F0/0.12 12.1 F0/0.34 34.4

VLA N 12 VLA N 34
F0/0 14.1 F0/0.14 14.2

VLA N 14 VLA N 14
Host-1 192.168.1.1
SRE-R1 SRE-R4 Host-1 192.168.4.4
Basic configurations are same as for 1.1.1
R1
router isis
is-type level-1
no net 49.0012.0000.0000.0001.00
net 49.1234.0000.0000.0001.00
!
end
!
clear isis *
R2
router isis
is-type level-1
no net 49.0012.0000.0000.0002.00
net 49.1234.0000.0000.0002.00
!
end
!
clear isis *
R4
router isis
is-type level-1
no net 49.0034.0000.0000.0004.00
net 49.1234.0000.0000.0004.00
!
end
!
clear isis *
R3
router isis 3
no net 49.0034.0000.0000.0003.00
net 49.1234.0000.0000.0003.00
is-type level-1
!
commit
!
end
!
clear isisafi-all unicast route
Verify the applied configurations for any copy paste or typing error.
Lets check on R1:
Though ISIS Level 1 is enabled on all devices globally above interface is still showing both Circuit Types. If we want
to see only Circuit Type Level 1, we need to enable Level 1 on the interface particularly.
Enabling ISIS Level 1 globally automatically disables Level 2 operations on the whole device as we can see Level 2
Metric and other attributes are disappeared.
Lets enable IS Type Level 1 on this interface and check:
R1
interface fastethernet0/0.12
isis circuit-type level-1
Circuit Type Level 2 is disappeared.
R2:
R4:
R3:
1.1.3 ISIS Level 2
Configure all devices in ISIS domain in below areas:
R1 49.0001
R2 49.0002
R3 49.0003
R4 49.0004
All devices in domain should form only Level 2 adjacencies.
Host-2 192.168.2.2
G0/0//0.23 23.3
VLA N 23
F0/0.23 23.1
VLA N 23
F0/0.12 12.2
VLA N 12 SRE-R2
Host-3 192.168.3.3
G0/0//1 13.3
XRV-R3
G0/0//0.34 34.3
VLA N 34
ISIS
Level 2
Ccieperfectsolutions.com
F0/1 13.1
F0/0.12 12.1 F0/0.34 34.4

VLA N 12 VLA N 34
F0/0 14.1 F0/0.14 14.2

VLA N 14 VLA N 14
Host-1 192.168.1.1
SRE-R1 SRE-R4 Host-1 192.168.4.4
Basic configurations are same as for 1.1.2.
R1
router isis
is-type level-2-only
no net 49.1234.0000.0000.0001.00
net 49.0001.0000.0000.0001.00
!
noisis circuit-type level-1
end
!
clear isis *
R2
router isis
no net 49.1234.0000.0000.0002.00
net 49.0002.0000.0000.0002.00
!
end
!
clear isis *
R4
router isis
no net 49.1234.0000.0000.0004.00
net 49.0002.0000.0000.0004.00
!
end
!
clear isis *
R3
router isis 3
no net 49.1234.0000.0000.0003.00
net 49.0003.0000.0000.0003.00
!
commit
!
Lets verify on R1:
R2
R4
R3
1.1.4ISIS Multi Level
Configure R1 in area 49.0124.

R1 should not form Inter Area ISIS adjacencies.
Configure R2 in area 49.0124 it should build Level 2 neighbor ship with R3.
Configure R3 in area 49.0234 it should build Level 2 neighbor ship with R4.
Configure R4 in area 49.0124 so that it can send default route to R1.
Basic configurations are same as for 1.1.3.
R1
interface fastethernet0/1
shutdown
!
router isis
is-type level-1
no net 49.0001.0000.0000.0001.00
net 49.0124.0000.0000.0001.00
!
end
!
clear isis *
R2
router isis
is-type level-1-2
no net 49.0002.0000.0000.0002.00
net 49.0124.0000.0000.0001.00
!
end
!
clear isis *
R4
router isis
is-type level-1-2
no net 49.0002.0000.0000.0004.00
net 49.0124.0000.0000.0004.00
!
end
!
clear isis *
R3
interface gigabitethernet0/0/0/1
shutdown
!
router isis 3
no net 49.0003.0000.0000.0003.00
net 49.0234.0000.0000.0003.00
!
commit
!
end
!
R1 has two ISIS Level 1 Adjacencies.
R1 is receiving Attached bit from both Level 1 2 adjacencies.
Instead of sending Level 2 routes, Level 1 - 2 routers generate a default route to its Level 1 neighbors.
In above output R1 is receiving default route from both the Level 1-2 peers but not the R3 host route 192.168.3.3.
This design has a serious loop issue if configured at the edge of network, to reach 192.168.3.3 R1 will do load
sharing by routing packets to its both Level 1-2 peers.
R3 Host 193.168.3.3 is not in R1 routing table, it has default route installed from two routers with traffic count
share 1.
Trace from R1 Host to R3 Host is passing via both R1 and R4.
Lets check the return path from R3 to R1:
RP/0/0/CPU0:CPS-R01-XRv-R3#sh ip route 192.168.1.1

Sat May 31 07:41:38.885 UTC
Routing entry for 192.168.1.1/32

Known via "isis 3", distance 115, metric 30, type level-2
Installed May 31 07:10:37.253 for 00:31:01
Routing Descriptor Blocks
192.168.23.1, from 192.168.2.2, via GigabitEthernet0/0/0/0.23
Route metric is 30
192.168.34.2, from 192.168.4.4, via GigabitEthernet0/0/0/0.34
Route metric is 30
No advertising protos.
RP/0/0/CPU0:CPS-R01-XRv-R3#traceroute 192.168.1.1 source 192.168.3.3
Sat May 31 07:41:52.274 UTC

1 192.168.34.2 19 msec 9 msec 9 msec

2 192.168.14.1 49 msec 39 msec 19 msec
R3 is also receiving R1 Host route from both R2 and R4, further it depends on the number of transit links. If we add
one more device either between R2 R3 or R4 R3, scenario will change, forward and reverse path will not remain
same.
R2 has two neighbors, R1 as Level 1 and R3 as Level 2.
It has attached bit associated for itself and R4.
As per above R2 will use R1 path to reach R4, generally Level 1 routers are considered Stub or Edge Routers.
R4 has two neighbors, R1 as Level 1 and R3 as Level 2.
It has attached bit associated for itself and R4.
Here again R4 will transit R1 to reach R2.
RP/0/0/CPU0:CPS-R01-XRv-R3#sh isis adjacency

Sat May 31 10:50:55.737 UTC
IS-IS 3 Level-2 adjacencies:

System Id Interface SNPA State Hold Changed NSF IPv4 IPv6
BFD BFD
CPS-R01-R2 Gi0/0/0/0.23 ca02.0fe4.0008 Up 7 03:44:14 Yes None None
CPS-R01-R4 Gi0/0/0/0.34 ca03.0c88.0008 Up 7 03:40:27 Yes None None
Total adjacency count: 2

R3 has two Level 2 neighbors, R2 and R4.
RP/0/0/CPU0:CPS-R01-XRv-R3#sh isis database

Sat May 31 10:51:06.217 UTC
IS-IS 3 (Level-2) Link State Database

CPS-R01-R2.00-00 0x00000018 0x560c 949 0/0/0
CPS-R01-R2.03-00 0x00000016 0x08b8 958 0/0/0
CPS-R01-XRv-R3.00-00* 0x00000022 0xa606 578 0/0/0
CPS-R01-R4.00-00 0x0000001b 0xd282 647 0/0/0
CPS-R01-R4.03-00 0x00000014 0x18a6 972 0/0/0
Total Level-2 LSP count: 5 Local Level-2 LSP count: 1
No attached bit association on R3.
RP/0/0/CPU0:CPS-R01-XRv-R3#sh route isis
Sat May 31 10:51:14.166 UTC

Perfect Routing Table for a core device.
Lets deal with Route Leaking options in next section to change the default ISIS behavior, by default Level 1 routers
only receive default route from boundary or Level 1-2 routers, at the Edge of network Level 1-2 routers use Level 1
router as transit path because of rule to prefer Level 1 routes over Level 2 to access their connected networks, if
they do not have ISIS Level 1 adjacency between them.
1.1.5 ISIS Route Leaking
Create additional Loopback1 (192.168.XX.XX/32) on R1 and R3.
Advertise these Loopbacks in to ISIS domain.
R2 should only advertise R3 Loopback0 to R1.

R4 should only advertise R3 Loopback1 to R1.
R2 should only advertise R1 Loopback0 to R3 from Level 1 ISIS database.

R4 should advertise R1 Loopback1 and other networks but not the loopback0 to R3.
Basic configurations and design remains intact as in 1.1.4.
Step 1:
R1
interface loopback1
ip add 192.168.11.11 255.255.255.255
ip router isis
R3
interface loopback1
ip add 192.168.33.33/32
!
router isis 3
interface loopback1
CPS-R01-R1#ping 192.168.33.33 source lo1

!!!!!
CPS-R01-R1#
Step 2:
R2
router isis
redistributeisisip level-2 into level-1 distribute-list 101
!
access-list 101 permit ip host 192.168.3.3 host 255.255.255.255
!
clear isis rib redistribution *
CPS-R01-R1#sh ip route isis | iia

i*L1 0.0.0.0/0 [115/10] via 192.168.14.2, 00:01:53, FastEthernet0/0.14
[115/10] via 192.168.12.2, 00:01:53, FastEthernet0/0.12
i L1 192.168.2.2 [115/20] via 192.168.12.2, 00:01:53, FastEthernet0/0.12
iia 192.168.3.3 [115/158] via 192.168.12.2, 00:01:53, FastEthernet0/0.12
CPS-R01-R1#
An access list has deny action at the end by default thats why only one route is getting redistributed. Host
255.255.255.255 is wildcard for 0.0.0.0 which means all IPv4 addresses are allowed.
R4
router isis
redistributeisisip level-2 into level-1 route-map level-2-to-level-1
!
route-map level-2-to-level-1 permit 10
matchip address 10
!
clear isis rib redistribution *
A route-map has deny action at the end by default thats why only one route is getting redistributed.
CPS-R01-R1#sh ip route isis | iia

iia 192.168.3.3 [115/158] via 192.168.12.2, 00:05:27, FastEthernet0/0.12
iia 192.168.33.33
CPS-R01-R1#
CPS-R01-R1#sh ip route 192.168.33.33
Routing entry for 192.168.33.33/32
Known via "isis", distance 115, metric 158, type inter area
Redistributing via isis
Last update from 192.168.14.2 on FastEthernet0/0.14, 00:02:38 ago
Routing Descriptor Blocks:
* 192.168.14.2, from 192.168.4.4, 00:02:38 ago, via FastEthernet0/0.14
Route metric is 158, traffic share count is 1
CPS-R01-R1#
Even if R2 and R4 respectively stop advertising loopbacks of R3, connectivity will work via default route.
Step 3:
R2
router isis
redistributeisisip level-1 into level-2 distribute-list 102
!
access-list 102 permit ip host 192.168.1.1 host 255.255.255.255

Sat May 31 13:05:46.143 UTC

Except 192.168.1.1/32, other routes are filtered.
R4
router isis
redistribute isis ip level-1 into level-2 route-map level-1-to-level-2
!
matchip address 12
!
access-list 12 permit host 192.168.11.11

Sat May 31 13:18:53.589 UTC

R4
access-list 12 deny host 192.168.1.1
access-list 12 permit any

Sat May 31 13:24:06.738 UTC

Now except R1 loopback 0, R3 is receiving everything from R4.
Are we done? Tricky part is still not completed:
R2 should only advertise R1 Loopback0 to R3 from Level 1 ISIS database.R2 needs to advertise its Level 2
database routes, lets look in to R2 database
CPS-R01-R2#sh isis database

CPS-R01-R1.00-00 0x00000039 0xC053 1020 0/0/0
CPS-R01-R2.00-00 * 0x0000002A 0x8625 545 1/0/0
CPS-R01-R2.02-00 * 0x00000020 0x39F7 575 0/0/0
CPS-R01-R4.00-00 0x00000030 0x4D01 1027 1/0/0
CPS-R01-R4.02-00 0x00000023 0x3FEA 1015 0/0/0

CPS-R01-R2.00-00 * 0x0000002E 0xFCDA 501 0/0/0
CPS-R01-R2.03-00 * 0x00000026 0xE7C8 1185 0/0/0
CPS-R01-XRv-R3.00-00 0x0000003F 0x420A 1019 0/0/0
CPS-R01-R4.00-00 0x0000003D 0x1A05 1022 0/0/0
CPS-R01-R4.03-00 0x00000025 0xF5B7 1018 0/0/0
CPS-R01-R2#
It got many Level 2 LSPs.
CPS-R01-R2#sh isis database verbose | b IS-IS Level-2

CPS-R01-R2.00-00 * 0x0000002F 0xFADB 1153 0/0/0
NLPID: 0xCC
IP Address: 192.168.2.2
Metric: 20 IP 192.168.1.1 255.255.255.255
CPS-R01-R2.03-00 * 0x00000026 0xE7C8 1078 0/0/0

CPS-R01-XRv-R3.00-00 0x0000003F 0x420A 912 0/0/0
NLPID: 0xCC
IP Address: 192.168.3.3
Metric: 10 IP 192.168.3.3 255.255.255.255
Metric: 10 IP 192.168.23.0 255.255.255.0
Metric: 10 IP 192.168.33.33 255.255.255.255
Metric: 10 IP 192.168.34.0 255.255.255.252
CPS-R01-R4.00-00 0x0000003D 0x1A05 916 0/0/0

NLPID: 0xCC
IP Address: 192.168.4.4
Metric: 30 IP 192.168.2.2 255.255.255.255
Metric: 10 IP 192.168.4.4 255.255.255.255
Metric: 20 IP 192.168.11.11 255.255.255.255
Metric: 20 IP 192.168.12.0 255.255.255.252
Metric: 10 IP 192.168.14.0 255.255.255.252
Metric: 30 IP 192.168.23.0 255.255.255.252
Metric: 10 IP 192.168.34.0 255.255.255.252
CPS-R01-R4.03-00 0x00000025 0xF5B7 911 0/0/0

CPS-R01-R2#
Quite a number of prefixes, whole Level 2 Topology here, even 192.168.11.11 is also showing originated from R4.
Confusion is so easy, whatever the R2 is having in L2 Database Table is received from R3, will it be able send back?
Its best mechanism to avoid loops with one drawback of not having redundancy like we do have in Level 2 to Level
1 route leaking, with that default route always works as backup path, but if R2 gets failed R1 Loopback 0 cannot be
reachable to R3 via R4, same for Loopback 1.
1.1.6 ISIS Passive Interface
Advertise all Loopbacks in the topology without using ip router isis.
Make sure those loopbacks never try to form ISIS adjacency on them.
Does not use redistribute command to advertise them.
R1
interface loopback0
noip router isis
!
interface loopback1
noip router isis
R2
interface loopback0
noip router isis
R4
interface loopback0
noip router isis
R3
router isis 3
interface Loopback0
no address-family ipv4 unicast
!
!
interface Loopback1
no address-family ipv4 unicast
!
commit
R1
router isis
passive-interface Loopback0
To use passive interface or passive, ISIS needs to have at least one interface configured with ip router isis or
enabled for IP address family.
CPS-R01-R1#sh clns interface lo0
Loopback0 is up, line protocol is up
CLNS protocol processing disabled
CPS-R01-R1#
CPS-R01-R2#sh ip route isis | i L1

CPS-R01-R2#
R2
router isis
R4
router isis
R3
router isis 3
interface Loopback0
passive
!
interface Loopback1
passive
!
commit
All the loopbacks are advertised in to ISIS.
Passive interface default is another way around to stop unnecessary LSP floods on not required interfaces; it can be
used as below to achieve the same purpose:
R1
router isis
passive-interface default
no passive-interface FastEthernet0/0.12
no passive-interface FastEthernet0/0.14
1.1.7 ISIS Network Types
Configure ISIS Network Type Point to Point between R2 and R3.
Make sure there is no DIS selection on this link.
Circuit ID: CPS-R01-R2.03 is ID of DIS which is R2.
LAN ID: CPS-R01-R2.03 is the ID of DIS which is R2. Media Type is LAN or broadcast.
Like OSPF, default ISIS network on Ethernet is broadcast where DIS (DR) is elected.
LSP Sequence Num marked with * are called Pseudo Node LSP, these do help to reduce database size and simplifies
SPF calculation in ISIS broadcast networks.
Lets change the ISIS network type to point to point:
R2
interfacefastethernet 0/0.23
R3
router isis 3
!
point-to-point
!
commit
Circuit ID 00 means no DIS Election on the link.

No DIS Election over Point to Point links.
SNPA PtoP means network point to point. Media Type changed to P2P.
1.1.8 ISIS DIS Election
Make sure R3 is acting as DIS on the Link between R3 and R4.
Currently R4 is acting as DIS.
Currently R4 is acting as DIS.
Default priority of DIS is 64, the highest is 127.
R3
router isis 3
priority 127
!
commit
Highest Priority wins, now R3 has become DIS.
1.1.9 ISIS Metric Types
Configure all devices in domain to support ISIS TLV 135.
By default ISIS enabled routers use metric style narrow which supports maximum route metric 63.
Any type of interface participating in ISIS has default metric 10.
Lets move ahead and change the metric type:
R1, R2, R4
router isis
metric-style wide
R3
router isis 3
metric-style wide
We can see metric style wide is enabled, wide metric is known as TLV 135. It allows ISIS to support extended
metric which is required particularly for MPLS TE. In above output R1 has stopped accepting and generating
metric types narrow which may create issues if network is live during transition. ISIS has a granularity by allowing
devices to support both types of metric by using command metric-style-transition.
R1
router isis
metric-style transition
1.1.10 ISIS Multi Instance
Configure ISIS as per drawing below.
Configure global instance for area 49.0124 and an additional ISIS instance ISIS_0023 on R2 for area 49.0023.
Configure 2 ISIS Instances on R3, Instance ISIS_0023 for area 49.0023 and Instance ISIS_0034 for area 49.0034.
R2 and R3 hosts should be advertised in to area 49.0124.
Do not use ip router isis to advertise loopbacks.

R1 should have ISIS route for all the hosts in the network.
R1 should be able to reach all the hosts in network.
You can use redistribute connected on R2 Global instance.
Clean up all old configurations and do a fresh configuration.
SW
vlan database
!
vlan 12
!
vlan 13
!
vlan 14
!
vlan 23
!
vlan 34
!
apply
!
exit
no shut
!
!
!
!
R1
no shut
!
ip add 192.168.12.1 255.255.255.252
!
ip add 192.168.14.1 255.255.255.252
!
ip add 192.168.13.1 255.255.255.252
!
interface loopback0
ip add 192.168.1.1 255.255.255.255
R2
hostname CPS-R01-R2
no shut
!
ip add 192.168.12.2 255.255.255.252
!
ip add 192.168.23.1 255.255.255.252
!
interface loopback0
ip add 192.168.2.2 255.255.255.255
XRv-R3
hostname CPS-R01-XRv-R3
no shut
!
ip add 192.168.23.2/24
!
ip add 192.168.34.1/24
ip add 192.168.13.2/24
no shut
!
interface loopback0
ip add 192.168.3.3/32
commit
R4
hostname CPS-R01-R4
no shut
!
ip add 192.168.14.2 255.255.255.252
!
ip add 192.168.34.2 255.255.255.252
!
interface loopback0
ip add 192.168.4.4 255.255.255.255
Lets start configuring ISIS on R1.
router isis
net 49.0124.0000.0000.0001.00
passive-interface loopback0
!
ip router isis
!
ip router isis
R1 is enabled for ISIS Routing as per drawing and advertising required interfaces in to ISIS.
R4
router isis
net 49.0124.0000.0000.0004.00
!
ip router isis
!
ip router isis
R4 has its all desired interfaces enabled for ISIS Routing.

R1 and R4 have Level 1 adjacency established.
R4 is elected as DIS.
R4 is receiving R1 Loopback 0 but not the network between R1 R2 a Level 2 route.
R2:
router isis
net 49.0124.0000.0000.0002.00
!
ip router isis
router isis ISIS_0023

net 49.0023.0000.0000.0023.00
!
ip router isis ISIS_0023
R2 has its all desired interfaces enabled for ISIS Routing.

R2 has ISIS default instance enabled for FastEthernet0/0.12.
It has additional ISIS instance enabled for FastEthernet0/0.23 and Loopback0.
R1 and R2 have Level 2 adjacency established for ISIS default instance. R2 is elected as DIS.
R2 is receiving 3 routes from R1.
Make sure to use separate system IDs and NET ID for each instance.
R3
net 49.0034.0000.0000.0034.00
!
!
net 49.0023.0000.0000.0023.00
!
!
interface loopback0
passive
!
commit
R3 has R2 as Level 2 neighbor in ISIS instance ISIS_0023.

R3 has R4 as Level 2 neighbor in ISIS instance ISIS_0034.
R3 is receiving 2 routes from R2 which are in R2 routing instance ISIS_23.
R3 is receiving 3 routes from R4.
If routes are not distributed between the instances those are advertised in both instances, by default those get
advertised to the neighbors of same instance.
Lets check on R4:
It has two neighbors as per drawing.

Its only receiving R1 loopback 0 in routing table.
R1 is only advertising loopback 0 to R3 which is in Level 1. By default Level 2 routes are not advertise to Level 1
neighbors to achieve this we need to do redistribution of Level 2 in Level 1 at R1.
R3 is not advertising instance ISIS_0023 routes to instance ISIS_0034 neighbors.
R2 is also not receiving R3 ISIS_0034 routes.
Lets do mutual redistribute in R3 both instances:

redistributeisis ISIS_0023 level-1-2 metric 10

redistributeisis ISIS_0034 level-1-2 metric 10
Now R4 has routes of R3 instance ISIS_0023.

i L2 192.168.23.0/24
CPS-R01-R2#
R2 is also receiving R3 ISIS_0034 route.
R4 is receiving Level 1 routes from R1 and other routes from R3.

Lets have a look at routing table of R1:
R1 is receiving only two routes from R4, if we want Level 2 routes from R4, we need to perform route leaking on
R4.
R1 is not receiving any route from R2 because R2 default instance is still not redistributed with ISIS_0023 by which
R2 is receiving R3 and R4 routes.
Lets perform route leaking on R4:
R4
router isis
!
access-list 34 permit 192.168.3.3
!
matchip address 34
Filtration is key thing while route leaking to avoid loops, if we do not add filter for R2, R1 will start using R4 to
reach R2.
We can see a inter area route in R1 routing table from R4.
Lets perform redistribution on R2 to receive R3 Host on R1 via R2.
R2
router isis
redistribute isis ISIS_0023 ip route-map ISIS_0023-to-Global
route-map ISIS_0023-to-Global permit 10

match ip address 23
!
Now we can 192.168.3.3 is coming from R2. ISIS Routing perference it selects Level 1 route over Level 2 and
Level 2 route over external.
Still we are not seeing R2 Loopback0 in R1 routing table if we leak it from R4, path would be longer.
Lets add redistribute connected in R2 Global instance:
R2
router isis
redistribute connected
CPS-R01-R1#sh ip route isis | i .12

CPS-R01-R1#
Lets have a look at R3 routing table:

Looks clean but if R4 fails it will lose the reach ability to R1, lets redistribute R2 Global instance to ISIS_0023 to
allow R1 Host.

redistributeisis ISIS_0023 ip route-map ISIS_0023-to-Global
route-map ISIS_0023-to-Global permit 10

matchip address 23
!
Sun Jun 1 07:20:01.471 UTC

CPS-R01-R1#tclsh
+>192.168.1.1
+>192.168.2.2
+>192.168.3.3
+>}

!!!!!!!!!!
!!!!!!!!!!
!!!!!!!!!!
!!!!!!!!!!
CPS-R01-R1(tcl)#
Lets have check for routing tables:
CPS-R01-R1#sh ip route isis | b Gate

Gateway of last resort is 192.168.14.2 to network 0.0.0.0

192.168.2.0/32 is subnetted, 1 subnets
CPS-R01-R1#
R1 will reach R2 Host via R2

CPS-R01-R2#sh ip route isis | b Gate


i L2 192.168.23.0/24
CPS-R01-R2#



i L2 192.168.23.0/24
i L2 192.168.23.0/30
CPS-R01-R4#

Here, we can find one sub optimal path for R2 R4, R2 will transit R1 to reach R4, while R4 will transit R3 to reach
R2, if we perform route leaking from R1 Level 2 to Level 1, this should be shorted out.
R1
router isis
!
!
matchip address 12
CPS-R01-R4#sh ip route isis

i L2 192.168.23.0/24
i L2 192.168.23.0/30
CPS-R01-R4#
CPS-R01-R4#sh isis database verbose | i 192.168.2.2

Metric: 138 IP-Interarea 192.168.2.2 255.255.255.255
Metric: 10 IP-External 192.168.2.2 255.255.255.255
CPS-R01-R4#
If we enable wide metrics it will show as Level 2 route and internal routes are preferred over inter area routes.
CPS-R01-R4#sh isis database verbose | i 192.168.2.2

Metric: 10 IP-Interarea 192.168.2.2/32
Metric: 10 IP 192.168.2.2/32
CPS-R01-R4#
Simulate such practicals and try to innovate unlike connecting 3 - 4 routers in planned way to get minimum issues
like we see in other workbooks, play around you need to understand all these caveats. Cisco Tests your concepts.
1.1.11 ISIS Path Selection
Configure ISIS as per below drawing.
Optimize ISIS path so that R3 uses R1 to reach R5 connected host.
Optimize ISIS path so that R2 uses R4 to reach R5 connected host.
Loopbacks should be not advertised using either ip router isis or passive command.
Enable ISIS wide Metrics.
SW:
vlan database
!
vlan 12
!
vlan 13
!
vlan 14
!
vlan 23
!
vlan 34
!
apply
!
exit

no shut
!
!
!
!
R1
no shut
!
ip add 192.168.12.1 255.255.255.252
!
ip add 192.168.14.1 255.255.255.252
!
interface loopback0
ip add 192.168.1.1 255.255.255.255
!
ip add 192.168.13.1 255.255.255.252
no shut
!
interface GigabitEthernet1/0
ip add 192.168.15.1 255.255.255.252
no shut
R2
no shut
!
ip add 192.168.12.2 255.255.255.252
!
ip add 192.168.23.1 255.255.255.252
!
interface loopback0
ip add 192.168.2.2 255.255.255.255
XRv-R3
no shut
!
ip add 192.168.23.2/24
!
ip add 192.168.34.1/24
ip add 192.168.13.2/24
no shut
!
interface loopback0
ip add 192.168.3.3/32
R4
no shut
!
ip add 192.168.14.2 255.255.255.252
!
ip add 192.168.34.2 255.255.255.252
!
ip add 192.168.45.1 255.255.255.252
no shut
!
interface loopback0
ip add 192.168.4.4 255.255.255.255
R5
ip add 192.168.15.2 255.255.255.252
no shut
!
ip add 192.168.45.2 255.255.255.252
no shut
!
interface loopback0
ip add 192.168.5.5 255.255.255.255
R1
router isis
net 49.1234.0000.0000.0001.00
metric-style wide
redistribute connected route-map connected
!
ip router isis
!
ip router isis
!
ip router isis
!
route-map connected permit 10
match interface Loopback0
R2
router isis
net 49.0124.0000.0000.0002.00
metric-style wide
!
ip router isis
ip router isis

R3
net 49.1234.0000.0000.0003.00
metric-style wide
redistribute connected level-2 route-policy connected
!
!
!
route-policy connected
if destination in (192.168.3.3) then
pass
endif
exit
commit
R4
router isis
net 49.1234.0000.0000.0004.00
metric-style wide
!
ip router isis
!
ip router isis

Lets verify Level 2 ISIS on all devices in area 49.1234:
R1 has ISIS enabled for three interfaces and it is redistributing connected interface in to ISIS.
R1 has 3 ISIS Level 2 neighbors, R2, R3 and R4.
R2 has been elected DIS between R1-R2; R1 has been elected DIS between R1-R3; R4 is elected DIS between R1-R4.
Because of not disabling ISIS Level 1 globally it has associated Attachment bit.
R1 has installed R2 Host route directly from R2.
All look good as expected.
R2 has ISIS enabled for two interfaces and it is redistributing connected interface in to ISIS.
R2 has 2 ISIS Level 2 neighbors, R2 and R3.
R2 has been elected DIS between R1-R2; R2 has been elected DIS between R2-R3.
Because of disabling ISIS Level 1 globally it has no Attachment bit association.
R2 has installed R4 Host route from R4 both neighbors R1 and R3.
R3 has ISIS enabled for three interfaces and it is redistributing connected interface in to ISIS.
R3 has 3 ISIS Level 2 neighbors, R1, R2 and R4.
R4 has ISIS enabled for two interfaces and it is redistributing connected interface in to ISIS.
R4 has 2 ISIS Level 2 neighbors, R1 and R3.
R4 has been elected DIS between R1-R4; R4 has been elected DIS between R3-R4.
Because of not disabling ISIS Level 1 globally it has associated Attachment bit and Level 1 database.
R4 has installed R2 Host route from both neighbors R1 and R3.

Lab1 Latest Update

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Lab1 Latest Update

Hochgeladen von

Copyright:

Verfügbare Formate

Disclaimer: CCIE SPv3 Lab Exam Workbook is designed to provide extensive practical technical information to

copyright 2014 CcieperfectSolutions.com, All rights reserved.

1.1 ISIS for IPv4 Troubleshooting

2.1 PPP Multilink

3.1 IBGP VPNv4 Troubleshooting

4.1 PPP over MPLS

1.1 OSPF for IPv4 Troubleshooting

2.1 PPP Multilink

3.1 IBGP VPNv4 Troubleshooting

4.1 PPP over MPLS

1.1 Implement ISIS

1.2 Implement OSPF

1.4 Implement MPLS

1.5 Implement Traffic Engineering

3.1Implement MPLS L3 VPN

4.1Implement MPLS L2 VPN

5.1.1 IOS XR Configuration

R1 Loopback0 9.9.0.1/32 2002:9:9::1/128

Loopback1 172.9.0.1/32 2002:172:9::1/128

R2 Loopback0 9.9.0.2/32 2002:9:9::2/128

Loopback1 172.9.0.2/32 2002:172:9::2/128

R3 Loopback0 9.9.0.3/32 2002:9:9::3/128

Loopback1 172.9.0.3/32 2002:172:9::3/128

R4 Loopback0 9.9.0.4/32 2002:9:9::4/128

R5 Loopback0 9.9.0.5/32 2002:9:9::5/128

R6 Loopback0 9.9.0.6/32 2002:9:9::6/128

R7 Loopback0 9.9.0.7/32 2002:9:9::7/128

R8 Loopback0 9.9.0.8/32 2002:9:9::8/128

Loopback1 172.9.0.8/32 2002:172:9::8/128

R9 Loopback0 9.9.0.9/32 2002:9:9::9/128

R10 Loopback0 9.9.0.10/32 2002:9:9::10/128

R11 Loopback0 172.9.0.11/32 2002:172:9::11/128

R12 Loopback0 172.9.0.12/32 2002:172:9::12/128

R13 Loopback0 192.9.0.13/32

R14 Loopback0 172.9.0.14/32 2002:172:9::14/128

R15 Loopback0 172.9.0.15/32 2002:172:9::15/128

R16 Loopback0 192.9.0.16/32

R17 Loopback0 172.9.0.17/32 2002:172:9::17/128

R18 Loopback0 172.9.0.18/32 2002:172:9::18/128

R19 Loopback0 192.9.0.19/32

R20 Loopback0 172.9.0.20/32

R21 Loopback0 172.9.0.21/32

R22 Loopback0 172.9.0.22/32

R23 Loopback0 172.9.0.23/32

R24 Loopback0 172.9.0.24/32

Table 2 : Loopback Interface Multicast Groups

R10 Loopback0 239.255.0.10

R11 Loopback0 239.255.172.11

R12 Loopback0 239.255.172.12

R13 Loopback0 239.255.172.13

R14 Loopback0 239.255.172.14

R15 Loopback0 239.255.172.15

1.1 ISIS for IPv4 Troubleshooting

Router Area Interface

RP/0/0/CPU0:CPS_R0_R2# show running-config interface loopback 0

RP/0/0/CPU0:CPS_R0_R2# show running-config interface gigabitEthernet 0/0/0/0.23

RP/0/0/CPU0:CPS_R0_R2# show running-config interface gigabitEthernet 0/0/0/0.25

RP/0/0/CPU0:CPS_R0_R2# show running-config router isis abc

RP/0/0/CPU0:CPS_R0_R3#show running-config interface loopback 0

RP/0/0/CPU0:CPS_R0_R3#show running-config interface gigabitEthernet 0/0/0/0.23

RP/0/0/CPU0:CPS_R0_R3#show running-config interface gigabitEthernet 0/0/0/0.34

RP/0/0/CPU0:CPS_R0_R3#show running-config interface gigabitEthernet 0/0/0/0.35

RP/0/0/CPU0:CPS_R0_R3#show running-config interface gigabitEthernet 0/0/0/0.37

RP/0/0/CPU0:CPS_R0_R4#show running-config interface loopback 0