Sponsored Content
Operating Systems AIX Error doing clogin into a wpar Post 303037376 by Neo on Wednesday 31st of July 2019 01:26:15 AM
Old 07-31-2019
You can also log into a system WPAR remotely by using a network-based login command, such as the rlogin command, the telnet command, or the rsh command.
 

10 More Discussions You Might Find Interesting

1. Infrastructure Monitoring

snmpget not working on AIX shared wpar

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)
Discussion started by: avazeer
0 Replies

2. UNIX for Dummies Questions & Answers

> 5 ")syntax error: operand expected (error token is " error

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)
Discussion started by: metal005
4 Replies

3. AIX

Unexpected Behaviour with WPAR

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)
Discussion started by: 03sep2011
0 Replies

4. AIX

Virtualization: WPAR vs LPAR

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)
Discussion started by: ppchu99
4 Replies

5. Shell Programming and Scripting

WPAR monitoring shell script suggestions needed

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

6. UNIX for Advanced & Expert Users

LPAR,DLPAR and WPAR

Can anyone please let know difference between LPAR/DLPAR/WPAR. and its purpose ??? (3 Replies)
Discussion started by: Pavithran
3 Replies

7. AIX

Versioned WPAR's

Hi everybody. is anyone using versioned WPAR's? Has anyone clustered them with PowerHA? Please share your experience. Regards, firefox (7 Replies)
Discussion started by: firefox111
7 Replies

8. AIX

Wpar network,i'm confused

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

9. AIX

How to Load a CICS IPC Kernel Extension in a versioned "rootvg" WPAR ?

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)
Discussion started by: The Doctor
4 Replies

10. AIX

No iscsi available in newly created AIX wpar

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
rancid-run(1)						      General Commands Manual						     rancid-run(1)

NAME
rancid-run - run rancid for each of the groups SYNOPSIS
rancid-run [-V] [-f rancid.conf] [-f rancid.conf] [-m mail_rcpt] [-r device_name] [group [group ...]] DESCRIPTION
rancid-run is a sh(1) script to run rancid(1) for a set of rancid group(s). rancid-run reads rancid.conf(5) to configure itself, then uses control_rancid(1) to run rancid(1) for each rancid group. The set of rancid groups can either be provided as command-line arguments or via the LIST_OF_GROUPS variable in rancid.conf(5), if the group argument is omitted. A lock file is maintained per-group to prevent simultaneous runs for a given group by rancid-run(1). The lock file will be named .<group>.run.lock and will be located in /var/lib/rancid. A log file is produced under $LOGDIR/logs for each rancid group processed. The file name will be <group>.YYYYMMDD.HHMMSS (year month day . hour minute second). rancid-run is normally used to run rancid from cron(8). For example: 0 * * * * /usr/local/rancid/bin/rancid-run The command-line options are as follows: -V Prints package name and version strings. -f rancid.conf Specify an alternate configuration file. -m mail_rcpt Specify the recipient of diff mail, which is normally rancid-<group>. The argument may be a single address, multiple comma separated addresses, or -m may be specified multiple times. -r device_name Run rancid for a single device, device_name. device_name should be name, as it appears in a group's router.db. The device must be marked "up". If a group is not specified on the command-line, rancid will be run against any group in which the device_name appears. The -r option alters the subject line of the diff mail. It will begin with <group name>/<device name> rather than just the group name alone. ENVIRONMENT
rancid-run utilizes the following environment variables from rancid.conf(5). BASEDIR Location of group directories, etc. This is set to the "localstatedir" by the configure script at installation time. LIST_OF_GROUPS List of rancid groups to collect. PATH Search path for utilities. TMPDIR Directory to hold temporary files. ERRORS
If rancid fails to run or collect a device's configuration, the particular group's log file (mentioned above) should be consulted. Any errors produced by the revision control system (CVS or Subversion) or any of the rancid scripts should be included there, whether they be a botched cvs tree, login authentication failure, rancid configuration error, etc. If the log file produces no clues, the next debugging step should be run the commands manually. For example, can the user who runs rancid login to the device with 'clogin hostname', and so on. FILES
$BASEDIR/etc/rancid.conf rancid-run configuration file. SEE ALSO
control_rancid(1), rancid.conf(5), router.db(5) 5 October 2006 rancid-run(1)
All times are GMT -4. The time now is 08:07 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy