[ZBX-16948] Template Server Cisco UCS SNMPv2 (False alarms for Disks) Created: 2019 Nov 19 Updated: 2019 Nov 22 Resolved: 2019 Nov 22 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Templates (T) |
Affects Version/s: | 4.4.1 |
Fix Version/s: | None |
Type: | Incident report | Priority: | Minor |
Reporter: | Archie Spangler | Assignee: | Aigars Kadikis |
Resolution: | Fixed | Votes: | 0 |
Labels: | templates | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
Linux Redhat 7. |
Attachments: |
![]() ![]() |
Description |
I am seeing issues where the cucsStorageControllerOperState (1.3.6.1.4.1.9.9.719.1.45.1.1.6.{#SNMPINDEX}) is "unknown" for all Controllers in the table? Is this a problem with USC / snmp? I see the same for both B-Series and C-Series systems. We are running UCS 5.0(3)N2(4.02a) Example: Name/OID: cucsStorageControllerOperState.23753313; Value (Integer): unknown (0) This causes "Disk array controller status" Zabbix problems for all the disks. |
Comments |
Comment by Aigars Kadikis [ 2019 Nov 20 ] |
By using online snmptranslate I see the number 0 is equivalent to state 'unknown':
Please if the integer value really is 0! snmpwalk -On -v2c -cpublic <ip> .1.3.6.1.4.1.9.9.719.1.45.1.1.6
|
Comment by Archie Spangler [ 2019 Nov 20 ] |
Here are the results of the command. This is why I was thinking that maybe it's a problems with Cisco not populating these values properly. If you think that is the case, I will open a case with Cisco.
|
Comment by Aigars Kadikis [ 2019 Nov 22 ] |
Yes, the behavior from Zabbix perspective is as expected. Please contact Cisco if the numbers are not correct. |