When I access the vm and check the events I can see an entry in the log that there is a problem with the sshd application, but it's not specified. I'm clueless here. Any of you have any ideas?
Thanks in advance.
sshd connection issue between host and vmManagement during upgrade 2.0 to 2.1
-
Cliff
sshd connection issue between host and vmManagement during upgrade 2.0 to 2.1
I'm trying to upgrade a bics 2.0 to 2.1. after the command 'k2upgrade2' and following the wizard, the host will connect to the several VMs to backup saved data from the VMs to the USBdisk. When the wizard shows the script, it hangs when trying to backup the files from the vmManagement. When i go back to the linux shell using ctrl+alt+F1, i can see that the host is trying to login on the vm but is blocked; the line "k2admi@{ip@vmManagement} password:" keeps scrolling.
When I access the vm and check the events I can see an entry in the log that there is a problem with the sshd application, but it's not specified. I'm clueless here. Any of you have any ideas?
Thanks in advance.
When I access the vm and check the events I can see an entry in the log that there is a problem with the sshd application, but it's not specified. I'm clueless here. Any of you have any ideas?
Thanks in advance.
-
Cliff
I think the issue is solved.
On the vmManagement there is a programm installed called copssh for the ssh support. In one of the folders, /prog files/copssh/etc/ there is a file called sshd.config. check if it is permitted to access the machine with empty password. there is a parameter there 'PermitEmptyPassword'. there must be another folder called k2admin/.ssh and check if there are any 'key' files (public keys) if not, what i did is copy them from the folder /Administrator/.ssh to the k2admin folder.
go back to the host. login under root or admin and test the connection 'ssh k2admin@{ip@vmManagement}'. if connected without password, $ appears. type exit and run k2upgrade2 again.
cheers.
Clifford
On the vmManagement there is a programm installed called copssh for the ssh support. In one of the folders, /prog files/copssh/etc/ there is a file called sshd.config. check if it is permitted to access the machine with empty password. there is a parameter there 'PermitEmptyPassword'. there must be another folder called k2admin/.ssh and check if there are any 'key' files (public keys) if not, what i did is copy them from the folder /Administrator/.ssh to the k2admin folder.
go back to the host. login under root or admin and test the connection 'ssh k2admin@{ip@vmManagement}'. if connected without password, $ appears. type exit and run k2upgrade2 again.
cheers.
Clifford
-
agiftel
Upgrade 2.0 to 2.1
Hi, have you have success upgrading BICS 2.0 to 2.1 ? I have a lot of issues .. and upgrade is not going fine. I am following TC1266 ed2 step by step... but some steps are missing and is not proprely how Alcatel says on it ( TC ).
Have you??
Thanks for informations
P.S. this question is just to understand if TC is correct at all or... not...
Have you??
Thanks for informations
P.S. this question is just to understand if TC is correct at all or... not...
-
agiftel
Hi, have you have success upgrading BICS 2.0 to 2.1 ? I have a lot of issues .. and upgrade is not going fine. I am following TC1266 ed2 step by step... but some steps are missing and is not proprely how Alcatel says on it ( TC ).
Have you??
Thanks for informations
P.S. this question is just to understand if TC is correct at all or... not...
Have you??
Thanks for informations
P.S. this question is just to understand if TC is correct at all or... not...
-
Cliff
You are correct ... the TC is incomplete. Procedure is not very well documented to say the least. Issues that could arrise, and more inportant, sollutions to those issues, are not mentioned. This also counts for the normal I&M documentation and the BiCS troubleshooting document.
Eventually after 6 days, I had to do a complete new install of the BiCS loosing al UC data. I managed to save the a-lu data. Fortunatly for me the number of UC users were minimal.
Eventually after 6 days, I had to do a complete new install of the BiCS loosing al UC data. I managed to save the a-lu data. Fortunatly for me the number of UC users were minimal.
-
agiftel
