It was the easiest test I’ve taken since I started preparing for the CCNA R&S Cert…
OK, maybe this comes across a bit arrogant, but that is not what I mean at all, let me explain.
I am not suggesting that the exam is easy, it is not. Anyone who is, or was preparing for a CCNA certification, needs to work hard at it because it is a well known fact that the exam is pretty demanding.
I mean, if you really prepared to pass the exam, and you do pass the exam… you know a lot about networking.
Continue reading CCNA R&S Certification Exam… a piece of cake…
On the last article, we mostly talked about Subnetting theory, however, subnetting is one of those topics which you don’t really understand until you practice, practice and… practice. I mean, you still need the theory of course, but you need just enough theory to get you started with the practice. While practicing, you are going to hear “click!” in your head… many times.
Continue reading VLSM and Subnetting Practice.
As you can imagine, there are many aspects you will need to take into consideration when putting together a network, specially if dealing with a large corporate network. It’s simply not the same, configuring a network for a small office with 5 employees than configuring a network for a corporate branch with 5000 employees.
Some of the concepts we need to consider when designing a LAN are very straight forward like physical space, cabling, power source, static IP addressing, etc. and some are more complex like flexibility, expandability, security, routing protocol implementation, dynamic IP addressing, IP sub-netting, etc. Basically, the complexity of a network is directly proportional to the size of the network itself.
Luckily, we are getting ready for the CCNA, and its scope states; “…skills required to install, operate, and troubleshoot small to medium-size enterprise branch networks”, so let’s keep this in mind.
Continue reading 1.2 Select the components required to meet a given network specification.
Terms you need to understand.
Broadcast: In this case, a Data-Link layer (Layer 2) message sent to ALL devices attached to the same network segment.
Collision: When more then one device transmit data at the same time on shared media, the packets collide, data becomes corrupted and after a random period of time, devices have to re-transmit the data.
Broadcast Domain: All devices that a Broadcast message reaches at the Data -Link layer within a network is called a Broadcast domain. A network can have more then one Broadcast domain and a Broadcast domain is delimited by devices that stop Broadcast messages.
Collision Domain: Anywhere within a network where a Collision can occur. The limits of a Collision domain are marked by those devices that break up Collision Domains.
Continue reading Broadcast and Collision Domains.
Unicast Addresses: Unique-Local.
Before we talk about Unique-Local Addresses (ULA), let me tell you about Site-Local addresses; it was deprecated in favor of the ULA back in 2004 because the term “site” was too ambiguous, no body agreed upon a clear definition of the term “site”; what was considered a “Site”?
Also, the provability of Site-Local address being globally unique were no that high, as opposed to ULAs.
ULAs are meant to be routed within an organization’s LAN or even WAN, but they are not routable over the public network (Internet), hence, you can think of ULAs very much as IPv4’s Private addresses.
Continue reading IPv6 for future CCNAs (+), Final Part.
In IPv6 for future CCNAs – Part I, we ended the article talking, very lightly, about IPv6 address types. Let´s go ahead and dig deeper into the concepts.
To recap, the IPv6 address types are:
One-to-one communication. Unique address assigned to an interface, a packet sent to a Unicast address will be received by one single interface. There are several types of Unicast addresses:
Hi guys, this post got awarded “Best Publication” at the Cisco Support Community”! Thanks a lot.
A little bit of history:
Before we talk about Spanning Tree Protocol, let’s organize the different variants of STP. The original STP was developed by Radia Perlman while working for DCE back in 1990. At this time there were no switches yet, only bridges, but because bridges and switches technically do the same job -only switches do it more efficiently and have more features- they suffer from the same issues. Also, because STP was developed during a time when therewere only bridges, the terminology used in STP, even today, makes reference to bridges a lot (Root Bridge, Bridge-ID, etc.). So, when you read about STP from different sources, remember that the terms Switch and Bridge might be used interchangeably.
Continue reading Spanning Tree Protocol, from a future CCNA`s perspective.