Dumbass Section : Serial1/0:encaps failed on broadcast for link 38(BRIDGE)

#Topology#

#Symptom#
no ip traffic from 172.16.13.3 <-> 172.16.13.1
debug frame-relay packet on R3 gives following output

*Mar  1 15:32:12.917: Serial1/0: broadcast search
*Mar  1 15:32:12.917: Serial1/0:encaps failed on broadcast for link 38(BRIDGE)

#Resolution#
Ip routing was disabled from a previous configuration. It seems that IOS needs IP Routing enabled for encapsulation of IP packets on Frame Relay Links
Activate IP Routing on R3

R3#debug frame-relay packet
Frame Relay packet debugging is on
R3#ping 172.16.13.1 rep
R3#ping 172.16.13.1 repeat 1

Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 172.16.13.1, timeout is 2 seconds:

*Mar  1 15:51:01.479: Serial1/0: broadcast search
*Mar  1 15:51:01.483: Serial1/0:encaps failed on broadcast for link 38(BRIDGE)
*Mar  1 15:51:01.483: Serial1/0: broadcast search
*Mar  1 15:51:01.483: Serial1/0:encaps failed on broadcast for link 38(BRIDGE)
*Mar  1 15:51:02.485: Serial1/0: broadcast search
*Mar  1 15:51:02.485: Serial1/0:encaps failed on broadcast for link 38(BRIDGE)
*Mar  1 15:51:02.485: Serial1/0: broadcast search
*Mar  1 15:51:02.485: Serial1/0:encaps failed on broadcast for link 38(BRIDGE).
Success rate is 0 percent (0/1)
R3#
*Mar  1 15:51:03.486: Serial1/0: broadcast search
*Mar  1 15:51:03.486: Serial1/0:encaps failed on broadcast for link 38(BRIDGE)
*Mar  1 15:51:03.486: Serial1/0: broadcast search
*Mar  1 15:51:03.486: Serial1/0:encaps failed on broadcast for link 38(BRIDGE)
*Mar  1 15:51:04.488: Serial1/0: broadcast search
*Mar  1 15:51:04.488: Serial1/0:encaps failed on broadcast for link 38(BRIDGE)
*Mar  1 15:51:04.488: Serial1/0: broadcast search
*Mar  1 15:51:04.488: Serial1/0:encaps failed on broadcast for link 38(BRIDGE)
R3#
R3#sh ip route
Default gateway is not set

Host               Gateway           Last Use    Total Uses  Interface
ICMP redirect cache is empty
R3#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
R3(config)#ip routing
R3(config)#exit
R3#sh ip route
*Mar  1 15:51:14.557: %SYS-5-CONFIG_I: Configured from console by console
R3#ping 172.16.13.1 repeat 1

Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 172.16.13.1, timeout is 2 seconds:
!
Success rate is 100 percent (1/1), round-trip min/avg/max = 60/60/60 ms
R3#
*Mar  1 15:51:17.393: Serial1/0(o): dlci 301(0x48D1), pkt type 0x800(IP), datagramsize 104
*Mar  1 15:51:17.449: Serial1/0(i): dlci 301(0x48D1), pkt type 0x800, datagramsize 104
R3#

Cisco 360 CIERS1 - Review

This week i had the pleasure to take the CIERS1 course.
On the first day, i've done my first CCIE-like lab ever. The CIERS1-CA-LAB01.
My Score was 71/100 (Cisco states an average score on all attendants of 53/100)
So i think this was quite good for the first time.
Day 2-4 we had some lectures and smaller technology focussed labs (BGP,QoS,Multicast etc.)
But on the fifth day i made a momentous mistake, i didn't take the CIERS-CA-LAB02 guide to to the tasks. I  used the CIERS-CA-LAB01-guide. So i wasted 3,5 hours on doing CIERS-CA-LAB01 on a preconfigured network for the CIERS-CA-LAB02. I wondered about the wrong configured IPs, but didn't thought about it too long. I was just hunting for full IGP reachability. After 3 hours i had full IGP reachability and realized that i used the wrong lab guide. This made my day. I was so frustrated, that i didn't had passion to really start again.
I was very angry about myself. I did a write-erase-reload on every device and started again. But now with CIERS1-CA-LAB02-guide. My motivation was below -39843 and i only got 14 out of 75 point. I'm really pissed. I mean really really pissed.

So remind -> ALWAYS READ THE ENTIRE LAB BEFORE YOU START !!!!!!
 ALWAYS!!!!!!!!

The course consisted of 30 % lecture and 70 % labs.
- 1. Day - Assesment Lab (Frame Relay, Catalyst Configuration, IGP (OSPF,EIGRP,RIP), Reistribution,BGP)
- 2. Day - Review Assesment Lab and Technologys, Advanced BGP Lab (a bad next-hop issue)
- 3. Day - Review BGP, Review MPLS, Review Multicast, Multicast Lab
- 4. Day - Review QoS, QoS Lab, Troubleshooting Lab (CIERS-TA-LAB02 - 2 hours)
- 5. Day - Configuration Lab (CIERS-CA-LAB02 - 6 hours), Review Lab

My recommodations before go for the course :
- Master the Frame Relay-thing. I think younger network engineers (like me) don't understand Frame Relay at all, because they never ever used it. Frame-Relay is contained in every lab, i think. I will have to study on this section, especially the different ways of running OSPF over Frame Relay
- do a lot of small technology based-labs (master IGP) before you attend the course
- don't go there just after the written exam, the written exam is a piece of shit. Further study in every topic is necessary to get most out of CIERS1 (after this week, i have to admit that it was to early to attend this course)

Notes-Section : In OSPF, Loopbacks are always advertised as /32 except...

#Topology#

#Note#
In OSPF, Loopbacks are advertised as /32 as described in RFC2328 Section 9.1.
It is seemed as a stub host, because over a loopback, there will be no transit-traffic.

You can change this behavior with the ip ospf network point-to-point command on the Loopback-Interface. Have a look ->

#Config#
#Rack1R1#

Rack1R1#sh run int lo0
Building configuration...

Current configuration : 95 bytes
!
interface Loopback0
 ip address 150.1.1.1 255.255.255.0
 ip ospf network point-to-point
end

Rack1R1#
Rack1R1#sh ip ospf interface lo0
Loopback0 is up, line protocol is up 
  Internet Address 150.1.1.1/24, Area 0 
  Process ID 1, Router ID 150.1.1.1, Network Type POINT_TO_POINT, Cost: 1
  Transmit Delay is 1 sec, State POINT_TO_POINT,
  Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
    oob-resync timeout 40
  Supports Link-local Signaling (LLS)
  Index 1/1, flood queue length 0
  Next 0x0(0)/0x0(0)
  Last flood scan length is 0, maximum is 0
  Last flood scan time is 0 msec, maximum is 0 msec
  Neighbor Count is 0, Adjacent neighbor count is 0 
  Suppress hello for 0 neighbor(s)
Rack1R1#
Rack1R1#sh ip route 150.1.1.1
Routing entry for 150.1.1.0/24
  Known via "connected", distance 0, metric 0 (connected, via interface)
  Routing Descriptor Blocks:
  * directly connected, via Loopback0
      Route metric is 0, traffic share count is 1

Rack1R1#
Rack1R1#sh ip route 150.1.3.3
Routing entry for 150.1.3.3/32
  Known via "ospf 1", distance 110, metric 66, type intra area
  Last update from 164.1.13.3 on Serial0/1, 02:15:50 ago
  Routing Descriptor Blocks:
  * 164.1.13.3, from 150.1.3.3, 02:15:50 ago, via Serial0/1
      Route metric is 66, traffic share count is 1

Rack1R1#

#Rack1R3#

Rack1R3#sh run int lo0
Building configuration...

Current configuration : 63 bytes
!
interface Loopback0
 ip address 150.1.3.3 255.255.255.0
end

Rack1R3#
Rack1R3#sh ip ospf interface lo0
Loopback0 is up, line protocol is up 
  Internet Address 150.1.3.3/24, Area 0 
  Process ID 1, Router ID 150.1.3.3, Network Type LOOPBACK, Cost: 1
  Loopback interface is treated as a stub Host
Rack1R3#
Rack1R3#sh ip route 150.1.1.1
Routing entry for 150.1.1.0/24
  Known via "ospf 1", distance 110, metric 782, type intra area
  Last update from 164.1.13.1 on Serial1/2, 02:17:59 ago
  Routing Descriptor Blocks:
  * 164.1.13.1, from 150.1.1.1, 02:17:59 ago, via Serial1/2
      Route metric is 782, traffic share count is 1

Rack1R3#sh ip route 150.1.3.3
Routing entry for 150.1.3.0/24
  Known via "connected", distance 0, metric 0 (connected, via interface)
  Routing Descriptor Blocks:
  * directly connected, via Loopback0
      Route metric is 0, traffic share count is 1

Rack1R3#