300-135 TSHOOT Study Guide
300-135 TSHOOT Study Guide
This workbook covers all the information you need to pass the Cisco CCNP
Routing and Switching, Route300-101 exam. The workbook is design to take
a practical approach of learning with real life examples and case studies.
The following topics are general guidelines for the content likely to be
included on the exam
Ø Network Principles 5%
Ø Layer 2 Technologies 40%
Ø Layer 3 Technologies 40%
Ø VPN Technologies 5%
Ø Infrastructure Security 5%
Ø Infrastructure Services 5%
This workbook covers all the information you need to pass the Cisco CCNP
Routing and Switching, Route300-101 exam. The workbook is design to take
a practical approach of learning with real life examples and case studies.
IPSpecialist provides full support to the candidates in order for them to pass
the exam.
Prior to registration, decide which exam to take, note the exam name and
number. For complete exam details, refer to the “Current Exam List” from
the Cisco website.
The following topics are general guidelines for the content likely to be
included on the exam
Ø Network Principles 5%
Ø Layer 2 Technologies 40%
Ø Layer 3 Technologies 40%
Ø VPN Technologies 5%
Ø Infrastructure Security 5%
Ø Infrastructure Services 5%
CLI Tools
Cisco IOS offers Command Line Interface CLI, which provides help in
troubleshooting network issues. Some examples of the commands used in
CLI are:
Show
Debugging
Show
The command "show" is very popular and helpful for the network
Router#
Router# show debugging
Router#
Router# no debug ntp packets
Router#
Redirect Debugging
In order to redirect the output the results of debugging, logging command is
used in configuration mode. This redirection of debugging can be destined to
console lines, VTY lines, internal buffer, or any syslog server. Logging to the
console lines has huge overhead on the network device while VTY line
consumes lesser overheads than Console. For even lesser overhead, use
Syslog server and for least overheads internal buffer are used.
Router(config)# logging ?
A.B.C.D IP address of the logging host
buffered Set buffered logging parameters
console Set console logging parameters
host Set syslog server IP address and parameters
on Enable logging to all enabled destinations
trap Set syslog server logging level
userinfo Enable logging of user info on privileged mode enabling
Router(config)#
Router#
// Logging console enable logging on Console
CLI Tools
Cisco IOS offers Command Line Interface CLI, which provides help in
troubleshooting network issues. Some examples of the commands used in
CLI are:
Show
Debugging
Show
The command "show" is very popular and helpful for the network
Router#
Router# show debugging
Router#
Router# no debug ntp packets
Router#
Redirect Debugging
In order to redirect the output the results of debugging, logging command is
used in configuration mode. This redirection of debugging can be destined to
console lines, VTY lines, internal buffer, or any syslog server. Logging to the
console lines has huge overhead on the network device while VTY line
consumes lesser overheads than Console. For even lesser overhead, use
Syslog server and for least overheads internal buffer are used.
Router(config)# logging ?
A.B.C.D IP address of the logging host
buffered Set buffered logging parameters
console Set console logging parameters
host Set syslog server IP address and parameters
on Enable logging to all enabled destinations
trap Set syslog server logging level
userinfo Enable logging of user info on privileged mode enabling
Router(config)#
Router#
// Logging console enable logging on Console
Traceroute
Traceroute command is also a very useful and important command while
troubleshooting the network. Upon a successful completion of traceroute
command, it means that up to layer 3 is in function as the ping command
indicates. Difference from ping is, Traceroute command also results the track
of path covered to reach the destination along with the timestamp. When
traceroute command is executed, Sequence of UDP (User Datagram Protocol)
with incrementing TTL (Time to Live) value is send. First 3 datagram is sent
with TTL value of 1, so it expires when hit first router. Router reply back
with ICMP time exceeded message. Now, Another 3 UDP packets are sent
with TTL of 2. This process continues till reaches the destination.
Conditional Debugging
Mind Map
Ping
Ping command is used for identification of Network Connectivity. If ping is
successful, it means that Physical, Data-Link and Network layer are in
function so you can focus on upper layers such as transport, session
presentation, and Application layers. Vice versa, an unsuccessful ping
indicates the need of troubleshoot of Layer 1, Layer 2 and Layer 3. Ping
command uses ICMP (Internet Control Message Protocol) echo message to
the destination address and the destination reply back. For every reply of
ICMP echo packet, an exclamation mark appears at output as shown in the
next figure.
Port Error
In order to troubleshoot, the switch starts with layer 1. Check the cabling and
connectivity first. By observing the statistics of port, number of packets sent
and received, as well as dropped, can be measured which helps to
troubleshoot the issue. Dropping of packet may be due to congestion in the
network or Bad Cabling. Auto MDIX (Medium Dependant Interface
Crossover) enables the switch to auto detect the cable type. Straight through
and Crossover both cables can be used for like and unlike devices if Auto-
MDIX feature is enabled on switch.
Duplex Error
If a switch connected to a device configured with half duplex, then switch is
configured with full duplex on an interface. The interface will face duplex
mismatch and packet are dropped due to collusion. Cisco Switch can be
configured as auto negotiation for both speed and Duplex settings to
negotiate with respect to the device it is connected with.
SDM Template
SDM is Switching Database Manager. It is used to manage the switching
information of Layer 2 up to Layer 3. For this, Ternary Content Addressable
Memory or TCAM is used. Basic purpose of TCAM is forwarding Lookups.
As far as SDM Templates are concerned, there are four templates:
Routing Template
Routing Template is used for allocation of resources to the routing
Mind Map
Port Error
In order to troubleshoot, the switch starts with layer 1. Check the cabling and
connectivity first. By observing the statistics of port, number of packets sent
and received, as well as dropped, can be measured which helps to
troubleshoot the issue. Dropping of packet may be due to congestion in the
network or Bad Cabling. Auto MDIX (Medium Dependant Interface
Crossover) enables the switch to auto detect the cable type. Straight through
and Crossover both cables can be used for like and unlike devices if Auto-
MDIX feature is enabled on switch.
Duplex Error
If a switch connected to a device configured with half duplex, then switch is
configured with full duplex on an interface. The interface will face duplex
mismatch and packet are dropped due to collusion. Cisco Switch can be
configured as auto negotiation for both speed and Duplex settings to
negotiate with respect to the device it is connected with.
SDM Template
SDM is Switching Database Manager. It is used to manage the switching
information of Layer 2 up to Layer 3. For this, Ternary Content Addressable
Memory or TCAM is used. Basic purpose of TCAM is forwarding Lookups.
As far as SDM Templates are concerned, there are four templates:
Routing Template
Routing Template is used for allocation of resources to the routing
To enable:
Switch(config)# cdp run
Switch(config)# end
To disable:
Switch(config)#no cdp run
Switch(config)# end
Configuring LLDP
Switch>en
Switch#config t
Switch(config)#lldp run
//Enable LLDP Globally
Switch(config)#int eth 0/0
Switch(config-if)#lldp transmit
// Send LLDP Packets
Switch(config-if)#lldp receive
// Receive LLDP Packets
Switch(config-if)#ex
Characteristics of LLDP
Hold time
Time in seconds, device hold the LLDP packets before discarding ranging
from 0 to 65535 seconds with default value of 120 seconds
Command:
Switch(config)#lldp holdtime 150
Reinit
Time delay in second to initial LLDP on an interface ranging from 2 to 5
secs. 2 seconds is default
Timer
Time in second to send LLDP updates. Range of the timer is from 5 seconds
to 65534 seconds, default value is 30 seconds.
Command:
Switch(config)#lldp timer 120
Switch(config)#udld enable
// Enable UDLD enable mode globally
Switch(config)#int eth 0/0
Switch(config-if)#udld port
// Enable UDLD enable mode on interface
Switch(config)#udld aggressive
// Enable UDLD Aggressive mode globally
Switch(config)#int eth 0/0
Access Ports:
By default Switch, ports are assigned to Dynamic Auto. These switch ports
can be changed to Access and Trunk ports as well.
Commands
Switch(config)#int fa 0/1
Switch(config-if)#switchport mode ?
Trunk Ports:
Switch(config)#int fa 0/2
Switch(config-if)#switchport mode trunk
Switch(config-if)#ex
Verification:
Switch#show int fa 0/2 switchport
Command
Switch#show VLAN id 1
Command
Switch#show int fa 0/3 switchport
Switch(config)#udld enable
// Enable UDLD enable mode globally
Switch(config)#int eth 0/0
Switch(config-if)#udld port
// Enable UDLD enable mode on interface
Switch(config)#udld aggressive
// Enable UDLD Aggressive mode globally
Switch(config)#int eth 0/0
Switch(VLAN)#VLAN ?
<1-1005> ISL VLAN index
Switch(VLAN)#VLAN 10
VLAN 10 modified:
Switch(VLAN)#ex
APPLY completed.
Exiting....
Verification:
Switch#show VLAN 10
Command
Switch#show VLAN id 1
Command
Switch#show int fa 0/3 switchport
VTP pruning blocks unneeded flooded traffic to VLANs on trunk ports that
are included in the pruning-eligible list. Only VLANs included in the
pruning-eligible list can be pruned. By default, VLANs 2 through 1001 is
pruning eligible switch trunk ports. If the VLANs are configured as pruning-
ineligible, the flooding continues. VTP pruning is supported in all VTP
versions.
802.1Q Encapsulation
Dot 1Q Trunking
DOt1Q is actually the IEEE standard 802.1Q that is used for trunking
encapsulation. In a switched network, Dot1Q encapsulation on a trunk port
allows the tagged frames of multiple VLANs to be transported.
Supporting Modes of Trunk
Dynamic Auto
Dynamic Desirable
Trunk
No negotiate
Dot 1Q Tunnelling
802.1Q is also used for tunneling by service providers to provide clients with
layer 2 VPN connectivity. Customers can continue to use their own VLAN
ID configurations while the Internet service provider maintains those tagging.
To verify Manual Pruning, issue the command show int eth 0/0 switchport
Compatibility of PAgP
Compatibility of LACP
Configuration:
SW1(config)#interface range Ethernet 0/0 - 1
SW1(config-if-range)#channel-group 1 mode on
SW1(config-if-range)#exit
SW1(config)#exit
Verification
To verify Manual Pruning, issue the command show int eth 0/0 switchport
Compatibility of PAgP
Compatibility of LACP
Configuration:
SW1(config)#interface range Ethernet 0/0 - 1
SW1(config-if-range)#channel-group 1 mode on
SW1(config-if-range)#exit
SW1(config)#exit
Switch1#
Switch 3
Switch3#show spanning-tree
VLAN0001
Spanning tree enabled protocol ieee
Root ID Priority 32769
Address 0001.63DD.5992
This bridge is the root Root Bridge
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Switch3#
Switch3#
Case Study:
Verification
Configuration:
Router 1
Router(config)#int port-channel 1
*Mar 1 00:00:43.367: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel1,
changed state to down.0.1
Router(config-if)#ip add 10.0.0.1 255.255.255.0
Router(config-if)#no sh
Router(config-if)#ex
//After examination of the results, it is found that Priorities are not set, by taking default calculations;
Switch with Lowest MAC wins the Election for every VLAN. Hence Load is on Bridge Switch
Solution:
Switch A:
SwitchA(config)#spanning-tree VLAN 10 priority 0
SwitchA(config)#ex
// Making Switch A Bridge for VLAN 10.
Switch B:
SwitchB(config)#spanning-tree VLAN 20 priority 0
SwitchB(config)#ex
// Making Switch B Bridge for VLAN 20.
Switch C:
SwitchC(config)#spanning-tree VLAN 30 priority 0
SwitchC(config)#ex
// Making Switch C Bridge for VLAN 30.
Switch 1
Switch1#show spanning-tree
VLAN0001
Spanning tree enabled protocol ieee
Root ID Priority 32769 Priority of Root Bridge
Address 0001.63DD.5992 Indicates MAC address of Root Bridge
Cost 38 Cost to Root Bridge
Port 2(FastEthernet0/2)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Case Study:
An Issue is reported that two switches are not participating in Spanning tree
Election. No information are exchanging between them.
Troubleshooting
Switch1#Show spanning-tree
Configuration:
Switch 1:
S1(config)#VLAN 10
S1(config-VLAN)#ex
S1(config)#VLAN 20
S1(config-VLAN)#ex
S1(config)#VLAN 30
S1(config-VLAN)#ex
S1(config)#VLAN 40
S1(config-VLAN)#ex
S1(config)#
S1(config)#int range Ethernet 0/0,Ethernet 0/1
S1(config-if-range)#switchport trunk encapsulation dot1q
// First change the encapsulation from Auto to dot1Q
S1(config-if-range)#switchport mode trunk
//Change the Port from Access to Trunk
S1(config-if-range)#ex
S1(config)#
S1(config)#spanning-tree mst configuration
S1(config-mst)#instance 1030 VLAN 10,30
//Remember Instance Number, Assign Correct VLANs
// Remember Priority (33,798) will be the sum of Default Priority (32768) andn Instance
Number(1030)
S1(config-mst)#name IPS
//Requires the same Configuration on all switches
Case Study:
An Issue is reported that two switches are not participating in Spanning tree
Election. No information are exchanging between them.
Troubleshooting
Switch1#Show spanning-tree
From the output, we can see the status of the Interface Ethernet 0/0 which is
the trunk port between Switch 1 and Switch 2. This Interface is not enabled
with any Port guard Feature, any bpdu filter or any bpdu guard. Instance 0
is in Root Port Role and Status is Forwarding. Instance 1030 is in
Designated port role and in forwarding State. Where as from previous
output of Switch 1 For instance 0 is Designated Port. That’s all we need
from MST.
The command Show spanning-tree also shows the Output of MST ports so
we can also just use Show Spanning-tree command.
S2#show spanning-tree
The Output also shows the details of MST1030 that VLAN 10 and VLAN
30 are mapped on it. Root Bridge is the MAC address AABB.CC00.2100
with Priority 1030 which this switch. MAC Address of this switch is
AABB.CC00.2100 and the Priority of this switch is 1030 for MST 1030.
Interface Ethernet 0/0 is the Designated port in forwarding state similarly
Troubleshooting
Start with IP addressing of Management PC
Issue ipconfig at command prompt of PC
Subnet mask is 255.0.0.0 which means /8. Router is configured with /30
which means 255.255.255.252. Correct the addressing from Control panel.
Verification:
Troubleshooting:
Troubleshooting
Start with IP addressing of Management PC
Issue ipconfig at command prompt of PC
Subnet mask is 255.0.0.0 which means /8. Router is configured with /30
which means 255.255.255.252. Correct the addressing from Control panel.
Solution:
Relay-Router #config t
Enter configuration commands, one per line. End with CNTL/Z.
Relay-Router (config)#int eth 0/0
Relay-Router (config-if)#ip helper-address 11.0.0.2
Relay-Router (config-if)#ex
Relay-Router (config)#
Relay-Router#show run
interface Ethernet0/0
Server Configuration:
R1(config)# hostname server
SERVER(config)# ipv6 unicast-routing
no ip cef
no ipv6 cef
!
interface Ethernet0/0
no ip address
duplex auto
speed auto
shutdown
!
interface Ethernet1/0
Solution:
Relay-Router #config t
Enter configuration commands, one per line. End with CNTL/Z.
Relay-Router (config)#int eth 0/0
Relay-Router (config-if)#ip helper-address 11.0.0.2
Relay-Router (config-if)#ex
Relay-Router (config)#
Relay-Router#show run
interface Ethernet0/0
Server-Router#show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route
Server-Router #
Server-Router #config t
Enter configuration commands, one per line. End with CNTL/Z.
Server-Router (config)#ip route 10.0.0.0 255.255.255.0 11.0.0.1
Server-Router (config)#ex
Server-Router #
%SYS-5-CONFIG_I: Configured from console by console
Server-Router #
Server Configuration:
R1(config)# hostname server
SERVER(config)# ipv6 unicast-routing
Troubleshooting:
London#show ip route
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
a - application route
+ - replicated route, % - next hop override
Troubleshooting
Case Study:
The Company added a New Router (R3) into its network. It is configured
with OSPF as the other routers are. Issue is reported that older routers do not
identify this new router, hence, no adjacency is formed.
Troubleshooting
Troubleshooting:
London#show ip route
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
a - application route
+ - replicated route, % - next hop override
Solution:
*May 8 10:21:26.452: %OSPF-5-ADJCHG: Process 10, Nbr 10.0.0.2 on Ethernet0/0 from FULL to
DOWN, Neighbor Down: Interface down or detached
*May 8 10:21:26.460: %OSPF-5-ADJCHG: Process 20, Nbr 10.0.0.2 on Ethernet0/0 from
LOADING to FULL, Loading Done
*May 8 10:21:43.295: %OSPF-5-ADJCHG: Process 20, Nbr 10.0.0.2 on Ethernet0/0 from FULL to
DOWN, Neighbor Down: Interface down or detached
Verification
CompanyB#ping 11.0.0.01
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 11.0.0.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
London(config)#int lo 0
London(config-if)#ip add 12.0.0.1 255.0.0.0
London(config)#router ospf 1
London(config-router)#net 10.0.0.0 0.255.255.255 area 0
London(config-router)#net 12.0.0.0 0.255.255.255 area 0
London(config-router)#ex
London#show ip route
Berlin(config)#int lo 0
Berlin(config-if)#
Berlin(config-if)#ip add 11.0.0.1 255.0.0.0
Berlin(config-if)#no sh
Berlin(config)#router ospf 1
Solution:
Now, remove the interface from Passive
R3(config)#router ospf 1
R3(config-router)#no passive-interface eth 0/0
R3(config-router)#ex
R3(config)#
*May 8 09:44:48.225: %OSPF-5-ADJCHG: Process 1, Nbr 11.0.0.2 on Ethernet0/0 from
LOADING to FULL, Loading Done
Verification
R3#ping 10.0.0.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.0.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
Case Study:
Troubleshooting:
R1(config)#router rip
R1(config-router)#version 2
R1(config-router)#net 11.0.0.0
R1(config-router)#no auto-summary
R1(config-router)#ex
// introduce the RIP network
Router # 02:
R2#config t
Enter configuration commands, one per line. End with CNTL/Z.
R2(config)#router rip
R2(config-router)#version 2
R2(config-router)#net 11.0.0.0
//Introduce the RIP network
R2(config-router)#redistribute ospf 1 metric
// redistributing OSPF Process 1 routes in RIP protocol. Make sure the Process Number of OSPF
R2(config-router)#ex
R2(config)#
Router # 03:
R3(config)#int fa 0/0
R3(config-if)#ip add 10.0.0.1 255.255.255.0
// Assign Correct IP address and Subnet Mask
R3(config-if)#no sh
//Must Turn up the interface
R3(config-if)#ex
R3(config)#
R3(config)#int lo 0
R3(config-if)#ip add 192.168.1.1 255.255.255.0
// Assign Correct IP address and Subnet Mask
R3(config-if)#no sh
//Must Turn up the interface
R3(config-if)#ex
R3(config)#
R3(config)#int lo 1
R3(config-if)#ip add 192.168.0.1 255.255.255.0
// Assign Correct IP address and Subnet Mask
R3(config-if)#no sh
//Must Turn up the interface
R3(config-if)#ex
R3(config)#
R3(config)#router ospf 1
R3(config-router)#net 10.0.0.0 0.0.0.255 area 0
R3(config-router)#net 192.168.1.0 0.0.0.255 area 0
London(config)#int lo 0
London(config-if)#ip add 12.0.0.1 255.0.0.0
Case Study
In this case, Route Redistribution is considered. R2 is to redistribute the
OSPF routes into RIP only Router.
Router # 01:
R1(config)#int eth 0/1
R1(config-if)#ip add 11.0.0.1 255.0.0.0
// Assign Correct IP address and Subnet Mask
R1(config-if)#no sh
//Must Turn up the interface
R1(config)#router rip
R1(config-router)#version 2
R1(config-router)#net 11.0.0.0
R1(config-router)#no auto-summary
R1(config-router)#ex
// introduce the RIP network
Router # 02:
R2#config t
Enter configuration commands, one per line. End with CNTL/Z.
R2(config)#router rip
R2(config-router)#version 2
R2(config-router)#net 11.0.0.0
//Introduce the RIP network
R2(config-router)#redistribute ospf 1 metric
// redistributing OSPF Process 1 routes in RIP protocol. Make sure the Process Number of OSPF
R2(config-router)#ex
R2(config)#
Router # 03:
R3(config)#int fa 0/0
R3(config-if)#ip add 10.0.0.1 255.255.255.0
// Assign Correct IP address and Subnet Mask
R3(config-if)#no sh
//Must Turn up the interface
R3(config-if)#ex
R3(config)#
R3(config)#int lo 0
R3(config-if)#ip add 192.168.1.1 255.255.255.0
// Assign Correct IP address and Subnet Mask
R3(config-if)#no sh
//Must Turn up the interface
R3(config-if)#ex
R3(config)#
R3(config)#int lo 1
R3(config-if)#ip add 192.168.0.1 255.255.255.0
// Assign Correct IP address and Subnet Mask
R3(config-if)#no sh
//Must Turn up the interface
R3(config-if)#ex
R3(config)#
R3(config)#router ospf 1
R3(config-router)#net 10.0.0.0 0.0.0.255 area 0
R3(config-router)#net 192.168.1.0 0.0.0.255 area 0
For Router 1:
Router 1 has three networks:
1. 192.168.2.0/30
2. 192.168.1.0/30
3. 192.168.0.0/30
255
Network 255 255 255
128 64 32 16 8 4 2 1
192.168.2.0/30 192 168 0 0 0 0 0 0 1 0 0
192.168.1.0/30 192 168 0 0 0 0 0 0 0 1 0
192.168.0.0/30 192 168 0 0 0 0 0 0 0 0 0
Now the subnet mask will be /22. Wild card mask of the summarised network
will be 0.0.3.255
For Router 2:
Router 1 has three networks:
1. 192.168.2.0/30
2. 192.168.3.0/30
3. 192.168.4.0/30
255
Network 255 255 255
128 64 32 16 8 4 2 1
192.168.2.0/30 192 168 0 0 0 0 0 0 1 0 0
192.168.3.0/30 192 168 0 0 0 0 0 0 1 1 0
192.168.4.0/30 192 168 0 0 0 0 0 1 0 0 0
Now the subnet mask will be /21. Wild card mask of the summarised network
will be 0.0.7.255
Router 2
Router2(config)#router ospf 1
Router2(config-router)#net 192.168.0.0 0.0.7.255 area 0
// Enter Manually Summarized network for Summarization
// Make sure about the Wild card bits. If wild card bits are not correct, only the networks lie in the
wild card will be learned only
R1#show ip route
R2#show ip route
Topology Diagram:
Case Study:
Consider the case in which Router 3 is to be configured for Policy Based
Routing. All the traffic from 192.168.0.0/24 Network should be forwarded
to Router 1 via Router 2.
Configuration:
Router # 01:
R1(config)#int eth 0/0
R1(config-if)#ip add 11.0.0.1 255.0.0.0
// Assign Correct IP address and MAsk
R1(config-if)#no sh
// Must turn up the interface
R1(config-if)#ex
R1(config)#router rip
R1(config-router)#version 2
Router 1:
Router(config)#router rip
Router(config-router)#version 2
Router(config-router)#net 192.168.2.0
Router(config-router)#net 192.168.1.0
Router(config-router)#net 192.168.0.0
Router(config-router)#auto-summary
// Auto summary is enabled by default in RIP
// introduce all networks
Router(config-router)#ex
R4(config)#router rip
R4(config-router)#version 2
R4(config-router)#net 192.168.0.0
R4(config-router)#no auto-summary
// Introduce Every Directly connected Network
For Router 1:
Router 1 has three networks:
1. 192.168.2.0/30
2. 192.168.1.0/30
3. 192.168.0.0/30
255
Network 255 255 255
128 64 32 16 8 4 2 1
192.168.2.0/30 192 168 0 0 0 0 0 0 1 0 0
192.168.1.0/30 192 168 0 0 0 0 0 0 0 1 0
192.168.0.0/30 192 168 0 0 0 0 0 0 0 0 0
Now the subnet mask will be /22. Wild card mask of the summarised network
will be 0.0.3.255
For Router 2:
Router 1 has three networks:
1. 192.168.2.0/30
2. 192.168.3.0/30
3. 192.168.4.0/30
255
Network 255 255 255
128 64 32 16 8 4 2 1
192.168.2.0/30 192 168 0 0 0 0 0 0 1 0 0
192.168.3.0/30 192 168 0 0 0 0 0 0 1 1 0
192.168.4.0/30 192 168 0 0 0 0 0 1 0 0 0
Now the subnet mask will be /21. Wild card mask of the summarised network
will be 0.0.7.255
Case Study:
In this case, RIP and OSPF are configured and routes are redistributed among
them. Due to their default administrative values, routing loop may also be
created but in this case, router is using longer path due to default AD values.
As the RIP is redistributing the Loopback address 10.0.0.1/8 into OSPF, both
OSPF routers using type 5 LSA can share the redistributed route. Due to this
R2 is using R3 to R1 to reach 10.0.0.1/8 instead of using R1 directly.
Topology Diagram
Troubleshooting:
Solution:
R1(config)#router rip
R1(config-router)#distance 100
R1(config-router)#ex
R1(config)#end
R1#clear ip route *
R2(config)#router rip
R2(config-router)#distance 100
R2(config-router)#ex
R2(config)#end
R2#clear ip route *
R3(config)#router rip
R3(config-router)#distance 100
R3(config)#router rip
R3(config-router)#version 2
R3(config-router)#net 10.0.0.0
R3(config-router)#net 192.168.0.0
R3(config-router)#net 12.0.0.0
R3(config-router)#no auto-summary
// Introduce Every Directly connected Network
R3(config)#ip access-list standard Policy1
// Remember the Access-list name, It is case sensitive
R3(config-std-nacl)#permit 192.168.0.0 0.0.0.255
// carefully permit or deny the network or host. It can affect the entire network if it is wrong
R3(config-std-nacl)#ex
R3(config)#route-map R3toR1 permit
R3(config-route-map)#match ip address Policy1
// Make sure the access-list assigned to route map is the right one
R3(config-route-map)#set ip next-hop 10.0.0.2
// Next hop IP address is the next node the filtered traffic forwarded to.
R3(config-route-map)#ex
R3(config)#int eth 0/0
R3(config-if)#ip policy route-map R3toR1
// Apply the Route map on the correct interface
R3(config-if)#end
R3#
Router # 04:
R1(config)#router eigrp 1
// In case of different Autonomous System Number, adjacency will not form
R1(config-router)#net 10.0.0.0 0.255.255.255
// Make sure the network statement
R1(config-router)#net 172.16.0.0 0.0.255.255
// Make sure the subnet mask
R1(config-router)#net 172.17.0.0 0.0.255.255
R1(config-router)#net 172.18.0.0 0.0.255.255
R1(config-router)#no auto-summary
R1(config-router)#ex
// Introducing EIGRP directly Connected Networks
R2
R2(config)#router eigrp 1
// In case of different Autonomous System Number, adjacency will not form
R2(config-router)#net 10.0.0.0 0.255.255.255
R2(config-router)#net 192.168.0.0 0.0.0.255
R2(config-router)#net 192.168.1.0 0.0.0.255
R2(config-router)#net 192.168.2.0 0.0.0.255
R2(config-router)#no auto-summary
R2(config-router)#ex
R2
Case Study:
Consider the case of Four Routers. Heavy traffic is exchanged between R1
and R4. By using EIGRP, load balancing is to be configured so that R1 can
used two paths to access R4 by using R2 and By using R3. Initially Equal
Cost load balancing is to be configured.
Configuration:
Routr 1:
Router(config)#hostname R1
R1(config)#int eth 0/0
R1(config-if)#ip add 10.0.0.1 255.0.0.0
Router 2:
Router(config)#hostname R2
R2(config)#int eth 0/0
R2(config-if)#ip add 10.0.0.2 255.0.0.0
// Assign an IP address and Mask
R2(config-if)#no sh
//Must turn up the interface
R2(config-if)#ex
R2(config)#int eth 0/1
R2(config-if)#ip add 12.0.0.2 255.0.0.0
// Assign an IP address and Mask
R2(config-if)#no sh
//Must turn up the interfac
R2(config-if)#ex
R2(config)#router eigrp 1
R2(config-router)#net 10.0.0.0 0.255.255.255
R2(config-router)#net 12.0.0.0 0.255.255.255
R2(config-router)#no auto-summary
R2(config-router)#ex
// Introduce Each an every directly connected network, Remember to configure Wild card bits.
Router 4:
Router(config)#hostname R4
R4(config)#int eth 0/0
R4(config-if)#ip add 13.0.0.1 255.0.0.0
// Assign an IP address and Mask
R4(config-if)#no sh
//Must turn up the interface
R4(config-if)#ex
R4(config)#int eth 0/1
R4(config-if)#ip add 12.0.0.1 255.0.0.0
// Assign an IP address and Mask
R4(config-if)#no sh
//Must turn up the interface
R4(config-if)#ex
R4(config)#router eigrp 1
R4(config-router)#net 13.0.0.0 0.255.255.255
R4(config-router)#net 12.0.0.0 0.255.255.255
Verification:
Traffic Share count on both interfaces Ethernet 0/0 and Ethernet 0/1 is equal
“Traffic Share count 1”
R1#conf t
R1(config)#router eigrp 1
R1(config-router)#variance ?
<1-128> Metric variance multiplier
R1(config-router)#variance 2
R1(config-router)#exit
Router 2:
Router(config)#hostname R2
R2(config)#int eth 0/0
R2(config-if)#ip add 10.0.0.2 255.0.0.0
// Assign an IP address and Mask
R2(config-if)#no sh
//Must turn up the interface
R2(config-if)#ex
R2(config)#int eth 0/1
R2(config-if)#ip add 12.0.0.2 255.0.0.0
// Assign an IP address and Mask
R2(config-if)#no sh
//Must turn up the interfac
R2(config-if)#ex
R2(config)#router eigrp 1
R2(config-router)#net 10.0.0.0 0.255.255.255
R2(config-router)#net 12.0.0.0 0.255.255.255
R2(config-router)#no auto-summary
R2(config-router)#ex
// Introduce Each an every directly connected network, Remember to configure Wild card bits.
In the output, U shows that the network is in the Update state. If any network
is in reply state, it will be represented by “r”.
Static: Static Option allows sharing the updates of Static Routes with its
neighbours. By default static routes are not shared. Use redistribute static
command to share static route updates.
Topology:
Configuration
R1:
R1# show ip route
R2(config)#router Eigrp 1
R2(config)#eigrp stub receive-only
Verification:
R1#show ip route
Show running configuration will also show that router is configured as stub
receive only.
R2(config)#router Eigrp 1
R2(config)#eigrp stub receive-only
Verification:
R2#ping 1000::1 to check successful connectivity
Show running configuration will also show that router is configured as stub
receive only.
Berlin(config)#router ospf 1
Berlin(config-router)#net 11.0.0.0 0.255.255.255 area 0
// Introduce Correct network, Every directly connected Network. Make sure you have to configure
Wild card bits. Mention correct Area
Verification of Neighbourship:
London# Show ip ospf nei
Verification:
R2#ping 1000::1 to check successful connectivity
Verification:
London# Show ip ospf nei
From the output, we can observe the Process ID running on the interface,
Router ID, Network Type (Point to Point/Multipoint/Broadcast/NMBA),
State of Router (DR,BDR,ABR or ASBR) Hello and Dead Timer in seconds
etc.
Topology:
Case Study:
In this Lab, OSPF is configured with different areas to troubleshoot the
processes of OSPF routing Protocol. London Router link are connected in
OSPF area 0. Berlin Router is connected with Area 0 via Ehternet 0/0 as
well as Connected with Area 10 via Ethernet 0/1. New York is running
OSPF Area 10 as well as introducing its RIP route into OSPF, which help
us in troubleshooting LSA Type 7 as well.
Configuration:
NewYork(config)#int eth 0/1
NewYork(config-if)# ip add 10.0.0.1 255.0.0.0
//Configure Correct IP Addressing and Mask
NewYork(config-if)# no sh
// Make sure to up every interface
NewYork(config)# int lo 0
NewYork(config-if)# ip add 192.168.0.1 255.255.255.0
//Configure Correct IP Addressing and Mask
NewYork(config)#router ospf 1
Berlin(config)#router ospf 1
Berlin(config-router)#net 11.0.0.0 0.255.255.255 area 0
// Introduce Correct network, Every directly connected Network. Make sure you have to configure
Wild card bits. Mention correct Area
Verification:
London# Show ip ospf nei
Display the information of interfaces along with Area ID, IP address cost
and the state.
Number of LSA in the Area, Interfaces allowed in the area can be observed
by
Case Study:
Configure the Router R1 and R2 with IPv4 BGP Routing Protocol and
Verify the Neighbour Adjacency. BGP IPv4 Authentication should also be
enabled to authenticate the neighbour before forming adjacency.
Configuration:
R1
R1(config)#int fa 0/0
R1(config-if)#ip add 10.0.0.2 255.255.255.0
R1(config-if)#no sh
R1(config)#router bgp 65000
// Autonomous system must be defined and same as in the neighbour details of remote router
R1(config-router)#neighbor 10.0.0.1 remote-as 65001
// Remote Autonomous system Number is to be configured here. Donot configure the same
autonomous system for eBGP.
R1(config-router)#neighbor 10.0.0.1 password 0 ipspecialist
// Remember the password to configure on the remote Router. Make sure it is case sensitive
R1(config-router)#ex
R2
R2(config)#int fa 0/0
R2(config-if)#ip add 10.0.0.1 255.255.255.0
R2(config-if)#no sh
R2(config)#router bgp 65001
// Autonomous system must be defined and same as in the neighbour details of remote router
R2(config-router)#neighbor 10.0.0.2 remote-as 65000
// For eBGP, make sure the remote autonomous system number is configured
R2(config-router)#neighbor 10.0.0.2 password 0 ipspecialist
// Configure the correct password to be authenticated by the remote Router. Make sure it is case
sensitive
Topology:
Case Study
Configure the two routers with OSPFv3 Routing Protocol to connect with
each other. Verify the Neighbour adjacencies and Routing Table.
Configuration:
London
Router(config)#hostname London
London(config)#ipv6 unicast-routing
// Globally enable IPv6 Routing
London(config)#int eth 0/0
London(config-if)#ipv6 enable
// Enable IPv6 on an interface.
London(config-if)#ipv6 add 2001::1/64
// IPv6 address for an Interface OSPF will use all the prefix if more than one prefix is configured on
interface
London(config-if)#ipv6 ospf 1 area 0
// Enable IPv6 OSPF on an interface. For OSPFv3, it must be configured on an interface
London(config-if)#no sh
London(config-if)#ipv6 router ospf 1
London(config-rtr)#router-id 1.1.1.1
//Unique Router ID must be configured
London(config-rtr)#ex
London(config)#int lo 0
Router(config)#hostname Border-65001
Border-65001(config)#int eth 0/0
Border-65001(config-if)#ip add 10.0.0.2 255.255.255.252
Border-65001(config-if)#no sh
// In case of down interface, Or down line protocol, Adjacency will not formed
Border-65001(config-if)#ex
Case Study:
Configure the Router R1 and R2 with IPv4 BGP Routing Protocol and
Verify the Neighbour Adjacency. BGP IPv4 Authentication should also be
enabled to authenticate the neighbour before forming adjacency.
Configuration:
R1
R1(config)#int fa 0/0
R1(config-if)#ip add 10.0.0.2 255.255.255.0
R1(config-if)#no sh
R1(config)#router bgp 65000
// Autonomous system must be defined and same as in the neighbour details of remote router
R1(config-router)#neighbor 10.0.0.1 remote-as 65001
// Remote Autonomous system Number is to be configured here. Donot configure the same
autonomous system for eBGP.
R1(config-router)#neighbor 10.0.0.1 password 0 ipspecialist
// Remember the password to configure on the remote Router. Make sure it is case sensitive
R1(config-router)#ex
R2
R2(config)#int fa 0/0
R2(config-if)#ip add 10.0.0.1 255.255.255.0
R2(config-if)#no sh
R2(config)#router bgp 65001
// Autonomous system must be defined and same as in the neighbour details of remote router
R2(config-router)#neighbor 10.0.0.2 remote-as 65000
// For eBGP, make sure the remote autonomous system number is configured
R2(config-router)#neighbor 10.0.0.2 password 0 ipspecialist
// Configure the correct password to be authenticated by the remote Router. Make sure it is case
sensitive
Case Study:
Internal And External BGP are configure in this Lab with Autonomous
System Number 65000 and 65001. External BGP link connected these
routers. Internal Netowrk is operating on Internal BGPs.
Topology Diagram:
Configuration:
Border Router of Autonomous System 65000:
Router(config)#hostname Border-65000
Border-65000(config)#int eth 0/0
Border-65000(config-if)#ip add 10.0.0.1 255.255.255.252
Border-65000(config-if)#no sh
// In case of down interface, Or down line protocol, Adjacency will not formed
Border-65000(config-if)#ex
Border-65000(config)#
*May 18 06:29:36.524: %LINK-3-UPDOWN: Interface Ethernet0/0, changed state to up
*May 18 06:29:37.529: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0/0,
changed state to up
Border-65000(config)#int eth 0/1
Border-65000(config-if)#ip add 172.17.0.1 255.255.0.0
Border-65000(config-if)#no sh
The Border Router shows that the IPS peer group is set be in passive
transport connection mode. Which means that IPS peer group members can
not initiate the session. Now, if the other end is configured with Active state
then it will be fine. In case if the other end is configured with Passive, no
one will initiate the session.
Tunnel mode
Make sure the tunnel mode is GRE/IP by show int tunnel [tunnel no]
command
Routing Protocol
Tunnel Network is to be advertised in any Dynamic Routing protocol.
Configuration
Router 1:
Router(config)#hostname R1
R1(config)#int eth 0/1
R1(config-if)#ip add 172.16.0.1 255.255.0.0
R1(config-if)#no sh
*Jul 31 00:32:36.418: %LINK-3-UPDOWN: Interface Ethernet0/1, changed state to up
*Jul 31 00:32:37.422: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0/1, changed
state to up
R1(config)#router rip
R1(config-router)#net 172.16.0.0
R1(config-router)#net 10.0.0.0
R1(config-router)#no auto-summary
R1(config-router)#ex
Cloud:
Router(config)#int fa 0/0
Router(config-if)#ip add 10.0.0.2 255.0.0.0
Router(config-if)#no sh
*Mar 1 00:06:44.131: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state to up
*Mar 1 00:06:45.131: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0,
changed state to up
Router(config)#int fa 0/1
Router(config-if)#ip add 11.0.0.02 255.0.0.0
Router(config-if)#no sh
*Mar 1 00:07:04.011: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to up
*Mar 1 00:07:05.011: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/1,
changed state to upnet
Router(config)#router rip
Router(config-router)#net 10.0.0.0
Router(config-router)#net 11.0.0.0
Router(config-router)#no auto-summary
Router(config-router)#ex
Router 2:
Router(config)#hostname R2
R2(config)#int eth 0/0
R2(config-if)#ip add 11.0.0.1 255.0.0.0
R2(config-if)#no sh
*Jul 31 00:38:32.945: %LINK-3-UPDOWN: Interface Ethernet0/0, changed state to up
*Jul 31 00:38:33.946: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0/0, changed
state to up
In this figure, the output shows that 172.17.0.2 neighbour state is idle. In
order to troubleshoot the fault, let us check the running configuration of
Tunnel mode
Make sure the tunnel mode is GRE/IP by show int tunnel [tunnel no]
command
Routing Protocol
Tunnel Network is to be advertised in any Dynamic Routing protocol.
IPS_Router(config)#service password-encryption
// Enable all password encryption
IPS_Router(config)#ip domain name specialist.net
IPS_Router(config)#crypto key generate rsa modulus 1024
The name for the keys will be: IPS_Router.specialist.net
% The key modulus size is 1024 bits
% Generating 1024 bit RSA keys, keys will be non-exportable...
[OK] (elapsed time was 1 seconds)
IPS_Router(config)#line console 0
IPS_Router(config-line)#login authentication default
// enable aaa default setting on line console 0. Default setting includes Console vty and Aux line to be
authenticated.
IPS_Router(config-line)#end
IPS_Router(config)#line vty 0 4
IPS_Router(config-line)#login authentication default
// enable aaa local authentication on vty lines
IPS_Router(config-line)#transport input ssh
// By default telnet is enabled. This command overwrite the configuration and SSH will be allowed
on vty line only.
IPS_Router(config-line)#ex
IPS_Router(config)#line aux 0
IPS_Router(config-line)#login authentication default
// enable aaa local authentication on Aux line
IPS_Router(config-line)#end
Cloud:
Router(config)#int fa 0/0
Router(config-if)#ip add 10.0.0.2 255.0.0.0
Router(config-if)#no sh
*Mar 1 00:06:44.131: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state to up
*Mar 1 00:06:45.131: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0,
changed state to up
Router(config)#int fa 0/1
Router(config-if)#ip add 11.0.0.02 255.0.0.0
Router(config-if)#no sh
*Mar 1 00:07:04.011: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to up
*Mar 1 00:07:05.011: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/1,
changed state to upnet
Router(config)#router rip
Router(config-router)#net 10.0.0.0
Router(config-router)#net 11.0.0.0
Router(config-router)#no auto-summary
Router(config-router)#ex
Router 2:
Router(config)#hostname R2
R2(config)#int eth 0/0
R2(config-if)#ip add 11.0.0.1 255.0.0.0
R2(config-if)#no sh
*Jul 31 00:38:32.945: %LINK-3-UPDOWN: Interface Ethernet0/0, changed state to up
*Jul 31 00:38:33.946: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0/0, changed
state to up
IPS_Router(config)#service password-encryption
// Enable all password encryption
IPS_Router(config)#ip domain name specialist.net
IPS_Router(config)#crypto key generate rsa modulus 1024
The name for the keys will be: IPS_Router.specialist.net
% The key modulus size is 1024 bits
% Generating 1024 bit RSA keys, keys will be non-exportable...
[OK] (elapsed time was 1 seconds)
IPS_Router(config)#line console 0
IPS_Router(config-line)#login authentication default
// enable aaa default setting on line console 0. Default setting includes Console vty and Aux line to be
authenticated.
IPS_Router(config-line)#end
IPS_Router(config)#line vty 0 4
IPS_Router(config-line)#login authentication default
// enable aaa local authentication on vty lines
IPS_Router(config-line)#transport input ssh
// By default telnet is enabled. This command overwrite the configuration and SSH will be allowed
on vty line only.
IPS_Router(config-line)#ex
IPS_Router(config)#line aux 0
IPS_Router(config-line)#login authentication default
// enable aaa local authentication on Aux line
IPS_Router(config-line)#end
Configuration:
IPS#clock set 10:20:00 22 apr 2017
Apr 22 10:20:00.000: %SYS-6-CLOCKUPDATE: System clock has been updated from 10:21:48
UTC Fri Apr 21 2017 to 10:20:00 UTC Sat Apr 22 2017, configured from console by IPspecialist on
console.
IPS#show clock
IPS(config)#time-range Halfday
IPS(config-time-range)#periodic ?
Friday Friday
Monday Monday
Saturday Saturday
Sunday Sunday
Thursday Thursday
Tuesday Tuesday
Wednesday Wednesday
Daily Every day of the week
weekdays Monday thru Friday
Troubleshooting
R1#show access-list
Shows the access list configured on a router. Access list 100 is available
which is denying the host IP address 10.0.0.10 to the host 10.0.0.1 with the
time-range Halfday.
IPS#show clock
Configuration:
IPS#clock set 10:20:00 22 apr 2017
Apr 22 10:20:00.000: %SYS-6-CLOCKUPDATE: System clock has been updated from 10:21:48
UTC Fri Apr 21 2017 to 10:20:00 UTC Sat Apr 22 2017, configured from console by IPspecialist on
console.
IPS#show clock
IPS(config)#time-range Halfday
IPS(config-time-range)#periodic ?
Friday Friday
Monday Monday
Saturday Saturday
Sunday Sunday
Thursday Thursday
Tuesday Tuesday
Wednesday Wednesday
Daily Every day of the week
weekdays Monday thru Friday
Troubleshooting
R1#show access-list
Shows the access list configured on a router. Access list 100 is available
which is denying the host IP address 10.0.0.10 to the host 10.0.0.1 with the
time-range Halfday.
Verification:
R1# show ipv6 access-list
This command shows the access list and the expressions of the access-list
configured on the router.
The output shows that R2 has learned about the Loopback addresses
configured on the Router 1 via OSPFv3. Let’s try to ping the Loopback
interfaces for connectivity.
Successful ping shows the access to the network 1000::1 passes the traffic
filter. Now check the connectivity to the other loopback interface
R2# Ping 1001::1
R1 Configuration:
R1(config)#int eth 0/0
R1(config-if)#ip add 10.0.0.1 255.255.255.0
//Assign the correct IP address and Subnet Masking
R1(config-if)#no sh
//Remember to turn interface up
*May 19 09:49:42.485: %LINK-3-UPDOWN: Interface Ethernet0/0, changed state to up
*May 19 09:49:43.485: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0/0,
changed state to up
R1(config)#int lo 0
*May 19 09:49:50.623: %LINEPROTO-5-UPDOWN: Line protocol on Interface Loopback0,
changed state to up
R1(config-if)#ip add 192.168.0.1 255.255.255.0
//Assign the correct IP address and Subnet Masking
R1(config)#router rip
R1(config-router)#net 10.0.0.0
R2 Configuration:
R2(config)#int eth 0/0
R2(config-if)#ip add 10.0.0.2 255.255.255.0
//Assign the correct IP address and Subnet Masking
R2(config-if)#no sh
//Remember to turn interface up
*May 19 09:51:16.467: %LINK-3-UPDOWN: Interface Ethernet0/0, changed state to up
*May 19 09:51:17.468: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0/0,
changed state to up
R2(config)#router rip
R2(config-router)#net 10.0.0.0
R2(config-router)#net 11.0.0.0
R2(config-router)#no aut0-summary
R3 Configuration:
R3(config)#int eth 0/1
R3(config-if)#ip add 11.0.0.2 255.255.255.0
R3(config)#int lo 0
*May 19 09:54:48.073: %LINEPROTO-5-UPDOWN: Line protocol on Interface Loopback0,
changed state to up
R3(config-if)#ip add 192.168.0.1 255.255.255.0
R3(config)#router rip
R3(config-router)#net 11.0.0.0
R3(config-router)#net 192.168.0.0
R3(config-router)#no aut0-summary
The output shows that R2 has learned about the Loopback addresses
configured on the Router 1 via OSPFv3. Let’s try to ping the Loopback
interfaces for connectivity.
Successful ping shows the access to the network 1000::1 passes the traffic
filter. Now check the connectivity to the other loopback interface
R2# Ping 1001::1
As shown in the output, 10.0.0.1 route is not dropped, successful ping from
R2 Configuration:
R2(config)#int eth 0/0
R2(config-if)#ip add 10.0.0.2 255.255.255.0
//Assign the correct IP address and Subnet Masking
R2(config-if)#no sh
//Remember to turn interface up
*May 19 09:51:16.467: %LINK-3-UPDOWN: Interface Ethernet0/0, changed state to up
*May 19 09:51:17.468: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0/0,
changed state to up
R2(config)#router rip
R2(config-router)#net 10.0.0.0
R2(config-router)#net 11.0.0.0
R2(config-router)#no aut0-summary
R3 Configuration:
R3(config)#int eth 0/1
R3(config-if)#ip add 11.0.0.2 255.255.255.0
Topology:
Configuration:
NTP-Client(config)#int eth 0/1
NTP-Client(config-if)#ip add 10.0.0.1 255.255.255.0
NTP-Client(config-if)#no sh
*Mar 1 00:19:43.803: Configuring snmpv3 USM user, persisting snmpEngineBoots. Please Wait...
NTP-Client(config)#logging 10.0.0.10
NTP-Server
NTP-Server#clock set 03:52:00 apr 24 2017
*Apr 24 03:52:00.000: %SYS-6-CLOCKUPDATE: System clock has been updated from 00:22:26
UTC Fri Mar 1 2002 to 03:52:00 UTC Mon Apr 24 2017, configured from console by console.
NTP-Server#show clock
03:52:05.919 UTC Mon Apr 24 2017
SNMP verification:
Topology:
Configuration:
NTP-Client(config)#int eth 0/1
NTP-Client(config-if)#ip add 10.0.0.1 255.255.255.0
NTP-Client(config-if)#no sh
Syslog Verification:
Open source 3CDaemon server used in this lab contains Syslog server along
with FTP and other servers. Click on 3CD icon on start menu to start it and
view its operations. As OP Manager is also installed on same management
station. We may need to stop manage engine service before starting syslog
server.
To stop manage engine service, type services.msc in start menu and stop the
Manage Engine OPManager service.
Any scp supported software can be used from workstation to access any
location within cisco IOS.
NTP Verification
NTP-Client>en
NTP-Client#config t
Enter configuration commands, one per line. End with CNTL/Z.
NTP-Client(config)#ntp update-calendar
NTP-Client(config)#end
May 12 06:16:56.468: %SYS-5-CONFIG_I: Configured from console by
console
Configuration
Router(config)#Hostname NTPv4Server
NTPv4Server(config)#int eth 0/0
NTPv4Server(config-if)#no ip add
NTPv4Server(config-if)#ipv6 enable
//Enable IPv6 on an interface
NTPv4Server(config-if)#ipv6 add 2001::1/64
//Assign IP address on an Interface
NTPv4Server(config-if)#no sh
// Must turn up the interface
NTPv4Server(config-if)#ex
*May 22 11:50:09.973: %LINK-3-UPDOWN: Interface Ethernet0/0, changed state to up
*May 22 11:50:10.978: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0/0,
changed state to up
//Interface and Interface Line Protocol, Both are up
NTPv4Server(config)#ntp master 1
// Set the Router as Authoritative NTP server
NTPv4Server(config)#ntp server 2001::1 version 4
Set NTP Version Number
Router(config)#hostname NTPv4Client
NTPv4Client(config)#int eth 0/0
NTPv4Client(config-if)#no ip add
NTPv4Client(config-if)#ipv6 enable
//Enable IPv6 on an interface
NTPv4Client(config-if)#ipv6 add 2001::2/64
//Assign IP address on an Interface
NTPv4Client(config-if)#no sh
// Must turn up the interface
NTPv4Client(config-if)#ex
Troubleshooting
NTPv4Server#show ntp status
Stratum value 1 and Reference Local shows that this is the NTP master.
Reference clock is its local Clock.
NTP association command shows the NTP server address and its details
Any scp supported software can be used from workstation to access any
location within cisco IOS.
NTP Verification
NTP-Client>en
NTP-Client#config t
Enter configuration commands, one per line. End with CNTL/Z.
NTP-Client(config)#ntp update-calendar
NTP-Client(config)#end
May 12 06:16:56.468: %SYS-5-CONFIG_I: Configured from console by
console
Configuration
Router(config)#Hostname NTPv4Server
NTPv4Server(config)#int eth 0/0
NTPv4Server(config-if)#no ip add
NTPv4Server(config-if)#ipv6 enable
//Enable IPv6 on an interface
NTPv4Server(config-if)#ipv6 add 2001::1/64
//Assign IP address on an Interface
NTPv4Server(config-if)#no sh
// Must turn up the interface
NTPv4Server(config-if)#ex
*May 22 11:50:09.973: %LINK-3-UPDOWN: Interface Ethernet0/0, changed state to up
*May 22 11:50:10.978: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0/0,
changed state to up
//Interface and Interface Line Protocol, Both are up
NTPv4Server(config)#ntp master 1
// Set the Router as Authoritative NTP server
NTPv4Server(config)#ntp server 2001::1 version 4
Set NTP Version Number
Router(config)#hostname NTPv4Client
NTPv4Client(config)#int eth 0/0
NTPv4Client(config-if)#no ip add
NTPv4Client(config-if)#ipv6 enable
//Enable IPv6 on an interface
NTPv4Client(config-if)#ipv6 add 2001::2/64
//Assign IP address on an Interface
NTPv4Client(config-if)#no sh
// Must turn up the interface
NTPv4Client(config-if)#ex
Troubleshooting
NTPv4Server#show ntp status
Stratum value 1 and Reference Local shows that this is the NTP master.
Reference clock is its local Clock.
Router#debug ip nat
Debug ip nat shows run time debugging data of Nat translation. As shows
source address is 10.0.10 input interface is Ethernet 0/0 is translated.
Topology Diagram:
Case Study:
In this Case, Static (One to One mapping) is performed in the shown network
topology. The Source IP address 10.0.0.10 is translated into 192.168.0.1 IP
address.
Configuration:
Router(config)#int eth 0/0
Router(config-if)#ip add 10.0.0.1 255.0.0.0
//Configure correct IP address and Mask
Router(config-if)#no sh
//Must Turn Up the interface
Router(config-if)#ex
*May 23 05:32:38.546: %LINK-3-UPDOWN: Interface Ethernet0/0, changed state to up
//Interface is Up successfully
*May 23 05:32:39.550: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0/0,
changed state to up
//Interface Line Protocol is Up successfully
Troubleshooting
Ping from PC 1 to Lo interface 13.0.0.1
Router#debug IP nat
Assigned Address translations are expired, moving back to pool IPS for
Troubleshooting
Ping from PC 1 to Lo interface 13.0.0.1
Case Study:
In this Lab, we are troubleshooting the process of Port Address Translation in
which number of IP address of an internal network i.e. 10.0.0.0/8 will be
translated By PAT (Port Address Translation) into 1.0.0.0 network along with
Port numbers.
Router 1:
Router(config)#hostname R1
R1(config)#int eth 0/1
R1(config-if)#ip add 10.0.0.1 255.0.0.0
//Assign Correct IP address and Subnet Mask
R1(config-if)#no sh
// Must Turn up the interface
R1(config-if)#ex
*Mar 1 00:00:47.987: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state to up
*Mar 1 00:00:48.987: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0,
changed state to up
//Interface and Interface Line Protocol, Both are up
R1(config)#int eth 0/0
R1(config-if)#ip add 192.168.1.1 255.255.255.0
//Assign Correct IP address and Subnet Mask
R1(config-if)#no sh
Troubleshooting:
Ping from PC 1 to Lo interface 13.0.0.1
Router#debug ip nat
Reserved Translation timeout, Address are assigned back in pool for reuse
Router#debug ip nat
Reserved Translation timeout, Address are assigned back in pool for reuse
R1(config)#ip sla 1
R1(config-ip-sla)#?
R1#show track 1
R1#Ping 172.16.0.10
R1#traceroute 172.16.0.10
Router(config)#hostname R2
R2(config)#int eth 0/0
R2(config-if)#ip add 10.0.0.2 255.0.0.0
//Assign Correct IP address and Subnet Mask
R2(config-if)#no sh
//Must Turn up the interface
R2(config-if)#ex
*May 23 09:30:28.899: %LINK-3-UPDOWN: Interface Ethernet0/0, changed state to up
//Interface is Up
*May 23 09:30:29.904: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0/0,
changed state to up
//Interface Line Porotocol is Up
R2(config)#int eth 0/1
R2(config-if)#ip add 11.0.0.2 255.0.0.0
//Assign Correct IP address and Subnet Mask
R2(config-if)#no sh
//Must Turn up the interface
R2(config-if)#ex