Вы находитесь на странице: 1из 1042

Solaris CLuster

Descripcion comando
Ruta cluster /usr/cluster/bin/cluster
Page 1
ibase=16
obase=16
converir hexa a decimal
reinicio y mensaje messagess shutdown -Fr +1 "El servidor se reinicia por mantenimiento DOMINO en 2 minutos"
PROBADO Y RECOMPROBADO
Page 2
ibase=16
shutdown -Fr +1 "El servidor se reinicia por mantenimiento DOMINO en 2 minutos"
Page 3
Descripcion Solucion
cuando no sirva el ERRPT luksvrtsm/home/ibmadmcc >errpt -a
0315-021 Cannot open error message catalog /var/adm/ras/codepoint.cat.
The error report will still run, but it will not have explanatory messages.
luksvrtsm/home/ibmadmcc >cd /var/adm/ras
luksvrtsm/var/adm/ras >ls -l codepoint*
-rw-r--r-- 1 bin bin 67872 Feb 22 2011 codepoint.cat.gz
luksvrtsm/var/adm/ras >ls -l /usr/lib/nls/msg/$LANG/codepoint.cat
-rw-r--r-- 1 bin bin 199231 Feb 22 2011 /usr/lib/nls/msg/en_US/codepoint.cat
luksvrtsm/var/adm/ras >man cp
luksvrtsm/var/adm/ras >sudo cp -p /usr/lib/nls/msg/$LANG/codepoint.cat .
Password:
luksvrtsm/var/adm/ras >ls -l codepoint*
-rw-r--r-- 1 bin bin 199231 Feb 22 2011 codepoint.cat
-rw-r--r-- 1 bin bin 67872 Feb 22 2011 codepoint.cat.gz
luksvrtsm/var/adm/ras >errpt -a
luksvrtsm/var/adm/ras >errpt
luksvrtsm/var/adm/ras >
0315-021 Cannot open error message catalog /var/adm/ras/codepoint.cat.
The error report will still run, but it will not have explanatory messages.
-rw-r--r-- 1 bin bin 67872 Feb 22 2011 codepoint.cat.gz
luksvrtsm/var/adm/ras >ls -l /usr/lib/nls/msg/$LANG/codepoint.cat
-rw-r--r-- 1 bin bin 199231 Feb 22 2011 /usr/lib/nls/msg/en_US/codepoint.cat
luksvrtsm/var/adm/ras >sudo cp -p /usr/lib/nls/msg/$LANG/codepoint.cat .
-rw-r--r-- 1 bin bin 199231 Feb 22 2011 codepoint.cat
-rw-r--r-- 1 bin bin 67872 Feb 22 2011 codepoint.cat.gz
acceso a servers altamira
Se ingresa a la tsm telefonica
Se salta a la maquina sg-au-cmcol03 10.201.136.122
Y de ahy ssh a las de altamira
Page 6
SVEA Physloc
------ --------------------------------------------
ent12 U9179.MHB.06BA4DP-V2-C10-T1 Virtual
SEA ent30 compartida
Backing device ent26 Fisica
Status Available
Physloc
1 Fisica ent26 real adapter Se compone de etherchannel
2 ctl_chan ent19
3 virtual ent12 List of virtual adapters associated with the SEA
4 compartida ent30 X lsattr -El SEA
etherchannel etherchannel etherchannel etherchannel
Switch
Crear una seahttp://notanothersheep.com/node/48
STORAGE-IBM-SAP-BEST-PRACTICES
Descripcion Comandos Observaciones
Se deben crear los VG escalables Opcion -s El almacenamiento debe ser IBM
Tambien se deben crear los lv con la opcion Mklv -ex
Los logical volume se deben revisar as Si tienen interpolicy maximum estan bien si no validar e informar
Bases de datos /Oracle/$SID/sapdata1
/Oracle/$SID/origlogA El MirrlogA es el backup de orilogA
/Oracle/$SID/origlogB El MirrlogB es el backup de orilogB
MirrlogA
MirrlogB
SAP VGLOGS Orig, mirrlog
VGDATA Sapdata y otros
VGSAP /usr/sap/trans
/usr/sap/exe
/usr/sap/app
Page 9
STORAGE-IBM-SAP-BEST-PRACTICES
Page 10
STORAGE-IBM-SAP-BEST-PRACTICES
Page 11
STORAGE-IBM-SAP-BEST-PRACTICES
Page 12
STORAGE-IBM-SAP-BEST-PRACTICES
Page 13
STORAGE-IBM-SAP-BEST-PRACTICES
Page 14
STORAGE-IBM-SAP-BEST-PRACTICES
mklv -t paging -y paging00 swapvg 798 >> crear el lv de paging
Page 15
STORAGE-IBM-SAP-BEST-PRACTICES
Si tienen interpolicy maximum estan bien si no validar e informar
El MirrlogA es el backup de orilogA
El MirrlogB es el backup de orilogB
Page 16
STORAGE-IBM-SAP-BEST-PRACTICES
Page 17
STORAGE-IBM-SAP-BEST-PRACTICES
Page 18
STORAGE-IBM-SAP-BEST-PRACTICES
Page 19
STORAGE-IBM-SAP-BEST-PRACTICES
Page 20
STORAGE-IBM-SAP-BEST-PRACTICES
Page 21
STORAGE-IBM-SAP-BEST-PRACTICES
mklv -t paging -y paging00 swapvg 798 >> crear el lv de paging
Page 22
INFORMACION IBM
Descripcin
Ver estado de agente de monitoreo en la ruta /opt/IBM/ITM/bin
Direccion ip para acceder a los servidores de suramericana
Direccion ip Windows para acceder a los servidores de Bancolombia
Scrippt para los clientes en los QEV cuando se deba preservar la informacion en el geckos
Informes de gestion y desempeo
/usr/sbin/pcmpath query essmap | grep -w $real |grep path0 |awk '{print $5}'
Page 23
INFORMACION IBM
Page 24
INFORMACION IBM
Page 25
INFORMACION IBM
Page 26
INFORMACION IBM
Page 27
INFORMACION IBM
sudo pcmpath query device|more
Page 28
INFORMACION IBM
Comando User Passwd
sudo ./cinfo -R
192.168.250.131
10.222.39.18
cat /tmp/users.txt | awk -F : '{print "sudo /usr/sbin/usermod -c \"661/C/*CDPTMR//DPE_CO_COLOMBIA_TELECOMUNICACIONES_SA-MIDRANGE/"$2"\" "$1}'
url
/usr/sbin/pcmpath query essmap | grep -w $real |grep path0 |awk '{print $5}'
Page 29
INFORMACION IBM
Page 30
INFORMACION IBM
Page 31
INFORMACION IBM
Page 32
INFORMACION IBM
Page 33
INFORMACION IBM
sudo pcmpath query device|more
Page 34
INFORMACION IBM
cat /tmp/users.txt | awk -F : '{print "sudo /usr/sbin/usermod -c \"661/C/*CDPTMR//DPE_CO_COLOMBIA_TELECOMUNICACIONES_SA-MIDRANGE/"$2"\" "$1}'
/usr/sbin/pcmpath query essmap | grep -w $real |grep path0 |awk '{print $5}'
Page 35
MANEJO DE IF
compara igualdad de expresiones que resultan en un nmero. Pueden ser expresiones numricas o lgicas, ya que stas tambin resultan en nmeros. Los operadores numricos derivan sus letras del ingles
-eq (igualdad)
-neq (no igual, desigualdad)
-lt (menor)
-gt (mayor)
-le (menor o igual)
-ge (mayor o igual)
Page 36
MANEJO DE IF
compara igualdad de expresiones que resultan en un nmero. Pueden ser expresiones numricas o lgicas, ya que stas tambin resultan en nmeros. Los operadores numricos derivan sus letras del ingles
Page 37
MANEJO DE IF
compara igualdad de expresiones que resultan en un nmero. Pueden ser expresiones numricas o lgicas, ya que stas tambin resultan en nmeros. Los operadores numricos derivan sus letras del ingles
Page 38
agregar HBA VIrtual in aix NPIV
Descripcion Pasos
Se tiene una lpar sin nada recien instaladas
Se requiere ingresar un HBA a la lpar
1
2
3
Page 39
agregar HBA VIrtual in aix NPIV
NPIV
Se debe agregar el FC a la lpar en la hmc y al Vio cosa que concuerden los dos
Despues de ello se va a la lpar y se reconoce el device fcsX Cfgmgr
Page 40
SALIDA STANDAR Y ERROR DE LOG
Salida estandar * * * * * /usr/sap/trans/bin/transfer_datafiles.sh > /tmp/evcidencia.txt
Salida error * * * * * /usr/sap/trans/bin/transfer_datafiles.sh > /home/eq1adm/evidencia.txt 2>&1
Page 41
SALIDA STANDAR Y ERROR DE LOG
* * * * * /usr/sap/trans/bin/transfer_datafiles.sh > /tmp/evcidencia.txt
* * * * * /usr/sap/trans/bin/transfer_datafiles.sh > /home/eq1adm/evidencia.txt 2>&1
Page 42
Scripts
Descripcin
Mover archivos viejos a /interfase/movil/salida/historia y dejar los archivos actuales
Page 43
Scripts
Comandos
########## tarea1 usuario erpadm
#Se ejecuta a las 18:00 lunes, miercoles y viernes
#!/usr/bin/ksh
ruta=/interfase/movil/salida
cd $ruta
fecha=$(date +%m%e)
actual="G_DESCUENTOS____2012$fecha"
ayer=$(ls |grep -v $actual |grep G_DESCUENTOS____2012)
mv /interfase/movil/salida/$ayer /interfase/movil/salida/historia
mv /interfase/movil/salida/O_DDIC* /interfase/movil/salida/historia
Page 44
ORACLE rack
BAJAR SERVICIOS EN ORACLE OHME
SETEAR PARAMETROS DE RED PERSISTENTES
Page 45
ORACLE rack
cobogceoprd02/u01/app/11.2.0.2/grid/bin >crsctl stop cluster
no -p -o udp_sendspace=65536
Page 46
Auditoria aix
sudo aixpert -c -p >> Correr el script para ver las desviaciones
sudo audit query >> ver si estan corriendo la audioria
sudo audit shutdown >> apagar la auitoria
sudo audit on >> arrancar la auditoria
sudo audit start >> iniciar el bin process
OJO no darle esto "sudo audit on ; sudo audit off" (por que se puede caer la maquina) (Esto es )
sudo /usr/sbin/aixpert -c
/etc/security/aixpert/check_report.txt
/usr/sbin/aixpert -f /etc/security/aixpert/core/appliedaixpert.xml
Page 47
Auditoria aix
OJO no darle esto "sudo audit on ; sudo audit off" (por que se puede caer la maquina) (Esto es )
Ver cuantas desviaciones hay
Ver las desviaciones
pasa la norma y corrige todo
Page 48
Auditoria aix
/etc/security/aixpert/log/ logs no ver
pero hay que corregir el archivo /etc/security/aixpert/core/appliedaixpert.xml PILAS CON LA MASCARA PARA SAP
mls_minalpha_1ABB51AB_B17EBC84
entonces antes de ejecutar la norma sacar copia del /etc/security/aixpert/core/appliedaixpert.xml
ejecutar norma
renombrar el otro archivo para no tener que moficar nada adentro
Page 49
Auditoria aix
PILAS CON LA MASCARA PARA SAP
Page 50
gssd y nfsgyd
gssd y nfsgyd 1BA7DF4E
If kerberos support is not installed, the gssd daemon will not start.
Ensure that the krb5.client.rte and modcrypt.base filesets are installed. If either is not installed, the gssd daemon will not run.
Page 51
gssd y nfsgyd
Ensure that the krb5.client.rte and modcrypt.base filesets are installed. If either is not installed, the gssd daemon will not run.
Page 52
AGENTES DE MONITOREO TSM
DESCRIPCION
Instalacio de agentes de tivoli monitoring
Page 53
AGENTES DE MONITOREO TSM
Page 54
AGENTES DE MONITOREO TSM
Page 55
AGENTES DE MONITOREO TSM
En el archivo /opt/IBM/ITM/config/kul_configfile
Limpieza logs Agentes Monitoreo
Page 56
AGENTES DE MONITOREO TSM
Script para revisar el estado del agente
Cambio_Hostname_Agente_Tivoli
Page 57
AGENTES DE MONITOREO TSM
Depurara el archivo /var/adm/wtmp
Page 58
AGENTES DE MONITOREO TSM
COMANDOS
Instalacion de agente tivoli agent monitoring
1. El instalador est en vmserver SABmiller /tiv
2. Se ejecuta el archivo /install.sh en esta carpeta y muestra lo siguiente:
PRODUCTIVO-pcbpbwd1:/tiv>./install.sh
INSTALL
Enter the name of the IBM Tivoli Monitoring directory
[ default = /opt/IBM/ITM ]:
ITM home directory "/opt/IBM/ITM" already exists.
OK to use it [ 1-yes, 2-no; "1" is default ]?
Select one of the following:
1) Install products to the local host.
2) Install products to depot for remote deployment (requires TEMS).
3) Install TEMS support for remote seeding
4) Exit install.
Please enter a valid number: 1
Initializing ...
International Program License Agreement
Part 1 - General Terms
BY DOWNLOADING, INSTALLING, COPYING, ACCESSING, CLICKING ON
AN "ACCEPT" BUTTON, OR OTHERWISE USING THE PROGRAM,
LICENSEE AGREES TO THE TERMS OF THIS AGREEMENT. IF YOU ARE
ACCEPTING THESE TERMS ON BEHALF OF LICENSEE, YOU REPRESENT
AND WARRANT THAT YOU HAVE FULL AUTHORITY TO BIND LICENSEE
TO THESE TERMS. IF YOU DO NOT AGREE TO THESE TERMS,
- DO NOT DOWNLOAD, INSTALL, COPY, ACCESS, CLICK ON AN
"ACCEPT" BUTTON, OR USE THE PROGRAM; AND
- PROMPTLY RETURN THE UNUSED MEDIA, DOCUMENTATION, AND
Press Enter to continue viewing the license agreement, or
enter "1" to accept the agreement, "2" to decline it, "3"
to print it, "4" to read non-IBM terms, or "99" to go back
Page 59
AGENTES DE MONITOREO TSM
to the previous screen.
1
Enter a 32-character encryption key, or just press Enter to use the default
Default = IBMTivoliMonitoringEncryptionKey
....+....1....+....2....+....3..
GSkit encryption key has been set.
Key File directory: /opt/IBM/ITM/keyfiles
Product packages are available in /tiv/unix
The following products are currently installed in "/opt/IBM/ITM:"
IBM GSKit Security Interface V07.40.27.00 @ HP-UX R11 Integrity (32 bit)
IBM GSKit Security Interface V07.40.27.00 @ HP-UX R11 Integrity (64 bit)
All agents require that application support files that contain agent-specific information be installed on the Tivoli Enterprise Monitoring Server that the agents will connect to, Tivoli Enterprise Portal Server and Tivoli Enterprise Portal desktop and browser client. Install application support before starting to install any Tivoli Enterprise Monitoring Agents.
The following products are available for installation:
1) Agentless Monitoring for AIX Operating Systems V06.22.02.00
2) Agentless Monitoring for HP-UX Operating Systems V06.22.02.00
3) Agentless Monitoring for Linux Operating Systems V06.22.02.00
4) Agentless Monitoring for Solaris Operating Systems V06.22.02.00
5) Agentless Monitoring for Windows Operating Systems V06.22.02.00
6) Monitoring Agent for UNIX Logs V06.22.02.00
7) Monitoring Agent for UNIX OS V06.22.02.00
8) Tivoli Enterprise Services User Interface Extensions V06.22.02.00
9) Universal Agent V06.22.02.00
10) all of the above
Type the numbers for the products you want to install, type "b" to change operating system, or type "q" to quit selection.
If you enter more than one number, separate the numbers by a comma or a space.
Type your selections here: 6 7
The following products will be installed:
Monitoring Agent for UNIX Logs V06.22.02.00
Monitoring Agent for UNIX OS V06.22.02.00
Are your selections correct [ 1=Yes, 2=No ; default is "1" ] ?
Page 60
AGENTES DE MONITOREO TSM
... installing "Monitoring Agent for UNIX Logs V06.22.02.00 for HP-UX R11 Integrity (64 bit)"; please wait.
=> installed "Monitoring Agent for UNIX Logs V06.22.02.00 for HP-UX R11 Integrity (64 bit)".
... Initializing component Monitoring Agent for UNIX Logs V06.22.02.00 for HP-UX R11 Integrity (64 bit).
... Monitoring Agent for UNIX Logs V06.22.02.00 for HP-UX R11 Integrity (64 bit) initialized.
... installing "Monitoring Agent for UNIX OS V06.22.02.00 for HP-UX R11 Integrity (64 bit)"; please wait.
=> installed "Monitoring Agent for UNIX OS V06.22.02.00 for HP-UX R11 Integrity (64 bit)".
... Initializing component Monitoring Agent for UNIX OS V06.22.02.00 for HP-UX R11 Integrity (64 bit).
... Monitoring Agent for UNIX OS V06.22.02.00 for HP-UX R11 Integrity (64 bit) initialized.
Do you want to install additional products or product support packages [ 1=Yes, 2=No ; default is "2" ] ? 2
... postprocessing; please wait.
... finished postprocessing.
Installation step complete.
You may now configure any locally installed IBM Tivoli Monitoring product via the "/opt/IBM/ITM/bin/itmcmd config" command.
3. Se va a la carpeta /opt/IBM/ITM/bin/ y se ejecuta el ./itmcmd config -A ul y ./itmcmd config ux muestra un mensaje asi:
NOta: dependiendo del cliente en el campo TEMS Host Name se digita el la direccion ip del servidor de tivoli que tiene este cliente.
En el caso de SABMILLER es 10.1.129.247:
RODUCTIVO-pcbpbwd1:/opt/IBM/ITM/bin>./itmcmd config -A ux
Agent configuration started...
Will this agent connect to a TEMS? [1=YES, 2=NO] (Default is: 1):
TEMS Host Name (Default is: 10.162.2.27): 10.162.2.247
Network Protocol [ip, sna, ip.pipe or ip.spipe] (Default is: ip.pipe):
Now choose the next protocol number from one of these:
- ip
- sna
- ip.spipe
- 0 for none
Network Protocol 2 (Default is: ip):
Now choose the next protocol number from one of these:
- sna
Page 61
AGENTES DE MONITOREO TSM
- ip.spipe
- 0 for none
Network Protocol 3 (Default is: 0):
IP Port Number (Default is: 1918):
IP.PIPE Port Number (Default is: 1918):
Enter name of KDC_PARTITION (Default is: null):
Configure connection for a secondary TEMS? [1=YES, 2=NO] (Default is: 2):
Enter Optional Primary Network Name or 0 for "none" (Default is: 0):
Are you installing this product into a clustered environment [1=YES, 2=NO] (Default is: 2):
Se quita el comentario de errpt /var/adm/ras
Ojo para esto hay que bajar los agentes
---no olvidar avisar a command center ----
cd /opt/IBM/ITM/bin
sudo ./itmcmd agent stop ux
sudo ./itmcmd agent stop ul
sudo ./itmcmd agent stop px
Buscar un archivo RunInfo en la siguiente direccion
cd /opt/IBM/ITM/config/.ConfigData
cat RunInfo
para ver la basura que hay
luego remover el archivo
rm /opt/IBM/ITM/config/.ConfigData/RunInfo
y luego subir los agentes
cd /opt/IBM/ITM/bin
sudo
sudo ./itmcmd agent start ul
sudo ./itmcmd agent start px
Page 62
AGENTES DE MONITOREO TSM
Revisar si estan corriendo
cd /opt/IBM/ITM/bin
./cinfo -r
por ultimo revisar que el archivo se haya creado.
cat /opt/IBM/ITM/config/.ConfigData/RunInfo
check_agent_ITM.sh en /home/ibmadmux/Desktop/INFORMACION/SCRIPTS
Es necesario reportar al Command Center que se bajarn los Agentes del
Servidor al que se le cambiar el Hostname Y notificar de nuevo que se
subieron.
1. Es necesario que se realice el cambio de Hostname como root.
2. Los agentes deben ser bajados. Se ejecuta estas lneas de comando
ps -fea | grep -i itm #Para listar procesos
/opt/IBM/ITM/bin/cinfo -R #Para listar los estados de los Agentes
/opt/IBM/ITM/bin/itmcmd agent stop all #Para bajar TODOS los Agentes
Para asegurarse de hacer correctamente el cambio de hostname, validar que
existen los archivos .conf y .ini de los agentes UX UL y PX
cd /opt/IBM/ITM/config
ls
4. Ingresar a px.ini para realizar el cambio de hostname:
vi px.ini
5. Estando en el vi de px.ini, en la ltima parte aparecer estas dos lneas:
CTIRA_HOSTNAME=
CTIRA_SYSTEM_NAME=
6. Escribir entre comillas simples el nuevo HOSTNAME sin dejar espacios:
Por ejemplo:
CTIRA_HOSTNAME='nodo2_Sambox_test'
CTIRA_SYSTEM_NAME='nodo2_Sambox_test'
7. Realizar los pasos 4, 5 y 6 para el ux.ini y el ul.ini:
vi ux.ini
vi ul.ini
Observacin: El Nuevo Hostname deber ser el mismo para px.ini, ux.ini y
ul.ini
8. Validar en cada agente haciendo:
cat px.ini
cat ux.ini
cat ul.ini
9. Por ltimo, se deben subir los agentes para el servidor. Ejecutar:
/opt/IBM/ITM/bin/itmcmd agent start all
y luego validar con:
/opt/IBM/ITM/bin/cinfo -R
ps -fea | grep -i itm
Page 63
AGENTES DE MONITOREO TSM
10. Reportar al Command Center que los agentes estn correctamente Arriba.
Validar un filesystem con suficiente espacio (aprox. de la mita, por ejemplo
/tmp)
Convertir el archivo wtmp a ASCII y limpiar el archivo /var/adm/wtmp:
/usr/sbin/acct/fwtmp < /var/adm/wtmp > /tmp/wtmp_dummy_`date
"+%d%m%y"`;> /var/adm/wtmp
Convertir un archivo ASCII de /var/adm/wtmp al formato wtmp:
/usr/sbin/acct/fwtmp -ic < /tmp/wtmp_dummy > /var/adm/wtmp
Page 64
AGENTES DE MONITOREO TSM
Page 65
AGENTES DE MONITOREO TSM
All agents require that application support files that contain agent-specific information be installed on the Tivoli Enterprise Monitoring Server that the agents will connect to, Tivoli Enterprise Portal Server and Tivoli Enterprise Portal desktop and browser client. Install application support before starting to install any Tivoli Enterprise Monitoring Agents.
Type the numbers for the products you want to install, type "b" to change operating system, or type "q" to quit selection.
Page 66
AGENTES DE MONITOREO TSM
... installing "Monitoring Agent for UNIX Logs V06.22.02.00 for HP-UX R11 Integrity (64 bit)"; please wait.
... Initializing component Monitoring Agent for UNIX Logs V06.22.02.00 for HP-UX R11 Integrity (64 bit).
... installing "Monitoring Agent for UNIX OS V06.22.02.00 for HP-UX R11 Integrity (64 bit)"; please wait.
Do you want to install additional products or product support packages [ 1=Yes, 2=No ; default is "2" ] ? 2
You may now configure any locally installed IBM Tivoli Monitoring product via the "/opt/IBM/ITM/bin/itmcmd config" command.
3. Se va a la carpeta /opt/IBM/ITM/bin/ y se ejecuta el ./itmcmd config -A ul y ./itmcmd config ux muestra un mensaje asi:
NOta: dependiendo del cliente en el campo TEMS Host Name se digita el la direccion ip del servidor de tivoli que tiene este cliente.
Page 67
AGENTES DE MONITOREO TSM
Page 68
AGENTES DE MONITOREO TSM
Page 69
AGENTES DE MONITOREO TSM
Page 70
AGENTES DE MONITOREO TSM
Page 71
AGENTES DE MONITOREO TSM
All agents require that application support files that contain agent-specific information be installed on the Tivoli Enterprise Monitoring Server that the agents will connect to, Tivoli Enterprise Portal Server and Tivoli Enterprise Portal desktop and browser client. Install application support before starting to install any Tivoli Enterprise Monitoring Agents.
Page 72
AGENTES DE MONITOREO TSM
Page 73
AGENTES DE MONITOREO TSM
Page 74
AGENTES DE MONITOREO TSM
Page 75
AGENTES DE MONITOREO TSM
Page 76
AGENTES DE MONITOREO TSM
Page 77
AGENTES DE MONITOREO TSM
All agents require that application support files that contain agent-specific information be installed on the Tivoli Enterprise Monitoring Server that the agents will connect to, Tivoli Enterprise Portal Server and Tivoli Enterprise Portal desktop and browser client. Install application support before starting to install any Tivoli Enterprise Monitoring Agents.
Page 78
ALARMAS CLIENTES
Cliente Alarma FS Action plan Server
Colombina /oracle/PIC/oraarch Escalar a Sandra Silva sappidrp
Page 79
ALARMAS CLIENTES
Descripcin
Este lo revisa sap y ellos lo pueden depurar pidiendo un backup a tsm
Page 80
PRNG ssh problema
# ls -l /dev/random /dev/urandom
crw-r--r-- 1 root system 39, 0 Jan 22 10:48
/dev/random
crw-r--r-- 1 root system 39, 1 Jan 22 10:48
/dev/urandom
# chmod o+r /dev/random /dev/urandom
# stopsrc -s sshd
# startsrc -s sshd
Si no funciona
# stopsrc -s sshd
# rm -rf /dev/random
# rm -rf /dev/urandom
# mknod /dev/random c 39 0
# mknod /dev/urandom c 39 1
# randomctl -l
# ls -ald /dev/random /dev/urandom
# startsrc -s sshd
Page 81
ONLY HMC
DESCRIPCION COMANDOS
Visualizar que virtual scsi de una lpar pertenece a un VIOSERVER lshwres -r virtualio --rsubtype scsi -m $mach --level lpar -F lpar_name,lpar_id,remote_lpar_name,slot_num,remote_slot_num
Ver la capacidad de los servidores, tambien muestra todas las cajas y sus capacidades
Informacin del WIKY
Cambiar geckos del usuario chhmcusr -i
Cambiar los geckos de un usuario en la HMC
chhmcusr -i "name=lp,description=\"661;S;*CHMCSG;CO_ADM_HMC_SEGUROS_DEL_ESTADO\""
Crear un usuario mkhmcusr -u ibmitspc -d "661/I/C04200//Castano Cardenas. Paula Andrea/pcastan@co.ibm.com" -a hmcsuperadmin -M 90 --passwd 'Liberty12'
chhmcusr -i "name=ibmitspc,remote_webui_access=1,remote_ssh_access=1,pwage=90"
VALIDAR LOS DISPOSITIVOS VIRTUALES QUE TIENE UNA LPAR for machine in `lssyscfg -r sys -F name`
Este script valida cuantos dispositivos virtuales tiene cada una de las lpar, mostrando como
est en el perfil, hasta cuanto es lo maximo que puede llegar y cuanto est consumiendo en
el momento. Desde una HMC do
echo -e "\nCOMO EST LA CONFIGURACION EN CADA UNO DE LOS PERFILES"
echo $machine
lssyscfg -r prof -m $machine -F name,lpar_name,lpar_id,max_virtual_slots
echo -e "\nMAXIMO CUANTOS DISPOSITIVOS SOPORTA CADA PARTICION"
lshwres -m $machine -r virtualio --rsubtype slot --level lpar -F lpar_name,lpar_id,curr_max_virtual_slots
echo -e "\nACTUALMENTE CUANTOS DISPOSITIVOS SE ESTAN USANDO"
for lparname in `lssyscfg -r lpar -m $machine -F name`
do
export lparid=`lssyscfg -r lpar -m $machine -F lpar_id --filter lpar_names=$lparname`
export slots=0
slots=$(($slots+`lshwres -m $machine -r virtualio --rsubtype fc --level lpar --filter lpar_ids=$lparid|grep -c lpar_name`))
slots=$(($slots+`lshwres -m $machine -r virtualio --rsubtype eth --level lpar --filter lpar_ids=$lparid|grep -c lpar_name`))
slots=$(($slots+`lshwres -m $machine -r virtualio --rsubtype serial --level lpar --filter lpar_ids=$lparid|grep -c lpar_name`))
slots=$(($slots+`lshwres -m $machine -r virtualio --rsubtype scsi --level lpar --filter lpar_ids=$lparid|grep -c lpar_name`))
echo "$lparname: $slots slots"
done
done
COMANDOS DE HMC Lswres
Lssyscfg
The lssyscfg command is used to get information about the attributes of managed
systems
Comandos cambio de contrasea chhmcusr -u ibmitsds -t passwd -v Colombia2012
Eliminar un usuario rmhmcusr -u ibmadmrc
Page 82
ONLY HMC
lshwres -r virtualio --rsubtype scsi -m $mach --level lpar -F lpar_name,lpar_id,remote_lpar_name,slot_num,remote_slot_num
Cambiar los geckos de un usuario en la HMC
chhmcusr -i "name=lp,description=\"661;S;*CHMCSG;CO_ADM_HMC_SEGUROS_DEL_ESTADO\""
mkhmcusr -u ibmitspc -d "661/I/C04200//Castano Cardenas. Paula Andrea/pcastan@co.ibm.com" -a hmcsuperadmin -M 90 --passwd 'Liberty12'
chhmcusr -i "name=ibmitspc,remote_webui_access=1,remote_ssh_access=1,pwage=90"
for machine in `lssyscfg -r sys -F name`
echo -e "\nCOMO EST LA CONFIGURACION EN CADA UNO DE LOS PERFILES"
echo $machine
lssyscfg -r prof -m $machine -F name,lpar_name,lpar_id,max_virtual_slots
echo -e "\nMAXIMO CUANTOS DISPOSITIVOS SOPORTA CADA PARTICION"
lshwres -m $machine -r virtualio --rsubtype slot --level lpar -F lpar_name,lpar_id,curr_max_virtual_slots
echo -e "\nACTUALMENTE CUANTOS DISPOSITIVOS SE ESTAN USANDO"
for lparname in `lssyscfg -r lpar -m $machine -F name`
export lparid=`lssyscfg -r lpar -m $machine -F lpar_id --filter lpar_names=$lparname`
slots=$(($slots+`lshwres -m $machine -r virtualio --rsubtype fc --level lpar --filter lpar_ids=$lparid|grep -c lpar_name`))
slots=$(($slots+`lshwres -m $machine -r virtualio --rsubtype eth --level lpar --filter lpar_ids=$lparid|grep -c lpar_name`))
slots=$(($slots+`lshwres -m $machine -r virtualio --rsubtype serial --level lpar --filter lpar_ids=$lparid|grep -c lpar_name`))
slots=$(($slots+`lshwres -m $machine -r virtualio --rsubtype scsi --level lpar --filter lpar_ids=$lparid|grep -c lpar_name`))
echo "$lparname: $slots slots"
Revisa estado online
Revisa configuracion
The lssyscfg command is used to get information about the attributes of managed
chhmcusr -u ibmitsds -t passwd -v Colombia2012
rmhmcusr -u ibmadmrc
Page 83
ONLY HMC
lshwres -r virtualio --rsubtype scsi -m $mach --level lpar -F lpar_name,lpar_id,remote_lpar_name,slot_num,remote_slot_num
mkhmcusr -u ibmitspc -d "661/I/C04200//Castano Cardenas. Paula Andrea/pcastan@co.ibm.com" -a hmcsuperadmin -M 90 --passwd 'Liberty12'
slots=$(($slots+`lshwres -m $machine -r virtualio --rsubtype eth --level lpar --filter lpar_ids=$lparid|grep -c lpar_name`))
slots=$(($slots+`lshwres -m $machine -r virtualio --rsubtype serial --level lpar --filter lpar_ids=$lparid|grep -c lpar_name`))
slots=$(($slots+`lshwres -m $machine -r virtualio --rsubtype scsi --level lpar --filter lpar_ids=$lparid|grep -c lpar_name`))
Page 84
VER ERRPT
VER ERRPT
errpt -t | awk '/SC_DISK_ERR9/ {print
$1}' | xargs errpt -atj
Page 85
terminal_hmc_open_terminal
Para trabajar con la hmc, por tunel ssh, es necesario abrir los purtos
80,443,8443,9960,9735,2300,2301,2302
Si se van a abrir varias consolas a servidores, se sugiere abrir el rango de puerto 30000-30009
Comparto un ejemplo
#!/bin/sh
/usr/bin/tsocks /usr/bin/ssh -fN -L 8080:11.0.2.172:80 -L 9443:11.0.2.172:443 -L 8443:11.0.2.172:8443 -L 9960:11.0.2.172:9960 -L 9735:11.0.2.172:9735 -L 2300:11.0.2.172:2300 -L 2301:11.0.2.172:2301 -L 2302:11.0.2.172:2302 -L 30000:11.0.2.172:30000 -L 30001:11.0.2.172:30001 -L 30002:11.0.2.172:30002 -L 30003:11.0.2.172:30003 -L 30004:11.0.2.172:30004 -L 30005:11.0.2.172:30005 -L 30006:11.0.2.172:30006 -L 30007:11.0.2.172:30007 -L 30008:11.0.2.172:30008 -L 30009:11.0.2.172:30009 ibmadmed@10.1.135.86
Page 86
terminal_hmc_open_terminal
Si se van a abrir varias consolas a servidores, se sugiere abrir el rango de puerto 30000-30009
/usr/bin/tsocks /usr/bin/ssh -fN -L 8080:11.0.2.172:80 -L 9443:11.0.2.172:443 -L 8443:11.0.2.172:8443 -L 9960:11.0.2.172:9960 -L 9735:11.0.2.172:9735 -L 2300:11.0.2.172:2300 -L 2301:11.0.2.172:2301 -L 2302:11.0.2.172:2302 -L 30000:11.0.2.172:30000 -L 30001:11.0.2.172:30001 -L 30002:11.0.2.172:30002 -L 30003:11.0.2.172:30003 -L 30004:11.0.2.172:30004 -L 30005:11.0.2.172:30005 -L 30006:11.0.2.172:30006 -L 30007:11.0.2.172:30007 -L 30008:11.0.2.172:30008 -L 30009:11.0.2.172:30009 ibmadmed@10.1.135.86
Page 87
terminal_hmc_open_terminal
/usr/bin/tsocks /usr/bin/ssh -fN -L 8080:11.0.2.172:80 -L 9443:11.0.2.172:443 -L 8443:11.0.2.172:8443 -L 9960:11.0.2.172:9960 -L 9735:11.0.2.172:9735 -L 2300:11.0.2.172:2300 -L 2301:11.0.2.172:2301 -L 2302:11.0.2.172:2302 -L 30000:11.0.2.172:30000 -L 30001:11.0.2.172:30001 -L 30002:11.0.2.172:30002 -L 30003:11.0.2.172:30003 -L 30004:11.0.2.172:30004 -L 30005:11.0.2.172:30005 -L 30006:11.0.2.172:30006 -L 30007:11.0.2.172:30007 -L 30008:11.0.2.172:30008 -L 30009:11.0.2.172:30009 ibmadmed@10.1.135.86
Page 88
terminal_hmc_open_terminal
/usr/bin/tsocks /usr/bin/ssh -fN -L 8080:11.0.2.172:80 -L 9443:11.0.2.172:443 -L 8443:11.0.2.172:8443 -L 9960:11.0.2.172:9960 -L 9735:11.0.2.172:9735 -L 2300:11.0.2.172:2300 -L 2301:11.0.2.172:2301 -L 2302:11.0.2.172:2302 -L 30000:11.0.2.172:30000 -L 30001:11.0.2.172:30001 -L 30002:11.0.2.172:30002 -L 30003:11.0.2.172:30003 -L 30004:11.0.2.172:30004 -L 30005:11.0.2.172:30005 -L 30006:11.0.2.172:30006 -L 30007:11.0.2.172:30007 -L 30008:11.0.2.172:30008 -L 30009:11.0.2.172:30009 ibmadmed@10.1.135.86
Page 89
terminal_hmc_open_terminal
/usr/bin/tsocks /usr/bin/ssh -fN -L 8080:11.0.2.172:80 -L 9443:11.0.2.172:443 -L 8443:11.0.2.172:8443 -L 9960:11.0.2.172:9960 -L 9735:11.0.2.172:9735 -L 2300:11.0.2.172:2300 -L 2301:11.0.2.172:2301 -L 2302:11.0.2.172:2302 -L 30000:11.0.2.172:30000 -L 30001:11.0.2.172:30001 -L 30002:11.0.2.172:30002 -L 30003:11.0.2.172:30003 -L 30004:11.0.2.172:30004 -L 30005:11.0.2.172:30005 -L 30006:11.0.2.172:30006 -L 30007:11.0.2.172:30007 -L 30008:11.0.2.172:30008 -L 30009:11.0.2.172:30009 ibmadmed@10.1.135.86
Page 90
terminal_hmc_open_terminal
/usr/bin/tsocks /usr/bin/ssh -fN -L 8080:11.0.2.172:80 -L 9443:11.0.2.172:443 -L 8443:11.0.2.172:8443 -L 9960:11.0.2.172:9960 -L 9735:11.0.2.172:9735 -L 2300:11.0.2.172:2300 -L 2301:11.0.2.172:2301 -L 2302:11.0.2.172:2302 -L 30000:11.0.2.172:30000 -L 30001:11.0.2.172:30001 -L 30002:11.0.2.172:30002 -L 30003:11.0.2.172:30003 -L 30004:11.0.2.172:30004 -L 30005:11.0.2.172:30005 -L 30006:11.0.2.172:30006 -L 30007:11.0.2.172:30007 -L 30008:11.0.2.172:30008 -L 30009:11.0.2.172:30009 ibmadmed@10.1.135.86
Page 91
Scripts nutresa
Descripcion
Mueve el archivo mas viejo que est en la ruta hacia /interfase/movil/salida/historia
Page 92
Scripts nutresa
#!/usr/bin/ksh
ruta=/interfase/movil/salida
cd $ruta
dia=$(date +%e)
for i in 1 2 3 4 5 6 7 8 9
do
if expr $dia = $i; then dia=0$i; fi
done
mes=$(date +%m)
for machine in `lssyscfg -r sys -F name`
actual="G_DESCUENTOS____2012$fecha"
ayer=$(ls |grep -v $actual |grep G_DESCUENTOS____2012)
mv /interfase/movil/salida/$ayer /interfase/movil/salida/historia
mv /interfase/movil/salida/O_DDIC* /interfase/movil/salida/historia
Page 93
RECUPERAR CLAVE PADMIN
RECUPERAR CLAVE PADMIN
ibmadmcm@hmc595:~> command=`printf "oem_setup_env\ncp /etc/security/passwd /tmp/passwd.new.1"`
ibmadmcm@hmc595:~> viosvrcmd -m Server-9119-FHA-SN0289DB4 -p VIO8_Produccion_SNCH -c "$command"
#Security copy
ibmadmcm@hmc595:~> command=`printf "oem_setup_env\ncp /etc/security/passwd /tmp/passwd.new.2"`
ibmadmcm@hmc595:~> viosvrcmd -m Server-9119-FHA-SN0289DB4 -p VIO8_Produccion_SNCH -c "$command"
ibmadmcm@hmc595:~> command=`printf "oem_setup_env\ncat /etc/security/passwd"` #to check the encrypted password in the padmin line
ibmadmcm@hmc595:~> viosvrcmd -m Server-9119-FHA-SN0289DB4 -p VIO8_Produccion_SNCH -c "$command"
#replace password in file /tmp/passwd.new.1 for a well know encrypted password
ibmadmcm@hmc595:~> command=`printf 'oem_setup_env\nperl -p -i -e "s/NB\/klkuWBH6iU/QnJRbcWUhesjg/g" /tmp/passwd.new.1'`
ibmadmcm@hmc595:~> viosvrcmd -m Server-9119-FHA-SN0289DB4 -p VIO8_Produccion_SNCH -c "$command"
#replace unix time lastupdate line number in the file
ibmadmcm@hmc595:~> command=`printf 'oem_setup_env\nperl -p -i -e "s/1355453602/1365024072/g" /tmp/passwd.new.1'`
ibmadmcm@hmc595:~> viosvrcmd -m Server-9119-FHA-SN0289DB4 -p VIO8_Produccion_SNCH -c "$command"
#replace the file
ibmadmcm@hmc595:~> command=`printf "oem_setup_env\ncp /tmp/passwd.new.1 /etc/security/passwd"`
ibmadmcm@hmc595:~> viosvrcmd -m Server-9119-FHA-SN0289DB4 -p VIO8_Produccion_SNCH -c "$command"
#try to login into the vio server with the new padmin password
$swrole PAdmin
ibmadmcm's Password:
$ su - padmin
padmin's Password:
$ r o
oem_setup_env
$ ioscli oem_setup_env
# id
uid=0(root) gid=204(ibmadmin)
Page 94
RECUPERAR CLAVE PADMIN
ibmadmcm@hmc595:~> command=`printf "oem_setup_env\ncp /etc/security/passwd /tmp/passwd.new.1"`
ibmadmcm@hmc595:~> viosvrcmd -m Server-9119-FHA-SN0289DB4 -p VIO8_Produccion_SNCH -c "$command"
ibmadmcm@hmc595:~> command=`printf "oem_setup_env\ncp /etc/security/passwd /tmp/passwd.new.2"`
ibmadmcm@hmc595:~> viosvrcmd -m Server-9119-FHA-SN0289DB4 -p VIO8_Produccion_SNCH -c "$command"
ibmadmcm@hmc595:~> command=`printf "oem_setup_env\ncat /etc/security/passwd"` #to check the encrypted password in the padmin line
ibmadmcm@hmc595:~> viosvrcmd -m Server-9119-FHA-SN0289DB4 -p VIO8_Produccion_SNCH -c "$command"
ibmadmcm@hmc595:~> command=`printf 'oem_setup_env\nperl -p -i -e "s/NB\/klkuWBH6iU/QnJRbcWUhesjg/g" /tmp/passwd.new.1'`
ibmadmcm@hmc595:~> viosvrcmd -m Server-9119-FHA-SN0289DB4 -p VIO8_Produccion_SNCH -c "$command"
ibmadmcm@hmc595:~> command=`printf 'oem_setup_env\nperl -p -i -e "s/1355453602/1365024072/g" /tmp/passwd.new.1'`
ibmadmcm@hmc595:~> viosvrcmd -m Server-9119-FHA-SN0289DB4 -p VIO8_Produccion_SNCH -c "$command"
ibmadmcm@hmc595:~> command=`printf "oem_setup_env\ncp /tmp/passwd.new.1 /etc/security/passwd"`
ibmadmcm@hmc595:~> viosvrcmd -m Server-9119-FHA-SN0289DB4 -p VIO8_Produccion_SNCH -c "$command"
Page 95
Proceso Activacin
El grupo Unix Unicamente debe velar en activar los componentes ssh sudo
Pagina de medios paquetes aix oss4aix.org
Page 96
Proceso Activacin
sistema operativo modificar fechas
inicio dia de diligenciamiento
fin un mes despues de esta fecha
Page 97
Mapear CD AIX VIO
1 lsrep
2 crear el repositorio mkrep -sp rootvg -size 8G
3 Se crea el device
mkvdev -fbo -vadapter
vhost3
4 Se carga la imagen al vhost
loadopt -disk aix_61 -vtd
vtopt0
5 Se desmonta unloadopt -vtd vtopt0
m
unloadopt -vtd vtopt0

Page 98
Mapear CD AIX VIO
Page 99
Mapear CD AIX VIO
Page 100
Mapear CD AIX VIO
Page 101
Mapear CD AIX VIO
Page 102
Mapear CD AIX VIO
sudo mklv -y itm_lv -t jfs2 rootvg 1G; sudo crfs -v jfs2 -d itm_lv -m /opt/IBM/ITM -A yes -p rw; sudo mount /opt/IBM/ITM
Page 103
Mapear CD AIX VIO
Page 104
Mapear CD AIX VIO
Page 105
Mapear CD AIX VIO
Page 106
Mapear CD AIX VIO
Page 107
Mapear CD AIX VIO
Page 108
Mapear CD AIX VIO
sudo mklv -y itm_lv -t jfs2 rootvg 1G; sudo crfs -v jfs2 -d itm_lv -m /opt/IBM/ITM -A yes -p rw; sudo mount /opt/IBM/ITM
Page 109
LOGFORM
PA QUE SIRVE EL LOGFORM
Page 110
Actividad listado discos AIX
1 Se ejecuta este script
2 Se validan todos vscsi guardados en el archivo
3 Se ejecuta este comando para ver vscsi10
4 Vamos a la hmc y ejecutamos
5 Y buscamos el slot_num=14
6
Tenemos en cuenta el remote_slot_num=15
lsmap -all | grep 10 Numero de la lpar (en hexadecimal)
lsmap -vadapter vhost13 | grep Backing
Solo los discos lsmap -vadapter vhost13 | grep Backing |awk '{print $3}'
2972000 6625
Estos son los IDS que requiere storage
Page 111
Actividad listado discos AIX
Extraer lo siguiente
Saber cual es el disco del rootvg
Van por el virtualscsci 0 y 1
Ejecutamos en la lpar
Hacemos el mismo procedimiento de la hmc
Crear un repositorio
Scan rate En la memoria es la que recorre todas las paginas si ve una libre la toma pero si no hay, puede empezar a tomar la que un proceso esta utlizando
Page 112
Actividad listado discos AIX
Page 113
Actividad listado discos AIX
Page 114
Actividad listado discos AIX
Page 115
Actividad listado discos AIX
sudo pcmpath query device|more
Page 116
Actividad listado discos AIX
for disco in `lspv | awk '{print $1}'`
do
lspath -l $disco -s available -F"name:connection:parent:path_status:status" >> $HOME/prosap1.txt
done
lscfg -vpl vscsi10 Hardware Location Code......U9117.MMA.1084FC5-V10-C14-T1
lshwres -m Server-9117-MMA-SN1084FC5 -r virtualio --rsubtype scsi --level lpar --filter lpar_ids=10
lpar_name=PROSAP1,lpar_id=10,slot_num=14,state=1,is_required=0,adapter_type=client,remote_lpar_id=2,remote_lpar_name=VIO4_PRD_COLOMBINA,remote_slot_num=15
lpar_name=PROSAP1,lpar_id=10,slot_num=10,state=1,is_required=0,adapter_type=client,remote_lpar_id=1,remote_lpar_name=VIO3_PRD_COLOMBINA,remote_slot_num=15
Buscamos el remote_slot_num=15
vhost9 U9117.MMA.1084FC5-V1-C26 0x0000000a
vhost10 U9117.MMA.1084FC5-V1-C27 0x0000000a
vhost11 U9117.MMA.1084FC5-V1-C51 0x0000000a
vhost13 U9117.MMA.1084FC5-V1-C15 0x0000000a
vhost14 U9117.MMA.1084FC5-V1-C36 0x0000000a
vhost15 U9117.MMA.1084FC5-V1-C37 0x0000000a
vhost16 U9117.MMA.1084FC5-V1-C38 0x0000000a
Backing device hdisk47
Backing device hdisk48
Backing device hdisk57
Backing device hdisk58
Backing device hdisk59
Backing device hdisk60
Backing device hdisk61
Backing device hdisk62
Backing device hdisk63
Backing device hdisk64
Backing device hdisk65
Backing device hdisk215
Backing device hdisk216
Backing device hdisk222
Backing device hdisk223
Backing device hdisk260
Backing device hdisk246
Backing device hdisk299
Backing device hdisk303
Backing device hdisk18
SOLO LOS IDENTIFICAFDORES
for real in `lsmap -vadapter vhost13 | grep Backing|awk '{print $3}'` for real in `lsmap -vadapter vhost13 | grep Backing|awk '{print $3}'`
do do
/usr/sbin/pcmpath query essmap | grep $real /usr/sbin/pcmpath query essmap | grep -w $real |grep path0 |awk '{print $5}'
done done
Page 117
Actividad listado discos AIX
Lspv |grep rootvg
hdisk136 00c84fc56f00ad4c rootvg active
lspath -l hdisk136 -F"name:connection:parent"
hdisk136:ad0000000000:vscsi0 Tener en cuenta la lun
hdisk136:ad0000000000:vscsi1
lscfg -vpl vscsi0 U9117.MMA.1084FC5-V10-C2-T1
lscfg -vpl vscsi1 U9117.MMA.1084FC5-V10-C3-T1
lshwres -m Server-9117-MMA-SN1084FC5 -r virtualio --rsubtype scsi --level lpar --filter lpar_ids=10
lpar_name=PROSAP1,lpar_id=10,slot_num=3,state=1,is_required=1,adapter_type=client,remote_lpar_id=2,remote_lpar_name=VIO4_PRD_COLOMBINA,remote_slot_num=26
lpar_name=PROSAP1,lpar_id=10,slot_num=2,state=1,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=VIO3_PRD_COLOMBINA,remote_slot_num=26
ibmadmgp@vio3_prd_col$ lsmap -all |grep 000a
vhost9 U9117.MMA.1084FC5-V1-C26 0x0000000a
mkrep -sp rootvg -size 20G
En la memoria es la que recorre todas las paginas si ve una libre la toma pero si no hay, puede empezar a tomar la que un proceso esta utlizando
Page 118
Actividad listado discos AIX
Page 119
Actividad listado discos AIX
Page 120
Actividad listado discos AIX
Page 121
Actividad listado discos AIX
Page 122
Actividad listado discos AIX
lpar_name=PROSAP1,lpar_id=10,slot_num=14,state=1,is_required=0,adapter_type=client,remote_lpar_id=2,remote_lpar_name=VIO4_PRD_COLOMBINA,remote_slot_num=15
lpar_name=PROSAP1,lpar_id=10,slot_num=10,state=1,is_required=0,adapter_type=client,remote_lpar_id=1,remote_lpar_name=VIO3_PRD_COLOMBINA,remote_slot_num=15
SOLO LOS IDENTIFICAFDORES
for real in `lsmap -vadapter vhost13 | grep Backing|awk '{print $3}'`
/usr/sbin/pcmpath query essmap | grep -w $real |grep path0 |awk '{print $5}'
Page 123
Actividad listado discos AIX
lpar_name=PROSAP1,lpar_id=10,slot_num=3,state=1,is_required=1,adapter_type=client,remote_lpar_id=2,remote_lpar_name=VIO4_PRD_COLOMBINA,remote_slot_num=26
lpar_name=PROSAP1,lpar_id=10,slot_num=2,state=1,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=VIO3_PRD_COLOMBINA,remote_slot_num=26
Page 124
BACKUP_RESTORE
A924A5FC 0910042613 P S SYSPROC SOFTWARE PROGRAM ABNORMALLY TERMINATED
BC3BE5A3 0910042613 P S SRC SOFTWARE PROGRAM ERROR
192AC071 1003124913 T O errdemon ERROR LOGGING TURNED OFF
9DBCFDEE 1003125113 T O errdemon ERROR LOGGING TURNED ON
2BFA76F6 1003125013 T S SYSPROC SYSTEM SHUTDOWN BY USER
26120107 1003125113 U S LIBLVM PHYSICAL VOLUME DEFINED AS MISSING
5BEAD71B 1003125113 I S LIBLVM Activation of a no quorum volume group w
78ABDDEB 1003125113 I O SYSJ2 META-DATA I/O ERROR
78ABDDEB 1003125113 I O SYSJ2 META-DATA I/O ERROR
78ABDDEB 1003125113 I O SYSJ2 META-DATA I/O ERROR
78ABDDEB 1003125113 I O SYSJ2 META-DATA I/O ERROR
A6DF45AA 1003125113 I O RMCdaemon The daemon is started.
78ABDDEB 1003125313 I O SYSJ2 META-DATA I/O ERROR
78ABDDEB 1003125313 I O SYSJ2 META-DATA I/O ERROR
78ABDDEB 1003125313 I O SYSJ2 META-DATA I/O ERROR
78ABDDEB 1003125313 I O SYSJ2 META-DATA I/O ERROR
26120107 1003130113 U S LIBLVM PHYSICAL VOLUME DEFINED AS MISSING
5BEAD71B 1003130113 I S LIBLVM Activation of a no quorum volume group w
26120107 1003130813 U S LIBLVM PHYSICAL VOLUME DEFINED AS MISSING
5BEAD71B 1003130813 I S LIBLVM Activation of a no quorum volume group w
26120107 1003131013 U S LIBLVM PHYSICAL VOLUME DEFINED AS MISSING
5BEAD71B 1003131013 I S LIBLVM Activation of a no quorum volume group w
26120107 1003132613 U S LIBLVM PHYSICAL VOLUME DEFINED AS MISSING
5BEAD71B 1003132613 I S LIBLVM Activation of a no quorum volume group w
78ABDDEB 1003133313 I O SYSJ2 META-DATA I/O ERROR
78ABDDEB 1003133313 I O SYSJ2 META-DATA I/O ERROR
78ABDDEB 1003133313 I O SYSJ2 META-DATA I/O ERROR
78ABDDEB 1003133313 I O SYSJ2 META-DATA I/O ERROR
78ABDDEB 1003133313 I O SYSJ2 META-DATA I/O ERROR
78ABDDEB 1003133313 I O SYSJ2 META-DATA I/O ERROR
5BEAD71B 1003145513 I S LIBLVM Activation of a no quorum volume group w
26120107 1003145513 U S LIBLVM PHYSICAL VOLUME DEFINED AS MISSING
5BEAD71B 1003145513 I S LIBLVM Activation of a no quorum volume group w
26120107 1003152213 U S LIBLVM PHYSICAL VOLUME DEFINED AS MISSING
5BEAD71B 1003152213 I S LIBLVM Activation of a no quorum volume group w
5BEAD71B 1003153613 I S LIBLVM Activation of a no quorum volume group w
5BEAD71B 1003153713 I S LIBLVM Activation of a no quorum volume group w
5BEAD71B 1003154113 I S LIBLVM Activation of a no quorum volume group w
5BEAD71B 1003161413 I S LIBLVM Activation of a no quorum volume group w
26120107 1003161413 U S LIBLVM PHYSICAL VOLUME DEFINED AS MISSING
5BEAD71B 1003161413 I S LIBLVM Activation of a no quorum volume group w
Page 125
BACKUP_RESTORE
26120107 1003162713 U S LIBLVM PHYSICAL VOLUME DEFINED AS MISSING
5BEAD71B 1003162713 I S LIBLVM Activation of a no quorum volume group w
26120107 1003172313 U S LIBLVM PHYSICAL VOLUME DEFINED AS MISSING
5BEAD71B 1003172313 I S LIBLVM Activation of a no quorum volume group w
26120107 1003173813 U S LIBLVM PHYSICAL VOLUME DEFINED AS MISSING
078BA0EB 1003173813 I S LIBLVM Forced activation of a volume group
Page 126
BACKUP_RESTORE
A924A5FC 0910042613 P S SYSPROC SOFTWARE PROGRAM ABNORMALLY TERMINATED
Page 127
ONLy HPUX
Descripcion
Ver maquinas virtuales en HPUX b.11.23
Conectarse a la consola del servidor
Creacion de un filesystem para agente de SRM
Se valida en que vg se tiene espacio
Se toma del vg00 512mb y se crea el logical volume srm_lv
Se da formato
Se copia al fstab y se monta
identifcar si es un disco duro interno y listar los discos duros del sistema
Listar discos duros HPUX
se ve que son solo dos discos de 36.4 GB
Validar el espacio total del vg por ende del disco
Saber los adaptadores de red
Lista paquetes
Saber los adaptadores de fibras
Cuando aparezca el error de cambio de password
ejecutar
clarea la informacion que tiene el user
CAMBIAR PROPIETARIO DE UN ENLACE SIMBOLICO
Agregar swap en hpux
Ver como quedo la swap
Ver tamao de swap
Borrar intentos fallidos en linux
Ver los intentos fallidos
Dar formato a un logical volume
Buscar espacio libre en un vg
Page 128
ONLy HPUX
Cuando se quiera cambiar el password del user root y no sepamos la ultima contrasea
Error y no sepamos el anterior password
Se borra unicamente lo que esta en color azul y se guarda y cierra
Y se da este comando para desbloquearlo /usr/lbin/modprpw -k root
Se da passwd root
Idetificadores de los discos o Wwpn
Comprimir un filesystem /oracle
Exportar VGS en hpux
Se ubica en la ruta /tmp y se guardan en un archivos los nombres de los vgs
Cat vgsserver
Estos son los vgs de los discos externos
Se sacan los mapas de los vgs
Special files de deben guardar
Despues de haber desmontado los filesystem se procede a desactivar los vgs
Despues de borrados los vgs se eliminan los discos de la san pero del autopath
Primero se borran a nivel de autopath
Y segundo a nivel de sistema operativo aca no se muestran los discos internos osea los que tengan hardware path 73.4GST373454LC
Con este comando se Borra el disco de sistema operativo a travez del hardware path
Unir el recurso 2 al cluster HPUX
Page 129
ONLy HPUX
Ver la velocidad de una tarjeta de red en hpux
Autonegotiation = On.
7200
Page 130
ONLy HPUX
Comandos
hpvmstatus
Hpvmconsole -P BW
Se crea directorio /var/adm/perfmg
Vgdisplay (VG00) PE Size (Mb) 16 X Free PE 2730
Lvcreate -n srm_lv -L 512m vg00
newfs /dev/vg00/rsrm_lv
ioscan -fnkC disk
disk 2 1/0/0/2/0.6.0 sdisk CLAIMED DEVICE HP 36.4GST373455LC#36
/dev/dsk/c0t6d0 /dev/dsk/c0t6d0s2 /dev/rdsk/c0t6d0 /dev/rdsk/c0t6d0s2
/dev/dsk/c0t6d0s1 /dev/dsk/c0t6d0s3 /dev/rdsk/c0t6d0s1 /dev/rdsk/c0t6d0s3
disk 0 1/0/0/3/0.6.0 sdisk CLAIMED DEVICE HP 36.4GMAU3036NC
/dev/dsk/c2t6d0 /dev/dsk/c2t6d0s2 /dev/rdsk/c2t6d0 /dev/rdsk/c2t6d0s2
/dev/dsk/c2t6d0s1 /dev/dsk/c2t6d0s3 /dev/rdsk/c2t6d0s1 /dev/rdsk/c2t6d0s3
Vgdisplay (VG00) PE Size (Mb) 16 X Total PE 2730
ioscan -fnC lan
swlist
ioscan -fnC fc
Password cannot be changed. Reason: password lifetime has passed
/usr/lbin/modprpw -l -k qasadm
CHOWN -H oracle:dba rODS_asm_042
lvcreate -n lvol5 -L 4096 vg24
swapon -p 0 /dev/vg24/lvol5
swapinfo -tam
swapinfo -tam
faillog -r
faillog
sudo newfs -F vxfs -o largefiles -b 8192 /dev/vg07/rlvol2
vgdisplay | grep -e "VG Name" -e "Free PE"
Page 131
ONLy HPUX
Old password
/tcb/files/auth/r/root
:u_pwd=0sMn39Y7yxZzE:\
Y se cambia la contrasea
autopath display | grep "Lun WWN"
Lun WWN : 6005-08B4-0010-6D8A-0001-6000-0825-0000
Cd /
tar cvf /med/oracle.tar ./oracle
Vgsserver
vgexe
vgd01
vgd03
pcbqbwd1:/tmp/IBM/vgs>for i in `cat vgsserver` do vgexport -s -p -v -m $i.map /dev/$i done
ll /dev/vg*/group
Y se desmontan los filesystem asociados al vg o lV
pcbqbwd1:/tmp/IBM/vgs>for i in `cat vgsserver` do
vgchange -a n $i
vgexport -s -v -m /tmp/$i.map /dev/$i
done
Autopath display | grep "Lun WWN"|awk '{print "autopath delete -l "$NF}' >borroauto
ioscan -fnkC disk | grep disk | grep -v 73.4GST373454LC >disksan
rmsf -H 2/0/6/1/0.3.9.0.0.2.1
cmruncm -n pcbprod2
HP-UX: como ampliar un filesystem online
Page 132
ONLy HPUX
Autonegotiation = On.
7200
Page 133
ONLy HPUX
BW es la maquina virtual
43680 4gb
/dev/dsk/c0t6d0s1 /dev/dsk/c0t6d0s3 /dev/rdsk/c0t6d0s1 /dev/rdsk/c0t6d0s3
/dev/dsk/c2t6d0s1 /dev/dsk/c2t6d0s3 /dev/rdsk/c2t6d0s1 /dev/rdsk/c2t6d0s3
desqa:/etc>passwd -s qasadm
qasadm PS 09/05/11 7 90 15
desqa:/etc>passwd -s qasadm
qasadm PS 00/00/00 7 90 15
Fila total columna USED HBOGDE7:/home/ibmadmcm: swapinfo -tam
53 % usada Mb Mb Mb PCT START/ Mb
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
dev 8192 1383 6809 17% 0 - 1 /dev/vg00/lvol2
dev 8192 0 8192 0% 0 - 0 /dev/vg24/lvol5
reserve - 6511 -6511
memory 7755 4899 2856 63%
total 24139 12793 11346 53% - 0 -
Page 134
ONLy HPUX
:u_pwd=0sMn39Y7yxZzE:\
pcbqbwd1:/tmp/IBM/vgs>cat borroauto
pcbqbwd1:/tmp/IBM/vgs>cat elidsksan autopath delete -l 6005-08B4-0010-6D8A-0001-6000-0825-0000
rmsf -H 2/0/5/1/0.13.0.0.0.0.1 autopath delete -l 6005-08B4-0010-6D8A-0001-6000-082F-0000
rmsf -H 2/0/5/1/0.13.0.0.0.0.2 autopath delete -l 6005-08B4-0010-6D8A-0001-6000-0845-0000
rmsf -H 2/0/5/1/0.13.0.0.0.0.3 autopath delete -l 6005-08B4-0010-6D8A-0001-6000-084A-0000
rmsf -H 2/0/5/1/0.13.0.0.0.0.4 autopath delete -l 6005-08B4-0010-6D8A-0001-6000-084F-0000
rmsf -H 2/0/5/1/0.13.0.0.0.0.5 autopath delete -l 6005-08B4-0010-6D8A-0001-6000-085A-0000
rmsf -H 2/0/5/1/0.13.0.0.0.0.6 autopath delete -l 6005-08B4-0010-6D8A-0001-6000-081E-0000
rmsf -H 2/0/5/1/0.13.0.0.0.0.7 autopath delete -l 6005-08B4-0010-6D8A-0001-6000-0863-0000
rmsf -H 2/0/5/1/0.13.0.0.0.1.0 autopath delete -l 6005-08B4-0010-6D8A-0001-6000-082A-0000
rmsf -H 2/0/5/1/0.13.0.0.0.1.1
rmsf -H 2/0/5/1/0.13.0.0.0.1.2
lvextend -A y -L 11264 /dev/vg00/lvol8
fsadm -F vxfs -b 11534336 /var
Page 135
ONLy HPUX
pcbqbwd1:/> netstat -i
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
lo0 4136 loopback localhost 1601216319 0 1601215342 0 0
lan21 1500 10.162.5.0 pcbqbwd1 805860144 0 803987373 0 0
pcbqbwd1:/>lanadmin -x 21
Speed = 100 Full-Duplex.
Autonegotiation = On.
7200
Page 136
ONLy HPUX
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
Page 137
ONLy HPUX
autopath delete -l 6005-08B4-0010-6D8A-0001-6000-0825-0000
autopath delete -l 6005-08B4-0010-6D8A-0001-6000-082F-0000
autopath delete -l 6005-08B4-0010-6D8A-0001-6000-0845-0000
autopath delete -l 6005-08B4-0010-6D8A-0001-6000-084A-0000
autopath delete -l 6005-08B4-0010-6D8A-0001-6000-084F-0000
autopath delete -l 6005-08B4-0010-6D8A-0001-6000-085A-0000
autopath delete -l 6005-08B4-0010-6D8A-0001-6000-081E-0000
autopath delete -l 6005-08B4-0010-6D8A-0001-6000-0863-0000
autopath delete -l 6005-08B4-0010-6D8A-0001-6000-082A-0000
Page 138
Crear una lpar
Pasos
1 Ubicar el server en el cual se va a instalar
2
Page 139
INstalacion de agentes ITM
Orden Instalacion
1 Agent
2 6.21
3 Agent
4 Systemp
Page 140
ONLY VIOS
Descripcion Comandos
Mostrar todos los dispositivos scsi lsmap -all
Crear dispositivos mkdev
Una particion no debe tener mas de 26 vscsi
Mostrar todos los dispositivos scsi de red lsmap -all |grep net
Muestra los dispositivos virtuales lsdev -virtual |grep net
Muestra estadistica de la SEA entstat -all eth1 (SEA)
Pasarse a modo aix desde la vio con ello se ejecutan comandos de aix oem_setup_env
http://www.notesofanerd.com/downloads/Virtualize_CD-DVD_Devices.pdf Virtualizar unidades de CD o DVD
Page 141
CREAR UN RAW DEVICE AIX
DESCRIPCION
CREACION UN RAW DEVICE A PARTIR DE LA SOLICITUD
Por favor nos colaboran creando los siguientes raw devices en el volumen group datosvg del servidor FNABOGIQPRE y asignar permisos iq127:iq127 Nombre Raw Device Tamano hist21_iqmain_r 1598 PPS hist22_iqmain_r 1598 PPS
Page 142
CREAR UN RAW DEVICE AIX
COMANDO
mklv -t raw -y hist21_iqmain_r datosvg 1598
eso para el
priemro
donde t 03:48:09 PM
es el tipo 03:48:11 PM

y es
elnombre 03:48:16 PM

datos es el
volume
group 03:48:27 PM

y lo ultimo es
el valor 03:48:38 PM

que se puede
dar en PP o
megas o
gigas 03:48:51 PM
Por favor nos colaboran creando los siguientes raw devices en el volumen group datosvg del servidor FNABOGIQPRE y asignar permisos iq127:iq127 Nombre Raw Device Tamano hist21_iqmain_r 1598 PPS hist22_iqmain_r 1598 PPS
Page 143
CREAR UN RAW DEVICE AIX
Por favor nos colaboran creando los siguientes raw devices en el volumen group datosvg del servidor FNABOGIQPRE y asignar permisos iq127:iq127 Nombre Raw Device Tamano hist21_iqmain_r 1598 PPS hist22_iqmain_r 1598 PPS
Page 144
CMDB
CMDB
IP: 129.39.183.179
BD: inventorynew
Puerto: 3306
usuario: consulta
pass: Gdf.c0nsulta
Las vistas generadas actualmente son:
Informacin servidores (Informacin de HW)
SELECT * FROM serverDView
' Informacin por lpar, incluye informacin de HW, perfil de configuracin, swap, agentes de monitoreo, versin SO, comando y fecha del ltimo mksysb o sysback y medio de instalacin requerido para recuperar el sistema:
SELECT * FROM lparDView
Informacin de HBAs (fcs): Disponibilidad, ubicacin, parmetros velocidad (lg_term_dma, max_xfer_size, num_cmd_elems) (se usa para identificar best practices de red y realizar planes de configuracin correspondientes)
SELECT * FROM lparFCSView
Informacin de HBAs (fscsi): Disponibilidad, ubicacin, parmetros conexin (attach, dytrnk, fc_err_recov) (se usa para identificar best practices de red y realizar planes de configuracin correspondientes)
SELECT * FROM lparFSCSIView
Informacin de red (IP, mscara e IP de la HMC conectada) por interfaz/lpar, hace parte de una plantilla de sysreg
SELECT * FROM lparIPView
Informacin de red (velocidad) por interfaz/lpar, ubicacin y disponibilidad (se usa para identificar best practices de red y realizar planes de configuracin correspondientes)
SELECT * FROM lparNetView
Informacin subsistemas (actualmente slo estalmacenada la versin, sin embargo la tabla correspondiente a subsistemas puede almacenar # de checklist de activacin y desactivacin, y fecha de actualizacin del subsistema. Los subsistemas automatizados hasta ahora son: HACMP, sudo, ssh, nim, tsm client, donde para sysreg slo se activan ssh y sudo.
SELECT * FROM lparSubsysView
Page 145
CMDB
' Informacin por lpar, incluye informacin de HW, perfil de configuracin, swap, agentes de monitoreo, versin SO, comando y fecha del ltimo mksysb o sysback y medio de instalacin requerido para recuperar el sistema:
Informacin de HBAs (fcs): Disponibilidad, ubicacin, parmetros velocidad (lg_term_dma, max_xfer_size, num_cmd_elems) (se usa para identificar best practices de red y realizar planes de configuracin correspondientes)
Informacin de HBAs (fscsi): Disponibilidad, ubicacin, parmetros conexin (attach, dytrnk, fc_err_recov) (se usa para identificar best practices de red y realizar planes de configuracin correspondientes)
Informacin de red (IP, mscara e IP de la HMC conectada) por interfaz/lpar, hace parte de una plantilla de sysreg
Informacin de red (velocidad) por interfaz/lpar, ubicacin y disponibilidad (se usa para identificar best practices de red y realizar planes de configuracin correspondientes)
Informacin subsistemas (actualmente slo estalmacenada la versin, sin embargo la tabla correspondiente a subsistemas puede almacenar # de checklist de activacin y desactivacin, y fecha de actualizacin del subsistema. Los subsistemas automatizados hasta ahora son: HACMP, sudo, ssh, nim, tsm client, donde para sysreg slo se activan ssh y sudo.
Page 146
CMDB
' Informacin por lpar, incluye informacin de HW, perfil de configuracin, swap, agentes de monitoreo, versin SO, comando y fecha del ltimo mksysb o sysback y medio de instalacin requerido para recuperar el sistema:
Informacin de HBAs (fcs): Disponibilidad, ubicacin, parmetros velocidad (lg_term_dma, max_xfer_size, num_cmd_elems) (se usa para identificar best practices de red y realizar planes de configuracin correspondientes)
Informacin de HBAs (fscsi): Disponibilidad, ubicacin, parmetros conexin (attach, dytrnk, fc_err_recov) (se usa para identificar best practices de red y realizar planes de configuracin correspondientes)
Informacin subsistemas (actualmente slo estalmacenada la versin, sin embargo la tabla correspondiente a subsistemas puede almacenar # de checklist de activacin y desactivacin, y fecha de actualizacin del subsistema. Los subsistemas automatizados hasta ahora son: HACMP, sudo, ssh, nim, tsm client, donde para sysreg slo se activan ssh y sudo.
Page 147
CMDB
Informacin subsistemas (actualmente slo estalmacenada la versin, sin embargo la tabla correspondiente a subsistemas puede almacenar # de checklist de activacin y desactivacin, y fecha de actualizacin del subsistema. Los subsistemas automatizados hasta ahora son: HACMP, sudo, ssh, nim, tsm client, donde para sysreg slo se activan ssh y sudo.
Page 148
cores lpar
cores lpar cores caja
tsmsrvcolom/home/ibmadmhe >lparstat -i |grep Active
Active Physical CPUs in system : 8
Active CPUs in Pool : 8
tsmsrvcolom/home/ibmadmhe >lparstat -i |grep Desired
Desired Virtual CPUs : 1
Desired Memory : 4096 MB
Desired Variable Capacity Weight : 0
Desired Capacity : 1.00
Page 149
cores lpar
Un procesador virtual es una representacin de un procesador fsico que se presenta al sistema operativo. Un procesador virtual no puede tener una mayor capacidad de procesamiento de un procesador fsico. La capacidad de un procesador virtual ser igual o menor que la capacidad de procesamiento de un procesador fsico. En trminos de capacidad, un procesador fsico puede supoort hasta 10 procesadores virtuales.
Por ejemplo, si una particin lgica tiene 1,80 unidades de procesamiento y dos procesadores virtuales, cada procesador virtual tiene 0,90 unidades de procesamiento.
Por defecto, el nmero de unidades de procesamiento se redondea a un nmero entero:
- Si se especifica 0,50 unidades de procesamiento, 1 procesador virtual se le asignar.
- Si se especifica 2,25 unidades de procesamiento, 3 procesador virtual se le asignar.
Se puede cambiar la configuracin por defecto, y se debe considerar esto, porque en particiones uncaped el lmite superior de la capacidad de procesamiento en una particin de micro-se determina por el nmero de procesadores virtuales que posee.
Por ejemplo, si tiene una particin con 0,50 unidades de procesamiento y un procesador virtual, la particin no puede exceder de 1,00 unidades de procesamiento. Sin embargo, si la misma particin con 0,50 unidades de procesamiento se asigna a dos procesadores virtuales y recursos de procesamiento disponibles, la particin podra utilizar un adicional de 1,50 unidades de procesamiento.
El nmero de procesadores virtuales no se puede extender ms de 10 veces de la Capacaty derecho.
(Si la EC = 0,5 entonces el nmero mximo de Procesador Virtual no puede ser ms de 5.)
Page 150
cores lpar
cores de la caja
cores de la lpar
Page 151
cores lpar
Un procesador virtual es una representacin de un procesador fsico que se presenta al sistema operativo. Un procesador virtual no puede tener una mayor capacidad de procesamiento de un procesador fsico. La capacidad de un procesador virtual ser igual o menor que la capacidad de procesamiento de un procesador fsico. En trminos de capacidad, un procesador fsico puede supoort hasta 10 procesadores virtuales.
Por ejemplo, si una particin lgica tiene 1,80 unidades de procesamiento y dos procesadores virtuales, cada procesador virtual tiene 0,90 unidades de procesamiento.
Se puede cambiar la configuracin por defecto, y se debe considerar esto, porque en particiones uncaped el lmite superior de la capacidad de procesamiento en una particin de micro-se determina por el nmero de procesadores virtuales que posee.
Por ejemplo, si tiene una particin con 0,50 unidades de procesamiento y un procesador virtual, la particin no puede exceder de 1,00 unidades de procesamiento. Sin embargo, si la misma particin con 0,50 unidades de procesamiento se asigna a dos procesadores virtuales y recursos de procesamiento disponibles, la particin podra utilizar un adicional de 1,50 unidades de procesamiento.
El nmero de procesadores virtuales no se puede extender ms de 10 veces de la Capacaty derecho.
Page 152
cores lpar
Page 153
cores lpar
Un procesador virtual es una representacin de un procesador fsico que se presenta al sistema operativo. Un procesador virtual no puede tener una mayor capacidad de procesamiento de un procesador fsico. La capacidad de un procesador virtual ser igual o menor que la capacidad de procesamiento de un procesador fsico. En trminos de capacidad, un procesador fsico puede supoort hasta 10 procesadores virtuales.
Se puede cambiar la configuracin por defecto, y se debe considerar esto, porque en particiones uncaped el lmite superior de la capacidad de procesamiento en una particin de micro-se determina por el nmero de procesadores virtuales que posee.
Por ejemplo, si tiene una particin con 0,50 unidades de procesamiento y un procesador virtual, la particin no puede exceder de 1,00 unidades de procesamiento. Sin embargo, si la misma particin con 0,50 unidades de procesamiento se asigna a dos procesadores virtuales y recursos de procesamiento disponibles, la particin podra utilizar un adicional de 1,50 unidades de procesamiento.
Page 154
cores lpar
Page 155
cores lpar
Un procesador virtual es una representacin de un procesador fsico que se presenta al sistema operativo. Un procesador virtual no puede tener una mayor capacidad de procesamiento de un procesador fsico. La capacidad de un procesador virtual ser igual o menor que la capacidad de procesamiento de un procesador fsico. En trminos de capacidad, un procesador fsico puede supoort hasta 10 procesadores virtuales.
Por ejemplo, si tiene una particin con 0,50 unidades de procesamiento y un procesador virtual, la particin no puede exceder de 1,00 unidades de procesamiento. Sin embargo, si la misma particin con 0,50 unidades de procesamiento se asigna a dos procesadores virtuales y recursos de procesamiento disponibles, la particin podra utilizar un adicional de 1,50 unidades de procesamiento.
Page 156
cores lpar
Page 157
cores lpar
Un procesador virtual es una representacin de un procesador fsico que se presenta al sistema operativo. Un procesador virtual no puede tener una mayor capacidad de procesamiento de un procesador fsico. La capacidad de un procesador virtual ser igual o menor que la capacidad de procesamiento de un procesador fsico. En trminos de capacidad, un procesador fsico puede supoort hasta 10 procesadores virtuales.
Por ejemplo, si tiene una particin con 0,50 unidades de procesamiento y un procesador virtual, la particin no puede exceder de 1,00 unidades de procesamiento. Sin embargo, si la misma particin con 0,50 unidades de procesamiento se asigna a dos procesadores virtuales y recursos de procesamiento disponibles, la particin podra utilizar un adicional de 1,50 unidades de procesamiento.
Page 158
firmware fibra
lscfg -vl fcs0 el firmware es el Z9
firmware fibra
Page 159
TIPS Reinicio particiones AIX
Descripcion
cuando se vaya a reiniciar una maquina
validar si esta compartiendo filesystems por NFS a otros server para no bloquearlo
ver el bootlist que est el disco y no lan
Page 160
licencias IBM
Page 161
licencias IBM
Page 162
Relacion de confianza IBM
Descripcion
Crear relacin de confianza
Paso 2
Page 163
Relacion de confianza IBM
Pasos
En la maquina base se ejecuta ssh-keygen -t rsa -b 1024
Se debe tener el archivo C:\$user\INFORMACION\INFORMACION\GESTION DIARIA\Relaciones de confianza\ssh-copy-id
./ssh-copy-id IP_SERVER
Clave
Y listo
copiar el contenido de la llave id_rsa.pub de la maquina base
llevarla a la otra maquina y copiarla en autorized keys
Page 164
Relacion de confianza IBM
Se debe tener el archivo C:\$user\INFORMACION\INFORMACION\GESTION DIARIA\Relaciones de confianza\ssh-copy-id
Page 165
CASOS REPITIVOS AVIANCA
SE ACCEDE CON EL USUARIO IBMADMJL
SE DEBE TOMAR LOS USUARIOS QUE EXPIRAN LOS DEL CLIENTE
sudo chage -d 2012-02-02 SE PONE LA FECHA ACTUAL
ylopez
emartinez
rmolina
gmontoya
jpacheco
jpinzon
equintero
oromero
rsanchez
eserna
osierra
jtamayo
fusuga
azambrano
lzamora
malopez
jmorales
mecardenas
ccruz
calfonso
hjimenez
jeppfiles
gangulo
bpaez
aalfaro
sherrera
dsegura
gsandoval
Page 166
CASOS REPITIVOS AVIANCA
postfix
omar
jguevara
hlopez
hmena
agutierrez
mmarin
lfernandez
amarin
sposada
sgeney
abetancourt
mgomez
ehernandez
jmotato
ftorres
jvalle
lvasquez
lavila
rruiz
aparra
lguzman
gespinosa
jsalazar
jguerra
elondono
fmarulanda
jmesa
jsaldana
ecortes
osantander
fhenao
evanegas
hmejia
arico
smejia
cmarengo
jyandar
lmiranda
jduran
mtalero
apardo
mbeltran
jnarvaez
Page 167
CASOS REPITIVOS AVIANCA
jrestrepo
jtalero
planvuelo
xwinuser
eaguirre
jsarmiento
lcossio
gicastro
nbecerra
cgonzalez
lcastaneda
agarcia
alaverde
azapata
ibmadmnfp
vacosta
ccramston
dvalencia
sobando
lzapata
cdiez
mramirez
jgalindo
jmontoya
jmdiaz
perfmgr
nruiz
gaquino
gbotia
Page 168
CASOS REPITIVOS AVIANCA
opscntl
opscadm
hayala
wbarbosa
jcampino
hcanasteros
mcardenas
jcastiblanco
ldelgado
jdiaz
afonseca
jgomez
cjabonero
tjacanamijoy
njimenez
ylopez
emartinez
rmolina
gmontoya
jpacheco
jpinzon
equintero
oromero
rsanchez
eserna
osierra
jtamayo
fusuga
azambrano
lzamora
malopez
jmorales
mecardenas
ccruz
calfonso
hjimenez
jeppfiles
gangulo
bpaez
aalfaro
sherrera
dsegura
gsandoval
Page 169
CASOS REPITIVOS AVIANCA
postfix
omar
jguevara
hlopez
hmena
agutierrez
mmarin
lfernandez
amarin
sposada
sgeney
abetancourt
mgomez
ehernandez
jmotato
ftorres
jvalle
lvasquez
lavila
rruiz
aparra
lguzman
gespinosa
jsalazar
jguerra
elondono
fmarulanda
jmesa
jsaldana
ecortes
osantander
fhenao
evanegas
hmejia
arico
smejia
cmarengo
jyandar
lmiranda
jduran
mtalero
apardo
mbeltran
jnarvaez
Page 170
CASOS REPITIVOS AVIANCA
jrestrepo
jtalero
planvuelo
xwinuser
eaguirre
jsarmiento
lcossio
gicastro
nbecerra
cgonzalez
lcastaneda
agarcia
alaverde
azapata
ibmadmnfp
vacosta
ccramston
dvalencia
sobando
lzapata
cdiez
mramirez
jgalindo
jmontoya
jmdiaz
perfmgr
nruiz
gaquino
gbotia
Page 171
Crear SEA
http://www-
01.ibm.com/
support/doc
view.wss?ui
d=isg3T101
1040
Page 172
subir ip y gateway automatico
Switch ID: ETHERNET0
Hypervisor Information
Virtual Memory
Total (KB) 79
I/O Memory
VRM Minimum (KB) 100
VRM Desired (KB) 100
DMA Max Min (KB) 128
Transmit Information
Transmit Buffers
Buffer Size 65536
Buffers 32
History
No Buffers 0
Virtual Memory
Total (KB) 2048
I/O Memory
VRM Minimum (KB) 2176
VRM Desired (KB) 16384
DMA Max Min (KB) 16384
Receive Information
Receive Buffers
Buffer Type Tiny Small Medium Large Huge
Min Buffers 512 512 128 24 24
Max Buffers 2048 2048 256 64 64
Allocated 512 512 128 24 24
Registered 512 512 128 24 24
History
Max Allocated 512 512 128 24 24
Lowest Registered 512 512 128 24 24
Virtual Memory
Minimum (KB) 256 1024 2048 768 1536
Maximum (KB) 1024 4096 4096 2048 4096
I/O Memory
VRM Minimum (KB) 4096 4096 2560 864 1632
VRM Desired (KB) 16384 16384 5120 2304 4352
DMA Max Min (KB) 16384 16384 8192 4096 8192
I/O Memory Information
Total VRM Minimum (KB) 15524
Total VRM Desired (KB) 61028
Total DMA Max Min (KB) 69760
ncsmg011/home/ibmadmhe#lsconf |grep Serial
Page 173
subir ip y gateway automatico
ncsmg011/home/ibmadmhe#entstat ent3 |grep VLAN
ncsmg011/home/ibmadmhe#lsdev -c adapter
ent0 Defined Virtual I/O Ethernet Adapter (l-lan)
ent1 Defined Virtual I/O Ethernet Adapter (l-lan)
ent2 Available Virtual I/O Ethernet Adapter (l-lan)
ent3 Available Virtual I/O Ethernet Adapter (l-lan)
fcs0 Available 31-T1 Virtual Fibre Channel Client Adapter
fcs1 Available 32-T1 Virtual Fibre Channel Client Adapter
fcs2 Available 41-T1 Virtual Fibre Channel Client Adapter
vsa0 Available LPAR Virtual Serial Adapter
vscsi0 Defined Virtual SCSI Client Adapter
vscsi1 Defined Virtual SCSI Client Adapter
vscsi2 Defined Virtual SCSI Client Adapter
vscsi3 Defined Virtual SCSI Client Adapter
vscsi4 Available Virtual SCSI Client Adapter
vscsi5 Available Virtual SCSI Client Adapter
ncsmg011/home/ibmadmhe#sudo su -
Password:
[compat]: 3004-300 You entered an invalid login name or password.
Sorry, try again.
Password:
ncsmg011/#
ncsmg011/#
ncsmg011/#clear
ncsmg011/#ifconfig en2 up
ncsmg011/#ifconfig en3 up
ncsmg011/#ifconfig -a
en2: flags=1e080863,480<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACTIVE),CHAIN>
tcp_sendspace 262144 tcp_recvspace 262144 rfc1323 1
en3: flags=1e080863,480<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACTIVE),CHAIN>
tcp_sendspace 262144 tcp_recvspace 262144 rfc1323 1
lo0: flags=e08084b,c0<UP,BROADCAST,LOOPBACK,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,LARGESEND,CHAIN>
inet 127.0.0.1 netmask 0xff000000 broadcast 127.255.255.255
inet6 ::1%1/0
tcp_sendspace 131072 tcp_recvspace 131072 rfc1323 1
ncsmg011/#tcpdump -vvv -i en2
tcpdump: listening on en2, link-type 1, capture size 96 bytes
18:30:08.529274 ec:44:76:e4:f9:13 (oui Unknown) > 01:00:0c:cc:cc:cd (oui Unknown) SNAP Unnumbered, ui, Flags [Command], length 50
18:30:08.679881 IP (tos 0xc0, ttl 255, id 5, offset 0, flags [none], proto: VRRP (112), length: 40) 10.24.1.254 > 224.0.0.18: VRRPv2, Advertisement, vrid 3, prio 100, authtype none, intvl 1s, length 20, addrs: 10.24.1.1
18:30:08.712986 IP (tos 0xc0, ttl 255, id 8, offset 0, flags [none], proto: VRRP (112), length: 40) 10.24.1.254 > 224.0.0.18: VRRPv2, Advertisement, vrid 6, prio 100, authtype none, intvl 1s, length 20, addrs: 10.24.1.2
18:30:08.871834 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.24.1.142 tell 10.24.1.253, length 46
18:30:09.477932 IP (tos 0xc0, ttl 255, id 8, offset 0, flags [none], proto: VRRP (112), length: 40) 10.24.1.254 > 224.0.0.18: VRRPv2, Advertisement, vrid 6, prio 100, authtype none, intvl 1s, length 20, addrs: 10.24.1.2
18:30:09.501723 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has ncerp053 tell 10.24.1.58, length 46
18:30:09.644890 IP (tos 0xc0, ttl 255, id 5, offset 0, flags [none], proto: VRRP (112), length: 40) 10.24.1.254 > 224.0.0.18: VRRPv2, Advertisement, vrid 3, prio 100, authtype none, intvl 1s, length 20, addrs: 10.24.1.1
18:30:09.767513 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has ncerp053 tell ncerp033, length 46
Page 174
subir ip y gateway automatico
18:30:10.077650 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has ncerp053 tell ncerp043, length 46
18:30:10.151241 IP (tos 0x0, ttl 30, id 8296, offset 0, flags [none], proto: UDP (17), length: 104) 10.24.1.137.58270 > 10.24.1.255.14000: UDP, length 76
^C
10 packets received by filter
0 packets dropped by kernel
ncsmg011/#dev
ksh: dev: not found.
ncsmg011/#dev
ksh: dev: not found.
ncsmg011/#lsdev |grep ent
ent0 Defined Virtual I/O Ethernet Adapter (l-lan)
ent1 Defined Virtual I/O Ethernet Adapter (l-lan)
ent2 Available Virtual I/O Ethernet Adapter (l-lan)
ent3 Available Virtual I/O Ethernet Adapter (l-lan)
fcs0 Available 31-T1 Virtual Fibre Channel Client Adapter
fcs1 Available 32-T1 Virtual Fibre Channel Client Adapter
fcs2 Available 41-T1 Virtual Fibre Channel Client Adapter
vscsi0 Defined Virtual SCSI Client Adapter
vscsi1 Defined Virtual SCSI Client Adapter
vscsi2 Defined Virtual SCSI Client Adapter
vscsi3 Defined Virtual SCSI Client Adapter
vscsi4 Available Virtual SCSI Client Adapter
vscsi5 Available Virtual SCSI Client Adapter
ncsmg011/#lsattr -El en0
alias4 IPv4 Alias including Subnet Mask True
alias6 IPv6 Alias including Prefix Length True
arp on Address Resolution Protocol (ARP) True
authority Authorized Users True
broadcast Broadcast Address True
monitor off Enable/Disable monitor attribute True
mtu 1500 Maximum IP Packet Size for This Device True
mtu_bypass off Enable/Disable largesend for virtual Ethernet True
netaddr 11.0.2.158 Internet Address True
netaddr6 IPv6 Internet Address True
netmask 255.255.255.0 Subnet Mask True
prefixlen Prefix Length for IPv6 Internet Address True
remmtu 576 Maximum IP Packet Size for REMOTE Networks True
rfc1323 Enable/Disable TCP RFC 1323 Window Scaling True
security none Security Level True
state up Current Interface Status True
tcp_mssdflt Set TCP Maximum Segment Size True
tcp_nodelay Enable/Disable TCP_NODELAY Option True
tcp_recvspace Set Socket Buffer Space for Receiving True
tcp_sendspace Set Socket Buffer Space for Sending True
thread off Enable/Disable thread attribute True
ncsmg011/#lsattr -El en1
Page 175
subir ip y gateway automatico
alias4 IPv4 Alias including Subnet Mask True
alias6 IPv6 Alias including Prefix Length True
arp on Address Resolution Protocol (ARP) True
authority Authorized Users True
broadcast Broadcast Address True
monitor off Enable/Disable monitor attribute True
mtu 1500 Maximum IP Packet Size for This Device True
mtu_bypass off Enable/Disable largesend for virtual Ethernet True
netaddr 10.24.1.73 Internet Address True
netaddr6 IPv6 Internet Address True
netmask 255.255.255.0 Subnet Mask True
prefixlen Prefix Length for IPv6 Internet Address True
remmtu 576 Maximum IP Packet Size for REMOTE Networks True
rfc1323 Enable/Disable TCP RFC 1323 Window Scaling True
security none Security Level True
state up Current Interface Status True
tcp_mssdflt Set TCP Maximum Segment Size True
tcp_nodelay Enable/Disable TCP_NODELAY Option True
tcp_recvspace Set Socket Buffer Space for Receiving True
tcp_sendspace Set Socket Buffer Space for Sending True
thread off Enable/Disable thread attribute True
ncsmg011/#sudo
ncsmg011/# -a netmask=255.255.255.0 -a state=up <
en2 changed
ncsmg011/#chdev -l en2 -a netaddr=10.24.1.73 -a netmask=255.255.255.0 -a stat>
ncsmg011/#lsattr -El en0
alias4 IPv4 Alias including Subnet Mask True
alias6 IPv6 Alias including Prefix Length True
arp on Address Resolution Protocol (ARP) True
authority Authorized Users True
broadcast Broadcast Address True
monitor off Enable/Disable monitor attribute True
mtu 1500 Maximum IP Packet Size for This Device True
mtu_bypass off Enable/Disable largesend for virtual Ethernet True
netaddr 11.0.2.158 Internet Address True
netaddr6 IPv6 Internet Address True
netmask 255.255.255.0 Subnet Mask True
prefixlen Prefix Length for IPv6 Internet Address True
remmtu 576 Maximum IP Packet Size for REMOTE Networks True
rfc1323 Enable/Disable TCP RFC 1323 Window Scaling True
security none Security Level True
state up Current Interface Status True
tcp_mssdflt Set TCP Maximum Segment Size True
tcp_nodelay Enable/Disable TCP_NODELAY Option True
tcp_recvspace Set Socket Buffer Space for Receiving True
tcp_sendspace Set Socket Buffer Space for Sending True
Page 176
subir ip y gateway automatico
thread off Enable/Disable thread attribute True
ncsmg011/# -a netmask=255.255.255.0 -a state=up <
en3 changed
ncsmg011/#ifconfig -a
en2: flags=1e080863,480<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACTIVE),CHAIN>
inet 10.24.1.73 netmask 0xffffff00 broadcast 10.24.1.255
tcp_sendspace 262144 tcp_recvspace 262144 rfc1323 1
en3: flags=1e080863,480<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACTIVE),CHAIN>
inet 11.0.2.158 netmask 0xffffff00 broadcast 11.0.2.255
tcp_sendspace 262144 tcp_recvspace 262144 rfc1323 1
lo0: flags=e08084b,c0<UP,BROADCAST,LOOPBACK,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,LARGESEND,CHAIN>
inet 127.0.0.1 netmask 0xff000000 broadcast 127.255.255.255
inet6 ::1%1/0
tcp_sendspace 131072 tcp_recvspace 131072 rfc1323 1
ncsmg011/#mkdev -l inet0
inet0 Available
ncsmg011/#
mkdev -l inet0
Page 177
subir ip y gateway automatico
Page 178
subir ip y gateway automatico
en2: flags=1e080863,480<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACTIVE),CHAIN>
en3: flags=1e080863,480<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACTIVE),CHAIN>
lo0: flags=e08084b,c0<UP,BROADCAST,LOOPBACK,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,LARGESEND,CHAIN>
18:30:08.529274 ec:44:76:e4:f9:13 (oui Unknown) > 01:00:0c:cc:cc:cd (oui Unknown) SNAP Unnumbered, ui, Flags [Command], length 50
18:30:08.679881 IP (tos 0xc0, ttl 255, id 5, offset 0, flags [none], proto: VRRP (112), length: 40) 10.24.1.254 > 224.0.0.18: VRRPv2, Advertisement, vrid 3, prio 100, authtype none, intvl 1s, length 20, addrs: 10.24.1.1
18:30:08.712986 IP (tos 0xc0, ttl 255, id 8, offset 0, flags [none], proto: VRRP (112), length: 40) 10.24.1.254 > 224.0.0.18: VRRPv2, Advertisement, vrid 6, prio 100, authtype none, intvl 1s, length 20, addrs: 10.24.1.2
18:30:08.871834 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.24.1.142 tell 10.24.1.253, length 46
18:30:09.477932 IP (tos 0xc0, ttl 255, id 8, offset 0, flags [none], proto: VRRP (112), length: 40) 10.24.1.254 > 224.0.0.18: VRRPv2, Advertisement, vrid 6, prio 100, authtype none, intvl 1s, length 20, addrs: 10.24.1.2
18:30:09.501723 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has ncerp053 tell 10.24.1.58, length 46
18:30:09.644890 IP (tos 0xc0, ttl 255, id 5, offset 0, flags [none], proto: VRRP (112), length: 40) 10.24.1.254 > 224.0.0.18: VRRPv2, Advertisement, vrid 3, prio 100, authtype none, intvl 1s, length 20, addrs: 10.24.1.1
18:30:09.767513 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has ncerp053 tell ncerp033, length 46
Page 179
subir ip y gateway automatico
18:30:10.077650 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has ncerp053 tell ncerp043, length 46
18:30:10.151241 IP (tos 0x0, ttl 30, id 8296, offset 0, flags [none], proto: UDP (17), length: 104) 10.24.1.137.58270 > 10.24.1.255.14000: UDP, length 76
Page 180
subir ip y gateway automatico
Page 181
subir ip y gateway automatico
en2: flags=1e080863,480<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACTIVE),CHAIN>
en3: flags=1e080863,480<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACTIVE),CHAIN>
lo0: flags=e08084b,c0<UP,BROADCAST,LOOPBACK,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,LARGESEND,CHAIN>
Page 182
subir ip y gateway automatico
Page 183
subir ip y gateway automatico
18:30:08.679881 IP (tos 0xc0, ttl 255, id 5, offset 0, flags [none], proto: VRRP (112), length: 40) 10.24.1.254 > 224.0.0.18: VRRPv2, Advertisement, vrid 3, prio 100, authtype none, intvl 1s, length 20, addrs: 10.24.1.1
18:30:08.712986 IP (tos 0xc0, ttl 255, id 8, offset 0, flags [none], proto: VRRP (112), length: 40) 10.24.1.254 > 224.0.0.18: VRRPv2, Advertisement, vrid 6, prio 100, authtype none, intvl 1s, length 20, addrs: 10.24.1.2
18:30:09.477932 IP (tos 0xc0, ttl 255, id 8, offset 0, flags [none], proto: VRRP (112), length: 40) 10.24.1.254 > 224.0.0.18: VRRPv2, Advertisement, vrid 6, prio 100, authtype none, intvl 1s, length 20, addrs: 10.24.1.2
18:30:09.644890 IP (tos 0xc0, ttl 255, id 5, offset 0, flags [none], proto: VRRP (112), length: 40) 10.24.1.254 > 224.0.0.18: VRRPv2, Advertisement, vrid 3, prio 100, authtype none, intvl 1s, length 20, addrs: 10.24.1.1
Page 184
Cluster solaris
Descripcion Comando
Ver el estado del cluster /usr/cluster/bin/clrg status
Ponerlos Online
sudo /usr/cluster/bin/clrg
online mqm-rg
Page 185
Samba
Samba Bajar servicio samba sudo smbcontrol nmbd shutdown
Subir servicio samba sudo smbd -D sudo nmbd -D
Cuando de instale una version nueva Ejecutar testparm Este comando prueba el archivo de configuracion
Page 186
Samba
sudo smbcontrol smbd shutdown
Este comando prueba el archivo de configuracion
Page 187
Configurar sea
ingresar una vlan a una sea Desde el vio por dlpar
Desde el vio sshj buscas la sea
Page 188
Configurar sea
ncsmg011/#tcpdump -vvv -i en2
Page 189
Configurar sea
buscas la sea mkvdev -vlan entX -
mkvdev -vlan ent31 -tagid 165
Page 190
sap mejores practicas
Crear dos VG uno para DB y otro para sap
Crear un vg con estas opciones mkvg -S -s 128M -y sapvg hdisk2 hdisk3 hdisk4 hdisk5 hdisk6
Crear un lV con estas opciones sudo mklv -y sapmnt_lv -e x -t jfs2 sapvg 10G; sudo crfs -v jfs2 -d sapmnt_lv -m /sapmnt -A yes -p rw; sudo mount /sapmnt
./cl_crfs -cspoc " -g SDB_RG " -v jfs2 -d db2inslv -m /DB2INSCLQ -A no -p rw
Page 191
sap mejores practicas
mkvg -S -s 128M -y sapvg hdisk2 hdisk3 hdisk4 hdisk5 hdisk6
sudo mklv -y sapmnt_lv -e x -t jfs2 sapvg 10G; sudo crfs -v jfs2 -d sapmnt_lv -m /sapmnt -A yes -p rw; sudo mount /sapmnt
./cl_crfs -cspoc " -g SDB_RG " -v jfs2 -d db2inslv -m /DB2INSCLQ -A no -p rw
Page 192
Syslog-ftp
Se agrega -ld al final de la linea en el /etc/inetd.conf
Se crea el archivo /var/log/ftp.log
Ahora se agrega lo siguiente en el archivo /etc/syslog.conf
Se reinician los dos demonios
Page 193
Syslog-ftp
ftp stream tcp6 nowait root /usr/sbin/ftpd ftpd -ld -d Sends debugging messages to the syslogd daemon.
Refresh -s inetd; refresh -s syslogd
daemon.debug /var/log/ftp.log
Page 194
Syslog-ftp
Sends debugging messages to the syslogd daemon.
Page 195
Ver cuanto consume un proceso e
Ver cuanto consume un proceso en memoria
C:\$user\ver consumo de procesos en memoria
Page 196
WWN EN UNA AIX
1. Se revisa en la lpar si se tienen hbas.
agbispbd/home/ibmadmcv >lsdev -c adapter |grep fc
fcs0 Available 05-08 FC Adapter
fcs1 Available 07-08 FC Adapter
fcs2 Available 07-09 FC Adapter
2. Se revisa si a estas fibras se presenta discos o tapes.
agbispbd/home/ibmadmcv >lsdev |grep 05-08
fcnet0 Defined 05-08-01 Fibre Channel Network Protocol Device
fcs0 Available 05-08 FC Adapter
fscsi0 Available 05-08-02 FC SCSI I/O Controller Protocol Device
agbispbd/home/ibmadmcv >lsdev |grep 07-08
dac0 Available 07-08-02 DS3/4/5K PCM User Interface
dac1 Available 07-08-02 DS3/4/5K PCM User Interface
fcnet1 Defined 07-08-01 Fibre Channel Network Protocol Device
fcs1 Available 07-08 FC Adapter
fscsi1 Available 07-08-02 FC SCSI I/O Controller Protocol Device
hdisk0 Available 07-08-02 MPIO Other DS4K Array Disk
hdisk1 Available 07-08-02 MPIO DS5100/5300 Disk
hdisk4 Available 07-08-02 MPIO DS5100/5300 Disk
hdisk5 Available 07-08-02 MPIO DS5100/5300 Disk
hdisk6 Available 07-08-02 MPIO DS5100/5300 Disk
hdisk7 Available 07-08-02 MPIO DS5100/5300 Disk
hdisk8 Available 07-08-02 MPIO DS5100/5300 Disk
hdisk9 Available 07-08-02 MPIO DS5100/5300 Disk
hdisk10 Available 07-08-02 MPIO DS5100/5300 Disk
hdisk11 Available 07-08-02 MPIO DS5100/5300 Disk
hdisk12 Available 07-08-02 MPIO DS5100/5300 Disk
hdisk13 Available 07-08-02 MPIO DS5100/5300 Disk
hdisk14 Available 07-08-02 MPIO DS5100/5300 Disk
hdisk15 Available 07-08-02 MPIO DS5100/5300 Disk
agbispbd/home/ibmadmcv >lsdev |grep 07-09
fcnet2 Defined 07-09-01 Fibre Channel Network Protocol Device
fcs2 Available 07-09 FC Adapter
fscsi2 Available 07-09-02 FC SCSI I/O Controller Protocol Device
rmt0 Defined 07-09-02 Other FC SCSI Tape Drive
rmt1 Defined 07-09-02 Other FC SCSI Tape Drive
En este caso:
La fibra fcs0 se encuentra conectada pero sin usar.
La fibra fcs1 presenta discos
La fibra fcs2 presenta tapes.
3. para validar las wwn de las fibras se ejecuta el comando
Page 197
WWN EN UNA AIX
agbispbd/home/ibmadmcv >lscfg -vpl fcs2 |grep Net
Network Address.............10000000C96977CD
agbispbd/home/ibmadmcv >lscfg -vpl fcs0 |grep Net
Network Address.............10000000C966C315
agbispbd/home/ibmadmcv >lscfg -vpl fcs1 |grep Net
Network Address.............10000000C96977CC
4. Cuando se ejecute el comando lspath
y aparezca Enabled hdisk0 fscsi0 significa que las hbas estan conectadas a la lpar
Se debe identifar que partition number tiene la lpar.
agbispbd/home/ibmadmcv >lparstat -i |grep "Partition Number"
Partition Number : 1
5. Ahora nos dirijimos en la vioserver y ejecutamos lo siguiente:
lsmap -all |grep 0000001
vhost1 U8233.E8B.068849P-V2-C6 0x00000001
Con ello sabemos a que vhost pertenece.
lsmap -v adapter vhost1
--------------- -------------------------------------------- ------------------
vhost1 U8233.E8B.068849P-V2-C6 0x00000001
VTD vSOagerppbd
Status Available
LUN 0x8100000000000000
Backing device hdisk20
Physloc U5802.001.008D216-P1-C6-T2-W203200A0B847A17E-L0
Mirrored false
VTD vagerhdisk21
Status Available
LUN 0x8300000000000000
Backing device hdisk21
Physloc U5802.001.008D216-P1-C6-T2-W203200A0B847A17E-L1000000000000
Mirrored false
VTD vagerhdisk22
Status Available
LUN 0x8400000000000000
Backing device hdisk22
Page 198
WWN EN UNA AIX
Physloc U5802.001.008D216-P1-C6-T2-W203200A0B847A17E-L2000000000000
Mirrored false
lspath |grep hdisk20
en este comando aparece fcsci0 fcsci1
lsdev -dev fcs0 -vpd |grep Net >> si aparece fcsci0
lsdev -dev fcs1 -vpd |grep Net >> si aparece fcsci1
Con ello se validan cuantas hbas tiene esta lpar aparte de las fisicas anteriormente mencionadas y la WWPN WWN.
Page 199
WWN EN UNA AIX
Page 200
WWN EN UNA AIX
si aparece vscsi0 significa que un vioserver esta mapeando un disco a la lpar y con ello se requiere validar las hbas que van al vio y a su vez a la lpar.
Page 201
WWN EN UNA AIX
Con ello se validan cuantas hbas tiene esta lpar aparte de las fisicas anteriormente mencionadas y la WWPN WWN.
Page 202
WWN EN UNA AIX
Page 203
WWN EN UNA AIX
si aparece vscsi0 significa que un vioserver esta mapeando un disco a la lpar y con ello se requiere validar las hbas que van al vio y a su vez a la lpar.
Page 204
mirrorvg_rootvg
sudo extendvg hdiskX
sudo mirrorvg rootvg
sudo rm -rf /dev/ipldevice
sudo ln /dev/rhdiskX /dev/ipldevice
sudo chpv -c hdisk anterior rootvg hay que limpiar el disco que estaba antes en el rootvg
sudo bosboot -ad /dev/hdiskX
sudo bootlist -m normal hdisk8
sudo rmlv dumplv
sudo unmirrorvg rootvg hdiskviejo
sudo chpv -c hdiskviejo
sudo reducevg rootvg hdiskviejo
mklv -y lg_dumplv -t sysdump rootvg 16
Page 205
BUCLE COMANDOS
while true^Jdo^Jdate^Jlssrc -ls clstrmgrES|grep state^Jecho ------------------^Jsleep 5^Jdone
Page 206
BUCLE COMANDOS
while true^Jdo^Jdate^Jlssrc -ls clstrmgrES|grep state^Jecho ------------------^Jsleep 5^Jdone
Page 207
Asignar un disco ASM
Asignar un disco en ASM
ls -lrt *hdiskX Ver el disco que asign si es un cluster no importa el hdisk si no el major y minor
sudo mknod /dev/asm_disk17 c 13 22 Seguir el consecutivo
sudo chown grid:asmadmin /dev/asm_disk17 permisos
sudo chmod 660 /dev/asm_disk17 permisos
http://oracle-edge.blogspot.com/2012/05/how-to-create-asm-disks-on-aix.html
Limpiar disco ASM sudo dd if=/dev/zero of=/dev/asm_disk16 bs=8192 count=25000
Page 208
Asignar un disco ASM
si es un cluster no importa el hdisk si no el major y minor
Page 209
DISK_OPERATION_ERROR reserva
DCB47997 0920184313 T H hdisk1 DISK OPERATION ERROR
DCB47997 0920184313 T H hdisk1 DISK OPERATION ERROR
DCB47997 0920184313 T H hdisk1 DISK OPERATION ERROR
DCB47997 0920184313 T H hdisk7 DISK OPERATION ERROR
DCB47997 0920184313 T H hdisk7 DISK OPERATION ERROR
DCB47997 0920184313 T H hdisk8 DISK OPERATION ERROR
DCB47997 0920184313 T H hdisk10 DISK OPERATION ERROR

https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000014164715
https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000014956737
We found something wrong with the reservation as this is standalone server.
issue command "relbootrsv vg_name";shutdown -Fr ; pcmquerypr -Vh /dev/hdisk2
Then, this problem fixed.
lsvg
relbootrsv vg_name
Page 210
DISK_OPERATION_ERROR reserva
https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000014164715
https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000014956737
Page 211
Best practices HACMP
Page 212
Best practices HACMP
Page 213
Best practices HACMP
Page 214
Best practices HACMP
Page 215
Best practices HACMP
Page 216
Best practices HACMP
Page 217
Instalacion de LPAR TIPS
Cuando se realice el cruce de vio y lpar
Se debe realizar el mapeo de las hba fisicas con las virtuales del vio
Lsmap -vpl npiv
Se revisa con otro server de la misma caja por que path esta saliendo
Se va al vio despues de encontrar esto y se ejecuta
Vemos que todavia no se ha logueado
Para que se loguee le damos
Y eso lo hacemos en cada VIO
Page 218
Instalacion de LPAR TIPS
Lsmap -vpl npiv
Vfcmap -vadapter vfchost4 fcp fsc0
Vfcmap -vadapter vfchost5 fcp fsc1
Page 219
AGENTES SCM
mdebddd06/administrador/SCm >ls -lrt
total 313248
-rw-r--r-- 1 ibmadmhe staff 18033164 Jan 19 2007 scmclient_install.jar
-rwxr-xr-x 1 ibmadmhe staff 18139808 Jan 19 2007 scmclient_aix
-rwxr-xr-x 1 ibmadmhe staff 573421 Jan 19 2007 scmclient_hp11
-rwxr-xr-x 1 ibmadmhe staff 21176518 Jan 19 2007 scmclient_linux
-rwxr-xr-x 1 ibmadmhe staff 18127325 Jan 19 2007 scmclient_solaris
-rwxr-xr-x 1 ibmadmhe staff 37069197 Jan 19 2007 scmclient_linuxppc
-rwxr-xr-x 1 ibmadmhe staff 36665739 Jan 19 2007 scmclient_linux390
-rw-r--r-- 1 ibmadmhe staff 10581707 Jan 19 2007 SCMINST.JAR
mdebddd06/administrador/SCm >uname -a
AIX mdebddd06 1 6 0003182A4C00
mdebddd06/administrador/SCm >./scmclient_aix -console
InstallShield Wizard
Initializing InstallShield Wizard...
Preparing Java(tm) Virtual Machine...
...................................
...................................
...................................
...................................
...................................
...................................
...................................
...................................
...................................
...................................
...................................
...................................
...................................
...................................
...................................
...................................
....................
Select a language to be used for this wizard.
[X] 1 - English
[ ] 2 - French
[ ] 3 - German
[ ] 4 - Italian
[ ] 5 - Japanese
[ ] 6 - Korean
[ ] 7 - Portuguese (Brazil)
[ ] 8 - Simplified Chinese
[ ] 9 - Spanish
Page 220
AGENTES SCM
[ ] 10 - Traditional Chinese
To select an item enter its number, or 0 when you are finished: [0] 1
Enter 0 to continue or 1 to make another selection: [0]
--> ' --> IBM Security Compliance Manager Client Installation
IBM Tivoli Security Compliance Manager
Version 5.1.1.
Client Installation Utility
You are about to install a Client component of IBM Tivoli Security Compliance
Manager, Version 5.1.1.
Required Information
Descriptions of the components and the information you will need to supply
during their installation are listed below. For more information, please see
the IBM Tivoli Security Compliance Manager Installation Guide.
IBM Tivoli Security Compliance Manager Client
To successfully install the client, you must provide the following information:
Press ENTER to read the text [Type q to quit]

- The port number over which the client/server communication will be performed.
- The communication method: push or pull.
Push Mode - The connection originates from the client.
Pull Mode - The connection originates from the server.
If you select push mode, you will be required to supply the hostname and server
port for communication.

- Indicate if the client uses DHCP, and enter a DHCP client alias if desired
Page 221
AGENTES SCM
- For HP-UX installations, provide the location of the Java runtime
environment.

Press 1 for Next, 3 to Cancel or 4 to Redisplay [1] 1
International Program License Agreement

Part 1 - General Terms

BY DOWNLOADING, INSTALLING, COPYING, ACCESSING, OR USING THE PROGRAM
YOU AGREE TO THE TERMS OF THIS AGREEMENT. IF YOU ARE ACCEPTING THESE
TERMS ON BEHALF OF ANOTHER PERSON OR A COMPANY OR OTHER LEGAL
ENTITY, YOU REPRESENT AND WARRANT THAT YOU HAVE FULL AUTHORITY TO
BIND THAT PERSON, COMPANY, OR LEGAL ENTITY TO THESE TERMS. IF YOU DO
NOT AGREE TO THESE TERMS,



- DO NOT DOWNLOAD, INSTALL, COPY, ACCESS, OR USE THE PROGRAM; AND



- PROMPTLY RETURN THE PROGRAM AND PROOF OF ENTITLEMENT TO THE PARTY
Press Enter to continue viewing the license agreement, or, Enter "1" to accept
the agreement, "2" to decline it or "99" to go back to the previous screen, "3"
Print.
1
Press 1 for Next, 2 for Previous, 3 to Cancel or 4 to Redisplay [1] 1
IBM Tivoli Security Compliance Manager Client Install Location
Please specify a directory or press Enter to accept the default directory.
Directory Name: [/opt/IBM/SCM]
Press 1 for Next, 2 for Previous, 3 to Cancel or 4 to Redisplay [1] 1
Choose the setup type that best suits your needs.
[X] 1 - IBM Tivoli Security Compliance Manager Client
The IBM Tivoli Security Compliance Manager Client runs collectors that
are used by the IBM Tivoli Security Compliance Manager Server to monitor
Page 222
AGENTES SCM
compliance with security policies.
To select an item enter its number, or 0 when you are finished: [0]
Press 1 for Next, 2 for Previous, 3 to Cancel or 4 to Redisplay [1] 1
Client Communication Mode Configuration
Connection ports must be integer values between 26 and 65535.
Client connection port [1950]
Client communication mode:
[X] 1 - Push (Communication can be initiated by either the client or the server)
[ ] 2 - Pull (Communication is initiated only by the server)
To select an item enter its number, or 0 when you are finished: [0] 1
Enter 0 to continue or 1 to make another selection: [0]
Press 1 for Next, 2 for Previous, 3 to Cancel or 4 to Redisplay [1] 1
Server Communication Configuration
Server host name [] 10.201.138.42
Server connection port [1951]
[ ] 1 - Select the checkbox if this client uses DHCP.
To select an item enter its number, or 0 when you are finished: [0]
Press 1 for Next, 2 for Previous, 3 to Cancel or 4 to Redisplay [1] 1
IBM Tivoli Security Compliance Manager Client will be installed in the
following location:
/opt/IBM/SCM
with the following features:
Page 223
AGENTES SCM
IBM Tivoli Security Compliance Manager Client 5.1.1.1
for a total size:
47.5 MB
Press 1 for Next, 2 for Previous, 3 to Cancel or 4 to Redisplay [1] 1
Installing IBM Tivoli Security Compliance Manager Client. Please wait...
0 % complete
10 % complete
20 % complete
30 % complete
40 % complete
50 % complete
60 % complete
70 % complete
80 % complete
90 % complete
100 % complete
Creating uninstaller...
The InstallShield Wizard has successfully installed IBM Tivoli Security
Compliance Manager Client. Choose Finish to exit the wizard.
Press 3 to Finish or 4 to Redisplay [3] 3
You have mail in /usr/spool/mail/root
mdebddd06/administrador/SCm >
mdebddd06/administrador/SCm >
mdebddd06/administrador/SCm >
mdebddd06/administrador/SCm >
mdebddd06/administrador/SCm >
mdebddd06/administrador/SCm >
mdebddd06/administrador/SCm >ifconfig -a
en3: flags=1e080863,c0<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACTIVE),LARGESEND,CHAIN>
inet 10.203.10.87 netmask 0xfffffe00 broadcast 10.203.11.255
tcp_sendspace 131072 tcp_recvspace 65536 rfc1323 0
lo0: flags=e08084b,c0<UP,BROADCAST,LOOPBACK,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,LARGESEND,CHAIN>
inet 127.0.0.1 netmask 0xff000000 broadcast 127.255.255.255
inet6 ::1%1/0
tcp_sendspace 131072 tcp_recvspace 131072 rfc1323 1
mdebddd06/administrador/SCm >
Page 224
AGENTES SCM
mdebddd06/administrador/SCm >
mdebddd06/administrador/SCm >
mdebddd06/administrador/SCm >
mdebddd06/administrador/SCm >
mdebddd06/administrador/SCm >exit
$
$
$ exit
Connection to MDEBDDD06 closed.
ibmadmhe@arqsrmp01:/home/ibmuser/SCM> ssh Srmdeesbl09
Password:
ibmadmhe@arqsrmp01:/home/ibmuser/SCM>
ibmadmhe@arqsrmp01:/home/ibmuser/SCM>
ibmadmhe@arqsrmp01:/home/ibmuser/SCM> ssh ima
ibmadmhe@arqsrmp01:/home/ibmuser/SCM> ssh ibmuser@Srmdeesbl09
Password:
ibmadmhe@arqsrmp01:/home/ibmuser/SCM> ssh root@Srmdeesbl09
Password:
Last login: Fri Jan 25 15:06:40 2013 from arqsrmp01.suramericana.com.co
*******************************************************************************
* *
* *
* *
* El acceso no autorizado a este equipo esta PROHIBIDO !!! *
* Sanciones disciplinarias y legales seran aplicadas. *
* *
* *
* *
*******************************************************************************
Srmdeesbl09:~ #
Srmdeesbl09:~ #
Srmdeesbl09:~ #
Srmdeesbl09:~ #
Srmdeesbl09:~ # df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/system-lvroot
35G 34G 1.7G 96% /
tmpfs 3.8G 12K 3.8G 1% /dev/shm
/dev/sda1 244M 11M 220M 5% /boot
tmpfs 1.0M 4.0K 1020K 1% /FSRAM
Srmdeesbl09:~ #
Srmdeesbl09:~ #
Srmdeesbl09:~ # w
15:44:50 up 262 days, 23:09, 2 users, load average: 0.82, 4.05, 2.68
Page 225
AGENTES SCM
USER TTY LOGIN@ IDLE JCPU PCPU WHAT
ibmuser pts/0 14:40 33:13 0.14s 0.01s sshd: ibmuser [priv]
root pts/1 15:44 0.00s 0.02s 0.00s w
Srmdeesbl09:~ #
Srmdeesbl09:~ #
Srmdeesbl09:~ #
Srmdeesbl09:~ # exit
logout
Connection to Srmdeesbl09 closed.
ibmadmhe@arqsrmp01:/home/ibmuser/SCM>
ibmadmhe@arqsrmp01:/home/ibmuser/SCM>
ibmadmhe@arqsrmp01:/home/ibmuser/SCM>
ibmadmhe@arqsrmp01:/home/ibmuser/SCM> ls
C95ZTML.tar
ibmadmhe@arqsrmp01:/home/ibmuser/SCM>
ibmadmhe@arqsrmp01:/home/ibmuser/SCM>
ibmadmhe@arqsrmp01:/home/ibmuser/SCM>
ibmadmhe@arqsrmp01:/home/ibmuser/SCM> ssh ibmadmhe@MDEBDDD06
ibmadmhe@mdebddd06's password:
Last unsuccessful login: Fri Jan 25 11:03:44 COT 2013 on ssh from arqsrmp01.suramericana.com.co
Last login: Fri Jan 25 15:29:57 COT 2013 on /dev/pts/9 from arqsrmp01.suramericana.com.co
*******************************************************************************
* *
* *
* Welcome to AIX Version 6.1! *
* *
* *
* Please see the README file in /usr/lpp/bos for information pertinent to *
* this release of the AIX Operating System. *
* *
* *
*******************************************************************************
$
$
$
$ df -g
Filesystem GB blocks Free %Used Iused %Iused Mounted on
/dev/hd4 1.00 0.32 69% 12312 13% /
/dev/hd2 4.00 1.61 60% 55397 12% /usr
/dev/hd9var 1.25 0.36 72% 8899 9% /var
/dev/hd3 1.75 1.29 27% 5980 2% /tmp
/dev/hd1 0.50 0.14 72% 2077 6% /home
/dev/hd11admin 0.25 0.25 1% 5 1% /admin
/proc - - - - - /proc
/dev/hd10opt 0.75 0.46 39% 9952 9% /opt
/dev/livedump 0.25 0.25 1% 4 1% /var/adm/ras/livedump
Page 226
AGENTES SCM
/dev/ptfs_lv 18.00 12.96 29% 32521 2% /PTFs
/dev/product11_lv 65.00 24.93 62% 658956 10% /oracle
/dev/product10_lv 10.00 6.48 36% 16617 2% /oracle10
/dev/aplic_lv 2.12 0.68 68% 23030 13% /oracle/home/APLIC
/dev/dllo_lv 16.25 4.34 74% 104506 10% /oracle/home/DLLO
/dev/utl_lv 1.50 0.76 50% 1302 1% /oracle/home/utlfile
/dev/trace_lv 12.00 11.79 2% 70 1% /oracle/TRACE_DLLO
/dev/rman10_lv 4.50 2.63 42% 1797 1% /oracle/RMAN10
/dev/export_lv 49.75 44.42 11% 8647 1% /export
/dev/tivoli_lv 1.00 0.71 29% 2722 2% /usr/tivoli
/dev/itm_lv 1.00 0.37 63% 4271 5% /opt/IBM/ITM
/dev/admon_lv 5.00 0.98 81% 5634 3% /administrador
/dev/temporal_lv 1.00 0.92 9% 1272 1% /temporal
/dev/scm_lv 1.00 0.96 5% 484 1% /opt/IBM/SCM
/dev/perfmgr_lv 1.00 0.98 3% 85 1% /var/adm/perfmgr
/dev/nimlv 8.00 7.42 8% 15780 1% /nim/spot
/dev/nim_mksysb 40.00 9.38 77% 6 1% /nim/mksysb
/dev/archive_lv 1.00 0.56 45% 56 1% /archive_dllo
/dev/nim_lpp 10.00 8.25 18% 584 1% /nim/lpp
/dev/rman11_lv 13.00 1.34 90% 42 1% /oracle/RMAN11
$
$
$ cd ^C
$ cd ^C
$ cd /opt/IBM/SCM
$ ls
_jvm bin codeset jars lost+found scmclient_log.txt
_uninst client etc license msg tools
$ cd bin
$ ls
wbindmsg
$ cd ..
$ ls^C
$ ls
_jvm bin codeset jars lost+found scmclient_log.txt
_uninst client etc license msg tools
$ cd client
$ ls
ITSCMJ050101.sys client.jks collectors jacclient.UNIX jtzu public.jks scmclient.conf.UNIX
client.id client.pref jacclient jacclient.log lock schedules
$ clear
$ ls
ITSCMJ050101.sys client.jks collectors jacclient.UNIX jtzu public.jks scmclient.conf.UNIX
client.id client.pref jacclient jacclient.log lock schedules
$ pwd
Page 227
AGENTES SCM
/opt/IBM/SCM/client
$ ./^C
$ p s-fea ^C
$ ps -fea |grep jac
ibmadmhe 34669188 46465102 0 15:50:13 pts/2 0:00 grep jac
root 41550460 1 0 15:34:28 - 0:00 /bin/sh /opt/IBM/SCM/client/jacclient start
$
$ cat ^C
$ more jacclient.log
jacclient.log: The file access permissions do not allow the specified action.
$ ls -lrt
total 120
-rw-r--r-- 1 root system 110 Nov 28 2006 ITSCMJ050101.sys
-rwxr-x--- 1 root system 13464 Dec 13 2006 jacclient
drwxr-xr-x 3 root system 256 Jan 25 15:33 jtzu
-rw-r--r-- 1 root system 748 Jan 25 15:33 scmclient.conf.UNIX
-rwxr-x--- 1 root system 13464 Jan 25 15:33 jacclient.UNIX
-rw------- 1 root system 0 Jan 25 15:34 lock
drwx------ 2 root system 256 Jan 25 15:34 collectors
-rw-r----- 1 root system 647 Jan 25 15:34 client.pref
-rw------- 1 root system 3 Jan 25 15:34 client.id
-rw------- 1 root system 32 Jan 25 15:34 public.jks
-rw------- 1 root system 1419 Jan 25 15:35 client.jks
drwx------ 2 root system 256 Jan 25 15:35 schedules
-rw------- 1 root system 2398 Jan 25 15:49 jacclient.log
$ id
uid=333(ibmadmhe) gid=1(staff)
$ su -
root's Password:
3004-501 Cannot su to "root" : Authentication is denied.
$ sudo su -
mdebddd06/ >cd /opt/IBM/SCM/client/
mdebddd06/opt/IBM/SCM/client >ls
ITSCMJ050101.sys client.jks collectors jacclient.UNIX jtzu public.jks scmclient.conf.UNIX
client.id client.pref jacclient jacclient.log lock schedules
mdebddd06/opt/IBM/SCM/client >clear
mdebddd06/opt/IBM/SCM/client >ls
ITSCMJ050101.sys client.jks collectors jacclient.UNIX jtzu public.jks scmclient.conf.UNIX
client.id client.pref jacclient jacclient.log lock schedules
Page 228
AGENTES SCM
mdebddd06/opt/IBM/SCM/client >cd jacclient
ksh: jacclient: 0403-037 The specified path name is not a directory.
mdebddd06/opt/IBM/SCM/client >ls
mdebddd06/opt/IBM/SCM/client >ls -lryt
ls: Not a recognized flag: y
Usage: ls [-1ACFHLNRSabcdefgiklmnopqrstuxEUX] [File...]
mdebddd06/opt/IBM/SCM/client >ls -lrt
total 120
-rw-r--r-- 1 root system 110 Nov 28 2006 ITSCMJ050101.sys
-rwxr-x--- 1 root system 13464 Dec 13 2006 jacclient
drwxr-xr-x 3 root system 256 Jan 25 15:33 jtzu
-rw-r--r-- 1 root system 748 Jan 25 15:33 scmclient.conf.UNIX
-rwxr-x--- 1 root system 13464 Jan 25 15:33 jacclient.UNIX
-rw------- 1 root system 0 Jan 25 15:34 lock
drwx------ 2 root system 256 Jan 25 15:34 collectors
-rw-r----- 1 root system 647 Jan 25 15:34 client.pref
-rw------- 1 root system 3 Jan 25 15:34 client.id
-rw------- 1 root system 32 Jan 25 15:34 public.jks
-rw------- 1 root system 1419 Jan 25 15:35 client.jks
drwx------ 2 root system 256 Jan 25 15:35 schedules
-rw------- 1 root system 2398 Jan 25 15:49 jacclient.log
mdebddd06/opt/IBM/SCM/client >more jacclient.log
mdebddd06/opt/IBM/SCM/client >ping 10.201.138.42
PING 10.201.138.42: (10.201.138.42): 56 data bytes
64 bytes from 10.201.138.42: icmp_seq=0 ttl=123 time=0 ms
64 bytes from 10.201.138.42: icmp_seq=1 ttl=123 time=0 ms
^C
--- 10.201.138.42 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0/0/0 ms
mdebddd06/opt/IBM/SCM/client >telnet 10.201.138.42
ksh: telnet: not found.
mdebddd06/opt/IBM/SCM/client >
mdebddd06/opt/IBM/SCM/client >
mdebddd06/opt/IBM/SCM/client >more jacclient.log
mdebddd06/opt/IBM/SCM/client >telnet 10.201.138.42 3051
Trying...
telnet: connect: A remote host refused an attempted connect operation.
mdebddd06/opt/IBM/SCM/client >telnet 10.201.138.42 1950
Trying...
Connected to 10.201.138.42.
Escape character is '^]'.
j Q
f db e c lIn>v
^CConnection closed.
mdebddd06/opt/IBM/SCM/client >
Page 229
AGENTES SCM
mdebddd06/opt/IBM/SCM/client >
mdebddd06/opt/IBM/SCM/client >
mdebddd06/opt/IBM/SCM/client >
mdebddd06/opt/IBM/SCM/client >
mdebddd06/opt/IBM/SCM/client >netstat -na |grep 1950
tcp4 0 0 *.1950 *.* LISTEN
f100050017195008 stream 0 0 0 f100050017164c80 0 0
mdebddd06/opt/IBM/SCM/client >
mdebddd06/opt/IBM/SCM/client >
mdebddd06/opt/IBM/SCM/client >
mdebddd06/opt/IBM/SCM/client >
mdebddd06/opt/IBM/SCM/client >
mdebddd06/opt/IBM/SCM/client >
mdebddd06/opt/IBM/SCM/client >
mdebddd06/opt/IBM/SCM/client >clear
mdebddd06/opt/IBM/SCM/client >
mdebddd06/opt/IBM/SCM/client >
mdebddd06/opt/IBM/SCM/client >
mdebddd06/opt/IBM/SCM/client >
mdebddd06/opt/IBM/SCM/client >
mdebddd06/opt/IBM/SCM/client >ifconfig -a
en3: flags=1e080863,c0<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACTIVE),LARGESEND,CHAIN>
inet 10.203.10.87 netmask 0xfffffe00 broadcast 10.203.11.255
tcp_sendspace 131072 tcp_recvspace 65536 rfc1323 0
lo0: flags=e08084b,c0<UP,BROADCAST,LOOPBACK,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,LARGESEND,CHAIN>
inet 127.0.0.1 netmask 0xff000000 broadcast 127.255.255.255
inet6 ::1%1/0
tcp_sendspace 131072 tcp_recvspace 131072 rfc1323 1
mdebddd06/opt/IBM/SCM/client >
mdebddd06/opt/IBM/SCM/client >
mdebddd06/opt/IBM/SCM/client >
Page 230
AGENTES SCM
Page 231
AGENTES SCM
Page 232
AGENTES SCM
BY DOWNLOADING, INSTALLING, COPYING, ACCESSING, OR USING THE PROGRAM
YOU AGREE TO THE TERMS OF THIS AGREEMENT. IF YOU ARE ACCEPTING THESE
ENTITY, YOU REPRESENT AND WARRANT THAT YOU HAVE FULL AUTHORITY TO
BIND THAT PERSON, COMPANY, OR LEGAL ENTITY TO THESE TERMS. IF YOU DO
- PROMPTLY RETURN THE PROGRAM AND PROOF OF ENTITLEMENT TO THE PARTY
Page 233
AGENTES SCM
Page 234
AGENTES SCM
en3: flags=1e080863,c0<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACTIVE),LARGESEND,CHAIN>
lo0: flags=e08084b,c0<UP,BROADCAST,LOOPBACK,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,LARGESEND,CHAIN>
Page 235
AGENTES SCM
Page 236
AGENTES SCM
Last unsuccessful login: Fri Jan 25 11:03:44 COT 2013 on ssh from arqsrmp01.suramericana.com.co
Last login: Fri Jan 25 15:29:57 COT 2013 on /dev/pts/9 from arqsrmp01.suramericana.com.co
Page 237
AGENTES SCM
ITSCMJ050101.sys client.jks collectors jacclient.UNIX jtzu public.jks scmclient.conf.UNIX
ITSCMJ050101.sys client.jks collectors jacclient.UNIX jtzu public.jks scmclient.conf.UNIX
Page 238
AGENTES SCM
ITSCMJ050101.sys client.jks collectors jacclient.UNIX jtzu public.jks scmclient.conf.UNIX
ITSCMJ050101.sys client.jks collectors jacclient.UNIX jtzu public.jks scmclient.conf.UNIX
Page 239
AGENTES SCM
Page 240
AGENTES SCM
en3: flags=1e080863,c0<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACTIVE),LARGESEND,CHAIN>
lo0: flags=e08084b,c0<UP,BROADCAST,LOOPBACK,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,LARGESEND,CHAIN>
Page 241
LIBRERIA DE ISOS VIO
Ver los .iso n el VIO Lsrep
Name File Size Optical Access
2AIX61TL6v 1313 None rw
AAIXT6S5 1313 None ro
AIX1_61TL6 4040 DVD_BOE ro
AIX53_TL12 3552 None ro
AIX61TL6 1313 vtopt0 ro
AIX61TL6v 4040 CDVDBE013 rw
AIX61TL7-1 4243 DVDtest rw
Desmonta una unidad unloadopt -vtd vtopt0
Page 242
FUNCIONAMIENTO NOVAVENTA
Page 243
FUNCIONAMIENTO NOVAVENTA
Page 244
MKDVD
MKDVD
1 OPCION NO
2 OPCION ISO
3 OPCION PANTALLAZO
Page 245
MKDVD
Page 246
MKDVD
Page 247
MKDVD
Page 248
MKDVD
Page 249
MKDVD
Page 250
presentar un disco de un vio a
chdev -l disco -a pv=yes Si esta con data omitir este paso
chdev -l hdiskX -a reserve_policy=no_reserve
chdev -l hdiskX -a que_depth=40
chdev -l hdisk70 -a PR_key_value=1 -a reserve_policy=PR_shared Pasarlo PR_shared
renombrar un disco rendev-I hdisk2 -n cldisk1
Page 251
presentar un disco de un vio a
Pasarlo PR_shared
Page 252
ver serial linux vmware
dmidecode |grep UU
serial linux vmware
Page 253
Caracteres especiales ^M
perl -pi -e 's/\r\n/\n/g'
^M
Page 254
convertir a bloques
Valot kilobytes * 2
Page 255
pagina firmware pseries
http://www-304.ibm.com/support/customercare/flrt/
Page 256
NFS_Version4_usrsap
http://www.rootvg.net/content/view/476/1/
NFS_Version4_usrsap
Page 257
installing BASH AIX
Instalando bash en AIX
Page 258
installing BASH AIX
Page 259
Probando MKSYSB
Probar MKSYSB
https://www.ibm.com/developerworks/community/blogs/torator/entry/testing_the_integrity_of_a_mksysb_image30?lang=en
Page 260
Probando MKSYSB
https://www.ibm.com/developerworks/community/blogs/torator/entry/testing_the_integrity_of_a_mksysb_image30?lang=en
Page 261
AMPLIAR FS CLUSTER SOLARIS
Crecer un fs EN CLUSTER 3.2 DE SOLARIS 10
cRECER fs SOLARIS CLUSTER
Ampliar Espacio en SVM con el Cluster
1. PRESENTAR DISCOS AL SISTEMA OPERATIVO :
root@com101 # cfgadm -al
root@com101_n2 # format
Searching for disks...done
c8t60060E8004A41E000000A41E000005E4d0: configured with capacity of 24.99GB
c8t60060E8004A41E000000A41E00000922d0: configured with capacity of 19.99GB
97. c8t60060E8004A41E000000A41E000005DFd0 <HITACHI-OPEN-V-SUN-5009 cyl 4094 alt 2 hd 15 sec 512>
/scsi_vhci/ssd@g60060e8004a41e000000a41e000005df
98. c8t60060E8004A41E000000A41E000005E4d0 <HITACHI-OPEN-V-SUN-5009 cyl 6824 alt 2 hd 15 sec 512>
/scsi_vhci/ssd@g60060e8004a41e000000a41e000005e4
99. c8t60060E8004A41E000000A41E000005E6d0 <HITACHI-OPEN-V-SUN-5009 cyl 5459 alt 2 hd 15 sec 512>
/scsi_vhci/ssd@g60060e8004a41e000000a41e000005e6
339. c8t60060E8004A41E000000A41E00000792d0 <HITACHI-OPEN-V-SUN-5009 cyl 5459 alt 2 hd 15 sec 512>
/scsi_vhci/ssd@g60060e8004a41e000000a41e00000792
340. c8t60060E8004A41E000000A41E00000922d0 <HITACHI-OPEN-V-SUN-5009 cyl 5459 alt 2 hd 15 sec 512>
/scsi_vhci/ssd@g60060e8004a41e000000a41e00000922
341. c8t60060E8004A41E000000A41E00001000d0 <HITACHI-OPEN-V-SUN-5009 cyl 49150 alt 2 hd 15 sec 512>
/scsi_vhci/ssd@g60060e8004a41e000000a41e00001000
342. c8t60060E8004A41E000000A41E00001001d0 <HITACHI-OPEN-V-SUN-5009 cyl 49150 alt 2 hd 15 sec 512>
/scsi_vhci/ssd@g60060e8004a41e000000a41e00001001
Specify disk (enter its number): 98
selecting c8t60060E8004A41E000000A41E000005E4d0
[disk formatted]
Disk not labeled. Label it now? yes
format> disk 340
selecting c8t60060E8004A41E000000A41E00000922d0
[disk formatted]
Disk not labeled. Label it now? yes
root@com100_n1 # scdidadm -r
did instance 359 created.
did subpath com100_n1:/dev/rdsk/c0t60060E8004A41E000000A41E00000922d0 created for instance 359.
Page 262
AMPLIAR FS CLUSTER SOLARIS
did instance 360 created.
did subpath com100_n1:/dev/rdsk/c0t60060E8004A41E000000A41E000005E4d0 created for instance 360.
root@com101_n2 # scdidadm -r
DID subpath "/dev/rdsk/c8t60060E8004A41E000000A41E000005E4d0s2" created for instance "360".
DID subpath "/dev/rdsk/c8t60060E8004A41E000000A41E00000922d0s2" created for instance "359".
root@com101_n2 # df -h |grep gprsindx
/dev/md/gprs_ds/dsk/d22 359G 355G 421M 100% /gprsindx2
/dev/md/gprs_ds/dsk/d21 374G 371G 200M 100% /gprsindx1
#N/A
2. PRESENTAR DISCOS AL SOLARIS VOLUME MANAGER :
root@com101_n2 # metaset -s gprs_ds -a /dev/did/rdsk/d359 /dev/did/rdsk/d360
#N/A
3. CRECER VOLUMENES Y FILESYSTEMS :
root@com101_n2 # metattach -s gprs_ds d2 /dev/did/rdsk/d359s0 /dev/did/rdsk/d360s0
gprs_ds/d2: components are attached
root@com101 # metastat -s gprs_ds -i d21
gprs_ds/d21: Soft Partition
Device: gprs_ds/d2
State: Okay
Size: 291504128 blocks (139 GB)
Extent Start Block Block count
0 32 165675008
1 331350112 67108864
2 532676768 58720256
gprs_ds/d2: Concat/Stripe
Size: 729139200 blocks (347 GB)
Stripe 0: (interlace: 32 blocks)
Device Start Block Dbase State Reloc Hot Spare
/dev/dsk/c8t60060E8004A41E000000A41E0000054Ad0s0 0 No Okay Yes
/dev/dsk/c8t60060E8004A41E000000A41E00000550d0s0 0 No Okay Yes
/dev/dsk/c8t60060E8004A41E000000A41E00000557d0s0 0 No Okay Yes
/dev/dsk/c8t60060E8004A41E000000A41E0000055Dd0s0 0 No Okay Yes
Stripe 1: (interlace: 32 blocks)
Device Start Block Dbase State Reloc Hot Spare
/dev/dsk/c8t60060E8004A41E000000A41E00000573d0s0 0 No Okay Yes
Page 263
AMPLIAR FS CLUSTER SOLARIS
/dev/dsk/c8t60060E8004A41E000000A41E00000575d0s0 0 No Okay Yes
/dev/dsk/c8t60060E8004A41E000000A41E00000577d0s0 0 No Okay Yes
/dev/dsk/c8t60060E8004A41E000000A41E00000579d0s0 0 No Okay Yes
Stripe 2: (interlace: 32 blocks)
Device Start Block Dbase State Reloc Hot Spare
/dev/dsk/c8t60060E8004A41E000000A41E00000584d0s0 0 No Okay Yes
/dev/dsk/c8t60060E8004A41E000000A41E00000585d0s0 0 No Okay Yes
/dev/dsk/c8t60060E8004A41E000000A41E00000586d0s0 0 No Okay Yes
/dev/dsk/c8t60060E8004A41E000000A41E00000587d0s0 0 No Okay Yes
Stripe 3: (interlace: 32 blocks)
Device Start Block Dbase State Reloc Hot Spare
/dev/dsk/c8t60060E8004A41E000000A41E0000067Ad0s0 0 No Okay Yes
/dev/dsk/c8t60060E8004A41E000000A41E0000067Bd0s0 0 No Okay Yes
/dev/dsk/c8t60060E8004A41E000000A41E00000678d0s0 0 No Okay Yes
/dev/dsk/c8t60060E8004A41E000000A41E00000679d0s0 0 No Okay Yes
Stripe 4: (interlace: 32 blocks)
Device Start Block Dbase State Reloc Hot Spare
/dev/dsk/c8t60060E8004A41E000000A41E000006E3d0s0 0 No Okay Yes
/dev/dsk/c8t60060E8004A41E000000A41E000006E4d0s0 0 No Okay Yes
/dev/dsk/c8t60060E8004A41E000000A41E000006E5d0s0 0 No Okay Yes
/dev/dsk/c8t60060E8004A41E000000A41E000006E6d0s0 0 No Okay Yes
root@com101_n2 # metattach -s gprs_ds d21 20g
gprs_ds/d21: Soft Partition has been grown
root@com101_n2 # metattach -s gprs_ds d22 25g
metattach: com101_n2: gprs_ds/d22: not enough space available for request
root@com101_n2 # metattach -s gprs_ds d22 24g
metattach: com101_n2: gprs_ds/d22: not enough space available for request
root@com101_n2 # metattach -s gprs_ds d22 23g
metattach: com101_n2: gprs_ds/d22: not enough space available for request
root@com101_n2 # metattach -s gprs_ds d22 22g
gprs_ds/d22: Soft Partition has been grown
root@com101_n2 # metattach -s gprs_ds d22 500mb
gprs_ds/d22: Soft Partition has been grown
root@com101_n2 # metattach -s gprs_ds d22 200mb
gprs_ds/d22: Soft Partition has been grown
root@com101_n2 # metattach -s gprs_ds d22 100mb
gprs_ds/d22: Soft Partition has been grown
root@com101_n2 # metattach -s gprs_ds d22 100mb
metattach: com101_n2: gprs_ds/d22: not enough space available for request
Page 264
AMPLIAR FS CLUSTER SOLARIS
root@com101_n2 # metattach -s gprs_ds d22 50mb
metattach: com101_n2: gprs_ds/d22: not enough space available for request
Crecimiento de FS
root@com101_n2 # growfs -M /gprsindx1 /dev/md/gprs_ds/rdsk/d21
/dev/md/gprs_ds/rdsk/d21: Unable to find Media type. Proceeding with system determined parameters.
Warning: 4096 sector(s) in last cylinder unallocated
/dev/md/gprs_ds/rdsk/d21: 838860800 sectors in 136534 cylinders of 48 tracks, 128 sectors
409600.0MB in 8534 cyl groups (16 c/g, 48.00MB/g, 5824 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 98464, 196896, 295328, 393760, 492192, 590624, 689056, 787488, 885920,
Initializing cylinder groups:
...............................................................................
...............................................................................
............
super-block backups for last 10 cylinder groups at:
837944864, 838043296, 838141728, 838240160, 838338592, 838437024, 838535456,
838633888, 838732320, 838830752
root@com101_n2 # growfs -M /gprsindx2 /dev/md/gprs_ds/rdsk/d22
/dev/md/gprs_ds/rdsk/d22: Unable to find Media type. Proceeding with system determined parameters.
/dev/md/gprs_ds/rdsk/d22: 812163072 sectors in 132188 cylinders of 48 tracks, 128 sectors
396564.0MB in 8262 cyl groups (16 c/g, 48.00MB/g, 5824 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 98464, 196896, 295328, 393760, 492192, 590624, 689056, 787488, 885920,
Initializing cylinder groups:
...............................................................................
...............................................................................
.......
super-block backups for last 10 cylinder groups at:
811212320, 811310752, 811409184, 811507616, 811597856, 811696288, 811794720,
811893152, 811991584, 812090016
#N/A
4. VERIFICAR CRECIMIENTO :
ANTES :
/dev/md/gprs_ds/dsk/d22 359G 355G 421M 100% /gprsindx2
/dev/md/gprs_ds/dsk/d21 374G 371G 200M 100% /gprsindx1
DESPUES :
/dev/md/gprs_ds/dsk/d22 381G 355G 23G 94% /gprsindx2
/dev/md/gprs_ds/dsk/d21 394G 371G 20G 95% /gprsindx1
Page 265
AMPLIAR FS CLUSTER SOLARIS
97. c8t60060E8004A41E000000A41E000005DFd0 <HITACHI-OPEN-V-SUN-5009 cyl 4094 alt 2 hd 15 sec 512>
98. c8t60060E8004A41E000000A41E000005E4d0 <HITACHI-OPEN-V-SUN-5009 cyl 6824 alt 2 hd 15 sec 512>
99. c8t60060E8004A41E000000A41E000005E6d0 <HITACHI-OPEN-V-SUN-5009 cyl 5459 alt 2 hd 15 sec 512>
339. c8t60060E8004A41E000000A41E00000792d0 <HITACHI-OPEN-V-SUN-5009 cyl 5459 alt 2 hd 15 sec 512>
340. c8t60060E8004A41E000000A41E00000922d0 <HITACHI-OPEN-V-SUN-5009 cyl 5459 alt 2 hd 15 sec 512>
341. c8t60060E8004A41E000000A41E00001000d0 <HITACHI-OPEN-V-SUN-5009 cyl 49150 alt 2 hd 15 sec 512>
342. c8t60060E8004A41E000000A41E00001001d0 <HITACHI-OPEN-V-SUN-5009 cyl 49150 alt 2 hd 15 sec 512>
did subpath com100_n1:/dev/rdsk/c0t60060E8004A41E000000A41E00000922d0 created for instance 359.
Page 266
AMPLIAR FS CLUSTER SOLARIS
did subpath com100_n1:/dev/rdsk/c0t60060E8004A41E000000A41E000005E4d0 created for instance 360.
DID subpath "/dev/rdsk/c8t60060E8004A41E000000A41E000005E4d0s2" created for instance "360".
DID subpath "/dev/rdsk/c8t60060E8004A41E000000A41E00000922d0s2" created for instance "359".
/dev/dsk/c8t60060E8004A41E000000A41E0000054Ad0s0 0 No Okay Yes
/dev/dsk/c8t60060E8004A41E000000A41E00000550d0s0 0 No Okay Yes
/dev/dsk/c8t60060E8004A41E000000A41E00000557d0s0 0 No Okay Yes
/dev/dsk/c8t60060E8004A41E000000A41E0000055Dd0s0 0 No Okay Yes
/dev/dsk/c8t60060E8004A41E000000A41E00000573d0s0 0 No Okay Yes
Page 267
AMPLIAR FS CLUSTER SOLARIS
/dev/dsk/c8t60060E8004A41E000000A41E00000575d0s0 0 No Okay Yes
/dev/dsk/c8t60060E8004A41E000000A41E00000577d0s0 0 No Okay Yes
/dev/dsk/c8t60060E8004A41E000000A41E00000579d0s0 0 No Okay Yes
/dev/dsk/c8t60060E8004A41E000000A41E00000584d0s0 0 No Okay Yes
/dev/dsk/c8t60060E8004A41E000000A41E00000585d0s0 0 No Okay Yes
/dev/dsk/c8t60060E8004A41E000000A41E00000586d0s0 0 No Okay Yes
/dev/dsk/c8t60060E8004A41E000000A41E00000587d0s0 0 No Okay Yes
/dev/dsk/c8t60060E8004A41E000000A41E0000067Ad0s0 0 No Okay Yes
/dev/dsk/c8t60060E8004A41E000000A41E0000067Bd0s0 0 No Okay Yes
/dev/dsk/c8t60060E8004A41E000000A41E00000678d0s0 0 No Okay Yes
/dev/dsk/c8t60060E8004A41E000000A41E00000679d0s0 0 No Okay Yes
/dev/dsk/c8t60060E8004A41E000000A41E000006E3d0s0 0 No Okay Yes
/dev/dsk/c8t60060E8004A41E000000A41E000006E4d0s0 0 No Okay Yes
/dev/dsk/c8t60060E8004A41E000000A41E000006E5d0s0 0 No Okay Yes
/dev/dsk/c8t60060E8004A41E000000A41E000006E6d0s0 0 No Okay Yes
Page 268
AMPLIAR FS CLUSTER SOLARIS
/dev/md/gprs_ds/rdsk/d21: Unable to find Media type. Proceeding with system determined parameters.
/dev/md/gprs_ds/rdsk/d21: 838860800 sectors in 136534 cylinders of 48 tracks, 128 sectors
/dev/md/gprs_ds/rdsk/d22: Unable to find Media type. Proceeding with system determined parameters.
/dev/md/gprs_ds/rdsk/d22: 812163072 sectors in 132188 cylinders of 48 tracks, 128 sectors
Page 269
RESTAURAR EN UNA RUTA UN MKSYS
Descripcin
Este comando restaura los fs del S.O. desde donde est ubicado, si se para en el / daa todo el S.O. del servidor donde est
Sirve para probar que un backup imagen haya quedado bien
Este comando visualiza
Visualizar los archivos respaldados en un mksysb
Page 270
RESTAURAR EN UNA RUTA UN MKSYS
Comando
restorevgfiles -f '/imagen_soa/FNABOGTSM1
restore -Tqvf FNABOGTSM1
restore -Tqvf
sudo su -c "restore -Tvf /dev/rmt0"
Page 271
NFS EN AIX
TENER EN CUENTA PARA MONTAR EL NFS EN AIX
SMITTY NFS TENER EN CUENTA LA OPCION ACCESS PONER LOS DOS SERVER O EL SERVER QUE SE NECESITE
INICIAR EL SERVICIO DE NFS startsrc -s rpc.mountd
startsrc -s nfsd
lssrc -a
Page 272
NFS EN AIX
SMITTY NFS TENER EN CUENTA LA OPCION ACCESS PONER LOS DOS SERVER O EL SERVER QUE SE NECESITE
Page 273
mksysb-default
Page 274
mksysb-default
Page 275
mksysb-default
Page 276
SAMBA BIDIRECCIONAL
SAMBA BIDIRECCIONAL
smbclient -L 9.7.58.115 -U Administradores
mount 9.7.58.115/Comparit /mnt/compartir
WINDOWS
Page 277
CIFS
CIFS
montar cifs
mount -v cifs -n 10.16.20.13/DEVUSER/zxsa1254 -o fmode=775 -o uid=204 -o gid=218 /DS_D_ERP_P /DS_D_ERP_P
dejarlo en el /etc/filesystems
/DS_D_ERP_P:
dev = /DS_D_ERP_P
vfs = cifs
nodename = 10.16.20.13/DEVUSER/zxsa1254
mount = true
options = uid=204,gid=218,fmode=775
account = false
/DS_P_ERP_P 10.16.20.10/PRODUSER/zxsa1254 /DS_P_ERP_P cifs -- uid=222,gid=232,fmode=775,rw yes no
Page 278
CIFS
Page 279
CIFS
Page 280
CIFS
Page 281
CIFS
Page 282
CIFS
Page 283
CIFS
Page 284
CIFS
fuser -kucx /cdrom
Page 285
CIFS
mount -v cifs -n 10.16.20.13/DEVUSER/zxsa1254 -o fmode=775 -o uid=204 -o gid=218 /DS_D_ERP_P /DS_D_ERP_P
/DS_P_ERP_P 10.16.20.10/PRODUSER/zxsa1254 /DS_P_ERP_P cifs -- uid=222,gid=232,fmode=775,rw yes no prod
Page 286
BORRAR DISCOS A LA FIJA
SE EJECUTA EN LA LPAR
odmget -q name=hdisk1 CuAt |grep value odmget -q name=$i CuAt |grep value
lspath -l $disco -s available -F"name:connection:parent:path_status:status" >> $HOME/prosap1.txt
Y EN LOS VIO SE valida el ID y deben concodar
DISCO EN prosap1 oem_setup_env
DISCO EN VIO3 hdisk606
DISCO EN VIO4 hdisk603
Para MPIO: fget_config -Av | grep "nombre disco en el storage"
mpio_get_config -Av Storage 5100
Page 287
BORRAR DISCOS A LA FIJA
lspath -l $disco -s available -F"name:connection:parent:path_status:status" >> $HOME/prosap1.txt
Page 288
Creacion FS GPFS
sudo ./mmcrfs opengdop -F /usr/lpp/mmfs/opengdop -B 512K -Q yes -T /opengdop
sudo ./mmchfs opengdop -W opengdop_gpfs
Cuando se vaya a agregar discos a un FS o extender el filesystem
http://blog.nixveda.com/2012/05/increase-size-of-gpfs-filesystem-online.html
Page 289
Creacion FS GPFS
Crear un FS GPFS
Page 290
SWAP EN AIX
SWAP IN AIX
PAGINACION
ibmadmhe@tsmargos:/home/ibmadmhe# svmon -G |grep space
pg space 13107200 22423
total en uso
Se multiplica 13107200 X 4 52428800 dividido en 1024 51200
Page 291
SWAP EN AIX
Page 292
RETIRAR DEL IFCONFIG UNA INTERF
chdev -l en3 -a state=detach
RETIRAR DEL IFCONFIG UNA INTERFAZ
Page 293
Importvg misma lpar igual lvs
Cuando se van a replicar discos en la misma maquina y se necesita importar el vg con otro nombre los logical vo
Page 294
Importvg misma lpar igual lvs
Cuando se van a replicar discos en la misma maquina y se necesita importar el vg con otro nombre los logical vo
Page 295
DISK_OPERATION_ERROR
DISK OPERATION ERROR
SE DA POR RESERVA EN DISCO Y SE DEBEN RETIRAR LAS FIBRAS ADICIONALES QUE SE TENGAN EN EL STORAGE. SE DEBE EJECUTAR LOS SIGUIENTES COMANDOS EN LOS VOLUME GROUP Y ADEMAS REINICIAR LA LPAR.

LABEL: SC_DISK_ERR4
IDENTIFIER: DCB47997
Date/Time: Fri Sep 20 18:33:34 GMT-05:00 2013
Sequence Number: 132027607
Machine Id: 00F6D5514C00
Node Id: xd1ds01
Class: H
Type: TEMP
WPAR: Global
Resource Name: hdisk5
Resource Class:
Resource Type:
Location:
VPD:
Manufacturer................IBM
Machine Type and Model......2107900
Serial Number...............75P51414057
EC Level....................3.70
Device Specific.(Z0)........10
Device Specific.(Z1)........0003
Device Specific.(Z2)........075
Device Specific.(Z3)........21407
Device Specific.(Z4)........08
Device Specific.(Z5)........00
Description
DISK OPERATION ERROR
Probable Causes
MEDIA
DASD DEVICE
User Causes
MEDIA DEFECTIVE
Recommended Actions
FOR REMOVABLE MEDIA, CHANGE MEDIA AND RETRY
PERFORM PROBLEM DETERMINATION PROCEDURES
Failure Causes
MEDIA
Page 296
DISK_OPERATION_ERROR
DISK DRIVE
Recommended Actions
FOR REMOVABLE MEDIA, CHANGE MEDIA AND RETRY
PERFORM PROBLEM DETERMINATION PROCEDURES
Detail Data
PATH ID
1
SENSE DATA
0A00 2800 0000 0007 0000 0104 0000 0000 0000 0000 0000 0000 0118 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0001 1E00 0000 0000 0000 0000 0000 0000 0000 0003 0000
0000 003D 001D
Page 297
DISK_OPERATION_ERROR
SE DA POR RESERVA EN DISCO Y SE DEBEN RETIRAR LAS FIBRAS ADICIONALES QUE SE TENGAN EN EL STORAGE. SE DEBE EJECUTAR LOS SIGUIENTES COMANDOS EN LOS VOLUME GROUP Y ADEMAS REINICIAR LA LPAR.
Page 298
DISK_OPERATION_ERROR
Page 299
DISK_OPERATION_ERROR
SE DA POR RESERVA EN DISCO Y SE DEBEN RETIRAR LAS FIBRAS ADICIONALES QUE SE TENGAN EN EL STORAGE. SE DEBE EJECUTAR LOS SIGUIENTES COMANDOS EN LOS VOLUME GROUP Y ADEMAS REINICIAR LA LPAR.
Page 300
ACT-TLS+ALT-DISK-COPY
alt_disk_copy -l "acNgX" -P "all" -b "update_all" -l "/install/5300TL9SP2" -d "hdisk1"
Se agrega el -i y s ele indica donde se genro el archivo /tmp/dataimage
alt_disk_install -X VG Limpiar el alt_disk_copy
Page 301
NPIV
vfcmap -vadapter vfchost0 -fcp fcs1 Mapear una fibra del vfhost0 a la del VIO
Page 302
Errores al parchar aix
Solucion
http://www-304.ibm.com/support/docview.wss?uid=swg21393928
Page 303
Errores al parchar aix
Page 304
ESTUDIO AIX-ODM
ODM
La odm (object data Manager): Es un conjunto de tablas binarias donde se registra muchas d ela configuracin de AIX. Este conjunto de tabalas forma una base de datos hecha para uso interna del sistema operativo
En la Odm se encuentra
* Tabla con detalle de drivers instalados en el sistema, Estas tablas permiten la deteccin y configuracin automatica de mucho hardware que podria estar instalado en una estacin de trabajo.
* Relacion de de conexiones entre ellos
* Tablas del inventario de software instalado y la historia de los cambios de version
Cada vez que se inicia el aix este pasa por fases de deteccin de software, Este funciona pr el cfgmgr el cual detecta los cambios de hardware (ya que este es casi plug and play)
Lee la ODM y escribe los cambios en la parte misma que contiene el hardware real con sus propiedades.
TABLA pdDv
Lsdev -P -H Caracteristicas de los dispositivos conocidos por el sistema estan alamacenados en la tabla PdDv y las caracteristicas de fabrica de los mismos estn almacenadas en la tabla pdAt
En ambas los dispositivos estan clasificadas por clase (Class) , tipo (type) y subclase (subclass)
La clase indica lo que hace el dispositivo su funcion; el tipo indica el modelo y la subclase indica como se conecta al sistema
Page 305
ESTUDIO AIX-ODM
En la ODM tambien hay definiciones genericas que en muchos casos permiten usar dispositivos de hardware para los que no hay un driver especifico
Aparecen definidos as:
Other SCSI disk permite conectar discos duros de otros fabricantes diferentes a IBM pero sin sus caracteristicas particulares o especiales
La lista completa de dispositivos que una instalacion de AIX reconoce asi
Lsdev -P
TABLA CuDv
Page 306
ESTUDIO AIX-ODM
Muestra dispositivos automaticamente detectados como los que manualmente se han configurado por el administrador y esto esta almacenado en la base de datos personalidad
(Customized)
La segunda columna
Available El dispositivo esta listo para usarse o se est usando
Defined Se definin en ciualquier momento pero por alguna razn no es usable o existe un conflictoi
Para ver los atributos de un dispositivo
Page 307
ESTUDIO AIX-ODM
El cfgmg no detecta cambios en cables paralelos o seriales
Smit devices
Page 308
ESTUDIO AIX-ODM
Tarjeta principal System Planar
CODIGOS DE UBICACION
lsdev -C -H Dos pares indican una tarjeta adaptadora
Tres pares un dispositivo integrado en un planar
Page 309
ESTUDIO AIX-ODM
lsdev -C -H
Ejemplo de los cosigos
AB-CD Identifica el planar, el bus y numero de ranura de la tarjeta controladora de este dispositivo SCSI
EF Identificador del conector de bus SCSi en la tarjeta controladora al que est conectado este dispositivo
G,H ID SCSI del dispositivo (PUN)
Unidad logica (LUN)
/var/adm/ras Aca se encuentran los log de instalacion de inicio de booteo
/var/adm/ras BosMenus.log Aca se encuentran los log de instalacion
Page 310
ESTUDIO AIX-ODM
La odm (object data Manager): Es un conjunto de tablas binarias donde se registra muchas d ela configuracin de AIX. Este conjunto de tabalas forma una base de datos hecha para uso interna del sistema operativo
Tabla con detalle de drivers instalados en el sistema, Estas tablas permiten la deteccin y configuracin automatica de mucho hardware que podria estar instalado en una estacin de trabajo.
Tablas del inventario de software instalado y la historia de los cambios de version
Cada vez que se inicia el aix este pasa por fases de deteccin de software, Este funciona pr el cfgmgr el cual detecta los cambios de hardware (ya que este es casi plug and play)
Lee la ODM y escribe los cambios en la parte misma que contiene el hardware real con sus propiedades.
Caracteristicas de los dispositivos conocidos por el sistema estan alamacenados en la tabla PdDv y las caracteristicas de fabrica de los mismos estn almacenadas en la tabla pdAt
En ambas los dispositivos estan clasificadas por clase (Class) , tipo (type) y subclase (subclass)
La clase indica lo que hace el dispositivo su funcion; el tipo indica el modelo y la subclase indica como se conecta al sistema
Page 311
ESTUDIO AIX-ODM
En la ODM tambien hay definiciones genericas que en muchos casos permiten usar dispositivos de hardware para los que no hay un driver especifico
Other SCSI disk permite conectar discos duros de otros fabricantes diferentes a IBM pero sin sus caracteristicas particulares o especiales
Page 312
ESTUDIO AIX-ODM
Muestra dispositivos automaticamente detectados como los que manualmente se han configurado por el administrador y esto esta almacenado en la base de datos personalidad
Se definin en ciualquier momento pero por alguna razn no es usable o existe un conflictoi
Page 313
ESTUDIO AIX-ODM
Page 314
ESTUDIO AIX-ODM
Dos pares indican una tarjeta adaptadora Cuatro pares a un periferico
Tres pares un dispositivo integrado en un planar
Page 315
ESTUDIO AIX-ODM
Identifica el planar, el bus y numero de ranura de la tarjeta controladora de este dispositivo SCSI
Identificador del conector de bus SCSi en la tarjeta controladora al que est conectado este dispositivo
Page 316
ESTUDIO AIX-ODM
La odm (object data Manager): Es un conjunto de tablas binarias donde se registra muchas d ela configuracin de AIX. Este conjunto de tabalas forma una base de datos hecha para uso interna del sistema operativo
Tabla con detalle de drivers instalados en el sistema, Estas tablas permiten la deteccin y configuracin automatica de mucho hardware que podria estar instalado en una estacin de trabajo.
Caracteristicas de los dispositivos conocidos por el sistema estan alamacenados en la tabla PdDv y las caracteristicas de fabrica de los mismos estn almacenadas en la tabla pdAt
Page 317
ESTUDIO AIX-ODM
Page 318
ESTUDIO AIX-ODM
Page 319
ESTUDIO AIX-ODM
Page 320
ESTUDIO AIX-ODM
Page 321
AIX-Saber de donde viene un pro
1
ps gwww
2 786620 - A 0:00 /usr/sbin/nimsh -s
3 lslpp -w /usr/sbin/nimsh
Page 322
repositorio DVD REDHAT
1 Se va a la siguiente ruta /etc/yum/pluginconf.d
2 Se pone enable=0 Rhnplugin.conf security.conf
3 Se crea el archivo en rhel.repo /etc/yum.repos.d/
4 Backup nohup rsync -avz --exclude=/proc --exclude=/sys --exclude=/Backup /* /Backup/NVAPP043/ &
[rhel55]
Name=Red hat 5
baseurl=file:///media/DVD1
enabled=1
gpgcheck=0
/usr/sbin/exportfs -a
/Backup 10.0.6.17(rw,sync,no_root_squash) Crear archivos propiedad de root
Page 323
repositorio DVD REDHAT
Para que no salga a internet
nohup rsync -avz --exclude=/proc --exclude=/sys --exclude=/Backup /* /Backup/NVAPP043/ &
Page 324
Leer disco aix
Ocupacion disco
sudo readvgda -p hdisk12
Page 325
Crear FS GPFS AIX
Crear FS GPFS AIX
ibmadmhe@tsmargos:/home/ibmadmhe# svmon -G |grep space
1. se crea el archivo con la data del disco nuevo y se le asigna el nombre:
http://blog.nixveda.com/2012/05/increase-size-of-gpfs-filesystem-online.html
/dev/hdisk5:gdoprd01_gpfs:gdoprd02_gpfs:dataAndMetadata::opengdop
sudo mmcrnsd -F /usr/lpp/mmfs/archive
2. Revision de discos
ibmadmhe@coboggdoprd01:/usr/lpp/mmfs/bin# sudo ./mmlsnsd
File system Disk name NSD servers
---------------------------------------------------------------------------
archivelogs_gpfs gdoprdnsd1 gdoprd01_gpfs,gdoprd02_gpfs
smart_gpfs gdoprdnsd2 gdoprd01_gpfs,gdoprd02_gpfs
(free disk) opengdop gdoprd01_gpfs,gdoprd02_gpfs
(free disk) smartfile gdoprd01_gpfs,gdoprd02_gpfs
(free disk) tb_disk1 gdoprd01_gpfs,gdoprd02_gpfs
(free disk) tb_disk2 gdoprd01_gpfs,gdoprd02_gpfs
(free disk) tb_disk3 gdoprd01_gpfs,gdoprd02_gpfs
3. sudo ./mmcrfs smartfile -F /usr/lpp/mmfs/smartfile -B 512K -Q yes -T /smartfiles
4. sudo ./mmmount all
5. Se cambia el nombre del Logical volume con la etiqueta _gpfs as:
sudo ./mmchfs smartfile -W smartfile_gpfs
sudo ./mmcrfs opengdop -F /usr/lpp/mmfs/opengdop -B 512K -Q yes -T /opengdop
sudo ./mmchfs opengdop -W opengdop_gpfs
Page 326
ERROR VG
"extendvg: LVM system call returned with error code (-271). 0516-792 extendvg: Unable to extend volume group."
synclvodm -Pv nombre_vg
Para validacin del disco que tiene el VG en la ODM, se utiliza el comando:
odmget -q "name=nombre_vg and attribute=pv" CuAt
Page 327
ERROR VG
"extendvg: LVM system call returned with error code (-271). 0516-792 extendvg: Unable to extend volume group."
Page 328
Certificacion-AIX
Describa aqu su nota nueva.
chvg -Qn datavg >> esta seguro que con el mirror, si se va un disco el otro lo respalda
odmget -q name=hdisk1 CuAt |grep value
Iswpar-S syswpar1 >>Listar atributos de seguridad en una wpar

alt_disk_copy -O >>Un administrador planea duplicar el rootvg activo en un sistema dado a un disco de reserva que ser
migrado a un hardware ms nuevo. Qu bandera en 'alt_disk_copy' debe usarse para reiniciar el dispositivo definido por el usuario
configuraciones a los valores predeterminados?
esacli problem >> On AIX 7, which command will list a summary of the issues detected by Electronic Service Agent?
chwpar-R CPU=8%-35%,45% skippy >> asignarle CPU a una wpar
Reqeriemientos minimos para instalar AIX 7.1 desde un DVD
A. IBM PowerPC 970, POWER4, POWER5, POWER6 or POWER7 Server 512MB Memory
la ultima vez que el server se reinicio
Identificar estado de un filesystem
Which command will show all the logical volumes, filesystem mount points, and the volume group in
which they reside?
Which of the following is an AIX 7 Cluster Aware feature?
Which TWO groups of actions will create a CDROM file system for device cd0 and mount this on /cdfs?
How can an administrator enable the Workload Partitions Manager feature after AIX 7 has been
installed with the default options?
What are key considerations when planning for Live Application Mobility?
An administrator needs to limit the size of the filesystem cache. Which tuning parameters need to be
adjusted?
An administrator is required to implement resource control for a running system WPAR called "skippy :.
Which flag of the chwpar command will set the CPU Resource control limits for this WPAR to a minimum
of 8%. a desired of 35% and a maximum of 45%?
Which configuration will provide an LPAR maximum network resilience and performance with two
Ethernet adapters?
Page 329
Certificacion-AIX
Describa aqu su nota nueva.
chvg -Qn datavg >> esta seguro que con el mirror, si se va un disco el otro lo respalda
odmget -q name=hdisk1 CuAt |grep value
Iswpar-S syswpar1 >>Listar atributos de seguridad en una wpar
alt_disk_copy -O >>Un administrador planea duplicar el rootvg activo en un sistema dado a un disco de reserva que ser
migrado a un hardware ms nuevo. Qu bandera en 'alt_disk_copy' debe usarse para reiniciar el dispositivo definido por el usuario
configuraciones a los valores predeterminados?
On AIX 7, which command will list a summary of the issues detected by Electronic Service Agent?
chwpar-R CPU=8%-35%,45% skippy >> asignarle CPU a una wpar
Reqeriemientos minimos para instalar AIX 7.1 desde un DVD
A. IBM PowerPC 970, POWER4, POWER5, POWER6 or POWER7 Server 512MB Memory
la ultima vez que el server se reinicio
Identificar estado de un filesystem
Which command will show all the logical volumes, filesystem mount points, and the volume group in
Which of the following is an AIX 7 Cluster Aware feature?
Which TWO groups of actions will create a CDROM file system for device cd0 and mount this on /cdfs?
How can an administrator enable the Workload Partitions Manager feature after AIX 7 has been
installed with the default options?
What are key considerations when planning for Live Application Mobility?
An administrator needs to limit the size of the filesystem cache. Which tuning parameters need to be
An administrator is required to implement resource control for a running system WPAR called "skippy :.
Which flag of the chwpar command will set the CPU Resource control limits for this WPAR to a minimum
of 8%. a desired of 35% and a maximum of 45%?
Which configuration will provide an LPAR maximum network resilience and performance with two
Page 330
Certificacion-AIX
migrado a un hardware ms nuevo. Qu bandera en 'alt_disk_copy' debe usarse para reiniciar el dispositivo definido por el usuario
who -b
filemon
Isvg | Isvg -il
Cluster configurations on the cluster repository disk
Define cd0 mount point as /cdfs in file /etc/cdromd.conf startsrc -s cdromd cdmount cd0
crfs-vcdrfs-pro-d'cd0'-mVcdfs' mount /cdfs
chedition -e command
That the WPAR is checkpointable and both global environments are on the same subnet
sb_min and sb_max
chwpar-r PROC=8%-35%,45% skippy
Configure both Ethernet adapters as IEEE 802.3ad link Aggregated with src_dst_port mode
Page 331
Error no more process aix
lsattr -El sys0 |grep max 128
chdev -l
sys0 -a
maxuproc='
800'
Page 332
ERROR_bosboot_ipldevice
Page 333
ERROR_bosboot_ipldevice
Page 334
ERROR_bosboot_ipldevice
Page 335
ERROR_bosboot_ipldevice
Page 336
ERROR_bosboot_ipldevice
Page 337
ERROR_bosboot_ipldevice
Page 338
Migracion de 5.3 a 6.1 AIX
Pasos para migrar
Tener en cuenta los drivers
con este driver vemos los caminos de los discos diferente
datapath query essmap
pcmpath driver actualizado
sudo chps -s 50 hd5 (se reduce a 50pps el espacio de EL LV de paginacion )
para sincronizar el rootvg
Saber si el disco esta en mirror
1. Creamos el Logical Volume en el VIOSERVER de 50GB utilizando el rootvg del VIO pa realizar la migracion y se lo presentamos a la lpar
2. Desde la lpar le damos el comando para copiar toda el diskmapping del server
3. Ahora realizamos el Altdiskcopy desde la lpar al disco que presentamos desde el vio
Cuando se corre el comando hay que hacer
1. romper el mirror por que el suma los dos discos del mirror entonces por eso se rompe
2. si los lv tienen mas de 12 caracters hay que modificar el image.data para que no afecte la ejecucion del mkszfile
3. Dejar demasiado espacio en el filesystem /usr
despues de haber realizado el atl_disk copy
4. Se da un exportvg rootvg hdisk2 (disco al cual se le realizo el altdiskcopy) con los medios del driver
5. Ahora se d el sudo reducevg rootvg hdisk2 para que se retire el disco del VG
Validar primero que el disco sea el correcto
6. Nos vamos para el VIOSERVER y desmapeamos el disco del server en cuestion.
Cuando estemos seguros ejecutamos
Vamos al VIOSERVER
PARA nmapear un lv desde el vio a la lpar
8. Ahora buscamos el servidor con el cual se realiza la migracion ( )
9. ingresamos por la HMC y hacemos como si reinstalaramos el SO y damos la opcion migrar
y despues seguimos con el procedimiento de excel.
3. Se realiza lel booteo del cd a esta particion ya copiada y se elige la opcion de migrar
4. Despues de instalado los paquetes del sistema se reinicia para que se tomen los cambios
5. Se debe validar cuando hay miror muchas veces el mirror no sirve por que lo presentan desde un mismo disco desde e VIO y por ende se daa el disco y se caga el sistema operativo
6. En este caso vamos a desmapear dos discos que supuestamente estaba en mirror del sistema operativo pero como se tomaron los nuevos discos solictados anteriormente a storage este ya no sirve y como se dijo anteriormente es un disco haciendo mirror
7. Primero Se validan que los discos aun siguen en el sistema (hasta este momento el server esta con estos discos SO)
8. Se reinicia la maquina aplicando el cambio de los discos
Page 339
Migracion de 5.3 a 6.1 AIX
9. Ahora se se revisa el estado de estos dos discos los cuales pertencian al oldrootgvg
10.Se evidencia que ahora el disco 2 es el disco del sistema operativo y los discos 0 y 1 quedaron volando por eso hay que desmapearlos del SO
11. Se retira el oldrootvg el cual era el anterior sistema operativo
12. en la particion se ejeciuta el comand para saber de que vhost se le asigno
Ubicamos la ubicaion virtual la cual es C3 y C4
Ahora buscamos en el siguiente comando de HMC el slot_num=4 y slot_num=3
Tener en cuenta ahora el remote_slot_num=15 y remote_slot_num=10
13. COMA NDO HMC
Page 340
Migracion de 5.3 a 6.1 AIX
lpar_name=viosnudes2,lpar_id=1,slot_num=29,state=1,is_required=1,adapter_type=server,remote_lpar_id=8,remote_lpar_name=null,remote_slot_num=8
lpar_name=viosnudes2,lpar_id=1,slot_num=28,state=1,is_required=1,adapter_type=server,remote_lpar_id=7,remote_lpar_name=null,remote_slot_num=5
lpar_name=viosnudes2,lpar_id=1,slot_num=26,state=1,is_required=1,adapter_type=server,remote_lpar_id=3,remote_lpar_name=NCBI012 BI_QA,remote_slot_num=7
lpar_name=viosnudes2,lpar_id=1,slot_num=25,state=1,is_required=1,adapter_type=server,remote_lpar_id=3,remote_lpar_name=NCBI012 BI_QA,remote_slot_num=6
lpar_name=viosnudes2,lpar_id=1,slot_num=20,state=1,is_required=1,adapter_type=server,remote_lpar_id=5,remote_lpar_name=NCNPD012,remote_slot_num=6
lpar_name=viosnudes2,lpar_id=1,slot_num=19,state=1,is_required=1,adapter_type=server,remote_lpar_id=5,remote_lpar_name=NCNPD012,remote_slot_num=5
lpar_name=viosnudes2,lpar_id=1,slot_num=16,state=1,is_required=1,adapter_type=server,remote_lpar_id=5,remote_lpar_name=NCNPD012,remote_slot_num=4
lpar_name=viosnudes2,lpar_id=1,slot_num=15,state=1,is_required=1,adapter_type=server,remote_lpar_id=4,remote_lpar_name=NCPOR012,remote_slot_num=4
lpar_name=viosnudes2,lpar_id=1,slot_num=14,state=1,is_required=1,adapter_type=server,remote_lpar_id=3,remote_lpar_name=NCBI012 BI_QA,remote_slot_num=4
lpar_name=viosnudes2,lpar_id=1,slot_num=11,state=1,is_required=1,adapter_type=server,remote_lpar_id=5,remote_lpar_name=NCNPD012,remote_slot_num=3
lpar_name=viosnudes2,lpar_id=1,slot_num=10,state=1,is_required=1,adapter_type=server,remote_lpar_id=4,remote_lpar_name=NCPOR012,remote_slot_num=3
lpar_name=viosnudes2,lpar_id=1,slot_num=9,state=1,is_required=1,adapter_type=server,remote_lpar_id=3,remote_lpar_name=NCBI012 BI_QA,remote_slot_num=3
lpar_name=viosnudes2,lpar_id=1,slot_num=6,state=1,is_required=1,adapter_type=server,remote_lpar_id=9,remote_lpar_name=NCDBE053 Helados,remote_slot_num=3
lpar_name=viosnudes2,lpar_id=1,slot_num=49,state=1,is_required=1,adapter_type=server,remote_lpar_id=4,remote_lpar_name=NCPOR012,remote_slot_num=5
lpar_name=viosnudes2,lpar_id=1,slot_num=50,state=1,is_required=0,adapter_type=server,remote_lpar_id=11,remote_lpar_name=Borrar,remote_slot_num=30
lpar_name=viosnudes2,lpar_id=1,slot_num=51,state=1,is_required=0,adapter_type=server,remote_lpar_id=2,remote_lpar_name=migracion,remote_slot_num=2
lsdev -dev fcs0 -vpd |grep Net >> si aparece fcsci0
12. sabiendo que la partion es la numero 4
13. damos el siguiente comando en el VIO
Se da estos dos comandos por que el remote_slot_number eran 10 y 15
Page 341
Migracion de 5.3 a 6.1 AIX
Ahora se eliminan los VTD
Se eliminan los comit cuando se realiza la migracion
CUANDO SE PIERDA UN PATH DE UN VIO
Z
Page 342
Migracion de 5.3 a 6.1 AIX
datapath driver obsoleto
lspath unicamente muestra el vpath y este a su vez por que fibra presenta los discos
cada vpath me muestra las fibras por la cuales esta.
y ese si mnuestra los discos por el lspath
(esta actividad se puede realizar en culquier momento)
syncvg -v rootvg arregla cosas que quedan corruptas
lsvg -l sapscmpbdvg columnas PV 1 no esta en mirror y dos esta en mirror
-L 50G rootvg
mkszfile
Sudo alt_disk_copy -d hdisk2
2. si los lv tienen mas de 12 caracters hay que modificar el image.data para que no afecte la ejecucion del mkszfile
<f
lspath -l hdisk13 -F"connection:parent:status"
lscfg -vpl vscsi0
Vamos al vio y debe concordar LUN como C2 T1
Sudo exportvg alt_diskvg
sudo rmdev -Rdl hdisk13
rmvdev -vtd migncerpno2
mkvdev -vdev migncpor2_lv -vadapter vhost17 -dev migncerpno2
5. Se debe validar cuando hay miror muchas veces el mirror no sirve por que lo presentan desde un mismo disco desde e VIO y por ende se daa el disco y se caga el sistema operativo
6. En este caso vamos a desmapear dos discos que supuestamente estaba en mirror del sistema operativo pero como se tomaron los nuevos discos solictados anteriormente a storage este ya no sirve y como se dijo anteriormente es un disco haciendo mirror
hdisk0 00018c45d037bfd4 rootvg active
hdisk1 00018c45f7228fcf rootvg active
hdisk6 00018c45a60c8ab4 sapepqvg active
hdisk7 00018c45a60c8c74 sapepqvg active
hdisk8 00018c45a60c8d8b sapepqvg active
Page 343
Migracion de 5.3 a 6.1 AIX
hdisk9 00018c45a60c8ea2 sapepqvg active
hdisk2 00018c45932aab20 altinst_rootvg
hdisk0 00018c45d037bfd4 none
hdisk1 00018c45f7228fcf none
hdisk6 00018c45a60c8ab4 sapepqvg active
hdisk7 00018c45a60c8c74 sapepqvg active
hdisk8 00018c45a60c8d8b sapepqvg active
hdisk9 00018c45a60c8ea2 sapepqvg active
hdisk2 00018c45932aab20 rootvg
10.Se evidencia que ahora el disco 2 es el disco del sistema operativo y los discos 0 y 1 quedaron volando por eso hay que desmapearlos del SO
ncpor012/home/ibmadmhe#lsvg
old_rootvg
rootvg
sapepqvg
Exportvg old_rootvg
lspath -l hdisk1 -s available -F"name:connection:parent:path_status:status"
hdisk1:810000000000:vscsi1:Available:Enabled
lspath -l hdisk0 -s available -F"name:connection:parent:path_status:status"
hdisk0:820000000000:vscsi0:Available:Enabled
ncpor012/home/ibmadmgp#lscfg -l vscsi0
vscsi0 U9133.55A.061C4EH-V4-C3-T1 Virtual SCSI Client Adapter
ncpor012/home/ibmadmgp#lscfg -l vscsi1
vscsi1 U9133.55A.061C4EH-V4-C4-T1 Virtual SCSI Client Adapter
lpar_name=NCPOR012,lpar_id=4,slot_num=4,state=1,is_required=1,a
dapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes
2,remote_slot_num=15
lpar_name=NCPOR012,lpar_id=4,slot_num=3,state=1,is_required=1,a
dapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes
2,remote_slot_num=10
ibmadmgp@HMCSNCH4:~> lshwres -m Server-9133-55A-SN061C4EH --rsubtype scsi --level lpar -r virtualio
lpar_name=viosnudes2,lpar_id=1,slot_num=38,state=1,is_required=1,adapter_type=server,remote_lpar_id=10,remote_lpar_name=NCPI011,remote_slot_num=7
lpar_name=viosnudes2,lpar_id=1,slot_num=37,state=1,is_required=1,adapter_type=server,remote_lpar_id=10,remote_lpar_name=NCPI011,remote_slot_num=6
lpar_name=viosnudes2,lpar_id=1,slot_num=36,state=1,is_required=1,adapter_type=server,remote_lpar_id=10,remote_lpar_name=NCPI011,remote_slot_num=5
lpar_name=viosnudes2,lpar_id=1,slot_num=35,state=1,is_required=1,adapter_type=server,remote_lpar_id=10,remote_lpar_name=NCPI011,remote_slot_num=4
lpar_name=viosnudes2,lpar_id=1,slot_num=34,state=1,is_required=1,adapter_type=server,remote_lpar_id=10,remote_lpar_name=NCPI011,remote_slot_num=3
lpar_name=viosnudes2,lpar_id=1,slot_num=32,state=1,is_required=1,adapter_type=server,remote_lpar_id=9,remote_lpar_name=NCDBE053 Helados,remote_slot_num=6
lpar_name=viosnudes2,lpar_id=1,slot_num=30,state=1,is_required=1,adapter_type=server,remote_lpar_id=9,remote_lpar_name=NCDBE053 Helados,remote_slot_num=4
Page 344
Migracion de 5.3 a 6.1 AIX
lpar_name=viosnudes2,lpar_id=1,slot_num=29,state=1,is_required=1,adapter_type=server,remote_lpar_id=8,remote_lpar_name=null,remote_slot_num=8
lpar_name=viosnudes2,lpar_id=1,slot_num=28,state=1,is_required=1,adapter_type=server,remote_lpar_id=7,remote_lpar_name=null,remote_slot_num=5
lpar_name=viosnudes2,lpar_id=1,slot_num=26,state=1,is_required=1,adapter_type=server,remote_lpar_id=3,remote_lpar_name=NCBI012 BI_QA,remote_slot_num=7
lpar_name=viosnudes2,lpar_id=1,slot_num=25,state=1,is_required=1,adapter_type=server,remote_lpar_id=3,remote_lpar_name=NCBI012 BI_QA,remote_slot_num=6
lpar_name=viosnudes2,lpar_id=1,slot_num=20,state=1,is_required=1,adapter_type=server,remote_lpar_id=5,remote_lpar_name=NCNPD012,remote_slot_num=6
lpar_name=viosnudes2,lpar_id=1,slot_num=19,state=1,is_required=1,adapter_type=server,remote_lpar_id=5,remote_lpar_name=NCNPD012,remote_slot_num=5
lpar_name=viosnudes2,lpar_id=1,slot_num=16,state=1,is_required=1,adapter_type=server,remote_lpar_id=5,remote_lpar_name=NCNPD012,remote_slot_num=4
lpar_name=viosnudes2,lpar_id=1,slot_num=15,state=1,is_required=1,adapter_type=server,remote_lpar_id=4,remote_lpar_name=NCPOR012,remote_slot_num=4
lpar_name=viosnudes2,lpar_id=1,slot_num=14,state=1,is_required=1,adapter_type=server,remote_lpar_id=3,remote_lpar_name=NCBI012 BI_QA,remote_slot_num=4
lpar_name=viosnudes2,lpar_id=1,slot_num=11,state=1,is_required=1,adapter_type=server,remote_lpar_id=5,remote_lpar_name=NCNPD012,remote_slot_num=3
lpar_name=viosnudes2,lpar_id=1,slot_num=10,state=1,is_required=1,adapter_type=server,remote_lpar_id=4,remote_lpar_name=NCPOR012,remote_slot_num=3
lpar_name=viosnudes2,lpar_id=1,slot_num=9,state=1,is_required=1,adapter_type=server,remote_lpar_id=3,remote_lpar_name=NCBI012 BI_QA,remote_slot_num=3
lpar_name=viosnudes2,lpar_id=1,slot_num=6,state=1,is_required=1,adapter_type=server,remote_lpar_id=9,remote_lpar_name=NCDBE053 Helados,remote_slot_num=3
lpar_name=viosnudes2,lpar_id=1,slot_num=49,state=1,is_required=1,adapter_type=server,remote_lpar_id=4,remote_lpar_name=NCPOR012,remote_slot_num=5
lpar_name=viosnudes2,lpar_id=1,slot_num=50,state=1,is_required=0,adapter_type=server,remote_lpar_id=11,remote_lpar_name=Borrar,remote_slot_num=30
lpar_name=viosnudes2,lpar_id=1,slot_num=51,state=1,is_required=0,adapter_type=server,remote_lpar_id=2,remote_lpar_name=migracion,remote_slot_num=2
lpar_name=NCPI011,lpar_id=10,slot_num=7,state=1,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes2,remote_slot_num=38
lpar_name=NCPI011,lpar_id=10,slot_num=6,state=1,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes2,remote_slot_num=37
lpar_name=NCPI011,lpar_id=10,slot_num=3,state=1,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes2,remote_slot_num=34
lpar_name=migracion,lpar_id=2,slot_num=2,state=0,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes2,remote_slot_num=51
lpar_name=NCBI012 BI_QA,lpar_id=3,slot_num=7,state=1,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes2,remote_slot_num=26
lpar_name=NCBI012 BI_QA,lpar_id=3,slot_num=6,state=1,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes2,remote_slot_num=25
lpar_name=NCBI012 BI_QA,lpar_id=3,slot_num=4,state=1,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes2,remote_slot_num=14
lpar_name=NCBI012 BI_QA,lpar_id=3,slot_num=3,state=1,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes2,remote_slot_num=9
lpar_name=NCPOR012,lpar_id=4,slot_num=5,state=1,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes2,remote_slot_num=49
lpar_name=NCPOR012,lpar_id=4,slot_num=4,state=1,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes2,remote_slot_num=15
lpar_name=NCPOR012,lpar_id=4,slot_num=3,state=1,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes2,remote_slot_num=10
lpar_name=NCNPD012,lpar_id=5,slot_num=6,state=1,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes2,remote_slot_num=20
lpar_name=NCNPD012,lpar_id=5,slot_num=3,state=1,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes2,remote_slot_num=11
lpar_name=NCDBE053 Helados,lpar_id=9,slot_num=6,state=1,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes2,remote_slot_num=32
lpar_name=NCDBE053 Helados,lpar_id=9,slot_num=4,state=1,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes2,remote_slot_num=30
lpar_name=NCDBE053 Helados,lpar_id=9,slot_num=3,state=1,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes2,remote_slot_num=6
Partition Number : 4
smap -all | grep 00004
vhost3 U9133.55A.061C4EH-V1-C10 0x00000004
vhost8 U9133.55A.061C4EH-V1-C15 0x00000004
vhost25 U9133.55A.061C4EH-V1-C49 0x00000004
lsmap -vadapter vhost3
Page 345
Migracion de 5.3 a 6.1 AIX
ibmadmgp@viosnudes2$ lsmap -vadapter vhost3
SVSA Physloc Client Partition ID
--------------- -------------------------------------------- ------------------
vhost3 U9133.55A.061C4EH-V1-C10 0x00000004
VTD datapidvc2
Status Available
LUN 0x8200000000000000
Backing device mir_ncpor012
Physloc
rmvdev -vtd datapidvc1
rmvdev -vtd datapidvc2
Smitty install
Software mainteni an utilities
Comit apli soft updates (remove saved files)
Detail ouput no y enter
sudo rmpath -l hdisk1 -p vscsi
Z
Page 346
Migracion de 5.3 a 6.1 AIX
lspath unicamente muestra el vpath y este a su vez por que fibra presenta los discos
lsvg -l sapscmpbdvg columnas PV 1 no esta en mirror y dos esta en mirror
/etc/image.data esto es para el altdiscopy
Me muestra por cual vhosts esta en el vio
vscsi0 U9119.FHA.02C9202-V19-C2-T1 Virtual SCSI Client Adapter
Hardware Location Code......U9119.FHA.02C9202-V19-C2-T1
Y lo retiramos desde el vio
NO GUIARSE POR EL NOMBRE IR A LA HMC Y AL VIO CRUZAR
5. Se debe validar cuando hay miror muchas veces el mirror no sirve por que lo presentan desde un mismo disco desde e VIO y por ende se daa el disco y se caga el sistema operativo
6. En este caso vamos a desmapear dos discos que supuestamente estaba en mirror del sistema operativo pero como se tomaron los nuevos discos solictados anteriormente a storage este ya no sirve y como se dijo anteriormente es un disco haciendo mirror
Page 347
Migracion de 5.3 a 6.1 AIX
lspath -l hdisk1 -s available -F"name:connection:parent:path_status:status"
lspath -l hdisk0 -s available -F"name:connection:parent:path_status:status"
ibmadmgp@HMCSNCH4:~> lshwres -m Server-9133-55A-SN061C4EH --rsubtype scsi --level lpar -r virtualio
lpar_name=viosnudes2,lpar_id=1,slot_num=38,state=1,is_required=1,adapter_type=server,remote_lpar_id=10,remote_lpar_name=NCPI011,remote_slot_num=7
lpar_name=viosnudes2,lpar_id=1,slot_num=37,state=1,is_required=1,adapter_type=server,remote_lpar_id=10,remote_lpar_name=NCPI011,remote_slot_num=6
lpar_name=viosnudes2,lpar_id=1,slot_num=36,state=1,is_required=1,adapter_type=server,remote_lpar_id=10,remote_lpar_name=NCPI011,remote_slot_num=5
lpar_name=viosnudes2,lpar_id=1,slot_num=35,state=1,is_required=1,adapter_type=server,remote_lpar_id=10,remote_lpar_name=NCPI011,remote_slot_num=4
lpar_name=viosnudes2,lpar_id=1,slot_num=34,state=1,is_required=1,adapter_type=server,remote_lpar_id=10,remote_lpar_name=NCPI011,remote_slot_num=3
lpar_name=viosnudes2,lpar_id=1,slot_num=32,state=1,is_required=1,adapter_type=server,remote_lpar_id=9,remote_lpar_name=NCDBE053 Helados,remote_slot_num=6
lpar_name=viosnudes2,lpar_id=1,slot_num=30,state=1,is_required=1,adapter_type=server,remote_lpar_id=9,remote_lpar_name=NCDBE053 Helados,remote_slot_num=4
Page 348
Migracion de 5.3 a 6.1 AIX
lpar_name=viosnudes2,lpar_id=1,slot_num=29,state=1,is_required=1,adapter_type=server,remote_lpar_id=8,remote_lpar_name=null,remote_slot_num=8
lpar_name=viosnudes2,lpar_id=1,slot_num=28,state=1,is_required=1,adapter_type=server,remote_lpar_id=7,remote_lpar_name=null,remote_slot_num=5
lpar_name=viosnudes2,lpar_id=1,slot_num=26,state=1,is_required=1,adapter_type=server,remote_lpar_id=3,remote_lpar_name=NCBI012 BI_QA,remote_slot_num=7
lpar_name=viosnudes2,lpar_id=1,slot_num=25,state=1,is_required=1,adapter_type=server,remote_lpar_id=3,remote_lpar_name=NCBI012 BI_QA,remote_slot_num=6
lpar_name=viosnudes2,lpar_id=1,slot_num=20,state=1,is_required=1,adapter_type=server,remote_lpar_id=5,remote_lpar_name=NCNPD012,remote_slot_num=6
lpar_name=viosnudes2,lpar_id=1,slot_num=19,state=1,is_required=1,adapter_type=server,remote_lpar_id=5,remote_lpar_name=NCNPD012,remote_slot_num=5
lpar_name=viosnudes2,lpar_id=1,slot_num=16,state=1,is_required=1,adapter_type=server,remote_lpar_id=5,remote_lpar_name=NCNPD012,remote_slot_num=4
lpar_name=viosnudes2,lpar_id=1,slot_num=15,state=1,is_required=1,adapter_type=server,remote_lpar_id=4,remote_lpar_name=NCPOR012,remote_slot_num=4
lpar_name=viosnudes2,lpar_id=1,slot_num=14,state=1,is_required=1,adapter_type=server,remote_lpar_id=3,remote_lpar_name=NCBI012 BI_QA,remote_slot_num=4
lpar_name=viosnudes2,lpar_id=1,slot_num=11,state=1,is_required=1,adapter_type=server,remote_lpar_id=5,remote_lpar_name=NCNPD012,remote_slot_num=3
lpar_name=viosnudes2,lpar_id=1,slot_num=10,state=1,is_required=1,adapter_type=server,remote_lpar_id=4,remote_lpar_name=NCPOR012,remote_slot_num=3
lpar_name=viosnudes2,lpar_id=1,slot_num=9,state=1,is_required=1,adapter_type=server,remote_lpar_id=3,remote_lpar_name=NCBI012 BI_QA,remote_slot_num=3
lpar_name=viosnudes2,lpar_id=1,slot_num=6,state=1,is_required=1,adapter_type=server,remote_lpar_id=9,remote_lpar_name=NCDBE053 Helados,remote_slot_num=3
lpar_name=viosnudes2,lpar_id=1,slot_num=49,state=1,is_required=1,adapter_type=server,remote_lpar_id=4,remote_lpar_name=NCPOR012,remote_slot_num=5
lpar_name=viosnudes2,lpar_id=1,slot_num=50,state=1,is_required=0,adapter_type=server,remote_lpar_id=11,remote_lpar_name=Borrar,remote_slot_num=30
lpar_name=viosnudes2,lpar_id=1,slot_num=51,state=1,is_required=0,adapter_type=server,remote_lpar_id=2,remote_lpar_name=migracion,remote_slot_num=2
lpar_name=NCPI011,lpar_id=10,slot_num=7,state=1,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes2,remote_slot_num=38
lpar_name=NCPI011,lpar_id=10,slot_num=6,state=1,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes2,remote_slot_num=37
lpar_name=NCPI011,lpar_id=10,slot_num=3,state=1,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes2,remote_slot_num=34
lpar_name=migracion,lpar_id=2,slot_num=2,state=0,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes2,remote_slot_num=51
lpar_name=NCBI012 BI_QA,lpar_id=3,slot_num=7,state=1,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes2,remote_slot_num=26
lpar_name=NCBI012 BI_QA,lpar_id=3,slot_num=6,state=1,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes2,remote_slot_num=25
lpar_name=NCBI012 BI_QA,lpar_id=3,slot_num=4,state=1,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes2,remote_slot_num=14
lpar_name=NCBI012 BI_QA,lpar_id=3,slot_num=3,state=1,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes2,remote_slot_num=9
lpar_name=NCPOR012,lpar_id=4,slot_num=5,state=1,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes2,remote_slot_num=49
lpar_name=NCPOR012,lpar_id=4,slot_num=4,state=1,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes2,remote_slot_num=15
lpar_name=NCPOR012,lpar_id=4,slot_num=3,state=1,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes2,remote_slot_num=10
lpar_name=NCNPD012,lpar_id=5,slot_num=6,state=1,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes2,remote_slot_num=20
lpar_name=NCNPD012,lpar_id=5,slot_num=3,state=1,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes2,remote_slot_num=11
lpar_name=NCDBE053 Helados,lpar_id=9,slot_num=6,state=1,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes2,remote_slot_num=32
lpar_name=NCDBE053 Helados,lpar_id=9,slot_num=4,state=1,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes2,remote_slot_num=30
lpar_name=NCDBE053 Helados,lpar_id=9,slot_num=3,state=1,is_required=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=viosnudes2,remote_slot_num=6
lsmap -vadapter vhost8
Page 349
Migracion de 5.3 a 6.1 AIX
SVSA Physloc Client Partition ID
--------------- -------------------------------------------- ------------------
vhost8 U9133.55A.061C4EH-V1-C15 0x00000004
VTD datapidvc1
Status Available
LUN 0x8100000000000000
Backing device roo_ncpor012
Physloc
Z
Page 350
Migracion de 5.3 a 6.1 AIX
Page 351
Migracion de 5.3 a 6.1 AIX
/usr/sbin/pcmpath query essmap | grep -w $real |grep path0 |awk '{print $5}'
Page 352
Migracion de 5.3 a 6.1 AIX
Page 353
Migracion de 5.3 a 6.1 AIX
Page 354
Migracion de 5.3 a 6.1 AIX
Page 355
Migracion de 5.3 a 6.1 AIX
/usr/sbin/pcmpath query essmap | grep -w $real |grep path0 |awk '{print $5}'
Page 356
CRON ERP COLOMBINA
cron erp de colombina Muestra las diferentes posibilidades del cron
En este caso la base de datos est en prosap3, la instancia central en prosap3 entonces este debe ser el cron en esta situacin para prosap1
Explicacin root_DB_CI_HOSTS
root_prosap3_prosap3.prosap1
Page 357
CRON ERP COLOMBINA
En este caso la base de datos est en prosap3, la instancia central en prosap3 entonces este debe ser el cron en esta situacin para prosap1
Page 358
VER MEMORIA TOTAL DE AIX
getconf REAL_MEMORY
The 'elseif keyword is not valid within ksh scripts.
VER MEMORIA TOTAL DE AIX
getconf DISK_SIZE /dev/hdisk0
ver tamao de un disco
getconf
HARDWARE_BITM
ODE ver arquitectura del sistema
getconf BOOT_DEVICE saber cual disco es el que bootea
Page 359
Discos HDISK_vs_iD
Mejor
for i in `lspv |awk '{print $1}'`
do
serial=$(lsattr -El $i |grep uniq|cut -c 28-31); tama=$(sudo bootinfo -s $i); echo $i $serial $tama
done
disco y serial
for i in `lspv |awk '{print $1}'`
do
serial=$(lsattr -El $i |grep uniq|cut -c 28-31);echo $i $serial
done
odmget -qattribute=unique_id CuAt|grep name | awk -F'"' '{print $2}'>/tmp/disco1
for i in `cat /tmp/disco1`
do
hostname >>/tmp/host1
done
odmget -qattribute=unique_id CuAt|grep value | awk -F'"' '{print $2}'>/tmp/serial1
odmget -qattribute=unique_id CuAt|grep name | awk -F'"' '{print "getconf DISK_SIZE /dev/"$2}' |sh >/tmp/size1
odmget -qattribute=unique_id CuAt|grep name | awk -F'"' '{print "lspv |grep -w "$2}' |sh|awk '{print $2}' >/tmp/pvid1
odmget -qattribute=unique_id CuAt|grep name | awk -F'"' '{print "lspv |grep -w "$2}' |sh|awk '{print $3}'>/tmp/vg1
echo "Hostname,Disk,Size,VG,PVID,Serial"
paste -d"," /tmp/host1 /tmp/disco1 /tmp/size1 /tmp/vg1 /tmp/pvid1 /tmp/serial1
rm /tmp/disco1 /tmp/size1 /tmp/vg1 /tmp/pvid1 /tmp/serial1 /tmp/host1
Page 360
Discos HDISK_vs_iD
serial=$(lsattr -El $i |grep uniq|cut -c 28-31); tama=$(sudo bootinfo -s $i); echo $i $serial $tama
odmget -qattribute=unique_id CuAt|grep name | awk -F'"' '{print "getconf DISK_SIZE /dev/"$2}' |sh >/tmp/size1
odmget -qattribute=unique_id CuAt|grep name | awk -F'"' '{print "lspv |grep -w "$2}' |sh|awk '{print $2}' >/tmp/pvid1
odmget -qattribute=unique_id CuAt|grep name | awk -F'"' '{print "lspv |grep -w "$2}' |sh|awk '{print $3}'>/tmp/vg1
Page 361
cambiar driver de multipath por
cambiar driver de multipath por MPIO
https://w3-connections.ibm.com/wikis/home?lang=en-us#!/wiki/W43a0bfcb12eb_4e95_9976_2d9daf135187/page/RDAC_MPIO_AIX
Page 362
cambiar driver de multipath por
https://w3-connections.ibm.com/wikis/home?lang=en-us#!/wiki/W43a0bfcb12eb_4e95_9976_2d9daf135187/page/RDAC_MPIO_AIX
Page 363
ACTUALIZAR VIOSERVER
ACTUALIZAR VIOSERVER
backup vioserver backupios -file /imagen_soa/BACKUPVIO1
Page 364
ACTUALIZAR VIOSERVER
Page 365
Script discos
for i in $(</tmp/DISCO)^Jdo^Jserial=`lsattr -El $i |grep uniq|cut -c 28-31`; echo $i $serial^Jdone
Page 366
Script discos
for i in $(</tmp/DISCO)^Jdo^Jserial=`lsattr -El $i |grep uniq|cut -c 28-31`; echo $i $serial^Jdone
Page 367
Saberprocesodeunpuerto
Saber de un puerto que proceso lo tiene
sudo netstat -Aan | grep 30542
sudo rmsock f1000e0002a0b3b8 tcpcb
Page 368
Saberprocesodeunpuerto
Page 369
CONSUMO TOTAL CPU - MEMORIA AIX
Saber CPU vmstat 1 1| tail -1 |awk '{print 100-$16, "% CPU USADA"}'
Memoria total de una lpar aix while true^Jdo^Jdate^Jlssrc -ls clstrmgrES|grep state^Jecho ------------------^Jsleep 5^Jdone
Memoria campo virtual svmon -G | grep memory | awk '{print $6/256}'
Memoria campo virtual svmon -i 2 2 -G -O unit=GB,timestamp=on
revisa el top de 10 procesos que mas estan consumiendo memoria sudo svmon -P -t 10 -O summary=basic,unit=MB,timestamp=on
Page 370
CONSUMO TOTAL CPU - MEMORIA AIX
while true^Jdo^Jdate^Jlssrc -ls clstrmgrES|grep state^Jecho ------------------^Jsleep 5^Jdone
sudo svmon -P -t 10 -O summary=basic,unit=MB,timestamp=on
Page 371
RENOMBRAR EL NOMBRE DEL DISCO A
rendev-I hdisk2 -n cldisk1
Page 372
RENOMBRAR EL NOMBRE DEL DISCO A
rendev-I hdisk2 -n cldisk1
Page 373
parchado aix
Despues de que se parche el servidor ejecutar sudo no -r -o lo_perf=0
sudo ifconfig lo0 -pktchain -largesend
Page 374
STATUS FIBRA-RED-AIX
Fcstat -e fsc0 Si da las estadisticas es por que esta conectada
Entstat entstat -d ent4 | grep -i Link
Page 375
The largest dump device is too
The largest dump device is too small
O
Page 376
The largest dump device is too
Page 377
Verificar discos CAPE
for i in $(</tmp/DISCOS1)^Jdo^Jlsattr -El $i |grep uniq |cut -c 28-31 >> /tmp/O.txt^Jdone
Se ven los id de los discos del sistema operativo
Se copia en otro archivo los id del cape
Page 378
HACMP
COMANDOS HACMP
sudo /usr/es/sbin/cluster/cspoc/cl_ls_shared_vgs -c -C revisar version antes
Saber que Vg comparte el cluster
Most commands should work on all PowerHA ( prior to 5.5) versions.
If there is some syntax error, please consult the manual page for that command.
How to start cluster daemons (options in that order: clstrmgr, clsmuxpd, broadcast message, clinfo, cllockd):
# clstart -m -s -b -i -l
How to show cluster state and substate (depends on clinfo):
# clstat
SNMP-based tool to show cluster state:
# cldump
Similar to cldump, perl script to show cluster state:
# cldisp
How to list the local view of the cluster topology:
# cltopinfo
How to list the local view of the cluster subsystems:
# clshowsrv -a
How to show all necessary info about HACMP:
# clshowsrv -v
How to show HACMP version:
# lslpp -L | grep cluster.es.server.rte
How to verify the HACMP configuration:
# /usr/es/sbin/cluster/diag/clconfig -v -O
How to list app servers configured including start/stop scripts:
# cllsserv
How to locate the resource groups and display their status:
# clRGinfo -v
How to rotate some of the log files:
# clcycle
A cluster ping program with more arguments:
# cl_ping
Cluster rsh program that take cluster node names as argument:
# clrsh
How to find out the name of the local node:
# get_local_nodename
How to check the HACMP ODM:
# clconfig
How to put online/offline or move resource groups:
# clRGmove
How to list the resource groups:
# cllsgrp
How to create a large snapshot of the hacmp configuration:
# clsnapshotinfo
How to show short resource group information:
# cllsres
How to list the cluster manager state:
Page 379
HACMP
# lssrc -ls clstrmgrES
Cluster manager states: ST_INIT: cluster configured and down
ST_NOT_CONFIGURED Node never started ST_JOINING: node joining the cluster
ST_INIT Node configured but down - not running ST_VOTING: Inter-node decision state for an event
ST_STABLE Node up and running ST_RP_RUNNING: cluster running recovery program
ST_RP_RUNNING ST_BARRIER: clstrmgr waiting at the barrier statement
ST_JOINING ST_CBARRIER: clstrmgr is exiting recovery program
ST_BARRIER ST_UNSTABLE: cluster unstable
ST_CBARRIER NOT_CONFIGURED: HA installed but not configured
ST_VOTING RP_FAILED: event script failed
ST_RP_FAILED Node with event error ST_STABLE: cluster services are running with managed resources (stable cluster) or cluster services have been "forced" down with resource groups potentially in the UNMANAGED state (HACMP 5.4 only)
How to show heartbeat information:
# lssrc -ls topsvcs
How to check logs related to hacmp:
# odmget HACMPlogs
How to list all information from topology HACMP:
# lssrc -lstopsvcs
How to show all info about group:
# lssrc -ls grpsvcs
How to list the logs:
# cllistlogs
How to list the resources defined for all resource group:
# clshowres
How to show resource information by resource group:
# clshowres -g'RG'
How to show resource information by node:
# clshowres -n'NODE'
How to locate the resource groups and display status (-s):
# clfindres
How to list interface name/interface device name/netmask associated with a specified ip label / ip address of a specific node:
# clgetif
Cluster verification utility:
# clverify
How to list cluster topology information:
# cllscf
X utility for cluster configuration:
# xclconfig
X utility for hacmp management:
# xhacmpm
X utility for cluster status:
# xclstat
How to force shutdown cluster immediately without releasing resources:
# clstop -f -N
How to do graceful shutdown immediately with no takeover:
# clstop -g -N
Page 380
HACMP
How to do graceful shutdown immediately with takeover:
# clstop -gr -N
How to sync the cluster topology:
# cldare -t
How to do the mock sync of topology:
# cldare -t -f
How to sync the cluster resources:
# cldare -r
How to do the mock sync of resources:
# cldare -r -f
How to list the name and security level of the cluster:
# cllsclstr
How to list the info about the cluster nodes:
# cllsnode
How to list info about node69:
# cllsnode -i node69
How to list the PVID of the shared hard disk for resource group dataRG:
# cllsdisk -g dataRG
How to list all cluster networks:
# cllsnw
How to list the details of network ether1:
# cllsnw -n ether1
How to show network ip/nonip interface information:
# cllsif
How to list the details of network adapter node1_service:
# cllsif -n node1_service
How to list the shared vgs which can be accessed by all nodes:
# cllsvg
How to list the shared vgs in resource group dbRG:
# cllsvg -g dbRG
How to list the shared lvs:
# cllslv
How to list the shared lvs in the resource group dbRG:
# cllslv -g dbRG
How to list the PVID of disks in the resource group appRG:
# cllsdisk -g appRG
How to list the shared file systems:
# cllsfs
How to list the shared file systems in the resource group sapRG:
# cllsfs -g sapRG
How to show info about all network modules:
# cllsnim
How to show info about ether network module:
# cllsnim -n ether
How to list the runtime parameters for the node node1:
# cllsparam -n node1
Page 381
HACMP
How to add a cluster definition with name dcm and id 3:
# claddclstr -i 3 -n dcm
How to create resource group sapRG with nodes n1,n2 in cascade:
# claddgrp -g sapRG -r cascading -n n1 n2
Creates an application server ser1 with startscript as /usr/start and stop script as /usr/stop:
# claddserv -s ser1 -b /usr/start -e /usr/stop
How to change cluster definitions name to dcmds and id to 2:
# clchclstr -i 2 -n dcmds
How to change the cluster security to enhanced:
# clchclstr -s enhanced
How to delete the resource group appRG and related resources:
# clrmgrp -g appRG
How to remove the node node69:
# clrmnode -n node69
How to remove the adapter named node69_svc:
# clrmnode -a node69_svc
How to remove all resources from resource group appRG:
# clrmres -g appRG
How to remove the application server app69:
# clrmserv app69
How to remove all applicaion servers:
# clrmserv ALL
How to list the nodes with active cluster manager processes from cluster manager on node node1clgetaddr node1 returns a pingable address from node node1:
# clgetactivenodes -n node1
How to list the info about resource group sapRG:
# clgetgrp -g sapRG
How to list the participating nodes in the resource group sapRG:
# clgetgrp -g sapRG -f nodes
How to get the ip label associated to the resource group:
# clgetip sapRG
How to list the network for ip 192.168.100.2, netmask 255.255.255.0:
# clgetnet 192.168.100.2 255.255.255.0
How to list the VG of LV nodelv:
# clgetvg -l nodelv
How to add node5 to the cluster:
# clnodename -a node5
How to change the cluster node name node5 to node3:
# clnodename -o node5 -n node3
Page 382
HACMP
links HACMP http://www.ibm.com/developerworks/aix/library/au-powerha/
How to start cluster daemons (options in that order: clstrmgr, clsmuxpd, broadcast message, clinfo, cllockd):
Page 383
HACMP
ST_INIT: cluster configured and down
ST_JOINING: node joining the cluster
ST_VOTING: Inter-node decision state for an event
ST_RP_RUNNING: cluster running recovery program
ST_BARRIER: clstrmgr waiting at the barrier statement
ST_CBARRIER: clstrmgr is exiting recovery program
ST_UNSTABLE: cluster unstable
NOT_CONFIGURED: HA installed but not configured
RP_FAILED: event script failed
ST_STABLE: cluster services are running with managed resources (stable cluster) or cluster services have been "forced" down with resource groups potentially in the UNMANAGED state (HACMP 5.4 only)
How to list interface name/interface device name/netmask associated with a specified ip label / ip address of a specific node:
Page 384
HACMP
Page 385
HACMP
How to list the nodes with active cluster manager processes from cluster manager on node node1clgetaddr node1 returns a pingable address from node node1:
Page 386
HACMP
http://www.ibm.com/developerworks/aix/library/au-powerha/
Page 387
HACMP
ST_STABLE: cluster services are running with managed resources (stable cluster) or cluster services have been "forced" down with resource groups potentially in the UNMANAGED state (HACMP 5.4 only)
Page 388
Parametros de fibra AIX
Parametros de fibra AIX
fcstat -D fcs0 | grep DMA 0 max_xfer_size 0x200000,
fcstat -D fcs0 | grep -i "High water mark" 55 num_cmd_elems 1024
Page 389
DESCRIPCION
11.23 obsoletos
11.31 actualizado
3 DIAS HABILES
passwd
PERMISOS DE UN USUARIO
forsar el desmonte de un filesystem
DESATACHAR UN MIRROR
LUN (todo debe tener label)
TIPS
Parchar solaris 9 y 10 tener disponible en el filesystem donde se empaqueta 3.6 gb
revisar la version de un paquete
reiniciar una maquina HPUX
Backup de sistema operativo
servidores
manejo consola sc
Validar semaforos
Parametros de kernel usuario
SOPORTE SUN
Agregar el default Gateway a un servidor
ENLACES SIMBOLICOS
AWK
Tarea programada
Bsqueda por nombre
listara todos aquellos ficheros que empiezen por in que su tercer caracter sea una letra que este entre la a y la z
ip en HPUX
vlan en hpux
Muestra Diferencias entre archivos
ver tamao de un filesystem
posicionarse en el directorio y se ve en kilobites el archivo mas grande
Evalua el 3 valor del parrafo mayor o igual a 500 y que muestre los parametros que se encuentran en $1 $2 $3 (usuario comentario y shell) PERO LOS ORDENA CON SORT
EXTRAYENDO VALORES CON UNA POSICION DESCONOCIDA asi que usaremos otra tcnica basada en el nmero total de campos encontrados.
Elimina todos lo elementos de una carpeta
Muestra todos los elementos que empiezan por lis
Se listaran todos los directorios y archivos que empiezen por l y que tenga cualquier otro caracter, por ejemplo li, la ..
Banner en un servidor
USUARIOS EN SAMBA
sacar usuarios del servidor
direccionamientos estaticos
Evalua el 3 valor del parrafo mayor o igual a 500 y que muestre los parametros que se encuentran en $1 $2 $3 (usuario comentario y shell)
Parchar solaris 9 y 10 tener disponible en el filesystem donde se empaqueta 3.6 gb
Ver ILO de un Servidor
Servicios en solaris 10Servicios en solaris 10Servicios en solaris 10Servicios en solaris 10Servicios en solaris 10
comando CUT
skill
slice de los discos discos
Nombres de instancia
DEBIAN
Crear un archivo con la fecha
Prioridad de procesos
Busca los ficheros ms recientes que el fichero (tal.txt)
Busca los ficheros con extension .sh y los elimina recursivamente
puertos en un servidor
busca archivos por nombre
cuenta los archivos por nombre
tipo de archivos de un disco
|
Bsqueda de directorios, ficheros, sockets o enlaces exclusivamente
Bsqueda por tamao
Bsquedas por ltimas modificaciones, accesos o cambio de permisos
Busca los archivos que poseen permisos 777
DESCOMPRIMIR ARCHIVOS
UNIQ
COMANDO SED
VER SERIAL DE UNA MAQUINA WINDOWS XP Y SERVER
UMASK
ubicacin de los syslog
Correr o compilar un archivo (./configure ) (make) (make install)
revisa los programas que se estan ejecutando y que llave estan usando
COMANDO TR
ubica y lista la localizacion del kernel
Limite de parametros del sistema
Borrar el contenido de un archivo sin eliminarlo
OTORGARLE DISCO A UNA ZONA
Archivo de configuracion de los niveles de inicio
permisos por defecto del archivo passwd
Ver los permisos de un archivo desde VI
busca los texto donde el segundo carcter es a y el quinto tambien, y el tercero no es b
asignar el default a una zona desde el papa ejemplo backcat
INSTALACION DE EXPLORER
xdm-config
Xresources
Xsession
gnome
FC
errores en disco en solaris
Desventajas de usar el comando kill -9
CPIO
Recrear un filesystem de mas de 1 Tera byte
donde se guardan los cron con el comando crontab -e
monta la unidad de CD
Ver ultimos usuarios conectados
matar muchos procesos zombies
Buscar procesos ZOMBIE
Tarjeta de sonido
marca del hardware
El comando startx es un script que ejecuta el proceso xinit
XWINDOW
/var/log
Cuando un usuario arranca X con el comando startx se ejecuta el script .
ver el archivo mas grande de un filesystem
ingresar a proxy-cca por el puerto 22222
diferencias entre LILO y GRUB
.so (libcrypt.so) refiere a shared object (objeto compartido)
La configuracin de una nueva librera se guarda en el fichero /etc/ld.so.conf
Cuando el fichero de configuracin se cambia, el fichero cach debe de ser actualizado, esto se hace con el comando ldconfig. Y genera el archivo /etc/ld.so.cache
salir de la consola de ldm
salir de la consola de SC
SUID
SGID
rutas persistentes
agregar rutas persistentes
Falla servidor crmbpm03
REVISAR SI LOS USUARIOS ESTAN BLOQUEADOS O CON VENCIEMIENTO
ELIMINAR EL VENCIMIENTO DE UN USUARIO
AGREGAR DISCOS CON VERITAS
ENVIAR CORREO DESDE EL SERVIDOR CON ADJUNTO
enlace simbolico ln -s /TELE/npr /TELIVR/Planos/
listar archivos abiertos y eliminados que quedan con un proceso pegado
agregar una ruta en solaris 10
agregar usuarios cron en hpux
ver cores de un servidor
configurar las direcciones ips en la interfaz con red hat
apachectl stop y start
Este comando devuelve una lista de todos los programas en ejecucin que estn usando TCP wrappers para el control de acceso a mquinas. Por lo tanto, cualquier programa listado debe ser detenido y relanzado si el paquete tcp_wrappers es actualizado.
ver porcentajes de memoria, cpu, usuarios
USUARIO EJECUTE SOLO UN PROGRAMA
RECONOCER LUN EN LINUX
Crear un usuario que solo pueda instalar (nada mas)
cambiar zona horaria en caliente
enlace simbolico
Forzar el cambio de contrasea
crear un usuario en aix
crear un archivo vacio de un tamao determinado tamao
reiniciar servicios en AIX
codigo fuente del kernel
configuracion correo en maquinas linux
ver si un proceso esta corriendo
modificar la hora en unix
VER LA VERSION DE SAMBA
Instalacion de solaris 10
Cambiar el boteo de un disco de el disco 0 al disco 1 (cuando uno de los dos este daado) desde SC
Cambiar desde el sistema operativo
conectarse a un dominio M5000
Crear Vlan en solaris
configurar Vlan en solaris
suscripcion en red hat network
buscar una linea con vi
Ingresar a un dominio de una M5000
denegar el ping que hacen a tu maquina linux
dejarlo como antes
Actualizar firmware en solaris (T2000)
shutdown
herramienta para ver remotamente la informacion del sistema de un servidor
Esta linea indica donde se encuentra el interprete de comandos en nuestro sistema
pagina por defecto para CUPS
eliminar proceso desde consola en windows
ver semaforos en unix
estado de servicios en RED HAT 4
habilitar servicio telnet en red hat 4
ver cuantos sockets tiene un servidor linux
cuantos nucleos tiene un servidor linux
cuando netstat -a demora o no aparece nada
Prevenir que un usuarios e loguee en una maquina
mensajes a todos los usuarios logueados
proceso de la shell
shell de un usuario FTP
shell de un usuario SFTP
eliminar el default gateway en linux
saber si hay un CDROM en el servidor
cambiar opcion de reinicio de true por false para que un ldm cuando se reinicie quede en el OK
agregar cdrom desde gloabal a ldm
Agregar vlan a un ldm desde la global
Ver el estado de las interfacez de red
meter maquinas al dominio y cambiar maquinas de una OU a otra (se debe agregar el grupo al usuario)
montar esta ruta en el archivo /parches
librera que no debe estar en solaris
utilidad limpiar el FMA. Todo esto con la finalidad de que se reseteen los indicadores de fallas y al conectarlo nuevamente indiquen el status actualizado
reconocer hbas o manejadores de backup en solaris
resetea todo desde el OK (lo mas recomendable cuando se agrega un dispositivo scsi o fibra a un servidor
Es un paquete que viene con el cluster que permite vi web administrar los nodos del cluster.
Muestra las diferencias interactivas en consola entre dos archivos
ERRROR AL FORZAR LA CONTRASEA CON EL COMANDO PASSWD -F USUARIO
eliminar los archivos generados por YUM en la ruta /var/cache/yum/rhel-x86_64-server-5
Cambiar hostname en solaris (hay que modificar 5 archivos )
Subir maquina crmbpm03
arrancar como un live cd
darle fsck al disco 0
Cluster tambien se denomina a un conjunto o determinados paquetes que actan en conjunto para determinado fin, Ejemplo los niveles de instalacin de solaris se dividen en varios cluster segn la seleccin de paquetes.
Borra los archivos temporales
Archivos sospechosos del sistema
verifica los datos y estado del RAID
reiniciar el servicio de snmp en HPUX
Cuantas vlan pueden ser creadas en una sola interfaz ????? 512 ce
Agregar rutas en Linux
montar un .iso en linux
Listar desde consola los SERVICIOS de un equipo o servidor
Sacar los procesadores fisicos de un servidor HPUX
Ver el cron de un usuario
Cambiar password para un usuario que usa samba
Descomprimir un cpio
Cuando no se pueda generar graficas teniendo la variable exportada y este maquina detrs de un firewall
ps en version BSD consumo de cpu y memoria
ACTIVIDADES REPLICA RFC
Dejar inmutable el archivo /etc/passwd y /etc/shaodw (el usuario root no puede modificar el archivo)
Muestra que esta haciendo un comando
promt shell
secuencia de comandos cuando llegue la seal "trap"
Habilitar las interfacez cuando no las muestre el comando ifconfig -a
Desde el servidor backcat se ejecuta este comando el cual agrega el default router al servidor etbftp (zona) el cual maneja la interfaz ce43002
SABER EL NUMERO DE CORE DE UN SERVIDOR HPUX
Borrar las primeras 1000 lineas de un archivo en VI
Que funcion tiene el archivo dead.letter
Resetear la system controller (NO APAGA EL HOSTNAME )
Ver que usuarios estan en un filesystem
Agregar un disco de una global a un LDM
pasos mas detallados en http://download.oracle.com/docs/cd/E22305_01/html/821-2931/virtualdiskbackend.html
Detener el servicio de telnet ftp en un servidor solaris 9
Cambiar nombre de un servidor SUSE 11
Cuando no toma las direcciones ip del dns hay que revisar que se tenga el nameserver adecuado y primero ya que si hay otro arriba tomar el que est de primeras.
enumeren todas las unidades en el rbol de dispositivos, incluidas las unidades que no estn configuradas.
Desconfigurar el disco para extraerlo
Led azul
Revisa todo el trafico que esta ingresando o saliendo a un ip de mi servidor
Reiniciar el servicio veritas cuando no abre
configurar dos tarjetas de red, para que se conviertan en activas o una pasiva y otra activa (se suman las velocidades de las dos tarjetas (activas) , lo anterior con el fin de lograr alta disponibilidad cada una se conecta a un switch "si se daa una tarjeta la otra que activa"
Borrar archivos de una carpeta de hace un mes
permitir a un usuario utilizar una verison de JAVA diferente a la del sistema
Muchos sistemas tienen varias versiones de JAVA
LOG DONDE AVISA QUE LA REPLICA DE CPAFACREV FILNALIZO
La swap es un espacio reservado en tu disco duro para poder usarse como una extension de memoria virtual de tu sistema
Ver caracteristicas de maquinas HPUX
Crear un demonio que suba con el runlevel 5
Eliminar archivos que tiene fecha de mayo o junio la $9 es la fila 9
Ver si una maquina suse esta suscrita o no??
INSTALAR POSTFIX EN SOLARIS 10
Howto install:
This package is to replace Sendmail on Solaris, so you have to uninstall first Sendmail:
# svcadm disable sendmail
# pkgrm SUNWsndmu
# pkgrm SUNWsndmr
Uncompress the file with bunzip2 and then install the package with pkgadd:
# bunzip2 CNDpostfix-2.4.6,REV=080102-SunOS5.10-sparc.pkg.bz2
# pkgadd -d CNDpostfix-2.4.6,REV=080102-SunOS5.10-sparc.pkg CNDpostfix
Now you can change /etc/postfix/main.cf according to your needs and start Postfix with:
# svcadm enable svc:/network/postfix:default
Sacar un cd o dvd de un solaris
ARCHIVO DONDE SE MODIFICA LOS LOCALES
Limites
semaforos
Instalar perl ksh en servidor linux viejos cuando no este el ksh lo anterior para ejecutar *.ksh
ciclo donde se guardan los datos en un archivo
Busca los usuarios que se encuentran en el archivo users.txt
guarda la variable y la compara con el passwd mostrando el item 4 el cual es el grupo y los imprime a /tmp/ultimo.txt
extraer un grupo apartir de un usuario se realiza con el paso anterior obviamente no sin antes relacionar los usuarios en un archivo
No olvidadar que para hacer la busqueda a los group id se deben poner :gid: para que la busqueda de resultado
WWPN EN LINUX
Expiracion
Saber I/O en solaris
Procesos que mas consumen
Montar un .iso en linux
Crecer un FS en Linux
Fallas en NFS
Intentos fallidos ver
Intentos fallidos borrar
PASOS
Ver espacio en disco filesystem
while true^Jdo^Jdate^Jlssrc -ls clstrmgrES|grep state^Jecho ------------------^Jsleep 5^Jdone
revisar memoria
CPU Utilization interacciones
acceder a la maquina cuando las dos sesiones estan ocupadas
APROVISIONAMIENTO DE SERVIDORES
subir con el usuario oramon
ver estado discos duros
Usuario nunca vence el passwd
revisar el estado del usuario "bloqueado"
incluir la direccin ip del servidor grid11g en el archivo /etc/hosts del servidor ideadb.
buscar un usuario en /ETC/PASSWD
revisar todos los procesos
puertos utilizados
PERMISOS
se ve los programas que se estan ejecutando
cuenta cuantos programas se estan ejecutando
modificar el home del usuario oramon en el servidor .. para que apunto al filesystem /AgenteOracle.
ingresar como root
ver RPMS gcc instalados
ver RPMS cc instalados
revision del sistema operativo
Nuevo Controlador
Serial de servidor
Bloquear su
Cuantos Discos tiene el serviodr
ver lo mirror
RAID
PAGINA DE NAGIOS
serial del servidor
Hba
Ver (modelo, cpu, memoria
Ver cuantos procesadores tiene
ubicacin visudo
Estado de la memoria fisica
Estado de la memoria swap
PERMISOS DE UN USUARIO
forsar el desmonte de un filesystem
creacion de grupos
ingresar un usuario existente a un grupo existente
muestra que es d1 y la composiciion
muestra los discos
/usr/local/sbin/visudo comando
ver maquinas hijas en un servidor (virtuales)
guardar configuracion del ldm que se tiene en el momento
iniciar una maquina virtual
Lista las configuraciones LDM que se han guardado
modificar path de las aplicaciones
aplicacin top
viose
instalar sin que pida ruta de instalacion
No encuentra las aplicaciones
banner
ultimos logueos en el servidor
Cuando (fecha)modificaron un archivo
abajo (vi)
Reconocer lun con (cuando se ingresa un nuevo DISCO)
actualiza los nuevos discos presentados (powermt config)
Muestra los disco y sus LUN
ingresa al disco directamente se busca en las opciones presentadas
lista el estado actual de la base de datos de los metadevice en uso
se inicializa 1 metadevice de 4 disco (concat strip)
pequeas LUN de un LUN grande (se inicializa 1 metadevice de otro disco (soft partition))
formato
monta el device en el filesystem
destachar un mirror
http://docs.oracle.com/cd/E26921_01/html/E25879/devconfig2-8.html#devconfig2-11 DESATACHAR UN DISPOSITIVO DE FIBRA O DISCO
device
[LUN 87]
rol device
borrar el metadevice creado (d55) forzado
parchar solaris 9 y 10 (fisicamente el cd ) crmems01
Ver si se tiene mirror los filesystem del O.S /usr /opt / /var /
se detach los mirror (primero los padre y luego los hijos (solo un segmento))
1. ingreso a la carpeta /mnt/sun/install/ actualiza las tools mas importantes del sistema
2. Se ejecuta el comando para actualizar el /etc/profile
2. Ingreso a la carpeta /mnt/sun/patch/10 actualiza los parches
3. Se genera el explorer(genera la foto de toda la configuracion actual)
4. single user (pasamos la maquina a single user sacamos a todo el mundo (ssh))
5. Ingresamos a la ILO (en caso de que tenga LDM ingresamos desde el papa(tibco1) as)
6. Se ejecuta en la carpeta donde se desempaqueto los parches
7. Finaliza el parchado
apagar LDM
dejar inactivas las ldm
Cuando se da init s (muchas veces pasa al ok entonces se debe ejecutar el comando)
ver el estado del servicio o demonio
parar el servicio de ftp
activa nuevamente el servicio de ftp
Cuando este en mantenimiento el servicio
revisar la version de un paquete
ubicacin de la aplicacin
ufsdump 0cf /mnt1/sep20globalcon2010/root.dmp (espacio) /
carpeta sysadmin que se monta en los serviodores
agregar el banner con el nombre en el profile
copiar en el vi /etc/issue - vi /etc/motd de otro servidor (politicas de )
Ir a /etc/ssh/sshd_config - (/Banner quitar el comentario ) - Root poner (NO) y reiniciar el servicio de ssh svcadm restart ssh
CONFIGURACION SAMBA (USUARIOS)
ASIGNAR CONTRASEA AL USUARIO QUE SE AGREG EN EL SMB.CONF
console
/etc/system/ (/ semm)
/etc/project
numero de telefono 6517954 (solicitan el serial de la maquina) (solicitaran los explorer para subirlos a una pagina)
route add default 10.113.4.1
la carpeta prueba1 que se encuentra en /tmp apunta a /export/home/admgt07/enlaca1
Ubicacin para autorizar acceso por NFS
Muestra los parametros nombre y comentario separados por de /etc/passwd
Es lo mismo de arriba pero poniendo un titulo de cada uno de los componentes
Se listar?n todos los archivos que tengan la primera letra una a la segunda debe ser A,B o C y despus cualquier cadena de caracteres.
minutos (0 - 59) hora (0 - 23) da del mes (1 - 31) mes (1 - 12) da de la semana (0 - 6, el domingo es 0) comando a ejecutar
Bsqueda por nombre
listara todos aquellos ficheros que empiezen por in que su tercer caracter sea una letra que este entre la a y la z
ip en HPUX
vlan en hpux
Muestra Diferencias entre archivos
ver tamao de un filesystem
posicionarse en el directorio y se ve en kilobites el archivo mas grande
Evalua el 3 valor del parrafo mayor o igual a 500 y que muestre los parametros que se encuentran en $1 $2 $3 (usuario comentario y shell) PERO LOS ORDENA CON SORT
Lo mismo pero mucho mas ordenado con printf
EXTRAYENDO VALORES CON UNA POSICION DESCONOCIDA asi que usaremos otra tcnica basada en el nmero total de campos encontrados.
Elimina todos lo elementos de una carpeta
Muestra todos los elementos que empiezan por lis
Se listaran todos los directorios y archivos que empiezen por l y que tenga cualquier otro caracter, por ejemplo li, la ..
direccionamientos estaticos
EXTRAYENDO VALORES CON UNA POSICION CONOCIDA
Evalua el 3 valor del parrafo mayor o igual a 500 y que muestre los parametros que se encuentran en $1 $2 $3 (usuario comentario y shell)
Ver ILO de un Servidor
caracteres (-c)
delimitadores (-d)
delimitadores (-d)
congelar procesos
logueos en el servidor
slice 0
slice 1
slice 2
slice 6
slice 5
muestra los dispositivos que tienen el driver cargado
Todos los drivers que el sistema reconoce
es un nombre de dispositivo abreviado que es creado por el propio kernel. Un ejemplo del uso de los nombres de instancia lo encontramos en la ejecucin del comando ifconfig a donde podemos ver en negrita el nombre de la instancia que corresponde con la interfaz de red
Instalar un dispositivo parando el sistema
Instalar un dispositivo sin parar el sistema
breve descripcion del comando sudo
breve descripcion del comando que contenga la palabra sudo
VALIDAR SI EL SERVICIO DE KERBEROS ESTA FUNCIONANDO CORRECTAMENTE
quitarle la shell a un usuario
bloquear un usuario
paquete_version_build_arquitectura
instala un paquete
desinstala un paquete
muestra paquetes instalados en todo el sistema
muestra todos los paquetes instalados por dpkg
version del dpkg
elimina todo hasta el registro de los archivos
buscar el dpkg
estado del paquete
Buscar los errores de dependencia
se defina la variable fecha (fecha=`date +%Y%d%m`)
El punto siginifica que en esa posicion puede ir cualquier caracter
Busca los ficheros ms recientes que el fichero (tal.txt)
Busca los ficheros con extension .sh y los elimina recursivamente
puertos en un servidor
busca archivos por nombre
cuenta los archivos por nombre
tipo de archivos de un disco
|
Bsqueda de directorios, ficheros, sockets o enlaces exclusivamente
Bsqueda por tamao
Bsquedas por ltimas modificaciones, accesos o cambio de permisos
Busca los archivos que poseen permisos 777
REMUEVE CUALQUIER LINEA DUPLICADA
Convierte los tabs de entrada en espacios. Use la opcion -t para especificar el tabstop.
Convierte los espacios de entrada en tabs. Use la opcion -t para especificar el tabstop.
pr es usado para romper archivos en paginas multiples de la salida; tpicamente usado para imprenta.
Permitir a un servidor hacerle ping a una maquina que se encuentre en el dominio
borrar una lnea
intervalo de lineas a borrar
borrar desde una determinada lnea en adelante
Borrar las lineas en blanco
eliminar los comentarios que comienzan normalmente con #
pasa a mayusculas todas las letras 'a'
Imprime las lneas que comienzan con d y e minsculas
ldd prints the shared libraries required by each program or shared library specified on the command line.
Los bits SUID, SGID y sticky
umask = 022 carpeta = 777 archivo = 666
ubicacin de los syslog
se debe agregar en el /etc/profile
revisa los programas que se estan ejecutando y que llave estan usando
reviso el estado y que fs tiene el etbftp desde backcat
Ingreso a la zona etbftp
opcion agregar Filesystem
agregamos el filesystem /almagran
agregamos de donde traemos el espacio
agregamos de donde traemos el espacio
tipo de archivos
finaliza
verifica si todo esta bien (si no, volvemos a add fs)
compila toda la informacion en el XML
estando en backcat vamos a
montamos el disco /dev/dsk/c2t3d0s5 en /zonas/etbftp/root/ALMAGRAN
Revisamos en etbftp si quedo correctamente
Ubicacin donde se guardan los paquetes descargados por apt
sustituir un carcter por otro
Borraremos las letras'a' y'e' de la palabra'murcielago'
Eliminaremos todos los espacios en blanco que tengamos repetidos en una frase
cuya especialidad es la de eliminar carcteres repetidos. Vemosla en accin.
nos permite eliminar los carcteres repetidos y a la vez sustituirlos por otro carcter.
El comandotrha substituido por un guin cualquier carcter que no fuera un nmero. Pues eso ha hecho, elsalto de lnea aunque invisible tambin es tenido en cuenta como un carcter
ubica y lista la localizacion del kernel
Limite de parametros del sistema
Borrar el contenido de un archivo sin eliminarlo
startup level
permisos por defecto del archivo passwd
BORRAR EL CONTENIDO DE UN ARCHIVO
Ver los permisos de un archivo desde VI
asignar el default a una zona desde el papa ejemplo backcat
1. Ir a /sysadmin/henrespr/INSTALACION\ MANUAL\ DE\ EXPLORER/
2. pkgadd -d Explorer (la carpeta que se descomprimi)
3. Correr /opt/SUNWexplo/bin/explorer -g (para que realice la primer configuracion por defecto)
4. Ejecuto explorer
xdm. El que viene por defecto con el sistema X. Se configura editando los ficheros que estn en/etc/X11/xdm
Xaccess. Controla los accesos a las sesiones locales.
Xresources. Son configuraciones de color para la pantalla de login.
Xservers. Asocia displays con procesos locales o remotos.
Xsession. Se ejecuta al iniciar sesin, controla el administrador de ventanas)
Xsetup_0. Valores iniciales de login para el servidor 0. Color (xsetroot) y reloj
xdm-config. Fichero principal de configuracin del xdm.
puntos que necesitan los scripts y los archivos de configuracion
contiene opciones para la pantalla de logueo
identifica el escritorio apropiado
opciones de gnome
FC
si aparecen 0's (ceros), no posee errores
Desventajas de usar el comando kill -9
recopila los archivos
Se necesita crecer un filesystem de 1T a 1.3T (OJO DEBE HABER SIDO CREADO CON LA OPCION -T EN EL newfs)
1. Almacenamiento suministra la lun de 300 GB
2. se reconoce la lun en el sistema operativo
3. se da label al disco
4. No es necesario darle newfs a este ya que al que se quiere unir ya lo tiene(omitir)
5. metattach d60 (device al que se quiere unir) /dev/dsk/c0t0(device que quiere unirse a d60)
6. growfs -M /sgs /dev/md/rdsk/d60 (la opcion -M es cuando el filesystem esta montado osea se hace la operacin en caliente)
ok
1. es el log generado por syslog, de tipo general
2. log dado por las funcionalidades del kernel
3. # el log donde esta todo el arranque del equipo
4. log donde registra todo lo que se hace con el comando sudo
5. log de seguridad
ps -fea |grep defunct| awk '{print "kill -9", $3}'|sh
du -hk | sort -nr | less
Cuando el fichero de configuracin se cambia, el fichero cach debe de ser actualizado, esto se hace con el comando ldconfig. Y genera el archivo /etc/ld.so.cache
~. ldm
#. sc
si un programa ejecutable tiene el bit suid, se ejecutar en nombre del titular del ejecutable, y no en nombre de la persona que inici el programa
si un programa ejecutable tiene el bit suid, se ejecutar en nombre del GRUPO titular del ejecutable, y no en nombre de EL GRUPO que inici el programa
Solaris
route add net 10.113.1.158 (host) 10.112.1.1 (gateway) 255.255.255.255 (mask)
lsof /usr/lib/libwrap.so*
MODIFICAR EL VISUDO
se muestra las variables de la shell SC
se cambia la variable con este comando (boot_device) es el elemento que se quiere cambiar
se cambia otra variable
Tener el archivo default router, netmask
Se crea el archivo hostname.ce2011 con la direccion ip de la vlan
Se modifica el archivo netmask con las direcciones de las vlan y sus respectivas mascaras
crear usuarios con variables globales
se ingresa a la XSCF> al dominio 0
ver si el servidor se encuentra en cluster
1. Se descomprime el archivo .zip (139434-08.zip)
2. Se ejecuta el .bin con el siguiente comando (para descargar el paquete a la System Controller)
3. Cuando se termine el anterior proceso
4. Se ingresa a la direccin de la System Controller y se ejecuta (para ver la version de la system controller)
5. se ejecuta (para ver la version de la OBP y el firmware )
6 . Se paga la maquina desde la SYStem controller
7. Se ejecuta (para ver el estado) (si esta normal proceder)
8. Se ejecuta (no hay que expecificar el paquete, ya que se descarg anteriormente con el comando sysfwdownload)
9. Se reinica la system controller
10. Se revisa el release
11. Se revisa el release de la system controller
(menos)c
(menos)f
(menos)F
(menos)h
utilidad limpiar el FMA. Todo esto con la finalidad de que se reseteen los indicadores de fallas y al conectarlo nuevamente indiquen el status actualizado
ERROR AVAIBLE LIBRARY
Cluster tambien se denomina a un conjunto o determinados paquetes que actan en conjunto para determinado fin, Ejemplo los niveles de instalacin de solaris se dividen en varios cluster segn la seleccin de paquetes.
Nombre del promt shell
No se puede agregar directamente en el servidor hay que hacerlo desde la global (ce43002:1 es la interfaz que se crea para la zona) se deben configurar igual en la global las dos ce0 y ce0:1
:1,2000d
Cuando un mail no puede enviarse, el archivo se copiar en un archivo de su directorio de usuario llamado dead.letter. (ver el archivo para ver que fallas tiene el envio)
se crea un id para el disco que reconosco previamente en este caso vol_c2t5006016010601FC1d25s2@primary-vds2
se agrega al servidor ssbdsun3 el disco virtual al vds2 quien es el que guarda la configuracion del disco para este servidor
se crea el device y se da newfs con esto se monta en el filesystem que queramos
se ingresa al /etc/inetd.conf y se comentarea la linea telnet o ftp tambien se comentarea en /etc/services
Cuando no toma las direcciones ip del dns hay que revisar que se tenga el nameserver adecuado y primero ya que si hay otro arriba tomar el que est de primeras.
mi ip 192.16.11.24 la ip la cual deseo saber si accede a mi maquuina y como 172.18.22.30
ALTA DISPONIBILIDAD EN TARJETAS DE RED
La swap es un espacio reservado en tu disco duro para poder usarse como una extension de memoria virtual de tu sistema
ls -lrt|grep May|awk '{print "rm -r ",$9}'|sh
se ejecuta share para ver si est compartiendo el recurso
si muestra algo se ejecuta unshare /cdrom/eis-dvd
eject y listo
hard
soft
guarda la variable y la compara con el passwd mostrando el item 4 el cual es el grupo y los imprime a /tmp/ultimo.txt
extraer un grupo apartir de un usuario se realiza con el paso anterior obviamente no sin antes relacionar los usuarios en un archivo
ver consumo de cpu
MEMORIA LIBRE, MEDIDA EN MB
SOLARIS 10
df -h (gigas) -k s (kilobytes) du -hs
top
top -d 6
grep luis /etc/passwd
more /etc/group
chown oramonoinstall /AgenteOracle
queda con todos los permisos
umount -f /dev/tatat/
Campos obligatorios (hardware red sistema operativo)
iostat
passwd -x -1 usuario
raidctl l
/usr/sbin/sneep
fcinfo hba-port -l
prtdiag -v
psrinfo
/usr/local/sbin/visudo
mpstat
swap -l (vmstat)
908528k = 1026mb
groupadd -g 700 admetbsr groupadd -g 800 admbck
- groupadd -g 900 admsrv
/usr/bin/gpasswd -a henry pruebita
swap -l (vmstat)
metastat y dispositivo (d1)
format
vi /usr/local/etc/sudoers
ldm list
ldm add-config <nombre de la configuracion>
ldom crmgate4 start
ldm list-config
vi /etc/profile
/usr/local/bin/top
ps -fea | grep console ---- kill -9 ID
pkgadd -d
PATH=$PATH/usr/local/bin/usr/local/sbin/opt/OV/bin/OpC/opt/OV/bin/usr/jdk
/etc/issue - /etc/motd
last|grep admg07
ls -lrtu scstart
$
powermt
powermt config o (devfsadm -v)(cfgadm -c configure c1 c2 c3 c4) (reconfigura todas las controladoras a nivel de sistema operativo)
powermt display dev=all | more
format c2t5006016141E0C680d0 u opcion .. ( Diferencia al ingresar directamente al disco no pide label)
metastat p /dev/md/dsk/
metainit d30 4 1 /dev/dsk/c2t5006016141E0C680d0s2 (cuidado con el espacio)1 OTRO DISCO
metainit d31 -p d30 5g (soft partition)
newfs /dev/md/rdsk/d31
mount /dev/md/dsk/d31 /SGS2
metadetach d0 d20 ( del d0 destachar el disco d20)
http://docs.oracle.com/cd/E26921_01/html/E25879/devconfig2-8.html#devconfig2-11 DESATACHAR UN DISPOSITIVO DE FIBRA O DISCO
/dev/md/dsk/
Cuando no aparezca [LUN 79] con el comando powermt display dev=all | more darle powermt config
/dev/md/rdsk/
metaclear -f d55
mount 10.111.8.199/cdrom/sol_10_1008_sparc /mnt
metastat -p | m (d0, d1, d2 (padres)) (d10, d20, d30 (hijos))
metadetach d0 d10
setup estndar.sh
. /.profile
unpack-patches /en la ruta que este disponible espacio /var
comando explorer (guarda toda la configuracion en /opt/SUNWexplo/output/)
init s (SOLO PARA INSTALAR LOS PARCHES)
telnet localhost 5000 Nombre del hijo(tib_pru01 tib_pru02) (lo anterior desde el papa)
./ install_all_pachtes
reboot
ldm stop crmsoa02
ldm unbind crmsoa02 "queda inactive"
boot -sw
mount -F
cd /usr/platform/`uname -i`/sbin {} ./scadm shownetwork ver ilo del servidor
svcs ftp
svcadm disable /network/ftp
svcadm enable /network/ftp
svcadm clear /network/ftp
pkginfo - l grep vx / pkinfo -l paquete
which whereis su
\\sa01\fs15\sysadmin
echo banner `hostname` >> /etc/profile (banner `hostname`)
Ir a /etc/ssh/sshd_config - (/Banner quitar el comentario ) - Root poner (NO) y reiniciar el servicio de ssh svcadm restart ssh
/etc/sfw/smb.conf
/usr/sfw/bin/smbpasswd -a Usuario
netstat -nr
ln -s /export/home/admgt07/enlaca1 /tmp/prueba1
/etc/dfs/dfstab
awk '{print $1, $5}' FS="" /etc/passwd
awk '$3 >= 500 {print $1 $5 $7 }' FS="" /etc/passwd
awk '$3 >= 500 {print $1 ,$5, $7| "sort" }' FS="" /etc/passwd
awk 'BEGIN { print "Usuario UID Shell\n------- --- -----" } $3 >= 500 { print $1, $3, $7 | "sort -r"}' FS="" /etc/passwd
awk 'BEGIN { print "Usuario UID Shell\n------------ ---- ----------" } $3 >= 500 \
{ printf "%12s %4d %10s\n", $1, $3, $7 | "sort -r"}' FS="" /etc/passwd
ls | xargs rm -fr
ls -la lis*
ls -la l?
ls -la a[ABC]*
ls -la in[a-z]*
crontab -e
diff archivo1 archivo2
du -hs*
du -k *
find . -name "*.jpg"
EXTRAYENDO VALORES CON UNA POSICION DESCONOCIDA asi que usaremos otra tcnica basada en el nmero total de campos encontrados.
EXTRAYENDO VALORES CON UNA POSICION CONOCIDA
find . -user torpedo
find . -type d (d, f, s l )
find . -size +200M
find . -mtime 1 (-atime cuando se accedi al fichero por ltima vez.)(-ctime cuando fueron cambiados los permisos del fichero por ltima vez. )(-mtime cuando fue cambiado el contenido del fichero por ltima vez.)
find . -perm 777
find . -newer "antiguo.txt"
find . -name "*.sh" -print0 | xargs -0 rm
echo "Esto es una prueba, 1 2 3, probando" | cut -c 1-4 muestra (Esto)
echo "Esto es una prueba, 1 2 3, probando" | cut -d " " -f 1 muestra (Esto es una prueba) y -f se refiere al primer campo
echo "Esto es una prueba, 1 2 3, probando" | cut -d "," -f 2 muestra (123) y -f2 se refiere al segundo campo
netstat -na
last
/
swap
disco entero
/usr
/opt
locate sudo
locate -c sudo
prtconf | grep -v not
/etc/path_to_inst
es un nombre de dispositivo abreviado que es creado por el propio kernel. Un ejemplo del uso de los nombres de instancia lo encontramos en la ejecucin del comando ifconfig a donde podemos ver en negrita el nombre de la instancia que corresponde con la interfaz de red
whatis sudo (man -f sudo)
apropos sudo (man -k sudo)
fstype /dev/dsk/c0t0d0s2
usermod -s /usr/bin/false noaccess
passwd -l noaccess
touch henry$fecha.txt (henry20100810.txt)
grep pegasus.x /etc/passwd muestra (pegasusx6665tog-pegasus OpenPegasus WBEM/CIM services/var/lib/Pegasus/sbin/nologin)
Ingresarlo al servidor DNS
vi /etc/resolv.conf
vi /etc/nsswitch.conf debe quedar la linea host igual al comentario
>usu
sed 'n_de_lnead' fichero sed '1d' fichero (elimina la primera linea)
sed '3,5d' fichero
sed '3,$d' fichero
sed '/^$/d' fichero
sed -e '/^#/d' /etc/services | less
sed 's/a/A/g' fichero
sed -n -e '/^[de]/p' texto1 (ver comentario)
ldd
/etc/syslog.conf
/usr/ccs/bin/usr/sfw/bin
zonecfg -z etbftp info
zonecfg -z etbftp
1. add fs
2. set=dir/almagran
3. set especial=/dev/dsk/c2t3d0s5
4. set raw=/dev/rdsk/c2t3d0s5
5. set type=ufs
6. end
7. verify
8. commit
9. /zonas/etbftp/root/
10. mount /dev/dsk/c2t3d0s5 /zonas/etbftp/root/ALMAGRAN
11. df -h
1. [echo murcielago | tr aeiou AEIOU (mUrcIElAgO)] [echo murcielago | tr aeiou AE (mErcEElAgE)]
2. echo murcielago | tr -d ae (murcilgo)
3. echo 'una frase muy tonta pero valdr' | tr -d ' ' (unafrasemuytontaperovaldr)
4. echo 'una frase muy tonta pero valdr' | tr -s ' ' (una frase muy tonta pero valdr)
5. echo 'una frase muy tonta pero valdr' | tr -s ' ' . (una.frase.muy.tonta.pero.valdr)
6. echo 'naci el 13-12-1966' | tr -c '0123456789' '-' (--------13-12-1966-)
lilo -q
/etc/inittab
/etc/passwd 644
cat /dev/null > un_archivo.txt
!ls -l file
grep .a[^b].a myfile
route add default 192.168.11.4 -ifp ce430021
iostat -En
LUN 26
powermt devfsadm -Cv
6. growfs -M /sgs /dev/md/rdsk/d60 (la opcion -M es cuando el filesystem esta montado osea se hace la operacin en caliente)
mount -F hsfs /dev/dsk/c0t0d0s0 /mnt
ps -fea |grep defunct| awk '{print "kill -9", $3}'|sh
du -hk | sort -nr | less
~. ldm
#. sc
chmod u+s /usr/bin/myapp se le agrega el SUID
chmod g-s /usr/bin/myapp se le quita el SGID
route add -p
mount -F -o user,autoremount /
passwd -s -a
passwd -x -1 admgt07
1. SE TIENE QUE VALIDAR CON DISK GROUP (SI SE REQUIERE CREAR UNO SE CREA SI NO SE INGRESA EL DISCO EN UN DISK GROUP EXTISTENTE)
2. SE DA BOTON DERECHO EN DISK. OPCION NEW VOLUME
3. SE ELIGE EL VOLUME GROUP DE LA OPCION 1
4. SE ELIGE LA OPCION MANUALMENTE PARA ELEGIR PROPIETARIO Y LOS DISCOS
5. SE ELIGEN LOS DISCOS (TENER PRESENTE LOS ID DE LOS DISCOS )
6. EN ESTA OPCION SE ELIEGE EL TIPO DEL FILESYSTEM, PROPIETARIO, TAMAO, OPCION FSCK "2", BOOT
/backupfullSO.log
lsof | grep deleted
route add net 10.113.1.158 10.112.1.1 255.255.255.255
ln -s /cfgte/planos /calldb/vol20/UTL_FILES/ (primero donde se tiene la capacidad o se va a gastar el espacio y de segundo a donde se quiere direccionar (no se gasta nada))
passwd -f usuario
truss -p 8306
C\Documents and Settings\henrespr\Escritorio\instalacion solaris 10
printenv
setenv boot_device instancia ( /pci@1f,700000/scsi@2/sd@0,0)
setenv diag_device instancia ( /pci@1f,700000/scsi@2/sd@0,0)
eeprom diag_device boot_device= instancia ( /pci@1f,700000/scsi@2/sd@0,0)
XSCF> console -d 0
ifconfig ce2011 plumb
10.112.1.113
10.112.1.113 255.255.255.248
vi +linenumber file.c
console -f -d 0
scstat -g
/usr/platform/SUNW,SPARC-Enterprise-T2000/sbin/sysfwdownload /opt/139434-08/Sun_System_Firmware-6_7_11-SPARC_Enterprise_T2000.bin
init 0
showsc version -v
showhost
poweroff
showkeyswitch
flashupdate -s 127.0.0.1
resetsc
showhost
showsc version -v
#!/bin/bash
ipcs
wall
/bin/true
/bin/sh
cdrw -M
ldm set-var auto-boot?=false crmucm01
ldm add-vdisk cdrom cdrom_d1@primary-vds0 crmucm01
ldm set-vnet pvid=1 vid=74,67,201,801,807 vnet0 crmbale2
dladm show-dev
mount -F hsfs /dev/rdsk/c0t0d0s2 /parches
/usr/lib/security/libpam_unix.1 debug
fmadm faulty
PROBE-SCSI-ALL estando en el OK
boot -- -r
/opt/SUNWcacao/bin/cacaoadm (svc:/application/management/common-agent-container-1:default (Cacao)
sdiff
SE
/etc/nodename, /etc/hosts, /etc/hostname, visudo, /etc/profile
mount -F ufs -o rw,remount /
boot cdrom -sw
fsck /dev/dsk/c1t0d0s0
Las VLAN se pueden crear de acuerdo a distintos criterios, pero cada VLAN se debe asignar una etiqueta o ID de VLAN (VID). The VID is a 12-bit identifier between 1 and 4094 that identifies a unique VLAN. El VID es un identificador de 12 bits entre 1 y 4094 que identifica a una VLAN de forma exclusiva. For each network interface (for example, ce0 , ce1 , ce2 , and so on) 512 possible VLANs can be created. Para cada interfaz de red (por ejemplo, ce0, CE1, CE2, y as sucesivamente) 512 VLAN se pueden crear. Because IP subnets are commonly used, use IP subnets when setting up a VLAN network interface. Debido a que las subredes IP se utilizan habitualmente, utiliza subredes IP al crear una interfaz de red VLAN. This means that each VID assigned to a VLAN interface of a physical network interface belongs to different subnets. Esto significa que cada VID asignada a una interfaz VLAN de una interfaz de red fsica pertenece a diferentes subredes.
crontab -l USUARIO
/usr/sfw/bin/smbpasswd
cpio -idmv < 10gr2_client_sol.cpio
EN el firewall deben quedar los permisos bidireccionales tcp 6000 /tcp 6030
/usr/ucb/ps -aux
RECONOCER LUN ASIGNADA POR ALMACENAMIENTO
CUAL FILESYSTEM SE VA A AMPLIAR
MODIFICAR SCRIPT DE REPLICA
truss
PS1=root@globalcon # PS2=root@globalcon >
trap "" 15
ifconfig ce0:1 plumb ifconfig ce0 plumb
route add default 192.168.11.4 -ifp ce43002:1
:1,2000d
Cuando un mail no puede enviarse, el archivo se copiar en un archivo de su directorio de usuario llamado dead.letter. (ver el archivo para ver que fallas tiene el envio)
SYSTEM CONTROLLER (RESETSC)
fuser -u /tmp
ldm add-vdsdev /dev/dsk/c2t5006016010601FC1d25s2 vol_c2t5006016010601FC1d25s2@primary-vds2
ldm add-vdisk vol_c2t5006016010601FC1d25s2 vol_c2t5006016010601FC1d25s2@primary-vds2 ssbdsun3
cfgadm -al
cfgadm -c unconfigure c0::dsk/c1t1d1
Se puede retirar el disco de forma segura
snoop 192.168.11.24 |grep 172.18.22.30
Link aggregation
find /var/spool/clientmqueue -type f -mtime 30 -exec rm {} \;
se modica el .profile del usuario admgt07
export JAVA_HOME=/usr/java/jdk1.5.0_07/bin/java (ruta de la version de java que se requiere)
export PATH=$PATH:/usr/java/jdk1.5.0_07/bin
guardar y salir
volverse a loguear echo $JAVA_HOME echo $PATH
1. se crea el script correspondiente y se guarda en /etc/rc.d/
2. En este caso /etc/rc.d/yast_new
3. se crea un link simbolico ln -s /etc/rc.d/yast_new /etc/rc.d/rc5.d/S13yast_new
4. Con ello se valida que al reiniciar la maquina el script se ejecuta en el run level 5
INSTALAR POSTFIX EN SOLARIS 10
Howto install:
This package is to replace Sendmail on Solaris, so you have to uninstall first Sendmail:
# svcadm disable sendmail
# pkgrm SUNWsndmu
# pkgrm SUNWsndmr
Uncompress the file with bunzip2 and then install the package with pkgadd:
# bunzip2 CNDpostfix-2.4.6,REV=080102-SunOS5.10-sparc.pkg.bz2
# pkgadd -d CNDpostfix-2.4.6,REV=080102-SunOS5.10-sparc.pkg CNDpostfix
Now you can change /etc/postfix/main.cf according to your needs and start Postfix with:
# svcadm enable svc:/network/postfix:default
share
unshare <recurso>
eject
/etc/default/init
ipcs -l
for i in $(</tmp/users.txt)
do
grep $i /etc/passwd |awk '{print $4}' FS=: >> /tmp/ultimo.txt
done
for i in $(</tmp/grupos.txt)
do
grep $i /etc/group |awk '{print $1}' FS=: >> /tmp/grupos1.txt
done
Sar -d 1 10 / iostat 1 10
ps -efo vsz,pid,comm | sort -rn|more
SOLARIS 9
df -h (gigas) -k s (kilobytes) du -hs
useradd -usermod -userdel
top -d 6
grep luis /etc/passwd
more /etc/group
chown oramonoinstall /AgenteOracle
queda con todos los permisos
umount /dev/tatat/ /filesystem
Campos obligatorios (hardware red sistema operativo)
su - oramon
iostat
passwd -x -1 usuario
passwd -s usuario
vi /etc/hosts
grep oramon /etc/passwd
vi /etc/passwd (se busca el usuario y se cambia el filesystem a /AgenteOracle).
vi /etc/vfstab (se ubica el anterior filesystem y se cambia a /AgenteOracle).
ps -fea | grep oracle92
ps -fea | grep oracle92 |wc -l
usermod -d /AgenteOracle oramon
sudo su -
uname -rs
pkgadd
sneep
chmod 550 /usr/bin/su - chmod u+s /usr/bin/su
format
metastat p |grep m (si es 0 1 o cualquiera)
https//ntpserver/nagios/ user etbadmin passw getronics
/usr/sbin/sneep
luxadm -e port seguido de luxadm -e dump_map /devices/.
prtdiag -v
psrinfo
/usr/local/sbin/visudo
mpstat
swap -l (vmstat)
ps -aux | more
sudo /usr/sbin/losf -i - /bin/netstat -natu
C\Documents and Settings\henrespr\Escritorio\LINUX
groupadd -g 700 admetbsr groupadd -g 800 admbck
- groupadd -g 900 admsrv
/usr/bin/gpasswd -a henry pruebita
/usr/local/bin/top
who / ps -fea | grep pts/6 ---- kill -9 ID primer fila
pkgadd -d
PATH=$PATH/usr/local/bin/usr/local/sbin
/etc/issue - /etc/motd
$
powermt config o (devfsadm -v)(cfgadm -c configure c1 c2 c3 c4) (reconfigura todas las controladoras a nivel de sistema operativo)
netstat -nr
crontab -e
du -hs*
du -k *
/etc/init.d/sshd restart
find . -mtime 1 (-atime cuando se accedi al fichero por ltima vez.)(-ctime cuando fueron cambiados los permisos del fichero por ltima vez. )(-mtime cuando fue cambiado el contenido del fichero por ltima vez.)
echo "Esto es una prueba, 1 2 3, probando" | cut -d " " -f 1 muestra (Esto es una prueba) y -f se refiere al primer campo
es un nombre de dispositivo abreviado que es creado por el propio kernel. Un ejemplo del uso de los nombres de instancia lo encontramos en la ejecucin del comando ifconfig a donde podemos ver en negrita el nombre de la instancia que corresponde con la interfaz de red
grep pegasus.x /etc/passwd muestra (pegasusx6665tog-pegasus OpenPegasus WBEM/CIM services/var/lib/Pegasus/sbin/nologin)
vi /etc/nsswitch.conf
vi /etc/nsswitch.conf debe quedar la linea host igual al comentario
022 - 777 = 755 022 - 666 = 644
/etc/syslog.conf
/usr/ccs/bin/usr/sfw/bin
1. [echo murcielago | tr aeiou AEIOU (mUrcIElAgO)] [echo murcielago | tr aeiou AE (mErcEElAgE)]
2. echo murcielago | tr -d ae (murcilgo)
3. echo 'una frase muy tonta pero valdr' | tr -d ' ' (unafrasemuytontaperovaldr)
4. echo 'una frase muy tonta pero valdr' | tr -s ' ' (una frase muy tonta pero valdr)
5. echo 'una frase muy tonta pero valdr' | tr -s ' ' . (una.frase.muy.tonta.pero.valdr)
6. echo 'naci el 13-12-1966' | tr -c '0123456789' '-' (--------13-12-1966-)
/etc/inittab
iostat -En
ps -fea |grep defunct| awk '{print "kill -9", $3}'|sh
du -hk | sort -nr | less
~. ldm
#. sc
1. SE TIENE QUE VALIDAR CON DISK GROUP (SI SE REQUIERE CREAR UNO SE CREA SI NO SE INGRESA EL DISCO EN UN DISK GROUP EXTISTENTE)
oe
lsof | grep deleted
route add net 10.113.1.158 10.112.1.1 255.255.255.255

ln -s /cfgte/planos /calldb/vol20/UTL_FILES/ (primero donde se tiene la capacidad o se va a gastar el espacio y de segundo a donde se quiere direccionar (no se gasta nada))
passwd -f usuario
truss -p 8306
vi +linenumber file.c
/usr/platform/SUNW,SPARC-Enterprise-T2000/sbin/sysfwdownload /opt/139434-08/Sun_System_Firmware-6_7_11-SPARC_Enterprise_T2000.bin
#!/bin/bash
ipcs
wall
/bin/true
/bin/sh
/usr/lib/security/libpam_unix.1 debug
Las VLAN se pueden crear de acuerdo a distintos criterios, pero cada VLAN se debe asignar una etiqueta o ID de VLAN (VID). The VID is a 12-bit identifier between 1 and 4094 that identifies a unique VLAN. El VID es un identificador de 12 bits entre 1 y 4094 que identifica a una VLAN de forma exclusiva. For each network interface (for example, ce0 , ce1 , ce2 , and so on) 512 possible VLANs can be created. Para cada interfaz de red (por ejemplo, ce0, CE1, CE2, y as sucesivamente) 512 VLAN se pueden crear. Because IP subnets are commonly used, use IP subnets when setting up a VLAN network interface. Debido a que las subredes IP se utilizan habitualmente, utiliza subredes IP al crear una interfaz de red VLAN. This means that each VID assigned to a VLAN interface of a physical network interface belongs to different subnets. Esto significa que cada VID asignada a una interfaz VLAN de una interfaz de red fsica pertenece a diferentes subredes.
truss
Si llega la seal 15 (SIGTERM) , no hagas nada)
:1,2000d
pkill -HUP inetd
snoop 192.168.11.24 |grep 172.18.22.30
/etc/init.d/isisd status
Link aggregation
find /var/spool/clientmqueue -type f -mtime 30 -exec rm {} \;
1. se crea el script correspondiente y se guarda en /etc/rc.d/
2. En este caso /etc/rc.d/yast_new
3. se crea un link simbolico ln -s /etc/rc.d/yast_new /etc/rc.d/rc5.d/S13yast_new
4. Con ello se valida que al reiniciar la maquina el script se ejecuta en el run level 5
sar -u 1 2 | tail -1 | awk '{print "% CPU\n","----\n",100 - $5,"%"}'
vmstat 1 2| tail -1 | awk '{ print $5/1024 , "MB" }
HPUX
df -h (gigas) -k s (kilobytes) du -hs
ioscan -faC lan
su - oramon
sam
passwd -x -1 usuario
passwd -s usuario
vi /etc/hosts
grep oramon /etc/passwd
vi /etc/passwd (se busca el usuario y se cambia el filesystem a /AgenteOracle).
vi /etc/vfstab (se ubica el anterior filesystem y se cambia a /AgenteOracle).
ps -fea | grep oracle92
ps -fea | grep oracle92 |wc -l
usermod -d /AgenteOracle oramon
sudo su - root
/usr/local/sbin/visudo
mpstat
swap -l (vmstat)
ps -aux | more
sudo /usr/sbin/losf -i - /bin/netstat -natu
C\Documents and Settings\henrespr\Escritorio\LINUX
groupadd -g 700 admetbsr groupadd -g 800 admbck
- groupadd -g 900 admsrv
shutdown -ry 0
netstat -nr
lanadmin
lanadmin opcion ppc
du -hs*
du -k *
find . -mtime 1 (-atime cuando se accedi al fichero por ltima vez.)(-ctime cuando fueron cambiados los permisos del fichero por ltima vez. )(-mtime cuando fue cambiado el contenido del fichero por ltima vez.)
grep pegasus.x /etc/passwd muestra (pegasusx6665tog-pegasus OpenPegasus WBEM/CIM services/var/lib/Pegasus/sbin/nologin)
022 - 777 = 755 022 - 666 = 644
/etc/syslog.conf
1. [echo murcielago | tr aeiou AEIOU (mUrcIElAgO)] [echo murcielago | tr aeiou AE (mErcEElAgE)]
2. echo murcielago | tr -d ae (murcilgo)
3. echo 'una frase muy tonta pero valdr' | tr -d ' ' (unafrasemuytontaperovaldr)
4. echo 'una frase muy tonta pero valdr' | tr -s ' ' (una frase muy tonta pero valdr)
5. echo 'una frase muy tonta pero valdr' | tr -s ' ' . (una.frase.muy.tonta.pero.valdr)
6. echo 'naci el 13-12-1966' | tr -c '0123456789' '-' (--------13-12-1966-)
/etc/inittab
ps -fea |grep defunct| awk '{print "kill -9", $3}'|sh
du -hk | sort -nr | less
mailx -s "Backup Full SO CFGPROD" gt_respaldos@etb.com.co, gt_servidores@etb.com.co < /tmp/backupfullSO.log
lsof | grep deleted
var/adm/cron
icapstatus (top logicos)
passwd -f usuario
truss -p 8306
vi +linenumber file.c
#!/bin/bash
ipcs
wall
/bin/true
/bin/sh
(archivos de configuracion /etc/SnmpAgent.d/snmpd.conf - /etc/snmp.conf) /sbin/init.d/SnmpMaster stop
Las VLAN se pueden crear de acuerdo a distintos criterios, pero cada VLAN se debe asignar una etiqueta o ID de VLAN (VID). The VID is a 12-bit identifier between 1 and 4094 that identifies a unique VLAN. El VID es un identificador de 12 bits entre 1 y 4094 que identifica a una VLAN de forma exclusiva. For each network interface (for example, ce0 , ce1 , ce2 , and so on) 512 possible VLANs can be created. Para cada interfaz de red (por ejemplo, ce0, CE1, CE2, y as sucesivamente) 512 VLAN se pueden crear. Because IP subnets are commonly used, use IP subnets when setting up a VLAN network interface. Debido a que las subredes IP se utilizan habitualmente, utiliza subredes IP al crear una interfaz de red VLAN. This means that each VID assigned to a VLAN interface of a physical network interface belongs to different subnets. Esto significa que cada VID asignada a una interfaz VLAN de una interfaz de red fsica pertenece a diferentes subredes.
ioscan -a |grep proc |wc -l
EJEMPLO DALEENQA 8 PROCESADORES ENTONCES TIENE 16 CORE (SE MULTIPLICAN POR 2 EL NUMERO DE PROCESADORES)
:1,2000d
snoop 192.168.11.24 |grep 172.18.22.30
find /var/spool/clientmqueue -type f -mtime 30 -exec rm {} \;
/opt/HORCM/caprdfact/logs/replica.log
matchinfo
reiniciar maquina hpux shutdown -ry 0
LINUX
df -h (gigas) -k s (kilobytes) du -hs
su - oramon
passwd -x -1 usuario
passwd -s usuario
vi /etc/hosts
grep oramon /etc/passwd
vi /etc/passwd (se busca el usuario y se cambia el filesystem a /AgenteOracle).
vi /etc/vfstab (se ubica el anterior filesystem y se cambia a /AgenteOracle).
ps -fea | grep oracle92
ps -fea | grep oracle92 |wc -l
usermod -d /AgenteOracle oramon
su
rpm -qa | grep gcc
rpm -qa | grep cc
mpstat
swap -l (vmstat)
ps -aux | more
sudo /usr/sbin/losf -i - /bin/netstat -natu
C\Documents and Settings\henrespr\Escritorio\LINUX
groupadd -g 700 admetbsr groupadd -g 800 admbck
- groupadd -g 900 admsrv
/usr/bin/gpasswd -a henry pruebita
netstat -nr
crontab -e
du -hs*
du -k *
VER COMENTARIO
dpkg -i
dpkg -r
dpkg -l
dpkg --listfiles
dpkg --print-avail
dpkg --purge
dpkg --search
dpkg --status
dpkg -C = dpkg -audit buscan paquetes parcialmente instalados
dpkg -install ethereal.deb -- force-depends-version
nice
renice
grep pegasus.x /etc/passwd muestra (pegasusx6665tog-pegasus OpenPegasus WBEM/CIM services/var/lib/Pegasus/sbin/nologin)
bzip2 -d linux-2.4.16.tar.bz2
tar cvf linux-2.4.16.tar
uniq (remueve cualquier lnea duplicada)
expand
unexpand
pr
ulimit -a
022 - 777 = 755 022 - 666 = 644
/etc/syslog.conf
/var/cache/apt/archives
1. [echo murcielago | tr aeiou AEIOU (mUrcIElAgO)] [echo murcielago | tr aeiou AE (mErcEElAgE)]
2. echo murcielago | tr -d ae (murcilgo)
3. echo 'una frase muy tonta pero valdr' | tr -d ' ' (unafrasemuytontaperovaldr)
4. echo 'una frase muy tonta pero valdr' | tr -s ' ' (una frase muy tonta pero valdr)
5. echo 'una frase muy tonta pero valdr' | tr -s ' ' . (una.frase.muy.tonta.pero.valdr)
6. echo 'naci el 13-12-1966' | tr -c '0123456789' '-' (--------13-12-1966-)
/etc/inittab
/etc/passwd 644
/etc/X11/xdm/xdm-config
/etc/X11/xdm/Xresources
/etc/X11/xdm/Xsession
/etc/X11/gdm
MUESTRA EL COMANDO ANTERIOR
no limpia procesos afectados antes de salir
ls *.c cpio -ov > /dev/fd0
/var/spool/cron/root
messages
dmesg
boot
sudo.log
secure
lastlog t
ps -fea |grep defunct| awk '{print "kill -9", $3}'|sh
ps -fea |grep defunct
sndconfig
dmidecode
El comando startx es un script que ejecuta el proceso xinit
xinitrc del usuario, si no existiese se ejecutara el script genrico xinitrc.
du -hk | sort -nr | less
LILO NO POSEE CONSOLA POR COMANDOS GRUB SI
ls -l /usr/bin/passwd -rwsr-xr-x 1 root wheel 17588 Sep 24 0053 /usr/bin/passwd
ls -l /usr/bin/passwd -rwxrwSr-x 1 root wheel 17588 Sep 24 0053 /usr/bin/passwd
etc/rc.d/rc.local
mailx -s "Backup Full SO CFGPROD" gt_respaldos@etb.com.co, gt_servidores@etb.com.co < /tmp/backupfullSO.log
lsof | grep deleted
/etc/sysconfig/network-scripts/ifcfg-lo (Loopback)
demonio para arrancar o parar el demonio apache
emcpdiscover
lssd
./hp_rescan -a
lssd
powermt config
/usr/sbin/timeconfig
chage -d 0 usuario
Se puede crear archivos de un tamao determinado en Linux usand el comando dd. Por ejemplo
$ cd /tmp
$ dd if=/dev/zero of=archivo.txt bs=1024 count=1048576 ( mkfile 2g prueba)
Este comando crea un archivo archivo.txt de 1GB (1024 * 1048576 bytes).
if archivo de entrada
of archivo de salida, el archivo que queremos crear
bs tamao de block en bytes
count cantidad de blocks de tamao bs
/usr/src/linux
Documentacion
grep relay /etc/postfix/main.cf
relayhost= 10.112.8.17
se reinicia el servicio postfix
strace-p 8306
hwclock --set --date="2000-02-25 1625" (bios)
date --set "2000-02-25 1625"
rpm --import /usr/share/rhn/RPM-GPG-KEY
vi +linenumber file.c
echo 1 >/proc/sys/net/ipv4/icmp_echo_ignore_all
echo 0 >/proc/sys/net/ipv4/icmp_echo_ignore_all
cancela un shutdown
no corrre el fsck en el reinicio
corrre el fsck en el reinicio
el sistema se detiene despues de apagarlo
#!/bin/bash
http://localhost:631/
ipcs
service --status-all
more /etc/xinetd.d/krb5-telnet
more /etc/xinetd.d/ekrb5-telnet y se reinicia el servicio Xinet
dmidecode "cpu's": 2
processor : 7 de 0 a 7 (8 nucleos) (quad core) (cada socket tiene un prcesador de 4 nucleos
problemas con el DNS
etc/nologin
wall
$$
/bin/true
/bin/sh
route del default
yum clean dbcache
tmpwatch
/etc/logwatch/conf/logwatch.conf
cat /proc/mdstat
Las VLAN se pueden crear de acuerdo a distintos criterios, pero cada VLAN se debe asignar una etiqueta o ID de VLAN (VID). The VID is a 12-bit identifier between 1 and 4094 that identifies a unique VLAN. El VID es un identificador de 12 bits entre 1 y 4094 que identifica a una VLAN de forma exclusiva. For each network interface (for example, ce0 , ce1 , ce2 , and so on) 512 possible VLANs can be created. Para cada interfaz de red (por ejemplo, ce0, CE1, CE2, y as sucesivamente) 512 VLAN se pueden crear. Because IP subnets are commonly used, use IP subnets when setting up a VLAN network interface. Debido a que las subredes IP se utilizan habitualmente, utiliza subredes IP al crear una interfaz de red VLAN. This means that each VID assigned to a VLAN interface of a physical network interface belongs to different subnets. Esto significa que cada VID asignada a una interfaz VLAN de una interfaz de red fsica pertenece a diferentes subredes.
ip route add 10.112.1.31/32 via 10.111.32.1 dev eth0.805
mount -o loop CDS-100-S10_Unix_Essentials_Featuring_the_Solaris_10_Operating_System.iso /mnt
crontab -u admangtb -l
chattr +i /etc/passwd y chattr +i /etc/shadow para ver los atributos lsattr ------------- /etc/passwd al cambiarlos queda ----i-------- /etc/passwd para quitarla otra opcion es chattr -i /etc/passwd
ltrace dtrace strace
EJEMPLO DALEENQA 8 PROCESADORES ENTONCES TIENE 16 CORE (SE MULTIPLICAN POR 2 EL NUMERO DE PROCESADORES)
:1,2000d
pkill -HUP inetd
se modifica el archivo /etc/HOSTNAME
etc/resolv.conf
boundig CONFIGURAR VER COMENTARIO
find /var/spool/clientmqueue -type f -mtime 30 -exec rm {} \;
1. se crea el script correspondiente y se guarda en /etc/rc.d/
2. En este caso /etc/rc.d/yast_new
3. se crea un link simbolico ln -s /etc/rc.d/yast_new /etc/rc.d/rc5.d/S13yast_new
4. Con ello se valida que al reiniciar la maquina el script se ejecuta en el run level 5
/etc/zmd/deviceid contenido
/etc/zmd/secret contenido
contenido y accede a la pagina https://nu.novell.com
si esto no funciona borrar los dos archivos anteriores y volver a ejecutar yast.
/etc/security/limits.conf
rpm -i pdksh-5.2.14-16.i386.rpm
<
ps aux --width 30 --sort -rss | head TOP 10 consumo de CPU
egrep -i 'port=|Portname' /proc/scsi/*/*
passwd -x 62
Sudo mount -o loop /DVD/rhel-server-5.8-i386-dvd.iso /media/DVD1
sudo /usr/sbin/lvextend -L5G /dev/mapper/vg00-lv_home
sudo /sbin/resize2fs /dev/mapper/vg00-lv_home
Cuando se tenga problema con un NFS
Crea un enlace simbolico y se busca el directorio y se elimina
sudo /sbin/pam_tally --user hcanasteros
sudo /sbin/pam_tally --user hcanasteros --reset=0
WINDOWS
mstsc /vnombre ip/admin
hmc administrador de recursos
1. mstsc /vsnmulp01 /admin
2. tsadmin
wmic
bios get serialnumber
wmic startup list full
10.113.1.116
mailx -s "Backup Full SO CFGPROD" gt_respaldos@etb.com.co, gt_servidores@etb.com.co < /tmp/backupfullSO.log
se agrega el usuario al grupo remote desktop y power users
pstools. Se ingresa por consola a la carpeta C:pstools y se ejecuta psexec \\CSHPTPR1 systeminfo
wmic process where name="AcroRd32.exe" delete
account operators
Las VLAN se pueden crear de acuerdo a distintos criterios, pero cada VLAN se debe asignar una etiqueta o ID de VLAN (VID). The VID is a 12-bit identifier between 1 and 4094 that identifies a unique VLAN. El VID es un identificador de 12 bits entre 1 y 4094 que identifica a una VLAN de forma exclusiva. For each network interface (for example, ce0 , ce1 , ce2 , and so on) 512 possible VLANs can be created. Para cada interfaz de red (por ejemplo, ce0, CE1, CE2, y as sucesivamente) 512 VLAN se pueden crear. Because IP subnets are commonly used, use IP subnets when setting up a VLAN network interface. Debido a que las subredes IP se utilizan habitualmente, utiliza subredes IP al crear una interfaz de red VLAN. This means that each VID assigned to a VLAN interface of a physical network interface belongs to different subnets. Esto significa que cada VID asignada a una interfaz VLAN de una interfaz de red fsica pertenece a diferentes subredes.
cs query
chattr +i /etc/passwd y chattr +i /etc/shadow para ver los atributos lsattr ------------- /etc/passwd al cambiarlos queda ----i-------- /etc/passwd para quitarla otra opcion es chattr -i /etc/passwd
http://www.tldp.org/HOWTO/LVM-HOWTO/recipeadddisk.html
sudo umount -fl /directorio
AIX
stopsrc -s sshd
startsrc -s sshd
topas
pwdadm -f ADMCHG usuario
mkuser id='3001' pgrp='dba' su='true' home='/home/efigmonv' gecos='Efigenia Monroy' efigmonv
/usr/sbin/useradd -c "Efigenia Monroy" -s /bin/csh -m -d /home/efigmonv -g 201 -u 3001 efigmonv
/usr/local/samba/bin/smbstatus
vi +linenumber file.c
#!/bin/bash
ipcs
/bin/true
/bin/sh
Las VLAN se pueden crear de acuerdo a distintos criterios, pero cada VLAN se debe asignar una etiqueta o ID de VLAN (VID). The VID is a 12-bit identifier between 1 and 4094 that identifies a unique VLAN. El VID es un identificador de 12 bits entre 1 y 4094 que identifica a una VLAN de forma exclusiva. For each network interface (for example, ce0 , ce1 , ce2 , and so on) 512 possible VLANs can be created. Para cada interfaz de red (por ejemplo, ce0, CE1, CE2, y as sucesivamente) 512 VLAN se pueden crear. Because IP subnets are commonly used, use IP subnets when setting up a VLAN network interface. Debido a que las subredes IP se utilizan habitualmente, utiliza subredes IP al crear una interfaz de red VLAN. This means that each VID assigned to a VLAN interface of a physical network interface belongs to different subnets. Esto significa que cada VID asignada a una interfaz VLAN de una interfaz de red fsica pertenece a diferentes subredes.
:1,2000d
find /var/spool/clientmqueue -type f -mtime 30 -exec rm {} \;
loopmount -i /export/ISO/AIX_6.1TL7SP4-1.iso -o "-V cdrfs -o ro" -m /ISO
Las VLAN se pueden crear de acuerdo a distintos criterios, pero cada VLAN se debe asignar una etiqueta o ID de VLAN (VID). The VID is a 12-bit identifier between 1 and 4094 that identifies a unique VLAN. El VID es un identificador de 12 bits entre 1 y 4094 que identifica a una VLAN de forma exclusiva. For each network interface (for example, ce0 , ce1 , ce2 , and so on) 512 possible VLANs can be created. Para cada interfaz de red (por ejemplo, ce0, CE1, CE2, y as sucesivamente) 512 VLAN se pueden crear. Because IP subnets are commonly used, use IP subnets when setting up a VLAN network interface. Debido a que las subredes IP se utilizan habitualmente, utiliza subredes IP al crear una interfaz de red VLAN. This means that each VID assigned to a VLAN interface of a physical network interface belongs to different subnets. Esto significa que cada VID asignada a una interfaz VLAN de una interfaz de red fsica pertenece a diferentes subredes.
NOMBRE CC RACK
Pos.
RACK
COCSFPR1 CCP (20) CCNFB 34
CSHPTPR1 CCP (20) CCNFB 36
COCSEPR2 CCA (114) CCAEG 33
COCSFPR2 CCA (114) CCAEG 39
Las VLAN se pueden crear de acuerdo a distintos criterios, pero cada VLAN se debe asignar una etiqueta o ID de VLAN (VID). The VID is a 12-bit identifier between 1 and 4094 that identifies a unique VLAN. El VID es un identificador de 12 bits entre 1 y 4094 que identifica a una VLAN de forma exclusiva. For each network interface (for example, ce0 , ce1 , ce2 , and so on) 512 possible VLANs can be created. Para cada interfaz de red (por ejemplo, ce0, CE1, CE2, y as sucesivamente) 512 VLAN se pueden crear. Because IP subnets are commonly used, use IP subnets when setting up a VLAN network interface. Debido a que las subredes IP se utilizan habitualmente, utiliza subredes IP al crear una interfaz de red VLAN. This means that each VID assigned to a VLAN interface of a physical network interface belongs to different subnets. Esto significa que cada VID asignada a una interfaz VLAN de una interfaz de red fsica pertenece a diferentes subredes.
Las VLAN se pueden crear de acuerdo a distintos criterios, pero cada VLAN se debe asignar una etiqueta o ID de VLAN (VID). The VID is a 12-bit identifier between 1 and 4094 that identifies a unique VLAN. El VID es un identificador de 12 bits entre 1 y 4094 que identifica a una VLAN de forma exclusiva. For each network interface (for example, ce0 , ce1 , ce2 , and so on) 512 possible VLANs can be created. Para cada interfaz de red (por ejemplo, ce0, CE1, CE2, y as sucesivamente) 512 VLAN se pueden crear. Because IP subnets are commonly used, use IP subnets when setting up a VLAN network interface. Debido a que las subredes IP se utilizan habitualmente, utiliza subredes IP al crear una interfaz de red VLAN. This means that each VID assigned to a VLAN interface of a physical network interface belongs to different subnets. Esto significa que cada VID asignada a una interfaz VLAN de una interfaz de red fsica pertenece a diferentes subredes.
SEA DESDE0
Crear SEA
1. Creo el link aggr
2. Creo la VLAn mkvdev -sea ent2 -vadapter ent3 -default ent3 -defaultid 1 Creo el adaptador virtual en la hmc y le agrego las VLAN
3. Taggeo las vlan en el vioserver mkvdev -vlan ent4
4. veo los dispositivos que crea
# lsdev |grep VLAN
ent5 Available VLAN
ent6 Available VLAN
ent7 Available VLAN
ent8 Available VLAN
5. Veo si las VLAN estan bien configuradas en el portchannel
tcpdump -vvv -i en5 en6 en7 ent8
como en este caso la ent6 me arrroja segmento de red de 10.231 asigno mi ip del vio en la interfaz ent6
asi
# ifconfig -a
en6: flags=1e084863,c0<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACTIVE),LARGESEND,CHAIN>
inet 10.222.33.17 netmask 0xffffffc0 broadcast 10.222.33.63
tcp_sendspace 131072 tcp_recvspace 65536 rfc1323 0
lo0: flags=e08084b,c0<UP,BROADCAST,LOOPBACK,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,LARGESEND,CHAIN>
inet 127.0.0.1 netmask 0xff000000 broadcast 127.255.255.255
inet6 ::1%1/0
tcp_sendspace 131072 tcp_recvspace 131072 rfc1323 1
Page 509
SEA DESDE0
Creo el adaptador virtual en la hmc y le agrego las VLAN
$ lsmap -all -net
SVEA Physloc
------ --------------------------------------------
ent3 U9117.570.10B6F2C-V6-C2-T1
SEA ent4
Backing device ent2
Status Available
Physloc
como en este caso la ent6 me arrroja segmento de red de 10.231 asigno mi ip del vio en la interfaz ent6
en6: flags=1e084863,c0<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,CHECKSUM_OFFLOAD(ACTIVE),LARGESEND,CHAIN>
lo0: flags=e08084b,c0<UP,BROADCAST,LOOPBACK,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT,LARGESEND,CHAIN>
Page 510
porcentaje USO memoria ram y sw
porcentaje USO memoria ram y swap
prtconf |grep Used Porcentaje memoria swap
for i in `cat /home/ibmadmhe/maquinas_argos |grep -v "#"`^Jdo^Jssh $i "hostname; amepat |grep True|grep -v ":""^Jdone
Top 20 memoria ram
ps aux | head -1 ; ps aux | sort -rn +3 |
head -15
sudo svmon -P -t 15 -O summary=basic
Page 511
porcentaje USO memoria ram y sw
Porcentaje memoria swap
for i in `cat /home/ibmadmhe/maquinas_argos |grep -v "#"`^Jdo^Jssh $i "hostname; amepat |grep True|grep -v ":""^Jdone
memoria swap
Sudo svmon -P -O
sortseg=pgsp
Page 512
porcentaje USO memoria ram y sw
Porcentaje memoria ram
Page 513
NTPSERVER AIX
http://www-01.ibm.com/support/docview.wss?uid=isg3T1000653
Page 514
Crear adaptadores virtuales des
En el perfil
chsyscfg -m Server-9117-MMB-SN06449ER -r prof -i 'name=DefaultU,lpar_id=3,"virtual_fc_adapters+=""33/Client/1/VIOS-ARGOS3A/310/C0507604FBE1005E,C0507604FBE1005F/0"""'
elimino el adaptador
En caliente
chhwres -r virtualio -m Server-9117-MMB-SN06449ER -o a -p coibmrppaix01 --rsubtype fc -a "adapter_type=client,remote_lpar_name=VIOS-ARGOS3A,remote_slot_num=310,\"wwpns=C0507604FBE1005E,C0507604FBE1005F\"" -s 33
Page 515
Crear adaptadores virtuales des
chsyscfg -m Server-9117-MMB-SN06449ER -r prof -i 'name=DefaultU,lpar_id=3,"virtual_fc_adapters+=""33/Client/1/VIOS-ARGOS3A/310/C0507604FBE1005E,C0507604FBE1005F/0"""'
chhwres -r virtualio -m Server-9117-MMB-SN06449ER -o a -p coibmrppaix01 --rsubtype fc -a "adapter_type=client,remote_lpar_name=VIOS-ARGOS3A,remote_slot_num=310,\"wwpns=C0507604FBE1005E,C0507604FBE1005F\"" -s 33
Page 516
Crear adaptadores virtuales des
chsyscfg -m Server-9117-MMB-SN06449ER -r prof -i 'name=DefaultU,lpar_id=3,"virtual_fc_adapters+=""33/Client/1/VIOS-ARGOS3A/310/C0507604FBE1005E,C0507604FBE1005F/0"""'
chhwres -r virtualio -m Server-9117-MMB-SN06449ER -o a -p coibmrppaix01 --rsubtype fc -a "adapter_type=client,remote_lpar_name=VIOS-ARGOS3A,remote_slot_num=310,\"wwpns=C0507604FBE1005E,C0507604FBE1005F\"" -s 33
Page 517
Intentos fallidos
Intentos fallidos
who -s /etc/security/failedlogin
Page 518
Procesadores en AIX
topas -L
Cada unidad de procesamiento son los mismo core
Por ejemplo
Tengo de unidad de procesamiento 2.5 y de cpus virtuales 3
entonces hay depende de muchas cosas
1. capped Si esta capado unicamente llegar endado de algun pico de CPU a 2.5
2. uncapped Si esta en uncapped el podr llegar en dado caso algun pico a 3
Entonces el concepto cambia ac para temas de licenciamiento y si estan en uncaped por ejemplo aca se tendrian 3 procesadores y no 2.5 oracle toma los 3 virtiuales
Page 519
Procesadores en AIX
para temas de licenciamiento y si estan en uncaped por ejemplo aca se tendrian 3 procesadores y no 2.5 oracle toma los 3 virtiuales
Page 520
Relacion de confianza HMC
Se borra asi: mkauthkeys -r "ssh-rsa AAAB3NzaC1yc2EAAA joe@somehost"
Se coloca asi : mkauthkeys -a "ssh-rsa AAAB3NzaC1yc2EAAA joe@somehost"
Page 521
ENJAULAR SFTP
https://calomel.org/sftp_chroot.html
Permisos 750
permisos root:GRUPODELUSUARIO
Page 522
wtmp
Depurar wtmp
Administracin archivo /var/adm/wtmp
Depuracin del archivo /var/adm/wtmp:
Validar un filesystem con suficiente espacio (aprox. de la mita, por ejemplo /tmp)
Convertir el archivo wtmp a ASCII y limpiar el archivo /var/adm/wtmp:
/usr/sbin/acct/fwtmp < /var/adm/wtmp > /tmp/wtmp_dummy_`date "+%d%m%y"`;> /var/adm/wtmp

Convertir un archivo ASCII de /var/adm/wtmp al formato wtmp:
/usr/sbin/acct/fwtmp -ic < /tmp/wtmp_dummy > /var/adm/wtmp
Page 523
wtmp
/usr/sbin/acct/fwtmp < /var/adm/wtmp > /tmp/wtmp_dummy_`date "+%d%m%y"`;> /var/adm/wtmp
Page 524
COMMIT AIX
https://sites.google.com/site/uyestebandiaz/tips-aix/how-to/comitt-and-rejecting-software-aix
Commit paquetes de Aix
Page 525
crear un archivo de 1G
crear un archivo de 1G
sudo /usr/sbin/lmktemp prueba 1024M
Page 526
SED
sed --in-place "s/PASS_MIN_LEN[ \t]*[0-9]*/PASS_MIN_LEN\t9/" /etc/login.defs
reemplazar una palabra
expect comando
spawn cyradm --auth login localhost --user cyrus
set adminpass [lindex $argv 0]
set adduser [lindex $argv 1]
expect "IMAP Password:"
send "$adminpass\r"
iexpect "localhost>"
send "cm user.$adduser\r"
send "lm\r"
send "quit\r"
expect eof
Page 527
FS CORRUPTO EN AIX ERRPT
C1348779 0725154013 I O SYSJ2 LOG I/O ERROR
filesystem corrupto aix
:-S
3:47:35 PM: Henry Fabian Espinosa: LABEL: J2_LOG_EIO
IDENTIFIER: C1348779
Date/Time: Thu Jul 25 15:40:10 COT 2013
Sequence Number: 9908079
Machine Id: 00F6D5514C00
Node Id: coboggdoprd02
Class: O
Type: INFO
WPAR: Global
Resource Name: SYSJ2
Description
LOG I/O ERROR
Probable Causes
ADAPTER HARDWARE OR MICROCODE
DISK DRIVE HARDWARE OR MICROCODE
SOFTWARE DEVICE DRIVER
STORAGE CABLE LOOSE, DEFECTIVE, OR UNTERMINATED
Recommended Actions
CHECK CABLES AND THEIR CONNECTIONS
INSTALL LATEST ADAPTER AND DRIVE MICROCODE
INSTALL LATEST STORAGE DEVICE DRIVERS
IF PROBLEM PERSISTS, CONTACT APPROPRIATE SERVICE REPRESENTATIVE
Detail Data
JFS2 LOG MAJOR/MINOR DEVICE NUMBER
0025 0001
ERROR CODE
0000 0005
BUF STRUCTURE B_FLAGS
0404 0404
BLOCK NUMBER
0006 4288
3:47:46 PM: Hernan Alejandro Schiavi: eso es de un fs corrupto
3:48:02 PM: Henry Fabian Espinosa: y como se cual es
Page 528
FS CORRUPTO EN AIX ERRPT
3:48:13 PM: Hernan Alejandro Schiavi: ls -l /dev
3:48:15 PM: Hernan Alejandro Schiavi: muestrame eso
3:48:19 PM: Hernan Alejandro Schiavi: puede ser un poco largo
3:48:36 PM: Henry Fabian Espinosa: ibmadmhe@coboggdoprd02:/tracedir# ls -l /dev
total 1294688
crw-rw---- 1 root system 10, 0 Aug 26 2012 IPL_rootvg
brw-rw---- 1 root system 10, 15 Oct 18 2012 ITM_lv
srwxrwxrwx 1 root system 0 Sep 05 2012 SRC
crw------- 1 root system 10, 0 Jul 24 09:35 __vg10
crw------- 1 root system 36, 0 Mar 05 18:08 __vg36
crw------- 1 root system 37, 0 Aug 26 2012 __vg37
crw-r--r-- 1 root system 2,150 Sep 19 2012 archivelogs_gpfs
drwxrwx--- 2 root asmadmin 4096 Oct 03 2012 asm
crw-rw---- 1 grid asmadmin 13, 7 Jul 25 15:44 asm_disk10
crw-rw---- 1 grid asmadmin 13, 13 Nov 21 2012 asm_disk11
crw-rw---- 1 grid asmadmin 13, 12 Dec 15 2012 asm_disk12
crw-rw---- 1 grid asmadmin 13, 14 Jul 25 15:44 asm_disk13
crw-rw---- 1 grid asmadmin 13, 11 Dec 20 2012 asm_disk14
crw-rw---- 1 grid asmadmin 13, 3 Jul 25 15:44 asm_disk15
cr--r----T 1 root system 8, 0 Aug 26 2012 audit
cr-------- 1 root system 41, 0 Oct 03 2012 bpf0
cr-------- 1 root system 41, 1 Oct 03 2012 bpf1
cr-------- 1 root system 41, 2 Oct 03 2012 bpf2
cr-------- 1 root system 41, 3 Oct 03 2012 bpf3
br--r--r-- 1 root system 13, 0 Aug 26 2012 cd0
crw-rw-rw- 1 root system 14, 0 Aug 26 2012 clone
crw--w--w- 1 root system 4, 0 Aug 26 2012 console
crw-rw-rw- 1 root system 14, 25 Aug 26 2012 echo
crw--w--w- 1 root system 6, 0 Jul 25 15:00 error
crw------- 1 root system 6, 1 Aug 26 2012 errorctl
crw-rw-rw- 1 root system 18, 1 Aug 26 2012 fscsi0
crw-rw-rw- 1 root system 18, 2 Aug 26 2012 fscsi1
crw-rw-rw- 1 root system 18, 0 Aug 26 2012 fscsi2
brw-rw---- 1 root system 37, 2 Mar 05 18:10 fslv00
brw-rw---- 1 root system 10, 8 Aug 26 2012 hd1
brw-rw---- 1 root system 10, 9 Aug 26 2012 hd10opt
brw-rw---- 1 root system 10, 10 Aug 26 2012 hd11admin
brw-rw---- 1 root system 10, 5 Aug 26 2012 hd2
brw-rw---- 1 root system 10, 7 Aug 26 2012 hd3
brw-rw---- 1 root system 10, 4 Aug 26 2012 hd4
brw-rw---- 1 root system 10, 1 Jul 24 09:35 hd5
brw-rw---- 1 root system 10, 2 Aug 26 2012 hd6
brw-rw---- 1 root system 10, 3 Aug 26 2012 hd8
brw-rw---- 1 root system 10, 6 Aug 26 2012 hd9var
brw------- 1 root system 13, 2 Aug 26 2012 hdisk0
brw------- 1 root system 13, 7 Sep 26 2012 hdisk10
Page 529
FS CORRUPTO EN AIX ERRPT
brw------- 1 root system 13, 13 Sep 26 2012 hdisk11
brw------- 1 root system 13, 12 Sep 26 2012 hdisk12
brw------- 1 root system 13, 14 Sep 26 2012 hdisk13
brw------- 1 root system 13, 11 Sep 26 2012 hdisk14
brw------- 1 root system 13, 3 Sep 26 2012 hdisk15
brw------- 1 root system 13, 6 Aug 26 2012 hdisk2
brw------- 1 root system 13, 4 Aug 26 2012 hdisk3
brw------- 1 root system 13, 5 Aug 26 2012 hdisk5
brw------- 1 root system 13, 8 Sep 19 2012 hdisk6
brw------- 1 root system 13, 9 Sep 19 2012 hdisk7
brw------- 1 root system 13, 1 Sep 19 2012 hdisk8
brw------- 1 root system 13, 10 Sep 19 2012 hdisk9
crw-rw---- 2 root system 10, 1 Aug 26 2012 ipl_blv
crw------- 2 root system 13, 6 Aug 26 2012 ipldevice
crw-rw-rw- 1 root system 24, 0 Aug 26 2012 iscsi0
cr--r----- 1 root system 2, 1 Aug 26 2012 kmem
brw-rw---- 1 root system 10, 11 Aug 26 2012 lg_dumplv
brw-rw---- 1 root system 10, 12 Aug 26 2012 livedump
srw-rw-rw- 1 root system 0 Sep 05 2012 log
brw-rw---- 1 root system 37, 1 Mar 05 18:10 loglv00
brw-rw---- 1 root system 10, 13 Oct 18 2012 medios_lv
cr--r----- 1 root system 2, 0 Aug 26 2012 mem
crw-rw-rw- 1 root system 2, 2 Jul 25 15:44 null
-rw-r--r-- 1 root system 662855289 Jul 25 15:44 null 2>&1
crw-rw-rw- 1 root system 14, 26 Aug 26 2012 nuls
crw-r--r-T 1 root system 3, 0 Aug 26 2012 nvram
crw-rw-r-- 1 root asmadmin 40, 0 Oct 03 2012 ofsctl
crw-rw---- 1 root system 37, 0 Aug 26 2012 oracle_vg
brw-rw---- 1 root system 36, 1 Mar 05 18:09 paging00
cr--r----- 1 root system 2, 4 Aug 26 2012 pmem
crw-rw-rw- 1 root system 14, 20 Aug 26 2012 ptc
drwxr-xr-x 2 root system 16384 Aug 26 2012 pts
crw-rw-rw- 1 root system 22, 0 Aug 26 2012 ptyp0
crw-rw-rw- 1 root system 22, 1 Aug 26 2012 ptyp1
crw-rw-rw- 1 root system 22, 2 Aug 26 2012 ptyp2
crw-rw-rw- 1 root system 22, 3 Aug 26 2012 ptyp3
crw-rw-rw- 1 root system 22, 4 Aug 26 2012 ptyp4
crw-rw-rw- 1 root system 22, 5 Aug 26 2012 ptyp5
crw-rw-rw- 1 root system 22, 6 Aug 26 2012 ptyp6
crw-rw-rw- 1 root system 22, 7 Aug 26 2012 ptyp7
crw-rw-rw- 1 root system 22, 8 Aug 26 2012 ptyp8
crw-rw-rw- 1 root system 22, 9 Aug 26 2012 ptyp9
crw-rw-rw- 1 root system 22, 10 Aug 26 2012 ptypa
crw-rw-rw- 1 root system 22, 11 Aug 26 2012 ptypb
crw-rw-rw- 1 root system 22, 12 Aug 26 2012 ptypc
crw-rw-rw- 1 root system 22, 13 Aug 26 2012 ptypd
Page 530
FS CORRUPTO EN AIX ERRPT
crw-rw-rw- 1 root system 22, 14 Aug 26 2012 ptype
crw-rw-rw- 1 root system 22, 15 Aug 26 2012 ptypf
crw-rw---- 1 root system 10, 15 Oct 18 2012 rITM_lv
crw-r--r-- 1 root system 35, 0 Sep 05 2012 random
cr--r--r-- 1 root system 13, 0 Aug 26 2012 rcd0
crw-rw---- 1 root system 37, 2 Mar 05 18:10 rfslv00
crw-rw---- 1 root system 10, 8 Aug 26 2012 rhd1
crw-rw---- 1 root system 10, 9 Aug 26 2012 rhd10opt
crw-rw---- 1 root system 10, 10 Aug 26 2012 rhd11admin
crw-rw---- 1 root system 10, 5 Aug 26 2012 rhd2
crw-rw---- 1 root system 10, 7 Aug 26 2012 rhd3
crw-rw---- 1 root system 10, 4 Aug 26 2012 rhd4
crw-rw---- 2 root system 10, 1 Aug 26 2012 rhd5
crw-rw---- 1 root system 10, 2 Aug 26 2012 rhd6
crw-rw---- 1 root system 10, 3 Aug 26 2012 rhd8
crw-rw---- 1 root system 10, 6 Aug 26 2012 rhd9var
crw------- 1 root system 13, 2 Aug 26 2012 rhdisk0
crw-rw---- 1 grid asmadmin 13, 7 Sep 26 2012 rhdisk10
crw-rw---- 1 grid asmadmin 13, 13 Sep 26 2012 rhdisk11
crw-rw---- 1 grid asmadmin 13, 12 Sep 26 2012 rhdisk12
crw-rw---- 1 grid asmadmin 13, 14 Sep 26 2012 rhdisk13
crw-rw---- 1 grid asmadmin 13, 11 Sep 26 2012 rhdisk14
crw-rw---- 1 grid asmadmin 13, 3 Sep 26 2012 rhdisk15
crw------- 2 root system 13, 6 Aug 26 2012 rhdisk2
crw------- 1 root system 13, 4 Aug 26 2012 rhdisk3
crw------- 1 root system 13, 5 Aug 26 2012 rhdisk5
crw------- 1 root system 13, 8 Sep 19 2012 rhdisk6
crw------- 1 root system 13, 9 Sep 19 2012 rhdisk7
crw------- 1 root system 13, 1 Sep 19 2012 rhdisk8
crw------- 1 root system 13, 10 Sep 19 2012 rhdisk9
crw-rw---- 1 root system 10, 11 Aug 26 2012 rlg_dumplv
crw-rw---- 1 root system 10, 12 Aug 26 2012 rlivedump
crw-rw---- 1 root system 37, 1 Mar 05 18:10 rloglv00
crw-rw---- 1 root system 10, 13 Oct 18 2012 rmedios_lv
crw-rw-rw- 1 root system 38, 0 Sep 05 2012 rmt0
crw-rw-rw- 1 root system 38, 1 Sep 05 2012 rmt0.1
crw-rw-rw- 1 root system 38, 2 Sep 05 2012 rmt0.2
crw-rw-rw- 1 root system 38, 3 Sep 05 2012 rmt0.3
crw-rw-rw- 1 root system 38, 4 Sep 05 2012 rmt0.4
crw-rw-rw- 1 root system 38, 5 Sep 05 2012 rmt0.5
crw-rw-rw- 1 root system 38, 6 Sep 05 2012 rmt0.6
crw-rw-rw- 1 root system 38, 7 Sep 05 2012 rmt0.7
crw-rw-rw- 1 root system 38, 8 Sep 05 2012 rmt1
crw-rw-rw- 1 root system 38, 9 Sep 05 2012 rmt1.1
crw-rw-rw- 1 root system 38, 10 Sep 05 2012 rmt1.2
crw-rw-rw- 1 root system 38, 11 Sep 05 2012 rmt1.3
Page 531
FS CORRUPTO EN AIX ERRPT
crw-rw-rw- 1 root system 38, 12 Sep 05 2012 rmt1.4
crw-rw-rw- 1 root system 38, 13 Sep 05 2012 rmt1.5
crw-rw-rw- 1 root system 38, 14 Sep 05 2012 rmt1.6
crw-rw-rw- 1 root system 38, 15 Sep 05 2012 rmt1.7
crw-rw-rw- 1 root system 38, 16 Sep 05 2012 rmt2
crw-rw-rw- 1 root system 38, 17 Sep 05 2012 rmt2.1
crw-rw-rw- 1 root system 38, 18 Sep 05 2012 rmt2.2
crw-rw-rw- 1 root system 38, 19 Sep 05 2012 rmt2.3
crw-rw-rw- 1 root system 38, 20 Sep 05 2012 rmt2.4
crw-rw-rw- 1 root system 38, 21 Sep 05 2012 rmt2.5
crw-rw-rw- 1 root system 38, 22 Sep 05 2012 rmt2.6
crw-rw-rw- 1 root system 38, 23 Sep 05 2012 rmt2.7
crw-rw-rw- 1 root system 38, 24 Sep 05 2012 rmt3
crw-rw-rw- 1 root system 38, 25 Sep 05 2012 rmt3.1
crw-rw-rw- 1 root system 38, 26 Sep 05 2012 rmt3.2
crw-rw-rw- 1 root system 38, 27 Sep 05 2012 rmt3.3
crw-rw-rw- 1 root system 38, 28 Sep 05 2012 rmt3.4
crw-rw-rw- 1 root system 38, 29 Sep 05 2012 rmt3.5
crw-rw-rw- 1 root system 38, 30 Sep 05 2012 rmt3.6
crw-rw-rw- 1 root system 38, 31 Sep 05 2012 rmt3.7
crw-rw-rw- 1 root system 38, 32 Sep 05 2012 rmt4
crw-rw-rw- 1 root system 38, 33 Sep 05 2012 rmt4.1
crw-rw-rw- 1 root system 38, 34 Sep 05 2012 rmt4.2
crw-rw-rw- 1 root system 38, 35 Sep 05 2012 rmt4.3
crw-rw-rw- 1 root system 38, 36 Sep 05 2012 rmt4.4
crw-rw-rw- 1 root system 38, 37 Sep 05 2012 rmt4.5
crw-rw-rw- 1 root system 38, 38 Sep 05 2012 rmt4.6
crw-rw-rw- 1 root system 38, 39 Sep 05 2012 rmt4.7
crw-rw-rw- 1 root system 38, 40 Sep 05 2012 rmt5
crw-rw-rw- 1 root system 38, 41 Sep 05 2012 rmt5.1
crw-rw-rw- 1 root system 38, 42 Sep 05 2012 rmt5.2
crw-rw-rw- 1 root system 38, 43 Sep 05 2012 rmt5.3
crw-rw-rw- 1 root system 38, 44 Sep 05 2012 rmt5.4
crw-rw-rw- 1 root system 38, 45 Sep 05 2012 rmt5.5
crw-rw-rw- 1 root system 38, 46 Sep 05 2012 rmt5.6
crw-rw-rw- 1 root system 38, 47 Sep 05 2012 rmt5.7
crw-rw-rw- 1 root system 38, 48 Sep 05 2012 rmt6
crw-rw-rw- 1 root system 38, 49 Sep 05 2012 rmt6.1
crw-rw-rw- 1 root system 38, 50 Sep 05 2012 rmt6.2
crw-rw-rw- 1 root system 38, 51 Sep 05 2012 rmt6.3
crw-rw-rw- 1 root system 38, 52 Sep 05 2012 rmt6.4
crw-rw-rw- 1 root system 38, 53 Sep 05 2012 rmt6.5
crw-rw-rw- 1 root system 38, 54 Sep 05 2012 rmt6.6
crw-rw-rw- 1 root system 38, 55 Sep 05 2012 rmt6.7
crw-rw-rw- 1 root system 38, 56 Sep 05 2012 rmt7
crw-rw-rw- 1 root system 38, 57 Sep 05 2012 rmt7.1
Page 532
FS CORRUPTO EN AIX ERRPT
crw-rw-rw- 1 root system 38, 58 Sep 05 2012 rmt7.2
crw-rw-rw- 1 root system 38, 59 Sep 05 2012 rmt7.3
crw-rw-rw- 1 root system 38, 60 Sep 05 2012 rmt7.4
crw-rw-rw- 1 root system 38, 61 Sep 05 2012 rmt7.5
crw-rw-rw- 1 root system 38, 62 Sep 05 2012 rmt7.6
crw-rw-rw- 1 root system 38, 63 Sep 05 2012 rmt7.7
crw-rw-rw- 1 root system 38, 64 Sep 05 2012 rmt8
crw-rw-rw- 1 root system 38, 65 Sep 05 2012 rmt8.1
crw-rw-rw- 1 root system 38, 66 Sep 05 2012 rmt8.2
crw-rw-rw- 1 root system 38, 67 Sep 05 2012 rmt8.3
crw-rw-rw- 1 root system 38, 68 Sep 05 2012 rmt8.4
crw-rw-rw- 1 root system 38, 69 Sep 05 2012 rmt8.5
crw-rw-rw- 1 root system 38, 70 Sep 05 2012 rmt8.6
crw-rw-rw- 1 root system 38, 71 Sep 05 2012 rmt8.7
crw-rw-rw- 1 root system 38, 72 Sep 05 2012 rmt9
crw-rw-rw- 1 root system 38, 73 Sep 05 2012 rmt9.1
crw-rw-rw- 1 root system 38, 74 Sep 05 2012 rmt9.2
crw-rw-rw- 1 root system 38, 75 Sep 05 2012 rmt9.3
crw-rw-rw- 1 root system 38, 76 Sep 05 2012 rmt9.4
crw-rw-rw- 1 root system 38, 77 Sep 05 2012 rmt9.5
crw-rw-rw- 1 root system 38, 78 Sep 05 2012 rmt9.6
crw-rw-rw- 1 root system 38, 79 Sep 05 2012 rmt9.7
crw-rw---- 1 root system 10, 0 Aug 26 2012 rootvg
crw-rw---- 1 root system 36, 1 Mar 05 18:09 rpaging00
crw-rw---- 1 root system 10, 14 Oct 18 2012 rsrm_lv
crw-rw---- 1 root system 10, 16 Jul 22 15:54 rtra_lv
crw-rw-rw- 1 root system 14, 15 Aug 26 2012 sad
crw------- 1 root system 19, 0 Aug 26 2012 sfw0
crw------- 1 root system 19, 8 Aug 26 2012 sfwcomm0
crw------- 1 root system 19, 16 Aug 26 2012 sfwcomm1
crw------- 1 root system 19, 24 Aug 26 2012 sfwcomm2
crw-rw-rw- 1 root system 14, 16 Aug 26 2012 slog
crw-r--r-- 1 root system 2,151 Sep 19 2012 smart_gpfs
crw-rw-rw- 1 root system 14, 27 Aug 26 2012 spx
brw-rw---- 1 root system 10, 14 Oct 18 2012 srm_lv
crw-rw---- 1 root system 36, 0 Aug 26 2012 swap_vg
crw------- 1 root system 7, 0 Aug 26 2012 sysdump
crw------- 1 root system 7, 1 Aug 26 2012 sysdumpctl
crw------- 1 root system 7, 3 Aug 26 2012 sysdumpfile
crw------- 1 root system 7, 2 Aug 26 2012 sysdumpnull
crw-rw-rw- 1 root system 5, 0 Jul 22 15:57 systrace
crw-rw-rw- 1 root system 5, 1 Jul 22 15:57 systrctl
brw-rw---- 1 root system 10, 16 Jul 24 09:35 tra_lv
crw-rw-rw- 1 root system 1, 0 Jul 25 15:34 tty
crw-rw-rw- 1 root system 23, 0 Aug 26 2012 ttyp0
crw-rw-rw- 1 root system 23, 1 Aug 26 2012 ttyp1
Page 533
FS CORRUPTO EN AIX ERRPT
crw-rw-rw- 1 root system 23, 2 Aug 26 2012 ttyp2
crw-rw-rw- 1 root system 23, 3 Aug 26 2012 ttyp3
crw-rw-rw- 1 root system 23, 4 Aug 26 2012 ttyp4
crw-rw-rw- 1 root system 23, 5 Aug 26 2012 ttyp5
crw-rw-rw- 1 root system 23, 6 Aug 26 2012 ttyp6
crw-rw-rw- 1 root system 23, 7 Aug 26 2012 ttyp7
crw-rw-rw- 1 root system 23, 8 Aug 26 2012 ttyp8
crw-rw-rw- 1 root system 23, 9 Aug 26 2012 ttyp9
crw-rw-rw- 1 root system 23, 10 Aug 26 2012 ttypa
crw-rw-rw- 1 root system 23, 11 Aug 26 2012 ttypb
crw-rw-rw- 1 root system 23, 12 Aug 26 2012 ttypc
crw-rw-rw- 1 root system 23, 13 Aug 26 2012 ttypd
crw-rw-rw- 1 root system 23, 14 Aug 26 2012 ttype
crw-rw-rw- 1 root system 23, 15 Aug 26 2012 ttypf
crw-r--r-- 1 root system 35, 1 Sep 05 2012 urandom
crw------- 1 root system 11, 0 Aug 26 2012 vio0
crw-rw-rwT 1 root system 12, 0 Aug 26 2012 vscsi0
crw-rw-rwT 1 root system 12, 1 Aug 26 2012 vscsi1
crw------- 1 root system 17, 0 Sep 05 2012 vty0
drwxr-xr-x 2 root system 256 Aug 26 2012 xti
crw-rw-rw- 1 root system 2, 3 Aug 26 2012 zero
3:51:05 PM: Hernan Alejandro Schiavi: brw-rw---- 1 root system 37, 1 Mar 05 18:10 loglv00
3:51:08 PM: Hernan Alejandro Schiavi: del oracle_vg
3:51:23 PM: Hernan Alejandro Schiavi: ese es el que parece mal o que no tuvo acceso
3:51:38 PM: Henry Fabian Espinosa: umm
3:52:04 PM: Hernan Alejandro Schiavi: JFS2 LOG MAJOR/MINOR DEVICE NUMBER
0025 0001
3:52:09 PM: Hernan Alejandro Schiavi: 0025 a decimal es 37
3:52:20 PM: Hernan Alejandro Schiavi: 37, 1 que corresponde al loglv00, fijate ahi en el /dev
3:52:25 PM: Henry Fabian Espinosa: aj
3:52:26 PM: Henry Fabian Espinosa: sip
Page 534
FS CORRUPTO EN AIX ERRPT
Page 535
FS CORRUPTO EN AIX ERRPT
Page 536
FS CORRUPTO EN AIX ERRPT
Page 537
FS CORRUPTO EN AIX ERRPT
Page 538
FS CORRUPTO EN AIX ERRPT
Page 539
FS CORRUPTO EN AIX ERRPT
Page 540
FS CORRUPTO EN AIX ERRPT
3:51:05 PM: Hernan Alejandro Schiavi: brw-rw---- 1 root system 37, 1 Mar 05 18:10 loglv00
3:52:20 PM: Hernan Alejandro Schiavi: 37, 1 que corresponde al loglv00, fijate ahi en el /dev
Page 541
cambiar el log de un vg loglv00
http://www.opendebug.com/article/411534
cambiar el log filesystem del volume group loglv00
Page 542
RMC NO FOUND
/usr/sbin/rsct/bin/rmcctrl -z
/usr/sbin/rsct/bin/rmcctrl -A
/usr/sbin/rsct/bin/rmcctrl -p
Reiniciar el demonio del RMC
dlpar no funciona
Page 543
error 0118 pcmpath SC_DISK_ERR9
LABEL: SC_DISK_ERR9
IDENTIFIER: B0EE9AF5
Date/Time: Mon Jul 22 15:51:12 COT 2013
Sequence Number: 9857020
Machine Id: 00F6D5514C00
Node Id: coboggdoprd02
Class: S
Type: TEMP
WPAR: Global
Resource Name: hdisk3
Description
REQUESTED OPERATION CANNOT BE PERFORMED
Probable Causes
MEDIA
User Causes
MEDIA DEFECTIVE
RESOURCE NOT AVAILABLE
Recommended Actions
FOR REMOVABLE MEDIA, CHANGE MEDIA AND RETRY
PERFORM PROBLEM DETERMINATION PROCEDURES
Failure Causes
MEDIA
DISK DRIVE
Recommended Actions
FOR REMOVABLE MEDIA, CHANGE MEDIA AND RETRY
PERFORM PROBLEM DETERMINATION PROCEDURES
Detail Data
PATH ID
1
SENSE DATA
0A00 2800 0000 0007 0000 0104 0000 0000 0000 0000 0000 0000 0118 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0001 08CB 0002 2D40 0000 0000 0000 0000 0000 0000 0000 0003 0000
0000 003D 001D
Page 544
error 0118 pcmpath SC_DISK_ERR9
Es error de reserva
SC_DISK_ERR9 y SENSE DATA 0118
error de reserva en disco
Solucion
varyonvg -bu rootvg
varyonvg -bu swapvg Mirar si la paginacin est libre, si es as darle swapoff a la espacio de paginacion y varyonvg -bu swapvg
Si la paginacion no puede bajarse darle lo siguiente:
/home/ibmadmhe/forceopen /dev/hdisk0 (disco del swap_vg)
0A00 2800 0000 0007 0000 0104 0000 0000 0000 0000 0000 0000 0118 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0001 08CB 0002 2D40 0000 0000 0000 0000 0000 0000 0000 0003 0000
Page 545
error 0118 pcmpath SC_DISK_ERR9
Mirar si la paginacin est libre, si es as darle swapoff a la espacio de paginacion y varyonvg -bu swapvg
Si la paginacion no puede bajarse darle lo siguiente:
/home/ibmadmhe/forceopen /dev/hdisk0 (disco del swap_vg)
Page 546
error 0118 pcmpath SC_DISK_ERR4
LABEL: SC_DISK_ERR4 POSBILE MAS ERROR DE STORAGE que de aix escalar de una
IDENTIFIER: DCB47997
Date/Time: Wed Jul 31 11:35:08 GMT-05:00 2013
LABEL: SC_DISK_ERR4
Machine Id: 00F6D5514C00
Node Id: xd1ds01
Class: H
Type: TEMP
WPAR: Global
Resource Name: hdisk3
Resource Class:
Resource Type:
Location:
VPD:
Manufacturer................IBM
Machine Type and Model......2107900
Serial Number...............75P51414055
EC Level....................3.70
Device Specific.(Z0)........10
Device Specific.(Z1)........0003
Device Specific.(Z2)........075
Device Specific.(Z3)........21407
Device Specific.(Z4)........08
Device Specific.(Z5)........00
Description
DISK OPERATION ERROR
Probable Causes
MEDIA
DASD DEVICE
User Causes
MEDIA DEFECTIVE
Recommended Actions
FOR REMOVABLE MEDIA, CHANGE MEDIA AND RETRY
PERFORM PROBLEM DETERMINATION PROCEDURES
Failure Causes
MEDIA
DISK DRIVE
Recommended Actions
FOR REMOVABLE MEDIA, CHANGE MEDIA AND RETRY
Page 547
error 0118 pcmpath SC_DISK_ERR4
PERFORM PROBLEM DETERMINATION PROCEDURES
Detail Data
PATH ID
1
SENSE DATA
0A00 2A00 0002 2660 0000 2004 0000 0000 0000 0000 0000 0000 0118 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0003 7516 000D F000 0000 0000 0000 0000 0000 0000 0000 0003 0000
0000 003D 001D
Page 548
error 0118 pcmpath SC_DISK_ERR4
POSBILE MAS ERROR DE STORAGE que de aix escalar de una
Page 549
error LOG I-O ERROR C1348779
IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION
C1348779 0731113513 I O SYSJ2 LOG I/O ERROR
ver rojo
---------------------------------------------------------------------------
LABEL: J2_LOG_EIO
IDENTIFIER: C1348779
Date/Time: Wed Jul 31 11:35:23 COT 2013
Sequence Number: 9992252
Machine Id: 00F6D5514C00
Node Id: coboggdoprd02
Class: O
Type: INFO
WPAR: Global
Resource Name: SYSJ2
Description
LOG I/O ERROR
Probable Causes
ADAPTER HARDWARE OR MICROCODE
DISK DRIVE HARDWARE OR MICROCODE
SOFTWARE DEVICE DRIVER
STORAGE CABLE LOOSE, DEFECTIVE, OR UNTERMINATED
Recommended Actions
CHECK CABLES AND THEIR CONNECTIONS
INSTALL LATEST ADAPTER AND DRIVE MICROCODE
INSTALL LATEST STORAGE DEVICE DRIVERS
IF PROBLEM PERSISTS, CONTACT APPROPRIATE SERVICE REPRESENTATIVE
Detail Data
JFS2 LOG MAJOR/MINOR DEVICE NUMBER
0025 0001
ERROR CODE
0000 0005
BUF STRUCTURE B_FLAGS
0404 0404
BLOCK NUMBER
0006 4620
Page 550
error LOG I-O ERROR C1348779
convertir el 25 que est en hexa a decimal
25 en hexa es 37
root@coboggdoprd02:/dev# ls -lrt |grep 37
crw-rw---- 1 root system 37, 0 Aug 26 2012 oracle_vg
crw------- 1 root system 37, 0 Aug 26 2012 __vg37
crw-rw-rw- 1 root system 38, 37 Sep 05 2012 rmt4.5
crw-rw---- 1 root system 37, 1 Mar 05 18:10 rloglv00
crw-rw---- 1 root system 37, 2 Mar 05 18:10 rfslv00
brw-rw---- 1 root system 37, 1 Mar 05 18:10 loglv00
brw-rw---- 1 root system 37, 2 Mar 05 18:10 fslv00
root@coboggdoprd02:/dev# lsvg -l oracle_vg
oracle_vg:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
loglv00 jfs2log 1 1 1 open/syncd N/A
fslv00 jfs2 100 100 1 open/syncd /oracle
Hay que reconstruir el log fs
http://www.opendebug.com/article/411534
cambiar el log filesystem del volume group
Page 551
consola desde el vio
mkvt -id 3
consola desde el vioserver
Page 552
reconocer hbas y discos en suse
160 cd /opt/hp/hp_fibreutils/
161 hp_rescan
162 hp_rescan -a
lsscsi
vgscan
vgchange -a y
mount -a
discos y fibras SUSE storage HP
Page 553
shell request failed on channel
shell request failed on channel 0
Esto pasa por que el usuario esta con muchos procesos
Page 554
ADD lpar standalone a nim
10:16:38 AM: Jorge Eduardo Ocampo Arango: ============================EN EL CLIENTE ===========
Se ingresa al servidor, se coloca la direccion del NIM en el hosts
se modifica el /etc/services
las siguientes lineas se comentan
/
#nimsh 3901/udp # NIM Service Handler
#nimaux 3902/tcp # NIMsh Auxiliary Port
#nimaux 3902/udp # NIMsh Auxiliary Port
y se colocan de ultimo cambiando el puerto al que se conectan
nimsh 39011/tcp # NIM Service Handler
nimsh 39011/udp # NIM Service Handler
nimaux 39022/tcp # NIMsh Auxiliary Port
nimaux 39022/udp # NIMsh Auxiliary Port
Se verifica que este instalado en nim
lslpp -l | grep -i nim.client
Se verifica el servicio de nimsh
lssrc -s nimsh
Subsystem Group PID Status
nimsh nimclient 10813664 active
Se reinicia el servicio si esta con status inoperative
sudo stopsrc -s nimsh; sudo startsrc -s nimsh
despues de que se cree el servidor en el nim como recurso, se debe ejecutar en la lpar
sudo niminit -a name=CPDEV_admon -a master=nimserver -a pif_name=en4 -a platform=chrp -a cable_type=N/A -a connect=nimsh
donde CPDEV_admon es el cliente como esta configurado en el nim
donde master=nimserver es el nombre del master
Page 555
ADD lpar standalone a nim
#N/A
10:16:58 AM: Jorge Eduardo Ocampo Arango: EN el NIM
para hacer el backup se ejecuta :
nim -o define -t mksysb -a source=hdvdev001 -a server=master -a mk_image=yes -a location=/archive/hdvdev001_20121130 mksysb_hdvdev
donde source=cliente server=master
10:17:10 AM: Jorge Eduardo Ocampo Arango: Para crear un recurso con los archivos a excluir
sudo su - -c nim -o define -a verbose=2 -t exclude_files -a server=master -a location=/export/nim/excludehdvlcp001 exclude_hdvlcp001
sudo su - -c nim -o define -t mksysb -a source=hdvlcp001 -a server=master -a mk_image=yes -a location=/archive/hdvlcp001_20130712 -a exclude_files=exclude_hdvlcp001 mksysb_hdvlcp001_20130712
Page 556
ADD lpar standalone a nim
10:16:38 AM: Jorge Eduardo Ocampo Arango: ============================EN EL CLIENTE ===========
sudo niminit -a name=CPDEV_admon -a master=nimserver -a pif_name=en4 -a platform=chrp -a cable_type=N/A -a connect=nimsh
Page 557
ADD lpar standalone a nim
nim -o define -t mksysb -a source=hdvdev001 -a server=master -a mk_image=yes -a location=/archive/hdvdev001_20121130 mksysb_hdvdev
10:17:10 AM: Jorge Eduardo Ocampo Arango: Para crear un recurso con los archivos a excluir
sudo su - -c nim -o define -a verbose=2 -t exclude_files -a server=master -a location=/export/nim/excludehdvlcp001 exclude_hdvlcp001
sudo su - -c nim -o define -t mksysb -a source=hdvlcp001 -a server=master -a mk_image=yes -a location=/archive/hdvlcp001_20130712 -a exclude_files=exclude_hdvlcp001 mksysb_hdvlcp001_20130712
Page 558
ADD lpar standalone a nim
Page 559
ADD lpar standalone a nim
sudo su - -c nim -o define -t mksysb -a source=hdvlcp001 -a server=master -a mk_image=yes -a location=/archive/hdvlcp001_20130712 -a exclude_files=exclude_hdvlcp001 mksysb_hdvlcp001_20130712
Page 560
Crear SEA DESDE 0
1. Tres interfacez de red un link aggregation y su backup
2. Creamos el link agreggation por smitty dos interfacez y el backup la tercera interfaz mode 82dab
3. Creamos el adaptador truncal virtual desde la hmc habilitamos los dos chulitos y dejamos las vlan que necesitamos usar.
4. Debemos tener VLANS gateway y mascaras
5. Creamos la SEA como es un solo vioserver no se necesita control channel
6. si hay 2 vioserver se debe crear el control channel
Page 561
Crear SEA DESDE 0
2. Creamos el link agreggation por smitty dos interfacez y el backup la tercera interfaz mode 82dab
3. Creamos el adaptador truncal virtual desde la hmc habilitamos los dos chulitos y dejamos las vlan que necesitamos usar.
Page 562
excluir files mksysb nim
excluir files mksysb nim
sudo nim -o define -t exclude_files -a server=master -a location=/administrador/exclude1 exclude1
sudo nim -o define -t mksysb -a source=coibmbwpaix01 -a server=master -a mk_image=yes -a location=/export/nim/images/coibm
Page 563
excluir files mksysb nim
sudo nim -o define -t exclude_files -a server=master -a location=/administrador/exclude1 exclude1
sudo nim -o define -t mksysb -a source=coibmbwpaix01 -a server=master -a mk_image=yes -a location=/export/nim/images/coibm mages/coibmbwpaix01 -a exclude_files=exclude1 coibmbwpaix01_BK
Page 564
excluir files mksysb nim
mages/coibmbwpaix01 -a exclude_files=exclude1 coibmbwpaix01_BK
Page 565
Live partition mobility
Live partition mobility
lsnportlogin -m Server-9117-MMB-SN000000 --filter lpar_ids=2
chnportlogin -m Server-9117-MMB-SN000000 -o login --id 2
Les decimos a storage que nos zonifiquen las wwpns fantasmas
Pasamos el validate
Le decimos a sap que haga el hardware key para reactivar la licencia
Garantizar que en storage vean los discos todas las wwpns incluyendo las fantasmas.
Page 566
Live partition mobility
Para que vean las wwpns fantasmas
Ver las wwpns fantasma
Para que storage las vean
Garantizar que en storage vean los discos todas las wwpns incluyendo las fantasmas.
Page 567
Live partition mobility
Page 568
PARCHAR POR NIM
PARCHAR POR NIM
quiubvo
2:58:53 PM: Henry Fabian Espinosa: home
2:58:59 PM: Henry Fabian Espinosa: supe supe
2:59:06 PM: Henry Fabian Espinosa: que hay cambio de nutresa?
2:59:11 PM: Henry Fabian Espinosa: maana cierto
2:59:53 PM: Carlos Andres Munoz Loaiza: sisas pero es solo un reboot
2:59:57 PM: Carlos Andres Munoz Loaiza: ahi hay disco alterno
3:00:04 PM: Carlos Andres Munoz Loaiza: asi que fresco
3:00:07 PM: Henry Fabian Espinosa: ah listo
3:00:14 PM: Henry Fabian Espinosa: entonces voy a hacer los previos ya
3:00:15 PM: Carlos Andres Munoz Loaiza: ya genere el disco alterno
3:00:24 PM: Carlos Andres Munoz Loaiza: 11.0.2.156
3:00:55 PM: Henry Fabian Espinosa: osea saco el alt_disk_copy o ya lo hizo
3:01:05 PM: Henry Fabian Espinosa: bueno fresco yo lo hago
3:01:07 PM: Henry Fabian Espinosa: hagale
3:01:10 PM: Henry Fabian Espinosa: relajado
3:01:15 PM: Henry Fabian Espinosa: yo hago eso maana
3:06:17 PM: Carlos Andres Munoz Loaiza: y si quieya lo hice
3:06:21 PM: Carlos Andres Munoz Loaiza: ya lo hice
3:06:44 PM: Henry Fabian Espinosa: de todas formas ya pedi caso
3:06:51 PM: Henry Fabian Espinosa: voy a sacar el cfg2html
3:07:08 PM: Henry Fabian Espinosa: a entonces ya quedo el alt_disk_copy unicamente ya saco el cfg2html y reinicio
3:07:11 PM: Henry Fabian Espinosa: y sale pa pintura
3:07:15 PM: Henry Fabian Espinosa: hagel pues mkvdev -vdev migncpor2_lv -vadapter vhost17 -dev migncerpno2
3:07:23 PM: Carlos Andres Munoz Loaiza: habria que parchar
3:07:25 PM: Carlos Andres Munoz Loaiza: pero eso es de 30 min
3:07:49 PM: Henry Fabian Espinosa: ah pense que ya habia parchado con alt_disk__copy
3:08:04 PM: Henry Fabian Espinosa: ah lo vamos a hacer en vivo
3:08:17 PM: Henry Fabian Espinosa: y con el backup al disco
3:09:16 PM: Henry Fabian Espinosa: hagale relajese
3:09:32 PM: Carlos Andres Munoz Loaiza: listones
3:09:32 PM: Henry Fabian Espinosa: eso es pelquiando sebas
3:09:40 PM: Carlos Andres Munoz Loaiza: desde el nim lanza el parchado
3:09:50 PM: Henry Fabian Espinosa: uy no lo he hecho
3:09:52 PM: Henry Fabian Espinosa: asi
3:10:01 PM: Carlos Andres Munoz Loaiza: ahh fresco
3:10:03 PM: Carlos Andres Munoz Loaiza: ya le muestro
3:10:09 PM: Carlos Andres Munoz Loaiza: conectese al 11.0.2.156
3:10:14 PM: Carlos Andres Munoz Loaiza: ese es el nim de Nutresa
3:11:20 PM: Henry Fabian Espinosa: listo
3:11:26 PM: Henry Fabian Espinosa: hay toy
3:11:31 PM: Carlos Andres Munoz Loaiza:
3:11:31 PM: Carlos Andres Munoz Loaiza:
3:11:31 PM: Carlos Andres Munoz Loaiza:
Page 569
PARCHAR POR NIM
3:11:42 PM: Carlos Andres Munoz Loaiza: lsnim -t standalone para listar las mquinas
3:12:08 PM: Henry Fabian Espinosa: ibmadmhe@snchnimsrv:/home/ibmadmhe>sudo lsnim -t standalone
ncpor063 machines standalone
ncscm012 machines standalone
snchpru machines standalone
ncbi014 machines standalone
ncmsg023 machines standalone
ncboe011 machines standalone
NCBO011 machines standalone
NCBO021 machines standalone
ncerp073 machines standalone
ncerp012 machines standalone
ncgrc011 machines standalone
NCERP011 machines standalone
ncerpnodo1 machines standalone
ncerpnodo2 machines standalone
ncbo043 machines standalone
Lotus_test machines standalone
nverp011 machines standalone
ncscm011 machines standalone
ncsmg011 machines standalone
ncpor011 machines standalone
ncpi011 machines standalone
ncnpd012 machines standalone
ncpor012 machines standalone
ncppm011 machines standalone
ncmsg013 machines standalone
ncdsd01 machines standalone
NCBOS033 machines standalone
NCBOS053 machines standalone
NCBOS011 machines standalone
PISSIS_N1 machines standalone
nctsmsrv machines standalone
ncpi023 machines standalone
nciprx013 machines standalone
nciprx023 machines standalone
ncbos011 machines standalone
tivolisdc03 machines standalone
NCBO033 machines standalone
snchsrvtsm machines standalone
NCPOR023_NEW machines standalone
NCPOR013_NEW machines standalone
NCPOR033_NEW machines standalone
ncsdir01 machines standalone
ncbinodo2 machines standalone
srvsoomnibus machines standalone
Page 570
PARCHAR POR NIM
NCFCMBKP1 machines standalone
ncpor043-clon machines standalone
ncpor043 machines standalone
NCDS011 machines standalone
NCDBE053 machines standalone
NCPI011-NEW machines standalone
nverp033 machines standalone
ncpor043-cnt machines standalone
HATEST2 machines standalone
HATEST1 machines standalone
TWSSRV_NEW machines standalone
ncbinodo1 machines standalone
NCSOL01 machines standalone
nverp023 machines standalone
ncerp083 machines standalone
ncds013 machines standalone
ncds023 machines standalone
ncpici13nodo1 machines standalone
ncdbe013 machines standalone
ncpornodo2 machines standalone
ncboe023 machines standalone
ncnpd013 machines standalone
ncscm013 machines standalone
ncpor033 machines standalone
3:12:18 PM: Carlos Andres Munoz Loaiza: ping ncscm013
3:12:30 PM: Henry Fabian Espinosa: ibmadmhe@snchnimsrv:/home/ibmadmhe>ping ncscm013
PING ncscm013: (11.0.2.167): 56 data bytes
64 bytes from 11.0.2.167: icmp_seq=0 ttl=255 time=0 ms
64 bytes from 11.0.2.167: icmp_seq=1 ttl=255 time=0 ms
64 bytes from 11.0.2.167: icmp_seq=2 ttl=255 time=0 ms
^C
3:12:41 PM: Carlos Andres Munoz Loaiza: lsnim -l ncscm013
3:13:05 PM: Henry Fabian Espinosa: ibmadmhe@snchnimsrv:/home/ibmadmhe>sudo lsnim -l ncscm013
ncscm013:
class = machines
type = standalone
connect = nimsh
platform = chrp
netboot_kernel = 64
if1 = master_net NCSCM013 C249F9377F19 ent0
cable_type1 = N/A
Cstate = ready for a NIM operation
prev_state = not running
Mstate = currently running
Page 571
PARCHAR POR NIM
cpuid = 00CC92024C00
3:13:20 PM: Carlos Andres Munoz Loaiza: nim -o lslpp ncscm013
3:13:29 PM: Carlos Andres Munoz Loaiza: para ver si le deja hacer operaciones
3:13:53 PM: Henry Fabian Espinosa: ibmadmhe@snchnimsrv:/home/ibmadmhe>sudo nim -o lslpp ncscm013
Fileset Level State Description
----------------------------------------------------------------------------
Path: /usr/lib/objrepos
466de7156d65d65bb24bf86a472a5b46
5.5.0.2 COMMITTED ISMP installed entry
Atape.driver 12.5.2.0 COMMITTED IBM AIX Enhanced Tape and
Medium Changer Device Driver
Director.install.msg.DE_DE
6.3.2.0 COMMITTED installation NLS catalogs for
AIX OS
Director.install.msg.ES_ES
6.3.2.0 COMMITTED installation NLS catalogs for
AIX OS
Director.install.msg.FR_FR
6.3.2.0 COMMITTED installation NLS catalogs for
AIX OS
Director.install.msg.IT_IT
6.3.2.0 COMMITTED installation NLS catalogs for
AIX OS
Director.install.msg.JA_JP
6.3.2.0 COMMITTED installation NLS catalogs for
AIX OS
Director.install.msg.Ja_JP
6.3.2.0 COMMITTED installation NLS catalogs for
3:14:08 PM: Henry Fabian Espinosa: yo le puedo mandar cualquier comando
3:14:10 PM: Carlos Andres Munoz Loaiza: listo
3:14:12 PM: Carlos Andres Munoz Loaiza: esta ok
3:14:50 PM: Henry Fabian Espinosa: y anton
3:15:01 PM: Carlos Andres Munoz Loaiza: ok
3:15:04 PM: Carlos Andres Munoz Loaiza: sntonces
3:15:55 PM: Henry Fabian Espinosa: .
3:16:24 PM: Carlos Andres Munoz Loaiza: lsnim -t mksysb
3:16:39 PM: Carlos Andres Munoz Loaiza: y busque si existe algo del ncscm013
3:17:02 PM: Henry Fabian Espinosa: ibmadmhe@snchnimsrv:/home/ibmadmhe>sudo lsnim -t mksysb
ncpici13nodo1mksysb resources mksysb
ncdbe013mksysb resources mksysb
nverp011mksysb resources mksysb
ncbinodo1mksysb resources mksysb
ncnpd013mksysb resources mksysb
ncerpnodo2mksysb resources mksysb
Page 572
PARCHAR POR NIM
Lotus_testmksysb resources mksysb
SAP71 resources mksysb
AIX71TL2SP1 resources mksysb
ncscm013mksysb resources mksysb
ncpor033mksysb resources mksysb
ncpor043-clonmksysb resources mksysb
ncpor043mksysb resources mksysb
ncboe023mksysb resources mksysb
ncmsg013mksysb resources mksysb
snchsrvtsmmksysb resources mksysb
ncerp012mksysb resources mksysb
ibmadmhe@snchnimsrv:/home/ibmadmhe>
3:17:08 PM: Henry Fabian Espinosa: ncscm013mksysb resources mksysb
3:17:10 PM: Carlos Andres Munoz Loaiza: ahi hay uno
3:17:20 PM: Carlos Andres Munoz Loaiza: remuevalo de la siguiente manera
3:17:29 PM: Carlos Andres Munoz Loaiza: nim -o remove nombre_mksysb
3:17:31 PM: Carlos Andres Munoz Loaiza: pero antes de
3:17:36 PM: Carlos Andres Munoz Loaiza: lsnim -l ncscm013mksysb
3:17:52 PM: Henry Fabian Espinosa: ibmadmhe@snchnimsrv:/home/ibmadmhe>sudo lsnim -l ncscm013mksysb
ncscm013mksysb:
class = resources
type = mksysb
arch = power
Rstate = ready for use
prev_state = unavailable for use
location = /export/nim/images/ncscm013.mksysb
version = 6
release = 1
mod = 7
oslevel_r = 6100-07
alloc_count = 0
server = master
creation_date = Fri May 31 18:48:12 2013
source_image = ncscm013
3:18:05 PM: Carlos Andres Munoz Loaiza: ok
3:18:12 PM: Carlos Andres Munoz Loaiza: eliminelo con esto
3:18:13 PM: Henry Fabian Espinosa: ahora si lo puedo borrar
3:18:20 PM: Carlos Andres Munoz Loaiza: nim -o remove ncscm013mksysb
3:18:27 PM: Carlos Andres Munoz Loaiza: y luego borra el archivo
3:18:48 PM: Henry Fabian Espinosa: /export/nim/images/ncscm013.mksysb
3:19:00 PM: Carlos Andres Munoz Loaiza: si
3:19:00 PM: Carlos Andres Munoz Loaiza: ese
3:19:09 PM: Henry Fabian Espinosa: listo
3:19:19 PM: Carlos Andres Munoz Loaiza: ya elimino la definicion?
Page 573
PARCHAR POR NIM
3:19:26 PM: Henry Fabian Espinosa: si tambein
3:19:29 PM: Carlos Andres Munoz Loaiza: y el archivo?
3:19:30 PM: Carlos Andres Munoz Loaiza: ok
3:19:33 PM: Henry Fabian Espinosa: tambkien
3:19:37 PM: Carlos Andres Munoz Loaiza: ahora generelo asi
3:19:38 PM: Henry Fabian Espinosa: ibmadmhe@snchnimsrv:/home/ibmadmhe>sudo nim -o remove ncscm013mksysb
ibmadmhe@snchnimsrv:/home/ibmadmhe>sudo ls -ld /export/nim/images/ncscm013.mksysb
-rw-r--r-- 1 root system 7907686400 May 31 18:47 /export/nim/images/ncscm013.mksysb
ibmadmhe@snchnimsrv:/home/ibmadmhe>sudoi
ibmadmhe@snchnimsrv:/home/ibmadmhe>sudo rm -rf /export/nim/images/ncscm013.mksysb
3:20:10 PM: Carlos Andres Munoz Loaiza: nim -o define -t mksysb -a server=master -a location=/export/nim/images/ncscm013.mksysb -a mk_image=yes -a source=ncscm013 ncscm013mksysb
3:20:32 PM: Henry Fabian Espinosa: hay vamos a crear un mksysb de la maquina
3:20:34 PM: Henry Fabian Espinosa: correcto
3:20:45 PM: Carlos Andres Munoz Loaiza: si
3:20:51 PM: Henry Fabian Espinosa: ya hay va
3:20:53 PM: Carlos Andres Munoz Loaiza: desde el nim
3:20:57 PM: Henry Fabian Espinosa: uy severo
3:20:58 PM: Carlos Andres Munoz Loaiza: ok
3:21:02 PM: Carlos Andres Munoz Loaiza: fcil no?
3:21:07 PM: Henry Fabian Espinosa: sisas
3:21:09 PM: Henry Fabian Espinosa: re facil
3:21:15 PM: Carlos Andres Munoz Loaiza:
3:21:35 PM: Henry Fabian Espinosa: bueno ya le aviso cuando termine
3:21:59 PM: Henry Fabian Espinosa: osea ya tenemos dos backups
3:22:06 PM: Henry Fabian Espinosa: 1 el que carlitos ya saco
3:22:07 PM: Carlos Andres Munoz Loaiza: si
3:22:10 PM: Henry Fabian Espinosa: y este
3:22:14 PM: Carlos Andres Munoz Loaiza: -si
3:22:18 PM: Henry Fabian Espinosa: ah severo
3:23:20 PM: Carlos Andres Munoz Loaiza: ya con eso quedamos tranquilos
3:23:26 PM: Carlos Andres Munoz Loaiza: y para parchar es lo siguiente
3:23:48 PM: Carlos Andres Munoz Loaiza: nim -o cust -a lpp_source=618lpp_res -a fixes="update_all" -a installp_flags=acNgX -a show_progress=yes -a accept_licenses=yes ncscm013
3:23:58 PM: Carlos Andres Munoz Loaiza: y sale
3:24:00 PM: Carlos Andres Munoz Loaiza: ojooooooooooooooooooooo
3:24:14 PM: Carlos Andres Munoz Loaiza: con este detalle despues que parche
3:24:25 PM: Henry Fabian Espinosa: eso lo ejecuto cuando vaya a parchar
3:24:30 PM: Carlos Andres Munoz Loaiza: si
3:24:35 PM: Henry Fabian Espinosa: osea cuando bajen los servicios de sap
3:24:42 PM: Carlos Andres Munoz Loaiza: si
3:24:45 PM: Henry Fabian Espinosa: ah ya
3:24:48 PM: Henry Fabian Espinosa: y despues reinicio
3:25:03 PM: Carlos Andres Munoz Loaiza: /ssi
3:25:06 PM: Carlos Andres Munoz Loaiza: pero ojoooooooooooooooooooo
3:25:09 PM: Carlos Andres Munoz Loaiza: con este detalle
3:25:10 PM: Carlos Andres Munoz Loaiza: bash-4.2# grep nimsh /etc/services
Page 574
PARCHAR POR NIM
#nimsh 3901/tcp # NIM Service Handler
#nimsh 3901/udp # NIM Service Handler
nimsh 39011/tcp # NIM Service Handler
nimsh 39011/udp # NIM Service Handler
3:25:30 PM: Carlos Andres Munoz Loaiza: cuando ud parcha el le activa el nimsh en el 3901
3:25:40 PM: Henry Fabian Espinosa: ah si
3:25:45 PM: Henry Fabian Espinosa: y ese puerto es de sap
3:25:48 PM: Henry Fabian Espinosa: si o que
3:25:59 PM: Henry Fabian Espinosa: osea pasos
3:26:03 PM: Carlos Andres Munoz Loaiza: bash-4.2# grep nimsh /etc/services
#nimsh 3901/tcp # NIM Service Handler
#nimsh 3901/udp # NIM Service Handler
nimsh 39011/tcp # NIM Service Handler
nimsh 39011/udp # NIM Service Handler
bash-4.2# grep nimaux /etc/services
#nimaux 3902/tcp # NIMsh Auxiliary Port
#nimaux 3902/udp # NIMsh Auxiliary Port
nimaux 39022/tcp # NIMsh Auxiliary Port
nimaux 39022/udp # NIMsh Auxiliary Port
3:26:11 PM: Carlos Andres Munoz Loaiza: asi debe quedar en el /etc/services
3:26:18 PM: Carlos Andres Munoz Loaiza: despues de que parche
3:26:21 PM: Carlos Andres Munoz Loaiza: si no , lo edita
3:26:26 PM: Carlos Andres Munoz Loaiza: y reinicia
3:26:29 PM: Henry Fabian Espinosa: ah ok
3:26:31 PM: Henry Fabian Espinosa: vale
3:26:35 PM: Henry Fabian Espinosa: debe quedar como me indica
3:26:37 PM: Carlos Andres Munoz Loaiza:
3:26:40 PM: Carlos Andres Munoz Loaiza: si
3:26:41 PM: Henry Fabian Espinosa: y sale
3:26:44 PM: Henry Fabian Espinosa: vale
3:26:46 PM: Henry Fabian Espinosa: algo mas
3:26:48 PM: Henry Fabian Espinosa: no
3:26:53 PM: Carlos Andres Munoz Loaiza: no
3:26:57 PM: Henry Fabian Espinosa: uy re breve
3:26:59 PM: Carlos Andres Munoz Loaiza: ya le termino el backup?
3:27:01 PM: Henry Fabian Espinosa: sisas
3:27:07 PM: Henry Fabian Espinosa: ibmadmhe@snchnimsrv:/home/ibmadmhe>sudo nim -o define -t mksysb -a server=master -a location=/export/nim/images/ncscm013.mksysb -a mk_image=yes -a source=ncscm013 ncscm013mksysb
+---------------------------------------------------------------------+
System Backup Image Space Information
(Sizes are displayed in 1024-byte blocks.)
+---------------------------------------------------------------------+
Required = 11350005 (11084 MB) Available = 20329752 (19854 MB)
Page 575
PARCHAR POR NIM
Creating information file (/image.data) for rootvg.
Creating list of files to back up.
Backing up 118242 files.........................
118242 of 118242 files (100%)
0512-038 savevg: Backup Completed Successfully.
3:27:23 PM: Carlos Andres Munoz Loaiza: s olosto
3:27:47 PM: Henry Fabian Espinosa: uy gracias
3:27:50 PM: Henry Fabian Espinosa: carlitos
3:27:52 PM: Henry Fabian Espinosa: severo
3:27:59 PM: Henry Fabian Espinosa: voy a hacer eso a la proxima
3:28:01 PM: Henry Fabian Espinosa: pa no oensar
3:28:05 PM: Henry Fabian Espinosa: ajjajajajaja
Page 576
PARCHAR POR NIM
3:07:08 PM: Henry Fabian Espinosa: a entonces ya quedo el alt_disk_copy unicamente ya saco el cfg2html y reinicio
Page 577
PARCHAR POR NIM
3:12:08 PM: Henry Fabian Espinosa: ibmadmhe@snchnimsrv:/home/ibmadmhe>sudo lsnim -t standalone
Page 578
PARCHAR POR NIM
3:12:30 PM: Henry Fabian Espinosa: ibmadmhe@snchnimsrv:/home/ibmadmhe>ping ncscm013
3:13:05 PM: Henry Fabian Espinosa: ibmadmhe@snchnimsrv:/home/ibmadmhe>sudo lsnim -l ncscm013
Page 579
PARCHAR POR NIM
3:13:53 PM: Henry Fabian Espinosa: ibmadmhe@snchnimsrv:/home/ibmadmhe>sudo nim -o lslpp ncscm013
3:17:02 PM: Henry Fabian Espinosa: ibmadmhe@snchnimsrv:/home/ibmadmhe>sudo lsnim -t mksysb
Page 580
PARCHAR POR NIM
3:17:52 PM: Henry Fabian Espinosa: ibmadmhe@snchnimsrv:/home/ibmadmhe>sudo lsnim -l ncscm013mksysb
Page 581
PARCHAR POR NIM
3:19:38 PM: Henry Fabian Espinosa: ibmadmhe@snchnimsrv:/home/ibmadmhe>sudo nim -o remove ncscm013mksysb
ibmadmhe@snchnimsrv:/home/ibmadmhe>sudo ls -ld /export/nim/images/ncscm013.mksysb
-rw-r--r-- 1 root system 7907686400 May 31 18:47 /export/nim/images/ncscm013.mksysb
ibmadmhe@snchnimsrv:/home/ibmadmhe>sudo rm -rf /export/nim/images/ncscm013.mksysb
3:20:10 PM: Carlos Andres Munoz Loaiza: nim -o define -t mksysb -a server=master -a location=/export/nim/images/ncscm013.mksysb -a mk_image=yes -a source=ncscm013 ncscm013mksysb
3:23:48 PM: Carlos Andres Munoz Loaiza: nim -o cust -a lpp_source=618lpp_res -a fixes="update_all" -a installp_flags=acNgX -a show_progress=yes -a accept_licenses=yes ncscm013
Page 582
PARCHAR POR NIM
3:25:30 PM: Carlos Andres Munoz Loaiza: cuando ud parcha el le activa el nimsh en el 3901
3:27:07 PM: Henry Fabian Espinosa: ibmadmhe@snchnimsrv:/home/ibmadmhe>sudo nim -o define -t mksysb -a server=master -a location=/export/nim/images/ncscm013.mksysb -a mk_image=yes -a source=ncscm013 ncscm013mksysb
Page 583
PARCHAR POR NIM
Page 584
PARCHAR POR NIM
Page 585
PARCHAR POR NIM
Page 586
PARCHAR POR NIM
Page 587
PARCHAR POR NIM
Page 588
PARCHAR POR NIM
Page 589
PARCHAR POR NIM
3:20:10 PM: Carlos Andres Munoz Loaiza: nim -o define -t mksysb -a server=master -a location=/export/nim/images/ncscm013.mksysb -a mk_image=yes -a source=ncscm013 ncscm013mksysb
3:23:48 PM: Carlos Andres Munoz Loaiza: nim -o cust -a lpp_source=618lpp_res -a fixes="update_all" -a installp_flags=acNgX -a show_progress=yes -a accept_licenses=yes ncscm013
Page 590
PARCHAR POR NIM
3:27:07 PM: Henry Fabian Espinosa: ibmadmhe@snchnimsrv:/home/ibmadmhe>sudo nim -o define -t mksysb -a server=master -a location=/export/nim/images/ncscm013.mksysb -a mk_image=yes -a source=ncscm013 ncscm013mksysb
Page 591
Agregar lpars standalone aix ni
Agregar lpars standalone aix nim
a smitty nim
b task
c manage machine
nimsh
ent
Page 592
0042_006 m_lslppconnect Error
ibmadmhe@nim:/home/ibmadmhe# sudo nim -o lslpp almpt04_copy
^C0042-001 nim: processing error encountered on "master":
0042-006 m_lslpp: (From_Master) connect Error 0
0042-008 nimsh: Request denied - nim
HACMP node as NIM client - network settings
The best practice is to not use DNS name resolution on HACMP nodes and use the local hosts file instead. But in NIM environment, where the NIM master is using the DNS name resolution You can get stucked.
Typical error message like this:
nim:/# nim -o lslpp hacmp62
0042-001 nim: processing error encountered on "master":
0042-006 m_lslpp: (From_Master) connect Error 0
0042-008 nimsh: Request denied - nim
If follow the below steps it will be resolved:
The first step is to remove - if exists - on all HACMP node the /etc/resolv.conf and set the /etc/netsvc.conf to hosts = local.
Then set the hosts file, like this:
######### HACMP DEFINITIONS #############
#Persistent IP labels
192.168.42.93 hacmp61p
192.168.42.92 hacmp62p
#Base IP labels
# !!!!! it is important, that the one base label needs to be paired with the node hostname on all node.
10.0.0.1 hacmp61b1 hacmp61
10.0.0.2 hacmp62b1 hacmp62
#Service IP labels
192.168.42.91 ha1
192.168.42.90 ha2
######### END HACMP DEFINITIONS #############
Run the niminit and view / edit if necessary / the /etc/niminfo file.
Make sure that every section use the simple hostname. Do not use the FQDN.
After edited the /etc/niminfo file run the nimclient -C to reload the nimsh service.
Sample niminfo file from node hacmp62:
Page 593
0042_006 m_lslppconnect Error
export NIM_NAME=hacmp62
export NIM_HOSTNAME=hacmp62
export NIM_CONFIGURATION=standalone
export NIM_MASTER_HOSTNAME=nim
export NIM_MASTER_PORT=1058
export NIM_REGISTRATION_PORT=1059
export NIM_SHELL="shell"
export NIM_MASTERID=00F672134C00
....
export NIM_HOSTS=" 127.0.0.1:loopback:localhost 192.168.42.92:hacmp62 192.168.42.32:nim "
....
export ROUTES=" default:0:192.168.42.254 "
Page 594
0042_006 m_lslppconnect Error
The best practice is to not use DNS name resolution on HACMP nodes and use the local hosts file instead. But in NIM environment, where the NIM master is using the DNS name resolution You can get stucked.
The first step is to remove - if exists - on all HACMP node the /etc/resolv.conf and set the /etc/netsvc.conf to hosts = local.
# !!!!! it is important, that the one base label needs to be paired with the node hostname on all node.
Page 595
0042_006 m_lslppconnect Error
export NIM_HOSTS=" 127.0.0.1:loopback:localhost 192.168.42.92:hacmp62 192.168.42.32:nim "
Page 596
0042_006 m_lslppconnect Error
The best practice is to not use DNS name resolution on HACMP nodes and use the local hosts file instead. But in NIM environment, where the NIM master is using the DNS name resolution You can get stucked.
Page 597
DEFINIENDO CLIENTE AL NIM
Skip to main content
United States
IBM
Industries & solutions
Services
Products
Support & downloads
My IBM
Search
Print this page
E-mail this page
Digg
Facebook
Twitter
Delicious
Linked In
Stumbleupon
Alternate NIM Master Configurations and Applications
Technote (FAQ)
Question
How to set up and use alternate NIM masters
Cause
This document offers an easy to follow guideline on implementing an alternate NIM master environment for customers moderately experienced with Network Install Manager (NIM). After completing this guideline one will develop a clearer understanding of how to utilize an alternate NIM master and work with the various functions and restrictions within the environment.
Answer
Introduction
References -
1. NIM Setup Guide
2. NIM Communication Between a Firewall
3. IBM RedBook - NIM A-Z for AIX 5L
Testing Environment
Procedures -
Page 598
DEFINIENDO CLIENTE AL NIM
1.) Define Server A as NIM Master
2.) Initializing Server B as the Alternate
3.) Initiate Server A as alternate of Server B
4.) Defining a Client to Server A
5.) Synchronizing the Alternate Master's NIM database
6.) Taking Over Clients
Conclusion
This document was written to provide NIM users with a step by step procedure on how to implement an alternate NIM master for their NIM environment. An alternate NIM master provides the capabilities of having a backup NIM server that can synchronize existing resources with the original NIM master and takeover NIM clients.
Alternate NIM masters are used to provide redundancy in cases where a primary NIM server has a scheduled outtage for maintenance but NIM operations must continue within the environment. Additionally, the alternate can serve to maintain NIM resources as a backup in case the primary NIM server crashes, becomes corrupted, or resources are removed.
For testing purposes, this document will work with the AIX version 6.1 Technology Level 2 throughout the examples. Although the examples are worked with AIX 6100-02, testing of alternate master operation was performed for AIX versions 5300-09 to 5300-12 and 6100-00 to 6100-05. It's important to note that beyond 6100-04, nimsh is required as the communication protocol between alternate masters. This will be stressed throughout the examples when the communication between alternate NIM master is addressed.
Back to top
A few NIM resources are provided below if needed for references and usage support before working with alternate masters.
1. NIM Setup Guide -
http://www-1.ibm.com/support/docview.wss?rs=0&q1=NIM+Setup+Guide&uid=isg3T1010383&loc=en_US&cs=utf-8&cc=us&lang=en
2. NIM Communication Between a Firewall -
http://www.ibm.com/support/docview.wss?uid=isg3T1011808
3. IBM RedBook - NIM A-Z for AIX 5L -
http://www.redbooks.ibm.com/abstracts/sg247296.html?Open
Back to top
server A/server A hostname= Primary 6100-02* NIM Server/LPAR
server B/server B hostname= Secondary 6100-02* NIM Server/LPAR used as alternate master
Page 599
DEFINIENDO CLIENTE AL NIM
client/client hostname =Test 6100-02* NIM Client Server/LPAR
* It is highly recommended to have the systems updated to the latest service pack for the technology level installed. This ensures that all of the latest security and operational fixes are applied to the system.
Back to top
1.) Define Server A as NIM Master
Before defining a NIM master, ensure that the following filesets have been installed to the system: bos.sysmgt.nim.master and bos.sysmgt.nim.spot.
Configure Server A as NIM maste r
#N/A
# smitty nim >>> Configure the NIM Environment >>> Advanced Configuration >>> Initialize the NIM Master Only
Configure Network Installation Management Master Fileset
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[Entry Fields]
* Network Name [network name]
* Primary Network Install Interface [selected interface] +
Allow Machines to Register Themselves as Clients? [yes] +
Alternate Port Numbers for Network Communications
(reserved values will be used if left blank)
Client Registration [] #
Client Communications []
#N/A
Verify Server A is NIM master:
#N/A
Niminfo file of server A:
# more /etc/niminfo
export NIM_NAME=master
export NIM_CONFIGURATION=master
Page 600
DEFINIENDO CLIENTE AL NIM
export NIM_MASTER_PORT=1058
export NIM_REGISTRATION_PORT=1059
export NIM_MASTER_HOSTNAME =<server A hostname>
#N/A
Back to top
2.) Initializing Server B as the Alternate
In this situation Server B was not defined as NIM master as in the first step of the procedure per the following instructions :
Initializing the alternate master using SMIT
http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.install/doc/insgdrf/adv_config_alt_master_support.htm?resultof=%22%61%6c%74%65%72%6e%61%74%65%22%20%22%61%6c%74%65%72%6e%22%20%22%6d%61%73%74%65%72%22%20
Initialize Server B as alternate:
#N/A
# smitty niminit_altmstr
Initialize This Machine as an Alternate Master
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[Entry Fields]
* This Machine Name [server B hostname]
* Primary Network Install Interface [selected interface] +
* Host Name of Master with which to Initialize [server A hostname]
Hardware Platform Type chrp
Kernel to use for Network Boot [64] +
Communication Protocol used to communicate with [] +
Alternate Master
Use F4 to see options. Note this option will display what protocol is supported considering the AIX version running on the system. If nimsh is not an option its because it was not supported for alternate masters until 6.1 TL 4
#N/A
Results of Alternate Master Initialization Operation:
#N/A
COMMAND STATUS
Command: OK stdout: yes stderr: no
Page 601
DEFINIENDO CLIENTE AL NIM
Before command completion, additional instructions may appear below.
0513-071 The nimesis Subsystem has been added.
0513-071 The nimd Subsystem has been added.
0513-059 The nimesis Subsystem has been started. Subsystem PID is 204848.
#N/A
The next step is to ensure that Server A is aware of the new alternate master as a NIM resource:
Confirm that alternate_master resource was defined on Server A
#N/A
# lsnim
master machines master
boot resources boot
nim_script resources nim_script
master_net networks ent
server B hostname machines alternate_master
#N/A
Check the /etc/niminfo file on Server B (the alternate)
#N/A
# more /etc/niminfo
export NIM_NAME=master
export NIM_CONFIGURATION=master
export NIM_MASTER_PORT=1058
export NIM_REGISTRATION_PORT=1059
export NIM_MASTER_HOSTNAME=server B hostname
export NIM_ALTERNATE_MASTER="server A hostname"
#N/A
At this point Server B is successfully defined as an alternate of Server A. If server A needs to be an alternate master of Server B, continue to Step 3 of the procedures.
Back to top
3.) Initiate Server A as alternate of Server B
Page 602
DEFINIENDO CLIENTE AL NIM
Define Server A as an alternate master of Server B
#N/A
# smitty niminit_altmstr
Initialize This Machine as an Alternate Master
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[Entry Fields]
* This Machine Name [server A hostname]
* Primary Network Install Interface [en0] +
* Host Name of Master with which to Initialize [server B hostname]
Hardware Platform Type chrp
Kernel to use for Network Boot [64] +
Communication Protocol used to communicate with [] +
Alternate Master
Use F4 to see options. Note this option will display what protocol is supported considering the AIX version running on the system. If nimsh is not an option its because it was not supported until 6.1 TL4
Run the command
#N/A
After the command is run, check the niminfo file of Server A for any updates:
Check the niminfo file of Server A. Updated /etc/niminfo file
#N/A
# more /etc/niminfo
export NIM_NAME=master
export NIM_CONFIGURATION=master
export NIM_MASTER_PORT=1058
export NIM_REGISTRATION_PORT=1059
export NIM_MASTER_HOSTNAME= <server A hostname>
export NIM_ALTERNATE_MASTER="<server B hostname>
#N/A
NOTE: Once an alternate master has been added to the NIM environment, previously defined clients should be re-defined to recognize the alternate master(#smitty niminit). Re-defining the clients gives the alternate master remote access to the clients either through rsh or nimsh. A common error encountered is as follows:
0042-372 c_switch_master: The client is not configured to allow this master to execute this command
The issue is resolved simply by removing the /etc/niminfo file from the client and redefining the client on the client side:
Page 603
DEFINIENDO CLIENTE AL NIM
Redefine the client:
#N/A
# niminit -a name=<client> -a master=<master>
#N/A
Once clients have been re-defined, their sync_required attribute is set to no, indicating that they recognize the alternate master. Only clients running AIX 5.3 or later recognize alternate masters!
Verify the resources of Server B to see the alternate NIM Server A listed
#N/A
# lsnim
master machines master
boot resources boot
nim_script resources nim_script
master_net networks ent
server A definition machines alternate_master
#N/A
Verify the resources on Server A to see the alternate NIM Server B listed
#N/A
# lsnim
master machines master
boot resources boot
nim_script resources nim_script
master_net networks ent
server B definition machines alternate_master
client definition machines standalone
#N/A
Back to top
4.) Defining a Client to Server A
Page 604
DEFINIENDO CLIENTE AL NIM
Define a client to original Server A to test sync and replication
#N/A
On the client run:
# smitty niminit
Configure Network Installation Management Client Fileset
[Entry Fields]
* Machine Name [client hostname]

* Primary Network Install Interface [en0] +
* Host Name of Network Install Master [server A hostname]
Hardware Platform Type chrp
Kernel to use for Network Boot [mp] +
Communication Protocol used by client [] +
Ethernet Interface Options
Network Speed Setting [] +
Network Duplex Setting [] +
Comments []

#N/A
Run the command until OK. Check the /etc/niminfo file on the client
#N/A
# more /etc/niminfo
#------------------ Network Install Manager ---------------
# warning - this file contains NIM configuration information
# and should only be updated by NIM
export NIM_NAME=<client NIM name definition>
export NIM_HOSTNAME=<client hostname>
export NIM_CONFIGURATION=standalone
export NIM_MASTER_HOSTNAME=<server A hostname>
export NIM_MASTER_PORT=1058
export NIM_REGISTRATION_PORT=1059
export NIM_SHELL="shell"
export NIM_MASTER_HOSTNAME_LIST="<server A hostname> <server B hostname>"
export NIM_BOS_IMAGE=/SPOT/usr/sys/inst.images/installp/ppc/bos
export NIM_BOS_FORMAT=rte
export NIM_HOSTS=" 127.0.0.1:loopback:localhost <client IP>:<client hostname> <server A IP>:<server A hostname>"
Page 605
DEFINIENDO CLIENTE AL NIM
export NIM_MOUNTS=""
export ROUTES=" default:0:<default gateway IP> "
#N/A
Check client definition on Server A
#N/A
# lsnim -l client hostname client hostname:
class = machines
type = standalone
current_master = server A hostname
sync_required = no
connect = shell
platform = chrp
netboot_kernel = 64
if1 = net1 client hostname 8EB220004002 ent0
cable_type1 = N/A
Cstate = ready for a NIM operation
prev_state = ready for a NIM operation
Mstate = currently running
cpuid = 00068A0AD700
Notice that the sync_required = no attribute for this particular client. But if the attribute is set to YES, then synchronization needs to be performed for the clients.
#N/A
Back to top
5.) Synchronizing the Alternate Master's NIM database
Provided is an example of sync-ing a mksysb, spot, and image.data resource from Server A to Server B (resource filesystem /nim already exists and is mounted on Server B)
Example of Synchronization and Replication of Resources
#N/A
Server A with mksysb, spot, and image.data resource defined:
# lsnim
master machines master
boot resources boot
nim_script resources nim_script
Page 606
DEFINIENDO CLIENTE AL NIM
master_net networks ent
server B hostname machines alternate_master
client hostname machines standalone
client hostname_sysb resources mksysb
client hostname_spot resources spot
clinet hostname_im resources image_data
Server B with no resources other than alternate_master:
# lsnim
master machines master
boot resources boot
nim_script resources nim_script
master_net networks ent
server A hostname machines alternate_master
Resource filesystem /nim (10GB) on Server A
# df -g | grep nim
/dev/fslv01 10.00 8.34 17% 3206 1% /nim
# cd /nim
# ls
im_data lost+found lpp mksysb spot
Resource filesystem /nim (10GB) on Server B
# df -g | grep nim
/dev/fslv01 10.00 10.00 1% 10 1% /nim
# cd /nim
# ls
lost+found
Confirm which master has control of the clients
Check the /etc/niminfo file of the client or run the following from one of the masters:
Page 607
DEFINIENDO CLIENTE AL NIM
# nim -o lslpp <client hostname>
If the client is assigned to that master and can communicate, then the output of the command will return a list of filesets which are installed on the client. Otherwise the output will return:
0042-001 nim: processing error encountered on "master":
0042-378 m_lslpp: The current master for "<client hostname>"
is "<current master hostname>". You must run the "takeover" operation to
become the current master before you can execute the "/usr/lpp/bos.sysmgt/nim/methods/c_ckspot"
operation on this client.
or
0042-001 nim: processing error encountered on "master":
0042-006 m_lslpp: (From_Master) connect Connection refused
<client hostname>: Connection refused
Syncronization will duplicate the resource definitions from the NIM database of server A to server B
NOTE: You should consider the following issues when synchronizing the alternate master's NIM database:
* Object definitions are reset when the database is restored on master B.
* After the database is restored on master B, master B does not control any NIM objects until you perform the takeover operation. As a result, master B can not run any NIM operations to any objects in its database.
On Master A run the following operation to set up the synchronization and replication of resources and clients:
# smitty nim_altmstr >>> Synchronize an Alternate Master's NIM database >>>
Synchronize an Alternate Master's NIM database
Type or select a value for the entry field.
Press Enter AFTER making all desired changes.
[Entry Fields]
* Alternate Master [Use F4 and select Server B] +
<server B hostname> machines alternate_master
Synchronize an Alternate Master's NIM database
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
Page 608
DEFINIENDO CLIENTE AL NIM
[Entry Fields]
* Target Name <server B hostname>
Force yes +
Replicate yes +
NOTE: Use F1 or Esc+1 while the 'Force' and 'Replicate' fields are highlighted for more information.
Run the command until it returns OK.
Output of Sync and Replication:
COMMAND STATUS
Command: OK stdout: yes stderr: no
Before command completion, additional instructions may appear below.
[TOP]
a ./etc/objrepos/nim_attr 8 blocks
a ./etc/objrepos/nim_attr.vc 8 blocks
a ./etc/objrepos/nim_object 8 blocks
a ./etc/objrepos/nim_object.vc 8 blocks
a ./etc/NIM.level 1 blocks
a ./etc/niminfo 2 blocks
The original NIM database was backed up to the
following location prior to this operation:
"/export/nim/backups/server B hostname.10073807242010.backup"
0513-044 The nimesis Subsystem was requested to stop.
0513-004 The Subsystem or Group, nimd, is currently inoperative.
0513-083 Subsystem has been Deleted.
0513-083 Subsystem has been Deleted.
5 objects deleted
43 objects deleted
Restoring the NIM database from /tmp/_nim_dir_17626/mnt0
x ./etc/NIM.level, 8 bytes, 1 tape blocks
The level of the NIM master fileset on this machine is: 5.3.9.0
The level of the NIM database backup is: 5.3.9.0
Level check is successful.
Page 609
DEFINIENDO CLIENTE AL NIM
x ./etc/objrepos/nim_attr, 4096 bytes, 8 tape blocks
x ./etc/objrepos/nim_attr.vc, 4096 bytes, 8 tape blocks
x ./etc/objrepos/nim_object, 4096 bytes, 8 tape blocks
x ./etc/objrepos/nim_object.vc, 4096 bytes, 8 tape blocks
x ./etc/NIM.level, 8 bytes, 1 tape blocks
x ./etc/niminfo, 233 bytes, 1 tape blocks
0513-071 The nimesis Subsystem has been added.
0513-071 The nimd Subsystem has been added.
0513-059 The nimesis Subsystem has been started. Subsystem PID is 28042.
Finished restoring the NIM database
Updating master definition in database from janky definition
Updated master attribute platform to chrp
Updated master attribute netboot_kernel to mp
Updated master attribute if1 to master_net server B hostname 00145EB74C7E ent2
Updated master attribute cable_type1 to N/A
Finished updating master definition
Resetting machines
Reset master
Reset server B
Reset client
Finished resetting machines
Removing NIM client client
Finished removing client
Resetting NIM resources
Finished resetting NIM resources
Replicating NIM resources. Please wait, takes time....
Replicating resource client hostname_sysb
Replicated resource client hostname-_sysb
Replicating resource client hostname_spot
version=5
release=3
mod=9
Replicated resource client hostname_spot
Replicating resource client hostname_im
Replicated resource client hostname_im
Finished Replicating NIM resources
Checking NIM resources
Keeping client hostname_sysb
Keeping client hostname_spot
Keeping client hostname_im
Finished checking NIM resources
Checking NIM SPOTs
checking client hostname_spot
Finished checking SPOTs
nim_master_recover Complete
Page 610
DEFINIENDO CLIENTE AL NIM
#N/A
Resource results on Server B after sync/replication:
#N/A
# lsnim
master machines master
boot resources boot
nim_script resources nim_script
master_net networks ent
client hostname machines standalone
client hostname_sysb resources mksysb
client hostname_spot resources spot
clinet hostname_im resources image_data
# ls /nim
im_data lost+found mksysb spot
#N/A
NOTE: Its highly recommended to create the same filesystem structure and subdirectory locations for the NIM resources as on the primary server to reduce complications during the replication.
The NIM A-Z manual does not recommend synchronizing the SPOT resources, but rather creating a SPOT from the replicated lpp_source on the alternate master. Regardless, during alternate master testing, the SPOTs were also replicated without any issues.
As long as the resource locations are the same on the alternate master, the resources will be replicated along with the client definitions. IMPORTANT!: If the resource locations are not re-created or mounted on the alternate_master the resources will try to be created in / and possibly fill up the / directory.
Back to top
6.) Taking Over Clients
The takeover operation is utilized when the alternate NIM master needs to take control of the NIM environment.
Before taking over clients on the alternate master, one of two things needs to be completed. First, the client needs to be defined on the alternate master, and second, a sync needs to be run from server A before the takeover (Discussed on Step 5.).
Run the takeover command on Server B to take control from Server A
#N/A
# smitty nim_altmstr >>> Takeover control of NIM clients from an Alternate Master
Takeover control of NIM clients from an Alternate Master
Page 611
DEFINIENDO CLIENTE AL NIM
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[Entry Fields]
* Target Name server A
Force no +
Run the command:
COMMAND STATUS
Command: OK stdout: yes stderr: no
Before command completion, additional instructions may appear below.
Updating the NIM database on the "alternate_master" "server B"...
+-----------------------------------------------------------------------------+
"update" Operation Summary
+-----------------------------------------------------------------------------+
Target Result
------ ------
client hostname SUCCESS
#N/A
Once the takeover is complete with Result = SUCCESS, perform a few checks to ensure the clients were taken over successfully.
Server B after the sync:
#N/A
# lsnim
master machines master
boot resources boot
nim_script resources nim_script
master_net networks ent
server A machines alternate_master
client hostname machines standalone
client hostname_sysb resources mksysb
client hostname_spot resources spot
clinet hostname_im resources image_data
#N/A
Page 612
DEFINIENDO CLIENTE AL NIM
Client /etc/niminfo defined under Server A before the takeover:
#N/A
# more /etc/niminfo
#------------------ Network Install Manager ---------------
# warning - this file contains NIM configuration information
# and should only be updated by NIM
export NIM_NAME=client hostname
export NIM_HOSTNAME=client fully qualified hostname
export NIM_CONFIGURATION=standalone
export NIM_MASTER_HOSTNAME=server A hostname
export NIM_MASTER_PORT=1058
export NIM_REGISTRATION_PORT=1059
export NIM_SHELL="shell"
export NIM_MASTER_HOSTNAME_LIST="server A hostname server B hostname"
export NIM_BOS_IMAGE=/SPOT/usr/sys/inst.images/installp/ppc/bos
export NIM_BOS_FORMAT=rte
...
#N/A
As long as Server A is defined as an alternate master of Server B, the takeover operation can be run on Server A to take back control of the clients.
Results of Server B takeover from Server A:
#N/A
Client /etc/niminfo defined under Server B after takeover:
# more /etc/niminfo
#------------------ Network Install Manager ---------------
# warning - this file contains NIM configuration information
# and should only be updated by NIM
export NIM_NAME=client hostname
export NIM_HOSTNAME=client fully qualified hostname
export NIM_CONFIGURATION=standalone
export NIM_MASTER_HOSTNAME=server B hostname
export NIM_MASTER_PORT=1058
export NIM_REGISTRATION_PORT=1059
export NIM_SHELL="shell"
export NIM_MASTER_HOSTNAME_LIST="server B hostname server A hostname"
export NIM_BOS_IMAGE=/SPOT/usr/sys/inst.images/installp/ppc/bos
export NIM_BOS_FORMAT=rte
...
Page 613
DEFINIENDO CLIENTE AL NIM
#N/A
Back to top
Conclusion
Once the NIM environment has been established to synchronize resources and takeover NIM clients, the implementation of Alternate NIM Masters has been completed.
A few things to consider when working with Alternate NIM Masters are as follows: 1.) Although an alternate master may be in place as a backup, one should always keep another backup of each NIM servers database for safe measure. 2.) Do not update one master without planning on updating the alternate, as both masters must be at the same oslevel. 3.) Communication protocols (nimsh/rsh) between the masters should be set the same.
NIM is an ever dynamic and complex tool, but its applications are progressively useful. Alternate Masters is one of many NIM functions provided that may be subject to changes and improvements in the future. If additional support is needed for possible defects, general inquiries, and/or usage, please contact our 1-800-IBM-SERV support line.
Back to top
Rate this page:
(1 users)Average rating
Did the information help you achieve your goal?YesNoDon't know
Comments:*required
Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Rate this page:
(1 users)Average rating
Add comments
Document information
AIX family
Software version:
5.3, 6.1, 7.1
Operating system(s):
AIX
Software edition:
Enterprise, Standard
Reference #:
Page 614
DEFINIENDO CLIENTE AL NIM
T1012143
Modified date:
17/11/10
Translate my page
Tags
Add a tag | Search all tags
My tags | All tags
View as cloud | list
Resources
Connect with us
Create a profile
Communities
Academic collaboration
Research collaboration
IBMers past and present
IBM Voices
Key topics
A smarter planet
Big data and analytics
Cloud computing
Security and resilience
Smarter commerce
Smarter Computing
Sustainability
Smarter Cities
Information for
C-suite executives
Industries
Midsize business solutions
Small business solutions
Developers
IBM Business Partners
Investors
Job seekers
Shop & buy
Page 615
DEFINIENDO CLIENTE AL NIM
Special offers
Personal computers
Ready to buy?
Financing
Find a sales rep
Find a Business Partner
IBM logo merchandise
About IBM
Latest news
IBM's Centennial
IBM Research
Corporate responsibility
Employee directory
More about IBM
Popular links
Careers
Fix central
Passport Advantage
Product security bulletins
Software
System x
Watson
Footer links
Contact
Privacy
Terms of use
Accessibility
Page 616
DEFINIENDO CLIENTE AL NIM
This document offers an easy to follow guideline on implementing an alternate NIM master environment for customers moderately experienced with Network Install Manager (NIM). After completing this guideline one will develop a clearer understanding of how to utilize an alternate NIM master and work with the various functions and restrictions within the environment.
Page 617
DEFINIENDO CLIENTE AL NIM
This document was written to provide NIM users with a step by step procedure on how to implement an alternate NIM master for their NIM environment. An alternate NIM master provides the capabilities of having a backup NIM server that can synchronize existing resources with the original NIM master and takeover NIM clients.
Alternate NIM masters are used to provide redundancy in cases where a primary NIM server has a scheduled outtage for maintenance but NIM operations must continue within the environment. Additionally, the alternate can serve to maintain NIM resources as a backup in case the primary NIM server crashes, becomes corrupted, or resources are removed.
For testing purposes, this document will work with the AIX version 6.1 Technology Level 2 throughout the examples. Although the examples are worked with AIX 6100-02, testing of alternate master operation was performed for AIX versions 5300-09 to 5300-12 and 6100-00 to 6100-05. It's important to note that beyond 6100-04, nimsh is required as the communication protocol between alternate masters. This will be stressed throughout the examples when the communication between alternate NIM master is addressed.
A few NIM resources are provided below if needed for references and usage support before working with alternate masters.
http://www-1.ibm.com/support/docview.wss?rs=0&q1=NIM+Setup+Guide&uid=isg3T1010383&loc=en_US&cs=utf-8&cc=us&lang=en
server B/server B hostname= Secondary 6100-02* NIM Server/LPAR used as alternate master
Page 618
DEFINIENDO CLIENTE AL NIM
* It is highly recommended to have the systems updated to the latest service pack for the technology level installed. This ensures that all of the latest security and operational fixes are applied to the system.
Before defining a NIM master, ensure that the following filesets have been installed to the system: bos.sysmgt.nim.master and bos.sysmgt.nim.spot.
# smitty nim >>> Configure the NIM Environment >>> Advanced Configuration >>> Initialize the NIM Master Only
Page 619
DEFINIENDO CLIENTE AL NIM
In this situation Server B was not defined as NIM master as in the first step of the procedure per the following instructions :
http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.install/doc/insgdrf/adv_config_alt_master_support.htm?resultof=%22%61%6c%74%65%72%6e%61%74%65%22%20%22%61%6c%74%65%72%6e%22%20%22%6d%61%73%74%65%72%22%20
Use F4 to see options. Note this option will display what protocol is supported considering the AIX version running on the system. If nimsh is not an option its because it was not supported for alternate masters until 6.1 TL 4
Page 620
DEFINIENDO CLIENTE AL NIM
The next step is to ensure that Server A is aware of the new alternate master as a NIM resource:
At this point Server B is successfully defined as an alternate of Server A. If server A needs to be an alternate master of Server B, continue to Step 3 of the procedures.
Page 621
DEFINIENDO CLIENTE AL NIM
Use F4 to see options. Note this option will display what protocol is supported considering the AIX version running on the system. If nimsh is not an option its because it was not supported until 6.1 TL4
NOTE: Once an alternate master has been added to the NIM environment, previously defined clients should be re-defined to recognize the alternate master(#smitty niminit). Re-defining the clients gives the alternate master remote access to the clients either through rsh or nimsh. A common error encountered is as follows:
0042-372 c_switch_master: The client is not configured to allow this master to execute this command
The issue is resolved simply by removing the /etc/niminfo file from the client and redefining the client on the client side:
Page 622
DEFINIENDO CLIENTE AL NIM
Once clients have been re-defined, their sync_required attribute is set to no, indicating that they recognize the alternate master. Only clients running AIX 5.3 or later recognize alternate masters!
Page 623
DEFINIENDO CLIENTE AL NIM
export NIM_HOSTS=" 127.0.0.1:loopback:localhost <client IP>:<client hostname> <server A IP>:<server A hostname>"
Page 624
DEFINIENDO CLIENTE AL NIM
Notice that the sync_required = no attribute for this particular client. But if the attribute is set to YES, then synchronization needs to be performed for the clients.
Provided is an example of sync-ing a mksysb, spot, and image.data resource from Server A to Server B (resource filesystem /nim already exists and is mounted on Server B)
Page 625
DEFINIENDO CLIENTE AL NIM
Page 626
DEFINIENDO CLIENTE AL NIM
If the client is assigned to that master and can communicate, then the output of the command will return a list of filesets which are installed on the client. Otherwise the output will return:
become the current master before you can execute the "/usr/lpp/bos.sysmgt/nim/methods/c_ckspot"
Syncronization will duplicate the resource definitions from the NIM database of server A to server B
NOTE: You should consider the following issues when synchronizing the alternate master's NIM database:
* After the database is restored on master B, master B does not control any NIM objects until you perform the takeover operation. As a result, master B can not run any NIM operations to any objects in its database.
On Master A run the following operation to set up the synchronization and replication of resources and clients:
Page 627
DEFINIENDO CLIENTE AL NIM
NOTE: Use F1 or Esc+1 while the 'Force' and 'Replicate' fields are highlighted for more information.
Page 628
DEFINIENDO CLIENTE AL NIM
Page 629
DEFINIENDO CLIENTE AL NIM
NOTE: Its highly recommended to create the same filesystem structure and subdirectory locations for the NIM resources as on the primary server to reduce complications during the replication.
The NIM A-Z manual does not recommend synchronizing the SPOT resources, but rather creating a SPOT from the replicated lpp_source on the alternate master. Regardless, during alternate master testing, the SPOTs were also replicated without any issues.
As long as the resource locations are the same on the alternate master, the resources will be replicated along with the client definitions. IMPORTANT!: If the resource locations are not re-created or mounted on the alternate_master the resources will try to be created in / and possibly fill up the / directory.
The takeover operation is utilized when the alternate NIM master needs to take control of the NIM environment.
Before taking over clients on the alternate master, one of two things needs to be completed. First, the client needs to be defined on the alternate master, and second, a sync needs to be run from server A before the takeover (Discussed on Step 5.).
Page 630
DEFINIENDO CLIENTE AL NIM
Once the takeover is complete with Result = SUCCESS, perform a few checks to ensure the clients were taken over successfully.
Page 631
DEFINIENDO CLIENTE AL NIM
As long as Server A is defined as an alternate master of Server B, the takeover operation can be run on Server A to take back control of the clients.
Page 632
DEFINIENDO CLIENTE AL NIM
Once the NIM environment has been established to synchronize resources and takeover NIM clients, the implementation of Alternate NIM Masters has been completed.
A few things to consider when working with Alternate NIM Masters are as follows: 1.) Although an alternate master may be in place as a backup, one should always keep another backup of each NIM servers database for safe measure. 2.) Do not update one master without planning on updating the alternate, as both masters must be at the same oslevel. 3.) Communication protocols (nimsh/rsh) between the masters should be set the same.
NIM is an ever dynamic and complex tool, but its applications are progressively useful. Alternate Masters is one of many NIM functions provided that may be subject to changes and improvements in the future. If additional support is needed for possible defects, general inquiries, and/or usage, please contact our 1-800-IBM-SERV support line.
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Page 633
DEFINIENDO CLIENTE AL NIM
Page 634
DEFINIENDO CLIENTE AL NIM
Page 635
DEFINIENDO CLIENTE AL NIM
This document offers an easy to follow guideline on implementing an alternate NIM master environment for customers moderately experienced with Network Install Manager (NIM). After completing this guideline one will develop a clearer understanding of how to utilize an alternate NIM master and work with the various functions and restrictions within the environment.
Page 636
DEFINIENDO CLIENTE AL NIM
This document was written to provide NIM users with a step by step procedure on how to implement an alternate NIM master for their NIM environment. An alternate NIM master provides the capabilities of having a backup NIM server that can synchronize existing resources with the original NIM master and takeover NIM clients.
Alternate NIM masters are used to provide redundancy in cases where a primary NIM server has a scheduled outtage for maintenance but NIM operations must continue within the environment. Additionally, the alternate can serve to maintain NIM resources as a backup in case the primary NIM server crashes, becomes corrupted, or resources are removed.
For testing purposes, this document will work with the AIX version 6.1 Technology Level 2 throughout the examples. Although the examples are worked with AIX 6100-02, testing of alternate master operation was performed for AIX versions 5300-09 to 5300-12 and 6100-00 to 6100-05. It's important to note that beyond 6100-04, nimsh is required as the communication protocol between alternate masters. This will be stressed throughout the examples when the communication between alternate NIM master is addressed.
Page 637
DEFINIENDO CLIENTE AL NIM
* It is highly recommended to have the systems updated to the latest service pack for the technology level installed. This ensures that all of the latest security and operational fixes are applied to the system.
Page 638
DEFINIENDO CLIENTE AL NIM
http://publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.install/doc/insgdrf/adv_config_alt_master_support.htm?resultof=%22%61%6c%74%65%72%6e%61%74%65%22%20%22%61%6c%74%65%72%6e%22%20%22%6d%61%73%74%65%72%22%20
Use F4 to see options. Note this option will display what protocol is supported considering the AIX version running on the system. If nimsh is not an option its because it was not supported for alternate masters until 6.1 TL 4
Page 639
DEFINIENDO CLIENTE AL NIM
Page 640
DEFINIENDO CLIENTE AL NIM
Use F4 to see options. Note this option will display what protocol is supported considering the AIX version running on the system. If nimsh is not an option its because it was not supported until 6.1 TL4
NOTE: Once an alternate master has been added to the NIM environment, previously defined clients should be re-defined to recognize the alternate master(#smitty niminit). Re-defining the clients gives the alternate master remote access to the clients either through rsh or nimsh. A common error encountered is as follows:
Page 641
DEFINIENDO CLIENTE AL NIM
Once clients have been re-defined, their sync_required attribute is set to no, indicating that they recognize the alternate master. Only clients running AIX 5.3 or later recognize alternate masters!
Page 642
DEFINIENDO CLIENTE AL NIM
Page 643
DEFINIENDO CLIENTE AL NIM
Page 644
DEFINIENDO CLIENTE AL NIM
Page 645
DEFINIENDO CLIENTE AL NIM
If the client is assigned to that master and can communicate, then the output of the command will return a list of filesets which are installed on the client. Otherwise the output will return:
* After the database is restored on master B, master B does not control any NIM objects until you perform the takeover operation. As a result, master B can not run any NIM operations to any objects in its database.
Page 646
DEFINIENDO CLIENTE AL NIM
Page 647
DEFINIENDO CLIENTE AL NIM
Page 648
DEFINIENDO CLIENTE AL NIM
NOTE: Its highly recommended to create the same filesystem structure and subdirectory locations for the NIM resources as on the primary server to reduce complications during the replication.
The NIM A-Z manual does not recommend synchronizing the SPOT resources, but rather creating a SPOT from the replicated lpp_source on the alternate master. Regardless, during alternate master testing, the SPOTs were also replicated without any issues.
As long as the resource locations are the same on the alternate master, the resources will be replicated along with the client definitions. IMPORTANT!: If the resource locations are not re-created or mounted on the alternate_master the resources will try to be created in / and possibly fill up the / directory.
Before taking over clients on the alternate master, one of two things needs to be completed. First, the client needs to be defined on the alternate master, and second, a sync needs to be run from server A before the takeover (Discussed on Step 5.).
Page 649
DEFINIENDO CLIENTE AL NIM
Page 650
DEFINIENDO CLIENTE AL NIM
Page 651
DEFINIENDO CLIENTE AL NIM
A few things to consider when working with Alternate NIM Masters are as follows: 1.) Although an alternate master may be in place as a backup, one should always keep another backup of each NIM servers database for safe measure. 2.) Do not update one master without planning on updating the alternate, as both masters must be at the same oslevel. 3.) Communication protocols (nimsh/rsh) between the masters should be set the same.
NIM is an ever dynamic and complex tool, but its applications are progressively useful. Alternate Masters is one of many NIM functions provided that may be subject to changes and improvements in the future. If additional support is needed for possible defects, general inquiries, and/or usage, please contact our 1-800-IBM-SERV support line.
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Page 652
DEFINIENDO CLIENTE AL NIM
Page 653
DEFINIENDO CLIENTE AL NIM
Page 654
DEFINIENDO CLIENTE AL NIM
This document offers an easy to follow guideline on implementing an alternate NIM master environment for customers moderately experienced with Network Install Manager (NIM). After completing this guideline one will develop a clearer understanding of how to utilize an alternate NIM master and work with the various functions and restrictions within the environment.
Page 655
DEFINIENDO CLIENTE AL NIM
This document was written to provide NIM users with a step by step procedure on how to implement an alternate NIM master for their NIM environment. An alternate NIM master provides the capabilities of having a backup NIM server that can synchronize existing resources with the original NIM master and takeover NIM clients.
Alternate NIM masters are used to provide redundancy in cases where a primary NIM server has a scheduled outtage for maintenance but NIM operations must continue within the environment. Additionally, the alternate can serve to maintain NIM resources as a backup in case the primary NIM server crashes, becomes corrupted, or resources are removed.
For testing purposes, this document will work with the AIX version 6.1 Technology Level 2 throughout the examples. Although the examples are worked with AIX 6100-02, testing of alternate master operation was performed for AIX versions 5300-09 to 5300-12 and 6100-00 to 6100-05. It's important to note that beyond 6100-04, nimsh is required as the communication protocol between alternate masters. This will be stressed throughout the examples when the communication between alternate NIM master is addressed.
Page 656
DEFINIENDO CLIENTE AL NIM
Page 657
DEFINIENDO CLIENTE AL NIM
Page 658
DEFINIENDO CLIENTE AL NIM
Page 659
DEFINIENDO CLIENTE AL NIM
NOTE: Once an alternate master has been added to the NIM environment, previously defined clients should be re-defined to recognize the alternate master(#smitty niminit). Re-defining the clients gives the alternate master remote access to the clients either through rsh or nimsh. A common error encountered is as follows:
Page 660
DEFINIENDO CLIENTE AL NIM
Page 661
DEFINIENDO CLIENTE AL NIM
Page 662
DEFINIENDO CLIENTE AL NIM
Page 663
DEFINIENDO CLIENTE AL NIM
Page 664
DEFINIENDO CLIENTE AL NIM
Page 665
DEFINIENDO CLIENTE AL NIM
Page 666
DEFINIENDO CLIENTE AL NIM
Page 667
DEFINIENDO CLIENTE AL NIM
As long as the resource locations are the same on the alternate master, the resources will be replicated along with the client definitions. IMPORTANT!: If the resource locations are not re-created or mounted on the alternate_master the resources will try to be created in / and possibly fill up the / directory.
Page 668
DEFINIENDO CLIENTE AL NIM
Page 669
DEFINIENDO CLIENTE AL NIM
Page 670
DEFINIENDO CLIENTE AL NIM
A few things to consider when working with Alternate NIM Masters are as follows: 1.) Although an alternate master may be in place as a backup, one should always keep another backup of each NIM servers database for safe measure. 2.) Do not update one master without planning on updating the alternate, as both masters must be at the same oslevel. 3.) Communication protocols (nimsh/rsh) between the masters should be set the same.
NIM is an ever dynamic and complex tool, but its applications are progressively useful. Alternate Masters is one of many NIM functions provided that may be subject to changes and improvements in the future. If additional support is needed for possible defects, general inquiries, and/or usage, please contact our 1-800-IBM-SERV support line.
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Page 671
DEFINIENDO CLIENTE AL NIM
Page 672
DEFINIENDO CLIENTE AL NIM
Page 673
DEFINIENDO CLIENTE AL NIM
This document offers an easy to follow guideline on implementing an alternate NIM master environment for customers moderately experienced with Network Install Manager (NIM). After completing this guideline one will develop a clearer understanding of how to utilize an alternate NIM master and work with the various functions and restrictions within the environment.
Page 674
DEFINIENDO CLIENTE AL NIM
For testing purposes, this document will work with the AIX version 6.1 Technology Level 2 throughout the examples. Although the examples are worked with AIX 6100-02, testing of alternate master operation was performed for AIX versions 5300-09 to 5300-12 and 6100-00 to 6100-05. It's important to note that beyond 6100-04, nimsh is required as the communication protocol between alternate masters. This will be stressed throughout the examples when the communication between alternate NIM master is addressed.
Page 675
DEFINIENDO CLIENTE AL NIM
Page 676
DEFINIENDO CLIENTE AL NIM
Page 677
DEFINIENDO CLIENTE AL NIM
Page 678
DEFINIENDO CLIENTE AL NIM
Page 679
DEFINIENDO CLIENTE AL NIM
Page 680
DEFINIENDO CLIENTE AL NIM
Page 681
DEFINIENDO CLIENTE AL NIM
Page 682
DEFINIENDO CLIENTE AL NIM
Page 683
DEFINIENDO CLIENTE AL NIM
Page 684
DEFINIENDO CLIENTE AL NIM
Page 685
DEFINIENDO CLIENTE AL NIM
Page 686
DEFINIENDO CLIENTE AL NIM
Page 687
DEFINIENDO CLIENTE AL NIM
Page 688
DEFINIENDO CLIENTE AL NIM
Page 689
DEFINIENDO CLIENTE AL NIM
A few things to consider when working with Alternate NIM Masters are as follows: 1.) Although an alternate master may be in place as a backup, one should always keep another backup of each NIM servers database for safe measure. 2.) Do not update one master without planning on updating the alternate, as both masters must be at the same oslevel. 3.) Communication protocols (nimsh/rsh) between the masters should be set the same.
Page 690
DEFINIENDO CLIENTE AL NIM
Page 691
DEFINIENDO CLIENTE AL NIM
Page 692
DEFINIENDO CLIENTE AL NIM
Page 693
DEFINIENDO CLIENTE AL NIM
For testing purposes, this document will work with the AIX version 6.1 Technology Level 2 throughout the examples. Although the examples are worked with AIX 6100-02, testing of alternate master operation was performed for AIX versions 5300-09 to 5300-12 and 6100-00 to 6100-05. It's important to note that beyond 6100-04, nimsh is required as the communication protocol between alternate masters. This will be stressed throughout the examples when the communication between alternate NIM master is addressed.
Page 694
Parchar nim server
Parchar nim server
Se debe actualizar a ultimo tls
hacer gencopy de los tls
despues
Para crear un spot nuevo y lpp_source
Subir los medios de instalacion en este caso para aix 7.1 el OS del nim es aix 7.1
nim_master_setup -a device=/depot/AIX3DVD -BF
Page 695
Parchar nim server
Actualizar los spot y lpp_source existentes
gencopy -X -b "-qv" -d /ruta/TLS -t /ruta/TLS_nueva all
sudo nim_update_all -l lpp_source -s spot -Bu -d /export/GENCOPY_AIX71TL2SP3
el device es el gencopy de los medios de instalacion
Page 696
convertir bff a normal gencopy
gencopy -X -b "-qv" -d /export/nim/lpp_source/614lpp_res/ -t /export/SO/bos.data/ bos.adt.debug
paquetes aix verlos desde el CD
Page 697
convertir bff a normal gencopy
gencopy -X -b "-qv" -d /export/nim/lpp_source/614lpp_res/ -t /export/SO/bos.data/ bos.adt.debug
Page 698
AJUSTAR HORA AIX
AJUSTAR HORA AIX
agregarle un segundo sudo date -a +1
ajuste hora sudo date 02221107
Page 699
Comando clevacuate
Comando clevacuate cambiuo cluster sirpi
Page 700
Procesos que consumen mas memor
Procesos que consumen mas memoria hpux
How to find out which processes are using more
memory:
gz-hp-ux:/# top -f top.out -n 10000 -d 1
gz-hp-ux:/# sort -n -k7,7 top.out
gz-hp-ux:/# sort -n -k7,7 top.out | awk '{if ($7~/M$/)
{print $0}}'
Page 701
Procesos que consumen mas memor
Page 702
Procesos que consumen mas memor
Page 703
Procesos que consumen mas memor
Page 704
Procesos que consumen mas memor
Page 705
Procesos que consumen mas memor
Page 706
Procesos que consumen mas memor
Page 707
Procesos que consumen mas memor
Page 708
Procesos que consumen mas memor
Page 709
Procesos que consumen mas memor
Page 710
Procesos que consumen mas memor
Page 711
Procesos que consumen mas memor
vmstat 1 2| tail -1 | awk '{ print $5/1024 , "MB" }
Page 712
Procesos que consumen mas memor
Page 713
Procesos que consumen mas memor
Page 714
Procesos que consumen mas memor
Page 715
Procesos que consumen mas memor
Page 716
Procesos que consumen mas memor
Page 717
Procesos que consumen mas memor
Page 718
Procesos que consumen mas memor
Page 719
Procesos que consumen mas memor
Page 720
Procesos que consumen mas memor
Page 721
Procesos que consumen mas memor
Page 722
Procesos que consumen mas memor
Page 723
Procesos que consumen mas memor
vmstat 1 2| tail -1 | awk '{ print $5/1024 , "MB" }
Page 724
Actualizar Tls AIX
Question
What is the recommended process for upgrading to a new Technology Level or Service Pack in AIX ?
Answer
-- Updating to a New Technology Level or Service Pack --
Update_All in 5.3, 6.1, and AIX 7
This document describes the recommended preparation and process when considering updating your system to a new technology level or adding a service pack to an existing technology level. In all we will review some key words and terminology, run through recommended pre-checks, discuss the update_all process using both SMIT and command line, and finally post-checks & FAQ.
Key Words / Terminology :
V.R.M.F. (Version, Release, Maintenance Level, Fix Level)
This represents your operating system level and is mentioned because of the change made in the 5300-07 technology level update. Previous to 5300-07 updates are recognized by their last numerical level entry only.
Ex.
bos.rte.install 5.3.0.60
Beginning with 5300-07 the 3rd number, or Maintenance Level number will also be included and will represent the Technology level of the fileset, followed by the Fix Level.
Ex.
bos.rte.install 5.3.7.0
*Note that the Fix Level entry does not necessarily represent the Service Pack level. Any similarity is simply coincidental.
Oslevel faillog
You will also notice a change to how the operating system level reads. With the introduction of 5300-06 you will notice more information provided when running the oslevel command.
# oslevel -s
6100-06-06-1140
The addition of the last four digits simply represents the year (11) and week (40) of the release of your technology level/service pack (-06-06).
Update_all
This is the recommended method of installation when upgrading your technology level or service pack level only. This installation method should not be used when attempting to upgrade the version or release level of your operating system.
Ex.
5300-0x to 6100-0x - do NOT use update_all
6100-0x to 7100-0x - do NOT use update_all
Recommended Pre-Checks :
1. The back-out
It is recommended to have at least one back-out method available to you in case a restore is required. Recommended back out methods include : mksysb restore, sysback restore, altinst_rootvg clone, and multibos. More information on any of these back-out methods can be found at the publib documentation site by using this link to click through to the appropriate infocenter and search features found here :
http://publib16.boulder.ibm.com/pseries/
2. Boot Image Verification
The hd5 logical volume holds your boot image. There are a few checks to make against your boot image before starting your update_all process.
Page 725
Actualizar Tls AIX
First, find out which disk contains your hd5 logical volume.
# lslv -m hd5
hd5:N/A
LP PP1 PV1
0001 0001 hdisk0
The listing under the PV1 column indicates on which disk hd5 is located. Any other entries under PV2..etc, simply represent mirrored copies.
Next, verify your boot image can be successfully recreated using the hdisk# from above and by using /dev/ipldevice.
# bosboot -ad /dev/hdisk0
bosboot: Boot image is 35795 512 byte blocks.
# bosboot -ad /dev/ipldevice
bosboot: Boot image is 35795 512 byte blocks.
If either of these two commands fail for any reason, please call the support center for resolution before proceeding.
Finally, with the continual introduction of new devices and hardware the boot images are growing larger. You will want to make sure your hd5 logical volume has enough free and contiguous space to hold the boot image. Currently the recommended allocated space to have for hd5 is 32meg. This is of concern in environments with smaller disk sizes, and should be checked before running an update.
# lsvg -l rootvg |grep hd5
hd5 boot 1 1 1 closed/syncd N/A
# lsvg rootvg |grep SIZE
VG STATE: active PP SIZE: 32 megabyte(s)
The single partition (in bold (1)) is 32meg in size. This should be enough to contain the boot image. Smaller partition sizes will require more partitions to be allocated.
Your hd5 partitions also need to be contiguous partitions. Check this by running the following command :
# lspv -M hdisk0 |grep hd5
hdisk0:1 hd5:1
hdisk0:2 hd5:2
hdisk0:3 hd5:3
You can see in this example that the hd5 logical volume covers the first 3 partitions on the disk and they are all contiguous. If your partitions are not contiguous, or are not covered on the first partitions of the disk please call the software support line for assistance with correcting this.
Again, you may only have 1 partition that is large enough to handle the boot image, or you may have multiple smaller partitions. Either is fine.
3. Firmware
Firmware should be kept up to date and be checked whenever a technology level update is considered. In general firmware updates should be applied before software updates, but that is not a rule set in stone. You should always refer to the firmware download site installation information and follow those instructions.
You can access the firmware download site here :
http://www-933.ibm.com/support/fixcentral/
If there are any questions concerning the firmware update, installation instructions, or if there are software considerations please contact the hardware support center first.
4. Fileset Consistency
Page 726
Actualizar Tls AIX
You should run the following command to check fileset consistency :
# lppchk -v
Ideally this should return to the command line with no output. If you do receive output and are unfamiliar with how to resolve it, please call the support center for assistance before running your upgrade.
5. Space
In order to see if you have enough space for your update you can run the update_all operation in preview mode. This will provide you with an estimated system resources listing of the necessary space. In order to do this you will first have to install the fileset bos.rte.install. Following are two examples of how to update this fileset first, so a preview update_all can be executed. The example below shows initially committing the bos.rte.install update. If you would feel more comfortable using the apply feature in this case, feel free to do so. Note that if you do Apply you will need to Commit before continuing with the actual update_all process.
From an unmounted cdrom device (cd0).
# installp -acd /dev/cd0 bos.rte.install
From a download directory (/fixes/6100-06)
# installp -acd /fixes/6100-06 bos.rte.install
Using SMITTY
# smitty install_all
* INPUT device / directory for software /dev/cd0
* SOFTWARE to install [bos.rte.install]
PREVIEW only? (install operation will NOT occur) no
Once the installation is complete you will then be able to run the preview operation on the remaining filesets to get an estimate of the required space for your update.
# smitty update_all
* INPUT device / directory for software /dev/cd0
* SOFTWARE to update _update_all
PREVIEW only? (update operation will NOT occur) yes
The preview will show something similar to this in regards to the space requirements :
RESOURCES
---------------
Estimated system resource requirements for filesets being installed:
(All sizes are in 512-byte blocks)
Filesystem
Needed Space
Free Space
/
402
239312
/usr
Page 727
Actualizar Tls AIX
94352
165440
/var
1
237384
/tmp
52304
259240
/opt
6648
158576
Total
153707
1059952
Running the update using SMIT or command line :
This section will cover the update_all process. In all cases the input device (location of the software) will be referred to as being a local cdrom drive (/dev/cd0). You can always use a download directory or nfs mount point, simply substitute the input device as necessary. This process is also executed presuming you are logged in as root (as opposed to using sudo).
1. SMITTY :
By menu selection options you would take the following path :
# smitty
Software Installation and Maintenance
Install and Update Software
Update Installed Software to Latest Level (Update All)
-or use the fastpath-
# smitty update_all
INPUT device / directory for software /dev/cd0
SOFTWARE to update _update_all
PREVIEW only? (update operation will NOT occur) no
COMMIT software updates? yes
SAVE replaced files? no
AUTOMATICALLY install requisite software? yes
EXTEND file systems if space needed? yes
Page 728
Actualizar Tls AIX
VERIFY install and check file sizes? no
DETAILED output? no
Process multiple volumes? yes
ACCEPT new license agreements? yes*
Preview new LICENSE agreements? No
The only required change would be the option for ACCEPT new license agreements. All other given defaults should remain as they are. Pressing <Enter> here will bring up a confirmation dialog box to which you press <Enter> again. The only other interaction you may have is if you need to switch out a volume of the media package. When complete, the upper left corner Command: field will have one of two outcomes :
OK : Your installation has completed without error. You can either scroll down or exit out and view the /smit.log file for the log of the installation.
FAILED : One or more filesets failed for some reason. You can either scroll down or exit out and view the /smit.log file for the log of the installation. Corrective action should be taken before rebooting.
2. Command line :
You will use the install_all_updates command if opting to run this from command line.
This command does have a representative manpage so feel free to review the flags, however this command was intended to be easily executed so running a basic update will not be a very long command.
# install_all_updates -Y -cd /dev/cd0
Once complete you will find the log of the installation in /var/adm/ras/install_all_updates.log. By default the fileset updates will be installed in the APPLIED state. The "-c" flag has been added to the above command to specify that all filesets install in the COMMITTED state. See the FAQ at the end of this document for more information concerning APPLIED vs COMMITTED.
Post checks :
Presuming your update_all was successful you will want to check the following commands. If you receive unexpected output please contact the support center for assistance.
* Please see FAQ statement 11 and 11a below regarding post-update_all issues.
# oslevel -r
This should return with the expected TL output
# oslevel -s
This should return with the expected TL and SP output.
# lppchk -v
This should come back ideally with no output.
FAQ and Opinions
This section is contains the most commonly asked questions and a few recommendations concerning the update_all. Most answers will be kept short and to the point (as much as possible).
1. Is it okay to install my Technology Level in the APPLIED state ? What if I want to reject the TL update if there is a problem ?
With the introduction of Technology Levels and the all or nothing packaging format, these updates are bringing in on the upwards of 400+ fileset updates for each TL. Attempting to perform a reject process on so much code simply does not work well, and is not supported. Recommended back-out methods are discussed earlier in this document.
1a. Does the same hold true for Service Packs ?
The Service Pack updates are certainly much smaller groups of updates....typically numbering around 40-50 per update. While you certainly will have a better chance of successfully rejecting 40 filesets instead of 400, it would still be best to have one of the back-out methods mentioned earlier.
2. Why does my update_all have problems when I use an NFS mounted cdrom ?
Page 729
Actualizar Tls AIX
When running an update_all over NFS, you create your own mount point for the cdrom drive. This does not allow it to recognize the fact that there are multiple volumes available that contain the correct requisite filesets. Multiple update_all operations may be needed on each volume when NFS mounting a cdrom drive. A better option may be to bffcreate the contents of all CDs down to a directory, then NFS mount that directory.
3. The update_all failed. What now ?
Do not reboot. You can review the log to find out what failed and why. If you are comfortable and familiar with these situations you can correct the failures and re-update the filesets. If not, please call the helpdesk and open a PMR for assistance. Have the log available to email in if necessary.
4. I need to run my update today but I may not be able to reboot until next week. Is that a problem ?
Plans should be made to reboot as soon as the update is complete and checks have been made to ensure there were no failures. System files will have been replaced, but the corresponding kernel and library updates will not be loaded until boot time. You will likely encounter problems if you delay rebooting.
5. Is it recommended to reboot before issuing a TL upgrade ?
If this is possible, absolutely. There are systems out there that have not been rebooted in a year or more. Who is to say that something has not happened in that time that simply would not show up until a reboot. Rebooting the system first assures a good boot image, a stable system, and would isolate any problem that normally would not be caught until the post-update reboot as either a preexisting issue, or an issue directly related to the TL update itself.
6. Some say to use base AIX install media when updating the TL, others say the TL fix downloads or CDs should be used. Which is right ?
The recommendation is to use the TL fix downloads from FixCentral, or the TL CDs that can be ordered either online or from AIX SupportLine. You can also use the base AIX installation media, however without getting into a long answer, the recommendation is using the TL fix packages.
7. How long will the update_all take ?
This is a question that does not quite have a definite answer. The length of time required for the update_all depends on how many filesets are being updated as well as the available system resources such as processors and memory.
Giving a ballpark figure however, going up one TL should only take about 30-60 minutes plus reboot time. Some admins prefer to be more on the conservative side and block a 2-3 hour downtime. Consideration should also be made to the amount of time it would take to restore, depending on the backup method selected.
8. Is it okay to run the update_all while people are online ?
Updating could affect running processes. As such, applications should be down and users offline as a general rule.
9. Where can I download new service packs or technology levels ?
TL and SP updates can be acquired from the FixCentral website located here :
http://www-933.ibm.com/support/fixcentral/
10. Will product X at level Y.Z work with my new technology level ?
Some products may only be certified up to a certain operating system level while other products may require an update. The best thing to do would be to contact product X's support center. If it is an IBM product feel free to contact our support center and open a PMR requesting to speak to the product X team. Any 3rd party products should be cleared by their support before upgrading.
11. The 'oslevel -s' and/or 'oslevel -r' commands do not report what I expect after the udpate. How can I determine what is missing ?
If your 'oslevel' commands do not report correctly after your update_all you can add the "-l" flag to determine which filesets still need to be updated in order to complete your upgrade.
The syntax :
# oslevel -rl <level>
# oslevel -sl <level>
Example :
# oslevel -rl 6100-01
-or-
# oslevel -sl 6100-00-01-0748
The filesets listed will show an "Actual Level" heading (your current level) and a "Maintenance Level" heading (the level you need to be at to satisfy the TL/SP).
11a. Some filesets occasionally require multiple update_all operations.
There are cases where a second update_all operations need to be executed to pick up the full TL update. This is not defective behavior. Please also take note that this tip is not intended to resolve a "FAILED" status of your update_all. If you notice that your TL update was successful, but some filesets did not get updated and are on your media or in your download location, you may need to run the update_all a second time to pick them up.
12. What are other best practices with regards to keeping the AIX operating system updated?
IBM maintains a best practices site for service and support for Power Systems.
Page 730
Actualizar Tls AIX
Visit http://www.ibm.com/support/customercare/sas/f/best for more information.
Page 731
Actualizar Tls AIX
What is the recommended process for upgrading to a new Technology Level or Service Pack in AIX ?
This document describes the recommended preparation and process when considering updating your system to a new technology level or adding a service pack to an existing technology level. In all we will review some key words and terminology, run through recommended pre-checks, discuss the update_all process using both SMIT and command line, and finally post-checks & FAQ.
This represents your operating system level and is mentioned because of the change made in the 5300-07 technology level update. Previous to 5300-07 updates are recognized by their last numerical level entry only.
Beginning with 5300-07 the 3rd number, or Maintenance Level number will also be included and will represent the Technology level of the fileset, followed by the Fix Level.
*Note that the Fix Level entry does not necessarily represent the Service Pack level. Any similarity is simply coincidental.
You will also notice a change to how the operating system level reads. With the introduction of 5300-06 you will notice more information provided when running the oslevel command.
The addition of the last four digits simply represents the year (11) and week (40) of the release of your technology level/service pack (-06-06).
This is the recommended method of installation when upgrading your technology level or service pack level only. This installation method should not be used when attempting to upgrade the version or release level of your operating system.
It is recommended to have at least one back-out method available to you in case a restore is required. Recommended back out methods include : mksysb restore, sysback restore, altinst_rootvg clone, and multibos. More information on any of these back-out methods can be found at the publib documentation site by using this link to click through to the appropriate infocenter and search features found here :
The hd5 logical volume holds your boot image. There are a few checks to make against your boot image before starting your update_all process.
Page 732
Actualizar Tls AIX
The listing under the PV1 column indicates on which disk hd5 is located. Any other entries under PV2..etc, simply represent mirrored copies.
Next, verify your boot image can be successfully recreated using the hdisk# from above and by using /dev/ipldevice.
If either of these two commands fail for any reason, please call the support center for resolution before proceeding.
Finally, with the continual introduction of new devices and hardware the boot images are growing larger. You will want to make sure your hd5 logical volume has enough free and contiguous space to hold the boot image. Currently the recommended allocated space to have for hd5 is 32meg. This is of concern in environments with smaller disk sizes, and should be checked before running an update.
The single partition (in bold (1)) is 32meg in size. This should be enough to contain the boot image. Smaller partition sizes will require more partitions to be allocated.
Your hd5 partitions also need to be contiguous partitions. Check this by running the following command :
You can see in this example that the hd5 logical volume covers the first 3 partitions on the disk and they are all contiguous. If your partitions are not contiguous, or are not covered on the first partitions of the disk please call the software support line for assistance with correcting this.
Again, you may only have 1 partition that is large enough to handle the boot image, or you may have multiple smaller partitions. Either is fine.
Firmware should be kept up to date and be checked whenever a technology level update is considered. In general firmware updates should be applied before software updates, but that is not a rule set in stone. You should always refer to the firmware download site installation information and follow those instructions.
If there are any questions concerning the firmware update, installation instructions, or if there are software considerations please contact the hardware support center first.
Page 733
Actualizar Tls AIX
Ideally this should return to the command line with no output. If you do receive output and are unfamiliar with how to resolve it, please call the support center for assistance before running your upgrade.
In order to see if you have enough space for your update you can run the update_all operation in preview mode. This will provide you with an estimated system resources listing of the necessary space. In order to do this you will first have to install the fileset bos.rte.install. Following are two examples of how to update this fileset first, so a preview update_all can be executed. The example below shows initially committing the bos.rte.install update. If you would feel more comfortable using the apply feature in this case, feel free to do so. Note that if you do Apply you will need to Commit before continuing with the actual update_all process.
Once the installation is complete you will then be able to run the preview operation on the remaining filesets to get an estimate of the required space for your update.
Page 734
Actualizar Tls AIX
This section will cover the update_all process. In all cases the input device (location of the software) will be referred to as being a local cdrom drive (/dev/cd0). You can always use a download directory or nfs mount point, simply substitute the input device as necessary. This process is also executed presuming you are logged in as root (as opposed to using sudo).
Page 735
Actualizar Tls AIX
The only required change would be the option for ACCEPT new license agreements. All other given defaults should remain as they are. Pressing <Enter> here will bring up a confirmation dialog box to which you press <Enter> again. The only other interaction you may have is if you need to switch out a volume of the media package. When complete, the upper left corner Command: field will have one of two outcomes :
OK : Your installation has completed without error. You can either scroll down or exit out and view the /smit.log file for the log of the installation.
FAILED : One or more filesets failed for some reason. You can either scroll down or exit out and view the /smit.log file for the log of the installation. Corrective action should be taken before rebooting.
This command does have a representative manpage so feel free to review the flags, however this command was intended to be easily executed so running a basic update will not be a very long command.
Once complete you will find the log of the installation in /var/adm/ras/install_all_updates.log. By default the fileset updates will be installed in the APPLIED state. The "-c" flag has been added to the above command to specify that all filesets install in the COMMITTED state. See the FAQ at the end of this document for more information concerning APPLIED vs COMMITTED.
Presuming your update_all was successful you will want to check the following commands. If you receive unexpected output please contact the support center for assistance.
This section is contains the most commonly asked questions and a few recommendations concerning the update_all. Most answers will be kept short and to the point (as much as possible).
1. Is it okay to install my Technology Level in the APPLIED state ? What if I want to reject the TL update if there is a problem ?
With the introduction of Technology Levels and the all or nothing packaging format, these updates are bringing in on the upwards of 400+ fileset updates for each TL. Attempting to perform a reject process on so much code simply does not work well, and is not supported. Recommended back-out methods are discussed earlier in this document.
The Service Pack updates are certainly much smaller groups of updates....typically numbering around 40-50 per update. While you certainly will have a better chance of successfully rejecting 40 filesets instead of 400, it would still be best to have one of the back-out methods mentioned earlier.
Page 736
Actualizar Tls AIX
When running an update_all over NFS, you create your own mount point for the cdrom drive. This does not allow it to recognize the fact that there are multiple volumes available that contain the correct requisite filesets. Multiple update_all operations may be needed on each volume when NFS mounting a cdrom drive. A better option may be to bffcreate the contents of all CDs down to a directory, then NFS mount that directory.
Do not reboot. You can review the log to find out what failed and why. If you are comfortable and familiar with these situations you can correct the failures and re-update the filesets. If not, please call the helpdesk and open a PMR for assistance. Have the log available to email in if necessary.
4. I need to run my update today but I may not be able to reboot until next week. Is that a problem ?
Plans should be made to reboot as soon as the update is complete and checks have been made to ensure there were no failures. System files will have been replaced, but the corresponding kernel and library updates will not be loaded until boot time. You will likely encounter problems if you delay rebooting.
If this is possible, absolutely. There are systems out there that have not been rebooted in a year or more. Who is to say that something has not happened in that time that simply would not show up until a reboot. Rebooting the system first assures a good boot image, a stable system, and would isolate any problem that normally would not be caught until the post-update reboot as either a preexisting issue, or an issue directly related to the TL update itself.
6. Some say to use base AIX install media when updating the TL, others say the TL fix downloads or CDs should be used. Which is right ?
The recommendation is to use the TL fix downloads from FixCentral, or the TL CDs that can be ordered either online or from AIX SupportLine. You can also use the base AIX installation media, however without getting into a long answer, the recommendation is using the TL fix packages.
This is a question that does not quite have a definite answer. The length of time required for the update_all depends on how many filesets are being updated as well as the available system resources such as processors and memory.
Giving a ballpark figure however, going up one TL should only take about 30-60 minutes plus reboot time. Some admins prefer to be more on the conservative side and block a 2-3 hour downtime. Consideration should also be made to the amount of time it would take to restore, depending on the backup method selected.
Updating could affect running processes. As such, applications should be down and users offline as a general rule.
Some products may only be certified up to a certain operating system level while other products may require an update. The best thing to do would be to contact product X's support center. If it is an IBM product feel free to contact our support center and open a PMR requesting to speak to the product X team. Any 3rd party products should be cleared by their support before upgrading.
11. The 'oslevel -s' and/or 'oslevel -r' commands do not report what I expect after the udpate. How can I determine what is missing ?
If your 'oslevel' commands do not report correctly after your update_all you can add the "-l" flag to determine which filesets still need to be updated in order to complete your upgrade.
The filesets listed will show an "Actual Level" heading (your current level) and a "Maintenance Level" heading (the level you need to be at to satisfy the TL/SP).
There are cases where a second update_all operations need to be executed to pick up the full TL update. This is not defective behavior. Please also take note that this tip is not intended to resolve a "FAILED" status of your update_all. If you notice that your TL update was successful, but some filesets did not get updated and are on your media or in your download location, you may need to run the update_all a second time to pick them up.
12. What are other best practices with regards to keeping the AIX operating system updated?
Page 737
Actualizar Tls AIX
Page 738
Actualizar Tls AIX
This document describes the recommended preparation and process when considering updating your system to a new technology level or adding a service pack to an existing technology level. In all we will review some key words and terminology, run through recommended pre-checks, discuss the update_all process using both SMIT and command line, and finally post-checks & FAQ.
This represents your operating system level and is mentioned because of the change made in the 5300-07 technology level update. Previous to 5300-07 updates are recognized by their last numerical level entry only.
This is the recommended method of installation when upgrading your technology level or service pack level only. This installation method should not be used when attempting to upgrade the version or release level of your operating system.
It is recommended to have at least one back-out method available to you in case a restore is required. Recommended back out methods include : mksysb restore, sysback restore, altinst_rootvg clone, and multibos. More information on any of these back-out methods can be found at the publib documentation site by using this link to click through to the appropriate infocenter and search features found here :
Page 739
Actualizar Tls AIX
Finally, with the continual introduction of new devices and hardware the boot images are growing larger. You will want to make sure your hd5 logical volume has enough free and contiguous space to hold the boot image. Currently the recommended allocated space to have for hd5 is 32meg. This is of concern in environments with smaller disk sizes, and should be checked before running an update.
You can see in this example that the hd5 logical volume covers the first 3 partitions on the disk and they are all contiguous. If your partitions are not contiguous, or are not covered on the first partitions of the disk please call the software support line for assistance with correcting this.
Firmware should be kept up to date and be checked whenever a technology level update is considered. In general firmware updates should be applied before software updates, but that is not a rule set in stone. You should always refer to the firmware download site installation information and follow those instructions.
Page 740
Actualizar Tls AIX
Ideally this should return to the command line with no output. If you do receive output and are unfamiliar with how to resolve it, please call the support center for assistance before running your upgrade.
In order to see if you have enough space for your update you can run the update_all operation in preview mode. This will provide you with an estimated system resources listing of the necessary space. In order to do this you will first have to install the fileset bos.rte.install. Following are two examples of how to update this fileset first, so a preview update_all can be executed. The example below shows initially committing the bos.rte.install update. If you would feel more comfortable using the apply feature in this case, feel free to do so. Note that if you do Apply you will need to Commit before continuing with the actual update_all process.
Page 741
Actualizar Tls AIX
This section will cover the update_all process. In all cases the input device (location of the software) will be referred to as being a local cdrom drive (/dev/cd0). You can always use a download directory or nfs mount point, simply substitute the input device as necessary. This process is also executed presuming you are logged in as root (as opposed to using sudo).
Page 742
Actualizar Tls AIX
The only required change would be the option for ACCEPT new license agreements. All other given defaults should remain as they are. Pressing <Enter> here will bring up a confirmation dialog box to which you press <Enter> again. The only other interaction you may have is if you need to switch out a volume of the media package. When complete, the upper left corner Command: field will have one of two outcomes :
FAILED : One or more filesets failed for some reason. You can either scroll down or exit out and view the /smit.log file for the log of the installation. Corrective action should be taken before rebooting.
This command does have a representative manpage so feel free to review the flags, however this command was intended to be easily executed so running a basic update will not be a very long command.
Once complete you will find the log of the installation in /var/adm/ras/install_all_updates.log. By default the fileset updates will be installed in the APPLIED state. The "-c" flag has been added to the above command to specify that all filesets install in the COMMITTED state. See the FAQ at the end of this document for more information concerning APPLIED vs COMMITTED.
This section is contains the most commonly asked questions and a few recommendations concerning the update_all. Most answers will be kept short and to the point (as much as possible).
With the introduction of Technology Levels and the all or nothing packaging format, these updates are bringing in on the upwards of 400+ fileset updates for each TL. Attempting to perform a reject process on so much code simply does not work well, and is not supported. Recommended back-out methods are discussed earlier in this document.
The Service Pack updates are certainly much smaller groups of updates....typically numbering around 40-50 per update. While you certainly will have a better chance of successfully rejecting 40 filesets instead of 400, it would still be best to have one of the back-out methods mentioned earlier.
Page 743
Actualizar Tls AIX
When running an update_all over NFS, you create your own mount point for the cdrom drive. This does not allow it to recognize the fact that there are multiple volumes available that contain the correct requisite filesets. Multiple update_all operations may be needed on each volume when NFS mounting a cdrom drive. A better option may be to bffcreate the contents of all CDs down to a directory, then NFS mount that directory.
Do not reboot. You can review the log to find out what failed and why. If you are comfortable and familiar with these situations you can correct the failures and re-update the filesets. If not, please call the helpdesk and open a PMR for assistance. Have the log available to email in if necessary.
Plans should be made to reboot as soon as the update is complete and checks have been made to ensure there were no failures. System files will have been replaced, but the corresponding kernel and library updates will not be loaded until boot time. You will likely encounter problems if you delay rebooting.
If this is possible, absolutely. There are systems out there that have not been rebooted in a year or more. Who is to say that something has not happened in that time that simply would not show up until a reboot. Rebooting the system first assures a good boot image, a stable system, and would isolate any problem that normally would not be caught until the post-update reboot as either a preexisting issue, or an issue directly related to the TL update itself.
The recommendation is to use the TL fix downloads from FixCentral, or the TL CDs that can be ordered either online or from AIX SupportLine. You can also use the base AIX installation media, however without getting into a long answer, the recommendation is using the TL fix packages.
This is a question that does not quite have a definite answer. The length of time required for the update_all depends on how many filesets are being updated as well as the available system resources such as processors and memory.
Giving a ballpark figure however, going up one TL should only take about 30-60 minutes plus reboot time. Some admins prefer to be more on the conservative side and block a 2-3 hour downtime. Consideration should also be made to the amount of time it would take to restore, depending on the backup method selected.
Some products may only be certified up to a certain operating system level while other products may require an update. The best thing to do would be to contact product X's support center. If it is an IBM product feel free to contact our support center and open a PMR requesting to speak to the product X team. Any 3rd party products should be cleared by their support before upgrading.
There are cases where a second update_all operations need to be executed to pick up the full TL update. This is not defective behavior. Please also take note that this tip is not intended to resolve a "FAILED" status of your update_all. If you notice that your TL update was successful, but some filesets did not get updated and are on your media or in your download location, you may need to run the update_all a second time to pick them up.
Page 744
Actualizar Tls AIX
Page 745
Actualizar Tls AIX
This document describes the recommended preparation and process when considering updating your system to a new technology level or adding a service pack to an existing technology level. In all we will review some key words and terminology, run through recommended pre-checks, discuss the update_all process using both SMIT and command line, and finally post-checks & FAQ.
It is recommended to have at least one back-out method available to you in case a restore is required. Recommended back out methods include : mksysb restore, sysback restore, altinst_rootvg clone, and multibos. More information on any of these back-out methods can be found at the publib documentation site by using this link to click through to the appropriate infocenter and search features found here :
Page 746
Actualizar Tls AIX
Finally, with the continual introduction of new devices and hardware the boot images are growing larger. You will want to make sure your hd5 logical volume has enough free and contiguous space to hold the boot image. Currently the recommended allocated space to have for hd5 is 32meg. This is of concern in environments with smaller disk sizes, and should be checked before running an update.
You can see in this example that the hd5 logical volume covers the first 3 partitions on the disk and they are all contiguous. If your partitions are not contiguous, or are not covered on the first partitions of the disk please call the software support line for assistance with correcting this.
Firmware should be kept up to date and be checked whenever a technology level update is considered. In general firmware updates should be applied before software updates, but that is not a rule set in stone. You should always refer to the firmware download site installation information and follow those instructions.
Page 747
Actualizar Tls AIX
In order to see if you have enough space for your update you can run the update_all operation in preview mode. This will provide you with an estimated system resources listing of the necessary space. In order to do this you will first have to install the fileset bos.rte.install. Following are two examples of how to update this fileset first, so a preview update_all can be executed. The example below shows initially committing the bos.rte.install update. If you would feel more comfortable using the apply feature in this case, feel free to do so. Note that if you do Apply you will need to Commit before continuing with the actual update_all process.
Page 748
Actualizar Tls AIX
This section will cover the update_all process. In all cases the input device (location of the software) will be referred to as being a local cdrom drive (/dev/cd0). You can always use a download directory or nfs mount point, simply substitute the input device as necessary. This process is also executed presuming you are logged in as root (as opposed to using sudo).
Page 749
Actualizar Tls AIX
The only required change would be the option for ACCEPT new license agreements. All other given defaults should remain as they are. Pressing <Enter> here will bring up a confirmation dialog box to which you press <Enter> again. The only other interaction you may have is if you need to switch out a volume of the media package. When complete, the upper left corner Command: field will have one of two outcomes :
Once complete you will find the log of the installation in /var/adm/ras/install_all_updates.log. By default the fileset updates will be installed in the APPLIED state. The "-c" flag has been added to the above command to specify that all filesets install in the COMMITTED state. See the FAQ at the end of this document for more information concerning APPLIED vs COMMITTED.
With the introduction of Technology Levels and the all or nothing packaging format, these updates are bringing in on the upwards of 400+ fileset updates for each TL. Attempting to perform a reject process on so much code simply does not work well, and is not supported. Recommended back-out methods are discussed earlier in this document.
The Service Pack updates are certainly much smaller groups of updates....typically numbering around 40-50 per update. While you certainly will have a better chance of successfully rejecting 40 filesets instead of 400, it would still be best to have one of the back-out methods mentioned earlier.
Page 750
Actualizar Tls AIX
When running an update_all over NFS, you create your own mount point for the cdrom drive. This does not allow it to recognize the fact that there are multiple volumes available that contain the correct requisite filesets. Multiple update_all operations may be needed on each volume when NFS mounting a cdrom drive. A better option may be to bffcreate the contents of all CDs down to a directory, then NFS mount that directory.
Do not reboot. You can review the log to find out what failed and why. If you are comfortable and familiar with these situations you can correct the failures and re-update the filesets. If not, please call the helpdesk and open a PMR for assistance. Have the log available to email in if necessary.
Plans should be made to reboot as soon as the update is complete and checks have been made to ensure there were no failures. System files will have been replaced, but the corresponding kernel and library updates will not be loaded until boot time. You will likely encounter problems if you delay rebooting.
If this is possible, absolutely. There are systems out there that have not been rebooted in a year or more. Who is to say that something has not happened in that time that simply would not show up until a reboot. Rebooting the system first assures a good boot image, a stable system, and would isolate any problem that normally would not be caught until the post-update reboot as either a preexisting issue, or an issue directly related to the TL update itself.
The recommendation is to use the TL fix downloads from FixCentral, or the TL CDs that can be ordered either online or from AIX SupportLine. You can also use the base AIX installation media, however without getting into a long answer, the recommendation is using the TL fix packages.
Giving a ballpark figure however, going up one TL should only take about 30-60 minutes plus reboot time. Some admins prefer to be more on the conservative side and block a 2-3 hour downtime. Consideration should also be made to the amount of time it would take to restore, depending on the backup method selected.
Some products may only be certified up to a certain operating system level while other products may require an update. The best thing to do would be to contact product X's support center. If it is an IBM product feel free to contact our support center and open a PMR requesting to speak to the product X team. Any 3rd party products should be cleared by their support before upgrading.
There are cases where a second update_all operations need to be executed to pick up the full TL update. This is not defective behavior. Please also take note that this tip is not intended to resolve a "FAILED" status of your update_all. If you notice that your TL update was successful, but some filesets did not get updated and are on your media or in your download location, you may need to run the update_all a second time to pick them up.
Page 751
Actualizar Tls AIX
Page 752
Actualizar Tls AIX
This document describes the recommended preparation and process when considering updating your system to a new technology level or adding a service pack to an existing technology level. In all we will review some key words and terminology, run through recommended pre-checks, discuss the update_all process using both SMIT and command line, and finally post-checks & FAQ.
It is recommended to have at least one back-out method available to you in case a restore is required. Recommended back out methods include : mksysb restore, sysback restore, altinst_rootvg clone, and multibos. More information on any of these back-out methods can be found at the publib documentation site by using this link to click through to the appropriate infocenter and search features found here :
Page 753
Actualizar Tls AIX
Finally, with the continual introduction of new devices and hardware the boot images are growing larger. You will want to make sure your hd5 logical volume has enough free and contiguous space to hold the boot image. Currently the recommended allocated space to have for hd5 is 32meg. This is of concern in environments with smaller disk sizes, and should be checked before running an update.
Page 754
Actualizar Tls AIX
In order to see if you have enough space for your update you can run the update_all operation in preview mode. This will provide you with an estimated system resources listing of the necessary space. In order to do this you will first have to install the fileset bos.rte.install. Following are two examples of how to update this fileset first, so a preview update_all can be executed. The example below shows initially committing the bos.rte.install update. If you would feel more comfortable using the apply feature in this case, feel free to do so. Note that if you do Apply you will need to Commit before continuing with the actual update_all process.
Page 755
Actualizar Tls AIX
Page 756
Actualizar Tls AIX
The only required change would be the option for ACCEPT new license agreements. All other given defaults should remain as they are. Pressing <Enter> here will bring up a confirmation dialog box to which you press <Enter> again. The only other interaction you may have is if you need to switch out a volume of the media package. When complete, the upper left corner Command: field will have one of two outcomes :
Once complete you will find the log of the installation in /var/adm/ras/install_all_updates.log. By default the fileset updates will be installed in the APPLIED state. The "-c" flag has been added to the above command to specify that all filesets install in the COMMITTED state. See the FAQ at the end of this document for more information concerning APPLIED vs COMMITTED.
Page 757
Actualizar Tls AIX
When running an update_all over NFS, you create your own mount point for the cdrom drive. This does not allow it to recognize the fact that there are multiple volumes available that contain the correct requisite filesets. Multiple update_all operations may be needed on each volume when NFS mounting a cdrom drive. A better option may be to bffcreate the contents of all CDs down to a directory, then NFS mount that directory.
If this is possible, absolutely. There are systems out there that have not been rebooted in a year or more. Who is to say that something has not happened in that time that simply would not show up until a reboot. Rebooting the system first assures a good boot image, a stable system, and would isolate any problem that normally would not be caught until the post-update reboot as either a preexisting issue, or an issue directly related to the TL update itself.
Some products may only be certified up to a certain operating system level while other products may require an update. The best thing to do would be to contact product X's support center. If it is an IBM product feel free to contact our support center and open a PMR requesting to speak to the product X team. Any 3rd party products should be cleared by their support before upgrading.
There are cases where a second update_all operations need to be executed to pick up the full TL update. This is not defective behavior. Please also take note that this tip is not intended to resolve a "FAILED" status of your update_all. If you notice that your TL update was successful, but some filesets did not get updated and are on your media or in your download location, you may need to run the update_all a second time to pick them up.
Page 758
Actualizar Tls AIX
Page 759
Actualizar Tls AIX
Page 760
Actualizar Tls AIX
Page 761
Actualizar Tls AIX
In order to see if you have enough space for your update you can run the update_all operation in preview mode. This will provide you with an estimated system resources listing of the necessary space. In order to do this you will first have to install the fileset bos.rte.install. Following are two examples of how to update this fileset first, so a preview update_all can be executed. The example below shows initially committing the bos.rte.install update. If you would feel more comfortable using the apply feature in this case, feel free to do so. Note that if you do Apply you will need to Commit before continuing with the actual update_all process.
Page 762
Actualizar Tls AIX
Page 763
Actualizar Tls AIX
Page 764
Actualizar Tls AIX
Page 765
Actualizar Tls AIX
Page 766
Actualizar Tls AIX
Page 767
Actualizar Tls AIX
Page 768
Actualizar Tls AIX
In order to see if you have enough space for your update you can run the update_all operation in preview mode. This will provide you with an estimated system resources listing of the necessary space. In order to do this you will first have to install the fileset bos.rte.install. Following are two examples of how to update this fileset first, so a preview update_all can be executed. The example below shows initially committing the bos.rte.install update. If you would feel more comfortable using the apply feature in this case, feel free to do so. Note that if you do Apply you will need to Commit before continuing with the actual update_all process.
Page 769
Actualizar Tls AIX
Page 770
Actualizar Tls AIX
Page 771
Actualizar Tls AIX
Page 772
Actualizar Tls AIX
Page 773
Actualizar Tls AIX
Page 774
Actualizar Tls AIX
Page 775
Actualizar Tls AIX
In order to see if you have enough space for your update you can run the update_all operation in preview mode. This will provide you with an estimated system resources listing of the necessary space. In order to do this you will first have to install the fileset bos.rte.install. Following are two examples of how to update this fileset first, so a preview update_all can be executed. The example below shows initially committing the bos.rte.install update. If you would feel more comfortable using the apply feature in this case, feel free to do so. Note that if you do Apply you will need to Commit before continuing with the actual update_all process.
Page 776
ALTDISKCOPYVIO
Para el vio utilice el comando alt_root_vg -target hdisk1, hdisk1 es el disco destino
Page 777
0506-365 Cannot mount guarded f
0506-365 Cannot mount guarded filesystem.
0506-365 Cannot mount guarded filesystem.
The filesystem is potentially mounted on another node.
http://unixcoders.wordpress.com/2013/08/28/filesystem-mountguard/
The solution is quite easy:
root@server:/ >chfs -a mountguard=no /test
mount: /dev/testlv on /test
0506-365 Cannot mount guarded filesystem.
The filesystem is potentially mounted on another node.
root@server:/ >
root@server:/ >mount -o noguard /test
mount: /dev/testlv on /test
Mount guard override for filesystem.
The filesystem is potentially mounted on another node.
Replaying log for /dev/testlv
Page 778
Crear FS en powerHA
sudo ./cli_mklv -y zdiadian_lv -t jfs2 ci_vg 6G
sudo ./cli_crfs -v jfs2 -A no -a logname=/dev/logcivg -m /ZDIADIAN_local -d zdiadian_lv
Crear Fs en hacmp mejor asi
sudo ./cli_mklv -y stag112_lv -t jfs2 oraclevg 10G
sudo ./cli_crfs -v jfs2 -A no -a check=false -a options=rw -a mountguard=yes -m /oracle/stage/112_64 -d stag112_lv
Page 779
Crear FS en powerHA
sudo ./cli_crfs -v jfs2 -A no -a check=false -a options=rw -a mountguard=yes -m /oracle/stage/112_64 -d stag112_lv
Page 780
borrar rutas y dejar el defaul
Borrar una ruta chdev -l inet0 -a delroute="net,-hopcount,0,,0,10.231.2.1"
Agregar el gateway chdev -l inet0 -a route="net,-hopcount,0,,0,10.205.100.107"
mkvdev -vdev migncpor2_lv -vadapter vhost17 -dev migncerpno2
Page 781
dsh comandos remotos
export WCOLL=/home/gibsonc/wcolls/aix
export DSH_NODE_OPTS="-q" The
DSH_NODE_RSH variable indicates which
remote command executable to use
se guardan los host en un archivo /home/gibsonc/wcolls/aix
se jecuta dsh date; hostname
Page 782
COMPARTIR NFS HACMP
compartir NFS EN HACMP
Apr 22, 2013
10:42:13 AM: Henry Fabian Espinosa: Liliana buenos dias como estas
10:42:55 AM: Liliana Lizarazo Florez: Hola buenos das.
10:43:10 AM: Henry Fabian Espinosa: Liliana que pena contigo es que tengo una pregunta sencilla
10:43:36 AM: Liliana Lizarazo Florez: si, dime.
10:44:12 AM: Henry Fabian Espinosa: en un cluster hacmp cual es el procedimiento para exportar un FS por NFS hacia otros nodois
10:48:41 AM: Liliana Lizarazo Florez: este filesystem debe adicionarse como directorio a exportar en el recurso definido en HACMP. Luego se debe sincronizar el cluster para que actualice la informacin en los nodos del cluster.
10:49:28 AM: Liliana Lizarazo Florez: Pregunta, ese fs. tambin va a se montado en los nodos del cluster?
10:49:33 AM: Henry Fabian Espinosa: sip
10:49:39 AM: Henry Fabian Espinosa: por cross mounting
10:51:20 AM: Henry Fabian Espinosa: ven pero como lo agrego?
10:51:27 AM: Henry Fabian Espinosa: es que la verdad nunca lo he hecho
10:51:58 AM: Henry Fabian Espinosa: y como es el cluster de colombina prefiero preguntarle a alguien que sepa bastante para no embarrarla
10:55:04 AM: Liliana Lizarazo Florez: el filesystem ya est creado?
10:55:13 AM: Henry Fabian Espinosa: sip
10:55:17 AM: Henry Fabian Espinosa: ya esta creado
10:56:05 AM: Liliana Lizarazo Florez: con qu nombre qued?
10:56:39 AM: Henry Fabian Espinosa: /ZDIADIAN_local
10:59:06 AM: Liliana Lizarazo Florez: a que recurso pertenece ese filesystem
10:59:22 AM: Henry Fabian Espinosa: sapscs_rg
10:59:54 AM: Liliana Lizarazo Florez: ingresa por smit a ese recurso
11:00:20 AM: Henry Fabian Espinosa: Move cursor to desired item and press Enter.
Initialization and Standard Configuration
Extended Configuration
System Management (C-SPOC)
Problem Determination Tools
Can't find what you are looking for ?
Not sure where to start ?
11:00:24 AM: Henry Fabian Espinosa: por (C-SPOC)
11:00:26 AM: Henry Fabian Espinosa: cierto
11:02:18 AM: Liliana Lizarazo Florez: un momento.
11:02:24 AM: Henry Fabian Espinosa: ok gracias
11:04:55 AM: Liliana Lizarazo Florez: por extended configuration
11:05:28 AM: Liliana Lizarazo Florez: Luego por Extended Resource configuration
11:05:56 AM: Henry Fabian Espinosa: listo
11:05:57 AM: Henry Fabian Espinosa:
11:06:02 AM: Liliana Lizarazo Florez: HACMP Extended Resource Group Configuration
11:06:21 AM: Henry Fabian Espinosa: Move cursor to desired item and press Enter.
Page 783
COMPARTIR NFS HACMP
Add a Resource Group
Change/Show a Resource Group
Change/Show Resources and Attributes for a Resource Group
Remove a Resource Group
Show All Resources by Node or Resource Group
11:06:25 AM: Liliana Lizarazo Florez: y Change/Show Resources and Attributes for a Resource Group
11:06:55 AM: Henry Fabian Espinosa: ah ok
11:07:02 AM: Henry Fabian Espinosa: Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[Entry Fields]
Resource Group Name sapscs_rg
Participating Nodes (Default Node Priority) prosap1 prosap3
Startup Policy Online On Home Node Only
Fallover Policy Fallover To Next Priority Node In The List
Fallback Policy Never Fallback
Service IP Labels/Addresses [prosap1] +
Application Servers [scsappl_prosap1] +
Volume Groups [ci_vg ] +
Use forced varyon of volume groups, if necessary false +
Automatically Import Volume Groups false +
Filesystems (empty is ALL for VGs specified) [ ] +
Filesystems Consistency Check fsck +
Filesystems Recovery Method sequential +
Filesystems mounted before IP configured true +
Filesystems/Directories to Export (NFSv2/3) [/BANCOS_local /CEN_local /MES_local /archivado_local /ley1393_local /planos_local /sapmnt/PRO_local /usr/sap/trans_local] +
+
Filesystems/Directories to Export (NFSv4) [] +
Stable Storage Path (NFSv4) [] +
Filesystems/Directories to NFS Mount [/BANCOS;/BANCOS_local /CEN;/CEN_local /MES;/MES_local /archivado;/archivado_local /ley1393;/ley1393_local /planos;/planos_local /sapmnt/PR>
Network For NFS Mount [] +
Tape Resources [] +
Raw Disk PVIDs [] +
Fast Connect Services [] +
Communication Links [] +
Primary Workload Manager Class [] +
Secondary Workload Manager Class [] +
Page 784
COMPARTIR NFS HACMP
Miscellaneous Data []
WPAR Name [] +
SVC PPRC Replicated Resources [] +
EMC SRDF(R) Replicated Resources [] +
11:07:26 AM: Henry Fabian Espinosa: y las agrego con ese formato cierto
11:08:19 AM: Liliana Lizarazo Florez: veo que hay un grupo de volumenes exportados, en Filesystems/Directories to Export (NFSv2/3) al final debes adicionar el que vas a exportar
11:08:28 AM: Henry Fabian Espinosa: ah ok
11:09:54 AM: Liliana Lizarazo Florez: y en Filesystems/Directories to NFS Mount tambin adiciona el filesystem como debe quedar montado en el cluster
11:10:03 AM: Henry Fabian Espinosa: ah ok
11:11:07 AM: Henry Fabian Espinosa: listo la verdad son dos NFS que debo exportar
11:11:20 AM: Henry Fabian Espinosa:
11:11:26 AM: Henry Fabian Espinosa: y ya los agregu
11:11:55 AM: Henry Fabian Espinosa: ya hay quedaron los dos
11:12:24 AM: Henry Fabian Espinosa: y listo cierto
11:12:31 AM: Henry Fabian Espinosa: no mas en ese menu
11:13:24 AM: Liliana Lizarazo Florez: si, slo ese menu
11:13:27 AM: Henry Fabian Espinosa: ok
11:13:39 AM: Henry Fabian Espinosa: listo no salieron errores
11:13:43 AM: Henry Fabian Espinosa: COMMAND STATUS
Command: OK stdout: no stderr: no
Before command completion, additional instructions may appear below.
11:14:20 AM: Liliana Lizarazo Florez: te falta hacer la sincronizacin
11:16:07 AM: Henry Fabian Espinosa: esa sincronizacion por donde la realizo
11:17:03 AM: Henry Fabian Espinosa: Pantallazo
11:17:04 AM: Henry Fabian Espinosa:
11:17:25 AM: Liliana Lizarazo Florez: por extended configuration
11:17:48 AM: Henry Fabian Espinosa:
11:17:57 AM: Liliana Lizarazo Florez: si
11:18:00 AM: Henry Fabian Espinosa: eso no genera indisponibilidad de nada cierto
11:18:42 AM: Liliana Lizarazo Florez: no,
11:19:00 AM: Henry Fabian Espinosa:
11:19:19 AM: Henry Fabian Espinosa: le damos Yes
11:19:30 AM: Liliana Lizarazo Florez: si
11:19:46 AM: Henry Fabian Espinosa: listo ya le di enter
11:21:43 AM: Liliana Lizarazo Florez: ya termin o an est verificando la configuracin
11:21:58 AM: Henry Fabian Espinosa: ya termin pero en failed
11:22:06 AM: Henry Fabian Espinosa: WARNING: Directory: /ZDIADIAN_local was specified to be exported on node: prosap1.
Since this is not a filesystem, make sure the filesystem
in which this directory resides has been specified
as a filesystem for the resource group.
Page 785
COMPARTIR NFS HACMP
WARNING: Directory: /ZDIADIAN_local was specified to be exported on node: prosap3.
Since this is not a filesystem, make sure the filesystem
in which this directory resides has been specified
as a filesystem for the resource group.
WARNING: Directory: /DATACREDITO_local was specified to be exported on node: prosap1.
Since this is not a filesystem, make sure the filesystem
in which this directory resides has been specified
as a filesystem for the resource group.
WARNING: Directory: /DATACREDITO_local was specified to be exported on node: prosap3.
Since this is not a filesystem, make sure the filesystem
in which this directory resides has been specified
as a filesystem for the resource group.
WARNING: Directory: /ZDIADIAN_local was specified to be exported on node: prosap1.
Since this is not a filesystem, make sure the filesystem
in which this directory resides has been specified
as a filesystem for the resource group.
11:22:21 AM: Henry Fabian Espinosa: WARNING: Directory: /ZDIADIAN_local was specified to be exported on node: prosap3.
Since this is not a filesystem, make sure the filesystem
in which this directory resides has been specified
as a filesystem for the resource group.
WARNING: Directory: /DATACREDITO_local was specified to be exported on node: prosap1.
Since this is not a filesystem, make sure the filesystem
in which this directory resides has been specified
as a filesystem for the resource group.
WARNING: Directory: /DATACREDITO_local was specified to be exported on node: prosap3.
Since this is not a filesystem, make sure the filesystem
in which this directory resides has been specified
as a filesystem for the resource group.
ERROR:
NFS mount point /DATACREDITO is in VG ci_vg in resource group sapscs_rg.
The NFS mount point must not be in a shared VG.
ERROR:
NFS mount point /DATACREDITO is in VG ci_vg in resource group sapscs_rg.
The NFS mount point must not be in a shared VG.
11:22:45 AM: Henry Fabian Espinosa: NFS mount point /DATACREDITO is in VG ci_vg in resource group sapscs_rg.
The NFS mount point must not be in a shared VG.
Page 786
COMPARTIR NFS HACMP
WARNING: Application monitors are required for detecting application failures
in order for HACMP to recover from them. Application monitors are started
by HACMP when the resource group in which they participate is activated.
The following application(s), shown with their associated resource group,
do not have an application monitor configured:
Application Server Resource Group
-------------------------------- ---------------------------------
orappl_prosap3 oracle_rg
scsappl_prosap1 sapscs_rg
Completed 60 percent of the verification checks
WARNING: Filesystem or directory: /ZDIADIAN_local is configured to be exported in HACMP,
but it does not have a corresponding entry in /usr/es/sbin/cluster/etc/exports file on node: prosap1.
HACMP will use default behavior to export this filesystem or directory.
WARNING: Filesystem or directory: /DATACREDITO_local is configured to be exported in HACMP,
but it does not have a corresponding entry in /usr/es/sbin/cluster/etc/exports file on node: prosap1.
HACMP will use default behavior to export this filesystem or directory.
WARNING: Filesystem or directory: /ZDIADIAN_local is configured to be exported in HACMP,
but it does not have a corresponding entry in /usr/es/sbin/cluster/etc/exports file on node: prosap3.
HACMP will use default behavior to export this filesystem or directory.
WARNING: Filesystem or directory: /DATACREDITO_local is configured to be exported in HACMP,
but it does not have a corresponding entry in /usr/es/sbin/cluster/etc/exports file on node: prosap3.
HACMP will use default behavior to export this filesystem or directory.
11:25:58 AM: Henry Fabian Espinosa: pero mira que veo los filesystems compartidos
11:26:20 AM: Henry Fabian Espinosa: prosap1-PLT/home/ibmadmhe >share
/ZDIADIAN_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/DATACREDITO_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/archivado_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/BANCOS_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/CEN_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/planos_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/sapmnt/PRO_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/usr/sap/trans_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:devsap:qassap:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51:192.168.105.31:192.168.105.29
/ley1393_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:devsap:qassap:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51:192.168.105.31:192.168.105.29
/MES_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
11:27:33 AM: Henry Fabian Espinosa: pero si replic en el otro nodo
11:27:49 AM: Liliana Lizarazo Florez: y mont los filesystems?
11:27:56 AM: Henry Fabian Espinosa: nop no los monto
11:28:07 AM: Henry Fabian Espinosa: prosap3-PLT/home/ibmadmhe >share
/ZDIADIAN_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/DATACREDITO_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/archivado_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/BANCOS_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/CEN_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
Page 787
COMPARTIR NFS HACMP
/planos_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/sapmnt/PRO_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/usr/sap/trans_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:devsap:qassap:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51:192.168.105.31:192.168.105.29
/ley1393_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:devsap:qassap:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51:192.168.105.31:192.168.105.29
/MES_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
11:28:26 AM: Henry Fabian Espinosa: prosap1-PLT/home/ibmadmhe >df -g
Filesystem GB blocks Free %Used Iused %Iused Mounted on
/dev/hd4 1.62 0.78 52% 16443 8% /
/dev/hd2 6.75 1.41 80% 99286 22% /usr
/dev/hd9var 2.00 0.29 86% 31476 27% /var
/dev/hd3 5.00 1.17 77% 1195 1% /tmp
/dev/hd1 4.00 1.39 66% 10061 4% /home
/dev/hd11admin 3.62 3.62 1% 13 1% /audit
/proc - - - - - /proc
/dev/hd10opt 2.25 1.49 34% 12870 4% /opt
/dev/livedump 0.25 0.25 1% 5 1% /var/adm/ras/livedump
/dev/admin_lv 1.00 0.45 55% 430 1% /administrador
/dev/oracle_lv 0.25 0.25 1% 41 1% /oracle
/dev/oracli_lv 0.50 0.17 67% 31 1% /oracle/client
/dev/usrtiv_lv 1.00 0.61 40% 805 1% /usr/tivoli
/dev/datasrv_lv 1.00 0.66 34% 1933 2% /datasvr
/dev/perfdata_lv 4.50 0.63 87% 78466 35% /perfdata
/dev/auditsap_lv 25.25 3.05 88% 1811 1% /audit/sap
/dev/srm_lv 0.12 0.11 10% 93 1% /var/adm/perfmgr
/dev/medioslv 94.75 14.09 86% 22303 1% /medios
/dev/itm_lv 1.00 0.51 50% 4318 4% /opt/IBM/ITM
/dev/bancos_lv 8.00 2.26 72% 6852 2% /BANCOS_local
/dev/cen_lv 1.88 1.25 34% 33554 11% /CEN_local
/dev/mes_lv 2.00 2.00 1% 10 1% /MES_local
/dev/archivado_lv 199.62 23.82 89% 1934 1% /archivado_local
/dev/ley1393_lv 0.12 0.12 7% 49 1% /ley1393_local
/dev/planos_lv 1.12 0.32 72% 5972 8% /planos_local
/dev/sapmnt_lv 25.88 14.60 44% 818581 17% /sapmnt/PRO_local
/dev/tivolisap_lv 0.50 0.50 1% 11 1% /tivolisap
/dev/usrsappro_lv 31.50 22.32 30% 31450 1% /usr/sap/PRO
/dev/usrsaptra_lv 77.75 17.09 79% 249424 6% /usr/sap/trans_local
prosap1:/BANCOS_local 8.00 2.26 72% 6852 2% /BANCOS
prosap1:/CEN_local 1.88 1.25 34% 33554 11% /CEN
prosap1:/MES_local 2.00 2.00 1% 10 1% /MES
prosap1:/archivado_local 199.62 23.82 89% 1934 1% /archivado
prosap1:/ley1393_local 0.12 0.12 7% 49 1% /ley1393
prosap1:/planos_local 1.12 0.32 72% 5972 8% /planos
prosap1:/sapmnt/PRO_local 25.88 14.60 44% 818581 17% /sapmnt/PRO
prosap1:/usr/sap/trans_local 77.75 17.09 79% 249424 6% /usr/sap/trans
/dev/zdiadian_lv 6.00 5.86 3% 461 1% /ZDIADIAN_local
Page 788
COMPARTIR NFS HACMP
/dev/datac_lv 6.00 6.00 1% 4 1% /DATACREDITO_local
11:29:49 AM: Henry Fabian Espinosa: prosap1-PLT/home/ibmadmhe >lsvg -l ci_vg
ci_vg:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
archivado_lv jfs2 1597 1597 4 open/syncd /archivado_local
DATACREDITO_local prosap1 /DATACREDITO nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
cen_lv jfs2 15 15 1 open/syncd /CEN_local
planos_lv jfs2 9 9 1 open/syncd /planos_local
sapmnt_lv jfs2 207 207 1 open/syncd /sapmnt/PRO_local
usrsappro_lv jfs2 252 252 3 open/syncd /usr/sap/PRO
usrsaptra_lv jfs2 622 622 3 open/syncd /usr/sap/trans_local
tivolisap_lv jfs2 4 4 1 open/syncd /tivolisap
ley1393_lv jfs2 1 1 1 open/syncd /ley1393_local
mes_lv jfs2 16 16 1 open/syncd /MES_local
logcivg jfs2log 1 1 1 open/syncd N/A
zdiadian_lv jfs2 48 48 1 open/syncd /ZDIADIAN_local
datac_lv jfs2 48 48 1 open/syncd /DATACREDITO_local
11:31:23 AM: Liliana Lizarazo Florez: cuals son los filesystems nuevos?
11:31:33 AM: Henry Fabian Espinosa: zdiadian_lv jfs2 48 48 1 open/syncd /ZDIADIAN_local
datac_lv jfs2 48 48 1 open/syncd /DATACREDITO_local
11:38:23 AM: Liliana Lizarazo Florez: regalame el lsfs de los dos nodos
11:38:27 AM: Henry Fabian Espinosa: ok
11:38:48 AM: Henry Fabian Espinosa: prosap1-PLT/home/ibmadmhe >lsfs
Name Nodename Mount Pt VFS Size Options Auto Accounting
/dev/hd4 -- / jfs2 3407872 rw yes no
/dev/hd1 -- /home jfs2 8388608 rw yes no
/dev/hd2 -- /usr jfs2 14155776 rw yes no
/dev/hd9var -- /var jfs2 4194304 rw yes no
/dev/hd3 -- /tmp jfs2 10485760 rw yes no
/dev/hd11admin -- /audit jfs2 7602176 rw yes no
/proc -- /proc procfs -- rw yes no
/dev/hd10opt -- /opt jfs2 4718592 rw yes no
/dev/livedump -- /var/adm/ras/livedump jfs2 524288 rw yes no
/dev/admin_lv -- /administrador jfs2 2097152 rw yes no
/dev/oracle_lv -- /oracle jfs2 524288 rw yes no
/dev/oracli_lv -- /oracle/client jfs2 1048576 rw yes no
/dev/usrtiv_lv -- /usr/tivoli jfs2 2097152 rw yes no
/dev/datasrv_lv -- /datasvr jfs2 2097152 rw yes no
/dev/perfdata_lv -- /perfdata jfs2 9437184 rw yes no
/dev/auditsap_lv -- /audit/sap jfs2 52953088 rw yes no
/dev/srm_lv -- /var/adm/perfmgr jfs2 262144 rw yes no
/BANCOS_local prosap1 /BANCOS nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/CEN_local prosap1 /CEN nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/MES_local prosap1 /MES nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
Page 789
COMPARTIR NFS HACMP
/archivado_local prosap1 /archivado nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/ley1393_local prosap1 /ley1393 nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/planos_local prosap1 /planos nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/sapmnt/PRO_local prosap1 /sapmnt/PRO nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/usr/sap/trans_local prosap1 /usr/sap/trans nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/ZDIADIAN_local prosap1 /ZDIADIAN nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
DATACREDITO_local prosap1 /DATACREDITO nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/dev/parches_lv -- /parches_SP4 jfs2 -- rw yes no
/dev/medioslv -- /medios jfs2 198705152 rw yes no
/dev/itm_lv -- /opt/IBM/ITM jfs2 2097152 rw yes no
/dev/archivado_lv -- /archivado_local jfs2 418643968 rw no no
/dev/bancos_lv -- /BANCOS_local jfs2 16777216 rw no no
/dev/cen_lv -- /CEN_local jfs2 3932160 rw no no
/dev/planos_lv -- /planos_local jfs2 2359296 rw no no
/dev/sapmnt_lv -- /sapmnt/PRO_local jfs2 54263808 rw no no
/dev/usrsappro_lv -- /usr/sap/PRO jfs2 66060288 rw no no
/dev/usrsaptra_lv -- /usr/sap/trans_local jfs2 163053568 rw no no
/dev/tivolisap_lv -- /tivolisap jfs2 1048576 rw no no
/dev/ley1393_lv -- /ley1393_local jfs2 262144 rw no no
/dev/mes_lv -- /MES_local jfs2 4194304 rw no no
/dev/zdiadian_lv -- /ZDIADIAN_local jfs2 12582912 rw no no
/dev/mirrlogA_lv -- /oracle/PRO/mirrlogA jfs2 -- rw no no
/dev/mirrlogB_lv -- /oracle/PRO/mirrlogB jfs2 -- rw no no
/dev/orilogA_lv -- /oracle/PRO/origlogA jfs2 -- rw no no
/dev/orilogB_lv -- /oracle/PRO/origlogB jfs2 -- rw no no
/dev/orapro_lv -- /oracle/PRO jfs2 -- rw no no
/dev/orapro_112_lv -- /oracle/PRO/112_64 jfs2 -- rw no no
/dev/sapreorg_lv -- /oracle/PRO/sapreorg jfs2 -- rw no no
/dev/ora_stage_lv -- /oracle/stage jfs2 -- rw no no
/dev/oraarch_lv -- /oracle/PRO/oraarch jfs2 -- rw no no
/dev/itmora_lv -- /itmoracle jfs2 -- rw no no
/dev/tivoliora_lv -- /tivoliora jfs2 -- rw no no
/dev/datac_lv -- /DATACREDITO_local jfs2 12582912 rw no no
/dev/sapdata1_lv -- /oracle/PRO/sapdata1 jfs2 -- rw no no
/dev/sapdata10_lv -- /oracle/PRO/sapdata10 jfs2 -- rw no no
/dev/sapdata11_lv -- /oracle/PRO/sapdata11 jfs2 -- rw no no
/dev/sapdata12_lv -- /oracle/PRO/sapdata12 jfs2 -- rw no no
/dev/sapdata2_lv -- /oracle/PRO/sapdata2 jfs2 -- rw no no
/dev/sapdata3_lv -- /oracle/PRO/sapdata3 jfs2 -- rw no no
/dev/sapdata4_lv -- /oracle/PRO/sapdata4 jfs2 -- rw no no
/dev/sapdata5_lv -- /oracle/PRO/sapdata5 jfs2 -- rw no no
/dev/sapdata6_lv -- /oracle/PRO/sapdata6 jfs2 -- rw no no
/dev/sapdata7_lv -- /oracle/PRO/sapdata7 jfs2 -- rw no no
/dev/sapdata8_lv -- /oracle/PRO/sapdata8 jfs2 -- rw no no
/dev/sapdata9_lv -- /oracle/PRO/sapdata9 jfs2 -- rw no no
/dev/sapdata13_lv -- /oracle/PRO/sapdata13 jfs2 -- rw no no
Page 790
COMPARTIR NFS HACMP
/dev/sapdata14_lv -- /oracle/PRO/sapdata14 jfs2 -- rw no no
11:39:10 AM: Henry Fabian Espinosa:
11:39:10 AM: Henry Fabian Espinosa:
11:39:12 AM: Henry Fabian Espinosa: prosap3-PLT/home/ibmadmhe >lsfs
Name Nodename Mount Pt VFS Size Options Auto Accounting
/dev/hd4 -- / jfs2 3407872 rw yes no
/dev/hd1 -- /home jfs2 5505024 rw yes no
/dev/hd2 -- /usr jfs2 14155776 rw yes no
/dev/hd9var -- /var jfs2 9699328 rw yes no
/dev/hd3 -- /tmp jfs2 8912896 rw yes no
/dev/hd11admin -- /audit jfs2 9175040 rw yes no
/proc -- /proc procfs -- rw yes no
/dev/hd10opt -- /opt jfs2 1835008 rw yes no
/dev/livedump -- /var/adm/ras/livedump jfs2 524288 rw yes no
/dev/admin_lv -- /administrador jfs2 6291456 rw yes no
/dev/auditsap_lv -- /audit/sap jfs2 31457280 rw yes no
/dev/oracle_lv -- /oracle jfs2 15204352 rw yes no
/dev/oracli_lv -- /oracle/client jfs2 2621440 rw yes no
/dev/usrtiv_lv -- /usr/tivoli jfs2 2621440 rw yes no
/dev/perfdata_lv -- /perfdata jfs2 1048576 rw yes no
/dev/optIBM_lv -- /opt/IBM jfs2 4718592 rw yes no
/dev/srm_lv -- /var/adm/perfmgr jfs2 262144 rw yes no
/BANCOS_local prosap1 /BANCOS nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/CEN_local prosap1 /CEN nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/MES_local prosap1 /MES nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/archivado_local prosap1 /archivado nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/ley1393_local prosap1 /ley1393 nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/planos_local prosap1 /planos nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/sapmnt/PRO_local prosap1 /sapmnt/PRO nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/usr/sap/trans_local prosap1 /usr/sap/trans nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/ZDIADIAN_local prosap1 /ZDIADIAN nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/DATACREDITO_local prosap1 /DATACREDITO nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/dev/mirrlogA_lv -- /oracle/PRO/mirrlogA jfs2 3670016 rw no no
/dev/mirrlogB_lv -- /oracle/PRO/mirrlogB jfs2 3670016 rw no no
/dev/orilogA_lv -- /oracle/PRO/origlogA jfs2 3670016 rw no no
/dev/orilogB_lv -- /oracle/PRO/origlogB jfs2 3670016 rw no no
/dev/orapro_lv -- /oracle/PRO jfs2 8388608 rw no no
/dev/orapro_112_lv -- /oracle/PRO/112_64 jfs2 31457280 rw no no
/dev/sapreorg_lv -- /oracle/PRO/sapreorg jfs2 12582912 rw no no
/dev/ora_stage_lv -- /oracle/stage jfs2 12582912 rw no no
/dev/oraarch_lv -- /oracle/PRO/oraarch jfs2 943718400 rw no no
/dev/itmora_lv -- /itmoracle jfs2 13631488 rw no no
/dev/tivoliora_lv -- /tivoliora jfs2 2097152 rw no no
/dev/sapdata1_lv -- /oracle/PRO/sapdata1 jfs2 1255669760 rw no no
/dev/sapdata10_lv -- /oracle/PRO/sapdata10 jfs2 1255669760 rw no no
Page 791
COMPARTIR NFS HACMP
/dev/sapdata11_lv -- /oracle/PRO/sapdata11 jfs2 1255669760 rw no no
/dev/sapdata12_lv -- /oracle/PRO/sapdata12 jfs2 1255669760 rw no no
/dev/sapdata2_lv -- /oracle/PRO/sapdata2 jfs2 1255669760 rw no no
/dev/sapdata3_lv -- /oracle/PRO/sapdata3 jfs2 1255669760 rw no no
/dev/sapdata4_lv -- /oracle/PRO/sapdata4 jfs2 1255669760 rw no no
/dev/sapdata5_lv -- /oracle/PRO/sapdata5 jfs2 1255669760 rw no no
/dev/sapdata6_lv -- /oracle/PRO/sapdata6 jfs2 1255669760 rw no no
/dev/sapdata7_lv -- /oracle/PRO/sapdata7 jfs2 1255669760 rw no no
/dev/sapdata8_lv -- /oracle/PRO/sapdata8 jfs2 1255669760 rw no no
/dev/sapdata9_lv -- /oracle/PRO/sapdata9 jfs2 1255669760 rw no no
/dev/sapdata13_lv -- /oracle/PRO/sapdata13 jfs2 1255669760 rw no no
/dev/archivado_lv -- /archivado_local jfs2 -- rw no no
/dev/bancos_lv -- /BANCOS_local jfs2 -- rw no no
/dev/cen_lv -- /CEN_local jfs2 -- rw no no
/dev/planos_lv -- /planos_local jfs2 -- rw no no
/dev/sapmnt_lv -- /sapmnt/PRO_local jfs2 -- rw no no
/dev/usrsappro_lv -- /usr/sap/PRO jfs2 -- rw no no
/dev/usrsaptra_lv -- /usr/sap/trans_local jfs2 -- rw no no
/dev/tivolisap_lv -- /tivolisap jfs2 -- rw no no
/dev/ley1393_lv -- /ley1393_local jfs2 -- rw no no
/dev/mes_lv -- /MES_local jfs2 -- rw no no
/dev/datac_lv -- /DATACREDITO jfs2 -- rw no no
/dev/sapdata14_lv -- /oracle/PRO/sapdata14 jfs2 1256194048 rw no no
prosap3-PLT/home/ibmadmhe >
11:41:32 AM: Liliana Lizarazo Florez: en prosap3 hay un filesystem local con /dev/datac_lv -- /DATACREDITO con el mismo nombre del fs que se ext exportando por hacmp
11:42:14 AM: Henry Fabian Espinosa: lo quito del /etc/filesystems?
11:42:29 AM: Henry Fabian Espinosa: ah claro
11:42:32 AM: Henry Fabian Espinosa: si toca quitarlo
11:43:43 AM: Henry Fabian Espinosa: ya lo quit
11:43:49 AM: Liliana Lizarazo Florez: ese filsystem a que volumen de grupo pertenece?
11:44:22 AM: Henry Fabian Espinosa: al vg ci_vg
11:44:26 AM: Henry Fabian Espinosa: pero en prosap1
11:44:29 AM: Henry Fabian Espinosa: ambos
11:44:51 AM: Henry Fabian Espinosa: voy a volver a sincronizar
11:44:54 AM: Liliana Lizarazo Florez: y en prosap3 el que es /de/datac_lv?
11:45:14 AM: Henry Fabian Espinosa: no a ninguno
11:46:20 AM: Henry Fabian Espinosa: sincronizo nuavamente?
11:47:55 AM: Liliana Lizarazo Florez: regalame nuevamente la salida del comando lsfs de prosap3
11:47:58 AM: Henry Fabian Espinosa: ok
11:48:13 AM: Henry Fabian Espinosa: prosap3-PLT/home/ibmadmhe >lsfs
Name Nodename Mount Pt VFS Size Options Auto Accounting
/dev/hd4 -- / jfs2 3407872 rw yes no
/dev/hd1 -- /home jfs2 5505024 rw yes no
/dev/hd2 -- /usr jfs2 14155776 rw yes no
/dev/hd9var -- /var jfs2 9699328 rw yes no
Page 792
COMPARTIR NFS HACMP
/dev/hd3 -- /tmp jfs2 8912896 rw yes no
/dev/hd11admin -- /audit jfs2 9175040 rw yes no
/proc -- /proc procfs -- rw yes no
/dev/hd10opt -- /opt jfs2 1835008 rw yes no
/dev/livedump -- /var/adm/ras/livedump jfs2 524288 rw yes no
/dev/admin_lv -- /administrador jfs2 6291456 rw yes no
/dev/auditsap_lv -- /audit/sap jfs2 31457280 rw yes no
/dev/oracle_lv -- /oracle jfs2 15204352 rw yes no
/dev/oracli_lv -- /oracle/client jfs2 2621440 rw yes no
/dev/usrtiv_lv -- /usr/tivoli jfs2 2621440 rw yes no
/dev/perfdata_lv -- /perfdata jfs2 1048576 rw yes no
/dev/optIBM_lv -- /opt/IBM jfs2 4718592 rw yes no
/dev/srm_lv -- /var/adm/perfmgr jfs2 262144 rw yes no
/BANCOS_local prosap1 /BANCOS nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/CEN_local prosap1 /CEN nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/MES_local prosap1 /MES nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/archivado_local prosap1 /archivado nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/ley1393_local prosap1 /ley1393 nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/planos_local prosap1 /planos nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/sapmnt/PRO_local prosap1 /sapmnt/PRO nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/usr/sap/trans_local prosap1 /usr/sap/trans nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/ZDIADIAN_local prosap1 /ZDIADIAN nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/DATACREDITO_local prosap1 /DATACREDITO nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/dev/mirrlogA_lv -- /oracle/PRO/mirrlogA jfs2 3670016 rw no no
/dev/mirrlogB_lv -- /oracle/PRO/mirrlogB jfs2 3670016 rw no no
/dev/orilogA_lv -- /oracle/PRO/origlogA jfs2 3670016 rw no no
/dev/orilogB_lv -- /oracle/PRO/origlogB jfs2 3670016 rw no no
/dev/orapro_lv -- /oracle/PRO jfs2 8388608 rw no no
/dev/orapro_112_lv -- /oracle/PRO/112_64 jfs2 31457280 rw no no
/dev/sapreorg_lv -- /oracle/PRO/sapreorg jfs2 12582912 rw no no
/dev/ora_stage_lv -- /oracle/stage jfs2 12582912 rw no no
/dev/oraarch_lv -- /oracle/PRO/oraarch jfs2 943718400 rw no no
/dev/itmora_lv -- /itmoracle jfs2 13631488 rw no no
/dev/tivoliora_lv -- /tivoliora jfs2 2097152 rw no no
/dev/sapdata1_lv -- /oracle/PRO/sapdata1 jfs2 1255669760 rw no no
/dev/sapdata10_lv -- /oracle/PRO/sapdata10 jfs2 1255669760 rw no no
/dev/sapdata11_lv -- /oracle/PRO/sapdata11 jfs2 1255669760 rw no no
/dev/sapdata12_lv -- /oracle/PRO/sapdata12 jfs2 1255669760 rw no no
/dev/sapdata2_lv -- /oracle/PRO/sapdata2 jfs2 1255669760 rw no no
/dev/sapdata3_lv -- /oracle/PRO/sapdata3 jfs2 1255669760 rw no no
/dev/sapdata4_lv -- /oracle/PRO/sapdata4 jfs2 1255669760 rw no no
/dev/sapdata5_lv -- /oracle/PRO/sapdata5 jfs2 1255669760 rw no no
/dev/sapdata6_lv -- /oracle/PRO/sapdata6 jfs2 1255669760 rw no no
/dev/sapdata7_lv -- /oracle/PRO/sapdata7 jfs2 1255669760 rw no no
/dev/sapdata8_lv -- /oracle/PRO/sapdata8 jfs2 1255669760 rw no no
/dev/sapdata9_lv -- /oracle/PRO/sapdata9 jfs2 1255669760 rw no no
Page 793
COMPARTIR NFS HACMP
/dev/sapdata13_lv -- /oracle/PRO/sapdata13 jfs2 1255669760 rw no no
/dev/archivado_lv -- /archivado_local jfs2 -- rw no no
/dev/bancos_lv -- /BANCOS_local jfs2 -- rw no no
/dev/cen_lv -- /CEN_local jfs2 -- rw no no
/dev/planos_lv -- /planos_local jfs2 -- rw no no
/dev/sapmnt_lv -- /sapmnt/PRO_local jfs2 -- rw no no
/dev/usrsappro_lv -- /usr/sap/PRO jfs2 -- rw no no
/dev/usrsaptra_lv -- /usr/sap/trans_local jfs2 -- rw no no
/dev/tivolisap_lv -- /tivolisap jfs2 -- rw no no
/dev/ley1393_lv -- /ley1393_local jfs2 -- rw no no
/dev/mes_lv -- /MES_local jfs2 -- rw no no
/dev/sapdata14_lv -- /oracle/PRO/sapdata14 jfs2 1256194048 rw no no
11:49:07 AM: Liliana Lizarazo Florez: si, vuelve a correr la sincronizacin.
11:49:10 AM: Henry Fabian Espinosa: ok
11:51:41 AM: Henry Fabian Espinosa: ERROR:
NFS mount point /DATACREDITO is in VG ci_vg in resource group sapscs_rg.
The NFS mount point must not be in a shared VG.
ERROR:
NFS mount point /DATACREDITO is in VG ci_vg in resource group sapscs_rg.
The NFS mount point must not be in a shared VG.
11:52:13 AM: Liliana Lizarazo Florez: cmo se cre ese filsystem?
11:52:47 AM: Henry Fabian Espinosa: se creo as
11:53:16 AM: Henry Fabian Espinosa: sudo ./cli_mklv -y zdiadian_lv -t jfs2 ci_vg 6G
sudo ./cli_crfs -v jfs2 -A no -m /ZDIADIAN_local -d zdiadian_lv
11:53:48 AM: Henry Fabian Espinosa: en la ruta /usr/es/sbin/cluster/cspoc
11:54:42 AM: Liliana Lizarazo Florez: y el de /DATACREDITO
11:54:45 AM: Henry Fabian Espinosa: igual
11:54:56 AM: Henry Fabian Espinosa: los dos de la misma forma
11:57:34 AM: Liliana Lizarazo Florez: pero cuando se cre /DATACREDITO se le di el path /DATCREDITO_local o se cambio despus?
11:58:04 AM: Henry Fabian Espinosa: no se creo /DATCREDITO_local
11:58:09 AM: Henry Fabian Espinosa: se creo /DATCREDITO_local
11:58:17 AM: Henry Fabian Espinosa: si quieres lo puedo borrar
11:58:21 AM: Henry Fabian Espinosa: y lo volvemos a crear
12:02:33 PM: Liliana Lizarazo Florez: en prosap1 aparece /dev/datac_lv -- /DATACREDITO_local jfs2 12582912 rw no no y en prosap3 apareca como /dev/datac_lv -- /DATACREDITO jfs2 -- rw no no
12:03:37 PM: Liliana Lizarazo Florez: deja nuevamente el /etc/filesystem como estaba
12:03:53 PM: Liliana Lizarazo Florez: y vamos a verificar en HACMP como ve este filesystem
12:05:43 PM: Henry Fabian Espinosa: #File System Volume Group Resource Group Node List
/archivado_local ci_vg sapscs_rg prosap3,prosap1
/BANCOS_local ci_vg sapscs_rg prosap3,prosap1
/CEN_local ci_vg sapscs_rg prosap3,prosap1
/planos_local ci_vg sapscs_rg prosap3,prosap1
/sapmnt/PRO_local ci_vg sapscs_rg prosap3,prosap1
/usr/sap/PRO ci_vg sapscs_rg prosap3,prosap1
Page 794
COMPARTIR NFS HACMP
/usr/sap/trans_local ci_vg sapscs_rg prosap3,prosap1
/tivolisap ci_vg sapscs_rg prosap3,prosap1
/ley1393_local ci_vg sapscs_rg prosap3,prosap1
/MES_local ci_vg sapscs_rg prosap3,prosap1
/ZDIADIAN_local ci_vg sapscs_rg prosap3,prosap1
/DATACREDITO_local ci_vg sapscs_rg prosap3,prosap1
/oracle/PRO/sapdata1 db_vg oracle_rg prosap1,prosap3
/oracle/PRO/sapdata10 db_vg oracle_rg prosap1,prosap3
/oracle/PRO/sapdata11 db_vg oracle_rg prosap1,prosap3
/oracle/PRO/sapdata12 db_vg oracle_rg prosap1,prosap3
/oracle/PRO/sapdata2 db_vg oracle_rg prosap1,prosap3
/oracle/PRO/sapdata3 db_vg oracle_rg prosap1,prosap3
/oracle/PRO/sapdata4 db_vg oracle_rg prosap1,prosap3
/oracle/PRO/sapdata5 db_vg oracle_rg prosap1,prosap3
/oracle/PRO/sapdata6 db_vg oracle_rg prosap1,prosap3
/oracle/PRO/sapdata7 db_vg oracle_rg prosap1,prosap3
/oracle/PRO/sapdata8 db_vg oracle_rg prosap1,prosap3
/oracle/PRO/sapdata9 db_vg oracle_rg prosap1,prosap3
/oracle/PRO/sapdata13 db_vg oracle_rg prosap1,prosap3
/oracle/PRO/sapdata14 db_vg oracle_rg prosap1,prosap3
prosap1: /usr/sbin/synclvodm: No logical volumes in volume group hb_vg.
/oracle/PRO/mirrlogA log_vg oracle_rg prosap1,prosap3
/oracle/PRO/mirrlogB log_vg oracle_rg prosap1,prosap3
/oracle/PRO/origlogA log_vg oracle_rg prosap1,prosap3
/oracle/PRO/origlogB log_vg oracle_rg prosap1,prosap3
/oracle/PRO ora_vg oracle_rg prosap1,prosap3
/oracle/PRO/112_64 ora_vg oracle_rg prosap1,prosap3
/oracle/PRO/sapreorg ora_vg oracle_rg prosap1,prosap3
/oracle/stage ora_vg oracle_rg prosap1,prosap3
/oracle/PRO/oraarch ora_vg oracle_rg prosap1,prosap3
/itmoracle ora_vg oracle_rg prosap1,prosap3
/tivoliora ora_vg oracle_rg prosap1,prosap3
12:05:47 PM: Henry Fabian Espinosa: mira el prosap1
12:06:50 PM: Henry Fabian Espinosa: #File System Volume Group Resource Group Node List
/archivado_local ci_vg sapscs_rg prosap3,prosap1
/BANCOS_local ci_vg sapscs_rg prosap3,prosap1
/CEN_local ci_vg sapscs_rg prosap3,prosap1
/planos_local ci_vg sapscs_rg prosap3,prosap1
/sapmnt/PRO_local ci_vg sapscs_rg prosap3,prosap1
/usr/sap/PRO ci_vg sapscs_rg prosap3,prosap1
/usr/sap/trans_local ci_vg sapscs_rg prosap3,prosap1
/tivolisap ci_vg sapscs_rg prosap3,prosap1
/ley1393_local ci_vg sapscs_rg prosap3,prosap1
/MES_local ci_vg sapscs_rg prosap3,prosap1
/ZDIADIAN_local ci_vg sapscs_rg prosap3,prosap1
Page 795
COMPARTIR NFS HACMP
/DATACREDITO_local ci_vg sapscs_rg prosap3,prosap1
/oracle/PRO/sapdata1 db_vg oracle_rg prosap1,prosap3
/oracle/PRO/sapdata10 db_vg oracle_rg prosap1,prosap3
/oracle/PRO/sapdata11 db_vg oracle_rg prosap1,prosap3
/oracle/PRO/sapdata12 db_vg oracle_rg prosap1,prosap3
/oracle/PRO/sapdata2 db_vg oracle_rg prosap1,prosap3
/oracle/PRO/sapdata3 db_vg oracle_rg prosap1,prosap3
/oracle/PRO/sapdata4 db_vg oracle_rg prosap1,prosap3
/oracle/PRO/sapdata5 db_vg oracle_rg prosap1,prosap3
/oracle/PRO/sapdata6 db_vg oracle_rg prosap1,prosap3
/oracle/PRO/sapdata7 db_vg oracle_rg prosap1,prosap3
/oracle/PRO/sapdata8 db_vg oracle_rg prosap1,prosap3
/oracle/PRO/sapdata9 db_vg oracle_rg prosap1,prosap3
/oracle/PRO/sapdata13 db_vg oracle_rg prosap1,prosap3
/oracle/PRO/sapdata14 db_vg oracle_rg prosap1,prosap3
prosap3: synclvodm: No logical volumes in volume group hb_vg.
prosap3: /usr/sbin/synclvodm: No logical volumes in volume group hb_vg.
/oracle/PRO/mirrlogA log_vg oracle_rg prosap1,prosap3
/oracle/PRO/mirrlogB log_vg oracle_rg prosap1,prosap3
/oracle/PRO/origlogA log_vg oracle_rg prosap1,prosap3
/oracle/PRO/origlogB log_vg oracle_rg prosap1,prosap3
/oracle/PRO ora_vg oracle_rg prosap1,prosap3
/oracle/PRO/112_64 ora_vg oracle_rg prosap1,prosap3
/oracle/PRO/sapreorg ora_vg oracle_rg prosap1,prosap3
/oracle/stage ora_vg oracle_rg prosap1,prosap3
/oracle/PRO/oraarch ora_vg oracle_rg prosap1,prosap3
12:07:06 PM: Henry Fabian Espinosa: /itmoracle ora_vg oracle_rg prosap1,prosap3
/tivoliora ora_vg oracle_rg prosap1,prosap3
12:08:11 PM: Henry Fabian Espinosa: pero no lo agregu
12:08:16 PM: Henry Fabian Espinosa: no lo deje como estaba
12:08:32 PM: Henry Fabian Espinosa: mentiras no o deje como estaba
12:08:45 PM: Henry Fabian Espinosa: no le agregue el filesystem
12:11:58 PM: Liliana Lizarazo Florez: si corres el lsfs en prosap3 te aparece /DATACREDITO_local
12:13:19 PM: Henry Fabian Espinosa: prosap3-PLT/home/ibmadmhe >lsfs |grep /DATA
/DATACREDITO_local prosap1 /DATACREDITO nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
12:13:23 PM: Henry Fabian Espinosa: solo el nfs
12:13:57 PM: Liliana Lizarazo Florez: debera ver el filseystem como local tal como est en prosap1
12:14:02 PM: Henry Fabian Espinosa: si cierto
12:14:15 PM: Henry Fabian Espinosa: y /ZDIADIAN tampoco est
12:15:07 PM: Henry Fabian Espinosa: y si copiamos el /etc/filesystems
12:15:14 PM: Henry Fabian Espinosa: del nodo prosap1 y prosap3
12:15:20 PM: Henry Fabian Espinosa: del nodo prosap1 al prosap3
12:15:26 PM: Henry Fabian Espinosa: para que queden iguales
Page 796
COMPARTIR NFS HACMP
12:15:31 PM: Henry Fabian Espinosa: para probar
12:16:21 PM: Liliana Lizarazo Florez: no. slo copia lo que tiene que ver con estos dos filsystems
12:16:26 PM: Henry Fabian Espinosa: ah ok
12:16:27 PM: Henry Fabian Espinosa: vale
12:21:30 PM: Henry Fabian Espinosa: prosap3-PLT/home/ibmadmhe >
prosap3-PLT/home/ibmadmhe >lsfs
Name Nodename Mount Pt VFS Size Options Auto Accounting
/dev/hd4 -- / jfs2 3407872 rw yes no
/dev/hd1 -- /home jfs2 5505024 rw yes no
/dev/hd2 -- /usr jfs2 14155776 rw yes no
/dev/hd9var -- /var jfs2 9699328 rw yes no
/dev/hd3 -- /tmp jfs2 8912896 rw yes no
/dev/hd11admin -- /audit jfs2 9175040 rw yes no
/proc -- /proc procfs -- rw yes no
/dev/hd10opt -- /opt jfs2 1835008 rw yes no
/dev/livedump -- /var/adm/ras/livedump jfs2 524288 rw yes no
/dev/admin_lv -- /administrador jfs2 6291456 rw yes no
/dev/auditsap_lv -- /audit/sap jfs2 31457280 rw yes no
/dev/oracle_lv -- /oracle jfs2 15204352 rw yes no
/dev/oracli_lv -- /oracle/client jfs2 2621440 rw yes no
/dev/usrtiv_lv -- /usr/tivoli jfs2 2621440 rw yes no
/dev/perfdata_lv -- /perfdata jfs2 1048576 rw yes no
/dev/optIBM_lv -- /opt/IBM jfs2 4718592 rw yes no
/dev/srm_lv -- /var/adm/perfmgr jfs2 262144 rw yes no
/BANCOS_local prosap1 /BANCOS nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/CEN_local prosap1 /CEN nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/MES_local prosap1 /MES nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/archivado_local prosap1 /archivado nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/ley1393_local prosap1 /ley1393 nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/planos_local prosap1 /planos nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/sapmnt/PRO_local prosap1 /sapmnt/PRO nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/usr/sap/trans_local prosap1 /usr/sap/trans nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/ZDIADIAN_local prosap1 /ZDIADIAN nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/DATACREDITO_local prosap1 /DATACREDITO nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/dev/mirrlogA_lv -- /oracle/PRO/mirrlogA jfs2 3670016 rw no no
/dev/mirrlogB_lv -- /oracle/PRO/mirrlogB jfs2 3670016 rw no no
/dev/orilogA_lv -- /oracle/PRO/origlogA jfs2 3670016 rw no no
/dev/orilogB_lv -- /oracle/PRO/origlogB jfs2 3670016 rw no no
/dev/orapro_lv -- /oracle/PRO jfs2 8388608 rw no no
/dev/orapro_112_lv -- /oracle/PRO/112_64 jfs2 31457280 rw no no
/dev/sapreorg_lv -- /oracle/PRO/sapreorg jfs2 12582912 rw no no
/dev/ora_stage_lv -- /oracle/stage jfs2 12582912 rw no no
/dev/oraarch_lv -- /oracle/PRO/oraarch jfs2 943718400 rw no no
/dev/itmora_lv -- /itmoracle jfs2 13631488 rw no no
/dev/tivoliora_lv -- /tivoliora jfs2 2097152 rw no no
/dev/sapdata1_lv -- /oracle/PRO/sapdata1 jfs2 1255669760 rw no no
Page 797
COMPARTIR NFS HACMP
/dev/sapdata10_lv -- /oracle/PRO/sapdata10 jfs2 1255669760 rw no no
/dev/sapdata11_lv -- /oracle/PRO/sapdata11 jfs2 1255669760 rw no no
/dev/sapdata12_lv -- /oracle/PRO/sapdata12 jfs2 1255669760 rw no no
/dev/sapdata2_lv -- /oracle/PRO/sapdata2 jfs2 1255669760 rw no no
/dev/sapdata3_lv -- /oracle/PRO/sapdata3 jfs2 1255669760 rw no no
/dev/sapdata4_lv -- /oracle/PRO/sapdata4 jfs2 1255669760 rw no no
/dev/sapdata5_lv -- /oracle/PRO/sapdata5 jfs2 1255669760 rw no no
/dev/sapdata6_lv -- /oracle/PRO/sapdata6 jfs2 1255669760 rw no no
/dev/sapdata7_lv -- /oracle/PRO/sapdata7 jfs2 1255669760 rw no no
/dev/sapdata8_lv -- /oracle/PRO/sapdata8 jfs2 1255669760 rw no no
/dev/sapdata9_lv -- /oracle/PRO/sapdata9 jfs2 1255669760 rw no no
/dev/sapdata13_lv -- /oracle/PRO/sapdata13 jfs2 1255669760 rw no no
/dev/archivado_lv -- /archivado_local jfs2 -- rw no no
/dev/bancos_lv -- /BANCOS_local jfs2 -- rw no no
/dev/cen_lv -- /CEN_local jfs2 -- rw no no
/dev/planos_lv -- /planos_local jfs2 -- rw no no
/dev/sapmnt_lv -- /sapmnt/PRO_local jfs2 -- rw no no
/dev/usrsappro_lv -- /usr/sap/PRO jfs2 -- rw no no
/dev/usrsaptra_lv -- /usr/sap/trans_local jfs2 -- rw no no
/dev/tivolisap_lv -- /tivolisap jfs2 -- rw no no
/dev/ley1393_lv -- /ley1393_local jfs2 -- rw no no
/dev/mes_lv -- /MES_local jfs2 -- rw no no
/dev/sapdata14_lv -- /oracle/PRO/sapdata14 jfs2 1256194048 rw no no
/dev/datac_lv -- /DATACREDITO_local jfs2 -- rw no no
/dev/zdiadian_lv -- /ZDIADIAN_local jfs2 -- rw no no
12:21:35 PM: Henry Fabian Espinosa: ya las agregue
12:24:38 PM: Liliana Lizarazo Florez: vuelve a hacer la verificacin del cluster
12:25:15 PM: Henry Fabian Espinosa: ok
12:26:03 PM: Henry Fabian Espinosa: igual
12:26:04 PM: Henry Fabian Espinosa: ERROR:
NFS mount point /DATACREDITO is in VG ci_vg in resource group sapscs_rg.
The NFS mount point must not be in a shared VG.
ERROR:
NFS mount point /DATACREDITO is in VG ci_vg in resource group sapscs_rg.
The NFS mount point must not be in a shared VG.
12:26:15 PM: Henry Fabian Espinosa: y con los mismos warnning
12:28:17 PM: Henry Fabian Espinosa: Command: failed stdout: yes stderr: no
Before command completion, additional instructions may appear below.
[TOP]
The following file collections will be processed:
HACMPSCRIPTS
Page 798
COMPARTIR NFS HACMP
Starting file propagation to remote node prosap3.
Total number of files propagated to node prosap3: 0
WARNING: Running cluster verification in modified mode verifies only those HA components that have changed.
If you have made system level changes to your cluster nodes, please re-execute verification in normal mode.
HACMPadapter Modified
HACMPnode Modified
HACMPresource Modified
HACMPtopsvcs Modified
Verification to be performed on the following:
Cluster Topology
Cluster Resources
Retrieving data from available cluster nodes. This could take a few minutes.
Start data collection on node prosap1
Start data collection on node prosap3
Collector on node prosap3 completed
Collector on node prosap1 completed
Data collection complete
Verifying Cluster Topology...
Completed 10 percent of the verification checks
Completed 20 percent of the verification checks
WARNING: Multiple communication interfaces are recommended for networks that
use IP aliasing in order to prevent the communication interface from
becoming a single point of failure. There are fewer than the recommended
number of communication interfaces defined on the following node(s) for
the given network(s):
Node: Network:
---------------------------------- ----------------------------------
prosap1 net_ether_01
prosap3 net_ether_01
Completed 30 percent of the verification checks
Completed 40 percent of the verification checks
Verifying Cluster Resources...
Completed 50 percent of the verification checks
Page 799
COMPARTIR NFS HACMP
WARNING: Directory: /ZDIADIAN_local was specified to be exported on node: prosap1.
Since this is not a filesystem, make sure the filesystem
in which this directory resides has been specified
as a filesystem for the resource group.
WARNING: Directory: /ZDIADIAN_local was specified to be exported on node: prosap3.
Since this is not a filesystem, make sure the filesystem
in which this directory resides has been specified
as a filesystem for the resource group.
WARNING: Directory: /DATACREDITO_local was specified to be exported on node: prosap1.
Since this is not a filesystem, make sure the filesystem
in which this directory resides has been specified
as a filesystem for the resource group.
WARNING: Directory: /DATACREDITO_local was specified to be exported on node: prosap3.
Since this is not a filesystem, make sure the filesystem
in which this directory resides has been specified
as a filesystem for the resource group.
WARNING: Directory: /ZDIADIAN_local was specified to be exported on node: prosap1.
Since this is not a filesystem, make sure the filesystem
in which this directory resides has been specified
as a filesystem for the resource group.
WARNING: Directory: /ZDIADIAN_local was specified to be exported on node: prosap3.
Since this is not a filesystem, make sure the filesystem
in which this directory resides has been specified
as a filesystem for the resource group.
WARNING: Directory: /DATACREDITO_local was specified to be exported on node: prosap1.
Since this is not a filesystem, make sure the filesystem
in which this directory resides has been specified
as a filesystem for the resource group.
WARNING: Directory: /DATACREDITO_local was specified to be exported on node: prosap3.
Since this is not a filesystem, make sure the filesystem
in which this directory resides has been specified
as a filesystem for the resource group.
ERROR:
NFS mount point /DATACREDITO is in VG ci_vg in resource group sapscs_rg.
The NFS mount point must not be in a shared VG.
ERROR:
NFS mount point /DATACREDITO is in VG ci_vg in resource group sapscs_rg.
The NFS mount point must not be in a shared VG.
Page 800
COMPARTIR NFS HACMP
WARNING: Application monitors are required for detecting application failures
in order for HACMP to recover from them. Application monitors are started
by HACMP when the resource group in which they participate is activated.
The following application(s), shown with their associated resource group,do not have an application monitor configured:
Application Server Resource Group
-------------------------------- ---------------------------------
orappl_prosap3 oracle_rg
scsappl_prosap1 sapscs_rg
Completed 60 percent of the verification checks
WARNING: Filesystem or directory: /ZDIADIAN_local is configured to be exported in HACMP,
but it does not have a corresponding entry in /usr/es/sbin/cluster/etc/exports file on node: prosap1.
HACMP will use default behavior to export this filesystem or directory.
WARNING: Filesystem or directory: /DATACREDITO_local is configured to be exported in HACMP,
but it does not have a corresponding entry in /usr/es/sbin/cluster/etc/exports file on node: prosap1.
HACMP will use default behavior to export this filesystem or directory.
WARNING: Filesystem or directory: /ZDIADIAN_local is configured to be exported in HACMP,
but it does not have a corresponding entry in /usr/es/sbin/cluster/etc/exports file on node: prosap3.
HACMP will use default behavior to export this filesystem or directory.
WARNING: Filesystem or directory: /DATACREDITO_local is configured to be exported in HACMP,
but it does not have a corresponding entry in /usr/es/sbin/cluster/etc/exports file on node: prosap3.
HACMP will use default behavior to export this filesystem or directory.
Completed 70 percent of the verification checks
Completed 80 percent of the verification checks
Completed 90 percent of the verification checks
Verifying XD Solutions...
Completed 100 percent of the verification checks
Verification exiting with error count: 2
cldare: Failures detected during verification. Please correct
the errors and retry this command.
Verification has completed normally.
12:30:52 PM: Liliana Lizarazo Florez: es como si en los nodos la informacin del filesystem estuviera inconsistente. Trata de remover el filesystem y vuelvelo a crear
12:31:10 PM: Henry Fabian Espinosa: el /DATACREDITO cierto
12:31:12 PM: Henry Fabian Espinosa: unicamente
12:31:17 PM: Liliana Lizarazo Florez: si.
12:31:26 PM: Henry Fabian Espinosa: ven y esos warnnings son normales
12:31:26 PM: Henry Fabian Espinosa: =
12:34:21 PM: Liliana Lizarazo Florez: en este caso son normales, porque el nombre del filesystem lo est viendo diferente, para HACMP el nombre es /DATACREDITO y no /DATACREDITO_local
Page 801
COMPARTIR NFS HACMP
12:34:30 PM: Henry Fabian Espinosa: ah ok
12:34:47 PM: Henry Fabian Espinosa: mira le d prosap1-PLT/usr/es/sbin/cluster/cspoc >sudo ./cli_rmfs /DATACREDITO_local
12:35:33 PM: Henry Fabian Espinosa: voy a eliminar el logical volumen
12:35:55 PM: Henry Fabian Espinosa: pero antes lo quito manualmente del /etc/filesystem en ambos nodos cierto
12:36:01 PM: Henry Fabian Espinosa: para que no halla problema
12:36:14 PM: Liliana Lizarazo Florez: no, ya no debera existir.
12:36:24 PM: Henry Fabian Espinosa: prosap1-PLT/usr/es/sbin/cluster/cspoc >lsfs |grep /DATA
/DATACREDITO_local prosap1 /DATACREDITO nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/dev/datac_lv -- /DATACREDITO_local jfs2 -- rw no no
prosap1-PLT/usr/es/sbin/cluster/cspoc >
12:36:41 PM: Henry Fabian Espinosa: no lo borr
12:39:26 PM: Liliana Lizarazo Florez: entonces, no est haciendo de manera correcta la operacin.
12:39:48 PM: Henry Fabian Espinosa: pues hagamos una prueba y comprobamos
12:39:55 PM: Henry Fabian Espinosa: lo quito del /etc/filesystem
12:39:59 PM: Henry Fabian Espinosa: de ambos nodos
12:39:59 PM: Liliana Lizarazo Florez: si.
12:40:08 PM: Henry Fabian Espinosa: y lo vuelvo a crear
12:40:14 PM: Henry Fabian Espinosa: y hay nos damos cuenta
12:40:26 PM: Henry Fabian Espinosa: y lo crea en ambos nodos correcto?
12:40:49 PM: Liliana Lizarazo Florez: si, la operacin debe ejecutarse en ambos nodos, para que el cluster est consistente.
12:40:55 PM: Henry Fabian Espinosa: ok
12:41:27 PM: Henry Fabian Espinosa: prosap1-PLT/usr/es/sbin/cluster/cspoc >sudo ./cli_rmlv datac_lv
0518-507 odmget: Could not retrieve object for HACMPresource, ODM error number 5904
prosap1: rmlv: Logical volume datac_lv is removed.
12:42:45 PM: Henry Fabian Espinosa: pero si lo borro del prosap3
12:42:51 PM: Henry Fabian Espinosa: del /etc/filesysytems
12:43:12 PM: Liliana Lizarazo Florez: y en prosap1 tambin?
12:43:18 PM: Henry Fabian Espinosa: no en prosap1 no
12:43:25 PM: Henry Fabian Espinosa: ya lo borr
12:43:34 PM: Henry Fabian Espinosa: ahora voy a crearlo nuevamente
12:43:42 PM: Liliana Lizarazo Florez: ok.
12:46:12 PM: Henry Fabian Espinosa: listo
12:46:14 PM: Henry Fabian Espinosa: ya lo cree
12:46:30 PM: Henry Fabian Espinosa: y en ambos nodos los relaciono en el /etc/filesystems
12:46:55 PM: Liliana Lizarazo Florez: como se ve el lsfa
12:47:00 PM: Liliana Lizarazo Florez: digo lsfs
12:47:16 PM: Henry Fabian Espinosa: prosap1-PLT/home/ibmadmhe >lsfs |grep DATA
/DATACREDITO_local prosap1 /DATACREDITO nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/dev/data_lv -- /DATACREDITO_local jfs2 12582912 rw no no
12:47:30 PM: Henry Fabian Espinosa: prosap3-PLT/home/ibmadmhe >lsfs |grep /DATACREDITO_local
/DATACREDITO_local prosap1 /DATACREDITO nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/dev/data_lv -- /DATACREDITO_local jfs2 -- rw no no
prosap3-PLT/home/ibmadmhe >
Page 802
COMPARTIR NFS HACMP
12:47:44 PM: Henry Fabian Espinosa: listo intentamos sincronizar?
12:47:52 PM: Liliana Lizarazo Florez: si.
12:49:29 PM: Henry Fabian Espinosa: listo ya salio OK
12:49:44 PM: Liliana Lizarazo Florez: ejecuta un df
12:50:06 PM: Henry Fabian Espinosa: prosap1-PLT/home/ibmadmhe >df -g
Filesystem GB blocks Free %Used Iused %Iused Mounted on
/dev/hd4 1.62 0.78 52% 16451 8% /
/dev/hd2 6.75 1.41 80% 99286 22% /usr
/dev/hd9var 2.00 0.30 85% 31464 26% /var
/dev/hd3 5.00 1.17 77% 1194 1% /tmp
/dev/hd1 4.00 1.39 66% 10061 4% /home
/dev/hd11admin 3.62 3.62 1% 13 1% /audit
/proc - - - - - /proc
/dev/hd10opt 2.25 1.49 34% 12870 4% /opt
/dev/livedump 0.25 0.25 1% 5 1% /var/adm/ras/livedump
/dev/admin_lv 1.00 0.45 55% 430 1% /administrador
/dev/oracle_lv 0.25 0.25 1% 41 1% /oracle
/dev/oracli_lv 0.50 0.17 67% 31 1% /oracle/client
/dev/usrtiv_lv 1.00 0.61 40% 805 1% /usr/tivoli
/dev/datasrv_lv 1.00 0.66 34% 1933 2% /datasvr
/dev/perfdata_lv 4.50 0.63 87% 78468 35% /perfdata
/dev/auditsap_lv 25.25 3.04 88% 1811 1% /audit/sap
/dev/srm_lv 0.12 0.11 10% 93 1% /var/adm/perfmgr
/dev/medioslv 94.75 14.09 86% 22303 1% /medios
/dev/itm_lv 1.00 0.51 50% 4318 4% /opt/IBM/ITM
/dev/bancos_lv 8.00 2.26 72% 6852 2% /BANCOS_local
/dev/cen_lv 1.88 1.25 34% 33594 11% /CEN_local
/dev/mes_lv 2.00 2.00 1% 10 1% /MES_local
/dev/archivado_lv 199.62 23.82 89% 1934 1% /archivado_local
/dev/ley1393_lv 0.12 0.12 7% 49 1% /ley1393_local
/dev/planos_lv 1.12 0.32 72% 5972 8% /planos_local
/dev/sapmnt_lv 25.88 14.59 44% 820081 17% /sapmnt/PRO_local
/dev/tivolisap_lv 0.50 0.50 1% 11 1% /tivolisap
/dev/usrsappro_lv 31.50 22.29 30% 31450 1% /usr/sap/PRO
/dev/usrsaptra_lv 77.75 17.09 79% 249463 6% /usr/sap/trans_local
prosap1:/BANCOS_local 8.00 2.26 72% 6852 2% /BANCOS
prosap1:/CEN_local 1.88 1.25 34% 33594 11% /CEN
prosap1:/MES_local 2.00 2.00 1% 10 1% /MES
prosap1:/archivado_local 199.62 23.82 89% 1934 1% /archivado
prosap1:/ley1393_local 0.12 0.12 7% 49 1% /ley1393
prosap1:/planos_local 1.12 0.32 72% 5972 8% /planos
prosap1:/sapmnt/PRO_local 25.88 14.59 44% 820081 17% /sapmnt/PRO
prosap1:/usr/sap/trans_local 77.75 17.09 79% 249463 6% /usr/sap/trans
/dev/zdiadian_lv 6.00 5.86 3% 461 1% /ZDIADIAN_local
/dev/data_lv 6.00 6.00 1% 4 1% /DATACREDITO_local
Page 803
COMPARTIR NFS HACMP
prosap1:/DATACREDITO_local 6.00 6.00 1% 4 1% /DATACREDITO
prosap1:/ZDIADIAN_local 6.00 5.86 3% 461 1% /ZDIADIAN
12:50:09 PM: Henry Fabian Espinosa: perfecto
12:50:12 PM: Henry Fabian Espinosa: era eso
12:50:42 PM: Liliana Lizarazo Florez: verifica en prosap3 que tambin hayan quedado montados
12:50:46 PM: Henry Fabian Espinosa: ok
12:50:59 PM: Henry Fabian Espinosa: si tambien
12:51:49 PM: Liliana Lizarazo Florez: perfecto.
12:52:06 PM: Henry Fabian Espinosa: listo y en el /usr/es/sbin/cluster/etc/exports
12:52:11 PM: Henry Fabian Espinosa: deben quedar realcionados
12:52:12 PM: Henry Fabian Espinosa: cierto
12:52:20 PM: Liliana Lizarazo Florez: si.
12:52:23 PM: Henry Fabian Espinosa: ah ok
12:52:23 PM: Henry Fabian Espinosa: si
12:52:29 PM: Henry Fabian Espinosa: muchas gracias
12:52:32 PM: Liliana Lizarazo Florez: dnd.New incoming message: Click to scroll to bottom...
Page 804
COMPARTIR NFS HACMP
10:43:10 AM: Henry Fabian Espinosa: Liliana que pena contigo es que tengo una pregunta sencilla
10:44:12 AM: Henry Fabian Espinosa: en un cluster hacmp cual es el procedimiento para exportar un FS por NFS hacia otros nodois
10:48:41 AM: Liliana Lizarazo Florez: este filesystem debe adicionarse como directorio a exportar en el recurso definido en HACMP. Luego se debe sincronizar el cluster para que actualice la informacin en los nodos del cluster.
10:49:28 AM: Liliana Lizarazo Florez: Pregunta, ese fs. tambin va a se montado en los nodos del cluster?
10:51:58 AM: Henry Fabian Espinosa: y como es el cluster de colombina prefiero preguntarle a alguien que sepa bastante para no embarrarla
Page 805
COMPARTIR NFS HACMP
11:06:25 AM: Liliana Lizarazo Florez: y Change/Show Resources and Attributes for a Resource Group
Service IP Labels/Addresses [prosap1] +
Application Servers [scsappl_prosap1] +
Volume Groups [ci_vg ] +
Use forced varyon of volume groups, if necessary false +
Automatically Import Volume Groups false +
Filesystems (empty is ALL for VGs specified) [ ] +
Filesystems Consistency Check fsck +
Filesystems Recovery Method sequential +
Filesystems mounted before IP configured true +
Filesystems/Directories to Export (NFSv2/3) [/BANCOS_local /CEN_local /MES_local /archivado_local /ley1393_local /planos_local /sapmnt/PRO_local /usr/sap/trans_local] +
+
Filesystems/Directories to Export (NFSv4) [] +
Stable Storage Path (NFSv4) [] +
Filesystems/Directories to NFS Mount [/BANCOS;/BANCOS_local /CEN;/CEN_local /MES;/MES_local /archivado;/archivado_local /ley1393;/ley1393_local /planos;/planos_local /sapmnt/PR>
Network For NFS Mount [] +
Tape Resources [] +
Raw Disk PVIDs [] +
Fast Connect Services [] +
Communication Links [] +
Primary Workload Manager Class [] +
Secondary Workload Manager Class [] +
Page 806
COMPARTIR NFS HACMP
WPAR Name [] +
SVC PPRC Replicated Resources [] +
EMC SRDF(R) Replicated Resources [] +
11:08:19 AM: Liliana Lizarazo Florez: veo que hay un grupo de volumenes exportados, en Filesystems/Directories to Export (NFSv2/3) al final debes adicionar el que vas a exportar
11:09:54 AM: Liliana Lizarazo Florez: y en Filesystems/Directories to NFS Mount tambin adiciona el filesystem como debe quedar montado en el cluster
11:13:43 AM: Henry Fabian Espinosa: COMMAND STATUS
11:22:06 AM: Henry Fabian Espinosa: WARNING: Directory: /ZDIADIAN_local was specified to be exported on node: prosap1.
Page 807
COMPARTIR NFS HACMP
WARNING: Directory: /DATACREDITO_local was specified to be exported on node: prosap1.
WARNING: Directory: /DATACREDITO_local was specified to be exported on node: prosap3.
11:22:21 AM: Henry Fabian Espinosa: WARNING: Directory: /ZDIADIAN_local was specified to be exported on node: prosap3.
WARNING: Directory: /DATACREDITO_local was specified to be exported on node: prosap1.
WARNING: Directory: /DATACREDITO_local was specified to be exported on node: prosap3.
11:22:45 AM: Henry Fabian Espinosa: NFS mount point /DATACREDITO is in VG ci_vg in resource group sapscs_rg.
Page 808
COMPARTIR NFS HACMP
WARNING: Filesystem or directory: /ZDIADIAN_local is configured to be exported in HACMP,
but it does not have a corresponding entry in /usr/es/sbin/cluster/etc/exports file on node: prosap1.
WARNING: Filesystem or directory: /DATACREDITO_local is configured to be exported in HACMP,
but it does not have a corresponding entry in /usr/es/sbin/cluster/etc/exports file on node: prosap1.
WARNING: Filesystem or directory: /ZDIADIAN_local is configured to be exported in HACMP,
but it does not have a corresponding entry in /usr/es/sbin/cluster/etc/exports file on node: prosap3.
WARNING: Filesystem or directory: /DATACREDITO_local is configured to be exported in HACMP,
but it does not have a corresponding entry in /usr/es/sbin/cluster/etc/exports file on node: prosap3.
/ZDIADIAN_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/DATACREDITO_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/archivado_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/BANCOS_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/CEN_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/planos_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/sapmnt/PRO_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/usr/sap/trans_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:devsap:qassap:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51:192.168.105.31:192.168.105.29
/ley1393_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:devsap:qassap:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51:192.168.105.31:192.168.105.29
/MES_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/ZDIADIAN_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/DATACREDITO_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/archivado_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/BANCOS_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/CEN_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
Page 809
COMPARTIR NFS HACMP
/planos_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/sapmnt/PRO_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/usr/sap/trans_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:devsap:qassap:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51:192.168.105.31:192.168.105.29
/ley1393_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:devsap:qassap:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51:192.168.105.31:192.168.105.29
/MES_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
d
Page 810
COMPARTIR NFS HACMP
DATACREDITO_local prosap1 /DATACREDITO nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
11:31:33 AM: Henry Fabian Espinosa: zdiadian_lv jfs2 48 48 1 open/syncd /ZDIADIAN_local
/BANCOS_local prosap1 /BANCOS nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/CEN_local prosap1 /CEN nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/MES_local prosap1 /MES nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
Page 811
COMPARTIR NFS HACMP
/archivado_local prosap1 /archivado nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/ley1393_local prosap1 /ley1393 nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/planos_local prosap1 /planos nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/sapmnt/PRO_local prosap1 /sapmnt/PRO nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/usr/sap/trans_local prosap1 /usr/sap/trans nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/ZDIADIAN_local prosap1 /ZDIADIAN nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
DATACREDITO_local prosap1 /DATACREDITO nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
Page 812
COMPARTIR NFS HACMP
/BANCOS_local prosap1 /BANCOS nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/CEN_local prosap1 /CEN nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/MES_local prosap1 /MES nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/archivado_local prosap1 /archivado nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/ley1393_local prosap1 /ley1393 nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/planos_local prosap1 /planos nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/sapmnt/PRO_local prosap1 /sapmnt/PRO nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/usr/sap/trans_local prosap1 /usr/sap/trans nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/ZDIADIAN_local prosap1 /ZDIADIAN nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/DATACREDITO_local prosap1 /DATACREDITO nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
Page 813
COMPARTIR NFS HACMP
11:41:32 AM: Liliana Lizarazo Florez: en prosap3 hay un filesystem local con /dev/datac_lv -- /DATACREDITO con el mismo nombre del fs que se ext exportando por hacmp
11:47:55 AM: Liliana Lizarazo Florez: regalame nuevamente la salida del comando lsfs de prosap3
Page 814
COMPARTIR NFS HACMP
/BANCOS_local prosap1 /BANCOS nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/CEN_local prosap1 /CEN nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/MES_local prosap1 /MES nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/archivado_local prosap1 /archivado nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/ley1393_local prosap1 /ley1393 nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/planos_local prosap1 /planos nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/sapmnt/PRO_local prosap1 /sapmnt/PRO nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/usr/sap/trans_local prosap1 /usr/sap/trans nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/ZDIADIAN_local prosap1 /ZDIADIAN nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/DATACREDITO_local prosap1 /DATACREDITO nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
Page 815
COMPARTIR NFS HACMP
11:57:34 AM: Liliana Lizarazo Florez: pero cuando se cre /DATACREDITO se le di el path /DATCREDITO_local o se cambio despus?
12:02:33 PM: Liliana Lizarazo Florez: en prosap1 aparece /dev/datac_lv -- /DATACREDITO_local jfs2 12582912 rw no no y en prosap3 apareca como /dev/datac_lv -- /DATACREDITO jfs2 -- rw no no
12:03:53 PM: Liliana Lizarazo Florez: y vamos a verificar en HACMP como ve este filesystem
12:05:43 PM: Henry Fabian Espinosa: #File System Volume Group Resource Group Node List
Page 816
COMPARTIR NFS HACMP
12:06:50 PM: Henry Fabian Espinosa: #File System Volume Group Resource Group Node List
Page 817
COMPARTIR NFS HACMP
12:07:06 PM: Henry Fabian Espinosa: /itmoracle ora_vg oracle_rg prosap1,prosap3
12:11:58 PM: Liliana Lizarazo Florez: si corres el lsfs en prosap3 te aparece /DATACREDITO_local
/DATACREDITO_local prosap1 /DATACREDITO nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
12:13:57 PM: Liliana Lizarazo Florez: debera ver el filseystem como local tal como est en prosap1
Page 818
COMPARTIR NFS HACMP
12:16:21 PM: Liliana Lizarazo Florez: no. slo copia lo que tiene que ver con estos dos filsystems
/BANCOS_local prosap1 /BANCOS nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/CEN_local prosap1 /CEN nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/MES_local prosap1 /MES nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/archivado_local prosap1 /archivado nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/ley1393_local prosap1 /ley1393 nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/planos_local prosap1 /planos nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/sapmnt/PRO_local prosap1 /sapmnt/PRO nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/usr/sap/trans_local prosap1 /usr/sap/trans nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/ZDIADIAN_local prosap1 /ZDIADIAN nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
/DATACREDITO_local prosap1 /DATACREDITO nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
Page 819
COMPARTIR NFS HACMP
Page 820
COMPARTIR NFS HACMP
WARNING: Running cluster verification in modified mode verifies only those HA components that have changed.
If you have made system level changes to your cluster nodes, please re-execute verification in normal mode.
Page 821
COMPARTIR NFS HACMP
WARNING: Directory: /DATACREDITO_local was specified to be exported on node: prosap1.
WARNING: Directory: /DATACREDITO_local was specified to be exported on node: prosap3.
WARNING: Directory: /DATACREDITO_local was specified to be exported on node: prosap1.
WARNING: Directory: /DATACREDITO_local was specified to be exported on node: prosap3.
Page 822
COMPARTIR NFS HACMP
The following application(s), shown with their associated resource group,do not have an application monitor configured:
WARNING: Filesystem or directory: /ZDIADIAN_local is configured to be exported in HACMP,
but it does not have a corresponding entry in /usr/es/sbin/cluster/etc/exports file on node: prosap1.
WARNING: Filesystem or directory: /DATACREDITO_local is configured to be exported in HACMP,
but it does not have a corresponding entry in /usr/es/sbin/cluster/etc/exports file on node: prosap1.
WARNING: Filesystem or directory: /ZDIADIAN_local is configured to be exported in HACMP,
but it does not have a corresponding entry in /usr/es/sbin/cluster/etc/exports file on node: prosap3.
WARNING: Filesystem or directory: /DATACREDITO_local is configured to be exported in HACMP,
but it does not have a corresponding entry in /usr/es/sbin/cluster/etc/exports file on node: prosap3.
12:30:52 PM: Liliana Lizarazo Florez: es como si en los nodos la informacin del filesystem estuviera inconsistente. Trata de remover el filesystem y vuelvelo a crear
12:34:21 PM: Liliana Lizarazo Florez: en este caso son normales, porque el nombre del filesystem lo est viendo diferente, para HACMP el nombre es /DATACREDITO y no /DATACREDITO_local
Page 823
COMPARTIR NFS HACMP
12:34:47 PM: Henry Fabian Espinosa: mira le d prosap1-PLT/usr/es/sbin/cluster/cspoc >sudo ./cli_rmfs /DATACREDITO_local
12:35:55 PM: Henry Fabian Espinosa: pero antes lo quito manualmente del /etc/filesystem en ambos nodos cierto
12:36:24 PM: Henry Fabian Espinosa: prosap1-PLT/usr/es/sbin/cluster/cspoc >lsfs |grep /DATA
/DATACREDITO_local prosap1 /DATACREDITO nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
12:39:26 PM: Liliana Lizarazo Florez: entonces, no est haciendo de manera correcta la operacin.
12:40:49 PM: Liliana Lizarazo Florez: si, la operacin debe ejecutarse en ambos nodos, para que el cluster est consistente.
12:41:27 PM: Henry Fabian Espinosa: prosap1-PLT/usr/es/sbin/cluster/cspoc >sudo ./cli_rmlv datac_lv
12:46:30 PM: Henry Fabian Espinosa: y en ambos nodos los relaciono en el /etc/filesystems
/DATACREDITO_local prosap1 /DATACREDITO nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
12:47:30 PM: Henry Fabian Espinosa: prosap3-PLT/home/ibmadmhe >lsfs |grep /DATACREDITO_local
/DATACREDITO_local prosap1 /DATACREDITO nfs -- bg,hard,intr,vers=3,sec=sys,rw no no
Page 824
COMPARTIR NFS HACMP
Page 825
COMPARTIR NFS HACMP
12:50:42 PM: Liliana Lizarazo Florez: verifica en prosap3 que tambin hayan quedado montados
12:52:32 PM: Liliana Lizarazo Florez: dnd.New incoming message: Click to scroll to bottom...
Page 826
COMPARTIR NFS HACMP
10:48:41 AM: Liliana Lizarazo Florez: este filesystem debe adicionarse como directorio a exportar en el recurso definido en HACMP. Luego se debe sincronizar el cluster para que actualice la informacin en los nodos del cluster.
Page 827
COMPARTIR NFS HACMP
Filesystems/Directories to Export (NFSv2/3) [/BANCOS_local /CEN_local /MES_local /archivado_local /ley1393_local /planos_local /sapmnt/PRO_local /usr/sap/trans_local] +
Filesystems/Directories to NFS Mount [/BANCOS;/BANCOS_local /CEN;/CEN_local /MES;/MES_local /archivado;/archivado_local /ley1393;/ley1393_local /planos;/planos_local /sapmnt/PR>
Page 828
COMPARTIR NFS HACMP
Page 829
COMPARTIR NFS HACMP
Page 830
COMPARTIR NFS HACMP
/ZDIADIAN_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/DATACREDITO_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/archivado_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/BANCOS_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/CEN_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/planos_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/sapmnt/PRO_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/usr/sap/trans_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:devsap:qassap:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51:192.168.105.31:192.168.105.29
/ley1393_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:devsap:qassap:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51:192.168.105.31:192.168.105.29
/MES_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/ZDIADIAN_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/DATACREDITO_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/archivado_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/BANCOS_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/CEN_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
Page 831
COMPARTIR NFS HACMP
/planos_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/sapmnt/PRO_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
/usr/sap/trans_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:devsap:qassap:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51:192.168.105.31:192.168.105.29
/ley1393_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:devsap:qassap:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51:192.168.105.31:192.168.105.29
/MES_local -vers=3,sec=sys,anon=-1,rw,root=prosap1:prosap2:prosap3:prosap4:prosap1_pers:prosap3_pers:192.168.105.52:192.168.105.53:192.168.105.3:192.168.105.50:192.168.105.2:192.168.105.51
Page 832
COMPARTIR NFS HACMP
Page 833
COMPARTIR NFS HACMP
Page 834
COMPARTIR NFS HACMP
Page 835
COMPARTIR NFS HACMP
Page 836
COMPARTIR NFS HACMP
Page 837
COMPARTIR NFS HACMP
12:02:33 PM: Liliana Lizarazo Florez: en prosap1 aparece /dev/datac_lv -- /DATACREDITO_local jfs2 12582912 rw no no y en prosap3 apareca como /dev/datac_lv -- /DATACREDITO jfs2 -- rw no no
Page 838
COMPARTIR NFS HACMP
Page 839
COMPARTIR NFS HACMP
Page 840
COMPARTIR NFS HACMP
Page 841
COMPARTIR NFS HACMP
Page 842
COMPARTIR NFS HACMP
Page 843
COMPARTIR NFS HACMP
Page 844
COMPARTIR NFS HACMP
12:34:21 PM: Liliana Lizarazo Florez: en este caso son normales, porque el nombre del filesystem lo est viendo diferente, para HACMP el nombre es /DATACREDITO y no /DATACREDITO_local
Page 845
MONTAR FS ENCRIPTADO
http://wiki.sabayon.org/index.php?title=HOWTO:_Mount_Encrypted_Partition MONTAR FS ENCRIPTADO
http://pissedoffadmins.com/os/mount-unknown-filesystem-type-
lvm2_member.html aCTIVAR VG
Page 846
MONTAR FS ENCRIPTADO
MONTAR FS ENCRIPTADO
aCTIVAR VG
Page 847
montar cifs aix
/DS_D_ERP_P 10.16.20.13/DEVUSER/zxsa1254 /DS_D_ERP_P cifs -- uid=204,gid=218,fmode=775,rw yes no
rmcifsmnt -f
Page 848
montar cifs aix
/DS_D_ERP_P 10.16.20.13/DEVUSER/zxsa1254 /DS_D_ERP_P cifs -- uid=204,gid=218,fmode=775,rw yes no Desarrollo
Page 849
ONLY AIX
DESCRIPCION
Listar servidores administados por la HMC (filtrado):
odmget -q name=hdisk1 CuAt |grep value
3. Listar todos los perfiles almacenados en un servidor (filtrado):
Listar todo el perfil de una particin (filtrado):
1. Validacin de recursos del sistema en uso y disponibles:
VIOS
Cmo restaurar archivos o filesystems desde una imgen de mksysb?
4. sudo ./mmmount all
Mejores practicas para un sistema en produccion aix
Page 850
ONLY AIX
Asignar disco externo de un VIO a una lpar:
Page 851
ONLY AIX
ver atributos de usuario
Cambiar atributo de usuario
oslevel -s
Saber las wwn de un aix
Ver demonios en aix
detener un demonio
asegurar que no se vuelva a activar con el reinicio
ODM
ODM maneja lo siguiente
Page 852
ONLY AIX
Que compone una HBA
lsattr -El fscx
Se nota que esta maquina es una lpar ya que tiene un vios server asociado.
Muestra los Hilos de procesamiento
ver procesadores en este caso hay 2 nmon y sar muestran 4 pero cada uno tiene 2 hilos
Eliminar banderas de cambio de contrasea al inicio d sesion
Pagina de medios paquetes aix
Crecer un filesystem en AIX
El filesystem es /usr/sap
# cllsvg
Page 853
ONLY AIX
Vemos que pertenece al vg sapnpdqvg entonces validamos cuanto espacio tiene libre (29 GB)
Si necesitamos solo 10G para aumentarle al filesystem digitamos lo siguiente
Si se lo queremos quitar
Cuando se necesite solicitar almacenamiento revisar:
1. Las hbas esten virtualizadas
2. Si estan virtualizadas se tiene ue validar todo en el VIOSERVER
3.Se valida el serial la lpar
4. Se valida el serial en el VIOSERVER
5. si concuerdan se tiene que realizar la busqueda y validar que tiene cada vhost
6. Cabe recalcar que los discos que aparecen el VIO no deben ser precisamente los de la lpar
por ejemplo el serial corresponde al partition number 5 en la lpar se valida con lparstat -i
Este tiene 2 vhost pero solo uno esta llevando discos a la lpar
Lo sabemos as.
Vamos a la lpar y ejecutamos lo siguiente: lspath y tomamos un disco de esos, el hdisk6
lscfg -vpl hdisk6
hdisk6 U9133.55A.061C4EH-V5-C3-T1-L8300000000000000 Virtual SCSI Disk Drive identificador de LUN 83
Con lo anterior podemos estar seguros de que el espacio que asignen lo pueden dar por la hba por la que va el disco anterior
--------------- -------------------------------------------- ------------------
vhost0 U9133.55A.061C4EH-V1-C11 0x00000005
VTD PD12disk112
Status Available
LUN 0x8600000000000000
Page 854
ONLY AIX
Backing device hdisk112
Physloc U787B.001.DNWFGF2-P1-C3-T1-W205600A0B847D566-LC000000000000
VTD PD12disk120
Status Available
LUN 0x8300000000000000
Backing device hdisk120
Physloc U787B.001.DNWFGF2-P1-C3-T1-W205600A0B847D566-L12000000000000
VTD PD12disk121
Status Available
LUN 0x8400000000000000
Backing device hdisk121
Physloc U787B.001.DNWFGF2-P1-C3-T1-W205600A0B847D566-L13000000000000
VTD PD12disk122
Status Available
LUN 0x8500000000000000
Backing device hdisk122
Physloc U787B.001.DNWFGF2-P1-C3-T1-W205600A0B847D566-L14000000000000
VTD vroot_pd012
Status Available
LUN 0x8100000000000000
Backing device root_pd012
Physloc
Ver paquetes instalados en aix 5.3
Desinstalar paquetes
Saber a que arquitectura esta un servidor AIX
Lists name, availability status, location code, and a brief
description
Lists current or default attribute values of a device. For example
Performs rudimentary consistency checking on an attached tape
device by reading a tape volume
Defines, or defines and configures, a new device in the system,
or configures a device that was previously defined
Unconfigures a device. The command makes a device
unavailable but still defined, or it removes the definition from the
object data manager (ODM).
Changes the attributes of a defined or available device. For
example, the following command sets the block size to 1024
EJECUTAR UN COMANDO ROOT DESDE UN USUARIO MORTAL
Por ejemplo estoy con el usuario ibmadmcv
ASTSM:/home/ibmadmcm >id
Page 855
ONLY AIX
uid=209(ibmadmcm) gid=15(ibmadmin)
Requiero ver los discos que estan en el sistema pero smitty no permite ejecutarlo como sudo smitty disk tapes
la solucin es enviarle por medio de su el comando en este caso smitty tape
Crecer un filesystem en AIX cuando presentan el servidor es virtual y tiene virtual scsi
1. Se debe validar que la lpar cuantos vioserver tiene
2. Por lo general deben tener dos VIOSERVER por el tema de la redundancia
3. En este ejemplo se tiene solo un VIOSERVER para la lpar
4. Ingresamos primero al VIO cuando las personas de storage nos den disco
5. Se reconoce el disco desde el VIOSERVER as
6. Se debe validar antes de todo un lspv y comparamos despues del cfgmgr otro lspv
7. validamos el disco ingresado hdisk58
8. Validamos de cuanto es el disco
9. vemos si el disco esta reservado
10. Retiramos la reserva
11.revisamos en el VIO los disco que tiene el Vhost0
12. Mapeamos el disco el ultimo valor el id que tendra o nombre
DESDE LA LPAR
13. vamos a la lpar y ejecutamos el cfgmgr
14. revidsamos que se halla ingresado el disco
15. Agregamos el disco al vg
16. revisamos el lv
17. error que suele ocurrir es
18. Para solucionar esto incrementamos a 2048 l item MAX LPs: 512
19. Se incrementa el filsystem
listo
BAJAR UNA MAQUINA CUANDO SE MODIFICA EL PERFIL
Crear el filesystem para el agente de TSM
Ver en que HMC se encuentra una lpar
Manual interesante de SUDO http://www.linux-magazine.es/issue/70/074-077_LineadeComandosLM70.pdf
Ver con que disco esta el bootlist
Se revisa que no tenga entradas de red a menos que bootee por red debe mostrar unicamente los caminos a un disco
3:23:48 PM: Carlos Andres Munoz Loaiza: nim -o cust -a lpp_source=618lpp_res -a fixes="update_all" -a installp_flags=acNgX -a show_progress=yes -a accept_licenses=yes ncscm013
Se revisa nuevamente
Ver los path por que fibra
Proxy de ibm
Forzar inicio de sesion cambio de clave
Page 856
ONLY AIX
Borrar el errpt
Errpt -aj codigo
VER CONSUMO DE MEMORIA
VER CUANTOS PROCESADORES TIENE EL SERVER
Asignar paginacion en un aix
Se asigna mas espacio en otro disoc
Se crea un lv de 25G o 798 pps
Se activ ala swap
Se deja automatico
Se reduce el lv a 512 MB
Ver como estan distribuidos los lv de swap
Muestra posicion del devide
Saber si una impresora est bien configurada,
QUITAR LA BANDERA DE solicitud de cambio forzado de contrasea al inicio de sesion
Instalacion de SSH en aix
Instalar estos paquetes uno es la dependencia de la otro
BUSCAR DOS VALORES en una sola linea
Crear grupo en aix
Power Care IBM
Comentario reunion
Explicacion de grafica de paginacion de memoria
Page 857
ONLY AIX
Crecer un filesystem en AIX en Cluster
Se va a la sigiuiente ruta para saber el resource group
Despues vamos a
Se valida el vg si hay espacio y se ejecuta el siguiente comando estando en /usr/sbin/cluster/sbin
Crecer los max LPS de un logical volumen en hacmp
ERRORES HACMP
Montar un DVD en aix
Desintalar un paquete en aix por comandos
Instalar un paquete
-d es el directorio
DESMONTAR FORZADAMENTE UN FS
Instalar un paquete que se encuentra en un carpeta por ejemplo Compilador de C
Cambiar la velocidad de una fibra de tapes y dejarla persistente
Crear un ISO apartir de un FS
Cuando una consola est ocupada en la HMC
Rutas estaticas persistentes
Saber si es de 64 bits o 32 bits
DESINSTALAR DRIVER DE MULTIPATH
Les comparto el script para desinstalar el driver del multipath, cuando se tiene el disco de boot en la SAN.
CUANDO UN vio NO PUEDA REALIZAR DLPAR desde el VIOSERVER
EJECUTAR EN EL VIO
Con mput puedo mandar informacion por ftp o sftp
Copiar archivos bloque a bloque con archivos ocultos
Copiar con rsync remotamente
Velocidad de un fibra
Page 858
ONLY AIX
Depuracion del /var
Validar si existen muchos archivos mail comprimidos el la ruta /var/spool/mail y borrarlos en caso de ser necesario.
Page 859
ONLY AIX
COMANDOS
lssyscfg -r sys -F name,type_model,serial_num,state
Lssyscfg -r lpar -m "NOMBRE_SERVIDOR" -F name,lpar_id,state,os_version,curr_profile
lssyscfg -r prof -m "NOMBRE_SERVIDOR" -F name,lpar_name,lpar_id,lpar_env
lssyscfg -r prof -m "NOMBRE_SERVIDOR" --filter "lpar_names=\"NOMBRE_LPAR\""
lshwres -r proc -m "NOMBRE_LPAR" --level sys
Hmc
Particiones o servidores
Virtual input /output server
Restauracin de filesystems:
Rebobinar cinta: mt -f /dev/rmtX -rewind
Adelandar 3 posiciones en la cinta: tctl fsf 3
Restaurar el directorio/filesystem:
restore -xdvf <mksysb image> ./filesystem
restore -xdvf /dev/rmtX.1 ./filesystem
Restauracin de archivos:
Rebobinar cinta: mt -f /dev/rmtX -rewind
Adelandar 3 posiciones en la cinta: tctl fsf 3
Restaurar el archivo:
restore -xvf <mksysb image> ./ruta/archivo
restore -xvf /dev/rmtX.1 ./ruta/archivo
mkvdev -vdev migncpor2_lv -vadapter vhost17 -dev migncerpno2
2. Redundancia de red (sea o Etherchannel) procurar a nivel de switch
3. En almacenamiento interno se debe configurar el rootvg como mirror LV recomndable
4. En todo sistema productivo, sea virtualizado o no,se debe disponer al menos de 2 interfaces
(puertos) HBA n lo posible en tarjetas diferentes para brindar redundancia de caminos entre la
lpar y el storage, y en la medida de los posible en switchs SAN diferentes y al menos 1 interfaz
(puerto) de HBA con conexin a la librera para los respaldos correspondientes del sistema. No se
recomienda mezclar la SAN de backups con la de storage a travs de una misma interfaz (puerto)
HBA.
5. Todo servidor debe estar conectado a una consola de gestin (HMC) y tanto la HMC como las
lpars y los VIO Servers, deben tener comnunicacin a travs de una red LAN y en lo posible co
conexin a travs de SOCKS con el fin de asegurar el correcto funcionamiendo de la gestin
dinmica de los sistemas y la comunicacin de los administradores al sistema.
Page 860
ONLY AIX
Debido a un incidente presentado, se debe validar en caso de que diferentes lpars compartan la
misma VLAN de red, que al asignar VLANs (PVIDs SEAs) comunes en varias lpars en el mismo
servidor, no se generen LOOPS en los swiches de LAN, sto debido a un incidente presentado en la
configuracin de un cliente particular que la nica diferencia con respecto a los dems clientes en
que se ha realizado sta configuracin, es que hace uso de la VLAN 1 en switch CISCO, donde no
se recomienda el uso de dicha VLAN en los sistemas de redes.
6. Para validar y balancear: Para los sistemas productivos crticos se recomienda la configuracin
de los procesadores en modo capped, sto con el fin de que ningn otro sistema con
configuracin uncapped haga uso de los recursos de procesador del sistema productivo.
Ejecutar cfgmgr como root, o cfgdev como padmin
2. Ejecutar comando de scan de discos para validacin de la asignacin:
Para MPIO: fget_config -Av | grep "nombre disco en el storage"
Para SDD: datapath query device | grep "serial del disco del storage"
3. Una vez indentificado el disco o los diferentes caminos, eliminar la reserva para todos los
caminos de dicho disco:
Para MPIO:

Para SDD:
chdev -l vpathX -a reserve_policy=no_reserve
4. Validar el vhost correspondiente a la particin:
con usuario padmin: lsmap -all
con usuario root: /usr/ios/cli/ioscli lsmap -all
5. Una vez indentificado el vhost, mapear el disco a la lpar:
Para MPIO:
con usuario padmin: mkvdev -vdev hdiskX -vadapter vhostY -dev nombre_vtd_a_dar
con usuario root: /usr/ios/cli/ioscli mkvdev -vdev hdiskX -vadapter vhostY -dev
nombre_vtd_a_dar
Para SDD:
con usuario padmin: mkvdev -vdev vpathX -vadapter vhostY -dev nombre_vtd_a_dar
con usuario root: /usr/ios/cli/ioscli mkvdev -vdev vpatdhX -vadapter vhostY -dev
nombre_vtd_a_dar
6. Validar que el disco est correctamente mapeado:
Para MPIO:
con usuario padmin: lsmap -vadapter vhostX | awk '/nombre_vtd_a_dar/,/hdiskX/ {print}'
con usuario root: /usr/ios/cli/ioscli lsmap -vadapter vhostX | awk '/nombre_vtd_a_dar/,/hdiskX/
{print}'
Para SDD:
con usuario padmin: lsmap -vadapter vhostX | awk '/nombre_vtd_a_dar/,/vpathX/ {print}'
con usuario root: /usr/ios/cli/ioscli lsmap -vadapter vhostX | awk '/nombre_vtd_a_dar/,/vpathX/
{print}'
Page 861
ONLY AIX
7. Ingresar a la lpar correspondiente y ejecutar cfgmgr como root.
8. Validar que el disco sea detectado con lspv
9. Validar que el nuevo disco en la lpar corresponda al LUN en el VIO:
Para MPIO:
con usuario padmin: lsmap -vadapter vhostX | awk '/nombre_vtd_a_dar/,/hdiskX/ {print}'
con usuario root: /usr/ios/cli/ioscli lsmap -vadapter vhostX | awk '/nombre_vtd_a_dar/,/hdiskX/
{print}'
Para SDD:
con usuario padmin: lsmap -vadapter vhostX | awk '/nombre_vtd_a_dar/,/vpathX/ {print}'
con usuario root: /usr/ios/cli/ioscli lsmap -vadapter vhostX | awk '/nombre_vtd_a_dar/,/vpathX/
{print}
En la lpar en que fue asignado el disco, validar que el siguiente comando tenga el mismo nmero
que la LUN del comando anterior en el VIO:
Para MPIO:
lscfg -vl hdiskZ
Para SDD:
lscfg -vl vpathZ
10. Validar que el tamao del disco en el VIO y en la lpar coincidan (opcional):
en el VIO:
bootinfo -s hdiskX
en la lpar:
bootinfo -s hdiskZ
luser -f usuario
chuser atributo usuario
6100-01-09-1015
Version 6.1 TL 01 service pack 09-1015
lsdev -c adapter sale fcs0 y fcs1
lscfg -vpl fcs0 |grep Net
lscfg -vpl fcs1 |grep Net
lssrc -a
sudo stopsrc -s sendmail
Comentar la linea correspondiente de sendmail en /etc/rc.tcpip:
# "/usr/lib/sendmail -bi" or "/usr/ucb/newaliases"
Data Object Manager (ODM) es un sistema de gestin de base de datos y configuracin de
dispositivos integrados en el sistema operativo AIX de IBM. El ODM es nica para AIX en
comparacin con otros sistemas operativos UNIX. Los datos gestionados por ODM se almacenan y
mantienen como objetos con atributos asociados. Interaccin de las aplicaciones de lenguaje de
programacin C con el ODM se realiza a travs de la interfaz de programacin de aplicaciones
(API) de la biblioteca; scripts de shell y los usuarios disponen de utilidades de lnea de comandos
como nos odmshow, odmadd, odmchange odmdelete y tratar con l.
configuracin de la red
Volumen lgico de gestin de configuracin
Software instalado de informacin
Page 862
ONLY AIX
Los dispositivos que tiene drivers para AIX
Los dispositivos lgicos o controladores de software
Dispositivo de hardware fsico instalado
Los mens, pantallas y los comandos que utiliza SMIT
fscx Esta siempre esta en defined
fscsix avaible
fcnetx avaible
ver atributos de la fibra
lparstat -i
smtctl
SMT is currently enabled.
SMT boot mode is not set.
SMT threads are bound to the same physical processor.
proc0 has 2 SMT threads.
Bind processor 0 is bound with proc0
Bind processor 1 is bound with proc0
proc2 has 2 SMT threads.
Bind processor 2 is bound with proc2
Bind processor 3 is bound with proc2
pwdadm -c usuario
oss4aix.org
df -k |grep /usr/sap
/dev/usrsap_lv 5242880 3445236 35% 4825 1% /usr/sap
/dev/usrsap_lv 5.00 3.29 35% 4825 1% /usr/sap
ncnpd012/usr/sbin#sudo lslv usrsap_lv
Password:
LOGICAL VOLUME: usrsap_lv VOLUME GROUP: sapnpdqvg
LV IDENTIFIER: 00018c450000d6000000012aaf9b3b6c.3 PERMISSION: read/write
VG STATE: active/complete LV STATE: opened/syncd
TYPE: jfs2 WRITE VERIFY: off
MAX LPs: 512 PP SIZE: 32 megabyte(s)
COPIES: 1 SCHED POLICY: parallel
LPs: 160 PPs: 160
STALE PPs: 0 BB POLICY: relocatable
INTER-POLICY: minimum RELOCATABLE: yes
INTRA-POLICY: middle UPPER BOUND: 1024
MOUNT POINT: /usr/sap LABEL: None
MIRROR WRITE CONSISTENCY: on/ACTIVE
EACH LP COPY ON A SEPARATE PV ?: yes
Serialize IO ?: NO
DEVICESUBTYPE : DS_LVZ
COPY 1 MIRROR POOL: None
COPY 2 MIRROR POOL: None
Page 863
ONLY AIX
COPY 3 MIRROR POOL: None
ncnpd012/usr/sbin#lsvg sapnpdqvg
VOLUME GROUP: sapnpdqvg VG IDENTIFIER: 00018c450000d6000000012aaf9b3b6c
VG STATE: active PP SIZE: 32 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 3796 (121472 megabytes)
MAX LVs: 256 FREE PPs: 910 (29120 megabytes)
LVs: 12 USED PPs: 2886 (92352 megabytes)
OPEN LVs: 12 QUORUM: 3 (Enabled)
TOTAL PVs: 4 VG DESCRIPTORS: 4
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 4 AUTO ON: yes
MAX PPs per VG: 32768 MAX PVs: 1024
LTG size (Dynamic): 256 kilobyte(s) AUTO SYNC: no
HOT SPARE: no BB POLICY: relocatable
PV RESTRICTION: none
sudo chfs -a size=+10G /usr/sap
sudo chfs -a size=-10G /usr/sap
lparstat -i serial machine
lsmap -all
lsmap -all |grep vhost0 en caso de que sea el vhost0
ibmadmcm@viosnudes2$ lsmap -vadapter vhost13
SVSA Physloc Client Partition ID
--------------- -------------------------------------------- ------------------
vhost13 U9133.55A.061C4EH-V1-C20 0x00000005
VTD vmroot_pd012
Status Available
LUN 0x8100000000000000
Backing device mroot_pd012
Physloc
ibmadmcm@viosnudes2$ lsmap -vadapter vhost0
SVSA Physloc Client Partition ID
--------------- -------------------------------------------- ------------------
vhost0 U9133.55A.061C4EH-V1-C11 0x00000005
VTD PD12disk112
Status Available
LUN 0x8600000000000000
Page 864
ONLY AIX
Backing device hdisk112
Physloc U787B.001.DNWFGF2-P1-C3-T1-W205600A0B847D566-LC000000000000
VTD PD12disk120
Status Available
LUN 0x8300000000000000
Backing device hdisk120
Physloc U787B.001.DNWFGF2-P1-C3-T1-W205600A0B847D566-L12000000000000
VTD PD12disk121
Status Available
LUN 0x8400000000000000
Backing device hdisk121
Physloc U787B.001.DNWFGF2-P1-C3-T1-W205600A0B847D566-L13000000000000
VTD PD12disk122
Status Available
LUN 0x8500000000000000
Backing device hdisk122
Physloc U787B.001.DNWFGF2-P1-C3-T1-W205600A0B847D566-L14000000000000
VTD vroot_pd012
Status Available
LUN 0x8100000000000000
Backing device root_pd012
Physloc
lslpp -l
installp -u <paquete>
bootinfo -K
lsdev -Cl rmt0
lsattr -E -l rmt0
tapechk
mkdev
rmdev
chdev
sudo su - -c "smitty tape"
Page 865
ONLY AIX
Requiero ver los discos que estan en el sistema pero smitty no permite ejecutarlo como sudo smitty disk tapes
sudo su - -c "smitty tape"
cfgmgr
lspv
bootinfo -s hdisk58
lsattr -E -l hdisk58
chdev -l hdisk98 -a reserve_policy=no_reserve
lsmap -vadapter vhost0
mkvdev -vdev hdisk58 -vadapter vhost0 -dev PD12disk58
cfgmgr
lspv
extendvg sapnpdqvg hdisk4
lslv usrsap_lv
0516-787 extendlv: Maximum allocation for logical volume usrsap_lv
is 512.
sudo chlv -x 2048 usrsap_lv
sudo chfs -a size=+50G /usr/sap
sudo su - -c shutdown -F now
sudo mklv -y itm_lv -t jfs2 rootvg 1G; sudo crfs -v jfs2 -d itm_lv -m /opt/IBM/ITM -A yes -p rw; sudo mount /opt/IBM/ITM
Lsrsrc IBMMANAGENTServer
lslv -m hd5
muestra: hdisk3 blv=hd5
bootlist m normal hdisk?
Bosboot ad /dev/hdisk0
bootlist m normal o
Sudo pcmpath query device|more
proxy1.argentina.ibm.com 8080
pwdadm -f ADMCHG username
Page 866
ONLY AIX
borrar errpt > errpclear 2 de los dos ultimos dias
Ver el errpt
NMON M ///////lsconf |grep Mem
NMON P /////// lsconf
La swap en vgroot debe estar en 512 MB
mkvg -y swapvg hdisk13 >> crear el VG
mklv -t paging -y paging00 swapvg 798 >> crear el lv de paging
swapon /dev/paging00 >> activar la swap
chps -a y paging00 >> dejar automatico la nueva swap
chps -d 392 hd6 >> reducir la swap 392 pps
swapon -a activa todo
lsps -a
scfg
Npiv
lsque -qZDR5711006I; grep ZDR5711006I /administrador/shells/subircola.sh;lpstat -pZDR5711006I;ping printzdr526i
sudo chsec -f /etc/security/passwd -s ibmitsoh -a flags=
Estan en nogsi
egrep "10.15.0.19|10.15.0.18" /etc/hosts
awk '/ipnumero1/ {print $0} /segundaip/{print $0}' /etc/hosts
mkgroup id='655' ibmdesa
Un disco duro local puede aceptar 16 operaciones al mismo tiempo
Los parametros de fibra trunk y queque_depth no estan al detalle como recomendacion hay que realizar pruebas para el mejor funcionamiento
El disk wait muestra los discos que se estan encolando
Cuando se definan las opciones capped y uncapped en los procesadors hay que tener en cuenta la prioridad
Se debe activar y dejar uncapped los procesadores de los VIOSERVER
"invscout" comando que ve las necesidades de la lpar en cuanto a microcodigo o firware
En cuanto a la red si hay varias maquinas lpar que estan en la misma SEA estas no muestran transacciones al swicth
FS CACHE
Aplicaciones
Page 867
ONLY AIX
Sistema
/usr/sbin/cluster/utilities # ./clRGinfo
/usr/sbin/cluster/sbin
sudo cl_chfs -cspoc " -g sapdb_rg01" -a size=+10G /oracle/XP1/sapdata5
/usr/es/sbin/cluster/sbin/cl_chlv -x'8000' saptemp1
clutils.log
mount -V cdrfs -o ro /dev/cd0 /cdrom
nstallp -ugw vac.* vacpp.* xlmass.* memdbg.*
installp -acXYg -d . vac.C
fuser -kucx /cdrom
installp -aXYgd /cdrom/usr/sys/inst.images -e /tmp/install.log all
1. rmdev -Rl fcs6
2. Chdev -l fcs6 -a max_xfer_size=0x40000 -a num_cmd_elems=1024 -P
3 .cfgmgr
Mkisofs
Rmvterm -p (nombre_lpar) -m (nombre de la caja)
sudo chdev -l inet0 -a route="net,-hopcount,0,-netmask,255.255.255.0,,,,,-
static,129.39.183,10.230.4.129"
bootinfo -y
C:\$user\INFORMACION\INFORMACION\GESTION DIARIA\desinstalar driver de multipath
/usr/sbin/rsct/install/bin/recfgct
stopsrc -s ctrmc; startsrc -s ctrmc
Mput
sudo sh -c "rsync -av /home/henry/ /home/tsminst1"
sudo nohup rsync -avz --exclude=/proc --exclude=/sys --exclude=/Backup --exclude=/DVD /* ibmadmla@10.24.3.22:/BACKUP_NOERP01P/NOERP01P &
Fcstat fibra (fcs0)
Page 868
ONLY AIX
/usr/bin/du -sm /var/spool/mail/* | /usr/bin/sort -rn | /usr/bin/head | /usr/bin/awk '!/.gz$/ {if ($1 > 200) {system ("/usr/bin/gzip -c "$2" > "$2"_`/usr/bin/date \"+%d%m%y_%T\"`.gz;>"$2)}}'
Validar si existen muchos archivos mail comprimidos el la ruta /var/spool/mail y borrarlos en caso de ser necesario.
Page 869
ONLY AIX
Lpar1 Particiones logicas
Lpar2 Particiones logicas
Lpar3 Particiones logicas
Page 870
ONLY AIX
chdev -l hdiskX -a reserve_policy=no_reserve
Page 871
ONLY AIX
starsrc -s nfsd
sudo startsrc -s sendmail -a "-bd -q30m" Cuando no quiera subir
Page 872
ONLY AIX
Page 873
ONLY AIX
Page 874
ONLY AIX
Page 875
ONLY AIX
sudo chfs -a size=+10G /iobobj
sudo mklv -y itm_lv -t jfs2 rootvg 1G; sudo crfs -v jfs2 -d itm_lv -m /opt/IBM/ITM -A yes -p rw; sudo mount /opt/IBM/ITM Ponerle
Page 876
ONLY AIX
mkvg -S -v 2048 -y work_vg hdisk14
mklv -t paging -y paging01 swapvg 798 hdisk14 Se deja un PP libre pa el log
lsque -qZDR5711006I; grep ZDR5711006I /administrador/shells/subircola.sh;lpstat -pZDR5711006I;ping printzdr526i
Los parametros de fibra trunk y queque_depth no estan al detalle como recomendacion hay que realizar pruebas para el mejor funcionamiento
Cuando se definan las opciones capped y uncapped en los procesadors hay que tener en cuenta la prioridad
En cuanto a la red si hay varias maquinas lpar que estan en la misma SEA estas no muestran transacciones al swicth
Son archivos abiertos que estan en memoria
Los umbrales no deben exeder cada umbral
Cuando el umbral de app sobrepasa el umbral a FS cache puede haber un problema y los archivos pasarian a escribir directamente al disco presentando fallas en el performance
Page 877
ONLY AIX
Entrar a la ruta /usr/es/sbin/cluster/cspoc
for i in /db2/P21/sapdata1 /db2/P21/sapdata2 /db2/P21/sapdata3 /db2/P21/sapdata4^Jdo^J./cli_chfs -a size=+2G $i^Jd
Suponiendo que la fibra sea la 6 asi se pone en defined
Se asignan los valores
3. Se reconfigura nuevmamente
Socks colombina
sudo nohup rsync -avz --exclude=/proc --exclude=/sys --exclude=/Backup --exclude=/DVD /* ibmadmla@10.24.3.22:/BACKUP_NOERP01P/NOERP01P &
Page 878
ONLY AIX
/usr/bin/du -sm /var/spool/mail/* | /usr/bin/sort -rn | /usr/bin/head | /usr/bin/awk '!/.gz$/ {if ($1 > 200) {system ("/usr/bin/gzip -c "$2" > "$2"_`/usr/bin/date \"+%d%m%y_%T\"`.gz;>"$2)}}'
Page 879
ONLY AIX
Page 880
ONLY AIX
Page 881
ONLY AIX
Page 882
ONLY AIX
Page 883
ONLY AIX
Page 884
ONLY AIX
Page 885
ONLY AIX
Page 886
ONLY AIX
Cuando el umbral de app sobrepasa el umbral a FS cache puede haber un problema y los archivos pasarian a escribir directamente al disco presentando fallas en el performance
Page 887
ONLY AIX
for i in /db2/P21/sapdata1 /db2/P21/sapdata2 /db2/P21/sapdata3 /db2/P21/sapdata4^Jdo^J./cli_chfs -a size=+2G $i^Jd
mkuser id='3001' pgrp='dba' su='true' home='/home/efigmonv' gecos='Efigenia Monroy' efigmonv
mkuser id='3001' pgrp='dba' su='true' home='/home/efigmonv' gecos='Efigenia Monroy' efigmonv
Page 888
ONLY AIX
Page 889
ONLY AIX
Page 890
ONLY AIX
Page 891
ONLY AIX
Page 892
ONLY AIX
Page 893
ONLY AIX
Page 894
ONLY AIX
Page 895
ONLY AIX
Page 896
ONLY AIX
Page 897
ONLY AIX
mkuser id='3001' pgrp='dba' su='true' home='/home/efigmonv' gecos='Efigenia Monroy' efigmonv
mkuser id='3001' pgrp='dba' su='true' home='/home/efigmonv' gecos='Efigenia Monroy' efigmonv
Page 898
rsync tunnel ssh
rsync tunnel ssh
http://toddharris.net/blog/2005/10/23/rsyncing-through-an-ssh-tunnel/
Page 899
ver permisos que no tiene dueo
find / \( -
fstype jfs -o -
fstype jfs2 \)
-nouser -
print
http://www.ibm.com/developerworks/aix/library/au-satuidgid/
Permisos de todos los archivos que tiene permisos de w en otros
sudo su - -c "find /temporal -type f -perm -o+w -exec ls -ld {} \;"
Page 900
INVSCOUT
invscout:
it helps to show which firmware (microcode) should be updated:
1. download: http://public.dhe.ibm.com/software/server/firmware/catalog.mic
2. copy on the server to: /var/adm/invscout/microcode
3. run: invscout (it will collect data and creates: /var/adm/invscout/<hostname>.mup)
4. upload <hostanme>.mup to: http://www14.software.ibm.com/webapp/set2/mds/fetch?page=mdsUpload.html
Page 901
INVSCOUT
4. upload <hostanme>.mup to: http://www14.software.ibm.com/webapp/set2/mds/fetch?page=mdsUpload.html
Page 902
mandar comandos desde la hmc al
mandar comandos desde la hmc al VIO
viosvrcmd -m caja -p nombrevios -c comando
Page 903
Ver log de subida IAX
sudo alog -o -t boot |more
Page 904
disco no ocupado
lquerypv -ht /dev/hdisk343
Page 905
MENSAJE HMC BA090007
MENSAJE HMC BA090007
BA090007
Explanation
An attempt to read the boot disk failed because of a reserve condition.
Problem determination
* Identify and remove any active RESERVES on the fibre channel storage server.
Solucion
Hola Henry,
Te envo el detalle del mensaje, cualquier consulta me avisas.
214 SCAN_ERROR_CHRP Nov 19 14:56:24 COIBMSXPAIX01 H PERM sysplanar0
--This SRC means:
BA090007
Explanation: An attempt to read the boot disk failed because of a reserve condition.
Problem determination: Identify and remove any active RESERVES on the fibre channel storage server.
.....
..... lsvg -p rootvg
.....
rootvg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk8 active 799 54 11..02..00..00..41
hdisk8 Available 70-T1-01 U9117.MMB.0644A3R-V17-C70-T1-W5005076303081020-L4038403400000000 MPIO IBM 2107 FC Disk
-- Native MPIO in use.
On AIX "devrsrv" can be used to query and clear reservations. devrsrv in included in AIX 6.1 TL7 and AIX 7.1 TL1 and above. Here is more information on the command:
http://pic.dhe.ibm.com/infocenter/aix/v6r1/index.jsp?topic=%2Fcom.ibm.aix.cmds%2Fdoc%2Faixcmds2%2Fdevrsrv.htm
Examples:
Query:
# devrsrv -c query -l hdisk0
Clear:
# devrsrv -c release -l hdisk0
# devrsrv -f -l hdisk0
Page 906
MENSAJE HMC BA090007
Page 907
MENSAJE HMC BA090007
2013-11-19 19:54:11 UTC TZ=America/Bogota <--CHRP Analysis SRC: BA090007
Problem determination: Identify and remove any active RESERVES on the fibre channel storage server.
hdisk8 Available 70-T1-01 U9117.MMB.0644A3R-V17-C70-T1-W5005076303081020-L4038403400000000 MPIO IBM 2107 FC Disk
On AIX "devrsrv" can be used to query and clear reservations. devrsrv in included in AIX 6.1 TL7 and AIX 7.1 TL1 and above. Here is more information on the command:
http://pic.dhe.ibm.com/infocenter/aix/v6r1/index.jsp?topic=%2Fcom.ibm.aix.cmds%2Fdoc%2Faixcmds2%2Fdevrsrv.htm
Page 908
MENSAJE HMC BA090007
Page 909
configurar nmon lpars
configurar nmon lpars
Page 910
configurar nmon lpars
Page 911
CAMBIO PASSWORD CON CLAVE
echo "$user:$passU" | sudo /usr/bin/chpasswd
Comando sin clave echo "Clave" |sudo -S passwd Usuario
erm
Page 912
EEH temporary error for adapter
EEH temporary error for adapter
1532D3BD 0702160513 T H ent2 EEH temporary error for adapter
apagar y volver a prender la lpar para que cargue el perfil
Page 913
secuencia_ksh_csh
secuencia ksh bash cssh
Page 914
secuencia_ksh_csh
Page 915
filemon
filemon
Page 916
filemon
Page 917
Tunnel ssh
tsocks ssh -f ibmadmhe@10.1.128.21 -L 9997:10.201.1.83:443 -N
En la maquina base se ejecuta ssh-keygen -t rsa -b 1024
tunnel ssh
Page 918
AGENTES TIVOLI
TEMS TIVOLI TELEFONICA
MORATO 10.201.129.30
GLOBAL CROSSING 10.201.2.130
Page 919
0516-404 allocp no crecer FS
0516-404 allocp: This system cannot fulfill the allocation request.
There are not enough free partitions or not enough physical volumes
to keep strictness and satisfy allocation requests. The command
should be retried with different allocation characteristics
causa UPPER BOUND dejarlo en 1024 http://docs.gz.ro/node/111
Page 920
0516-404 allocp no crecer FS
http://docs.gz.ro/node/111
Page 921
INSTALACION DE TL'S EN AIX
PASOS
1 PASAR LOS MEDIOS DE FIX CENTRAL IBM
2 PARA INSTALAR DE UN TL SE PUEDE HACER EN MODO NORMAL
3 SMITTY INSTALLP
4 Update Installed Software to Latest Level (Update All)
5 INPUT device / directory for software Se pone la ruta (si estas ubicado hay poner .)
6 PREVIEW only? (update operation will NOT occur) Yes Para revise cuales dependencias le hacen falta
7 COMMIT software updates? No Por lo general se deja NO
8 ACCEPT new license agreements? Yes Para arrancar con el parchado
Page 922
INSTALACION DE TL'S EN AIX
Se pone la ruta (si estas ubicado hay poner .)
Para revise cuales dependencias le hacen falta
Por lo general se deja NO
Para arrancar con el parchado
Page 923
reconocer discos en linux
Saber que est en el sistema:
#fdisk -l > /tmp/DISCOS1.txt
Hacer un scan de nuevos discos
SCSI:
# echo "- - -" >
/sys/class/scsi_host/host1/scan
# echo "- - -" >
/sys/class/scsi_host/host2/scan
# echo "- - -" >
/sys/class/scsi_host/host3/scan
# echo "- - -" >
/sys/class/scsi_host/host4/scan
Verificar si el nuevo disco
SCSI es reconocido por el SO:
# fdisk -l > /tmp/DISCOS2.txt
ver la diferencia:
#sdiff /tmp/DISCOS1.txt /tmp/DISCOS2.txt |grep ">"
Page 924
Illegal parameter or structure
AIX 6.1
PROBLEM DESCRIPTION:
--------------------
O cliente reportou que est recebendo os seguintes erros:
uberaba:/:)swap -l
device maj,min total free
0516-022 : Illegal parameter or structure value.
0516-022 : Illegal parameter or structure value.
0516-022 : Illegal parameter or structure value.
/dev/paging02 10, 16 16384MB 16377MB
/dev/paging01 10, 15 16384MB 16383MB
/dev/paging00 10, 13 16384MB 16383MB
/dev/hd6 10, 2 16384MB 16383MB
uberaba:/:)lsps -a
Page Space Physical Volume Volume Group Size %Used Active Auto Type
Chksum
0516-022 : Illegal parameter or structure value.
0516-022 : Illegal parameter or structure value.
0516-022 : Illegal parameter or structure value.
paging02 hdisk10 rootvg 16384MB 1 yes yes lv 0
paging01 hdisk10 rootvg 16384MB 1 yes yes lv 0
paging00 hdisk1 rootvg 16384MB 1 yes yes lv 0
hd6 hdisk1 rootvg 16384MB 1 yes yes lv 0
ACTION TAKEN:
-------------
Solicitei ao cliente o envio da consulta abaixo da ODM para obter todas
as paging spaces que haviam no AIX:
# odmget CuAt | grep paging
value = "paging"
name = "paging00"
name = "paging00"
name = "paging00"
value = "paging"
name = "paging00"
name = "paging01"
name = "paging01"
name = "paging01"
name = "paging01"
value = "paging"
Page 925
Illegal parameter or structure
name = "paging01"
name = "paging02"
name = "paging02"
name = "paging02"
name = "paging02"
value = "paging"
name = "paging02"
name = "paging04"
name = "paging04"
name = "paging04"
name = "paging04"
value = "paging"
name = "paging04"
name = "paging05"
name = "paging05"
name = "paging05"
name = "paging05"
value = "paging"
name = "paging05"
name = "paging06"
name = "paging06"
name = "paging06"
name = "paging06"
value = "paging"
name = "paging06"
name = "paging04"
name = "paging05"
name = "paging06"
name = "paging00"
# odmget -q value=paging CuAt
CuAt:
name = "hd6"
attribute = "type"
value = "paging"
type = "R"
generic = "DU"
rep = "s"
nls_index = 639
CuAt:
name = "paging00"
attribute = "type"
value = "paging"
type = "R"
generic = "DU"
Page 926
Illegal parameter or structure
rep = "s"
nls_index = 639
CuAt:
name = "paging01"
attribute = "type"
value = "paging"
type = "R"
generic = "DU"
rep = "s"
nls_index = 639
CuAt:
name = "paging02"
attribute = "type"
value = "paging"
type = "R"
generic = "DU"
rep = "s"
nls_index = 639
CuAt:
name = "paging04"
attribute = "type"
value = "paging"
type = "R"
generic = "DU"
rep = "s"
nls_index = 639
CuAt:
name = "paging05"
attribute = "type"
value = "paging"
type = "R"
generic = "DU"
rep = "s"
nls_index = 639
CuAt:
name = "paging06"
attribute = "type"
value = "paging"
type = "R"
generic = "DU"
rep = "s"
Page 927
Illegal parameter or structure
nls_index = 639
Validei junto com ele atravs do lsvg -l que as paging spaces faltantes
no estavam em nenhum dos VG's ativos.
Passei para ele que em algum momento estes paging spaces existiram no
servidor, mas que em algum momento os discos ondem ele estavam foi
removido indevidamente do servidor.
Enviei a ele os comandos abaixo para limpar a ODM dos paging spaces:
# odmget CuAt > /tmp/backup_CuAt.bak <- backup da ODM CuAt
# odmdelete -q name=paging04 -o CuAt
# odmdelete -q name=paging05 -o CuAt
# odmdelete -q name=paging06 -o CuAt
Aps remover as entradas da ODM os comandos lsps e swap voltaram a
executar com sucesso, o cliente agradeceu o atendimento e autorizou o
encerramento do chamado.
Page 928
Para crear una relacion de confianza obligatoriamente el usuario debe ser propietario de HOME
procedimiento correcto:
DESDE SGS NUEVO
ssh-keygen -t dsa -b 1024
cd .ssh/
bash-3.00$ pwd
/INTERFASES/SGS/ALTURAMORA/.ssh
bash-3.00$ mv id_dsa.pub id_dsa.pub_sgs
bash-3.00$ scp id_dsa.pub_sgs moraadm@rmcapro:.ssh/id_dsa.pub_sgs
cat id_dsa.pub_rmcapro >> authorized_keys
chmod 600 authorized_keys
rm id_dsa.pub_sgs
rm id_dsa.pub_rmcapro
los permisos deben ser 755
En la maquina base se ejecuta ssh-keygen -t rsa -b 1024
DESDE RMCAPRO
ssh-keygen -t dsa -b 1024
cd .ssh/
bash-3.00$ pwd
/INTERFASES/SGS/ALTURAMORA/.ssh
mv id_dsa.pub id_dsa.pub_rmcapro
scp id_dsa.pub_rmcapro moraadm@10.113.4.205:.ssh/id_dsa.pub_rmcapro
cat id_dsa.pub_sgs >> authorized_keys
chmod 600 authorized_keys
rm id_dsa.pub_sgs
rm id_dsa.pub_rmcapro
RED aix
Cuando esta asi es por que va directamente a la caja y no esta virtualizado HEA 1 Logical I/O Slot lhea0 ent0
$ lsslot -c slot
# Slot Description Device(s)
HEA 1 Logical I/O Slot lhea0 ent0
U9117.MMA.1084FC5-V5-C0 Virtual I/O Slot vsa0
U9117.MMA.1084FC5-V5-C2 Virtual I/O Slot vscsi0
U9117.MMA.1084FC5-V5-C3 Virtual I/O Slot vscsi1
U9117.MMA.1084FC5-V5-C4 Virtual I/O Slot vscsi2
U9117.MMA.1084FC5-V5-C5 Virtual I/O Slot vscsi3
U9117.MMA.1084FC5-V5-C6 Virtual I/O Slot vscsi4
U9117.MMA.1084FC5-V5-C7 Virtual I/O Slot vscsi5
U9117.MMA.1084FC5-V5-C8 Virtual I/O Slot vscsi6
U9117.MMA.1084FC5-V5-C9 Virtual I/O Slot vscsi7
U9117.MMA.1084FC5-V5-C10 Virtual I/O Slot vscsi8
U9117.MMA.1084FC5-V5-C11 Virtual I/O Slot vscsi9
U9117.MMA.1084FC5-V5-C12 Virtual I/O Slot vscsi10
U9117.MMA.1084FC5-V5-C13 Virtual I/O Slot vscsi11
U9117.MMA.1084FC5-V5-C14 Virtual I/O Slot vscsi12
U9117.MMA.1084FC5-V5-C15 Virtual I/O Slot vscsi13
Aca si est virtualizado desde el VIO U9117.MMA.1084FC5-V5-C16 Virtual I/O Slot ent1
Revisar configuracion de la Lhea lscfg -vpl lhea0
Page 931
RED aix
HEA 1 Logical I/O Slot lhea0 ent0
# Slot Description Device(s)
HEA 1 Logical I/O Slot lhea0 ent0
U9117.MMA.1084FC5-V5-C0 Virtual I/O Slot vsa0
U9117.MMA.1084FC5-V5-C2 Virtual I/O Slot vscsi0
U9117.MMA.1084FC5-V5-C3 Virtual I/O Slot vscsi1
U9117.MMA.1084FC5-V5-C4 Virtual I/O Slot vscsi2
U9117.MMA.1084FC5-V5-C5 Virtual I/O Slot vscsi3
U9117.MMA.1084FC5-V5-C6 Virtual I/O Slot vscsi4
U9117.MMA.1084FC5-V5-C7 Virtual I/O Slot vscsi5
U9117.MMA.1084FC5-V5-C8 Virtual I/O Slot vscsi6
U9117.MMA.1084FC5-V5-C9 Virtual I/O Slot vscsi7
U9117.MMA.1084FC5-V5-C10 Virtual I/O Slot vscsi8
U9117.MMA.1084FC5-V5-C11 Virtual I/O Slot vscsi9
U9117.MMA.1084FC5-V5-C12 Virtual I/O Slot vscsi10
U9117.MMA.1084FC5-V5-C13 Virtual I/O Slot vscsi11
U9117.MMA.1084FC5-V5-C14 Virtual I/O Slot vscsi12
U9117.MMA.1084FC5-V5-C15 Virtual I/O Slot vscsi13
U9117.MMA.1084FC5-V5-C16 Virtual I/O Slot ent1
lscfg -vpl lhea0
Page 932
Descripcion
Procedimiento para crear un VG
se reconoce el disco
se da formato LVM al disco
se asigna todo el espacio (segun sea)
Se crea el Volume Group
Se crea el Logical Volume apartir de Volume group
Mkfs se da label a la particion mkfs.ext3 /dev/VGDATA/lvm_oracle
VGDATA Volume group
LVM_ORACLE Logical volume
Creacion de vlan suse
Eliminacion de Vlan
servicios
Comandos
vconfig add eth0 5
ifconfig eth0.5
ifconfig eth0.5 192.168.1.100 netmask 255.255.255.0 broadcast 192.168.1.255 up
ifconfig eth0.5 down
vconfig rem eth0.5
chkconfig
comentarios
se agrega el id de la vlan a la interfaz eth0
SE ASIGNA LA IP A LA VLAN
Buscar un grupo en el directorio activos
Obtener el listado de este grupo
Buscar UNA OU en el directorio activo
Listar los equipos
dsquery group -name G_GGS_USB-ENABLED GRUPO
dsget group "CN=G_GGS_USB-ENABLED,CN=Grupos,DC=etb,DC=com,DC=co" -members
dsquery ou -name Equipos_Vi OU
dsquery computer "OU=Equipos_VI,OU=COMPUTADOR ES,DC=etb,DC=com,DC=co"
UNIDAD ORGANIZACIONAL
CRTICA ---F-X- 123525 23/09/10 S2KAUTP03 OS SYSADMIN MEMORY PAGES/SEC THE THRESHOLD OF 25,00 HAS BEEN CROSSED BY 81,71.
CRTICA ------- 63733 27/09/10 SGSPRODHA-GT BAC SYSADMIN DISCO NUMERO DE IOS 5107.33%, EXCEDE EL UMBRAL CONFIGURADO 4800.00%.
CRTICA ------- 102103 29/10/10 ETB-SIEBELDB-GT BAC SYSADMIN RED NUMERO DE PAQUETES ENVIADOS 113296.73, EXCEDE EL UMBRAL CONFIGURADO 98000.00%
CRTICA ---F-X- 123525 23/09/10 S2KAUTP03 OS SYSADMIN MEMORY PAGES/SEC THE THRESHOLD OF 25,00 HAS BEEN CROSSED BY 81,71. ALARMA DE PAGINACION DE MEMORIA
CRTICA ------- 63733 27/09/10 SGSPRODHA-GT BAC SYSADMIN DISCO NUMERO DE IOS 5107.33%, EXCEDE EL UMBRAL CONFIGURADO 4800.00%. IOS del disco generalmente por un pico en las transacciones (normal)
CRTICA ------- 102103 29/10/10 ETB-SIEBELDB-GT BAC SYSADMIN RED NUMERO DE PAQUETES ENVIADOS 113296.73, EXCEDE EL UMBRAL CONFIGURADO 98000.00% SE REVISA EL SERVIDOR Y EN ESTE MOMENTO TRABAJA SIN PROBLEMAS, LA ALARMA OCURRE POR UN PICO EN LAS TRANSACCIONES.
IOS del disco generalmente por un pico en las transacciones (normal)
SE REVISA EL SERVIDOR Y EN ESTE MOMENTO TRABAJA SIN PROBLEMAS, LA ALARMA OCURRE POR UN PICO EN LAS TRANSACCIONES.
SE REVISA EL SERVIDOR Y EN ESTE MOMENTO TRABAJA SIN PROBLEMAS, LA ALARMA OCURRE POR UN PICO EN LAS TRANSACCIONES.
Linea a comentar prestamo de ro
#linea para comentariar cuando se presta root
#if [[ $cnt = 1 ]]; then
#exit 1
#fi
#fin de la linea comentariada por root
TTYS=ALL
Permit login root = yes
secundary login agregarlo en el /etc/profile
if [ `whoami` = "root" ]
then
REAL_USER=${REAL_USER:-$(who am i | awk '{print $1}')}
export REAL_USER
if [[ $REAL_USER = "root" ]];then
#Set the tty type on the below line based on the type of console
if [[ $(tty|awk '{print index($0,"vty")+index($0,"lft")}') = 0 ]];then
TOPppid=$(ps -ef|grep dtsession|grep -v grep|awk '{print $2}')
TOPppid=${TOPppid:-"1"}
cnt=$$
while [ $cnt -gt 1 ] && [ $cnt -ne $TOPppid ] && [ $REAL_USER = "root" ]
do
PPID_Name=$(ps -p $cnt -o ppid=,ruser= )
cnt=$(echo "$PPID_Name"|awk '{print $1}')
REAL_USER=$(echo "$PPID_Name"|awk '{print $2}')
done
#linea para comentariar cuando se presta root
#if [[ $cnt = 1 ]]; then
#exit 1
#fi
#fin de la linea comentariada por root
fi
fi
Dir="/var/log"
if [[ ! -d $Dir ]];then
mkdir $Dir
fi
WHOas="${REAL_USER}.as.${LOGNAME}"
HISTFILE="$Dir/.hist.${WHOas}"
if [ ! -f $HISTFILE ]; then
Page 943
Linea a comentar prestamo de ro
printf "\001\001\n\000\000" > $HISTFILE
touch ${HISTFILE}_smit.log ${HISTFILE}_smit.script
chmod 600 ${HISTFILE} ${HISTFILE}_smit.log ${HISTFILE}_smit.script
fi
export HISTFILE
echo "#\n# Begin $WHOas ($(tty)) on $(date +%m-%d-%Y@%T)" >> $HISTFILE
printf "\000\000" >> $HISTFILE
alias smitty='smitty -l "${HISTFILE}_smit.log" -s "${HISTFILE}_smit.script"'
alias smit='smit -l "${HISTFILE}_smit.log" -s "${HISTFILE}_smit.script"'
fi
Page 944
Installation of 125670-04 failed. Return code 1 No hay problema
Installation of 119309-03 failed. Return code 8 No hay problema
Installation of 119309-03 failed. Return code 15 No hay problema
IRQ 0 CRONOMETRO DEL SISTEMA
IRQ 1 CONTROLADOR DEL TECLADO
IRQ 2 Interrupciones encascadaparalas interrupciones IRQ del 8 al 15.
IRQ 3 Segundo Puerto Serie (COM2). Amenudoestambinparaelcuartopuertoserie(COM4)
IRQ 4 Primer Puerto Serie (COM1). Tambin es utilizado pordefectoparael COM3
IRQ 5 TARJETA DE SONIDO
IRQ 6 CONTROLADORA DE DISQUERA
IRQ 7 Puerto ParaleloLPT1paraimpresorasocualquierotrodispositivoque utilizapuertoparalelo.
IRQ 8 Reloj del Sistema.
IRQ 9, 10, 11 Interrupcindisponibleparaperifricosextras.
IRQ 12
Mouse PS/2 oPlacade Red o similares.
IRQ 13 Coprocesador/Unidad de punto flotante
IRQ 14 Canal IDE Primario
IRQ 15 Canal IDE Secundario
Segundo Puerto Serie (COM2). Amenudoestambinparaelcuartopuertoserie(COM4)
Puerto ParaleloLPT1paraimpresorasocualquierotrodispositivoque utilizapuertoparalelo.
Ejemplo Descripcin
01 * * * *
Se ejecuta al minuto 1
de cada hora de todos
los das
15 8 * * *
A las 815 a.m. de cada
da
15 20 * * *
A las 815 p.m. de cada
da
00 5 * * 0
A las 5 a.m. todos los
domingos
* 5 * * Sun
Cada minuto de 500a.m.
a 559a.m. todos los
domingos
45 19 1 * *
A las 745 p.m. del
primero de cada mes
01 * 20 7 *
Al minuto 1 de cada
hora del 20 de julio
10 1 * 12 1
A la 110 a.m. todos los
lunes de diciembre
00 12 16 * Wen
Al medioda de los das
16 de cada mes y que
sea Mircoles Domingo
30 9 20 7 4
A las 930 a.m. del dia
20 de julio y que sea
jueves 0
30 9 20 7 *
A las 930 a.m. del dia
20 de julio sin importar
el da de la semana
20 * * * 6
Al minuto 20 de cada
hora de los sbados
20 * * 1 6
Al minuto 20 de cada
hora de los sbados de
enero
00 00,12 * * * /export/home/admgt07/gestion.sh
se ejecuta este script a
las 12 de la noche y a
las 10 del dia
Lunes Martes Miercoles Jueves Viernes Sabado
1 2 3 4 5 6
Secundary login
Instrucciones para habilitar el secondary logging para sudo su -
El secondary logging permite crear un log personal para cada usuario al momento de hacer sudo su -
KSH
1. Agregar al final del /etc/profile. Y verificar que no haya ningun script de SysLog.
IMPORTANTE: Hacer un Backup del profile por si algo sale mal.

if [ `whoami` = "root" ]
then
REAL_USER=${REAL_USER:-$(who am i | awk '{print $1}')}
export REAL_USER
if [[ $REAL_USER = "root" ]];then
#Set the tty type on the below line based on the type of console
if [[ $(tty|awk '{print index($0,"vty")+index($0,"lft")}') = 0 ]];then
TOPppid=$(ps -ef|grep dtsession|grep -v grep|awk '{print $2}')
TOPppid=${TOPppid:-"1"}
cnt=$$
while [ $cnt -gt 1 ] && [ $cnt -ne $TOPppid ] && [ $REAL_USER = "root" ]
do
PPID_Name=$(ps -p $cnt -o ppid=,ruser= )
cnt=$(echo "$PPID_Name"|awk '{print $1}')
REAL_USER=$(echo "$PPID_Name"|awk '{print $2}')
done
if [[ $cnt = 1 ]]; then
exit 1
fi
fi
fi
Dir="/var/log"
if [[ ! -d $Dir ]];then
mkdir $Dir
fi
WHOas="${REAL_USER}.as.${LOGNAME}"
HISTFILE="$Dir/.hist.${WHOas}"
if [ ! -f $HISTFILE ]; then
printf "\001\001\n\000\000" > $HISTFILE
touch ${HISTFILE}_smit.log ${HISTFILE}_smit.script
chmod 600 ${HISTFILE} ${HISTFILE}_smit.log ${HISTFILE}_smit.script
fi
Page 950
Secundary login
export HISTFILE
echo "#\n# Begin $WHOas ($(tty)) on $(date +%m-%d-%Y@%T)" >> $HISTFILE
printf "\000\000" >> $HISTFILE
alias smitty='smitty -l "${HISTFILE}_smit.log" -s "${HISTFILE}_smit.script"'
alias smit='smit -l "${HISTFILE}_smit.log" -s "${HISTFILE}_smit.script"'
fi
IMPORTANTE 2: Tener en cuenta que este script evita el login directo con root. Si el cliente requiere login por root, se deben comentar las siguientes lineas
if [[ $cnt = 1 ]]; then
exit 1
fi
2. Salir de la sesion de root, y volver a ingresar a con sudo su -
3. Validar que se creen los logs de usuario en /var/log/, deberian existir tres archivos con una sintaxis similar a :
/var/log/.hist.ibmadmxx.as.root_smit.script
/var/log/.hist.ibmadmxx.as.root_smit.log
/var/log/.hist.ibmadmxx.as.root
NOTA IMPORTANTE:
Para que el script de validacin, pase correctamente se deben cumplir las siguientes reglas:
1. Se debe crear un log personal con los comandos ejecutados durante sudo su -
2. Debe existir en la maquina un log con ms de 60 dias
Para correr el script:
Descargarlo de http://w3.tap.ibm.com/w3ki02/display/SSOSPM/51.+Projects
Copiarlo por SCP a la maquina, y ejecutarlo con la siguiente sintaxis
./secondary_logging.v111 -a NOMBRE_DE_LA CUENTA -u USUARIO PERSONAL
Para mayor informacin del script, verificar el archivo README presente en el archivo tar
Referencia: https://w3.tap.ibm.com/w3ki07/display/sudocomp/Secondary+Logging
BASH Mtodo 1
1. Realizar un backup del /etc/profile/
#Secondary Logging BASH
if [ `echo $LOGNAME` = "root" ]
Page 951
Secundary login
then
REAL_USER=${REAL_USER:-$(echo $LOGNAME)}
export REAL_USER
if [[ $REAL_USER = "root" ]];then
#Set the tty type on the below line based on the type of console
if [[ $(tty|awk '{print index($0,"vty")+index($0,"lft")}') = 0 ]];then
TOPppid=$(ps -ef|grep dtsession|grep -v grep|awk '{print $2}')
TOPppid=${TOPppid:-"1"}
cnt=$$
while [ $cnt -gt 1 ] && [ $cnt -ne $TOPppid ] && [ $REAL_USER = "root" ]
do
PPID_Name=$(ps -p $cnt -o ppid,ruser|tail -1 )
cnt=$(echo "$PPID_Name"|awk '{print $1}')
REAL_USER=$(echo "$PPID_Name"|awk '{print $2}')
done
if [[ $cnt = 1 ]]; then
exit 1
fi
fi
fi
Dir="/var/log"
if [[ ! -d $Dir ]];then
mkdir $Dir
fi
WHOas="${REAL_USER}.as.${LOGNAME}"
HISTFILE="$Dir/.hist.${WHOas}"
if [ ! -f $HISTFILE ]; then
printf "\001\001\n\000\000" > $HIST
FILE
touch ${HISTFILE}_smit.log ${HISTFILE}_smit.script
chmod 600 ${HISTFILE} ${HISTFILE}_smit.log ${HISTFILE}_smit.script
fi
export HISTFILE
echo "#\n# Begin $WHOas ($(tty)) on $(date +%m-%d-%Y@%T)" >> $HISTFILE
printf "\000\000" >> $HISTFILE
alias smitty='smitty -l "${HISTFILE}_smit.log" -s "${HISTFILE}_smit.script"'
alias smit='smit -l "${HISTFILE}_smit.log" -s "${HISTFILE}_smit.script"'
fi
BASH Mtodo 2
1. Validar que version de BASH tiene el SO.
bash --version
Page 952
Secundary login
Si tiene 2.0 o menor:
Agregar al final del $HOME_ROOT/.bashrc
# Secondary Logging
export HISTSIZE=10000
#export HISTTIMEFORMAT="%F %T " Non supported in bash 2.05b
export HISTFILE=/var/log/sudo/root_history-$(who am i | awk '{print $1}';exit)-$(date "+%d%m%Y%H%M%S")
export PROMPT_COMMAND='history -a'
Si es mayor a 3.0 :
# Secondary Logging
export HISTSIZE=10000
export HISTTIMEFORMAT="%F %T "
export HISTFILE=/var/log/sudo/root_history-$(who am i | awk '{print $1}';exit)
export PROMPT_COMMAND='history -a'
2. Garantizar que el directorio /var/log/sudo exista
3. Cerrar la sesin y volver a hacer sudo su -
4. Validar que el log se haya creado
Como sugerencia, se puede aadir la siguiente linea en el crontab del root, con el fin de no llenar el /var con los logs de sudo
00 00 * * * find /var/log/sudo -name "root_history*" -mtime +60 -exec rm {} \;
Page 953
Secundary login
El secondary logging permite crear un log personal para cada usuario al momento de hacer sudo su -
Page 954
Secundary login
IMPORTANTE 2: Tener en cuenta que este script evita el login directo con root. Si el cliente requiere login por root, se deben comentar las siguientes lineas
3. Validar que se creen los logs de usuario en /var/log/, deberian existir tres archivos con una sintaxis similar a :
Para que el script de validacin, pase correctamente se deben cumplir las siguientes reglas:
Page 955
Secundary login
Page 956
Secundary login
export HISTFILE=/var/log/sudo/root_history-$(who am i | awk '{print $1}';exit)-$(date "+%d%m%Y%H%M%S")
Como sugerencia, se puede aadir la siguiente linea en el crontab del root, con el fin de no llenar el /var con los logs de sudo
Page 957
Caracteres especiales
^ Corresponde al inicio de la lnea
. Filtra un slo caracter
$ Corresponde al final de la lnea
* Filtra cero o ms caracteres
[] Filtra todo el rango dentro de los []
ejemplos todos estos los pueden colocar dentro de las ' ' en el comando sed para filtrar segn sea el caso
/./
Filtra cualquier lnea que tenga
al menos 1 caracter
/.../
Filtra cualquier lnea que tenga
al menos 3 caracter
/^#/
Filtra cualquier lnea que
comience con #
/^$/ Filtra cualquier lnea en blanco
/)$/
Filtra cualquier lnea que
termine con ')' (sin espacios)
/) *$/
Filtra cualquier lnea que
termine con ')' seguido por cero
o ms espacios
/[xyz]/
Filtra cualquier linea que
contenga las letras 'x' 'y' o 'z' en
minsculas
/^[DEF]/
Filtra cualquier lnea que
comience con 'D', 'E' o 'F'
RPM
Operation Short Option Long Option
Upgrade/install -U --upgrade
Install -I --install
Remove -e --erase
Query -q --query
Verify -V --verify
Check signature -K --checksig
Freshen (upgrade) already-installed
package -F --freshen
Initialize database None --initdb
Rebuild database None --rebuilddb
rpm -Uvh instalar o actualizar un paquete RPM
rpm -ivh --replacepkgs foo-1.0-1.i386.rpm ignora errores
rpm -qlp muestra todos los archivos instalados desde un rpm
rpm -qf /etc/exports Muestra los archivos instalados en un directorio
rpm -F
instalar o actualizar un paquete RPM
DEVICE COMENTARIO
DEV/HDA PRIMARIO
DEV/HDa1 PRIMARIO 1ER PARTICION O SLICE
DEV/HDB SECUNDARIO
DEV/HDC5 DISCO C PARTICION 5
DEV/SDA DISCO PRIMARIO
DEV/SDA4 DISCO PRIMARIO SLICE O PARTICION 4
DESCRIPCION
SECUENCIA Y NIVELES DE EJECUCION DEL BOOT
lpr
Puerto TCP/IP mas alto
dig
pool.ntp.org
restaura el codigo fuente (arbol) a su estado por defecto
depmod
insmod
lsmod
rmmod
modinfo
modprobe
revisa las dependencias antes de compilar
Limpia los temporales que se crean en la compilacion
compila y descomprime el kernle con la utilidad bzip2
compilar todos los modulos del kernel
Mueve los archivos al directorio correcto y modifica el /etc/lilo.conf o grub
habilitar o carga un nuevo modulo de kernel requerido
mkinitrd
Necesidad de instalar un Kernel
Tipos de kernel
filter
crear una impresora en linux
permisos 644
maquinas permitidas para imprimir
si se quiere permiten a todos los usuarios del servidor
Comandos impresin
ghostscript
Una impresora Postscript es uno que aceptan archivos PostScript (. Ps) para ser impreso. Non postscript printers normally accepts PCL files. Las impresoras no PostScript normalmente acepta archivos de PCL. Postscript printers are more portable, while PCL normally need more advanced drivers. impresoras PostScript son ms porttiles, mientras que PCL normalmente necesitan conductores ms avanzados.
Windows printers via samba
CUPS
lpstat
lprm
lpr
Broadcast
defines if networking must be started. (can also contain the HOSTNAME variable)
comando at
paginas MAN instaladas por los paquetes
Crea el /etc/shadow deja que administre las claves a partir de /etc/passwd
Deja administre las claves el /etc/passwd
creates the /etc/gshadow file
deletes the gshadow file
apsfilter
magicfilter
permite el acceso de maquinas
denega el acceso
maquina que voy a darle el acceso, filesystem que quiero compartir y permisos
Se permite el acceso desde un UID = 0 sin conversin. Es decir, los accesos de root en el cliente se convierten en accesos de root en el servidor. Root tiene privilegios en el recurso que le compartieron
Los accesos desde el cliente con UID=0 (root) se convierten en el servidor en accesos con UID de un usuario annimo (opcin por defecto)
permisos 644
El directorio se exporta como un sistema de archivos de slo lectura
El directorio se exporta como un sistema de archivos de lectura/escritura.
Todos los accesos desde el cliente (con cualquier UID) se transforman en accesos de usuario annimo.
la utilidad de sistema que crea, comprime o mueve automticamente nuevos archivos de registro segn el /etc/logrotatate.conf
ubicacin del man
mensaje que muestra cuando se ingresa por telnet
checkear sin la configuracion de apache es correcta
ver las ultimas conexiones y del archivo el cual lee
efectua cambios cuando se modifica /etc/newaliases
ubicacin del man
Limpiar el master boot record de un linux para cuando se vaya a formatear un disco no quede en disco el grub (y no aparezca el mensaje de GRUB)
paginas de documenatcion de LINUX
Donde se guardan las colas de impresin
Realiza backup incremental
crea el backup cpio
extrae los archivos desde el device
saca el backup de /home y lo guarda en /backups/home_backup en nivel 5
restaurarlo
Seccion del man que muestra los comandos
alias de un comando se guarda en
que HACE chmod g+s /home/software
From the user's point of view, which answer describes the appearance of an NFS mounted directory? Select one.
What is CHAP? Select one.
Which one of these protocols is used as a datagram delivery service by the remaining three? Select one
Which one of these protocols is used as a datagram delivery service by the remaining three? Select one.
What program is run on a client machine to request an IP address from a DHCP server? Select one
COMANDO TEST
How many hosts can exist on a subnet with mask 255.255.255.128? Select one
For an Internet workstation with a single network interface, what routes must be added to interface eth0 after it is initialized? Select one.
Consider the following excerpt from file /etc/resolv.conf of a Linux workstation: nameserver 127.0.0.1 nameserver 192.168.1.5 nameserver 192.168.250.2
Which of the following is true regarding BIND v4 and BIND v8 configuration files? Select one.
What types of files are located in the directory tree specified by the Apache DocumentRoot configuration directive? Select one.
La mascara es usada por el equipo local para determinar cuales son subredes locales y cuales estan en redes remotas
Ver cuales son los servidores de correo de un dominio
Siempre se deja reservada 3 host y 1 de gateway y 2 broadcast (192.168.11.64/26) osea en total son 64 menos 3 = a 61
11000000.10101000.00000000.00000001
11111111.11111111.00000000.00000000
Cantidad de hosts
Correra entre las 6 de la tarde y las 7 de la maana de lunes a viernes el sript.sh
Dejar inmutable el archivo /etc/passwd y /etc/shaodw (el usuario root no puede modificar el archivo)
Procesos durante el inicio
AGREGAR AL USUARIO STEWAR AL GRUPO WHEEL
reconstruir depedencias de modulos
autolimpiar los modulos cargados
During the two-way communication that takes place during a chat script used to start PPP, what is chat communicating with? Select one
After a PPP connection is established and authenticated, what needs to be done before the interface can be used? Select one
What is the systemwide bash configuration file called? Include the entire path.
How can the finger daemon be enabled? Select one.
PASOS
1. BIOS initializes its devices
2. The Boot Loader on MBR of boot disk is read and executed
3. At this point the Boot Loader may allow the user to enter Kernel options.
4. The Kernel and maybe initrd is fetched from the Floppy/Hard disk/CDROM.
5. The Kernel initializes its hardware environment, using modules compiled in the kernel.
6. The Kernel starts its first process init (PID=1)
7. The Kernel tests the root (/) and other partitions as per fstab and mounts them.
8. The Kernel initializes more hardware using /etc/modules.conf and some boot scripts.
9. init reads its configuration file /etc/inittab and acts accordingly. /etc/inittab contains the
10.list of processes that init should start, like console gettys, default runlevel, run level definitions, etc.
11. init starts the default run level scripts and passes control to the getty on virtual terminal 1 for user login.
12. If xdm/kdm/gdm display manager is started as part of the default runlevel, then the display manager takes over control of the display for graphic user login
Dependencias de los modulos
Inserta los modulos al kernel
lista los modulos
elimina un modulo de kernel instalado
muestra informacion acerca del modulo del kernel
instala modulos y sus dependencias (o las elimina)
1
2
3
4
1
Monolithic:
Modular:
es similar a un driver en windows
se crea una carpeta en la ruta
la carpeta puede llamarse printer1
se crean dentro de printer1 los archivos vacios
(logs de fallas de impresin)
(evita que dos trabajos no se envien simultaneamente)
(numero de trabajo que envia el lpr consecutivamente)
(es lo que muestra el comando lpc)
se declaran los parametros en el archivo /etc/printcap
linea de control de impresin
mostrar la cola de impresin en lnea
elimina trabajos de la cola de impresin
presenta un trabajo de impresin
archivo de configuracion
un filtro de impresin que convierte datos post script en no-postscript
Una impresora Postscript es uno que aceptan archivos PostScript (. Ps) para ser impreso. Non postscript printers normally accepts PCL files. Las impresoras no PostScript normalmente acepta archivos de PCL. Postscript printers are more portable, while PCL normally need more advanced drivers. impresoras PostScript son ms porttiles, mientras que PCL normalmente necesitan conductores ms avanzados.
componentes de samba para impresin
archivo de configuracion
-a
-c
-p
-s
protocolos de red TCP
protocolos de red TCP
Se permite el acceso desde un UID = 0 sin conversin. Es decir, los accesos de root en el cliente se convierten en accesos de root en el servidor. Root tiene privilegios en el recurso que le compartieron
Los accesos desde el cliente con UID=0 (root) se convierten en el servidor en accesos con UID de un usuario annimo (opcin por defecto)
la utilidad de sistema que crea, comprime o mueve automticamente nuevos archivos de registro segn el /etc/logrotatate.conf
si es (directorio)
si es (archivo)
si es (si tiene permiso (SGID))
si es (si tiene permiso (SUID))
si es (muestra el arhivo con el group ID)
si es (sticky bit)
si es si es un link simbolico
si el archivo o carpeta fue modificado
si es si es de lectura
si es si es de escritura
si es si es de ejecucion.
asigna el
Limpiar el master boot record de un linux para cuando se vaya a formatear un disco no quede en disco el grub (y no aparezca el mensaje de GRUB)
Consider the following excerpt from file /etc/resolv.conf of a Linux workstation: nameserver 127.0.0.1 nameserver 192.168.1.5 nameserver 192.168.250.2
What types of files are located in the directory tree specified by the Apache DocumentRoot configuration directive? Select one.
La mascara es usada por el equipo local para determinar cuales son subredes locales y cuales estan en redes remotas
Siempre se deja reservada 3 host y 1 de gateway y 2 broadcast (192.168.11.64/26) osea en total son 64 menos 3 = a 61
LINUX
1. Bios inicializa los devices
2. El master Boot Record es leido y ejectutado
3. En este punto el cargador de arranque puede permitir el ingreso de usuarios a las opciones del kernel
4. Tal vez descargue de la unidad floppy disco duro y cdrom lo necesario
5. El kernel incializa el entorno de hardaware, usando modulos complidos en el kernel
6. El kernel inicia el primer proceso init (PID =1)
7. El kernel prueba la raiz / y otras particiones que se encuentran en el fstab
8. el kernel inicializa mas hardware usabdo /Etc/modules.conf y algunos del script boot
9. Init lee las configuracion del archivo /etc/inittab y actua de acuerdo con este
10. lista de procesos que init debe iniciar(default run level)
11. init inicia el script del nivel de ejecucion
12. Si xdm / kdm / gestor de ventanas gdm se inicia como parte del nivel de ejecucin, a continuacin, el administrador de pantalla toma el control de la pantalla de inicio de sesin grfica de usuario
envia impresiones
65535
para realizar bsquedas de nombre de host saber cuales son los dns a los que se conecta la maquiina
cluster virtual con varios servidores de tiempo
mkproper
make dep
make clean
make bzimage
make modules
make install
make modules_install
crea imgenes de disco RAM inicial para precargar los mdulos
copiar los archivos del mapa del sistema al directorio /boot
copiar la imagen del kernel al directorio /boot
instalar modulos en la ubicacin correcta
All device drivers are compiled into the kernel.
Some device drivers are compiled as loadable modules

/var/spool/lpd
/var/spool/lpd/printer1
errs
lock
.seq
status
print1 | theprinter \
lp=/dev/lp1 \
sd=/var/spool/lpd/print1 \
if=/var/spool/lpd/lp/filter \
/etc/host.lpd
nombre del servidor y usuario
signo mas nombre del servidor
lpc
lpq
lprm
lpr
/etc/printcap
Una impresora Postscript es uno que aceptan archivos PostScript (. Ps) para ser impreso. Non postscript printers normally accepts PCL files. Las impresoras no PostScript normalmente acepta archivos de PCL. Postscript printers are more portable, while PCL normally need more advanced drivers. impresoras PostScript son ms porttiles, mientras que PCL normalmente necesitan conductores ms avanzados.
/etc/cups/cupsd.conf
Muestra el estado de las impresoras
muestra las clases de impresoras
muestra el estado de la impresora (enable - disable)
Muestra impresoras y device
elimina trabajos de impresin
enviar trabajos a la impresora
Cual es el broadcast de 172.18.20.0\26 172.18.20.192
/etc/sysconfig/network
similar a cron
usr/share/doc
PWCONV
pwunconv
/usr/sbin/grpconv
/usr/sbin/grpunconv
interfaz amigable MENU
Crea nueva entreda de impresin
Habilita multiple impresoras
etc/host.allow
etc/hosts.deny
/etc/exports
no_root_squash
root_squash
ro
rw
sync
all_squash
/usr/share/man/
/etc/issue.net
test -d
test -f
test -g
test -u
test -G
test -k
test -L
test -N
test -r
test -w
test -x
apachectl configtest
last /var/log /wtmp
newaliases
TLDP the linux documentation project HOW TO
/var/spool/lpd
tar -A incremental
ls /home |cpio -o > /dev/rmt0
cpio -i < /dev/rmt0
dump /sbin/dump -5f /backups/home_backup /home
restore -r /home_backup
seccion 8
~/.bashrc.
The SGID bit will be set for /home/software, to keep group membership of the directory consistent for all files created.
Part of the local filesystem, accessed using ordinary pathnames.
An authentication protocol embedded in the PPP data stream.
TCP Y UDP
IP es el protocolo de datagrama subyacente.
pump
With the top bit of the last byte set in the subnet mask (.128), there are 7 bits left. 2
7
is 128, less the network address and broadcast address, leaving 126 addresses for hosts.
d. Routes to the interface and the network are required to exchange information on the local LAN. To act as an Internet workstation (i.e., using Netscape), a default gateway is also necessary.
A caching-only name server is running.
The information is largely the same, but the syntax is different.
Add a route to ppp0.
Web site HTML files.
netmask
dig lpi.org MX
192.168.11.64/26
192.168.0.1/16
255.255.0.0
Numero de hosts 65536 (para esto se toamn en cuenta los ceros osea 2 a la 16 {este valor se le restan tres y queda 65533 }
00 18-07 * * 1-5 script.sh
chattr +i /etc/passwd y chattr +i /etc/shadow para ver los atributos lsattr ------------- /etc/passwd al cambiarlos queda ----i-------- /etc/passwd para quitarla otra opcion es chattr -i /etc/passwd
kernel loaded; init; rc.sysinit; runlevel scripts.
gpasswd -a stewart wheel
depmod -a
modprobe -k
The modem
etc/profile
For security purposes, fingerd is usually disabled using a comment in /etc/inetd.conf.
12. Si xdm / kdm / gestor de ventanas gdm se inicia como parte del nivel de ejecucin, a continuacin, el administrador de pantalla toma el control de la pantalla de inicio de sesin grfica de usuario
lp ubicacin del dispositivo de impresin
sd ubicacin del directorio, el cual guarda los documentos antes de que sea enviada a la impresora
if especifica el filtro antes de enviar un impresin (magicfilter o apsfilter)
mc especifica el numero de copias de un archivo que puede imprimir usando el comando print
sh previene la imporesion de paginas simulataneas
if especifica el log que contiene los errores
rm remote printer
Una impresora Postscript es uno que aceptan archivos PostScript (. Ps) para ser impreso. Non postscript printers normally accepts PCL files. Las impresoras no PostScript normalmente acepta archivos de PCL. Postscript printers are more portable, while PCL normally need more advanced drivers. impresoras PostScript son ms porttiles, mientras que PCL normalmente necesitan conductores ms avanzados.
The SGID bit will be set for /home/software, to keep group membership of the directory consistent for all files created.
Numero de hosts 65536 (para esto se toamn en cuenta los ceros osea 2 a la 16 {este valor se le restan tres y queda 65533 }
chattr +i /etc/passwd y chattr +i /etc/shadow para ver los atributos lsattr ------------- /etc/passwd al cambiarlos queda ----i-------- /etc/passwd para quitarla otra opcion es chattr -i /etc/passwd
ubicacin del directorio, el cual guarda los documentos antes de que sea enviada a la impresora
apsfilter permite imprimir varios formatos de datos
Una impresora Postscript es uno que aceptan archivos PostScript (. Ps) para ser impreso. Non postscript printers normally accepts PCL files. Las impresoras no PostScript normalmente acepta archivos de PCL. Postscript printers are more portable, while PCL normally need more advanced drivers. impresoras PostScript son ms porttiles, mientras que PCL normalmente necesitan conductores ms avanzados.
sin tener que convertir manualmentea un formato
Una impresora Postscript es uno que aceptan archivos PostScript (. Ps) para ser impreso. Non postscript printers normally accepts PCL files. Las impresoras no PostScript normalmente acepta archivos de PCL. Postscript printers are more portable, while PCL normally need more advanced drivers. impresoras PostScript son ms porttiles, mientras que PCL normalmente necesitan conductores ms avanzados.
de impresin especifico
Una impresora Postscript es uno que aceptan archivos PostScript (. Ps) para ser impreso. Non postscript printers normally accepts PCL files. Las impresoras no PostScript normalmente acepta archivos de PCL. Postscript printers are more portable, while PCL normally need more advanced drivers. impresoras PostScript son ms porttiles, mientras que PCL normalmente necesitan conductores ms avanzados.
Una impresora Postscript es uno que aceptan archivos PostScript (. Ps) para ser impreso. Non postscript printers normally accepts PCL files. Las impresoras no PostScript normalmente acepta archivos de PCL. Postscript printers are more portable, while PCL normally need more advanced drivers. impresoras PostScript son ms porttiles, mientras que PCL normalmente necesitan conductores ms avanzados.
Descripcion
VERIFICA ESTADO DE LA PARTICION SWAP
Kernel Monolitico
Kernel Modular
Version principal (Major version)
Version menor (minor version)
Patch level
Build number
(drivers)
Directorio que contiene los modulos
EL filesystem /proc actua como una interface entre el kernel y los procesos del sistema, este tiene apariencia de un filesystem normal y contiene archivos y carpetas (EL CONTENIDO DE LOS ARCHIVOS NO SE GUARDAN EN EL DISCO DURO) (SON GENERADOS POR DEMANDA POR EL KERNEL)
hostname
Cuando el /etc/passwd este corrupto se ingresa en el prompt LILO Linux init=/bin/bash
Cuando se este iniciando el sistema y se quiera ingresar al prompt de LILO CTRL+X ALT
Data Blocks
Superbloque
Inodo
Directorio Bloque
mkfs Crea un filesystem con tipo de archivo a partir de un devuice
Tipos de kernel y version
Filesystem
Opciones
more /proc/swaps
swapon -s
Carga todos los drivers
Carga los drivers cuando lo requiera el sistema
Cambio fundamental al codigo
Version estable (antes de entrar a produccion)
Se desarrollan para los dos ambientes estable y desarrollo
/lib/modules/2.6.26-2-686/kernel/drivers#
/lib/modules
filesystem /proc
/proc/sys/kernel/hostname
Guarad datos contenidos en un archivo "Determinado por numeros en el inodo"
el tamao del filesystem, fecha de creacion y total de numero de inodos
Un inodo es una lista de informacin relativa a un objeto determinado (por ejemplo, un archivo, directorio o enlace simblico). La informacin en poder del inodo incluye el tipo de objeto sobre el cual el nodo-i contiene informacin, permisos, informacin sobre la propiedad, y los lugares en los que se almacenan los datos.
Contiene el nombre de archivlos en un filesystem y sus correspondientes inodos.
mkfs -t ext3 /dev/fd0
Tipos de kernel y version
Filesystem
Un inodo es una lista de informacin relativa a un objeto determinado (por ejemplo, un archivo, directorio o enlace simblico). La informacin en poder del inodo incluye el tipo de objeto sobre el cual el nodo-i contiene informacin, permisos, informacin sobre la propiedad, y los lugares en los que se almacenan los datos.
Un inodo es una lista de informacin relativa a un objeto determinado (por ejemplo, un archivo, directorio o enlace simblico). La informacin en poder del inodo incluye el tipo de objeto sobre el cual el nodo-i contiene informacin, permisos, informacin sobre la propiedad, y los lugares en los que se almacenan los datos.
CRECER INODOS AIX
/var/mmfs/gen/mmsdrfs Veo donde estan los archivos de configiracion
crecer inodos aix
ver mmdf smartceo_gpfs -F
crecer sudo ./mmchfs smartceo_gpfs --inode-limit 80000:80000
http://www.ibm.com/developerworks/linux/library/l-snmp-gpfs/
configurar gpfs para que alerte
Alertas gpfs
su
Pagina para ver comandos utiles
GPFS cluster general commands on AIX
GPFS cluster general commands on AIX
Terminology:
mm ========> Multi Media
NSD ========> Network Shared Disk
mmfsd (1191 is default port) ========> GPFS daemon
Daemon will do I/O and buffer management.
Location of files:
/var/adm/ras/mmfs.log.latest ========> gpfs log file
/usr/lpp/mmfs/bin ========> GPFS command location
/var/mmfs/gen/mmsdrfs ========> Configuration file
Commands:
mmlscluster ========> to list the cluster
mmgetstate -aLs ========> to view the status of the GPFS cluster
mmlsconfig ========> Basic configuration information of the GPFS including no.of Filesystems
lsof -i :1191 -P ========> to check the daemon port listen state.
mmlsmgr -c ========> to view the GPFS manager
mmlsnfd -f <FS-name> -m ========> To check the
mmlsfs all ========> To check all GPFS file ssytems (lower alphabets are current values)
mmdf <mount-point> ========> To check the gpfs file system size
mmdsh ========> To configure trust relation between cluster nodes
mmlsnsd ========> To
mmlsdisk <file-system> -d <disk-name> ========> To view the disk information
mmaddnode ========> to add client node
Page 996
CRECER INODOS AIX
mmchnode ========> To change client node name
mmcrcluster ========> To create gpfs cluster
/usr/lpp/mmfs/samples ========> location of same files created by installing base filesets
mmlslicense ========> To view the GPFS license
mmlsmgr ========> To check the cluster Manager and File Manager
mmfsadm dump version ========> shows the Version and no.of days cluster is up.
mmshutdown -a ========> shutdown the GPFS cluser in all nodes.
mmstartup -a ========> Starts the cluster in all nodes.
mmfsadm dump config ========> GPFS attributes information
mmchcluster ========> To change the cluster
mmlsnsd ========> will show NSD disks
mmlsnsd -M ========> Show the detailed NSD disks
mmdf <F.S> ========> Show GPFS filesystem details
mmlsdisk <FS-name> ========> Will shows the disks for that file system
To remove GPFS file system:
mmumount <file-system> -a ========> To unmount
mmdelfs <File-system> ========> To remove gpfs filesystem
mmdelnsd <NSD-name>,<NSD-name> ========> To delete the NSD disk
mmcrnsd -F /tmp/disk.list ========> To create a nsd disk (/tmp/disk.list file with entries)
mmcrfs <FS-name> -F </tmp/fs.list> -A yes -T <mount-point> ========>To create File system
mmadddisk <FS-name> -F </tmp/fs.list> ========> To add new disk to File system
touch /var/mmfs/etc/ignoreStartupMount ========> To ignore any GPFS filesystem while system is rebooting.
touch /var/mmfs/etc/ignoreStartupMount.<devicename> ========> to do not mount this FS while system boot
Upgrading the GPFS cluster on AIX
All the GPFS nodes should be upgrade at same time.
Make sure the Application is stopped fully.
Before starting with OS Upgrade all the GPFS file system should be unmounted. If there are any application process running, and those process using the GPFS file systems, we cannot unmount the GPFS file systems.
Before the OS upgrade starts, the GPFS cluster should be stopped.
Before starting the OS Upgrade starts complete below steps.
# mmlscluster ======> View the cluster information
Example output:
GPFS cluster information
#N/A
GPFS cluster name: HOST.test1-gpfs
GPFS cluster id: 13882565243868289165
GPFS UID domain: HOST.test1-gpfs
Remote shell command: /usr/bin/ssh
Remote file copy command: /usr/bin/scp
GPFS cluster configuration servers:
Page 997
CRECER INODOS AIX
-----------------------------------
Primary server: test1-gpfs
Secondary server: test2-gpfs
Node Daemon node name IP address Admin node name Designation
-----------------------------------------------------------------------------------------------
1 test1-gpfs 192.168.199.137 test1-gpfs quorum
2 test3-gpfs 192.168.199.138 test3-gpfs quorum
3 test2-gpfs 192.168.199.139 test2-gpfs quorum
# mmlsfs all ======> View all the gpfs file systems
Example output:
File system attributes for /dev/gpfs1001:
#N/A
flag value description
---- ---------------- -----------------------------------------------------
-f 131072 Minimum fragment size in bytes
-i 512 Inode size in bytes
-I 32768 Indirect block size in bytes
-m 1 Default number of metadata replicas
-M 2 Maximum number of metadata replicas
-r 1 Default number of data replicas
-R 2 Maximum number of data replicas
-j cluster Block allocation type
-D nfs4 File locking semantics in effect
-k all ACL semantics in effect
-a -1 Estimated average file size
-n 64 Estimated number of nodes that will mount file system
-B 4194304 Block size
-Q user;group;fileset Quotas enforced
none Default quotas enabled
-F 1000000 Maximum number of inodes
-V 10.01 (3.2.1.5) File system version
-u yes Support for large LUNs?
-z no Is DMAPI enabled?
-L 4194304 Logfile size
-E yes Exact mtime mount option
-S no Suppress atime mount option
-K whenpossible Strict replica allocation option
-P system Disk storage pools in file system
-d gpfs1nsd;gpfs2nsd;gpfs3nsd;gpfs4nsd Disks in file system
-A yes Automatic mount option
-o none Additional mount options
-T /sasmart Default mount point
File system attributes for /dev/gpfs1002:
Page 998
CRECER INODOS AIX
#N/A
flag value description
---- ---------------- -----------------------------------------------------
-f 131072 Minimum fragment size in bytes
-i 512 Inode size in bytes
-I 32768 Indirect block size in bytes
-m 1 Default number of metadata replicas
Standard input -M 2 Maximum number of metadata replicas
-r 1 Default number of data replicas
-R 2 Maximum number of data replicas
-j cluster Block allocation type
-D nfs4 File locking semantics in effect
-k all ACL semantics in effect
-a -1 Estimated average file size
-n 64 Estimated number of nodes that will mount file system
-B 4194304 Block size
-Q user;group;fileset Quotas enforced
none Default quotas enabled
-F 1000000 Maximum number of inodes
-V 10.01 (3.2.1.5) File system version
-u yes Support for large LUNs?
-z no Is DMAPI enabled?
-L 4194304 Logfile size
-E yes Exact mtime mount option
-S no Suppress atime mount option
-K whenpossible Strict replica allocation option
-P system Disk storage pools in file system
-d gpfs5nsd Disks in file system
-A yes Automatic mount option
-o none Additional mount options
-T /sasplex1 Default mount point
File system attributes for /dev/gpfs1003:
#N/A
flag value description
---- ---------------- -----------------------------------------------------
-f 131072 Minimum fragment size in bytes
-i 512 Inode size in bytes
-I 32768 Indirect block size in bytes
-m 1 Default number of metadata replicas
-M 2 Maximum number of metadata replicas
-r 1 Default number of data replicas
-R 2 Maximum number of data replicas
-j scatter Block allocation type
-D nfs4 File locking semantics in effect
-k all ACL semantics in effect
Page 999
CRECER INODOS AIX
-a -1 Estimated average file size
-n 64 Estimated number of nodes that will mount file system
-B 4194304 Block size
Standard input -Q user;group;fileset Quotas enforced
none Default quotas enabled
-F 1000000 Maximum number of inodes
-V 10.01 (3.2.1.5) File system version
-u yes Support for large LUNs?
-z no Is DMAPI enabled?
-L 4194304 Logfile size
-E yes Exact mtime mount option
-S no Suppress atime mount option
-K whenpossible Strict replica allocation option
-P system Disk storage pools in file system
-d gpfs6nsd;gpfs7nsd;gpfs8nsd;gpfs9nsd;gpfs10nsd;gpfs11nsd;gpfs12nsd;gpfs13nsd;gpfs14nsd;gpfs15nsd;gpfs16nsd;gpfs17nsd;gpfs1
8nsd;gpfs19nsd;gpfs20nsd;gpfs21nsd;gpfs22nsd;
-d
gpfs23nsd;gpfs24nsd;gpfs25nsd;gpfs26nsd;gpfs27nsd;gpfs28nsd;gpfs29nsd;gpfs30nsd;gpfs31nsd;gpfs32nsd;gpfs33nsd;gpfs34nsd;g
pfs35nsd;gpfs36nsd;gpfs37nsd;gpfs38nsd;gpfs39nsd;
-d
gpfs40nsd;gpfs41nsd;gpfs42nsd;gpfs43nsd;gpfs44nsd;gpfs45nsd;gpfs46nsd;gpfs47nsd;gpfs48nsd;gpfs49nsd;gpfs50nsd;gpfs51nsd;g
pfs52nsd;gpfs53nsd;gpfs54nsd;gpfs55nsd;gpfs56nsd;
-d
gpfs57nsd;gpfs58nsd;gpfs59nsd;gpfs60nsd;gpfs61nsd;gpfs62nsd;gpfs63nsd;gpfs64nsd;gpfs65nsd;gpfs66nsd;gpfs67nsd;gpfs68nsd;g
pfs69nsd Disks in file system
-A yes Automatic mount option
-o none Additional mount options
-T /app1 Default mount point
File system attributes for /dev/gpfs1004:
#N/A
flag value description
---- ---------------- -----------------------------------------------------
-f 131072 Minimum fragment size in bytes
-i 512 Inode size in bytes
-I 32768 Indirect block size in bytes
-m 1 Default number of metadata replicas
-M 2 Maximum number of metadata replicas
-r 1 Default number of data replicas
-R 2 Maximum number of data replicas
-j cluster Block allocation type
-D nfs4 File locking semantics in effect
-k all ACL semantics in effect
-a -1 Estimated average file size
-n 64 Estimated number of nodes that will mount file system
-B 4194304 Block size
Page 1000
CRECER INODOS AIX
-Q user;group;fileset Quotas enforced
none Default quotas enabled
Standard input -F 1000000 Maximum number of inodes
-V 10.01 (3.2.1.5) File system version
-u yes Support for large LUNs?
-z no Is DMAPI enabled?
-L 4194304 Logfile size
-E yes Exact mtime mount option
-S no Suppress atime mount option
-K whenpossible Strict replica allocation option
-P system Disk storage pools in file system
-d gpfs70nsd Disks in file system
-A yes Automatic mount option
-o none Additional mount options
-T /sasuserhome Default mount point
# mmlsmount all =======> View the gpfs filesystem mounted on number of nodes
Example output:
File system gpfs1001 is mounted on 3 nodes.
File system gpfs1002 is mounted on 3 nodes.
File system gpfs1003 is mounted on 3 nodes.
File system gpfs1004 is mounted on 3 nodes.
Standard input: END
# lslpp -l |grep -i gpfs =======> Check the existing gpfs cluster version
Example output:
gpfs.base 3.2.1.18 APPLIED GPFS File Manager
gpfs.msg.en_US 3.2.1.11 APPLIED GPFS Server Messages - U.S.
gpfs.base 3.2.1.18 APPLIED GPFS File Manager
gpfs.docs.data 3.2.1.1 APPLIED GPFS Server Manpages and
# mmumount all -N test1-gpfs,test3-gpfs,test2-gpfs ==> Unmount the gpfs FS
Example output:
Wed May 11 00:05:35 CDT 2011: 6027-1674 mmumount: Unmounting file systems ...
# mmlsmount all =====> Verify all gpfs file system are un mounted
Example output:
File system gpfs1001 is not mounted.
File system gpfs1002 is not mounted.
File system gpfs1003 is not mounted.
File system gpfs1004 is not mounted.
# mmshutdown -a ======> Stop the gpfs cluster
Example output:
Wed May 11 00:08:22 CDT 2011: 6027-1341 mmshutdown: Starting force unmount of GPFS file systems
Wed May 11 00:08:27 CDT 2011: 6027-1344 mmshutdown: Shutting down GPFS daemons
Page 1001
CRECER INODOS AIX
test3-gpfs: Shutting down!
test2-gpfs: Shutting down!
test3-gpfs: 'shutdown' command about to kill process 516190
test2-gpfs: 'shutdown' command about to kill process 483444
test1-gpfs: Shutting down!
test1-gpfs: 'shutdown' command about to kill process 524420
test1-gpfs: Master did not clean up; attempting cleanup now
test1-gpfs: Wed May 11 00:09:28.423 2011: GPFS: 6027-311 mmfsd64 is shutting down.
test1-gpfs: Wed May 11 00:09:28.424 2011: Reason for shutdown: mmfsadm shutdown command timed out
test1-gpfs: Wed May 11 00:09:28 CDT 2011: mmcommon mmfsdown invoked. Subsystem: mmfs Status: down
test1-gpfs: Wed May 11 00:09:28 CDT 2011: 6027-1674 mmcommon: Unmounting file systems ...
Wed May 11 00:09:33 CDT 2011: 6027-1345 mmshutdown: Finished
# ps -ef|grep -i gpfs =====> Verify any cluster procee running
After GPFS cluster is stopped, then proceed with patching/upgrade.
Once the OS patching/upgrade complete, then upgrade the GPFS
Make sure the GPFS file systems are not in mounted state.
# mount wydainim010:/export/ibm _lpp /mnt ======> mount the NIM directory on /mnt
# /mnt/gpfs/3.3/3.3.0.12 ======> Change dir to the GPFS new version filesets location
# smitty update _all ======> Use update_all cmd to update the file sets do preview only
Example output:
INPUT device / directory for software .
* SOFTWARE to update_update_allPREVIEW only?
(update operation will NOT occur) yes =====> Select yes for Preview
COMMIT software updates? no =====> Select no for COMMIT filesets
SAVE replaced files? yes =====> Select yes here
AUTOMATICALLY install requisite software? yes+
EXTEND file systems if space needed? yes+
VERIFY install and check file sizes? no+
DETAILED output? no+
Process multiple volumes? yes+
ACCEPT new license agreements? yes =====> Accept new licence agreement
Preview new LICENSE agreements? no+
If everything is fine in PREVIEW stage, proceed with upgrading the GPFS filesets bye selecting PREVIEW as no
# lslpp -l |grep -i gpfs ======> Now verify the GPFS filesets version
Example output:
gpfs.base 3.3.0.8 APPLIED GPFS File Manager
gpfs.msg.en_US 3.3.0.5 APPLIED GPFS Server Messages - U.S.
Page 1002
CRECER INODOS AIX
gpfs.base 3.3.0.8 APPLIED GPFS File Manager
gpfs.docs.data 3.3.0.1 APPLIED GPFS Server Manpages and
Then continue with EMC upgrade and once the emc upgrade is done.
Make sure all the pv's are available in all nodes after the EMC upgrade.
Start the GPFS cluster.
# mmstartup -a =====> Starts the GPFS cluster
Example output:
Wed May 11 06:09:32 CDT 2011: 6027-1642 mmstartup: Starting GPFS ...
# mmlscluster ======> Check the GPFS cluster
Example output:
GPFS cluster information
#N/A
GPFS cluster name: HOST.test1-gpfs
GPFS cluster id: 13882565243868289165
GPFS UID domain: HOST.test1-gpfs
Remote shell command: /usr/bin/ssh
Remote file copy command: /usr/bin/scp
GPFS cluster configuration servers:
-----------------------------------
Primary server: test1-gpfs
Secondary server: test2-gpfs
Node Daemon node name IP address Admin node name Designation
-----------------------------------------------------------------------------------------------
1 test1-gpfs 192.168.199.137 test1-gpfs quorum
2 test3-gpfs 192.168.199.138 test3-gpfs quorum
3 test2-gpfs 192.168.199.139 test2-gpfs quorum
# mmgetstate -a ======> Check the GPFS cluster state on all nodes.
Example output:
Node number Node name GPFS state
------------------------------------------
1 test1-gpfs active
2 test3-gpfs active
3 test2-gpfs active
# mmlsfs all ======> Check all the filesystems
# mmmount all -a ======> Mount all the gpfs fil systems
Wed May 11 06:13:16 CDT 2011: 6027-1623 mmmount: Mounting file systems ...
# mmlsmount all ======> Check the file systems are mounted on all nodes.
Example output:
File system gpfs1001 is mounted on 3 nodes.
Page 1003
CRECER INODOS AIX
File system gpfs1002 is mounted on 3 nodes.
File system gpfs1003 is mounted on 3 nodes.
File system gpfs1004 is mounted on 3 nodes.
# mmlsconfig =======> Verify the GPFS cluster configuration information.
Example output:
Configuration data for cluster HOST.test1-gpfs:
----------------------------------------------------------
clusterName HOST.test1-gpfs
clusterId 13882565243868289165
clusterType lc
autoload yes
minReleaseLevel 3.2.1.5
dmapiFileHandleSize 32
maxblocksize 4096K
pagepool 1024M
maxFilesToCache 5000
maxStatCache 40000
maxMBpS 3200
prefetchPct 60
seqDiscardThreshhold 10240000000
worker1Threads 400
prefetchThreads 145
adminMode allToAll
File systems in cluster HOST.test1-gpfs:
---------------------------------------------------
/dev/gpfs1001
/dev/gpfs1002
/dev/gpfs1003
/dev/gpfs1004
Page 1004
CRECER INODOS AIX
mmlsconfig ========> Basic configuration information of the GPFS including no.of Filesystems
mmlsfs all ========> To check all GPFS file ssytems (lower alphabets are current values)
mmdsh ========> To configure trust relation between cluster nodes
mmlsdisk <file-system> -d <disk-name> ========> To view the disk information
Page 1005
CRECER INODOS AIX
/usr/lpp/mmfs/samples ========> location of same files created by installing base filesets
mmcrnsd -F /tmp/disk.list ========> To create a nsd disk (/tmp/disk.list file with entries)
mmcrfs <FS-name> -F </tmp/fs.list> -A yes -T <mount-point> ========>To create File system
mmadddisk <FS-name> -F </tmp/fs.list> ========> To add new disk to File system
touch /var/mmfs/etc/ignoreStartupMount ========> To ignore any GPFS filesystem while system is rebooting.
touch /var/mmfs/etc/ignoreStartupMount.<devicename> ========> to do not mount this FS while system boot
Before starting with OS Upgrade all the GPFS file system should be unmounted. If there are any application process running, and those process using the GPFS file systems, we cannot unmount the GPFS file systems.
Page 1006
CRECER INODOS AIX
Page 1007
CRECER INODOS AIX
Page 1008
CRECER INODOS AIX
-d gpfs6nsd;gpfs7nsd;gpfs8nsd;gpfs9nsd;gpfs10nsd;gpfs11nsd;gpfs12nsd;gpfs13nsd;gpfs14nsd;gpfs15nsd;gpfs16nsd;gpfs17nsd;gpfs1
gpfs23nsd;gpfs24nsd;gpfs25nsd;gpfs26nsd;gpfs27nsd;gpfs28nsd;gpfs29nsd;gpfs30nsd;gpfs31nsd;gpfs32nsd;gpfs33nsd;gpfs34nsd;g
gpfs40nsd;gpfs41nsd;gpfs42nsd;gpfs43nsd;gpfs44nsd;gpfs45nsd;gpfs46nsd;gpfs47nsd;gpfs48nsd;gpfs49nsd;gpfs50nsd;gpfs51nsd;g
gpfs57nsd;gpfs58nsd;gpfs59nsd;gpfs60nsd;gpfs61nsd;gpfs62nsd;gpfs63nsd;gpfs64nsd;gpfs65nsd;gpfs66nsd;gpfs67nsd;gpfs68nsd;g
Page 1009
CRECER INODOS AIX
# mmlsmount all =======> View the gpfs filesystem mounted on number of nodes
Wed May 11 00:08:22 CDT 2011: 6027-1341 mmshutdown: Starting force unmount of GPFS file systems
Page 1010
CRECER INODOS AIX
test1-gpfs: Wed May 11 00:09:28.424 2011: Reason for shutdown: mmfsadm shutdown command timed out
test1-gpfs: Wed May 11 00:09:28 CDT 2011: mmcommon mmfsdown invoked. Subsystem: mmfs Status: down
test1-gpfs: Wed May 11 00:09:28 CDT 2011: 6027-1674 mmcommon: Unmounting file systems ...
# /mnt/gpfs/3.3/3.3.0.12 ======> Change dir to the GPFS new version filesets location
# smitty update _all ======> Use update_all cmd to update the file sets do preview only
COMMIT software updates? no =====> Select no for COMMIT filesets
ACCEPT new license agreements? yes =====> Accept new licence agreement
If everything is fine in PREVIEW stage, proceed with upgrading the GPFS filesets bye selecting PREVIEW as no
Page 1011
CRECER INODOS AIX
# mmgetstate -a ======> Check the GPFS cluster state on all nodes.
# mmlsmount all ======> Check the file systems are mounted on all nodes.
Page 1012
CRECER INODOS AIX
# mmlsconfig =======> Verify the GPFS cluster configuration information.
Page 1013
CRECER INODOS AIX
Page 1014
CRECER INODOS AIX
Before starting with OS Upgrade all the GPFS file system should be unmounted. If there are any application process running, and those process using the GPFS file systems, we cannot unmount the GPFS file systems.
Page 1015
tabla FILTER
INPUT
OUTPUT
FORWARDING
tabla NAT
PREROUTING
POSTROUTING
OUTPUT
tabla MANGLE
iptables -F : borrado de reglas
iptables -L : listado de reglas que se est?n aplicando
iptables -A : append, a?adir regla
iptables -D : borrar una regla
Ejemplo
Aceptar conexiones al puerto 80 (www) en la tarjeta eth0
Nomenclatura:
Flags mas comunes
Notas:
Iptables consiste basicamente de tres tablas
usado para implementar el firewall. Aqui se produce el filtrado de paquetes.
todo el tr?fico entrante
todo el tr?fico saliente
para enrutar tr?fico a trav?s de nuestro ordenador hacia otro ordenador. Se supone que este tr?fico no es para nosotros
(masquerading) para hacer que otros ordenadores se conecten a trav?s del nuestro a una serie de servicios pero con nuestra ip, pareciendo que esas conexiones vienen de nuestro equipo.
para alterar el tr?fico as? como llegue a nosotros
para alterar paquetes generados localmente antes de enrutarlos
alterar paquetes justo antes de que salgan
sirve para alterar el estado de un paquete. No la comentaremos por ahora
iptables -A INPUT -i eth0 -s 0.0.0.0/0 -p TCP --dport www -j ACCEPT
-A: append, a?adir una regla. OJO, se a?ade al final!!
INPUT: estado del paquete (al entrar es input).
-i eth0: interfaz de red eth0
-s 0.0.0.0/0: direcci?n de acceso (cualquiera en este caso)
-p TCP: tipo de puerto
--dport: puerto de destino
-j ACCEPT: destino del paquete (se acepta, podr? ser DROP, LOG, REJECT, ... )
-s : source address. Ej: -s 192.168.1.0/24
-d : destino. Ej: -d 84.56.73.3
-p : tipo de protocolo (TCP, UDP, ICMP). Ej: -p TCP
--sport : puerto de origen
--dport: puerto de destino
-i = -in-interface : el interfaz por el que se entra (eth0,eth1, ppp0, ... )
-o = --out-interface: el interfaz por el que se sale (eth0,eth1, ppp0, ... )
-i se usa con reglas INPUT y FORWARD
-o se usa con reglas FORWARD y OUTPUT
Iptables consiste basicamente de tres tablas
para enrutar tr?fico a trav?s de nuestro ordenador hacia otro ordenador. Se supone que este tr?fico no es para nosotros
(masquerading) para hacer que otros ordenadores se conecten a trav?s del nuestro a una serie de servicios pero con nuestra ip, pareciendo que esas conexiones vienen de nuestro equipo.
Iptables consiste basicamente de tres tablas
Bug sintoma solucion
Bug 6934597 parche 142900-12
DESCRIPCION
Los componentes mas importantes solaris
bourne again shell
bourne shell
korn shell
C shell
CDE Login Manager
Cuantas estaciones de trabajdo por defecto son disponibles por defecto al inici de sesion
Inodo
ACL
ver el contenido de entradas ACL para un archivo o directorio
-rw-r--r-- 1 userc staff 0 Jan 22 13:40 file1
-rw-r--r--+ 1 userc staff 0 Jan 22 13:40 file2
setfacl -s u::7,g::6,o:4,m:6,u:usera:7 file2
setfacl -m m:rwx file2
setfacl -m u:userb:7 file2
Modifies the existing ACL entry.
Specifies a list of modifications to apply to ACLs for one or more files, directories, or both. See The table for a description of available ACL entries.
Specifies one or more files or directories.
SIGHUP
SIGINT
SIGKILL
SIGTERM
SE APRUEBA EL PRIMER MODULO
Seales
SOLARIS
The kernel, The shell y The directory hierarchy
bash
~/.profile sh
~/.kshrc ksh
~/.cshrc csh
~/.dtprofile
4
Un inodo es una lista de informacin relativa a un objeto determinado (por ejemplo, un archivo, directorio o enlace simblico). La informacin en poder del inodo incluye el tipo de objeto sobre el cual el nodo-i contiene informacin, permisos, informacin sobre la propiedad, y los lugares en los que se almacenan los datos.
getfacl
ACL TRIVIAL La falta del signo +
ACL NO TRIVIAL El signo +
m:7 (mascara 777) al archivo file2
userb (usuario) 7 (permisos)
-m
acl_entry
filename
Hang up Colgar sin tener que teminar reinicia sin terminar la seal
Interrupt Es lo que realiza el Ctrl+C
Kill Mata la seal
Terminate Termina pero muchos lo omiten kill o pkill sin opciones
SE APRUEBA EL PRIMER MODULO
Seales
glosario ingles
the lack of a la falta de un
behavior comportamiento
Un inodo es una lista de informacin relativa a un objeto determinado (por ejemplo, un archivo, directorio o enlace simblico). La informacin en poder del inodo incluye el tipo de objeto sobre el cual el nodo-i contiene informacin, permisos, informacin sobre la propiedad, y los lugares en los que se almacenan los datos.
Colgar sin tener que teminar reinicia sin terminar la seal
SE APRUEBA EL PRIMER MODULO
Un inodo es una lista de informacin relativa a un objeto determinado (por ejemplo, un archivo, directorio o enlace simblico). La informacin en poder del inodo incluye el tipo de objeto sobre el cual el nodo-i contiene informacin, permisos, informacin sobre la propiedad, y los lugares en los que se almacenan los datos.
Sacar snapshot de la XSCF https://support.oracle.com/CSP/ui/flash.html#tab=KBHome%28page=KBHome&id=%28%29%29,%28page=KBNavigator&id=%28bmDocDsrc=KB&bmDocTitle=Gathering%20diagnostic%20data%20for%20Sun%20SPARC%20Enterprise[TM]%20Mx000%20%28OPL%29%20Servers&from=BOOKMARK&viewingMode=1143&bmDocType=HOWTO&bmDocID=1008229.1%29%29
https://support.oracle.com/CSP/ui/flash.html#tab=KBHome%28page=KBHome&id=%28%29%29,%28page=KBNavigator&id=%28bmDocDsrc=KB&bmDocTitle=Gathering%20diagnostic%20data%20for%20Sun%20SPARC%20Enterprise[TM]%20Mx000%20%28OPL%29%20Servers&from=BOOKMARK&viewingMode=1143&bmDocType=HOWTO&bmDocID=1008229.1%29%29
https://support.oracle.com/CSP/ui/flash.html#tab=KBHome%28page=KBHome&id=%28%29%29,%28page=KBNavigator&id=%28bmDocDsrc=KB&bmDocTitle=Gathering%20diagnostic%20data%20for%20Sun%20SPARC%20Enterprise[TM]%20Mx000%20%28OPL%29%20Servers&from=BOOKMARK&viewingMode=1143&bmDocType=HOWTO&bmDocID=1008229.1%29%29
https://support.oracle.com/CSP/ui/flash.html#tab=KBHome%28page=KBHome&id=%28%29%29,%28page=KBNavigator&id=%28bmDocDsrc=KB&bmDocTitle=Gathering%20diagnostic%20data%20for%20Sun%20SPARC%20Enterprise[TM]%20Mx000%20%28OPL%29%20Servers&from=BOOKMARK&viewingMode=1143&bmDocType=HOWTO&bmDocID=1008229.1%29%29
Crecer un FS en caliente REd ha
sudo /usr/sbin/lvextend -l -32 /dev/mapper/VolGroup00-LogVol01
sudo /sbin/resize2fs /dev/mapper/VolGroup00-LogVol01
ext2online
/dev/VolGro
up00/LogVo
l00 EN suse
Page 1028
Crecer un FS en caliente REd ha
La cantidad de Pps que se tenga libres
Page 1029
Red Hat Enterprise Linux ES release 4 (Nahant Update 2)
Red Hat Enterprise Linux Server release 5.5 (Tikanga)
variantes de red hat 3 y 4
RHEL AS (Advanced Server).
RHEL ES (Entry Server).
RHEL WS (Workstation).
RH Desktop.
En RHEL 5 ha cambi el sistema de ediciones antes mencionado y usado en RHEL 3 y 4. As RHEL AS/ES/WS/Desktop han sido sustituidos1 por:
RHEL Advanced Platform (antiguo AS).
RHEL (antiguo ES).
RHEL Desktop with Workstation and Multi-OS option.
RHEL Desktop with Workstation option (antiguo WS).
RHEL Desktop with Multi-OS option.
RHEL Desktop (antiguo Desktop).
En RHEL 6 las ediciones son 8 (6 para servidores)
RHEL for Server
RHEL for HPC Head Node (para Computacin_de_alto_rendimiento)
RHEL for HPC Compute Node
RHEL for IBM System z
RHEL for IBM POWER
RHEL for SAP Business Applications
RHEL Workstation
RHEL Desktop
Relaciones con Fedora Core
RHL 6.2 RHL 6.2E
RHL 7.2 RHEL 2.1
RHL 9 RHEL 3
Fedora Core 3 RHEL 4
Fedora Core 6 RHEL 5
Fedora 12/13 RHEL 6
DESCRIPCION
(media-independent interface status manipulation tool)
para crear un sistema operativo en XEN se debe tener 30 GB 20 para sistema operativo y 10 para machine Virtual
up2date -u
cuando aparecen mensajes de dependencias de kernel se dirige en el directorio /etc/sysconfig/rhn (actualizar kernel)
se copia el archivo up2date (cp /etc/sysconfig/rhn/up2date /etc/sysconfig/rhn/up2date.VIEJO)
se edita el archivo /etc/sysconfig/rhn/up2date y se ubica la linea pkgSkiplist=kernel.. (se borra la parte despues del igual (=kernel...))
PARCHADO SERVIDORES RED HAT 4 (de 4 a 4.9)
se vuelve a enviar el comando up2date -u y se espera que nos diga que finaliz correctamente
OJO CUANDO NO SE PUEDA CONECTAR DESPUES DEL REINICIO REVISAR LAS MAC E INTERFACES (SACAR COPIAS DE LAS CONFIGURACIONES "IFCONFIG", "NETSTAT -NR", "DF -H")
yum update
Cuando se necesite aprovisionar un servidor en vmware tener en cuenta:
en la opcion de vmware configuracion seleccionar VERSION 7
QUITAR el floppy disk en settings manager
Para los servidores linux minimo 25 GB de espacio en disco 30GB lo ideal
Para eliminar una maquina virtual de raiz elegir "DELETED FROM DISK"
ERRORES AL SUSCRIBIR
Cuando se va a instalar un paquete RPM y sale un mensaje como: warning: libc-client-devel-2004g-2.2.1.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
Red hat 5
Red hat 4
INSTALACION RED HAT 5
Cuando se necesite parchar con DVD como repositorio
For Red Hat Enterprise Linux 4
In /etc/sysconfig/rhn/sources, comment out the following line:
This line needs to be commented out otherwise up2date will keep on looking for information using the Red Hat
Next, in the same file, create a line like the following:
dir mydvdrepo /media/cdrom/RedHat/RPMS
Note: The CD/DVD must be mounted and available in the directory /media/cdrom/ and the path must point to the
En RHEL 5 ha cambi el sistema de ediciones antes mencionado y usado en RHEL 3 y 4. As RHEL AS/ES/WS/Desktop han sido sustituidos1 por:
COMANDOS enlace
(mii-tool red hat) - ethtool (versiones avanzadas) http://www.guatewireless.org/os/linux/mii-tool-configurando-manualmente-la-velocidad-del-ethernet/
## comando para parchar servidores RED HAT 4
cuando aparecen mensajes de dependencias de kernel se dirige en el directorio /etc/sysconfig/rhn (actualizar kernel)
se edita el archivo /etc/sysconfig/rhn/up2date y se ubica la linea pkgSkiplist=kernel.. (se borra la parte despues del igual (=kernel...))
PARCHADO SERVIDORES RED HAT 4 (de 4 a 4.9)
OJO CUANDO NO SE PUEDA CONECTAR DESPUES DEL REINICIO REVISAR LAS MAC E INTERFACES (SACAR COPIAS DE LAS CONFIGURACIONES "IFCONFIG", "NETSTAT -NR", "DF -H")
Actualizacion en RED HAT 5
rhn_register solucion
service messagebus restart
An error has occurred: service haldaemon restart
dbus_bindings.DBusException
See /var/log/up2date for more information
Cuando se va a instalar un paquete RPM y sale un mensaje como: warning: libc-client-devel-2004g-2.2.1.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
rpm --import /usr/share/rhn/RPM-GPG-KEY
http://www.ajpdsoft.com/modules.php?name=News&file=article&sid=290
http://www.guatewireless.org/os/linux/mii-tool-configurando-manualmente-la-velocidad-del-ethernet/
Descripcion
Scripts Utiles LINUX
Ver memoria en utilizacion
10 procesos que estan consumiendo mas memoria
proceso que mas consume ram
ver que esta haciendo un proceso
Saber el total del proceso
Leer un archivo sa /var/log/sa
Maximo Se puede agregar unicamente una LUN de 2 Teras
Cuando se aproviona la maquina se debe agregar la ruta de gestion para poder conectarse a ella
Rutas de procedimientos
\\10.112.1.31\getronics\Infraestructura\Servidores\2.ADMINISTRACION de PLATAFORMA\Dcumentacin GT_Servidores ETB\8. ESTANDAR DE ASEGURAMIENTO
Para crrear cuentas se debe quitar el atributo de inmutable mientas tanto
/admin/script/upetb
watch free
ps aux | sort -nrk 4 | head
ps aux | awk '{print $2, $4, $11}' | sort -k2r | head -n 20 /////// ps -e -orss=,args= | sort -b -k1,1n | pr -TW$COLUMNS
pmap -d PID
pmap 14961
sar -f ARCHIVO
Osea si necesito ingresar 10 TERAS almacenamiento debe partir en 5 esa LUN y presentarlo de a 2 Teras cada una
172.18.0.0 10.111.32.1 255.255.0.0 UG 0 0 0 eth2
Documento
GI-SO-LN-ETB-01-Guia de aseguramiento linux.doc
chattr -i /etc/passwd
ntpserver
ps aux | awk '{print $2, $4, $11}' | sort -k2r | head -n 20 /////// ps -e -orss=,args= | sort -b -k1,1n | pr -TW$COLUMNS
Osea si necesito ingresar 10 TERAS almacenamiento debe partir en 5 esa LUN y presentarlo de a 2 Teras cada una
eth2 donde esta la vlan de gestion
/usr/local/nagios Ubicacin donde se encuentra el nagios
/usr/local/nagios/etc
/usr/local/nagios/etc/equipos Para ingresar o eliminar una maquina
/usr/local/nagios/etc/equipos Para ingresar o eliminar una maquina
/usr/local/nagios/bin voy a esta ruta y ejecuto
Lo importante es que no hallan errores warnnigs salen siempre
Por buenas practicas se recomienda copiar los /usr/local/nagios/etc cuando se hagan cambios significativos.
archivo hostsgroups.cfg >> revisar en criticos, virtuales, fisicos
archivo linux.cfg >> se agrega alfabeticamente la sentencia
./nagios -v ../etc/nagios.cfg
Por buenas practicas se recomienda copiar los /usr/local/nagios/etc cuando se hagan cambios significativos.
Por medio de dlpar asignar el dispositivo USB a la particin
Utilizar cfgmgr para detectar los dispositivos USB uno de ellos sera usbms0 usbms1 segun corresponda, para revisar los dispositivos puede utilizar lsdev |grep usb
una vez detectado el disco usbms0 se debe crear una carpeta para utilizar como punto de montaje mkdir /mnt_usb
Ahora se monta el disco con el comando mount -o log=NULL /dev/usbms0 /mnt_usb el disco ya esta formateado con jfs2
para revisar que todo salio bien ejecutar el comando df -g /mnt_usb Allencontraran 495GB disponibles para la copia, esta la pueden utilizar con el comando tradicional cp
Una vez copiados los archivos al disco externo ejecutar el comando de desmontaje umount /mnt_usb
si no es posible el desmontaje utilizar el comando fuser -ux /mnt_usb y fuser -ux /dev/usbms0 para listar los procesos del S.O. que siguen utilizando el disco y proceder a bajarlos con kill -9 <pid>
Utilizar cfgmgr para detectar los dispositivos USB uno de ellos sera usbms0 usbms1 segun corresponda, para revisar los dispositivos puede utilizar lsdev |grep usb
una vez detectado el disco usbms0 se debe crear una carpeta para utilizar como punto de montaje mkdir /mnt_usb
Ahora se monta el disco con el comando mount -o log=NULL /dev/usbms0 /mnt_usb el disco ya esta formateado con jfs2
para revisar que todo salio bien ejecutar el comando df -g /mnt_usb Allencontraran 495GB disponibles para la copia, esta la pueden utilizar con el comando tradicional cp
si no es posible el desmontaje utilizar el comando fuser -ux /mnt_usb y fuser -ux /dev/usbms0 para listar los procesos del S.O. que siguen utilizando el disco y proceder a bajarlos con kill -9 <pid>

Вам также может понравиться