StoreVirtual Storage
1752816 Members
4146 Online
108789 Solutions
New Discussion юеВ

Re: HP SAN 4730 Storevirtual Node error message when trying to update (last of 4 nodes)

 
peyrache
Respected Contributor

Re: HP SAN 4730 Storevirtual Node error message when trying to update (last of 4 nodes)

Shall try manual update ? may be
JY
jtslade
Advisor

Re: HP SAN 4730 Storevirtual Node error message when trying to update (last of 4 nodes)

as in using Support Mode in the CMC (how these were performed) or is there another way like from the command line interface. Can I skip active directory LDAP creation and verificaiton maybe in manual mode?

peyrache
Respected Contributor

Re: HP SAN 4730 Storevirtual Node error message when trying to update (last of 4 nodes)

Manual mode just let you arrange to select package to be installed
peyrache
Respected Contributor

Re: HP SAN 4730 Storevirtual Node error message when trying to update (last of 4 nodes)

May be related ?
Active Directory external authentication
All P4000 and StoreVirtual systems supported by LeftHand OS 10.0 and later which use Active Directory external
authentication
Issue
The CLIQ setadinfo command accepts several keyword-value pairs which are passed through LeftHand OS to the Microsoft Active
Directory server.
The baseDN and bindusername keywords accept text string values which can contain shell meta characters.
These values must be quoted correctly if they are to be successfully processed.
Cause
Active Directory wants to receive quoted strings for the baseDN and bindusername keywords. LeftHand OS will remove the quotes if
they are not double quoted.
For example,
baseDN="DC=john,DC=contoso,DC=com" bindusername="admin@john.contoso.com"
will fail when used with the CLIQ setadinfo command. This will work if additional single quote characters enclose the value.
baseDN='"DC=john,DC=contoso,DC=com"' bindusername='"admin@john.contoso.com"'
Resolution
Use double-quoted string values for the baseDN and bindusername keywords. Here is an example of the entire setadinfo command.
cliq.exe setadinfo login=10.10.10.100 username=admin password=pArx33g
baseDN='"DC=john,DC=contoso,DC=com"' adserver=ldap://10.10.10.137
bindusername='"admin@john.contoso.com"' bindpassword=eocws92uPW testonly=false
Another variation which can be used is the triple quotation, for example,
bindusername="""admin@john.contoso.com"""
jtslade
Advisor

Re: HP SAN 4730 Storevirtual Node error message when trying to update (last of 4 nodes)

Yes Support mode (the Yellowist CMC mode ever)

is what has been used to upgrade 3 of the 4 nodes.

Assen
HPE Pro

Re: HP SAN 4730 Storevirtual Node error message when trying to update (last of 4 nodes)

Hi jtslade,

could it be that the upgrade partition is still mounted?

you could check it from the cliq. Putty in to node (port 16022), log in with CMC credentials.

You can find more info in the HP StoreVirtual LeftHand OS Command Line
Interface User Guide

run the command

utility run="ps -ax"

look for process containing lefthand/upgrade, upgrade or similar

if you find something like the above, reboot the node and start the upgrade again. After reboot the upgrade partition should be unmounted.

BR

Assen


I am an HPE employee
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]

Accept or Kudo

jtslade
Advisor

Re: HP SAN 4730 Storevirtual Node error message when trying to update (last of 4 nodes)

This is the error here:

 

File "/etc/lefthand/brand/common/bin/create-ldap-cfg-tar.py", line 20, in ?
    from lhn import lockfile
EOFError: EOF read where object expected
INFO: created Active Directory config in /root/ldap-cfg.tar.bz2, SHA1 = []
ERROR: Failed to preserve Active Directory configuration.
       /root/ldap-cfg.tar.bz2 is missing from current SAN/iQ version

 

Either the Python script is corrupt (hence no hash on the tar AD).

Its fixable, but only by those that can access the HP SANiQ OS files directly.

 

My last thought on this would be to downgrade the node to 10.0 which as I understand is what had the original AD/LDAP intergration added. then upgrade back.

Its a lost cause. Thank you for everyone's help! Have a great weekend.