07-22-2013
on this class of server (if not "sneeped") you'll need to check the sn# on the physical machine.
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
lvmpvg(4) Kernel Interfaces Manual lvmpvg(4)
NAME
lvmpvg - LVM physical volume group information file
SYNOPSIS
DESCRIPTION
is an ASCII file that stores the volume-group information for all of the physical volume groups in the system. The information is stored
in a hierarchical format.
First, it starts with a volume group under which multiple physical volume groups can exist. Under each physical volume group, a list of
physical volumes can be specified. There must be at least one physical volume group in each volume group that appears in this file. The
physical-volume-group name must be unique within the corresponding volume group, although it is permissible to use a common physical volume
group name across different volume groups. There can be as many volume groups in this file as there are in the system.
Instead of using the and commands, the administrator can edit this file to create and extend physical volume groups. However, care must be
taken to ensure that all physical volumes to be included in the file have already been defined in their respective volume groups by previ-
ous use of or
The file format has the following structure. and are keywords that introduce the names of the volume group and physical volume group,
respectively.
pv_path
...
pv_path
...
pv_path
...
The variables are defined as follows:
pv_path The block device path name of a physical volume within the volume group.
pvg_name The name of the physical volume group. It must be unique within the volume group.
vg_name The path name of the volume group.
EXAMPLES
The following example shows an file containing two volume groups: the first containing two physical volume groups, each with two physical
volumes defined in it; the second containing three physical volume groups, each with one physical volume defined in it.
SEE ALSO
vgcreate(1M), vgextend(1M), vgreduce(1M), vgremove(1M), intro(7), lvm(7).
lvmpvg(4)