09-16-2008
Is your server direct attached or connected via switch (to the DS4k)? Is this a second DS4800 or is the second unit an expansion unit for the first DS?
10 More Discussions You Might Find Interesting
1. AIX
Sorry for my english.
We have a IBM BLADES JS21. AIX 5.3 update to 6.
Our JS21 has 2 FC (fcs0 and fcs1).
We have one DS4072, one Disk system with 2 controllers and 2 FC by controllers.
This means, all AIX FC see all Disk systems controllers by 2 FC switchs. (one fc two roads)
FC AIX... (4 Replies)
Discussion started by: fjgonzalez
4 Replies
2. AIX
Hi All,
I have mirrored SAN volume on my B80 rootvg. Can I just remove the mirror and "Remove a P V from a V G" and it will be a diskless AIX?
Is that going to boot on SAN rootvg volume?
Thanks in advance,
itik (3 Replies)
Discussion started by: itik
3 Replies
3. AIX
Hello,
I am using DS4800 SAN with AIX 5.3, and would like to increase the size of the DS4800 Luns, so that my FS increase also.
How to do this please ?
Modifying Lun risk to make all data of the FS being lost ! NO ? (8 Replies)
Discussion started by: astjen
8 Replies
4. AIX
Hi people...
i have a problem with a DS4800 san... it keeps me showing this message (on picture) and i dont know how to solve it!
someone knows?
thanks a lot (2 Replies)
Discussion started by: gfca
2 Replies
5. AIX
Hello!
I have this infraestructure:
- 1 POWER7 with single VIOS on Site A.
- 1 POWER6 with single VIOS on Site B.
- 1 LPAR called NodeA as primary node for PowerHA 6.1 on Site A.
- 1 LPAR called NodeB as secondary (cold) node for PowerHA 6.1 on SiteB.
- 1 Storage DS4700 on Site A.
- 1... (8 Replies)
Discussion started by: enzote
8 Replies
6. AIX
Hello,
Lets say for simplicity that I do not use any vlan config inside my server - one lpar group use hea physical port1, another group hea physical port2. Physical port1 configured as vlan1 on external switch, physical port2 as vlan2.
What is the common practice - should I isolate my vios... (0 Replies)
Discussion started by: vilius
0 Replies
7. AIX
Hi All,
I have a p520 box running 3 LPARs, 1 x VIOS, 1 x AIX 6.1 and 1 x AIX 7.1 and no HMC, all configuration is performed via VIOS/IVM
Until recently the box did not have the AIX7.1 LPAR and everything was fine with the box.
We needed to use AIX 7.1 for a new project, so I created a... (11 Replies)
Discussion started by: KevB
11 Replies
8. AIX
coming from this thread: https://www.unix.com/aix/211107-ibm-power-pseries-open-firmware-boot-vios-powervm-vet-code.html
PowerVM, formerly known as Advanced Power Virtualization (APV), is a chargeable feature of IBM POWER5, POWER6, POWER7, POWER8, and POWER9 servers and is required for support... (0 Replies)
Discussion started by: filosophizer
0 Replies
9. UNIX for Advanced & Expert Users
Hi everybody,
I have Power5 server with 4 internal hdisks each of 70Gb.
VIOS server was installed via Virtual I/O Server Image Repository on the HMC.
HMC release - 7.7.0
VIOS rootvg installed on 2 disk(these disks merged to one storage pool during VIOS install process),and 2 others hdisks... (2 Replies)
Discussion started by: Ravil Khalilov
2 Replies
10. AIX
hello
P6 was managed by HMC, tried to install on it VIOS 2.2.6
and got this error message
Hosting requires a hosting partition -- boot not permitted
vios-4 - imgbb.com
then after creating an lpar in HMC got this message
B2001230
vios-3 - imgbb.com
anyone know how to solve this... (3 Replies)
Discussion started by: filosophizer
3 Replies
LEARN ABOUT REDHAT
device
DEVICE(9) BSD Kernel Developer's Manual DEVICE(9)
NAME
device -- an abstract representation of a device
SYNOPSIS
typedef struct device *device_t;
DESCRIPTION
The device object represents a piece of hardware attached to the system such as an expansion card, the bus which that card is plugged into,
disk drives attached to the expansion card etc. The system defines one device, root_bus and all other devices are created dynamically during
autoconfiguration. Normally devices representing top-level busses in the system (ISA, PCI etc.) will be attached directly to root_bus and
other devices will be added as children of their relevant bus.
The devices in a system form a tree. All devices except root_bus have a parent (see device_get_parent(9)). In addition, any device can have
children attached to it (see device_add_child(9), device_add_child_ordered(9), device_find_child(9), device_get_children(9), and
device_delete_child(9)).
A device which has been successfully probed and attached to the system will also have a driver (see device_get_driver(9) and driver(9)) and a
devclass (see device_get_devclass(9) and devclass(9)). Various other attributes of the device include a unit number (see
device_get_unit(9)), verbose description (normally supplied by the driver, see device_set_desc(9) and device_get_desc(9)), a set of bus-spe-
cific variables (see device_get_ivars(9)) and a set of driver-specific variables (see device_get_softc(9)).
Devices can be in one of several states:
DS_NOTPRESENT the device has not been probed for existence or the probe failed
DS_ALIVE the device probe succeeded but not yet attached
DS_ATTACHED the device has been successfully attached
DS_BUSY the device is currently open
The current state of the device can be determined by calling device_get_state(9).
SEE ALSO
devclass(9), driver(9)
AUTHORS
This manual page was written by Doug Rabson.
BSD
June 16, 1998 BSD