These errors indicate a hardware problem or one of these problems:
Type 1 cabling
Hardware problem of an external connected device
Clock failure on the Supervisor
These errors are most commonly caused by a physical layer problem that is responsible for the back-up of a considerable amount of traffic to the internal K1 gigaports. K1 ASICs are the main chips that control the switch. Generally, the blockedTXQcount increments due to a configuration issue or faulty cabling.
In a normal environment, the Tx queue can only be blocked for approximately 20 seconds. A longer blockage indicates a significant problem. As a result, the blocked Tx queue count increments if the Tx queue has not drained for the gigaport in 35 seconds.
Conditions that can cause the blockedTXQcount to increment include front panel port misconfigurations, a duplex mismatch, cabling, faulty ports, faulty cabling, a bad line card and hardware problems related to an externally connected device.
To resolve this error, perform any of these workarounds:
Issue the show port counters command and verify whether values under the Xmit-Err column increases. If the value under this column increases then the problem is that traffic from a high bandwidth link being switched to a lower bandwidth link, or traffic from multiple inbound links beingswitched to a single outbound link. This error is anindication that the internal send (Tx) buffer is full. Check the Duplex and speed values configured.
Reseat the module and perform the diagnostic test.
Replace the cable on the port that generates the errors with a different, known good cable.
Reset the blade on the slot that generates the errors and the Supervisor Engine.
Hi,I want to access a server using the public IP from the same internal network.Please the config belowip dhcp excluded-address 192.168.0.1 192.168.0.100
ip dhcp excluded-address 192.168.3.1
ip dhcp pool HOME
network 192.168.0.0 255.255.255.0
Team, I will have a Mellanox switch with a NVIDIA MMA1L30-CM Optical Transceiver 100GbE QSFP28 LC-LC 1310nm CWDM4 on one end of a 100GB SM fiber link and a Nexus N9K-C9336-C-FX2 with a QSFP-100G-SM-SR on the other end. Can someone tell me i...
Hi All, I have an SDA fabric using closed mode authentication and looking to setup a fabric site wide voice VLAN. I created a voice IP pool in the fabric and noticed that its not set as the default voice VLAN on my fabric edge ports (the default voic...
I'm trying to understand the difference between the device ID, system IP & local system IP that you get from a REST API poll of the device API? Can these be different and if so under what conditions? Thanks