you should always be able to ssh to the node using ssh -i /etc/vcl/vcl.key 192.168.10.48 from your management node as root.
The admin account is just the user account you made the reservation as while logged into the VCL web interface. On Wed, May 6, 2015 at 8:26 AM, Elwin Litchfield <[email protected]> wrote: > After some investigation I thought the problem connecting via port 22 was in > external_sshd_config because the LISTENADDRESS 131.247.29.132 was > configured. > A new user admin was created, but the root password was changed. I was not > able to change the LISTENADDRESS to 192.168.10.48, the management network, > using gedit. > I was able to change it using vi. sshd service could not be restarted > because the root password must have been changed when the new admin user was > created. none of the known user passwords would work to restart sshd. > After reboot I was able to connect to 192.168.10.48 via putty or WinSCP, but > not logon. I tried all combinations of known users & passwords, all were > Access denied. But ssh -i /etc/vcl/vcl.key 192.168.10.48 connected. Also > the LISTENADDRESS 192.168.10.48 I had configured had changed back to > 131.247.29.132 > > Looks like I lost the failing connection via ssh condition by rebooting. I > checked netstat before the reboot and 192.168.10.48:ssh was there. After > reboot both 131.247.29.132:ssh & 192.168.10.48:ssh were there. > > Any ideas? Or what to look for before rebooting? > > > On Tue, May 5, 2015 at 10:25 AM, Elwin Litchfield <[email protected]> > wrote: >> >> no route to host error means that port 22 is not accessible True unable >> to putty to the host, also ssh -i /etc/vcl/vcl.key 192.168.10.48 worked in >> the past, but is now failing. I had a problem with a XenServer Centos 6 >> VM changing the ssh listen IP addresses to other networks from the >> management network. I removed all networks except the Public & Private >> networks but have not been able to test yet. >> >> Is VM7Cent6VCL1 pingable from the management node? Yes >> >> If not check your, maybe your dhcp settings are not correct and it's >> not getting an address on your VCL private network? DHCP settings >> match the ifconfig in VM6Cent6VCL1. >> >> Also did you figure out the MAC address to use? It looks like >> 00:50:56:XX:YY:ZZ is ok if the XX is not a high value. 00:50:56:3F:40:E3 >> worked till the VM quit listening to port 22 on the management network. I >> will research the XX value to determine the range that will work. >> >> It appears that I have two image name that point to the same virtual >> machine - VM7Cent6VCL1, but have two virtual image machines. I am in the >> process of installing a new VM to test using a clean install without on the >> fly modifications. >> >> >> On Tue, May 5, 2015 at 9:38 AM, Aaron Peeler <[email protected]> wrote: >>> >>> no route to host error means that port 22 is not accessible >>> >>> Is VM7Cent6VCL1 pingable from the management node? >>> >>> If not check your, maybe your dhcp settings are not correct and it's >>> not getting an address on your VCL private network? >>> >>> Also did you figure out the MAC address to use? >>> >>> >>> >>> >>> >>> On Mon, May 4, 2015 at 8:52 PM, Litchfield, Elwin L. >>> <[email protected]> wrote: >>> > The reservation expired & the VM is still powered on. Where should I >>> > be looking? >>> > >>> > Lewis Litchfield >>> > Technology Services – Viking Center Lab >>> > University of South Florida Sarasota-Manatee >>> > 941-359-4231 >>> > >>> >>> >>> >>> -- >>> Aaron Peeler >>> Program Manager >>> Virtual Computing Lab >>> NC State University >>> >>> All electronic mail messages in connection with State business which >>> are sent to or received by this account are subject to the NC Public >>> Records Law and may be disclosed to third parties. >> >> > -- Aaron Peeler Program Manager Virtual Computing Lab NC State University All electronic mail messages in connection with State business which are sent to or received by this account are subject to the NC Public Records Law and may be disclosed to third parties.
