小兔猫的夏城站

ENSP virtualbox5.2.44，Wireshark2.6.6版本下载地址

Mon, 23 Dec 2024 12:10:56 +0800

Wireshark官方下载链接

https://www.wireshark.org/download/win32/all-versions/

https://www.wireshark.org/download/win64/all-versions/

https://www.wireshark.org/download/win64/all-versions/Wireshark-pdb-win64-2.6.6.zip

Virtualbox官方下载链接

https://download.virtualbox.org/virtualbox/5.2.44/

https://download.virtualbox.org/virtualbox/5.2.44/VirtualBox-5.2.44-139111-Win.exe

vmware VCSA 校验码

Mon, 13 May 2024 17:52:10 +0800

File Name	Last Updated	SHA2	MD5
VMware vCenter Server Appliance VMware-VCSA-all-8.0.2-23504390.iso(10.48 GB) Build Number: 23504390	Mar 26, 2024 12.00AM	657d8fad61fb4d0a4675dc3a7c44549565011e3b56ad85e5a05aa51bc3c02779	8e114d20da3cd9ac0b0ddda5237fc909	File Name	Last Updated	SHA2	MD5
VMware vCenter Server Appliance Update Bundle VMware-vCenter-Server-Appliance-8.0.2.00300-23504390-updaterepo.zip(7.59 GB) Build Number: 23504390	Mar 26, 2024 12.00AM	10cd93e70bc12d9a6f127fedaa81e6fdd0578858804909cf3066fa51bc77e7c6	31c69204f4e19bce305c53ff958e6c05

8.0 U2C

File Name	Last Updated	SHA2	MD5
VMware vCenter Server Appliance VMware-VCSA-all-8.0.2-23504390.iso(10.48 GB) Build Number: 23504390	Mar 26, 2024 12.00AM	657d8fad61fb4d0a4675dc3a7c44549565011e3b56ad85e5a05aa51bc3c02779	8e114d20da3cd9ac0b0ddda5237fc909
VMware vCenter Server Appliance Update Bundle VMware-vCenter-Server-Appliance-8.0.2.00300-23504390-updaterepo.zip(7.59 GB) Build Number: 23504390	Mar 26, 2024 12.00AM	10cd93e70bc12d9a6f127fedaa81e6fdd0578858804909cf3066fa51bc77e7c6	31c69204f4e19bce305c53ff958e6c05

File Name

Last Updated

SHA2

MD5

VMware vCenter Server Appliance

VMware-VCSA-all-8.0.2-23504390.iso(10.48 GB)

Build Number: 23504390

Mar 26, 2024 12.00AM

657d8fad61fb4d0a4675dc3a7c44549565011e3b56ad85e5a05aa51bc3c02779

8e114d20da3cd9ac0b0ddda5237fc909

VMware vCenter Server Appliance Update Bundle

VMware-vCenter-Server-Appliance-8.0.2.00300-23504390-updaterepo.zip(7.59 GB)

Build Number: 23504390

Mar 26, 2024 12.00AM

10cd93e70bc12d9a6f127fedaa81e6fdd0578858804909cf3066fa51bc77e7c6

31c69204f4e19bce305c53ff958e6c05

8.0 U2b

File Name	Last Updated	SHA2	MD5
VMware vCenter Server Appliance VMware-VCSA-all-8.0.2-23319993.iso(10.47 GB) Build Number: 23319993	Feb 29, 2024 12.00AM	30ed88c6754c8623f892650c7887c83122d4fdc60ab506c5b0a90fd7200141b9	369a89b75913cc71ecb2be1273052676
VMware vCenter Server Appliance Update Bundle VMware-vCenter-Server-Appliance-8.0.2.00200-23319993-updaterepo.zip(7.58 GB) Build Number: 23319993	Feb 29, 2024 12.00AM	46983a39a9fd3ebb457cb658d061d9f716bfecb338f1945d54e194374a3245c7	479943469c15ede1597351ccd3839765

File Name

Last Updated

SHA2

MD5

VMware vCenter Server Appliance

VMware-VCSA-all-8.0.2-23319993.iso(10.47 GB)

Build Number: 23319993

Feb 29, 2024 12.00AM

30ed88c6754c8623f892650c7887c83122d4fdc60ab506c5b0a90fd7200141b9

369a89b75913cc71ecb2be1273052676

VMware vCenter Server Appliance Update Bundle

VMware-vCenter-Server-Appliance-8.0.2.00200-23319993-updaterepo.zip(7.58 GB)

Build Number: 23319993

Feb 29, 2024 12.00AM

46983a39a9fd3ebb457cb658d061d9f716bfecb338f1945d54e194374a3245c7

479943469c15ede1597351ccd3839765

8.0 U2a

File Name	Last Updated	SHA2	MD5
VMware vCenter Server Appliance VMware-VCSA-all-8.0.2-22617221.iso(10.23 GB) Build Number: 22617221	Oct 26, 2023 12.00AM	d2575650be939b41033b197fbda43670ca7120c770b33eb38914a51bbdf8c534	4f58dc3ed18aeed91c6e7953e51a9f79
VMware vCenter Server Appliance Update Bundle VMware-vCenter-Server-Appliance-8.0.2.00100-22617221-updaterepo.zip(7.57 GB) Build Number: 22617221	Oct 26, 2023 12.00AM	bfb0039d40788e0bd2516b35c6406c28957663cac5798e82e92abb5cb732ba5f	6fb83bf321290548def84d097e165c69

File Name

Last Updated

SHA2

MD5

VMware vCenter Server Appliance

VMware-VCSA-all-8.0.2-22617221.iso(10.23 GB)

Build Number: 22617221

Oct 26, 2023 12.00AM

d2575650be939b41033b197fbda43670ca7120c770b33eb38914a51bbdf8c534

4f58dc3ed18aeed91c6e7953e51a9f79

VMware vCenter Server Appliance Update Bundle

VMware-vCenter-Server-Appliance-8.0.2.00100-22617221-updaterepo.zip(7.57 GB)

Build Number: 22617221

Oct 26, 2023 12.00AM

bfb0039d40788e0bd2516b35c6406c28957663cac5798e82e92abb5cb732ba5f

6fb83bf321290548def84d097e165c69

vmware ESXI 8.0校验码

Mon, 13 May 2024 17:32:13 +0800

File Name	Last Updated	SHA2	MD5
VMware vSphere Hypervisor (ESXi) Offline Bundle VMware-ESXi-8.0U2b-23305546-depot.zip(941.86 MB) Build Number: 23305546	Feb 29, 2024 12.00AM	264ebd69044a85fc4ade78ff088f5d4fa9af3cbd23eca241f0855cb7bdeb8258	3c35b9016b95b4885c3544ee395e02dd
VMware vSphere Hypervisor (ESXi ISO) image VMware-VMvisor-Installer-8.0U2b-23305546.x86_64.iso(605.74 MB) Build Number: 23305546	Feb 29, 2024 12.00AM	42557a32b77bf6f66119c80d1055cc042544872672319097dcd98f5a06002527	bc300833a34521e99457116a27dd38dd

File Name

Last Updated

SHA2

MD5

VMware vSphere Hypervisor (ESXi) Offline Bundle

VMware-ESXi-8.0U2b-23305546-depot.zip(941.86 MB)

Build Number: 23305546

Feb 29, 2024 12.00AM

264ebd69044a85fc4ade78ff088f5d4fa9af3cbd23eca241f0855cb7bdeb8258

3c35b9016b95b4885c3544ee395e02dd

VMware vSphere Hypervisor (ESXi ISO) image

VMware-VMvisor-Installer-8.0U2b-23305546.x86_64.iso(605.74 MB)

Build Number: 23305546

Feb 29, 2024 12.00AM

42557a32b77bf6f66119c80d1055cc042544872672319097dcd98f5a06002527

bc300833a34521e99457116a27dd38dd

File Name	Last Updated	SHA2	MD5
VMware vSphere Hypervisor (ESXi) Offline Bundle VMware-ESXi-8.0U2-22380479-depot.zip(587.17 MB) Build Number: 22380479	Jan 03, 2024 12.00AM	76dbd1f0077b20b765c8084e74a5fd012c0c485297f60530e1f9703bdf051b5c	982c6dab9cb2c053e21523ac065bc9ad
VMware vSphere Hypervisor (ESXi ISO) image VMware-VMvisor-Installer-8.0U2-22380479.x86_64.iso(639.97 MB) Build Number: 22380479	Jan 03, 2024 12.00AM	ff062f843be45760b591096fbf7be0b1003f6469db24f2d2e40a4c8ed3d86c21	2403e11fb6d46dd57ba0a6ee0fa1c833

File Name

Last Updated

SHA2

MD5

VMware vSphere Hypervisor (ESXi) Offline Bundle

VMware-ESXi-8.0U2-22380479-depot.zip(587.17 MB)

Build Number: 22380479

Jan 03, 2024 12.00AM

76dbd1f0077b20b765c8084e74a5fd012c0c485297f60530e1f9703bdf051b5c

982c6dab9cb2c053e21523ac065bc9ad

VMware vSphere Hypervisor (ESXi ISO) image

VMware-VMvisor-Installer-8.0U2-22380479.x86_64.iso(639.97 MB)

Build Number: 22380479

Jan 03, 2024 12.00AM

ff062f843be45760b591096fbf7be0b1003f6469db24f2d2e40a4c8ed3d86c21

2403e11fb6d46dd57ba0a6ee0fa1c833

File Name	Last Updated	SHA2	MD5
VMware vSphere Hypervisor (ESXi) Offline Bundle VMware-ESXi-8.0U1a-21813344-depot.zip(556.18 MB) Build Number: 21813344	Jun 01, 2023 12.00AM	52dd56f65367afdc0503419370cee7bf62965940cd9cca3af6b9c2409e615950	c8ff9681df5ba4f26c272564fda34966
VMware vSphere Hypervisor (ESXi ISO) image VMware-VMvisor-Installer-8.0U1a-21813344.x86_64.iso(599.47 MB) Build Number: 21813344	Jun 01, 2023 12.00AM	fe1ba819ce9a84318a4cf39ca0bd273009089f5abf86c49b002f46b05d399514	05768de15c1cf8790af9702c077493e5

File Name

Last Updated

SHA2

MD5

VMware vSphere Hypervisor (ESXi) Offline Bundle

VMware-ESXi-8.0U1a-21813344-depot.zip(556.18 MB)

Build Number: 21813344

Jun 01, 2023 12.00AM

52dd56f65367afdc0503419370cee7bf62965940cd9cca3af6b9c2409e615950

c8ff9681df5ba4f26c272564fda34966

VMware vSphere Hypervisor (ESXi ISO) image

VMware-VMvisor-Installer-8.0U1a-21813344.x86_64.iso(599.47 MB)

Build Number: 21813344

Jun 01, 2023 12.00AM

fe1ba819ce9a84318a4cf39ca0bd273009089f5abf86c49b002f46b05d399514

05768de15c1cf8790af9702c077493e5

File Name	Last Updated	SHA2	MD5
VMware vSphere Hypervisor (ESXi) Offline Bundle VMware-ESXi-8.0U1-21495797-depot.zip(556.48 MB) Build Number: 21495797	Apr 28, 2023 12.00AM	68d9b58c9a00ec63fd899cda1a3d044d1fb0f2ee353bcf9c8e163483977f5d7c	a635841a634a63d05e010a889d091d0e
VMware vSphere Hypervisor (ESXi ISO) image VMware-VMvisor-Installer-8.0U1-21495797.x86_64.iso(599.76 MB) Build Number: 21495797	Apr 28, 2023 12.00AM	2d1b2f00c026df29f1e4b84d8e63f2c841feceeb5bdab65d89a54967e9a6f381	71439b86003fecda9aa04a126812ea99

File Name

Last Updated

SHA2

MD5

VMware vSphere Hypervisor (ESXi) Offline Bundle

VMware-ESXi-8.0U1-21495797-depot.zip(556.48 MB)

Build Number: 21495797

Apr 28, 2023 12.00AM

68d9b58c9a00ec63fd899cda1a3d044d1fb0f2ee353bcf9c8e163483977f5d7c

a635841a634a63d05e010a889d091d0e

VMware vSphere Hypervisor (ESXi ISO) image

VMware-VMvisor-Installer-8.0U1-21495797.x86_64.iso(599.76 MB)

Build Number: 21495797

Apr 28, 2023 12.00AM

2d1b2f00c026df29f1e4b84d8e63f2c841feceeb5bdab65d89a54967e9a6f381

71439b86003fecda9aa04a126812ea99

File Name	Last Updated	SHA2	MD5
VMware vSphere Hypervisor (ESXi) Offline Bundle VMware-ESXi-8.0b-21203435-depot.zip(947.79 MB) Build Number: 21203435	Feb 14, 2023 12.00AM	94c4e8fddaf8da2b127ba891b82fefbad6d672e7ac160477a159f462de29c5b6	3311032dada17653a5b017b3f2f0d3e4
VMware vSphere Hypervisor (ESXi ISO) image VMware-VMvisor-Installer-8.0b-21203435.x86_64.iso(620.61 MB) Build Number: 21203435	Feb 14, 2023 12.00AM	bdcbfc54e769165628f2f46b215a10de895098601a6fd37fc5ce9064ae7f9ce6	3f216edfc132a9606d8e8332d3ae34a6

File Name

Last Updated

SHA2

MD5

VMware vSphere Hypervisor (ESXi) Offline Bundle

VMware-ESXi-8.0b-21203435-depot.zip(947.79 MB)

Build Number: 21203435

Feb 14, 2023 12.00AM

94c4e8fddaf8da2b127ba891b82fefbad6d672e7ac160477a159f462de29c5b6

3311032dada17653a5b017b3f2f0d3e4

VMware vSphere Hypervisor (ESXi ISO) image

VMware-VMvisor-Installer-8.0b-21203435.x86_64.iso(620.61 MB)

Build Number: 21203435

Feb 14, 2023 12.00AM

bdcbfc54e769165628f2f46b215a10de895098601a6fd37fc5ce9064ae7f9ce6

3f216edfc132a9606d8e8332d3ae34a6

File Name	Last Updated	SHA2	MD5
VMware vSphere Hypervisor (ESXi) Offline Bundle VMware-ESXi-8.0-20513097-depot.zip(632.65 MB) Build Number: 20513097	Oct 20, 2022 12.00AM	27b501a74cc7e0975e61670becad613dfe76797ee104e6970d522bde750d10eb	daaa85f7d377e0c97b0d416f906c1d4d
VMware vSphere Hypervisor (ESXi ISO) image VMware-VMvisor-Installer-8.0-20513097.x86_64.iso(619.13 MB) Build Number: 20513097	Oct 20, 2022 12.00AM	78b8ee5613019f8d92da2b74fae674707679379803cb7b01b526747a849138c1	ecfa2f24c2f808c327a8eb83af11272e

File Name

Last Updated

SHA2

MD5

VMware vSphere Hypervisor (ESXi) Offline Bundle

VMware-ESXi-8.0-20513097-depot.zip(632.65 MB)

Build Number: 20513097

Oct 20, 2022 12.00AM

27b501a74cc7e0975e61670becad613dfe76797ee104e6970d522bde750d10eb

daaa85f7d377e0c97b0d416f906c1d4d

VMware vSphere Hypervisor (ESXi ISO) image

VMware-VMvisor-Installer-8.0-20513097.x86_64.iso(619.13 MB)

Build Number: 20513097

Oct 20, 2022 12.00AM

78b8ee5613019f8d92da2b74fae674707679379803cb7b01b526747a849138c1

ecfa2f24c2f808c327a8eb83af11272e

VPLEX：如何拆卸和重新连接mirror（leg）

Fri, 08 Mar 2024 16:16:03 +0800

原文链接：VPLEX：如何拆卸和重新安装镜子（支腿） |Dell 中国

说明

在分离或连接镜像之前，请确保确定正确的支路和群集名称。

Before detaching or attaching a mirror, ensure you identify the correct leg and cluster name.

在阵列上运行数组重新发现，以确保我们看到数组的最新状态
Run an array rediscover on the array to ensure that we are seeing the latest status of the array.

Example:
VPlexcli:/> cd /clusters/cluster-1/storage-elements/storage-arrays/EMC-CLARiiON-APM00111501539/
VPlexcli:/clusters/cluster-1/storage-elements/storage-arrays/EMC-CLARiiON-APM00111501539/> array re-discover

运行 show-use-hierarchy 以确定虚拟卷是否在一致性组中，是否必须将其删除。（不能对一致性组中的虚拟卷进行任何更改）
Run show-use-hierarchy to determine if the virtual-volume is within a consistency-group and must be removed. (No changes can be made on a virtual-volume within a consistency-group)

以下示例表明虚拟卷是一致性组（TEST01）的一部分，必须先删除，然后才能分离坏镜像段：

Example below indicates that the virtual-volume is part of consistency-group (TEST01) and must be removed first before we can detach the bad mirror leg:

VPlexcli:/> show-use-hierarchy /clusters/cluster-1/virtual-volumes/test_DR1_vol_vol
consistency-group: TEST01 (synchronous)
virtual-volume: test_DR1_vol_vol (1G, major-failure, distributed @ cluster-1, unexported)
distributed-device: test_DR1_vol (1G, raid-1, major-failure)
distributed-device-component: local_device_C1_DR1_leg (1G, raid-0, cluster-1)
extent: extent_C1_DR1_leg_1 (1G)
storage-volume: C1_DR1_leg (1G)
logical-unit: VPD83T3:60060160c9c02c00a49a72452eaae811
storage-array: EMC-CLARiiON-APM00111501539
distributed-device-component: local_device_C2_DR1_leg (1G, raid-0, critical-failure, cluster-2)
extent: extent_C2_DR1_leg_1 (1G, critical-failure)
storage-volume: C2_DR1_leg (1G, critical-failure)
logical-unit: VPD83T3:60060160c9c02c00c6243381ffa5e811
storage-array: EMC-CLARiiON-APM00111501539

使用以下命令从一致性组中删除虚拟卷。
Remove the virtual-volume from the consistency group using the below command.

Example:
VPlexcli:/> consistency-group remove-virtual-volumes --consistency-group TEST01 --virtual-volumes test_DR1_vol_vol

Note:

在使用启用了 RecoverPoint 的一致性组时，如果由于虚拟卷位于受 RecoverPoint 保护的一致性组中而无法从一致性组中删除，则必须首先从 RecoverPoint 一致性组中删除该卷，然后删除/销毁任何与该 RecoverPoint 一致性组相关的 R 集，这必须在 RecoverPoint 端完成。从 RecoverPoint 一致性组中删除该卷并且不再与任何 R-Set 关联后，您可以继续从 VPLEX 一致性组中删除该虚拟卷。

When using RecoverPoint enabled consistency-groups, if virtual-volume cannot be removed from consistency-group due to being in a consistency-group protected by RecoverPoint, you must first remove the volume from the RecoverPoint consistency-group within and also remove/destroy any R-sets that are involved with that RecoverPoint consistency-group and this must be done on the RecoverPoint side. After the volume has been removed from the RecoverPoint consistency-group and is no longer associated with any R-Sets, you can continue to remove the virtual-volume from the VPLEX consistency-group.

重新运行 show-use-hierarchy 以确认卷不再位于一致性组中，以便我们可以继续操作。
Rerun show-use-hierarchy to confirm that the volume is no longer in a consistency-group so that we can proceed further.

以下示例表明虚拟卷不再是一致性组（TEST01）的一部分：

Example below indicates that the virtual-volume is no longer part of the consistency-group (TEST01):

VPlexcli:/> show-use-hierarchy /clusters/cluster-1/virtual-volumes/test_DR1_vol_vol
virtual-volume: test_DR1_vol_vol (1G, major-failure, distributed @ cluster-1, unexported)
distributed-device: test_DR1_vol (1G, raid-1, major-failure)
distributed-device-component: local_device_C1_DR1_leg (1G, raid-0, cluster-1)
extent: extent_C1_DR1_leg_1 (1G)
storage-volume: C1_DR1_leg (1G)
logical-unit: VPD83T3:60060160c9c02c00a49a72452eaae811
storage-array: EMC-CLARiiON-APM00111501539
distributed-device-component: local_device_C2_DR1_leg (1G, raid-0, critical-failure, cluster-2)
extent: extent_C2_DR1_leg_1 (1G, critical-failure)
storage-volume: C2_DR1_leg (1G, critical-failure)
logical-unit: VPD83T3:60060160c9c02c00c6243381ffa5e811
storage-array: EMC-CLARiiON-APM00111501539

现在，我们可以使用以下命令从分布式设备（test_DR1_vol）中删除分布式设备组件/镜像支路（local_device_C2_DR1_leg）。如果如下所示成功分离镜像，请转到步骤 7。但是，如果由于错误“无法删除镜像，因为这会导致与现有的失败者设置冲突”而导致分离镜像失败，请转到步骤 6。
We can now remove the distributed-device-component/mirror leg (local_device_C2_DR1_leg) from the distributed-device (test_DR1_vol) by using the below command. If detaching mirror was successful like below, go to step 7. However, if detaching the mirror fails due to error "can't remove mirror as this would lead to conflict with existing loser settings," go to step 6.

Example:
VPlexcli:/> device detach-mirror --device test_DR1_vol --mirror local_device_C2_DR1_leg --discard --force
Detached mirror local_device_C2_DR1_leg.
Mirror local_device_C2_DR1_leg is below /clusters/cluster-2/devices.

关于上述命令拆下坏腿的注意事项：

始终使用标志 --device 在分布式设备级别运行设备分离，然后使用标志 --mirror 指定要分离的分布式设备组件。
使用标志 --discard 以防止在我们正在分离的分布式设备组件/镜像之上自动创建虚拟卷。
使用标志 --force 跳过任何提示。

Notes regarding the above command to detach the bad leg:

Always run the device detach at distributed-device level using the flag --device and then specify the distributed-device-component to detach using the flag --mirror.
Use the flag --discard in order to prevent a virtual-volume to be automatically created on top of the distributed-device-component/mirror which we are detaching.
Use the flag --force to skip any prompts.

如果由于与现有失败者设置冲突而在尝试分离镜像时收到错误，则必须首先更改分离规则集名称，以将对方集群作为获胜者。如果成功拆卸后视镜支腿，则可以跳过此步骤。
If you have received an error when attempting to detach the mirror due to conflicts with existing loser settings, you must first change the detach rule-set-name to have the opposing cluster as the winner. This step can be skipped if detaching the mirror leg was successful.

显示由于失败者设置冲突而收到的错误示例：

Example showing the error received due to conflicting loser settings:

VPlexcli:/> device detach-mirror --device test_DR1_vol --mirror local_device_C2_DR1_leg --discard --force
device detach-mirror: Evaluation of <<device detach-mirror --device test_DR1_vol --mirror local_device_C2_DR1_leg --discard --force>> failed.
cause: Unable to detach 'local_device_C2_DR1_leg' from device 'test_DR1_vol.
cause: Unable to detach mirror 'local_device_C2_DR1_leg' from distributed Device 'test_DR1_vol'.
cause: Can't remove the mirror, as this would lead to a conflict with the existing loser settings.

若要绕过冲突的失败者设置，首先必须将分布式设备规则集设置为将另一条腿作为获胜者。

To bypass the conflicting loser settings, you first must set the distributed-device rule-set to have the opposite leg as winner.

如何检查当前 rule-set-name 属性的示例：

Example on how to check the current rule-set-name attribute:

VPlexcli:/> cd /distributed-storage/distributed-devices/test_DR1_vol/
VPlexcli:/distributed-storage/distributed-devices/test_DR1_vol> ll

Attributes:
Name Value
---------------------- ----------------------
application-consistent false
auto-resume true
block-count 262144
block-size 4K
capacity 1G
clusters-involved [cluster-1, cluster-2]
consistency-group -
geometry raid-1
health-indications []
health-state ok
locality distributed
operational-status ok
rebuild-allowed true
rebuild-eta -
rebuild-progress -
rebuild-status done
rebuild-type full
rule-set-name cluster-2-detaches <--
service-status running
storage-array-family clariion
stripe-depth -
system-id test_DR1_vol
thin-capable true
transfer-size 128K
virtual-volume test_DR1_vol_vol

Contexts:
Name Description
----------------------------- ------------------------------------------------
at-cluster Contains cluster-specific information on the
enclosing distributed-device.
distributed-device-components Contains information about one cluster-local leg
of the enclosing distributed-device.

如何将 rule-set-name 属性设置为相反集群的示例：

Example on how to set the rule-set-name attribute to the opposite cluster:

VPlexcli:/distributed-storage/distributed-devices/test_DR1_vol> set rule-set-name cluster-1-detaches
VPlexcli:/distributed-storage/distributed-devices/test_DR1_vol> ll

Attributes:
Name Value
---------------------- ----------------------
application-consistent false
auto-resume true
block-count 262144
block-size 4K
capacity 1G
clusters-involved [cluster-1, cluster-2]
consistency-group -
geometry raid-1
health-indications []
health-state ok
locality distributed
operational-status ok
rebuild-allowed true
rebuild-eta -
rebuild-progress -
rebuild-status done
rebuild-type full
rule-set-name cluster-1-detaches <--
service-status running
storage-array-family clariion
stripe-depth -
system-id test_DR1_vol
thin-capable true
transfer-size 128K
virtual-volume test_DR1_vol_vol

Contexts:
Name Description
----------------------------- ------------------------------------------------
at-cluster Contains cluster-specific information on the
enclosing distributed-device.
distributed-device-components Contains information about one cluster-local leg
of the enclosing distributed-device.

现在，您可以分离镜像支路，而不会出现失败者设置冲突的错误。

Now you can detach the mirror leg without the error for conflicting loser settings.

VPlexcli:/> device detach-mirror --device test_DR1_vol --mirror local_device_C2_DR1_leg --discard --force
Detached mirror local_device_C2_DR1_leg.
Mirror local_device_C2_DR1_leg is below /clusters/cluster-2/devices.

重新运行 show-use-hierarchy 以验证是否已成功删除 distributed-device-component/mirror。
Rerun show-use-hierarchy to verify that the distributed-device-component/mirror has been removed successfully.

以下示例表明我们不再看到 distributed-device-component （local_device_C2_DR1_leg）附加：

Example below indicates that we no longer see distributed-device-component (local_device_C2_DR1_leg) attached any longer:

VPlexcli:/> show-use-hierarchy /clusters/cluster-1/virtual-volumes/test_DR1_vol_vol
virtual-volume: test_DR1_vol_vol (1G, distributed @ cluster-1, unexported)
distributed-device: test_DR1_vol (1G, raid-1)
distributed-device-component: local_device_C1_DR1_leg (1G, raid-0, cluster-1)
extent: extent_C1_DR1_leg_1 (1G)
storage-volume: C1_DR1_leg (1G)
logical-unit: VPD83T3:60060160c9c02c00a49a72452eaae811
storage-array: EMC-CLARiiON-APM00111501539

现在，我们可以将之前分离的支路再次重新连接到分布式设备（这将自动触发完全重建）。We can now reattach the previously detached leg again to the distributed-device (this will automatically trigger a full rebuild).

Example:
VPlexcli:/> device attach-mirror --device test_DR1_vol --mirror local_device_C2_DR1_leg

有关此步骤的说明：

Note regarding this step:

连接镜像支路会触发完全重建。始终使用标志 --device 在分布式设备级别运行设备附加，然后使用标志 --mirror 指定要附加的分布式设备组件。

Attaching the mirror leg triggers a full rebuild. Always run the device attach at the distributed-device level using the flag --device and then specify the distributed-device-component to attach using the flag --mirror.

重新运行 show-use-hierarchy 以验证分布式设备组件/镜像是否已成功重新连接。
Rerun show-use-hierarchy to verify that the distributed-device-component/mirror has been reattached successfully.

以下示例表明分布式设备组件（local_device_C2_DR1_leg）现在已重新连接到分布式设备（test_DR1_vol）。

Example below indicates that the distributed-device-component (local_device_C2_DR1_leg) is now reattached to the distributed-device (test_DR1_vol).

VPlexcli:/> show-use-hierarchy /clusters/cluster-1/virtual-volumes/test_DR1_vol_vol
virtual-volume: test_DR1_vol_vol (1G, minor-failure, distributed @ cluster-1, unexported)
distributed-device: test_DR1_vol (1G, raid-1, minor-failure)
distributed-device-component: local_device_C1_DR1_leg (1G, raid-0, cluster-1)
extent: extent_C1_DR1_leg_1 (1G)
storage-volume: C1_DR1_leg (1G)
logical-unit: VPD83T3:60060160c9c02c00a49a72452eaae811
storage-array: EMC-CLARiiON-APM00111501539
distributed-device-component: local_device_C2_DR1_leg (1G, raid-0, critical-failure, cluster-2)

extent: extent_C2_DR1_leg_1 (1G, critical-failure)严重故障

storage-volume: C2_DR1_leg (1G, critical-failure)

logical-unit: VPD83T3:60060160c9c02c00c6243381ffa5e811
storage-array: EMC-CLARiiON-APM00111501539

有关此步骤的说明：

Note regarding this step:

虚拟卷显示轻微故障状态，预计会看到“由于在严重故障段上发生的重建”。重建完成后，状态将更改。

The virtual-volume is showing minor-failure status is expected to be seen due to rebuilds occurring on the critical-failure leg. Once rebuilds have finished, the status changes.

检查重建状态。此输出显示重新生成完成的时间长度、完成的百分比和吞吐量值（M/s）。
Check the rebuild status. The output from this displays the length of time for the rebuild to complete, the percentage finished, and the throughput value (M/s).

Example:
VPlexcli:/> rebuild status
[1] storage_volumes marked for rebuild

Global rebuilds:
device rebuild type rebuilder director rebuilt/total percent finished throughput ETA
-------------------- ------------ ------------------ ------------- ---------------- ---------- ----------
C2_DR1_leg full s2_1ce9_spa 0.5G/1G 50.00% 87.5M/s 8.0hr

Local rebuilds:
No active local rebuilds.

将虚拟卷重新添加回原始一致性组，如下所示。
Readd the virtual-volume back to the original consistency-group like below.

Example:
VPlexcli:/> consistency-group add-virtual-volumes --consistency-group TEST01 --virtual-volumes test_DR1_vol_vol

重建完成后，最后一次运行 show-use-hierarchy，以确认两个镜像支路再次正常运行。（正常运行的卷不会输出次要故障、重大故障或严重故障。)
Run show-use-hierarchy one last time once rebuilds have finished to confirm that both mirror legs are healthy once again. (Healthy volumes will not output minor-failure, major-failure, or critical-failure.)

Example:
VPlexcli:/> show-use-hierarchy /clusters/cluster-1/virtual-volumes/test_DR1_vol_vol
consistency-group: TEST01 (synchronous)
virtual-volume: test_DR1_vol_vol (1G, distributed @ cluster-1, unexported)
distributed-device: test_DR1_vol (1G, raid-1)
distributed-device-component: local_device_C1_DR1_leg (1G, raid-0, cluster-1)
extent: extent_C1_DR1_leg_1 (1G)
storage-volume: C1_DR1_leg (1G)
logical-unit: VPD83T3:60060160c9c02c00a49a72452eaae811
storage-array: EMC-CLARiiON-APM00111501539
distributed-device-component: local_device_C2_DR1_leg (1G, raid-0, cluster-2)
extent: extent_C2_DR1_leg_1 (1G)
storage-volume: C2_DR1_leg (1G)
logical-unit: VPD83T3:60060160c9c02c00c6243381ffa5e811
storage-array: EMC-CLARiiON-APM00111501539

备注：

查看rebuild状态：
rebuild status
对rebuild进行暂停和继续同步的操作。
注意，需要进入到device的目录下，比如要对LUN009操作，则需要执行以下命令：
VPlexcli:/clusters/cluster-1/devices> cd device_CLARiiON0017_LUN_00009_1/
VPlexcli:/clusters/cluster-1/devices/device_CLARiiON0017_LUN_00009_1>
暂停rebuild：
VPlexcli:/clusters/cluster-1/devices/device_CLARiiON0017_LUN_00009_1> set rebuild-allowed false
恢复rebuild

VPlexcli:/clusters/cluster-1/devices/device_CLARiiON0017_LUN_00009_1> set rebuild-allowed true

VPLEX mirror 移除一个节点

Fri, 08 Mar 2024 14:34:32 +0800

转自DELL官网：‎VPLEX-Local怎么移除已经做了Mirror的Virtual Volume中的一个Device？ | DELL Technologies

问：VPLEX-Local怎么移除已经做了Mirror的Virtual Volume中的一个Device？

其实就是把其中一个leg断了，并且在不影响应用的情况下

答：

第一步：你需要知道哪个device与哪个device做了Local Mirror如下：

VPlexcli:/clusters/cluster-1/devices> ll device_CX_LUN8_512M_DBSrv09_10_G_1/components/

/clusters/cluster-1/devices/device_CX_LUN8_512M_DBSrv09_10_G_1/components:

Name Slot Type Operational Health Capacity

-------------------------------------------------- Number ------------ Status State --------

-------------------------------------------------- ------ ------------ ----------- ------ --------

device_CX_LUN8_512M_DBSrv09_10_G_12014Feb18_001747 0 local-device ok ok 512M

device_VNX_LUN8_512M_DBSrv09_10_G_1 1 local-device ok ok 512M

第二步：你需要知道你要断掉哪条腿。这里的命令指的是哪个slot。

下面的例子是要断掉slot 0上面的这条腿

VPlexcli:/clusters/cluster-1/devices> device detach-mirror -s 0 -i -f -d device_CX_LUN8_512M_DBSrv09_10_G_1

第三步：确认你断的腿对不对。由于当前的device做了Local Mirror，所以top devcie的名字不会变，top device里面的成员将是你留下的那条腿

VPlexcli:/clusters/cluster-1/devices> ll device_CX_LUN8_512M_DBSrv09_10_G_1/components/

/clusters/cluster-1/devices/device_CX_LUN8_512M_DBSrv09_10_G_1/components:

Name Slot Type Operational Health Capacity

----------------------------------- Number ------------ Status State --------

----------------------------------- ------ ------------ ----------- ------ --------

device_VNX_LUN8_512M_DBSrv09_10_G_1 0 local-device ok ok 512M

断腿需谨慎。切勿盲目断腿

问：额外问一下，怎么停止正在Local-mirror的过程？

答：好像无法停止Local-mirror。

如果你刚刚开始做Local-Mirror的时候，此时两个device处于rebuilding的状态，此时你是不能执行detach这个动作。只有当两个device执行完rebuild这个动作后才能停止。

如果你做的的是mobility，这个是可以停止的。但是这个动作是用于做后端存储数据迁移使用的。与Local-Mirror应用场景不同。并且两个device做完rebuild后，还可以执行canncel和commit两个动作。第一个动作是对source device做一份副本，当然，只有canncel动作的那个瞬间是数据完全形同。第二个动作是数据直接向destination device写。

备注：

注：命令全格式 device detac-mirror --slot 0 --discard --force --device device_CX_LUN8_512M_DBSrv09_10_G_1

device detach-mirror

[-d | --device ] [context-patch|device-name]

[-m | --mirror] [context-patch|mirror-name]

[-s | --slot] slot-number

[-i | --discard]

[-f | -force]

其中slot-number可使用命令 ll device_CX_LUN8_512M_DBSrv09_10_G_1/components/ 查看

DELL VPLEX 双活配置

Wed, 06 Mar 2024 11:14:11 +0800

注：旧版vplex需要支持flash的浏览器！！新版不需要

一、扫描存储映射给vplex的物理卷

二、将物理卷claim

注：物理卷的名称不能含有特殊字符，参考vplex挂载其他厂家的存储相关命令直接claim并创建extent

创建extent

三、创建device

四、同样创建另外一个device （device_GAD-AIX-9_1）

五、创建mirorr

ssh登录vplex

输入 vplexcli 进入控制台。

VPlexcli:/> ll clusters/cluster-1/devices/

ll clusters/cluster-1/devices/device_AIX-RAC9_1/

rebuilding完成后

vplex页面显示正常

六、创建虚拟卷

七、映射卷

在device处于rebuilding状态时，无法删除device，需要rebuilding完成后才能进行删除。

vplex挂载其他厂家的存储

Wed, 06 Mar 2024 11:02:47 +0800

现象：vplex挂载存储（其他厂家）不会自动生成Name，而是直接调用VPD83 ID作为name，由于VPD83 ID含有冒号“：”，无法进行claim。因此需要使用shell进行重命名并同时进行claim。

命令：

VPlexcli:/> storage-volume claim -n [ 自定义LUN名称 ] -d [ 显示的VPD83 ID]

注： (--appc参数：将该LUN强制定义为源LUN,RAID1只能作为源LUN，显示为data-protected）

admin@ZMWJW-VPLEX-01:~> vplexcli

VPlexcli:/> storage-volume claim -n HDS1-VM-02 -d VPD83T3:60060e80124f190050404f1900000002 --appc

VPlexcli:/> storage-volume claim -n AIX-RAC9 -d VPD83T3:60060e80125b370050405b370000000d

VPlexcli:/> ll clusters/cluster-1/storage-elements/storage-volumes/

VPlexcli:/> ll clusters/cluster-1/devices/

AIX oracle RAC运维命令

Wed, 06 Mar 2024 02:42:32 +0800

Oracle RAC 运行状态查询

以下命令以grid用户执行

查看RAC集群运行状态

zdb1:/home/grid>crs_stat -t

Name Type Target State Host

------------------------------------------------------------

ora.ARCH.dg ora....up.type ONLINE ONLINE zdb1

ora.DATA.dg ora....up.type ONLINE ONLINE zdb1

ora....ER.lsnr ora....er.type ONLINE ONLINE zdb1

ora....N1.lsnr ora....er.type ONLINE ONLINE zdb1

ora....VOTE.dg ora....up.type ONLINE ONLINE zdb1

ora.asm ora.asm.type ONLINE ONLINE zdb1

ora.cvu ora.cvu.type ONLINE ONLINE zdb1

ora.gsd ora.gsd.type OFFLINE OFFLINE

ora....network ora....rk.type ONLINE ONLINE zdb1

ora.oc4j ora.oc4j.type ONLINE ONLINE zdb1

ora.ons ora.ons.type ONLINE ONLINE zdb1

ora....ry.acfs ora....fs.type ONLINE ONLINE zdb1

ora.scan1.vip ora....ip.type ONLINE ONLINE zdb1

ora.zdb.db ora....se.type ONLINE ONLINE zdb1

ora....SM1.asm application ONLINE ONLINE zdb1

ora....B1.lsnr application ONLINE ONLINE zdb1

ora.zdb1.gsd application OFFLINE OFFLINE

ora.zdb1.ons application ONLINE ONLINE zdb1

ora.zdb1.vip ora....t1.type ONLINE ONLINE zdb1

ora....SM2.asm application ONLINE ONLINE zdb2

ora....B2.lsnr application ONLINE ONLINE zdb2

ora.zdb2.gsd application OFFLINE OFFLINE

ora.zdb2.ons application ONLINE ONLINE zdb2

ora.zdb2.vip ora....t1.type ONLINE ONLINE zdb2

zdb1:/home/grid>

查看RAC数据库运行状态

zdb1:/home/grid>srvctl status database -d zdb

Instance zdb1 is running on node zdb1

Instance zdb2 is running on node zdb2

zdb1:/home/grid>

3、查看RAC注册表磁盘状态

[grid@zdb1 ~]$ ocrcheck

zdb1:/home/grid>ocrcheck

Status of Oracle Cluster Registry is as follows :

Version : 3

Total space (kbytes) : 262120

Used space (kbytes) : 3100

Available space (kbytes) : 259020

ID : 436901300

Device/File Name : +OCR_VOTE

Device/File integrity check succeeded

Device/File not configured

Cluster registry integrity check succeeded

Logical corruption check bypassed due to non-privileged user

zdb1:/home/grid>

4、查看RAC仲裁盘状态

zdb1:/home/grid>crsctl query css votedisk

## STATE File Universal Id File Name Disk group

-- ----- ----------------- --------- ---------

1. ONLINE 1a4419e58a2e4fd8bfddd85d0ea16b5b (/dev/rhdisk10) [OCR_VOTE]

2. ONLINE 1f30dc1eb6b74f59bf78c98e5cb611f5 (/dev/rhdisk8) [OCR_VOTE]

3. ONLINE 8487c76c2f864f82bf5530f41b9fe31d (/dev/rhdisk9) [OCR_VOTE]

Located 3 voting disk(s).

zdb1:/home/grid>

5、查看监听运行状态

zdb1:/home/grid>lsnrctl status

LSNRCTL for IBM/AIX RISC System/6000: Version 11.2.0.4.0 - Production on 21-SEP-2015 16:20:05

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER)))

STATUS of the LISTENER

------------------------

Alias LISTENER

Version TNSLSNR for IBM/AIX RISC System/6000: Version 11.2.0.4.0 - Production

Start Date 18-SEP-2015 18:21:21

Uptime 2 days 21 hr. 58 min. 44 sec

Trace Level off

Security ON: Local OS Authentication

SNMP ON

Listener Parameter File /u01/app/11.2.0/grid/network/admin/listener.ora

Listener Log File /u01/app/grid/diag/tnslsnr/zdb1/listener/alert/log.xml

Listening Endpoints Summary...

(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENER)))

(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.1.150)(PORT=1521)))

(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.1.152)(PORT=1521)))

Services Summary...

Service "+ASM" has 1 instance(s).

Instance "+ASM1", status READY, has 1 handler(s) for this service...

Service "zdb" has 1 instance(s).

Instance "zdb1", status READY, has 1 handler(s) for this service...

Service "zdbXDB" has 1 instance(s).

Instance "zdb1", status READY, has 1 handler(s) for this service...

The command completed successfully

三、Oracle RAC 启动与关闭

在Oracle 11gR2 下的RAC，架构发生了变化。CRS的信息也是放在ASM 实例里的，所以要关asm必须关闭crs。如果还使用了acfs的话，一关crs那么acfs里的信息也不能访问了，所以一般不重启机器，不轻易关crs, 其他的service可以根据自己的需要去stop/start。注意：11g RAC 开启资源相对比较慢(即使命令后面显示的资源都start succeeded,通过crs_stat -t查看都不一定online), 需要耐心并查看log。

Oracle RAC关闭

关闭数据库：

这个和以前是一样的，还是以grid用户执行srvctl命令：

zdb1:/home/grid> srvctl stop database -d zdb （关闭所有节点）

zdb1:/home/grid> srvctl stop database -d -i zmd1 （关闭单示例）

然后查看状态：

zdb1:/home/grid> srvctl status database -d zdb

Instance zdb1 is not running on node zdb1

Instance zdb2 is not running on node zdb2

2、停止节点集群服务，必须以root用户：

zdb1:/home/grid># cd /u01/app/11.2.0/grid/bin/

zdb1:/home/grid>./crsctl stop cluster -all ----停止所有节点服务

Oracle RAC启动

情况一：重启两节点服务器

1、crs集群启动

重启服务器crs集群会自动启动，但是启动过程较慢，需要几分钟时间

通过crs_stat -t 命令查看crs集群启动是否成功。

2、数据库启动

数据库需要手动启动

zdb1:/home/grid> srvctl start database -d zdb

然后查看状态：

zdb1:/home/grid>srvctl status database -d zdb

Instance zdb1 is running on node zdb1

Instance zdb2 is running on node zdb2

情况二：服务器未重启

1、启动节点集群服务，必须以root用户：

zdb1:/home/grid> cd /u01/app/11.2.0/grid/bin/

zdb1:/home/grid> ./crsctl start cluster -all ----启动所有节点服务

启动数据库：

以grid用户执行srvctl命令：

zdb1:/home/grid>srvctl start database -d zdb

然后查看状态：

zdb1:/home/grid> srvctl status database -d zdb

Instance zdb1 is running on node zdb1

Instance zdb2 is running on node zdb2

注：两个节点zdb1和zdb2的root用户下，共有四个脚本。oracle_start.sh和oracle_stop.sh为数据库的启停脚本，crs_start.sh和crs_stop.sh为crs集群启停脚本。可以root用户下执行脚本即可。

四、日志查看

1、RAC集群日志查看

RAC集群日志位置：

/opt/crs/log

重点查看alert*.log、ocssd.log、crsd.log

RAC数据库日志查看

实例zdb1

/u01/app/oracle/diag/rdbms/zdb/zdb1/trace/alert.log

实例zdb2

/u01/app/oracle/diag/rdbms/zdb/zdb2/trace/alert.log

操作系统日志

errpt -a

集群环境下_超详细的Oracle集群环境下日志文件的位置和功能说明（转载）

Wed, 06 Mar 2024 02:32:36 +0800

转自:https://blog.csdn.net/weixin_28929201/article/details/112706565

概述

有朋友问到一般Oracle会看哪些日志，单实例的就没啥好讲了，下面主要总结下RAC的一些常用日志及其路径，便于平时排查相关问题。

RAC11G常用日志

1、oracle 下的alert日志

路径：$ORACLE_BASE/diag/rdbms/rfdb/RFDB1/trace/alertRFDB1.log

仅包含本地节点上oracle集群件的跟踪和诊断日志文件。

2、grid 下的 alert 日志

路径：$ORACLE_HOME/log/rfdb1/alertrfdb1.log

仅包含ASM的跟踪和诊断日志文件。

3、css的日志

$ORACLE_HOME/log/rfdb1/cssd/ocssd.log

包含CSS日志，其中包括来自客户端CSS侦听器的操作，系统会对该日志每20M进行归档一次。

4、crs的日志

路径：$ORACLE_HOME/log/rfdb1/crsd/crsd.log

包含CRSD守护进程的跟踪和调试日志,系统会对该日志每10M进行归档一次。

5、ohas的日志

路径：$ORACLE_HOME/log/rfdb1/ohasd/ohasd.log

OHAS是服务器启动后打开的第一个Grid Infrastructure组件。它被配置为以init(1)打开，并负责生成agent进程。

6、evm的日志

路径：$ORACLE_HOME/log/rfdb1/evmd/evmd.log

包含EVM守护进程的跟踪和诊断日志文件。

总结

alert.log不说，大家都懂得，crsd、cssd、evmd这三个目录分别对应crs三个进程的日志，熟悉Oracle集群环境下日志文件的位置和功能有助于我们快速定位故障的位置，还是需要记住的。

oracle 常见日志路径

Wed, 06 Mar 2024 02:29:05 +0800

集群启动日志：

zdb2:[/u01/app/11.2.0.4/grid/diag/rdbms/zdb/zdb2/trace]$ls

alert_zdb2.log zdb2_lms2_14418104.trc zdb2_ora_52363342.trc zdb2_p030_18743368.trc

数据库启动日志：

zdb2:[/u01/app/oracle/diag/rdbms/zdb/zdb2/trace]$ls

alert_zdb2.log zdb2_lms2_14418104.trc zdb2_ora_52363342.trc zdb2_p030_18743368.trc

1.集群相关日志主要放在$ORACLE_CRS_HOME/log,$ORACLE_HOME/log中。

$ORACLE_CRS_HOME/log目录下内容如下

[oracle@rac1 log]$ pwd
/u01/app/11.2.0/11ggrid/log
[oracle@rac1 log]$ ls
crs/ diag/ rac1/
[oracle@rac1 log]$

$ORACLE_HOME/log内容如下
[oracle@rac1 log]$ cd $ORACLE_HOME
[oracle@rac1 dbhome_1]$ cd log
[oracle@rac1 log]$ pwd
/u01/app/oracle/product/11.2.0/dbhome_1/log
[oracle@rac1 log]$ ls
diag/ rac1/
[oracle@rac1 log]$

2.具体日志与目录的对应说明

CRS日志存放在$ORACLE_CRS_HOME/log/HOSTNAME/crsd下

[oracle@rac1 crsd]$ pwd
/u01/app/11.2.0/11ggrid/log/rac1/crsd
[oracle@rac1 crsd]$ ll
total 6212
-rw-r--r-- 1 root root 6338257 Sep 21 22:24 crsd.log
-rw-r--r-- 1 root root     812 Sep 7 00:06 crsdOUT.log
-rw-r--r-- 1 root root     114 Aug 7 20:10 crsd.trc
[oracle@rac1 crsd]$ tail -10 crsd.log
        TextMessage[rac1]
        WAIT:
        TextMessage[0]
]
2012-09-21 22:24:01.928: [UiServer][2604460944] Container [ Name: UI_DATA
        RESULT:
        TextMessage[223]
]
2012-09-21 22:24:01.928: [UiServer][2604460944] Done for ctx=0xc605e68
2012-09-21 22:24:01.937: [ CRSCCL][2648554384]clscsend completed:msgTag= 0xcccccccc version= 0 msgType= 0 msgId= 130 msglen = 991 clschdr.size_clscmsgh= 1079 src= (1, 4294366130) dest= (2, 4294385480)
[oracle@rac1 crsd]$

CSS日志存放在“$ORA_CRS_HOME/log//cssd”目录
[oracle@rac1 cssd]$ pwd
/u01/app/11.2.0/11ggrid/log/rac1/cssd
[oracle@rac1 cssd]$ ls
cssdOUT.log ocssd.l01 ocssd.l02 ocssd.l03 ocssd.l04 ocssd.log ocssd.trc
[oracle@rac1 cssd]$ more cssdOUT.log
08/07/12 20:08:56: CSSD starting
08/07/12 20:11:08: CSSD starting
08/15/12 23:23:27: CSSD starting
08/17/12 19:48:02: CSSD handling signal 15
08/17/12 19:48:02: CSSD killed
08/17/12 19:50:12: CSSD starting
08/17/12 22:42:00: CSSD handling signal 15
08/17/12 22:42:00: CSSD killed
08/17/12 22:44:22: CSSD starting
08/18/12 22:17:57: CSSD handling signal 15
08/18/12 22:17:57: CSSD killed
08/18/12 22:20:10: CSSD starting
09/07/12 00:05:14: CSSD starting
[oracle@rac1 cssd]$

EVM日志存放在“$ORA_CRS_HOME/log//evmd”目录

[oracle@rac1 evmd]$ pwd
/u01/app/11.2.0/11ggrid/log/rac1/evmd
[oracle@rac1 evmd]$ ls
evmd.log evmdOUT.log evmd.trc
[oracle@rac1 evmd]$ more evmd.log
Oracle Database 11g Clusterware Release 11.2.0.1.0 - Production Copyright 1996, 2009
Oracle. All rights reserved.
[ clsdmt][3046398864]Listening to (ADDRESS=(PROTOCOL=ipc)(KEY=rac1DBG_EVMD))
2012-08-07 20:12:17.831: [ clsdmt][3046398864]PID for the Process [19602], connkey
2
2012-08-07 20:12:17.839: [ clsdmt][3046398864]Creating PID [19602] file for home /u
01/app/11.2.0/11ggrid host rac1 bin evm to /u01/app/11.2.0/11ggrid/evm/init/
2012-08-07 20:12:17.865: [ clsdmt][3046398864]Writing PID [19602] to the file [/u01
/app/11.2.0/11ggrid/evm/init/rac1.pid]
2012-08-07 20:12:18.302: [ default][3046692560] ENV Logging level for Module: CLSVER
0
2012-08-07 20:12:18.302: [ default][3046692560] ENV Logging level for Module: CLUCLS
0
2012-08-07 20:12:18.302: [ default][3046692560] ENV Logging level for Module: COMMCR
S 0
2012-08-07 20:12:18.302: [ default][3046692560] ENV Logging level for Module: COMMNS
0
2012-08-07 20:12:18.302: [ default][3046692560] ENV Logging level for Module: CRSOCR
0
2012-08-07 20:12:18.302: [ default][3046692560] ENV Logging level for Module: CSSCLN
T 0
2012-08-07 20:12:18.302: [ default][3046692560] ENV Logging level for Module: EVMAGE
NT 0
2012-08-07 20:12:18.303: [ default][3046692560] ENV Logging level for Module: EVMAPP
0
2012-08-07 20:12:18.303: [ default][3046692560] ENV Logging level for Module: EVMCOM
M 0
2012-08-07 20:12:18.303: [    EVMD][3046692560] ENV Logging level for Module: EVMD
0
--More--(1%)

$ORA_CRS_HOME/log/和$ORACLE_HOME/log/目录中的racg目录中记录了RACG可执行文件对应的日志

[oracle@rac1 racg]$ pwd
/u01/app/11.2.0/11ggrid/log/rac1/racg
[oracle@rac1 racg]$ ls
racgeut/ racgevtf/ racgmain/
[oracle@rac1 racg]$

$ORA_CRS_HOME/log//client和$ORACLE_HOME/log //client”目录记录了与srvctl、ocrdump、ocrconfig以及ocrcheck命令对应的日志信息。

[oracle@rac1 rac1]$ pwd
/u01/app/oracle/product/11.2.0/dbhome_1/log/rac1
[oracle@rac1 rac1]$ ls
client/
[oracle@rac1 rac1]$

[[oracle@rac1 client]$ pwd
/u01/app/11.2.0/11ggrid/log/rac1/client
[oracle@rac1 client]$ ls
clscfg.log          ocrcheck_25681.log   oifcfg11.trc oifcfg6.trc
crsctl.log          ocrcheck_6982.log    oifcfg12.trc oifcfg7.trc
crsctl.trc          ocrconfig_17191.log oifcfg13.trc oifcfg8.trc
gpnptool_17951.log ocrconfig_17634.log oifcfg14.trc oifcfg9.trc
gpnptool_17951.trc ocrconfig_18620.log oifcfg1.trc   oifcfg.log
gpnptool_17959.log ocrconfig_20321.log oifcfg2.trc   oifcfg.trc
gpnptool_17959.trc ocrconfig_25725.log oifcfg3.trc   olsnodes.log
oclskd.log          ocrdump_25560.log    oifcfg4.trc   olsnodes.trc
ocrcheck_16786.log oifcfg10.trc         oifcfg5.trc
[oracle@rac1 client]$

集群中ALERT文件的位置$ORACLE_CRS_HOME/LOG/HOSTNAME下

[oracle@rac1 rac1]$ pwd
/u01/app/11.2.0/11ggrid/log/rac1
[oracle@rac1 rac1]$ ls
admin/ alertrac1.log crsd/ ctssd/    evmd/   gnsd/   mdnsd/ racg/
agent/ client/        cssd/ diskmon/ gipcd/ gpnpd/ ohasd/ srvm/
[oracle@rac1 rac1]$