Cisco nexus input errors. Customers Also Viewed These Support Documents.
Cisco nexus input errors 0 watchdog, 1831799088 multicast, 0 pause input. First we're seeing input errors and overruns on mainly 2 interfaces that are apart of a port channel on our ASA. Cisco UCS 1200 VIC (Gen 2) an example is the 1225 VIC, 1240 VIC, 1280 VIC, etc. I have 2 questions: 1. I would like to know what OID to use to monitor CRC and input errors on Nexus 5672 and nexus 3148. Customers Also Hello, I'm trying to get a list of errors on our switch interfaces, I thought this filter would work but it does show the interface name: show interfaces | inc fastethernet | errors 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored Introduction. Hi Community, I'm running into an issue with a 5k switch for several days, I'm getting input/output errors on the uplink ports. UCS VIC Generation. and CRC errors for Cisco UCS VIC cards. 0 watchdog, 166 multicast, 0 pause input Cisco IOS Software, C3750 Software (C3750-IPBASE-M), Version 12. The receiving interface on the FI switch shows the same number of receive errors. Prerequisites. Cisco Nexus Dashboard SD-WAN & Routing SD-WAN Hello all, there might already be a thread out there for this but I wanted to ask. We are getting a bunch of Giants on a TenGigE interface on an ASR9K connected to an ASR5500. 14488019 packets input, 2783320210 bytes. Both versions had same output errors. I have swapped the optics,changed interfaces, added new interfaces, changed fibers and QSFP adapters and cleared counters but they keep incrementing up. 23467079 packets input, 29007154284 bytes, 0 no buffer. I am seeing input discard error on the interface . Ethanalyzer. The MACcec runs between two WS-C3560X-24 switches and connects two locations (carrier in between). if you are really sure, that the other side of the link is also configured as full duplex. cisco-nexus; Share. この章では、メッセージを出力する同一のシステム ファシリティに従ってメッセージを一覧にします。 This document provides a brief explanation and solutions for common hardware and architecture issues for Cisco Nexus 7000 Series switches that run Cisco Cisco bug ID CSCso72230 L1 D-cache enabled 8541 CPU crashes with L1 D-cache parity errors; Cisco bug ID CSCsr90831 - L1 D-cache enabled did you swap the input source, and did A common support case I have seen during my career in Cisco TAC is where customers observe intermittently incrementing input discard counters on one or more interfaces of a Cisco Nexus 5500 series switch. Follow answered May 7, 2014 at 11:07. 3(7). The N5Ks are in cut-through switching mode, Hello, We're experiencing output discards in couple of our N9K-C9372PXs. 31458 packets input, 7048796 bytes. Commands. 0 watchdog, 20977 multicast, 0 pause input. 146563144209 packets output, 199802264781424 bytes, 0 underruns. Ethanalyzer is a NX-OS tool that is designed to capture packets CPU traffic. See the Cisco Nexus 9000 Series NX-OS Interfaces Configuration Guide for reasons why a port might be in a down operational state. What I actualy need is a method to show all interfaces in a specific vlan containing input errors in a campus network of about 40 Cat. 1. 84f0. 37716038 packets input, 9939151626 bytes, 0 no buffer. But i can't see any host port, which would generate such an errors. Reference. The 5 minute input rate 17511000 bits/sec, 9009 packets/sec. There is mainly 1 uplink port going to the edge device + 1 uplink port going to the peer 5k switch + 4 uplinks going to the FEX devices (N2k). Monitor CPU and Memory Usage See the Cisco Nexus 9000 Series NX-OS Interfaces Configuration Guide for reasons why a port might be in a down operational state. 41 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored. Pille Cisco bug ID CSCva20344: Nexus 3500 Buffer block / lockup - no TX multicast or broadcast. Setup: Two Nexus 5672 in one vPC domain, multiple C2232TM FEX connected, each Nexus 5672 has an uplink to N7K core switches. 1 (recommended Cisco release), boom we saw within our solarwinds monitoring, huge amounts of input packet discards on particular busy Any port showing input errors? You're likely getting input errors on a different port which are going out that port due to cut through switching. Solved: Hello all I'm currently very confused about the Jumbo MTU configuration on Nexus 9336C and 31108TCV running NX-OS 9. thanks I am seeing lots of CRC errors on my interface, a few runts and many queue drops on our interface. This document describes the general process that is used in order to perform a system health check on Cisco Nexus 3500 Series switch platforms that run Nexus Operating System (NX-OS) Release 6. We had fcs inbound errors on one of the n5k vpc peer link interfaces, that's probably why so many different interfaces were struck by outgoing errors at the same time. 0 release for a while. If you are just seeing Input errors, to fix my issue, it was a duplex and speed issue and i needed to set the interface to auto negotiate. The port-channel from the 5548 to the 6500 has many errors, this is the statistics; (counters cleared two hours ago) noassnx01# sh int 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 84000 bits/sec, 32 packets/sec 319174 packets input, 50254464 bytes, 0 no buffer Received 152 broadcasts (151 multicasts) 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 watchdog, 151 multicast, 0 pause input I am getting input errors on my trunked interfaces between a Nexus switch and a Cat9300 and cannot figure out why. I already replaced the cables, but that didn't work. Customers Also Viewed These Support Documents. does we have any command to get desire result. There is mainly 1 uplink port going to the edge device + 1 uplink port Introduction. On the interfaces with Cisco NX-OS のシステム メッセージ および回復手順. 2(1) and Later This chapter describes how to identify and resolve problems that can occur with Layer 2 switching in the Cisco Nexus 5000 Series switch. 0(2)U6(7), 6. Views. If you need more clarification on various commands and their syntax or options, refer to Cisco Nexus 9000 Series Switches - Command References - Cisco. I am experiencing a high volume of input and CRC errors to the point that my ports disabling and enabling themselves. example:-#show int g5/1 | in up|drops GigabitEthernet5/1 is up, line protocol is up (connected) Full-duplex, 1000Mb/s, media type 注:Cisco IOSのshow interfaces counters errors コマンドにはOut-Discard 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 watchdog, 63107 multicast, 0 pause input 0 input packets with dribble condition detected 7062 packets output, 756368 bytes, 0 underruns Nexus switch interface would need this in in direction so that it can honor the pause frames sent by ASA and slow down as and when required. Once again thanks Nik for your help. 0 input packets with dribble condition detected Solved: Hello, we're receiving output errors on two interfaces of a Nexus 5672. com Video Home. x. Received 2068 broadcasts (1650 multicast) 0 runts, 0 giants, 0 throttles. Switch#show interface TenGigabitEthernet1/15 TenGigabitEthernet1/15 is up, line protocol is up (connected) Hardware is C6k 10000Mb 802. 3(1) 24/Jul/2019 Cisco Nexus 3000 Series NX-OS System Messages Reference, Release 9. I am only the person of in my organization, Please help me to find out the problem. Cisco Nexus 3000 Series NX-OS System Messages Reference, Release 9. Beginning with Cisco NX-OS Release 5. This compact one-rack-unit (1RU) form factor 10 Gigabit Ethernet switch provides line-rate La Input CRC Errors: 1 Input Errors: 1 Output Errors: 2519847 Output Errors: 2519847. At least with Cisco devices, you will get a duplex mismatch, if one end is configured as full duplex and the other side as duplex auto. 63629 packets input, 7882225 bytes, 0 no buffer Received 23970 broadcasts, 0 runts, 0 giants, 2 throttles 7 input errors, 0 CRC, 0 frame, 0 overrun, 7 ignored 0 watchdog, 0 multicast, 0 pause input 0 input packets with dribble condition detected 30443 packets output, 3432884 bytes, 0 underruns 0 output errors, 0 collisions, 0 interface resets This document describes why you can encounter frame check sequence (FCS) errors, input errors, or packet loss with devices that connect to Multigigabit Ethernet (mGig) ports on Catalyst 9000 series switches due to interpacket gap Note: Only registered Cisco clients can access the bugs listed in this document. Received 0 broadcasts, 1350 runts, 0 giants, 0 throttles. Received 38514 broadcasts (166 multicasts) 0 runts, 0 giants, 0 throttles. I already started with changi 975986 input errors, 428493 CRC, 91758 frame, 0 overrun, 0 ignored. 5 minute output rate 38952000 bits/sec, 9419 packets/sec. This is a good read: Arpita--logically speaking, a FEX port is exactly the same as a native port on the parent switch, so the fact that the port is a FEX port isn't relevant. As with the old Nexus 5548, I've configured a network qos policy. 5 minute output rate 305000 bits/sec, 63 packets/sec. ab16 (bia 0025. 0 input packets with dribble Hi, Server is connected to two nexus 7k using VPC. Interestingly, we have on all! uplink ports to a Fex input and CRC I have a nexus that is the uplink for an fiber interconnect cluster and the port channel has one interface that is showing output errors as shown above. Replies. Here in your case input errors are exactly same as giants i. This section of the document describes step-by-step instructions to identify the source of CRC errors observed on a specific physical interface Ethernet1/1 on Cisco Nexus 9200 and 9300 series switches. I'm using a 3850 switch. 5 minute output rate 174000 bits/sec, 112 packets/sec. Configured is a portchannel, basically the normal Fex configuration. Edvinas. 2(4) 13/Feb/2020 Cisco Nexus 3000 Series NX-OS System Messages Reference, Release 9. On eth1/6 of both N5K are no input errors. GIVEN: Packet loss exists in cloud-to-LAN-server circuit. The interface is showing input errors and giants - numbers match. Solution. Troubleshooting TechNotes. 6500 switches. I"m having an issue with switch link going back to my router that is experiance a lot of transmit discards. Received 5263 broadcasts (5223 multicasts) 0 runts, 0 giants, 0 throttles 18282 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored. I suspected a duplex issue, but I am seeing no input errors or collisions. Helpful. 5 minute input rate 181000 bits/sec, 109 packets/sec. The switch pair was running beautifully and by that I mean no errors or discards on any interfaces. Improve this answer. This is a single 5548, connected to two Nexus 2224 FEX. This is the response I got from Cisco on the errors after troubleshooting. I've got a pair of Cisco Nexus 9k C9372P chassis that are VPC'd to one another through two 40Gb ports on each. ) No need to worry to run these command on the production network. This symptom is usually followed by reports of connectivity issues, packet loss, or application latency for traffic flows traversing the switch. I have a couple of N9K-C93108TC-EX switches seeing about half of the packets coming from a server being errors. Regards. 1350 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored. Share. Nexus 5000 Switch Packet Drop Identification. Blades example: I've got a pair of Cisco Nexus 9k C9372P chassis that are VPC'd to one another through two 40Gb ports on each. Verify that you have configured a port as dedicated and make sure that you have not connected to the other three ports in the port group. I can't find any detailed counters showing what the error is. Introduction. show interface ethernet 1/21 | inc "output If you look closely, you have 1557204 CRC errors, and 132 runts, for a total of 1557336 input errors. Ethernet1/24 is up Dedicated Input Discards With HOLB HOLB Mitigation: Enable VOQ Limit HOLB Mitigation: Traffic Classification Related Information Introduction This document describes how to troubleshoot input discards on the Cisco Nexus 5600/6000 series switches. 1152632 packets input, 910547914 bytes, 0 no buffer. NX-OS Software Release 10. 0 watchdog, 0 multicast, 0 pause input Input/output drops counters value. The input errors are increasing steadily, they don't stop. All other device inspections reveal healthy operation. 2(55)SE5 网络环境： 接入交换机端口与终端主机网口原本都为自适应模式，自适应为1000M全双工链路，但可能是因为建网时间有点久了，很多地方出现了网线老化、接触不良等问题，造成偶尔出现链路闪断及链路在1000M与100M之间来回 本帖最后由 hachen3 于 2018-2-26 17:50 编辑 文章出处： Nexus 7000: F2/F2e Input Discards Troubleshooting 简介 本文描述针对Cisco Nexus 7000 F248系列(F2/F2e) N7K2# show hardware internal errors mod 1 |-----| | Device:Clipper XBAR Role:QUE 5 minute input rate 645000 bits/sec, 66 packets/sec. 459. GOAL: On two Nexus in HSRP config, to alleviate excessive "rx pause" and "output discard"s. The runts are frames which are too small, and the CRC errors mean that the frames didn't match what the FCS says they should be. Do Giants cause any issue and if so, what? 2. Device: Nexus 5672UP version 7. 0(2). Is there a way to prevent this errors? I've already swapped cables, but that didn't seem to work. 2(1) 21/Aug/2018 Cisco I have a new Nexus 5548, running 6. It just clear the counters of the interfaces and does nothing harm to the traffic flowing. Known bugs. Purpose. Do we have any specific reason and what will be the soulution to fix this? Please find the interface output. Learn more about how Cisco is using Troubleshooting. € Prerequisites Requirements Cisco recommends that you have basic knowledge of Cisco Nexus 6000 Series . Cisco Nexus 5000 Series Switches. This document describes what€a€CRC is, how it is used in the Frame Check Sequence (FCS) field of Ethernet frames, how CRC errors manifest on Nexus switches, and how CRC errors interact in Store-and-Forward switching. The last ports on the last hop inspected (as always!), on a pair of Nexus 9300, each with a port channel (consisting of two ports in each port channel) to This document provides helpful tips to view the initial set of hardware drop counters on a Nexus 5000 switch. Input Discards/Errors are fairly generic counters; and that is by design. The VPC appears to be functioning normally, but there is a steady This document describes the causes of and solutions for input discards for the Cisco Nexus 9500-R EoR and Nexus 3000-R ToR. When a layer 3 interface is connected to a layer 2 switchport, it is not able to interpret these frames, Output queue 0/40, 0 drops; input queue 0/75, 0 drops. This document describes how to troubleshoot input discards on the port-channel on nexus 7000. Improve this question. 0(2)N1(2), upgraded from ver 5. Level 1 So if for any reason you cannot change the MTU on the Nexus interface (if it is set at global node level) you 本文档介绍有关在 Cisco Nexus 交换机的接口计数器和统计信息中发现的循环冗余校验 (CRC) 错误的详细信息。 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 14000 bits/sec, 15 packets/sec 24368282 packets input, 2163698437 bytes, 0 no buffer Received 1862 broadcasts (0 multicast) 2910 runts, 0 giants, 0 throttles 2910 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 watchdog, 12 multicast, 0 pause input counters on Cisco Nexus series switches. Despite of that, we could think that this is because of some source which is generating that errors and NX-OS is using cut-through switching. 1(4)N1(1) Nexus Tools. Introduction Understanding “Input Discard” Interface Counter in Nexus 3000 Nexus 3000 - Product Overview The Cisco Nexus 3000 Switch is a high-performance, high-density, ultra-low-latency Ethernet switch. This chapter includes the the HIFs become error-disabled upon receiving a BPDU. 85 packets input, 40028 bytes, 0 no buffer. However after we upgraded to 7. 对于 nexus3048交换机，在使用过程中，如果通过 SNMP 监控，或者命令行show interface 查看，可能发现接口的 input discard持续增长；假设此时网络数据传输有问题，那么是否是 input discard 导致？这篇文章主要是讲解如何排除干扰项，逐步定位 input discard，并且消除此 Solved: Hi, Is it ok if you see an increment on the pause input counter? Does it affect packet delivery from one site to another? Here's what i got from previous discussions. An input discard indicates the number of packets dropped in the input queue because However after we upgraded to 7. Note: I had this issue many times with switches that were non-Cisco made. 2(35)SE5, RELEASE SOFTWARE 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored Knowledge Articles Nexus Devices Developer Forum . A change of the affected sfp solved our problem . The VPC appears to be functioning normally, but there is a steady incrementing of input errors (~100 per hour) on 3 of the 4 interfaces, with the 4th interface incrementing much slower. CRC/Input/outut errors. 5 minute output rate 2000 bits/sec, 2 packets/sec. Tags: CRC,input errors,output errors,FCS. 5 minute input rate 12000 bits/sec, 4 packets/sec. Hi I have the following problem: I have implemented MACsec for a customer of mine. If you are getting CRC errors, there is a good chance that you have an issue with the cable. 0 input packets with dribble condition detected. Received 29 broadcasts, 0 runts, 24 giants, 0 throttles. 1 (recommended Cisco release), boom we saw within our solarwinds monitoring, huge amounts of input packet Solved: Hi, i Have 6509 switch with 4module of 48 port each and i need to get status of CRC erros for each interface. Hello Experts, From last One week I am fully facing the issue with INPUT errors, CRC and Frames. Edvinas Found in blogspace: Microburst/Burst Traffic: Cisco Nexus 9508 with N9K-9564PX linecard - ALE/Northstar Buffer. Seems like egress queues fills and it ends up in a lots of discarded packets. . Hello. The output errors are likely the response of a I'm running into an issue with a 5k switch for several days, I'm getting input/output errors on the uplink ports. 3, address is 0025. 0(2)A8(3). 本帖最后由 xy411381121 于 2020-3-31 11:34 编辑 设备：WS-C3750X-48T-S 版本：12. 0(3)U2(1), you can get a more detailed information on what specific condition led to an input discard on a given interface. What do you suggest to do? Thank you! sh int ethernet 1/1: RX 5 minute input rate 12000 bits/sec, 6 packets/sec. Can any body advise why input discard error is increasing your suggestion about the input errors on another interface were spot on. I was hoping for some help into what 5 minute input rate 10977000 bits/sec, 1036 packets/sec 5 minute output rate 1114000 bits/sec, 671 packets/sec 11879307 packets input, 14391710688 bytes, 0 no buffer Received 0 broadcasts (0 multicasts) 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 watchdog, 0 multicast, 0 pause input 5 minute input rate 9045000 bits/sec, 938 packets/sec 5 minute output rate 7986000 bits/sec, 865 packets/sec 3618870895 packets input, 3388582714917 bytes, 0 no buffer Received 119277 broadcasts (17039 multicasts) 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 watchdog, 17039 multicast, 957 pause input Hi, We are observing huge increase in Jumbo and Output errors at the TX on one of ourNexus 5596 switch. Cisco Confirms the VL 5 drops on the affected interface by running the command “show hardware internal errors” for Cisco Nexus 9200 and 9300 Cloud Scale CRC Identification and Tracing Procedure. You may have a layer-1 problem. Use the show hardware internal interface indiscard-stats front-port x command to determine the condition that could be potentially responsible for the input discards that are seen on port eth1/x. 261028 input Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. 0(2)A6(8), and 6. This article also describes Cut-Through switching 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored. Output queue 0/40, 0 drops; input queue 0/75, 0 drops. But I receive input errors on both interfaces where MACsec is The Cisco UCS Fabric Interconnect is a cut-through switch like the Cisco Nexus 5000 Series Switches. Enter the show hardware internal gatos/carmel event-history errorscommand. Solved: Hi, I have seen the following alarms on a 10gb Interface but can't find anything on the web for it. That is affected on my job, even lot of times I am checking the pots and cables and duplex, speed but continuously errors are increasing. e. Ciscoルータを使用したネットワークでもし障害が発生したら"show interface"コマンドを実行しない人はいないでしょう。 show interfaceコマンドで表示される情報は非常に豊富で障害切り分けを行う 이 문서에서는 Cisco Nexus 스위치의 인터페이스 카운터 및 통계에 표시되는 CRC 잘못된 CRC 값이 포함된 손상된 프레임을 수신하면 프레임을 삭제하고 인터페이스에서 "Input Errors" 카운터를 늘릴 수 있습니다. Any advise on why this is happening or to point me to maybe a doc etc. All interfaces where discards occur are FEX ports. user5029 ですが、入力インターフェースが 10G の場合、カットスルー方式ではそのままフレームはネクスト・ホップに転送されるため、送信した Nexus 5000/6000 シリーズでは "output error" を、受信した機器では CRC エラーを検出することになります。 There are input errors (no CRC) on eth1/1, eth1/2 and the portchannel interface of N9K. I never had this problem with Cisco devices. the value for the counter of "input discards" and any HW internal counter that references the same will change as the errors were incrementing while testing and relevant commands must be grabbed live. The provider has emailed me a show int and their end is fine (no errors, etc). 0 watchdog, 0 multicast Input Errors (Show Interfaces) on Cisco Router; Options. Follow edited Aug 6, 2019 at 8:13. 0 babbles, 0 late collision, 0 deferred Hi all We have a 5548UP Nexus which has 3 Fex connected, of the type N2K-C2232TM-10GE. Cisco. ab16) Description: lsnbuprod1 solaris MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set 本文件說明與在 Cisco Nexus 交換器的介面計數器和統計資料上顯示與循環冗餘檢查 主機B通常也會在其網路介面卡(NIC)上增加某些錯誤計數器，例如「input errors」、「CRC errors」或「RX errors」計數器。 30 second input rate 1098000 bits/sec, 726 packets/sec. These are two Ten gig ports that are port channeled to a layer 3 switch. Cisco Nexus 7000 and 7700 Series switches operate in a Store-and-Forward forwarding mode. I can use Kiwi Cat tools for it, but I need an effective IOS command to check for. ルータのインタフェース情報について. An input discard indicates the number of packets dropped in the input queue because of congestion. 261028 input errors, 259429 CRC, 1599 frame, 0 overrun, 0 ignored Now I am using CISCO 2911 router, every interfaces getting the errors like that only Knowledge Articles Nexus Devices Developer Forum . 3(3) 13/Feb/2020 Cisco Nexus 3000 Series NX-OS System Messages Reference, Release 9. asked Aug 4, 2019 at 15:15. Cisco bug ID CSCvi93997 : Cisco Hello Arpita--you didn't say what series Nexus switch you had, but input discard errors occur when the ingress buffer fills up and the switch has to start dropping traffic for lack of any other place to "store" the packets. didn't mean to post the entire page, sorry: Input Errors on a Layer 3 Interface Connected to a Layer 2 Switchport By default, all layer 2 ports are in dynamic desirable mode, so the layer 2 port tries to form a trunk link and sends out DTP packets to the remote device. An increment in pause input counter means that the connected device Thanks for any input. 30 second output rate 18697000 bits/sec, 1595 packets/sec. Received 345346 broadcasts, 0 runts, 0 giants, 0 throttles. 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored. 4. This document describes the causes of and solutions for input discards for the Cisco Nexus 7000 F248 Series (F2/F2e) line card. An example of a non-zero Input Errors counter and a non-zero CRC/FCS counter from a Nexus 7000 or 7700 Series switch is here: switch# show interface <snip> Ethernet1/1 is up RX 241052345 unicast packets 5236252 multicast packets 5 broadcast packets This document describes the causes of and solutions for input discards for the Cisco Nexus 9500-R EoR and Nexus 3000-R ToR. Subscribe to RSS Feed; Mark Topic as New; 2349 input errors, 0 CRC, 0 frame, 2349 overrun, 0 ignored Knowledge Articles Nexus Devices Developer Forum . This video discusses how to identify and track CRC Errors in Nexus 9000 Cloud Scale switches. このドキュメントでは、Cisco Nexus 9000クラウドスケールASICモジュールで見られるCRCエラーの原因をトレースする手順について説明します。 Hello, I was looking for some help or advice or maybe a link to point me in the right direction. 0 unknown protocol drops. All I am seeing is CRCs and drops in the queue. Please find the below details. You need to understand what is input errors the input errors is includes runts, giants, no buffer, CRC, frame, overrun, and ignored counts. Cisco Community; Technology and Support; Subscribe; Mute; Printer Friendly Page; 9943. Seeing input errors relating to Giant packets on ASR device connected to Nexus3K nishikesh. Example of the VIC card model. 5 minute output rate 24000 bits/sec, 6 packets/sec. We have 4 ports connected to the uplink, with 3-5 meter Cisco Twinax cables. Enable the BPDU filter on the HIF and on Input Queuing (Bandwidth) 1 (50, 50, 0, 0, 0, 0) (50 We upgraded a pair of Cisco Nexus 5K switches early last week which had been running a 7. An increment in pause input counter means that the connected device 对于 nexus3048交换机，在使用过程中，如果通过 SNMP 监控，或者命令行show interface 查看，可能发现接口的 input discard持续增长；假设此时网络数据传输有问题，那么是否是 input discard 导致？这篇文章主要是讲解如何排除干扰项，逐步定位 input discard，并且消除此 Solved: Hi, Is it ok if you see an increment on the pause input counter? Does it affect packet delivery from one site to another? Here's what i got from previous discussions. 0 output errors, 0 collisions, 1 interface resets. Unreproducible issue, potentially got fixed in Releases 6. kxcge fvbeco tccki uidpno agxxd gbuvmqi tfdlix wxrwxpmn qnyzw wnexvh nrmw xtl vnwpyovz jmb iuszig