Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1263
  • Last Modified:

VIO SEA Error

I am attempting to create a Shared Ethernet Adapter on my VIO server (which will service my iSeries partitions).

When I attempt to create the SEA, I get the following error

Failed to configure SEA with return code 22 and SEA specific error code 9:
Opening real adapter ent18 failed with error 22.

We have successfully created a SEA on our VLAN2, but when we attempt to create this SEA for our VLAN 1...we are having issues.

Anyone have any ideas?

Thanks!
0
Matthew Roessner
Asked:
Matthew Roessner
  • 5
  • 4
1 Solution
 
woolmilkporcCommented:
Could it be that there is already a protocol device en18 configured over ent18?
Or is ent18 already in use for another SEA?

If so this keeps the adapter from being opened by cfgsea (mkvdev).

Check (as padmin) with

lsdev | grep en18

If you see "Available" then check the settings:

lsdev -attr -dev en18

You will see the IP config, if any.

Decide whether you must keep this address or not. Depending on this decision either choose a different adapter or remove the device with

rmdev -dev en18

Then run "cfgdev" to reconfigure the en18 device as "Defined" and proceed with configuring the SEA.

Note: You can check which adapters are eligible for SEA with

lsdev -type ent4sea

and you can see your SEAs with

lsdev -type sea

wmp
0
 
Matthew RoessnerAuthor Commented:
We don't have any interfaces configured for our ent18 which is a Etherchannel:

lsdev -type ent4sea

 name            status      description
 ent13           Available   4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)
 ent14           Available   4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)
 ent15           Available   4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)
 ent18           Available   EtherChannel / IEEE 802.3ad Link Aggregation

We are attempting to connect the SEA to ent18
0
 
woolmilkporcCommented:
Well,

the only instance where I saw such behaviour was under out-of-memory conditions, but this was error 12, not 22.

Anyway, how much memory does the VIOS partition have? IBM recommend assigning 2 GB per processor core.

SEA RC 9 means something like "Device not ready". Are you sure that this Etherchannel is in a good state? Are the underlying adapters "Available"?

I'd recommend removing the Etherchannel (lnagg) device and its adapters completely.

Then re-detect the physical adapters with "cfgdev". Are these still "Available"?

If so, recreate the lnagg and retry cfgsea.

If the physical adapters don't show up as "Available" or don't show up at all check the VIOS LPAR config on the HMC.
0
Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

 
Matthew RoessnerAuthor Commented:
We tried all of the recommendations you suggested (multiple times). We are running 12 GB of memory on each of our VIO servers, so I think we should have plenty of memory.

Are physical adapters appear to be in OK shape....at least we don't see any issues with them and they are all showing link lights and appear to be in a good state. (everything shows available

ent0             Available   4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)
ent1             Available   4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)
ent2             Available   4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)
ent3             Available   4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)
ent4             Available   4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)
ent5             Available   4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)
ent6             Available   4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)
ent7             Available   4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)
ent8             Available   4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)
ent9             Available   4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)
ent10            Available   4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)
ent11            Available   4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)
ent12            Available   4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)
ent13            Available   4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)
ent14            Available   4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)
ent15            Available   4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)
ent16            Available   Virtual I/O Ethernet Adapter (l-lan)
ent17            Available   Virtual I/O Ethernet Adapter (l-lan)
ent18            Available   EtherChannel / IEEE 802.3ad Link Aggregation
ent19            Available   EtherChannel / IEEE 802.3ad Link Aggregation
ent20            Available   Virtual I/O Ethernet Adapter (l-lan)
ent21            Available   Virtual I/O Ethernet Adapter (l-lan)
ent22            Available   Shared Ethernet Adapter
0
 
woolmilkporcCommented:
>> We tried all ... << 

Did you remove/recreate the LNAGG including its physical adapters?

Is the virtual adapter (l-lan) to be bridged by the SEA allowed "Use this adapter for Ethernet Bridging"?

If both of the above is true all that I can still recommend is checking the error log ("errlog" as padmin). If there's also nothing I fear I can't help any further.

Perhaps you should open a ticket with IBM.
0
 
Matthew RoessnerAuthor Commented:
We deleted the ENT18 (LNAGG) completely and recreated the entire aggregate link (multiple times....
0
 
woolmilkporcCommented:
Not only ent18, delete also the physical adapters making up the aggregate ...
0
 
Matthew RoessnerAuthor Commented:
We had to delete all of the adapters that made up the aggregate and let them re-populate. Then, we were able to re-create the aggregate and then ultimately the SEA
0
 
woolmilkporcCommented:
Fine, that's exactly what I suggested. Glad to see it worked!

Thx for the points!

wmp
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now