TWSD-922 SNMP Engine ID should not be synchronized with the peer device and must remain unique for each device of APV.|AS-22473|WBSDC

Review Request #1030 — Created Aug. 25, 2025 and submitted

mmiriam
APV10
rel_apv_10_7
TWSD-922
ngurunathan, pradeep, tanya

SNMP Engine ID should not be synchronized with the peer device and must remain unique for each device of APV. Updated existing snmp host CLI command by dividing it into 3 seperate commands. snmp host, snmp engineid and snmp auth.

In primary device:
snmp host 192.168.16.1 3 "array1"
snmp engineid 192.168.16.1 "12345678"
snmp auth 192.168.16.1 "admin@123" authNopriv "admin@123" 162 "SHA1"

In secondary device:
AN(config)#sh run snmp

snmp configuration

snmp community "public"
snmp contact ""
snmp location ""
snmp host 192.168.16.1 3 "public"
snmp engineid 192.168.16.1 ""
snmp auth 192.168.16.1 "" authNopriv "" 0 ""
no snmp enable traps
snmp traps loglevel err
snmp ipcontrol off
snmp off

In secondery set engineid:
APV2#snmp engineid 192.168.16.1 "125686387"

Then in primery set snmp auth:
APV1#snmp auth 192.168.16.1 "admin@123" authNopriv "admin@123" 162 "SHA1"

APV2#sh run snmp
APV2#snmp configuration
snmp community "public"
snmp contact ""
snmp location ""
snmp host 192.168.16.1 3 "public"
snmp engineid 192.168.16.1 "12568638"
snmp auth 192.168.16.1 "XXXXXXXXX3MSAKA1KYEX5DPuknEYwNA==" authNopriv "" 162 "SHA1"
no snmp enable traps
snmp traps loglevel err
snmp ipcontrol off
snmp off

Description From Last Updated

are we introducing "snmp_server_lock" here? Why it is required, if we have not used earlier?

pradeeppradeep

pInfo is from shared memory so we are using lock while using it and it was used in earlier code …

mmiriammmiriam

should we print that "host not found ?

pradeeppradeep

sure will update this

mmiriammmiriam
pradeep
  1. 
      
  2. should we print that "host not found ?

  3. 
      
pradeep
  1. 
      
  2. are we introducing "snmp_server_lock" here?
    Why it is required, if we have not used earlier?

  3. 
      
mmiriam
  1. 
      
  2. pInfo is from shared memory so we are using lock while using it and it was used in earlier code also

  3. 
      
ngurunathan
  1. Ship It!
  2. 
      
pradeep
  1. Ship It!
  2. 
      
mmiriam
mmiriam
Review request changed

Status: Closed (submitted)

Loading...