Can hardly believe I am almost ready to graduate. The last three semesters have been a blur and I am sure if you think its all summed up in the several blog posts so far that it probably was but alas I assure you that working full time and studying has left me little time to post.

This however excites me to much to keep it to myself. I have finally taken the initive to draft and build a home IT lab that will allow me (and a select few who pay tribute in the way of pizza and Mt Dew) the ability to perfect the things we have learned thus far with hands on practice that dont involve driving to the campus lab everytime we need a hacker fix.

The foot notes on this I think are self explanatory but long story short its designed to practice for certification (CCNA, MCITP, LINUX+) and also be fully scalable to grow as I head into the advanced program later this year.

If anyone happens upon this and wants to comment feel free to chime in on the comments (you will be the first). Right now time is against me but I have all the equipment at my house and as soon as spring break hits and my vacation from work starts you better believe I will be wiring this bitch up.

Pics will follow when I am done. Hope you enjoy.

My days in semester 3 of the Cisco Networking Academy are drawing to a middle, in just a few hours I will have to take a midterm skills final that will test my knowledge of the Cisco VLAN Trunking Protocol (or VTP), so before I jump into that I will lay down what I have learned here.

VTP is Cisco propritary, Juniper and other switches might have equivlent commands but VTP only works on Cisco equipment. VTP basically advertises and synces information regarding VLANS to all switches on a network or to be more thorough, all switches in the same VTP domain.

SWITCH(config)# vtp domain YOURDOMAIN

Cisco switches running VTP can be configured into one of three modes (that I know of so far) and they are; server, transparent, and client.

SWITCH(config)# vtp mode server

This is the default VTP mode. A VTP domain must have atleast one switch configured as the VTP server so that information regarding VLANs can be propagated to other switches in the domain. On a server you can create, add, edit, and delete VLANs. Any of these changes are sent out to other switches on a VTP domain.
SWITCH(config)# vtp mode transparent

Switches running in transparent mode are said to not participate in the domain, and while that is technically correct they do play a part as a forwarding device between server switches and clients.
SWITCH(config)# vtp mode client
Client switches listen for updates from other switches via VTP advertisements and update their VLAN configs accordingly. This is dependent on a connection to a switch running VTP server mode. Also it is not possible to create, add, delete or edit VLANs on the client.

This is just the very tip of the iceburg regarding VLANS. I have to say that semester 3 cisco is by far the most interesting instruction I have had to date. The content is well writen and presented very clearly, where at times transparent concepts from previous semesters (such as how different routing protocols achieve network convergence) were clear as mud. Love this class, learning alot, wish I had time to write more.

I have been exposed to Cisco routers for some time now. Something that has always bugged the hell out of me is that every time an interface farts, coughs, or burps the IOS by default floods the CLI with the interfaces thoughts and feelings and consequently causing you to possibly slip up a command.

no logging console tells the interfaces in the back seat to shut up all together and let you drive the router. Some people have a problem with this and I can see how you might miss some important information regarding interfaces and overall connections in general but I find that if (and I hope your not forgetting to) check the interfaces and config before saving it to make sure everything is up and running then you probably wont miss anything important.

logging synchronous  lets the router express it's feelings about your relationship and complain about the other routers and not cut you off when you are entering network addresses by moving the input cursor down a level to make room for the routers complaining. It's the command that most admins agree on I guess, and is probably the option Dr Phil would choose if he were in this business.

I for one hate those updates, have found them more annoying than informative, and prefer to turn them off all together. Well, back to packet tracer labs. Just needed to vent.

 

During my second semester as a CIT major one of the things we had to get used to doing was learning the different debug and show commands available to us in different privilege modes on the routers. One thing that made all that a little bit easier was the do command.

The command can be used in privilege mode to force the router to do some commands otherwise restricted to EXEC mode.


ROUTER1(config)$sh run                 
                  ^
% Invalid input detected at ‘^’ marker.

ROUTER1(config)do sh run

Building configuration. . .

So as you can see no hoping back and forth between config modes. The only limit my research yields to do command to is using it to change the current config mode itself (it cannot be used to initiate the config t command.)