Originally posted by: SystemAdmin
This is the response that I got from IBM (In a nutshell, not an issue):
When we configure the etherchannel interface and reboot the system, AIX
tries to configure interfaces via /etc/rc.net file which called by phase
2 cfgmgr. (without HACMP) /etc/rc.net file first call defif followed by
cfgif program. (these programs in the /usr/lib/methods/ directory which
linked by /etc/methods directory) At the cfgif step, AIX tries to config
ure interfaces with their IP address, subnet mask, and so on. But until
this stage, etherchannel devices can't be configured because cfgech
method is never called until this stage. So, at this time, AIX gets the
error message "No such devices (ENODEV)" which is errno 19.
But after this stage, /etc/rc.net file calles definet and cfginet and
cfginet method calls the cfgech (config etherchannel) to configure
etherchannel device. So, all etherchannel devices are activated normally
at thi s stage without HACMP. So every system which has etherchannel
device rec eive the ENODEV (errno 19). But the syslogd is not started,
the console message you have sent to me is not showed up.
(if_en: ns_alloc(en6) failed with errno = 19) if_en uses the bsdlog()
function to send this messag e and bsdlog() messages are used by syslog
daemon. But if we installed the HACMP, this logic is slightly changed.
HACMP updates the /etc/inittab file to call /sbin/rc.boot file for
phase 3. and another net.rc file (harc.net) file is inserted in the
inittab fi le just after srcmstr line. So they uses harc.net file to
configure netw ork interfaces.
In the harc file, it calles defif and cfgif as rc.net file does. so this
cfgif stage, system gets the error message which is same as normal
boot(without HACMP). and this error message goes to syslog daemon which
is st arted by HACMP just before. This is the message you've seen in
the conslog file. But, after that, harc file calls the cfgech method,
and cfgif again. In this stage, etherchannel is normally set up and
available.
I tested this behavior in AIX 5.2, and 5.3 without HACMP, and always the
result is same.
In conclusion, this is normal flow of setting up etherchannel, so you
can ignore this message because the etherchannel device and interface
has no problem and works properly.
#AIX-Forum