Question about real world experience and certification to reinforce the skills

N2IT

I was hoping some of you could provide their input.

In my last role I used to monitor networks using monitor event tools like Tivoli netview and Ciscoworks and actually SSH/Telnetting into the routers and switches to see what/if there was a problem from from the network. Usually it was just basic review type work, running some basic commands (EG. sh int brief or sh int) maybe a total of 15 to get into the routers and then the switch to see where the problem was. Most of the time the protocol was down or actual line. I'll be honest most events that ended up going that far went to a ISP for assistance. A lot of times you would see fiber cuts and acts of God be the culprit. Anyway I was wondering if there was a Cisco certification that would fit that skill level/role and would help fill in the knowledge gaps. Something tells me the CCNA is a bit of an overkill.

This is mostly out of curiosity than anything. I am in over my head with studies at the moment anyway so this is unrealistic, but I was just curious.

Thanks

martell1000

there are these new CCT certs but no one seems to take them here. but from what you described CCENT would be the way to go. it covers all basic routing and switch operations and gives you halfway to the CCNA.

N2IT

martell1000 wrote: »

there are these new CCT certs but no one seems to take them here. but from what you described CCENT would be the way to go. it covers all basic routing and switch operations and gives you halfway to the CCNA.

Thanks for the reply.

Roguetadhg

CCT might be the best way. Yes, CCENT would be a good filler, but the content gets into configuration, implementation, design. Albeit, not as deep as ICND2. From what it sounds like you're not interested into much more than just knowing how to maintain what is already built. CCENT goes more deeply into the topics, but take a look at the information and see if it matches - or not.

R+S:

To prepare onsite support technicians to diagnose, restore, repair, and replace critical Cisco routing and switching network devices.

Data Center:

To prepare onsite support technicians to diagnose, restore, repair, and replace critical Cisco Data Center Solutions.

Telepresence:

To prepare onsite technicians to support and maintain Cisco Unified Computing System components and servers.

https://learningnetwork.cisco.com/community/certifications/cct
http://www.cisco.com/web/learning/le3/docs/CCT_vs_CCENT_Skill_Set_Comparison_Chart.pdf


ICND1 [CCENT] Exam Info: https://learningnetwork.cisco.com/community/certifications/ccna/icnd1?tab=1

N2IT

Roguetadhg wrote: »

CCT might be the best way. Yes, CCENT would be a good filler, but the content gets into configuration, implementation, design. Albeit, not as deep as ICND2. From what it sounds like you're not interested into much more than just knowing how to maintain what is already built. CCENT goes more deeply into the topics, but take a look at the information and see if it matches - or not.

R+S:

To prepare onsite support technicians to diagnose, restore, repair, and replace critical Cisco routing and switching network devices.

Data Center:

To prepare onsite support technicians to diagnose, restore, repair, and replace critical Cisco Data Center Solutions.

Telepresence:

To prepare onsite technicians to support and maintain Cisco Unified Computing System components and servers.

https://learningnetwork.cisco.com/community/certifications/cct
http://www.cisco.com/web/learning/le3/docs/CCT_vs_CCENT_Skill_Set_Comparison_Chart.pdf


ICND1 [CCENT] Exam Info: https://learningnetwork.cisco.com/community/certifications/ccna/icnd1?tab=1

Thanks for the post. You are correct I am really not into design or set up, more of a high level understanding and being able to fill in the knowledge I already have, which isn't much compared to a lot of you.

Turgon

N2IT wrote: »

I was hoping some of you could provide their input.

In my last role I used to monitor networks using monitor event tools like Tivoli netview and Ciscoworks and actually SSH/Telnetting into the routers and switches to see what/if there was a problem from from the network. Usually it was just basic review type work, running some basic commands (EG. sh int brief or sh int) maybe a total of 15 to get into the routers and then the switch to see where the problem was. Most of the time the protocol was down or actual line. I'll be honest most events that ended up going that far went to a ISP for assistance. A lot of times you would see fiber cuts and acts of God be the culprit. Anyway I was wondering if there was a Cisco certification that would fit that skill level/role and would help fill in the knowledge gaps. Something tells me the CCNA is a bit of an overkill.

This is mostly out of curiosity than anything. I am in over my head with studies at the moment anyway so this is unrealistic, but I was just curious.

Thanks

From the looks of things you already have some useful background. I would work harder on building positive relationships with Cisco specialists where mutual trust is in place than persuing any particular certification. Cisco qualifications are fairly good at explaining how things work, but somewhat less effective at troubleshooting. This comes with experience in the field and a development of an engineer's instinct.

Roguetadhg

Turgon: How does one get the troubleshooting experience?

N2IT

Turgon wrote: »

From the looks of things you already have some useful background. I would work harder on building positive relationships with Cisco specialists where mutual trust is in place than persuing any particular certification. Cisco qualifications are fairly good at explaining how things work, but somewhat less effective at troubleshooting. This comes with experience in the field and a development of an engineer's instinct.

Seriously all my Cisco knowledge is hands on. I've never read a book or labbed. I was thrown into the mix and basically asked question after question until I learned. I remember some of the plants being on Fractional T1's with a back up DSL or Cable line. I always found it interesting that they would use the back up line for email and messaging and use the T 1 line for the production systems like SAP or some of the vertical software prioritary to the manufacting environment. When I first started I always thought the back up was just that the back up, but later I found out that it was utilized for other client server applications like Office Communicator and Exchange. Kind of cool!

I remember guys having microwaves next to the routing equipment or wireless phones and troubleshooting for hours why the circuit was bouncing or why they were having intermitten connectivity issues.

Troubleshooting networks can be challenging but a lot of fun. Of course their were times when it was over your head and then you got the network engineer involved and he usually ended up teaching you some awesome information related to networking. Towards the end it was a lot fun, they would install another application or give you rights to a networking tool almost like a badge of honor. I remember one time a plant was just at a crawl. I was working with the networking engineering group and they just started working on it. I mentioned early that day that a lot of people complained of bombed symantec upgrades and they check the NetQoS and saw 90+ % of the bandwidth was being used for install pushes. I suppose something automated went wrong and the install was kicked off to a whole plant/business unit during peak hours. It was pretty neat, in fact that day they gave me access to a whole array of new networking tools and would come on by and show me how they worked. NetQoS was one of them.

Good times I say good times!

martell1000

if i were you i would get the cbt nuggets series for ICND1 and see if CCENT is maybe the right thing. there might be a lot of new stuff in it but i guess it never hurts to get more knowledge. also it never hurts to get a cert on your resume to prove you went through it....

martell1000

oh and one thing about troubleshooting: what turgon mentioned is absolutely true, but if you learned the concepts of how stuff works its way more easy to get troubleshooting going.

for example: i have been dealing with ospf some years ago, but never caught the "big picture" until i worked through the ccnp route material... now pieces start mending together as i learn the concepts...