Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2043
  • Last Modified:

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
0
Andrea Chiavegato
Asked:
Andrea Chiavegato
2 Solutions
 
Danny McDanielClinical Systems AnalystCommented:
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).
0
 
Andrea ChiavegatoAuthor Commented:
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
0
 
PenguinNCommented:
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.
0
Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

 
Danny McDanielClinical Systems AnalystCommented:
Is this the "free" version of ESXi?
0
 
Andrea ChiavegatoAuthor Commented:
No, is the enterprise PLUS.
thanks
0
 
Andrea ChiavegatoAuthor Commented:
for "PenguinN" - in the file the "#" is not present - see the attachment.

do you have an another idea ?
file-inetd.conf.jpg
0
 
jackiechen858Commented:
From your screenshot, You are using ESXi 4.1 not ESX4.1.



ESXi only has a "Tech Support Mode", not full SSHD, so probably there is no /etc/ssh/ folder at all.

check this http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1017910
0
 
cdrivedaveCommented:
ESXi uses 'dropbear' as the SSH server, which stores its host keys in

/etc/dropbear/dropbear_dss_host_key
and
/etc/dropbear/dropbear_rsa_host_key

There's nothing wrong with the ESXi installation; it's just a different version of the software. ESX is based on redhat and is very 'heavy' compared to ESXi, which is based on busybox and is very 'light'. The file structure, binaries, etc are all completely different and ESX is now at end-of-development.
0

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now