H3C-S5500-EISI系列以太網(wǎng)交換機-故障處理手冊-6W100-整本手冊

H3CS5500-EI&S5500-SI系列以太網(wǎng)交換機故障處理手冊Copyright?2014杭州華三通信技術有限公司版權所有，保留一切權利。非經(jīng)本公司書面許可，任何單位和個人不得擅自摘抄、復制本文檔內(nèi)容的部分或全部，并不得以任何形式傳播。本文檔中的信息可能變動，恕不另行通知。目錄1ACL相關特性故障處理··························································································································11.1ACL下發(fā)失敗故障處理·························································································································11.1.1故障描述····································································································································11.1.2故障處理流程·····························································································································21.1.3故障處理步驟·····························································································································21.2故障診斷命令········································································································································32IRF相關特性故障處理···························································································································42.1IRF建立失敗故障處理··························································································································42.1.1故障描述····································································································································42.1.2故障處理流程·····························································································································42.1.3故障處理步驟·····························································································································52.2故障診斷命令········································································································································63聚合相關特性故障處理··························································································································63.1聚合不成功故障處理·····························································································································63.1.1故障描述····································································································································63.1.2故障處理流程·····························································································································73.1.3故障處理步驟·····························································································································73.2故障診斷命令········································································································································84端口相關故障處理·································································································································84.1端口不Linkup故障處理························································································································84.1.1故障描述····································································································································84.1.2故障處理流程·····························································································································94.1.3故障處理步驟·····························································································································94.2故障診斷命令······································································································································105其它常見故障處理·······························································································································115.1CPU占用率高故障處理·······················································································································115.1.1故障描述··································································································································115.1.2故障處理流程···························································································································115.1.3故障處理步驟···························································································································115.1.4故障診斷命令···························································································································125.2二層流量轉發(fā)丟包······························································································································125.2.1故障描述··································································································································125.2.2故障處理流程···························································································································13i

5.2.3故障處理步驟5.2.4故障診斷命令5.3三層轉發(fā)丟包故障···························································································································13···························································································································15······························································································································165.3.1故障描述··································································································································165.3.2故障處理流程···························································································································175.3.3故障處理步驟···························································································································175.3.4故障診斷命令···························································································································185.4PoE供電異?！ぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁぁ?85.4.1故障描述··································································································································185.4.2故障處理流程···························································································································185.4.3故障處理步驟···························································································································195.4.4故障診斷命令···························································································································20ii

本文檔適用于H3CS5500-EI&S5500-SI系列以太網(wǎng)交換機Release2208及以上版本。1ACL相關特性故障處理1.1ACL下發(fā)失敗故障處理1.1.1故障描述用戶下發(fā)ACL失敗，具體分兩種失敗情況：??執(zhí)行下發(fā)命令后設備提示硬件資源不足。執(zhí)行下發(fā)命令后設備無任何錯誤提示，但ACL不起作用。11.1.2故障處理流程圖1ACL下發(fā)失敗故障診斷流程圖1.1.3故障處理步驟1.查看下發(fā)時是否報硬件資源不足下發(fā)ACL配置時如果界面打印出“Reason:Notenoughhardwareresource”字樣，則表明ACL下發(fā)失敗是由硬件資源不足導致。通過displayaclresource命令可以進一步確認ACL硬件資源使用情況，如果顯示信息中Remaining條目為0，則表示ACL硬件資源用盡，設備無法再下發(fā)ACL。如果下發(fā)時沒有報“Reason:Notenoughhardwareresource”字樣，則根據(jù)下發(fā)方式進行步驟選擇，如果是通過MQC（QoS策略）方式下發(fā)請進行步驟2，通過包過濾（packet-filter）方式下發(fā)請進行步驟3。22.檢查QoS策略配置是否正確通過下面命令分別檢查不同使用情況下QoS策略的配置情況：??顯示端口上QoS策略配置信息，displayqospolicyinterface顯示VLAN上QoS策略配置信息，displayqosvlan-policy?顯示全局QoS策略配置信息，displayqospolicyglobal?顯示控制平面上QoS策略配置信息，displayqospolicycontrol-planeslotslot-number如果QoS策略中缺少流分類和流行為關聯(lián)的配置，則補充相應配置。否則可通過下面兩個命令分別檢查下QoS策略中的類和流行為是否配置正確。?顯示配置的類信息，displaytrafficclassifieruser-defined顯示配置的流行為信息，displaytrafficbehavioruser-defined如果沒有正確配置，則進行正確配置，否則進行步驟4。3.檢查packet-filter配置是否正確可以通過displaypacket-filter命令檢查進行步驟4。4.檢查ACL配置是否正確?packet-filter配置是否正確，如果不正確，則進行正確配置，否則可以通過displayacl命令檢查ACL是否配置正確，如果不正確，則進行正確配置，否則進行步驟5。5.尋求技術支持如果上述檢查完成后故障仍無法排除，請聯(lián)系H3C的技術支持工程師。1.2故障診斷命令命令displayaclresource說明顯示ACL資源的使用情況顯示指定端口或所有端口上QoS策略的配置信息和displayqospolicyinterfacedisplayqosvlan-policy運行情況顯示基于VLAN應用QoS策略的信息顯示基于全局應用QoS策略的信息顯示控制平面應用QoS策略的信息顯示配置的類信息displayqospolicyglobaldisplayqospolicycontrol-planedisplaytrafficclassifieruser-defineddisplaytrafficbehavioruser-defineddisplaypacket-filter顯示配置的流行為信息顯示ACL在報文過濾中的應用情況32IRF相關特性故障處理2.1IRF建立失敗故障處理2.1.1故障描述用戶規(guī)劃IRF后，嘗試將多臺設備組成一個IRF系統(tǒng)，發(fā)現(xiàn)IRF沒有成功建立。2.1.2故障處理流程圖2IRF建立失敗故障診斷流程圖IRF建立失敗使用最多9臺S5500-EI/4臺S5500-SI設備是否是是IRF成員數(shù)目是否達到上限？設備故障是否排除？建立IRF否否各成員設備的成員編號配置成員設備的成員編故障是否排除？在IRF內(nèi)是否唯一？號使其唯一否是IRF物理是否正確端口的連接關系按正確的方式連接IRF物理端口是否故障是否排除？否是IRF物理10Gbps速率連接是否為否否使用實現(xiàn)10Gbps連接正確的模塊或電纜是故障是否排除？否是是是開啟IRF物理端口并激活IRF端口配置IRF鏈路狀態(tài)是否正常故障是否排除？否是否各成員設備的軟件版本使各成員設備使用相同故障是否排除？是否一致的軟件版本否是尋求技術支持故障排除42.1.3故障處理步驟1.檢查IRF中成員設備數(shù)量通過displayirf命令可以查看當前IRF中的成員設備數(shù)量，如果當前IRF中組成員數(shù)目已經(jīng)達到上限，則其它設備不能再加入IRF。S5500-EI設備最多支持使用9臺設備建立IRF；S5500-SI設備最多支持使用4臺設備建立IRF。2.檢查IRF中各成員設備的成員編號是否唯一通過執(zhí)行displayirfconfiguration命令可以查看到IRF中的成員設備編號，如果有兩臺成員設備的成員編號相同，則這兩臺設備之間無法建立IRF。請為各設備配置不同的成員編號。3.檢查物理連線是否正確在進行成員設備的連接時，一臺設備上與IRF-Port1綁定的IRF物理端口只能和鄰居成員設備IRF-Port2口上綁定的IRF物理端口相連。(1)通過displayirfconfiguration命令查看各設備上IRF端口和IRF物理端口的綁定關系。(2)通過綁定關系確認物理連接是否正確。(3)如果存在連接錯誤，重新進行物理連接或重新配置IRF端口和IRF物理端口的綁定關系。在S5500-SI/EI系列交換機上進行IRF端口和IRF物理端口的綁定時，需要注意的是：?綁定到IRF-Port1的IRF物理端口必須位于綁定到IRF-Port2的IRF物理端口的左側（面向設備后面板的方向）?在配置聚合IRF端口時，同一塊接口模塊擴展卡上的IRF物理端口必須對應到相同的IRF端口4.檢查IRF物理連接的速率檢查用于IRF連接的端口是否來自于以下類型的接口模塊擴展卡上：?????單端口10GEXFP接口模塊擴展卡（LSPM1XP1P）雙端口10GEXFP接口模塊擴展卡（LSPM1XP2P）短距雙端口10GECX4接口模塊擴展卡（LSPM1CX2P）雙端口10GESFP+接口模塊擴展卡（LSPM2SP2P）雙端口1/10GBase-T接口模塊擴展卡（LSPM1XGT2P）請檢查插入IRF物理端口的模塊是否帶有10Gbps、XFP、SFP+標記，如果使用10GE雙絞線或CX4/SFP+線纜連接，檢查線纜上的標簽是否帶有10Gbps、CX4、SFP+標記。S5500-SI/EI設備只支持通過10G速率的鏈路實現(xiàn)IRF連接，所以只有帶有10Gbps、CX4、SFP+或者XFP標記的線纜或模塊才可以用于多臺設備之間的IRF連接。5.檢查IRF鏈路狀態(tài)(1)通過displayirftopology命令顯示IRF拓撲狀態(tài)，查看Link字段確認IRF鏈路狀態(tài)。(2)如果Link字段顯示為DOWN，執(zhí)行displayinterface命令查看IRF物理端口的狀態(tài)。?如果IRF物理端口狀態(tài)為DOWN(Administratively)，使用undoshutdown命令開啟該端口；如果IRF物理端口顯示為DOWN，檢查并重新連接物理連接，使端口正常工作。?如果IRF端口綁定的IRF物理端口中至少有一個處于UP狀態(tài)，則進行下一步操作。(3)保存當前配置，在系統(tǒng)視圖下執(zhí)行irf-port-configurationactive命令激活IRF端口的配置。5

激活IRF端口配置會引起IRF合并，非Master設備將會重啟。為避免重啟造成配置丟失，請在執(zhí)行irf-port-configurationactive命令之前保存所有成員設備的配置。6.檢查各成員設備(1)用戶可通過displayversion命令查看各設備上運行的軟件版本(2)如果兩臺設備上使用的軟件版本差異過大，則不能組成IRF。出現(xiàn)這種現(xiàn)象時，上運行的軟件版本建議采用升級低版本的方式解決。通常情況下，IRF系統(tǒng)啟動文件的自動加載功能可以自動同步各成員設備間運行的軟件版本，使其與Master設備保持一致。但是如果成員設備間的版本差異過大，則該功能可能無法完成自動同步。7.尋求技術支持如果上述檢查完成后故障仍無法排除，請聯(lián)系H3C的技術支持工程師。2.2故障診斷命令命令說明displayversiondisplayirf顯示系統(tǒng)版本信息顯示本IRF的相關信息displayirfconfigurationdisplayinterface顯示本IRF中所有設備的配置信息顯示端口的信息displayversion顯示設備上運行的軟件版本激活設備上所有IRF端口下的配置irf-port-configurationactive3聚合相關特性故障處理3.1聚合不成功故障處理3.1.1故障描述用戶配置聚合后，發(fā)現(xiàn)聚合失敗。63.1.2故障處理流程圖3聚合不成功故障診斷流程圖聚合失敗否否故障是否排除是否物理連接是否正確是正確連接是聚合組中成員端口是否UP成員端口UP故障是否排除是否否配置本端口的端口屬性類配置和第二類配置與參考端口相同本端口的端口屬性類配置和第二類配置與參考端口是否相同是故障是否排除否是否是否為動態(tài)聚合是否配置本端口的對端端口的端口屬性類配置和第二類配置與參考端口的對端端口相同本端口的對端端口的屬性類配置和第二類配置與參考端口的對端端口是否相同故障是否排除是否是是是故障是否排除聚合成員是否超過8個使聚合成員端口小于8個否否故障排除尋求技術支持3.1.3故障處理步驟1.物理連線是否正確根據(jù)聚合規(guī)劃進行線路檢查，檢查物理線路是否完全按照規(guī)劃進行連接。72.聚合組中成員端口是否通過displayinterface命令查看聚合組中的成員端口是否處于不UP故障流程處理，具體請參見4.1端口不Linkup故障處理。3.本端口的端口屬性類配置和第二類配置與參考端口是否相同在本設備上通過執(zhí)行displaycurrent-configurationinterface查看聚合UPUP狀態(tài)。如果沒有UP，可按照端口接口及本端Unselected端口的屬性類配置和第二類配置與參考端口是否相同。如果配置不同，則將其配置相同。4.是否為動態(tài)聚合，則直接到步驟6，否5.本端口的對端端口的端口屬性類配置和第二類配置與參考端口的對端端口是否相同Unselected狀態(tài)端口相連接設備上執(zhí)行displaycurrent-configurationinterface命令查看對端Unselected端口的若不是動態(tài)聚合則進行步驟5。在與本端屬性類配置和第二類配置與參考端口的對端端口是否相同。如果配置不同，則將其配置相同。6.聚合組中成員端口是否超過通過displaylink-aggregationverbose命令查看聚合組中成員端口是否8個，則編號較大的端口為Unselected狀態(tài)視圖下使用undoportlink-aggregationgroup命令將Selected端口中為Selected狀態(tài)7.尋求技術支持后故障仍無法排除，請聯(lián)系H3C的技術支持工程師。8個超過8個。如果成員端口超過將成?？梢栽谝蕴W(wǎng)接口不適用的端口從聚合組中刪除，以使必須使用的端口。如果上述檢查完成3.2故障診斷命令命令說明displaycurrent-configurationinterfacedisplayinterface顯示接口當前生效的配置顯示以太網(wǎng)接口的相關信息顯示系統(tǒng)上已有的二層聚合接口或三層聚合接口displaylink-aggregationverbose所對應的聚合組的詳細信息4端口相關故障處理4.1端口不Linkup故障處理4.1.1故障描述端口和對端連接，無法Linkup。84.1.2故障處理流程圖4端口不Linkup故障診斷流程圖4.1.3故障處理步驟1.檢查端口物理連接是否到位重新插拔網(wǎng)線，看端口是否UP。2.檢查端口是否被shutdown。執(zhí)行displayinterfacebrief命令，查看對應接口顯示信息的第二列是否顯示為ADM。若為ADM，請通過undoshutdown命令激活端口。3.檢查兩端端口的速率執(zhí)行displayinterfacebrief命令，請通過speed命令和duplex命令配置端口4.確認網(wǎng)線質(zhì)量或光口的光模塊類型及其波長是否匹配查看端口是否UP。、雙工模式是否匹配。查看端口顯示信息的速率與雙工是否與對端一致。若不一致，的速率和雙工模式。更換網(wǎng)線插入端口，9如果是光口，檢查光模塊的類型和波長是否匹配。光模塊標簽上沒標明的可以通過displaytransceiverinterface命令行查看。<Sysname>displaytransceiverinterfaceten-gigabitethernet1/1/1Ten-GigabitEthernet1/1/1transceiverinformation:TransceiverType:10G_BASE_SR_SFPConnectorType:LCWavelength(nm):850TransferDistance(m):80(50um),30(62.5um)DigitalDiagnosticMonitoring:YESVendorName:FINISARCORP.OrderingName:SFP_XGE_SX-MM8505.如果是子卡端口，請檢查子卡狀態(tài)是否正常。執(zhí)行displaydevice命令，查看最后一列是否顯示為Normal。若不是，請拔出子卡，再重新插入或更換為同類型子卡插入插槽。[Sysname]displaydeviceSlot1SubSNoPortNumPCBVerFPGAVerCPLDVerBootRomVerAddrLMTypeState052REV.CNULL007607IVLMAINNormal12REV.ANULLNULLNULLIVL2*10GENormal6.使用端口內(nèi)部環(huán)回檢測命令檢查物理端口是否有問題[Sysname-GigabitEthernet1/0/2]loopbackinternal%Apr2612:40:25:30920005500IFNET/4/LINKUPDOWN:GigabitEthernet1/0/2:linkstatusisUP%Apr2612:40:25:53120005500IFNET/4/LINKUPDOWN:GigabitEthernet1/0/2:linkstatusisDOWNLoopinternalsucceeded!7.尋求技術支持如果上述檢查完成后故障仍無法排除，請聯(lián)系H3C的技術支持工程師。4.2故障診斷命令命令說明displaydevice顯示設備信息displayinterfacebrief顯示所有端口的概要信息顯示接口數(shù)上插入的可插拔接口模塊的主要特征參displaytransceiverinterfaceloopbackinternal開啟以太網(wǎng)端口的內(nèi)部環(huán)回測試功能105其它常見故障處理5.1CPU占用率高故障處理5.1.1故障描述displaycpu-usage命令顯示設備的CPU占用率比較高。5.1.2故障處理流程圖5CPU占用率高故障診斷流程圖5.1.3故障處理步驟1.找出占用CPU資源的任務使用隱藏模式下的displaycpu-usagetask[slotslot-id]命令，可以查看CPU資源的占用情況。2.針對具體的下面列出一些常見的占用CPU的任務：任務進行分析?bRX1、bRX2任務能收到大量上送CPU的報文，可以使用displayinterface命令看看能是設備間連設備可端口有沒有收到大量廣播報文。另外，還需要檢查網(wǎng)絡中是否有報文形成了環(huán)路。若存在環(huán)路，可線錯誤導致的，需要檢查設備的連接情況。?MSTP任務11該任務占用CPU資源可能是因為設備收到較多的STP協(xié)議產(chǎn)生的TCN/TC報文，導致頻繁刪除MAC地址。使用displaystpbpdu-statisticsinterface命令可以查看端口收發(fā)BPDU報文的情況，重點關注TCN/TC報文的計數(shù)。AGNT任務???該任務占用CPU資源，可能是因為網(wǎng)管軟件在頻繁地從設備獲取MIB信息。這一點需要請客戶確認網(wǎng)管軟件的工作情況。ROUT任務該任務占用CPU資源較高，可能是網(wǎng)絡中的路由在震蕩?？梢允褂胐isplayiprouting-table系列命令查看路由變化的情況。L2X0、L2X1任務該任務占用CPU資源較高，可能是設備學習的MAC地址在反復震蕩。請排查網(wǎng)絡拓撲是否有不穩(wěn)定的情況。3.尋求技術支持如果上述檢查完成后故障仍無法排除，請聯(lián)系H3C的技術支持工程師。5.1.4故障診斷命令命令說明_hidecmd進入命令行隱藏模式視圖displaycpu-usagetask[slotslot-id]displayinterface命令行隱藏模式視圖，顯示CPU資源的占用情況太接網(wǎng)口的相關信息表中當前激活路由的摘要信息指定端口上的BPDU統(tǒng)計信息displayiprouting-tabledisplaystpbpdu-statisticsinterface5.2二層流量轉發(fā)丟包5.2.1故障描述設備二層轉發(fā)丟包，即源端和目的端在同一二層網(wǎng)絡的同一VLAN內(nèi)，通信過程中有丟包。125.2.2故障處理流程圖6二層流量轉發(fā)丟包故障診斷流程圖5.2.3故障處理步驟1.查看端口使用displayinterface命令查看端口下是否有錯包請前往步驟3進行后續(xù)步驟的檢查下是否有錯包。如果有錯包，請前往步驟2，如果沒有錯包，。<H3C>displayinterfaceGigabitEthernet1/0/36GigabitEthernet1/0/36currentstate:UPIPPacketFrameType:PKTFMT_ETHNT_2,HardwareAddress:000f-e200-002b……Last300secondsoutput:0packets/sec10bytes/sec0%Input(total):57packets,7838bytes0unicasts,50broadcasts,2multicasts,0pauses13Input(normal):52packets,-bytes0unicasts,50broadcasts,2multicasts,0pausesInput:5inputerrors,0runts,0giants,0throttles5CRC,0frame,-overruns,0aborts-ignored,-parityerrors2.端口下有錯包端口下有錯包有以下幾種可能的故障原因，可使用排除法定位：?端口本身硬件故障：通過將連接端口的線纜連接到配置相同且可正常工作的端口查看是否端口本身硬件故障。如果是端口本身硬件故障，請將線纜連接到可正常工作的端口。?鏈路上光模塊、光纖或以太網(wǎng)雙絞線故障：通過更換完好的光模塊、光纖或以太網(wǎng)雙絞線定位是否光纖或以太網(wǎng)雙絞線故障。如果是光模塊、光纖或以太網(wǎng)雙絞線故障，請更換完好的光模塊、光纖或以太網(wǎng)雙絞線。?對端配置問題，查看對端速率、雙工模式的配置是否和本端一致。如果對端速率和雙工模式的配置與本端不一致，請更新配置保證本端和對端速率和雙工模式的配置一致。如果通過上述方法仍然無法解決錯包問題，請前往步驟7。3.報文因匹配ACL被過濾(1)檢查端口、VLAN以及全局下是否配置請檢查端口了ACL或QoS策略的packet-filter（使用displaypacket-filter查看）、qospolicy（使用displayqospolicy查看vlanpolicy（使用displayqosvlan-policy查看及globalpolicy（使用displayqospolicyglobal查看了ACL或QoS策略的流分類而被丟棄，請參考ACL或QoS了ACL或QoS策略，如果配置了ACL或QoS策略，進入的報文是否因匹配流分類而被丟棄，包括端口下的），）以）。如果報文因匹配的配置方法通過更新配置使報文不被丟棄。(2)檢查是否因命令查看端口下是否配置ipsourcebinding或ipverifysource，使用displayipsourcebinding/displayipv6sourcebinding可以查看綁定表項信息。如果端口配置了ipsourceguard且述display命令發(fā)現(xiàn)沒有匹配報文的表項，請根據(jù)您使用的綁定表項的生成方法進一步匹配一些特性自動創(chuàng)建的的ACL而被過濾，在以太網(wǎng)接口視圖下使用displaythis了下面特性或使用關的具體命令查看：特性相??端口是否配置通過上排查。查看端口是否配置了Portal認證，戶，報文會被該端口丟棄。使用displayportalinterface可以顯示指定VLAN接口戶根據(jù)實際情況確定是否可以取消Portal認證：在二層以太網(wǎng)端口視圖下，使用undo沒有通過Portal認證的用或二層以太網(wǎng)端口的的Portal配置信息。請用portal命令，可以取消二層Portal認證配置；在端口所屬VLAN的對應VLAN虛接口下使用undoportalserverserver-name可以取消三層Portal認證。?使用displaydot1x命令查看端口是否使能部署功能，那未認證成功的用戶訪問除FreeIP以外的網(wǎng)段時就會丟包。請定位用成功用戶，且未認證成功用戶訪問的是否是FreeIP以外的網(wǎng)段來進一步確認丟包原因。4.端口被協(xié)議設置為block狀態(tài)使用displaystpbrief命令查看端口是否為discarding狀態(tài)，請根據(jù)stp的相關配置進一步排查。H3C建議您將連接配置為邊緣端口或關閉該端口的stp功能。了EAD快速部署。如果使能了802.1X的EAD快速戶是否是未認證?被stp設置為discarding狀態(tài)。如果端口被stp設置終端設備的端口14??如果端口屬于某個聚合組，使用displaylink-aggregationverbose命令查看聚合口的詳細信息，當該端口Status為Unselected狀態(tài)時，該端口無法收發(fā)數(shù)據(jù)報文。請定位端口成為Unselected狀態(tài)的原因，如聚合組內(nèi)成員端口的屬性類配置與參考端口不一致，進一步排查解決。查看端口是否被RRPP阻塞：使用為Down或Blocked時端口不能轉發(fā)數(shù)據(jù)。如果Portstatus為Down，請定位該端口成為Downshutdown，進一步排查解決；如果Portstatus為Blocked，請定位該端口成為Blocked狀態(tài)的原因，如主節(jié)點主于主環(huán)鏈路down，多歸屬Smartlink阻塞：使用為STANDBY或DOWN時端口不能轉發(fā)數(shù)據(jù)。如果State為DOWN，請定為端口成為DOWN了MonitorLink功能造成該端口DOWN，或該端口shutdown，進一步排查解決；如果State為STANDBY，請該設備SmartLink組的主5.配置相關丟包displayrrppverbose命令查看端口狀態(tài)，當Portstatus狀態(tài)的原因，如端口沒有接入線纜或端口被、副端口角色配置錯誤，或由子環(huán)廣播風暴抑制機制會臨時阻塞邊緣端口。?查看端口是否被displaysmart-linkgroup命令查看端口狀態(tài)，當State狀態(tài)的原因，如上行鏈路上的設備配置所在鏈路連接發(fā)生故障或端口被將、從端口互換。?在以太網(wǎng)接口視圖下使用displaythis命令查看端口是否在報文所屬VLAN中。如果端口不在報文所屬VLAN中，請加入該VLAN。將端口?使用displaymac-addressblackhole命令查看是否因為匹配了黑洞MAC地址表項被丟包。請根據(jù)實際情況確定是否可以取消該黑洞MAC。如果需要刪除該黑洞MAC，請使用undomac-addressblackholemac-addressvlanvlan-id命令刪除。displayqoslrinterface查看是否有端口限速的配置。如果端口有限速的配置，請查看令牌生成速度和突發(fā)流量配置值是否合理，可以通過使用qoslroutboundcir??使用committed-information-rate[cbscommitted-burst-size]命令調(diào)整令牌生成速度和突發(fā)流量配置值定位解決。在以太網(wǎng)接口視圖下使用displaythis命令查看端口是否有風暴抑制相關配置，包括廣播風暴抑制比（broadcast-suppression），組播風暴抑制比（multicast-suppression），未知單播風暴抑制比（unicast-suppression）。如果端口下配置了風暴抑制比，可以通過將風暴抑制比的數(shù)值調(diào)大定位解決。6.擁塞丟包如果通過前面步驟仍然沒有解決丟包問題，且通過displayinterface命令查看擁塞管理的相關內(nèi)容定位端口是否因擁塞丟包，并參考擁塞管理的內(nèi)容定位解決。到端口存在丟包，請參考如果通過上述方法仍然無法解決丟包問題，請前往步驟7。7.尋求技術支持如果上述檢查完成后故障仍無法排除，請聯(lián)系H3C的技術支持工程師。5.2.4故障診斷命令命令說明displayinterface顯示以太網(wǎng)端口的相關信息displaypacket-filter顯示ACL在報文過濾中的應用情況15命令說明displayqospolicy顯示用戶定義策略的配置信息displayqospolicyinterfacedisplayqosvlan-policydisplayqospolicyglobaldisplaythis顯示指定端口或所有端口上QoS策略的配置信息和運行情況顯示基于VLAN應用QoS策略的信息顯示基于全局應用QoS策略的信息在以太網(wǎng)接口視圖下使用此命令查看接口的當前配置displayipsourcebinding/displayipv6sourcebinding查看IPSourceGuard綁定表項信息顯示指定接口的Portal配置信息顯示802.1X的會話連接信息displayportalinterfacedisplaydot1x、相關統(tǒng)計信息或配置信息displaystp顯示生成樹的狀態(tài)和統(tǒng)計信息displaylink-aggregationverbosedisplayrrppverbosedisplaysmart-linkgroupdisplaymac-addressblackholedisplayqoslrinterface查看聚合口的詳細信息顯示RRPP的詳細信息查看SmartLink組的信息查看黑洞MAC地址表項信息顯示端口限速配置情況5.3三層轉發(fā)丟包故障5.3.1故障描述設備三層轉發(fā)丟包，即發(fā)送端IP地址和目的端IP地址不在同一網(wǎng)段內(nèi)，通信過程中有丟包。165.3.2故障處理流程圖7三層轉發(fā)丟包故障診斷流程圖5.3.3故障處理步驟1.檢查端口是否有故障根據(jù)5.2二層流量轉發(fā)丟包一節(jié)的故障定位處理方法，定位是否是設備端口故障（包括端口硬件故障和端口配置故障）：?如果是端口故障，請按照5.2二層流量轉發(fā)丟包一節(jié)的故障處理思路進行處理。?如果不是端口故障，則執(zhí)行步驟2。2.查看ARP表項是否正確使用displayarp命令查看設備上是否學習到網(wǎng)關設備的ARP表項、學習到的ARP表項是否?如果設備上未學習到ARP表項或?qū)W習到的表項錯誤，通過打開debuggingarppacket查看設備ARP表項學習來定位ARP問題的對于未學習到ARP表項，可以使用arpstatic命令手工添加靜態(tài)ARP表項。正確：情況，原因。?如果設備上ARP表項學習正確，請執(zhí)行步驟3。3.查看路由表項是否正確使用displayiprouting-table命令查看設備上學習的路?如果設備上學習到的路正確，請根據(jù)您使用的具體的路由協(xié)議進行進一步排查。?如果設備上的路4.尋求技術支持由信息是否正確：由信息不由信息正確，請執(zhí)行步驟4。如果上述檢查完成后故障仍無法排除，請聯(lián)系H3C的技術支持工程師。175.3.4故障診斷命令命令說明打開ARP的報文調(diào)試信息開關顯示ARP表項debuggingarppacketdisplayarpdisplayiprouting-table顯示路由表中當前激活路由的摘要信息5.4PoE供電異常5.4.1故障描述PoE機型PoE供電不正常。5.4.2故障處理流程圖8PoE供電異常故障診斷流程圖185.4.3故障處理步驟?S5500-28C-PWR-EI、S5500-52C-PWR-EI、S5500-28C-PWR-SI、S5500-52C-PWR-SI各包含PoE+和PoE兩種機型：PoE+機型單端口最大PoE供電功率為30W，PoE機型單端口最大PoE供電功率為15.4W。?不同型號設備的顯示信息不同，請以設備實際情況為準。通過下面命令查看供電細節(jié)：(1)在任意視圖中執(zhí)行displaypoedevice命令查看顯示PSE的工作狀態(tài)。如果工作狀態(tài)顯示為faulty，則說明PSE故障。如下所示：<Sysname>displaypoedevicePSEIDSlotNoSubSNoPortNumMaxPower(W)StateModel41024370faultyPD67024以上顯示信息說明該PSE存在故障。此時，請使用poeupdate命令升級PSE軟件。升級方法如下所示：<Sysname>system-view[Sysname]poeupdatefullver_3_9_0_release.binpse4ThiscommandwillfullyupdatefirmwareonthespecificPSE(s),Continue?[Y/N]:ySystemisdownloadingfirmwareintothehardware.Pleasewait..................UpdatefirmwareonthespecificPSE(s)successfully!以上顯示信息說明PSE軟件升級成功。再次執(zhí)行displaypoedevice命令查看顯示PSE的工作狀態(tài)。如果工作狀態(tài)顯示為on或off，則說明PSE故障已修復。如下所示：[Sysname]displaypoedevicePSEIDSlotNoSubSNoPortNumMaxPower(W)StateModel41024370offPD67024(2)在任意視圖中執(zhí)行displaypoepse命令查看顯示PSE的信息。確認當前整機供電功率、平均功率、峰值功率是否正常、PSE檢測非標準PD功能是否打開等。如下所示：[Sysname]displaypoepsePSEID:4PSESlotNo:1PSESubSlotNo:0PSEModel:PD67024PSEPowerEnabled:enabledPSEPowerPriority:-PSECurrentPower:0WPSEAveragePower:0WPSEPeakPower:0W