Earlier this week Sony announced that it will stop making the 3.5 inch floppy disk March 1 2011. The disk first appeared in 1982 with 264KB formatted. When I bought the Amiga Computer in 1988 It sported a 720k 3.5 inch drive, later on I moved on to a 386 IBM compatible with 1.44MB 3.5 inch drive allowing for the latest HD = High Density floppies.. Later years we saw the 3.5 inch grow to 2.8 MB (wish i rarely saw and truthfully don’t think they even took off) .
I moved on to the 120 MB zip disk, which i still have a few today. It’s funny just last month I found a box of old floppy disks from the mid 90’s. Going through the disks was traveling back in time, I found old word docs, Viso drawings and some digital pics that were save in 320x 240 resolution.
WOOT. Most of the people I talked to about this thought that the production of floppy had already stopped years ago. Desktops and Laptops have not included a floppy drive for sometime, but if you administer a server you are familiarized with the old “recovery disk” ; Linux and Microsoft servers both use them.
Flash drives are here to stay but I don’t think that I will be finding a flash drive still in good condition and able to retrieve files that is 15 years old. I heard to many horror stories of flash drives failing after a few years, Perhaps has they mature in the future they will become more durable.
Yesterday I received my new CCNP books from Cisco Press. Surprisingly the price was not that bad what I got. All three courses, 642- 902, 813 and the 832. I opt for Certs Kits for each as well.
The complete course was around $250 which includes the “Official Certification Guides” , Cert Kits and shipping.
The Cert Kits includes a Quick Reference booklets, flash cards (found online) and a DVD. Each DVD in the same familiar format as the the Video Mentor series is, each with an introduction and roughly 5 to 6 hours of video, each covering the the material talk about in the Certification Guides.
This is makes this series stand out is that the Cert Kits complement the Cert Guides. I would recommend that you buy them both. While scanning through the new material I notice that this time Cisco is really pushing hard on the routing and switching. They have left a lot of the VOiP and security out, which was found in the ONT (642-845) and ISCW (642-825) tracks.
Just received our first Juniper router, a J2300; this will be added to our lab along with the Extreme Summit and the rest of Cisco gear. At first glance the J2300 looks like any other device that will fit a 19in rack. The first thing I had to do was pop the top off and see what made this tick. As you can see from the following picture there not a whole lot in here. The box appears rather empty, I did notice a beefy processor and a standard compact flash.
The power supply is 250watt, not much going on here, than again you really don’t much to drive this thing.
root@J2300> show version
JUNOS Software Release [7.1R1.3] (Export edition)
I’ll continue my updates through the month as I slowly configure the router. One thing I did notice is that you realy dont need to console cable, the router has it own built in management web GUI that is connected to 192.168.1.1. The code DOES not look like you typical Cisco config, it looks more like programmers code, like C, perl or PhP.
The Juniper 2300 will be a challenge that I look forward to. Check back for more updates on the J2300.
Just revived an interesting email from Global Knowledge on troubleshooting.
This is subject where I find that new upcoming engineers are lacking in the fine art of effective troubleshooting. It is real easy to become a “parts-engineer” in today’s throw -it-away and replace society. However with the economy on stand still, most companies are reluctant to take that approach, they would rather “configure-it-out”.
Troubleshooting is not something you can easily read from a book, it must be physical learned. you can find that guides like the one blow may give you a foundation.
Gather the facts: This process is the corner stone of all the other processes rely on. First of all, refer to previous trouble tickets to see if this particular problem has occurred in the past and what methods were used to correct it. If this is the very first time, determine if changes were made to the system (i.e., IOS or other application upgrades). Interview user(s) who are affected by the problem and see if this just recently occurred or has been occurring over a period of time. Then review any protocols that may be involved with the problem to understand how they normally function. Pull any necessary trace files or dumps and analyze the traces for abnormal behaviors and you may have to execute debug commands when needed. Also topology diagrams are critical in helping to isolate the problem.
Read the complete article here here…