Sponsored Content
Top Forums UNIX for Advanced & Expert Users How to identify the blade from VIO server? Post 303024476 by x41 on Tuesday 9th of October 2018 12:13:57 PM
Old 10-09-2018
How to identify the blade from VIO server?

Hello,
I would like to identify the blade or/and bladecenter from the hosted VIO server.
I prefer the "command line" solution. May be kdb.
Like, I want to ask the child about his father.
Thank you
 

8 More Discussions You Might Find Interesting

1. Solaris

adding memory to sun blade server ...

Hi, this is my 1st post here, I don't know is it proper or not for the question I have, but I may try ask anyway, since it is question about sun's hw/sw issue... I have my blade 1000 installed additional memory kits, it was originally 2G memory installed on Group0(Bank 0/2) Dimm slots, I got... (5 Replies)
Discussion started by: netshu
5 Replies

2. AIX

How to identify which HDD is allocated to VIO server

Hello All, I am new to AIX VIO LPAR server. We have VIO 1.5 server installed with few logical valumes and 3-4 Virtual machines running. I wanted to restructer the space allocation to logical values. but don't know which harddisk, hold VIO server installation. Can someone please help to me... (8 Replies)
Discussion started by: kishorbhede
8 Replies

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

4. AIX

VIO server on p520

trying to put VIO server software into this p520, firmware upgraded to the latest and greatest..SF240_415_318 , I think a few questions, on this practice AIX machine on AIX 7.1 VIO can only be installed if ASMI or HMC is running ??? if so, perhaps ASMI is much simpler, since I will need to... (2 Replies)
Discussion started by: ppchu99
2 Replies

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

6. AIX

Mirroring vio server

Hi, I would like to know installing vio server on local disk and mirroring rootvg, if I am creating AIX VIO CLIENT(lpar), and any of single local hard disk failuare. will it affect lpars? will lpars able to boot. what needs to be done? (1 Reply)
Discussion started by: manoj.solaris
1 Replies

7. AIX

VIO Server

Hi, I am facing an issue in vio server. When I run bosboot -ad /dev/hdisk0 I am getting an error trustchk: Verification of attributes failed: /usr/sbin/bootinfo : accessauths regards, vjm Please use code tags next time for your code and data. (8 Replies)
Discussion started by: vjm
8 Replies

8. AIX

network interfaces on vio server

Hi, I would like to know after the installation of vio server. how many logical network interfaces will be created on vio server if I am having two physical interfaces on vio server. I am asking this question because I would like know to on the basis of logical network interfaces creation on... (0 Replies)
Discussion started by: manoj.solaris
0 Replies
DEVICE_IDENTIFY(9)					   BSD Kernel Developer's Manual					DEVICE_IDENTIFY(9)

NAME
DEVICE_IDENTIFY -- identify a device, register it SYNOPSIS
#include <sys/param.h> #include <sys/bus.h> void DEVICE_IDENTIFY(driver_t *driver, device_t parent); DESCRIPTION
The identify function for a device is only needed for devices on busses that cannot identify their children independently, e.g. the ISA bus. It is used to recognize the device (usually done by accessing non-ambiguous registers in the hardware) and to tell the kernel about it and thus creating a new device instance. BUS_ADD_CHILD(9) is used to register the device as a child of the bus. The device's resources (such as IRQ and I/O ports) are registered with the kernel by calling bus_set_resource() for each resource (refer to bus_set_resource(9) for more information). Since the device tree and the device driver tree are disjoint, the DEVICE_IDENTIFY() routine needs to take this into account. If you load and unload your device driver that has the identify routine, the child node has the potential for adding the same node multiple times unless specific measure are taken to preclude that possibility. EXAMPLES
The following pseudo-code shows an example of a function that probes for a piece of hardware and registers it and its resource (an I/O port) with the kernel. void foo_identify(driver_t *driver, device_t parent) { device_t child; retrieve_device_information; if (devices matches one of your supported devices && not already in device tree) { child = BUS_ADD_CHILD(parent, 0, "foo", -1); bus_set_resource(child, SYS_RES_IOPORT, 0, FOO_IOADDR, 1); } } SEE ALSO
BUS_ADD_CHILD(9), bus_set_resource(9), device(9), device_add_child(9), DEVICE_ATTACH(9), DEVICE_DETACH(9), DEVICE_PROBE(9), DEVICE_SHUTDOWN(9) AUTHORS
This manual page was written by Alexander Langer <alex@FreeBSD.org>. BSD
May 13, 2004 BSD
All times are GMT -4. The time now is 05:21 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy