Data Infrastructure Management Software Discussions
Data Infrastructure Management Software Discussions
[2016-06-15 19:42:48] [NORMAL ] [main] Poller will monitor a [FILER] at [192.168.110.50:443]
[2016-06-15 19:42:48] [NORMAL ] [main] Poller will use [password] authentication with username [opmadmin] and password [**********]
[2016-06-15 19:42:48] [WARNING] [connect] Setting HTTP/1.0 because reverse hostname resolution (IP -> hostname) fails. To enable HTTP/1.1 ensure reverse hostname resolution succeeds.
[2016-06-15 19:42:48] [DEBUG ] [sysinfo] Updating system-info cache
[2016-06-15 19:42:50] [WARNING] [sysinfo] Update of system-info cache DOT Version failed with reason: Authorization failed
Check the IP address is the cluster lif.
Check the opmadmin account has been created on the cluster with the correct password and privileges.
You could also try the admin account temporarily to rule out an account issue.
Cheers,
Chris
Which would be?
SCORSAN::> network interface show
Logical Status Network Current Current Is
Vserver Interface Admin/Oper Address/Mask Node Port Home
----------- ---------- ---------- ------------------ ------------- ------- ----
Cluster
SCORSAN01_clus1
up/up 169.254.179.178/16 SCORSAN01 e0a true
SCORSAN01_clus2
up/up 169.254.191.27/16 SCORSAN01 e0c true
SCORSAN02_clus1
up/up 169.254.99.148/16 SCORSAN02 e0a true
SCORSAN02_clus2
up/up 169.254.96.93/16 SCORSAN02 e0c true
SCORSAN
SCORSAN01_node_mgmt
up/up 192.168.110.51/24 SCORSAN01 e0M true
SCORSAN02_node_mgmt
up/up 192.168.110.52/24 SCORSAN02 e0M true
cluster_mgmt up/up 192.168.110.50/24 SCORSAN01 e0M true
scorsan1_icl up/up 172.29.1.207/24 SCORSAN01 a10g-11 true
scorsan2_icl up/up 172.29.1.208/24 SCORSAN02 a10g-11 true
scorsvm01
cifs_01 up/up 172.29.1.201/24 SCORSAN01 a10g-11 true
cifs_02 up/up 172.29.1.202/24 SCORSAN02 a10g-11 true
iscsi_01 up/up 172.29.62.5/24 SCORSAN01 a10g-13 true
iscsi_02 up/up 172.29.62.6/24 SCORSAN02 a10g-13 true
mgmt_lif up/up 192.168.110.55/24 SCORSAN01 e0i true
nfs_10 up/up 172.29.61.10/24 SCORSAN02 a10g-12 true
nfs_11 up/up 172.29.61.11/24 SCORSAN01 a10g-12 true
nfs_12 up/up 172.29.61.12/24 SCORSAN02 a10g-12 true
nfs_13 up/up 172.29.61.13/24 SCORSAN01 a10g-12 true
nfs_14 up/up 172.29.61.14/24 SCORSAN02 a10g-12 true
nfs_15 up/up 172.29.61.15/24 SCORSAN01 a10g-12 true
nfs_16 up/up 172.29.61.16/24 SCORSAN02 a10g-12 true
nfs_17 up/up 172.29.61.17/24 SCORSAN01 a10g-12 true
nfs_18 up/up 172.29.61.18/24 SCORSAN02 a10g-12 true
nfs_19 up/up 172.29.61.19/24 SCORSAN01 a10g-12 true
nfs_20 up/up 172.29.61.20/24 SCORSAN02 a10g-12 true
nfs_5 up/up 172.29.61.5/24 SCORSAN01 a10g-12 true
nfs_6 up/up 172.29.61.6/24 SCORSAN01 a10g-12 true
nfs_7 up/up 172.29.61.7/24 SCORSAN01 a10g-12 true
nfs_8 up/up 172.29.61.8/24 SCORSAN01 a10g-12 true
nfs_9 up/up 172.29.61.9/24 SCORSAN02 a10g-12 true
30 entries were displayed.
The list of cluster_mgt lifs can be shown using:
blob1::> net int show -role cluster-mgmt (network interface show) Logical Status Network Current Current Is Vserver Interface Admin/Oper Address/Mask Node Port Home ----------- ---------- ---------- ------------------ ------------- ------- ---- blob1 cluster_mgmt up/up 10.64.32.220/24 mt_stc4009 e0a true
From the names of your LIFs it looks like you are talking to a cluster lif. So then the Authorization failed message is telling you that the account is still incorrect.
I would just create a new user as stated in the Harvest admin guide:
security login role create -role netapp-harvest-role -access readonly -cmddirname "version" security login role create -role netapp-harvest-role -access readonly -cmddirname "cluster identity show" security login role create -role netapp-harvest-role -access readonly -cmddirname "cluster show" security login role create -role netapp-harvest-role -access readonly -cmddirname "system node show" security login role create -role netapp-harvest-role -access readonly -cmddirname "statistics" security login role create -role netapp-harvest-role -access readonly -cmddirname "lun show" security login role create -role netapp-harvest-role -access readonly -cmddirname "network interface show" security login role create -role netapp-harvest-role -access readonly -cmddirname "qos workload show"
security login create -user-or-group-name netapp-harvest -application ontapi -role netapp-harvest-role -authmethod password
Then update your netapp-harvest.conf file poller section to this:
[SCORSAN]
hostname = 192.168.110.50
username = netapp-harvest
password = YOUR_PASSWORD
site = OR
And restart the poller:
/opt/netapp-harvest/netapp-manager -restart
Cheers,
Chris
This is just some of the output, but it looks like it's working after I added the account to the Netapp. I attached a screenshot also.
I'm a network engineer that shouldn't even be working on this, but take a look at the screenshot and see if you think it's working correctly.
Thanks for all your help.
[vdi_02-wid1352.DELAY_CENTER_NETWORK] [wait_time] = [0]
[2016-06-16 11:02:06] [DEBUG ] [workload_detail_volume][SCORSAN02:kernel:vdi_02-wid1352.DELAY_CENTER_NETWORK][vdi_02-wid1352.DELAY_CENTER_NETWORK] [service_time] = [0]
[2016-06-16 11:02:06] [DEBUG ] [workload_detail_volume][SCORSAN02:kernel:vdi_02-wid1352.DELAY_CENTER_NETWORK][vdi_02-wid1352.DELAY_CENTER_NETWORK] [wait_time] = [0]
[2016-06-16 11:02:06] [DEBUG ] [workload_detail_volume][SCORSAN01:kernel:vdi_02-wid1352.DELAY_CENTER_QOS_LIMIT][vdi_02-wid1352.DELAY_CENTER_QOS_LIMIT] [service_time] = [0]
[2016-06-16 11:02:06] [DEBUG ] [workload_detail_volume][SCORSAN01:kernel:vdi_02-wid1352.DELAY_CENTER_QOS_LIMIT][vdi_02-wid1352.DELAY_CENTER_QOS_LIMIT] [wait_time] = [0]
[2016-06-16 11:02:06] [DEBUG ] [workload_detail_volume][SCORSAN02:kernel:vdi_02-wid1352.DELAY_CENTER_QOS_LIMIT][vdi_02-wid1352.DELAY_CENTER_QOS_LIMIT] [service_time] = [0]
[2016-06-16 11:02:06] [DEBUG ] [workload_detail_volume][SCORSAN02:kernel:vdi_02-wid1352.DELAY_CENTER_QOS_LIMIT][vdi_02-wid1352.DELAY_CENTER_QOS_LIMIT] [wait_time] = [0]
[2016-06-16 11:02:06] [DEBUG ] [workload_detail_volume][SCORSAN01:kernel:vdi_sas-wid13212.CPU_dblade][vdi_sas-wid13212.CPU_dblade] [service_time] = [1268560475543]
[2016-06-16 11:02:06] [DEBUG ] [workload_detail_volume][SCORSAN01:kernel:vdi_sas-wid13212.CPU_dblade][vdi_sas-wid13212.CPU_dblade] [wait_time] = [3984048371222]
[2016-06-16 11:02:06] [DEBUG ] [workload_detail_volume][SCORSAN02:kernel:vdi_sas-wid13212.CPU_dblade][vdi_sas-wid13212.CPU_dblade] [service_time] = [0]
[2016-06-16 11:02:06] [DEBUG ] [workload_detail_volume][SCORSAN02:kernel:vdi_sas-wid13212.CPU_dblade][vdi_sas-wid13212.CPU_dblade] [wait_time] = [0]
[2016-06-16 11:02:06] [DEBUG ] [workload_detail_volume][SCORSAN01:kernel:vdi_sas-wid13212.CPU_nblade][vdi_sas-wid13212.CPU_nblade] [service_time] = [857995623192]
[2016-06-16 11:02:06] [DEBUG ] [workload_detail_volume][SCORSAN01:kernel:vdi_sas-wid13212.CPU_nblade][vdi_sas-wid13212.CPU_nblade] [wait_time] = [1275958009261]
[2016-06-16 11:02:06] [DEBUG ] [workload_detail_volume][SCORSAN02:kernel:vdi_sas-wid13212.CPU_nblade][vdi_sas-wid13212.CPU_nblade] [service_time] = [0]
[2016-06-16 11:02:06] [DEBUG ] [workload_detail_volume][SCORSAN02:kernel:vdi_sas-wid13212.CPU_nblade][vdi_sas-wid13212.CPU_nblade] [wait_time] = [0]
[2016-06-16 11:02:06] [DEBUG ] [workload_detail_volume][SCORSAN01:kernel:vdi_sas-wid13212.DELAY_CENTER_CLUSTER_INTERCONNECT][vdi_sas-wid13212.DELAY_CENTER_CLUSTER_INTERCONNECT] [service_time] = [0]
[2016-06-16 11:02:06] [DEBUG ] [workload_detail_volume][SCORSAN01:kernel:vdi_sas-wid13212.DELAY_CENTER_CLUSTER_INTERCONNECT][vdi_sas-wid13212.DELAY_CENTER_CLUSTER_INTERCONNECT] [wait_time] = [0]
[2016-06-16 11:02:06] [DEBUG ] [workload_detail_volume][SCORSAN02:kernel:vdi_sas-wid13212.DELAY_CENTER_CLUSTER_INTERCONNECT][vdi_sas-wid13212.DELAY_CENTER_CLUSTER_INTERCONNECT] [service_time] = [0]
[2016-06-16 11:02:06] [DEBUG ] [workload_detail_volume][SCORSAN02:kernel:vdi_sas-wid13212.DELAY_CENTER_CLUSTER_INTERCONNECT][vdi_sas-wid13212.DELAY_CENTER_CLUSTER_INTERCONNECT] [wait_time] = [0]
[2016-06-16 11:02:06] [DEBUG ] [workload_detail_volume][SCORSAN01:kernel:vdi_sas-wid13212.DELAY_CENTER_DISK_IO][vdi_sas-wid13212.DELAY_CENTER_DISK_IO] [service_time] = [0]
[2016-06-16 11:02:06] [DEBUG ] [workload_detail_volume][SCORSAN01:kernel:vdi_sas-wid13212.DELAY_CENTER_DISK_IO][vdi_sas-wid13212.DELAY_CENTER_DISK_IO] [wait_time] = [674655900722]
[2016-06-16 11:02:06] [DEBUG ] [workload_detail_volume][SCORSAN02:kernel:vdi_sas-wid13212.DELAY_CENTER_DISK_IO][vdi_sas-wid13212.DELAY_CENTER_DISK_IO] [service_time] = [0]
[2016-06-16 11:02:06] [DEBUG ] [workload_detail_volume][SCORSAN02:kernel:vdi_sas-wid13212.DELAY_CENTER_DISK_IO][vdi_sas-wid13212.DELAY_CENTER_DISK_IO] [wait_time] = [0]
[2016-06-16 11:02:06] [DEBUG ] [workload_detail_volume][SCORSAN01:kernel:vdi_sas-wid13212.DELAY_CENTER_NETWORK][vdi_sas-wid13212.DELAY_CENTER_NETWORK] [service_time] = [0]
[2016-06-16 11:02:06] [DEBUG ] [workload_detail_volume][SCORSAN01:kernel:vdi_sas-wid13212.DELAY_CENTER_NETWORK][vdi_sas-wid13212.DELAY_CENTER_NETWORK] [wait_time] = [0]
[2016-06-16 11:02:06] [DEBUG ] [workload_detail_volume][SCORSAN02:kernel:vdi_sas-wid13212.DELAY_CENTER_NETWORK][vdi_sas-wid13212.DELAY_CENTER_NETWORK] [service_time] = [0]
[2016-06-16 11:02:06] [DEBUG ] [workload_detail_volume][SCORSAN02:kernel:vdi_sas-wid13212.DELAY_CENTER_NETWORK][vdi_sas-wid13212.DELAY_CENTER_NETWORK] [wait_time] = [0]
[2016-06-16 11:02:06] [DEBUG ] [workload_detail_volume][SCORSAN01:kernel:vdi_sas-wid13212.DELAY_CENTER_QOS_LIMIT][vdi_sas-wid13212.DELAY_CENTER_QOS_LIMIT] [service_time] = [0]
[2016-06-16 11:02:06] [DEBUG ] [workload_detail_volume][SCORSAN01:kernel:vdi_sas-wid13212.DELAY_CENTER_QOS_LIMIT][vdi_sas-wid13212.DELAY_CENTER_QOS_LIMIT] [wait_time] = [0]
[2016-06-16 11:02:06] [DEBUG ] [workload_detail_volume][SCORSAN02:kernel:vdi_sas-wid13212.DELAY_CENTER_QOS_LIMIT][vdi_sas-wid13212.DELAY_CENTER_QOS_LIMIT] [service_time] = [0]
[2016-06-16 11:02:06] [DEBUG ] [workload_detail_volume][SCORSAN02:kernel:vdi_sas-wid13212.DELAY_CENTER_QOS_LIMIT][vdi_sas-wid13212.DELAY_CENTER_QOS_LIMIT] [wait_time] = [0]
[2016-06-16 11:02:06] [DEBUG ] [workload_detail_volume] data-list poller next refresh at [2016-06-16 11:03:00]
[2016-06-16 11:02:06] [DEBUG ] Sleeping [54] seconds
Yes! You have data flowing in now!! I would restart it now without the verbose (-v) flag.
Cheers,
Chris Madden
Storage Architect, NetApp EMEA (and author of Harvest)
Blog: It all begins with data
If this post resolved your issue, please help others by selecting ACCEPT AS SOLUTION or adding a KUDO or both!
One last question, my implentor told me to get rid of the 7 stuff, not sure what that is, but how do I do that. Something about reducing cluter.
If you don't have 7-mode you can remove the unneeded dashboards.
In Grafana just click on the dashboard list, and then on the dashboard with 7-mode in the name to load it:
Then click delete dashboard:
And repeat for all those unneeded dashboards.
Cheers,
Chris
Deployed the 2.1.5 OVA, installed NMSDK via the GUI and Harvest 1.3 via CLI. Trying to get Harvest to start but getting the following:
root@cbivadva01eus:/opt/netapp-harvest# ./netapp-manager -start
STATUS POLLER GROUP
############### #################### ##################
[STARTED] CLUSTER01 US
Can't locate NaServer.pm in @INC (you may need to install the NaServer module) (@INC contains: /opt/netapp-harvest/lib /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.20.2 /usr/local/share/perl/5.20.2 /usr/lib/x86_64-linux-gnu/perl5/5.20 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.20 /usr/share/perl/5.20 /usr/local/lib/site_perl .) at /opt/netapp-harvest/netapp-worker line 37.
BEGIN failed--compilation aborted at /opt/netapp-harvest/netapp-worker line 37.
root@cbivadva01eus:/opt/netapp-harvest# ./netapp-manager -status
STATUS POLLER GROUP
############### #################### ##################
[NOT RUNNING] CLUSTER01 US
Where can I start to look for a resolution... pretty sure I've overlooked something here but I'm at a loss for what it might be at the moment.
The error indicates that harvest can't find the SDK in any perl include path.
Actually the SDK seems to install quite nicely using the Admin GUI. I have since re-deployed the OVA (2.1.5) to start with a clean slate.
So I go to the Admin GUI and install the SDK v5.6
I know I can't install Harvest using the GUI so I use the GUI just to download/extract the Harvest files to /tmp/upgrade-bundle then I install Harvest manually per the Harvest Admin Guide.
I run the command for Ubuntu logged into the ADVA concole as 'root':
dpkg -i netapp-harvest_1.3_all.deb
and I get this error:
dpkg: error processing archive netapp-harvest_1.3_all.deb (--install):
cannot access archive: No such file or directory
Errors were encountered while processing:
netapp-harvest_1.3_all.deb
I recall deploying the OVA being a LOT more simpler than this as recently as last year.
Hi @nicholsongc
The ADVA expects you to load the SDK and Harvest using the maintenance GUI.
Load NetApp Harvest and the SDK from the tools->Maintenance tab, “upload package” button, and then after uploaded the “upgrade now” button.
The ADVA will unpack and install the software for you. The files to upload are:
The Harvest part can be a little confusing because when Yann released the OVA I only had a tgz package format for the software. In v1.3 I created native package formats but when I tried to have these posted to the Toolchest I learned they don't support file formats like .deb, so I decided to put all the installer types into one zip file. So for clarity, you need to upload the tgz file to the ADVA and it should work!
I think Yann explains it in the video on his blog: http://ybontap.tynsoe.org/wordpress/graphite-va/
Cheers,
Chris Madden
Solution Architect - 3rd Platform - Systems Engineering NetApp EMEA (and author of Harvest)
Blog: It all begins with data
If this post resolved your issue, please help others by selecting ACCEPT AS SOLUTION or adding a KUDO or both!
Thank you @madden! I've moved from NetApp PSC to customer so I appreciate the assitance. Harvest is up and running now I'm hitting error 13001 trying to get OCUM 6.2P1 configured for capacity.
I got the same error trying to add 7-mode systems to Harvest until Yann enlightened me that I needed TLS enabled. Does anyone have any guidance on what I need to do to get OCUM 6.2P1 configured for Harvest? I have both a cDOT and 7-Mode of OCUM running currently.
Hi @nicholsongc
You are running an older version of OCUM and probably hitting this issue:
Cheers,
Chris Madden
Solution Architect - 3rd Platform - Systems Engineering NetApp EMEA (and author of Harvest)
Blog: It all begins with data
If this post resolved your issue, please help others by selecting ACCEPT AS SOLUTION or adding a KUDO or both!
I ran in to same issue and part of troubleshooting i found library files are not loading/detecting properly.
Download the available SDK from NetApp site and execute the below commands.
### Download from the NetApp Support Site and install using (modify version if needed):
unzip -j netapp-manageability-sdk-5.6.zip netapp-manageability-sdk-5.6/lib/perl/NetApp/* -d /opt/netapp-harvest/lib
restart netaapp-harvest service.
If possible take backup of existing SDK lib directory.