Solstice SyMON 1.3 User's Guide
  Search only this book
Download this book in PDF

Config Reader

B

The Config Reader determines the configuration of a machine, along with the status of its components. Its output is depicted in these consoles:
  • Physical View
  • Logical View
Tables B-2 through B-4 list the Config Reader data hierarchy. Use the information in this appendix if you want to write event rules that monitor the output of the Config Reader.

Terminology

The terms in Table B-1 are used to explain the information in Table B-2.
Table B-1
PropertyTermDefinition
PinstanceThis is a decimal or hexadecimal number acquired by reading /etc/path_to_inst, which maps physical device names to the instance number; refer to the man page for more information.
Pupa-portidThis property exists for SBus and CPU units. Each board has two CPU slots, A and B, which have unique numbers. For example, board 0 has upa-portid 0 and 1, and board 1 has upa-portid 2 and 3, and so on. portid/2 = slot number.
Pupa-midThis property is displayed for fhc, sbus, cpu-unit and central modes. It is always equal to upa-portid.
PhpuThis stands for hot plugable unit. You can replace hot plugable units without powering the system down.

Data Hierarchy

These abbreviations are used in the following tables in this chapter:
  • I = Integer
  • H = Hexadecimal
  • A = ASCII
Table B-2 lists the Config Reader data hierarchy for the Ultra Enterprise 3000, 4000, 5000, and 6000 systems that describe the configuration of the host. They can also be electrical entities. For example, the system_3v node is not a physical entity but is the input voltage to system boards.
Each node has a set of properties that describe its state; for example, if an LED is on or off, or if a voltage level is acceptable. The node and its properties are grouped together in Table B-2 in the following order:
  • The first column contains the node or property name.
  • The second column specifies whether the parameter is a node (N) or a property (P). A node in the hierarchy is a starting point for a branch of the hierarchy. All properties that belong to a node appear below the node and are marked with a P. For example, cpu.busy and cpu.user fall under the cpu node. The node and its properties are grouped together.
  • The third column contains the data type of the property. Note that the Config Reader always encloses the value of a property between double quotes (" ").
  • The fourth column lists the default value, which is not listed for every entry.
  • The last column explains the meaning of the node or property.

Ultra Enterprise 3000, 4000, 5000, and 6000

The following table is the Config Reader data hierarchy for the Ultra Enterprise 3000, 4000, 5000, and 6000 server systems.
Table B-2 Config Reader Data Hierarchy for the Ultra Enterprise 3000, 4000, 5000,
and 6000 Systems
NameNode or PropertyTypeDefault ValueDescription
AC_PSN


statusP"A""OK"/"FAIL"AC connector and switch
SUNW,fasN

Host Bus Adapter driver
tape_countP"I"Number of tapes attached to a particular slot
disk_countP "I"Number of disks attached to a particular slot
instance*P "I"
device_type*P "A""scsi"
SUNW,ffb(N)N

UPA color frame buffer and graphics accelerator (N) = instance number
* Refer to Table B-1.



Table B-2 Config Reader Data Hierarchy for the Ultra Enterprise 3000, 4000, 5000,
and 6000 Systems (Continued)
NameNode or PropertyTypeDefault ValueDescription
bufferP"A""Single"/"Double"
3DRAMP"A"3-D RAM model and version number
DACP"A"Revision of DAC chip
FBC_versionP"H "
revisionP"A"Revision of FFB board
instance*P"I"
upa-portid*P"I"
widthP"I"Pixels
heightP"I"Pixels
device_typeP"A""display"
modelP"A"
SUNW,hmeN

Fast Ethernet device driver
instance*P"I"
device_typeP"A""network"
SUNW,leoN

Double-buffered SBus color frame buffer and graphics accelerator
instance*P"I"
widthP"I"Pixels
heightP"I"Pixels
modelP"A"
device_typeP"A""display"
SUNW,pln(N)N

SPARCstorage Array
disk_countP"I"Number of attached disks
device_typeP"A"SPARCstorage Array
instance*P"I"
* Refer to Table B-1.



Table B-2 Config Reader Data Hierarchy for the Ultra Enterprise 3000, 4000, 5000,
and 6000 Systems (Continued)
NameNode or PropertyTypeDefault ValueDescription
SUNW,rtvcN

Real-time video capture
instance*P "I"
modelP
SUNW,soc(N)*N

Serial Optical Controller device driver; (N) = instance number
device_typeP"A"See DescriptionSerial Optical Channel Processor Host Adapter
instance*P"I"
modelP
soc-wwnP"I"World Wide Web device name
port-wwnsP"I"
board(N)N

(N) = board number
hpuP"A""yes"Hot plug unit
temperatureP"A""N C< " where N is an integer
state=P"A". "active:" Normal state for boards after the operating system has booted . "disabled:" Disabled by the PROM because it was listed in the 'disabled-board-list' property in the options node . "failed:" A board that is failed by POST and powered off in the testing phase of PROM operations . "hot-plug:" Intermediate state after a board is hotplugged . "low-power:" The state that hotplug boards are in before they are removed . "unknown:" Unused
fruP"A""yes"Field replaceable unit
* Refer to Table B-1.



Table B-2 Config Reader Data Hierarchy for the Ultra Enterprise 3000, 4000, 5000,
and 6000 Systems (Continued)
NameNode or PropertyTypeDefault ValueDescription
typeP"A"See DescriptionOne of: clock, cpu/memory, Dual SBus I/O, disk-board, SBus/FFB I/O, pci I/O
board-numP"I"For example, Ultra-Enterprise 3000: up to 4
memory_sizeP "A""N MB," N is an integer (CPU/memory boards only)
cdromN


mounted_partitionsP"I"
device_typeP"A""CD-ROM"
nameP"A"For example c0t6d0
instance*P"I"
centralN

Only exists under the clock board
instance*P"I"
upa-mid*P"I"
clock-boardN


instance*P"I"
cpu-unit(N)N

(N) = unit
fruP"A""yes"Field replaceable unit
clock-frequencyP"A"N MHz, where N is an integer
cpu-typeP"A"For example sparc
statusP"A""online"/"offline"
modelP"A"
processor-idP"I"2*board number (+1 if cpu-unit=B )
unitP"A""A" or "B" (each board takes two CPUs)
upa-mid*P"I"
* Refer to Table B-1.



Table B-2 Config Reader Data Hierarchy for the Ultra Enterprise 3000, 4000, 5000,
and 6000 Systems (Continued)
NameNode or PropertyTypeDefault ValueDescription
upa-portid*P"I"

icache-size*P"A"
"N KB" or "N MB," where N is a fixed point number
dcache-sizeP"A"
"N KB" or "N MB," where N is a fixed point number
ecache-sizeP"A"
"N KB" or "N MB," where N is a fixed point number
device_typeP"A""cpu"
board#P"A"Board number on which this node resides
disk_fanN

Exists only in Ultra Enterprise 3000 systems
hpuP "A""yes"Hotplug unit?
statusP "A""OK"/"FAIL"
fanN

In the Ultra Enterprise 4000, 5000, and
6000, the AC_PS has a fan node
statusP "A""OK"/"FAIL"
fhcN

Fire Hose controller; one associated with each AC; contains board CSR, which controls on-board devices such as PROMs, RAM and UARTs
instance*P "I"
upa-mid*P "I"
version#P "I"Version number
board#P "I"Board number on which this node resides
modelP "A"Address controller
acN


* Refer to Table B-1.



Table B-2 Config Reader Data Hierarchy for the Ultra Enterprise 3000, 4000, 5000,
and 6000 Systems (Continued)
NameNode or PropertyTypeDefault ValueDescription
instance*P "I"

version#P "I"

modelP "A"

device_typeP "A""memory-controller"
eepromN

Electrically programmable read-only memory
modelP"A"
environmentN
instance*P"I"
flashpromN


instance*P"I"
modelP"A"
sbus-speedP


keyswitch



positionP"A""Normal Mode," "Secure mode," or
"Diagnostic mode"
led(N)N

Power supplies have two LEDs: green (off = no power) and amber (on=FAIL). Boards have three LEDs. Refer to the Ultra Enterprise Maintenance Manual for LED combinations.
led-numP"I"1, 2, or 3
stateP"A""on"/"off"
peripheral_PS(N)N

184w power supply for SCSI peripherals, additional power for boards in system and pre-charge power for hot plugging boards.
hpuP"A" "yes"Hot plug unit
* Refer to Table B-1.



Table B-2 Config Reader Data Hierarchy for the Ultra Enterprise 3000, 4000, 5000,
and 6000 Systems (Continued)
NameNode or PropertyTypeDefault ValueDescription
statusP"A""OK"/"FAIL"
unit#P "I"Unique number of this power supply
fruP"A" "yes"Field replaceable unit
nf(N)N

SBus FDDI Driver
etherP"A"Ethernet address; for example 8:0:20:75:af:f8
inetP "I"Internet address; for example 129.146.65.45
symbolP"A"Network name corresponding to the inet address above
nameP"A"Driver name; for example, nf0
instance*P"I"
modelP"A"
device_typeP"A""network"
power_supply(N)N

300w board supply, (N) = unit number
hpuP"A""yes"Hot plug unit
statusP"A""OK"/"FAIL"
unit#PUnique number of the power supply
fruP"A""yes"Field replaceable unit
sbus(N)N

Peripheral bus; N=instance number
instance*P"I"
upa-portid*P"I"
upa-mid*P"I"
version#*P
board#P"A"Board number on which this node resides
* Refer to Table B-1.



Table B-2 Config Reader Data Hierarchy for the Ultra Enterprise 3000, 4000, 5000,
and 6000 Systems (Continued)
Node or Name...........Property TypeDefault ValueDescription
device_type*.......P..."A"

model...........P

"sbus"
network_count......P..."I"
Network devices attached to this SBus
remote_console......N

status=..........P..."A""Enabled/Disabled"
sd(0)...........N

fru............P..."A"

mounted_partitions...P..."I"

device_type........P..."A"

"yes"Field replaceable unit
name............P..."A"
instance.........P..."I"

"disk" for example, "c0t0d0"
The following data, which is a continuation of the properties that go with the sd(0) node (above) is the output of Config Reader if the disk has mounted partition.
name............P..."A"
For example, c0t0d0s0
percent_used.......P..."I"
For example, 49%
total_bytes........P..."I"
n Mbytes or n Kbytes
avail_bytes........P..."I"
n Mbytes or n Kbytes
used_bytes........P..."I"
n Mbytes or n Kbytes
device_type*.......P..."A"
Partition
export name.......P..."A"
For example, c0t0d0s7
simm(0)..........N

board_reference_number P..."A"



slot............P... "I"

size............P..."A"


CPU/memory slot where this SIMM resides
type............P..."A"
DRAM
* Refer to Table B-1.

Table B-2 Config Reader Data Hierarchy for the Ultra Enterprise 3000, 4000, 5000,
and 6000 Systems (Continued)
NameNode or PropertyTypeDefault ValueDescription
fruP"A""yes"Field replaceable unit
sramN

Static RAM
instance*P"I"
st(N)N

SCSI tape, N is the instance number
fruP"A""yes"Field replaceable unit
modelP"A"For example, Exabyte EXB-8500 8mm
nameP"A"For example, /dev/rmt/0n
statusP"A""OK/FAIL"
device_typeP"A""tape drive"
instance*P "I"
systemN

Contains general properties of the system
total_processorsP"I"Number of processors in the machine
total_memoryP "A"N MB, where N is an integer
total_disksP "I"
total_tape_devicesP "I"
sample numberP "I"Since daemon started on server
timestampP "A"For example Tue Mar 26 10:33:08 1996
hostnameP "A"Machine name
OSP"A"Value as returned by uname(2) in release field
OS_versionP"A"Value as returned by uname(2) in release field
architectureP"A"For example, sparc, mc68030, m32100, or 8386
machineP"A"For example sun4u
* Refer to Table B-1.



Table B-2 Config Reader Data Hierarchy for the Ultra Enterprise 3000, 4000, 5000,
and 6000 Systems (Continued)
Node or Name...........Property TypeDefault ValueDescription
platform.........P..."A"

serial_number......P..."I"

Value as returned by the
uname -i command
System_clock_frequency P..."A"
N MHz, where N is an integer
The following nodes are not physical entities. They are the output of different power supplies in the system that is used for purposes such as hotplugging and peripherals.
hot_plug_charges.....N

fru............P..."A" "no"Field replaceable unit
auxiliary_5v.......N

status...........P..."A""OK"/"FAIL"
fru............P..."A""no"Field replaceable unit
peripheral_12v

status...........P..."A""OK"/"FAIL"
fru............P..."A""no"Field replaceable unit
peripheral_12v_precharge N

status...........P..."A""OK"/"FAIL"
fru............P..."A""no"Field replaceable unit
peripheral_5v......N

status...........P..."A""OK"/"FAIL"
fru............P..."A""no"Field replaceable unit
peripheral_5vprecharge N

status...........P..."A""OK"/"FAIL"
fru............P..."A""no"Field replaceable unit
system_5v.........N

status...........P..."A""OK"/"FAIL"
fru............P..."A""no"Field replaceable unit
* Refer to Table B-1.

Table B-2 Config Reader Data Hierarchy for the Ultra Enterprise 3000, 4000, 5000,
and 6000 Systems (Continued)
NameNode or PropertyTypeDefault ValueDescription
system_5v_ prechargeN


statusP"A""OK"/"FAIL"
fruP"A""no"Field replaceable unit
system_3vN


statusP"A""OK"/"FAIL"
fruP"A""no"Field replaceable unit
system_3v_ prechargeN


statusP"A""OK"/"FAIL"
fruP"A""no"Field replaceable unit
* Refer to Table B-1.



SPARCserver 1000/1000E and SPARCcenter 2000/2000E

The following table is the Config Reader data hierarchy for the SPARCstation 1000/1000E and the SPARCcenter 2000/2000E.
Table B-3 SPARCserver 1000/1000E and SPARCcenter 2000/2000E Config Reader
Data Hierarchy
NameNode or PropertyTypeDefault ValueDescription
QLGC, isp(N)N

(N) = unit number
device_typeP"A""SCSI controller"
disk_countP"I"
fruP"A""yes"Field replaceable unit
instance*P"I"
modelP"A"
tape_countP"I"
* Refer to Table B-1.



Table B-3 SPARCserver 1000/1000E and SPARCcenter 2000/2000E Config Reader
Data Hierarchy (Continued)
NameNode or PropertyTypeDefault ValueDescription
board(N)N

(N) = board number. This is a unique number ranging from 0 to the maximum number of boards per machine.
board-numP"I"
same as N, above
fruP"A""yes"Field replaceable unit
stateP"A"One of "Active," "disabled," or "failed.". "active:" Normal state for boards after the operating system has booted . "disabled:" Disabled by the PROM because it was listed in the 'disabled-board-list' property in the options node . "failed:" A board that is failed by POST and powered off in the testing phase of PROM operations.
typeP"A""cpu/memory/io"
cgsix(N)N

(N) = unit number
device_typeP"A""display"
instance*P"I"
modelP"A"
cpu-unit(N)N

(N) = unit number
board#P"I"Board number on which this node resides
clock-frequencyP"A""N MHz"
cpu-typeP"sparc"
device_typeP"cpu"
fruP"A""yes"Field replaceable unit
moduleP"A"
* Refer to Table B-1.



Table B-3 SPARCserver 1000/1000E and SPARCcenter 2000/2000E Config Reader
Data Hierarchy (Continued)
NameNode or PropertyTypeDefault ValueDescription
processor-idP"I"2*board number ( +1 if cpu-unit is "B")
sparc-versionP"I"
statusP"A""online"/"offline"
unitP"A""A" or "B" (each board takes two CPUs)
dma(N)N

(N) = unit number
instance*P"I"
modelP"A"
esp(N)N

(N) = unit number
chipP"A"
device_typeP"A""SCSI controller"
disk_countP"I"Number of disks attached to this node
instance*P"I"
tape_countP"I"Number of tapes attached to this node
io-unit(N)N


board#P"I"Board number on which this node resides
device-idP"I"
instance*P"I"
mem-unit board#N"I"
Board number on which this node resides
device-idP"I"
device_typeP"A""memory"
sizeP"A""N MB"
statusP"A""OK"/"FAIL"
* Refer to Table B-1.



Table B-3 SPARCserver 1000/1000E and SPARCcenter 2000/2000E Config Reader
Data Hierarchy (Continued)
NameNode or PropertyTypeDefault ValueDescription
le(N)N

(N) = unit number
aliasP
"le"
device_typeP
"network"
etherP
"8:0:20:74:30:43"
inetP
"129.146.235.47"
instance*P"I"
nameP"le0"
symbolP"pump"
lebuffer(N)N

(N) = unit number
instance*P"I"
modelP"A"
network_countP"I"
sbi(N)N

(N) = unit number
device_typeP"SBus card"
instance*P"I"
simm(N)N

(N) = unit number
group#P"I"
memory-typeP"RAM"
sizeP"32MB"
sd(N)N

(N) = disk number
device_typeP"disk"
fruP"A""yes"Field replaceable unit
instance*P"I"
mounted_partitionsP"I"
name="c1t3d0"P"A""N mbytes"Partition name
* Refer to Table B-1.



Table B-3 SPARCserver 1000/1000E and SPARCcenter 2000/2000E Config Reader
Data Hierarchy (Continued)
NameNode or PropertyTypeDefault ValueDescription
directory_nameP"A"
For example, / or /usr
avail_bytesP"A""N mbytes"
device_typeP"partition"You don't see these partitions unless mounted_partitions != 0
nameP"c1t3d0s0"You don't see these partitions unless mounted_partitions != 0
percent_usedP"A""N%"You don't see these partitions unless mounted_partitions != 0
total_bytesP"A""N mbytes"You don't see these partitions unless mounted_partitions != 0
used_bytesP"A""N mbytes"You don't see these partitions unless mounted_partitions != 0
slot(N)N

Slot where boards are physically
installed; (N) = unit number
slot-numP"I"
sdN

This node only exists in cases where no disks are attached to the SCSI controller
device_typeP"A""block"
fruP"A""yes"Field replaceable unit
stN

This node only exists in cases where no tapes are attached
device_typeP"A""byte"
fruP"A""yes"Field replaceable unit
systemN


OSP"A"Value as returned by uname(2) in the release field
OS_versionP"A"Value as returned by uname(2) in the release field
* Refer to Table B-1.



Table B-3 SPARCserver 1000/1000E and SPARCcenter 2000/2000E Config Reader
Data Hierarchy (Continued)
NameNode or PropertyTypeDefault ValueDescription
System_clock_frequencyP"A""N MHz"
architectureP"A"For example, sparc, mc68030, m32100, or 8386
hostnameP"A"Machine name
machineP"A""sun4d"
platformP"A"Value as returned by the
uname -i command
serial_numberP"I"
timestampP"A"
total_disksP"I"Number of disks attached to the machine
total_memoryP"A""N MB"
total_processorsP"I"Number of processors in the machine
total_tape_devicesP"I"Number of tapes attached to the machine
* Refer to Table B-1.



Ultra Enterprise 2 and 150 Systems

The following table is the Config Reader data hierarchy for the Ultra Enterprise 2 and 150 systems.
Table B-4
NameNode or PropertyTypeDefault ValueDescription
SUNW,fasN

Host Bus Adapter driver
tape_countP"I"
Number of tapes attached to a slot
disk_countP "I"
Number of disks attached to a slot
instance*P "I"
device_type*P "A""scsi"
* Refer to Table B-1.



Table B-4 (Continued)
NameNode or PropertyTypeDefault ValueDescription
SUNW,ffb(N)


UPA color frame buffer and graphics accelerator (N) = instance number
bufferP"A""Single"/"Double"
3DRAMP"A"3-D RAM model and version number
DACP"A"Revision of DAC chip
FBC_versionP"H "
revisionP"A"Revision of FFB board
instance*P"I"
upa-portid*P"I"
widthP"I"Pixels
heightP"I"Pixels
device_typeP"A""display"
modelP"A"
SUNW,hmeN

Fast Ethernet device driver
instance*P"I"
device_typeP"A""network"
SUNW,leoN

Double-buffered SBus color frame buffer and graphics accelerator
instance*P"I"
widthP"I"Pixels
heightP"I"Pixels
modelP"A"
device_typeP"A""display"
SUNW,pln(N)N

SPARCstorage Array
disk_countP"I"Number of attached disks
device_typeP"A"SPARCstorage Array
* Refer to Table B-1.



Table B-4 (Continued)
NameNode or PropertyTypeDefault ValueDescription
instance*P"I"

SUNW,rtvcN

Real-time video capture
instance*P "I"
modelP
SUNW,soc(N)*N

Serial Optical Controller device driver; (N) = instance number
device_typeP"A"See DescriptionSerial Optical Channel Processor Host Adapter
instance*P"I"
modelP
soc-wwnP"I"World Wide Web device name
port-wwnsP"I"
system-boardN


state=P"A""active:" Normal state for boards after the operating system has booted "unknown:" Unused
fruP"A""yes"Field replaceable unit
board-numP"I"Always 1.
memory_sizeP "A"N MB, where N is an integer (CPU/memory boards only)
cdromN


mounted_partitionsP"I"
device_typeP"A"CD-ROM
nameP"A"For example, c0t6d0
instance*P"I"
cpu-unit(N)N

(N) = unit
fruP"A""yes"Field replaceable unit
* Refer to Table B-1.



Table B-4 (Continued)
NameNode or PropertyTypeDefault ValueDescription
clock-frequencyP"A"
N MHz, where N is an integer
cpu-typeP"A"
For example, sparc
statusP"A""online"/"offline"
modelP"A"
processor-idP"I"0 or 1 (only 0 possible on the Ultra Enterprise 150)
unitP"A""A" or "B" (only on the Ultra Enterprise 2)
upa-mid*P"I"
upa-portid*P"I"
icache-size*P"A"N KB or N MB, where N is a fixed point number
dcache-sizeP"A"N KB or N MB, where N is a fixed point number
ecache-sizeP"A"N KB or N MB, where N is a fixed point number
device_typeP"A""cpu"
nf(N)N

SBus FDDI Driver
etherP"A"Ethernet address; for example, 8:0:20:75:af:f8
inetP "I"Internet address; for example, 129.146.65.45
symbolP"A"Network name corresponding to the inet address above
nameP"A"Driver name; for example. nf0
instance*P"I"
modelP"A"
device_typeP"A""network"
* Refer to Table B-1.



Table B-4 (Continued)
Node or Name..........Property TypeDefault ValueDescription
sbus(N).........N

instance*........P..."I"

upa-portid*.......P..."I"

upa-mid*........P..."I"

version#*........P


Peripheral bus; N=instance number
device_type*......P..."A"

model..........P

"sbus"
network_count.....P..."I"
Network devices attached to this SBus
sd(0)..........N

fru...........P..."A"

mounted_partitions..P..."I"

device_type......P..."A"

"yes"Field replaceable unit
name...........P..."A"
instance........P..."I"

"disk" for example, c0t0d0
The following data, which is a continuation of the properties that go with the sd(0) node (above), is the output of Config Reader if the disk has mounted partition.
name...........P..."A"
For example, c0t0d0s0
percent_used......P..."I"
For example, 49%
total_bytes......P..."I"
n Mbytes or n Kbytes
avail_bytes......P..."I"
n Mbytes or n Kbytes
used_bytes.......P..."I"
"n Mbytes or n Kbytes
device_type*......P..."A"
"partition"
export name......P..."A"
For example, c0t0d0s7
simm(N).........N
N is SIMM instance.
slot...........P... "I"
CPU/memory slot where this SIMM resides
* Refer to Table B-1.

Table B-4 (Continued)
NameNode or PropertyTypeDefault ValueDescription
sizeP"A"

typeP"A"
"dram"
fruP"A""yes"Field replaceable unit
board-reference-numberP"A'Address of simm on board.
st(N)N

SCSI tape, N is the instance number
fruP"A""yes"Field replaceable unit
modelP"A"For example, Exabyte EXB-8500 8mm
nameP"A"For example, /dev/rmt/0n
statusP"A""OK/FAIL"
device_typeP"A""tape drive"
instance*P "I"
systemN

Contains general properties of the system
total_processorsP"I"Number of processors in the machine
total_memoryP "A"N MB, where N is an integer
total_disksP "I"
total_tape_devicesP "I"
sample numberP "I"Since daemon started on server
timestampP "A"For example, Tue Mar 26 10:33:08 1996
hostnameP "A"Machine name
OSP"A"Value as returned by uname(2) in release field
OS_versionP"A"Value as returned by uname(2) in release field
architectureP"A"For example, sparc, mc68030, m32100, or 8386
machineP"A"For example, sun4u
* Refer to Table B-1.



Table B-4 (Continued)
NameNode or PropertyTypeDefault ValueDescription
platformP"A"
Specific model of the hardware platform
serial_numberP"I"
System_clock_frequencyP"A"
N MHz, where N is an integer
sbus-board(N)N

The SBus board in slot N.
board-numP"I"
The number of the board in its particular SBus.
fruP"A""yes"Field replaceable unit
modelP"A"Board model--either a model name (if the board is identified by Solstice Symon) or the Open Boot PROM model string (for example, SUNW,501-2739).
stateP"A""active:" Normal state for boards after the operating system has booted.
leN

Ethernet device driver
instance*P"I"
device_typeP"A""network"
etherP"A"
Ethernet address; for example "8:0:20:75:af:f8"
inetP "I"Internet address; for example "129.146.65.45"
nameP"A"Driver name; for example, le0
device_typeP"A""network"
SUNW,fdtwoN

Floppy disk device
instance*P"I"
device_typeP"A""block"
fruP"A""yes"Field replaceable unit
* Refer to Table B-1.



If any component of a hierarchy path contains a period ( . ) in it, you may not be able to use the findlist function to find it. For example, if you search for the mount point /export/a0.test reported by the Config Reader via the path:
system.slot.board.io-unit.sbi.dma.esp.sd./export/a0.test,
the node will not be found.  Instead, use:
system.slot.board.io-unit.sbi.dma.esp.sd.* to find this node.