Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Customer Case # 01586057
Now that XFS is the default filesystem for RHEL 7.x, when using SNMP to monitor filesystems, XFS is returned as hrFSOther, which causes it to be ignored by most SNMP monitoring tools.
hrFSType --> The value of this object identifies the type of this file system.
Currently hrFSTypes we can see from mibs files are listed below:-
# less /usr/share/snmp/mibs/HOST-RESOURCES-TYPES.txt
...
hrFSOther OBJECT-IDENTITY
hrFSUnknown OBJECT-IDENTITY
hrFSBerkeleyFFS OBJECT-IDENTITY
hrFSSys5FS OBJECT-IDENTITY
hrFSFat OBJECT-IDENTITY
hrFSHPFS OBJECT-IDENTITY
hrFSHFS OBJECT-IDENTITY
hrFSMFS OBJECT-IDENTITY
hrFSNTFS OBJECT-IDENTITY
hrFSVNode OBJECT-IDENTITY
hrFSJournaled OBJECT-IDENTITY
hrFSiso9660 OBJECT-IDENTITY
hrFSRockRidge OBJECT-IDENTITY
hrFSNFS OBJECT-IDENTITY
hrFSNetware OBJECT-IDENTITY
hrFSAFS OBJECT-IDENTITY
hrFSDFS OBJECT-IDENTITY
hrFSAppleshare OBJECT-IDENTITY
hrFSRFS OBJECT-IDENTITY
hrFSDGCFS OBJECT-IDENTITY
hrFSBFS OBJECT-IDENTITY
hrFSFAT32 OBJECT-IDENTITY
hrFSLinuxExt2 OBJECT-IDENTITY
Version-Release number of selected component (if applicable):
7.all
How reproducible:
Always.
Steps to Reproduce:
1. install rhel 7 w/default xfs filesystem
2. install and configure net-snmp
3. snmpwalk / poll for filesystems
Actual results:
+++++++++++++++++++++++++++++++++++++++++++++++++++
# cat /proc/mounts | grep vdb1
/dev/vdb1 /xfs xfs rw,seclabel,relatime,attr2,inode64,noquota 0 0
# df -h | grep vdb1
/dev/vdb1 1014M 33M 982M 4% /xfs
# rpm -qa | grep net-snmp
net-snmp-5.7.2-20.el7_1.1.x86_64
snmpwalk output:
HOST-RESOURCES-MIB::hrFSIndex.39 = INTEGER: 39
HOST-RESOURCES-MIB::hrFSMountPoint.39 = STRING: "/xfs"
HOST-RESOURCES-MIB::hrFSRemoteMountPoint.39 = ""
HOST-RESOURCES-MIB::hrFSType.39 = OID: HOST-RESOURCES-TYPES::hrFSOther <<--
HOST-RESOURCES-MIB::hrFSAccess.39 = INTEGER: readWrite(1)
+++++++++++++++++++++++++++++++++++++++++++++++++++
Expected results:
SNMP to return a new or correct hrFSType (for example):
OID: HOST-RESOURCES-TYPES::hrFSXfs
Additional info:
I don't know if it's extensible or if it's fixed by RFC1514.
There is no standard type for XFS files systems. Someone could define an OID for it, but it's unlikely to come from the IETF. And no matter where it comes from, it's unlikely that any monitoring tools that don't handle hrFSOther would do any better with the new type.
As Robert wrote in previous comment, we can't simply add a new OID for XFS to Net-SNMP. RFC and *all* 3rd party client tools would need to be updated too. It's better to update the clients to recognize hrFSOther.
Description of problem: Customer Case # 01586057 Now that XFS is the default filesystem for RHEL 7.x, when using SNMP to monitor filesystems, XFS is returned as hrFSOther, which causes it to be ignored by most SNMP monitoring tools. hrFSType --> The value of this object identifies the type of this file system. Currently hrFSTypes we can see from mibs files are listed below:- # less /usr/share/snmp/mibs/HOST-RESOURCES-TYPES.txt ... hrFSOther OBJECT-IDENTITY hrFSUnknown OBJECT-IDENTITY hrFSBerkeleyFFS OBJECT-IDENTITY hrFSSys5FS OBJECT-IDENTITY hrFSFat OBJECT-IDENTITY hrFSHPFS OBJECT-IDENTITY hrFSHFS OBJECT-IDENTITY hrFSMFS OBJECT-IDENTITY hrFSNTFS OBJECT-IDENTITY hrFSVNode OBJECT-IDENTITY hrFSJournaled OBJECT-IDENTITY hrFSiso9660 OBJECT-IDENTITY hrFSRockRidge OBJECT-IDENTITY hrFSNFS OBJECT-IDENTITY hrFSNetware OBJECT-IDENTITY hrFSAFS OBJECT-IDENTITY hrFSDFS OBJECT-IDENTITY hrFSAppleshare OBJECT-IDENTITY hrFSRFS OBJECT-IDENTITY hrFSDGCFS OBJECT-IDENTITY hrFSBFS OBJECT-IDENTITY hrFSFAT32 OBJECT-IDENTITY hrFSLinuxExt2 OBJECT-IDENTITY Version-Release number of selected component (if applicable): 7.all How reproducible: Always. Steps to Reproduce: 1. install rhel 7 w/default xfs filesystem 2. install and configure net-snmp 3. snmpwalk / poll for filesystems Actual results: +++++++++++++++++++++++++++++++++++++++++++++++++++ # cat /proc/mounts | grep vdb1 /dev/vdb1 /xfs xfs rw,seclabel,relatime,attr2,inode64,noquota 0 0 # df -h | grep vdb1 /dev/vdb1 1014M 33M 982M 4% /xfs # rpm -qa | grep net-snmp net-snmp-5.7.2-20.el7_1.1.x86_64 snmpwalk output: HOST-RESOURCES-MIB::hrFSIndex.39 = INTEGER: 39 HOST-RESOURCES-MIB::hrFSMountPoint.39 = STRING: "/xfs" HOST-RESOURCES-MIB::hrFSRemoteMountPoint.39 = "" HOST-RESOURCES-MIB::hrFSType.39 = OID: HOST-RESOURCES-TYPES::hrFSOther <<-- HOST-RESOURCES-MIB::hrFSAccess.39 = INTEGER: readWrite(1) +++++++++++++++++++++++++++++++++++++++++++++++++++ Expected results: SNMP to return a new or correct hrFSType (for example): OID: HOST-RESOURCES-TYPES::hrFSXfs Additional info: I don't know if it's extensible or if it's fixed by RFC1514.