We are running 3par 3.1.3 MU2, T800.
Go two nodes hung due to CLI connections execeed 64, HP said work around is to login as root and issue. onallnodes killall tpdtcl
There is a known bug in 3.1.3 MU2, my problem is I cant find out root password and HP want share cause you can do real damage as root level access.
Any ideas on root password logging into nodes via serial cable?
Thanks
Root access for 3.1.3 MU2
Re: Root access for 3.1.3 MU2
if you've been dealing with HP, i would ask them to login as spdood and clear that for you.
failing that are you logged in from IMC on your pc or a collegues pc? If so go to security & domains tab and select conections and you will see the current connection on there, you can close connection from that GUI. Please note connections from IMC often take up 4 - 6 connection per user. so it might be worth asking a collegue to log out to free up some connections.
failing that are you logged in from IMC on your pc or a collegues pc? If so go to security & domains tab and select conections and you will see the current connection on there, you can close connection from that GUI. Please note connections from IMC often take up 4 - 6 connection per user. so it might be worth asking a collegue to log out to free up some connections.
Re: Root access for 3.1.3 MU2
Issue has been resolved.
First issue is a bug in the code 3.1.3 MU2, 3.1.3 MU3 should resolve it, its in the release notes for 3.1.3 from HP.
To clear the TPDCTL processes you have to get access to root at the node level. I logged into SP via root and the ssh into the array via root, which it will allow you to. I ran a KILL command for all the TPDCTL processes and that unhung two nodes out of the 8 I had, worked great. I could not work with HP since I had no active contract.
I got the SSH command from a resource on this forum, so he was very helpful, got the kill command from a HP resource I had. Must be very careful at root level since you are the process level of the array.
Thank you
First issue is a bug in the code 3.1.3 MU2, 3.1.3 MU3 should resolve it, its in the release notes for 3.1.3 from HP.
To clear the TPDCTL processes you have to get access to root at the node level. I logged into SP via root and the ssh into the array via root, which it will allow you to. I ran a KILL command for all the TPDCTL processes and that unhung two nodes out of the 8 I had, worked great. I could not work with HP since I had no active contract.
I got the SSH command from a resource on this forum, so he was very helpful, got the kill command from a HP resource I had. Must be very careful at root level since you are the process level of the array.
Thank you
Re: Root access for 3.1.3 MU2
It is still present in 3.2.2 (MU2) had it twice on an array. Was triggered by a disk failure in a node. Made access (management) to the array impossible until this was done.
-
- Posts: 6
- Joined: Fri Jun 23, 2023 8:47 am
Re: Root access for 3.1.3 MU2
Were you able to SSH to 3PAR via SP when you have 3.3.2 version? Seems like HPE strengthen the security and even by authenticating with the ssh key it still asks for the time-based/encrypted password. Wondering if anyone got around that.
For anyone trying to get a root access to SP:
- GRUB loader is protected with a password so you need to boot with a live CD (such as gparted)
- mount /dev/sda1 /mnt
- navigate to /mnt/grub and comment the password part in the grub.conf file
- restart the VM and append at the end of the kernel line: init=/bin/bash
- remount the partition to rw: mount / -rw -o remount
- passwd command to change the root password, then restart the VM
SSH keys of the 3PAR are stored under /home/hpesupport/.ssh
For anyone trying to get a root access to SP:
- GRUB loader is protected with a password so you need to boot with a live CD (such as gparted)
- mount /dev/sda1 /mnt
- navigate to /mnt/grub and comment the password part in the grub.conf file
- restart the VM and append at the end of the kernel line: init=/bin/bash
- remount the partition to rw: mount / -rw -o remount
- passwd command to change the root password, then restart the VM
SSH keys of the 3PAR are stored under /home/hpesupport/.ssh