Problems using Acceleport RAS on Unixware 7.1.1 or 7.1.3 systems.


	Technical Support Drivers Firmware Upgrades FAQs Product Documentation Cabling Support Tools Legacy Products About Digi Support Knowledge Base Online Support Request FTP Site Related Links Inside Out Networks

Home > Support >kbase >

Problems using Acceleport RAS on Unixware 7.1.1 or 7.1.3 systems. Problems using Acceleport RAS on Unixware 7.1.1 or 7.1.3 systems.

Digi is currently aware of a problem which occurs when attempting to install an Acceleport RAS or Xp card into a Unixware 7.1.1 (with maintenance pack uw711m3) or Unixware 7.1.3 system.

To clarify, here are the combinations of OS/patch level in which the problem is or isn't seen:

Unixware 7.1.1 base OS - netcfg -> WAN shows our board listed after digiras driver has been installed.

Unixware 7.1.1 with uw711m1 installed - netcfg -> WAN shows our board listed after digiras driver has been installed.

Unixware 7.1.1 with uw711m2 installed - netcfg -> WAN does NOT show our board listed after digiras driver has been installed.

Unixware 7.1.1 with uw711m3 installed - netcfg -> WAN does NOT show our board listed after digiras driver has been installed.

Unixware 7.1.3 base OS - netcfg -> WAN does NOT show our board listed after digiras driver has been installed.

Unixware 7.1.3 with uw713m1 installed - netcfg -> WAN does NOT show our board listed after digiras driver has been installed.

A workaround for the Unixware 7.1.1 problem exists in that if the digiras driver and Acceleport RAS or Xp card is installed prior to the installation of maintenance pack 2 or 3, the card and devices will still be seen and useable by the OS and applications. It is only the installation of new cards which will be affected once the Unixware maintenance pack is added to the system. By the same token, removing the maintenance pack in the Unixware 7.1.1 environment will allow the Acceleport cards to again be added via netcfg -> WAN.

Engineers at Digi are investigating this issue in order to see if anything can be done to the digiras driver to resolve this issue. The possibility exists that a patch from SCO may be needed to resolve this issue instead.