Andrea Chiavegato
asked on
Problem SSH connection with ESX 4.1.0 348481 UPDATE 1 - URGENT !!
We have two ESX vSphere structures:
structure "A" -> with a vSphere 4.0.1
structure "B" -> with ESX version 4.1.0, 348481 UPDATE 1 (latest version available today)
We use Veeam Backup & Replication v.5 for backups of VM
- in the structure "A" I don't have problem
- in the structure "B" the phisical HOSTS don't see the physical storage connected to ESX (fiber channel and iSCSI).
In the structure "B" we have enabled the following:
1) Local TSM enable (see attachment "Structure B - Local TSM enable.jpg")
2) Remote TSM enable SSH (see attachment "Structure B - Remote TSM SSH enable.jpg")
In the structure "B", I think that the problem may be with communication in SSH.
For example: if I use SSH with putty, I enter in the host but I can not see the folder as the "ssh", which should be inside the folder "etc" (see attachment "new host - no show folder SSH.pdf")
In the old structure "A" attached, you see attachment "old host - show folder SSH - ok.jpg"
So, in I also notice that the prompt is "root@...", in the new structure "B" is different, but I use always the root account.
If I use Veeam also in the structure "A" (Structure A - show SSH connection TAG.jpg) appears TAG SSH connection, while in structure "B" this does not appear (Structure B - don't show SSH connection TAG.jpg)
I do not think is a problem of Veeam, I think it is a problem of physical configuration of ESX.
Is very urgent.
Thanks
new-host---no-show-folder-SSH.jpg
old-host---show-folder-SSH---ok.jpg
Structure-A---show-SSH-connectio.jpg
Structure-B---don-t-show-SSH-con.jpg
Structure-B---Local-TSM-enable.jpg
Structure-B---Remote-TSM-SSH-ena.jpg
structure "A" -> with a vSphere 4.0.1
structure "B" -> with ESX version 4.1.0, 348481 UPDATE 1 (latest version available today)
We use Veeam Backup & Replication v.5 for backups of VM
- in the structure "A" I don't have problem
- in the structure "B" the phisical HOSTS don't see the physical storage connected to ESX (fiber channel and iSCSI).
In the structure "B" we have enabled the following:
1) Local TSM enable (see attachment "Structure B - Local TSM enable.jpg")
2) Remote TSM enable SSH (see attachment "Structure B - Remote TSM SSH enable.jpg")
In the structure "B", I think that the problem may be with communication in SSH.
For example: if I use SSH with putty, I enter in the host but I can not see the folder as the "ssh", which should be inside the folder "etc" (see attachment "new host - no show folder SSH.pdf")
In the old structure "A" attached, you see attachment "old host - show folder SSH - ok.jpg"
So, in I also notice that the prompt is "root@...", in the new structure "B" is different, but I use always the root account.
If I use Veeam also in the structure "A" (Structure A - show SSH connection TAG.jpg) appears TAG SSH connection, while in structure "B" this does not appear (Structure B - don't show SSH connection TAG.jpg)
I do not think is a problem of Veeam, I think it is a problem of physical configuration of ESX.
Is very urgent.
Thanks
new-host---no-show-folder-SSH.jpg
old-host---show-folder-SSH---ok.jpg
Structure-A---show-SSH-connectio.jpg
Structure-B---don-t-show-SSH-con.jpg
Structure-B---Local-TSM-enable.jpg
Structure-B---Remote-TSM-SSH-ena.jpg
If you are saying that the ESX 4.1 hosts or the physical backup host can't see the iSCSI or FC storage, then the issue isn't with SSH... it's probably a problem with zoning or presentation of the LUN's from the SAN to the host(s).
ASKER
No, the hosts see the storage Fibre Channel and iSCSI VM working properly and regularly.
When I use Veeam Backup or FAST SCP (which uses SSH API of VMWare) I can not do the backup on storage. This is why I did not request any authentication but only SSH authentication SOAP.
Thanks
When I use Veeam Backup or FAST SCP (which uses SSH API of VMWare) I can not do the backup on storage. This is why I did not request any authentication but only SSH authentication SOAP.
Thanks
1.) Go and edit the /etc/inetd.conf file type : vi /etc/inetd.conf
2.) Uncomment the line where you can see “#ssh” (line 32). Remove the “#” mark at the beginning.
3.) Then press ESC and type in :wq!
4.) Then run the command /sbin/services.sh restart
Source: http://www.vmug.nl/modules.php?name=Forums&file=viewtopic&t=5288
That should do the trick, also check if root has access.
2.) Uncomment the line where you can see “#ssh” (line 32). Remove the “#” mark at the beginning.
3.) Then press ESC and type in :wq!
4.) Then run the command /sbin/services.sh restart
Source: http://www.vmug.nl/modules.php?name=Forums&file=viewtopic&t=5288
That should do the trick, also check if root has access.
Is this the "free" version of ESXi?
ASKER
No, is the enterprise PLUS.
thanks
thanks
ASKER
for "PenguinN" - in the file the "#" is not present - see the attachment.
do you have an another idea ?
file-inetd.conf.jpg
do you have an another idea ?
file-inetd.conf.jpg
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.