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 FREEBSD
if_gre
GRE(4) BSD Kernel Interfaces Manual GRE(4)
NAME
gre -- encapsulating network device
SYNOPSIS
To compile the driver into the kernel, place the following line in the kernel configuration file:
device gre
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
if_gre_load="YES"
DESCRIPTION
The gre network interface pseudo device encapsulates datagrams into IP. These encapsulated datagrams are routed to a destination host, where
they are decapsulated and further routed to their final destination. The ``tunnel'' appears to the inner datagrams as one hop.
gre interfaces are dynamically created and destroyed with the ifconfig(8) create and destroy subcommands.
This driver corresponds to RFC 2784. Encapsulated datagrams are prepended an outer datagram and a GRE header. The GRE header specifies the
type of the encapsulated datagram and thus allows for tunneling other protocols than IP. GRE mode is also the default tunnel mode on Cisco
routers. gre also supports Cisco WCCP protocol, both version 1 and version 2.
The gre interfaces support a number of additional parameters to the ifconfig(8):
grekey Set the GRE key used for outgoing packets. A value of 0 disables the key option.
enable_csum Enables checksum calculation for outgoing packets.
enable_seq Enables use of sequence number field in the GRE header for outgoing packets.
EXAMPLES
192.168.1.* --- Router A -------tunnel-------- Router B --- 192.168.2.*
/
/
+------ the Internet ------+
Assuming router A has the (external) IP address A and the internal address 192.168.1.1, while router B has external address B and internal
address 192.168.2.1, the following commands will configure the tunnel:
On router A:
ifconfig greN create
ifconfig greN inet 192.168.1.1 192.168.2.1
ifconfig greN inet tunnel A B
route add -net 192.168.2 -netmask 255.255.255.0 192.168.2.1
On router B:
ifconfig greN create
ifconfig greN inet 192.168.2.1 192.168.1.1
ifconfig greN inet tunnel B A
route add -net 192.168.1 -netmask 255.255.255.0 192.168.1.1
NOTES
The MTU of gre interfaces is set to 1476 by default, to match the value used by Cisco routers. This may not be an optimal value, depending
on the link between the two tunnel endpoints. It can be adjusted via ifconfig(8).
For correct operation, the gre device needs a route to the decapsulating host that does not run over the tunnel, as this would be a loop.
The kernel must be set to forward datagrams by setting the net.inet.ip.forwarding sysctl(8) variable to non-zero.
SEE ALSO
gif(4), inet(4), ip(4), me(4), netintro(4), protocols(5), ifconfig(8), sysctl(8)
A description of GRE encapsulation can be found in RFC 2784 and RFC 2890.
AUTHORS
Andrey V. Elsukov <ae@FreeBSD.org>
Heiko W.Rupp <hwr@pilhuhn.de>
BUGS
The current implementation uses the key only for outgoing packets. Incoming packets with a different key or without a key will be treated as
if they would belong to this interface.
The sequence number field also used only for outgoing packets.
BSD
November 7, 2014 BSD