06-22-2010
Maybe I have different firmware revisions, but that login routine doesn't look like an iLOM routine. Is there a terminal server involved?
10 More Discussions You Might Find Interesting
1. Solaris
Hello !
i'm facing an anoying problem during configuration of our new T5220 Enperise server. I've upgarded 'em with a pci-e ethernet expantion card for four additional networkinterfaces using the nxge drivers. i could fix them to 100 fdx rather simple by adding the following settings to the ... (6 Replies)
Discussion started by: moofoo
6 Replies
2. Solaris
Hi Peeps,
Apologies if this is the wrong forum for this, if it is can someone point me in the direction of the right one?
Problem:
I've dropped an XVR-300 Graphics card into a T5220, configured it to output and input from the screen and keyboard instead of the virtual console. It... (3 Replies)
Discussion started by: callmebob
3 Replies
3. Solaris
Hi,
I have Sun SPARC Enterprise T5140 and I can't access it via serial port using preconfigured administrator account, as described in Sun Integrated Lights Out Manager 2.0 User's Guide: I'm always receive "Login incorrect" message. I'm really confused! Does anyone experience such circumstances?... (12 Replies)
Discussion started by: Sapfeer
12 Replies
4. Solaris
I 've 2 different T5220 and both are showing different prompts when i ssh to the console.
1. Shows sc> ALOM
2. Shows -> ILOM
as far as i know the T5220 comes with ILOM , so why i 'm seeing 2 different type of console for same tyep of hardware ?
and i found that we... (6 Replies)
Discussion started by: fugitive
6 Replies
5. Solaris
Hi,
SC on one of my T5220 is not responding .. it does not show not let me type anything .. what could be the reason for it ? though when i powercycle the box from sc it shows me the system coming up but after that does not let me login thru sc
sc> console -f
Enter #. to return to ALOM. (2 Replies)
Discussion started by: fugitive
2 Replies
6. Solaris
We're just about to migrate a large application from an Enterprise 6900 to a pair of T5220s utilising LDOMs. Does anyone have any experience of LDOMs on this kit and can provide any recommendations or pitfalls to avoid?
I've heard that use of LDOMs can have an impact on I/O speeds as it's all... (9 Replies)
Discussion started by: JerryHone
9 Replies
7. Solaris
Hi,
We have two T5220 servers in our datacentre
one server is showing 64 processors online
and another showing 32 processors online
two are newly purchased, there is no hardware faults in this server
one server has 64gb memory and it shows 64 processors,
and other having 32gb memory and it... (5 Replies)
Discussion started by: rajasekg
5 Replies
8. Solaris
Hi Guys and Gals,
Wondering if anyone could help me, tricky one this.
Got a T5220 with a graphics card. When you power it on, it outputs its output to the screen and you can type commands with the keyboard etc.
But no matter what version of Solaris 10 you use, when you do a boot cdrom... (1 Reply)
Discussion started by: callmebob
1 Replies
9. Solaris
Hello guys,
can anyone give me some advice on how to perform
clean installation of Solaris 10 on T5220 ?
I am connected with serial management port on the machine,
i have the ok promt and now i should eject the dvdrom to insert
Solaris dvd into and start the clean install.
So how to do that... (3 Replies)
Discussion started by: tonijel
3 Replies
10. Solaris
Have a T5220 with Oracle SN stickers on outside with one SN, but the ILOM shows a different SN (from another server). It seems this is a issue with T5220's (a co-worker ran into similar problem with 2 of his servers, he just had the ILOM's swapped).
Anyone know the command to change the ILOM... (3 Replies)
Discussion started by: RTM
3 Replies
LEARN ABOUT ULTRIX
rlogind
rlogind(8c) rlogind(8c)
Name
rlogind - remote login server
Syntax
/etc/rlogind
Description
The server is used for the program. The server provides a remote login facility with authentication based on privileged port numbers.
The server is invoked by when it receives a connection on the port indicated in the login service specification. For further information,
see When a service request is received, the following protocol is initiated:
1. The server checks the client's source port. If the port is not in the range 0-1023, the server aborts the connection.
2. The server checks the client's source address and requests the corresponding host name. If the hostname cannot be determined, the dot-
notation representation of the host address is used.
Once the source port and address have been checked, allocates a pseudo terminal and manipulates file descriptors so that the slave half of
the pseudo terminal becomes the stdin, stdout, and stderr for a login process. For further information, see
The login process is an instance of the program, invoked with the option. The login process then proceeds with the authentication process
as described in but if automatic authentication fails, it reprompts the user to log in on a standard terminal line.
The parent of the login process manipulates the master side of the pseudo terminal, operating as an intermediary between the login process
and the client instance of the program. In normal operation, the packet protocol described in is invoked to provide ^S/^Q type facilities
and propagate interrupt signals to the remote programs. The login process propagates the client terminal's baud rate and terminal type, as
found in the environment variable, TERM. For further information see
The screen or window size of the terminal is requested from the client, and any changes in the window size from the client are sent to the
pseudo terminal.
Restrictions
The authentication procedure used here assumes the integrity of each client machine and the connecting medium. This is insecure, but it is
useful in an open environment.
Diagnostics
All diagnostic messages are returned on the connection associated with the stderr, after which any network connections are closed. An
error is indicated by a leading byte with a value of 1.
Hostname for your address unknown
No entry in the host name database existed for the client's machine.
Try again
A fork by the server failed.
/bin/sh: ...
The user's login shell could not be started.
See Also
rlogin(1c), inetd(8c)
rlogind(8c)