Archive

Posts Tagged ‘bcmsn’

Cisco CCNA / CCNP / BCMSN Exam Review: Trunking And Trunking Protocols

February 10th, 2010

To earn your CCNA or CCNP certification, you’ve got to understand the basics of trunking. This isn’t just a CCNA topic - you must have an advanced understanding of trunking and etherchannels to pass the BCMSN exam and earn your CCNP as well. Before we address those advanced topics, though, you need to master the fundamentals!

A trunk allows inter-VLAN traffic to flow between directly connected switches. By default, a trunk port is a member of all VLANs, so traffic for any and all VLANs can travel across this trunk. That includes broadcast traffic!

The default mode of a switch port does differ between models, so always check your documentation. On Cisco 2950 switches, every single port is in dynamic desirable mode by default, meaning that every port is actively attempting to trunk. On these switches, the only action needed from us is to physically connect them with a crossover cable. In just a few seconds, the port light turns green and the trunk is up and running. The command show interface trunk will verify trunking.

How does the receiving switch know what VLAN the frame belongs to? The frames are tagged by the transmitting switch with a VLAN ID, reflecting the number of the VLAN whose member ports should receive this frame. When the frame arrives at the remote switch, that switch will examine this ID and then forward the frame appropriately.

There are two major trunking protocols you must understand and compare successfully, those being ISL and IEEE 802.1Q. Let’s take a look at the details of ISL first.
Read more…

CCNP Certification / BCMSN Exam Tutorial: QoS Service Types

October 24th, 2009

To pass the CCNP exams, you’ve got to master Quality of Service, and the first step in doing so is knowing the differences between the different QoS types.

Now this being Cisco, we can’t just have one kind of QoS! We’ve got best-effort delivery, Integrated Services, and Differentiated Services. Let’s take a quick look at all three.

Best-effort is just what it sounds like - routers and switches making their “best effort” to deliver data. This is considered QoS, but it’s kind of a “default QoS”. Best effort is strictly “first in, first out” (FIFO).

An entire path from Point A to Point B will be defined in advance when Integrated Services are in effect. Integrated Services is much like the High-Occupancy Vehicle lanes found in many larger cities. If your car has three or more people in it, you’re considered a “priority vehicle” and you can drive in a special lane with much less congestion than regular lanes. Integrated Services will create this lane in advance for “priority traffic”, and when that traffic comes along, the path already exists. Integrated Services uses the Resource Reservation Protocol (RSVP) to create these paths. RSVP guarantees a quality rate of service, since this “priority path” is created in advance.
Read more…