topic Re: Weird notification log in ExtremeSwitching (EXOS/Switch Engine)

Weird notification log

Netnoddy — Wed, 17 Apr 2024 12:45:02 GMT

I'm experiencing these weird looking log entries on an exos switch running (ExtremeXOS version 31.7.2.28 31.7.2.28-patch1-21)

Anybody else seeing these? Everything seems to be working fine just a bit weary of something on it's way to hell 🙂

04/16/2024 09:36:00.47 <Noti:Card.IPv4Adj.Notice> vrId 2 adj 10.1.20.166: Update failed on unit 0 (Invalid parameter), flags 0x10102, flags2 0x10000000
04/16/2024 09:36:00.47 <Noti:Card.IPv4Adj.Notice> vrId 2 adj 10.1.20.166: Unable to add RIOT host with egress object index = 508186 (Invalid parameter)

Re: Weird notification log

Brent_Addis — Thu, 18 Apr 2024 21:44:26 GMT

Seems ACL or QOS related to me. Do you have any ACLs/QOS settings?

Perhaps somethings changed between firmware releases and an old command is no longer valid, although being loaded?

Other option is, backup your config, remove anything apart from vlan / l3 info such as routing, factory reset and paste the config back on.

Re: Weird notification log

Netnoddy — Fri, 19 Apr 2024 06:33:23 GMT

We do indeed have an acl configured for this port.
I could try and remove the acl, wait and see.

Re: Weird notification log

Netnoddy — Mon, 22 Apr 2024 11:13:11 GMT

I removed the acl but the messages keep coming.

We do have qos configured too. Just need to figure out how to disable qos on a port.