03-14-2014
Maybe I don't understand network settings completely:
In HMC's network settings currently there are two adapters with next :
-eth0 (assuming direct connection to FSP) , Private, Autodetection, enabled DHCP server (192.168.128.2-192.168.255.254), greyed out settings for IPv4 (192.168.128.1)
-eth1 (assuming management port), Open, Autodetection, DHCP disabled, IPv4 192.168.1.121, 255.255.255.0.
Routing settings: Default Gateway 192.168.1.1 for eth1
No tagging involved.
VIOS and LPAR;s are on same subnet as eth1.
Now I figured that default gateway has to be the same one that of VIOS and LPAR's are using in order for HMC to connect to them via console.
You are right that IP settings for eth1 does not matter but than I can not reach remotely HMC unless I change route, which in turn makes problem for HMC accessing LPAR's via console.
Now I tried attaching cable to eth2 and connecting it to new subnet, added static NET route 192.168.1.0, 192.168.50.1, 255.255.255.0 for eth2 and everything works fine (192.168.50.1 is new subnet gateway). I can remotely access HMC and still HMC can access LPAR's via console.
So my question now is if you missconfigure IP settings on VIOS how can I access missconfigured system or better question how you can access VIOS that does not have network interface? e.g. in KVM I do not care about network settings at all as long as I have physical access to hypervisor (I can access guests via console).
Thanks
10 More Discussions You Might Find Interesting
1. AIX
Hello guys,
It would be so nice of you if someone can provide me with these informations.
1) My SAN group assigned 51G of LUN space to the VIO server.I ran cfgdev to discover the newly added LUN. Unfortunately most of the disks that are in VIO server is 51G. How would I know which is the newly... (3 Replies)
Discussion started by: solaix14
3 Replies
2. AIX
I created a profile in HMC for a new LPAR and activated it but not yet installed AIX.
Is there a step to make this new LPAR available as vhostX from the VIO server after creating and activating an HMC profile?
I already shared the CD-ROM device from the HMC profile.
Thanks.
-... (1 Reply)
Discussion started by: learner1
1 Replies
3. AIX
Hello,
I have created mapping of 2 virtual adapters for Lpars using following command:
mkvdev -vdev ipanalyzerlv1 -vadapter vhost11
mkvdev -vdev ipanalyzerlv -vadapter vhost13
The above two commands were succesfull
but when I want to map the third virtual device to the same Lpar than... (3 Replies)
Discussion started by: Vit0_Corleone
3 Replies
4. AIX
Hi All,
Besides the licenses on VIO and LPAR. What's the main difference with the two? I have installed VIO, my manager told me so, because it's like a free hypervisor but I never installed LPAR before. How do you install it? And if you can give more info on the two, that would be great.
... (5 Replies)
Discussion started by: itik
5 Replies
5. AIX
Hi All,
i would like to know if it's possible to know all the IP Addresses of all LPAR's interfaces from HMC (without connect into LPAR).
And if i can know also the "Application" hostname of LPAR from HMC.
Thanks in advance.
Bye
Mario (2 Replies)
Discussion started by: Zio Bill
2 Replies
6. AIX
Hi guys,
does anyone know how to get a list of the LPAR running on VIOS?
Thanks! (5 Replies)
Discussion started by: cecco16
5 Replies
7. AIX
I am trying to install AIX 5.3 on one of the LPARs through VIOS but I get this error 0518
Reference Code Selection
0518 (Time stamp: 12/18/12 12:10:20 AM UTC)
Starting kernel (Time stamp: 12/18/12 12:10:15 AM UTC)
AIX is starting. (Time stamp: 12/18/12 12:10:15 AM... (10 Replies)
Discussion started by: filosophizer
10 Replies
8. AIX
Does anyone know of a command that can be run on the lpar to show the name of the lpars managing HMC?
We have a large environment and records a little old on which HMC manages which lpars....if i could login to an lpar and just issue a command to show me its managing hmc that would be great. (2 Replies)
Discussion started by: Foiled
2 Replies
9. UNIX for Beginners Questions & Answers
We want to integrate powervm by using openstack with hmc.
Now we encounter problem with the console, we can open the terminal within hmc, and I think hmc using tech java applet.
sample applet code like
<applet codebase="https://172.16.28.174/hmc/"... (0 Replies)
Discussion started by: eagle
0 Replies
10. AIX
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
fence_lpar
FENCE_AGENT(8) System Manager's Manual FENCE_AGENT(8)
NAME
fence_lpar - Fence agent for IBM LPAR
DESCRIPTION
fence_lpar accepts options on the command line as well as from stdin. Fenced sends parameters through stdin when it execs the agent.
fence_lpar can be run by itself with command line options. This is useful for testing and for turning outlets on or off from scripts.
PARAMETERS
-o, --action=<action>
Fencing Action (Default Value: reboot)
-a, --ip=<ip>
IP Address or Hostname This parameter is always required.
-l, --username=<name>
Login Name This parameter is always required.
-p, --password=<password>
Login password or passphrase
-S, --password-script=<script>
Script to retrieve password
-x, --ssh
SSH connection (Default Value: 1)
-k, --identity-file=<filename>
Identity file for ssh
-n <id> Name of the partition
Partition name
-s <id> Name of the managed system
Managed system name
-H, --hmc-version=<version>
Force HMC version to use (3 or 4) (Default Value: 4)
-c, --command-prompt=<prompt>
Force command prompt (Default Value: [':~>', ']$', '$ '])
-4, --inet4-only
Forces agent to use IPv4 addresses only
-6, --inet6-only
Forces agent to use IPv6 addresses only
-u, --ipport=<port>
TCP port to use for connection with device
-v, --verbose
Verbose mode
-D, --debug-file=<debugfile>
Write debug information to given file
-V, --version
Display version information and exit
-h, --help
Display help and exit
-C, --separator=<char>
Separator for CSV created by operation list (Default Value: ,)
--power-timeout
Test X seconds for status change after ON/OFF (Default Value: 20)
--shell-timeout
Wait X seconds for cmd prompt after issuing command (Default Value: 3)
--login-timeout
Wait X seconds for cmd prompt after login (Default Value: 15)
--power-wait
Wait X seconds after issuing ON/OFF (Default Value: 0)
--delay
Wait X seconds before fencing is started (Default Value: 0)
--retry-on
Count of attempts to retry power on (Default Value: 1)
ACTIONS
on Power on machine.
off Power off machine.
reboot Reboot machine.
status This returns the status of the plug/virtual machine.
list List available plugs with aliases/virtual machines if there is support for more then one device. Returns N/A otherwise.
monitor
Check if fencing device is running. List available plugs/virtual machines or get status of machine (if it does not support more).
metadata
The operational behavior of this is not known.
STDIN PARAMETERS
action Fencing Action (Default Value: reboot)
ipaddr IP Address or Hostname This parameter is always required.
login Login Name This parameter is always required.
passwd Login password or passphrase
passwd_script
Script to retrieve password
secure SSH connection (Default Value: 1)
identity_file
Identity file for ssh
partition
Partition name
managed
Managed system name
hmc_version
Force HMC version to use (3 or 4) (Default Value: 4)
cmd_prompt
Force command prompt (Default Value: [':~>', ']$', '$ '])
inet4_only
Forces agent to use IPv4 addresses only
inet6_only
Forces agent to use IPv6 addresses only
ipport TCP port to use for connection with device
verbose
Verbose mode
debug Write debug information to given file
version
Display version information and exit
help Display help and exit
separator
Separator for CSV created by operation list (Default Value: ,)
power_timeout
Test X seconds for status change after ON/OFF (Default Value: 20)
shell_timeout
Wait X seconds for cmd prompt after issuing command (Default Value: 3)
login_timeout
Wait X seconds for cmd prompt after login (Default Value: 15)
power_wait
Wait X seconds after issuing ON/OFF (Default Value: 0)
delay Wait X seconds before fencing is started (Default Value: 0)
retry_on
Count of attempts to retry power on (Default Value: 1)
fence_lpar (Fence Agent) 2009-10-20 FENCE_AGENT(8)