Ad Widget

Collapse

Adding RAID discovery rules to Fujitsu Server template

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • trantor
    Junior Member
    • May 2024
    • 3

    #1

    Adding RAID discovery rules to Fujitsu Server template

    Hi everyone,

    I'm tyring to add raid discovery to this Fujitsu template https://github.com/zabbix/community-..._rx2530_m2/6.0

    I've read a lot of documentation and watch how other templates works but I have an issue creating the item prototype/discovery.

    On other brand like hp/dell only the last part one the OID change like : 1.3.6.1.4.1.674.10892.5.5.1.20.130.4.1.24.X

    The OID of physical drive on Fujitsu servers are note like other servers (hp/dell) that have just the last part that change.

    Here is an output listing physical

    snmpwalk -v2c -c public 192.168.44.99 1.3.6.1.4.1.231.2.49.1.5.2.1.24 ; physical device display name / Device display name
    Code:
    Server with 4 physical disks
    iso.3.6.1.4.1.231.2.49.1.5.2.1.24.0.0.8.0 = STRING: "SAMSUNG MZ7KH480HAHQ-00005 (3)"
    iso.3.6.1.4.1.231.2.49.1.5.2.1.24.0.1.9.0 = STRING: "SAMSUNG MZ7KH480HAHQ-00005 (2)"
    iso.3.6.1.4.1.231.2.49.1.5.2.1.24.0.2.10.0 = STRING: "SAMSUNG MZ7KH480HAHQ-00005 (0)"
    iso.3.6.1.4.1.231.2.49.1.5.2.1.24.0.3.11.0 = STRING: "SAMSUNG MZ7KH480HAHQ-00005 (1)"
    The last 4 digits are different between several others Fujitsu servers, below the coresponding OID :
    Code:
    snmpwalk -v2c -c public 192.168.44.99 1.3.6.1.4.1.231.2.49.1.5.2.1.1 ; Controller number
    iso.3.6.1.4.1.231.2.49.1.5.2.1.1.0.0.8.0 = INTEGER: 0
    iso.3.6.1.4.1.231.2.49.1.5.2.1.1.0.1.9.0 = INTEGER: 0
    iso.3.6.1.4.1.231.2.49.1.5.2.1.1.0.2.10.0 = INTEGER: 0
    iso.3.6.1.4.1.231.2.49.1.5.2.1.1.0.3.11.0 = INTEGER: 0
    
    snmpwalk -v2c -c public 192.168.44.99 1.3.6.1.4.1.231.2.49.1.5.2.1.2 ; Channel/Port number (index) SCSI: bus (channel) number SAS/SATA
    iso.3.6.1.4.1.231.2.49.1.5.2.1.2.0.0.8.0 = INTEGER: 0
    iso.3.6.1.4.1.231.2.49.1.5.2.1.2.0.1.9.0 = INTEGER: 1
    iso.3.6.1.4.1.231.2.49.1.5.2.1.2.0.2.10.0 = INTEGER: 2
    iso.3.6.1.4.1.231.2.49.1.5.2.1.2.0.3.11.0 = INTEGER: 3
    
    snmpwalk -v2c -c public 192.168.44.99 1.3.6.1.4.1.231.2.49.1.5.2.1.3 ; Device target number (index) SCSI: target number (SCSI ID) SAS/SATA:
    iso.3.6.1.4.1.231.2.49.1.5.2.1.3.0.0.8.0 = INTEGER: 8
    iso.3.6.1.4.1.231.2.49.1.5.2.1.3.0.1.9.0 = INTEGER: 9
    iso.3.6.1.4.1.231.2.49.1.5.2.1.3.0.2.10.0 = INTEGER: 10
    iso.3.6.1.4.1.231.2.49.1.5.2.1.3.0.3.11.0 = INTEGER: 11
    
    snmpwalk -v2c -c public 192.168.44.99 1.3.6.1.4.1.231.2.49.1.5.2.1.4 ; Device logical unit number (index) SCSI: logical unit number (SCSI LUN)
    iso.3.6.1.4.1.231.2.49.1.5.2.1.4.0.0.8.0 = INTEGER: 0
    iso.3.6.1.4.1.231.2.49.1.5.2.1.4.0.1.9.0 = INTEGER: 0
    iso.3.6.1.4.1.231.2.49.1.5.2.1.4.0.2.10.0 = INTEGER: 0
    iso.3.6.1.4.1.231.2.49.1.5.2.1.4.0.3.11.0 = INTEGER: 0
    How can I properly configure the discovery rules and the itmes prototype with all these values ?
    May I somehow use some discovery like : iso.3.6.1.4.1.231.2.49.1.5.2.1.24.{#CTRL_NB}.{#POR T_NB}.{#TARGET_NB}.{#LUN_NB} ?
    Or maybe use some MACRO ?

    Does anyone can help me out with this ?

    Regards​
  • murdoua
    Junior Member
    • Dec 2024
    • 8

    #2
    Hi, were you able to make this work? I`m currently monitoring RAID drive via amCLI-based custom sh script and would like to go via extending this snmp template if possible.

    Comment

    Working...