11-16-2011
hi,
virtual ethernet adapter is mapped to the vio server through the VLAN which u have configured on the sea.
u have to map the virtual scsi adapter by mapping the id's on both of the VIOS and the LPAR.
10 More Discussions You Might Find Interesting
1. AIX
Hi,
I define 2 new LV on the vio server and run a cfgmgr on the partition and see my 2 new hdisk (hdisk6 and hdisk7).
I extend my vg vg000 (on the partition) and add the 2 hdisks.
I had a filesystem on the vg000 and when I added the disk I would like to increase the filesystem. But I cannot do a... (0 Replies)
Discussion started by: touny
0 Replies
2. AIX
Hello,
Searched in all IBM Redbooks and on the internet and couldn't find anything about the new feature of POWER 6 which Virtual Fibre ( Fiber ) channel adapter.
It is similar to virtual scsi adapter.
In my client partition I created the virtual Fibre Adapter mapped it with the VIO... (1 Reply)
Discussion started by: filosophizer
1 Replies
3. Programming
Hi,
I found on linuxgazette.net/93/bhaskaran.html page very useful sample of virtual driver (not connected to real hardware).
I try to compile it with no effect.
So:
I got fresh Ubuntu 9.10 (kernel 2.6.31-14)
My source is saved in networkAdapter.c file in /usr/src/myModules directory.
I... (21 Replies)
Discussion started by: Chrisdot
21 Replies
4. AIX
I just wondering if there are ways to open multiple virtual terminal to a single LPAR.
After I have use putty to login to the VIOS. I will use mkvt -id <LPAR id> to open console but if my friend want to open 2 second one, it will say, VT already connected.
IS there a way to work this around ? ... (1 Reply)
Discussion started by: wingcross
1 Replies
5. AIX
All
I am trying allocate an IVE to an LPAR (not a VIO) running AIX 7.1. I am getting the error:
HSCL068A
Explanation
Logical port can not be assigned to Logical Partition because this Logical Partition is not the promiscuous LPAR for the physical port.
Has anyone encountered this... (1 Reply)
Discussion started by: johnf
1 Replies
6. IP Networking
Hi,
I just want to know whether two MAC address can exist in a adapter..
I mean one there will be mandatory one
And another as user defined one..
Any replies will be more helpful..
Please help..
:wall: (0 Replies)
Discussion started by: Priya Amaresh
0 Replies
7. AIX
Hello,
VIOS 2.2.1.4 using IVM.
I'm trying to extend a virtual disk assigned to a running lpar so that I can expand the lpar's datavg and grow some filesystems for the user.
Storage admin expanded the lun and new size was reflected in VIO right away. I then needed the storage pool to... (2 Replies)
Discussion started by: j_aix
2 Replies
8. AIX
hi all i have entered Aix environment 4 months had experienced in linux
what i am facing is i am unable to do sort of RnD with aix like
installation on my own, creating vgs managing networks, the VIOS, storage,lpars,
So we have a setup here almost all are in live production environment
with... (4 Replies)
Discussion started by: vax
4 Replies
9. AIX
Hello,
Is there a way to run
xclock
or
startx
on LPAR, since LPAR doesn't have any console or it is connected to HMC
usually the way is to export the display to some PC which has Xmanager running on it, but in my case, I want to run xmanager on the AIX Lpar and run on it the... (2 Replies)
Discussion started by: filosophizer
2 Replies
10. AIX
Note: Newbie to IBM virtualization :-)
Query: Created a new AIX7.1 lpar on a system with same config as one before however the new one is having issues going out to physical network.
Now on comparison the only thing which differs between these two machines is an additional en1 and ent1 shown... (7 Replies)
Discussion started by: max
7 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