Reset Search
 

 

Article

Why SNMP trap does not get generated if one of the community names set by default is removed in VDX platforms.

« Go Back

Information

 
TitleWhy SNMP trap does not get generated if one of the community names set by default is removed in VDX platforms.
Symptoms

In VDX, six community names are configured by default but SNMP trap does not get generated if one of community names set by default is removed.This issue is due to mismatch of SNMP community security name with SNMP target parameter security name.

Users running into this issue tend to experience this issue when utilizing,more or less, theprocess outlinedbelow:

Step 1:
Load VDX with 2.1.0b with factory default configuration and check VDX has total 6 community names by CLI show run snmp.

Step 2:
Add the below configuration

2a. Management IP

interface Management 11/0
ip address 111.11.111.111/11
ip gateway-address 000.00.000.0


2b. snmp-server host

snmp-server host 101.01.010.10 public

2c. Bring eth 11/0/1 link-up status

interface TenGigabitEthernet 11/0/1
no shutdown


Step 3:
Check VDX is able to generate SNMP trap if tengig 11/0/1 goes link up or down.

3a.Theshow run snmp output is seen below; the attached pcap file is a sample snmp-trap packets.

sw0# show run snmp
snmp-server contact "Field Support."
snmp-server location "End User Premise."
snmp-server community ConvergedNetwork
!
snmp-server community OrigEquipMfr
rw
!
snmp-server community "Secret C0de"
rw
!
snmp-server community common
!
snmp-server community private
rw
!
snmp-server community public
!
snmp-server host 101.01.010.10 public
!
snmp-server user snmpadmin1 groupname snmpadmin auth-password * priv-password * snmp-server user snmpadmin2 groupname snmpadmin auth-password * priv-password * snmp-server user snmpadmin3 groupname snmpadmin auth-password * priv-password * snmp-server user snmpuser1 auth-password * priv-password * snmp-server user snmpuser2 auth-password * priv-password * snmp-server user snmpuser3 auth-password * priv-password * sw0#


Step 4:
Remove one of the community names and then save running-configuration.

sw0# conf t

Entering configuration mode terminal:

sw0(config)# no snmp-server community OrigEquipMfr
2011/08/22-10:22:52, [SNMP-1005], 3985,, INFO, sw0, SNMP configuration attribute, community string 2 , has changed from [OrigEquipMfr] to
sw0(config)# end


sw0# show run snmp
snmp-server contact "Field Support."
snmp-server location "End User Premise."
snmp-server community ConvergedNetwork
!
snmp-server community "Secret C0de"
rw
!
snmp-server community common
!
snmp-server community private
rw
!
snmp-server community public
!
snmp-server host 101.01.010.10 public
!
snmp-server user snmpadmin1 groupname snmpadmin auth-password * priv-password * snmp-server user snmpadmin2 groupname snmpadmin auth-password * priv-password * snmp-server user snmpadmin3 groupname snmpadmin auth-password * priv-password * snmp-server user snmpuser1 auth-password * priv-password * snmp-server user snmpuser2 auth-password * priv-password * snmp-server user snmpuser3 auth-password * priv-password * sw0# sw0# copy running-configstartup-config This operation will modify your startup configuration. Do you want to continue? [y/n]:y sw0# sw0# reload


Warning: Unsaved configuration will be lost.
Are you sure you want to reload the switch? [y/n]:y The system is going down for reload NOW !!


Note: SNMP trap can be generated unless reloading the box.

Step 5:
After VDX comes up, the userbrings the eth 11/0/1 link-down by shutdown command, but snmp-trap is not generated.

Note: The process outlined above is typically how users run into this issue. The steps outlined are not a fix.

Environment
Software Release: NOS 2.1.0b release
Fixed in Version: N/A
Cause
Resolution
Users can resolve thisissue by upgrading to the 2.1.1 release. This will fix the issue.
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255