06-04-2022 02:20 PM
When I do a sh int counter errors I see this errors IntMacTx-Er.
Can please anyone correctly explain or send link to official document: what IntMacTx-Er means.
06-04-2022 02:30 PM
What model of sw you have?
06-04-2022 02:37 PM
Nexus device. You can find output of this command here: https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus7000/sw/interfaces/command/cisco_nexus7000_interfaces_command_ref/show_commands.html#wp3038965280
switching mode: Cut-Through
Just explain of IntMacTx-Err interesting
06-04-2022 02:35 PM
Hi
IntMacTx-Er - Interface mac TX - Transmission error
IntMacRx-Er - Interface mac RX - Reception error
There´s a Bug the increments this value without necessary a problem.
01-06-2025 07:58 AM
reading the but notes, i'd like to mention
a) N9K5 specific
b) not "not necessary a problem" but "contact TAC and narrow down the faulty FM which needs a reboot"
No offense, maybe Cisco edited the bug-notes in the meantime!?
01-06-2025 08:28 AM
since the original documentation seems to be "incomplete" somehow...
I'll add some content to this old thread since the subject fits perfect...
I have two switches, N9K, as VPC-Pair connecting two different Servers via VPC/LACP:
A# show int e1/7,e1/23 counters errors
--------------------------------------------------------------------------------
Port Align-Err FCS-Err Xmit-Err Rcv-Err UnderSize OutDiscards
--------------------------------------------------------------------------------
Eth1/7 0 0 1270786 0 0 0
Eth1/23 0 0 1270786 0 0 0
----------------------------------------------------------------------------------
Port Single-Col Multi-Col Late-Col Exces-Col Carri-Sen Runts
----------------------------------------------------------------------------------
Eth1/7 0 0 0 0 0 0
Eth1/23 0 0 0 0 0 0
----------------------------------------------------------------------------------
Port Giants SQETest-Err Deferred-Tx IntMacTx-Er IntMacRx-Er Symbol-Err
----------------------------------------------------------------------------------
Eth1/7 0 -- 0 1270786 0 0
Eth1/23 0 -- 0 1270786 0 0
----------------------------------------------------------------------------------
Port InDiscards
----------------------------------------------------------------------------------
Eth1/7 0
Eth1/23 0
--------------------------------------------------------------------------------
Port Stomped-CRC
--------------------------------------------------------------------------------
Eth1/7 0
Eth1/23 0
and
B# show int e1/7,e1/23 counters errors
--------------------------------------------------------------------------------
Port Align-Err FCS-Err Xmit-Err Rcv-Err UnderSize OutDiscards
--------------------------------------------------------------------------------
Eth1/7 0 0 1349123 0 0 0
Eth1/23 0 0 1349123 0 0 0
----------------------------------------------------------------------------------
Port Single-Col Multi-Col Late-Col Exces-Col Carri-Sen Runts
----------------------------------------------------------------------------------
Eth1/7 0 0 0 0 0 0
Eth1/23 0 0 0 0 0 0
----------------------------------------------------------------------------------
Port Giants SQETest-Err Deferred-Tx IntMacTx-Er IntMacRx-Er Symbol-Err
----------------------------------------------------------------------------------
Eth1/7 0 -- 0 1349123 0 0
Eth1/23 0 -- 0 1349123 0 0
----------------------------------------------------------------------------------
Port InDiscards
----------------------------------------------------------------------------------
Eth1/7 0
Eth1/23 0
--------------------------------------------------------------------------------
Port Stomped-CRC
--------------------------------------------------------------------------------
Eth1/7 0
Eth1/23 0
Server 1 is connected by A.e1/7 and B.e1/7
Server 2 is connected by A.e1/23 and B.e1/23
=> no other issues at "ethernet-interface"-level like QoS-Drops etc.
=> since both switches count similar numbers
=> and both switches count local identical errors at both ports (which belong to different VPC-Port-Channels!)
version 10.3(5) Bios:version 01.09
interface Ethernet1/7
switchport mode trunk
channel-group X mode active
no shutdown
interface port-channelX
switchport mode trunk
vpc X
interface Ethernet1/23
switchport mode trunk
channel-group Y mode active
no shutdown
interface port-channelY
switchport mode trunk
vpc Y
(both ports are VLAN-Trunks with identical "allowed-vlan"-lists)
This is a "TX" = "Transmit"-Issue => but not of an independent port.
There are no "InDiscards" or "Stomped-CRC" Errors at any other port.
I'd guess:
...some kind of broadcast which the switch needs to propagate to both Ports but fails for "unknown" reason...
but there is now VLAN only active at _three_ ports [1x incoming, and both ports as outgoing] so other interfaces would would count the same amount of TX-Errors - since there are no other interfaces => we can rule out flooding.
Any idea, what could happen inside the switch, it's a non-modular N9K-C93180YC-FX3...
01-06-2025 08:55 AM
...show hardware internal"-stuff doesn't count any error
Action-Plan:
* watch error# - do the increase or not.
btw.
* Spanning-Tree stable, last Topology-Change months ago...
* no "SPAN (monitor session)" configured...
06-04-2025 01:31 AM - edited 06-04-2025 01:32 AM
Hi r.heitmann,
Almost same configuration for me and kind of the same errors.
2 x Nexus C9332D-GX2B in VPC (version 10.4(4)M)
2 x 100Gb interface (Official 100Gb SR4 tranceivers - one on each Nexus in the VPC) forming a LACP aggregate to a Fortigate (Fortinet official 100Gb SR4)
Interface in trunk mode with multiple VLAN
IntMacTx-Er on the Nexus side (for the interface and the Port-channel)
And on the Fortigate side:
==== Switch Error Counters =====
rx_err :4922783
rx_crc_err :0
rx_len_err :0
rx_carrier_err :0
rx_over_err :6352441
rx_under_err :0
rx_drop_pkts :0
tx_collision_err:0
tx_drop_pkts :0
I have other LACP port-channel with other Nexus (N9K-C93180YC-FX3) and Netapp Device with the same kind of configuration and tranceivers and no errors on theses ports.
It seems to have no impact on the network traffic, we don't see any problem. But still annoying to have these errors counters increasing.
I will continue to investigate.
Regards.
Nicolas
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide