TR(4S) — DEVICES AND NETWORK INTERFACES
NAME
tr − Sun Token Ring network interface
CONFIG-- Sparcstation 1 SYSTEM
device-driver tr # TMS380 token ring
AVAILABILITY
This interface is only available with the Sun Token Ring SBus (TRI/S) controller product. Refer to the Sun TRI/S Installation and Administration Guide for information on how to install this product.
DESCRIPTION
The SBus based Sun TRI/S controller provides access to a 4/16 Mb/s shielded twisted pair token ring local area network. This controller runs on firmware that is downloaded from the onboard EPROM. The TRI/S driver (TR) supports transmission and reception of data packets conforming to the 802.2 Logical Link Control protocol (RFC 1042). The driver also supports Source Routing as specified in 802.5 Token Ring protocol. A compile-time option is provided to either turn on or off the source route feature. When source routing is disabled, packets addressed to the station will still be received. In addition, nit_if(4N) provides a streams access to the token ring interface that can bypass the standard protocol layers.
The driver supports general network and controller-specific IOCTLs. Arguments are passed in the standard way, using unions to the ifreq structure. For a general description of network interfaces, see if(4N).
SunNet Controller Management
The following ioctl calls may be used to manipulate network interfaces. Unless specified otherwise, the request takes an ifreq structure as its parameter. The ioctl’s are common with ethernet.
SIOCGIFADDRGet interface address.
SIOCSIFADDRSet interface address.
SIOCADDMULTIAdd multicast address.
SIOCDELMULTIDelete multicast address.
SIOCSIFFLAGSSet new flags.
SEE ALSO
arp(4P) etherfind(8C) if(4N) ifconfig(8C) inet(4F) netstat(8C) ping(8C)
DIAGNOSTICS/MESSAGES
The following group of six messages pertain to initial bring-up of the ring. If an ifconfig is successful none of these messages will be observed. Otherwise, they are listed in the order in which they occur. Following are additional diagnostic messages. To find out what action needs to be taken on receiving these messages, please refer to the TRI/S Installation and Administration Guide.
tr%d: not used- SBus slot %d is a slave-only port
The token ring card has been installed in a non-DMA master slot.
tr%d: Bad token ring adaptor card: <02>
The internal Bring-up Diagnostics (BUD) on the TI TMS380 chip failed.
tr%d: Bad token ring adaptor card: <03>
The initialize command on the TI Eagle chip failed.
tr%d: Token ring adaptor insertion on to ring failed 3 times
Attempts to open the controller and insert into the ring failed three times.
tr%d: open <expression>
An open command to the adapter failed. The expression will indicate the phase of the open command or the particular error.
i)- tr%d open phase lobe media failure
ii)- tr%d open phase physical insertion failure
iii)- tr%d open phase address verification failure
iv)- tr%d open phase ring poll failure
v)- tr%d open phase request initialization failure
vi)- tr%d open command function failure
vii)- tr%d open command signal loss
viii)- tr%d open command timeout failure
ix)- tr%d open command ring failure
x)- tr%d open command ring beaconing
xi)- tr%d open command duplicate node address
xii)- tr%d open command request initialization
xiii)- tr%d open command remove received
tr%d: Initial receive or transmit command failed.
After opening the controller onto the ring, there was a failure of either the initial receive or transmit command.
tr%d: Ring up.
The ring is up and operational.
tr%d: ring down.
When the ring goes down due to a auto remove error, lobe wire fault, remove received or simply the user ifconfig-ing down the interface, this message is displayed.
tr%d: Bad token ring adapter card: <11>
Token ring adapter check status=0x%x
An adapter check interrupt was received indicating a serious problem with the controller. The controller will automatically be reinitialized. It is suggested that a full complement of diagnostics be run on the token ring controller. Below is a breakout of the meaning of the status:
Bit #
15- Controller parity error.
14 - DMA read abort.
13- DMA write abort.
12,11,3,2,1- Internal Eagle chip H/W problems.
5- Internal DMA underrun when transmitting onto the ring.
4- Internal DMA overrun when receiving from the ring.
Ring status: 0x%x.
This message is displayed when the adapter detects an unusual condition. Read only the two least significant bytes of the Ring Status. Please refer to the TRI/S Installation and Administration Guide to decode the bytes. Following this message, the messages below may appear.
tr%d: signal loss.
Indicates that the controller has detected a loss of signal on the ring.
tr%d: beaconing activity:xmiting or receiving beacon frames
Adapter has detected unusual occurence that requires beaconing activity.
tr%d: xmiting beacon frames
Adapter has detected unusual occurence that requires beaconing activity.
tr%d: open/short in cable.
Indicates that the controller has detected an open or short circuit between the adapter and the wiring concentrator.
tr%d: beacon auto removal.
Indicates that the adapter has failed the lobe wrap test and has deinserted from the ring.
tr%d: received Remove Ring Station MAC frame.
Indicates that the adapter has received a Remove Ring Station MAC frame and has deinserted from the ring.
tr%d: error counter overflow.
∗∗∗∗∗∗∗∗∗∗∗∗ START READ ERROR LOG DUMP ∗∗∗∗∗∗∗∗∗∗∗∗
line error= 0x%x burst error= 0x%x
fci error = 0x%xlost frame= 0x%x
recv congestion= 0x%xframe copy= 0x%x
token error = 0x%xdma bus error = 0x%x
One of the adapter’s error counters has overflowed to 255. These counters keep track of things such as line error, receive congestion, and lost frame error. For further explanation of these counters, please refer to the TRI/S Installation and Administration Guide.
tr%d: single station.
The controller is the only operational token ring station on the ring.
tr%d: MAC claim token frames detected.
This message indicates that the controller has observed Claim Token MAC frames on the ring.
Sun Release 4.1 — Last change: