I understand that private network is used to manage FSP's and let's forget remote access to HMC (I will work directly on HMC hardware in server room). Question is why I cannot access VIOS via HMC console if I change default gateway for eth1 in Network settings? (this automatically starts another question what would happen if I put wrong network parameters in VIOS, how am I suppose to access it?).
A well configuration of eth2 (reverted everything back) does not guarantee that I will have access to VIOS if I missconfigure it (according to the problem on eth1).
What I would like to see is that I can access VIOS from HMC (hardware side) via console no matter of eth1 settings, or default gateway. Currently this is not case if I change dafault gateway.
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)
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)
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)
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)
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)
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)
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)
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)
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
dhcp-helper
DHCP-HELPER(8) System Manager's Manual DHCP-HELPER(8)NAME
dhcp-helper - A DHCP/BOOTP relay agent.
SYNOPSIS
dhcp-helper [OPTION]...
DESCRIPTION
dhcp-helper is a DHCP and BOOTP relay agent. It listens for DHCP and BOOTP broadcasts on directly connected subnets and relays them to DHCP
or BOOTP servers elsewhere. It also relays replies from the remote servers back to partially configured hosts. Once hosts are fully config-
ured they can communicate directly with their servers and no longer need the services of a relay.
OPTIONS
The only required option is at least one DHCP server to relay to. The simplest way to configure dhcp-helper on a router is just to give the
interface to the network containing the DHCP server with a -b option. All the other interfaces present on the machine will then accept DHCP
requests. On a machine which does not have an interface on the network containing the DHCP server, use a -s option instead.
-s <server>
Specify a DHCP or BOOTP server to relay to. The server may be given as a machine name or dotted-quad IP address. More than one
server may be specified.
-b <interface>
Relay to a DHCP or BOOTP server using broadcast via <interface>. This eliminates the need to give a server address. <interface> is
automatically added to the list of interfaces which will not receive DHCP requests.
-i <interface>
Specify which local interfaces to listen on for DHCP/BOOTP broadcasts. If no -i flags are given all interfaces are used except those
specified by -e flags and those specified by -b flags.
-e <interface>
Specify which local interfaces to exclude.
-p Use alternative ports (1067/1068) for the DHCP client and server.
-v Report the software release version and copyright information.
-d Debug mode, do not change UID, write a pid-file or go into the background.
-r <file>
Specify an alternate path for dhcp-helper to record its process-id in. Normally /var/run/dhcp-helper.pid.
-u <username>
Specify the userid to which dhcp-helper will change after startup. The daemon must normally be started as root, but it will drop
root priviledges after startup by changing id to another user. Normally this user is "nobody" but that can be over-ridden with this
switch.
NOTES
Dhcp-helper requires a 2.2 or later Linux kernel. The "Linux packet filter" and "packet socket" facilities are not required, which is the
chief advantage of this software over the ISC DHCP relay daemon.
AUTHOR
This manual page was written by Simon Kelley <simon@thekelleys.org.uk>.
DHCP-HELPER(8)