check and rewrite
i have the work from a old student, need to check the same and rewrite it……..
must pass through plagiarism checker
Individual: Troubleshooting Eigrp Routing Related Problems
Antonio Lewis
February 6, 2018
Daniel Dronsick
Running head: INDIVIDUAL: TROUBLESHOOTING EIGRP ROUTING RELATED 1
INDIVIDUAL: TROUBLESHOOTING EIGRP ROUTING RELATED 15
Individual: Troubleshooting EIGRP Routing Related Problems
NYEDGE1#show
running config
^
% Invalid input detected at ‘^’ marker.
NYEDGE1#show running
Building configuration…
Current configuration : 1506 bytes
!
!
Last configuration change at 00:16:41 UTC Wed Jan 31 2018
version 15.2
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname NYEDGE1
!
boot-start-marker
boot-end-marker
!
!
!
no aaa new-model
!
ip cef
!
!
!
!
!
!
!
!
no ipv6 cef
!
multilink bundle-name authenticated
!
!
!
!
license udi pid CISCO2911/K9 sn FCZ1820707L
!
!
!
redundancy
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Loopback0
ip address 10.16.18.1 255.255.255.0
!
interface Embedded-Service-Engine0/0
no ip address
shutdown
!
interface GigabitEthernet0/0
ip address 192.168.4.1 255.255.255.240
duplex auto
speed auto
!
interface GigabitEthernet0/1
ip address 172.14.0.1 255.255.255.0
duplex auto
speed auto
!
interface GigabitEthernet0/2
no ip address
shutdown
duplex auto
speed auto
!
interface Serial0/0/0
no ip address
shutdown
!
interface Serial0/0/1
no ip address
shutdown
clock rate 2000000
!
!
!
router eigrp 800
network 10.0.0.0
network 10.16.18.0 0.0.0.255
network 172.14.0.0 0.0.0.255
network 192.168.4.0
passive-interface GigabitEthernet0/0
!
!
router eigrp 8001
network 192.168.20.16 0.0.0.15
!
ip forward-protocol nd
!
no ip http server
no ip http secure-server
!
!
!
!
!
control-plane
!
!
!
line con 0
line aux 0
line 2
no activation-character
no exec
transport preferred none
transport output lat pad telnet rlogin lapb-ta mop udptn v120 ssh
stopbits 1
line vty 0 4
login
transport input all
!
scheduler allocate 20000 1000
!
End
NYEDGE2#show running
Building configuration…
Current configuration : 1643 bytes
!
! Last configuration change at 00:09:22 UTC Wed Jan 31 2018
version 15.2
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname NYEDGE2
!
boot-start-marker
boot-end-marker
!
!
!
no aaa new-model
!
ip cef
!
!
!
!
!
!
!
!
no ipv6 cef
!
multilink bundle-name authenticated
!
!
!
!
license udi pid CISCO2911/K9 sn FCZ1820604U
!
!
!
redundancy
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Loopback10
ip address 172.16.10.1 255.255.255.128
!
interface Loopback11
ip address 172.16.10.129 255.255.255.128
!
interface Loopback12
ip address 172.16.11.1 255.255.255.240
shutdown
!
interface Embedded-Service-Engine0/0
no ip address
shutdown
!
interface GigabitEthernet0/0
ip address 192.168.4.2 255.255.255.240
duplex auto
speed auto
!
interface GigabitEthernet0/1
ip address 172.14.0.2 255.255.255.0
duplex auto
speed auto
!
interface GigabitEthernet0/2
no ip address
shutdown
duplex auto
speed auto
!
interface Serial0/0/0
no ip address
shutdown
clock rate 2000000
!
interface Serial0/0/1
no ip address
shutdown
clock rate 2000000
!
!
!
router eigrp 800
network 172.14.0.0 0.0.0.255
network 172.16.10.0 0.0.0.127
network 172.16.11.0 0.0.0.15
network 192.168.4.0
!
!
router eigrp 8001
network 192.168.20.16 0.0.0.15
!
ip forward-protocol nd
!
no ip http server
no ip http secure-server
!
!
!
!
!
control-plane
!
!
!
line con 0
line aux 0
line 2
no activation-character
no exec
transport preferred none
transport output lat pad telnet rlogin lapb-ta mop udptn v120 ssh
stopbits 1
line vty 0 4
login
transport input all
!
scheduler allocate 20000 1000
!
End
YWAN1#show running
Building configuration…
Current configuration : 2078 bytes
!
! Last configuration change at 01:34:05 UTC Wed Jan 31 2018
version 15.2
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname NYWAN1
!
boot-start-marker
boot-end-marker
!
!
no logging console
!
no aaa new-model
!
ip cef
!
!
!
!
!
!
no ipv6 cef
!
multilink bundle-name authenticated
!
!
!
!
!
!
!
voice-card 0
!
!
!
!
!
!
!
!
license udi pid CISCO2911/K9 sn FCZ1820707T
hw-module pvdm 0/0
!
!
!
!
redundancy
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Embedded-Service-Engine0/0
no ip address
shutdown
!
interface GigabitEthernet0/0
ip address 172.16.5.1 255.255.255.252
ip hello-interval eigrp 800 300
duplex auto
speed auto
!
interface GigabitEthernet0/1
ip address 172.16.16.1 255.255.255.0
duplex auto
speed auto
!
interface GigabitEthernet0/2
no ip address
shutdown
duplex auto
speed auto
!
interface Serial0/0/0
no ip address
encapsulation frame-relay
!
interface Serial0/0/0.256 point-to-point
bandwidth 256
ip address 172.88.0.9 255.255.255.252
snmp trap link-status
frame-relay interface-dlci 256
!
interface Serial0/0/0.641 point-to-point
bandwidth 64
ip address 172.88.0.1 255.255.255.252
snmp trap link-status
frame-relay interface-dlci 641
!
interface Serial0/0/1
no ip address
shutdown
!
interface Serial0/1/0
no ip address
shutdown
!
interface Serial0/1/1
no ip address
shutdown
!
interface Serial0/2/0
no ip address
shutdown
clock rate 2000000
!
!
router eigrp 800
network 172.16.5.0 0.0.0.3
network 172.16.16.0 0.0.0.255
network 172.88.0.0
network 172.88.0.0 0.0.0.3
network 172.88.0.4 0.0.0.3
network 186.12.0.0 0.0.0.3
network 192.168.16.0
!
ip forward-protocol nd
!
no ip http server
no ip http secure-server
!
!
!
!
!
control-plane
!
!
!
!
!
!
!
mgcp profile default
!
!
!
!
!
gatekeeper
shutdown
!
!
!
line con 0
line aux 0
line 2
no activation-character
no exec
transport preferred none
transport output pad telnet rlogin lapb-ta mop udptn v120 ssh
stopbits 1
line vty 0 4
login
transport input all
!
scheduler allocate 20000 1000
!
End
NYWAN1#show running
Building configuration…
Current configuration : 2206 bytes
!
! Last configuration change at 01:48:01 UTC Wed Jan 31 2018
version 15.2
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname NYWAN1
!
boot-start-marker
boot-end-marker
!
!
no logging console
!
no aaa new-model
!
ip cef
!
!
!
!
!
!
no ipv6 cef
!
multilink bundle-name authenticated
!
!
!
!
!
!
!
voice-card 0
!
!
!
!
!
!
!
!
license udi pid CISCO2911/K9 sn FCZ1820707T
hw-module pvdm 0/0
!
!
!
!
redundancy
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Embedded-Service-Engine0/0
no ip address
shutdown
!
interface GigabitEthernet0/0
ip address 172.16.5.1 255.255.255.252
ip hello-interval eigrp 800 300
duplex auto
speed auto
!
interface GigabitEthernet0/1
ip address 172.16.16.1 255.255.255.0
duplex auto
speed auto
!
interface GigabitEthernet0/2
no ip address
shutdown
duplex auto
speed auto
!
interface Serial0/0/0
no ip address
encapsulation frame-relay
!
interface Serial0/0/0.256 point-to-point
bandwidth 256
ip address 172.88.0.9 255.255.255.252
snmp trap link-status
frame-relay interface-dlci 256
!
interface Serial0/0/0.641 point-to-point
bandwidth 64
ip address 172.88.0.1 255.255.255.252
snmp trap link-status
frame-relay interface-dlci 641
!
interface Serial0/0/1
no ip address
shutdown
!
interface Serial0/0/1.512
bandwidth 512
!
interface Serial0/0/1.642
bandwidth 64
!
interface Serial0/0/1.768
bandwidth 768
!
interface Serial0/1/0
no ip address
shutdown
!
interface Serial0/1/1
no ip address
shutdown
!
interface Serial0/2/0
no ip address
shutdown
clock rate 2000000
!
!
router eigrp 800
network 172.16.5.0 0.0.0.3
network 172.16.16.0 0.0.0.255
network 172.88.0.0
network 172.88.0.0 0.0.0.3
network 172.88.0.4 0.0.0.3
network 186.12.0.0 0.0.0.3
network 192.168.16.0
!
ip forward-protocol nd
!
no ip http server
no ip http secure-server
!
!
!
!
!
control-plane
!
!
!
!
!
!
!
mgcp profile default
!
!
!
!
!
gatekeeper
shutdown
!
!
!
line con 0
line aux 0
line 2
no activation-character
no exec
transport preferred none
transport output pad telnet rlogin lapb-ta mop udptn v120 ssh
stopbits 1
line vty 0 4
login
transport input all
!
scheduler allocate 20000 1000
!
End
WEEK3LAB/NYACCESS1 x
NYACCESS1#
*Mar 1 00:02:51.790: %LINK-3-UPDOWN: Interface FastEthernet0/24, changed state to up
*Mar 1 00:02:52.167: %LINK-3-UPDOWN: Interface FastEthernet0/23, changed state to up
*Mar 1 00:02:52.796: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/24, changed state to up
*Mar 1 00:02:53.174: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/23, changed state to up
*Mar 1 00:03:11.780: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/23, changed state to down
*Mar 1 00:03:13.382: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/24, changed state to down
*Mar 1 00:03:14.800: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/23, changed state to up
*Mar 1 00:03:16.394: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/24, changed state to up
*Mar 1 00:03:48.891: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan16, changed state to up
NYACCESS1#show running-config
Building configuration…
Current configuration : 1372 bytes
!
version 12.2
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname NYACCESS1
!
boot-start-marker
boot-end-marker
!
!
!
!
no aaa new-model
system mtu routing 1500
!
!
!
!
!
!
!
!
spanning-tree mode pvst
spanning-tree extend system-id
!
vlan internal allocation policy ascending
!
!
interface FastEthernet0/1
switchport access vlan 16
switchport mode access
!
interface FastEthernet0/2
!
interface FastEthernet0/3
!
interface FastEthernet0/4
!
interface FastEthernet0/5
!
interface FastEthernet0/6
!
interface FastEthernet0/7
!
interface FastEthernet0/8
!
interface FastEthernet0/9
!
interface FastEthernet0/10
!
interface FastEthernet0/11
!
interface FastEthernet0/12
!
interface FastEthernet0/13
!
interface FastEthernet0/14
!
interface FastEthernet0/15
!
interface FastEthernet0/16
!
interface FastEthernet0/17
!
interface FastEthernet0/18
!
interface FastEthernet0/19
!
interface FastEthernet0/20
!
interface FastEthernet0/21
!
interface FastEthernet0/22
!
interface FastEthernet0/23
!
interface FastEthernet0/24
!
interface GigabitEthernet0/1
!
interface GigabitEthernet0/2
!
interface Vlan1
no ip address
no ip route-cache
shutdown
!
interface Vlan16
ip address 192.168.16.7 255.255.255.0
no ip route-cache
!
ip http server
ip http secure-server
!
line con 0
line vty 5 15
!
end
NYACCESS1#
WEEK3LAB/NYCORE1 x
NYCORE1#show running-config
Building configuration…
Current configuration : 2380 bytes
!
! Last configuration change at 00:02:41 UTC Mon Mar 1 1993
!
version 15.0
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname NYCORE1
!
boot-start-marker
boot-end-marker
!
!
no logging console
!
no aaa new-model
switch 1 provision ws-c3750v2-24ps
system mtu routing 1500
ip routing
!
!
!
!
!
!
!
!
!
!
!
!
spanning-tree mode pvst
spanning-tree extend system-id
spanning-tree vlan 16 priority 24576
!
vlan internal allocation policy ascending
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Loopback10
ip address 172.16.11.129 255.255.255.240
!
interface FastEthernet1/0/1
switchport access vlan 4
switchport mode access
!
interface FastEthernet1/0/2
switchport access vlan 5
switchport mode access
!
interface FastEthernet1/0/3
!
interface FastEthernet1/0/4
!
interface FastEthernet1/0/5
!
interface FastEthernet1/0/6
!
interface FastEthernet1/0/7
!
interface FastEthernet1/0/8
!
interface FastEthernet1/0/9
!
interface FastEthernet1/0/10
!
interface FastEthernet1/0/11
!
interface FastEthernet1/0/12
!
interface FastEthernet1/0/13
!
interface FastEthernet1/0/14
!
interface FastEthernet1/0/15
!
interface FastEthernet1/0/16
!
interface FastEthernet1/0/17
!
interface FastEthernet1/0/18
!
interface FastEthernet1/0/19
!
interface FastEthernet1/0/20
!
interface FastEthernet1/0/21
!
interface FastEthernet1/0/22
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface FastEthernet1/0/23
!
interface FastEthernet1/0/24
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface GigabitEthernet1/0/1
!
interface GigabitEthernet1/0/2
!
interface Vlan1
no ip address
!
interface Vlan4
ip address 192.168.4.5 255.255.255.240
!
interface Vlan5
ip address 172.16.5.2 255.255.255.252
!
interface Vlan8
ip address 192.168.8.1 255.255.255.224
!
interface Vlan16
ip address 192.168.16.1 255.255.255.128
!
interface Vlan24
ip address 192.168.24.1 255.255.255.128
!
interface Vlan32
ip address 192.168.32.1 255.255.255.192
!
interface Vlan40
ip address 192.168.40.1 255.255.255.224
!
!
router eigrp 800
network 172.16.5.0 0.0.0.3
network 172.16.11.0 0.0.0.15
network 192.168.4.0
network 192.168.8.0
network 192.168.16.0
network 192.168.24.0
network 192.168.32.0
network 192.168.40.0
!
ip http server
ip http secure-server
!
!
!
!
!
!
line con 0
line vty 5 15
!
end
NYCORE1#
WEEK3LAB/NYCORE2 x
NYCORE2#
*Mar 1 00:02:40.373: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/24, changed state to up
*Mar 1 00:02:41.690: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0/22, changed state to up
*Mar 1 00:02:47.168: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
*Mar 1 00:03:01.772: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan4, changed state to up
*Mar 1 00:03:09.397: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan8, changed state to up
*Mar 1 00:03:09.397: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan16, changed state to up
*Mar 1 00:03:09.397: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan24, changed state to up
*Mar 1 00:03:09.397: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan32, changed state to up
*Mar 1 00:03:09.397: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan40, changed state to up
NYCORE2#show runnning-condfig
^
% Invalid input detected at ‘^’ marker.
NYCORE2#show running-config
Building configuration…
Current configuration : 2139 bytes
!
! Last configuration change at 00:02:39 UTC Mon Mar 1 1993
!
version 15.0
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname NYCORE2
!
boot-start-marker
boot-end-marker
!
!
!
no aaa new-model
switch 1 provision ws-c3750v2-24ps
system mtu routing 1500
ip routing
!
!
!
!
!
!
!
!
!
!
!
spanning-tree mode pvst
spanning-tree extend system-id
!
vlan internal allocation policy ascending
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface FastEthernet1/0/1
switchport access vlan 4
switchport mode access
!
interface FastEthernet1/0/2
!
interface FastEthernet1/0/3
!
interface FastEthernet1/0/4
!
interface FastEthernet1/0/5
!
interface FastEthernet1/0/6
!
interface FastEthernet1/0/7
!
interface FastEthernet1/0/8
!
interface FastEthernet1/0/9
!
interface FastEthernet1/0/10
!
interface FastEthernet1/0/11
!
interface FastEthernet1/0/12
!
interface FastEthernet1/0/13
!
interface FastEthernet1/0/14
!
interface FastEthernet1/0/15
!
interface FastEthernet1/0/16
!
interface FastEthernet1/0/17
!
interface FastEthernet1/0/18
!
interface FastEthernet1/0/19
!
interface FastEthernet1/0/20
!
interface FastEthernet1/0/21
!
interface FastEthernet1/0/22
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 16
switchport mode trunk
!
interface FastEthernet1/0/23
!
interface FastEthernet1/0/24
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 4,8,16,24,32,40
switchport mode trunk
!
interface GigabitEthernet1/0/1
!
interface GigabitEthernet1/0/2
!
interface Vlan1
no ip address
!
interface Vlan4
ip address 192.168.4.6 255.255.255.240
!
interface Vlan8
ip address 192.168.8.2 255.255.255.224
!
interface Vlan16
ip address 192.168.16.2 255.255.255.0
!
interface Vlan24
ip address 192.168.24.2 255.255.255.128
!
interface Vlan32
ip address 192.168.32.2 255.255.255.192
!
interface Vlan40
ip address 192.168.40.2 255.255.255.224
!
!
router eigrp 80
network 192.168.0.0
network 192.168.4.0
network 192.168.8.0
network 192.168.16.0
auto-summary
!
ip http server
ip http secure-server
!
!
!
!
!
!
line con 0
line vty 5 15
!
end
NYCORE2#
WEEK3LAB/NYEDGE1 x
NYEDGE1#
*May 7 15:15:42.343: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to down
*May 7 15:15:45.491: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
*May 7 15:15:46.491: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up
*May 7 15:16:07.551: %DUAL-5-NBRCHANGE: EIGRP-IPv4 800: Neighbor 172.14.0.2 (GigabitEthernet0/1) is up: new adjacency
*May 7 15:17:18.499: %LINK-3-UPDOWN: Interface GigabitEthernet0/0, changed state to up
*May 7 15:17:19.499: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0, changed state to up
NYEDGE1#show running-config
Building configuration…
Current configuration : 1451 bytes
!
! Last configuration change at 15:15:42 UTC Thu May 7 2015
version 15.2
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname NYEDGE1
!
boot-start-marker
boot-end-marker
!
!
!
no aaa new-model
!
ip cef
!
!
!
!
!
!
!
!
no ipv6 cef
!
multilink bundle-name authenticated
!
!
!
!
license udi pid CISCO2911/K9 sn FCZ18206055
!
!
!
redundancy
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Loopback0
ip address 10.16.18.1 255.255.255.0
!
interface Embedded-Service-Engine0/0
no ip address
shutdown
!
interface GigabitEthernet0/0
ip address 192.168.4.1 255.255.255.240
duplex auto
speed auto
!
interface GigabitEthernet0/1
ip address 172.14.0.1 255.255.255.0
duplex auto
speed auto
!
interface GigabitEthernet0/2
no ip address
shutdown
duplex auto
speed auto
!
interface Serial0/0/0
no ip address
shutdown
!
interface Serial0/0/1
no ip address
shutdown
clock rate 2000000
!
!
!
router eigrp 800
network 10.0.0.0
network 10.16.18.0 0.0.0.255
network 172.14.0.0 0.0.0.255
network 192.168.4.0
passive-interface GigabitEthernet0/0
!
ip forward-protocol nd
!
no ip http server
no ip http secure-server
!
!
!
!
!
control-plane
!
!
!
line con 0
line aux 0
line 2
no activation-character
no exec
transport preferred none
transport output lat pad telnet rlogin lapb-ta mop udptn v120 ssh
stopbits 1
line vty 0 4
login
transport input all
!
scheduler allocate 20000 1000
!
end
WEEK3LAB/NYEDGE2 x
6+F{F{sk*Mar 6 13:58:37.019: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to down
NYEDGE2#
*Mar 6 13:58:40.543: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
*Mar 6 13:58:41.543: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up
*Mar 6 13:58:44.215: %DUAL-5-NBRCHANGE: EIGRP-IPv4 800: Neighbor 172.14.0.1 (GigabitEthernet0/1) is up: new adjacency
*Mar 6 13:59:55.551: %LINK-3-UPDOWN: Interface GigabitEthernet0/0, changed state to up
*Mar 6 13:59:56.551: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0, changed state to up
*Mar 6 14:00:49.255: %DUAL-5-NBRCHANGE: EIGRP-IPv4 800: Neighbor 192.168.4.5 (GigabitEthernet0/0) is up: new adjacency
NYEDGE2#show running-config
Building configuration…
Current configuration : 1588 bytes
!
! Last configuration change at 13:58:36 UTC Tue Mar 6 2018
version 15.2
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname NYEDGE2
!
boot-start-marker
boot-end-marker
!
!
!
no aaa new-model
!
ip cef
!
!
!
!
!
!
!
!
no ipv6 cef
!
multilink bundle-name authenticated
!
!
!
!
license udi pid CISCO2911/K9 sn FCZ1820604R
!
!
!
redundancy
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Loopback10
ip address 172.16.10.1 255.255.255.128
!
interface Loopback11
ip address 172.16.10.129 255.255.255.128
!
interface Loopback12
ip address 172.16.11.1 255.255.255.240
shutdown
!
interface Embedded-Service-Engine0/0
no ip address
shutdown
!
interface GigabitEthernet0/0
ip address 192.168.4.2 255.255.255.240
duplex auto
speed auto
!
interface GigabitEthernet0/1
ip address 172.14.0.2 255.255.255.0
duplex auto
speed auto
!
interface GigabitEthernet0/2
no ip address
shutdown
duplex auto
speed auto
!
interface Serial0/0/0
no ip address
shutdown
clock rate 2000000
!
interface Serial0/0/1
no ip address
shutdown
clock rate 2000000
!
!
!
router eigrp 800
network 172.14.0.0 0.0.0.255
network 172.16.10.0 0.0.0.127
network 172.16.11.0 0.0.0.15
network 192.168.4.0
!
ip forward-protocol nd
!
no ip http server
no ip http secure-server
!
!
!
!
!
control-plane
!
!
!
line con 0
line aux 0
line 2
no activation-character
no exec
transport preferred none
transport output lat pad telnet rlogin lapb-ta mop udptn v120 ssh
stopbits 1
line vty 0 4
login
transport input all
!
scheduler allocate 20000 1000
!
end
NYEDGE2#
WEEK3LAB/NYWAN1 x
NYWAN1#show running-config
Building configuration…
Current configuration : 1971 bytes
!
! Last configuration change at 14:03:34 UTC Tue Mar 6 2018
version 15.2
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname NYWAN1
!
boot-start-marker
boot-end-marker
!
!
no logging console
!
no aaa new-model
!
ip cef
!
!
!
!
!
!
no ipv6 cef
!
multilink bundle-name authenticated
!
!
!
!
!
!
!
voice-card 0
!
!
!
!
!
!
!
!
license udi pid CISCO2911/K9 sn FCZ1820605U
hw-module pvdm 0/0
!
!
!
!
redundancy
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Embedded-Service-Engine0/0
no ip address
shutdown
!
interface GigabitEthernet0/0
ip address 172.16.5.1 255.255.255.252
ip hello-interval eigrp 800 300
duplex auto
speed auto
!
interface GigabitEthernet0/1
ip address 172.16.16.1 255.255.255.0
duplex auto
speed auto
!
interface GigabitEthernet0/2
no ip address
shutdown
duplex auto
speed auto
!
interface Serial0/0/0
no ip address
encapsulation frame-relay
!
interface Serial0/0/0.256 point-to-point
bandwidth 256
ip address 172.88.0.9 255.255.255.252
snmp trap link-status
frame-relay interface-dlci 256
!
interface Serial0/0/0.641 point-to-point
bandwidth 64
ip address 172.88.0.1 255.255.255.252
snmp trap link-status
frame-relay interface-dlci 641
!
interface Serial0/0/1
no ip address
shutdown
!
interface Serial0/1/0
no ip address
shutdown
!
interface Serial0/1/1
no ip address
shutdown
!
interface Serial0/2/0
no ip address
shutdown
clock rate 2000000
!
!
router eigrp 800
network 172.16.5.0 0.0.0.3
network 172.16.16.0 0.0.0.255
network 172.88.0.0
!
ip forward-protocol nd
!
no ip http server
no ip http secure-server
!
!
!
!
!
control-plane
!
!
!
!
!
!
!
mgcp profile default
!
!
!
!
!
gatekeeper
shutdown
!
!
!
line con 0
line aux 0
line 2
no activation-character
no exec
transport preferred none
transport output pad telnet rlogin lapb-ta mop udptn v120 ssh
stopbits 1
line vty 0 4
login
transport input all
!
scheduler allocate 20000 1000
!
end
NYWAN1#
WEEK3LAB/PLABCSO01 LAN.PNG
WEEK3LAB/Week3Lab x
Introduction
The
Troubleshooting routing related technologies EIGRP module is part of the series of the troubleshooting modules which takes a different approach to learning from what has previously been used in this course.
Instead of providing you with a set of instructions and walkthroughs on how to configure specific technologies, this module provides you with a pre-configured environment which you will use to hone your troubleshooting and diagnostic skills.
In this module are a number of problems that you will need to diagnose and solve, these are outlined in the symptoms section.
All the issues that are present in the lab are formed from technologies that you have learnt about within the previous modules in this course. You will need to use the skills learnt in those modules to help you resolve the issues that are present in the lab.
There are no walkthroughs!
You will need to follow the process of:
Predicting normal operation
You will need to use any of the information provided within the exercise and the diagram that is shown at the beginning of each section for this. The diagram displays everything about the lab that you need to know, you must trust the diagram to be correct.
Isolate a specific problem
Use your knowledge of
show commands to locate issues, compare the output from these commands to what is documented in the diagram and within any textual content in this module.
Carry out root cause analysis
Combine both the output of the commands and the diagram to make your configuration changes to resolve the issues that have been documented.
Example
The following example is aimed to help you understand the format of this module.
Note: There is no requirement to execute the commands outlined in this example; they are not part of this lab.
Diagram
Symptom
There is no route in
NYEDGE2’s routing table for 172.16.15.0/24 which is a loopback interface on
NYEDGE1.
Troubleshooting
Observing the diagram we can see the following:
· Both routers have two interfaces on the same subnets (172.14.0.0/24 and 192.168.20.16/28)
· Both routers are in EIGRP AS 8001
Using these observations we could predict that EIGRP must be running on at least one of the interfaces on both routers, this interface should be the same on each router. We could also predict that the Loopback10 subnet must also be configured under EIGRP.
Using our knowledge we can focus on the following
potentialareas that could be causing the communication to fail:
· Incorrect AS numbers
· Incorrect masks on interfaces
· Incorrect EIGRP network statements
· Incorrect hello intervals
· Interface status not up/up
There could be other issues, but this is a good list to start with before we need to get too advanced.
Looking at these areas in sequence, we can use the following process to resolve the communication issue.
Note: This may not be the most effective way to resolve this issue, it simply serves as an example as an approach you could take.
Step 1
First let’s look at the EIGRP AS on either router. To do this we can use the
show ip protocols command:
NYEDGE1
NYEDGE1#show ip protocols
Routing Protocol is “eigrp 8001”
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Default networks flagged in outgoing updates
Default networks accepted from incoming updates
EIGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0
EIGRP maximum hopcount 100
EIGRP maximum metric variance 1
Redistributing: eigrp 8001
EIGRP NSF-aware route hold timer is 240s
Automatic network summarization is not in effect
Maximum path: 4
Routing for Networks:
172.16.15.0/24
192.168.20.0/28
Routing Information Sources:
Gateway Distance Last Update
Distance: internal 90 external 170
NYEDGE2
NYEDGE2#show ip protocols
Routing Protocol is “eigrp 8001”
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Default networks flagged in outgoing updates
Default networks accepted from incoming updates
EIGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0
EIGRP maximum hopcount 100
EIGRP maximum metric variance 1
Redistributing: eigrp 8001
EIGRP NSF-aware route hold timer is 240s
Automatic network summarization is not in effect
Maximum path: 4
Routing for Networks:
192.168.16.0
Routing Information Sources:
Gateway Distance Last Update
Distance: internal 90 external 170
Observing the output from both routers we can see that they are both configured with the same EIGRP AS number 8001.
However, we can also see further down in the output that the routing for networks section doesn’t look correct on
NYEDGE2. We are seeing a network of 192.168.16.0/24 which doesn’t exist in the diagram.
Observing the same list in
NYEDGE1, we could predict that this should be the 192.168.20.0 network instead. As
NYEDGE1 is not configured to run EIGRP on the 172.14.0.0/24 network, we can assume that we shouldn’t run EIGRP on this interface.
Correct this configuration error:
NYEDGE2#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
NYEDGE2(config)#router eigrp 8001
NYEDGE2(config-router)#no network 192.168.16.0
NYEDGE2(config-router)#network 192.168.20.16 0.0.0.15
Confirm if this configuration change has corrected this issue we can view the EIGRP neighbors table, or of course the routing table.
NYEDGE2#show ip eigrp neighbors
IP-EIGRP neighbors for process 8001
NYEDGE2#
It appears the table is still empty, indicating this wasn’t the only issue.
Step 2
Let’s confirm the EIGRP configuration on
NYEDGE1:
NYEDGE1#show run | section eigrp
router eigrp 8001
network 172.16.15.0 0.0.0.255
network 192.168.20.0 0.0.0.15
no auto-summary
Now, take a very close look at the diagram and at this output. This is a very subtle mistake made in the configuration when looking at the diagram.
The network statement that is configured for the 192.168.20 subnet is actually incorrect. The subnet address is not 192.168.20.0/28 it is in fact 192.168.20.16/28.
Correcting this issue:
NYEDGE1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
NYEDGE1(config)#router eigrp 8001
NYEDGE1(config-router)#no network 192.168.20.0 0.0.0.15
NYEDGE1(config-router)#network 192.168.20.16 0.0.0.15
NYEDGE1(config-router)#
Aug 12 07:09:33.783: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 8001: Neighbor 192.168.20.18 (GigabitEthernet0/0) is up: new adjacency
Instantly we see the neighbour adjacency come up.
Confirming that the route is now present on
NYEDGE2:
NYEDGE2#show ip route
Codes: 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
Gateway of last resort is not set
172.14.0.0/24 is subnetted, 1 subnets
C 172.14.0.0 is directly connected, GigabitEthernet0/1
172.16.0.0/24 is subnetted, 1 subnets
D 172.16.15.0 [90/156160] via 192.168.20.17, 00:00:55, GigabitEthernet0/0
192.168.20.0/28 is subnetted, 1 subnets
C 192.168.20.16 is directly connected, GigabitEthernet0/0
This very subtle
typo has had a drastic impact in our network. It’s often that these human mistakes occur in the real world and typically they are hard to spot because it may not be the entire statement that’s incorrect, just a small part of it.
You may also experience multiple issues, as in this case.
You can see that by using your knowledge that you have learnt in this course and using a logical approach to troubleshooting, you will be able to resolve the issues documented in this module.
Connecting to your lab
In this module you may need to work on any of the devices within the lab. You will need to determine which device is appropriate to issue your troubleshooting commands and configuration changes on.
· NYEDGE1
· NYEDGE2
· NYWAN1
· NYCORE1
· NYCORE2
· NYACCESS1
· PLABCSCO01
During the boot up process an activity indicator will be displayed in the device name tab:
· Black – Powered Off
· Blue – Working on your request
· Green – Ready to access
If the remote terminal is not displayed automatically in the main window (or popup) click the
Connect icon located in the tools bar to start your session.
Copyright Notice
This document and its content is copyright of Practice-IT – © Practice-IT 2014. All rights reserved. Any redistribution or reproduction of part or all of the contents in any form is prohibited other than the following:
1) You may print or download to a local hard disk extracts for your personal and non-commercial use only.
2) You may copy the content to individual third parties for their personal use, but only if you acknowledge the website as the source of the material. You may not, except with our express written permission, distribute or commercially exploit the content. Nor may you transmit it or store it in any other website or other form of electronic retrieval system.
1 of 4
Next
Top
Done
0 hours : 0 minutes, Succesfully changed content and lab.
0 hours : 0 minutes, PLABCSCO01 is currently in state Off
0 hours : 0 minutes, NYACCESS1 is currently having an action being processed, please wait for this to complete before you connect to it.
0 hours : 0 minutes, NYCORE2 is currently having an action being processed, please wait for this to complete before you connect to it.
0 hours : 0 minutes, NYCORE1 is currently having an action being processed, please wait for this to complete before you connect to it.
0 hours : 0 minutes, NYWAN1 is currently having an action being processed, please wait for this to complete before you connect to it.
0 hours : 0 minutes, NYEDGE2 is currently having an action being processed, please wait for this to complete before you connect to it.
0 hours : 0 minutes, NYEDGE1 is currently having an action being processed, please wait for this to complete before you connect to it.
0 hours : 0 minutes, Session start time 3-6:9:21
NYEDGE1
Busy
NYEDGE2
Busy
NYWAN1
Busy
NYCORE1
Busy
NYCORE2
Busy
NYACCESS1
Busy
PLABCSCO01
Off
Auto logout
59 mins.
Exercise 1 – Troubleshooting EIGRP
The configurations that have been applied to the devices within this lab have a number of incorrect settings and are causing numerous problems.
This exercise rolls up all your troubleshooting and configuration skills learnt within the modules of this course. You will need to use all of these skills to correct the configurations on each of the devices such that you resolve the symptoms that have been noted in the symptoms list below.
Pay close attention to the diagram shown below,
this diagram will give you all the information you need to fix the issues. As with any real world scenario, if there is something you don’t understand, you may need to refer to your favourite search engine to gain some additional understanding on a particular technology.
Symptoms
The following symptoms have been observed. Use your skills and the information in the diagram below to resolve them.
· Server PLABCSCO01 is receiving intermittent ping replies from 172.16.16.1 as shown in the image below after this list.
· The route for 10.16.18.0/24 is going via NYEDGE2 and not directly via NYEDGE1 as it should when using a traceroute from PLABCSCO01.
· NYCORE2 has no EIGRP adjacencies.
· There is an incorrect route entry for 192.168.16.0, there should only be a /24 route in any of the routing tables for this subnet.
· There is no load balancing between NYWAN1 serial interfaces s0/0/0.641 and s0/0/0.256
· The route for 172.16.10.128/25 is not being advertised.
· The route for 172.16.11.0/28 is not being advertised.
· The route for 172.16.11.128/28 is not being advertised.
Intermittent ping results on
PLABCSCO01 while pinging 172.16.16.1:
Issue hints:
While diagnosing the problems outlined above you will need to check things such as:
· Autonomous system numbers
· Correct masks applied to interfaces
· Correct network addresses (including the mask) under the EIGRP configuration
· Correct hello intervals
· Correct interface status
· Correct variance statement
Diagram
Use this diagram as a reference to how the network should be configured for correct operation.
End results
The diagram above is correct and how the lab should be configured for optimal data transmission.
If you have resolved all the issues your ping between
PLABCSCO01 and 172.16.16.1 should be stable without any errors.
You should see the following routes on
NYWAN1:
· 172.16.10.128/25
· 172.16.11.0/28
· 172.16.11.128/28
You should see multiple routing entries for the following network addresses on
NYWAN1:
· 192.168.224.0/24
· 192.168.225.0/24
· 192.168.226.0/27
· 192.168.226.32/27
The next hop for 10.16.18.0/24 on
NYCORE1 should point directly to
NYEDGE1, not via
NYEDGE2
Prev
2 of 4
Next
Top
Done
Exercise 2 – Resolutions
This exercise does not cover fixing the actual problems outlined in exercise 1. Instead, this exercise serves as a list of configuration items that you should have resolved.
Problem 1
Incorrect hello timer.
Problem 2
Incorrectly configured passive-interface.
Problem 3
Incorrectly configured Autonomous System number.
Problem 4
Incorrect IP address configuration on SVI.
Problem 5
No variance command under EIGRP.
Problem 6
Missing network statement under EIGRP.
Problem 7
Interface is shutdown.
Problem 8
Incorrect network statement under EIGRP.
Summary
In this module you analysed and hopefully resolved the configuration errors for the following technologies:
· Incorrectly configured EIGRP AS numbers.
· Incorrect hello intervals.
· Missing or incorrect network statements.
· Passive interfaces.
· Missing or incorrect variance commands.
· Incorrectly configured IP addresses.
image1
image2
image3
Top-quality papers guaranteed
100% original papers
We sell only unique pieces of writing completed according to your demands.
Confidential service
We use security encryption to keep your personal data protected.
Money-back guarantee
We can give your money back if something goes wrong with your order.
Enjoy the free features we offer to everyone
-
Title page
Get a free title page formatted according to the specifics of your particular style.
-
Custom formatting
Request us to use APA, MLA, Harvard, Chicago, or any other style for your essay.
-
Bibliography page
Don’t pay extra for a list of references that perfectly fits your academic needs.
-
24/7 support assistance
Ask us a question anytime you need to—we don’t charge extra for supporting you!
Calculate how much your essay costs
What we are popular for
- English 101
- History
- Business Studies
- Management
- Literature
- Composition
- Psychology
- Philosophy
- Marketing
- Economics