In the last couple weeks I observed several discussions on some of the mailing lists in regard to the old question – “Why are we using Loopback interfaces for iBGP peering in MPLS”. Do we really have to?
In the last couple weeks I observed several discussions on some of the mailing lists in regard to the old question – “Why are we using Loopback interfaces for iBGP peering in MPLS”. Do we really have to?
After a long process of updating our entire CCIE Voice product portfolio, I’m pleased to announce that our CCIE Voice Blended Learning Solution is now 100% completed and shipping! The Volume 2 Video Tutorials and Audio on Demand are now shipping. The Audio should be in your Member’s Area if you’ve purchased the Audio on Demand. All Voice BLSs will be shipped out over the next week.
Regards, Wayne
I often come up with ideas for my posts based on questions I have from my students. In a CCIE Security 5-day ILT I had a student ask me the question: Does the ASA use a config-register like a router does?
In today’s blog we are going to take a look at QoS on the Catalyst 3560 platform – the only switch we need to be concerned with in the CCIE R&S lab. QoS on the 3560 is quite an elaborate topic. This article is not designed to teach you every possible command and option there is to know, but is designed rather to take a look at the most important aspects that are important to understand from the perspective of a CCIE R&S candidate. The ultimate resource for Catalyst 3560 QoS information is of course the 3560 software configuration guide. We will first look at the general QoS model, and then take some time to break apart each section. I won’t lie to you guys — 3560 QoS is an intense topic for most people. This blog will be lengthy, but I will try to keep it to the most important things. 10 or 11 pages is certainly probably more attractive than picking it out of the 1300 page configuration guide yourself : ) Hopefully after reading this blog you will have a much clearer understanding of your options when dealing with 3560 QoS.
