Sponsored Content
Full Discussion: Sun X4270 ILOM Login issue
Special Forums Hardware Sun X4270 ILOM Login issue Post 302622745 by mystition on Thursday 12th of April 2012 02:22:21 PM
Old 04-12-2012
Thanks for your reply guys! The RJ-45 to DB9 cable was faulty.
The issue was resolved by changing the cable.
 

8 More Discussions You Might Find Interesting

1. 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

2. Solaris

PAM login library files corrupted, have ILOM, can I get root?

I was installing sfw sudo and its dependencies (libiconv, libintl, libgcc)on Solaris 10, running on an x86 x4200 and I corrupted some PAM library files. It's a standard Solaris 10 base install, with some added software & libraries from a vendor. I am on console trying to get root access back,... (1 Reply)
Discussion started by: Mariognarly
1 Replies

3. Solaris

x4600 iLOM issue

I need to configure the iLOM for x4600 server. before I can set the IP details and commit, I need to set network state should be enabled. However my firmware is already the latest and I need not upgrade. I am not able to set the /SP/network state to enable. pls assist. i BELIEVE the bug was fixed... (5 Replies)
Discussion started by: incredible
5 Replies

4. Solaris

ILOM Banner Sun x41XX servers

Is it possible to set the information that shows in the cli banner when you login to the ILOM? In addition, after I set the hostname of the ILOM, how do I check it? (2 Replies)
Discussion started by: brialt1
2 Replies

5. Solaris

Sun X4540 Ilom - Solaris 10

Hello Admins, I am trying to access the solaris 10 host using the ilo. When I do start /SP/console, it just hangs, it doesn't give me any login prompt... I tried reset /SYS and also did reset /SP...but no luck... We have Sun X4540.... Any help appreciated..Thanks (9 Replies)
Discussion started by: snchaudhari2
9 Replies

6. Solaris

SUN ILOM

Hi, I am just confused with iLOM. Is iLOM is applicable for SPARC as well as X86 servers?? which are having CMM. Hope ALOM will be applicable for rest of the servers like v240 kind of series. Can any one pls clarify this?? Thanks in Advance Vaisakh K S (3 Replies)
Discussion started by: vks47
3 Replies

7. Solaris

ILOM Sunservice login incorrect

We have tried to perform the data collection of 11 SUN FIRE X4170 SERVER as part of preventive maintenance activity. But, when we tried to access the ILOM using sunservice user we got a “login incorrect” prompt. We used the “changeme” password. can we use the root/changeme account instead... (4 Replies)
Discussion started by: chozie
4 Replies

8. Solaris

How to start up console on Sun Fire X2200 ILOM using SSH?

Hi Oracle Hardware Specialists, I have shutdown a Sun Fire X2200 server running Solaris 10 x86 to single user mode to experiment some backup commands using Web based Sun embedded Lights Out Manager Redirection to open up a console session. However, it is not possible to copy & past text with... (7 Replies)
Discussion started by: gjackson123
7 Replies
APT_AUTH.CONF(5)							APT							  APT_AUTH.CONF(5)

NAME
apt_auth.conf - Login configuration file for APT sources and proxies DESCRIPTION
APT configuration files like sources.list(5) or apt.conf(5) need to be accessible for everyone using apt tools on the system to have access to all package-related information like the available packages in a repository. Login information needed to connect to a proxy or to download data from a repository on the other hand shouldn't always be accessible by everyone and can hence not be placed in a file with world-readable file permissions. The APT auth.conf file /etc/apt/auth.conf can be used to store login information in a netrc-like format with restrictive file permissions. NETRC-LIKE FORMAT The format defined here is similar to the format of the ~/.netrc file used by ftp(1) and similar programs interacting with servers. It is a simple token-based format with the following tokens being recognized; Unknown tokens will be ignored. Tokens may be separated by spaces, tabs or newlines. machine hostname[:port][/path] Entries are looked up by searching for the machine token matching the hostname of the URI apt needs login information for. Extending the netrc-format a portnumber can be specified. If no port is given the token matches for all ports. Similar the path is optional and only needed and useful if multiple repositories with different login information reside on the same server. A machine token with a path matches if the path in the URI starts with the path given in the token. Once a match is made, the subsequent tokens are processed, stopping when the end of file is reached or another machine token is encountered. login name The username to be used. password string The password to be used. EXAMPLE
Supplying login information for a user named apt with the password debian for the sources.list(5) entry deb http://example.org/debian stretch main could be done in the entry directly: deb http://apt:debian@example.org/debian stretch main Alternatively an entry like the following in the auth.conf file could be used: machine example.org login apt password debian Or alternatively within a single line: machine example.org login apt password debian If you need to be more specific all of these lines will also apply to the example entry: machine example.org/deb login apt password debian machine example.org/debian login apt password debian machine example.org/debian/ login apt password debian On the other hand neither of the following lines apply: machine example.org:80 login apt password debian machine example.org/deb/ login apt password debian machine example.org/ubuntu login apt password debian machine example.orga login apt password debian machine example.net login apt password debian NOTES
Basic support for this feature is present since version 0.7.25, but was undocumented for years. The documentation was added in version 1.5 changing also the implementation slightly. For maximum backward compatibility you should avoid multiple machine tokens with the same hostname, but if you need multiple they should all have a path specified in the machine token. FILES
/etc/apt/auth.conf Login information for APT sources and proxies in a netrc-like format. Configuration Item: Dir::Etc::netrc. SEE ALSO
apt.conf(5) sources.list(5) BUGS
APT bug page[1]. If you wish to report a bug in APT, please see /usr/share/doc/debian/bug-reporting.txt or the reportbug(1) command. AUTHOR
APT team NOTES
1. APT bug page http://bugs.debian.org/src:apt APT 1.6.3ubuntu0.1 17 August 2017 APT_AUTH.CONF(5)
All times are GMT -4. The time now is 11:54 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy