HP 1920 Prevent UP/DOWN logging

[Dunky]

Is there a way of stopping the logging of interface up/down and associated messages?

I currently have "info-center loghost n.n.n.n" and "snmp-agent target-host trap address udp-domain n.n.n.n  params securityname pa55w0rd v2C" set and I am getting notifications every time a PC is turned on/off....

Jul 31 18:20:03 192.168.100.10 2016 local7 warning SWITCH-06 %%10IFNET/4/INTERFACE UPDOWN(t) Trap 1.3.6.1.6.3.1.1.5.3: Interface 18923520 is Down, ifAdminStatus is 1, ifOperStatus is 2
Jul 31 18:20:03 192.168.100.10 2016 local7 err SWITCH-06 %%10IFNET/3/LINK_UPDOWN(l) GigabitEthernet1/0/13 link status is DOWN.
Jul 31 18:20:07 192.168.100.10 2016 local7 warning SWITCH-06 %%10IFNET/4/INTERFACE UPDOWN(t) Trap 1.3.6.1.6.3.1.1.5.4: Interface 18923520 is Up, ifAdminStatus is 1, ifOperStatus is 1
Jul 31 18:20:07 192.168.100.10 2016 local7 err SWITCH-06 %%10IFNET/3/LINK_UPDOWN(l) GigabitEthernet1/0/13 link status is UP.
Jul 31 18:20:07 192.168.100.10 2016 local7 alert SWITCH-06 %%10MSTP/1/PFWD(t) Trap 1.3.6.1.4.1.25506.8.35.14.0.1: Instance 0's Port 0.18923520 has been set to forwarding state!
Jul 31 18:20:07 192.168.100.10 2016 local7 alert SWITCH-06 %%10MSTP/1/PFWD(t) Trap 1.3.6.1.4.1.25506.8.35.14.0.1: Instance 1's Port 1.18923520 has been set to forwarding state!
Jul 31 18:20:07 192.168.100.10 2016 local7 info SWITCH-06 %%10MSTP/6/MSTP_FORWARDING(l) Instance 0's port GigabitEthernet1/0/13 has been set to forwarding state.
Jul 31 18:20:07 192.168.100.10 2016 local7 info SWITCH-06 %%10MSTP/6/MSTP_FORWARDING(l) Instance 1's port GigabitEthernet1/0/13 has been set to forwarding state.
Jul 31 18:20:56 192.168.100.10 2016 local7 warning SWITCH-06 %%10IFNET/4/INTERFACE UPDOWN(t) Trap 1.3.6.1.6.3.1.1.5.3: Interface 18923520 is Down, ifAdminStatus is 1, ifOperStatus is 2
Jul 31 18:20:56 192.168.100.10 2016 local7 err SWITCH-06 %%10IFNET/3/LINK_UPDOWN(l) GigabitEthernet1/0/13 link status is DOWN.
Jul 31 18:20:59 192.168.100.10 2016 local7 warning SWITCH-06 %%10IFNET/4/INTERFACE UPDOWN(t) Trap 1.3.6.1.6.3.1.1.5.4: Interface 18923520 is Up, ifAdminStatus is 1, ifOperStatus is 1
Jul 31 18:20:59 192.168.100.10 2016 local7 err SWITCH-06 %%10IFNET/3/LINK_UPDOWN(l) GigabitEthernet1/0/13 link status is UP.
Jul 31 18:20:59 192.168.100.10 2016 local7 alert SWITCH-06 %%10MSTP/1/PFWD(t) Trap 1.3.6.1.4.1.25506.8.35.14.0.1: Instance 0's Port 0.18923520 has been set to forwarding state!
Jul 31 18:20:59 192.168.100.10 2016 local7 alert SWITCH-06 %%10MSTP/1/PFWD(t) Trap 1.3.6.1.4.1.25506.8.35.14.0.1: Instance 1's Port 1.18923520 has been set to forwarding state!
Jul 31 18:20:59 192.168.100.10 2016 local7 info SWITCH-06 %%10MSTP/6/MSTP_FORWARDING(l) Instance 0's port GigabitEthernet1/0/13 has been set to forwarding state.
Jul 31 18:20:59 192.168.100.10 2016 local7 info SWITCH-06 %%10MSTP/6/MSTP_FORWARDING(l) Instance 1's port GigabitEthernet1/0/13 has been set to forwarding state.

is there a way of stopping the messages associated with UP/DOWN on specific ports being generated - on Cisco it is "no logging event link-status"  on the interface - is there an equivalent for the 1920's?

Thanks

[parnassus]

I though - erroneously - that (Port/Trunk) Interface State Up/Down messages belonged to the Syslog's Informational severity level...and so I though you can just abruptly adapt (via the info-center syslog command) the severity levels of the system log to exclude those Informational messages you don't want to be logged and log what you really need.

As example, in order of severity, excluding Debug, Information and Notification, leaving Warning, Error, Critical Alert and Emergency...but the annoying messages you reported

Jul 31 18:20:03 192.168.100.10 2016 local7 err SWITCH-06 %%10IFNET/3/LINK_UPDOWN(l) GigabitEthernet1/0/13 link status is DOWN.

Jul 31 18:20:07 192.168.100.10 2016 local7 err SWITCH-06 %%10IFNET/3/LINK_UPDOWN(l) GigabitEthernet1/0/13 link status is UP.

seem to belong to the Error severity level (and so they are related to a supposed Error Condition).

That's strange (IMHO link status Up/Down should be Informational).

Just for curiosity, what does the display logbuffer summary command reports?

[Dunky]

As requested...

[SWITCH-06]dis logbuffer summary
  SLOT EMERG ALERT  CRIT ERROR  WARN NOTIF  INFO DEBUG
     1     0     0     0   192     6    47   267     0

What I need is to disable the syslog messages on specific ports just like you can in Cisco IOS.

Its looking as though this isnt possible?

[parnassus]

Well, HPE OfficeConnect 1920 Switch Series is Comware 5.20 based and (HPE) Comware 5.20 is not like Cisco IOS or HP ProVision (now ArubaOS-Switch), neither like HPE Comware 7...simply because Comware 5.20 is similar but not comparable (in terms of all possible available commands)...AFAIK, and I'm not an expert, I was unable to find a suitable command to disable/enable the link status monitoring nor globally neither per interface as happens with the Cisco IOS.

Probably you should play with SNMP Traps on one side and with Syslog severity level on the other...if those messages are too noisy for your monitoring system.

I hope someone else can step in and give an help...but we're speaking about Comware 5.20 and its limited set of (CLI) commands (not to speak about its more limited Web User Interface).

[Dunky]

After some investigations it appears that the ports that are generating lots of up/down messages are MACbook's and from what research I have been ableto do it looks like a known problem with certain versions.  I am now persuing that angle and may have a fix.

Going back to the original question of 'Is it possible to disable the syslog/snmp traps for specific interfaces?' the answer appears to be NO (grrrrr, how difficult is it to think that this might be a really useful feature!).

[Dunky · Accepted solution]

Finally found the answer - YES IT CAN BE DONE!!!!

To disable logging for a specific interface...

int g1/0/1

undo enable log updown