Operating Systems AIX Need to replace a broken PV in a VIO VG used for client LPARs (and it won't release the old one) Post 303043872 by zxmaus on Sunday 9th of February 2020 08:00:44 PM
Old 02-09-2020
is it still mapped to the VMs ? If so unmap it - then try to remove it again.
This User Gave Thanks to zxmaus For This Post:

10 More Discussions You Might Find Interesting

1. AIX

Virtual Ethernet VIO HMC LPARs

Hi, I am little confused about the virtual Ethernet configuration on VIO and Client Partitions. There is alot of info on the internet but it gets more confusing.... If I have LHEA, it is very simple. Just assign LHEA (logical host ethernet adapter) to client partition -> run smitty tcpip and... (10 Replies)
Discussion started by: filosophizer
10 Replies

2. AIX

vio server and vio client

Hi, I want to know wheather partition size for installation of vio client can be specified on vio server example If I am installing vio server on blade with 2*300gb hard disk,after that I want to create 2 vio client (AIX Operating system) wheather I can specify hard disk size while... (1 Reply)
Discussion started by: manoj.solaris
1 Replies

3. AIX

rebooting vio client

Hi, I would like to reboot vio client but I am not able to access vio client(I am not able to get putty) , I am able to get putty of vio server, is there any command by using which from vio server I can reboot vio client? (3 Replies)
Discussion started by: manoj.solaris
3 Replies

4. AIX

Finding cpu information on vio client

Hi, I am having single p series blade with Single Physcial CPU with dual core, on that vio server is installed, I have created vio client allocate 0.9 each cpu , now when I am running prtconf command on vio client it is showing "2" no of processor, My query using which command it will... (1 Reply)
Discussion started by: manoj.solaris
1 Replies

5. AIX

Unable to connect VIO client

Hi I am facing very strange issue on my vio server 5 vio clients are confgured, now I am to connect 3 vio client , i am unable to connect 2 vio client my ip address,subnet mask,gateway is correct. i have rebooted and reconfigured the ip address, but issue is persists. Kindly suggest how to... (0 Replies)
Discussion started by: manoj.solaris
0 Replies

6. AIX

Inherited VIO server an LPARs

Lucky me, someone has installed a server and got it running with the best intentions, but leaving me a headache. :wall: We have a simple p520 with 4 disks. 2x145Gb & 2x300Gb. The smaller disk pair have been built into a VIO mirrored rootvg, and quite right too. The other two disks form a... (3 Replies)
Discussion started by: rbatte1
3 Replies

7. AIX

how will i know if a lun has been already mapped to a vio client

Hi im logged in to the vio servers now. when i give # lspv | wc -l i get the count as 6246 how will i know if a lun has been already mapped to a vio client or it is left free without mapping to any of the vio client ? (1 Reply)
Discussion started by: newtoaixos
1 Replies

8. AIX

vio server ethernet to vio client ethernet(concepts confusing)

Hi In the vio server when I do # lsattr -El hdisk*, I get a PVID. The same PVID is also seen when I put the lspv command on the vio client partition. This way Im able to confirm the lun using the PVID. Similarly how does the vio client partition gets the virtual ethernet scsi client adapter... (1 Reply)
Discussion started by: newtoaixos
1 Replies

9. 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

10. AIX

Rebooting redundant VIOs and mirroring of PVs they serve to client LPARs

need to confirm: we have a system with two VIOs each serving a partition on a local disk to a client LPAR. That client LPAR has them both in a VG which is mirrored (exact). So each disk has a copy of the client LV that the client VG supports. This is the setup that was bequeathed to us by the... (3 Replies)
Discussion started by: maraixadm
3 Replies
rsm_memseg_import_map(3RSM)			      Remote Shared Memory Library Functions			       rsm_memseg_import_map(3RSM)

rsm_memseg_import_map, rsm_memseg_import_unmap - map or unmap imported segment SYNOPSIS
cc [ flag... ] file... -lrsm [ library... ] #include <rsmapi.h> int rsm_memseg_import_map(rsm_memseg_import_handle_t im_memseg,void **address, rsm_attribute_t attr, rsm_permission_t perm, off_t offset, size_t length); int rsm_memseg_import_unmap(rsm_memseg_import_handle_t im_memseg); DESCRIPTION
The rsm_memseg_import_map() and rsm_memseg_import_unmap() functions provide for mapping and unmapping operations on imported segments. The mapping operations are only available for native architecture interconnects such as Dolphin-SCI or Sun Fire Link. Mapping a segment allows that segment to be accessed by CPU memory operations, saving the overhead of calling the memory access primitives described on the rsm_mem- seg_import_get(3RSM) and rsm_memseg_import_put(3RSM) manual pages. The rsm_memseg_import_map() function maps an import segment into caller's address space for the segment to be accessed by CPU memory opera- tions. The im_memseg argument represents the import segment that is being mapped. The location where the process's address space is mapped to the segment is pointed to by the address argument. The attr argiment can be one fo the following: RSM_MAP_NONE The system will choose available virtual address to map and return its value in the address argument. RSM_MAP_FIXED The import segment should be mapped at the requested virtual address specified in the address argument. The perm argument determines whether read, write or a combination of accesses are permitted to the data being mapped. It can be either RSM_PERM_READ, RSM_PERM_WRITE, or RSM_PERM_RDWR. The offset argument is the byte offset location from the base of the segment being mapped to address. The length argument indicates the number of bytes from offset to be mapped. The rsm_memseg_import_unmap() function unmaps a previously mapped import segment. RETURN VALUES
Upon successful completion, these functions return 0. Otherwise, an error value is returned to indicate the error. ERRORS
The rsm_memseg_import_map() and rsm_memseg_import_unmap() functions can return the following errors: RSMERR_BAD_SEG_HNDL Invalid segment handle. The rsm_memseg_import_map() function can return the following errors: RSMERR_BAD_ADDR Invalid address. RSMERR_BAD_LENGTH Invalid length. RSMERR_BAD_MEM_ALIGNMENT The address is not aligned on a page boundary. RSMERR_BAD_OFFSET Invalid offset. RSMERR_BAD_PERMS Invalid permissions. RSMERR_CONN_ABORTED Connection aborted. RSMERR_MAP_FAILED Map failure. RSMERR_SEG_ALREADY_MAPPED Segment already mapped. RSMERR_SEG_NOT_CONNECTED Segment not connected. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ |MT-Level |MT-Safe | +-----------------------------+-----------------------------+ SEE ALSO
rsm_memseg_import_connect(3RSM), rsm_memseg_import_get(3RSM), rsm_memseg_import_put(3RSM), rsm_memseg_get_pollfd(3RSM), attributes(5) SunOS 5.10 13 Nov 2002 rsm_memseg_import_map(3RSM)

Featured Tech Videos

All times are GMT -4. The time now is 05:48 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy