I see under the LPARs profile, the LHEA lists 4 etities. leave it to IBM to NOT call them NICs or give them names of any sort, like 'broadcom xxxx' , they just leave them as
You might want to read this for help on configuring LHEAs. IMHO you should go for SEAs instead because these are more high-availability.
Anyhow, the "ugly names" you belittle are location codes. You can deduct from the location code exactly where a (physical) adapter has been placed and of which type it is. This information is much more valuable when you have a big system with several CECs and dozens of adapters and you want to replace one of these than the "Broadcom blabla" would be. It is really not IBMs fault that you seemingly have never had to administrate anything even midrange-sized, let alone the bigger irons.
You might have a very small system but it is built (and works) the same way as the dozen or so p780s that populate our data center. To work with a system that houses 50 LPARs with ease you need other methods than when you work with some PC. ESX basically run on PC hardware, somewhat rugged ip to be data center-ready. AIX does not. AIX runs on systems far bigger in every respect than any PC. Just have a look at the p780 and p870 datasheets to find out just how big these systems can get.
You might find the methods employed overly complicated but i can tell you from years-long experience that they are perfectly reasonable in an enterprise-level context. I suggest you either start using these methods and exploit the advantages they offer or you return to administrating your ESXi- or whatever virtualisation-platform you prefer.
Hi all,
I have the following configuration
2 ds3524 storage disk systems located over 2 locations
2 P720 server located over 2 locations
DS3524 are connected to san switch.
Each vio server has 1 fc adapter attached to a san switch.
per p720 server 2 virtual io servers. Vio 1 has 1 lun... (2 Replies)
hi guys,
i need to develop following setup for a customer:
high availability oracle database on aix7 and linux in 2 different LPAR using dual ps700 blande a ds3400 and HMC.
the question is, it is possible to have automatic vioc failover(aix,linux) when for example 1 vios goes down?
in... (6 Replies)
Hi,
I am creating "LSOF" solaris package from solaris "source" files. I have compiled the source file and with that i created prototype file also. Then using pkgmk command i can make the package .
In the package i am having (pkginfo pkgmap reloc) two file and one directory respectively
But... (3 Replies)
Hello everyone,
I've been attempting to make a program which creates user accounts from a file which contains the usernames required. It also checks if the directory of the username exists in the C:\Users directory and then is going to give the option to delete the directory, or rename it, this... (1 Reply)
Some simple questions about Intellistation 285 and powervm.
I want to learn AIX,so i will buy an used I285 from ebay.
1)Will support aix 7.1?
2)Is powervm avaliable?Where to download or buy it?
Thanks (3 Replies)
There can be configurations in IBM Server wherein a
standalone partition is created on some supported IBM Server
Or
A VIOS - VIOC LPARs created.
Now in both cases they are lpars. But if I want to differentiate b/w a standalone LPAR vs an VIOC LPAR how can I do..?
On a... (2 Replies)
Hello,
POWER7 machine.
4 x 1Gbit port ethernet adapter is dedicated to vios. 8023ad etherchannel is created using those 4 ports. Etherchannel adapter is shared to lpars using SEA.
If I test network performance directly from vios partition (using iperf) I'm geting nice 4Gbit throughput. But if... (3 Replies)
Hello,
After installing on P6 which is POWERVM IVM VIOS enabled (VET CODE D21C77ACD9229817CA1F00002C10004164 )
i get this message
"I/O hosting requires a hosting partition - boot not permitted".
HMC was connected to the machine
then HMC was removed through ASMI
Searching on... (2 Replies)
Discussion started by: filosophizer
2 Replies
LEARN ABOUT DEBIAN
log::any::adapter::development
Log::Any::Adapter::Development(3pm) User Contributed Perl Documentation Log::Any::Adapter::Development(3pm)NAME
Log::Any::Adapter::Development -- Manual for developing new Log::Any adapters
VERSION
version 0.07
SYNOPSIS
The adapter module:
package Log::Any::Adapter::YAL;
use strict;
use warnings;
use Log::Any::Adapter::Util qw(make_method);
use base qw(Log::Any::Adapter::Base);
# Optionally initialize object
#
sub init {
my ($self) = @_;
$self->{attr} = ...;
}
# Create logging methods: debug, info, etc.
#
foreach my $method ( Log::Any->logging_methods() ) {
make_method($method, sub { ... });
}
# Create detection methods: is_debug, is_info, etc.
#
foreach my $method ( Log::Any->detection_methods() ) {
make_method($method, sub { ... });
}
and the application:
Log::Any->set_adapter('YAL');
DESCRIPTION
This document describes how to implement a new Log::Any adapter.
The easiest way to start is to look at the source of existing adapters, such as Log::Any::Adapter::Log4perl and
Log::Any::Adapter::Dispatch.
NAMING
If you are going to publicly release your adapter, call it 'Log::Any::Adapter::something' so that users can use it with
Log::Any->set_adapter(I<something>);
If it's an internal driver, you can call it whatever you like and use it like
Log::Any->set_adapter('+My::Log::Adapter');
BASE CLASS
All adapters must directly or indirectly inherit from Log::Any::Adapter::Base.
METHODS
Constructor
The constructor ("new") is provided by Log::Any::Adapter::Base. It will:
o place any adapter arguments into a hash, along with the category
o bless the hash into your subclass
o call "init" which may be optionally provided by your subclass
At this point, overriding the default constructor is not supported. Hopefully it will not be needed.
The constructor is called whenever a log object is requested. e.g. If the application initializes Log::Any like so:
Log::Any->set_adapter('Log::YAL', yal_object => $yal, depth => 3);
and then a class requests a logger like so:
package Foo;
use Log::Any qw($log);
Then $log will be populated with the return value of:
Log::Any::Adapter::Yal->new(yal_object => $yal, depth => 3, category => 'Foo');
This is memoized, so if the same category should be requested again (e.g. through a separate "get_logger" call, the same object will be
returned. Therefore, you should try to avoid anything non-deterministic in your "init" function.
Required methods
The following methods have no default implementation, and MUST be defined by your subclass:
debug ($msg)
info ($msg)
notice ($msg)
warning ($msg)
error ($msg)
critical ($msg)
alert ($msg)
emergency ($msg)
These methods log a message at the specified level.
To help generate these methods programmatically, you can get a list of the method names with
Log::Any->logging_methods
is_debug ()
is_info ()
is_notice ()
is_warning ()
is_error ()
is_critical ()
is_alert ()
is_emergency ()
These methods return a boolean indicating whether the specified level is active.
To help generate these methods programmatically, you can get a list of the method names with
Log::Any->detection_methods
Optional methods
The following methods have no default implementation but MAY be provided by your subclass:
init ()
This is called after the adapter object is created and blessed into your class. It will be a hash containing the parameters that were
passed to new(). Perform any necessary validation or initialization here.
Support methods
The following methods are useful for defining adapters:
delegate_method_to_slot ($slot, $method, $adapter_method)
Handle the specified $method by calling $adapter_method on the object contained in $self->{$slot}.
See Log::Any::Adapter::Dispatch and Log::Any::Adapter::Log4perl for examples of usage.
Log::Any->logging_methods
Returns a list of logging methods: debug, info, etc.
Log::Any->detection_methods
Returns a list of detection methods: is_debug, is_info, etc.
Log::Any->logging_and_detection_methods
Returns a combined list of logging and detection methods.
SEE ALSO
Log::Any
COPYRIGHT AND LICENSE
This software is copyright (c) 2011 by Jonathan Swartz.
This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.
perl v5.14.2 2012-02-22 Log::Any::Adapter::Development(3pm)