Great tip:
Friday, March 4, 2022
How to map network share UNC as link on disk on Windows
Wednesday, April 15, 2020
TSM: ANR8985E The drive xxx in library xxx is using an encryption method that is incompatible with the current server settings.
I have faced confusing error message:
ANR8985E The drive xxx in library xxx is using an encryption method that is incompatible with the current server settings.
The root case of error was that I defined device class explicitly with parameter DRIVEEncryption and value OFF.
There was impact even I did not use encryption on library and its drives.
Drive was encryption capable but not enabled on library:
[root@tsm1 ITDT]# ./itdt -f /dev/IBMtape0 encryption
Getting drive encryption settings...
Encryption settings:
Drive Encryption Capable... Yes
Encryption Method.......... Library
Encryption State........... NA
Exit with code: 0
So I changed DRIVEEncryption to ALLOW (default) even I did not use encryption and error message disappeared and volume got mounted...
define devclass IBMTAPE01WORM LIBRary=IBMTAPE01 DEVTYPE=LTO FORMAT=ULTRIUM8C WORM=YES MOUNTLimit=DRIVES DRIVEEncryption=ALLOW LBProtect=READWrite
ANR8985E The drive xxx in library xxx is using an encryption method that is incompatible with the current server settings.
The root case of error was that I defined device class explicitly with parameter DRIVEEncryption and value OFF.
There was impact even I did not use encryption on library and its drives.
Drive was encryption capable but not enabled on library:
[root@tsm1 ITDT]# ./itdt -f /dev/IBMtape0 encryption
Getting drive encryption settings...
Encryption settings:
Drive Encryption Capable... Yes
Encryption Method.......... Library
Encryption State........... NA
Exit with code: 0
So I changed DRIVEEncryption to ALLOW (default) even I did not use encryption and error message disappeared and volume got mounted...
define devclass IBMTAPE01WORM LIBRary=IBMTAPE01 DEVTYPE=LTO FORMAT=ULTRIUM8C WORM=YES MOUNTLimit=DRIVES DRIVEEncryption=ALLOW LBProtect=READWrite
Friday, February 22, 2019
TSM: Replicate Node fails with ANR9999D_2930690409 and rc=1120
I have had a problem when running replicate node between two TSM / Spectrum Protect servers, replication failed with nothing saying error message ANR9999D_2930690409 and rc=1120.
02/12/2019 12:30:47 ANR9999D_2930690409 SmReplServerSession(smrepl.c:2609) Thread<1537>: Replication session 246 for TSM on Linux/x86_64 failed, rc=1120 (SESSION: 246)1537>
02/12/2019 12:30:47 ANR9999D Thread<1537> issued message 9999 from: (SESSION: 246)1537>
Root cause was missing archive copy group on target server, wow, one may think that this could be common configuration mistake when configuring replication, but IBM doesn't think so when showing message which You can not understand :)
You can compare and validate policies on source and replication servers by command:
VALIDATE REPLPOLICY TARGET_TSM_SERVER_NAME
Wednesday, August 8, 2018
AIX: How to determine / identify volume serial for Infinibox (Infinidat) w/o HPT
How to list / identify serial number of volume from Infinibox (Infinidat) without Host Power Tools?
This command can be used to determine / list serial number of disk located on Infinibox in AIX:
for i in `lsdev -Cc disk | grep INFINIDAT | awk '{ print $1}'`do
echo $i "\c"
lsattr -El $i -a unique_id | awk '{ print $2 }' | cut -c 5-34
done
Enjoy IT!
Tuesday, January 23, 2018
TSM: ANS0338E An invalid operation was attempted on a node on target server with replication
Error message "ANS0338E An invalid operation was attempted on a node" can be related to state of node on TSM server - node can be replicated to target server and has to be removed from replication by command "remove replnode nodename".
Thursday, January 11, 2018
IBM PowerVM: lsmap for NPIV readeable output
lsmap -all -npiv is not readeable so I found nice command:
lsmap -all -npiv -field "VFC client name" "FC name" Status Name ClntName -fmt :
vfchost0: : :fcs0:NOT_LOGGED_IN
vfchost1: : :fcs0:NOT_LOGGED_IN
vfchost2: : :fcs0:NOT_LOGGED_IN
vfchost3: : :fcs0:NOT_LOGGED_IN
lsmap -all -npiv -field "VFC client name" "FC name" Status Name ClntName -fmt :
vfchost0: : :fcs0:NOT_LOGGED_IN
vfchost1: : :fcs0:NOT_LOGGED_IN
vfchost2: : :fcs0:NOT_LOGGED_IN
vfchost3: : :fcs0:NOT_LOGGED_IN
Wednesday, October 11, 2017
Linux: How to display PCI devices topology
[user@hostname ~]# lspci -tv
-+-[0007:80]-+-00.0 Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe
| +-00.1 Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe
| +-00.2 Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe
| \-00.3 Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe
+-[0005:50]---00.0 Texas Instruments TUSB73x0 SuperSpeed USB 3.0 xHCI Host Controller
+-[0004:01]---00.0 Mellanox Technologies MT27600 [Connect-IB]
+-[0003:70]---00.0 IBM PCI-E IPR SAS Adapter (ASIC)
+-[0000:01]---00.0 Mellanox Technologies MT27520 Family [ConnectX-3 Pro]
\-[0000:00]-
Thursday, November 24, 2016
Brocade SAN incoming SSH authentication not working - ssh login without password: wrong permissions on authorized_keys file
I have faced issue in FOS v7.4.1d that incoming SSH authentication (ssh login without password) did not work, even I have configured regarding to Brocade manual:
http://www.brocade.com/content/html/en/administration-guide/fos-741-adminguide/GUID-6FE6380F-52C8-4C5F-A69E-23EE7DB57E65.html
The root cause of problem was in permissions on authorized_keys on Brocade SAN SW:
Login as root user:
ssh root@SANSW
Change directory to: /fabos/users/admin/.ssh
SANSW:root> cd /fabos/users/admin/.ssh
and list permisisons
SANSW:root> ls -la
total 32
drwxr-xr-x 2 root admin 4096 Nov 13 17:27 ./
drwxr-xr-x 3 root admin 4096 Sep 8 17:30 ../
-rw-r--r-- 1 root admin 10240 Nov 13 17:27 authorizedKeys.tar
-rw------- 1 root admin 392 Nov 13 17:27 authorized_keys
-rw------- 1 root admin 392 Nov 13 17:27 authorized_keys.admin
-rw-r--r-- 1 root admin 134 Jul 15 01:09 environment
Change permissions of authorized_keys.admin file for user admin:
SANSW:root> chmod g+r,a+r authorized_keys.admin
SANSW:root> ls -la
total 32
drwxr-xr-x 2 root admin 4096 Nov 13 17:27 ./
drwxr-xr-x 3 root admin 4096 Sep 8 17:30 ../
-rw-r--r-- 1 root admin 10240 Nov 13 17:27 authorizedKeys.tar
-rw------- 1 root admin 392 Nov 13 17:27 authorized_keys
-rw-r--r-- 1 root admin 392 Nov 13 17:27 authorized_keys.admin
-rw-r--r-- 1 root admin 134 Jul 15 01:09 environment
http://www.brocade.com/content/html/en/administration-guide/fos-741-adminguide/GUID-6FE6380F-52C8-4C5F-A69E-23EE7DB57E65.html
The root cause of problem was in permissions on authorized_keys on Brocade SAN SW:
Login as root user:
ssh root@SANSW
Change directory to: /fabos/users/admin/.ssh
SANSW:root> cd /fabos/users/admin/.ssh
and list permisisons
SANSW:root> ls -la
total 32
drwxr-xr-x 2 root admin 4096 Nov 13 17:27 ./
drwxr-xr-x 3 root admin 4096 Sep 8 17:30 ../
-rw-r--r-- 1 root admin 10240 Nov 13 17:27 authorizedKeys.tar
-rw------- 1 root admin 392 Nov 13 17:27 authorized_keys
-rw------- 1 root admin 392 Nov 13 17:27 authorized_keys.admin
-rw-r--r-- 1 root admin 134 Jul 15 01:09 environment
Change permissions of authorized_keys.admin file for user admin:
SANSW:root> chmod g+r,a+r authorized_keys.admin
SANSW:root> ls -la
total 32
drwxr-xr-x 2 root admin 4096 Nov 13 17:27 ./
drwxr-xr-x 3 root admin 4096 Sep 8 17:30 ../
-rw-r--r-- 1 root admin 10240 Nov 13 17:27 authorizedKeys.tar
-rw------- 1 root admin 392 Nov 13 17:27 authorized_keys
-rw-r--r-- 1 root admin 392 Nov 13 17:27 authorized_keys.admin
-rw-r--r-- 1 root admin 134 Jul 15 01:09 environment
Thursday, November 19, 2015
AIX: How to synchronize more PP/LP in parallel by LVM NUM_PARALLEL_LPS
Command syncvg can be customized to synchronize different number of LPs in parallel
syncvg -p <#>
If you use mirrorvg you can set environment variable NUM_PARALLEL_LPS before running command:
export NUM_PARALLEL_LPS=<#>
Value <#> can be number in range of 1-32
syncvg -p <#>
If you use mirrorvg you can set environment variable NUM_PARALLEL_LPS before running command:
export NUM_PARALLEL_LPS=<#>
Value <#> can be number in range of 1-32
Monday, July 20, 2015
AIX: devscan reporting and diagnostic tool for SAN devices
Are you looking for reporting and diagnostic tool for SAN devices on AIX?
Lets try IBM support tool called devscan which can report for each LUN:
- ODM name and status
- PVID, if there is one
- Device type
- Capacity and block size
- SCSI status
- Reservation status, both SCSI-2 and SCSI-3
- ALUA status
- Time to service a SCSI Read
Source and download:
https://www-304.ibm.com/support/docview.wss?uid=aixtoolsc9e095f
Wednesday, April 1, 2015
AIX: How to get CPU / processor socket and core count for IBM Power server
Here is the command for AIX which shows you the count of processor cards (sockets) installed in your Power server including information about count of cores per one socket. The terminology processor in IBM Power server and AIX world describes core in relation to HW.
Command:
lscfg -vp|grep WAY
Example:
lscfg -vp|grep WAY
6-WAY PROC CUOD:
6-WAY PROC CUOD:
Expample shows you that system has two sockets and each has 6 cores, so system has 12 cores.
Command:
lscfg -vp|grep WAY
Example:
lscfg -vp|grep WAY
6-WAY PROC CUOD:
6-WAY PROC CUOD:
Expample shows you that system has two sockets and each has 6 cores, so system has 12 cores.
Friday, February 20, 2015
AIX: How to determine / identify volume UID from Storwize / SVC
How to list / identify volume ID UID from Storwize / SVC?
This command can be used to determine / list volume UID of disk located on Storwize / SVC in AIX:
for i in `lsdev -t 2145 | awk '{ print $1}'`do
echo $i "\c"
lsattr -El $i -a unique_id | awk '{ print $2 }' | cut -c 6-37
done
or for MPIO without HAS and SDDPCM:
for i in `lsdev -t mpioosdisk | awk '{ print $1}'`
do
echo $i "\c"
lsattr -El $i -a unique_id | awk '{ print $2 }' | cut -c 6-37
done
You get volume UID which can be used to identify disk on Storwize / SVC in GUI or running command lsvdisk.
lsvdisk -filtervalue vdisk_UID=60050111111111111000000000000002Enjoy IT!
Thursday, June 12, 2014
PowerVM: network outage during fallback in SEA load sharing environment
Problem summary
In a dual VIOS setup where SEA is configured in load sharing mode and backup SEA is created over etherchannel in IEEE802.3d mode. Rebooting backup VIOS will result in VIO client communication loss for 30 seconds.
Friday, March 28, 2014
TSM: Why are backups going to tape instead of disk
Technote (troubleshooting)
Problem(Abstract)
Tivoli Storage Manager TSM Client backups and/or
archives may go to a tape pool although the management class used sends
data to a disk pool
Cause
DISK pool is not available or does not have free space or data size exceeds threshold.
Resolving the problem
Tuesday, November 19, 2013
DS8000: Code (Firmware) Recommendation
DS8000 Code Recommendation can be found here:
http://www-01.ibm.com/support/docview.wss?uid=ssg1S1004456&myns=s028&mynp=OCST8NCA&mynp=OCSTXN8P&mynp=OCSTUVMB&mynp=OCHW2C2&mynp=OCHW2B2&mync=E
http://www-01.ibm.com/support/docview.wss?uid=ssg1S1004456&myns=s028&mynp=OCST8NCA&mynp=OCSTXN8P&mynp=OCSTUVMB&mynp=OCHW2C2&mynp=OCHW2B2&mync=E
Subscribe to:
Posts (Atom)