SNMP on Nexus 1000v

Unanswered Question
Apr 21st, 2014
User Badges:

I'm having a bear of a time trying to get SNMP to work on a 1000v.  Here's the current SNMP configuration:

 

show run snmp all

!Command: show running-config snmp all
!Time: Mon Apr 21 10:55:17 2014

version 4.2(1)SV1(5.1)
logging level snmpd 7
snmp-server aaa-user cache-timeout 3600
snmp-server protocol enable
no snmp-server globalEnforcePriv
snmp-server tcp-session auth
snmp-server user admin network-admin auth md5 <redacted> priv <redacted> localizedkey
snmp-server community <redacted> group network-operator
snmp-server community <redacted> use-acl SNMP-V1-RO

 show ip int bri
IP Interface Status for VRF "default"(1)
Interface            IP Address      Interface Status
UI-1000v-TEST# show ip int bri vrf all
IP Interface Status for VRF "default"(1)
Interface            IP Address      Interface Status

IP Interface Status for VRF "management"(2)
Interface            IP Address      Interface Status
mgmt0                172.20.255.230  protocol-up/link-up/admin-up

I'm guessing that this has something to do with the fact that I'm using the management vrf for connectivity to the 1000v.  I think the SNMP process is bound to the default vrf.  I fired up ethanalyzer on the 1000v and I can definitely see the SNMP queries hit the 1000v.  It just doesn't respond.  What else do I need to apply to the 1000v in order for it to respond to my SNMP queries?

 

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
sdavids5670 Mon, 04/21/2014 - 10:05
User Badges:

I think I'm hitting a bug.  I have the exact same configuration on other 1000Vs and they are working fine.

Marc Lariviere Tue, 06/03/2014 - 11:11
User Badges:

Hi,

 

2 weeks ago, half of mu N1000V's have become unreachable.  And now, there arre all unreachable.

 

The only way I found to get around the problem is to remove the ACL.

 

Marc Lariviere

Actions

This Discussion