Pertemuan 5 Troubleshooting Routing Protocols

1
Pertemuan 5 Troubleshooting Routing Protocols
2
Discussion Topics

• Routing protocol troubleshooting process
• Troubleshooting RIP configuration
• Troubleshooting IGRP configuration
• Troubleshooting EIGRP configuration
• Troubleshooting OSPF configuration

3
Troubleshooting Process

1. Analyze the network failure, make a clear problem
   statement.
2. Gather the facts needed to help isolate possible
   causes.
3. Consider possible problems based on the facts
   that have been gathered.
4. Create an action plan based on the remaining
   potential problems.
5. Implement the action plan, performing each step
   carefully while testing to see whether the
   symptom disappears.
6. Analyze the results to determine whether the
   problem has been resolved. If it has, the process
   is complete.
7. If the problem has not been resolved, create an
   action plan based on the next most likely problem
   in the list. Return to Step 4, change one
   variable at a time, and repeat the process until
   the problem is solved.
8. Once the actual cause of the problem is
   identified, try to solve it.

4
Use show Commands and TCP/IP Tools
5
Troubleshooting RIP Configuration

• Layer 1 or Layer 2 connectivity issues exist.
• VLSM subnetting is configured. VLSM subnetting
  cannot be used with RIPv1
• Mismatched RIPv1 and RIPv2 routing configurations
  exist.
• Network statements are missing or incorrectly
  assigned.
• The outgoing interface is down.
• The advertised network interface is down.

6
Troubleshooting IGRP Configuration
7
Troubleshooting EIGRP Configuration
8
Troubleshooting EIGRP Configuration
9
Troubleshooting OSPF Configuration
10
Examining the values

• R1show interface s 0/0
• R1show inter s 0/0
• Serial0/0 is up, line protocol is up
• Hardware is PowerQUICC Serial
• Internet address is 172.16.3.1/30
• MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,
• reliability 255/255, txload 1/255, rxload
  1/255
• Encapsulation HDLC, loopback not set
• lttext omittedgt

• The bandwidth (BW) metric is a static value used
  by some routing protocols such as EIGRP and OSPF
  to calculate their routing metric.
• The value of the bandwidth may or may not reflect
  the actual physical bandwidth of the interface.
• Modifying the bandwidth does not change the
  actual bandwidth of the link.

11
Examining the values

• R1show interface s 0/0
• R1show inter s 0/0
• Serial0/0 is up, line protocol is up
• Hardware is PowerQUICC Serial
• Internet address is 172.16.3.1/30
• MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,
• reliability 255/255, txload 1/255, rxload
  1/255
• Encapsulation HDLC, loopback not set
• lttext omittedgt

• Delay is a measure of the time it takes for a
  packet to traverse a route.
• The delay (DLY) metric is a static value based on
  type of link that the interface is connected to
  and is expressed in microseconds.

12
Examining the values

• R1show interface s 0/0
• R1show inter s 0/0
• Serial0/0 is up, line protocol is up
• Hardware is PowerQUICC Serial
• Internet address is 172.16.3.1/30
• MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,
• reliability 255/255, txload 1/255, rxload
  1/255
• Encapsulation HDLC, loopback not set
• lttext omittedgt

• Reliability (reliability) is a measure of the
  probability that the link will fail or how often
  the link has experienced errors.
• Reliability is measured dynamically with a value
  between 0 and 255 with 1 being a minimally
  reliable link and 255 a 100 percent reliable.
• Reliability uses error rate for its measurement
  and is calculated on a five minute weighted
  average, so not to allow sudden peaks and valleys
  to make a significant impact.
• Reliability is displayed as a fraction of 255.
• Higher the value, the more reliable the link.
• So, 255/255 would be 100 reliable, whereas a
  link of 234/255 would be 91.8 reliable.

13
Examining the values

• R1show interface s 0/0
• R1show inter s 0/0
• Serial0/0 is up, line protocol is up
• Hardware is PowerQUICC Serial
• Internet address is 172.16.3.1/30
• MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,
• reliability 255/255, txload 1/255, rxload
  1/255
• Encapsulation HDLC, loopback not set
• lttext omittedgt

• Load (load) reflects the amount of traffic
  utilizing the link. Load is a dynamic value
  between 0 and 255.
• Load uses channel occupancy for measurement and
  like reliability is calculated on a five minute
  weighted average, so not to allow sudden peaks
  and valleys to make a significant impact.
• Channel occupancy is just a parameter used for
  determining how much of the link is being used.

14
Examining the values

• R1show interface s 0/0
• R1show inter s 0/0
• Serial0/0 is up, line protocol is up
• Hardware is PowerQUICC Serial
• Internet address is 172.16.3.1/30
• MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,
• reliability 255/255, txload 1/255, rxload
  1/255
• Encapsulation HDLC, loopback not set
• lttext omittedgt

• Similar to reliability, load is expressed as a
  fraction of 255. However, a lower load value is
  more desirable.
• Load is displayed as both an outbound or transmit
  load value (txload), and an inbound or receive
  load value (rxload).\
• Load is expressed as a fraction of 255.
• Lower the value, the lesser the load on the link.
  
• So, 1/255 would be a minimally loaded link.
• 40/255 is a link at 16 percent capacity, and
  255/255 would be a link that is 100 percent
  saturated.