07-22-2013
Tried it ... chassis serial unknown
tried also showplatform -p csn
10 More Discussions You Might Find Interesting
1. Solaris
Hello, I'm trying to fix this server System Board (CPU/Memory Unit). The error indicates that its missing 3.3VDC. So far all the fuses and caps have been checked. I new at this type of machine, need help for idea on this system. Thank you in advance.
Vu (0 Replies)
Discussion started by: vhtran
0 Replies
2. Solaris
Hi all ,
I am trying to install solaris 9 on E2900 that is connect to a 3320 SCSI storage , The issue is that i want to have the SCSI disks(3320) to start with controllers 1 and 2 ( c1t0 ....c2t0) and my 2 local disks on c3 and c4 .
Is there a way that i could accomplish that ...
Thanks... (3 Replies)
Discussion started by: ppass
3 Replies
3. Solaris
Hi men,
Have you ever meet this error ?
I install full Sun MC 4.0 packages (+ Add ons) exception of Sun Midrange Platform Administration because i don't know how to configure it
Then all other servers are ok, only E2900 servers have Config reader module error: Data Acquisition error
I... (12 Replies)
Discussion started by: tien86
12 Replies
4. Solaris
Dear Friends,
Sun Fire E2900 crashed. I collected explorer output. core dump files been generated.
There some interesting output files related to crash dumps, that I need some help from you guys to understand.
The file in the explorer output is under /sysconfig/crash it's called:... (5 Replies)
Discussion started by: Sun Fire
5 Replies
5. Solaris
I am looking for the below Document ID:
Document ID: 75970 Title: "Simulating a Boot Drive Failure for Testing Purposes for Solstice DiskSuite, Solaris Volume Manager or Veritas Volume Manager"
I tried searching on the web and Oracle and I cannot find this document; ever since Oracle... (2 Replies)
Discussion started by: Keepcase
2 Replies
6. Solaris
Hi,
I am fairly new to Solaris , i have an e2900 server which gives the following output on the console:
Fri Sep 23 08:20:57 noname.example.com lom: /N0/SB0 : F
ailed AR interconnect test. Status = 00060040
Fri Sep 23 08:21:00 noname.example.com lom: AR Intercon
nect test: System board... (7 Replies)
Discussion started by: steve_b72
7 Replies
7. Emergency UNIX and Linux Support
Hi,
I have a scheduled activity to reboot E2900 server. But suddenly I came to know that console ip is not pinging, not connecting via telnet, as it used to connect. I already checked with my onsite person and he changed cable, still no luck. Network person checked his switch, which is showing... (8 Replies)
Discussion started by: solaris_1977
8 Replies
8. Solaris
What would you think is a reasonable useful lifespan for a Sunfire e2900. I'm not referring to it's performance capabilities as much as I'm referring to the hardware's ability to perform reliably. (2 Replies)
Discussion started by: DustinT
2 Replies
9. Solaris
While trying to perform a firmware upgrade on this ilom, the system refused to allow uploading of more than ~900k or so... We tried multiple approaches using FTP and all failed. I decided to start this morning by firing up Apache on another box and trying the same process via HTTP but when I went... (8 Replies)
Discussion started by: DustinT
8 Replies
10. Shell Programming and Scripting
Hello @all
first of all in the best case this script has to work on every os (lnx/aix/sun).
It's very simple what it should do.
I have a standard path and I'll call it for this example /myhome/scripts
Within this path there are more files and folders and some of them are tagged with... (4 Replies)
Discussion started by: Miniqpa
4 Replies
LEARN ABOUT OPENSOLARIS
machine-info
MACHINE-INFO(5) machine-info MACHINE-INFO(5)
NAME
machine-info - Local machine information file
SYNOPSIS
/etc/machine-info
DESCRIPTION
The /etc/machine-info file contains machine metadata.
The basic file format of machine-info is a newline-separated list of environment-like shell-compatible variable assignments. It is possible
to source the configuration from shell scripts, however, beyond mere variable assignments no shell features are supported, allowing
applications to read the file without implementing a shell compatible execution engine.
/etc/machine-info contains metadata about the machine that is set by the user or administrator.
Depending on the operating system other configuration files might be checked for machine information as well, however only as fallback.
You may use hostnamectl(1) to change the settings of this file from the command line.
OPTIONS
The following machine metadata parameters may be set using /etc/machine-info:
PRETTY_HOSTNAME=
A pretty human-readable UTF-8 machine identifier string. This should contain a name like "Lennart's Laptop" which is useful to present
to the user and does not suffer by the syntax limitations of internet domain names. If possible, the internet hostname as configured in
/etc/hostname should be kept similar to this one. Example: if this value is "Lennart's Computer" an Internet hostname of
"lennarts-computer" might be a good choice. If this parameter is not set, an application should fall back to the Internet host name for
presentation purposes.
ICON_NAME=
An icon identifying this machine according to the XDG Icon Naming Specification[1]. If this parameter is not set, an application should
fall back to "computer" or a similar icon name.
CHASSIS=
The chassis type. Currently, the following chassis types are defined: "desktop", "laptop", "convertible", "server", "tablet",
"handset", "watch", and "embedded", as well as the special chassis types "vm" and "container" for virtualized systems that lack an
immediate physical chassis. Note that many systems allow detection of the chassis type automatically (based on firmware information or
suchlike). This setting (if set) shall take precedence over automatically detected information and is useful to override misdetected
configuration or to manually configure the chassis type where automatic detection is not available.
DEPLOYMENT=
Describes the system deployment environment. One of the following is suggested: "development", "integration", "staging", "production".
LOCATION=
Describes the system location if applicable and known. Takes a human-friendly, free-form string. This may be as generic as "Berlin,
Germany" or as specific as "Left Rack, 2nd Shelf".
EXAMPLE
PRETTY_HOSTNAME="Lennart's Tablet"
ICON_NAME=computer-tablet
CHASSIS=tablet
DEPLOYMENT=production
SEE ALSO
systemd(1), os-release(5), hostname(5), machine-id(5), hostnamectl(1), systemd-hostnamed.service(8)
NOTES
1. XDG Icon Naming Specification
http://standards.freedesktop.org/icon-naming-spec/icon-naming-spec-latest.html
systemd 237 MACHINE-INFO(5)