| This article is the topic of Episode 5 of | | | | Analysis Team. This person does not need to |
| "The Sniffer Guy" podcast series available | | | | have a solid technical understanding but must |
| through iTunes. | | | | be able to follow the gist of it when |
| | | | interviewing the technical team in order to |
| INTRODUCTION: | | | | "translate" the information into a document |
| | | | that is understandable to both a technical |
| Application & Network Performance | | | | and NON-technical reader. |
| Analysis is a team sport. Rarely are all the | | | | |
| required skills in one skull. Perhaps it is | | | | Network & Application performance |
| best understood once you think in terms of | | | | Analysis troubleshooting doesn't require |
| functions and skill-sets within a | | | | separate people in each role - single |
| Troubleshooting process. In order to be able | | | | individuals can perform multiple roles. The |
| to handle ANYTHING that comes along, you will | | | | Senior NAPA may be able to perform all |
| need team members with high level skills in | | | | roles--at a high level. However, the Client's |
| Enterprise Applications--Operating | | | | Subject Matter Experts (SME) will still be |
| Systems--Databases--Server Issues and a | | | | required. Consider them a guest member of the |
| detailed understanding of Protocols and | | | | team. |
| Packet-Level transactions. But, to expect one | | | | |
| or two people to have detailed knowledge of | | | | FREQUENT ROLE COMBINATIONS: |
| all these areas is unrealistic. | | | | |
| | | | Project Manager--Technical Writer |
| The Senior Network and Application | | | | |
| Performance Analyst (NAPA)Â (TM) will | | | | Network & Application performance |
| need to be able to communicate with all these | | | | Analysis -- Protocol Analysis |
| individuals, teams and managers. | | | | |
| Communication & interviewing abilities | | | | Enterprise Application Specialist -- |
| are mandatory. If, even by some chance, you | | | | Operating System Specialist |
| have the world's best troubleshooter--what if | | | | |
| they leave? This Team approach is practical | | | | INTIAL STEPS: |
| and stable. | | | | |
| | | | 1) NAPA meets with Client Management - |
| THE 7 PRIMARY TEAM ROLES: | | | | determines goals. |
| | | | |
| Network & Application Performance Analyst | | | | 2) EAS meets with Application Subject Matter |
| (NAPA)Â (TM) - Team Manager & | | | | Experts (SME) - begins to map out the |
| Technical Team Lead. This person needs to | | | | Interpath. |
| understand all the various technical issues | | | | |
| and be able to discuss them and ask the right | | | | 3) NAPA gathers all applicable documentation |
| questions of the individual experts. They are | | | | - begins environmental overview. |
| the hub of the team's wheel. The NAPA must | | | | |
| learn all the Client's goals - Technical - | | | | 4) NAPA- EAS determine test goals. |
| Political - Management - Budgetary and then | | | | |
| is able to scale the team accordingly. | | | | 5) NAPA- EAS - Client SME design test plan - |
| | | | select test transactions. |
| Enterprise Application Specialist (EAS) - | | | | |
| Able to map Application flow from functional | | | | 6) NAPA- Network Engineer - Client Network |
| & transactional basis. Understands | | | | SME. |
| Database interactions - Multi-Tiered | | | | |
| Architecture - Web Servers. | | | | 7) Map out Interpath within Network |
| | | | Infrastructure. |
| Protocol Analyst - Packet-Sniffer Guru. | | | | |
| Understands Network Protocols - Topology | | | | 8) Plan how to place Sniffer, Ethereal - |
| Framing - Troubleshooting from the Packet | | | | WireShark. Mirrors (SPANs) - Taps - Host |
| Level. This individual will be capturing | | | | Based - Wire Speed, etc. |
| trace files and analyzing the traffic at the | | | | |
| protocol and packet-level. | | | | 9) Implement plan & deploy tools. |
| | | | |
| Network Engineer - Familiar with wide variety | | | | 10) Protocol Analyst - NAPA executes selected |
| of vendors i.e. Cisco--Foundry-- | | | | Application Transaction for performance |
| Nortel--Troubleshooting Layers 1-3. If this | | | | analysis - captures appropriate trace files - |
| team member is part of an in-house team, they | | | | log User experience. |
| need only be up to date on the manufacture's | | | | |
| equipment in place within the organization. | | | | 11) Protocol Analyst performs analysis of |
| However, if your team is a consulting | | | | trace files & begins Documentation. |
| team...this individual has to have experience | | | | |
| with a wide range of manufactures. | | | | 12) Theories are developed - Test Plan |
| | | | modified - second round of analysis testing |
| Operating Systems Specialist - UNIX & | | | | (where needed). |
| Windows, Other... | | | | |
| | | | Having a Champion within Client's |
| Project Manager - Maintains Task List - Gant | | | | organization is critical. Organization's |
| Chart - Reports to Client's Management | | | | staff members are not accountable to The NAPA |
| | | | Team - does not have to provide information |
| Technical Writer - Creates deliverable | | | | or perform tasks. Will not do so when busy - |
| documentation showing work & resolutions | | | | but always busy! A Champion will help clear |
| provided by Network Application Performance | | | | the path of internal escalation. |