2009年08月28日 星期五 10时45分50秒 CST
Aug 22 02:30:16 Cluster.Framework: [ID 801593 daemon.notice] stdout: becoming primary for ipnet-data1
Aug 22 02:30:21 Cluster.Framework: [ID 801593 daemon.notice] stdout: becoming primary for ipnet-data5
Aug 22 02:30:49 Cluster.scdpmd: [ID 922726 daemon.notice] The status of device: /dev/did/rdsk/d2s0 is set to MONITORED
Aug 22 02:30:49 Cluster.scdpmd: [ID 489913 daemon.notice] The state of the path to device: /dev/did/rdsk/d2s0 has changed to OK
Aug 22 02:30:49 Cluster.scdpmd: [ID 922726 daemon.notice] The status of device: /dev/did/rdsk/d4s0 is set to MONITORED
Aug 22 02:30:49 Cluster.scdpmd: [ID 977412 daemon.notice] The state of the path to device: /dev/did/rdsk/d4s0 has changed to FAILED
Aug 22 02:30:49 Cluster.scdpmd: [ID 922726 daemon.notice] The status of device: /dev/did/rdsk/d5s0 is set to MONITORED
Aug 22 02:30:49 Cluster.scdpmd: [ID 489913 daemon.notice] The state of the path to device: /dev/did/rdsk/d5s0 has changed to OK
Aug 22 02:30:49 Cluster.scdpmd: [ID 922726 daemon.notice] The status of device: /dev/did/rdsk/d6s0 is set to MONITORED
Aug 22 02:30:49 Cluster.scdpmd: [ID 489913 daemon.notice] The state of the path to device: /dev/did/rdsk/d6s0 has changed to OK
Aug 22 02:30:49 Cluster.scdpmd: [ID 922726 daemon.notice] The status of device: /dev/did/rdsk/d3s0 is set to MONITORED
Aug 22 02:30:49 Cluster.scdpmd: [ID 489913 daemon.notice] The state of the path to device: /dev/did/rdsk/d3s0 has changed to OK
Aug 22 02:30:49 Cluster.scdpmd: [ID 922726 daemon.notice] The status of device: /dev/did/rdsk/d9s0 is set to MONITORED
Aug 22 02:30:49 Cluster.scdpmd: [ID 489913 daemon.notice] The state of the path to device: /dev/did/rdsk/d9s0 has changed to OK
Aug 22 02:30:49 Cluster.scdpmd: [ID 922726 daemon.notice] The status of device: /dev/did/rdsk/d10s0 is set to MONITORED
Aug 22 02:30:49 Cluster.scdpmd: [ID 489913 daemon.notice] The state of the path to device: /dev/did/rdsk/d10s0 has changed to OK
Aug 22 02:30:52 Cluster.RGM.global.rgmd: [ID 224900 daemon.notice] launching method <hastorageplus_prenet_start> for resource <ipnet-datav5>, resource group <ipnet-rg>, node <>, timeout <1800> seconds
Aug 22 02:30:52 Cluster.RGM.global.rgmd: [ID 224900 daemon.notice] launching method <hastorageplus_prenet_start> for resource <ipnet-data>, resource group <ipnet-rg>, node <>, timeout <1800> seconds
Aug 22 02:30:52 Cluster.RGM.global.rgmd: [ID 863274 daemon.notice] 40 fe_rpc_command: cmd_type(enum):<1>:cmd=</usr/cluster/lib/rgm/rt/hastorageplus/hastorageplus_prenet_start>:tag=<ipnet-rg.ipnet-datav5.10>: Calling security_clnt_connect(..., host=<>, sec_type {0:WEAK, 1:STRONG, 2:DES} =<1>, ...)
Aug 22 02:30:52 Cluster.RGM.global.rgmd: [ID 944595 daemon.notice] 39 fe_rpc_command: cmd_type(enum):<1>:cmd=</usr/cluster/lib/rgm/rt/hastorageplus/hastorageplus_prenet_start>:tag=<ipnet-rg.ipnet-data.10>: Calling security_clnt_connect(..., host=<>, sec_type {0:WEAK, 1:STRONG, 2:DES} =<1>, ...)
Aug 22 02:30:53 Cluster.RGM.global.rgmd: [ID 515159 daemon.notice] method <hastorageplus_prenet_start> completed successfully for resource <ipnet-datav5>, resource group <ipnet-rg>, node <>, time used: 0% of timeout <1800 seconds>
Aug 22 02:30:53 Cluster.RGM.global.rgmd: [ID 515159 daemon.notice] method <hastorageplus_prenet_start> completed successfully for resource <ipnet-data>, resource group <ipnet-rg>, node <>, time used: 0% of timeout <1800 seconds>
Aug 22 02:30:53 Cluster.RGM.global.rgmd: [ID 224900 daemon.notice] launching method <hastorageplus_monitor_start> for resource <ipnet-data>, resource group <ipnet-rg>, node <>, timeout <90> seconds
Aug 22 02:30:53 Cluster.RGM.global.rgmd: [ID 863274 daemon.notice] 40 fe_rpc_command: cmd_type(enum):<1>:cmd=</usr/cluster/lib/rgm/rt/hastorageplus/hastorageplus_monitor_start>:tag=<ipnet-rg.ipnet-data.7>: Calling security_clnt_connect(..., host=<>, sec_type {0:WEAK, 1:STRONG, 2:DES} =<1>, ...)
Aug 22 02:30:53 Cluster.RGM.global.rgmd: [ID 224900 daemon.notice] launching method <hastorageplus_monitor_start> for resource <ipnet-datav5>, resource group <ipnet-rg>, node <>, timeout <90> seconds
Aug 22 02:30:53 Cluster.RGM.global.rgmd: [ID 944595 daemon.notice] 39 fe_rpc_command: cmd_type(enum):<1>:cmd=</usr/cluster/lib/rgm/rt/hastorageplus/hastorageplus_monitor_start>:tag=<ipnet-rg.ipnet-datav5.7>: Calling security_clnt_connect(..., host=<>, sec_type {0:WEAK, 1:STRONG, 2:DES} =<1>, ...)
Aug 22 02:30:53 Cluster.RGM.global.rgmd: [ID 515159 daemon.notice] method <hastorageplus_monitor_start> completed successfully for resource <ipnet-data>, resource group <ipnet-rg>, node <>, time used: 0% of timeout <90 seconds>
Aug 22 02:30:53 Cluster.RGM.global.rgmd: [ID 515159 daemon.notice] method <hastorageplus_monitor_start> completed successfully for resource <ipnet-datav5>, resource group <ipnet-rg>, node <>, time used: 0% of timeout <90 seconds>
Aug 22 02:30:55 mac: [ID 736570 kern.info] NOTICE: e1000g0 unregistered
Aug 22 02:30:55 mac: [ID 736570 kern.info] NOTICE: e1000g1 unregistered
Aug 22 02:31:00 pseudo: [ID 129642 kern.info] pseudo-device: devinfo0
Aug 22 02:31:00 genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo@0
Aug 22 02:31:01 : [ID 988885 daemon.error] libpnm error: can\'t connect to PNMd on HNIPNM5240C.
Aug 22 02:31:57 fctl: [ID 517869 kern.warning] WARNING: fp(1)::GPN_ID for D_ID=10100 failed
Aug 22 02:31:57 fctl: [ID 517869 kern.warning] WARNING: fp(1)::N_x Port with D_ID=10100, PWWN=2101001b32a11aff disappeared from fabric
Aug 22 02:31:57 fctl: [ID 517869 kern.warning] WARNING: fp(0)::GPN_ID for D_ID=10200 failed
Aug 22 02:31:57 fctl: [ID 517869 kern.warning] WARNING: fp(0)::N_x Port with D_ID=10200, PWWN=2100001b32811aff disappeared from fabric
Aug 22 02:32:06 cl_runtime: [ID 489438 kern.notice] NOTICE: clcomm: Path :nxge3 - HNIPNM5240C:nxge3 being drained
Aug 22 02:32:06 cl_runtime: [ID 489438 kern.notice] NOTICE: clcomm: Path :nxge2 - HNIPNM5240C:nxge2 being drained
Aug 22 02:32:06 ip: [ID 678092 kern.notice] TCP_IOC_ABORT_CONN: local = 000.000.000.000:0, remote = 172.016.004.002:0, start = -2, end = 6
Aug 22 02:32:06 ip: [ID 302654 kern.notice] TCP_IOC_ABORT_CONN: aborted 0 connection
Aug 22 02:32:06 cl_runtime: [ID 250885 kern.notice] NOTICE: CMM: Quorum device /dev/did/rdsk/d9s2: owner set to node 1.
Aug 22 02:32:06 cl_runtime: [ID 446068 kern.notice] NOTICE: CMM: Node HNIPNM5240C (nodeid = 2) is down.
Aug 22 02:32:06 cl_runtime: [ID 108990 kern.notice] NOTICE: CMM: Cluster members: .
Aug 22 02:32:07 cl_runtime: [ID 279084 kern.notice] NOTICE: CMM: node reconfiguration #54 completed.
Aug 22 02:32:07 cl_runtime: [ID 396947 kern.warning] WARNING: clq_scsi3: One of the key 0x49e82ce600000001 was found to be invalid value on quorum device /dev/did/rdsk/d9s2.
Aug 22 02:32:07 cl_runtime: [ID 396947 kern.warning] WARNING: clq_scsi3: One of the key 0x49e82ce600000002 was found to be invalid value on quorum device /dev/did/rdsk/d9s2.
Aug 22 02:32:07 cl_runtime: [ID 250885 kern.notice] NOTICE: CMM: Quorum device /dev/did/rdsk/d9s2: owner set to node 1.
Aug 22 02:32:07 Cluster.Framework: [ID 801593 daemon.notice] stdout: fencing node HNIPNM5240C from shared devices
Aug 22 02:32:07 Cluster.CCR: [ID 651093 daemon.warning] reservation message(fence_node) - Fencing node 2 from disk /dev/did/rdsk/d4s2
Aug 22 02:32:07 Cluster.CCR: [ID 551094 daemon.warning] reservation warning(fence_node) - Unable to open device /dev/did/rdsk/d4s2, will retry in 2 seconds
Aug 22 02:32:07 Cluster.CCR: [ID 651093 daemon.warning] reservation message(fence_node) - Fencing node 2 from disk /dev/did/rdsk/d5s2
Aug 22 02:32:07 Cluster.CCR: [ID 651093 daemon.warning] reservation message(fence_node) - Fencing node 2 from disk /dev/did/rdsk/d6s2
Aug 22 02:32:07 Cluster.CCR: [ID 651093 daemon.warning] reservation message(fence_node) - Fencing node 2 from disk /dev/did/rdsk/d3s2
Aug 22 02:32:07 Cluster.CCR: [ID 651093 daemon.warning] reservation message(fence_node) - Fencing node 2 from disk /dev/did/rdsk/d10s2
Aug 22 02:32:09 Cluster.CCR: [ID 551094 daemon.warning] reservation warning(fence_node) - Unable to open device /dev/did/rdsk/d4s2, will retry in 2 seconds
Aug 22 02:32:11 last message repeated 1 time
Aug 22 02:32:13 Cluster.CCR: [ID 192619 daemon.warning] reservation error(fence_node) - Unable to open device /dev/did/rdsk/d4s2
Aug 22 02:33:06 cl_runtime: [ID 604153 kern.notice] NOTICE: clcomm: Path :nxge3 - HNIPNM5240C:nxge3 errors during initiation
Aug 22 02:33:06 cl_runtime: [ID 604153 kern.notice] NOTICE: clcomm: Path :nxge2 - HNIPNM5240C:nxge2 errors during initiation
Aug 22 02:33:06 cl_runtime: [ID 618107 kern.warning] WARNING: Path :nxge3 - HNIPNM5240C:nxge3 initiation encountered errors, errno = 62. Remote node may be down or unreachable through this path.
Aug 22 02:33:06 cl_runtime: [ID 618107 kern.warning] WARNING: Path :nxge2 - HNIPNM5240C:nxge2 initiation encountered errors, errno = 62. Remote node may be down or unreachable through this path.
Aug 22 02:33:23 fctl: [ID 517869 kern.warning] WARNING: fp(0)::N_x Port with D_ID=10200, PWWN=2100001b32811aff reappeared in fabric
Aug 22 02:33:26 fctl: [ID 517869 kern.warning] WARNING: fp(1)::N_x Port with D_ID=10100, PWWN=2101001b32a11aff reappeared in fabric
Aug 22 02:33:44 nxge: [ID 339653 kern.notice] NOTICE: nxge2: xcvr addr:0x1b - link is down
Aug 22 02:33:45 nxge: [ID 339653 kern.notice] NOTICE: nxge3: xcvr addr:0x1a - link is down
Aug 22 02:33:48 nxge: [ID 339653 kern.notice] NOTICE: nxge2: xcvr addr:0x1b - link is up 1000 Mbps full duplex
Aug 22 02:33:49 nxge: [ID 339653 kern.notice] NOTICE: nxge3: xcvr addr:0x1a - link is up 1000 Mbps full duplex
Aug 22 02:33:55 cl_runtime: [ID 537175 kern.notice] NOTICE: CMM: Node HNIPNM5240C (nodeid: 2, incarnation #: 1250879633) has become reachable.
Aug 22 02:33:55 cl_runtime: [ID 387288 kern.notice] NOTICE: clcomm: Path :nxge2 - HNIPNM5240C:nxge2 online
Aug 22 02:33:55 cl_runtime: [ID 377347 kern.notice] NOTICE: CMM: Node HNIPNM5240C (nodeid = 2) is up; new incarnation number = 1250879633.
Aug 22 02:33:55 cl_runtime: [ID 108990 kern.notice] NOTICE: CMM: Cluster members: HNIPNM5240C.
Aug 22 02:33:55 Cluster.Framework: [ID 801593 daemon.notice] stdout: releasing reservations for scsi-2 disks shared with HNIPNM5240C
Aug 22 02:33:55 cl_runtime: [ID 387288 kern.notice] NOTICE: clcomm: Path :nxge3 - HNIPNM5240C:nxge3 online
Aug 22 02:33:56 Cluster.CCR: [ID 551094 daemon.warning] reservation warning(release_shared_scsi2) - Unable to open device /dev/did/rdsk/d4s2, will retry in 2 seconds
Aug 22 02:34:00 last message repeated 2 times
Aug 22 02:34:02 Cluster.CCR: [ID 192619 daemon.warning] reservation error(release_shared_scsi2) - Unable to open device /dev/did/rdsk/d4s2
Aug 22 02:34:02 cl_runtime: [ID 279084 kern.notice] NOTICE: CMM: node reconfiguration #55 completed.
Aug 22 02:34:02 cl_runtime: [ID 396947 kern.warning] WARNING: clq_scsi3: One of the key 0x49e82ce600000001 was found to be invalid value on quorum device /dev/did/rdsk/d9s2.
Aug 22 02:34:02 cl_runtime: [ID 396947 kern.warning] WARNING: clq_scsi3: One of the key 0x49e82ce600000002 was found to be invalid value on quorum device /dev/did/rdsk/d9s2.
Aug 22 02:34:02 cl_runtime: [ID 250885 kern.notice] NOTICE: CMM: Quorum device /dev/did/rdsk/d9s2: owner set to node 1.
Aug 22 02:34:22 Cluster.CCR: [ID 551094 daemon.warning] reservation warning(release_shared_scsi2) - Unable to open device /dev/did/rdsk/d4s2, will retry in 2 seconds
Aug 22 02:34:26 last message repeated 2 times
Aug 22 02:34:28 Cluster.CCR: [ID 192619 daemon.warning] reservation error(release_shared_scsi2) - Unable to open device /dev/did/rdsk/d4s2
Aug 22 02:35:08 Cluster.RGM.global.rgmd: [ID 529407 daemon.notice] resource group ipnet-rg state on node HNIPNM5240C change to RG_OFF_PENDING_BOOT
Aug 22 02:35:08 Cluster.RGM.global.rgmd: [ID 529407 daemon.notice] resource group ipnet-rg state on node HNIPNM5240C change to RG_OFF_BOOTED
Aug 22 02:35:08 Cluster.RGM.global.rgmd: [ID 529407 daemon.notice] resource group ipnet-rg state on node HNIPNM5240C change to RG_OFFLINE
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 529407 daemon.notice] resource group ipnet-rg state on node change to RG_PENDING_OFFLINE
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource ipnet-datav5 state on node change to R_MON_STOPPING
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource ipnet-data state on node change to R_MON_STOPPING
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 224900 daemon.notice] launching method <hastorageplus_monitor_stop> for resource <ipnet-data>, resource group <ipnet-rg>, node <>, timeout <90> seconds
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 224900 daemon.notice] launching method <hastorageplus_monitor_stop> for resource <ipnet-datav5>, resource group <ipnet-rg>, node <>, timeout <90> seconds
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 863274 daemon.notice] 40 fe_rpc_command: cmd_type(enum):<1>:cmd=</usr/cluster/lib/rgm/rt/hastorageplus/hastorageplus_monitor_stop>:tag=<ipnet-rg.ipnet-data.8>: Calling security_clnt_connect(..., host=<>, sec_type {0:WEAK, 1:STRONG, 2:DES} =<1>, ...)
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 944595 daemon.notice] 39 fe_rpc_command: cmd_type(enum):<1>:cmd=</usr/cluster/lib/rgm/rt/hastorageplus/hastorageplus_monitor_stop>:tag=<ipnet-rg.ipnet-datav5.8>: Calling security_clnt_connect(..., host=<>, sec_type {0:WEAK, 1:STRONG, 2:DES} =<1>, ...)
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 515159 daemon.notice] method <hastorageplus_monitor_stop> completed successfully for resource <ipnet-datav5>, resource group <ipnet-rg>, node <>, time used: 0% of timeout <90 seconds>
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 515159 daemon.notice] method <hastorageplus_monitor_stop> completed successfully for resource <ipnet-data>, resource group <ipnet-rg>, node <>, time used: 0% of timeout <90 seconds>
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource ipnet-datav5 state on node change to R_ONLINE_UNMON
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource ipnet-data state on node change to R_ONLINE_UNMON
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource ipnet-datav5 state on node change to R_POSTNET_STOPPING
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource ipnet-data state on node change to R_POSTNET_STOPPING
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 224900 daemon.notice] launching method <hastorageplus_postnet_stop> for resource <ipnet-data>, resource group <ipnet-rg>, node <>, timeout <1800> seconds
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 224900 daemon.notice] launching method <hastorageplus_postnet_stop> for resource <ipnet-datav5>, resource group <ipnet-rg>, node <>, timeout <1800> seconds
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 784560 daemon.notice] resource ipnet-datav5 status on node change to R_FM_UNKNOWN
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 922363 daemon.notice] resource ipnet-datav5 status msg on node change to <Stopping>
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 784560 daemon.notice] resource ipnet-data status on node change to R_FM_UNKNOWN
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 922363 daemon.notice] resource ipnet-data status msg on node change to <Stopping>
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 944595 daemon.notice] 39 fe_rpc_command: cmd_type(enum):<1>:cmd=</usr/cluster/lib/rgm/rt/hastorageplus/hastorageplus_postnet_stop>:tag=<ipnet-rg.ipnet-data.11>: Calling security_clnt_connect(..., host=<>, sec_type {0:WEAK, 1:STRONG, 2:DES} =<1>, ...)
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 863274 daemon.notice] 40 fe_rpc_command: cmd_type(enum):<1>:cmd=</usr/cluster/lib/rgm/rt/hastorageplus/hastorageplus_postnet_stop>:tag=<ipnet-rg.ipnet-datav5.11>: Calling security_clnt_connect(..., host=<>, sec_type {0:WEAK, 1:STRONG, 2:DES} =<1>, ...)
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 515159 daemon.notice] method <hastorageplus_postnet_stop> completed successfully for resource <ipnet-datav5>, resource group <ipnet-rg>, node <>, time used: 0% of timeout <1800 seconds>
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 515159 daemon.notice] method <hastorageplus_postnet_stop> completed successfully for resource <ipnet-data>, resource group <ipnet-rg>, node <>, time used: 0% of timeout <1800 seconds>
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource ipnet-datav5 state on node change to R_OFFLINE
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 784560 daemon.notice] resource ipnet-datav5 status on node change to R_FM_OFFLINE
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 922363 daemon.notice] resource ipnet-datav5 status msg on node change to <>
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource ipnet-data state on node change to R_OFFLINE
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 784560 daemon.notice] resource ipnet-data status on node change to R_FM_OFFLINE
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 922363 daemon.notice] resource ipnet-data status msg on node change to <>
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 529407 daemon.notice] resource group ipnet-rg state on node change to RG_OFFLINE
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 529407 daemon.notice] resource group ipnet-rg state on node HNIPNM5240C change to RG_PENDING_ONLINE
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 784560 daemon.notice] resource ipnet-datav5 status on node HNIPNM5240C change to R_FM_UNKNOWN
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 922363 daemon.notice] resource ipnet-datav5 status msg on node HNIPNM5240C change to <Starting>
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource ipnet-datav5 state on node HNIPNM5240C change to R_PRENET_STARTING
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 784560 daemon.notice] resource ipnet-data status on node HNIPNM5240C change to R_FM_UNKNOWN
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 922363 daemon.notice] resource ipnet-data status msg on node HNIPNM5240C change to <Starting>
Aug 22 02:35:50 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource ipnet-data state on node HNIPNM5240C change to R_PRENET_STARTING
Aug 22 02:35:51 Cluster.Framework: [ID 801593 daemon.notice] stdout: no longer primary for ipnet-data5
Aug 22 02:35:51 Cluster.Framework: [ID 801593 daemon.notice] stdout: no longer primary for ipnet-data1
Aug 22 02:35:55 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource ipnet-data state on node HNIPNM5240C change to R_JUST_STARTED
Aug 22 02:35:55 Cluster.RGM.global.rgmd: [ID 784560 daemon.notice] resource ipnet-data status on node HNIPNM5240C change to R_FM_ONLINE
Aug 22 02:35:55 Cluster.RGM.global.rgmd: [ID 922363 daemon.notice] resource ipnet-data status msg on node HNIPNM5240C change to <>
Aug 22 02:35:55 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource ipnet-data state on node HNIPNM5240C change to R_ONLINE_UNMON
Aug 22 02:35:55 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource ipnet-datav5 state on node HNIPNM5240C change to R_JUST_STARTED
Aug 22 02:35:55 Cluster.RGM.global.rgmd: [ID 784560 daemon.notice] resource ipnet-datav5 status on node HNIPNM5240C change to R_FM_ONLINE
Aug 22 02:35:55 Cluster.RGM.global.rgmd: [ID 922363 daemon.notice] resource ipnet-datav5 status msg on node HNIPNM5240C change to <>
Aug 22 02:35:55 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource ipnet-datav5 state on node HNIPNM5240C change to R_ONLINE_UNMON
Aug 22 02:35:56 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource ipnet-datav5 state on node HNIPNM5240C change to R_ONLINE
Aug 22 02:35:56 Cluster.RGM.global.rgmd: [ID 443746 daemon.notice] resource ipnet-data state on node HNIPNM5240C change to R_ONLINE
Aug 22 02:35:56 Cluster.RGM.global.rgmd: [ID 529407 daemon.notice] resource group ipnet-rg state on node HNIPNM5240C change to RG_ONLINE
Aug 22 02:59:03 explorer: [ID 702911 daemon.notice] Explorer started
Aug 22 03:01:30 picld[244]: [ID 126618 daemon.error] PICL snmpplugin: cannot fetch object value (err=-1)
Aug 22 03:01:31 explorer: [ID 702911 daemon.notice] Explorer interrupted
Aug 22 03:02:07 mac: [ID 469746 kern.info] NOTICE: e1000g0 registered
Aug 22 03:02:07 e1000g: [ID 766679 kern.info] Intel(R) PRO/1000 Network Connection, Driver Ver. 5.2.8
Aug 22 03:02:51 explorer: [ID 702911 daemon.notice] Explorer started
Aug 22 03:05:20 pseudo: [ID 129642 kern.info] pseudo-device: lockstat0
Aug 22 03:05:20 genunix: [ID 936769 kern.info] lockstat0 is /pseudo/lockstat@0
Aug 22 03:05:20 pseudo: [ID 129642 kern.info] pseudo-device: fbt0
Aug 22 03:05:20 genunix: [ID 936769 kern.info] fbt0 is /pseudo/fbt@0
Aug 22 03:05:20 pseudo: [ID 129642 kern.info] pseudo-device: profile0
Aug 22 03:05:20 genunix: [ID 936769 kern.info] profile0 is /pseudo/profile@0
Aug 22 03:05:20 pseudo: [ID 129642 kern.info] pseudo-device: systrace0
Aug 22 03:05:20 genunix: [ID 936769 kern.info] systrace0 is /pseudo/systrace@0
Aug 22 03:05:20 pseudo: [ID 129642 kern.info] pseudo-device: sdt0
Aug 22 03:05:20 genunix: [ID 936769 kern.info] sdt0 is /pseudo/sdt@0
Aug 22 03:05:32 rootnex: [ID 349649 kern.info] ramdisk0 at root
Aug 22 03:05:32 genunix: [ID 936769 kern.info] ramdisk0 is /ramdisk-root
Aug 22 03:05:32 pseudo: [ID 129642 kern.info] pseudo-device: ramdisk1024
Aug 22 03:05:32 genunix: [ID 936769 kern.info] ramdisk1024 is /pseudo/ramdisk@1024
Aug 22 03:05:32 pseudo: [ID 129642 kern.info] pseudo-device: llc10
Aug 22 03:05:32 genunix: [ID 936769 kern.info] llc10 is /pseudo/llc1@0
Aug 22 03:05:32 ebus: [ID 521012 kern.info] su0 at ebus0: offset 0,ca0000
Aug 22 03:05:32 genunix: [ID 936769 kern.info] su0 is /ebus@c0/serial@0,ca0000
Aug 22 03:05:32 pseudo: [ID 129642 kern.info] pseudo-device: lofi0
Aug 22 03:05:32 genunix: [ID 936769 kern.info] lofi0 is /pseudo/lofi@0
Aug 22 03:05:32 pseudo: [ID 129642 kern.info] pseudo-device: trapstat0
Aug 22 03:05:32 genunix: [ID 936769 kern.info] trapstat0 is /pseudo/trapstat@0
Aug 22 03:05:32 pseudo: [ID 129642 kern.info] pseudo-device: ntwdt0
Aug 22 03:05:32 genunix: [ID 936769 kern.info] ntwdt0 is /pseudo/ntwdt@0
Aug 22 03:05:32 pseudo: [ID 129642 kern.info] pseudo-device: mdesc0
Aug 22 03:05:32 genunix: [ID 936769 kern.info] mdesc0 is /pseudo/mdesc@0
Aug 22 03:05:32 mac: [ID 469746 kern.info] NOTICE: e1000g1 registered
Aug 22 03:05:32 e1000g: [ID 766679 kern.info] Intel(R) PRO/1000 Network Connection, Driver Ver. 5.2.8
Aug 22 03:05:33 pseudo: [ID 129642 kern.info] pseudo-device: fcsm0
Aug 22 03:05:33 genunix: [ID 936769 kern.info] fcsm0 is /pseudo/fcsm@0
Aug 22 03:05:33 pseudo: [ID 129642 kern.info] pseudo-device: fssnap0
Aug 22 03:05:33 genunix: [ID 936769 kern.info] fssnap0 is /pseudo/fssnap@0
Aug 22 03:05:33 pseudo: [ID 129642 kern.info] pseudo-device: winlock0
Aug 22 03:05:33 genunix: [ID 936769 kern.info] winlock0 is /pseudo/winlock@0
Aug 22 03:05:33 pseudo: [ID 129642 kern.info] pseudo-device: pm0
Aug 22 03:05:33 genunix: [ID 936769 kern.info] pm0 is /pseudo/pm@0
Aug 22 03:05:33 pseudo: [ID 129642 kern.info] pseudo-device: rsm0
Aug 22 03:05:33 genunix: [ID 936769 kern.info] rsm0 is /pseudo/rsm@0
Aug 22 03:20:27 explorer: [ID 702911 daemon.notice] Explorer interrupted
Aug 25 09:48:57 explorer: [ID 702911 daemon.notice] Explorer started
Aug 25 10:20:48 explorer: [ID 702911 daemon.notice] Explorer finished
Aug 25 10:27:14 genunix: [ID 834635 kern.info] /scsi_vhci/ssd@g600a0b8000562972000005eb4a136bc5 (ssd16) multipath status: optimal, path /pci@500/pci@0/pci@d/SUNW,qlc@0,1/fp@0,0 (fp1) to target address: w202200a0b8562972,4 is online Load balancing: round-robin
Aug 25 10:27:16 genunix: [ID 834635 kern.info] /scsi_vhci/ssd@g600a0b8000562972000005e94a136b56 (ssd17) multipath status: optimal, path /pci@500/pci@0/pci@d/SUNW,qlc@0,1/fp@0,0 (fp1) to target address: w202200a0b8562972,3 is online Load balancing: round-robin
Aug 25 10:27:17 genunix: [ID 834635 kern.info] /scsi_vhci/ssd@g600a0b8000562972000005e64a136b47 (ssd18) multipath status: optimal, path /pci@500/pci@0/pci@d/SUNW,qlc@0,1/fp@0,0 (fp1) to target address: w202200a0b8562972,2 is online Load balancing: round-robin
Aug 25 10:27:18 genunix: [ID 834635 kern.info] /scsi_vhci/ssd@g600a0b80005629da0000040549e7a43e (ssd12) multipath status: optimal, path /pci@500/pci@0/pci@d/SUNW,qlc@0,1/fp@0,0 (fp1) to target address: w202200a0b8562972,1 is standby Load balancing: round-robin
Aug 25 10:27:18 genunix: [ID 834635 kern.info] /scsi_vhci/ssd@g600a0b80005629da0000040249e7a3e0 (ssd13) multipath status: optimal, path /pci@500/pci@0/pci@d/SUNW,qlc@0,1/fp@0,0 (fp1) to target address: w202200a0b8562972,0 is standby Load balancing: round-robin
Aug 25 10:27:48 genunix: [ID 834635 kern.info] /scsi_vhci/ssd@g600a0b8000562972000005eb4a136bc5 (ssd16) multipath status: optimal, path /pci@500/pci@0/pci@d/SUNW,qlc@0/fp@0,0 (fp0) to target address: w202300a0b8562972,4 is standby Load balancing: round-robin
Aug 25 10:27:49 genunix: [ID 834635 kern.info] /scsi_vhci/ssd@g600a0b8000562972000005e94a136b56 (ssd17) multipath status: optimal, path /pci@500/pci@0/pci@d/SUNW,qlc@0/fp@0,0 (fp0) to target address: w202300a0b8562972,3 is standby Load balancing: round-robin
Aug 25 10:27:50 genunix: [ID 834635 kern.info] /scsi_vhci/ssd@g600a0b8000562972000005e64a136b47 (ssd18) multipath status: optimal, path /pci@500/pci@0/pci@d/SUNW,qlc@0/fp@0,0 (fp0) to target address: w202300a0b8562972,2 is standby Load balancing: round-robin
Aug 25 10:27:52 genunix: [ID 834635 kern.info] /scsi_vhci/ssd@g600a0b80005629da0000040549e7a43e (ssd12) multipath status: optimal, path /pci@500/pci@0/pci@d/SUNW,qlc@0/fp@0,0 (fp0) to target address: w202300a0b8562972,1 is online Load balancing: round-robin
Aug 25 10:27:53 genunix: [ID 834635 kern.info] /scsi_vhci/ssd@g600a0b80005629da0000040249e7a3e0 (ssd13) multipath status: optimal, path /pci@500/pci@0/pci@d/SUNW,qlc@0/fp@0,0 (fp0) to target address: w202300a0b8562972,0 is online Load balancing: round-robin
Aug 26 08:21:23 explorer: [ID 702911 daemon.notice] Explorer started
Aug 26 08:57:49 explorer: [ID 702911 daemon.notice] Explorer finished
Aug 28 08:21:25 in.mpathd[172]: [ID 594170 daemon.error] NIC failure detected on nxge1 of group ipmp1
Aug 28 08:21:25 in.mpathd[172]: [ID 832587 daemon.error] Successfully failed over from NIC nxge1 to NIC nxge0
Aug 28 08:21:33 in.mpathd[172]: [ID 299542 daemon.error] NIC repair detected on nxge1 of group ipmp1
Aug 28 08:21:33 in.mpathd[172]: [ID 620804 daemon.error] Successfully failed back to NIC nxge1作者: michael1983 时间: 2009-08-28 15:32
主机发生重启,应用发生切换了。
怎么会没问题?
要找出主机重启的原因。
看看是不是硬件问题作者: l_x1103 时间: 2009-08-28 16:51
恩,好像也不知道哪个人进机房把什么一根线弄掉了,又插上了....
郁闷 机房我还真没去过,具体说的东东 雾水濛濛....作者: michael1983 时间: 2009-09-02 12:41
昏死
原来是把线搞掉了啊
追究他的责任啊
不能就这么算了作者: o0不知火舞0o 时间: 2009-09-06 11:02
哈哈。楼主一定不能就这么算了