Contents
Creating a SEA in a VIO
We will see how to create a SEA
to bridge packets to client LPAR
Get the
list of current devices in VIOs
$ lsdev -type adapter
name status description
ent0 Available 2-Port 10/100/1000 Base-TX PCI-Express Adapter (14104003)
ent1 Available 2-Port 10/100/1000 Base-TX PCI-Express Adapter (14104003)
ent2 Available Virtual I/O Ethernet Adapter (l-lan)
fcs0 Available 8Gb PCI Express Dual Port FC Adapter (df1000f114108a03)
fcs1 Available 8Gb PCI Express Dual Port FC Adapter (df1000f114108a03)
pager0 Available Pager Kernel Extension
vasi0 Available Virtual Asynchronous Services Interface (VASI)
vbsd0 Available Virtual Block Storage Device (VBSD)
vhost0 Available Virtual SCSI Server Adapter
vsa0 Available LPAR Virtual Serial Adapter
As seen above the VIOS already
has a Virtual device and Physical device for bridging. If there are no virtual
devices, we can create one from HMC
If you are adding a new device
use 'cfgmgr' to 'see' the new device
Note down the names of the
adapters needed to bridging
Here we have
Physical: ent0 Virtual: ent2
make sure that the physical
interface properties are proper (Ex. Duplex, speed etc...)
If any of the interface has IP
configuration, use 'rmtcpip' to remove them
Get the
current slot information
$ lsdev -slots
# Slot Description Device(s)
U8233.E8B.1000A1P-V7-C0 Virtual I/O Slot vsa0
U8233.E8B.1000A1P-V7-C11 Virtual I/O Slot ent2
U8233.E8B.1000A1P-V7-C12 Virtual I/O Slot vhost0
U8233.E8B.1000A1P-V7-C32769 Virtual I/O Slot vasi0
Create
SEA
$ mkvdev -sea ent0 -vadapter ent2 -defaultid 7 -default ent2
ent3 Available
en3
et3
details
§ -sea --
the physical adapter on which to create SEA
§ -vadapter
-- the virtual adapter on which to create SEA (can give multiple virtual
adapters)
§ -default
-- the vitual adapter to use as default adapter
§ -defaultid
-- The PVID to use for the SEA. (PVID for the SEA)
The additional VID will be
automatically added by VIO, based on the virtual adapters.
verify
the virtual device
$ lsdev -virtual
name status description
ent2 Available Virtual I/O Ethernet Adapter (l-lan)
vasi0 Available Virtual Asynchronous Services Interface (VASI)
vbsd0 Available Virtual Block Storage Device (VBSD)
vhost0 Available Virtual SCSI Server Adapter
vsa0 Available LPAR Virtual Serial Adapter
ent3 Available Shared Ethernet Adapter
$ lsdev -type adapter
name status description
ent0 Available 2-Port 10/100/1000 Base-TX PCI-Express Adapter (14104003)
ent1 Available 2-Port 10/100/1000 Base-TX PCI-Express Adapter (14104003)
ent2 Available Virtual I/O Ethernet Adapter (l-lan)
ent3 Available Shared Ethernet Adapter
fcs0 Available 8Gb PCI Express Dual Port FC Adapter (df1000f114108a03)
fcs1 Available 8Gb PCI Express Dual Port FC Adapter (df1000f114108a03)
pager0 Available Pager Kernel Extension
vasi0 Available Virtual Asynchronous Services Interface (VASI)
vbsd0 Available Virtual Block Storage Device (VBSD)
vhost0 Available Virtual SCSI Server Adapter
vsa0 Available LPAR Virtual Serial Adapter
Get
attributes of the SEA
$ lsdev -dev ent3 -attr
attribute value description user_settable
accounting disabled Enable per-client accounting of network statistics True
ctl_chan Control Channel adapter for SEA failover True
gvrp no Enable GARP VLAN Registration Protocol (GVRP) True
ha_mode disabled High Availability Mode True
jumbo_frames no Enable Gigabit Ethernet Jumbo Frames True
large_receive no Enable receive TCP segment aggregation True
largesend 0 Enable Hardware Transmit TCP Resegmentation True
netaddr 0 Address to ping True
pvid 7 PVID to use for the SEA device True
pvid_adapter ent2 Default virtual adapter to use for non-VLAN-tagged packets True
qos_mode disabled N/A True
real_adapter ent0 Physical adapter associated with the SEA True
thread 1 Thread mode enabled (1) or disabled (0) True
virt_adapters ent2 List of virtual adapters associated with the SEA (comma separated) True
Assigin
an IP to SEA adaper
This is not necessary. You can
create a another virtual adapter on the same VLAN on the SEA's PVID or vid,
then assign an IP to it
$ mktcpip -hostname sys414_vios7 -interface en3 \
> -inetaddr 10.6.133.142 -netmask 255.255.255.0 \
> -gateway 10.6.133.254
you can try and ping an ip within your network to verify connectivity
get
routing table
# netstat -rn
Routing tables
Destination Gateway Flags Refs Use If Exp Groups
Route Tree for Protocol Family 2 (Internet):
default 10.6.133.254 UG 1 61 en3 - -
10.6.133.0 10.6.133.142 UHSb 0 0 en3 - - =>
10.6.133/24 10.6.133.142 U 2 29 en3 - -
10.6.133.142 127.0.0.1 UGHS 0 2 lo0 - -
10.6.133.255 10.6.133.142 UHSb 0 0 en3 - -
127/8 127.0.0.1 U 2 77 lo0 - -
Route Tree for Protocol Family 24 (Internet v6):
::1 ::1 UH 0 54 lo0 - -
or use 'lstcpip -routtable' as padmin
Create an VSCSI disk in AIX VIO
Configuring iSCSI target
using 'targetcli' > Configuring packet forwarding > Configuring postfix for first
time > Create a new database in mysql> Create an VSCSI disk in AIX
VIO
VSCSI is required to map disk
to client LPARs
VIOS will 'own' the physical
resource. The VIOS will present an virtual resource (virtual target device) to
the LPAR. This virtual device is backed by a physical device
We need a virtual SCSI adapter in VIOS and client LPAR for presenting a disk to client LPAR. This relationship is one-to-one. That is, for every LPAR, there must be 2 virtual SCSI adapters. Once in VIOS and one in client LPAR