Why CW have to logon to config mode to perform snmp credential?

Unanswered Question
Feb 21st, 2010

Can gents,

Im using RME to check snmp strings on all devices.

Can someone tell me why does RME needs to logon to config mode ("%SYS-5-CONFIG_I") to perform Device Credential Verification?

Your prompt respond would be greatly appreciated.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Joe Clarke Sun, 02/21/2010 - 21:48

In order to verify the SNMP read-write credentials, RME obtains the current sysLocation, then sets sysLocation to that same value.  This constitutes a configuration change.

baotran09 Sun, 02/21/2010 - 22:49

What do you mean  "constitutes a configuration change"? CW doesnt update the snmp does it?

Why does it need to go to config mode, it can check the snmp string on priviledge mode.

baotran09 Mon, 02/22/2010 - 07:36

Hi C;arke,

Are you able to tell me exactly what CW do when it enter config mode?

Does it perform commands like 'wr mem'. IF not what commands does it use in the background?

I work in a environment where change ro Production is quiet strict.

I compare the configs and there's wasnt any changes (unless i missed something).

Is there a way to disable this function?

Joe Clarke Mon, 02/22/2010 - 09:05

It doesn't enter config mode.  If you are only testing SNMP credentials, it doesn't even telnet or SSH to the device.  However, RME DOES make a config change.  As I said, it performs an SNMP SET on sysLocation.  This action constitutes a configuration change.  However, the "change" is simply to set the value of sysLocation to its current value.  If the device accepts this change, then RME knows the SNMP read-write credential is a good one.

baotran09 Mon, 02/22/2010 - 19:28

If CW doesnt enter the config mode then how come I get this message "%SYS-5-CONFIG_I:" after i performed snmp credential verification?

Joe Clarke Mon, 02/22/2010 - 21:58

RME is making a config change.  The SYS-5-CONFIG_I message doesn't necessarily mean that some one entered config t mode.  All it means is that the running configuration has been changed.  You will note that the configuration was changed by "snmp".  This means that an SNMP SET was performed which changed the configuration in some way.  In this particular case, RME changed the value of sysLocation (i.e. snmp-server location). However, the new value will be the same as the previous value.


This Discussion