rename volume group AIX

I need to rename appoggiovg volumegroup

root@paul:/#lsvg
hpsanvg
rootvg
oraexpvg
dati2vg
dati3vg
dati4vg
dati5vg
appoggiovg

Appoggiovg is create over hdisk7

I need:

varyoffvg appoggiovg
exportvg appoggiovg

root@paul:/#lspv
hdisk2          00c655c40fab3811                    rootvg          active
hdisk0          00c7662d78e1b21f                    hpsanvg         active
hdisk1          00c655c4d544cca6                    oraexpvg        active
hdisk3          00c655c444918136                    dati2vg         active
hdisk4          00c655c4db40e342                    dati3vg         active
hdisk5          00c655c428a07b90                    dati4vg         active
hdisk6          00c655c428a0de52                    dati5vg         active
hdisk7          00c655c4ae67c723                    None

root@paul:/#importvg -y dati6vg hdisk7

root@paul:/#lspv
hdisk2          00c655c40fab3811                    rootvg          active
hdisk0          00c7662d78e1b21f                    hpsanvg         active
hdisk1          00c655c4d544cca6                    oraexpvg        active
hdisk3          00c655c444918136                    dati2vg         active
hdisk4          00c655c4db40e342                    dati3vg         active
hdisk5          00c655c428a07b90                    dati4vg         active
hdisk6          00c655c428a0de52                    dati5vg         active
hdisk7          00c655c4ae67c723                    dati6vg         active

rename volume group AIX

Integrazione Command View 10.2 con HP SIM 7.2

Monitoraggio EVA 8100 con HP SIM, installazione HP COMMAND VIEW 10.2 e HP System Insight Manager sullo stesso server windows 2008 r2 standard

– Installare prima HP SIM  e poi COMMAND VIEW 10.2  per evitare conflitto di porte tcp

– Verificare post installazione il corretto uso delle porte  tcp WBEM/WMI e SMI-S  (il primo installato con HP SIM e il secondo con il command view)
C: netstat –anb >netstat.txt

TCP 0.0.0.0:5988 0.0.0.0:0 LISTENING 1712 [JavaWrapper.exe]
TCP 0.0.0.0:5989 0.0.0.0:0 LISTENING 460 [WMIServer.exe]
. . . . . . . . .
TCP 0.0.0.0:60000 0.0.0.0:0 LISTENING 1712 [JavaWrapper.exe]

Nel caso evidenziato  :

WBEM/WMI utilizzala porta 5989
SMI-S utilizza le porte 5988 e 60000

aggiungere a : C:Program FilesHPSystems Insight Managerconfig
identificationwbemportlist.xml le righe in BLUE

<?xml version=“1.0” encoding=“UTF-8”?>
<wbemportlist>
               <port id=“5989” protocol=“https”>
                    <cimnamespacelist>
                         <cimnamespace name=“root/cimv2”/>
                         <cimnamespace name=“vmware/esxv2”/>
                         <cimnamespace name=“root/hpq”/>
                   </cimnamespacelist>
                  <interopnamespacelist>
                         <interopnamespace name=“root/pg_interop”/>
                         <interopnamespace name=“root”/>
                         <interopnamespace name=“root/emulex”/>
                         <interopnamespace name=“root/qlogic”/>
                         <interopnamespace name=“root/ibm”/>
                         <interopnamespace name=“root/emc”/>
                         <interopnamespace name=“root/smis/current”/>
                         <interopnamespace name=“root/hitachi/dm51”/>
                         <interopnamespace name=“interop”/>
                         <interopnamespace name=“root/interop”/>
                         <interopnamespace name=“root/switch”/>
                         <interopnamespace name=“root/cimv2”/>
                   </interopnamespacelist>
              </port>
             <port id=“60000” protocol=“https”>
                   <interopnamespacelist>
                         <interopnamespace name=“interop”/>
                  </interopnamespacelist>
             </port>
</wbemportlist>

Salvare il file e e riavviare servizio hp sim
E rilanciare da HP SIM il discovery del server su cui sono installati i componenti command view e hp sim

Maggiori info  qua HP SIM and COMMAND VIEW whitepaper

Integrazione Command View 10.2 con HP SIM 7.2

Enable serial logging from ESXi 5.1

During installation

If an ESXi 5.1 host does not successfully install, serial line logging can be configured when booting the installer using advanced kernel boot-time parameters. This takes effect for the current boot, and does not persist across future reboots.
To enable serial-line logging during installation:

  1. At the Loading ESXi installer screen, press Shift+O.
  2. At the prompt, append the advanced option to specify a serial port after runweasel:

    > runweasel debugLogToSerial=1 logPort=com1

  3. Press Enter to boot.
  4. Logging starts after the first loading progress bar finishes.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2032350

Enable serial logging from ESXi 5.1

Determining driver ESXi 5

~ # esxcfg-scsidevs -a

vmhba38 ahci              link-n/a  sata.vmhba38                            (0:0:31.2) Intel Corporation Patsburg 6 Port SATA AHCI Controller
vmhba39 ahci              link-n/a  sata.vmhba39                            (0:0:31.2) Intel Corporation Patsburg 6 Port SATA AHCI Controller
vmhba0  ahci              link-n/a  sata.vmhba0                             (0:0:31.2) Intel Corporation Patsburg 6 Port SATA AHCI Controller
vmhba1  qla2xxx           link-n/a  fc.20000024ff0aa474:21000024ff0aa474    (0:17:0.0) QLogic Corp ISP2532-based 8Gb Fibre Channel to PCI Express HBA
vmhba2  megaraid_sas      link-n/a  unknown.vmhba2                          (0:22:0.0) LSI / Symbios Logic MegaRAID SAS Fusion Controller
vmhba3  qla2xxx           link-n/a  fc.20000024ff0aa479:21000024ff0aa479    (0:32:0.0) QLogic Corp ISP2532-based 8Gb Fibre Channel to PCI Express HBA
vmhba40 ahci              link-n/a  sata.vmhba40                            (0:0:31.2) Intel Corporation Patsburg 6 Port SATA AHCI Controller
vmhba32 bnx2i             unbound   iscsi.vmhba32                           Broadcom iSCSI Adapter
vmhba33 bnx2i             unbound   iscsi.vmhba33                           Broadcom iSCSI Adapter
vmhba34 bnx2i             unbound   iscsi.vmhba34                           Broadcom iSCSI Adapter
vmhba35 bnx2i             unbound   iscsi.vmhba35                           Broadcom iSCSI Adapter
vmhba36 ahci              link-n/a  sata.vmhba36                            (0:0:31.2) Intel Corporation Patsburg 6 Port SATA AHCI Controller
vmhba37 ahci              link-n/a  sata.vmhba37                            (0:0:31.2) Intel Corporation Patsburg 6 Port SATA AHCI Controller

~ # vmkload_mod -s qla2xxx | grep Version

 Version: Version 902.k1.1-9vmw, Build: 799733, Interface: 9.2 Built on: Aug  1 2012
~ #

Determining driver ESXi 5

Windows 2008 backup to NAS linkstation Buffalo

I have this error when try to backup my windows 2008 whit native  backup software to share over NAS linkstation :

 http://kb.backupassist.com/articles.php?aid=3298

 Need to change the configuration of samba, but the smb.conf is Protected

–  Enable access ssh :
Downalod acp_commander.jar from :

 http://downloads.nas-central.org/TOOLS/ALL_LS_KB_ARM9/ACP_COMMANDER/acp_commander.jar

Test connection to NAS

java -jar acp_commander.jar -t <ip nas> -ip <ip nas> -pw adminpasswordhere -c “ls /”


Change root password

java -jar acp_commander.jar -t <ip nas> -ip <ip nas> -pw adminpasswordhere -c “(echo newrootpass;echo newrootpass)|passwd”

Allow root to login on ssh

java -jar acp_commander.jar -t <ip nas> -ip <ip nas> -pw adminpasswordhere -c “sed -i ‘s/UsePAM yes/UsePAM no/g’ /etc/sshd_config”

java -jar acp_commander.jar -t <ip nas> -ip <ip nas> -pw adminpasswordhere -c “sed -i ‘s/PermitRootLogin no/PermitRootLogin yes/g’ /etc/sshd_config”

Restart ssh service

java -jar acp_commander.jar -t <ip nas> -ip <ip nas> -pw adminpasswordhere -c “/etc/init.d/sshd.sh restart”


Now i need to modify smb.conf

ssh connection to NAS

Edit /etc/init.d/smb.sh 

insert  this line :

sed -i ‘/[global]/a    strict allocate = yes ‘ /etc/samba/smb.conf


after 
/usr/local/sbin/nas_configgen -c samba


Restart samba (/etc/init.d/smb.sh restart) or reboot nas
 



Windows 2008 backup to NAS linkstation Buffalo