Projet

Général

Profil

Révision 5d2c0cfb

ID5d2c0cfb89e3ecc6ff966acff3968457ba68840f
Parent 9de5e7c9
Enfant d18b942a

Ajouté par Diver il y a presque 9 ans

Documentation

Voir les différences:

plugins/emc/emc_vnx_file_
4 4

  
5 5
=head1 NAME 
6 6

  
7
 emc_vnx_file_stats - Plugin to monitor Basic, NFSv3 and NFSv4 statistics of EMC VNX 5300 Unified Storage system's Datamovers
7
 emc_vnx_file_stats - Plugin to monitor Basic, NFSv3 and NFSv4 statistics of 
8
 EMC VNX 5300 Unified Storage system's Datamovers
8 9

  
9 10
=head1 AUTHOR
10 11

  
......
21 22

  
22 23
=head1 DESCRIPTION
23 24

  
24
 The plugin monitors basic statistics of EMC Unified Storage system Datamovers and NFS statistics of EMC VNX5300 Unified 
25
 Storage system. Probably it can also be compatible with other Isilon or Celerra systems. It uses SSH to connect to Control 
26
 Stations, then remotely executes '/nas/sbin/server_stats' and fetches and parses data from it. It supports gathering 
27
 data both from active/active and active/passive Datamover configurations, ignoring offline or standby Datamovers. 
25
 The plugin monitors basic statistics of EMC Unified Storage system Datamovers 
26
 and NFS statistics of EMC VNX5300 Unified Storage system. Probably it can 
27
 also be compatible with other Isilon or Celerra systems. It uses SSH to connect
28
 to Control Stations, then remotely executes '/nas/sbin/server_stats' and 
29
 fetches and parses data from it. It supports gathering data both from 
30
 active/active and active/passive Datamover configurations, ignoring offline or 
31
 standby Datamovers. 
28 32
 If all Datamovers are offline or absent, the plugin returns error.
29
 This plugin also automatically chooses Primary Control Station from the list by calling '/nasmcd/sbin/getreason' and 
30
 '/nasmcd/sbin/t2slot'.
33
 This plugin also automatically chooses Primary Control Station from the list by
34
  calling '/nasmcd/sbin/getreason' and '/nasmcd/sbin/t2slot'.
31 35
 
32 36
 At the moment data is gathered from the following statistics sources:
33 37
  * nfs.v3.op - Tons of timings about NFSv3 RPC calls
34 38
  * nfs.v4.op - Tons of timings about NFSv4 RPC calls
35 39
  * nfs.client - Here new Client addresses are rescanned and added automatically.
36
  * basic-std Statistics Group - Basic Statistics of Datamovers (eg. CPU, Memory etc.)
40
  * basic-std Statistics Group - Basic Statistics of Datamovers (eg. CPU, Memory
41
  etc.)
37 42
 
38
 It's quite easy to comment out unneeded data to make graphs less overloaded or to add new statistics sources.
43
 It's quite easy to comment out unneeded data to make graphs less overloaded or
44
 to add new statistics sources.
45

  
46
=head1 LIST OF GRAPHS
47

  
48
 These are Basic Datamover Graphs.
49
 Graph category CPU:
50
	EMC VNX 5300 Datamover CPU Util %
51
 Graph category Network:
52
	EMC VNX 5300 Datamover Network bytes over all interfaces
53
	EMC VNX 5300 Datamover Storage bytes over all interfaces
54
 Graph category Memory:
55
	EMC VNX 5300 Datamover Memory
56
	EMC VNX 5300 File Buffer Cache
57
	EMC VNX 5300 FileResolve
58

  
59
 These are NFS (v3,v4) Graphs.
60
 Graph category NFS:
61
	EMC VNX 5300 NFSv3 Calls per second
62
	EMC VNX 5300 NFSv3 uSeconds per call
63
	EMC VNX 5300 NFSv3 Op %
64
	EMC VNX 5300 NFSv4 Calls per second
65
	EMC VNX 5300 NFSv4 uSeconds per call
66
	EMC VNX 5300 NFSv4 Op %
67
	EMC VNX 5300 NFS Client Ops/s
68
	EMC VNX 5300 NFS Client B/s
69
	EMC VNX 5300 NFS Client Avg uSec/call
39 70

  
40 71
=head1 COMPATIBILITY
41 72

  
42
 The plugin has been written for being compatible with EMC VNX5300 Storage system, as this is the only EMC storage which 
43
 i have.
44
 By the way, i am pretty sure it can also work with other VNX1 storages, like VNX5100 and VNX5500.
45
 About VNX2 series, i don't know whether the plugin will be able to work with them. Maybe it would need some corrections
46
 in command-line backend. The same situation is with other EMC systems, so i encourage you to try and fix the plugin. 
73
 The plugin has been written for being compatible with EMC VNX5300 Storage 
74
 system, as this is the only EMC storage which i have.
75
 By the way, i am pretty sure it can also work with other VNX1 storages, like
76
 VNX5100 and VNX5500.
77
 About VNX2 series, i don't know whether the plugin will be able to work with 
78
 them. Maybe it would need some corrections in command-line backend. The same
79
 situation is with other EMC systems, so i encourage you to try and fix the 
80
 plugin. 
47 81

  
48 82
=head1 CONFIGURATION
49 83

  
50
 The plugin uses SSH to connect to Control Stations. It's possible to use 'nasadmin' user, but it would be better
51
 if you create read-only global user by Unisphere Client. The user should have only Operator role.
52
 I created "operator" user but due to the fact that Control Stations already had one internal "operator" user,
53
 the new one was called "operator1". So be careful. After that, copy .bash_profile from /home/nasadmin to a newly created
84
 The plugin uses SSH to connect to Control Stations. It's possible to use 
85
 'nasadmin' user, but it would be better if you create read-only global user by
86
 Unisphere Client. The user should have only Operator role.
87
 I created "operator" user but due to the fact that Control Stations already
88
 had one internal "operator" user, the new one was called "operator1". So be 
89
 careful. After that, copy .bash_profile from /home/nasadmin to a newly created
54 90
 /home/operator1
55 91
 
56
 On munin-node side choose a user which will be used to connect through SSH. Generally user "munin" is ok. Then,
57
 execute "sudo su munin -s /bin/bash", "ssh-keygen" and "ssh-copy-id" to both Control Stations with newly created 
92
 On munin-node side choose a user which will be used to connect through SSH.
93
 Generally user "munin" is ok. Then, execute "sudo su munin -s /bin/bash", 
94
 "ssh-keygen" and "ssh-copy-id" to both Control Stations with newly created 
58 95
 user.
59 96
 
60
 Make a link from /usr/share/munin/plugins/emc_vnx_file_stats to /etc/munin/plugins/.
61
 If you want to get NFS statistics, name the link as "emc_vnx_file_nfs_stats_<NAME>", otherwise to get Basic Datamover
62
 statistics you have to name it "emc_vnx_file_basicdm_stats_<NAME>", where <NAME> is any arbitrary name of your 
63
 storage system. The plugin will return <NAME> in its answer as "host_name" field.
97
 Make a link from /usr/share/munin/plugins/emc_vnx_file_stats to 
98
 /etc/munin/plugins/. If you want to get NFS statistics, name the link as 
99
 "emc_vnx_file_nfs_stats_<NAME>", otherwise to get Basic Datamover statistics
100
 you have to name it "emc_vnx_file_basicdm_stats_<NAME>", where <NAME> is any
101
 arbitrary name of your storage system. The plugin will return <NAME> in its 
102
 answer as "host_name" field.
64 103

  
65 104
 For example, assume your storage system is called "VNX5300".
66
 Make a configuration file at /etc/munin/plugin-conf.d/emc_vnx_file_stats_VNX5300
105
 Make a configuration file at 
106
 /etc/munin/plugin-conf.d/emc_vnx_file_stats_VNX5300
67 107
 
68 108
 [emc_vnx_file_*]
69
 user munin							# SSH Client local user
70
 env.username operator1						# Remote user with Operator role
71
 env.cs_addr 192.168.1.1 192.168.1.2				# Control Stations addresses
72
 env.nas_servers server_2 server_3				# This is the default value and can be omitteda
109
 user munin				
110
 env.username operator1				
111
 env.cs_addr 192.168.1.1 192.168.1.2		
112
 env.nas_servers server_2 server_3		
113

  
114
 Where: 
115
 user - SSH Client local user
116
 env.username - Remote user with Operator role
117
 env.cs_addr - Control Stations addresses
118
 env.nas_servers - This is the default value and can be omitted
73 119

  
74 120
=head1 HISTORY
75 121

  

Formats disponibles : Unified diff