01-28-2011
Anyone using NPIV?
Is anyone here using NPIV with AIX? If you are, what type of switch are you connected to? Also, please share some impressions of NPIV over traditional port-to-port LUN assignments. We are looking to move to NPIV and need some convincing argume... I mean information.
8 More Discussions You Might Find Interesting
1. AIX
Hi All,
I'm preparing to migrate some servers from vscsi to pass-thru NPIV. I am planning to have the SAN team move the exact LUNs from vio1/vio2 to those two VWWN through NPIV.
My question is on the partition itself.. right now, let's say I have hdisk0/1/2/3/4 that are part of datavg. They... (2 Replies)
Discussion started by: lapfrank
2 Replies
2. AIX
All
I am at a loss with a VIO server running ios 2.2.0.10-FP-24 SP-01. The VIO server is fitted with two 8Gb PCI Express Dual Port FC Adapters. However when I run the lsnports command only two of the adapter ports show as capable:
$ lsnports
name physloc ... (4 Replies)
Discussion started by: johnf
4 Replies
3. AIX
Hi All..
On to a new implementation with AIX 7.1 san boot from EMC disks (Using NPIV). Anyone played with this recently?
Wondering if we need PowerPath on the AIX clients or has native MPIO matured to replace it. Thoughts?
Thanks
Mr B (6 Replies)
Discussion started by: balaji_prk
6 Replies
4. AIX
Hi,
I want to change from vscsi to npiv. Is it possible to use both on the same adapter, so we can change the systems one by one, or must we place a second FC adapter in the VIO servers?
Thanks,
Ronald (2 Replies)
Discussion started by: ronaldm60
2 Replies
5. AIX
Hello all I hope someone can help me with this. I have a single LPAR which is supplied a rootvg and datavg disk set from a dual VIO server configuration. I see dual path disks for all the datavg disks but only see one path for the rootvg disks.
The client LPAR has the following:
fcs0 ... (3 Replies)
Discussion started by: johnf
3 Replies
6. AIX
Hi All :)
i would like to know if i can customize the WWN of the new VFC (NPIV).
Or, if i must move the LPAR on another server with another FCS, i have to change the zoning??
Thanks in advance.
Mario
---------- Post updated 09-21-12 at 02:51 AM ---------- Previous update was 09-20-12 at... (1 Reply)
Discussion started by: Zio Bill
1 Replies
7. AIX
Please forgive me here as I don't fully understand what I am talking about here so if I use the wrong terminology please overlook me.
We have multiple AIX LPARs on the managed system with two VIO Servers. A Co-Worker and I are trying to set up a new LPAR client (The guy that knows this is out)... (14 Replies)
Discussion started by: juredd1
14 Replies
8. AIX
Hi all ,
we're implementing a new NPIV infrastructure with AIX san boot on EMC2 VMAX 5876 , for economic reason , they don't wont to install Powerpath multipath sw , but only ODM drivers from EMC2 , this behavior is supported and can work?!
in the past we implemented NPIV on DS8000 family... (2 Replies)
Discussion started by: BabylonRocker76
2 Replies
VALE(4) BSD Kernel Interfaces Manual VALE(4)
NAME
vale -- a very fast Virtual Local Ethernet using the netmap API
SYNOPSIS
device netmap
DESCRIPTION
vale is a feature of the netmap(4) module that implements multiple Virtual switches that can be used to interconnect netmap clients, includ-
ing traffic sources and sinks, packet forwarders, userspace firewalls, and so on.
vale is implemented completely in software, and is extremely fast. On a modern machine it can move almost 20 Million packets per second
(Mpps) per core with small frames, and about 70 Gbit/s with 1500 byte frames.
OPERATION
vale dynamically creates switches and ports as clients connect to it using the netmap(4) API.
vale ports are named vale[bdg:][port] where vale is the prefix indicating a VALE switch rather than a standard interface, bdg indicates a
specific switch (the colon is a separator), and port indicates a port within the switch. Bridge and port names are arbitrary strings, the
only constraint being that the full name must fit within 16 characters.
See netmap(4) for details on the API.
LIMITS
vale currently supports up to 4 switches, 16 ports per switch, with 1024 buffers per port. These hard limits will be changed to sysctl vari-
ables in future releases.
SYSCTL VARIABLES
vale uses the following sysctl variables to control operation:
dev.netmap.bridge The maximum number of packets processed internally in each iteration. Defaults to 1024, use lower values to trade
latency with throughput.
dev.netmap.verbose Set to non-zero values to enable in-kernel diagnostics.
EXAMPLES
Create one switch, with a traffic generator connected to one port, and a netmap-enabled tcpdump instance on another port:
tcpdump -ni vale-a:1 &
pkt-gen -i vale-a:0 -f tx &
Create two switches, each connected to two qemu machines on different ports.
qemu -net nic -net netmap,ifname=vale-1:a ... &
qemu -net nic -net netmap,ifname=vale-1:b ... &
qemu -net nic -net netmap,ifname=vale-2:c ... &
qemu -net nic -net netmap,ifname=vale-2:d ... &
SEE ALSO
netmap(4)
http://info.iet.unipi.it/~luigi/vale/
Luigi Rizzo, Giuseppe Lettieri: VALE, a switched ethernet for virtual machines, June 2012, http://info.iet.unipi.it/~luigi/vale/
AUTHORS
The vale switch was designed and implemented in 2012 by Luigi Rizzo and Giuseppe Lettieri at the Universita` di Pisa.
vale was funded by the European Commission within FP7 Projects CHANGE (257422) and OPENLAB (287581).
BSD
July 27, 2012 BSD