Paul,
If you are using NWAM for networking (versus DefaultFixed) then you
do not setup naming via normal channels. Instead you must use netcfg and
setup a NWAM location and enable that. The location will then proceed to
configure naming, when it is in use.
See item #2, 2a, 2b, 2c in my FAQ. It has the links to the various NWAM
documents and the explanations you are seeking.
https://stbeehive.oracle.com/teamcollab/wiki/Solaris+Naming:Naming+to+SMF+%28nss2smf%29+FAQ
Doug.
On 08/11/11 00:38, Jan Damborsky wrote:
Hi Paul,
please see my response in line.
Thank you,
Jan
On 08/11/11 01:11, Paul de Nijs wrote:
All,
I've been struggling with the sc_profiles to get my network interface
plumbed up after the OS installation (build 170 and up ?)
I hope someone can help me. There is not much hair left on my scull ;-(
How the heck can I make that work in b 170 and up. Everything worked
fine before b170, having this on the sc profile:
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE service_bundle SYSTEM
'/usr/share/lib/xml/dtd/service_bundle.dtd.1'>
<service_bundle name="system configuration" type="profile">
<service name="network/physical" type="service" version="1">
<instance name="nwam" enabled="true" />
<instance name="default" enabled="true" />
</service>
</service_bundle>
In the examples for 170 is see:
<?xml version='1.0'?>
<!DOCTYPE service_bundle SYSTEM
"/usr/share/lib/xml/dtd/service_bundle.dtd.1">
<service_bundle type="profile" name="system configuration">
<service name="network/physical" version="1">
<instance name="default" enabled="true">
<property_group name='netcfg' type='application'>
<propval name='active_ncp' type='astring' value='Automatic'/>
</property_group>
</instance>
</service>
</service_bundle>
I assumed that it would plumb up the interface I initially booted
from and initialize that interface from DHCP. Well, that is not the
case ...
What do I need to do to have the same behavior as before build 170 ?
No special steps are required modulo changing SC profile -
and SC profile above looks correct.
Could you please verify if profile was correctly applied and
if nwam is indeed controlling network configuration on that system ?
# svcprop -p netcfg/active_ncp network/physical:default
Automatic
# pgrep nwamd
100
#
If nwam is up and running on your system, then I may recommend
to ping networking guys about why it does not bring up the network
as expected.
Please don't tell me that I need to define a interface as described
in <image_location>/auto_install/sc_profiles/static_network.xml
No it's not needed. Automatic network configuration (via nwam(5)) is
still available in 170+.
Because I really don't know the interface name before I do the
installation, like eri0/e1000g0/nxge0/bge0 or whatever.
Also I don't want to use the "derived manifest", since that implies
that I have to do something by hand after the installation.
There MUST be a way to make this work as it used to work.
Then there is also another problem I see, like setting up NIS
(domainame/nsswitch.conf):
Pulling Doug into the loop - Doug do you happen to know what
Paul may be doing wrong as far as NIS configuration goes ?
If I include the following sc_profiles:
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE service_bundle SYSTEM
'/usr/share/lib/xml/dtd/service_bundle.dtd.1'>
<service_bundle name="system configuration" type="profile">
<service name="network/nis/domain" version="1">
<instance name="default" enabled="true">
<property_group name="config" type="application">
<propval name="domainname" type="hostname" value="SAE.West.Sun.COM" />
<propval name='ypservers' type='host' value='minister minister196
saegw1 saegw1-196 saegw2 saegw2-196 onager onager196'/>
</property_group>
</instance>
</service>
</service_bundle>
and
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE service_bundle SYSTEM
'/usr/share/lib/xml/dtd/service_bundle.dtd.1'>
<service_bundle name="system configuration" type="profile">
<service name="system/name-service/switch" type="service" version="1">
<property_group name="config" type="application">
<propval name='host' type='astring' value='files nis dns' />
<propval name='password' type='astring' value='files nis' />
<propval name='group' type='astring' value='files nis' />
<propval name='network' type='astring' value='files nis' />
<propval name='netmask' type='astring' value='files nis' />
<propval name='automount' type='astring' value='files nis' />
<propval name='alias' type='astring' value='files nis' />
<propval name='printer' type='astring' value='user nis' />
<propval name='auth_attr' type='astring' value='user nis' />
<propval name='prof_attr' type='astring' value='user nis' />
</property_group>
</service>
</service_bundle>
They all create the needed files (/etc/defaultdomain,
/var/yp/binding<domainname>/ypservers, and /etc/nsswitch.conf)
But if I plumb up my network like I used to do
(/etc/network.<interface> with a IP address), add my hostname in the
/etc/hosts and reboot, my /etc/nsswitch.conf resets to the
"nsswitch.files" configuration, and I really cannot change the
"system/name-service/switch" properties. not even svccfg apply
/etc/svc/profile/<nsswitch_confg>.xml (the saved xml file used for
the installation) works anymore.
Doing the stuff by hand:
svccfg <<- EOF
select system/name-service/switch
setprop config/password=astring: "files nis"
setprop config/group=astring: "files nis"
setprop config/host=astring: "files nis dns"
setprop config/ipnode=astring: "files nis dns"
setprop config/network=astring: "files nis"
setprop config/netmask=astring: "files nis"
setprop config/alias=astring: "files nis"
setprop config/automount=astring: "files nis"
setprop config/printer=astring: "user nis"
setprop config/user_attr=astring: "user nis"
select system/name-service/switch:default
refresh
quit
EOF
works, but after a reboot, it's all default again.
Please, can someone tell me what I missed ?
Thanks
Paul
--
Paul de Nijs | Principal Sales Consultant, HPC Benchmark Engineer |
+1.503.617.8572
Oracle HPC Sales Support
3295 NW 211th Terrace | Hillsboro, OR 97124-7110
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
