By default, the data for the FibreChannelHostPort (HBA) are not available in the default configuration of Net-SNMP agent. To discover the FibreChannelHostPort, you need to configure NETSNMP-EXTENDED-MIB on each KVM hypervisor host.

Note:

This is applicable only when KVM hypervisor is configured with NET-SNMP agent.

Steps to configure NETSNMP-EXTENDED-MIB on kvm hypervoisor host:

  1. Add the following entries to the snmpd.conf file (default patch /etc/snmp/snmpd.conf).

    extend-sh WWN /bin/cat /sys/class/fc_host/host?/port_name

    extend-sh ID /bin/cat /sys/class/fc_host/host?/port_id

    extend-sh type /bin/cat /sys/class/fc_host/host?/port_type

    extend-sh symbolicName /bin/cat /sys/class/fc_host/host?/symbolic_name

    extend-sh fabricName /bin/cat /sys/class/fc_host/host?/fabric_name

    extend-sh state /bin/cat /sys/class/fc_host/host?/port_state

    extend-sh nodeName /bin/cat /sys/class/fc_host/host?/node_name

  2. Restart the SNMP agent by using the following command:

    service snmpd restart

  3. After restarting the SNMP agent, you get FibreChannelHostPort data in oid nsExtendOutLine{ .1.3.6.1.4.1.8072.1.3.2.4.1.2}.

  4. The output is indexed as follows:

  5. nsExtendOutline.”3.87.87.78”.index = Output //represents "3(3 chars).WWN(87.87.78 in ASCII)”

  6. nsExtendOutline.”4.116.121.112.101”.index = Output //represents "4(4 chars).type(116.121.112.101 in ASCII)”

  7. nsExtendOutline.”10.102.97.98.114.105.99.78.97.109.101”.index = Output //represents “10(10 chars).fabricName(102.97.98.114.105.99.78.97.109.101 in ASCII)”

  8. nsExtendOutline.”8.110.111.100.101.78.97.109.101”.index = Output //represents “8(8 chars).nodeName(110.111.100.101.78.97.109.101 in ASCII)”

  9. nsExtendOutline.”12.115.121.109.98.111.108.105.99.78.97.109.101”.index = Output //represents “12(12 chars).symbolicName(115.121.109.98.111.108.105.99.78.97.109.101 in ASCII)”

    Where the index is a number per FibreChannelHostPort configured on KVM, and it starts from 1.

  10. If snmpd is not able to execute the command because of some permissions, the same oid will provide the output, which is dumped in log as unmatched data.

    Note:

    These configurations must be copied as is without changing any content.