/var/spool/snmp isn't mounted after the VCSA VM is failed over to another host.
Article ID: 344862
Updated On:
Products
VMware vCenter Server
Issue/Introduction
Symptoms:
1. Enable the snmpd in the VCSA.
2. Confirm that running the 'snmpwalk' command from a Linux box wherein it indicates the information of '/var/spool/snmp'.
3. Reset the VCSA VM from the Host Client where it is running on.
4. Wait for VCSA to be up.
5. Check if the 'snmpwalk' command from a Linux box does not show the information of '/var/spool/snmp'.
Customer monitors VCSA using SNMP. It works fine until the VC machine is failed over to another host, after which the complete information is not visible.
- hrStorageSize.19 is the parameter which I not seen.
- -snmp service is in start state after failover as well
- The work-around is to restart snmp service after which it is visible again, but hes asking for a resolution.
1. Enable the snmpd in the VCSA.
2. Confirm that running the 'snmpwalk' command from a Linux box wherein it indicates the information of '/var/spool/snmp'.
3. Reset the VCSA VM from the Host Client where it is running on.
4. Wait for VCSA to be up.
5. Check if the 'snmpwalk' command from a Linux box does not show the information of '/var/spool/snmp'.
Environment
VMware vCenter Server 6.7.x
VMware vCenter Server 6.5.x
VMware vCenter Server 7.0.x
VMware vCenter Server 6.5.x
VMware vCenter Server 7.0.x
Cause
This seems to happen because /var/spool/snmp isn't mounted in the VCSA VM from Linux OS
[ Before resetting VCSA VM]
------------------------------------------------------------------------------------------
root@vcsa70ga-00 [ ~ ]# df -lh
Filesystem Size Used Avail Use% Mounted on
devtmpfs 5.9G 0 5.9G 0% /dev
tmpfs 5.9G 536K 5.9G 1% /dev/shm
tmpfs 5.9G 1.2M 5.9G 1% /run
tmpfs 5.9G 0 5.9G 0% /sys/fs/cgroup
/dev/sda3 46G 5.1G 39G 12% /
/dev/sda2 120M 24M 88M 22% /boot
/dev/mapper/lifecycle_vg-lifecycle 98G 2.2G 91G 3% /storage/lifecycle
/dev/mapper/netdump_vg-netdump 985M 2.5M 915M 1% /storage/netdump
/dev/mapper/vtsdblog_vg-vtsdblog 4.9G 52M 4.6G 2% /storage/vtsdblog
/dev/mapper/vtsdb_vg-vtsdb 9.8G 67M 9.2G 1% /storage/vtsdb
/dev/mapper/archive_vg-archive 49G 139M 47G 1% /storage/archive
tmpfs 5.9G 4.8M 5.9G 1% /tmp
/dev/mapper/updatemgr_vg-updatemgr 98G 297M 93G 1% /storage/updatemgr
/dev/mapper/imagebuilder_vg-imagebuilder 9.8G 596M 8.7G 7% /storage/imagebuilder
/dev/mapper/db_vg-db 9.8G 137M 9.2G 2% /storage/db
/dev/mapper/autodeploy_vg-autodeploy 9.8G 1.7G 7.7G 18% /storage/autodeploy
/dev/mapper/seat_vg-seat 9.8G 96M 9.2G 2% /storage/seat
/dev/mapper/core_vg-core 25G 134M 24G 1% /storage/core
/dev/mapper/dblog_vg-dblog 15G 89M 14G 1% /storage/dblog
/dev/mapper/log_vg-log 9.8G 439M 8.9G 5% /storage/log
tmpfs 1.0M 0 1.0M 0% /var/spool/snmp ### <-- This is missing after the reset.
------------------------------------------------------------------------------------------
[ VCSA VM booting after the reset]
------------------------------------------------------------------------------------------
root@vcsa70ga-00 [ ~ ]# df -lh
Filesystem Size Used Avail Use% Mounted on
devtmpfs 5.9G 0 5.9G 0% /dev
tmpfs 5.9G 528K 5.9G 1% /dev/shm
tmpfs 5.9G 1.2M 5.9G 1% /run
tmpfs 5.9G 0 5.9G 0% /sys/fs/cgroup
/dev/sda3 46G 5.1G 39G 12% /
/dev/sda2 120M 24M 88M 22% /boot
/dev/mapper/lifecycle_vg-lifecycle 98G 2.2G 91G 3% /storage/lifecycle
/dev/mapper/netdump_vg-netdump 985M 2.5M 915M 1% /storage/netdump
/dev/mapper/vtsdblog_vg-vtsdblog 4.9G 52M 4.6G 2% /storage/vtsdblog
/dev/mapper/vtsdb_vg-vtsdb 9.8G 67M 9.2G 1% /storage/vtsdb
/dev/mapper/archive_vg-archive 49G 139M 47G 1% /storage/archive
tmpfs 5.9G 4.8M 5.9G 1% /tmp
/dev/mapper/updatemgr_vg-updatemgr 98G 297M 93G 1% /storage/updatemgr
/dev/mapper/imagebuilder_vg-imagebuilder 9.8G 596M 8.7G 7% /storage/imagebuilder
/dev/mapper/db_vg-db 9.8G 137M 9.2G 2% /storage/db
/dev/mapper/autodeploy_vg-autodeploy 9.8G 1.7G 7.7G 18% /storage/autodeploy
/dev/mapper/seat_vg-seat 9.8G 96M 9.2G 2% /storage/seat
/dev/mapper/core_vg-core 25G 134M 24G 1% /storage/core
/dev/mapper/dblog_vg-dblog 15G 89M 14G 1% /storage/dblog
/dev/mapper/log_vg-log 9.8G 435M 8.9G 5% /storage/log
[ Before resetting VCSA VM]
------------------------------------------------------------------------------------------
root@vcsa70ga-00 [ ~ ]# df -lh
Filesystem Size Used Avail Use% Mounted on
devtmpfs 5.9G 0 5.9G 0% /dev
tmpfs 5.9G 536K 5.9G 1% /dev/shm
tmpfs 5.9G 1.2M 5.9G 1% /run
tmpfs 5.9G 0 5.9G 0% /sys/fs/cgroup
/dev/sda3 46G 5.1G 39G 12% /
/dev/sda2 120M 24M 88M 22% /boot
/dev/mapper/lifecycle_vg-lifecycle 98G 2.2G 91G 3% /storage/lifecycle
/dev/mapper/netdump_vg-netdump 985M 2.5M 915M 1% /storage/netdump
/dev/mapper/vtsdblog_vg-vtsdblog 4.9G 52M 4.6G 2% /storage/vtsdblog
/dev/mapper/vtsdb_vg-vtsdb 9.8G 67M 9.2G 1% /storage/vtsdb
/dev/mapper/archive_vg-archive 49G 139M 47G 1% /storage/archive
tmpfs 5.9G 4.8M 5.9G 1% /tmp
/dev/mapper/updatemgr_vg-updatemgr 98G 297M 93G 1% /storage/updatemgr
/dev/mapper/imagebuilder_vg-imagebuilder 9.8G 596M 8.7G 7% /storage/imagebuilder
/dev/mapper/db_vg-db 9.8G 137M 9.2G 2% /storage/db
/dev/mapper/autodeploy_vg-autodeploy 9.8G 1.7G 7.7G 18% /storage/autodeploy
/dev/mapper/seat_vg-seat 9.8G 96M 9.2G 2% /storage/seat
/dev/mapper/core_vg-core 25G 134M 24G 1% /storage/core
/dev/mapper/dblog_vg-dblog 15G 89M 14G 1% /storage/dblog
/dev/mapper/log_vg-log 9.8G 439M 8.9G 5% /storage/log
tmpfs 1.0M 0 1.0M 0% /var/spool/snmp ### <-- This is missing after the reset.
------------------------------------------------------------------------------------------
[ VCSA VM booting after the reset]
------------------------------------------------------------------------------------------
root@vcsa70ga-00 [ ~ ]# df -lh
Filesystem Size Used Avail Use% Mounted on
devtmpfs 5.9G 0 5.9G 0% /dev
tmpfs 5.9G 528K 5.9G 1% /dev/shm
tmpfs 5.9G 1.2M 5.9G 1% /run
tmpfs 5.9G 0 5.9G 0% /sys/fs/cgroup
/dev/sda3 46G 5.1G 39G 12% /
/dev/sda2 120M 24M 88M 22% /boot
/dev/mapper/lifecycle_vg-lifecycle 98G 2.2G 91G 3% /storage/lifecycle
/dev/mapper/netdump_vg-netdump 985M 2.5M 915M 1% /storage/netdump
/dev/mapper/vtsdblog_vg-vtsdblog 4.9G 52M 4.6G 2% /storage/vtsdblog
/dev/mapper/vtsdb_vg-vtsdb 9.8G 67M 9.2G 1% /storage/vtsdb
/dev/mapper/archive_vg-archive 49G 139M 47G 1% /storage/archive
tmpfs 5.9G 4.8M 5.9G 1% /tmp
/dev/mapper/updatemgr_vg-updatemgr 98G 297M 93G 1% /storage/updatemgr
/dev/mapper/imagebuilder_vg-imagebuilder 9.8G 596M 8.7G 7% /storage/imagebuilder
/dev/mapper/db_vg-db 9.8G 137M 9.2G 2% /storage/db
/dev/mapper/autodeploy_vg-autodeploy 9.8G 1.7G 7.7G 18% /storage/autodeploy
/dev/mapper/seat_vg-seat 9.8G 96M 9.2G 2% /storage/seat
/dev/mapper/core_vg-core 25G 134M 24G 1% /storage/core
/dev/mapper/dblog_vg-dblog 15G 89M 14G 1% /storage/dblog
/dev/mapper/log_vg-log 9.8G 435M 8.9G 5% /storage/log
Resolution
VMware is aware of the problem and they are planning to fix this in the future versions of 6.5 , 6.7 and 7.0
Additional Information
Impact/Risks:
SNMP will not be working perfectly after the failover of the VC VM
SNMP will not be working perfectly after the failover of the VC VM
Feedback
Yes
No
Powered by
