I have running dual VIOS on a P9 systems, and just created a new LPAR profile. My objective is to create LPAR Client VFC adapters, and then DLPAR VFC Server adapters on the VIOS.
In the HMC v9 Enhanced GUI, I have DLPAR a VFC adapter to both VIOS, however, you can't specify the partner adapter to connect to? Why is that?
Also, when I use command line to DLPAR the VFC adapters using chhwres with the -s option, to specify the partner adapter when adding in the VFC adapters to a VIOS, it says that the VFC adapter with X value already has the X value partner adapter already associated with another adapter.
e.g In the VIOS profile, an existing Server Fibre Channel Adapter has Adapter ID 14 and Partner Adapter ID 11, and I want to DLPAR Server Fibre Channel Adapter Adapter ID 15 and Partner Adapter ID 11 (for another LPAR of course) and it won't allow.
Command:
Why is this failing? All existing Server Fibre Channel adapters in the VIOS profile all have obviously different Server Adapter IDs but all pointing to the same Partner Adapter IDs to their own LPAR clients.
I am trying to run the lscod command against an HMC that has managed system names with spaces.
Tried enclosing the managed system names in quotes; single and double.
How do I get the command to run?
ssh hmcname lscod -m 'managed system 1' -t cap -r proc -c cuod
Thanks,
~Donavon (0 Replies)
I started the AIX install with a fiber channel disk, and let it run:
restricted by GSA ADP Schedule Contract with IBM Corp.
. . . . . << End of copyright notice for perfagent.tools >>. . . .
... (2 Replies)
Hi,
We have a P595 machine with a dual port Fiber card per VIOs.
We have two VIOs in the box.
VIO1: ---> 2 port Fiber Card
VIO2: ---> 2 port Fiber Card
One port on each fiber card is utilized. Connected to SAN switches. We are getting all disks from SAN both for VIOs and LPARs.
Now... (0 Replies)
Hi,
I am executing below commands on HMC. I see that there is only colon ":" in output.
Can someone please help why I am getting ":" in output? Why I am not getting proper output?
xxxxx@yyyyhmc1:~> viosvrcmd -m PCC-p590#2-SN024D8F0 -p ppvio1 -c "lsmap -all"
:xxxxx@yyyyhmc1:~> viosvrcmd... (0 Replies)
Hi all,
i would like to know if it's possible upgrade AIX 5.3 to 6.1 on a LPAR without use the HMC.
so i would like to know if i must use the console to do it or i can do all from the up&running system on LPAR.
Thanks in advance.
Mario (4 Replies)
I am trying to generate a report to track dlpar operation performed on a MS and was wondering if anyone has done this before.
I can get history from HMC using lssvcevents , but this does not give me details as to what quantity was added or removed .
Any thoughts ?
Thanks (3 Replies)
Hi ,
I would like to access the cd drive of , i have power series server , and have lpars .
I try to install AIX in an lpar via HMC, but it can't access the cd drive.
how i can make installtion or make the the cd drive accessible in hmc or in power series server?
Thanks in advance (2 Replies)
Trying to get the IP address of the HMC connected to some servers running AIX 6 and 7. I thought this would be as easy as running 'lsrsrc IBM.MCP IPAddresses', but when I run that command, the resource is empty. Is there some where else I should be looking, or is there a reason why this resource... (5 Replies)
hello
P6 was managed by HMC, tried to install on it VIOS 2.2.6
and got this error message
Hosting requires a hosting partition -- boot not permitted
vios-4 - imgbb.com
then after creating an lpar in HMC got this message
B2001230
vios-3 - imgbb.com
anyone know how to solve this... (3 Replies)
Discussion started by: filosophizer
3 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)