NIM Problems creating a mksysb_resource Post: 302198291

Sponsored Content

Operating Systems AIX NIM Problems creating a mksysb_resource Post 302198291 by pdtak on Thursday 22nd of May 2008 02:15:14 PM

05-22-2008

Registered User

Thanks for your answer Bakunin, but the problem was bigger than what you and I thought.
We have an Etherchannel setup on our P5-590's, and here's the answer from IBM support:

Unforunately, Etherchannel (and other multiple adapter protocols,
like VIPA, Virtual IP Addressing) is not supported with NIM.

NIM requires, when performing a network boot for a client, that
-all- network traffic occur between only -two- adapters: The NIM
primary network adapter and the client's configured network adapter
(for boot purposes).

Etherchannel attempts to "load balance" network traffic by distributing
the network traffic for the system among the multiple adapters it has
in its configuration. This means that a BOOTP request can come in
one of the Etherchannel network adapters, but the response to the
client goes out another adapter, and is ignored by the client,
because the response packet was send by a different adapter than
the adapter that received it.
This behaviour prevents NIM from performing network boots of clients.

The only recourse is to either remove the Etherchannel configuration
from the NIM master system, or separate a -dedicated- network
adapter for use by NIM -only-, such that only NIM traffic can go out
and be received by this adapter.

There is also an unsupported method of getting Etherchannel and
NIM to cooperate. You can set the Etherchannel device to
"netif_backup", with one adapter acting as the 'primary' network
adapter for the system, and the other second adapter acting as a
"Backup Adapter", so that all network traffic goes in and out of
the 'primary' adapter, and the 'backup' adapter is only on standby,
to take over if the 'primary' adapter fails. This method is
unsupported, because the Etherchannel failover to the backup
adapter could happen in the middle of a NIM network boot of a
client, and will cause the network boot to fail.

pdtak

View Public Profile for pdtak

Find all posts by pdtak

10 More Discussions You Might Find Interesting

1. AIX

migrate NIM server through NIM installation

I try to migrate a NIM server from one server to another. I try to do a mksysb on NIM server restore the NIM server's mksysb to a client through NIM installation shutdown NIM server start newly installed client as NIM server Does anyone do this before? who can give me some suggestion?

2. AIX

Nim

Hello everyone I have two questions. 1.-The NIM and EZNIM are the same. 2.-If I have in one partition NIM installed I need to install EZNIM or I need to unistall NIM and then install EZNIM. Thanks for your comments.

3. Shell Programming and Scripting

help needed with creating challenging bash script with creating directories

Hi, Can someone help me with creating a bash shell script. I need to create a script that gets a positive number n as an argument. The script must create n directories in the current directory with names like map_1, map_2 etcetera. Each directory must be contained within its predecessor. So...

4. AIX

Back up a client NIM from nim master

Hello everyone Im trying to backup a nim client from nim master but I got this message COMMAND STATUS Command: failed stdout: yes stderr: no Before command completion, additional instructions may appear below. 0042-001 nim:...

5. AIX

NIM : remove nim client info from the client

Hi. I change my client's IP and hostname but I forgot to change anything on the master. How can I redefine or modify my client's resource from my master, or with using smit niminit from my client ? Tks

6. Homework & Coursework Questions

Creating a .profile, displaying system variables, and creating an alias

Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted! 1. The problem statement, all variables and given/known data: Here is what I am supposed to do, word for word from my assignment page: 1. Create/modify and print a...

7. AIX

Creating NIM SPOT using an existing mksysb from cliet

Hi, i backed up a test LPAR using mksyb utility on AIX. and transferred it to NIM server via NFS. I want to create a SPOT using this mksysb . Please explain me the procedure. And got something online, but that procedure is different. Please respond.

8. AIX

Problem in communication nim client with nim master

Hello, I have an AIX6.1 machine which is a nim client to my nim master which is also AIX6.1 machine. I had some problem to perform an installation on my client using smit nim . i removed /etc/niminfo file in order to do the initialization again but when i run the command niminit -a name=client...

9. AIX

How to know NIM name from NIM client?

Friend's, I was playing around with NIM in my environment & had a quick question in mind which I didn't/couldn't find answer to, which is -- how to find the name of the NIM server sitting on the NIM client? All leads to the answer would be much appreciated, many thanks! -- Souvik

10. HP-UX

Problems creating and accessing with user

Hi, I have created the user 'mastersa' in several servers. I need to change the user ID to '0'. However, after doing this, I am not able to login (Access denied). Even after I change the password, I still get this error. Why is this? Also, when I attempt to delete the user account, I get...

LEARN ABOUT BSD

hy

HY(4)							     Kernel Interfaces Manual							     HY(4)

NAME

       hy - Network Systems Hyperchannel interface

SYNOPSIS

       /sys/conf/SYSTEM:
	    NHY  hy_controllers # Hyperchannel

DESCRIPTION

       The hy interface provides access to a Network Systems Corporation Hyperchannel Adapter.

       The  network  to  which the interface is attached is specified at boot time with an SIOCSIFADDR ioctl.  The host's address is discovered by
       reading the adapter status register.  The interface will not transmit or receive packets until the network number is known.

DIAGNOSTICS

       hy%d: unit number 0x%x port %d type %x microcode level 0x%x.  Identifies the device during autoconfiguration.

       hy%d: can't handle af%d.  The interface was handed a message with addresses formatted in an  unsuitable	address  family;  the  packet  was
       dropped.

       hy%d:  can't  initialize.  The interface was unable to allocate UNIBUS resources. This is usually due to having too many network devices on
       an 11/750 where there are only 3 buffered data paths.

       hy%d: NEX - Non Existent Memory.  Non existent memory error returned from hardware.

       hy%d:  BAR overflow.  Bus address register overflow error returned from hardware.

       hy%d: Power Off bit set, trying to reset.  Adapter has lost power, driver will reset the bit and see if power is still out in the adapter.

       hy%d: Power Off Error, network shutdown.  Power was really off in the adapter, network connections are dropped.	 Software  does  not  shut
       down the network unless power has been off for a while.

       hy%d: RECVD MP > MPSIZE (%d).  A message proper was received that is too big.  Probable a driver bug.  Shouldn't happen.

       hy%d: xmit error - len > hy_olen [%d > %d].  Probable driver error.  Shouldn't happen.

       hy%d: DRIVER BUG - INVALID STATE %d.  The driver state machine reached a non-existent state.  Definite driver bug.

       hy%d: watchdog timer expired.  A command in the adapter has taken too long to complete.	Driver will abort and retry the command.

       hy%d: adapter power restored.  Software was able to reset the power off bit, indicating that the power has been restored.

SEE ALSO

       intro(4N), inet(4F)

BUGS

       If  the	adapter  does not respond to the status command issued during autoconfigure, the adapter is assumed down.  A reboot is required to
       recognize it.

       The adapter power fail interrupt seems to occur sporadically when power has, in fact, not failed.  The driver will believe that	power  has
       failed  only  if it can not reset the power fail latch after a ``reasonable'' time interval.  These seem to appear about 2-4 times a day on
       some machines.  There seems to be no correlation with adapter rev level, number of ports used etc. and whether a  machine  will	get  these
       ``bogus powerfails''.  They don't seem to cause any real problems so they have been ignored.

3rd Berkeley Distribution					  August 20, 1987							     HY(4)