1. Vlan Tagging, Load Sharing with 10G adapters

2. Agenda VIOS Sizing considerations for 10G adapters.
10G adapter settings
Vlan Tagging with 10G adapters
Vlan Tagging with Load Sharing
Network Migration from 1G to 10G
Q & A

3. VIOS Sizing Considerations
CPU:
- Enable shared processing mode for additional Processor capacity.
- EC should be set based on average consumption.
- Suggested Sharing mode is uncapped.
- VIOS typically should have higher weight.
Memory:
- 2GB per 16 cpus.
- 512M for each 10G port.
- 16M for each Virtual adapter.
- Monitor the usage of resources on VIOS regularly.
- A good starting point would be 6GB desired memory and EC 1 cpu, VCPU, uncapped, weight of 128

4. 10G adapter Settings
First important thing is to meet with your network team.
1G to 10G does not give 10 fold increase in performance.
In each LPAR
- Enable rfc132 option.
- Use the Maximum available MTU size (64k).
On each VIO server
- VIOS must be at version or later
- Enable large_send, flow_ctrl, large_receive and jumbo_frames.
- SEA adapter itself needs to have large_send, large_receive and jumbo_frames enabled.
On Network Switch
- Check with network team if the switch has flow_ctrl enabled. If not have it enabled.

5. Vlan Tagging with 10G adapters
Create virtual Ethernet adapter for control channel and add unused vlan to it.
Create virtual Ethernet adapter to add all the vlans.
- Check access to external networks/Ethernet bridging or check the bridging adapter option and give it trunk priority.
- Check IEEE 802.1q
- Add PVID
- Add all the additional vlans
vlan IDs should be identical to Vlan IDs on switch port.
create SEA with default ID
mkvdev -sea entx -vadapter <virt. Adapter> -default <virt. Adapter> -defaultid <pvid of virt. Adapter> - attr ha_mode = auto ctl_chan = <ctl chan virt. Adapter>
Associate each additional vlan to SEA
- mkvdev -vlan <sea> -tagid <additional vlan>
- A new virt adapter is created for each vlan.
- Repeat this command for all the vlan tags.
Configure vlan tagging same way on secondary vio server with the exception of setting trunk priority to a different value to the virtual adapter. Also add the same vlan id to the control channel adapter on secondary vio server.
Command to check details of SEA.
entstat -d < entX > | egrep -i "state|link|priority|active|availability|vlan"

6. Vlan Tagging with Load Sharing (1 of 2)
Requirements:
VIOS must at version or later
Load Sharing must be enabled first on the primary SEA. The secondary SEA initiates the load sharing and wants the primary
to be ready.
SEA should be vlan tagged which means there should be 2 or more vlans defined.
There should be two or more trunk/virtual adapters for Load Sharing.
Vlan IDs should be identical on primary and backup SEAs.
Do not confuse Load Sharing with Load Balancing because load sharing is network traffic split between networks.

7. Vlan Tagging with Load Sharing (1 of 2)
Configuration:
Create virtual Ethernet adapter for control channel.
Add an unused vlan to it.
Create virtual Ethernet adapter to add the vlan.
- Check access to external networks/Ethernet bridging or check the bridging adapter option and give it trunk priority.
- Check IEEE 802.1q
- PVID should be unused vlan on VIO server.
- Add the vlan
- Repeat this step for each of the vlans.
create SEA with default ID
mkvdev -sea entx -vadapter <virt. Adapter>,<virtual adapter> default <virt. Adapter> -defaultid <pvid of virt. Adapter> -attr ha_mode=sharing ctl_chan=<ctl chan virt. Adapter>
eg: mkvdev –sea ent0 –vadapter ent3,ent4,ent5,ent6 –default ent3 –defaultid 10 -attr ha_mode=sharing ctl_chan=ent1
If you have an SEA already defined, its mode can be dynamically changed to load sharing by,
chdev –dev <sea> -attr ha_mode=sharing
Configure vlan tagging the same way on secondary vio server with the exception of setting trunk priority to a different value to the virtual adapter. Also add the same vlan id to the control channel adapter on secondary vio server.
Command to check details of SEA.
entstat -d <entX>|egrep -i "state|link|priority|active|availability|vlan“
State Shows "PRIMARY_SH" or "BACKUP_SH"
High Availability Mode shows "Sharing"

8. Neigel Griffith’s Load Sharing diagram

9. Network Migration from 1G to 10G
Migration from 1G to 10G adapters:
This requires a short network outage on the lpar.
Create a virtual adapter on the lpar using dlpar with the appropriate vlan id from the tagged list.
Log into console session and remove the existing Ethernet adapter.
On the lpar, ifconfig en0 down; ifconfig en0 detach; rmdev –dl ent0.
Remove the adapter using dlpar and save the dlpar config to profile.
Run cfgmgr on the lpar to configure the new Virtual Ethernet adapter.
smitty tcpip or mktcpip on the new adapter with ipadress, netmask, GW etc.

10. Q & A