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 OSX
localemanager
localemanager(8) BSD System Manager's Manual localemanager(8)NAME
localemanager -- Configure OpenDirectory Server Locales
SYNOPSIS
localemanager operation [-l localename] [-subnet 1.2.3.4/5] [-server servername] [-i IP address]
DESCRIPTION
localemanager creates, destroys, and edits OpenDirectory Server Locale information. Locales are collections of OpenDirectory servers to
assist clients in locating the nearest OpenDirectory Server.
To use OpenDirectory Server Locales, simply create a locale on an OD server with the createLocale operation. Then add servers and subnets to
the locale. All localemanager operations are performed on the local OpenDirectory node.
The first time a locale is created, a DefaultLocale will automatically be created as well. The DefaultLocale will be used for any clients
that don't match a subnet in any other locale.
Before a locale can be configured, the server must already be an OpenDirectory server.
Locales can be defined on each of the OD servers or on a single OD server in the group of OD master/replicas. For the latter, the locale
information will get replicated to all of the other servers but locales will need to be "enabled" on the other servers by running the command
localemanager enableLocales.
Commands:
help Displays the commands and options.
createLocale Creates a new locale on the local OD server. This command requires the -l option.
deleteLocale Deletes a locale from the local OD server. This command requires the -l option.
showLocale Displays the current locale(s). The -l option can be used to display a specific locale. If -l is not specified, all locales
are displayed.
enableLocales
Enables the use of locales on an OD server. This command is automatically run the first time any localemanager command is run
on an OD server. Therefore this command only needs to be run if no other localemanager commands have been (or will be) run on
this server.
addSubnet Adds a new subnet to the specified locale. This command requires the -l -subnet options.
removeSubnet Removes a subnet from the specified locale. This command requires -l -subnet options.
addServer Adds a server to the specified locale. This command requires the -l -server options. If the -i option is specified, that IP
address will be used by locale clients. This may be useful for multi-homed servers to restrict locale clients to a specific
network interface. If the -i option is not specified the IP address(es) will be looked up.
removeServer Removes a server from the specified locale. This command requires -l -server options. If the -i option is specified, only
that IP address will be removed from the locale. If the -i option is no specified, all of the server's IP addresses will be
removed from the locale.
Options:
-l locale Locale name.
-subnet 192.168.0.0/16
Subnet specified in CIDR notation.
-server server.example.com
Server fully-qualified domain name.
-i 192.168.1.1
Use this IP address for the server. Typically used to limit locale clients to a specific interface on a multi-homed server.
FILES
/var/log/localemanager.log localemanager log file.
SEE ALSO slapconfig(8)HISTORY
First introduced in Mac OS X 10.7
Darwin June 2, 2019 Darwin