The document provides an overview and agenda for a training session on SolarWinds Profiler Storage, Virtual, and Server products. It covers Profiler architecture, file analysis features, configuring alerts, troubleshooting agent reporting issues, and optimizing performance through load balancing. The session demonstrates how to use file analysis, configure alerts, troubleshoot agents, and ensure proper workload distribution across agents and servers. Attendees learn how to effectively monitor, manage and troubleshoot their storage, virtual, and server environments using Profiler.

1. Storage Profiler and Virtual & Server Profiler Session 1

2. SolarWinds Subject Matter Experts Dan Wendeln- Education and Certification Manager Brian Radovich – Product Manager, Storage Today’s Topic: Customer Training – Profiler Storage, Virtual and Server Introduction

4. If not, use the GoToWebinar chat or Q&A panel to let us know.

5. How do you win the free stuff?

6. How do you ask questions and when?

7. Will this be recorded?

9. Goals for today’s training session By the end of this session you should understand: Profiler Architecture & System Recommendations File Analysis Features Alert Configuration and Best Practices Troubleshooting Agent Reporting Issues Load Balancing and Resource Management in Profiler

10. Profiler and the SolarWinds Portfolio SolarWinds manages Network Devices Routers, Switches, Firewalls Servers Physical and Virtual Software Applications Exchange, SQL Storage Devices SAN array, NAS, DAS SolarWinds products Periodically check device performance Alert network administrators of problems Report on overall performance Identify and diagnose issues Resolve network issues Network Storage Apps

11. Objective #1 - Profiler Architecture

13. Server

14. Data Repository

15. GUI & Reporting

16. Configuration Manager

17. Poller/Agents

18. Collect Data

19. Monitor & Alert

20. Execute Actions

21. Communication

22. Server & Agent: HTTP, HTTPS & SNMP

25. Windows 32 or 64bit

26. Dual Processor, 4 GB RAM

27. Min 2 VM Pollers

28. Poller/agent: Single Processor, 1 GB of RAM

29. Medium: Up to 3000 Disks & 1500 VM/Servers

30. Windows 64bit

31. Quad Processor, 8-16 GB RAM

32. Min 7 VM Pollers

33. Poller/agent: Single/Dual Processor, 2GB of RAM

34. Large: Up to 30,000 disks, 5000+ VM

35. Windows 64bit

36. 8-16 Processors, 16-64GB RAM

37. 1 Poller per ~200VM

39. Analyzes how you are using your file storage

40. Works on any formatted storage:Server, VM or NAS device

41. What does it report?

42. Summary Information

43. By Owner, Age and Type

44. Find specific files via File Rules

46. Physical server (with agent)

47. Turn on FA via wrench or policy

48. NAS/VM

49. Get a list of Shares

50. Assign shares to an poller/agent

53. By file extension (.dmp, .tmp, .core, etc.)File Analysis – Using Rules A file rule defines files that you would like to find. To create a file rule: Create the rule. Assign it to a policy. Push the policy out. All file analysis runs will also output the files that meet the criteria of the rule.

56. File Analysis File Analysis Demo

58. B. 100 - 250

59. C. 250 - 500

60. D. 500 – 1000

62. B. 100 - 250

63. C. 250 - 500

64. D. 500 – 1000

65. E. > 1000Poll Closed

67. Threshold: Storage, Performance, File Analysis

68. Change: Asset

69. Actions

70. Send an SNMP Trap

71. Execute a script

72. Where do the traps go?

73. Profiler Event Monitor

74. Email – setup up Notifications for your account

77. Check profiler services status and recent time stamp

78. MySQL, ProfilerCollector, ProfilerEventReceiver, ProfilerMaintenance, ProfilerPoller, ProfilerWebServer

79. Check the device status

80. Hover over status icon by device name

82. Agent Troubleshooting Almost all agents are yellow on the Server Monitor. Some data is not being collected If all the agents are yellow & the times are greater than 2 or 3 minutes, check the event receiver If all the agents are yellow & the times are less than 2 or 3 minutes, check the collector One or more agents are yellow on the Server Monitor. Press the stoplight to validate communicate & review which modules are online and offline If not receiving real time, review the logs to see if some data is not available If you can’t communicate with the agent, go to that agent & review the core.xml and kernel.log. If you see fatal.log, it is usually a configuration issue

83. More Troubleshooting Tips Event Receiver Issues: Check to see if the service is running. Another application could be using port 162 (port is configurable). Collector Issues: In large environment you can run the collector out of memory. This implies you should spread the load to more poller agents. If the collector loses the connection to the database, it may stop collecting. If the database is up, restart the collector. If the database is down, start the database & then start the collector.

84. Objective #4 – Agent Reporting Issues Troubleshooting Demo

86. B. SAN/Storage Issues

87. C. Network Issues

88. D. Application Issues

90. B. SAN/Storage Issues

91. C. Network Issues

92. D. Application Issues

93. E. datacenter IssuesPoll Closed

95. Server web slowness, missing arrays, no data, high memory or CPU utilization

96. ~200 VM per Poller/Agent

97. Where to place agents

98. Physical servers that are File Servers or have HBA

99. VM that you create specifically for Profiler

100. Understanding agent and server loads