Troubleshooting (CRAM Notes)

Troubleshooting Methodology

  • Problem Isolation – determining at what layer of the OSI model and on what device and links the problem may occur
  • Documentation – document the processes you use and the information you find
  • Resolve – find the root cause after isolation, document what happened, fix the root cause of the problem, fix the problem
  • Escalate – if you can’t fix the issue, send a written escalation to organization or third party with as much info as possible
  • Verify and Monitor – carefully verify and monitor your solution to ensure the issue are tury resolved

OSI Model

  • It is important to follow the OSI model using either a top down or bottom up approach depending on specific issues.
  • Review
    • Application
    • Presentation
    • Session
    • Transport
    • Network
    • Data Link
    • Physical

Please     Do     Not     Throw     Sausage     Pizza     Away

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s