somebody can help me to fix this? I'm restoring the wpar from wpar mksysb not a mksysb from principal Lpar.
It is not clear if the error comes from the host LPAR or the workload partition and you will have to investigate this first. It might be that the WPAR mksysb is faulty and missing something vital. Depending on what it is you might be able to circumvent it (i.e. by using normal network login as Neo suggested) or not. You also can try to put some missing file into the WPARs filesystem (which is accessible from the hosting LPAR) but for this you will need to know what it is that is missing.
If the error comes from the LPARs side perhaps something for the clogin command to work is missing and you need to correct this on your LPAR.
In other words: there are a lot of things that could be responsible for this error and we have simply not enough information. Care to describe your environment and the error in some greater detail?
Hi,
I have a shared AIX wpar configured.
I have started snmpd process on shared AIX wpar.
But when i tried to query a MIB id using the following command
/opt/OV/bin/snmpget -d -v 1 -c public -p <hostname> .1.3.6.1.2.1.1.7.0
i get the following error message
#... (0 Replies)
im kinda new to shell scripting so i need some help
i try to run this script and get the error code
> 5 ")syntax error: operand expected (error token is "
the code for the script is
#!/bin/sh
#
# script to see if the given value is correct
#
# Define errors
ER_AF=86 # Var is... (4 Replies)
Hello,
We have a system running AIX 6.1.7.1. We have created a Workload Partition(wpar) on this system with wpar specific routing enabled.
On wpar, we are running DNS (UDP/53) and syslog (UDP/514).
en0: 1.1.1.1/255.255.255.0 NOT assigned to any wpar
en1:... (0 Replies)
seems to be WPAR is quite easy to set up..without additional licenses..
If I don't need Linux and all my legacy and new apps are happy in AIX 7.1 (the latest OS), I could save all troubles and use WPAR.
Can someone comment on this ??
One copy of OS to maintain, so to speak..
... (4 Replies)
Hi All,
This is for WPAR monitoring shell script, earlier opened thread was closed, had to open a new thread, as suggested I have used script as below, But am trying to get the output in below format, need suggestions with it. Below is the lswpar output, required output format.
... (7 Replies)
Hi.
I've setup a wpar on aix
mkwpar -h ibmunix2 -i -r -N interface=en0 address=10.6.0.1 netmask=255.255.255.0 -n ibmunix2
When i log into ibmunix2 it can't ping any external host,include the ibm host.
How to set route for network please?
I've set ibmunix2 with a different subnet.
... (7 Replies)
Anyone running CICS TX in a WPAR ?
In my attempts to run CICS TX 5.1.0.1 in a WPAR..... CICS fails to start due to unable to load a CICS IPC Kernel Extension. The Kernel Extension is 64 bit (so not a 32 vs 64 bit issue).
Base system/LPAR is Power8 and AIX 7.1 TL3 SP5. WPAR is versioned... (4 Replies)
AIX 7.1
New to WPAR, hopefully just missing something simple here.
Creating the WPAR like this.....
(The box where the WPAR is hosted does have an iscsi protocol device)
mkwpar -h wpar08 -l -n wpar08 -N interface=en0 address=xxx.xx.xx.xxx netmask=255.255.255.0 -D devname=/dev/iscsi0 -D... (0 Replies)
Discussion started by: TomR
0 Replies
LEARN ABOUT DEBIAN
lg.conf
lg.conf(5) File Formats Manual lg.conf(5)NAME
lg.conf - looking glass configuration file
DESCRIPTION
lg.conf contains configuration for the looking glass scripts.
The syntax is that of perl(1). It is used to set variables that affect run-time behavior and/or to locate resources.
VARIABLES
The following variables are used (alphabetically):
LG_AS_REG
*** not implemented.
LG_BGP_RT
Allows show ip bgp neighbor commands that can produce heavy output, such as sh ip bgp neighbor <ip> advertised-routes for a transit
customer when the neighbor address is followed by 'advertised-routes' for the sh ip bgp neighbor query.
LG_CACHE_DIR
Sets the location of the cache directory. The looking glass uses this to hold lock files, log files, and output from cached
commands.
Default: ./tmp
Note that the default is relative to the directory where lg.cgi runs in the server's document root (e.g.:
/usr/local/www/data/lg/tmp).
LG_CACHE_TIME
Sets the number of seconds that the looking glass should cache output from commands that tend to produce a lot of output, such as
'show ip bgp dampened-paths'.
Default: 600
LG_CLOGINRC
Defines the location of the cloginrc(5) that the looking glass should use. The path may be relative to the directory where the CGI
scripts run in the server's document root.
Default: $HOME/.cloginrc
Note that the .cloginrc must be readable by the user or group that will be running the CGI and that clogin(1) will not allow a world
readable .cloginrc. The user is normally that of the http server (httpd).
LG_IMAGE
Defines a html image tag (<img>) which, if defined, will be included at the top of the looking glass pages. It may contain any html
as it is simply handed off to print().
Example: $LG_IMAGE="<img src=/icons/rancid.gif hspace=0>
<font size=+2>FOO</font>";
LG_INFO
Defines information in html format which, if defined, will be included at the bottom of the looking glass form page. It may contain
any html as it is simply handed off to print().
Example: $LG_INFO="For Support contact <a href=mailto:webmaster@localhost>webmaster</a>";
LG_LOG Defines the fully qualified path name (i.e.: begins with '/') for the log file or the syslog(3) facility to use for logging. For
syslog, the argument is the lowercase name of a syslog facility (see syslog.h) without the 'LOG_' prefix.
Example: local0
Default: $LG_CACHE_DIR/lg.log
LG_ROUTERDB
Sets the location for the router.db file in rancid's router.db(5) format. It lists the devices that should be available to the
looking glass users. Only those devices of supported types and with state 'up' are made available. If not defined and the default
file does not exist, the looking glass will compile a list from the router.db files of all the groups present in rancid, that is,
the list will be a concatenation of the available router.db(5) files.
Note that if the concatenation method is used, it may be necessary to alter the mode of the router.db files in the rancid group
directories, since rancid's default umask is 027 (see rancid.conf(5)).
LG_STRIP
Causes the LG to strip login information from the looking glass results. Since Expect often munges disabling echo when passwords
are entered, this is a SECURITY CONCERN! However, this output can be very useful for debugging clogin problems.
LG_STYLE
Defines the URL of a style sheet to be used for HTML formatting.
PATH Is a colon separated list of directory pathnames in the file system where rancid's login scripts, clogin(1) etc.) and programs
needed within these, such as telnet(1), are located. Its value is set by configure. Should it be necessary to modify PATH, note
that it must include $BASEDIR/bin (see above).
Queries ...................................
ENVIRONMENT
LG_CONF
Location of lg.conf file. See the FILES section for more information.
ERRORS
lg.conf is interpreted directly by perl(1), so its syntax follows that of perl. Syntax errors may produce quite unexpected results.
FILES
/etc/rancid/lg.conf
Configuration file described here.
lg.conf is located by the value of the environment variable LG_CONF, in the CWD (current working directory), or the sysconfdir
defined when rancid was installed, in that order.
SEE ALSO cloginrc(5), lg_intro(1), router.db(5)HISTORY
In RANCID releases prior to 2.3, lg.conf was located in the util/lg sub-directory of the install path. This was changed to be more
consistent with common file location practices.
7 Jan 2004 lg.conf(5)