HA环境，1台主机会自动重启目前环境为：两台P710+DS5020，***6100-04+powerHA5.5 SP09,配置有：2个VG（分别都是1个HDISK），1个磁盘心跳VG。当配置完HA后，可以正常启动和切换，但在DB1上运行HA服务时会加载有两个VG，DAT***G和BACKUPVG，30分钟后DB1会自动重新启动，且没有发生切换。在DB2上运行此资源时正常，不会有此现象。DB1运行smitty clstart时，会自动加载资源组，但ERRPT里会报错，clinfoES和clstrmgrES无法重新启动。在DB1的hacmp.out里会发生强制停HA的日志，接着，DB2上才会出现死人开关的报错和卷组报错。DB1：errpt6D19271E& & I O topsvcs& && &&&Topology Services daemon stopped28854E81& & I O grpsvcs& && &&&Group Services daemon stopped99FA80C7& & U S haemd& && && & SOFTWAREAA8AB241& & T O OPERATOR& && & OPERATOR NOTIFICATIONBC3BE5A3& & P S SRC& && && && &SOFTWARE PROGRAM ERROR1BA7DF4E& & P S SRC& && && && &SOFTWARE PROGRAM ERRORCB4A951F& & I S SRC& && && && &SOFTWARE PROGRAM ERRORCB4A951F& & I S SRC& && && && &SOFTWARE PROGRAM ERRORAFA89905& & I O grpsvcs& && &&&Group Services daemon started97419D60& & I O topsvcs& && &&&Topology Services daemon startedA6DF45AA& & I O RMCdaemon& && &The daemon is started.2BFA76F6& & T S SYSPROC& && &&&SYSTEM SHUTDOWN BY USER9DBCFDEE& & T O errdemon& && & ERROR LOGGING TURNED ON192AC071& & T O errdemon& && & ERROR LOGGING TURNED OFFDB1上HACMP,out此时间段的日志：Nov 27 13:13:43 EVENT COMPLETED: network_up_complete DB1 net_diskhbmulti_01 0& && && && && && && && &HACMP Event SummaryEvent: TE_JOIN_NETWORKStart time: Sun Nov 27 13:13:42 2011End time: Sun Nov 27 13:13:43 2011Action:& && && && && & Resource:& && && && && && && && &Script Name:----------------------------------------------------------------------------No resources changed as a result of this event----------------------------------------------------------------------------:check_for_site_down[+54] [[ high = high ]]:check_for_site_down[+54] version=1.4:check_for_site_down[+55] :check_for_site_down[+55] cl_get_pathHA_DIR=es:check_for_site_down[+57] STATUS=0:check_for_site_down[+59] set +u:check_for_site_down[+61] [ ]:check_for_site_down[+72] exit 0Nov 27 14:28:10 EVENT START: node_down DB1 forced:node_down[62] [[ high == high ]]:node_down[62] version=1.66:node_down[63] cl_get_path:node_down[63] HA_DIR=es:node_down[65] NODENAME=DB1:node_down[65] export NODENAME:node_down[66] PARAM=forced:node_down[66] export PARAM:node_down[68] UPDATESTATDFILE=/usr/es/sbin/cluster/etc/updatestatd:node_down[71] : This will be the exit status seen by the Cluster Manager.:node_down[72] : If STATUS is not 0, the Cluster Manager will enter reconfiguration:node_down[73] : All lower level scripts should pass status back to the caller.:node_down[74] : This will allow a Resource Groups to be processed individaully,:node_down[75] : independent of the status of another resource group.:node_down[77] STATUS=0:node_down[77] typeset -i STATUS:node_down[79] EMULATE=REAL:node_down[81] set -u:node_down[83] (( 2 < 1 )):node_down[88] rm -f /tmp/.RPCLOCKDSTOPPED:node_down[89] rm -f /usr/es/sbin/cluster/etc/updatestatd:node_down[92] : For RAS debugging enhancement, the result of ps -edf is captured at this time:node_down[94] : begin ps -edf:node_down[95] ps -edfroot@DB1:/>errpt -aj BC3BE5A3|more---------------------------------------------------------------------------LABEL:& && && & SRC_SVKOIDENTIFIER:& &&&BC3BE5A3Date/Time:& && & Sun Nov 27 14:36:25 GMT+08:00 2011Sequence Number: 1045Machine Id:& && &00F6E95C4C00Node Id:& && && &DB1Class:& && && &&&SType:& && && && &PERMWPAR:& && && && &GlobalResource Name:& &SRC& && && && & DescriptionSOFTWARE PROGRAM ERRORProbable CausesAPPLICATION PROGRAMFailure CausesSOFTWARE PROGRAM& && &&&Recommended Actions& && &&&MANUALLY RESTART SUBSYSTEM IF NEEDEDDetail DataSYMPTOM CODE& && && &256SOFTWARE ERROR CODE& && & -9017ERROR CODE& && && &&&0DETECTING MODULE'srchevn.c'@line:'376'FAILING MODULEclstrmgrES估计应该是clstrmgrES进程错误引起的，但重新***HACMP并升到SP09后，故障一样。DB2 ERRPT：root@DB2:/>errptIDENTIFIER TIMESTAMP&&T C RESOURCE_NAME&&DESCRIPTION3D32B80D& & P S topsvcs& && &&&NIM thread blockedAB59ABFF& & U U LIBLVM& && && &Remote node Concurrent Volume Group failAB59ABFF& & U U LIBLVM& && && &Remote node Concurrent Volume Group failAB59ABFF& & U U LIBLVM& && && &Remote node Concurrent Volume Group failAB59ABFF& & U U LIBLVM& && && &Remote node Concurrent Volume Group failAB59ABFF& & U U LIBLVM& && && &Remote node Concurrent Volume Group failAB59ABFF& & U U LIBLVM& && && &Remote node Concurrent Volume Group fail3D32B80D& & P S topsvcs& && &&&NIM thread blocked96CD8511& & T S topsvcs& && &&&Dead Man Switch will once again be reset4FDB3BA1& & I S topsvcs& && &&&DeadMan Switch (DMS) close to trigger90EDB0A5& & P S topsvcs& && &&&Dead Man Switch being allowed to expire.请各位前辈帮忙，应该从哪着手检查呢？多谢了！回答邀答17回答&
, 中国金融电子化公司DeadMan Switch (DMS) close to triggerDeadMan Switch (DMS) close to trigger赞同浏览961&
系统工程师
, SRIE但是根据时间点，DB2的这个DEAD MAN日志是在DB1的重启后出现的，会是因为这个原因吗？但是根据时间点，DB2的这个DEAD MAN日志是在DB1的重启后出现的，会是因为这个原因吗？赞同浏览945&
系统工程师
, GA当配置完HA后，可以正常启动和切换，但在DB1上运行HA服务时会加载有两个VG，DAT***G和BACKUPVG
启动HA时，2个VG在DB1加载。你的配置就是如此，还是你是想表述这是不想要的结果？在描述清楚些。
30分钟后DB1会自动重新启动，且没有发生切换。在DB2上运行此资源时正常，不会有此现象。
部署...当配置完HA后，可以正常启动和切换，但在DB1上运行HA服务时会加载有两个VG，DAT***G和BACKUPVG
启动HA时，2个VG在DB1加载。你的配置就是如此，还是你是想表述这是不想要的结果？在描述清楚些。
30分钟后DB1会自动重新启动，且没有发生切换。在DB2上运行此资源时正常，不会有此现象。
部署的DB?无思路时，可先把db2启停脚本去掉，先行测试HACMP是否启动，切换，运行正常；然后在加入db2启停脚本测试就是排除法定位故障点赞同浏览960&
系统工程师
, SRIE启动群集服务后，DB1会启动两个VG和一个IP，这时，两台机服务均正常。目前启动脚本就只有一个BANNER语句，是空脚本。启动群集服务后，DB1会启动两个VG和一个IP，这时，两台机服务均正常。目前启动脚本就只有一个BANNER语句，是空脚本。赞同浏览955&
系统工程师
, GA启动群集服务后，DB1会启动两个VG和一个IP，这时，两台机服务均正常。目前启动脚本就只有一个BANNER语句 ...smalltree 发表于
就是“热备”方式，一节点主用，另一节点备用的方式咯。模拟故障的切换测试做过没，什么状况。可能是配置的原因，也可能是出现bug。你收...启动群集服务后，DB1会启动两个VG和一个IP，这时，两台机服务均正常。目前启动脚本就只有一个BANNER语句 ...smalltree 发表于
就是“热备”方式，一节点主用，另一节点备用的方式咯。模拟故障的切换测试做过没，什么状况。可能是配置的原因，也可能是出现bug。你收一个snap -e发给IBM或传上来看看。赞同浏览914&
系统工程师
, SRIESNAP太大了，先上传HA LOGSNAP太大了，先上传HA LOG附件： (102.67 KB) (159.6 KB)赞同浏览965&
, 北京优兆科技有限公司NIM thread blocked看看2个节点间的通信正常吗？检查下心跳NIM thread blocked看看2个节点间的通信正常吗？检查下心跳赞同浏览953&
系统工程师
, SRIE原来配的是磁盘心跳，为了测试是不是磁盘心跳引起的，已经被我删除了，还未添加上去原来配的是磁盘心跳，为了测试是不是磁盘心跳引起的，已经被我删除了，还未添加上去赞同浏览947&
系统工程师
, GASNAP太大了，先上传HA LOGsmalltree 发表于
找了一个在各个日志中都有的时间点事件来查看：cluster.log [主要时间点事件，日志中显示这是cluster.log在28号最早事件]Nov 28 08:29:15 DB1 user:notice HACMP for AIX: EVENT START: node_up DB1 Nov 28 08:29...SNAP太大了，先上传HA LOGsmalltree 发表于
找了一个在各个日志中都有的时间点事件来查看：cluster.log [主要时间点事件，日志中显示这是cluster.log在28号最早事件]Nov 28 08:29:15 DB1 user:notice HACMP for AIX: EVENT START: node_up DB1 Nov 28 08:29:17 DB1 user:notice HACMP for AIX: EVENT START: acquire_service_addr Nov 28 08:29:19 DB1 user:notice HACMP for AIX: EVENT START: acquire_aconn_service en8 net_ether_01 Nov 28 08:29:19 DB1 user:notice HACMP for AIX: EVENT COMPLETED: acquire_aconn_service en8 net_ether_01 0 Nov 28 08:29:19 DB1 user:notice HACMP for AIX: EVENT COMPLETED: acquire_service_addr 0 Nov 28 08:29:25 DB1 user:notice HACMP for AIX: EVENT COMPLETED: node_up DB1 0 Nov 28 08:29:25 DB1 user:notice HACMP for AIX: EVENT START: node_up_complete DB1 Nov 28 08:29:25 DB1 user:notice HACMP for AIX: EVENT START: start_server db_app Nov 28 08:29:26 DB1 user:notice HACMP for AIX: EVENT COMPLETED: start_server db_app 0 Nov 28 08:29:27 DB1 user:notice HACMP for AIX: EVENT COMPLETED: node_up_complete DB1 0紧接着就是down forcedNov 28 08:35:11 DB1 user:notice HACMP for AIX: EVENT START: node_down DB1 forced Nov 28 08:35:12 DB1 user:notice HACMP for AIX: EVENT COMPLETED: node_down DB1 forced 0 Nov 28 08:35:12 DB1 user:notice HACMP for AIX: EVENT START: node_down_complete DB1 forced Nov 28 08:35:13 DB1 user:notice HACMP for AIX: EVENT COMPLETED: node_down_complete DB1 forced 0 Nov 28 08:35:13 DB1 local0:crit clstrmgrES[434226]: Mon Nov 28 08:35:13 approvalCb: Checking previous BEING_FORCE_DOWN flagNov 28 08:39:37 DB1 daemon:notice RMCdaemon[495632]: (Recorded using libct_ffdc.a cv 2):::Error ID: 6eKora07VhoC/v3Z0/6.e.1...................:::Reference ID:&&:::Template ID: a6df45aa:::Details File:&&:::Location: RSCT,rmcd.c,1.67,221& && && && && && && && &&&:::RMCD_INFO_0_ST The daemon is started.Nov 28 08:40:29 DB1 local0:crit clstrmgrES[360670]: Mon Nov 28 08:40:29 HACMP: clstrmgrES: VRMF fix level in product ODM = 9Nov 28 08:40:29 DB1 local0:crit clstrmgrES[360670]: Mon Nov 28 08:40:29 CLSTR_JOIN_AUTO_START - This is the normal start requestNov 28 08:40:30 DB1 daemon:notice topsvcs[1056784]: (Recorded using libct_ffdc.a cv 2):::Error ID: 6UpNEL0yVhoC/grl//6.e.1...................:::Reference ID:&&:::Template ID: 97419d60:::Details File:&&:::Location: rsct,bootstrp.C,1.215.1.10,4936& && && && && &:::TS_START_ST Topology Services daemon started Topology Services daemon started by: SRC Topology Services daemon log file location /var/ha/log/topsvcs.28.084029.ZZYCWL.en_US Topology Services daemon run directory /var/ha/run/topsvcs.ZZYCWL/Nov 28 08:40:33 DB1 daemon:notice grpsvcs[1077266]: (Recorded using libct_ffdc.a cv 2):::Error ID: 63Y7ej0/WhoC/Fb/1/6.e.1...................:::Reference ID:&&:::Template ID: afa89905:::Details File:&&:::Location: RSCT,pgsd.C,1.62.1.12,658& && && && && && && &:::GS_START_ST Group Services daemon started DIAGNOSTIC EXPLANATION HAGS daemon started by SRC. Log file is /var/ha/log/grpsvcs_trace.Nov 28 08:40:34 DB1 user:notice HACMP for AIX: clexit.rc : Unexpected termination of clinfoES.相应时间点hacmp.outNov 28 08:29:25 EVENT COMPLETED: node_up DB1 0Nov 28 08:29:27 EVENT COMPLETED: node_up_complete DB1 0----------------------------------------------------------------------------紧接着日志是：:check_for_site_down[+54] [[ high = high ]]:check_for_site_down[+54] version=1.4:check_for_site_down[+55] :check_for_site_down[+55] cl_get_pathHA_DIR=es:check_for_site_down[+57] STATUS=0:check_for_site_down[+59] set +u:check_for_site_down[+61] [ ]:check_for_site_down[+72] exit 0Nov 28 08:35:11 EVENT START: node_down DB1 forced:node_down[101] /usr/sbin/rsct/bin/dms/stopdms -s topsvcs在clinfo.log仅有以下日志Mon Nov 28 09:00:07 HAES Clinfo Version 5.5Mon Nov 28 09:00:07 cli_init_global_data: initializing data structuresMon Nov 28 09:00:07 maxClusters = 8maxNodes = 32Mon Nov 28 09:00:07 maxInterfaces = 8MAX_COMM_ADDRS = 512Mon Nov 28 09:00:07 maxGroups = 64Mon Nov 28 09:00:07 CL_Cluster_List::initialize() CalledMon Nov 28 09:00:07 AdapterMap::openSocket calledMon Nov 28 09:00:07 AdapterMap::update() Called, this = 202ab140Mon Nov 28 09:00:07 app_createPort: calledMon Nov 28 09:00:07 app_createPort: bind() failedMon Nov 28 09:00:07 clinfo: Returned from app_createPort(), app socket: -1Mon Nov 28 09:00:07 clinfo: Error in app_createPort().感觉是网卡问题，配置了绑定网卡吧在看cluster.logNov 28 08:54:37 DB1 user:notice HACMP for AIX: EVENT START: node_up DB1 Nov 28 08:54:39 DB1 user:notice HACMP for AIX: EVENT START: acquire_service_addr Nov 28 08:54:41 DB1 user:notice HACMP for AIX: EVENT START: acquire_aconn_service en8 net_ether_01 Nov 28 08:54:41 DB1 user:notice HACMP for AIX: EVENT COMPLETED: acquire_aconn_service en8 net_ether_01 0 Nov 28 08:54:41 DB1 user:notice HACMP for AIX: EVENT COMPLETED: acquire_service_addr 0 Nov 28 08:54:47 DB1 user:notice HACMP for AIX: EVENT COMPLETED: node_up DB1 0 Nov 28 08:54:47 DB1 user:notice HACMP for AIX: EVENT START: node_up_complete DB1 Nov 28 08:54:48 DB1 user:notice HACMP for AIX: EVENT START: start_server db_app Nov 28 08:54:48 DB1 user:notice HACMP for AIX: EVENT COMPLETED: start_server db_app 0 Nov 28 08:54:48 DB1 user:notice HACMP for AIX: EVENT COMPLETED: node_up_complete DB1 0 Nov 28 08:57:54 DB1 user:notice HACMP for AIX: EVENT START: node_down DB1 forced Nov 28 08:57:54 DB1 user:notice HACMP for AIX: EVENT COMPLETED: node_down DB1 forced 0 Nov 28 08:57:55 DB1 user:notice HACMP for AIX: EVENT START: node_down_complete DB1 forced Nov 28 08:57:55 DB1 user:notice HACMP for AIX: EVENT COMPLETED: node_down_complete DB1 forced 0 Nov 28 08:57:55 DB1 local0:crit clstrmgrES[512036]: Mon Nov 28 08:57:55 approvalCb: Checking previous BEING_FORCE_DOWN flagNov 28 08:57:55 DB1 local0:crit clstrmgrES[512036]: Mon Nov 28 08:57:55 approvalCb: Turning OFF BEING _FORCE_DOWN flag on local node.Nov 28 09:00:07 DB1 local0:crit clstrmgrES[512036]: Mon Nov 28 09:00:07 Starting the node from previous ForceDown stateNov 28 09:00:07 DB1 local0:crit clstrmgrES[512036]: Mon Nov 28 09:00:07 Startup after forced-down: Adding node-up event.Nov 28 09:00:07 DB1 local0:crit clstrmgrES[512036]: Mon Nov 28 09:00:07 CLSTR_JOIN_AUTO_START - This is the normal start requestNov 28 09:00:08 DB1 user:notice HACMP for AIX: clexit.rc : Unexpected termination of clinfoES. Nov 28 09:00:08 DB1 user:notice HACMP for AIX: EVENT START: node_up DB1 Nov 28 09:00:09 DB1 user:notice HACMP for AIX: EVENT START: acquire_service_addr Nov 28 09:00:10 DB1 user:notice HACMP for AIX: EVENT COMPLETED: acquire_service_addr 0 Nov 28 09:00:12 DB1 user:notice HACMP for AIX: EVENT COMPLETED: node_up DB1 0 Nov 28 09:00:12 DB1 user:notice HACMP for AIX: EVENT START: node_up_complete DB1 Nov 28 09:00:13 DB1 user:notice HACMP for AIX: EVENT START: start_server db_app Nov 28 09:00:13 DB1 user:notice HACMP for AIX: EVENT COMPLETED: start_server db_app 0 Nov 28 09:00:13 DB1 user:notice HACMP for AIX: EVENT COMPLETED: node_up_complete DB1 0 Nov 28 09:00:46 DB1 user:notice HACMP for AIX: EVENT START: node_down DB2 graceful #此时节点2也down了？Nov 28 09:00:46 DB1 user:notice HACMP for AIX: EVENT COMPLETED: node_down DB2 graceful 0 Nov 28 09:00:46 DB1 user:notice HACMP for AIX: EVENT START: node_down_complete DB2 graceful Nov 28 09:00:46 DB1 user:notice HACMP for AIX: EVENT COMPLETED: node_down_complete DB2 graceful 0 Nov 28 09:00:49 DB1 local0:crit clstrmgrES[512036]: Mon Nov 28 09:00:49 Removing 2 from ml_idxNov 28 09:02:08 DB1 user:notice HACMP for AIX: EVENT START: node_up DB2 Nov 28 09:02:08 DB1 user:notice HACMP for AIX: EVENT COMPLETED: node_up DB2 0 Nov 28 09:02:13 DB1 user:notice HACMP for AIX: EVENT START: node_up_complete DB2 Nov 28 09:02:13 DB1 user:notice HACMP for AIX: EVENT COMPLETED: node_up_complete DB2 0 Nov 28 09:02:18 DB1 user:notice HACMP for AIX: EVENT START: fail_interface DB2 192.168.2.2 #fail_interface 192.168.2.2，这个ip是db2的boot ip呀Nov 28 09:02:18 DB1 user:notice HACMP for AIX: EVENT COMPLETED: fail_interface DB2 192.168.2.2 0 Nov 28 09:02:50 DB1 local0:crit clstrmgrES[512036]: Mon Nov 28 09:02:50 HACMP: clstrmgrES: SrcStopForce: CalledNov 28 09:02:51 DB1 user:notice HACMP for AIX: EVENT START: node_down DB1 Nov 28 09:02:51 DB1 user:notice HACMP for AIX: EVENT START: stop_server db_app Nov 28 09:02:51 DB1 user:notice HACMP for AIX: EVENT COMPLETED: stop_server db_app 0 Nov 28 09:02:56 DB1 user:notice HACMP for AIX: EVENT START: release_service_addr Nov 28 09:02:57 DB1 user:notice HACMP for AIX: EVENT COMPLETED: release_service_addr 0 Nov 28 09:02:59 DB1 user:notice HACMP for AIX: EVENT COMPLETED: node_down DB1 0 Nov 28 09:03:05 DB1 user:notice HACMP for AIX: EVENT START: node_down_complete DB1 Nov 28 09:03:06 DB1 user:notice HACMP for AIX: EVENT COMPLETED: node_down_complete DB1 0 Nov 28 09:03:08 DB1 local0:crit clstrmgrES[512036]: Mon Nov 28 09:03:08 HACMP: clstrmgrES: approvalCb: Quit flag was set, exitingNov 28 09:03:13 DB1 daemon:notice topsvcs[671918]: (Recorded using libct_ffdc.a cv 2):::Error ID: 6SQG4h/FrhoC/Frd./6.e.1...................:::Reference ID: 6UpNEL0oihoC/SBf1/6.e.1...................:::Template ID: 6d19271e:::Details File:&&:::Location: rsct,comm.C,1.153,685& && && && && && && && & :::TS_STOP_ST Topology Services daemon stopped Topology Services daemon stopped by: Signal SIGTERM对比db1 netstat +db_res:cl_swap_IP_address[+1514] netstat -inName&&Mtu& &Network& &&&Address& && && &&&ZoneID& & Ipkts Ierrs& & Opkts Oerrs&&Collen8& &1500&&link#2& && &e4.1f.13.fa.e1.fd& && &-& && &462& &&&0& && & 54& &&&3& &&&0en8& &8.2& &192.168.2.1& && && && &-& && &462& &&&0& && & 54& &&&3& &&&0en8& &.62& &10.188.62.2& && && && &-& && &462& &&&0& && & 54& &&&3& &&&0en9& &1500&&link#3& && &5c.f3.fc.87.8c.80& && &-& &&&3596& &&&0& &&&1540& &&&0& &&&0en9& &8.3& &192.168.3.1& && && && &-& &&&3596& &&&0& &&&1540& &&&0& &&&0en9& &.62& &10.188.62.4& && && && &-& &&&3596& &&&0& &&&1540& &&&0& &&&0lo0& &16896 link#1& && && && && && && && && &&&-& &&&1555& &&&0& &&&1630& &&&0& &&&0lo0& && && && &127.0.0.1& && && && &&&-& &&&1555& &&&0& &&&1630& &&&0& &&&0lo0& &16896 ::1& && && && && && && && && && &&&0& &&&1555& &&&0& &&&1630& &&&0& &&&0db2 netstat+app_res:cl_swap_IP_address[+1514] netstat -inName&&Mtu& &Network& &&&Address& && && &&&ZoneID& & Ipkts Ierrs& & Opkts Oerrs&&Collen9& &1500&&link#2& && &5c.f3.fc.87.b0.80& && &-&&1274584& &&&0& &828188& &&&0& &&&0en9& &8.3& &192.168.3.2& && && && &-&&1274584& &&&0& &828188& &&&0& &&&0en9& &.62& &10.188.62.5& && && && &-&&1274584& &&&0& &828188& &&&0& &&&0en9& &.62& &10.188.62.3& && && && &-&&1274584& &&&0& &828188& &&&0& &&&0en8& &1500&&link#3& && &e4.1f.13.fa.e0.cd& && &-& && &&&0& &&&0& &043& &&&0en8& &8.2& &192.168.2.2& && && && &-& && &&&0& &&&0& &043& &&&0lo0& &16896 link#1& && && && && && && && && &&&-&&1188729& &&&0&&1232429& &&&0& &&&0lo0& && && && &127.0.0.1& && && && &&&-&&1188729& &&&0&&1232429& &&&0& &&&0lo0& &16896 ::1& && && && && && && && && && &&&0&&1188729& &&&0&&1232429& &&&0& &&&0HA配置是否有问题了？核实下etherchannel配置并测试找你的公司要支持吧，我们在这也是简单帮你看看。赞同浏览1219&
系统工程师
, SRIE每个EN8/EN9都用LACP绑定了四个网口，其中DB2上的192。168。2。2 EN8确实网络上有点问题，但这应该不能引起DB1的停机吧。每个EN8/EN9都用LACP绑定了四个网口，其中DB2上的192。168。2。2 EN8确实网络上有点问题，但这应该不能引起DB1的停机吧。赞同浏览986回答问题
系统工程师, SRIE评论222&
-- talk with trend,talk with technologist
京ICP备号-30