Saturday 9 March 2013

Solaris 10 branded zone - NIC vanishes after reboot


I’ve migrated a non-global Solaris 10 zone to a Solaris 10 branded zone. I made the zone an exclusive IP zone (samba’s AD integration i.e. winbind doesn’t work if I use a shared IP). However, when I rebooted the container, the NIC configuration got lost. I have to reconfigure it with ifconfig. Using /etc/hostname.net0 does not work. Seems to be no way to keep the config across reboots.

The problem is consistent across all the Solaris10 zones I’ve migrated.

Other symptoms: Physical network service doesn't start:

bash-3.2# svcs -xv
svc:/network/physical:default (physical network interfaces)
 State: maintenance since Wed Feb 27 13:31:54 2013
Reason: Start method exited with $SMF_EXIT_ERR_CONFIG.
   See: http://sun.com/msg/SMF-8000-KS
   See: man -M /usr/share/man -s 1M ifconfig
   See: /var/svc/log/network-physical:default.log
Impact: 6 dependent services are not running:
        svc:/milestone/network:default
        svc:/system/webconsole:console
        svc:/network/shares/group:default
        svc:/network/samba:default
        svc:/network/ssh:default
        svc:/network/winbind:default
bash-3.2#

Feedback from Oracle:
Bug 15802435 - SUNBT7182449 zonecfg configure-allowed-address does not work in solaris10 zones which is a regression of the fix for software defect Bug 15749195 - SUNBT7102421 allowed-address not configured at first boot after unconfiguration The latter has been made available with Solaris 11.1, which explains, why you didn't see the issue with Solaris 11.0 SRU 13.4 or earlier. Unfortunately there is no fix available officially for bug 15802435, yet.
Related error message (on the global zone):
Mar 12 14:02:53 hostname dlmgmtd[63]: [ID 183745 daemon.warning] Duplicate links in the repository: net0

EDIT: I updated to the latest patches. I've checked and now this problem is a thing of the past! Well done, Oracle, well done.

No comments:

Post a Comment

Note: only a member of this blog may post a comment.