Sponsored Content
Full Discussion: VIOS SEA Creation
Operating Systems AIX VIOS SEA Creation Post 302432168 by kkeng808 on Thursday 24th of June 2010 05:40:04 AM
Old 06-24-2010
Question VIOS SEA Creation

Hi Guys,

I'm getting the below error while trying to create a SEA adapter in VIOS

Code:
$ mkvdev -sea ent0 -vadapter ent2 -default ent2 -defaultid 1                    
                                                                                
                                                                                
Some error messages may contain invalid information                             
for the Virtual I/O Server environment.                                         
                                                                                
Method error (/usr/lib/methods/cfgsea):                                         
        0514-040 Error initializing a device into the kernel.                   
                                                                                
Command did not complete.                                                       
                                                                                
"Run mkdev" was last subcommand run.                                            
                                                                                
$


Not sure what this means.. Can someone throw some light in this Smilie
 

9 More Discussions You Might Find Interesting

1. AIX

VIOS SEA on LHEA doesn't work

I am trying to create a SEA on a LHEA port and it gives me error lsdev -Cc adapter: ent0 logical host ethernet port (l-hea) ent1 virtual I/O ethernet adapter mkvdev -sea ent0 -vadapter ent1 -default ent1 -defaultid 199 method error (/usr/lib/methods/cfgsea): Failed to configure SEA... (0 Replies)
Discussion started by: filosophizer
0 Replies

2. AIX

SEA

Hi all, I set up the following configuration on my system: - An LPar with a virtual adapter, first one with a vlan id=703 and id port=13. - The first adapter have to connect to a VIOS in which i configured an SEA. So, the VA is set up on interface ent2, SEA on ent29 (by linking a... (0 Replies)
Discussion started by: idro
0 Replies

3. AIX

How to set 4 SEA on single VIOS

Hi experts, i got a 4-port Adapter card on VIOS and would like to configure 4SEA for 4 difference segment IP client's LPAR use, first SEA succeed to be configured on ent0 but once second SEA configured, first SEA fail to be connected. Any issues i need to be concerned in order to configure 4 SEA on... (8 Replies)
Discussion started by: polar
8 Replies

4. AIX

Configure VIOS SEA w. load sharing

I am trying to install a VIOS pair with a load-sharing SEA adapter, following this recipe from Developerworks. Without load-sharing everything went fine and worked as expected, but somehow i am a bit lost and the first tries with "ha_mode=sharing" didn't work at all. Here is the situation: I... (6 Replies)
Discussion started by: bakunin
6 Replies

5. AIX

VIOS IP address - separate vlan for vios servers ?

Hello, Lets say for simplicity that I do not use any vlan config inside my server - one lpar group use hea physical port1, another group hea physical port2. Physical port1 configured as vlan1 on external switch, physical port2 as vlan2. What is the common practice - should I isolate my vios... (0 Replies)
Discussion started by: vilius
0 Replies

6. AIX

SEA configuration

i want configure a SEA over my vios , i have a message error : Method error (/usr/lib/methods/cfgsea): Failed to configure SEA with return code 1 and SEA-specific error code 10: Detailed info: Setting real adapter ent1 in promiscuous mode failed... (5 Replies)
Discussion started by: hedou
5 Replies

7. AIX

VIO SEA Adapters

hi guys BTW pretty new to VIO I inherited 2 I BM Power Server - blades PS701 - One is already configured using en8 # lsdev -Cc adapter | grep ent ent0 Available Logical Host Ethernet Port (lp-hea) ent1 Available Logical Host Ethernet Port (lp-hea) ent2 Available 04-20... (8 Replies)
Discussion started by: karlochacon
8 Replies

8. AIX

SEA to standby

hello, what will happen if i try to move sea of my 1 vio server to standby( using chdev command), when sea of other vio server is already in standby mode? (1 Reply)
Discussion started by: amvineeth
1 Replies

9. AIX

VIOS entstat versus seastat for SEA

Hello, I found that the packet counts given by entstat -d SEA is not the same as the total of the packet counts given by seastat -d SEA for the same interval of time. Do anyone have an explanation for the difference. We recently got a recommendation that the throughput on an SEA should not... (5 Replies)
Discussion started by: N8R
5 Replies
Error(3pm)						User Contributed Perl Documentation						Error(3pm)

NAME
Tk::Error - Method invoked to process background errors SYNOPSIS
Customization: require Tk::ErrorDialog; or sub Tk::Error { my ($widget,$error,@locations) = @_; ... } DESCRIPTION
The Tk::Error method is invoked by perl/Tk when a background error occurs. Two possible implementations are provided in the distribution and individual applications or users can (re)define a Tk::Error method (e.g. as a perl sub) if they wish to handle background errors in some other manner. A background error is one that occurs in a command that didn't originate with the application. For example, if an error occurs while executing a callback specified with a bind or a after command, then it is a background error. For a non-background error, the error can simply be returned up through nested subroutines until it reaches the top-level code in the application; then the application can report the error in whatever way it wishes. When a background error occurs, the unwinding ends in the Tk library and there is no obvious way for Tk to report the error. When Tk detects a background error, it saves information about the error and invokes the Tk::Error method later when Tk is idle. Tk::Error is invoked by perl/Tk as if by the perl code: $mainwindow->Tk::Error("error message", location ...); $mainwindow is the MainWindow associated with widget which detected the error, "error message" is a string describing the error that has been detected, location is a list of one or more "locations" which describe the call sequence at the point the error was detected. The locations are a typically a mixture of perl location reports giving script name and line number, and simple strings describing locations in core Tk or perl/Tk C code. Tk will ignore any result returned by the Tk::Error method. If another error occurs within the Tk::Error method (for example if it calls die) then Tk reports this error itself by writing a message to stderr (this is to avoid infinite loops due to any bugs in Tk::Error). If several background errors accumulate before Tk::Error is invoked to process them, Tk::Error will be invoked once for each error, in the order they occurred. However, if Tk::Error calls Tk->break, then any remaining errors are skipped without calling Tk::Error. The Tk module includes a default Tk::Error subroutine that simply reports the error on stderr. Tk::ErrorDialog An alternate definition is provided via: "require Tk::ErrorDialog;" that posts a dialog box containing the error message and offers the user a chance to see a stack trace showing where the error occurred. This is an OO implementation of the Tcl/Tk command bgerror, with a twist: since there is only one ErrorDialog widget, you aren't required to invoke the constructor to create it; it will be created automatically when the first background error occurs. However, in order to configure the -cleanupcode and -appendtraceback ErrorDialog options you must call the constructor and create it manually. The ErrorDialog object essentially consists of two subwidgets: a Dialog widget to display the background error and a Text widget for the traceback information. If required, you can invoke various widget methods to customize these subwidgets - their advertised names are described below. $mw->ErrorDialog(-cleanupcode => code, -appendtraceback => bool); $mw is a window reference. code is a CODE reference if special post-background error processing is required (default is undefined). The callback subroutine is called with @_ having the same arguments that Tk::Error was invoked with. bool is a boolean indicating whether or not to append successive tracebacks (default is 1, do append). Advertised ErrorDialog widgets error_dialog is the Dialog widget reference. text is the Text widget reference containing the traceback information. BUGS
If after or fileevent are not invoked as methods of a widget then perl/Tk is unable to provide a $mainwindow argument. To support such code from earlier versions of perl/Tk perl/Tk therefore calls Tk::Error with string 'Tk' instead: Tk->Tk::Error(...). In this case the Tk::Error in Tk::ErrorDialog and similar implementations cannot "popup" a window as they don't know which display to use. A mechanism to supply the MainWindow in applications which only have one (a very common case) should be provided. SEE ALSO
Tk::bind Tk::after Tk::fileevent KEYWORDS
background error, reporting perl v5.14.2 2010-05-29 Error(3pm)
All times are GMT -4. The time now is 09:14 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy