Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Newer
Older
100644 382 lines (282 sloc) 13.235 kB
99cca1f @cluther Initial commit.
cluther authored
1 ===============================================================================
2 ZenPacks.zenoss.SolarisMonitor
3 ===============================================================================
4
5 About
6 ===============================================================================
7
8 The SolarisMonitor ZenPack enables Resource Manager to use Secure Shell (SSH)
9 to monitor Solaris hosts. Resource Manager models and monitors devices placed
10 in the /Server/SSH/Solaris device class by running commands and parsing the
11 output. Parsing of command output is performed on the Resource Manager server
12 (if using a local collector) or on a distributed collector. The account used to
13 monitor the device does not require root access or special privileges.
14
15 In addition to the previously described modeling and monitoring features this
16 ZenPack also enables Resource Manager to model and monitor Sun Solaris LDOM
17 servers. Resource Manager will model devices utilizing the Simple Network
18 Management Protocol (SNMP) to collect LDOM information when a divice resides
19 in either the /Server/Solaris or /Server/SSH/Solaris device classes. The
20 discovered LDOM information will be displayed as components of the LDOM host
21 server.
22
23 Features
24 -------------------------------------------------------------------------------
25
26 The SolarisMonitor ZenPack provides:
27
28 * File system and process monitoring
29 * Network interfaces and route modeling
30 * CPU utilization information
31 * Hardware information (memory, number of CPUs, and model numbers)
32 * OS information (OS-level, command-style information)
33 * Pkginfo information (such as installed software)
34 * LDOM monitoring
35
36 Prerequisites
37 -------------------------------------------------------------------------------
38
39 ================== ========================================================
40 Prerequisite Restriction
41 ================== ========================================================
42 Zenoss Platform 3.1 or greater
43 Zenoss Processes zencommand, zenperfsnmp
44 Installed ZenPacks ZenPacks.zenoss.SolarisMonitor
45 Firewall Acccess Collector server to 22/tcp and 161/udp of Solaris server
46 Solaris Releases OpenSolaris 5.11, Solaris 9 and 10
47 ================== ========================================================
48
49 Limitations
50 -------------------------------------------------------------------------------
51
52 The SolarisMonitor ZenPack does not support monitoring in Solaris Zones or
53 systems containing Solaris Zones. (Implemented with Solaris 10, Solaris Zones
54 act as isolated virtual servers within a single operating system instance.)
55
56
57 Usage
58 ===============================================================================
59
60 Installation
61 -------------------------------------------------------------------------------
62
63 This ZenPack has no special installation considerations. Depending on the
64 version of Zenoss you're installing the ZenPack into, you will need to verify
65 that you have the correct package (.egg) to install.
66
67 * Zenoss 4.1 and later: The ZenPack file must end with ``-py2.7.egg``.
68 * Zenoss 3.0 - 4.0: The ZenPack file must end with ``-py2.6.egg``.
69
70 To install the ZenPack you must copy the ``.egg`` file to your Zenoss master
71 server and run the following command as the ``zenoss`` user::
72
73 zenpack --install <filename.egg>
74
75 After installing you must restart Zenoss by running the following command as
76 the ``zenoss`` user on your master Zenoss server::
77
78 zenoss restart
79
80 If you have distributed collectors you must also update them after installing
81 the ZenPack.
82
83 Configuring
84 -------------------------------------------------------------------------------
85
86 Depending on the version of Solaris you may be able to monitor the server using
87 either SSH or SNMP. For OpenSolaris and Solaris 10, you can choose to use
88 either SSH or SNMP monitoring. For Solaris 9, only SSH monitoring is supported.
89
90 Configuring SSH Monitoring
91 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
92
93 Use the following steps to configure Zenoss to monitor your Solaris server(s)
94 using SSH.
95
96 1. Navigate to the ``/Server/SSH/Solaris`` device class' configuration
97 properties.
98 2. Verify that the ``zCommandUsername`` and ``zCommandPassword`` are set to
99 valid login credentials.
100 3. Add your Solaris server(s) to the ``/Server/SSH/Solaris`` device class.
101
102 Configuring SNMP Monitoring
103 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
104
105 Use the following steps to configure Zenoss to monitor your Solaris server(s)
106 using SNMP.
107
108 1. Verify that the snmpd process is running on your Solaris server(s).
109 2. Navigate to the ``/Server/Solaris`` device class' configuration properties.
110 3. Verify that your Solaris server(s) SNMP community strings are listed in the
111 ``zSnmpCommunities`` property.
112 4. Add your Solaris server(s) to the ``/Server/Solaris`` device class.
113
114 Configuring LDOM Monitoring
115 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
116
117 For OpenSolaris and Solaris 10 servers you will also get support for monitoring
118 LDOMs if they're used on the server. However, this monitoring is always
119 performed using SNMP. If you're already monitoring your Solaris server using
120 SNMP there is no additional configuration required to monitor its LDOMs. If you
121 configured Zenoss to monitor your Solaris server using SSH you should take the
122 following steps to monitor LDOMs.
123
124 1. Verify that the snmpd process is running on your Solaris server(s).
125 2. Navigate to the ``/Server/SSH/Solaris`` device class' configuration
126 properties.
127 3. Verify that your Solaris server(s) SNMP community strings are listed in the
128 ``zSnmpCommunities`` property.
129 4. Remodel your Solaris server(s) if they're already in the system. Otherwise
130 add them to the ``/Server/SSH/Solaris`` device class.
131
132 Removal
133 -------------------------------------------------------------------------------
134
135 **Use caution when removing this ZenPack**
136
137 * Will **permanently** remove devices located in ``/Server/SSH/Solaris`` device
138 class.
139 * Will **permanently** remove LDOM modeled components for devices located in
140 ``/Server/Solaris``.
141 * Will **permanently** remove associated monitored data for LDOM components.
142 * Will **permanently** remove the ``/Server/SSH/Solaris`` device class.
143
144 To remove this ZenPack you must run the following command as the ``zenoss``
145 user on your master Zenoss server::
146
147 zenpack --remove ZenPacks.zenoss.SolarisMonitor
148
149 You must then restart the master Zenoss server by running the following command
150 as the ``zenoss`` user::
151
152 zenoss restart
153
154 Troubleshooting
155 -------------------------------------------------------------------------------
156
157 Resolving CHANNEL_OPEN_FAILURE Issues
158 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
159
160 The zencommand daemon's log file (``$ZENHOME/collector/zencommand.log``) may
161 show messages stating::
162
163 ERROR zen.SshClient CHANNEL_OPEN_FAILURE: Authentication failure WARNING:zen.SshClient:Open of command failed (error code 1): open failed
164
165 If the sshd daemon's log file on the remote device is examined, it may report
166 that the MAX_SESSIONS number of connections has been exceeded and that it is
167 denying the connection request. In the OpenSSH daemons, this MAX_SESSIONS
168 number is a compile-time option and cannot be reset in a configuration file.
169
170 To work around this sshd daemon limitation, use the configuration property
171 zSshConcurrentSessions to control the number of connections created by
172 zencommand to the remote device:
173
174 1. Navigate to the device or device class in the Resource Manager interface.
175 * If applying changes to a device class:
176 a. Select the class in the devices hierarchy.
177 b. Click Details.
178 c. Select Configuration Properties.
179 * If applying changes to a device:
180 a. Click the device in the device list.
181 b. Select Configuration Properties.
182 2. Set the ``zSshConcurrentSessions`` property. Try 10 first, and 2 if that
183 doesn't resolve the problem.
184
185 Resolving Command Timeout Issues
186 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
187
188 The zencommand daemon's log file ($ZENHOME/collector/zencommand.log) may show
189 messages stating::
190
191 WARNING:zen.zencommand:Command timed out on device device_name: command
192
193 If this occurs, it usually indicates that the remote device has taken too long
194 to return results from the commands. To increase the amount of time to allow
195 devices to return results, change the configuration property
196 ``zCommandCommandTimeout`` to a larger value.
197
198 1. Navigate to the device or device class in the Resource Manager interface.
199 * If applying changes to a device class:
200 a. Select the class in the devices hierarchy.
201 b. Click Details.
202 c. Select Configuration Properties.
203 * If applying changes to a device:
204 a. Click the device in the device list.
205 b. Select Configuration Properties.
206 2. Increase the ``zCommandCommandTimeout`` property incrementally to a maximum
207 of 240 until the timeout is resolved.
208
209
210 Appendixes
211 ===============================================================================
212
213 Appendix A: Installed Items
214 -------------------------------------------------------------------------------
215
216 =================== =================== ===================================
217 Type Name Location
218 =================== =================== ===================================
219 Device Class /SSH/Solaris /Devices/Server
220 Modeler Plugin df_ag zenoss.cmd.solaris
221 Modeler Plugin kstat zenoss.cmd.solaris
222 Modeler Plugin memory zenoss.cmd.solaris
223 Modeler Plugin netstat_an zenoss.cmd.solaris
224 Modeler Plugin netstat_r_vn zenoss.cmd.solaris
225 Modeler Plugin pkginfo zenoss.cmd.solaris
226 Modeler Plugin process zenoss.cmd.solaris
227 Modeler Plugin uname_a zenoss.cmd.solaris
228 Modeler Plugin hostid zenoss.snmp.solaris
229 Modeler Plugin ldommap zenoss.snmp.solaris
230 Monitoring Template Device /Server/SSH/Solaris
231 Monitoring Template FileSystem /Server/SSH/Solaris
232 Monitoring Template OSProcess /Server/SSH/Solaris
233 Monitoring Template ethernetCsmacd /Server/SSH/Solaris
234 Monitoring Template LDOM /Server
235 Monitoring Template LDOMVcpu /Server
236 Monitoring Template LDOMVds /Server
237 Event Class /Status/LDOM /
238 Event Class /Status/LDOM/vCPU /
239 Event Mapping ldomStateChange /Change
240 Event Mapping ldomVCpuChange /Change
241 Event Mapping ldomVccChange /Change
242 Event Mapping ldomVconsChange /Change
243 Event Mapping ldomVdiskChange /Change
244 Event Mapping ldomVdsChange /Change
245 Event Mapping ldomVmemChange /Change
246 Event Mapping ldomVnetChange /Change
247 Event Mapping ldomVswChange /Change
248 Event Mapping ldomCreate /Change/Add
249 Event Mapping ldomDestroy /Remove
250 MIB SUN-LDOM-MIB /
251 =================== =================== ===================================
252
253 Monitoring Templates
254 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
255
256 **Device** *(/Server/SSH/Solaris)*
257
258 - *Data Points*
259
260 - cpu_ssCpuIdle
261 - cpu_ssCpuInterrupt
262 - cpu_ssCpuSystem
263 - cpu_ssCpuUser
264 - io_read
265 - io_written
266 - percent_memory_percentMemUsed
267 - percent_swap_percentSwapUsed
268 - uptime_laLoadInt1
269 - uptime_laLoadInt5
270 - uptime_laLoadInt15
271 - uptime_sysUpTime
272
273 - *Thresholds*
274
275 - CPU Utilization
276 - high load
277
278 - *Graphs*
279
280 - Load Average
281 - CPU Utilization
282 - Memory Utilization
283 - IO
284
285 **FileSystem** *(/Server/SSH/Solaris)*
286
287 - *Data Points*
288
289 - disk_availBlocks
290 - disk_availNodes
291 - disk_percentInodesUsed
292 - disk_totalBlocks
293 - disk_totalInodes
294 - disk_usedBlocks
295 - disk_usedInodes
296
297 - *Thresholds*
298
299 - high_disk_usage
300
301 - *Graphs*
302
303 - Utilization
304 - Inode Utilization
305
306 **OSProcess** *(/Server/SSH/Solaris)*
307 - *Data Points*
308
309 - ps_count
310 - ps_cpu
311 - ps_mem
312
313 - *Graphs*
314
315 - CPU Utilization
316 - Memory
317 - Process Count
318
319 **ethernetCsmacd** *(/Server/SSH/Solaris)*
320 - *Data Points*
321
322 - intf_ifInErrors
323 - intf_ifInPackets
324 - intf_ifOutErrors
325 - intf_ifOutPackets
326 - intf_octets_ifInOctets
327 - intf_octets_ifOutOctets
328
329 - *Thresholds*
330
331 - Utilization 75 perc
332
333 - *Graphs*
334
335 - Throughput
336 - Packets
337
338 **LDOM** *(/Server)*
339
340 - *Data Sources*
341
342 - ldomOperState
343
344 - *Thresholds*
345
346 - operational state
347
348 **LDOMVcpu** *(/Server)*
349
350 - *Data Sources*
351
352 - ldomVcpuOperationalStatus
353 - ldomVcpuUtilPercent
354
355 - *Threshold*
356
357 - operational status
358
359 - *Graph Definition*
360
361 - CPU Utilization
362
363 **LDOMVds** *(/Server)*
364
365 - *Data Source*
366
367 - ldomVdsNumofAvailVolume
368 - ldomVdsNumofUsedVolume
369
370 - *Graph Definition*
371
372 - Volumes
373
374 Appendex B: Required Daemons
375 -------------------------------------------------------------------------------
376
377 In addition to the core platform daemons the following optional daemons are
378 required for this ZenPack to fully function.
379
380 * zenperfsnmp
381 * zencommand
Something went wrong with that request. Please try again.