Hardware Best Practices – Sizing Small - NPM 250 – 500, no NTA, 2 modules IPAM Medium - NPM SLX or smaller, 2 modules or less NTA 30,000 fps with top talker optimization, IPAM Large – NPM SLX with multiple pollers NTA 60,000 fps with top talker optimization, IPAM Hardware Best Practices Drivers Network size, number of elements, Orion modules, environmental and standards Network size and element count will drive number of pollers NTA, APM and NCM will drive SQL requirements Environmental and standards may define possible configurations Firewall locations and rules, hardware standards, database standards, connectivity
Orion Product Family - Slide - Enterprise Operations Console Orion Scalability Engines Orion Failover Engineīase requirements Orion Server(s) SQL Server Database SQL Storage Objective #1 – Hardware
Goals for today’s training session By the end of this session you should be able to: Understand Best Practices for Orion and SQL Hardware Understand SQL Performance Options Understand Orion Performance Options Diagnose and Fix Performance Problems How do you win the free stuff? How do you ask questions and when? Will this thing be recorded? If you don’t have a notebook, get one… Ask lots of questions – We have folks standing by to answer your chat questions! Īgenda Goals for today’s training session Hardware Recommendations for Orion and SQL SQL Performance Checking and Monitoring Orion Health Diagnosing Performance Problems Where to Learn More and Q&A Housekeeping Can you hear me now? If not, use the GoToWebinar chat or Q&A panel to let us know. Orion Network Performance Monitor (NPM) Optimization and Tuning TrainingĪ big “Howdy” from SolarWinds based in Austin, Texas Josh Stephens - Head Geek, Monster Blogger, Constant Tweeter Chris LaPoint– Director, Product Management Dan Weldeln – Manager, Training and Certification Today’s Topic: Orion NPM Customer Training – Orion Optimization and Tuning Who is SolarWinds? Dude, if you don’t’ know this you’re on the wrong webcast… Introduction
0 kommentar(er)
