Best Of
Re: I have always liked CBTNuggets
Any mentions of CBT Nuggets in an INE Forum will cause the forum to self-destruct within 30-seconds. Please move away from your computer. 
kbogart
IEOC Leaderboard Giveaway
Welcome to the new IEOC!
The IEOC Forum is an online community of network engineers and IT professionals. This is a great resource to use to start a discussion related to a specific technology, certification track, or tool. It is also a good opportunity to get your questions answered by others in this industry.
Some new features include:
• Mobile-friendly interface
• New leaderboard to recognize top contributors
• Ask a question and select the best response (drop down menu next to New Discussion)
• Community moderation to help control content
• Updated navigation & search features for easy topic/discussion search
• New community ranking system
We will also be awarding exciting prizes to the top 3 leaders on the leader board for the month of June.
Earn points by answering questions, earning badges, and other users reacting to your posts.
Monthly Prizes for Top Contributors
First Place Prize ($1400 value)
• Lenovo P 51 S Laptop
• Intel Core i7-7500U
• Windows 10 Pro, 32GB DDR4 Memory
• NVIDIA Quadro M520 - 2GB DDR5
• 500GB - 7200RPM Hard Drive laptop
• Plus a Swag bag of INE merch 
Second Place Prize ($800 value)
• Fluke [email protected] Network Cable Tester with Tone and Probe kit cable tester
• Swag bag of INE merch
Third Place Prize ($200 value)
• Virtual Internet Routing Lab subscription for 1 year
• Swag bag of INE merch
sneely
BGP Quick Guide : how to clear the BGP routing table, and speedup the convergence
it's may be a good practice to clear the routing table to speed up the BGP table Convergence process, but how ?
well there are plenty of options,
1) Hard clear of the neighbor :
commands:
- clear ip bgp <A.B.C.D> (ex, R1#clear ip bgp 1.2.3.4 )
- clear ip bgp * (* = all neighbors and not just one.)
this option clears the BGP neighbor relationship (removes the neighboring relationship then negotiate it again. )
this option may be Okay for the exam environment , but this may never be the best solution the real environment , why not ??
well , because the BGP internet table might be a 100's of thousands of Paths (IP addresses) , so if you hard clear the neighbors , you will lose all your routes and neighboring relationship, and will have to wait for BGP to renegotiate the neighboring relationship.
2) soft Clear :
commands:
- clear ip bgp * in (clears only inbound updates, asking the neighbor to send updates again)*
- clear ip bgp * out (clears it's outbound updates, sending the neighbor newer updates )
- clear ip bgp <A.B.C.D> soft (this command clears both inbound and outbound updates)
- clear ip bgp <A.B.C.D> soft in (clears only inbound updates, asking the neighbor to send updates again)*
clear ip bgp <A.B.C.D> soft out (clears it's outbound updates, sending the neighbor newer updates )*
soft clear is basically a clearing of the routing table either inbound or outbound (performing what is called a "Route Refresh"), requesting newer updates from the neighboring BGP table (when used inbound) or sending newer updates from our Local BGP table to our neighbors (when used outbound)
Note: there's nothing special about the outbound behavior other than what i explained
Inbound Behavior explained in depth :
(the previous description of soft reconfiguration is the default behavior when the "soft-reconfiguration inbound" feature is NOT activated)When soft-reconfiguration inbound is activated :
when this option(or feature) is activated, the router will create a backup of the routes received from his neighbor(s) before applying any filters or features to those routes. (let's call this backup table the "SOFT TABLE")
so when you initiate a soft clear to the neighbor(s) (as shown in the commands above) then the router initiating the command will do the following steps
- check the if there are any filters or route-maps toward that neighbor.
- instead of sending a request of a refresh(asking the neighbor for updates
again,hence Route-Refresh), the route will instead only use his "SOFT TABLE" and
apply those filters(from step one, if existed) to the routes in the "SOFT TABLE"
now the million dollar Question : HOW DO I ACTIVATE soft-reconfiguration inbound ?
simple, here's how
enable
configure terminal
router bgp
neighbor <A.B.C.D> soft-reconfiguration inbound
*Disclaimer :
although there are more clear options for the BGP protocol, i have only describe the protocols relevant to the CCNP Blueprint, or CCIE for IPv4 Address-family.
Bugazia
Re: Dynamic Trunk Protocol
before i give you a more precise Explanation, let's briefly discuss the theory of How Trunking works :
NOTE: I strongly recommend that you read my asnwer step by step to get a deeper understanding, and ultimately solve your Answer, once and for good, have a nice Reading 
let's say that we have two Switches : SW1 and SW2 conneted to each Other through Fa0/1 (as Shown in Fig.1 below)
Fig.1
What's Trunking?
Trunking is a method of Tagging (or Marking) the Frames Between Switches, were the Tag is the Vlan Number from the Source Interface of that Frame , so that way we can pass Frames from Multiple Vlans through a Trunk Link .
What's a Trunk Link ?
a Trunk Link is a Link that doesn't Belong to any Vlan (you can think of a Trunk Link as an Unbiased Link that accepts any Vlan regardless)
for example between SW1 and SW2 if we had that Link (FA0/1) in Vlan 10 , then FA0/1 Links will only forward the Vlan 10 frames (frames between H1 and H3 which are in Vlan 10) , on the other hand , if we put F0/1 links in Vlan 20 then it woould only forward frames between H2 and H3 (which are in Vlan 20).
but what if we wanted to forward Packets from Both Vlans (Vlan 10 and Vlan 20 ) between FA0/1 Links ?
this's where Trunk Links come into Play, Trunk Links allow for Multiple Vlans to be passed through the Links, by Tagging the frames with the Vlan Number from the interface that Initiated the Frame (the source of the frame), and then send it to the other side of the Link (FA0/1 in this example) so when the other side recieves the frame with a tag of a specific Vlan Number , it will effectively send that frame only to interfaces that has joined the Vlan (and other Trunk Links if existed)
for example, in Fig.1: if we set FA0/1 between SW1 and SW2 to a trunk Link , and then H1 Send a Broadcast Frame (a Frame with a destination of FF:FF:FF:FF:FF:FF) the following steps will happen : (keep an eye on Fig.1 Throughout this example)
1. H1 sends a frame to FF:FF:FF:FF:FF:FF (to the Broadcast Address) out it's interface towards SW1.
2. SW1 receives the frame (with a destination of FF:FF:FF:FF:FF:FF ), and because it's a Broadcast destination SW1 checks if it has any other interfaces in Vlan10, and it realizes that it has no other interfaces in that Vlan, so it checks if it has Trunk Interfaces.
3. SW1 finds out it has a Trunk Link ( after initiating the command: SW1# show interfaces Trunk ) whichs is FA0/1 , so it Tags (Marks) the Frame with a value of 10 (hence, Vlan 10) and floods the packet out that interface to SW2.
4. SW2 Receives the Frame sent from SW1 and (because it's a Trunk Link) it checks the Vlan tag in the Frame, it realizes that (Vlan Tag = 10 ) the Frame Belongs to Vlan 10.
5. SW2 does a look up and checks if it has any more Interfaces that are in Vlan 10 or are a Trunk, and it realizes that FA0/10 is in Vlan 10.
6. SW2 removes the Tag (the Value of 10) from the Packet and Floods the (sends the Broadcast) Frame out Interface FA0/10 to H3.
7. H3 receives the frame on it's Interface and checks the Destination address and realizes it's a Broadcast Frame, so it automatically accepts the frame (because all Hosts accept the Broadcast address frames by default)
NOW to answer your Question:
now that we have discussed the basic theory of Trunking, and had a basic detailed example of how it works, let's briefly discuss the Types of Trunk :
A ) in General there're two Types of Trunks (or Trunk encapsulations to be more precise..) :
1. ISL (Inter-Switch Link) Trunks: those are the First Type of Trunk encapsulation ever created, by Cisco ,for Cisco Devices (Cisco Proprietary ).
2. 802.1Q Trunks: also known us Dot1q, which are the Industry's standards (hence, are used by every vendor, Cisco or non Cisco devices..)created by IEEE organization, this type is now the commonly deployed trunking method, and is the Cisco Recommended way as well.
one point to keep in mind here is that the Trunk method in one Switch must match on the other side of the Switch on the Link between them (for example in Fig.1 the FA0/1 Link between SW1 and SW2, should either be Encapsulated with ISL or Dot1q), so we cannot have one side of the Link running ISL and the other Side Running Dot1q.
NOTE : i have only gave you a brief introduction of the two trunking Types, just to serve as an Introduction to what is to follow.
B ) Trunking Methods :
now let's Discuss the two methods that we can use to configure our trunks, which there are two ways:
1. Static Trunks:
as the name implies, this method is Static , so you basically just enter the Interface on which you want to change to a trunk and statically set it as a trunk.
Drawback to this method : if the other side is set as an Access Link(a link that belongs to one Vlan only) then we will have problems on the Link, so we have to be very careful.
how to configure it:
for example between SW1 and SW2 :
!__SW1:
enable
configure terminal
interface Fa0/1
switchport mode Trunk
end
!
!__SW2:
enable
configure terminal
interface Fa0/1
switchport mode Trunk
end
this trunking method is sometimes called the On Mode (because we have to set the Trunk method On Manually )
NOTE!: Notice that we used the configuration on Layer 2 Switches (like 2950, or 2960
Switches..etc), where the encapsulation method defaults to 802.1Q (Dot1q) encapsulation.
in Layer 3 Switches (like Catalyst 3550, or 3560,and 3750..etc) we will have to Manually set the Trunking method (using the interface command : Switchport trunk encapsulation dot1q)
so if SW1 and SW2 were to be Layer 3 switches, thenour configuration would be the following :
!__SW1&SW2:
enable
configure terminal
interface Fa0/1
switchport trunk encapsulation dot1q
switchport mode Trunk
end
2.Dynamic Trunks:
as we discussed earlier in Static Trunks, that the issue with static trunks is that they are static (hense, are more prone to Human Mistakes), one problem might be that a network engineer sets one end of the Link as a Trunk port, while leaving the other side as an Access port.
to solve this Static, sometimes problematic issue, Dynamic Trunks were Created:
as the name implies, Dynamic trunks negotiate the Trunk Type (802.1Q or ISL) and the Link Type (Access port or a Static Port) Dynamically .
but how does that happen ?
Dynamic Trunking send a frame called DTP (Dynamic Trunking Protocol ) frame,
which informs the other side of the link that it wants to become a Trunk.
There are two Types of Dynamic Trunks:
a ) Dynamic Desirable: this type means that the Switch's Interface wants to become a Trunk,so it sends a DTP frame to the other side asking it to become a Trunk Link, if the other side of the link sends a reply, then the Link becomes a trunk, else if the other side does not send back a reply, then the link becomes an Access Link.
b ) Dynamic Auto: this type means that the switch's interface does not mind becoming a Trunk, but it's NOT Motivation to do so, what do i mean by "NOT Motivated to do so" ?
it means that the Auto Link will not send DTP frames, asking to become a Trunk. instead it will just listen for DTP frames, and if it receives one, then it will become a Trunk port, else if it doesn't receive a DTP frame, then it will become an Access link. so basically Dynamic Auto is almost the same as Dynamic Desirable, only that it does NOT send DTP Frames.
NOTE: Effe
CONCLUSION:
Effectively, we then Have
Bugazia
