Master of Engineering in

Internetworking








TROUBLESHOOTING LAB

INWK 6113









GROUP NUMBER:


GROUP MEMBERS:
1
Issues resolved in part 1
1) In router 2 dlci 201 is mapped instead of 301.
2) In Router 4 the ip address was no broadcasted.
3) In router 3 Static mapping was not done.
Configurations of routers after making amendments.
It contains Show frame map and details of serial interfaces of router1,2,3 and 4.
8R1#show frame map
Serial0/0/0 (up): ip 28.8.134.3 dlci 103(0x67,0x1870), static,
broadcast,
CISCO, status defined, active
Serial0/0/0 (up): ip 28.8.134.4 dlci 104(0x68,0x1880), static,
broadcast,
CISCO, status defined, active
8R3(config)#do show frame map
Serial0/0/0 (up): ip 28.8.134.4 dlci 301(0x12D,0x48D0), static,
broadcast,
CISCO, status defined, active
Serial0/0/0 (up): ip 28.8.134.1 dlci 301(0x12D,0x48D0), static,
broadcast,
CISCO, status defined, active

8R4#show frame map
Serial0/0/0 (up): ip 28.8.134.1 dlci 401(0x191,0x6410), static,
broadcast,
CISCO, status defined, active
Serial0/0/0 (up): ip 28.8.134.3 dlci 401(0x191,0x6410), static,
broadcast,
CISCO, status defined, active

Show run Router 1

interface Serial0/0/0
ip address 28.8.134.1 255.255.255.0
encapsulation frame-relay
frame-relay map ip 28.8.134.3 103 broadcast
frame-relay map ip 28.8.134.4 104 broadcast
no frame-relay inverse-arp
Show run router 2
interface Serial0/0/0
no ip address
encapsulation frame-relay
clock rate 2000000
frame-relay intf-type dce
no frame-relay route 102 interface Serial0/1/0 201
frame-relay route 103 interface Serial0/0/1 301
2
frame-relay route 104 interface Serial0/1/0 401
!
interface Serial0/0/1
no ip address
encapsulation frame-relay
clock rate 2000000
frame-relay intf-type dce
frame-relay route 301 interface Serial0/0/0 103
!
interface Serial0/1/0
no ip address
encapsulation frame-relay
clock rate 2000000
frame-relay intf-type dce
frame-relay route 401 interface Serial0/0/0 104
Show run router 3
interface Serial0/0/0
ip address 28.8.134.3 255.255.255.248
encapsulation frame-relay
frame-relay map ip 28.8.134.4 301 broadcast
frame-relay map ip 28.8.134.1 301 broadcast
frame-relay interface-dlci 301
no frame-relay inverse-arp
frame-relay lmi-type cisco
show run router 4
interface Serial0/0/0
ip address 28.8.134.4 255.255.255.0
encapsulation frame-relay
no fair-queue
frame-relay map ip 28.8.134.1 401 broadcast
frame-relay map ip 28.8.134.3 401 broadcast
no frame-relay inverse-arp

ping router 4 to router 3
8R4#ping 28.8.134.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 28.8.134.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/4/8 ms
ping router 4 to router 1
8R4#ping 28.8.134.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 28.8.134.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
8R4#
3
Traceroute router 4 to router 3
8R4#traceroute 28.8.134.3
Type escape sequence to abort.
Tracing the route to 28.8.134.3
VRF info: (vrf in name/id, vrf out name/id)
1 28.8.134.1 4 msec 0 msec 0 msec
2 28.8.134.3 4 msec * 0 msec
.


PART 2:




We created Vlan 30 on switch 8S1 as it wasnt there in the switch

VLAN Name Status Ports
---- -------------------------------- --------- -------------------------------
1 default active Gi0/2, Gi0/5, Gi0/6, Gi0/7
Gi0/8, Gi0/9, Gi0/10, Gi0/11
Gi0/12, Gi0/13, Gi0/14, Gi0/15
Gi0/16, Gi0/20, Gi0/22, Gi0/24
10 VLAN0010 active Gi0/1
30 VLAN0030 active
40 VLAN0040 active Gi0/4
1002 fddi-default act/unsup
1003 token-ring-default act/unsup
1004 fddinet-default act/unsup
1005 trnet-default act/unsup

We Defined two static routes on 8R1 to 8R3 & 8R4
8R1#show run | i ip route
ip route 28.8.30.0 255.255.255.0 28.8.134.3
ip route 28.8.40.0 255.255.255.0 28.8.134.4
we Defined single static route on 8R3
8R3#show run | i ip route
ip route 28.8.0.0 255.255.192.0 28.8.134.1



we defined single static route on 8R4
8R4#show run | i ip route
ip route 28.8.0.0 255.255.192.0 28.8.134.1

8R1#ping 28.8.30.1
4
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 28.8.30.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
8R1#ping 28.8.134.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 28.8.134.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
8R1#ping 28.8.40.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 28.8.40.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
8R1#ping 28.8.134.4
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 28.8.134.4, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
8R1#ping 28.8.10.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 28.8.10.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms

PART 2:

1. Explain in brief how inverse-ARP works in a frame-relay network, and the advantages
and disadvantages when compared to static mapping. Note inverse-ARP is disabled in our
troubleshooting lab.

Inverse-Arp:
The static maps will map an IP address to a DLCI however, Inverse ARP does
it automatically. Inverse ARP will attempt to learn its neighboring devices
IP addresses and automatically create a dynamic map table.
Advantage:
Configuring Frame Relay Inverse ARP is actually quite simple. It is on by
default on all Frame Relay multipoint interfaces.
Disadvantage:
Problems arise from this feature such as routing loops or sub-optimal routing

2. There are two frame-relay encapsulation types and three LMI types, what are they and
whats the default settings? Do you need to match between the frame-relay switch and the
client site routers?

FR encapsulation:
5
Two frame relay encapsulation types are:
i) LMI
ii) IETF

IETF Frame Relay encapsulation- used to connect a Cisco router to a non-Cisco router

Three LMI types
i) Ansi
ii) Cisco
iii) Q.933A

Default type is LMI-type cisco. We need to match the frame relay encapsulation on frame relay
switch and client routers.

Frame Relay LMI needs to be matched between each couple of DTE-DCE devices (client FR
routers and FR Provider switch). The FR Switch device is responsible for managing and
maintaining status between the devices so need to understand the format the client DTE is using.

Consequently DTE router and DCE router with different LMI type will not be able to
communicate.

3. If xR3 sends broadcast traffic to the frame relay cloud, will it receive and reply from
xR4? Why or Why not?

FR WAN is a Non-Broadcast Multi-Access (NBMA), these networks allow for multi-access, but
have no broadcast ability like Ethernet

The hub will have to route between 2 DLCIs in order to pass traffic from one spoke to another.
This means that broadcast traffic will not be forwarded between the spokes.
xR4 will not receive and reply the broadcast traffic. (We are considering the hub and spoke
scenario).