Skip Navigation Links | |
Exit Print View | |
![]() |
man pages section 7: Device and Network Interfaces Oracle Solaris 10 1/13 Information Library |
- Serial Optical Controller for Fibre Channel Arbitrated Loop (SOC+) device driver
socal@sbus-slot,0
The Fibre Channel Host Bus Adapter is an SBus card which implements two full duplex Fibre Channel interfaces. Each Fibre Channel interface can connect to a Fibre Channel Arbitrated Loop (FC-AL).
The socal device driver is a nexus driver and implements portions of the FC-2 and FC-4 layers of FC-AL.
ELF Kernel Module
See attributes(5) for descriptions of the following attributes:
|
ANSI X3.230-1994, Fibre Channel Physical and Signalling Interface (FC-PH)
ANSI X3.272-1996, Fibre Channel Arbitrated Loop (FC-AL)
Fibre Channel Private Loop SCSI Direct Attach (FC-PLDA)
The messages described below may appear on system console in addition to being logged.
On the console, these messages are preceded by:
socal%d: port %a
where %d is the instance number of the socal controller and %a is the port on the host adapter.
The Fibre Channel loop is now online.
The Fibre Channel loop is now offline.
Move soc+ card to another slot.
Driver did not attach, devices will be inaccessible.
Driver did not attach, devices will be inaccessible.
Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
Driver was unable to map device registers; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
Driver was unable to map device registers; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
Driver was not able to add the interrupt routine to the kernel. Driver did not attach to device, devices will be inaccessible.
Driver was unable to access device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
Driver was unable to write device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
Driver was unable to verify device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible.