unixpowered.com

Today I had a need to jumpstart SunFire V240 using network interface in one of its PCI slots. In order to do that I need to find the MAC address of that interface, preferably with least amount of hassle. There was no Solaris installed and all I had was ok prompt. So I took a quick look at device aliases:

{1} ok devalias
xnet2                    /pci@1d,700000/pci@1/SUNW,hme@0,1:dhcp,
xnet1                    /pci@1e,600000/pci@3/SUNW,hme@0,1:dhcp,
xnet                     /pci@1e,600000/pci@2/SUNW,hme@0,1:dhcp,
net3                     /pci@1d,700000/network@2,1
net2                     /pci@1d,700000/network@2
net1                     /pci@1f,700000/network@2,1
net                      /pci@1f,700000/network@2
cdrom                    /pci@1e,600000/ide@d/cdrom@0,0:f
ide                      /pci@1e,600000/ide@d
disk3                    /pci@1c,600000/scsi@2/disk@3,0
disk2                    /pci@1c,600000/scsi@2/disk@2,0
disk1                    /pci@1c,600000/scsi@2/disk@1,0
disk0                    /pci@1c,600000/scsi@2/disk@0,0
disk                     /pci@1c,600000/scsi@2/disk@0,0
scsi                     /pci@1c,600000/scsi@2
sc-control               /pci@1e,600000/isa@7/rmc-comm@0,3e8
ttyb                     /pci@1e,600000/isa@7/serial@0,2e8
ttya                     /pci@1e,600000/isa@7/serial@0,3f8
name                     aliases

Starting with first net* alias I did:

{1} ok cd /pci@1d,700000
{1} ok ls
f00f8dac network@1
f00b3274 network@2,1
f00acbf4 network@2
{1} ok cd network@1
{1} ok ls
{1} ok pwd
/pci@1d,700000/network@1
{1} ok .properties
assigned-addresses       82000810 00000000 00600000 00000000 00200000
82000830 00000000 00100000 00000000 00100000
d-fru-len                00000000
d-fru-off                0000e800
d-fru-dev                eeprom
s-fru-len                00000800
s-fru-off                0000e000
s-fru-dev                eeprom
compatible               pci108e,abba.11
pci108e,abba
pciclass,020000
pciclass,0200
reg                      00000800 00000000 00000000 00000000 00000000
02000810 00000000 00000000 00000000 00200000
02000830 00000000 00000000 00000000 00100000
address-bits             00000030
max-frame-size           00004000
device_type              network
name                     network
local-mac-address        00 03 ba 4d b3 3f
version                  Sun PCI Gigaswift Base-X FCode 2.6 01/09/27
phy-type                 pcs
board-model              501-5524
model                    SUNW,pci-ce
fcode-rom-offset         00000000
66mhz-capable
fast-back-to-back
devsel-speed             00000002
latency-timer            00000040
cache-line-size          00000010
max-latency              00000040
min-grant                00000040
interrupts               00000001
00000002
00000003
00000004
class-code               00020000
revision-id              00000011
device-id                0000abba
vendor-id                0000108e

The MAC address of the network interface is shown in local-mac-address field above. All it took then was following boot command to get jumpstart going:

{1} ok boot /pci@1d,700000/network@1 -v - install nowin Continue Reading

It seems that starting with Solaris 06/07 nfs4_domain is required in sysidcfg file, otherwise jumpstart will go interactive. You can force a value for example nfs4_domain=example.net or you can set it to be dynamic. In that case the value will be derived from the name service in use. Solaris 10 has nfsmapid daemon that maps numeric UID/GID to a string in format user@example.net.

If there is a domain mismatch between NFS4 client and server, the client will see files on the server owned by nobody. On the server syslog might log something like this:

Mar 3 15:13:14 ultra /usr/lib/nfs/nfsmapid[275]: [ID 300081 daemon.error] valid_domain: Invalid inbound domain name example.net..

In my case there was a typo in /etc/resolv.conf file at the end of domain entry. The entry contained trailing dot. This Sun document has all the useful info that might help troubleshooting similar problems with nfsmapid.

Continue Reading