Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Document Version Release Date Details 2 November 29, 2021 Updated the Resolution with the fix, which is in HPE OneView versions 4.20.03 and 5.0. 1 August 12, 2019 Original Document Release Simple Network Management Protocol (SNMP) version 3 (SNMPv3) requires that an application recognize the identifier (snmpEngineID) of the remote SNMP protocol engine in order to retrieve or manipulate objects maintained on the remote SNMP agent. However, the OneView identifier may not be recognized by third-party software and may prevent any agent from being able to process it. The Request for Comments (RFC) 5343 and 3411 definition require an snmpEngineID value to be between 5 and 32 octets long, and it should be an octet string: SYNTAX OCTET STRING (SIZE(5..32)) HPE OneView SNMPv3 implementation uses an ASCII-encoded character string of 32 ASCII characters, not an octet string. As a result, SNMPv3 will send an ASCII encoding that is 64 octets long. For example, " 6665363736653535643038613234353063343636613037333332626430663136 " will be sent, rather than the " fe676e55d08a2450c466a07332bd0f16 " string displayed in the OneView User Interface. As a result, when an SNMPv3 trap is forwarded to BMC software, it will not recognize and process this EngineID value.
Any HPE Oneview version 4.10.X or version 4.20.X.
This issue is fixed in HPE OneView versions 4.20.03 and 5.0. As a workaround, manually set the snmpEngineID using the REST API. To retrieve the current snmpEngineID, use the following REST API call: GET /rest/global-settings/appliance/global/applianceSNMPv3EngineId Auth: abcdefghijklmnopqrstuvwxyz012345 X-Api-Version: 1000 Content-Type: application/json This will produce a response something like the following example: HTTP/1.1 200 OK Date: Mon, 29 Jul 2019 12:25:25 GMT { "category": "global-settings", "created": "2018-04-02T18:19:46.059Z", "description": null, "eTag": null, "group": "global", "modified": "2018-04-02T18:19:46.059Z", "name": "applianceSNMPv3EngineId", "settingCategory": "appliance", "state": null, "status": null, "type": "SettingV2", "uri": "/rest/global-settings/appliance/global/applianceSNMPv3EngineId", "value": "727a4bdf7546bf3e9fdad9776bf11638" } Then, the snmpEngineID should be set to specify a 16 character value, i.e. the first 16 characters of the current value with the following REST API call: PUT /rest/global-settings/appliance/global/applianceSNMPv3EngineId Auth: abcdefghijklmnopqrstuvwxyz012345 X-Api-Version: 500 Content-Type: application/json { "type": "SettingV2", "name": "applianceSNMPv3EngineId", "value": " 727a4bdf7546bf3e" } This will produce a response something like the following example: HTTP/1.1 200 OK Date: Mon, 29 Jul 2019 12:36:06 GMT { "category": "global-settings", "created": "2018-04-02T18:19:46.059Z", "description": null, "eTag": null, "group": "global", "modified": "2019-07-29T12:36:06.681Z", "name": "applianceSNMPv3EngineId", "settingCategory": "appliance", "state": null, "status": null, "type": "SettingV2", "uri": "/rest/global-settings/appliance/global/applianceSNMPv3EngineId", "value": " 727a4bdf7546bf3e" } At this point, the HPE OneView UI will be displayed as the new engine ID, but OneView must be re-started for the new value to be used. RECEIVE PROACTIVE UPDATES : Receive support alerts (such as Customer Advisories), as well as updates on drivers, software, firmware, and customer replaceable components, proactively via e-mail through HPE Subscriber's Choice. Sign up for Subscriber's Choice at the following URL: Proactive Updates Subscription Form. NAVIGATION TIP : For hints on navigating HPE.com to locate the latest drivers, patches, and other support software downloads for HPE systems and Options, refer to the Navigation Tips document . SEARCH TIP : For hints on locating similar documents on HPE.com, refer to the Search Tips Document .