Sponsored Content
Full Discussion: ILOM problem on T5220
Operating Systems Solaris ILOM problem on T5220 Post 302431665 by System Shock on Tuesday 22nd of June 2010 12:30:08 PM
Old 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

Problem fixing e1000gx ni to 100fdx / Solaris 10 / T5220

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

T5220 Console Problem

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

Problem using default account with ILOM on Sun SPARC Enterprise T5140

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

ILOM and sc on T5220

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

SC on T5220 not responding

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

LDOMs on T5220

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

T5220 server

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

T5220

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

T5220

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

T5220 ILOM serial number - how to change

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
RLOG(1L)																  RLOG(1L)

NAME
rlog - print log messages and other information about RCS files SYNOPSIS
rlog [ options ] file ... DESCRIPTION
Rlog prints information about RCS files. Files ending in `,v' are RCS files, all others are working files. If a working file is given, rlog tries to find the corresponding RCS file first in directory ./RCS and then in the current directory, as explained in co(1L). Rlog prints the following information for each RCS file: RCS file name, working file name, head (i.e., the number of the latest revision on the trunk), default branch, access list, locks, symbolic names, suffix, total number of revisions, number of revisions selected for print- ing, and descriptive text. This is followed by entries for the selected revisions in reverse chronological order for each branch. For each revision, rlog prints revision number, author, date/time, state, number of lines added/deleted (with respect to the previous revision), locker of the revision (if any), and log message. Without options, rlog prints complete information. The options below restrict this out- put. -L ignores RCS files that have no locks set; convenient in combination with -R, -h, or -l. -R only prints the name of the RCS file; convenient for translating a working file name into an RCS file name. -h prints only RCS file name, working file name, head, default branch, access list, locks, symbolic names, and suffix. -t prints the same as -h, plus the descriptive text. -b prints information about the revisions on the default branch (normally the highest branch on the trunk). -ddates prints information about revisions with a checkin date/time in the ranges given by the semicolon-separated list of dates. A range of the form d1<d2 or d2>d1 selects the revisions that were deposited between d1 and d2, (inclusive). A range of the form <d or d> selects all revisions dated d or earlier. A range of the form d< or >d selects all revisions dated d or later. A range of the form d selects the single, latest revision dated d or earlier. The date/time strings d, d1, and d2 are in the free format explained in co(1L). Quoting is normally necessary, especially for < and >. Note that the separator is a semicolon. -l[lockers] prints information about locked revisions. If the comma-separated list lockers of login names is given, only the revisions locked by the given login names are printed. If the list is omitted, all locked revisions are printed. -rrevisions prints information about revisions given in the comma-separated list revisions of revisions and ranges. A range rev1-rev2 means revisions rev1 to rev2 on the same branch, -rev means revisions from the beginning of the branch up to and including rev, and rev- means revisions starting with rev to the end of the branch containing rev. An argument that is a branch means all revisions on that branch. A range of branches means all revisions on the branches in that range. -sstates prints information about revisions whose state attributes match one of the states given in the comma-separated list states. -w[logins] prints information about revisions checked in by users with login names appearing in the comma-separated list logins. If logins is omitted, the user's login is assumed. Rlog prints the intersection of the revisions selected with the options -d, -l, -s, -w, intersected with the union of the revisions selected by -b and -r. EXAMPLES
rlog -L -R RCS/*,v rlog -L -h RCS/*,v rlog -L -l RCS/*,v rlog RCS/*,v The first command prints the names of all RCS files in the subdirectory `RCS' which have locks. The second command prints the headers of those files, and the third prints the headers plus the log messages of the locked revisions. The last command prints complete information. DIAGNOSTICS
The exit status always refers to the last RCS file operated upon, and is 0 if the operation was successful, 1 otherwise. IDENTIFICATION
Author: Walter F. Tichy, Purdue University, West Lafayette, IN, 47907. Revision Number: 1.2 ; Release Date: 87/03/17 . Copyright (C) 1982 by Walter F. Tichy. SEE ALSO
ci(1L), co(1L), ident(1L), rcs(1L), rcsdiff(1L), rcsintro(1L), rcsmerge(1L), rcsfile(5L) Walter F. Tichy, "Design, Implementation, and Evaluation of a Revision Control System," in Proceedings of the 6th International Conference on Software Engineering, IEEE, Tokyo, Sept. 1982. Purdue University RLOG(1L)
All times are GMT -4. The time now is 03:44 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy