CCIE Routing & Switching Advanced Technologies Class

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 46m
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 34m
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 59m

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:15	In our next section here, we're gonna talk about
0:00:20	There are some other topics we'll discuss in
0:00:26	like how does OSPF interact with frame relay?
0:00:28	How did the other IGPs and especially
0:00:33	But for discussion in this section, we're going to constrain
0:00:42	Now, frame relay is starting to become
0:00:47	because it's mainly being replaced by
0:00:51	like either Metro Ethernet, Gigabit,
0:00:56	and then optical technologies like OC-48, OC-192
0:01:03	would only be offered by service providers up to
0:01:10	So, in cases where frame relay
0:01:14	a lot of times in the core of the
0:01:18	they're not actually using frame
0:01:21	Okay, it's more common today where
0:01:24	between the service provider and the customer,
0:01:28	but then, in the service provider network,
0:01:32	using some sort of Layer 2 VPN technology.
0:01:35	So, we'll discuss that briefly when
0:01:40	But the main point being here is that frame relay is not gonna
0:01:46	as it was five years ago or
0:01:51	Now, to understand how frame relay works and
0:01:56	we first need to understand what are the differences between
0:02:03	Now, with broadcast such as Ethernet or
0:02:09	broadcast simply means
0:02:13	is able to send a packet to all connected
0:02:18	So, for Ethernet, the way this is accomplished is with
0:02:25	Where we have a Layer 2 broadcast frame
0:02:30	it delivers it to all ports that are
0:02:35	That's what we're referring
0:02:38	Meaning, the limitation of where a single host can
0:02:46	Now, using a broadcast media like Ethernet,
0:02:50	simplifies the Layer 3 to Layer 2 resolution,
0:02:54	which is where some source needs to figure out
0:02:59	or the frame relay DLCI number, or the ATM PVC
0:03:07	when we are building a frame
0:03:11	Now, the "Non-broadcast Multi-Access" or NBMA medias
0:03:16	such as frame relay, ATM, or ISDN,
0:03:19	the main difference between these and Ethernet...
0:03:22	is that a source cannot send a packet to all
0:03:29	So, a good analogy for this would be ISDN.
0:03:31	So, it's not possible for a router to dial every
0:03:37	when it's trying to send a particular Layer 2 frame.
0:03:41	Now, the equivalence of this in frame relay or ATM
0:03:45	would be that when the router sends a
0:03:48	the frame relay switches do
0:03:52	The frame relay... It's only gonna
0:03:55	that is bound based on
0:04:00	So, we'll also see what the basic
0:04:04	how the service provider will deal with
0:04:08	of inbound and outbound circuit numbers that are gonna
0:04:15	Now, since source is on the MBMA network,
0:04:18	you cannot send a packet to all
0:04:23	it means that we're gonna have some
0:04:27	when we actually try to use our higher
0:04:32	Now, some of the interface
0:04:36	which is called "Pseudo Broadcast"
0:04:39	where when I send a Layer 3
0:04:46	for example, the Layer 3 broadcast going
0:04:52	When the Layer 3 process delivers this
0:04:57	it's up to the frame relay process to
0:05:01	depending on how many circuits are
0:05:06	So, when we look at this from
0:05:09	if I have a single multicast feed
0:05:14	and I send it to a frame relay
0:05:18	it means that the 1 megabit per second feed
0:05:24	on that actual physical link.
0:05:26	The reason why is that we
0:05:30	that can be addressed to multiple Layer 2
0:05:35	So, this feature is called the
0:05:39	where we're basically tricking the Layer 3 process
0:05:43	in the thinking that the Layer 2 media is able to
0:05:51	Now, on a broadcast media,
0:05:53	we don't have this problem again because we can
0:05:59	Like the all F's address for Ethernet.
0:06:03	Now, this also means that the Layer 3
0:06:07	In the case of IPv4, this is what our
0:06:14	Where if a certain sender is trying to figure out what
0:06:19	whether it's be another host, or whether
0:06:23	the sender simply needs to
0:06:27	saying, "What's the MAC address
0:06:30	Then, whoever owns that IP address
0:06:34	should send a unicast reply
0:06:38	We're assuming that this address
0:06:42	because when I send the ARP request out,
0:06:44	it's going to the Layer 2 broadcast address.
0:06:48	So, everyone in the VLAN should receive
0:06:55	which means that if there is
0:06:57	they eventually should get it and reply.
0:07:01	Now, with the MBMA medias,
0:07:04	The reason why is that there's no Layer 2 address
0:07:12	Okay, technically, there is something in the
0:07:16	Frame relay originally
0:07:21	but the vast majority of the time,
0:07:24	So, it was theoretically possible but not
0:07:30	So, with a non-broadcast media,
0:07:32	the issue is actually the
0:07:35	We need to figure out what is the local Layer 2 address
0:07:45	So, in the case of frame relay,
0:07:48	that is mapping to some remote
0:07:54	Some MBMA medias do the remote
0:07:59	Example of the would be ISDN resolving
0:08:04	But in our case today for frame relay,
0:08:06	we are resolving the local Layer 2
0:08:12	This is why the protocol that's used
0:08:16	because it's the opposite
0:08:21	In Ethernet, IPv4 ARP says "I wanna know what's
0:08:29	Where with Inverse ARP, we're saying "What is my
0:08:37	Now, the problem we'll see with
0:08:41	is that it's only possible to send this packet to the
0:08:48	So, an Inverse ARP frame can only be
0:08:54	So, we'll see when we get into partially meshed
0:08:59	it's not possible for the spokes of the network
0:09:02	to resolve each other's addresses to Inverse ARP
0:09:05	if they don't have a directly connected PVC.
0:09:12	Now, regardless what type of MBMA we're talking
0:09:18	There's gonna be two general
0:09:21	that will control what the restrictions
0:09:26	And these types are multipoint
0:09:30	A multipoint interface simply means that
0:09:36	on the interface at the same time.
0:09:39	So, examples of this would be the
0:09:43	or multipoint sub-interfaces.
0:09:46	So, any interface that we're allowed to assign multiple
0:09:53	Since we have different
0:09:58	the router then needs to know
0:09:59	when I am building a frame to a
0:10:03	what is the appropriate Layer 2
0:10:08	So, we'll see that all multipoint interface
0:10:13	Whether we're doing this
0:10:17	or whether we're doing it
0:10:19	all multipoint interfaces in all
0:10:26	Now, the other variation would be point-to-point,
0:10:29	where a point-to-point interface is any type
0:10:36	Now, since there is only one Layer 2 circuit,
0:10:39	it means that we don't care
0:10:43	A good example of this
0:10:46	The PPP protocol by definition
0:10:52	It means that it can be only used if
0:10:56	The source and the destination.
0:10:59	This means that for PPP, we don't
0:11:03	because when I send a frame to the interface,
0:11:06	there's only one possible receiver. It's
0:11:11	Now, for multipoint MBMA interfaces,
0:11:14	point-to-point connections are going
0:11:18	A frame relay point-to-point sub-interface,
0:11:22	These links can only have one
0:11:27	which then implies they do not need
0:11:33	Configuration wise, this would mean
0:11:37	does not need either Inverse ARP
0:11:42	As long as we tell the router what is the
0:11:48	that is the address used in every
0:11:53	The key difference again being
0:11:57	since there can be multiple
0:12:00	the router needs to know which
0:12:04	when I'm sending a packet
0:12:08	So, it's the same logic that Ethernet
0:12:11	It knows that for this IP address, 1.2.3.4,
0:12:17	But for IP address 5.6.7.8,
0:12:22	So, it's a multipoint interface,
0:12:25	to figure out what's the Layer 2
0:12:30	Now, frame relay as a protocol itself,
0:12:34	it is MBMA, which means that we have
0:12:38	This again is only gonna be true
0:12:43	Again, point-to-point interfaces
0:12:48	The specific address that
0:12:51	is known as the "Data Link
0:12:55	The DLCI is the Layer 2 address in frame
0:13:01	and our directly connected neighbor.
0:13:04	So, within the frame relay network, the
0:13:09	It is considered a link local address.
0:13:14	So, link local addressing, similar to the
0:13:21	or the fe80 addressing in IPv6.
0:13:25	It means that for anyone
0:13:28	they don't care what my address is.
0:13:30	Because the only people that are using
0:13:36	Now, frame relay also supports
0:13:39	that runs between the DTE and the DCE,
0:13:45	And the DCE to DCE, which is the
0:13:51	This management protocol is the
0:13:55	that is used to tell the DCE devices, what is the
0:14:04	So, it's allowing us to do some
0:14:08	to make sure that if I send a frame out
0:14:12	that I can know with at least some degree of
0:14:19	Okay, that's what LMI mainly is doing
0:14:26	Now, configuration wise, the first step
0:14:31	is to turn the protocol on.
0:14:34	Normally, a serial interface will be
0:14:39	So, we would need to change
0:14:42	Once we enable the frame relay process,
0:14:45	the LMI type will automatically be detected
0:14:49	based on the type of frames that
0:14:54	So, we don't need to specify
0:14:59	The router will automatically detect this.
0:15:02	We can see this if we look at
0:15:05	It's gonna tell us what type we detected,
0:15:09	what are the number of errors
0:15:14	In the case of link status for frame relay,
0:15:18	the main serial interface in frame relay will
0:15:26	if we are receiving the LMI
0:15:31	If for some reason
0:15:34	or the LMI type does not agree
0:15:38	we would see that the
0:15:43	So, any line protocol down, either means
0:15:48	or in the case they are running frame relay,
0:15:56	Once we learn the LMI information
0:16:00	the LMI is gonna advertise us what are the circuit
0:16:05	and what is the individual
0:16:09	We can see this when we look at
0:16:12	That's the information
0:16:16	Now, we have four different status
0:16:19	In Show Frame Relay PVC.
0:16:21	The first being active, that means
0:16:26	or at least good between me
0:16:30	There can be some cases where
0:16:33	further in the cloud, or in the
0:16:35	the circuit is down, but if the
0:16:38	at least I know that it is good
0:16:42	If the circuit status is inactive,
0:16:46	it means that the number
0:16:49	but for some reason along the end-to-end
0:16:55	So, by default, the LMI protocol
0:17:00	between the DTE on one side
0:17:06	This means that no matter how many
0:17:09	the LMI keepalive keeps track of the
0:17:14	So, if I have a frame relay circuit that's
0:17:18	if I see the circuit status is active in Chicago,
0:17:24	If it's inactive, then, it's telling me that
0:17:28	but I don't really know what it is.
0:17:30	If the circuit status shows deleted,
0:17:33	it means that whatever number
0:17:37	is not what the switch is advertising.
0:17:40	The typical case for this is either you made a
0:17:47	where you used the wrong circuit number,
0:17:48	or in the Frame Relay Interface DLCI
0:17:53	So, circuit status is deleted.
0:17:54	It means that the DTE, who is the router...
0:17:57	is trying to use some value that
0:18:03	The last status, the static PVC, this
0:18:10	Typically, you would only see this last one
0:18:14	between two routers that are
0:18:19	Now, once we enable the encapsulation and
0:18:25	then, we need to tell the Layer 2 process,
0:18:29	what are the particular Layer 3 destinations that
0:18:35	So, this is gonna be a combination of logic
0:18:40	And the Layer 2 frame relay process.
0:18:44	So, we'll get into more detail about this
0:18:47	Especially when we look at
0:18:51	EIGRP over frame relay,
0:18:53	and multicast over frame relay,
0:18:55	there's a lot of Layer 3 issues
0:18:58	that end up being a problem in
0:19:03	that the higher level protocols don't understand.
0:19:07	So, there's actually some designs that you
0:19:12	because frame relay is a non-broadcast media,
0:19:14	and it doesn't support that
0:19:20	Now, when we do the resolution,
0:19:23	the goal here is to tell the router,
0:19:25	what is the local DLCI number that I need to
0:19:32	So, whether it's an IPv4
0:19:36	or whatever other protocol stack we're running.
0:19:39	Now, this resolution can happen two ways:
0:19:42	Either automatically through
0:19:45	or statically through the
0:19:49	In either case, wherever
0:19:52	we're gonna verify this by looking
0:19:56	So, this would be the same logic
0:20:00	It's showing us what are the
0:20:05	Now, the Static Frame
0:20:08	that would be the same
0:20:11	Where we're saying, "This particular MAC address is
0:20:18	Now, frame relay Inverse ARP is
0:20:23	once frame relay is on, and a supported
0:20:29	So, this means once you turn frame relay on,
0:20:34	the router will automatically
0:20:39	out all the circuits that
0:20:44	Certain protocols do not
0:20:46	like IP Version 6 and CLNS, which is a
0:20:54	In our case, since IS-IS is not within
0:20:58	we don't really need to worry about that.
0:21:00	Okay, but since IPv6 is,
0:21:03	we need to know that for any IPv6 configuration
0:21:09	we would be required to do a manual binding.
0:21:14	Because IPv6 does not support
0:21:19	So again, once we configure the protocol,
0:21:21	the Inverse ARP request is gonna go
0:21:27	We can configure the router
0:21:31	by saying No Frame Relay Inverse ARP.
0:21:33	We could also do this on a
0:21:38	But we cannot stop the
0:21:41	to an Inverse ARP request that it has received.
0:21:45	So, in some circumstances, we'll see
0:21:48	that we end up with
0:21:51	where the routers are sending
0:21:56	due to an error in the Layer 2
0:22:02	This means that in frame relay,
0:22:05	to make sure that the Inverse ARP reply comes
0:22:13	So, if I send an Inverse ARP request out,
0:22:15	and there is anyone who
0:22:18	in this case, IPv4.
0:22:20	They will reply with their address
0:22:26	Usually, for IPv4 ARP for
0:22:30	It's only true if you are running Proxy ARP would you
0:22:37	but Inverse ARP does not have
0:22:43	Once the dynamic mapping has been learned,
0:22:46	we'll see that it also support for the Pseudo
0:22:54	So, this means that if a
0:22:57	like an IP packet going to
0:23:01	is received at the frame relay interface,
0:23:04	it would be sent to all Layer 2 circuits
0:23:07	that have frame relay Inverse
0:23:11	Now, the static mapping statement
0:23:13	again is the same logic as a Static ARP Entry.
0:23:16	We're doing a manual binding between the
0:23:20	Syntax wise, this is the
0:23:23	followed by the protocol stack
0:23:27	with the destination addresses,
0:23:31	Or not the DLCI key word,
0:23:36	Okay, so when it says DLCI there,
0:23:40	Okay, then, we have
0:23:44	You technically don't have
0:23:46	but there's no reason that
0:23:49	Anytime you want to support either
0:23:54	over the frame relay circuit, you would
0:23:59	So this means for your IGPs
0:24:03	or for actual multicast routing with PIM
0:24:09	we would need to have the
0:24:13	Now, once we configure the static mapping,
0:24:16	it will override and disable
0:24:19	any dynamically learned mappings and
0:24:25	So, for example, if I configure a statement
0:24:29	1.2.3.4, 100.
0:24:33	I'm saying that for the destination address 1.2.3.4,
0:24:38	I'm gonna use circuit number 100.
0:24:41	This also means that on circuit 100,
0:24:44	I could no longer learn any dynamic
0:24:50	So, it is on a per-protocol and circuit basis.
0:24:59	Okay, there's a question, "The slide says Inverse ARP
0:25:04	Is that for the whole DLCI or
0:25:07	It's for the DLCI and a protocol pair.
0:25:11	So, if I were to do a static mapping for IPv6,
0:25:15	that would not disabled Inverse ARP for IPv4.
0:25:20	If I were to do an IPv4 mapping out circuit 100,
0:25:27	but not on any other circuits
0:25:32	So, unless we issue the No Frame
0:25:35	or the No Frame Relay Inverse ARP
0:25:41	this one here, this is gonna
0:25:45	Disable Inverse ARP completely for the protocol.
0:25:49	But again, the key is that
0:25:53	It does not disable the response.
0:25:56	So, if someone else in the network
0:26:00	the router will always respond and
0:26:06	This is why we can have some
0:26:10	if the router is receiving Inverse ARP requests
0:26:13	from people that are actually
0:26:17	So, we'll look at this a little bit today, and then in
0:26:24	Okay, the next thing I wanna
0:26:27	just Layer 2 frame relay is how the
0:26:33	where auto-install is basically a procedure
0:26:38	that has no configuration.
0:26:40	You plug in the interfaces whether
0:26:45	Turn the router on, it's going to try to automatically
0:26:52	Now, in order to do this,
0:26:55	the router needs to figure out an
0:26:59	to be used as a destination for the TFTP
0:27:05	So, the server can't send the packet to the router
0:27:10	So, the way the router does this is first by
0:27:15	Now, if it's an Ethernet interface, there's gonna
0:27:20	So, this means that the router will automatically
0:27:25	to try to get an address, and then try
0:27:30	For a point-to-point serial
0:27:36	it does this through the "Serial
0:27:40	Where with frame relay, it does
0:27:46	Now, the reason that I'm mentioning this
0:27:48	is that when the router boots up
0:27:53	it will automatically detect the encapsulation
0:27:58	learn the DLCIs through LMI,
0:28:01	and send a BOOTP request
0:28:06	Now, if the other side is not
0:28:10	meaning, they don't have the TFTP server set up,
0:28:15	it means that the router's process will fail,
0:28:18	and continue on to the normal operation
0:28:24	it says "Do you wanna terminate auto-install?"
0:28:27	Okay, that's what the router is talking about here
0:28:30	that it tried to get a configuration,
0:28:34	Okay, if you say yes, you'll see that it
0:28:38	depending on what particular
0:28:42	Now, for frame relay, the reason that this is
0:28:49	is that when the BOOTP requests fail,
0:28:53	the router maintains the Inverse ARP
0:28:59	To the address 0.0.0.0.
0:29:02	So, any time you look at the Show Frame Relay Map
0:29:05	and you see a mapping that goes to 0.0.0.0,
0:29:08	it means that the router tried to do the auto-install
0:29:16	The reason that this is an issue is that it's
0:29:21	So, if you have routers that are not supposed
0:29:26	but frame relay has resolved through Inverse
0:29:32	we'll see that we can exchange EIGRP updates,
0:29:39	and it's gonna screw up a bunch of things
0:29:44	So, the ends result of this is that if you get to the
0:29:50	and you see that the router
0:29:54	the very first thing you should do is
0:29:58	The reason why is that when the router
0:30:05	it stops the auto-install process.
0:30:09	The key is that when the router boots
0:30:12	then, it automatically start auto-install.
0:30:15	But once you save the config and
0:30:19	then it knows, "I already have a configuration,
0:30:23	Okay, there's no other way to
0:30:27	So, if you see it, that's the very
0:30:30	Otherwise, you're gonna have a
0:30:32	when you're trying to troubleshoot some
0:30:36	that's ultimately related to this
0:30:41	Now, the next variation that we have
0:30:46	this is the point-to-point sub-interface.
0:30:51	Again, the key with the
0:30:54	is that only one Layer 2 circuit
0:30:58	So, the router does not need to know what are
0:31:05	because no matter what packets
0:31:08	they're always gonna be using the
0:31:13	The only thing we need to do at
0:31:16	is issue the Frame Relay Interface DLCI
0:31:22	Now, we'll see that using the
0:31:25	this would be the preferred design
0:31:27	to fix Layer 3 or above issues that relate
0:31:36	So, if we were to run OSPF over frame relay,
0:31:40	the ideal design would be to use
0:31:45	and separate point-to-point subnets
0:31:51	Now, we'll see exactly why this
0:31:54	when we get into the details in the routing
0:31:59	Now, the different types of
0:32:02	again, we have the main interface, the multipoint
0:32:07	The Layer 3 to Layer 2 resolution
0:32:13	So, this means that no matter what
0:32:17	it's completely independent of
0:32:21	I can have a main interface and you
0:32:24	I can have a main interface you can
0:32:26	Okay, all of the combinations are supported.
0:32:28	As long as the Layer 3 to Layer 2
0:32:34	then, the frames are going to get encapsulated.
0:32:37	We'll look at the different show
0:32:40	from the frame relay process to figure out if there is
0:32:49	The next variation we'll look at configuration
0:32:57	Now, Partial Mesh basically means that
0:33:02	that do not have a full mesh of
0:33:08	So, in the case of Ethernet,
0:33:12	because any host can send a packet
0:33:18	just by using their Layer 2 address.
0:33:21	But with networks like frame relay and ATM,
0:33:24	unless the service provider has manually set up
0:33:29	you're not gonna be able to send
0:33:34	Now, you can send the packets indirectly
0:33:39	This is typical with the
0:33:43	Where we have one central site
0:33:44	that has Layer 2 circuits going to
0:33:48	Then, any of the spokes that wanna
0:33:51	the packets first needs to go into the
0:33:56	Now, the reason that this is an issue
0:33:59	is that the Layer 3 routing protocols and
0:34:04	have an issue understanding the difference
0:34:11	So, anytime that the Layer 3 subnet
0:34:14	does not map exactly one to one
0:34:19	we're gonna have design
0:34:24	One of these issues is related to
0:34:29	So, devices without a direct
0:34:33	cannot resolve each other with Inverse ARP.
0:34:37	So, when we're looking at the dynamic mappings,
0:34:40	if the routers don't have a PVC
0:34:44	they're not gonna be able to
0:34:47	So, Inverse ARP is a link local protocol.
0:34:51	I cannot receive a request in one circuit
0:34:53	and then forward it back out another circuit.
0:34:58	So, we'll see in an ideal world,
0:35:02	for any MBMA media type whether
0:35:08	we would always have an exact
0:35:14	to a point-to-point Layer 2 sub-interface.
0:35:18	So, this would then mean we don't need to
0:35:23	So, we wouldn't need the
0:35:26	or we wouldn't need the protocol
0:35:29	we would just assign the Layer 3 address
0:35:31	like the IPv4 address or the IPv6 address.
0:35:34	Assign the Layer 2 circuit number,
0:35:38	Then, the routing process would treat these
0:35:42	where two different circuits will have two
0:35:48	We'll see that there's certain
0:35:51	when a packet has to come in
0:35:56	Not just from a split horizon point of view,
0:35:58	but from an actual data plane point of view.
0:36:02	But again, we'll get into more details with this
0:36:05	But the overall point of this is
0:36:10	you would want point-to-point subnets that map
0:36:15	So, if I were to have a design where I had...
0:36:22	router 1,
0:36:23	router 2,
0:36:25	and router 3...
0:36:27	connected over frame relay.
0:36:30	Where router 1 is the hub, and
0:36:35	I would ideally want to configure on
0:36:42	We'll say, serial 0/0.1, serial 0/0.2.
0:36:46	Both of these are point-to-point.
0:36:49	Under there, we would have our IP address.
0:36:52	And we would have our
0:36:57	Same thing on router 3, we would have
0:37:00	with the IP address and the DLCI number.
0:37:04	Same thing on router 2.
0:37:09	So now, from a data place point of view,
0:37:13	if router 2 is trying to send packets to router 3,
0:37:16	they first have to be routed to router 1.
0:37:20	Then, routed back down to router 3.
0:37:24	We'll see in cases that router 2 and 3 think that
0:37:29	Based on the fact that they are
0:37:33	There's a bunch of control plane issues and data plane
0:37:39	Now, within the scope of the CCIE lab exam,
0:37:41	it's probably unlikely that they're gonna give
0:37:46	So, in the real world, you never have to deal
0:37:50	Just re-number the network so that your Layer 3
0:37:57	But you have a disconnect between
0:38:01	we're gonna have a bunch of design
0:38:05	So, we will talk about all of those
0:38:07	and see what are all the
0:38:10	but if you could fix it just by
0:38:13	you're gonna save yourself a lot

Now Viewing

CCIE Routing & Switching Advanced Technologies Class
Title:	CCIE Routing & Switching Advanced Technologies Class
Duration:	81h 59m
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!
$159/month	Add to Cart
Download this Course
$299.00	Add to Cart

Frame Relay

Create Bookmark