05-16-2011
HMC/LPAR license is not free and VIO is almost free but limited in functionality. Ahh I found a video topic with it, i'll post/summarize it here once i've seen it.
Thanks.
10 More Discussions You Might Find Interesting
1. AIX
Hello guys,
It would be so nice of you if someone can provide me with these informations.
1) My SAN group assigned 51G of LUN space to the VIO server.I ran cfgdev to discover the newly added LUN. Unfortunately most of the disks that are in VIO server is 51G. How would I know which is the newly... (3 Replies)
Discussion started by: solaix14
3 Replies
2. AIX
I have a DUAL VIO ( IBM Virtual I/O ) setup on p 570.
Two Vio server ( VIOS ) and many LPAR clients.
VIO ( latest version + service pack + applied the fix ) and AIX 6.1 ML2
When both VIOs are running, and if I turn on a Client LPAR, the LPAR hangs at LED 25b3 for more than 1 hour then it... (2 Replies)
Discussion started by: filosophizer
2 Replies
3. AIX
Hello,
I have created mapping of 2 virtual adapters for Lpars using following command:
mkvdev -vdev ipanalyzerlv1 -vadapter vhost11
mkvdev -vdev ipanalyzerlv -vadapter vhost13
The above two commands were succesfull
but when I want to map the third virtual device to the same Lpar than... (3 Replies)
Discussion started by: Vit0_Corleone
3 Replies
4. AIX
Hello,
Lets say for simplicity that I do not use any vlan config inside my server - one lpar group use hea physical port1, another group hea physical port2. Physical port1 configured as vlan1 on external switch, physical port2 as vlan2.
What is the common practice - should I isolate my vios... (0 Replies)
Discussion started by: vilius
0 Replies
5. AIX
Hi guys,
does anyone know how to get a list of the LPAR running on VIOS?
Thanks! (5 Replies)
Discussion started by: cecco16
5 Replies
6. AIX
I am trying to install AIX 5.3 on one of the LPARs through VIOS but I get this error 0518
Reference Code Selection
0518 (Time stamp: 12/18/12 12:10:20 AM UTC)
Starting kernel (Time stamp: 12/18/12 12:10:15 AM UTC)
AIX is starting. (Time stamp: 12/18/12 12:10:15 AM... (10 Replies)
Discussion started by: filosophizer
10 Replies
7. AIX
Hello,
What's the difference between lpar and a lun?
Best regards,
Vishal (2 Replies)
Discussion started by: Vishal_dba
2 Replies
8. AIX
Hi,
Just joined to new company with one Power 720 Express (8202-E4C) server and have no much experience with IBM systems.
I am trying to move everything I mentioned to different subnet as required by customer contract (currently sitting on same subnet as company lan). Access to this subnet will... (8 Replies)
Discussion started by: spricer
8 Replies
9. AIX
Hello,
VIOS 2.2.1.4 using IVM.
I'm trying to extend a virtual disk assigned to a running lpar so that I can expand the lpar's datavg and grow some filesystems for the user.
Storage admin expanded the lun and new size was reflected in VIO right away. I then needed the storage pool to... (2 Replies)
Discussion started by: j_aix
2 Replies
10. UNIX for Advanced & Expert Users
Hi everybody,
I have Power5 server with 4 internal hdisks each of 70Gb.
VIOS server was installed via Virtual I/O Server Image Repository on the HMC.
HMC release - 7.7.0
VIOS rootvg installed on 2 disk(these disks merged to one storage pool during VIOS install process),and 2 others hdisks... (2 Replies)
Discussion started by: Ravil Khalilov
2 Replies
LEARN ABOUT DEBIAN
tm::objectable
TM::ObjectAble(3pm) User Contributed Perl Documentation TM::ObjectAble(3pm)
NAME
TM::Synchronizable - Topic Maps, trait for storing objects into backends
SYNOPSIS
my $tm = .... # get a topic map from somewhere
use Class::Trait;
Class::Trait->apply ($tm, "TM::ObjectAble");
my %store; # find yourself a proper store, can be anything HASHish
# append it to the list of stores, or ....
push @{ $tm->storages }, \%store;
# prepend it to the list of stores
unshift @{ $tm->storages }, \%store;
# store it (the proper storage will take it)
$tm->objectify ('tm:some-topic', "whatever object or data");
# get it back
my @objects = $tm->object ('tm:some-topic', 'tm:some-topic2');
# get rid of it
$tm->deobjectify ('tm:some-topic');
DESCRIPTION
This trait implements functionality to store arbitrary data on a per-topic basis.
Conceptually, the storage can be thought as one large hash, as keys being use the internal topic identifiers, as values the object data.
But to allow different topics to store their object data in different places, this interface works with a list of such hashes. Each hash
(native or tied to some implementation) in the list is visited (starting from the start of the list) and can take over the storage. Whether
this is based on the topic id, on some other topic information, or on the MIME type of the data (if it has one), is up to the
implementation to decide.
INTERFACE
Methods
storages
$listref = $tm->storages
This method returns an array reference. You can "unshift" or "push" your storage implementation onto this list.
Example:
my %store1;
push @{ $tm->storages }, \%store1
objectify
$tm->objectify ($tid => $some_data, ...);
This method stores actually the data. It takes a hash, with the topic id as keys and according values and tries to find for each of the
pairs an appropriate storage. If none can be found, it will raise an exception.
NOTE: Yes, this is a stupid name.
deobjectify
$tm->deobjectify ($tid, ...)
This method removes any data stored for the provided topic(s). If no data can be found in the appropriate storage, an exception will be
raised.
object
@objects = $tm->object ($tid, ...)
This method returns any data stored for the provided objects. If no data can be found for a particular topic, then "undef" will be
returned.
SEE ALSO
TM
AUTHOR INFORMATION
Copyright 20(10), Robert Barta <drrho@cpan.org>, All rights reserved.
This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
http://www.perl.com/perl/misc/Artistic.html
perl v5.10.1 2010-10-27 TM::ObjectAble(3pm)