Sponsored Content
Operating Systems AIX VIO server does not show new LPAR Post 302610207 by petervg on Wednesday 21st of March 2012 04:11:37 AM
Old 03-21-2012
The Server SCSI adapter was a typo in this post. It was correct on the server.

After running
Code:
cfgdev

the new LPAR does show up in the lsmap output. Thanks.
 

10 More Discussions You Might Find Interesting

1. AIX

Help urgent : vio server - add extral disk on virtual lpar

Hi, I define 2 new LV on the vio server and run a cfgmgr on the partition and see my 2 new hdisk (hdisk6 and hdisk7). I extend my vg vg000 (on the partition) and add the 2 hdisks. I had a filesystem on the vg000 and when I added the disk I would like to increase the filesystem. But I cannot do a... (0 Replies)
Discussion started by: touny
0 Replies

2. AIX

Restoring mksysb to vio lpar?

I have a standard template I deploy for each of my AIX servers. It's in a mksysb format which I pulled via the nim server after I originally set it up. I'm trying to restore this mksysb over the wire to a remote system. The remote system is an lpar running under vio (no HMC attached). The disk... (1 Reply)
Discussion started by: scottsl
1 Replies

3. UNIX for Dummies Questions & Answers

Unix VIO vs Dynamic LPAR

Can you have a Dynamic LPAR without VIO and if yes is there a benefit to having both? I am attempting to implement VIO and Resource pooling at my company and want to understand the limitations. Also, I have been told the managing and allocation of the Logical Volumes is a time consuming task as... (0 Replies)
Discussion started by: bombers73
0 Replies

4. AIX

Lost root password in LPAR (VIO Server).

Hi, I've lost the root password in a virtual partition created in a IBM Vio Server. May I recover that somehow? Thanks (2 Replies)
Discussion started by: r4mp4g3
2 Replies

5. AIX

LPAR and vio disk mapping

We have a frame the uses 2 vios that assign disk storage to LPAR's. We have a LPAr with multiple disk and I want to know how do I tell which vio is serving the disk. For example the LPAr has hdisk 0, 1, 2, 3 all the same size. I want to know which vio is serving hdisk0, 1. (4 Replies)
Discussion started by: daveisme
4 Replies

6. AIX

VIO Backing Disk LPAR how to find which one ?

hello Folks, my vio: $ lsmap -all SVSA Physloc Client Partition ID --------------- -------------------------------------------- ------------------ vhost0 U9117.MMA.6534BE4-V2-C11 0x00000003 VTD ... (0 Replies)
Discussion started by: filosophizer
0 Replies

7. AIX

CDROM Issue on LPAR HMC VIO

Whenever I assign/unassign a CDROM ( RAID CTRL ) to Active LPAR from HMC, I have to reboot the LPAR. How can I do it without rebooting the LPARS. POWER6 with HMC LPARS = AIX 6.1 Any info developerWorks : AIX and UNIX : PowerVM Forum : Moving CD-ROM/DVD-ROM dynamically ... But... (5 Replies)
Discussion started by: filosophizer
5 Replies

8. AIX

LPAR - What is my VIO (hostname, IP, ...)

I am wondering if there is a command I can run from **with-in** LPAR server (server01) to find out the hostname or IP address or other parameters for VIO server in charge of server01? (1 Reply)
Discussion started by: ms1232
1 Replies

9. AIX

Possible to connect a LPAR to two different VIO's?

Just a question which may seem dumb to some out there, but then again I am not a super technie so that's my excuse. Is it possible to say provision a test AIX LPAR (has a 10gb boot lun and 20gb data) under a VIO which has connectivity to SAN Array A so it can see the disks provisioned to it,... (2 Replies)
Discussion started by: Johnny1314
2 Replies

10. AIX

cdrom confusion on the vio client lpar

Hi In my vio server I have the below output $ lsvopt | grep -i SAPSITGS sapsitgs_cdrom TL12UP.iso 3182 In my vio client lpar I have the below output root@sapsitgs:/ # lsdev -Cc cdromcd0 Available Virtual SCSI Optical Served by VIO Server cd1... (1 Reply)
Discussion started by: newtoaixos
1 Replies
atapi_ide(7)						 Miscellaneous Information Manual					      atapi_ide(7)

NAME
atapi_ide - Interface for ATAPI or IDE (PC) devices SYNOPSIS
PCI bus CMD/Acer ATAPI/IDE adapter: bus pci0 at * bus ata0 at * controller scsi0 at ata0 slot 0 controller scsi1 at ata0 slot 1 PCI bus Cypress ATAPI/IDE adapter: bus pci0 at * bus ata0 at * bus ata1 at * controller scsi0 at ata0 slot 0 controller scsi1 at ata1 slot 0 PCMCIA bus ATA/IDE disk card: bus pcmcia0 at * bus ata0 at pcmcia? controller scsi0 at ata0 DESCRIPTION
Devices commonly known for their use on PC devices as ATA or IDE devices are supported using the SCSI CAM device driver. The ATA standard has also been expanded to include what are known as ATAPI devices. The SCSI CAM device driver is also used for those disks and CD-ROM devices. These devices may also be known under the names EIDE, ATA-2, Fast-ATA, or Ultra-ATA. Beacuse the ATA/IDE standard was not developed until after many of the devices that used this standard were produced, there are many devices which do not strictly comply with the standard. While it is possible some industry standard devices may appear to work, it is also possible they will cause hang or data corruption cases when used under more stressful situations. For this reason, it is recommended that only the supported devices be used. These devices have been tested and are certified for correct operation. ATAPI/IDE controllers allow the connection of two devices. These two devices are known as the master device and the slave device. If only one device is connected, that device must be the master (slave-only configurations are not supported). When used by the SCSI CAM device driver, the IDE master device is assigned SCSI id 0 for that controller. The slave device is assigned SCSI id 1 for that controller. No other SCSI ids are assigned on that controller. Most ATAPI/IDE adapters contain two channels (known as the primary and secondary). Each of these channels may contain their own master and slave devices. Therefore, a dual channel ATAPI/IDE controller may contain up to 4 devices (a master and slave pair on each channel). These 4 devices are then accessed as SCSI id 0 and 1 on each channel. Many SCSI operations translate perfectly for use on IDE. For example, read and write operations are the same. However, many SCSI disk mode pages are emulated by the IDE device driver. For example, you can display the SCSI inquiry mode pages using the following command: % scu show inq pages pages are created by the device driver to contain the long (full IDE) form of the device name, serial number, revision, and the operational modes of the device. Only a shortened version of this information is available with the standard SCSI inquiry command. Note also that the following command: % scu show pages Shows that the SCSI mode pages contain only partial information. Only that informa- tion (such as geometry) that the drive reports to the system is able to be reformatted into these emulated SCSI mode pages. Much of the information (such as RPM) is simply not available from the drive, and therefore not accurately reported. ATAPI devices are much more closely related to SCSI devices, and as such contain their own mode pages. Therefore, for these devices, the mode page values reported are those from the device, and no emulation is involved. ATAPI tape devices are not supported at this time. FILES
/dev/disk/dsk??? /dev/disk/dsk??? RELATED INFORMATION
SCSI(7), rz(7), and disklabel(8) delim off atapi_ide(7)
All times are GMT -4. The time now is 10:15 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy