lp-hea are the native adapters attached to the Balde itself (they are HEA, and each HEA has 4 Logical ports). We use them, say for the first installation or for servers where you don't want redundancy, they are SPOF (single point of failure) adapters.
Virtual adapters (l-lan), are created at VIOS/client level, we create them at VIO level to define the priority of VIOS and add multiple vlans to it. At client level we create those for it to communicate to outer world.
Physical cable are the actual cables from which the traffic goes in and out of the Blade, without the physical port your virtual adapter at VIO are of no use.
Now coming to SEA (shared ethernet adapter), to create a SEA you need a physical adapter, a virtual adapter (actually two, one with trunking priority, vlans (if you want) and other is called control channel adapter, ctrl chan adapter is the heart beat of SEA). Then the VIO create a new adapter called SEA, remember that SEA will not be visible from HMC, you can only see it when you are in VIO.
If you have SEA, it will be redundant and you can avoid SPOF.
thanks a lot
so for what I understood I have to use these to create SEA
is it too much to ask who to do it? is by command or using smitty
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)
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)
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)
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)
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)
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)
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
LEARN ABOUT FREEBSD
if_ix
IXGBE(4) BSD Kernel Interfaces Manual IXGBE(4)NAME
ixgbe -- Intel(R) 10Gb Ethernet driver for the FreeBSD operating system
SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file:
device ixgbe
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
if_ixgbe_load="YES"
DESCRIPTION
The ixgbe driver provides support for PCI 10Gb Ethernet adapters based on the Intel 82598EB Intel(R) Network Connections. The driver sup-
ports Jumbo Frames, MSIX, TSO, and RSS.
For questions related to hardware requirements, refer to the documentation supplied with your Intel 10GbE adapter. All hardware requirements
listed apply to use with FreeBSD.
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 maximum MTU size for Jumbo Frames is 16114.
This driver version supports VLANs. For information on enabling VLANs, see ifconfig(8).
HARDWARE
The ixgbe driver supports the following cards:
o Intel(R) 10 Gigabit XF SR/AF Dual Port Server Adapter
o Intel(R) 10 Gigabit XF SR/LR Server Adapter
o Intel(R) 82598EB 10 Gigabit AF Network Connection
o Intel(R) 82598EB 10 Gigabit AT CX4 Network Connection
DIAGNOSTICS
ixgbe%d: Unable to allocate bus resource: memory A fatal initialization error has occurred.
ixgbe%d: Unable to allocate bus resource: interrupt A fatal initialization error has occurred.
ixgbe%d: watchdog timeout -- resetting The device has stopped responding to the network, or there is a problem with the network connection
(cable).
SUPPORT
For general information and support, go to the Intel support website at: http://support.intel.com.
If an issue is identified with the released source code on the supported kernel with a supported adapter, email the specific information
related to the issue to <freebsd@intel.com>.
SEE ALSO altq(4), arp(4), netintro(4), ng_ether(4), polling(4), vlan(4), ifconfig(8)HISTORY
The ixgbe device driver first appeared in FreeBSD 7.0.
AUTHORS
The ixgbe driver was written by Intel Corporation <freebsd@intel.com>.
BSD December 19, 2010 BSD