New HP laser jet Printer 4000 series

I need a solution

dear all

any clue on this, we have SEP polices configured with application control enabled, but we dont have any device control, these new printer doesn’t include driver CD, in fact hp came up with new idea having flash disk inside with driver in it. FIrst time connection to computer it will work as flash driver installs the driver and than it will be a regular USB printer cable. 

i’m facing issue with this, it has autorun.inf file which will be blocked by my polices, and they are not safe to allow it too, and  can’t allow as device cuz we are not blocking any devices, blocking on executiable files from any flash drive this is the polcy for us. allowed only doc and txt files.

please 

0

Related:

Driver Disk for Microsemi smartpqi 1.1.2-125 – For XenServer 7.2

Who Should Install this Driver Disk?

Customers running Citrix XenServer 7.2.0 who use Microsemi’s smartpqi driver and wish to use the latest version of the following:

Driver Module Version
smartpqi
1.1.2-125

Issues Resolved In this Driver Disk

Includes general enhancements and bug fixes.

Firmware requirements for this Driver Disk

Please ensure that your hardware is running firmware versions greater or equal to the ones specified below, according to the chipset of your particular device:

  • Microsemi Adaptec SmartRAID 3100 Adapters with Firmware 1.32 [0]
  • Microsemi Adaptec SmartHBA 2100 Adapters with Firmware 1.32 [0]

Note: If your device has been branded by your OEM, please ensure that you consult them regarding the currently supported driver/firmware versions.

Installing the Driver Disk

Customers should use XenServer Command Line Interface (CLI) to install this update. Once the driver has been installed, the server must be restarted. As with any software update, Citrix advises customers to back up their data before applying this driver disk.

Please note that the attachment to this article is a zip file. It contains both the driver disk ISO mentioned below, and the source code for the driver. The zip file should be unzipped (to produce the driver disk ISO image), before carrying out the steps below. The source code ISO is not necessary for driver disk installation: it is provided to fulfill licensing obligations.

Installing as Part of a Clean XenServer Installation

  1. Once you have selected your keyboard layout at the first installer prompt, you will be presented with a welcome screen. At this point, press F9 on your keyboard, and insert the CD with the driver disk in it, or use one of the other methods such as installation over the network.

    Users should note that if installation over HTTP or FTP is to be used, the ISO image must be unpacked at that location (i.e. the installer expects to find the contents of the ISO at that network location, not the ISO itself).

  2. The installer will proceed to attempt to load the driver. If this is successful, you can continue with the installation as normal. Near the end of the installation, you will be prompted to re-insert the driver disk (otherwise known as a XenServer supplemental pack) so that the driver can be installed onto disk. You must re-supply the driver disk at this point. Failure to do so will mean that the installation will not contain the new drivers. After this step, no further action is required.

If the installer fails to load the new driver from the driver disk, it is likely to be because an earlier version of the driver has already been loaded. In general, this is because a hardware component is present that is supported by the version of the driver that ships as part of XenServer (even if another component is present that requires a newer version of the driver). To avoid the existing driver being loaded, use the following procedure.

  1. Reboot the host, leaving the XenServer installation CD-ROM in the drive.
  2. At the boot: prompt, type:

    shell

  3. You will now be presented with a command prompt. Type the following:

    rmmod smartpqi

    If this succeeds (i.e. there are no error messages printed), the installer’s versions of the drivers have been unloaded. If error messages are presented, it is likely that other drivers depend on one or more of the drivers you are attempting to unload. If this is the case, please contact Citrix Technical Support.

  4. Type

    exit

    or press Control+D on your keyboard, to return to the installer.

  5. Use the procedure described above to provide the driver disk to the installer, which should now load correctly.

Installing the Update by using the xe Command Line Interface

Perform the following steps to install the update remotely using the xe CLI:

  1. Download the update to a known location on a computer that has XenCenter installed.
  2. Upload the update:

    xe update-upload file-name=driver-microsemi-smartpqi-1.1.2_125.iso

    Note: The UUID of the update is returned when the upload completes.

  3. Apply the update:

    xe update-apply uuid=119da241-7a63-42f1-852e-803a7fa5bbdb

  4. To complete the installation, restart the host. This ensures that the driver loads correctly.

Files

Update Files

Component Details
Filename driver-microsemi-smartpqi-1.1.2_125.iso
File sha256 4ff3a0f63c1042a508c4f747b853d9ce1437d5ca380de1641e42b83bfac284e1
Source Filename driver-microsemi-smartpqi-1.1.2_125-sources.iso
Source File sha256 0e9a02a23b5416ce8631dfd405b64a985c616d43dad07e6be21c8867196bc4a3
Zip Filename driver-microsemi-smartpqi-1.1.2_125.zip
Zip File sha256 079a37b5fcfbf28a74b8484fc18407142b445ef38d34ff77bdaa515932fca472
Size of the Zip file 0.12 MB

RPMs Provided

RPM Name
microsemi-smartpqi-1.1.2_125-1.x86_64.rpm

More Information

If you experience any difficulties, contact Citrix Technical Support.

For information on how to build driver disks, refer to Citrix XenServer ® 7.2 Supplemental Packs and the DDK Guide.

Related:

Driver Disk for Cisco enic 2.3.0.40 – For XenServer 7.2

Who Should Install this Driver Disk?

Customers running Citrix XenServer 7.2.0 who use Cisco’s enic driver and wish to use the latest version of the following:

Driver Module Version
enic 2.3.0.40

Issues Resolved In this Driver Disk

Includes general enhancements and bug fixes.

Note: If your device has been branded by your OEM, please ensure that you consult them regarding the currently supported driver/firmware versions.

Installing the Driver Disk

Customers should use XenServer Command Line Interface (CLI) to install this update. Once the driver has been installed, the server must be restarted. As with any software update, Citrix advises customers to back up their data before applying this driver disk.

Please note that the attachment to this article is a zip file. It contains both the drive disk ISO mentioned below, and the source code for the driver. The zip file should be unzipped (to produce the driver disk ISO image), before carrying out the steps below. The source code file is not necessary for driver disk installation: it is provided to fulfill licensing obligations.

Installing as Part of a Clean XenServer Installation

  1. Once you have selected your keyboard layout at the first installer prompt, you will be presented with a welcome screen. At this point, press F9 on your keyboard, and insert the CD with the driver disk in it, or use one of the other methods such as installation over the network.

    Users should note that if installation over HTTP or FTP is to be used, the ISO image must be unpacked at that location (i.e. the installer expects to find the contents of the ISO at that network location, not the ISO itself).

  2. The installer will proceed to attempt to load the driver. If this is successful, you can continue with the installation as normal. Near the end of the installation, you will be prompted to re-insert the driver disk (otherwise known as a XenServer supplemental pack) so that the driver can be installed onto disk. You must re-supply the driver disk at this point. Failure to do so will mean that the installation will not contain the new drivers. After this step, no further action is required.

If the installer fails to load the new driver from the driver disk, it is likely to be because an earlier version of the driver has already been loaded. In general, this is because a hardware component is present that is supported by the version of the driver that ships as part of XenServer (even if another component is present that requires a newer version of the driver). To avoid the existing driver being loaded, use the following procedure.

  1. Reboot the host, leaving the XenServer installation CD-ROM in the drive.
  2. At the boot: prompt, type:

    shell

  3. You will now be presented with a command prompt. Type the following:

    rmmod enic

    If this succeeds (i.e. there are no error messages printed), the installer’s versions of the drivers have been unloaded. If error messages are presented, it is likely that other drivers depend on one or more of the drivers you are attempting to unload. If this is the case, please contact Citrix Technical Support.

  4. Type

    exit

    or press Control+D on your keyboard, to return to the installer.

  5. Use the procedure described above to provide the driver disk to the installer, which should now load correctly.

Installing the Update by using the xe Command Line Interface

Perform the following steps to install the update remotely using the xe CLI:

  1. Download the update to a known location on a computer that has XenCenter installed.
  2. Upload the update:

    xe update-upload file-name=driver-cisco-enic-2.3.0.40.iso

    Note: The UUID of the update is returned when the upload completes.

  3. Apply the update:

    xe update-apply uuid=e20d2b5e-cb9b-4ed3-bf55-fa69c4b37422

  4. To complete the installation, restart the host. This ensures that the driver loads correctly.

Files

Update Files

Component Details
Filename driver-cisco-enic-2.3.0.40.iso
File sha256 666ae2385e5644ca1314d252671906faaf80c2c13d10c1910cb1bef6b85d9332
Source Filename driver-cisco-enic-2.3.0.40-sources.iso
Source File sha256 82bfee96a396048572845f185f8620f7d3d7b4a7e6e66b70d6da4df4e0d129eb
Zip Filename driver-cisco-enic-2.3.0.40.zip
Zip File sha256 f43223808521ee5d15c449b6b9e7da14fe2b7b3bd570f3d9580b18954d377157
Size of the Zip file 0.19 MB

RPMs Provided

RPM Name
cisco-enic-2.3.0.40-2.x86_64.rpm

More Information

If you experience any difficulties, contact Citrix Technical Support.

For information on how to build driver disks, refer to Citrix XenServer ® 7.2 Supplemental Packs and the DDK Guide.

Related:

Driver Disk for Emulex Be2net 11.1.196.6 – For XenServer 7.2

Who Should Install this Driver Disk?

Customers running Citrix XenServer 7.2.0 who use Emulex’s Be2net driver and wish to use the latest version of the following:

Driver Module Version
Be2net 11.1.196.6

Issues Resolved In this Driver Disk

Includes general enhancements and bug fixes.

Note: If your device has been branded by your OEM, please ensure that you consult them regarding the currently supported driver/firmware versions.

Installing the Driver Disk

Customers should use XenServer Command Line Interface (CLI) to install this update. Once the driver has been installed, the server must be restarted. As with any software update, Citrix advises customers to back up their data before applying this driver disk.

Please note that the attachment to this article is a zip file. It contains both the drive disk ISO mentioned below, and the source code for the driver. The zip file should be unzipped (to produce the driver disk ISO image), before carrying out the steps below. The source code file is not necessary for driver disk installation: it is provided to fulfill licensing obligations.

Installing as Part of a Clean XenServer Installation

  1. Once you have selected your keyboard layout at the first installer prompt, you will be presented with a welcome screen. At this point, press F9 on your keyboard, and insert the CD with the driver disk in it, or use one of the other methods such as installation over the network.

    Users should note that if installation over HTTP or FTP is to be used, the ISO image must be unpacked at that location (i.e. the installer expects to find the contents of the ISO at that network location, not the ISO itself).

  2. The installer will proceed to attempt to load the driver. If this is successful, you can continue with the installation as normal. Near the end of the installation, you will be prompted to re-insert the driver disk (otherwise known as a XenServer supplemental pack) so that the driver can be installed onto disk. You must re-supply the driver disk at this point. Failure to do so will mean that the installation will not contain the new drivers. After this step, no further action is required.

If the installer fails to load the new driver from the driver disk, it is likely to be because an earlier version of the driver has already been loaded. In general, this is because a hardware component is present that is supported by the version of the driver that ships as part of XenServer (even if another component is present that requires a newer version of the driver). To avoid the existing driver being loaded, use the following procedure.

  1. Reboot the host, leaving the XenServer installation CD-ROM in the drive.
  2. At the boot: prompt, type:

    shell

  3. You will now be presented with a command prompt. Type the following:

    rmmod Be2net

    If this succeeds (i.e. there are no error messages printed), the installer’s versions of the drivers have been unloaded. If error messages are presented, it is likely that other drivers depend on one or more of the drivers you are attempting to unload. If this is the case, please contact Citrix Technical Support.

  4. Type

    exit

    or press Control+D on your keyboard, to return to the installer.

  5. Use the procedure described above to provide the driver disk to the installer, which should now load correctly.

Installing the Update by using the xe Command Line Interface

Perform the following steps to install the update remotely using the xe CLI:

  1. Download the update to a known location on a computer that has XenCenter installed.
  2. Upload the update:

    xe update-upload file-name=driver-emulex-be2net-11.1.196.6.iso

    Note: The UUID of the update is returned when the upload completes.

  3. Apply the update:

    xe update-apply uuid=0e15fa69-d2c4-4f8b-b35c-ca7ec421d574

  4. To complete the installation, restart the host. This ensures that the driver loads correctly.

Files

Update Files

Component Details
Filename driver-emulex-be2net-11.1.196.6.iso
File sha256 a0343c7d10f81cb0b310955afe64c13d46cb3645651e7c5f03ae9536fc27b275
Source Filename driver-emulex-be2net-11.1.196.6-sources.iso
Source File sha256 01a97928652cbf68760a7274a43d2da4bc675ba04fd099f975e45192f94dca16
Zip Filename driver-emulex-be2net-11.1.196.6.zip
Zip File sha256 5eb0387b8ae6b460ebd64e3a2faf0a0b99992cead6ad58eb5ea73b61e50ecc85
Size of the Zip file 0.24 MB

RPMs Provided

RPM Name
emulex-be2net-11.1.196.6-2.x86_64.rpm

More Information

If you experience any difficulties, contact Citrix Technical Support.

For information on how to build driver disks, refer to Citrix XenServer ® 7.2 Supplemental Packs and the DDK Guide.

Related:

Driver Disk for Qlogic qede 8.30.13.0 – For XenServer 7.2

Who Should Install this Driver Disk?

Customers running Citrix XenServer 7.2.0 who use qlogic’s qede driver and wish to use the latest version of the following:

Driver Module Version
qede 8.30.13.0

Issues Resolved In this Driver Disk

Includes general enhancements and bug fixes.

Note: If your device has been branded by your OEM, please ensure that you consult them regarding the currently supported driver/firmware versions.

Installing the Driver Disk

Customers should use XenServer Command Line Interface (CLI) to install this update. Once the driver has been installed, the server must be restarted. As with any software update, Citrix advises customers to back up their data before applying this driver disk.

Please note that the attachment to this article is a zip file. It contains both the drive disk ISO mentioned below, and the source code for the driver. The zip file should be unzipped (to produce the driver disk ISO image), before carrying out the steps below. The source code file is not necessary for driver disk installation: it is provided to fulfill licensing obligations.

Installing as Part of a Clean XenServer Installation

  1. Once you have selected your keyboard layout at the first installer prompt, you will be presented with a welcome screen. At this point, press F9 on your keyboard, and insert the CD with the driver disk in it, or use one of the other methods such as installation over the network.

    Users should note that if installation over HTTP or FTP is to be used, the ISO image must be unpacked at that location (i.e. the installer expects to find the contents of the ISO at that network location, not the ISO itself).

  2. The installer will proceed to attempt to load the driver. If this is successful, you can continue with the installation as normal. Near the end of the installation, you will be prompted to re-insert the driver disk (otherwise known as a XenServer supplemental pack) so that the driver can be installed onto disk. You must re-supply the driver disk at this point. Failure to do so will mean that the installation will not contain the new drivers. After this step, no further action is required.

If the installer fails to load the new driver from the driver disk, it is likely to be because an earlier version of the driver has already been loaded. In general, this is because a hardware component is present that is supported by the version of the driver that ships as part of XenServer (even if another component is present that requires a newer version of the driver). To avoid the existing driver being loaded, use the following procedure.

  1. Reboot the host, leaving the XenServer installation CD-ROM in the drive.
  2. At the boot: prompt, type:

    shell

  3. You will now be presented with a command prompt. Type the following:

    rmmod qede

    If this succeeds (i.e. there are no error messages printed), the installer’s versions of the drivers have been unloaded. If error messages are presented, it is likely that other drivers depend on one or more of the drivers you are attempting to unload. If this is the case, please contact Citrix Technical Support.

  4. Type

    exit

    or press Control+D on your keyboard, to return to the installer.

  5. Use the procedure described above to provide the driver disk to the installer, which should now load correctly.

Installing the Update by using the xe Command Line Interface

Perform the following steps to install the update remotely using the xe CLI:

  1. Download the update to a known location on a computer that has XenCenter installed.
  2. Upload the update:

    xe update-upload file-name=driver-qlogic-fastlinq-8.30.13.0.iso

    Note: The UUID of the update is returned when the upload completes.

  3. Apply the update:

    xe update-apply uuid=24097536-ba7d-400c-80fa-411739ccb5be

  4. To complete the installation, restart the host. This ensures that the driver loads correctly.

Files

Update Files

Component Details
Filename driver-qlogic-fastlinq-8.30.13.0.iso
File sha256 69d92d0bd3cb2067b00074501d235e8e03c9cda6f3e32ad07e503d791d35c698
Source Filename driver-qlogic-fastlinq-8.30.13.0-sources.iso
Source File sha256 cff9f5f036688bb93abbf1c34c368dafe5ea817e2a827fcc16b5839556324d86
Zip Filename driver-qlogic-fastlinq-8.30.13.0.zip
Zip File sha256 6f84191596fdbfec94cfa98e65aa37a49629e39c53de4f66d35a59ee33c9b1be
Size of the Zip file 11.16 MB

RPMs Provided

RPM Name
qlogic-fastlinq-8.30.13.0-1.x86_64.rpm

More Information

If you experience any difficulties, contact Citrix Technical Support.

For information on how to build driver disks, refer to Citrix XenServer ® 7.2 Supplemental Packs and the DDK Guide.

Related:

Driver Disk for PMC-Sierra aacraid driver v1.2.1-55022 – For XenServer 7.0

Who Should Install this Driver Disk?

Customers running Citrix XenServer 7.0 who use PMC Sierra’s aacraid driver and wish to use the latest version of the following:

Driver Module Version
aacraid 1.2.1.55022

Issues Resolved In this Driver Disk

Includes general enhancements and bug fixes.

Firmware requirements for this Driver Disk

Please ensure that your hardware is running firmware versions greater or equal to the ones specified below, according to the chipset of your particular device:

  • Microsemi Adaptec HBA 1000 Series Host Bus Adapters with Firmware 3.52 [0]
  • Adaptec RAID 8805 with Firmware 33204

Note: If your device has been branded by your OEM, please ensure that you consult them regarding the currently supported driver/firmware versions.

Installing the Driver Disk

Customers should use the XenServer CLI to install this driver disk. Once the driver has been installed, the server must be restarted, in order for the driver to be loaded. As with any software update, Citrix advises customers to back up their data before applying this driver disk.

Please note that the attachment to this article is a zip file. It contains both the drive disk ISO mentioned below, and the source code for the driver. The zip file should be unzipped (to produce the driver disk ISO image), before carrying out the steps below. The source code file is not necessary for driver disk installation: it is provided to fulfill licensing obligations.

The file with filename ending metadata.md5 contains the checksum of the driver disk’s metadata. If, when you install the driver disk, you elect to verify the driver disk when prompted, you should check that the checksum presented by the installer is the same as that in the metadata MD5 checksum file included in this download.

Also present in the zip file is an MD5 checksum for the ISO image named aacraid.iso. This will allow you to verify that your download has been successful. This checksum is of the ISO only, and can be verified by following the instructions at CTX116166: How to verify downloaded ISO images.

Installing as Part of a Clean XenServer Installation

  1. Once you have selected your keyboard layout at the first installer prompt, you will be presented with a welcome screen. At this point, press F9 on your keyboard, and insert the CD with the driver disk in it, or use one of the other methods such as installation over the network.

    Users should note that if installation over HTTP or FTP is to be used, the ISO image must be unpacked at that location (i.e. the installer expects to find the contents of the ISO at that network location, not the ISO itself).

  2. The installer will proceed to attempt to load the driver. If this is successful, you can continue with the installation as normal. Near the end of the installation, you will be prompted to re-insert the driver disk (otherwise known as a XenServer supplemental pack) so that the driver can be installed onto disk. You must re-supply the driver disk at this point. Failure to do so will mean that the installation will not contain the new drivers. After this step, no further action is required.

If the installer fails to load the new driver from the driver disk, it is likely to be because an earlier version of the driver has already been loaded. In general, this is because a hardware component is present that is supported by the version of the driver that ships as part of XenServer (even if another component is present that requires a newer version of the driver). To avoid the existing driver being loaded, use the following procedure.

  1. Reboot the host, leaving the XenServer installation CD-ROM in the drive.
  2. At the boot: prompt, type:

    shell

  3. You will now be presented with a command prompt. Type the following:

    rmmod aacraid

    If this succeeds (i.e. there are no error messages printed),the installer’s versions of the drivers have been unloaded. If error messages are presented, it is likely that other drivers depend on one or more of the drivers you are attempting to unload. If this is the case, please contact Citrix Technical Support.

  4. Type

    exit

    or press Control+D on your keyboard, to return to the installer.

  5. Use the procedure described above to provide the driver disk to the installer, which should now load correctly.

Installing onto a Running XenServer System

  1. Download the driver disk directly to the XenServer host to be updated (Citrix recommends storing it in the /tmp/ directory), or first download the file to an Internet-connected computer, and burn the ISO image to a CD.
  2. Use XenCenter to access the XenServer host’s console, or log in directly using SSH.
  3. Mount the driver disk image. The directory being mounted varies depending on whether the driver disk is still in ISO form, or was burnt to CD. For a CD-ROM, use:

    mkdir -p /mnt/tmp

    mount /dev/<path to cd-rom> /mnt/tmp

    cd /mnt/tmp/

    ./install.sh

    cd /

    umount /mnt/tmp

    If instead, the ISO file is used, the steps are:

    mkdir -p /mnt/tmp

    mount /tmp/<path to ISO> /mnt/tmp -o loop,ro

    cd /mnt/tmp/

    ./install.sh

    cd /

    umount /mnt/tmp

  4. To complete the installation, restart the host. This ensures that the driver loads correctly.

Files

Driver Disk Files

File Name MD5 Checksum
aacraid.iso bdf8c855465804b17906797ef26c6ca6
aacraid.metadata.md5 7cc32babc2d5b40a0efa735f52635268
aacraid-1.2.1.55022-3.zip 8b0f81d8ec75a3969e291ac9ffeabd9a

RPMs Provided

Name Version RPM Name
aacraid-modules 1.2.1.55022 aacraid-modules-1.2.1.55022-3.x86_64.rpm
aacraid-3.10.0+10-modules 1.2.1.55022 aacraid-3.10.0+10-modules-1.2.1.55022-3.x86_64.rpm

More Information

If you experience any difficulties, contact Citrix Technical Support.

For information on how to build driver disks, refer to Citrix XenServer 7.0 Supplemental Packs & the DDK .

Related:

Non critical driver Management with DeployAnywhere

I need a solution

i want to install some non-critical driver with DeployAnywhere
The drivers are imported correctly in the DriversDB. 
my problem is, DeployAnywhere don’t find any of this drivers:
DA_Log from WinPE (example): 

“Reason For Driver Selection = Driver Not Found In Driver Database(s)”

i can find this driver in drivers.manifest.txt
So i analysed the DA_Log and found the client search the non critical drivers in :
” X:Windowsinf”
 

Command line :   /targetos=X64_WINDOWS10 /reportNonCriticalDevices /precheck /rad /exportDevicesIntoFile=X:Program FilesSymantecDeploymentLogs

Symantec Ghost 12.0.0 (build=10519).Built on Apr  5 2017 18:29:15 Copyright (C) 2017 Symantec Corporation. All rights reserved.

Start of DeployAnywhereMain().

Start of Initialize().

Not using a Driver Database

Precheck Target OS = X64_WINDOWS10

Performing precheck…

Getting devices from Target Machine and Deployed Image

Total no of device into Target Machine is 69

Total no of simulated device is 0

Finding driver service for drivers from X:Windowsinf

No of drivers into running OS Windows DB( X:Windowsinf ) is 346

so should i inject the non critical drivers in the winpe image?

or how can i inject the drivers direct from the ns site server?

0

Related:

7018776: How to extract Drivers from HP’s ProLiant Smart Array Controller Driver Diskettes .

The disk image may be mounted after it is extracted from the gzip archive then mounted using a loop back device. Assuming hpsa-3.4.16-145.sles11sp3.x86_64.dd.gz has been downloaded follow these steps to extract the kernel HPSA driver from the archive:

1. Extract the disk image:

gzip -d hpsa-3.4.16-145.sles11sp4.x86_64.dd.gz

2. Mount the disk image using a loop back device (as root):

mount -o loop hpsa-3.4.16-145.sles11sp4.x86_64.dd /mnt

The hpsa module can then be copied from /mnt/linux/suse/x86_64-sles11/modules.

Related:

Re: jbconfig does not see the jukebox or devices

I expected the smc0 to be showing “Defined”, not “Available”

Please refer to the following knowledge base article for additional information

smc0 driver conflict causes MODE_SENSE failure during jbconfig run

https://support.emc.com/kb/401758

Cause: If the atape driver is already installed, when you do a reboot with the IBM autochanger connected, the device with the logical name smc0 claims the robotic device initially. A conflict exists with the lus driver which prevents NetWorker from accessing the driver properly.

You can verify this by using the lsdev -Cs tape command. Look for smc0 to determine whether it is in the “Available” state.

# lsdev -Cc tape

rmt0 Available 00-01-01-4,0 Differential SCSI DLT Tape Drive

rmt1 Available 00-01-01-5,0 Differential SCSI DLT Tape Drive

smc0 Available 00-01-01-6,0 IBM 7337 Tape Medium Changer

To place smc0 in a “Defined” state, please issue the following command:

rmdev -l smc0

DO NOT remove smc driver if in a SAN environment, (do not run”rmdev -d”)!

Note that if the AIX Networker server reboots, smc0 will automatically become “Available” and the lus driver becomes “Defined” and Networker will not be able to operate the jukebox. Edit the /etc/rc.nsr startup file so that the lus driver will continue to be available after a reboot. Add the two lines below:

rmdev -l smc0

mkdev -l lus

Related:

7008330: How to manually uninstall the PlateSpin Block-Based Driver from a Linux source workload

This document (7008330) is provided subject to the disclaimer at the end of this document.

Environment

PlateSpin Forge 3.x
PlateSpin Protect 10.x

Situation

This article outlines the steps to remove the PlateSpin Block-Based Driver from a source Linux workload. On Linux, blkconfig provides all the controls for the Linux BBT driver. It is installed in /sbin.

Resolution

Run the following commands to manually remove the driver from the source:


1. Run the following command to check if the driver is active:
lsmod | grep blkwatch
2. If the result contains a line similar to the following example, the driver is still loaded in memory:
blkwatch_7616 70924 0
Run the following command to remove it from memory:
rmmod blkwatch_XXXX
Where XXXX will be replaced with a 4 digit number. Using the example from step 2, the command would be:
rmmod blkwatch_7616

3. Run the following command to remove the driver from the boot sequence:
blkconfig -u

4. Delete the following directory and file:
/lib/modules/[Kernel_Version]/Platespin

/etc/blkwatch.conf
5. run “ps -ef | grep ofx”
6. kill -9 “process found above step 5”
7. rm -rf /usr/lib/ofx

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related: