cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3439
Views
0
Helpful
4
Replies

Nexus not returning FQDN on SNMP sysName query

seabird505
Level 1
Level 1

Hi,

All the other switches / routers on quering for SNMP sysName.0 returns their FQDN in our network. The Nexus 7010 and 5020 switches in the network return only their name. "hostname xx" and "ip domain-name xx" defined on all the devices. The SNMP MIB is matching. There are no other SNMP related issues. How can I get the FQDN for these devices ?

$  snmpget -v 2c -c public m-65k-00.core sysName.0

SNMPv2-MIB::sysName.0 = STRING: m-65k-00.core.abcd.com

$  snmpget -v 2c -c public m-N7K-00.core sysName.0

SNMPv2-MIB::sysName.0 = STRING: m-N7K-00

$  snmpget -v 2c -c public m-N7K-00.core.abcd.com sysName.0

SNMPv2-MIB::sysName.0 = STRING: m-N7K-00


Thanks,

Rashid.

1 Accepted Solution

Accepted Solutions

Hi Rashid,

Forgot to mention something, this object is context-aware, if for example your SNMP requests arrive on the mgmt0 interface it's necessary to configure the domain-name under the VRF not just globally, eg:

  vrf context management

    ip domain-name lab.cisco.com

I checked the versions you mentioned in my lab and see the expected behaviour (sysName contains FQDN) when the above config is in place.

Kind Regards,

/Phil

View solution in original post

4 Replies 4

phiharri
Level 1
Level 1

Greetings Rashid,

This is fixed by CSCth05382 in 4.2(8) and 5.2(1).

HTH,

/Phil

Thanks Phil, That was really helpful. Seems the problem might not be fixed in (or re-appeared) in later releases. We are facing the issue both in N7K and N5K. They N7K in particular is running a later version than the earlier fixed version according to the bug page.

N7010# show version

Software

  BIOS:      version 3.22.0

  kickstart: version 5.2(3a)

  system:    version 5.2(3a)

  BIOS compile time:       02/20/10

  kickstart image file is: bootflash:///n7000-s1-kickstart.5.2.3a.bin

  kickstart compile time:  12/25/2020 12:00:00 [12/16/2011 14:04:59]

  system image file is:    bootflash:///n7000-s1-dk9.5.2.3a.bin

  system compile time:     12/15/2011 12:00:00 [12/16/2011 15:15:48]

N5020# show version

Software

  BIOS:      version 1.3.0

  loader:    version N/A

  kickstart: version 5.0(3)N2(2a)

  system:    version 5.0(3)N2(2a)

  power-seq: Module 1: version v1.2

  BIOS compile time:       09/08/09

  kickstart image file is: bootflash:///n5000-uk9-kickstart.5.0.3.N2.2a.bin

  kickstart compile time:  10/15/2011 9:00:00 [10/16/2011 03:44:53]

  system image file is:    bootflash:/n5000-uk9.5.0.3.N2.2a.bin

  system compile time:     10/15/2011 9:00:00 [10/16/2011 05:35:57]

Hi Rashid,

Forgot to mention something, this object is context-aware, if for example your SNMP requests arrive on the mgmt0 interface it's necessary to configure the domain-name under the VRF not just globally, eg:

  vrf context management

    ip domain-name lab.cisco.com

I checked the versions you mentioned in my lab and see the expected behaviour (sysName contains FQDN) when the above config is in place.

Kind Regards,

/Phil

Hi Phillip,

That did the trick. Its working returing FQDN now.

Thanks for your time.

Regards, Rashid.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Review Cisco Networking products for a $25 gift card