Transcript Trouble Reporting & Resolution

Trouble Reporting & Resolution
Assumptions
• “Expected” Traffic Profiles exist (‘rulesets’)
– Ideal vs. Expected [persistent problems may be ok]
– Acceptable, by application
•
•
•
•
Video
Voice
Haptic
Bulk
• Contact Database
Inputs
• Analysis (wholistic approach, data mining)
• Client
– Human
– Instruments [within stacks, applications]
• In-situ along path (e.g., router traps/alerts,
portable tester)
Intermediate
Outputs/Requirements
• Requests for data mining, analysis
Results
• Reports to user
– In profile
– Out of profile
• Who to call or email
• Trouble ticket generation
• A description of what is out of profile (“why”)
suitable for network engineers
• Feedback to system
– Request to update ruleset on in/out profile