01-09-2006 07:44 AM
Hi There
We have the following problem:
When configuring the SAN-switch with CLI - It sends syslog messages containing:
"Configured by...*****".
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?
Best Regards
Jarle Steffensen
Solved! Go to Solution.
02-10-2006 07:34 AM
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.
01-12-2006 09:10 AM
The Syslog application triggers configuration fetch, if configuration change messages like SYS-6-CFG_CHG, CPU_REDUN-6-RUNNING_CONFIG_CHG etc., are received.
Don't think the message "AAA-6-AAA_ACCOUNTING_MESSAGE" is included in this list, hence fetch is not happening.
You might have to update the config manually or run a periodic poll to check for config updates.
02-10-2006 07:16 AM
There is a bug discovered.
When using Fabric Manager ithe wrong syslog-message is written after the config change.
The error is somehow related to a SNMP mib wich is changed, wich again triggers the SYSLOG message.
The Development team from cisco is working on it.
02-10-2006 07:34 AM
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.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: