The decision to attend a computer training school is one of the most important you'll ever make, and even more important is which one to attend. Asking the right questions can give you an idea of whether a given IT school is a good investment. An earlier article I wrote on this subject was so popular that I thought I'd offer some more advice on the questions to ask before you write that check or take out that loan.
If the school offers a placement service, ask to talk to the people working in that department and ask them how they go about placing graduates. Most schools offer a list of companies that they've placed students with. Get this list and start calling some of these companies. Ask to speak to their HR department, and ask them for their opinion of the school. Even if they don't say a lot, their tone of voice can speak volumes.
Ask to meet some of their teachers, and don't be afraid to ask them how long they've taught at that particular school. If the average teacher has been there a while, that's a good sign. If there seems to be quite a bit of turnover at the school, that's not as good a sign.
Another key area is the availability of the computer labs during class and after the class is over. Speaking from experience, I can tell you that getting hands-on experience with the various software and hardware you'll be working with in the field is the #1 way to get ahead - just reading books won't do it. If you're taking a router class, does the school have real routers for you to work on? If you're taking a PC repair class, are there plenty of PCs for everyone in your class to work on, or do you have to share?
You want classes that offer hands-on experience during class, and you should be able to get into the computer labs after class. You may not be able to use the labs at night if the school offers night classes, but again I speak from experience - the time you spend in the computer labs after class is just as valuable as the time you spend in class. Make sure the labs will be available after class - and then get in there and work!
Showing posts with label class. Show all posts
Showing posts with label class. Show all posts
Friday, December 26, 2008
Computer Training School Tutorial: Know Your Instructor
Making the decision to attend a computer tech school can be one of the best decisions of your life. Another great decision is to tap a hidden wealth of knowledge that is right before every student at schools such as ECPI and ITT, but very few students take advantage of it.
When you're attending a computer training school, you must avoid the mentality that some other students will have - "I gotta go to school, I gotta be here, I can't wait to leave and go home". When you're preparing for a career working with computers, you've got to take advantage of every learning experience you can get, and that includes getting to know the most valuable resource at your school - your teachers!
Your teachers have busy schedules, but it was my experience that every single time I asked for help or had questions outside of class, my teachers went the extra mile to help me. I’m sure yours will do the same for you, but you have to let them know you want that help!
At your tech school, you must develop the skills and work ethic that you will use to succeed in the IT field. By staying after class, working overtime in the computer labs, and getting to know your instructors, you'll be astonished at the additional knowledge you can pick up. Almost any good teacher is going to have real-world experience, and you need to draw on that knowledge. Having lunch with an instructor is another great idea, as it allows you to get to know them away from the classroom.
Part of success in any field is making contacts for the future. You may not be in the IT field yet, but you should already be getting to know people with IT experience - and who better than your teachers? Besides, they hear about job openings all the time from friends, and the more you stand out from the crowd, the more likely you are to be remembered for such opportunities!
When you're attending a computer training school, you must avoid the mentality that some other students will have - "I gotta go to school, I gotta be here, I can't wait to leave and go home". When you're preparing for a career working with computers, you've got to take advantage of every learning experience you can get, and that includes getting to know the most valuable resource at your school - your teachers!
Your teachers have busy schedules, but it was my experience that every single time I asked for help or had questions outside of class, my teachers went the extra mile to help me. I’m sure yours will do the same for you, but you have to let them know you want that help!
At your tech school, you must develop the skills and work ethic that you will use to succeed in the IT field. By staying after class, working overtime in the computer labs, and getting to know your instructors, you'll be astonished at the additional knowledge you can pick up. Almost any good teacher is going to have real-world experience, and you need to draw on that knowledge. Having lunch with an instructor is another great idea, as it allows you to get to know them away from the classroom.
Part of success in any field is making contacts for the future. You may not be in the IT field yet, but you should already be getting to know people with IT experience - and who better than your teachers? Besides, they hear about job openings all the time from friends, and the more you stand out from the crowd, the more likely you are to be remembered for such opportunities!
Thursday, December 25, 2008
Cisco CCNP Certification / BCMSN Exam Tutorial: Writing QoS Policy
QoS - Quality of Service - is a huge topic on both the BCMSN exam and real-world networks. QoS is so big today that Cisco's created separate specialist certifications that cover nothing but QoS! It can be an overwhelming topic at first, but master the fundamentals and you're on your way to exam and job success.
If you work with QoS at any level - and sooner or later, you will - you've got to know how to write and apply QoS policies.
Creating and applying such a policy is a three-step process.
1. Create a QoS class to identify the traffic that will be affected by the policy.
2. Create a QoS policy containing the actions to be taken by traffic identified by the class.
3. Apply the policy to the appropriate interfaces.
If the phrase "identify the traffic" sounds like it's time to write an access-list, you're right! Writing an ACL is one of two ways to classify traffic, and is the more common of the two. Before we get to the less-common method, let's take a look at how to use an ACL to classify traffic.
You can use either a standard or extended ACL with QoS policies. The ACL will be written separately, and then called from the class map.
SW1(config)#access-list 105 permit tcp any any eq 80
SW1(config)#class-map WEBTRAFFIC
SW1(config-cmap)#match access-group 105
Now that we've identified the traffic to be affected by the policy, we better get around to writing the policy! QoS policies are configured with the policy-map command, and each clause of the policy will contain an action to be taken to traffic matching that clause.
SW1(config)#policy-map LIMIT_WEBTRAFFIC_BANDWIDTH
SW1(config-pmap)#class WEBTRAFFIC
SW1(config-pmap-c)#police 5000000 exceed-action drop
SW1(config-pmap-c)#exit
This is a simple policy, but it illustrates the logic of QoS policies. The policy map LIMIT_WEBTRAFFIC_BANDWIDTH calls the map-class WEBTRAFFIC. We already know that all WWW traffic will match that map class, so any WWW traffic that exceeds the stated bandwidth limitation will be dropped.
Finally, apply the policy to the appropriate interface.
SW1(config-if)#service-policy LIMIT_WEBTRAFFIC_BANDWIDTH in
Getting your CCNP is a great way to boost your career, and learning QoS is a tremendous addition to your skill set. Like I said, learn the fundamentals, don't get overwhelmed by looking at QoS as a whole, and you're on your way to success!
If you work with QoS at any level - and sooner or later, you will - you've got to know how to write and apply QoS policies.
Creating and applying such a policy is a three-step process.
1. Create a QoS class to identify the traffic that will be affected by the policy.
2. Create a QoS policy containing the actions to be taken by traffic identified by the class.
3. Apply the policy to the appropriate interfaces.
If the phrase "identify the traffic" sounds like it's time to write an access-list, you're right! Writing an ACL is one of two ways to classify traffic, and is the more common of the two. Before we get to the less-common method, let's take a look at how to use an ACL to classify traffic.
You can use either a standard or extended ACL with QoS policies. The ACL will be written separately, and then called from the class map.
SW1(config)#access-list 105 permit tcp any any eq 80
SW1(config)#class-map WEBTRAFFIC
SW1(config-cmap)#match access-group 105
Now that we've identified the traffic to be affected by the policy, we better get around to writing the policy! QoS policies are configured with the policy-map command, and each clause of the policy will contain an action to be taken to traffic matching that clause.
SW1(config)#policy-map LIMIT_WEBTRAFFIC_BANDWIDTH
SW1(config-pmap)#class WEBTRAFFIC
SW1(config-pmap-c)#police 5000000 exceed-action drop
SW1(config-pmap-c)#exit
This is a simple policy, but it illustrates the logic of QoS policies. The policy map LIMIT_WEBTRAFFIC_BANDWIDTH calls the map-class WEBTRAFFIC. We already know that all WWW traffic will match that map class, so any WWW traffic that exceeds the stated bandwidth limitation will be dropped.
Finally, apply the policy to the appropriate interface.
SW1(config-if)#service-policy LIMIT_WEBTRAFFIC_BANDWIDTH in
Getting your CCNP is a great way to boost your career, and learning QoS is a tremendous addition to your skill set. Like I said, learn the fundamentals, don't get overwhelmed by looking at QoS as a whole, and you're on your way to success!
Subscribe to:
Posts (Atom)
