topic BL860 i4 LOM Inbound Errors in Integrity Servers

BL860 i4 LOM Inbound Errors

tony22 — Mon, 16 Sep 2024 09:24:22 GMT

BL860 i4 LOM lan* Inbound Errors=1904, nwmgr and netstat -ni 输出都能看到这个Inbound Errors报错信息，清除计数为0 ，每天增长为300左右，系统日志没有报错，OA或iLO也没有报错。

Google Translated:

BL860 i4 LOM lan* Inbound Errors=1904, nwmgr and netstat -ni output can see this Inbound Errors error information, the clear count is 0, and increases to about 300 every day. There is no error in the system log, OA or iLO.

Re: BL860 i4 LOM Inbound Errors

jsm6 — Mon, 16 Sep 2024 09:30:55 GMT

Hi,

1.Are you seeing "Inbound errors" on only one LOM port or multiple?
2.You mean to say, even if count is cleared it increases by 300 counts everyday?
3.Is there any Virtual connected in this environment. If yes, check if there are any errors with this downlink/uplink?
4.What is this interface/IP used for (backup, mgmgt etc)?
5.Have you tried resetting the interface (after clearing counts) and see if Inbound errors re-occur?
6.Please share below commands output for that affected LOM.

# nwmgr -q info -c lanX (replace X with LAN number)
# nwmgr -g --st mib -c lanX (replace X with LAN number)
# netstat -ni

Thanks

Re: BL860 i4 LOM Inbound Errors

tony22 — Mon, 16 Sep 2024 09:30:43 GMT

1.Are you seeing "Inbound errors" on only one LOM port or multiple?

one LOM port, lan902(lan2,lan9) lan9 seeing"Inbound errors"

2.You mean to say, even if count is cleared it increases by 300 counts everyday?

yes

3.Is there any Virtual connected in this environment. If yes, check if there are any errors with this downlink/uplink?

C7000 10Gb pass-thru

4.What is this interface/IP used for (backup, mgmgt etc)?

oracle ADG

5.Have you tried resetting the interface (after clearing counts) and see if Inbound errors re-occur?

not resetting

6.Please share below commands output for that affected LOM.

# nwmgr -q info -c lanX (replace X with LAN number)

### /usr/sbin/nwmgr -q info -c lan9 ###
lan9:
Interface State =UP
MAC Address = 0xECEBB8FB817C
Subsystem = iocxgbe
Interface Type = 10GBASE-KR
Related Interface = lan902
Hardware Path = 1/0/0/4/0/0/1
NMID = 10
Feature Capabilities = Physical Interface
IPV4 Recv CKO
IPV4 Send CKO
VLAN Tag Offload
64Bit MIB Support
IPV4 TCP Segmentation Offload
UDP Multifrag CKO
Feature Settings = Physical Interface
IPV4 Recv CKO
IPV4 Send CKO
VLAN Tag Offload
64Bit MIB Support
IPV4 TCP Segmentation Offload
UDP Multifrag CKO
MTU = 9000
Speed = 10000 Mbps Full Duplex

lan9 PCI Properties:
Vendor ID: 0x19a2
Device ID: 0x710
Sub-Vendor ID: 0x103c
Sub-System ID: 0x177b
Firmware version: 4.9.416.17

lan9 Driver Properties:
Driver version: IOCXGBE_B.11.31.1905
Driver state: IOCXGBE_STATE_ONLINE
Transmit buffer descriptors: 2048
Receive buffer descriptors: 1024
Interrupt Coalescence Settings:

Interrupt Coalescence Settings:
Coalescence settings Current Minimum Maximum Default
Tx (usecs): 1000000 0 1000000 1000000
Rx (usecs): 20 0 1000000 20

Current multi-queue mode: TCP 4-tuple/UDP 2-tuple hash based

Interrupt and Queue Information:
Number of receive queues configured: 5
Number of receive queues active: 5
Name Intr ID CPU Number
------------- ------- ----------
Rx Queue # 0 0 46
Rx Queue # 1 1 32
Rx Queue # 2 2 34
Rx Queue # 3 3 36
Rx Queue # 4 4 38

# nwmgr -g --st mib -c lanX (replace X with LAN number)

### /usr/sbin/nwmgr -g --st mib -c lan9 ###

*** lan9 64 bit MIB statistics:
Interface Name = lan9
PPA Number = 9
Description = lan9 HP 10GBase-KR Release IOCXGBE_B.11.31.1905
Interface Type = 10GBASE-KR
MTU Size = 9000
Speed = 10.000000 Gbps
Station Address = 0xECEBB8FB817C
Administration Status = UP
Operation Status = UP
Last Change = Thu Nov 19 10:35:20 2020
Inbound Octets = 6788359575370
Inbound Unicast Packets = 1741335183
Inbound Multicast Packets = 0
Inbound Broadcast Packets = 80985445
Inbound Discards = 693
Inbound Errors = 1904
Inbound Unknown Protocols = 0
Outbound Octets = 4502844185731
Outbound Unicast Packets = 439179625
Outbound Multicast Packets = 0
Outbound Broadcast Packets = 61472
Outbound Discards = 0
Outbound Errors = 0
Outbound Queue Length = 4294967229
Counter Discontinuity Time = Tue Sep 28 04:27:45 2021
Physical Promiscuous Mode = FALSE
Physical Connector Present = TRUE
Interface Alias =
Link Up/Down Trap Enable = Enabled

# netstat -ni

### netstat -inv ###
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
lo0 32808 127.0.0.0 127.0.0.1 88064189553 0 88064209065 0 0
lan900:8 1500 172.29.2.0 172.29.2.180 1223743873 0 4233531 0 0
Warning: The above name 'lan900:801' is truncated, use -w to show the output in wide format
lan902:8 9000 10.250.12.0 10.250.12.180 106580292956 0 1643121 0 0
Warning: The above name 'lan902:801' is truncated, use -w to show the output in wide format
lan902 9000 10.250.12.0 10.250.12.179 87873345342 1904 73579117132 0 0
lan901 9000 10.250.2.0 10.250.3.179 302027873 0 37187637 0 0
lan900 1500 172.29.2.0 172.29.2.179 1071311512 0 1971450366 0 0
lan901:8 9000 169.254.0.0 169.254.23.75 107659899 0 107053731 0 0
Warning: The above name 'lan901:801' is truncated, use -w to show the output in wide format

Re: BL860 i4 LOM Inbound Errors

jsm6 — Mon, 16 Sep 2024 09:30:00 GMT

Hi,

Thank you for the details.

1.Clear LAN port stats for LAN 9
2.Reset the interface once (perform this during scheduled window or downtime)
3.Monitor further for any discards/errors.

If still Inbound error occurs, then this requires further validation (LAN port <-> 10Gbe switch <-> network switch). Would suggest log a support ticket.

Thanks.

Query: BL860 i4 LOM Inbound Errors

support_s — Wed, 31 Jul 2024 11:29:19 GMT

Hello,

Let us know if you were able to resolve the issue.

If you have no further query, and you are satisfied with the answer then kindly mark the topic as Solved so that it is helpful for all community members.

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.