09-16-2008
Hi,
its connected by a SAN switch... and its another DS4800!
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 OSF1
devswmgr
devswmgr(8) System Manager's Manual devswmgr(8)
NAME
devswmgr - utility to manage the device switch database
SYNOPSIS
/sbin/devswmgr [-option [parameter]]
OPTIONS
Displays the following information about the device switch database:
Whether a device switch database was read from the primary file or from a backup file
The number of entries that are in the device switch table Displays the major numbers that have been reserved by all drivers, a named
driver, or an instance of a named driver.
A driver that requires more than one entry in the device switch table uses a unique instance number to reference each of its device
switch table entries. Displays help for the devswmgr command. Releases all the major numbers for a device driver if just the
driver name is specified. Releases one major number for a device driver if the NAME and the INSTANCENUM of the driver are speci-
fied.
DESCRIPTION
The devswmgr command helps you manage the device switch table by displaying information about the devices drivers in the table.
You can also use the command to release device switch table entries. Typically, you release the entries for a driver after you have
unloaded the driver and do not plan to reload it later. Releasing the entries frees them for use by other device drivers.
EXAMPLES
The following example shows that a device switch table was loaded from the primary device and that there are 70 entries in it: %
/sbin/devswmgr -display Device switch information
device switch database read from primary file
device switch table has 70 entries The following example shows the major numbers in the device switch table that have been reserved for
the driver named cam_disk: % /sbin/devswmgr -getnum driver=cam_disk
Device switch reservation list
(*=entry in use)
driver name instance major
------------------------------- -------- -----
cam_disk 1 8*
FILES
The file that manages the device switch databases The primary device switch database file The backup device switch database file
SEE ALSO
Commands: scsimgr(8)
devswmgr(8)