Replacing the coordinator diskgroup in a cluster that is online

Posted on by

You can also replace the coordinator diskgroup using the vxfenswap utility. The following example replaces the coordinator disk group vxfencoorddg with a new disk group vxfendg.

To replace the coordinator diskgroup

  1. Make sure system-to-system communication is functioning properly.
  2. Make sure that the cluster is online.
    # vxfenadm -d
  3. Find the name of the current coordinator diskgroup (typically vxfencoorddg) that is in the /etc/vxfendg file.
    # cat /etc/vxfendg
    vxfencoorddg
  4. Find the alternative disk groups available to replace the current coordinator diskgroup.
    # vxdisk -o alldgs list
    DEVICE TYPE DISK GROUP STATUS
    rhdisk64 auto:cdsdisk – (vxfendg) online
    rhdisk65 auto:cdsdisk – (vxfendg) online
    rhdisk66 auto:cdsdisk – (vxfendg) online
    rhdisk75 auto:cdsdisk – (vxfencoorddg) online
    rhdisk76 auto:cdsdisk – (vxfencoorddg) online
    rhdisk77 auto:cdsdisk – (vxfencoorddg) online
  5. Validate the new disk group for I/O fencing compliance.
    Run the following command:
    # vxfentsthdw -c vxfendg
    vxfentsthdw -c vxfendg
    See Testing the coordinator disk group using vxfentsthdw -c
  6. If the new disk group is not already deported, run the following command to deport the disk group:# vxdg deport vxfendg
  7. Make sure that the /etc/vxfenmode file is updated to specify the correct disk policy.See the Veritas Cluster Server Installation Guide for detailed instructions.
  8. From any node, start the vxfenswap utility. For example, if vxfendg is the new diskgroup that you want to use as the coordinator diskgroup:
    # vxfenswap -g vxfendg [-n]
    The utility performs the following tasks:
    • Backs up the existing /etc/vxfentab file.
    • Creates a test file /etc/vxfentab.test for the diskgroup that is modified on each node of the cluster.
    • Reads the diskgroup you specified in the vxfenwap command and adds the diskgroup to the /etc/vxfentab.test file on each node.
    • Verifies that the serial number of the new disks are identical on all the nodes. The script terminates if the check fails.
    • Verifies that the new disk group can support I/O fencing on each node.
  9. If the disk verification passes, the script reports success and asks if you want to replace the coordinator disk group.
  10. Review the message that the utility displays and confirm that you want to replace the diskgroup. Else skip to step 11.
    Do you wish to commit this change? [y/n] (default: n) y
    If the utility successfully commits, the script moves the /etc/vxfentab.test file to the /etc/vxfentab file.The utility also updates the /etc/vxfendg file with this new diskgroup.
  11. Set the coordinator attribute value as “on” for the new coordinator disk group.
    # vxdg -g vxfendg set coordinator=on
    Set the coordinator attribute value as “off” for the old disk group.# vxdg -g vxfencoorddg set coordinator=off
  12. Verify that the coordinator disk group has changed.
    # cat /etc/vxfendgvxfendg
  13. If you do not want to replace the diskgroup, answer n.
    The vxfenswap utility rolls back the disk replacement operation.

How to migrate volumes to new disk enclosures using Veritas InfoScale and Storage Foundation

Posted on by

https://www.veritas.com/support/en_US/article.100009769
https://www.veritas.com/content/support/en_US/article.100009768.html
https://www.veritas.com/support/en_US/article.100022187
https://www.veritas.com/support/en_US/article.100023745

To limit the risk when using vxevac, the -k argument should be used.

Example:

# /etc/vx/bin/vxevac -g movedg -k hus_1300_1563 alloc=hus_1300_1564

As the “-k” option was specified, the user can use the rollback option to roll back the changes to the initial state.
# /etc/vx/bin/vxevac -g movedg rollback hus_1300_1563

Since the vxevac -k approach adds extra flexibility, the -k approach should be the recommended syntax in production environments and future use.

The user can safely place the vxevac –k operation in the background using &, and bring it to the foreground whenever needed.

Once the vxevac operation has finished, the user can then commit the event on successful completion.

# /etc/vx/bin/vxevac -g movedg commit hus_1300_1563

AIX Dump collection

Posted on by

Check coredump configuration

#sysdumpdev -l (where is the dump directory, full memory dump setting and type of dump)
#sysdumpdev -f require (modify dump from disallow to require)

# sysdumpdev -t traditional (The firmware-assisted dump may be changed to traditional dump with the following command)

# sysdumpdev -t fw-assisted ( switch back to firmware-assisted dump: )



#sysdumpdev -e (the estimated dump size)
Performing manual dump
#sysdumpstart -p (It will hang for sometime and reboot the machine automatically.

#snap -ac (collecting core information file will be here /tmp/ibmsupt/snap.pax.Z)

strace/truss examples

Posted on by

Linux strace sample

/usr/bin/strace -ftT -o /tmp/strace.out  “command”

AIX truss sample

truss -failed -o /tmp/truss.out -p pid

-d A timestamp will be included with each line of output. Time displayed is in seconds relative to the beginning of the trace. The first line of the trace output will show the base time from which the individual time stamps are measured. By default timestamps are not displayed.
-D Delta time is displayed on each line of output. The delta time represents the elapsed time for the LWP that incurred the event since the last reported event incurred by that thread. By default delta times are not displayed.

-f Follows all children created by the fork system call and includes their signals, faults, and system calls in the trace output. Normally, only the first-level command or process is traced. When the -f flag is specified, the process id is included with each line of trace output to show which process executed the system call or received the signal.

-a Displays the parameter strings which are passed in each exec system call.

-i Keeps interruptible sleeping system calls from being displayed. Certain system calls on terminal devices or pipes, such as open and kread, can sleep for indefinite periods and are interruptible. Normally, truss reports such sleeping system calls if they remain asleep for more than one second. The system call is then reported a second time when it completes. The -i flag causes such system calls to be reported only once, upon completion.

-l Display the id (thread id) of the responsible LWP process along with truss output. By default LWP id is not displayed in the output.

VPN 後遠端桌面常常忽然hang住

Posted on by

Temporarily disable them and verify the result.

Try disabling Receive Window Auto-Tuning.

Here is what you need to do:

  1. Go to Start and type cmd.
  2. Right-click on cmd and select “Run as administrator”.
  3. Type: netsh interface tcp set global autotuninglevel=disabled and press Enter.

If you want to to re-enable it:

Type: netsh interface tcp set global autotuninglevel=normal and press Enter.

If this doesn’t help, please post your concerns at Technet forums for further support.

http://social.technet.microsoft.com/Forums/en/w7itpronetworking/threads

Note: Ensure to enable all your security software by now.

Using Install Bundles to simultaneously install or upgrade full releases (base, maintenance, rolling patch), and individual patches

Posted on by
https://sort.veritas.com/public/documents/sfha/6.2/aix/productguides/html/vcs_install/ch20s10.htm

Base + maintenance + patch:

This integration method can be used when you install or upgrade from a lower version to 6.2.1.100.

Enter the following command:

# installmr -base_path <path_to_base> 
-patch_path <path_to_patch>
From the 6.1 or later release, you can add a maximum of five patches using -patch_path <path_to_patch> -patch2_path <path_to_patch> … -patch5_path <path_to_patch>

Disable AMF

Posted on by
https://sort.veritas.com/public/documents/vie/7.1/aix/productguides/html/vcs_admin/ch06s14s08s03.htm

To disable AMF on a system

  • Run the following command:haimfconfig -disable -amf

    check /etc/default/amf
  • AMF_START – Defines the startup behavior for the AMF module after a system reboot or when AMF is attempted to start using the init script. Valid values include:1 – Indicates that AMF is enabled to start up.0 – Indicates that AMF is disabled to start up. (default)
  • AMF_STOP – Defines the shutdown behavior for the AMF module during a system shutdown or when AMF is attempted to stop using the init script. Valid values include:1 – Indicates that AMF is enabled to shut down. (default)0 – Indicates that AMF is disabled to shut down.

dmpdr refresh utility

Posted on by
https://www.veritas.com/support/en_US/article.100039198.html

How to add and remove physical LUNs connected to a server: SOLARIS SPARC

Article: 100039198Last Published: 2019-04-03Ratings:  2 0Product(s): InfoScale & Storage Foundation

Description

When adding and removing physical LUNs that are connected to a server, it is necessary to run many steps. To reduce the complexity surrounding the multi-step Dynamic LUN reconfiguration process, Veritas has created a new non-interactive interface to aid the provisioning and removal of devices.

Solaris DR LUN overview


The sequence related to the removal and addition of LUNs is illustrated below:


Figure 1.0



New Interface

# /usr/lib/vxvm/voladm.d/bin/dmpdr -o refresh

The new enhanced dmpdr tool will only work in connection with Veritas DMP (Dynamic Multi-Pathing). Third-party multi-pathing drivers ( such as MPxIO and EMC PowerPath ) are not supported and will not work with the new interface.

When intentionally removing a LUN from a server, VxVM must be informed prior to any storage activity.

# vxdisk rm <disk-access-name>

The above command informs VxVM that the Veritas disk access (da) name is to be removed from the system. Adding and removing devices must be done at different times and not under the same reconfiguration event. Prior to adding new storage devices, “pre-checks” must be performed to minimize human error.

 

Dmpdr Tool

The enhanced dmpdr tool attempts to make life easier for system and storage administrators, as they no longer require skills in multiple areas.

  • The enhanced DMPDR (Dynamic Reconfiguration) tool has been enhanced and now includes a non-interactive interface to aid the complex LUN reconfiguration process
  • The DMPDR tool attempts to automate and perform the correct sequence of events on the host in the effort to reduce human error without the need for manual intervention
  • The DMPDR tool will try to auto-correct mistakes and refresh the different components in the I/O stack
  • The DMPDR tool will clean-up the OS device handles beneath the underlying DMP managed device and refresh VxVM and DMP

LUN Reconfiguration Process

Removal

Solaris DR removal process


Figure 2.0


The original LUN removal multi-step process has been replaced with 3 steps:

1. vxdisk rm <Veritas-disk-access-name>
2. Storage Array LUN removal commands and activity
3. /usr/lib/vxvm/voladm.d/bin/dmpdr -o refresh



Addition

The original LUN addition multi-step process has been replaced with 2 steps:

1. Storage Array LUN removal commands/activity
2. /usr/lib/vxvm/voladm.d/bin/dmpdr -o refresh


Note: The dmpdr script will create a log file under /var/adm/vx/ for each LUN reconfiguration event.


The enhanced dmpdr tool functionality is generally available with Veritas Volume Manager Public Patch 7.2.0.300 on sort.veritas.com.

Example:
 

vm-sol11_sparc-Patch-7.2.0.300 
https://sort.veritas.com/patch/detail/12971

Veritas Cloud Receiver edgeserver_host for infoscale

Posted on by

If this is pointed to a server it cannot find it will report a message in the logs once a week.

To stop the message:
This command needs to be run locally on node wherever InfoScale 7.4.1 is installed (Veritas Telemetry Collector is running).
/opt/VRTSvlic/tele/bin/TelemetryCollector -tcstop

檢查開機是否會自動啟動.

1.cat /etc/init.d/vrtsvlic (確認檔案不存在)

2.Redhat

systemctl -list-unit-files 檢查vrtsvlic是否enable

systemctl stop vrtsvlic.service

systemctl disable vrtsvlic.service

VMwaredisks agent 需要的權限

Posted on by

that the following privileges should be given to the VMwareDisks resource user:

All Privileges > Datastore > Low level file operations.
All Privileges > Virtual Machine > Configuration > Adding existing disk.
All Privileges > Virtual Machine > Change resource.
All Privileges > Virtual Machine > Configuration > Remove disk.

But one more privilege should be given to the user to resolve this kind of issue:

All Privileges > Virtual Machine > Configuration > Add or remove device.

安裝windows7 sp1失敗,錯誤0x80070490 元素找不到

Posted on by

參考這兩個網址解決的.
http://blogs.technet.com/b/asiasupp/archive/2011/06/20/the-error-0x80070490-element-not-found-when-you-are-installing-a-service-pack-or-update.aspx

http://social.technet.microsoft.com/Forums/windows/en-US/bfb3e5b5-a3bd-4124-b4d6-7fb437ac7b74/windows-7-errornotfound-0x80070490-while-trying-to-install-sp1

不過要注意setupapi.dev.log是在windows\inf目錄下
注意搜尋Failed uninstalling driver updates [HRESULT = 0x80070490 – ERROR_NOT_FOUND]
這個部分會顯示有個inf檔案有問題,這時候開DOS視窗用系統管理員身分.再用pnputil -a 後面加上 inf的檔案名稱
pnputil  -a <Inf File Path>
註冊成功後
就可成功安裝SP1了.

SQL query Application Report with Computer Names in SEPM DB

Posted on by

select  V_sem_computer.ip_addr1_text,         V_sem_computer.computer_name,        V_sem_computer.operation_system,        identity_map.NAME,        computer_application.app_hash,        sem_application.application_name,       sem_application.application_path,       sem_application.app_description, dateadd(s,convert(bigint,computer_application.TIME_STAMP)/1000,’01-01-1970 00:00:00′) TIME_STAMP, sem_application.version,        sem_application.file_size from computer_application WITH (NOLOCK),identity_map WITH (NOLOCK),SEM_APPLICATION WITH (NOLOCK),V_sem_computer WITH (NOLOCK) where  computer_application.group_id = identity_map.id and identity_map.type =  ‘SemClientGroup’ and sem_application.app_hash = computer_application.app_hash and computer_application.computer_id = V_sem_computer.computer_id and (sem_application.application_path like ‘%VanDyke%’ or sem_application.application_path like ‘%mRemote%’)

 

 

“removed was” when issue vxdisk list command

Posted on by

http://www.symantec.com/business/support/index?page=content&id=TECH65099

sun215k#vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
c1t0d0s2     auto:sliced     rootdisk     rootdg       online
c1t1d0s2     auto:sliced     –            –            online
–            –         mirdisk      rootdg       removed was:c1t1d0s2

sun215k#vxprint -qhtg rootdg
dg rootdg       default      default  64000    1226431496.7.sun215k

dm mirdisk      –            –        –        –        REMOVED
dm rootdisk     c1t0d0s2     auto     20351    143328960 –

v  home         –            ENABLED  ACTIVE   62918208 ROUND     –        fsgen
pl home-01      home         ENABLED  ACTIVE   62918208 CONCAT    –        RW
sd rootdisk-03  home-01      rootdisk 80410752 62918208 0         c1t0d0   ENA
pl home-02      home         DISABLED REMOVED  62918208 CONCAT    –        RW
sd mirdisk-03   home-02      mirdisk  62897856 62918208 0         –        RMOV

v  rootvol      –            ENABLED  ACTIVE   20972736 ROUND     –        root
pl rootvol-01   rootvol      ENABLED  ACTIVE   20972736 CONCAT    –        RW
sd rootdisk-02  rootvol-01   rootdisk 59438016 20972736 0         c1t0d0   ENA
pl rootvol-02   rootvol      DISABLED REMOVED  20972736 CONCAT    –        RW
sd mirdisk-02   rootvol-02   mirdisk  41925120 20972736 0         –        RMOV

v  swapvol      –            ENABLED  ACTIVE   41925120 ROUND     –        swap
pl swapvol-01   swapvol      ENABLED  ACTIVE   41925120 CONCAT    –        RW
sd rootdisk-01  swapvol-01   rootdisk 0        41925120 0         c1t0d0   ENA
pl swapvol-02   swapvol      DISABLED REMOVED  41925120 CONCAT    –        RW
sd mirdisk-01   swapvol-02   mirdisk  0        41925120 0         –        RMOV

2. Disassociate all REMOVED plexs via vxplex command

sun215k#vxplex -g rootdg dis home-02
sun215k#vxplex -g rootdg dis rootvol-02
sun215k#vxplex -g rootdg dis swapvol-02

sun215k#vxprint -qhtg rootdg
dg rootdg       default      default  64000    1226431496.7.sun215k

dm mirdisk      –            –        –        –        REMOVED
dm rootdisk     c1t0d0s2     auto     20351    143328960 –

pl home-02      –            DISABLED REMOVED  62918208 CONCAT    –        RW
sd mirdisk-03   home-02      mirdisk  62897856 62918208 0         –        RMOV

pl rootvol-02   –            DISABLED REMOVED  20972736 CONCAT    –        RW
sd mirdisk-02   rootvol-02   mirdisk  41925120 20972736 0         –        RMOV

pl swapvol-02   –            DISABLED REMOVED  41925120 CONCAT    –        RW
sd mirdisk-01   swapvol-02   mirdisk  0        41925120 0         –        RMOV

v  home         –            ENABLED  ACTIVE   62918208 ROUND     –        fsgen
pl home-01      home         ENABLED  ACTIVE   62918208 CONCAT    –        RW
sd rootdisk-03  home-01      rootdisk 80410752 62918208 0         c1t0d0   ENA

v  rootvol      –            ENABLED  ACTIVE   20972736 ROUND     –        root
pl rootvol-01   rootvol      ENABLED  ACTIVE   20972736 CONCAT    –        RW
sd rootdisk-02  rootvol-01   rootdisk 59438016 20972736 0         c1t0d0   ENA

v  swapvol      –            ENABLED  ACTIVE   41925120 ROUND     –        swap
pl swapvol-01   swapvol      ENABLED  ACTIVE   41925120 CONCAT    –        RW
sd rootdisk-01  swapvol-01   rootdisk 0        41925120 0         c1t0d0   ENA

3. Remove plex and disk information via vxedit command

sun215k#vxedit -g rootdg -rf rm home-02 rootvol-02 swapvol-02
sun215k#vxprint -qhtg rootdg
dg rootdg       default      default  64000    1226431496.7.sun215k

dm mirdisk      –            –        –        –        REMOVED
dm rootdisk     c1t0d0s2     auto     20351    143328960 –

v  home         –            ENABLED  ACTIVE   62918208 ROUND     –        fsgen
pl home-01      home         ENABLED  ACTIVE   62918208 CONCAT    –        RW
sd rootdisk-03  home-01      rootdisk 80410752 62918208 0         c1t0d0   ENA

v  rootvol      –            ENABLED  ACTIVE   20972736 ROUND     –        root
pl rootvol-01   rootvol      ENABLED  ACTIVE   20972736 CONCAT    –        RW
sd rootdisk-02  rootvol-01   rootdisk 59438016 20972736 0         c1t0d0   ENA

v  swapvol      –            ENABLED  ACTIVE   41925120 ROUND     –        swap
pl swapvol-01   swapvol      ENABLED  ACTIVE   41925120 CONCAT    –        RW
sd rootdisk-01  swapvol-01   rootdisk 0        41925120 0         c1t0d0   ENA

sun215k#vxedit -g rootdg -rf rm mirdisk

4. Run vxdisksetup

sun215k#vxdisksetup -fi c1t1d0 format=sliced

5. Run prtvtoc command to compare of private and public slice with root disk,it can be seen slice 3 is private and 4 is public for c1t1d0. But slice 3 is public and 4 is private for root disk

sun215k#prtvtoc /dev/dsk/c1t1d0s2
* /dev/dsk/c1t1d0s2 partition map

*           0     10176     10175
*
*                          First     Sector    Last
* Partition  Tag  Flags    Sector     Count    Sector  Mount Directory
      2      5    01          0 143349312 143349311
      3     15    01      10176     10176     20351
      4     14    01      20352 143328960 143349311

sun215k#prtvtoc /dev/dsk/c1t0d0s2
* /dev/dsk/c1t0d0s2 partition map

*                          First     Sector    Last
* Partition  Tag  Flags    Sector     Count    Sector  Mount Directory
      0      2    00   59458368  20972736  80431103
      1      3    01      20352  41925120  41945471
      2      5    00          0 143349312 143349311
      3     14    01      20352 143328960 143349311
      4     15    01          0     20352     20351
      7      8    00   80431104  62918208 143349311

6. Run vxdg command to add mirdisk into rootdg

sun215k#vxdg -g rootdg adddisk mirdisk=c1t1d0s2

7. Run vxmirror command

sun215k#vxmirror -g rootdg rootdisk mirdisk
VxVM vxmirror ERROR V-5-2-3604 No non-redundant volumes to mirror

8.So it needs to be identified private slice is 3 and 4 for public slice

sun215k#vxdisksetup -i c1t1d0 privslice=4 pubslice=3 format=sliced

9.Run vxmirror command again

sun215k#vxmirror -g rootdg rootdisk mirdisk
! vxassist -g rootdg mirror swapvol mirdisk

Cool! It can be seen volume is mirroring via vxtask lis

sun215k#vxtask list
TASKID  PTID TYPE/STATE    PCT   PROGRESS
  161           ATCOPY/R 98.60% 0/41925120/41338880 PLXATT swapvol swapvol-02 rootdg

NOTE:Sometimes disk slices will be changed back to private 3 and public 4 after run vxmirror command even if run command
#vxdisksetup -i c1t1d0 privslice=4 pubslice=3 format=sliced before.
This situation has been seen in this case.
The issue solved after used it to install OS then go back to the steps.