Sponsored Content
Operating Systems AIX Power8 S812L:HMC issue and ... Post 302962143 by lilyn on Tuesday 8th of December 2015 08:35:57 PM
Old 12-08-2015
Agent.kgb: still "no Disks Detected" with RH LE 7.2
 

10 More Discussions You Might Find Interesting

1. AIX

Hmc

Well i am right now working on an IBM P550 risc server with an HMC connected.. The server has 2 logical partitions (Lpar). both lpar is having Aix 5.3 installed. Now I have a doubt.. is it possible to have Aix in one lpar and windows 2003 in another.. cheers Bala (4 Replies)
Discussion started by: balaji_prk
4 Replies

2. AIX

Hmc

Hello everybody, had a question. Iam having a p650 box here, System Model: IBM,7038-6M2 Machine Serial Number: 1078DCC managed system - 1 which has 2 lpars on it i added memory to the box(made sure that memory added was in proper quads and was verified by a CE) after i rebooted the box, the... (4 Replies)
Discussion started by: karthikosu
4 Replies

3. AIX

CDROM Issue on LPAR HMC VIO

Whenever I assign/unassign a CDROM ( RAID CTRL ) to Active LPAR from HMC, I have to reboot the LPAR. How can I do it without rebooting the LPARS. POWER6 with HMC LPARS = AIX 6.1 Any info developerWorks : AIX and UNIX : PowerVM Forum : Moving CD-ROM/DVD-ROM dynamically ... But... (5 Replies)
Discussion started by: filosophizer
5 Replies

4. AIX

AIX and HMC installation issue

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)
Discussion started by: Gideon1a
2 Replies

5. AIX

HMC Commands

Hello All, Can anybody knows a command, what I can check the processes in the HMC restricted shell? :wall: (1 Reply)
Discussion started by: kalaso
1 Replies

6. AIX

[TIP] Migration to POWER8

Read "Migration to POWER8" article to get prepared for migration to POWER8: link removed, advertisement (0 Replies)
Discussion started by: pave01
0 Replies

7. AIX

New IBM Power8 (S822) and StorWiz V3700 SAN, best practices for production setup/config?

Hello, Got a IBM Power8 box (S822) that I am configuring for replacement of our existing IBM machine. Wanted to touch base with the expert community here to ensure I don't miss anything critical in my setup/config of AIX. Did a fresh AIX 7.1 install on the internal scsi hdisk, mirror'ed... (3 Replies)
Discussion started by: c3rb3rus
3 Replies

8. AIX

StorWize v3700 and Power8 (S822) AIX, configuration best practice for LUNs?

Hello, We have an Power8 System (S822) and a IBM StorWize v3700 SAN. The OS is AIX 7.1. With this hardware from what I read I need to download/install special SDDPCM drivers, so I did (SDDPCM VERSION 2.6.6.0 (devices.sddpcm.71.rte). I carved my volumes in the StorWize and presented to... (3 Replies)
Discussion started by: c3rb3rus
3 Replies

9. AIX

HMC in VmWare NIC sl0 issue.

Hi There, First of all I'm new to *nix world, so bear with me and English is not my native tongue :) Now I'm working on the HMC 7.3.3.0 ServPack:0 base_version:20080402.1 to make it work in VmWare (testing in Workstation) I've got HMC installed and realized that network options in GUI... (8 Replies)
Discussion started by: JKat
8 Replies

10. AIX

IBM Power Linux Cluster Fence device on Power8 Platform

wasn't quite sure which forum to post in. What typical fence device to configure for a Power Linux PaceMaker Cluster running on the Power8 Platform (S822 Model of hardware), or what should be ordered with the S822 for use as a Fence Device? (5 Replies)
Discussion started by: mrmurdock
5 Replies
Agent::Channel(3pm)					User Contributed Perl Documentation				       Agent::Channel(3pm)

NAME
Log::Agent::Channel - ancestor class for all Log::Agent channels SYNOPSIS
@Log::Agent::Channel::XXX::ISA = qw(Log::Agent::Channel); DESCRIPTION
The "Log::Agent::Channel" class is the root class from which all "Log::Agent" channels inherit. It is a deferred class, meaning that it cannot be instantiated directly. All the deferred routines need to be implemented by its heirs to form a valid driver. Internally, the various "Log::Agent::Driver" objects create "Log::Agent::Channel" instances for each logging channel defined at driver creation time. The channels are therefore architecturally hidden within "Log::Agent", since this module only provides redefined mappings for the various logxxx() routines (logerr(), logwarn(), logdie(), etc...). However, this does not mean that channel classes cannot be used externally: the "Log::Agent::Logger" extension makes "Log::Agent::Channel" objects architecturally visible, thereby offering an application-level logging API that can be redirected to various places transparently for the application. CHANNEL LIST
The following channels are currently made available by "Log::Agent". More channels can be defined by the "Log::Agent::Logger" extension: Log::Agent::Channel::File This channel writes logs to files, defined by their path or via a magical opening sequence such as "|cmd". See Log::Agent::Channel::File. Log::Agent::Channel::Handle This channel writes logs to an already opened descriptor, as specified by its file handle: an IO::Handle object, or a GLOB reference such as *FILE. See Log::Agent::Channel::Handle. Log::Agent::Channel::Syslog This channel redirects logs to the syslogd(8) daemon, which will then handle the dispatching to various logfiles, based on its own configuration. See Log::Agent::Channel::Syslog. INTERFACE
You need not read this section if you're only using "Log::Agent". However, if you wish to implement another channel, then this section might be of interest. The following routines are deferred and therefore need to be defined by the heir: write($priority, $logstring) Emit the log entry held in $logstring, at priority $priority. A trailing " " is added to the $logstring, if needed (i.e. if the physical entity does not do it already, like syslog does). The $priority argument must be a valid syslog priority, i.e. one of the following strings: "emerg", "alert", "crit", "err", "warning", "notice", "info", "debug". The $logstring may not really be a plain string. It can actually be a Log::Agent::Message object with an overloaded stringification routine, so the illusion should be complete. close Close the channel. make This is the creation routine. Its signature varies for each channel, naturally. AUTHOR
Raphael Manfredi <Raphael_Manfredi@pobox.com> SEE ALSO
Log::Agent::Channel::File(3), Log::Agent::Channel::Handle(3), Log::Agent::Channel::Syslog(3), Log::Agent::Logger(3). perl v5.10.0 2002-03-09 Agent::Channel(3pm)
All times are GMT -4. The time now is 12:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy