How do I add a virtual ethernet apdater to an lpar's profile

Answer

First step is to access the HMC that manages this managed server that is being worked on.

1) Select the managed machine

2) Select the lpar that needs to be modified

3) Select the "tasks" drop down menu

4) Select "configuration"

5) Select "Manage Profiles"

Then a new window will pop up

1) check box the profile that needs to be modified. Some servers will only have one profile, some
may have multiple. Select the one that is going to be used, or if the change needs to be made to
all of them, you may need to go back and do this again.

2) Select the "Actions" drop down menu

3) Select the option to "Edit" the profile

Then a new window will pop up.

1) Select the "Virtual Adapters" tab

2) Select the "Actions" drop down menu

3) Select the "Create Virtual Adapter" option

4) Select "Ethernet Adapter"

Then a new window will pop up:

If this virtual adapter is for a VIO client, then you only need to populate the Vlan that this client
adapter needs. i.e. if this client is on vlan 1 leave the default of 1 in this option. If it is going to be
on vlan 20, replace the number with a 20, ect...
If this virtual adapter is for a VIO server Then you may need additional options, especially if it
is needing "Vlan tagging" enabled for the virtual i/o clients.

To enable vlan tagging

1) check box the IEEE 802.1q check box
2) populate the "add VLAN ID" with the vlan you want to add
3) click the add button and you will notice that the new number is added to the list
4) check box the "use this adapter for Ethernet bridging" to indicate that this is going to be part
of an Share Ethernet Adapter on the VIO server, all SEA adapters require this check box. But,
not all SEA adapters require changing the priority unless you are setting up SEA failover.

This document was only developed to show screen shots for allocating a virtual adapter to an
lpar's profile. For detailed instructions on how to set up a SEA or SEA failover environment go
to this link:
How to use smitty to add a 2nd IP address & Network?
Most AIX system administrators use: smitty tcpip to add a hostname, IP address, network mask,
gateway and DNS server setting to get the virtual machines (LPAR) and AIX on a network. And
as a side benefit so we don't need to use the ghastly VTERM console any more as ssh or the
dreaded unsecure telnet (just don't do it) can now be used - as the root user:

# smitty tcpip
...

Minimum Configuration & Startup

Further Configuration
Use DHCP for TCPIP Configuration & Startup
 IPV6 Configuration
Quality of Service Configuration & Startup
Configure IP Security (IPv4)
Configure IP Security (IPv6)

Once smitty starts, you take the "Minimum Configuration & Startup" first line menu option
then select the Network interface like en0, en1 etc.

+---------------------------------------------------------------------
-----+
| Available Network Interfaces
|
|
|
| Move cursor to desired item and press Enter.
|
|
|
| en0 Standard Ethernet Network Interface
|
| en1 Standard Ethernet Network Interface
|
| et0 IEEE 802.3 Ethernet Network Interface
|
| et1 IEEE 802.3 Ethernet Network Interface
|
|
|
| F1=Help F2=Refresh F3=Cancel
|
| F8=Image F10=Exit Enter=Do
|
| /=Find n=Find Next
|
+---------------------------------------------------------------------
-----+

That sets up the primary network for the machine and the hostname matches the DNS server
name for the IP address.

* HOSTNAME
[orange.aixncc.uk.ibm>
* Internet ADDRESS (dotted decimal) [9.133.62.82]
Network MASK (dotted decimal) [255.255.255.0]
* Network INTERFACE en0
NAMESERVER
Internet ADDRESS (dotted decimal) [9.133.62.2]
DOMAIN Name [aixncc.uk.ibm.com]
Default Gateway
Address (dotted decimal or symbolic name) [9.137.62.1]
Cost [0]
#
Do Active Dead Gateway Detection? no
+
 Your CABLE Type N/A
+
START TCP/IP daemons Now no
+

But lots of machines in production have many networks for various purposes like backup, admin
network, user access and clustering.

So how to set up these 2nd, 3rd, 4th etc. Network interfaces is not so obvious.

Again start with: smitty tcpip

$ smitty tcpip
...

Minimum Configuration & Startup

Further Configuration
Use DHCP for TCPIP Configuration & Startup
IPV6 Configuration
Quality of Service Configuration & Startup
Configure IP Security (IPv4)
Configure IP Security (IPv6)

Then the second option "Further Configuration"

Hostname
Static Routes
Network Interfaces
Name Resolution
Client Network Services
Server Network Services
Manage Print Server
Select BSD style rc Configuration
Start Configured TCPIP Daemons
Stop TCPIP Daemons
Authentication Configuration

then down two to "Network Interfaces"

Network Interface Selection

Network Interface Drivers

then "Network Interface Selection"

List All Network Interfaces

Add a Network Interface
Change / Show Characteristics of a Network Interface
Remove a Network Interface
PVCs for IP over an ATM Network
Configure Aliases

then "Change / Show Characteristics of a Network Interface"

 +---------------------------------------------------------------------
-----+
| Available Network Interfaces
|
|
|
| Move cursor to desired item and press Enter.
|
|
|
| en0 Standard Ethernet Network Interface
|
| en1 Standard Ethernet Network Interface
|
| et0 IEEE 802.3 Ethernet Network Interface
|
| et1 IEEE 802.3 Ethernet Network Interface
|
|
|
| F1=Help F2=Refresh F3=Cancel
|
| F8=Image F10=Exit Enter=Do
|
| /=Find n=Find Next
|
+---------------------------------------------------------------------
-----+

then select the Network interface like en0, en1 but making sure you DO NOT select the
primary network interface that you set above.

Network Interface Name en1

INTERNET ADDRESS (dotted decimal) [1.1.1.2]
Network MASK (hexadecimal or dotted decimal) [255.255.255.0]
Current STATE up
+
Use Address Resolution Protocol (ARP)? yes
+
BROADCAST ADDRESS (dotted decimal) []
Interface Specific Network Options
('NULL' will unset the option)
rfc1323 []
tcp_mssdflt []
tcp_nodelay []
tcp_recvspace []
tcp_sendspace []
Apply change to DATABASE only no +