We have the following problem:
When configuring the SAN-switch with CLI - It sends syslog messages containing:
This againg triggers the "fetch configuration" on LMS, which fetches the new config.
When configuring the SAN-switch using the Fabric Manager (which configures the Switch using SNMP) it generates a syslog-message with the following text:
"%AAA-6-AAA_ACCOUNTING_MESSAGE: update:snmp_xxxx_y.z.x.y:amin*********** and so on"
This does not trigger "LMS fetch configuration".
Is this a bug in the SAN software?
Are there any workarounds?
Anyone having the same problem?
Generally SNMP-initiated changes do not generate the normal Syslog SYS_CONFIG or SYS_CONFIG_I messages similar to the first one you mentioned.
The second syslog message you mentioned is a AAA syslog event message. CiscoWorks RME and the Syslog Analyzer function does not actively listen for the AAA-6-AAA_ACCOUNTING_MESSAGE".
RME uses a Syslog automated action to grab configs and/or inventory when syslog-initiated changes are identified.
You'll note Under RME/Tools/Syslog/Automated actions that there is an existing, pre-made entry for Config Fetch. It currently doesn't listen to the AAA message you're interested in. You could ask your field sales SE to file a PERS on your behalf if this is important to you... Or you could create a new automated action that grabs the config with a script that you provide.