Sponsored Content
Full Discussion: VIO SEA Adapters
Operating Systems AIX VIO SEA Adapters Post 302842727 by karlochacon on Friday 9th of August 2013 05:58:34 PM
Old 08-09-2013
Quote:
Originally Posted by ibmtech
Ok,
When you click "View/Modify Host Ethernet Adapters", you are seeing two HEA's, now check the one on the top and select properties,
under general tab check mark the option called "Allow virtual Ethernet bridging" click ok and do the same for the other HEA adapter.

Then go to "Virtual Ethernet Bridge" and you will see a adapter.

Basically you are bridging two HEA adapters for redundancy.
thanks a lot

you know I can continue bothering you with question since I pretty lost in this topic for instance you say SEA makes no sense when having one VIO but my previous partner configured SEA... weird.

any documentation to read and continue after this since now I have to understand more about networking in VIO
 

7 More Discussions You Might Find Interesting

1. AIX

20EE0008 : No adapters found Adapter, Riser, System Bd.

Hello, When I try to upgrade AIX from 5.1 to 5.3 I get this error message 20EE0008 : No adapters found Adapter, Riser, System Bd. Anyone know anything about it ? (1 Reply)
Discussion started by: filosophizer
1 Replies

2. AIX

vio server and vio client

Hi, I want to know wheather partition size for installation of vio client can be specified on vio server example If I am installing vio server on blade with 2*300gb hard disk,after that I want to create 2 vio client (AIX Operating system) wheather I can specify hard disk size while... (1 Reply)
Discussion started by: manoj.solaris
1 Replies

3. Red Hat

Designating Default Gateway for multiple networks/adapters

Hi I have 4 NIC's connected to my RHEL 5.3 server. Two on one subnet creating bond0, and two on a second subnet which create bond1. Both bonds are set to use DHCP to obtain IP addresses. Here is the config file for ifcfg-bond0: DHCP_HOSTNAME=rrnltshckvmx001 DEVICE=bond0 BOOTPROTO=dhcp... (2 Replies)
Discussion started by: Padow
2 Replies

4. AIX

SEA

Hi all, I set up the following configuration on my system: - An LPar with a virtual adapter, first one with a vlan id=703 and id port=13. - The first adapter have to connect to a VIOS in which i configured an SEA. So, the VA is set up on interface ent2, SEA on ent29 (by linking a... (0 Replies)
Discussion started by: idro
0 Replies

5. AIX

vio server ethernet to vio client ethernet(concepts confusing)

Hi In the vio server when I do # lsattr -El hdisk*, I get a PVID. The same PVID is also seen when I put the lspv command on the vio client partition. This way Im able to confirm the lun using the PVID. Similarly how does the vio client partition gets the virtual ethernet scsi client adapter... (1 Reply)
Discussion started by: newtoaixos
1 Replies

6. Windows & DOS: Issues & Discussions

Order of Adapters in Windows 7

I am trying to get my boss' ipad to print on our local printers, and rapidly coming to loathe the product. After several false starts I'm attempting to use the free WePrint application, running on a Windows machine, to "forward" our printers from it to the ipad over the local network. I've hit... (2 Replies)
Discussion started by: Corona688
2 Replies

7. AIX

VIOS - fibre adapters not seeing luns

Hi guys, I've been trying to tackle this issue for days and I'm stumped. Hopefully someone can give more light on what else I can do. I have a p7 series box, with dual VIOS and 10 lpars and everything was working fine until I had to move the box to another location in the data centre. Ensured... (16 Replies)
Discussion started by: aixkidbee
16 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 06:03 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy