• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4005
  • Last Modified:

Odd error when trying to run commands in both ways.

believe or not! NIM again :-(
Here I go.

First, I create the client-MACHINE on the NIM.

On the NIM server:
bibmdes_cont:
   class          = machines
   type           = standalone
   connect        = nimsh
   platform       = chrp
   netboot_kernel = 64
   if1            = ent-Network1 bibmdes_cont 0
   cable_type1    = N/A
   Cstate         = ready for a NIM operation
   prev_state     = ready for a NIM operation
   Mstate         = currently running

ent-Network1:
   class      = networks
   type       = ent
   comments   = Generated during definition of bibmdes_cont
   Nstate     = ready for use
   prev_state = information is missing from this object's definition
   net_addr   = 172.17.32.80
   snm        = 255.255.255.240
   routing1   = default 172.17.32.94

Now, go to the client and setup nim.

On the client:
smitty nim
                                                        [Entry Fields]
* Machine Name                                       [bibmdes_cont]
* Primary Network Install Interface                  [en0]                                +
* Host Name of Network Install Master                [bibmnim]

  Hardware Platform Type                              chrp
  Kernel to use for Network Boot                     [64]                                 +
  Communication Protocol used by client              [nimsh]                              +
  Ethernet Interface Options
    Network Speed Setting                            []                                   +
    Network Duplex Setting                           []                                   +
  Comments                                           []


Setting up SSL
smitty nim_config_services
* Communication Protocol used by client              [nimsh]                              +

  NIM Service Handler Options
*   Enable Cryptographic Authentication              [enable]                             +
      for client communication?

Everythings looks OK, no error.

So, back to NIM, you can see the nimsh-secure protocol.

On the NIM:
bibmdes_cont:
   class          = machines
   type           = standalone
   connect        = nimsh (secure)
   platform       = chrp
   netboot_kernel = 64
   if1            = ent-Network1 bibmdes_cont 0
   cable_type1    = N/A
   Cstate         = ready for a NIM operation
   prev_state     = ready for a NIM operation
   Mstate         = currently running
   cpuid          = 0009EACAD400

############################################################

Trying to update_all from the client:
smitty nim
 Install and Update Software
 Update Installed Software to Latest Level (Update All)
 On the BOX (Select the LPP_SOURCE containing the install image) you can see all resources got them from the NIM, so I select the LPP resource:
  ENTER
  ENTER
 
 BUT get this error:
 
 Command: failed        stdout: yes           stderr: no

Before command completion, additional instructions may appear below.

0042-001 nimclient: processing error encountered on "master":
   0042-001 nim: processing error encountered on "master":
   0042-006 m_cust: (From_Master) connect Error 0

        0042-404 nconn: Error connecting to SSL object.
        0042-406 nconn: Error verifying SSL object after connection.
nconn: ð}
: Error 0

I did another test from the NIM, and get the same error.

Any idea why?

Thanks.
0
sminfo
Asked:
sminfo
  • 8
  • 4
2 Solutions
 
sminfoAuthor Commented:
And..

NIM is on AIX 6.1-TL6 latest SP
Client is on  AIX7.1-TL0-SP1

0
 
sminfoAuthor Commented:
More, I restart nimsh on the client
stopsrc -s nimsh
startsrc -s nimsh

and when repeat got this error:

Command: failed        stdout: yes           stderr: no

Before command completion, additional instructions may appear below.

0042-001 nimclient: processing error encountered on "master":
   0042-001 nim: processing error encountered on "master":
   0042-303 m_cust: the cust operation cannot be performed when
        the target has a Cstate of "cust_setup".  It may be
        necessary to reset the target before retrying the
        operation.


0
 
woolmilkporcCommented:
OK,

first, the NIM server should always be on the same or higher level as the client with the highest level!

OK, restarting nimsh is most probably the right thing here!

You can't do another "cust" after a failed operation, unless you "reset" the client.

smitty nim_mac_op -> (select client) -> select "reset" -> "Deallocate ...": yes -> "Force": yes ->  Go!

Then retry "cust".

wmp  
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
sminfoAuthor Commented:
wmp,

Sorry, the NIM is:
[root@bibmnim:/cdrom] oslevel -s
7100-00-02-1041
(BIBMDES_CONT):[root] / -> oslevel -s
7100-00-00-0000

So, from the NIM server:
smitty nim_mac_op -> (select client) -> select "reset" -> "Deallocate ...": yes -> "Force": yes ->  Go!

No error.

So, I ran again the above update_all command from the client geting this error now:

Before command completion, additional instructions may appear below.

0042-001 nimclient: processing error encountered on "master":
   0042-001 nim: processing error encountered on "master":
   0042-303 m_cust: the cust operation cannot be performed when
        the target has a Cstate of "cust_setup".  It may be
        necessary to reset the target before retrying the
        operation.



0
 
woolmilkporcCommented:
Now that's crazy!

I often had this 0042-303  error, but it always (always!) disappeared after a reset + deallocate + force!

Are you really sure that reset was successful?

wmp

0
 
sminfoAuthor Commented:
MAybe useful..

From the NIM it's the actual status of the MACHINE:

bibmdes_cont:
   class          = machines
   type           = standalone
   connect        = nimsh (secure)
   platform       = chrp
   netboot_kernel = 64
   if1            = ent-Network1 bibmdes_cont 0
   cable_type1    = N/A
   Cstate         = customization is being performed
   prev_state     = ready for a NIM operation
   Mstate         = currently running
   lpp_source     = aix71tl0sp2lpp
   nim_script     = nim_script
   cpuid          = 0009EACAD400
   control        = bibmdes_cont
0
 
sminfoAuthor Commented:
Yes, I ran again the reset as you said and it was OK..


So, I did another test, from the NIM:
[root@bibmnim:/cdrom] nim -o cust -a lpp_source=aix71tl0sp2lpp -a fixes=update_all bibmdes_cont

0042-001 nim: processing error encountered on "master":
   0042-006 m_cust: (From_Master) connect Error 0

0042-008 nimsh: Request denied - BIBMNIM0042-008 nimsh: Request denied - BIBMNIM

SO, I repeat the same above update_all command from the client:
and get the same error:
0042-001 nimclient: processing error encountered on "master":
   0042-001 nim: processing error encountered on "master":
   0042-006 m_cust: (From_Master) connect Error 0

0042-008 nimsh: Request denied - BIBMNIM

GGRRRRRRRRRRRRRRRRRRR :-)


Also, there's a firewall in the middle of both AIXs. May be is blocking some ports.. really don't know..
0
 
sminfoAuthor Commented:
wmp, look what is on the nimlog omn the client when I ran the above command from the NIM:

Thu May 12 15:36:24 2011        file descriptor is 5
Thu May 12 15:36:24 2011        file descriptor is : 5
Thu May 12 15:36:24 2011        family is : 24 (AF_INET6)
Thu May 12 15:36:24 2011        source port is : 1023
Thu May 12 15:36:24 2011        source addr is : ::ffff:172.16.32.98
Thu May 12 15:36:24 2011        source hostname is: BIBMNIM
Thu May 12 15:36:24 2011        getting 2nd port
Thu May 12 15:36:24 2011        count equals 0
Thu May 12 15:36:24 2011        count equals 1
Thu May 12 15:36:24 2011        count equals 2
Thu May 12 15:36:24 2011        count equals 3
Thu May 12 15:36:24 2011        count equals 4
Thu May 12 15:36:24 2011         got stderr port 1022
Thu May 12 15:36:24 2011        success: we got 1st write query is 0
Thu May 12 15:36:24 2011        success: we got 2nd write local id is 0009EACAD400
Thu May 12 15:36:24 2011        success: we got 3rd write remote id is 0009EABAD400
Thu May 12 15:36:24 2011        success: we got 4th write command is /usr/lpp/bos.sysmgt/nim/methods/c_nimpush "/usr/bin/lslpp" "-lcIqOu" "bos.sysmgt.nim.client"
Thu May 12 15:36:24 2011        passing OpenSSL setting of 0
Thu May 12 15:36:24 2011        error: remote value passed, 'BIBMNIM', does not match environment value 'bibmnim


Any idea??
0
 
woolmilkporcCommented:
Er,

could it be that you've setup your NIM master ("bibmnim" , I assume?) using CAPITAL letters somewhere?

I really can't tell you where this migt have happened (network? SSL?)

Please have a look!

wmp
0
 
sminfoAuthor Commented:
Wmp..

That's it.. The hostname entry in the /etc/hosts file was in capital. I changed it and it's working.
Just one detail. Once the client has been setup you have to  do two things, (at least for me :-))
1- Restart nimsh on the client.
2- Forced d eallocate , (as you said) all resources on the MACHINE.

:-)

This NIM's gonna kill me!!!!!!!!

Thanks again..
0
 
woolmilkporcCommented:
1) Restarting nimsh is only needed once after switching to SSL. That's an old bug. I thought it was already fixed somewhere in 5.3, but perhaps there's been a regression with AIX 6.

2) Reset/deallocate/force is only needed after a failed NIM operation before attempting a new operation - but then it's mandatory.

Thx again for the points! Looking forward to your next case. Did you succeed in setting up WLM (not to be confused wih WPAR)?

Cheers: The wmp
0
 
sminfoAuthor Commented:
Hi wmp,

Yes, I took a look to WLM, but not it's mot clear for me yet... but I used nice to rum my mksysb... thanks.
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

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