Posted: May 28th, 2015

SNMP for diagnostics and troubleshooting network problems

SNMP for diagnostics and troubleshooting network problems


The usual University penalties apply for late submission.
This is an individual assignment.  Submission of an assignment indicates that you, as a student, have completed the assignment yourself and the work of others has been fully acknowledged and referenced.
By submitting this assessed work, you are declaring that you are fit to submit, and you will therefore not normally be eligible to submit a request for mitigation for this work.
For further information, please refer to your course handbook or University Assessment Regulations.

This assessment is designed to test your abilities in applying network monitoring and network management tools for identifying network problems in real-life scenarios. You should be able to demonstrate an understanding of the tools and techniques you studied in the lab sessions. Your report should review literature related to a problem you wish to discuss. Following the review, you need to write a technical report on how you will use Observer or OpenNMS platforms to identify and/or diagnose the problems. There will be a demo/viva, where you should be able to justify the technical report.

You are free to select any problem area, but you need to agree it with your tutor. Ideally, you should choose an area like

Monitoring Quality of Service
Managing network security
Managing Network performance
Managing wireless networks
Managing network users
Remote monitoring in corporate networks
Network Management in Manufacturing
Network management for green ICT
SNMP for diagnostics and troubleshooting network problems
Managing cloud infrastructures using SNMP
Device management using SNMP
Network Mapping

You will produce a detailed technical report between 4000 and 5000 words (excluding references). Titles, Contents pages, and Bibliography are not included in the final word count.

IMPORTANT NOTE : All your findings MUST reflect use of either OpenNMS or Observer in context of your chosen topic. A non-technical generic report will not fetch marks. Ideally, you will perform some experiments and use screen-shots to help you with your discussion.

Marking Scheme
•    Title and Abstract submission  5 %. You need to have a clear technical title with an abstract that clearly outlines your project area.
•    Detailed description of the problem area – 5 %
•    Relevant literature review with references to journal and academic material – 10 %
•    Detailed analysis/justification based on tools and techniques, with explanation of experiments and/or research – 15 %
•    Accurate application of tools and methodology in context of problem area – 25 %
•    Referencing – 5 % Your report MUST NOT use any quotes. All work should be in your own words and fully cited and referenced using Leeds Beckett Harvard format. You should have at least 20 relevant references of high academic or scientific quality
•    Viva/Demo : – 35 % A viva and/or demo will be based on your report where you will be asked to justify your report. This will be in the lab and will involve demonstrations using your choosen tool (observer, openNMS) applied in context of your topic.

Your report should be viewable in PDF format or in Microsoft Office format.  You must upload your report to Turnitin via the VLE before 11 PM Fri 29th May 2015

Expert paper writers are just a few clicks away

Place an order in 3 easy steps. Takes less than 5 mins.

Calculate the price of your order

You will get a personal manager and a discount.
We'll send you the first draft for approval by at
Total price:
Live Chat+1-631-333-0101EmailWhatsApp