10-10-2018
padmin
The VIO user ID and commands
Quote:
Instead of using the root user ID to issue commands, an administrative user ID-padmin-is used for all of the VIO controls. This user ID has a shell called the IOS command-line interface (ioscli) that runs a unique set of commands for managing devices assigned to the VIO servers. Many of these commands are similar to regular AIX commands (for example, lsdev) but use different flags and command structures (for example, lsdev -dev). But, most of the superuser level commands are new and perform many different operations at once. In fact, when administered properly, systems administrators will rarely have to become root.
Helpful padmin commands include:
help: This command lists all of the commands available in the ioscli. If you pass a specific command into it, such as help updateios, you can see the specific flags and syntax for that command.
Quote:
cfgdev: This command is the equivalent of the cfgmgr command and detects new physical and logical devices added to the VIO server.
oem_setup_env: This command is the equivalent of running su - root but without the need to enter a password. Again, you will rarely have to become root on a VIO server.
mkvdev: This command manages the virtual devices that you create and serve up to the VIO client LPARs.
mktcpip, lstcpip, and rmtcpip: These commands manage your networking from the command line and circumvent the need for utilities such as smitty tcpip.
lsmap: This command shows the relationships between disk resources and VIO client LPARs.
Reference:
The VIO cheat sheet
8 More Discussions You Might Find Interesting
1. Solaris
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
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
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
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
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
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
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
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
LEARN ABOUT DEBIAN
fence_drac
fence_drac(8) System Manager's Manual fence_drac(8)
NAME
fence_drac - fencing agent for Dell Remote Access Card
SYNOPSIS
fence_drac [OPTION]...
DESCRIPTION
fence_drac is an I/O Fencing agent which can be used with the Dell Remote Access Card (DRAC). This card provides remote access to control-
ling power to a server. It logs into the DRAC through the telnet interface of the card. By default, the telnet interface is not enabled.
To enable the interface, you will need to use the racadm command in the racser-devel rpm available from Dell. To enable telnet on the
DRAC:
[root]# racadm config -g cfgSerial -o cfgSerialTelnetEnable 1
[root]# racadm racreset
fence_drac accepts options on the command line as well as from stdin. Fenced sends parameters through stdin when it execs the agent.
fence_drac can be run by itself with command line options. This is useful for testing and for turning outlets on or off from scripts.
Vendor URL: http://www.dell.com
OPTIONS
-a IPaddress
IP address or hostname of the switch.
-c cmd_prompt
Force fence_drac to use cmd_prompt as the command prompt
-d dracversion
Force fence_drac to treat the device as though it was for the specified drac version
-D dumpfile
Debug file of the telnet interaction
-h Print out a help message describing available options, then exit.
-l login
Login name.
-m modulename
The module name of the blade when using DRAC/MC firmware.
-o action
The action required. reboot (default), off, on or status.
-p password
Password for login.
-S path
Full path to an executable to generate the password for login.
-f seconds
Wait X seconds before fencing is started
-V Print out a version message, then exit.
STDIN PARAMETERS
action = < param >
The action required. reboot (default), off, on or status.
agent = < param >
This option is used by fence_node(8) and is ignored by fence_apc.
cmd_prompt = < param >
Force fence_drac to use cmd_prompt as the command prompt
drac_version = < param >
Force fence_drac to treat the device as though it was for the specified drac version.
debug = < dumpfile >
Debug file of the telnet interaction
ipaddr = < hostname | ip >
IP address or hostname of the switch.
login = < param >
Login name.
modulename = < param >
The module name of the blade when using DRAC/MC firmware.
passwd = < param >
Password for login.
passwd_script = < param >
Full path to an executable to generate the password for login.
delay = < param >
Wait X seconds before fencing is started
SEE ALSO
fence(8), fence_node(8)
fence_drac(8)