Points to consider:


                                       


HUB or the MANILA Router Point-to-Point Frame Relay Configurations:

R1#config t
Enter configuration commands, one per line.  End with CNTL/Z.
R1(config)#hostname MANILA
MANILA(config)#int s3/0
MANILA(config-if)#encapsulation frame-relay
MANILA(config-if)#no shut
MANILA(config-if)#exit

MANILA(config)#int s3/0.12 point-to-point
MANILA(config-subif)#ip address 192.168.12.1 255.255.255.0
MANILA(config-subif)#frame-relay interface-dlci 101
MANILA(config-fr-dlci)#EXIT

MANILA(config)#int s3/0.13 point-to-point
MANILA(config-subif)#ip address 192.168.13.1 255.255.255.0
MANILA(config-subif)#frame-relay interface-dlci 102
MANILA(config-fr-dlci)#^Z
MANILA#

 SPOKE1 or MELBOURNE Router Point-to-Point Frame Relay Configurations:

R2#config t
Enter configuration commands, one per line.  End with CNTL/Z.
R2(config)#hostname MELBOURNE
MELBOURNE(config)#
MELBOURNE(config)#int s4/0
MELBOURNE(config-if)#encapsulation frame-relay
MELBOURNE(config-if)#no shut
MELBOURNE(config-if)#exit

MELBOURNE(config)#int s4/0.21 point-to-point
MELBOURNE(config-subif)#ip address 192.168.12.2 255.255.255.0
MELBOURNE(config-subif)#frame-relay interface-dlci 202
MELBOURNE(config-fr-dlci)#exit

SPOKE2 or SINGAPORE Router Point-to-Point Frame Relay Configurations:

R3#CONFIG T
Enter configuration commands, one per line.  End with CNTL/Z.
R3(config)#hostname SINGAPORE
SINGAPORE(config)#int s3/0
SINGAPORE(config-if)#encapsulation frame-relay
SINGAPORE(config-if)#no shut
SINGAPORE(config-if)#exit

SINGAPORE(config)#int s3/0.31 point-to-point
SINGAPORE(config-subif)#ip address 192.168.13.2 255.255.255.0
SINGAPORE(config-subif)#frame-relay interface-dlci 203
SINGAPORE(config-fr-dlci)#^Z
SINGAPORE#

VERIFICATIONS FOR THE FRAME RELAY CONFIGURATIONS:

MANILA#show frame-relay map
Serial3/0.12 (up): point-to-point dlci, dlci 101(0x65,0x1850), broadcast
          status defined, active

Serial3/0.13 (up): point-to-point dlci, dlci 102(0x66,0x1860), broadcast
          status defined, active

MANILA#ping 192.168.12.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.12.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 80/95/104 ms

MANILA#ping 192.168.13.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.13.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 80/93/108 ms

As observed above, MANILA router can reach both the MELBOURNE and SINGAPORE routers

Now, let’s configure EIGRP on the HUB and Spoke Routers:

On MANILA router, I have created a loopback address for the 4 network segments which I’m planning to propagate to both MELBOURNE and SINGAPORE routers.

MANILA(config)#int lo1
MANILA(config-if)#ip add 100.100.1.1 255.255.255.0
MANILA(config-if)#int lo2
MANILA(config-if)#ip add 100.100.1.1 255.255.255.0
MANILA(config-if)#int lo3
MANILA(config-if)#ip add 100.100.3.1 255.255.255.0
MANILA(config-if)#int lo4
MANILA(config-if)#ip add 100.100.4.1 255.255.255.0
   

I have enabled EIGRP on MANILA router and added into EIGRP networks the segments to MANILA and SINGAPORE. I have propagated as well the 4 network address as seen below,
MANILA(config)#router eigrp 123
MANILA(config-router)#network 192.168.12.0
MANILA(config-router)#network 192.168.13.0
MANILA(config-router)#network 100.100.1.0 0.0.0.255
MANILA(config-router)#network 100.100.2.0 0.0.0.255
MANILA(config-router)#network 100.100.3.0 0.0.0.255
MANILA(config-router)#network 100.100.4.0 0.0.0.255
MANILA(config-router)#no auto-summary <— required to disabled auto-summary of the networks
Configuring EIGRP on both MELBOURNE and SINGAPORE Router:
MELBOURNE(config)#router eigrp 123
MELBOURNE(config-router)#network 192.168.12.0

 MELBOURNE(config-router)#no auto-summary
*Jul 12 14:27:24.967: %DUAL-5-NBRCHANGE: EIGRP-IPv4 123: Neighbor 192.168.12.1 (Serial4/0.21) is up: new adjacency
 

SINGAPORE(config)#router eigrp 123
SINGAPORE(config-router)#network 192.168.13.0

SINGAPORE(config-router)#no auto-summary

*Jul 12 14:28:01.507: %DUAL-5-NBRCHANGE: EIGRP-IPv4 123: Neighbor 192.168.13.1 (Serial3/0.31) is up: new adjacency

The moment that I have enabled EIGRP and add the network statement on both MANILA and SINGAPORE router, neighbor adjacency were formed as seen from console below, 
MANILA(config-if)#
*Jul 12 14:27:24.931: %DUAL-5-NBRCHANGE: EIGRP-IPv4 123: Neighbor 192.168.12.2 (Serial3/0.12) is up: new adjacency

*Jul 12 14:28:01.351: %DUAL-5-NBRCHANGE: EIGRP-IPv4 123: Neighbor 192.168.13.2 (Serial3/0.13) is up: new adjacency

VERIFICATIONS FOR THE EIGRP CONFIGURATIONS:
1. Neighbor Table shows that MANILA have formed the neighbor with both SINGAPORE and MELBOURNE router.
MANILA#show ip eigrp neighbors
EIGRP-IPv4 Neighbors for AS(123)
H   Address                 Interface              Hold Uptime   SRTT   RTO  Q  Seq
                                                   (sec)         (ms)       Cnt Num
1   192.168.13.2            Se3/0.13                 14 00:20:05  132   792  0  3
0   192.168.12.2            Se3/0.12                 11 00:20:42  156   936  0  3
MELBOURNE#show ip eigrp neighbors
EIGRP-IPv4 Neighbors for AS(123)
H   Address                 Interface              Hold Uptime   SRTT   RTO  Q  Seq
                                                   (sec)         (ms)       Cnt Num
0   192.168.12.1            Se4/0.21                 12 00:24:31 1576  5000  0  2
SINGAPORE#show ip eigrp neighbors
EIGRP-IPv4 Neighbors for AS(123)
H   Address                 Interface              Hold Uptime   SRTT   RTO  Q  Seq
                                                   (sec)         (ms)       Cnt Num
0   192.168.13.1            Se3/0.31                 12 00:24:27 1603  5000  0  4
2.  The topology table shows the details of the learned network addresses, reachability and the Feasible distance, and the address or gateway to reach the propagated network address.
MELBOURNE#show ip eigrp topology
EIGRP-IPv4 Topology Table for AS(123)/ID(192.168.12.2)
Codes: P – Passive, A – Active, U – Update, Q – Query, R – Reply,
       r – reply Status, s – sia Status
P 100.100.3.0/24, 1 successors, FD is 2297856
        via 192.168.12.1 (2297856/128256), Serial4/0.21
P 192.168.12.0/24, 1 successors, FD is 2169856
        via Connected, Serial4/0.21
P 192.168.13.0/24, 1 successors, FD is 2681856
        via 192.168.12.1 (2681856/2169856), Serial4/0.21
P 100.100.4.0/24, 1 successors, FD is 2297856
        via 192.168.12.1 (2297856/128256), Serial4/0.21
P 100.100.1.0/24, 1 successors, FD is 2297856
        via 192.168.12.1 (2297856/128256), Serial4/0.21
P 100.100.2.0/24, 1 successors, FD is 2297856
        via 192.168.12.1 (2297856/128256), Serial4/0.21
3. Below is the routing table for both MELBOURNE and SINGAPORE router.
MELBOURNE#show ip route eigrp
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
       + – replicated route, % – next hop override
Gateway of last resort is not set
      100.0.0.0/24 is subnetted, 4 subnets
D        100.100.1.0 [90/2297856] via 192.168.12.1, 00:27:29, Serial4/0.21
D        100.100.2.0 [90/2297856] via 192.168.12.1, 00:27:29, Serial4/0.21
D        100.100.3.0 [90/2297856] via 192.168.12.1, 00:27:29, Serial4/0.21
D        100.100.4.0 [90/2297856] via 192.168.12.1, 00:27:29, Serial4/0.21
D     192.168.13.0/24 [90/2681856] via 192.168.12.1, 00:27:29, Serial4/0.21
SINGAPORE#show ip route eigrp
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
       + – replicated route, % – next hop override
Gateway of last resort is not set
      100.0.0.0/24 is subnetted, 4 subnets
D        100.100.1.0 [90/2297856] via 192.168.13.1, 00:27:39, Serial3/0.31
D        100.100.2.0 [90/2297856] via 192.168.13.1, 00:27:39, Serial3/0.31
D        100.100.3.0 [90/2297856] via 192.168.13.1, 00:27:39, Serial3/0.31
D        100.100.4.0 [90/2297856] via 192.168.13.1, 00:27:39, Serial3/0.31
D     192.168.12.0/24 [90/2681856] via 192.168.13.1, 00:27:39, Serial3/0.31
As observed above, the network segments added into EIGRP by the HUB or MANILA routers were received on both MELBOURNE and SINGAPORE Router.
VERIFICATIONS FOR REACHABILITY:
SINGAPORE#ping 100.100.1.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 100.100.1.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 116/129/148 ms
SINGAPORE#ping 100.100.2.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 100.100.2.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 92/107/116 ms
SINGAPORE#ping 100.100.3.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 100.100.3.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 84/96/108 ms
SINGAPORE#ping 100.100.4.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 100.100.4.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 76/100/128 ms

Leave a comment

Quote of the week

"People ask me what I do in the winter when there's no baseball. I'll tell you what I do. I stare out the window and wait for spring."

~ Rogers Hornsby