Nortel Networks 5399 Thestatus word ! ~XXXX~, where XXXX arefour hexadecimal digits, decodes as follows:, The lowest nibble(bits 3 to 0) are a count of collisions during this transmission. For example:, The boot command display (using bfs) looks similar to this:

Nortel Networks 5399 Access Switch Hardware Installation Guide
Chapter 3 ROMMo nitor Commands
3-10
Thestatus word “! ~XXXX~”, where XXXX arefour hexadecimal digits,
decodes as follows:
8000 = Command complete
4000 = Chip is busy
2000 = Command completed withouterror
1000 = Command aborted issuanceof an ABORT command
800 = Late collision detected
400= Carrierlost
200 = CTS lost
100 = DMA underrun
80 = Transmissiondeferred because link was busy
40 = Collisiondetected during interframe spacing (SQE/Heartbeat
detected)
20 = Excessivecollisions
10 = Reserved
The lowest nibble(bits 3 to 0) are a count of collisions during this
transmission. For example:
~8802~ = Complete, Late collision,2 collisions
~8841~ = Complete, Late Collision, SQE detected, 1 collis ion
The boot command display (using bfs) looks similar to this:
monitor:: boot
Enter boot file name[(ip) “oper .64.enet”,\
(mop) “OPER_64_ENET.SYS” ]::
Waiting for CMB Config Block Info ...
Requesting default boot file “O PER_64_ENET.SYS” for MOP/VM S\
loads and “oper.64.enet” for al l other protocols.
Unanswered requests shown as ‘? ’,transmission errors as ‘*’.
Requesting boot from 192.9.2 00.88 via Ethernet...
Booting BFS file using open delay o f 8
Booting BFS file from 192.9.200 .88
Header received OK. Received da ta blocks shown as ‘.’.
................................
................................
............?...................
................................
......................?.........
.................EOF