Unexpected keys - LocalHost, PeerAddr, PeerPort

lborek

Hi,

After last upgrade 7.10-1 there is an issue with HPE MSA & Netapp FAS monitoring. 

Error is : 

Unexpected keys - LocalHost, PeerAddr, PeerPort at /usr/share/perl5/LWP/Protocol/http.pm line 33

Logs below. Any chance you guys seen it before? 

Thanks.

HPE MSA2040:

=========================

STORAGE: MSA_DC4_XXX_XXX: DOTHILL

=========================

  TCP connection to "X.X.X.X" on port "5988" is ok

  TCP connection to "X.X.X.X" on port "80" is ok

  TCP connection to "X.X.X.X" on port "5988" is ok

  TCP connection to "X.X.X.X" on port "80" is ok

/usr/bin/wbemcli -noverify -nl ei http://stor2rrd:XXXXX@X.X.X.X:5988/root/dhs:cim_computersystem

/usr/bin/wbemcli -noverify -nl ei http://stor2rrd:XXXXX@X.X.X.X:5988/root/dhs:cim_computersystem

/usr/bin/wbemcli -noverify -nl ei http://stor2rrd:XXXXX@X.X.X.X:5988/root/hpq:cim_computersystem

SMI-S API is ok, going to test Web-browser interface (WBE) through http

/usr/bin/perl /home/stor2rrd/stor2rrd/bin/dothill_apitest.pl stor2rrd XXXXX X.X.X.X http

Request error "Unexpected keys - LocalHost, PeerAddr, PeerPort at /usr/share/perl5/LWP/Protocol/http.pm line 33.

" : http://X.X.X.X/api/login/ :

SMI-S API is ok, going to test Web-browser interface (WBE) through http

/usr/bin/perl /home/stor2rrd/stor2rrd/bin/dothill_apitest.pl stor2rrd XXXXX X.X.X.X http

Request error "Unexpected keys - LocalHost, PeerAddr, PeerPort at /usr/share/perl5/LWP/Protocol/http.pm line 33.

" : http://X.X.X.X/api/login/ :

  connection failed!!

Netapp FAS : 

=========================

STORAGE: DC4_Netapp_X: NETAPP/CMODE

=========================

  TCP connection to "X.X.X.X" on port "22" is ok

  TCP connection to "X.X.X.x" on port "80" is ok

Testing SSH connection ....

/usr/bin/perl /home/stor2rrd/stor2rrd/bin/na_sshtest.pl X.X.X.X stor2rrd XXXXXX 22 "" 30 0 sshtest ssh -o ConnectTimeout=80 -o StrictHostKeyChecking=no -o PreferredAuthentications=publickey -o SendEnv=no CMODE

ontap_version::NetApp Release 9.7P11: Tue Jan 12 18:03:00 EST 2021

system_model::FAS8020

  SSH connection OK

  Testing API connection...

  ERROR Tue Apr 13 12:03:14 2021 na_apitest.pl: API test failed: Unexpected keys - LocalHost, PeerAddr, PeerPort

  INFO Tue Apr 13 12:03:14 2021 HOSTNAME: X.X.X.X, NETAPP MODE: C-mode

  INFO Tue Apr 13 12:03:14 2021 URL: http://X.X.X.X:80/servlets/netapp.servlets.admin.XMLrequest_filer

  API connection failed!!!

Lukas

Hello,

I see this error for the first time. Did this error occur in the previous version? Try this curl command.

echo -n "<user>_<password>" | md5sum | sed 's/ .*//g' | curl -k -X GET -H "Content-Type: application/json" https://<storage_hostname>/api/login/$(</dev/stdin)

where

user - username (HPE MSA2040)

password - password (HPE MSA2040)

storage_hostname - IP address or hostname (HPE MSA2040)

Output will something like

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<RESPONSE VERSION="L100">
  <OBJECT basetype="status" name="status" oid="1">
    <PROPERTY name="response-type" type="string" size="12" draw="false" sort="nosort" display-name="Response Type">Success</PROPERTY>
    <PROPERTY name="response-type-numeric" type="uint32" size="12" draw="false" sort="nosort" display-name="Response Type">0</PROPERTY>
    <PROPERTY name="response" type="string" size="180" draw="true" sort="nosort" display-name="Response">ef3796481f435219c411a3b770666be5</PROPERTY>
    <PROPERTY name="return-code" type="sint32" size="15" draw="false" sort="nosort" display-name="Return Code">1</PROPERTY>
    <PROPERTY name="component-id" type="string" size="80" draw="false" sort="nosort" display-name="Component ID"></PROPERTY>
    <PROPERTY name="time-stamp" type="string" size="25" draw="false" sort="datetime" display-name="Time">2021-04-13 14:04:51</PROPERTY>
    <PROPERTY name="time-stamp-numeric" type="uint32" size="25" draw="false" sort="datetime" display-name="Time">1618322691</PROPERTY>
  </OBJECT>
</RESPONSE>


Thank you

lborek

Hi Lukas,

Both Netapp & MSA were configured with http.  After i move them to htpps communication was restored. In case anyone hit same error in the future. 

Thanks.