Online Expert Day - HPE Data Storage - Live Now
April 24/25 - Online Expert Day - HPE Data Storage - Live Now
Read more
System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

Looking for any information on a HPUX system running Ultimate PLUS

zwalker
Occasional Visitor

Looking for any information on a HPUX system running Ultimate PLUS

Ok I have a HP 9000 rp3440 running HPUX 11.23. The box has Ultimate Plus database that I am trying to get into. This was a server that my company bought from someone that upgrade in hopes of being able to use some of the progrom on our pruduction system but we arent reeally sure whats on it. 

The only type of login i can get is a Console Login. im not sure on how to start and log into the Ultimate Plus Software.

I was given a set of credinctasl the the description was "Ultimate boot" but when I try to log in with them at the console log in it runs a small script then comes back and say "Ultimate PLUS reserves the console for UNIX administration tasks." i can not seem to find a non console login.

Any information anyone has would be much appriacted since i can not find much online about this. Thanks in advance.

3 REPLIES
Steven Schweda
Honored Contributor

Re: Looking for any information on a HPUX system running Ultimate PLUS

> [...] Ultimate Plus [...]

   I know nothing about it, but ...

> The only type of login i can get is a Console Login.

   What, exactly, are you doing to get that (on what)?

> i can not seem to find a non console login.

   Trying what, exactly?

   If Ultimate PLUS won't let you use the console, then you may need to
use a non-console terminal of some kind.

   I'd be looking for a set of administrator ("root") credentials, with
which I could ensure that the system is accessible over the network.
Then I'd try use the network to connect to the system (remsh/rsh, ssh,
Telnet, whatever) using the (magic) Ultimate Plus credentials.

> [...] bought from someone [...]

   In my quest for useful credentials, I might start with that
"someone".

zwalker
Occasional Visitor

Re: Looking for any information on a HPUX system running Ultimate PLUS

Thanks for replying, credentials arent my issue. I have the correct root user credentials, and the correct Ultimate PLUS credentials., Also It is connected to the network and I can Ping it but  using putty I can not get a login in prompt using telent. But here is the werid part if i try and connect via SSH I get a login prompt but anfter i enter a username and hit return it locks up. and after 5 or so mins its returns back to a login prompt but never askes for a password. Can you possibly shead some light on this issue for me.

Steven Schweda
Honored Contributor

Re: Looking for any information on a HPUX system running Ultimate PLUS

> [...] using putty I can not get a login in prompt using telent.

   How long did you wait?  DNS problems can cause long (30s?) delays
when the server tries to get the name of the client from its address.

> [...] connect via SSH I get a login prompt but anfter i enter a
> username and hit return it locks up. and after 5 or so mins its returns
> back to a login prompt but never askes for a password.

   I know nothing, but I'd guess that SSH would be even more sensitive
to DNS problems than Telnet is.

   If this system was transplanted from its original network into a new
network, then DNS problems would be easy to get.  Note that the usual
delay problems are caused by a failure when the server tries a reverse
(address-to-name) look-up of the client.  It wouldn't matter if the
client specified an address (instead of a name) to identify the server,
or if the forward (name-to-address) look-ups all work properly.

   The simple test for this DNS problem is, on the server:

      nslookup <client_ip_address>

If that's slow and/or fails, then you can expect problems with almost
any connection scheme.

   Adding stuff to /etc/hosts may let you work around DNS problems, but
getting DNS to work is usually wise in the long run.


> [...] using putty [...]

   I'd start by trying to connect from the system to itself (SSH,
Telnet, whatever), before dragging another computer into the mix.  If it
can't talk to itself, then connections from elsewhere are probably
doomed.

   Output from "ssh -v[v[v]] ..." might help diagnose SSH-specific
problems.  System log files may also provide some hints.  If "ping"
works, then I'd guess that bad routes are not the problem.