Sponsored Content
Full Discussion: VIOS Configuration Question
Operating Systems AIX VIOS Configuration Question Post 302979316 by zaxxon on Friday 12th of August 2016 07:53:32 AM
Old 08-12-2016
Hi gull04,

you're absolutely welcome. It also makes me recapitulate these very interessting things again Smilie

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 Smilie

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

Configuration Newbie Question

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

xterm font colors - configuration question?

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

gnome file manager configuration question

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

OpenSSH Configuration Question

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

VIOS

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

Question on the dhcp-server configuration for a fixed IP address.

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

Free Radius Configuration question

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

VIOS IP address - separate vlan for vios servers ?

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

VIOS 2.2.4.10 - Errors

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

IPMP Configuration Question/Problem

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
CS(4)							 BSD/i386 Kernel Interfaces Manual						     CS(4)

NAME
cs -- Ethernet device driver SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file: device cs Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_cs_load="YES" In /boot/device.hints: hint.cs.0.at="isa" hint.cs.0.port="0x300" hint.cs.0.irq="10" hint.cs.0.maddr="0xd000" DESCRIPTION
The cs driver provides support for ISA Ethernet adapters based on the Crystal Semiconductor CS8900 and CS8920 NICs. These devices are used on the IBM EtherJet ISA adapters and in many embedded applications where the high integration, small size and low cost of the CS89x0 family compensate for their drawbacks. The cs driver will obtain configuration parameters either from /boot/device.hints or from the card. At least the I/O port number must be specified. Other parameters specified in /boot/device.hints will be used if present; the card may be soft-configured so these may be any valid value. Adapters based on the CS8920 normally offer PnP configuration and the driver will detect the IBM EtherJet and the CSC6040 adapters automatically. Note that the CS8900 is limited to 4 IRQ values; these are normally implemented as 5, 10, 11 and 12. The CS8920 has no such limitation. Memory-mapped and DMA operation are not supported at this time. In addition to the ISA devices, the PC Card devices based on the CS889x0 family are also supported. The IBM EtherJet PCMCIA Card is the only known device based on this chip. The PC Card support does not need the above specific ISA hints to work. The PC Card support may not work for 10base2 (thinnet) connections and may bogusly claim to support 10base5 (there are no known cards that have an AUI necessary for 10base5 support on their dongles). DIAGNOSTICS
cs%d: full/half duplex negotiation timeout The attempt to negotiate duplex settings with the hub timed out. This may indicate a cabling problem or a faulty or incompatible hub. cs%d: failed to enable <media> The CS89x0 failed to select the nominated media, either because it is not present or not operating correctly. cs%d: No EEPROM, assuming defaults The CS89x0 does not have an EEPROM, or the EEPROM is hopelessly damaged. Operation will only be success- ful if the configuration entry lists suitable values for the adapter. cs%d: Invalid irq The IRQ specified in the configuration entry is not valid for the adapter. cs%d: Could not allocate memory for NIC There is a critical memory shortage. The adapter will not function. cs%d: Adapter has no media The adapter is not configured for a specific media type. The media type will have to be manually set. This is a %s, but LDN %d is disabled The PnP probe code found a recognised adapter, but the adapter is disabled. failed to read pnp parms A PnP adapter was found, but configuration parameters for it could not be read. failed to pnp card parameters The parameters obtained via PnP were not accepted by the driver. The adapter may not function. CAVEATS
The CS89x0 family of adapters have a very small RAM buffer (4K). This may cause problems with extremely high network loads or bursty network traffic. In particular, NFS operations should be limited to 1k read/write transactions in order to avoid overruns. SEE ALSO
arp(4), netintro(4), ng_ether(4), ifconfig(8) AUTHORS
The cs device driver was written by Maxim Bolotin and Oleg Sharoiko. This manpage was written by Michael Smith. BSD
July 16, 2005 BSD
All times are GMT -4. The time now is 01:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy