NS3000/iX Error Messages Reference Manual (36923-90043)

326 Chapter17
PCI 100Base-T Error Messages
SDI Driver Specific Status Values
configured.
Although the driver may attempt to continue using the previously read
multicast address list, the failure to allocate a data buffer and send a
new setup frame to the PCI 100Base-T card could result in some
network services/upper layer protocols (ULPs) not operating properly
(data frames intended for those ULPs may not be recognized by the
100Base-T card).
If that occurs, try to quiesce any active network traffic/sessions, then
bring down the network link (e.g., NETCONTROL STOP). Restart the
network.
Note all log messages, especially the “Cause” status for this error, and
check to see if the driver generated an internal dump file
(NETDMP##.PUB.SYS); see Appendix A , “Submitting a CR.”
2810 CLAS0003 MESSAGE: Cannot read current multicast list.
CAUSE: In response to a request to update the multicast address list
(and build a new setup frame for the PCI 100Base-T card), the DVR was
unable to successfully read the current multicast list of addresses
because it was too large for the driver to support. A maximum of 14
multicast addresses can be active at any one time on a single PCI
100Base-T link. There are likely too many network services/upper level
subsystems competing for resources on this link.
ACTION: The driver will try to continue to operate using the previously
activated multicast address list, but this error may prevent some upper
level subsystems from operating properly and receiving data over the
network. Try to quiesce any current network activity on the link and
then bring down the network link (e.g., NETCONTROL STOP).
Restart the network link, but limit the load of services/protocols that
are running on the same link. If multiple 100Base-T links are available
and configured on the system, consider balancing the load of upper level
subsystems running over each link.
3040 CLAS0003 MESSAGE: Pending message table full. Driver not finishing fast
enough.
CAUSE: While processing a new blocking request (requiring a driver exit
and later reply) and scanning a table in which to save the request, the
driver found an unused entry, but an entry counter indicated the table
was full (“Cause” is not used here).
ACTION: This fatal software error is only caused by a bug, because the
in use flags and counters should match. After reporting this error, the
driver will die, then will either attempt an auto- reset or else require a
manual shutdown and restart. If the problem persists, use Control-B at
the console to halt the system, take a memory dump, and reboot, see
Appendix A , “Submitting a CR.”