HP FDDI 9000 HP9000 PCI FDDI Release Notes for HP-UX 10.20, 11.0 and 11i - Page 10

Patches and Fixes in This Version - 11.00.16

Get HP FDDI 9000 PDF manuals and user guides View all HP FDDI 9000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 10 highlights

HP9000 PCI FDDI Release Note - 11.0 Patches and Fixes in This Version - 11.00.16 Patches and Fixes in This Version - 11.00.16 Fixes for the following symptoms are included in this version. Fixes one through seven are for the new release, 11.00.16. See Table 2-1 at the end of this section for additional information regarding ARs or patch releases and the specific fixes they contain. 1. Network management subagent for PCI FDDI is not available. 2. Details of unsolicited events are not available for the PCI FDDI Driver 3. Messages similar to the following are seen either on the system console or in the system log file (/var/adm/syslog.log, by default) on A and B class systems with non-cache=coherent I/O which have the PCI FDDI card and driver installed: vmunix FDDI[2] WARNING: cmd=0 failure status=lcee90 4. When the system is heavily loaded, the PCI FDDI driver may reset the card to recover from a time-out. During the reset, the IP state will go to the Down state, and it may not come back to the UP state even if the card recovers successfully. This fix depends on Patch PHNE_24413. 5. Sometimes the card reset will fail and the following message can be seen either on the system console or in the system log file: vmunix fddi4[2], reclaim_res: Card in wrong state 4, ff, 872, fddi4_rest 6. A system that has the PHCO_21596 patch or a superseding patch installed and has run insf -e to create the device files will cause the fddipciadmin not to work and the message similar to the following will be printed: fddipciadmin:/dev/lan1 is not a valid device, errno = 19 7. The lanadmin shared library for the PCI FDDI product does not need to have the suid bit set. The access bit should be 0555. 8. A system with the FDDI PCI product installed (from the June 2000 application release) may panic with a 'data memory protection fault' when an application running sustained and heavy loop-back traffic over the FDDI PCI interface is closed. The loop-back packets have a non-SNAP destination Service Access Point (SAP), i.e. a destination SAP that is not equal to 0xAA. 9. When promiscuous mode is enabled on an interface, outbound packets are not looped back to the unbound promiscuous stream. 10. The driver does not support clearing the card and driver statistics from the lanadmin(1M) 10

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
10
HP9000 PCI FDDI Release Note - 11.0
Patches and Fixes in This Version - 11.00.16
Patches and Fixes in This Version - 11.00.16
Fixes for the following symptoms are included in this version. Fixes one through seven are for
the new release, 11.00.16.
See Table 2-1 at the end of this section for additional information regarding ARs or patch
releases and the specific fixes they contain.
1.
Network management subagent for PCI FDDI is not available.
2.
Details of unsolicited events are not available for the PCI FDDI Driver
3.
Messages similar to the following are seen either on the system console or in the system
log file (/var/adm/syslog.log, by default) on A and B class systems with non-cache=coherent
I/O which have the PCI FDDI card and driver installed:
vmunix FDDI[2] WARNING: cmd=0 failure status=lcee90
4.
When the system is heavily loaded, the PCI FDDI driver may reset the card to recover
from a time-out. During the reset, the IP state will go to the
Down
state, and it may not
come back to the
UP
state even if the card recovers successfully. This fix depends on Patch
PHNE_24413.
5.
Sometimes the card reset will fail and the following message can be seen either on the
system console or in the system log file:
vmunix fddi4[2], reclaim_res: Card in wrong state 4, ff, 872, fddi4_rest
6.
A system that has the
PHCO_21596
patch or a superseding patch installed and has run
insf -e
to create the device files will cause the
fddipciadmin
not to work and the
message similar to the following will be printed:
fddipciadmin:/dev/lan1 is not a valid device, errno = 19
7.
The lanadmin shared library for the PCI FDDI product does not need to have the suid bit
set. The access bit should be
0555
.
8.
A system with the FDDI PCI product installed (from the June 2000 application release)
may panic with a ‘data memory protection fault’ when an application running sustained
and heavy loop-back traffic over the FDDI PCI interface is closed. The loop-back packets
have a non-SNAP destination Service Access Point (SAP), i.e. a destination SAP that is not
equal to 0xAA.
9.
When promiscuous mode is enabled on an interface, outbound packets are not looped back
to the unbound promiscuous stream.
10. The driver does not support clearing the card and driver statistics from the
lanadmin(1M)