I wanted somebody to answer that question for me so badly when I initially started. I accepted that a career in networking would suit me because I was PC savvy, I was actually intrigued by innovation from the standpoint of how it functioned and I accepted that I could be acceptable at working with PCs in general. Past that, I simply didn't have a dream of where I wanted to go or where I could follow certification. I realized that a CCNA prepared you to function as a Network Specialist or Network Engineer. All in all, I considered what does a Networking Engineer do exactly?
Individuals who read my post about my exam (https://learningnetwork.cisco.com/thread/63767) and career venture (https://learningnetwork.cisco.com/thread/63768) with Cisco have mentioned information about what I do as a Network Engineer. I am certain that the activity job varies somewhat based on the kind of company you work for. As for me, I work for a SP. I might want to give you some knowledge into what I do as a Network Engineer in my company, how Cisco certs helped me, how the activity helped me with certs, and how it expanded my vision. All while being somewhat vague and general because a great deal of information about our network and how it is managed is confidential.
At the same time, I have been "'expressing" this post for seven days now because I am so occupied with work and concentrates for CCNP Route. So this will wind up as a progression of posts. I will address a few things related to Cisco's PPDIOO Methodology and how that CCNP point has applied to my activity job in addition to some general information.
Occupation OVERVIEW
In general, my team takes structures created by architects, planners and salespeople and makes changes to the network topology based on issues like traffic blockage, preventative maintenance, necessary infrastructure upgrades, client issues, new item contributions, and so forth.
TEAM ROLES
My immediate team comprises of Lead Network Engineers (Level II) and Network Engineers (Level I). Activities based on the issues above are given to the Lead Network Engineers and they pick two or three Level 1 Network Engineers to chip away at the tasks with them.
Procedure/PPDIOO
This is the primary spot where my Cisco information was fortified and used. The emphasis of Cisco CCNP R&S on Design Plans and Design Goals will go far in preparing individuals for this industry. In my job detailed implementation plans are created and confirmed for a majority of the undertaking life cycle before ever contributing a config into a network gadget. The alteration or contribution of any configs into a network gadget is approached delicately as on the off chance that you are about to perform "network medical procedure" on a living network-LOL. Note: I am just exaggerating a bit, it is intense.
I don't want to make the post excessively long so to summarize just Prepare and Plan on a practical level right now:
PREPARE
At the point when an undertaking has been given the official "Go" our team starts be playing out a broad and detailed audit of the regional network topology.
This procedure incorporates accessing various network gadgets (switches, switches, DSLAMS) to check traffic type (mac addresses), neighbors, configs, and so forth by primarily utilizing a variety of show commands. This information is documented in spreadsheets and uploaded to our task site for peer audit. Also, this topology is frequently diagrammed by our team - on paper then in Visio.
The audit procedure is vital. The recorded details must be accurate as this information is what will be depended heavily upon all through the plan phase.
PLAN
When the audit phase is finished, which can be a protracted procedure relying upon how large the district is, our team transforms that document into a plan. Based upon my previous professional encounters the undertaking manager inside me is altogether excited with this methodology.
As a Level 1 Network Engineer I want the control of an exact, well-considered plan before I step into "medical procedure". I unquestionably never want to be accused of harming any Cisco machines during the time spent network augmentation-LOL.
The planning phase is crucial also, because the present attributes of the network decides the necessary advances that must be taken to reach the augmentation goals.
LAST WORD:
As a conclusion to this first post about "What does a Network Engineer do?", from what I have seen, the fundamental occupation of a Network Engineer is to "follow that packet". So, our work on the network is ALL about availability. I like to consider myself a blend of an air traffic controller, investigator and guide for packets - LOL! I realize I am as a rule so cheesy! Apologies, yet I do cherish paying special mind to the valuable packets that have lost their way! Okay, I will stop!
Truly, the Cisco certs give you the information to "help and release" the packets! Sorry again. Really, it is as yet the foundational information about how the packet will behave on a vlan, through a switch, switch, and so on that gets you during that time and the venture.
Individuals who read my post about my exam (https://learningnetwork.cisco.com/thread/63767) and career venture (https://learningnetwork.cisco.com/thread/63768) with Cisco have mentioned information about what I do as a Network Engineer. I am certain that the activity job varies somewhat based on the kind of company you work for. As for me, I work for a SP. I might want to give you some knowledge into what I do as a Network Engineer in my company, how Cisco certs helped me, how the activity helped me with certs, and how it expanded my vision. All while being somewhat vague and general because a great deal of information about our network and how it is managed is confidential.
At the same time, I have been "'expressing" this post for seven days now because I am so occupied with work and concentrates for CCNP Route. So this will wind up as a progression of posts. I will address a few things related to Cisco's PPDIOO Methodology and how that CCNP point has applied to my activity job in addition to some general information.
Occupation OVERVIEW
In general, my team takes structures created by architects, planners and salespeople and makes changes to the network topology based on issues like traffic blockage, preventative maintenance, necessary infrastructure upgrades, client issues, new item contributions, and so forth.
TEAM ROLES
My immediate team comprises of Lead Network Engineers (Level II) and Network Engineers (Level I). Activities based on the issues above are given to the Lead Network Engineers and they pick two or three Level 1 Network Engineers to chip away at the tasks with them.
Procedure/PPDIOO
This is the primary spot where my Cisco information was fortified and used. The emphasis of Cisco CCNP R&S on Design Plans and Design Goals will go far in preparing individuals for this industry. In my job detailed implementation plans are created and confirmed for a majority of the undertaking life cycle before ever contributing a config into a network gadget. The alteration or contribution of any configs into a network gadget is approached delicately as on the off chance that you are about to perform "network medical procedure" on a living network-LOL. Note: I am just exaggerating a bit, it is intense.
I don't want to make the post excessively long so to summarize just Prepare and Plan on a practical level right now:
PREPARE
At the point when an undertaking has been given the official "Go" our team starts be playing out a broad and detailed audit of the regional network topology.
This procedure incorporates accessing various network gadgets (switches, switches, DSLAMS) to check traffic type (mac addresses), neighbors, configs, and so forth by primarily utilizing a variety of show commands. This information is documented in spreadsheets and uploaded to our task site for peer audit. Also, this topology is frequently diagrammed by our team - on paper then in Visio.
The audit procedure is vital. The recorded details must be accurate as this information is what will be depended heavily upon all through the plan phase.
PLAN
When the audit phase is finished, which can be a protracted procedure relying upon how large the district is, our team transforms that document into a plan. Based upon my previous professional encounters the undertaking manager inside me is altogether excited with this methodology.
As a Level 1 Network Engineer I want the control of an exact, well-considered plan before I step into "medical procedure". I unquestionably never want to be accused of harming any Cisco machines during the time spent network augmentation-LOL.
The planning phase is crucial also, because the present attributes of the network decides the necessary advances that must be taken to reach the augmentation goals.
LAST WORD:
As a conclusion to this first post about "What does a Network Engineer do?", from what I have seen, the fundamental occupation of a Network Engineer is to "follow that packet". So, our work on the network is ALL about availability. I like to consider myself a blend of an air traffic controller, investigator and guide for packets - LOL! I realize I am as a rule so cheesy! Apologies, yet I do cherish paying special mind to the valuable packets that have lost their way! Okay, I will stop!
Truly, the Cisco certs give you the information to "help and release" the packets! Sorry again. Really, it is as yet the foundational information about how the packet will behave on a vlan, through a switch, switch, and so on that gets you during that time and the venture.
No comments:
Post a Comment