Hi,
thks for your reply but it's really clear for me.
One the MC, I see :
(CTRL-Wifi1) *#show snmp trap-list | include wlsxUser
wlsxUserAuthenticationFailed Yes Disabled
wlsxUserEntryAttributesChanged Yes EnabledwlsxUserEntryAuthenticated Yes Disabled
wlsxUserEntryChanged Yes Disabled
wlsxUserEntryCreated Yes Disabled
wlsxUserEntryDeAuthenticated Yes Disabled
wlsxUserEntryDeleted Yes Disabled
(CTRL-Wifi1) *#
(CTRL-Wifi1) *#
(CTRL-Wifi1) *#configure t
This controller is managed by a Mobility Master.
Configuration changes can only be performed on the Mobility Master.
(CTRL-Wifi1) *#
and on the MM at the /md hierarchy :
(SRV-Mobility-Master) *[md] #show runn | include wlsxUser
Building Configuration...
snmp-server trap disable wlsxUserAuthenticationFailed
snmp-server trap disable wlsxUserEntryAttributesChangedsnmp-server trap disable wlsxUserEntryAuthenticated
snmp-server trap disable wlsxUserEntryChanged
snmp-server trap disable wlsxUserEntryCreated
snmp-server trap disable wlsxUserEntryDeAuthenticated
snmp-server trap disable wlsxUserEntryDeleted
and the command to view trap configuration result of going to /MM ..
(SRV-Mobility-Master) *[md] #show snmp trap-list | include wlsxUser
The commands for applications run on MM need to be executed on /mm tree.
The commands for applications run on individual devices need to be executed on the device node in 'mdconnect' mode.
On the /MM :
(SRV-Mobility-Master) *[mm] #show running-config | include wlsxUser
Building Configuration...
snmp-server trap disable wlsxUserAuthenticationFailed
snmp-server trap disable wlsxUserEntryAttributesChangedsnmp-server trap disable wlsxUserEntryAuthenticated
snmp-server trap disable wlsxUserEntryChanged
snmp-server trap disable wlsxUserEntryCreated
snmp-server trap disable wlsxUserEntryDeAuthenticated
snmp-server trap disable wlsxUserEntryDeleted
(SRV-Mobility-Master) *[mm] #
(SRV-Mobility-Master) *[mm] #show snmp trap-list | include wlsxUser
wlsxUserAuthenticationFailed Yes Disabled
wlsxUserEntryAttributesChanged Yes DisabledwlsxUserEntryAuthenticated Yes Disabled
wlsxUserEntryChanged Yes Disabled
wlsxUserEntryCreated Yes Disabled
wlsxUserEntryDeAuthenticated Yes Disabled
wlsxUserEntryDeleted Yes Disabled
(SRV-Mobility-Master) *[mm] #
Is there something I miss ? does I need to restart a process ?
Why the configuration are not synchronised between the MCs ans the MM ?
Original Message:
Sent: Jan 23, 2023 11:37 PM
From: Colin Joseph
Subject: Filter trap MM-MC
Those traps need to be disabled/enabled in the MD hierarchy, because they are sourced by the MDs. The MMs also send their own traps, but not the traps you are observing.
------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
Original Message:
Sent: Jan 20, 2023 06:15 AM
From: Arubineo
Subject: Filter trap MM-MC
Hi,
I tried to filter snmp trap on my airwave as I saw a lot of snmp trap from AP which is not interesting for me for example :
wlsxUserEntryAttributesChanged
wlsxUserEntryCreated
wlsxUserEntryDeleted
even if I have disable this trap on the MM at the /mm hierarchy :
(SRV-Mobility-Master) *[mm] #show snmp trap-list | include wlsxUser
wlsxUserAuthenticationFailed Yes Disabled
wlsxUserEntryAttributesChanged Yes Disabled
wlsxUserEntryAuthenticated Yes Disabled
wlsxUserEntryChanged Yes Disabled
wlsxUserEntryCreated Yes Disabled
wlsxUserEntryDeAuthenticated Yes Disabled
wlsxUserEntryDeleted Yes Disabled
I saw these traps on the airwave comming from AP ..... what's the problem ? How can I filter these traps which take a huge number ?

thks for your help.