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