CCIE R&S Advanced Technologies Class v4.5 - Frame Relay Configuration Part 2

Transcript

1	Introduction	0h 43m
2	Using the Cisco Documentation	0h 52m
3	Ethernet Overview, Layer 2 Switchports, Trunking, ISL, 802.1q, DTP	0h 47m
4	VTP, VTP Authentication, VTP Pruning	1h 02m
5	VTP Prune Eligible List, VTP Transparent, VTP Troubleshooting, Trunk Allowed List, Extended VLANs	0h 48m
6	VLAN and VTP Review	0h 19m
7	SVIs, Native Routed Interfaces, Router-on-a-Stick	0h 46m
8	Layer 2 EtherChannel, EtherChannel Load Balancing, Layer 3 EtherChannel	0h 57m
9	802.1q Tunneling, Layer 2 Protocol Tunneling, EtherChannel over 802.1q Tunneling	1h 03m
10	STP Root Bridge Election, STP Root Port Election, STP Designated Port Election, STP Priority, STP Cost, STP Port-Priority	1h 06m
11	STP Review	0h 12m
12	STP Timers, STP PortFast	0h 34m
13	STP UplinkFast	0h 11m
14	STP BackboneFast	0h 12m
15	STP BPDU Filter	0h 13m
16	STP BPDU Guard	0h 11m
17	STP Root Guard	0h 11m
18	STP Loop Guard, Unidirectional Link Detection (UDLD)	0h 11m
19	Multiple Spanning-Tree Protocol (MST)	0h 40m
20	Rapid Spanning-Tree Protocol (RSTP), Rapid-PVST	0h 18m
21	MST with Multiple Regions	0h 33m
22	Flex Links	0h 16m
23	Frame Relay	0h 39m
24	Frame Relay Configuration Part 1	0h 34m
25	Frame Relay Configuration Part 2	0h 41m
26	Frame Relay Switching	0h 27m
27	Back-to-Back Frame Relay	0h 08m
28	Frame-Relay End-to-End Keepalives	0h 18m
29	PPP, PPP PAP Authentication, PPP CHAP Authentication	0h 59m
30	PPPoFR, PPPoE	0h 40m
31	Transparent Bridging, IRB	0h 32m
32	Fallback Bridging	0h 14m
33	IP Routing Overview, Switching Paths, Static Routing	0h 42m
34	Static Routing Examples	0h 25m
35	IP Default-Gateway, IP Default-Network	0h 14m
36	On-Demand Routing (ODR)	0h 07m
37	Floating Static Routes	0h 10m
38	Backup Interface	0h 29m
39	Enhanced Object Tracking, IP SLA, Reliable Static Routing	0h 21m
40	Policy Routing	0h 43m
41	GRE Tunneling, GRE Recursive Routing Errors	0h 27m
42	Reliable Backup Interface with GRE	0h 25m
43	RIP Overview, RIP Versions, RIP Auto-Summary	0h 48m
44	RIP Split-Horizon, RIP Timers	0h 22m
45	RIP Broadcast Updates, IP Directed Broadcast, IP Broadcast-Address, Smurf Attacks, Fraggle Attacks	0h 16m
46	RIP Unicast Updates	0h 03m
47	RIP Offset-List	0h 18m
48	RIP Authentication	0h 11m
49	RIP Summarization	0h 10m
50	Prefix-Lists, RIP Distribute-List Filtering, RIP Administrative Distance Filtering	0h 48m
51	RIP Default Routing, RIP Conditional Default Routing	0h 18m
52	RIP Triggered, RIP Validate Update Source,	0h 12m
53	EIGRP Overview	0h 29m
54	EIGRP Auto-Summary	0h 07m
55	EIGRP Split-Horizon	0h 11m
56	EIGRP Update Types, EIGRP Neighbor, EIGRP Passive-Interface	0h 24m
57	EIGRP Hello-Interval, EIGRP Hold-Time	0h 05m
58	EIGRP Authentication	0h 11m
59	EIGRP Time Based Authentication	0h 25m
60	EIGRP Path Selection, EIGRP Metric Weights, EIGRP Traffic Engineering	0h 47m
61	EIGRP Unequal Cost Load Balancing, EIGRP Variance	0h 19m
62	EIGRP QUERY, EIGRP Summarization, EIGRP Leak-Map	0h 28m
63	EIGRP Stub Router Advertisement	0h 22m
64	EIGRP Default Routing	0h 13m
65	EIGRP Route Filtering	0h 11m
66	EIGRP Router-ID	0h 07m
67	Miscellaneous EIGRP Features	0h 02m
68	OSPF Overview	0h 27m
69	Establishing OSPF Adjacencies, Understanding the OSPF Database	0h 43m
70	OSPF Network Type Broadcast, OSPF DR/BDR Election, OSPF over NBMA, OSPF Network Type Non-Broadcast and Point-to-Multipoint	0h 56m
71	OSPF Network Type Point-to-Point, OSPF Network Type Mismatch	0h 13m
72	OSPF Network Type Point-to-Multipoint Non-Broadcast, OSPF Per Neighbor Cost	0h 17m
73	OSPF Network Type Loopback	0h 02m
74	OSPF Path Selection	0h 27m
75	OSPF Convergence Timers	0h 09m
76	OSPF Authentication	0h 12m
77	OSPF Summarization	0h 32m
78	OSPF Stub Areas, OSPF Totally Stubby Areas, OSPF NSSAs, OSPF Totally NSSAs	0h 40m
79	Controlling OSPF NSSA Redistribution	0h 02m
80	OSPF Type 7 to 5 Translator Election, OSPF LSA Type 3 Filter, OSPF Forwarding Address Suppression	0h 24m
81	Route Redistribution Overview	0h 36m
82	Route Redistribution Configuration & Verification, Connected Redistribution	0h 22m
83	OSPF External Path Selection, TCL PING Scripting	0h 33m
84	Routing Loops Overview, EIGRP Route Loop Prevention	0h 55m
85	Metric Based Routing Loops, Route Tagging	0h 46m
86	Administrative Distance Based Routing Loops, Debug IP Routing, IP Route Profile	0h 58m
87	BGP Overview, BGP Peering Types	0h 51m
88	Establishing BGP Peerings, EBGP Multihop, BGP Neighbor Disable Connected Check, BGP TTL Security	0h 49m
89	BGP 4-Byte ASNs	0h 20m
90	BGP Local AS, BGP Peer Groups	0h 30m
91	BGP Next-Hop Self, BGP Next-Hop Processing	0h 30m
92	BGP Route Reflectors	0h 37m
93	Large Scale BGP Route Reflectors with Clusters	0h 34m
94	BGP Confederation	0h 37m
95	BGP NLRI Advertisements, BGP Network Statement, BGP Redistribution	0h 43m
96	BGP Aggregation, BGP Aggregation & Summary-Only, BGP Aggregation & Unsuppress-Map	0h 46m
97	BGP Origin, BGP Aggregation & AS-Set, BGP Aggregation & Advertise-Map	0h 22m
98	BGP Conditional Route Injection	0h 21m
99	BGP Bestpath Selection, BGP Multipath, BGP Weight	0h 53m
100	BGP Local Preference, BGP Local Preference and Communities, BGP AS-Path Prepending,	0h 30m
101	BGP MED, BGP MED Missing As Worst, BGP Deterministic MED	0h 17m
102	BGP Communites, BGP Regular Expressions	0h 43m
103	BGP Filtering, BGP Convergence Timers, BGP Default Routing, Miscellaneous BGP Features	0h 24m
104	MPLS Overview, MPLS Label Distribution Protocol (LDP)	1h 05m
105	MPLS Tunnels, MPLS Penultimate Hop Popping (PHP)	0h 40m
106	MPLS Layer 3 VPNs Overview, VRF Lite	0h 36m
107	MPLS Layer 3 VPNs and VPNv4 BGP	1h 08m
108	MPLS Layer 3 VPN Verification & Troubleshooting	0h 49m
109	MPLS Layer 3 VPN OSPF PE-CE Routing Overview	0h 06m
110	MPLS Layer 3 VPN OSPF PE-CE Routing Path Selection & Sham-Links	2h 01m
111	MPLS Layer 3 VPN OSPF PE-CE Routing Loop Prevention & Down-Bit, OSPF Capability VRF-Lite	0h 40m
112	IPv6 Overview, IPv6 ICMPv6 ND, IPv6 over NBMA	0h 44m
113	IPv6 Routing Overview, IPv6 Static Routing	0h 28m
114	IPv6 RIPng	0h 20m
115	IPv6 EIGRPv6	0h 09m
116	IPv6 OSPFv3	0h 31m
117	MP-BGP for IPv6	0h 26m
118	IPv6 Tunneling	1h 13m
119	Multicast Overview, IGMP	0h 34m
120	PIM Overview	0h 18m
121	PIM Dense Mode	1h 03m
122	PIM Sparse Mode	0h 30m
123	PIM Sparse Mode Configuration	0h 36m
124	PIM Sparse Mode RPF & RP Troubleshooting	0h 27m
125	Auto-RP, Multicast over GRE Tunnels	0h 53m
126	Bootstrap Router (BSR), Bidirectional PIM, Source Specific Multicast (SSM)	0h 40m
127	MSDP, Anycast RP	0h 27m
128	IPv6 Multicast Routing	0h 24m
129	QoS Overview, IntServ QoS, DiffServ QoS, IP Precedence, DSCP, MQC, HQF	0h 41m
130	MQC Classification	0h 44m
131	FIFO, FQ, WFQ, CBWFQ, HQF	0h 50m
132	LLQ	0h 23m
133	WRED	0h 31m
134	Traffic Shaping, Traffic Policing	0h 40m
135	Frame Relay Traffic Shaping (FRTS)	0h 33m
136	RSVP	0h 07m
137	Catalyst 3560 QoS	1h 00m
138	IOS Security Overview, Access Lists (ACLs)	0h 58m
139	Time Based ACLs, Dynamic ACLs	0h 33m
140	Reflexive ACLs	0h 21m
141	TCP Intercept, Content Based Access Control (CBAC)	0h 34m
142	Zone Based Policy Firewall (ZBPF)	1h 09m
143	AAA, Local Authentication, Local Authorization, Role Based CLI Access	0h 43m
144	Port Security, Static CAM Entries, Storm Control, 802.1X Authentication, PACLs, RACLs, VLAN Access Maps (VACLs)	0h 48m
145	DHCP Snooping, Dynamic ARP Inspection (DAI), IP Source Guard	0h 12m
146	Protected Ports, Private VLANs	0h 25m
147	IP Services Overview, HSRP	1h 10m
148	VRRP, GLBP	0h 28m
149	NAT	0h 42m
150	DHCP, DNS	0h 30m
151	NetFlow	0h 09m
152	WCCP, Miscellaneous IP Services	0h 06m
153	System Management Overview, NTP, NTP Authentication	0h 24m
154	SNMP, RMON	0h 38m
155	Syslog, Telnet, SSH, Banners	0h 21m
156	EEM Scripting, Miscellaneous System Management	0h 26m
Total Duration		81h 02m

Slides - Diagrams

Slides - Introduction

Slides - Ethernet Switching

Slides - Advanced Ethernet Switching

Slides - Frame Relay

Slides - PPP

Slides - Transport Bridging

Slides - Redistribution

Slides - IOS Security

Slides - Layer 2 Security

Slides - IP Services

Slides - System Management

0:00:12	So, up to this point, we look at the
0:00:17	verifying the we have the encapsulation
0:00:24	that we're learning the PVCs from the cloud.
0:00:27	Okay, once the circuits are active, then we
0:00:33	and any Layer 3 to Layer 2 resolution.
0:00:36	So, we saw using the dynamic
0:00:40	where as long as the protocol
0:00:43	in this case, the IPv4 address,
0:00:45	the router is gonna send the Inverse
0:00:50	If we were to look at this in a design
0:00:55	let's say between router 3, 4, and 5.
0:00:59	And on this link,
0:01:01	we'll say that router 3 has
0:01:10	We'll say, Encapsulation Frame Relay,
0:01:13	and No Shut.
0:01:16	Router 4, we'll do the same thing.
0:01:20	Encap.
0:01:21	Do Show IP Interface Brief.
0:01:24	This is interface serial 0/0/0.
0:01:29	Encap Frame Relay. IP address 100.0.0.4.
0:01:35	No Shut.
0:01:38	And then the same on...
0:01:40	5...
0:01:42	Encapsulation Frame Relay.
0:01:44	IP address 100.0.0.5.
0:01:49	And No Shutdown. So, in this type of design,
0:01:57	in between of the devices.
0:01:58	Once the line protocol comes up,
0:02:03	the frame relay process says,
0:02:08	I have IP configured on the link. So, I will send
0:02:14	Final results to this, when we look
0:02:18	we see that we have... Or we should
0:02:26	It may take a little bit of time to converge
0:02:31	Okay, 4 has mappings to 3 and 5.
0:02:38	3 has mappings to 4 and 5.
0:02:40	And then, 5 should have mappings
0:02:44	Okay, so, if we send packets
0:02:50	or router 4, we can see that
0:02:52	But also notice that on this segment,
0:02:55	we were able to resolve people
0:03:01	So, this is one of the problems with Inverse
0:03:05	That if we want a network that is essentially made
0:03:11	where we had a point-to-point
0:03:18	and then, we have a separate
0:03:25	since behind the scenes, there's a full mesh
0:03:33	We would see router 3, 4, and 5
0:03:39	and since there is no way to disable the reply,
0:03:43	then, 1 is gonna send the response back
0:03:51	Now, in a real design with frame relay,
0:03:55	because the service provider is not just
0:03:59	It's gonna give you whatever PVCs
0:04:04	But in our case, since the frame
0:04:08	for the purpose of changing the
0:04:13	then, we can sometimes run
0:04:15	where we're doing resolution for
0:04:20	So, what are some of the ways that we
0:04:25	3, 4, and 5, I want them to be able
0:04:31	So, these should be dynamic.
0:04:37	Router 1 and 2, I have
0:04:41	Even if I were to issue the No Frame Relay
0:04:47	it's still not gonna stop them from
0:04:53	There's two different variations
0:04:56	I could tell router 3, 4, and 5,
0:04:59	do not send the requests
0:05:04	So, I could go to...
0:05:07	router 5.
0:05:08	And when we look at the Show Frame
0:05:13	I could say that "I do not want...
0:05:18	to send...
0:05:21	frame relay Inverse ARP requests...
0:05:23	for IP out circuit 501 or 502."
0:05:29	Then, on router 4, I could do the same thing.
0:05:34	On router 3, I could say,
0:05:40	Another thing I could do...
0:05:42	is to assign the circuits to an
0:05:48	Because remember, for the circuit to
0:05:53	it has to have both the circuit and the
0:05:58	So, if we were to look at router 4
0:06:05	And look at the DLCIs.
0:06:08	We see that these are all
0:06:13	If I say that only circuits 403 and 405,
0:06:19	I could move 401, 402, and 413 to a
0:06:27	So, I could say on router 4,
0:06:35	where I will assign the frame relay
0:06:45	Now, when we look at the
0:06:49	these other circuit numbers are
0:06:53	If I also say, Show IP
0:07:03	IP is disabled on that link. Simply
0:07:10	So now, router 4 has no option but to not
0:07:16	because IP is not configured.
0:07:20	I could on router 3...
0:07:23	do it on a similar way, but I could move
0:07:28	Where when we say Show Frame
0:07:33	I'll take circuits 304 and 305 and move
0:07:38	And then, leave 301 and 302 on the
0:07:45	So, instead of what I have
0:07:49	I'll say, No IP Address.
0:07:52	I'll create a new sub-interface
0:07:56	I'll put the IP address on here...
0:08:01	along with Frame Relay
0:08:06	304 and 305.
0:08:15	So again, with the second command here,
0:08:18	this is only used to assign the
0:08:23	It doesn't have anything related to do with how
0:08:29	On the main interface, that command
0:08:34	You just can't see it in the config.
0:08:36	It's whatever circuits that are learned from the switch,
0:08:41	The only thing I'm doing here is just moving them
0:08:47	It's simply coincidental that since
0:08:53	and I don't already have static mappings,
0:08:56	then, I will run Inverse ARP on the circuits.
0:09:01	So, the Frame Relay Interface DLCI
0:09:04	It doesn't have anything to do with the frame
0:09:08	If we look at the Show
0:09:13	we should now see the mappings
0:09:17	Likewise on router 4.
0:09:24	And then, likewise on router 5.
0:09:28	Okay, these ones on router 5,
0:09:32	Because they appeared before
0:09:39	previously.
0:09:42	Then, ideally, just the last
0:09:50	There's a question here, "Would this
0:09:53	Maybe as a restriction of the lab.
0:09:56	That could be possible.
0:09:58	So, within the actual lab exam,
0:10:02	So, a lot of these solutions
0:10:04	some of them may not be feasible for
0:10:08	It just depends on what
0:10:12	So, if the question says "Don't add new interfaces."
0:10:18	What would be valid then is...
0:10:20	this variation here where I'm
0:10:25	Or maybe, I could just not
0:10:28	I could do static mappings for 3 and 4,
0:10:32	and then, I wouldn't have to worry about
0:10:38	So, if you were able to choose
0:10:41	Inverse ARP would basically
0:10:45	So, in order, you would want the
0:10:49	then the multipoint sub-interface.
0:10:53	Because the multipoint sub-interface give you more
0:10:59	Then, the multipoint interface
0:11:03	Followed by the static mappings
0:11:06	So, ideally, you wanna stay away from Inverse
0:11:18	So now, we have the mappings back from...
0:11:21	3 and 4.
0:11:22	We should be able to reach...
0:11:25	these two neighbors.
0:11:29	And also, notice that the broadcast
0:11:32	So, if I were to send a packet
0:11:40	this should be receive by both
0:11:45	Now, if we look at the
0:11:50	notice that from the Layer 3 process,
0:11:54	I am only sending one packet.
0:11:57	But from the Layer 2 point of view,
0:12:02	I'm sending one of the out...
0:12:05	circuit...
0:12:08	503.
0:12:10	And I'm sending another
0:12:14	The reason why is that the Layer 2
0:12:18	A Layer 3 broadcast.
0:12:21	Now, it needs to do the...
0:12:23	Pseudo Broadcast process.
0:12:26	So, it essentially looks through the
0:12:29	And says, "What are all of the circuits that have the
0:12:36	Which in this case, is...
0:12:40	circuit 503.
0:12:43	And circuit 504.
0:12:47	So, for the broadcast keyword, this has nothing
0:12:53	Okay, it doesn't matter
0:12:56	What the process is looking at is
0:13:00	What is the circuit number? And do
0:13:06	Because remember for a broadcast frame,
0:13:11	The destination is a broadcast address.
0:13:14	The same would be true
0:13:16	If you have a multicast OSPF
0:13:22	the unicast mapping for frame relay
0:13:28	It's only the broadcast keyword that goes along
0:13:35	Okay, we'll see next when we look
0:13:39	when we're trying to do the...
0:13:42	both unicast, multicast, and
0:13:46	there's a limit to where we
0:13:49	from an efficiency point
0:14:01	So, if we look at out different
0:14:06	we have the main interface
0:14:13	The same on...
0:14:15	router 2.
0:14:17	Okay, the main interface
0:14:19	Okay, actually, this on is not gonna work.
0:14:22	Until I add Frame Relay Map IP.
0:14:26	Router 1's address and the circuit number.
0:14:32	With this configuration,
0:14:37	but I would not be able to
0:14:41	Because I don't have the broadcasts
0:14:48	On router 3, we have a
0:14:54	that is doing Inverse ARP.
0:14:56	So, since the circuit number is assigned,
0:15:01	which are actually multiple circuits, 304, 305.
0:15:04	And we have the protocol enabled,
0:15:07	then, we're gonna send
0:15:12	On router 4,
0:15:15	we have the main interface with Inverse ARP.
0:15:19	So, the only thing we need here is just the...
0:15:22	encapsulation and the IP address.
0:15:28	Then, on router 5,
0:15:32	we have...
0:15:35	the same thing with Inverse ARP,
0:15:40	Okay, router 4 solved that problem of the...
0:15:43	the Inverse ARP by moving the other
0:15:53	Okay, there's a question, "How does the broadcast
0:15:59	There's an interaction between the
0:16:02	So, it knows what is a broadcast
0:16:08	It's based on the destination address.
0:16:10	So, if it's going towards the...
0:16:15	if it's going towards the all subnet
0:16:20	if it was going to the directed
0:16:24	which is this case would be... Like for
0:16:32	Or if it was going to anything in the class D range,
0:16:38	this would be anything that goes
0:16:47	So, programatically, there's just
0:16:49	"This is traffic that needs
0:16:54	As it hands it off to the Layer 2 process that way.
0:16:58	But the key is that the Layer 2 process doesn't really
0:17:04	It just says, "I know this is a...
0:17:07	broadcast or a multicast."
0:17:13	I'm gonna do that thing on,
0:17:17	Okay, the only thing that the process knows here
0:17:23	what circuits support broadcast?
0:17:27	Anything that matches there, we're gonna make a
0:17:32	So, we could see, it's sent out twice there.
0:17:37	Okay, other variations of these configs here,
0:17:40	on router 3, on this sub-interface,
0:17:44	we could take these...
0:17:48	Frame Relay Interface DLCI commands,
0:17:52	and we could replace them with
0:17:57	So, we could do a static mapping to router 4.
0:18:03	We could do a static mapping to router 5.
0:18:08	And then, it's gonna have the same result.
0:18:12	Okay, in this case,
0:18:14	these bottom two commands,
0:18:17	because the top two are already
0:18:21	The only case that you would
0:18:24	is that if you're trying to apply some sort of
0:18:30	Like a map class for frame
0:18:33	But I could remove these two bottom commands
0:18:36	because the frame relay map is
0:18:47	Okay, there's a question, "Are you saying the frame
0:18:51	No, it cannot.
0:18:53	So, it just knows that it is some type of packet that
0:19:01	So, it look through the Frame
0:19:04	and then it figures out whichever ones have
0:19:11	Behind the scenes, there's actually, there's a
0:19:15	There's a specific broadcast queue that is
0:19:19	So, there's some sort of interaction whether
0:19:24	That's like process switching or CEF switching.
0:19:27	When they arrive at the interface,
0:19:29	frame relay knows that they're supposed to use
0:19:34	So, really, from our perspective, we don't
0:19:39	That if you have the broadcast keyword, the frames
0:19:46	Okay, another variation here would
0:19:52	and we can move this off of the main interface
0:20:00	So, if I take the frame relay maps off...
0:20:08	for both of these addresses.
0:20:12	I'll say that I want a point-to-point...
0:20:16	sub-interface...
0:20:18	that has this particular address.
0:20:22	And this particular...
0:20:26	DLCI 201.
0:20:34	So, we're still able to transport
0:20:38	We would also be able to
0:20:41	Because when we look at the
0:20:45	there's a difference between how the process
0:20:49	versus any type of multipoint interface.
0:20:53	Again, remember, the multipoint interface is either
0:21:00	So when we look at this output from
0:21:01	notice that it doesn't have an IP
0:21:07	It says, "This is point-to-point."
0:21:12	Essentially, what this means is that if any packet
0:21:20	then, it will always use the circuit number
0:21:28	Regardless of what the unicast destination is
0:21:32	it's always getting circuit number
0:21:39	This is why this configuration is preferred,
0:21:45	So, the only thing we need to do is just assign
0:21:50	and the process is gonna
0:21:54	We don't need to do the Frame Relay Map
0:21:57	we don't need to do Inverse ARP.
0:21:59	Okay, if we try to do that, we'll see that
0:22:05	If we say Frame Relay Map IP
0:22:13	only Frame Relay Interface DLCI command should be used
0:22:19	Because we don't need that
0:22:27	Now, the real trouble comes in here
0:22:30	when we have multiple devices on
0:22:36	but we don't have a full mesh
0:22:39	which is either our Partial Mesh design
0:22:44	So, let's say now that between routers...
0:22:47	3, 4, and 5,
0:22:49	I don't want the full mesh of circuits anymore
0:22:55	So, we'll say that...
0:22:57	Router 4 is gonna be the hub.
0:23:05	Router 4 has one circuit
0:23:09	On this side, this is 403.
0:23:12	On the way back, it's 304.
0:23:18	From 4 to 5,
0:23:21	5 is using circuit...
0:23:24	504.
0:23:26	Then, on the way back, we have 405.
0:23:31	All three of these neighbors are gonna be on the
0:23:38	100.0.0.4, and 100.0.0.5.
0:23:52	From router 3's configuration, the only thing
0:23:57	would be to remove this mapping.
0:24:02	So, on the multipoint sub-interface, I do not want to
0:24:12	Okay, I'll also remove these
0:24:24	So, at this point, we should now
0:24:28	But we won't be able to reach router 5, because we
0:24:36	On router 4 who is the hub,
0:24:39	we have the main interface that is doing
0:24:46	So, this will work. It's not really the ideal case.
0:24:50	But we should still have the dynamic
0:24:56	On router 5,
0:24:58	I'm gonna change the...
0:25:02	main interface to a multipoint sub-interface.
0:25:07	Or excuse me, to a point-to-point sub-interface.
0:25:10	So, No IP Address.
0:25:14	Let's say, Encapsulation HTLC,
0:25:20	That should remove any of the
0:25:25	We'll create a point-to-point sub-interface...
0:25:29	with the address 100.0.0.5,
0:25:34	and Frame Relay...
0:25:38	Interface DLCI 504.
0:25:43	Okay, that's going to router 4.
0:25:54	Since router 5 has a
0:25:56	it knows that whether I'm going
0:26:01	or whether when I'm going to router 3,
0:26:04	I'm always gonna be using that same
0:26:09	So, if I were to send a packet,
0:26:11	Frame Relay Packets.
0:26:15	And we'll look at this on all three
0:26:17	Frame Relay Packets.
0:26:23	Debug Frame Packets.
0:26:24	On router 5, I'm gonna ping the
0:26:31	And I'm gonna send just one packet.
0:26:35	Okay, we see that works.
0:26:36	It's going out...
0:26:39	the sub-interface serial 0/0.1,
0:26:45	and it went out circuit 504.
0:26:50	Then, we have an inbound
0:26:56	this was the echo reply.
0:26:59	The other output, we can see that
0:27:03	which is the Ether-type 2000.
0:27:08	So, if we wanted to, we could disable CDP...
0:27:11	to stop it running on that circuit.
0:27:14	Now, router 4 who is the hub,
0:27:18	This was the ping request, the echo.
0:27:22	Then, we're replying back, this is the echo reply.
0:27:28	If router 5 pings router 3,
0:27:32	who is the other spoke.
0:27:36	Router 5 says that...
0:27:40	"The route to the packet...
0:27:42	is via serial 0/0/0.1."
0:27:49	This is a point-to-point sub-interface.
0:27:55	It doesn't matter what the destination is, as long as a
0:28:02	Router 4 who is the hub,
0:28:04	then receives this in.
0:28:09	It says that "A packet came in from 5.
0:28:14	I need to send it out to 3."
0:28:20	So, actually, this one here in the middle,
0:28:25	If we were to look at the Debug IP ICMP,
0:28:31	and let's Show Debug...
0:28:33	I want to...
0:28:38	That's fine. Let's say...
0:28:40	On these routers, let's say No CDP Run.
0:28:42	So, we stopped another output.
0:28:46	Okay, No CDP Run is gonna turn
0:28:59	So let's see again.
0:29:06	The hub is getting it.
0:29:08	And it's sending an ICMP redirect,
0:29:13	because it thinks that those neighbors
0:29:19	This is one of the other
0:29:22	the Partial Mesh for a Layer 3.
0:29:25	That for... It depends on the ICMP redirect
0:29:30	But it is potential that for every single packet
0:29:37	So, let's say that we have a web server here...
0:29:43	behind router 3. And we have a
0:29:47	When these clients hit the web server,
0:29:50	they're going in 4 interface and back out.
0:29:55	For everyone of these packets, it's potential
0:30:01	saying that "Really, you should be using this
0:30:07	The reason for us saying that is that it assumes
0:30:15	So, this is just one example
0:30:18	not understanding what's going on
0:30:27	But in any case, router 4 received the
0:30:33	3 gets it. It says, "The packet came in.
0:30:39	I'm trying to reply with the echo reply.
0:30:41	But I don't know how to send
0:30:48	If we look at the Debug IP Packet or...
0:30:51	Debug IP ICMP,
0:30:55	and send this ping again.
0:30:58	We see that when router 3 gets it,
0:31:01	the routing process is fine.
0:31:04	So, the packet came in. It was destined for us.
0:31:11	We then try to generate an ICMP echo reply.
0:31:15	It's supposed tocome from us locally,
0:31:17	go to router 5 which is located on this interface.
0:31:22	We send it then to the Layer 2 process.
0:31:29	that we don't know what?
0:31:40	The Layer 2 frame-relay process
0:31:44	that the address 100.0.0.5 is reachable out.
0:31:48	So, it doesn't have a mapping for that address.
0:31:50	If we look at the Show frame-relay map,
0:31:57	but we don't have the static
0:32:01	So, the disadvantage of this type of design,
0:32:04	is that if we wanted to use the
0:32:08	we would need then to put a static frame-relay
0:32:16	So, we'll say that to reach router 5, we're gonna
0:32:25	If there were other spokes,let's say,
0:32:32	for all of these destinations, we're still gonna
0:32:40	because that's the one that goes up to the hub.
0:32:44	So, design wise, it really doesn't make
0:32:48	Because you're adding a lot
0:32:51	that would be much easier solved if you were to
0:33:00	So, on router 5, 5 doesn't care
0:33:03	It knows that if it point to this interface
0:33:11	Now additionally, when I'm adding these
0:33:17	I said that for packets going to .4,
0:33:23	if they're going to .5, they use 304, .6, .7, .8, etc.
0:33:28	But notice also that I added the broadcast
0:33:35	This is what you would not want to do.
0:33:38	What is the reason that I would not wanna add
0:33:54	Everytime I send now one
0:34:00	the Layer 2 process is gonna replicate it five times.
0:34:05	So, if I were to send a ping,
0:34:12	Okay, let's say ping 255.255.255.255 repeat 1.
0:34:18	So, the Layer 3 process is generating just one ping.
0:34:23	Look how many responses we got though.
0:34:29	We're getting five responses in from the hub.
0:34:32	So, what this means is that when the
0:34:38	it says circuit 304 supports broadcast.
0:34:42	And also circuit 304, 304, 304 and 304 support it.
0:34:49	So, there's no sort of parser check in there
0:34:52	to say that if you already found in
0:34:57	there's no reason that you need to find it again.
0:35:02	So, from the configuration point of view, it doesn't really
0:35:08	as long as we put it nomore than one time.
0:35:13	Okay, no more than one
0:35:17	So, this means that if I were running IPv6,
0:35:21	I would need a separate broadcast
0:35:26	But I don't want to put it more
0:35:33	So, let's remove these broadcast keywords,
0:35:50	So, we remove...
0:35:53	all of these maps.
0:36:00	Okay then, I am going to do a quick edit
0:36:07	Okay, this can be useful in the lab exam to manipulate
0:36:14	I'll say Find no and Replace it with no.
0:36:18	Then Find broadcast and Replace it with no.
0:36:23	Now, I have the output that I want.
0:36:27	So, of course, there's a lot
0:36:31	But in this scope of the exam, you will
0:36:36	So, you might wanna start using that
0:36:42	So now here, I have five mappings. None of
0:36:50	if I were to add another one,
0:36:57	1.2.3.4 304 broadcast.
0:37:01	Frame-Relay Map IP
0:37:06	Now, we know this address isn't
0:37:11	It's not even on the same
0:37:14	But the pseudo process or the pseudo broadcast
0:37:22	Cause that's not what is looking for. It's looking
0:37:30	And it's saying, "On this interface, find any
0:37:36	If this has an IP mapping,
0:37:39	then I'm gonna send an IP broadcast
0:37:46	So now, if I ping,
0:37:50	255.255.255.255 repeat count of 1,
0:37:57	the packet does get to 4 and 4 can respond.
0:38:01	But it doesn't even matter what
0:38:07	So, it could be on this garbage mapping,
0:38:11	Okay, it could go to the actual address.
0:38:14	Normally, this is where you
0:38:16	There's really no reason you
0:38:21	It's just to show the point that the broadcast keyword
0:38:27	Okay, you could put 0.0.0.0
0:38:30	As long as you're looking at this protocol stack,
0:38:35	this Layer 2 circuit and your supporting broadcast,
0:38:49	Okay, any other questions up o this point with the
0:38:59	So, up to this point, this is just the basics
0:39:05	we're gonna spend a lot of time with frame-relay
0:39:08	within the scope of the routing process
0:39:13	Tomorrow we'll come back to frame-relay and talk about
0:39:20	then we'll look at some minor features like
0:39:24	and frame-relay header compression. There's some other
0:39:30	But as long as you know what are all the different
0:39:36	again, looking at essentially,
0:39:40	any of these options,
0:39:43	it doesn't matter what option you choose as
0:39:49	There are some that would be
0:39:53	like we saw that point-to-point
0:39:56	It make sense to do it that way because then,
0:39:59	we don't have to maintain a thousand mappings
0:40:04	And also, we will be covering
0:40:08	So, bridging over frame-relay.
0:40:14	We'll touch on the legacy
0:40:16	and then also Integrated Routing
0:40:20	And PPP over Frame-Relay, I'm not
0:40:24	And PPPoE. So, tomorrows class is gonna
0:40:31	And then some other of these
0:40:35	So, PPP over serial links, CHAP/PAP Authentication,

Now Viewing

CCIE R&S Advanced Technologies Class v4.5
Title:	CCIE R&S Advanced Technologies Class v4.5
Duration:	81h 02m
The CCIE Routing & Switching Advanced Technologies Class is the first step in understanding CCIE level technologies and is a companion to the Advanced Technologies Lab Workbook. Each technology you need to know for the CCIE Routing & Switching lab will be described in detail using an instructor led hands on demonstration. The class consists of over 80 hours of in depth explanations and examples.
Get instant access to our entire library!
	Sign Up
Download this Course
$299.00	Add to Cart

Frame Relay Configuration Part 2

Create Bookmark