VMware Cloud Community
Jsolarin
Contributor
Contributor
Jump to solution

How to update the SNMP syslocation on ESXi Blades

I'm running VMkernel 5.0.0 #1 SMP Release build-469512 Aug 18 2011 18:32:24 x86_64 unknown

I have put the <sysLocation></sysLocation> and <sysContact></sysContact> in the cat /etc/vmware/snmp.xml file.

I tried running the services.sh restart but when off the blade and doing an snmpget I still show the syslocation and syscontact as "not set"

Any help is appreciated.

Reply
0 Kudos
1 Solution

Accepted Solutions
tomtom901
Commander
Commander
Jump to solution

The system snmp namespace was not available on:

VMkernel localhost.vcaplab.local 5.0.0 #1 SMP Release build-914586 Nov 18 2012 1

However, it was available on:

VMkernel localhost.vcaplab.local 5.1.0 #1 SMP Release build-799733 Aug  1 2012 20:03:00 x86_64 GNU/Linux

So, if you really want this setting set, you need an update.

View solution in original post

Reply
0 Kudos
9 Replies
vmroyale
Immortal
Immortal
Jump to solution

Hello and welcome to the communities.

Check out VMware KB: Configuring SNMP Traps in ESXi/ESX for the procedure.

Brian Atkinson | vExpert | VMTN Moderator | Author of "VCP5-DCV VMware Certified Professional-Data Center Virtualization on vSphere 5.5 Study Guide: VCP-550" | @vmroyale | http://vmroyale.com
Reply
0 Kudos
tomtom901
Commander
Commander
Jump to solution

Use:

esxcli system snmp set --syslocation=Location --syscontact=tomtom901

Via SSH, that should suffice. Where Location and tomtom901 are your variables ofcourse.

Jsolarin
Contributor
Contributor
Jump to solution

Thank you for the quick response.

Unfortunately I have tried that command to no avail...

~ # esxcli system snmp set --syslocation=test --syscontact=test@test.com

Error: Unknown command or namespace system snmp set

When I run the system command in the esxcli I don't have a snmp sub command...

esxcli system

Usage: esxcli system {cmd} [cmd options]

Available Namespaces:

  boot                  Operations relating to host boot that allow manipulation of VMkernel boot time configuration.

  coredump              Operations pertaining to the VMkernel Core dump configuration.

  module                Operations that allow manipulation of the VMkernel loadable modules and device drivers. Operations include load, list and setting options.

  process               Commands relating to running processes.

  secpolicy             Options related to VMkernel access control subsystem. These options are typically in place for specific workarounds or debugging. These commands should be used at the direction of VMware Support Engineers.

  settings              Operations that allow viewing and manipulation of system settings.

  stats                 Access to various system statistics

  syslog                Operations relating to system logging

  visorfs               Operations pertaining to the visorfs memory filesytem.

  hostname              Operations pertaining the network name of the ESX host.

  time                  Commands to get and set system time.

  uuid                  Get the system UUID

  version               Commands to get version information.

  welcomemsg            Commands to get and set the welcome banner for DCUI.

Reply
0 Kudos
Jsolarin
Contributor
Contributor
Jump to solution

Thank you for the warm welcome.

Unfortunately that article does not contain information about the syslocation and syscontact when using the perl script...

Reply
0 Kudos
tomtom901
Commander
Commander
Jump to solution

Correct, it seems this is available from 5.1 on. That might also explain your issue. Is upgrading the ESXi host to 5.1 (at least, perhaps even 5.5) an option?

Jsolarin
Contributor
Contributor
Jump to solution

Since these blades are already in production I will have to investigate that type of upgrade.

Thank you for your help!

Reply
0 Kudos
tomtom901
Commander
Commander
Jump to solution

I will do a test first, install 5.0.0 and see if this namespace appears after an upgrade so you don't do the update in vain.

Reply
0 Kudos
tomtom901
Commander
Commander
Jump to solution

The system snmp namespace was not available on:

VMkernel localhost.vcaplab.local 5.0.0 #1 SMP Release build-914586 Nov 18 2012 1

However, it was available on:

VMkernel localhost.vcaplab.local 5.1.0 #1 SMP Release build-799733 Aug  1 2012 20:03:00 x86_64 GNU/Linux

So, if you really want this setting set, you need an update.

Reply
0 Kudos
Jsolarin
Contributor
Contributor
Jump to solution

Thank you Tomtom901. I really appreciate the extra help!

Wish me luck to get my management on board with an update haha.

Reply
0 Kudos