Devconfig !!HOT!! Download

0 views
Skip to first unread message

Astri Hirons

unread,
Jan 25, 2024, 4:19:43 PM1/25/24
to timipennse

To make the secure/non-secure differences seamless for the user, a configuration file is provided at $SDK_INSTALL_PATH/devconfig/devconfig.mak. In this configuration file, you can set certain options like the device type, keys to be used for signing and encryption etc. By default they will point to the dummy customer MPKs and MEKs but if you're using a production device with your own keys burned into the eFUSEs, please change the paths here to point to the right key files. Configuration of this file is currently manual, this will be made configurable by a GUI in an upcoming release.

Depending on the options given in the device configuration file (devconfig.mak mentioned above), appimage is generated for HS devices. If encryption is enabled in the configuration file, the binary will be first encrypted with the key specified and then the certificate will be generated using the customer MPK specified. If the device type is set as HS in the configuration file, nothing extra needs to be done for the appimage generation. The final *.appimage.hs file generated would be signed with customer MPK (and encrypted with customer MEK if that option is selected).

devconfig download


DOWNLOAD 🆗 https://t.co/6HIIyOk24Q




This is expected behavior since the 'vmglob -listall' cmd is returning some drives that are not listed in the subsequent call to 'vmoprcmd -devconfig -l'. This will not be logged as an error in scon.err but as a WARN message in SC 9201 P12, post-10.0.01 and post-10.0.00 P2 releases.

This document serves as a guide for upgrading from ADSM to TSM. The procedure described in this document will allow a complete recovery to an earlier service level if needed at a later date. This document is not specific to any particular ADSM supported operating system or specific ADSM version. Where an operating system command example is appropriate, AIX commands are used.NOTE: Please use this document in combination with the README filefor your type of operating system.Related documentationThe product documentation library is also available:
_resource/Pubs/index.htmlTSM overviewThe Tivoli Storage Manager (TSM) Server includes recovery log and database structural enhancements to support new functionality. For this reason,once this upgrade is applied, returning to an earlier servicelevel requires the reinitialization of the database and recoverylog volumes. This reinitialization process (dsmserv format), willremove all previous information stored in the database andrecovery log. This upgrade procedure, while more detailed thanprevious upgrade instructions, is designed to ensure that shoulda reversion to an earlier service level be necessary for anyreason, all information that could be required to assist in thatprocess is stored for future use. IMPORTANT: If a reversion is later needed, ensure that you keep your old installation media.TSM Server README files are available online at:

-storage-managementSelect one of the server directories, such as:

  • Maintenance (for example, 3.7.1, 3.7.2, 3.7.4, or 4.1.1, 4.1.2)
  • Patches (for example, 3.7.2.15, 4.1.2.12)
Inside each server directory will be server and client code in their respective directory paths. NOTE: Server full-product code, required for an ADSM to TSM Version/Release upgrade (for example, 3.7, 4.1), can be purchased through Tivoli Marketing at 1-800-2-TIVOLI or your localbranch/marketing office.Procedure
  1. Use the BACKUP DEVCONFIG command to back up the ADSM Device Configuration file to an alternate location (assuming that you have one defined), for example:BACKUP DEVCONFIG =/tmp/devconfig.bakThe QUERY OPTION command will show the DEVCONFIG option,if defined, which will identify the current location ofthis file. If you do not have one defined, please define it now byadding the following option to the dsmserv.opt file:DEVCONFIG //deconfig.outNOTE: You can acquire the same information throughthe QUERY LIBRARY, QUERY DRIVE, and other types of commands.Examples follow:Q LIBRARY * F=DQ DRIVE F=DQ DEVCLASS F=DQ SERVER F=D
  2. Copy the Server Options file, (dsmserv.opt), to an alternate location, for example:cp /usr/lpp/adsmserv/bin/dsmserv.opt /tmp/dsmserv.opt.bak
  3. If you are also updating ADSM code for the client residing on the same machine as the server, you should copy the Client Options file(s) to an alternate location. The default location for these files on AIX is usr/lpp/adsm/bin. An AIX platform example follows:cp /usr/lpp/adsm/bin/dsm.sys /tmp/dsm.sys.bakcp /usr/lpp/adsm/bin/dsm.opt /tmp/dsm.opt.bakNOTE: Windows, OS/2, and Netware clients do not have a dsm.sys file.
  4. Copy the operating system definitions for any devices utilized by ADSM. Use the AIX lsdev command to save the device definitions for any tape or optical device used with, and supported by, the ADSM device driver (the op, mt, lb names). AIX example commands follow:lsdev -Cc adsmtape > /tmp/device.configlsdev -Cc tape >> /tmp/device.configlsdev -Cc library >> /tmp/device.configlsdev -Cc rwoptical >> /tmp/device.configYou will also need to know the parent adapter of each device, enter:lsdev -Cc adapter >> /tmp/device.configNOTE: This is not needed for Atape/IBMTAPE devices, such as the 3570, 3575, 358X 3490,3590, 3494, or any device classified as GENERICTAPE to ADSM.Please refer to the TSM Server README file for your specific operating system to determine any special requirements related to the installation or support for devices. This may include required device-driver upgrades or required operating system maintenance.
  5. Collect the log and database information, as well as any other information that will be important to have, should an error occur during this upgrade. To collect this information, enter:Q SYSTEM
  6. Copy the dsmserv.dsk file to an alternate location, for example: cp /usr/lpp/adsmserv/bin/dsmserv.opt /tmp/dsmserv.opt.bak
  7. Prevent new processes from establishing themselves:
    • All systems should perform:
    • End all currently running processes using the QUERY PROCESS and CANCEL PROCESS commands.
    • End all currently running sessions using the QUERY SESSION and CANCEL SESSION commands.
  • If your system is heavily used, you may require:
  • In the dsmserv.opt file, add:DISABLESCHEDS YES This will disable schedules once ADSM is restarted.
  • In the dsmserv.opt file, add:EXPINTERVAL 0This will disable expiration once ADSM is restarted.
  • From the DSMADMC command line, for each storage pool, enter:QUERY STGThis will collect the information that you will later need if system recovery is required.
  • From the DSMADMC command line, for each storage pool, enter:UPDATE STG RECLAIM=100 HI=100This will disable migration and reclamation.
  • From the DSMADMC command line, enter:DISABLE SESSSIONSThis will prevent clients from connecting during upgrade.
  • From the DSMADMC command line, enter:HALTThis will stop ADSM Server.
  • Restart ADSM.
    • For UNIX, enter rc.adsmserv from the server/bin directory.
    • For Windows NT 4.0 or 2000, restart the service.
  • Complete a full ADSM database backup as shown in the following example:BACKUP DB DEVCLASS= TYPE=FULL SCRATCH=YESSCRATCH=NO can also be used if appropriate for your environment.
  • Use the BACKUP VOLHIST command to backup the ADSM Volume History file to an alternate location - if you have one defined. An example follows:BACKUP VOLHIST FILENAMES=/tmp/volhist.bakNOTE: The QUERY OPTION command will show the VOLUMEHISTORY option, if defined, which will identify the current location of this file. If you do not have one defined, please define it now by adding the following option to the dsmserv.opt file:VOLUMEHISTORY //volhis.out
  • Use QUERY MOUNT and DISMOUNT VOLUME to empty the drives if required.
  • Halt ADSM from the ADSM command line, enter:HALT
  • If you are upgrading your client, accomplish the following:
    • Copy dsm.sys and dsm.opt to a safe location.
    • For AIX, use installp -u adsm.client.
    • For Win32, use Control Panel -> Add/Remove -> ADSM Client.
  • Specifically for AIX, first remove your ADSM device definitions by entering:rmdev -dl mtXrmdev -dl lbXrmdev -dl odXWhere X represents the drive number. Do this for each drive contained in your output from step 4 (/tmp/device.config).
  • Install the new code from base-install media according to the instructions contained in the README file for you operating system type.
  • Install any required device driver updates or operating system updates as required from Step 4.
  • If the preceding steps were followed, and your devices are deleted from AIX, redefine your AIX devices using SMIT, enter:smitty devices
  • Select TSM Devices
  • Select Tape for mt's and add Device for each.
  • Select Optical for od's and add Device for each.
  • Select Library for lb's and add Device for each.
  • Verify that the dsmserv.opt file, and optionally the dsm.sys and dsm.opt files, are present in their default location as determined in steps 2 and 3.NOTE: The verification of the dsm.opt and dsm.sys files is only required when updating the ADSM client code.
  • Make any modifications to the dsmserv.opt, dsm.sys, and dsm.opt files as required - based on changes to the options contained within the files as outlined in the Release Notes and README files for the current version. Additionally, verify that the environment variables reflect the new directory structure.
  • Verify that the Device Configuration and Volume History files are present in the their default locations, as determined in step 4 and 10, respectively, in this document.
  • Ensure that the dsmserv.dsk file is present in the default location, as determined above.
  • Start the TSM server. If you are given a notice that the database needs to be updated, you can restart the ADSM server with the upgradedb parameter. This will not be required on subsequent restarts of the server.NOTE: On the AIX and NT platforms, it is not necessary to explicitly specify the upgradedb parameter as the initial dsmserv process will automatically perform this function. However, you can issue it without negative effect to the server.
  • Once you have verified that the server is operating normally, reset any values changed in step 7, including:
  • Remove ENABLE SCHEDS from the dsmserv.opt file.
  • Remove EXPINTERVAL 0 from the dsmserv.opt file.
  • For each pool changed, enter:UPDATE STG RECLAIM= HI=
  • At a dsmadmc command prompt, enter:ENABLE SESS
  • Stop ADSM from a dsmadmc command prompt, enter:HALT
  • Restart TSM.
    • On a UNIX platform, from the server/bin directory, enter:rc.adsmserv
    • On Windows NT or 2000, click start from within the NT/2000 services control panel.
    Cleanup procedures
    1. If appropriate for your environment, it is highly recommended that you install the current maintenance level for your version and release of TSM. This can be obtained via FTP over the public Internet within the maintenance subdirectory of the following ftp site: -storage-management
    2. Search for and remove any obsolete ADSM code that has been replaced with TSM code.
      • For AIX, enter:lslpp -l grep -i adsminstall -u adsm (or adsm.client, adsm.server, etc.)
      • For Solaris, enter:pkginfopkgrm
      • For Windows, use the Add/Remove Programs icon in the Control Panel.
      NOTE: Ensure that you do not uninstall a package that you have not replaced, with the exception of Space Management, which cannot run backlevel.
    3. For technical assistance, contact Tivoli Support at1-800-TIVOLI-8 or the IBM Support Line at 1-800-237-5711.



    [ Doc Ref: 98052918210162 Publish Date: Feb. 06, 2001 4FAX Ref: 8801 ]

dafc88bca6
Reply all
Reply to author
Forward
0 new messages