Originally posted by: LaurentOliva

I would like to define the "mgmt_profile2" attribute on my VIOS client defined into NIM server.

Here is how the client is defined right now :

$ lsnim -l my_vios1
my_vios1 :
   class          = management
   type           = vios
   connect        = nimsh
   platform       = chrp
   netboot_kernel = 64
   if1            = ent-Network76 my_vios1 0
   cable_type1    = tp
   mgmt_profile1  = hmc1 1 my_cec1
   Cstate         = ready for a NIM operation
   prev_state     = not running
   Mstate         = currently running
   cpuid          = xxxxxxxx
   Cstate_result  = success
 

$ nim -o change -a mgmt_profile2="hmc2 1 my_cec2" my_vios1

0042-001 nim: processing error encountered on "master":
   0042-130 m_chvios: "mgmt_profile" cannot be specified as an attribute
        for this operation

        ** Use lsnim -q <operation> <object name> or
           lsnim -q <operation> -t <type> to list required and optional
           resources and attributes for a particular NIM operation.
 

I can perform this operation on "regulars" nim client, here how i declare them :

$ lsnim -l my_server1
my_server1:
   class          = machines
   type           = standalone
   connect        = nimsh
   platform       = chrp
   netboot_kernel = 64
   if1            = ent-NetworkXX my_server1 F2XXXXXXXX15
   if2            = ent-NetworkXX my_server1 F2XXXXXXXX16
   cable_type1    = N/A
   cable_type2    = N/A
   mgmt_profile1  = hmc1 25 my_cec1
   mgmt_profile2  = hmc2 25 my_cec2
   Cstate         = ready for a NIM operation
   prev_state     = not running
   Mstate         = currently running
   cpuid          = 00F6BA3A4C00
   Cstate_result  = success
 

My NIM server is up_to_date :

7100-02-02-1316

Originally posted by: GarlandJoseph

i think this is working as designed or not-designed for vios servers.  Why wouldn't you use updateios?

Originally posted by: LaurentOliva

My goal is to define the two HMCs that are connected to CECs where my VIOs resides.

I can do that for standalone objects but not for the VIOs.

It seems that the integration of vios objects in NIM need a lot of fixes, before being usable in production.