Dear readers,
I'm creating a template for a MSA2324fc. I'm almost finished, except for one thing. I would like to read the error log from the device. But it seems that when an error is generated the error gets a unique random generatad oid. So i'm nog able to read out the errors, since i will not know what oid the error gets.
Anyone had a similar case? Please let me know.
Example screen:
Name/OID: .1.3.6.1.3.94.1.11.1.9.32.128.0.192.255.216.182.10 6.0.0.0.0.0.0.0.0.700; Value (OctetString): Vdisk scrub completed, no errors found. (Vdisk: vd01, SN: 00c0ffd8f9c600003eaa1d4b00000000)
Name/OID: .1.3.6.1.3.94.1.11.1.9.32.128.0.192.255.216.182.10 6.0.0.0.0.0.0.0.0.701; Value (OctetString): Disk enclosure event: fault. (enclosure: 1, WWN: 500C0FF0D8B66A3C) power supply 2, power supply status: Under voltage, DC failure
Name/OID: .1.3.6.1.3.94.1.11.1.9.32.128.0.192.255.216.182.10 6.0.0.0.0.0.0.0.0.702; Value (OctetString): FRU type: A/C PSU, Right, problem: encl 1. Product ID: , SN: rev: . Related event ID: 10000701, type: 168
Name/OID: .1.3.6.1.3.94.1.11.1.9.32.128.0.192.255.216.182.10 6.0.0.0.0.0.0.0.0.703; Value (OctetString): Auto-write-through trigger event: power supply failed.
Name/OID: .1.3.6.1.3.94.1.11.1.9.32.128.0.192.255.216.182.10 6.0.0.0.0.0.0.0.0.704; Value (OctetString): A scrub-vdisk job was started. (vdisk: vd01, SN: 00c0ffd8f9c600003eaa1d4b00000000)
Name/OID: .1.3.6.1.3.94.1.11.1.9.32.128.0.192.255.216.182.10 6.0.0.0.0.0.0.0.0.705; Value (OctetString): Vdisk scrub completed, no errors found. (Vdisk: vd01, SN: 00c0ffd8f9c600003eaa1d4b00000000)
Name/OID: .1.3.6.1.3.94.1.11.1.9.32.128.0.192.255.216.182.10 6.0.0.0.0.0.0.0.0.706; Value (OctetString): A scrub-vdisk job was started. (vdisk: vd01, SN: 00c0ffd8f9c600003eaa1d4b00000000)
I'm creating a template for a MSA2324fc. I'm almost finished, except for one thing. I would like to read the error log from the device. But it seems that when an error is generated the error gets a unique random generatad oid. So i'm nog able to read out the errors, since i will not know what oid the error gets.
Anyone had a similar case? Please let me know.
Example screen:
Name/OID: .1.3.6.1.3.94.1.11.1.9.32.128.0.192.255.216.182.10 6.0.0.0.0.0.0.0.0.700; Value (OctetString): Vdisk scrub completed, no errors found. (Vdisk: vd01, SN: 00c0ffd8f9c600003eaa1d4b00000000)
Name/OID: .1.3.6.1.3.94.1.11.1.9.32.128.0.192.255.216.182.10 6.0.0.0.0.0.0.0.0.701; Value (OctetString): Disk enclosure event: fault. (enclosure: 1, WWN: 500C0FF0D8B66A3C) power supply 2, power supply status: Under voltage, DC failure
Name/OID: .1.3.6.1.3.94.1.11.1.9.32.128.0.192.255.216.182.10 6.0.0.0.0.0.0.0.0.702; Value (OctetString): FRU type: A/C PSU, Right, problem: encl 1. Product ID: , SN: rev: . Related event ID: 10000701, type: 168
Name/OID: .1.3.6.1.3.94.1.11.1.9.32.128.0.192.255.216.182.10 6.0.0.0.0.0.0.0.0.703; Value (OctetString): Auto-write-through trigger event: power supply failed.
Name/OID: .1.3.6.1.3.94.1.11.1.9.32.128.0.192.255.216.182.10 6.0.0.0.0.0.0.0.0.704; Value (OctetString): A scrub-vdisk job was started. (vdisk: vd01, SN: 00c0ffd8f9c600003eaa1d4b00000000)
Name/OID: .1.3.6.1.3.94.1.11.1.9.32.128.0.192.255.216.182.10 6.0.0.0.0.0.0.0.0.705; Value (OctetString): Vdisk scrub completed, no errors found. (Vdisk: vd01, SN: 00c0ffd8f9c600003eaa1d4b00000000)
Name/OID: .1.3.6.1.3.94.1.11.1.9.32.128.0.192.255.216.182.10 6.0.0.0.0.0.0.0.0.706; Value (OctetString): A scrub-vdisk job was started. (vdisk: vd01, SN: 00c0ffd8f9c600003eaa1d4b00000000)