LMS 2.5 Fetch Config problem with SAN Switches (9200)

Answered Question
Jan 9th, 2006
User Badges:

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

Correct Answer by Jason Davis about 11 years 6 months ago

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.


http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/e_4_x/4_0_3/u_guide/syslog.htm#wp1211314


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.



  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (1 ratings)
Loading.
wdrootz Thu, 01/12/2006 - 09:10
User Badges:
  • Bronze, 100 points or more

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.

jsteffensen Fri, 02/10/2006 - 07:16
User Badges:

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.


Correct Answer
Jason Davis Fri, 02/10/2006 - 07:34
User Badges:
  • Cisco Employee,

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.


http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/e_4_x/4_0_3/u_guide/syslog.htm#wp1211314


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.



Actions

This Discussion