Sponsored Content
Full Discussion: VIO SEA Adapters
Operating Systems AIX VIO SEA Adapters Post 302842369 by karlochacon on Friday 9th of August 2013 02:46:59 AM
Old 08-09-2013
VIO SEA Adapters

hi guys
BTW pretty new to VIO

I inherited 2 I BM Power Server - blades PS701 - One is already configured using en8

Code:
# lsdev -Cc adapter | grep ent
ent0    Available       Logical Host Ethernet Port (lp-hea)
ent1    Available       Logical Host Ethernet Port (lp-hea)
ent2    Available 04-20 Gigabit Ethernet-SX PCI-X Adapter (14106703)
ent3    Available 04-21 Gigabit Ethernet-SX PCI-X Adapter (14106703)
ent4    Available       Virtual I/O Ethernet Adapter (l-lan)
ent5    Available       Virtual I/O Ethernet Adapter (l-lan)
ent6    Available       Virtual I/O Ethernet Adapter (l-lan)
ent7    Available       Virtual I/O Ethernet Adapter (l-lan)
ent8    Available       Shared Ethernet Adapter
ent9    Available       Shared Ethernet Adapter
# ifconfig -a
en8: flags=1e080863,180<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACTIVE),CHAIN>
        inet 10.116.125.xx netmask 0xffffff00 broadcast 10.6.25.255

I am trying to understand this topic about:
Logical Host Ethernet Port (lp-hea)
Gigabit Ethernet-SX PCI-X Adapter
Virtual I/O Ethernet Adapter (l-lan)

I really don't why too many adapters when my server only has 2 physical NICs

Well now I need to configure this new PS701 I configured an ip to en0 and is working but seeing configuration in the other PS701 I don't have any
Shared Ethernet Adapter

Code:
lsdev -Cc adapter | grep ent
ent0    Available       Logical Host Ethernet Port (lp-hea)
ent1    Available       Logical Host Ethernet Port (lp-hea)
ent2    Available 04-20 Gigabit Ethernet-SX PCI-X Adapter (14106703)
ent3    Available 04-21 Gigabit Ethernet-SX PCI-X Adapter (14106703)
ent4    Available       Virtual I/O Ethernet Adapter (l-lan)
ent5    Available       Virtual I/O Ethernet Adapter (l-lan)
ent6    Available       Virtual I/O Ethernet Adapter (l-lan)
ent7    Available       Virtual I/O Ethernet Adapter (l-lan)

So 3 questions:

1. Why too many virtual adapters l-lan and lp-hea ?
2. How do I configure these SEA?
3. Just creating SEA I will provide High availability to my PS701? I mean when adapter 1 fails adapter 2 will take over and LPARs will continue having connectivity?

thanks a lot
 

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
NFE(4)							   BSD Kernel Interfaces Manual 						    NFE(4)

NAME
nfe -- NVIDIA nForce MCP Ethernet driver SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file: device miibus device nfe Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_nfe_load="YES" DESCRIPTION
The nfe driver supports PCI Ethernet adapters based on the NVIDIA nForce Media and Communications Processors (MCP), such as the nForce, nForce 2, nForce 3, CK804, MCP04, MCP51, MCP55, MCP61, MCP65, MCP67, MCP73, MCP77 and MCP79 Ethernet controller chips. Supported features include (hardware support provided): o Receive/Transmit IP/TCP/UDP checksum offload o Hardware VLAN tag insertion/stripping o TCP segmentation offload (TSO) o MSI/MSI-X o Jumbo Frames Support for Jumbo Frames is provided via the interface MTU setting. Selecting an MTU larger than 1500 bytes with the ifconfig(8) utility configures the adapter to receive and transmit Jumbo Frames. The nfe driver supports the following media types: autoselect Enable autoselection of the media type and options. 10baseT/UTP Set 10Mbps operation. 100baseTX Set 100Mbps (Fast Ethernet) operation. 1000baseT Set 1000Mbps (Gigabit Ethernet) operation (recent models only). The nfe driver supports the following media options: half-duplex Force half duplex operation. full-duplex Force full duplex operation. For more information on configuring this device, see ifconfig(8). HARDWARE
The nfe driver supports the following NVIDIA MCP onboard adapters: o NVIDIA nForce MCP Networking Adapter o NVIDIA nForce MCP04 Networking Adapter o NVIDIA nForce 430 MCP12 Networking Adapter o NVIDIA nForce 430 MCP13 Networking Adapter o NVIDIA nForce MCP51 Networking Adapter o NVIDIA nForce MCP55 Networking Adapter o NVIDIA nForce MCP61 Networking Adapter o NVIDIA nForce MCP65 Networking Adapter o NVIDIA nForce MCP67 Networking Adapter o NVIDIA nForce MCP73 Networking Adapter o NVIDIA nForce MCP77 Networking Adapter o NVIDIA nForce MCP79 Networking Adapter o NVIDIA nForce2 MCP2 Networking Adapter o NVIDIA nForce2 400 MCP4 Networking Adapter o NVIDIA nForce2 400 MCP5 Networking Adapter o NVIDIA nForce3 MCP3 Networking Adapter o NVIDIA nForce3 250 MCP6 Networking Adapter o NVIDIA nForce3 MCP7 Networking Adapter o NVIDIA nForce4 CK804 MCP8 Networking Adapter o NVIDIA nForce4 CK804 MCP9 Networking Adapter LOADER TUNABLES
Tunables can be set at the loader(8) prompt before booting the kernel or stored in loader.conf(5). hw.nfe.msi_disable Whether or not MSI support is enabled in the driver. The default value is 0. hw.nfe.msix_disable Whether or not MSI-X support is enabled in the driver. The default value is 0. SYSCTL VARIABLES
The following sysctl(8) variables can be used to modify or monitor nfe behavior. dev.nfe.%d.process_limit Maximum number of Rx events to be processed in the event loop before rescheduling a taskqueue. The accepted range is 50 to 255, the default value is 192. The interface does not need to be brought down and up again before a change takes effect. SEE ALSO
altq(4), arp(4), intro(4), miibus(4), netintro(4), pci(4), polling(4), rgephy(4), sysctl(8), ifconfig(8) HISTORY
The nfe device driver first appeared in OpenBSD 3.9, and then in FreeBSD 7.0. AUTHORS
The nfe driver was written by Jonathan Gray <jsg@openbsd.org> and Damien Bergamini <damien@openbsd.org>. The nfe driver was ported to FreeBSD by Shigeaki Tagashira <shigeaki@se.hiroshima-u.ac.jp>. BSD
January 15, 2011 BSD
All times are GMT -4. The time now is 04:38 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy