Avinash K wrote:
> 
> 
> On 05/05/09 18:54, Sean McGrath wrote:
>> Avinash K stated:
>> <    Hi,
>> < <    Sorry forgot to attach the var logs. Below are the contents of 
>> the logs.
>> <    And also since it's in maintenance mode since pkg install, as 
>> mentioned I
>> <    am unable to create any install service.
>> < <    root at blr-v20z-1:~#
>> <    root at blr-v20z-1:~# cat 
>> /var/svc/log/system-install-server:default.log
>> <    [ May  5 12:37:40 Disabled. ]
>> <    [ May  5 12:37:40 Rereading configuration. ]
>> <    [ May  5 12:57:18 Stopping for maintenance due to 
>> administrative_request.
>> <    ]
>> <    [ May  5 12:57:18 Stopping for maintenance due to 
>> administrative_request.
>> <    ]
>> <    [ May  5 13:01:50 Disabled. ]
>> <    [ May  5 13:18:07 Stopping for maintenance due to 
>> administrative_request.
>> <    ]
>> <    [ May  5 13:18:07 Stopping for maintenance due to 
>> administrative_request.
>> <    ]
>> <    [ May  5 13:24:59 Leaving maintenance because clear requested. ]
>> <    [ May  5 13:24:59 Enabled. ]
>> <    [ May  5 13:24:59 Executing start method
>> <    ("/lib/svc/method/svc-install-server start"). ]
>> <    No install services are enabled. Incorrect configuration
>> < <    [ May  5 13:24:59 Method "start" exited with status 96. ]
>> <    [ May  5 13:25:37 Leaving maintenance because clear requested. ]
>> <    [ May  5 13:25:37 Enabled. ]
>> <    [ May  5 13:25:37 Executing start method
>> <    ("/lib/svc/method/svc-install-server start"). ]
>> <    No install services are enabled. Incorrect configuration
>> < <    [ May  5 13:25:37 Method "start" exited with status 96. ]
>> <    [ May  5 13:37:21 Leaving maintenance because clear requested. ]
>> <    [ May  5 13:37:21 Enabled. ]
>> <    [ May  5 13:37:21 Executing start method
>> <    ("/lib/svc/method/svc-install-server start"). ]
>> <    No install services are enabled. Incorrect configuration
>> < <    [ May  5 13:37:21 Method "start" exited with status 96. ]
>> <    [ May  5 13:38:41 Leaving maintenance because disable requested. ]
>> <    [ May  5 13:38:41 Disabled. ]
>> <    [ May  5 13:42:09 Enabled. ]
>> <    [ May  5 13:42:43 Executing start method
>> <    ("/lib/svc/method/svc-install-server start"). ]
>> <    No install services are enabled. Incorrect configuration
>> < <    [ May  5 13:42:44 Method "start" exited with status 96. ]
>> <    root at blr-v20z-1:~#
>> <    root at blr-v20z-1:~# installadm create-service -n sparc1 \ -s
>> <    /root/Desktop/osol-0906-111a-ai-sparc.iso <    
>> /export/aiserver/osol-0906-ai-sparc
>> <    NWAM is not disabled.  To disable, run # /usr/sbin/svcadm disable
>> <    svc:/network/physical:nwam
>> <    svc:/network/physical:default is not online.  Its current state is
>> <    disabled
>> <    To enable, run # /usr/sbin/svcadm enable 
>> svc:/network/physical:default
>> <    Automated Installations will not work with the current server 
>> network
>> <    setup.
>> <    Please check server network settings and try again.
>> <    The installadm SMF service (svc:/system/install/server:default) 
>> is no
>> <    longer online
>> <    because the last install service has been disabled or deleted.
>> <    root at blr-v20z-1:~#
>>
>>  The output from installadm isn't clear ?
>>
>>   'NWAM is not disabled.'
>>   'Automated Installations will not work with the current server 
>> network setup.'
>>
>>  You have nwam enabled, your install server (blr-v20z-1) needs to have
>>    a static IP address instead of a dynamic one.
>>
>>  The output from installadm isn't clear ?
>>
>>  AI working with NWAM is actually just fixed last Wednesday.  Though I 
>> don't
>>   think the updated packages are available yet.
>>   See: Bug 8346 AI should work with NWAM
>>   
> But previous time it had 2008.11 installed on it and the installadm was 
> working fine. Then also it had same IP and other configurations. So are 
> you suggesting that I need to wait till the build with the necessary fix 
> is released?
> Is there no workaround for the same? Will disabling nwam cause any 
> issues or solve the problem?
> 
> Regards,
> Avinash K

installadm has always required a static IP address and did not work correctly 
with nwam until the fix for 8346. You will either need to setup a static IP 
address for the server or wait for the fix for 8346 to be available. To use a 
static IP address you will need to disable nwam and manually set up a static IP 
address.

-evan

Reply via email to