|
|
Sponsored Content
Operating Systems
AIX
VIOS Configuration Question
Post 302979316 by zaxxon on Friday 12th of August 2016 07:53:32 AM
08-12-2016
Hi gull04,
you're absolutely welcome. It also makes me recapitulate these very interessting things again
I don't want to be a nitpicker, but each VIOS is his own OS/LPAR. VIOS #2 will start counting devices from ent0 again.
You wrote you have 1 HMC - quite a bit dangerous if it fails. The LPARs and VIOS will not complain and run if the HMC is down, but you can't do anything on the Managed Systems for this time.
Also remember that each HMC has a dhcpd which provides internal IP-addresses for the service processors (SP). If you have more than one, they may not see each other. They are attached to a NIC per Managed System often very simple by a plain network hub.
I do not completely understand the layout, tbh.
Does the same colors mean, that they are in the same EtherChannel? For instance the yellow
VIOS #1: ent0, ent1
VIOS #2: ent16
Which of the 3 is the main, which the backup? Are 2 of them supposed to form up as an aggregation as main adapter so you have a higher bandwith?
In terms of hardware failure, it would not make sense to use 1 port as main and 1 as backup when they are on the same adapter.
This might work if only 1 port fails, but usually the whole adapter says goodbye and then there would be nothing left.
Not sure if intended but you cannot form an EtherChannel from adapters of VIOS #1 and VIOS #2. You can only create an EtherChannel with adapters from the same OS/LPAR/VIOS.
Later on the upper layers you can hand over traffic to a vNIC on another VIOS with the HASEA.
For clarity - an EtherChannel is good for 2 things:
If the whole EtherChannel fails, ie. the main and backup physical adapters in it, or the whole VIOS goes down - then the HASEA comes into action. It hands over the traffic to VIOS #2, that is hopefully still up and running
If you describe the requirements on hardware failure or possible aggregation of adapters to get a higher throughput and how many networks are needed, we can maybe assist designing.
You wrote you have 4 x 4port NICs per Managed System - the 2 other are not used on the plan yet - maybe we can do something to make it more failsafe with these.
Cheers
zaxxon
you're absolutely welcome. It also makes me recapitulate these very interessting things again
I don't want to be a nitpicker, but each VIOS is his own OS/LPAR. VIOS #2 will start counting devices from ent0 again.
You wrote you have 1 HMC - quite a bit dangerous if it fails. The LPARs and VIOS will not complain and run if the HMC is down, but you can't do anything on the Managed Systems for this time.
Also remember that each HMC has a dhcpd which provides internal IP-addresses for the service processors (SP). If you have more than one, they may not see each other. They are attached to a NIC per Managed System often very simple by a plain network hub.
I do not completely understand the layout, tbh.
Does the same colors mean, that they are in the same EtherChannel? For instance the yellow
VIOS #1: ent0, ent1
VIOS #2: ent16
Which of the 3 is the main, which the backup? Are 2 of them supposed to form up as an aggregation as main adapter so you have a higher bandwith?
In terms of hardware failure, it would not make sense to use 1 port as main and 1 as backup when they are on the same adapter.
This might work if only 1 port fails, but usually the whole adapter says goodbye and then there would be nothing left.
Not sure if intended but you cannot form an EtherChannel from adapters of VIOS #1 and VIOS #2. You can only create an EtherChannel with adapters from the same OS/LPAR/VIOS.
Later on the upper layers you can hand over traffic to a vNIC on another VIOS with the HASEA.
For clarity - an EtherChannel is good for 2 things:
- To have a backup NIC available when one of the physical NICs fail.
- To be able to get a higher throughput by aggregating physical adapters as "main" adapter in an EtherChannel. The backup adapter can always be only 1 physical NIC.
If the whole EtherChannel fails, ie. the main and backup physical adapters in it, or the whole VIOS goes down - then the HASEA comes into action. It hands over the traffic to VIOS #2, that is hopefully still up and running
If you describe the requirements on hardware failure or possible aggregation of adapters to get a higher throughput and how many networks are needed, we can maybe assist designing.
You wrote you have 4 x 4port NICs per Managed System - the 2 other are not used on the plan yet - maybe we can do something to make it more failsafe with these.
Cheers
zaxxon
Last edited by zaxxon; 08-12-2016 at 09:45 AM..
|
|
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi -
I am fairly new with unix. I have a unix box, installed with Solaris 2.8. I can get the box hooked up to the internet, not using DHCP but static IP address behind a Linksys firewall. However, I cannot telnet to the unix box or from within the unix box. If I telnet from a windows... (8 Replies)
Discussion started by: trigeek8888
8 Replies
2. Linux
When I telnet (ssh) over to my Fedora system, I find the colors horrible. For instance, regular files are white text, which is fine, but directories show up as dark blue which is virtually invisible against the black background). Additionally, when using vi, I find the colors great doing perl... (3 Replies)
Discussion started by: ripley
3 Replies
3. Debian
Is there a way to configure the gnome file manager to open each directory in the same window instead of opening a new one? (Debian 5.0.0) (5 Replies)
Discussion started by: snorkack59
5 Replies
4. UNIX for Dummies Questions & Answers
In sshd_config it is written:
# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to specify options with their default value where
# possible, but leave them commented. Uncommented options change a
# default value.
So does that mean for the following:
... (2 Replies)
Discussion started by: mojoman
2 Replies
5. AIX
Can anybody provide me with usefull links to get knowledge how VIOS works and how to configure Lpars on it? I am tired and feel lazy to search through IBM redbooks :-) .. so pls help me :p (3 Replies)
Discussion started by: wwwzviadi
3 Replies
6. Debian
Hi ,
when i configure my server with a fixed ip address in dhcpd.conf as below
subnet 172.21.151.0 netmask 255.255.255.0 {
range 172.21.151.66 172.21.151.66;
}
host switch {
hardware ethernet 00:05:30:02:DB:31;
fixed-address 172.21.151.66;
}
when i start dhcpd server , it... (2 Replies)
Discussion started by: Gopi Krishna P
2 Replies
7. UNIX for Advanced & Expert Users
Solaris 10 on an X86 box - Config runs fine has a couple of items in log (really long log file).
When I try make I get
make: Fatal error in reader: Make.inc, line 84: Unexpected end of line seen
line 84 is
LIBRADIUS_WITH_OPENSSL = 1
any ideas on what to try? (1 Reply)
Discussion started by: NeedLotsofHelp
1 Replies
8. AIX
Hello,
Lets say for simplicity that I do not use any vlan config inside my server - one lpar group use hea physical port1, another group hea physical port2. Physical port1 configured as vlan1 on external switch, physical port2 as vlan2.
What is the common practice - should I isolate my vios... (0 Replies)
Discussion started by: vilius
0 Replies
9. AIX
Hi,
$ ioslevel
2.2.4.10
I always get these errors when I perform any action using the web interface of IVM / VIOS
Shutdown Partitions Help
You have chosen to shutdown the following partitions. The recommended shutdown method is to use the client operating systems shutdown... (1 Reply)
Discussion started by: filosophizer
1 Replies
10. Solaris
Hi,
I have two physical interface connected to solaris box.
1. e1000g1
2. e1000g2
I have added these interfaced under a same IPMP group "IPMP1"
After that I have configured a test address for e1000g1 like below
ifconfig e1000g1 addif <ip-address> netmask + broadcast + -failover... (1 Reply)
Discussion started by: praveensharma21
1 Replies
LEARN ABOUT DEBIAN
bt-adapter
bt-adapter(1) bluez-tools bt-adapter(1) NAME
bt-adapter - a bluetooth adapter manager SYNOPSIS
bt-adapter [OPTION...] Help Options: -h, --help Application Options: -l, --list -a, --adapter=<name|mac> -i, --info -d, --discover --set <property> <value> DESCRIPTION
This utility is used to manage Bluetooth adapters. You can list all available adapters, show information about adapter, change adapter properties or discover remote devices. OPTIONS
-h, --help Show help -l, --list List all available adapters -a, --adapter <name|mac> Specify adapter to use by his Name or MAC address (if this option does not defined - default adapter used) -i, --info Show information about adapter (returns all properties) -d, --discover Discover remote devices (with remote device name resolving) --set <property> <value> Change adapter properties (see ADAPTER PROPERTIES section for list of available properties) ADAPTER PROPERTIES
string Address [ro] The Bluetooth adapter address (MAC). string Name [rw] The Bluetooth adapter friendly name. uint32 Class [ro] The Bluetooth class of device. boolean Powered [rw] Switch an adapter on or off. This will also set the appropiate connectable state. boolean Discoverable [rw] Switch an adapter to discoverable or non-discoverable to either make it visible or hide it. If the DiscoverableTimeout is set to a non-zero value then the system will set this value back to false after the timer expired. In case the adapter is switched off, setting this value will fail. boolean Pairable [rw] Switch an adapter to pairable or non-pairable. Note that this property only affects incoming pairing requests. uint32 PaireableTimeout [rw] The pairable timeout in seconds. A value of zero means that the timeout is disabled and it will stay in pareable mode forever. uint32 DiscoverableTimeout [rw] The discoverable timeout in seconds. A value of zero means that the timeout is disabled and it will stay in discoverable/limited mode forever. The default value for the discoverable timeout should be 180 seconds (3 minutes). boolean Discovering [ro] Indicates that a device discovery procedure is active. list UUIDs [ro] List of 128-bit UUIDs that represents the available local services. AUTHOR
Alexander Orlenko <zxteam@gmail.com>. SEE ALSO
bt-agent(1) bt-audio(1) bt-device(1) bt-input(1) bt-monitor(1) bt-network(1) bt-serial(1) 2010-08-16 bt-adapter(1)