01-15-2016
A very concise description by agent.kgb, thank you for that!
@thread-o/p: notice that what agent.kgb described is in fact "best practice" and even if you would not have the need to reboot the VIOS right now you should set things up like agent.kgb described it anyway!
If you find out that this is not the case it would be a perfect occasion to get some downtime URGENTLY and correct this! Otherwise these problems will come back to haunt you and most probably will raise their ugly heads in the most inconvenient moment possible.
I hope this helps.
bakunin
This User Gave Thanks to bakunin For This Post:
10 More Discussions You Might Find Interesting
1. Solaris
Hi Guru's
Can any want here could explain to me the different between soft reboot and hard reboot .
Best Regards
Seelan (3 Replies)
Discussion started by: seelan3
3 Replies
2. 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
3. AIX
In a dual vio, how will u know one lpar is in which vio? (1 Reply)
Discussion started by: shobhan.murthy
1 Replies
4. AIX
Hi Guys,
I'm working on building a new 595 machine.. I'm try to achieve high availability for the VIO clients using 2 VIO servers, The ethernet part is satisfied using SEA failover, Now how do I achieve redundancy for the disks, its the servers internal disk attached to the scsi cards...
... (2 Replies)
Discussion started by: kkeng808
2 Replies
5. AIX
I am planning carving out dual VIO servers on a P750 based and would like to know how to allocate internal disks to the VIOS. This has 4 internal disks and I would to assign 2 disks to each VIO.
This is what I was thinking of assigning . Any advise?
vio1
U5802.001.9K8H757-P1-C1 PCI-E x8... (17 Replies)
Discussion started by: mk8570
17 Replies
6. AIX
I have same lun (hdisk3) assigned to 2 vios server (dual vio server) and this is mapped to the client lpar. I have sddpcm on the VIO.
On the VIOA, the attributes for fscsi1 and fscsi3 are set to fast_fail and dyntrk is set to yes
Now, if I do a lqueryvg -Atp on the hdisk3, I get a "DISK... (4 Replies)
Discussion started by: mk8570
4 Replies
7. Red Hat
I am working in AIX. In a P series machine both aix and linux os can install.. specific command is there for aix to list out the vio servers details mapped in a frame(ie. lssrc "IBM.ManagementServer", like that..) is there any command is der to list out vio servers details in linux or how to find... (1 Reply)
Discussion started by: muralikrish
1 Replies
8. 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
9. 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
10. AIX
I hope someone has experienced this problem before and can help. I have a P730 (8231-E2D) which is fitted with 8 IBM SAS disks on 2 separate SISSAS controllers. The disk type is ST9146853SS (Seagate SAS 146Gb).
The problem occurs when I try to install the VIO server software at 2.2.3. It... (3 Replies)
Discussion started by: johnf
3 Replies
LEARN ABOUT ULTRIX
reboot
reboot(8) System Manager's Manual reboot(8)
Name
reboot - automatic reboot procedures
Syntax
/etc/reboot [ -n ] [ -q ]
Description
The ULTRIX system is booted by loading a kernel image, usually into memory at location zero and transferring to zero. Because the system
is not reenterable, the kernel image must be read in from disk each time the system is bootstrapped.
When the reboot of a running system is desired, is normally used. If there are no users, can be used. The command causes the disks to be
synced, and then a multiuser reboot is initiated. The system is booted and an automatic disk check is performed. If the procedure suc-
ceeds, the system is then brought up for the users.
The system will reboot itself after a power failure or after a crash, provided auto-restart is enabled on your system. A consistency check
of the file systems will be performed and, unless the check fails, the system will resume multiuser operations.
Options
-n Prevents the disks from being synced.
-q Reboots quickly and ungracefully, without shutting down running processes first.
Files
System code
See Also
crash(8v), fsck(8), halt(8), init(8), newfs(8), rc(8), shutdown(8)
reboot(8)