Refining a lab scenario

[Tom4498]

This session builds on the design I setup in the last session.

R1
en
config t
int lo 0
ip address 172.16.1.1 255.255.255.255
no shut
exit
int e 0/0
ip address 10.1.10.1 255.255.255.0
no shut
exit
int s 0/0
ip address 192.168.1.1 255.255.255.0
encap frame-relay
no arp frame-relay
no frame-relay inverse-arp
frame-relay map ip 192.168.1.2 102 broadcast
frame-relay map ip 192.168.1.3 103 broadcast
frame-relay map ip 192.168.1.5 105 broadcast
no shut
exit
int s 0/1
ip address 172.31.1.1 255.255.255.252
bandwidth 128
no shut
end
wr mem

R2
en
config t
int lo 0
ip address 172.16.1.2 255.255.255.255
no shut
exit
int e 0/0
ip address 10.1.20.2 255.255.255.0
no shut
exit
int s 0/0
ip address 192.168.1.2 255.255.255.0
encap frame-relay
no arp frame-relay
no frame-relay inverse-arp
frame-relay map ip 192.168.1.1 201 broadcast
no shut
exit
int s 0/1
ip address 172.31.1.5 255.255.255.252
bandwidth 128
no shut
end
wr mem

R3 <-- The second ethernet is Fa 2/0, not Fa 2/1.
en
config t
int lo 0
ip address 172.16.1.3 255.255.255.255
no shut
exit
int e 0/0
ip address 10.1.31.3 255.255.255.0
no shut
exit
int fa 2/0
ip address 10.1.32.3 255.255.255.0
no shut
exit
int s 1/0
ip address 192.168.1.3 255.255.255.0
encap frame-relay
no arp frame-relay
no frame-relay inverse-arp
frame-relay map ip 192.168.1.1 301 broadcast
no shut
exit
int s 1/2
ip address 172.31.1.2 255.255.255.252
clock rate 128000
bandwidth 128
no shut
exit
int s 1/3
ip address 172.31.1.6 255.255.255.252
clock rate 128000
bandwidth 128
no shut
end
wr mem

R4
en
config t
int lo 0
ip address 172.16.1.4 255.255.255.255
no shut
exit
int e 0/0
ip address 10.1.41.4 255.255.255.0
no shut
exit
int e 0/1
ip address 10.1.42.4 255.255.255.0
no shut
exit
interface Serial0/0
encapsulation frame-relay
no ip address
no shut
exit
int s 0/0.46 point-to-point
ip address 192.168.46.1 255.255.255.252
frame-relay interface-dlci 406
no shut
exit
int s 0/1
ip address 172.31.1.9 255.255.255.252
bandwidth 128
no shut
end
wr mem

R5
en
config t
int lo 0
ip address 172.16.1.5 255.255.255.255
no shut
exit
int e 0/0
ip address 10.1.51.5 255.255.255.0
no shut
exit
int e 0/1
ip address 10.1.52.5 255.255.255.0
no shut
exit
interface Serial0/0
encapsulation frame-relay
no ip address
no shut
exit
int s 0/0.15 multipoint
ip address 192.168.1.5 255.255.255.0
no arp frame-relay
no frame-relay inverse-arp
frame-relay map ip 192.168.1.1 501 broadcast
exit
int s 0/0.56 point-to-point
ip address 192.168.56.1 255.255.255.252
frame-relay interface-dlci 506
no shut
exit
int s 0/1
ip address 172.31.1.10 255.255.255.252
clock rate 128000
bandwidth 128
no shut
end
wr mem

R6
en
config t
int lo 0
ip address 172.16.1.6 255.255.255.255
no shut
exit
int fa 4/0
ip address 10.1.61.6 255.255.255.0
no shut
exit
int fa 4/1
ip address 10.1.62.6 255.255.255.0
no shut
exit
int s 5/0
encapsulation frame-relay
no ip address
no shut
exit
int s 5/0.46 point-to-point
ip address 192.168.46.2 255.255.255.252
frame-relay interface-dlci 604
no shut
exit
int s 5/0.56 point-to-point
ip address 192.168.56.2 255.255.255.252
frame-relay interface-dlci 605
no shut
end
wr mem

BB3/R8
en
config t
int lo 0
ip address 172.16.1.8 255.255.255.255
no shut
exit
int e0
ip address 10.1.41.8 255.255.255.0
no shut
exit
int s1
ip address 172.31.1.14 255.255.255.252
clock rate 9600
bandwidth 9
no shut
end
wr mem

BB2/R9
en
config t
int lo 0
ip address 172.16.1.9 255.255.255.255
no shut
exit
int e 0
ip address 10.1.91.9 255.255.255.0
no shut
exit
int e 1
ip address 10.1.92.9 255.255.255.0
no shut
end
wr mem

BB1/R13
en
config t
int lo 0
ip address 172.16.1.13 255.255.255.255
no shut
exit
int e 0/0
ip address 10.1.41.13 255.255.255.0
no shut
int s 0/1
ip address 172.31.1.13 255.255.255.252
bandwidth 9
no shut
end
wr mem


SW1
en
config t
vlan 32
name VLAN_32
exit
vlan 41
name VLAN_41
exit
vlan 42
name VLAN_42
exit
vlan 52
name VLAN_52
exit
vlan 10
name VLAN_10
exit
vlan 20
name VLAN_20
exit
vlan 31
name VLAN_31
exit
vlan 41
name VLAN_41
exit
vlan 51
name VLAN_51
exit
vlan 61
name VLAN_61
exit
vlan 62
name VLAN_62
exit
vlan 91
name VLAN_91
exit
vlan 92
name VLAN_92
exit
vtp domain EXPERT_LABS
vtp pruning
int lo 0
ip address 172.16.1.11 255.255.255.255
no shut
exit
int fastEthernet 0/1
switchport mode access
switchport access vlan 10
no shut
exit
int fastEthernet 0/2
switchport mode access
switchport access vlan 20
no shut
exit
int fastEthernet 0/3
switchport mode access
switchport access vlan 31
no shut
exit
int fastEthernet 0/4
switchport mode access
switchport access vlan 41
no shut
exit
int fastEthernet 0/5
switchport mode access
switchport access vlan 51
no shut
exit
int fastEthernet 0/6
switchport mode access
switchport access vlan 61
no shut
exit
int fa 0/8
switchport mode access
switchport access vlan 41
exit
int range fastEthernet 0/13 - 15
switchport trunk encapsulation dot1q
switchport mode trunk
no shut
end
wr mem

SW2
en
config t
vtp domain EXPERT_LABS
vtp mode client
int lo 0
ip address 172.16.1.12 255.255.255.255
no shut
exit
int fastEthernet 0/3
switchport mode access
switchport access vlan 32
no shut
exit
int fastEthernet 0/4
switchport mode access
switchport access vlan 42
no shut
exit
int fastEthernet 0/5
switchport mode access
switchport access vlan 52
no shut
exit
int fastEthernet 0/6
switchport mode access
switchport access vlan 62
no shut
exit
int range fastEthernet 0/13 - 15
switchport trunk encapsulation dot1q
switchport mode trunk
no shut
exit
int fastEthernet 0/24
switchport mode access
switchport access vlan 41
no shut
end
wr mem

[Tom4498]

ATM isn't on the exam anymore, but I can pretend its another serial link.

R9/BB2
en
config t
int atm 0
ip address 172.31.1.18 255.255.255.252
no shut
no atm ilmi-keepalive
pvc 1/100
protocol ip 172.31.1.17
end
wr mem

R6
en
config t
int atm 0/0/0
ip address 172.31.1.17 255.255.255.252
no shut
no atm ilmi-keepalive
pvc 1/100
protocol ip 172.31.1.18
end
wr mem

The interfaces came up, but I can't ping across ATM. I will need to fiddle with this a little bit.

[Tom4498]

I decided to create a GRE tunnel between R4 and R5. The tunnel source and destination have to be either side of the link, ie s0/1 to s 0/1. The keepalive command tells the tunnel to go down, if it can't reach the other side. The interesting thing I found out was that if you used the same IP/Interface for source and destination, the tunnel will appear up.

R4
en
config t
int tu 45
ip address 10.1.45.1 255.255.255.252
keepalive 10 3
tunnel source Serial0/1
tunnel destination 172.31.1.10
end
wr mem

R5
en
config t
int tu 45
ip address 10.1.45.2 255.255.255.252
keepalive 10 3
tunnel source Serial0/1
tunnel destination 172.31.1.9
end
wr mem


There are issues with using Dynamic Routing protocols with Tunnels. I want to test how it works. I also wanted to play with RIPv1/2 and triggered updates.

R4
en
config t
router rip
no auto-summary
network 10.0.0.0
network 172.31.0.0
network 192.168.0.0
end
wr mem

R5
en
config t
router rip
no auto-summary
network 10.0.0.0
network 172.31.0.0
network 192.168.0.0
end
wr mem

The first issue that comes up, is auto-summary. The Ethernet interfaces are subnets of 10.0.0.0/8 and RIP thinks it has the route on itself, because of summarization. I added no auto-summary.


R4#sh ip proto
Routing Protocol is "rip"
Sending updates every 30 seconds, next due in 5 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Redistributing: rip
Default version control: send version 1, receive any version
Interface Send Recv Triggered RIP Key-chain
Ethernet0/0 1 1 2
Ethernet0/1 1 1 2
Serial0/1 1 1 2
Tunnel45 1 1 2
Automatic network summarization is not in effect
Maximum path: 4
Routing for Networks:
10.0.0.0
172.31.0.0
192.168.0.0
Routing Information Sources:
Gateway Distance Last Update
10.1.45.2 120 00:00:04
172.31.1.10 120 00:00:13
Distance: (default is 120)

R4#ping 10.1.41.4

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.41.4, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms

It sees the tunnel and serial interface both as paths to the remote router. The easiest solution is to add a static, but there are other ways.

I decided to try and force the traffic out the serial interfaces with a offset list to make the Tunnel interface unuseable.

en
config t
access-list 45 permit 10.1.45.0 0.0.0.3
router rip
offset-list 45 out 16 Tunnel 45
end
wr mem

I don't need an inbound list, because it is set outbound on both sides. Neither side should send traffic through the tunnel now.

I am now going to debug rip to see how it sends the data.


*Mar 1 02:42:28.123: RIP: sending v1 update to 255.255.255.255 via Ethernet0/0 (10.1.41.4)
*Mar 1 02:42:28.123: RIP: Update contains 2 routes
*Mar 1 02:42:28.123: RIP: Update queued
*Mar 1 02:42:28.123: RIP: sending v1 update to 255.255.255.255 via Ethernet0/1 (10.1.42.4)
*Mar 1 02:42:28.123: RIP: Update contains 2 routes
*Mar 1 02:42:28.123: RIP: Update queued
*Mar 1 02:42:28.123: RIP: sending v1 update to 255.255.255.255 via Serial0/1 (172.31.1.9)
*Mar 1 02:42:28.123: RIP: Update contains 1 routes
*Mar 1 02:42:28.123: RIP: Update queued
*Mar 1 02:42:28.123: RIP: sending v1 update to 255.255.255.255 via Tunnel45 (10.1.45.1)
*Mar 1 02:42:28.123: RIP: Update contains 1 routes
*Mar 1 02:42:28.127: RIP: Update queued
*Mar 1 02:42:28.127: RIP: Update sent via Ethernet0/0
*Mar 1 02:42:28.127: RIP: Update sent via Ethernet0/1
*Mar 1 02:42:28.127: RIP: Update sent via Serial0/1
*Mar 1 02:42:28.127: RIP: Update sent via Tunnel45
*Mar 1 02:42:35.551: RIP: received v1 update from 172.31.1.10 on Serial0/1
*Mar 1 02:42:35.551: RIP: Update contains 1 routes
*Mar 1 02:42:46.115: RIP: received v1 update from 10.1.45.2 on Tunnel45
*Mar 1 02:42:46.115: RIP: Update contains 1 routes

It looks like it is still sending updates through the tunnel. I just realized an offset list will not solve the problem, because the offset list is only for non-directly connected routes. I am going to have to try another method.


I removed 10.1.45.0 from router rip, but that removed my internal subnets from rip as well.