In numerous generation environments, acquiring firewall alterations from the service agency is usually an intense pain. A great deal of people use employing GRE/IPSEC to tube targeted traffic in between websites, so that the provider solely should start GRE/IPSEC locations, compared to each port per program. In this post, we’re heading to go over tips on how to carry out a rudimentary GRE tube in between websites, along with variety an EIGRP adjacency more than the item. Just as one extra benefit, we’re going to help PIM Dense-Mode with the tube interfaces, watching multicast targeted traffic move within the tube. Devoid of more ado, let’s are able to the item!
Your topology will be reasonably normal connected with everything you may possibly notice using some environments- several remote control websites, and also a backbone/service supplier which in turn we would like to tube targeted traffic more than.
Multicast more than GRE
Here’s what we’re going to complete:
1) Configure a rudimentary GRE tube in between Internet site A new along with Internet site B (and help PIM dense-mode)
2) Configure EIGRP to an adjacency within the Canal interface
3) Configure Internet site B’s Loopback66 to join multicast collection 224. 10. 10. 10, after that attempt to get to the item via R1 through this tube.
Adequate discuss, let’s get started!
GRE Canal Configuration with R1:
interface Tunnel0
ip handle 10. 10. 10. 1 255. 255. 255. 0
ip pim dense-mode
tube supplier 1. 1. 1. 1
tube desired destination 6. 6. 6. 6
GRE Canal Configuration with R6:
interface Tunnel0
ip handle 10. 10. 10. 6 255. 255. 255. 0
ip pim dense-mode
tube supplier 6. 6. 6. 6
tube desired destination 1. 1. 1. 1
Let’s make sure the tube will be on R1:
R1_AS50#show ip int br | my partner and i Tun
Tunnel0 10. 10. 10. 1 YES information upwards upwards
The particular tube will be upwards, let’s notice if we could ping over the item:
R1_AS50#ping 10. 10. 10. 6
Sort escape sequence to abort.
Mailing 5, 100-byte ICMP Displays to 10. 10. 10. 6, timeout will be only two mere seconds:
!!!!!
Achievements pace will be 100 % (5/5), round-trip min/avg/max = 4/34/64 milliseconds
R1_AS50#
R1_AS50#show ip way 10. 10. 10. 6
Course-plotting gain access to for 10. 10. 10. 0/24
Identified through "connected", long distance 0, metric 0 (connected, through interface)
Course-plotting Descriptor Hindrances:
* straight linked, through Tunnel0
Option metric will be 0, targeted traffic share depend will be 1
Awesome- so we could ping R6′s tube interface, along with we approved the way is over this Tunnel0 interface. Before we proceed any further, I will speak about that any of us get configured OSPF end-to-end- via R1 to R6.. so we accomplish get complete reachability through OSPF via Internet site A new to Internet site B.. we are solely configuring EIGRP throughout the tube to demonstrate 2 things: Our tube will be operating properly, which we could variety redirecting standard protocol adjacencies more than the tube.
EIGRP setting with Internet site A new:
BE AWARE: Detect we’re allowing OSPF for the Canal IP handle, DEFINITELY NOT the endpoints (ie: 1. 1. 1. 1/6. 6. 6. 6, respectively)
router eigrp 5
circle 10. 0. 0. 0
absolutely no auto-summary
EIGRP setting with Internet site B:
router eigrp 5
circle 10. 0. 0. 0
absolutely no auto-summary
Today let’s verify the EIGRP friend associations usually are operating:
R6_AS60#show ip eigrp neigh
IP-EIGRP neighbors for practice 5
H Tackle User interface Maintain Uptime SRTT RTO Queen Seq
(sec) (ms) Cnt Num
0 10. 10. 10. 1 Tu0 10 00: 41: 00 56 5000 0 5
Excellent! EIGRP will be operating within the tube. Today let’s test the multicast. Initial let’s configure Loopback66 with R6 to join multicast collection 224. 10. 10. 10 to be a device, along with we’ll post targeted traffic for this collection via R1 through this tube.
interface Loopback66
ip igmp join-group 224. 10. 10. 10
Today let’s go onto R1 along with attempt to post targeted traffic (ICMP) to your multicast collection:
R1_AS50#ping 224. 10. 10. 10 replicate 3
Sort escape sequence to abort.
Mailing 1, 100-byte ICMP Displays to 224. 10. 10. 10, timeout will be only two mere seconds:
Reply to obtain 0 via 10. 10. 10. 6, 25 milliseconds
Reply to obtain 0 via 10. 10. 10. 6, 31 milliseconds
Reply to obtain 0 via 10. 10. 10. 6, twenty six milliseconds
Awesome! We can easily struck the Multicast collection productively, yet let’s verify this mroute desk seems to be proper to the particular collection:
R1_AS50#show ip mroute 224. 10. 10. 10
(*, 224. 10. 10. 10), 00: 00: 24/stopped, RP 0. 0. 0. 0, red flags: N
Incoming interface: Null, RPF nbr 0. 0. 0. 0
Outgoing interface number:
Tunnel0, Forward/Dense, 00: 00: 24/00: 00: 00
We’ve got the (*, G) gain access to, along with Tunnel0 in this Outgoing User interface Checklist, or maybe ESSENTIAL OIL.. existence will be good!







0 comments:
Post a Comment