Skip to main content

developerWorks >  IBM Systems  >  Forums  >  IBM Systems Director Forum (System x, System z, Power Systems)  >  developerWorks

Use of non-standard SSH port with Director    Point your RSS reader here for a feed of the latest messages in this thread


     

 
 

My developerWorks
 Welcome, Guest
Sign in or register
This question is not answered.

Permlink Replies: 2 - Pages: 1 - Last Post: Nov 5, 2009 5:45 PM Last Post By: gcorneau Threads: [ Previous | Next ]
TimGilson

Posts: 35
Registered: Jul 27, 2007 04:44:53 AM
Use of non-standard SSH port with Director
Posted: Sep 28, 2009 12:33:11 PM
 
Click to report abuse...   Click to reply to this thread Reply
IBM System Director uses the default port 22 for SSH. We use a non-
standard port of 500 for SSH on our AIX and VIOS LPARs. Our HMCs are on
their standard port of 22.

Because of this, Director can communicate with our HMCs but not to our
AIX or VIOS LPARs. There is no mechanism to configure communication
with the HMCs on port 22 simultaneously with our LPARs on port 500. The
local /etc/ssh/ssh_config file on the Director LPAR is not honoured by
IBM Director, port 22 appears to be coded into Director for SSH. As a result of
this, we cannot deploy IBM Director.

We cannot change the HMC port from 22 (without deviating from the
standard, IBM supported HMC configuration) and cannot change our port
500 so Director must made to be configurable to simultaneously
communicate as required to mixed SSH client ports.

Is there a workaround or something I don't know about?
DirGuy

Posts: 15
Registered: Nov 04, 2009 04:21:35 PM
Re: Use of non-standard SSH port with Director
Posted: Nov 05, 2009 12:56:51 PM   in response to: TimGilson in response to: TimGilson's post
 
Click to report abuse...   Click to reply to this thread Reply
To do this you are going to probably need code written to support the 2nd ssh Service Access Point and Discovery of that SAP. It seems feasible, it's just doesn't appear to be implemented. If it's really needed, try contacting IBM and asking for a feature request and it might show up in the product one day. If you really really need the function now, you can try contacting IBM about a Lab Services engagement to do some custom programming for a fee.
gcorneau

Posts: 194
Registered: Mar 01, 2005 03:15:06 PM
Re: Use of non-standard SSH port with Director
Posted: Nov 05, 2009 05:45:55 PM   in response to: TimGilson in response to: TimGilson's post
 
Click to report abuse...   Click to reply to this thread Reply
Another option would be to upgrade your VIOS LPARs to 2.1.0.10 and use the IBM Systems Director Common Agent instead of Agentless (i.e. SSH) which is available at that level of VIOS code.

I would think that changing this port would also cause problems with the HMC->VIOS communication via "viosvrcmd". That would also reduce the capabilities in managing that type of environment with IBM Systems Director.

Glen Corneau
IBM Power Systems Advanced Technical Support
 Tags
Help

Use the search field to find all types of content in My developerWorks with that tag.

Use the slider bar to see more or fewer tags.

Popular tags shows the top tags for this particular type of content or application that you're viewing.

My tags shows your tags for this particular type of content or application that you're viewing.

 

MoreLess 


Point your RSS reader here for a feed of the latest messages in all forums