CCNA Security Certified!

Another notch on the CISCO totem pole!

On January 27, 2012, I received my CCNA Security certification!  It was tough and I still have a lot to learn, but that's what life is -- a process of learning.

CCNA certified!

Well, I am now CCNA certified!  What a battle it has been to find enough time required to study and mentally register this intense information while balancing work and most of all -- giving enough of my time to Becky, the true supporter and love of my life that has graciously allowed me the time to follow my dreams.

CCENT certified!

On July 8th, 2011 -- I became CCENT certified!  This is a huge relief and triumph as I have passed my first Cisco exam.  The time I have spent studying has truly paid off.

Security + Certified!

I took and passed the Security + Certification on April 22, 2011, of which I am very proud.  It's another check box checked off on the way to receiving my Bachelors and a better life for me and my family.

First attempt at L3 switching

I put the ip helper-address on the VLAN interfaces on S1, so that the PC and Mac can receive ip addresses from the DHCP server.

The big difference I see between my attempts of router-on-a-stick and L3 switching is that for L3 switching, you use the VLAN interfaces to assign IP addresses on the L3 switch as the gateways for the hosts in the designated VLAN.  

For router-on-a-stick, you create sub-interfaces (Fa0/0.10) on the router interface, assign IP addresses to those interfaces, set encapsulation dot1q on the sub-interface, because you are connected to a switch port that is trunking, and then you tell it what VLAN to forward. 

OSI MODEL

The OSI Model (Open System Interconnection)

The main troubleshooting structure in my opinion that is designed to:

1. Help software vendors create software that is inter-operable with any network.
2. Makes it easier for me and you to learn networking concepts and to create a basis for us to understand how data traverses the network.
3. Gives us a basic model of which we can troubleshoot from.

The reason for #1 and in me saying that in my opinion the OSI model is the main troubleshooting structure is that it breaks the layers down into several more layers than the TCP/IP model.  Though, it can be said that us as Networking professionals, really don't worry too much with troubleshooting above layer 3 anyway.  I will discuss the layer mappings between OSI and TCP/IP models a little further down in the post.  

The OSI model has 7 layers and is structured in a way to demonstrate data flow and to give us a structured approach to troubleshooting.  Now, the layers of the OSI burrito!

7 - Application Layer: This layer is where all the end user interaction happens and any protocol needing user attention, happens here.  Authentication also happens at this layer and the communication between a remote partner so that resources exist and that both ends agree on data integrity, privacy, and error recovery.  Some special things to note about this layer are: Authentication, Firewalls, SMTP/POP3, Telnet, HTTP, FTP/TFTP, RIP, and SNMP all happens at this layer. 

- Interfaces with the application
- Provides network access to applications

6 - Presentation Layer: This layer deals with how data is presented, the compatibility with the operating system, and to make sure that everything is in proper formatting, encrypted, compressed, and translated.  This layer also makes sure that everything is properly encapsulated for transmission.  Some special things to note about this layer are: Encryption, JPEG, ASCII, GIF, MPEG, MIDI, EBCDIC, TIFF all happen here. 

5 - Session Layer:  This layer is the manager of the two way communication between two remote hosts.  The session layer handles the creation, the maintenance, and tear-down of communication between those two hosts.  That's why this is called the session layer, because the overall communication is called a "SESSION".

- Logically keeps sessions separate

4 - Transport Layer:  This layer is responsible in establishing a logical end to end connection between two hosts and segments data received from the upper three layers.  This is where the magic happens!  The transport layer is responsible for making sure that data gets to the destination in the correct order and free of errors, so that it can be reassembled on the other host and make sense.  Some special things to note about this layer are: TCP/UDP, SPX, Positive acknowledgement and retransmission (PAR), Flow control, Windowing, SYN, ACK.
- Dictates how the data is sent
- Defines well-known services and ports

3 - Network Layer:   The network layer is sometimes called the routing layer.  This is the first layer of the three bottom layers that network engineers spend their time in.  There are two things that we are really concerned about in this layer and that is:

1. What valid paths exist from the local router to the destination?
2. What is the best and optimal path to get there?

Some special things to note about this layer are: IP, ARP, IGMP, ICMP, the logical path between A and B, Routers, and layer 3 switches.
- Provides logical addressing
- Finds the best path to a destination

2 - Data Link Layer:  Error detection is performed here through the frame check sequence (FCS), but is only checked and detected via the receiving host and is dropped if it doesn't match up, so there is no correction.  Some special things to note about this layer are: Switches, WAP, Cable modems/DSL, Ethernet, High Data Link Control (HDLC), Point-to-point protocol (PPP), Frame Relay, MAC address, and Bridges.

- Provides Physical addressing
- Ensures data is error-free (error detection, not correction)

1 - Physical Layer:   This is where the actual physical transmission of data occurs and the last step of encapsulation for the packets to be sent across the wire.  some special things to note about this layer are: Physical cabling, Pins, Connectors, Electrical current, Hubs, and repeaters.
- Provides access to the cable
- Electrical Signals, ones and zeros
------------------------------------------------------------------------------------------
The mapping between the two models (OSI and TCP/IP)

So as you can see, the OSI layer is separated into seven distinct layers while the TCP/IP model has chosen four.  The reason why I think the OSI model is more useful for troubleshooting is that it breaks down the troubleshooting process into an easier model with more levels and ways to better plan, separate, and attack each issue.

Let it begin!

So, it's been a wonderful holiday in which I've been granted tons of time to work on homework and studying.  I finally took some intense time away from my statistics class to work on some CCNA training.

I will start the on-going intense CCNA training starting in March through WGU, but I want to get some self-study time in before that.  The training material I have now for the CCNA is a combination of reading and video material.  Primarily, The Ultimate CCNA Study Guide by Chris Bryant of The Bryant Advantage.

I've been thinking about how I want to post the little tidbits of material that my brain can regurgitate into an easily readable format on this blog and the conclusion is that each post will have a specific subject about a certain topic.  That way it can be searched later or added to with further insight.

New blog, new start, and a new outlook on life!

Today is the start of a fresh new blog and outlook on life!

This blog is intended to be a personal page as well as a journal and training aid in gaining the supreme title of CCIE.

You might be wondering what CCIE means or even stands for.  CCIE to me is the top of the food-chain when you talk about Computer Networking.  CCIE is a certification from CISCO, who is the leading manufacturer of networking equipment and stands for "Cisco Certified Internetwork Expert".

I have been in IT for five years now doing Desktop Support for a local Community College.  It's a great job, but after a lot of soul searching, I have decided to take the Networking/Security path to a better future.  So it hit me, I better get my brain back in the game and go back to School.  I don't have a lot of free time on my hands to drive to and spend endless hours in a brick classroom, so I decided to enroll in Western Governors University to obtain a Bachelors of Science in Information Technology with an emphasis in Security.  Then onto a Masters in Information Security and Assurance.  I chose this School, because it's a School that can fit around my schedule and still be able to give me the training and knowledge that I need to succeed.  While obtaining a degree, I will gather numerous IT certifications (nine or more) to add to my resume.  Since I have been attending WGU, I have obtained my CIW: Associate and A+ certifications.  This January, I will embark on a wondrous journey to pass the CCNA (Cisco Certified Network Associate) Certification.  I am really excited about the training, the knowledge I will gain, and the feeling of taking another step in the right direction towards fulfilling my goal.

In regards to the CISCO certifications, they are ordered in the following:  CCNA, CCNP, and CCIE.  I will pass them in that order, but it will take years if not a decade.  That's why I created this blog, so that I could have a journal as well as a training tool to help me along the way.  This blog will be an expression of myself, an online pad to write down useful tips and tricks, and a record and compilation of what I've learned, so that I can better absorb the information and maybe help others that read this.  I hope that others will leave constructive comments, so that I too may learn from them.