Why does N1SM Service Provisioning System use ssh port 70000
We have a problem bringing up N1SMs (1.3.2) SPS (5.2.1) using ssh
as the communication channel protocol between server and remote
agent.
The error message returned says "Unable make ssh connection to "10.103.16.127:70000"."What does that mean?
Why is there an out-of-range 70000 port being used? Why is
the reasoning for it being hidden ... witness the comment inside
the cr_ra_linux_x86_64_5.2.sh remote agent shell.
if [ "$CTYPE" = "ssh" ] ; then
# Do not mention that we hardcoded the port to 70000 since it could be
# confusing to the users
So, how are we to debug this bad port code?
[660 byte] By [
peter_Ca] at [2007-11-26 22:17:02]
# 1
OK, first, Peter, don't make assumptions and slip to early conclusions.
SPS in N1SM (SM) is ONLY used as job engine. Port for ssh is dummy, so forget about it. If you want to use it for something else, definitely NOT recommended, it's too tight to SM.
Generally I would check whether you have properly setup n1smconfig.
Where do you get this error message? Please try to think and write about the problem you are seeing in terms of SM.
I will help you if you tell me your problem, if n1sm is properly installed and setup and n1smconfig was run and setup you shouldn't never witness this AND definitely not see SSH connection to agent on some odd address, SM uses SPS only locally (means 127.0.0.1).
# 2
When I tried to deploy a linux RPM component with N1SPS GUI the
GUI displayed the message as part of its preparation prior to its deployment.
When I searched the remote agent deployment shell (can you call it
a shell file if it contains both shell and binary?) to get a clue on why
a 70000 port number would appear in the error message I saw the comment
# Do not mention that we hardcoded the port to 70000 since it could be
# confusing to the users
Given the extreme sparseness of information displayed in the GUI's error
output which makes debugging difficult, I only had a strange port number
of 70000 as a clue to what might be wrong. Having found it deliberately
set to 70000 and then deliberately not explained to us "users", what was
a user to think?
# 3
AH ... so this doesn't really belong to this forum then ...
"RA deployment shell" can be called an "installer" if you want :)
since I know SPS, I can help you with this & if I were you I wouldn't be upset by the port 70000 (since you're AT&T you should know such port number is not even supported ;) )
so I think your ssh is not good setup in terms of : try to ssh to target node with RA, if you succeed without typing password you should be all set ... the rest of setup is in docs & guides (I'd say: http://docs.sfbay.sun.com/app/docs/doc/819-4445 or http://docs.sfbay.sun.com/app/docs/doc/819-4450 )
# 5
And some extras, try:
ldd /opt/SUNWn1sps/N1_Service_Provisioning_System/agent/lib/upgrade/5.2/linux/libna tive.so
then
fullfill what it needs, if you have 64bit RH, then get a good libstdc++.so.5 , so it will say something like:
# file libstdc++.so.5
libstdc++.so.5: ELF 64-bit LSB shared object, AMD x86-64, version 1 (SYSV), stripped
location of that .so will be /opt/sun/N1_Service_Provisioning_System/common/lib/linux/ or since this seems like upgrade it could be in that upgrade link, depends where we search for libraries (startup script might clarify)
