Within HPE OneView you can configure SNMPv1 read community string. What is the purpose of this feature?

Question

Options

• AThis is an SNMP community string that will be used when traps are forwarded to a WBEM
• BThis is an SNMP community string that will be used when traps are forwarded to other SNMP
• CThis is an SNMP community string that will be used to receive a trap's SNMP Agent
• DThis is an SNMP community string that will be used to receive traps from HPE Onboard

• A
  4% (2)
• B
  2% (1)
• C
  92% (45)
• D
  2% (1)

Explanation

Option C is correct because the SNMPv1 read community string in HPE OneView acts as a shared password that OneView uses to authenticate and accept incoming SNMP traps from managed devices' SNMP Agents - if the community string in the trap doesn't match, OneView will discard it.

Why the distractors are wrong:

• A is wrong because WBEM (Web-Based Enterprise Management) is an entirely different management protocol - SNMP community strings have no role in forwarding to WBEM systems.
• B is wrong because forwarding traps to other SNMP managers describes a proxy/relay scenario, which is not the function of the read community string configured in OneView.
• D is wrong because it's too narrow - HPE Onboard Administrator is just one specific device type, while the read community string applies broadly to any SNMP Agent sending traps to OneView.

Memory tip: Think "Read = Receive from Agents." OneView needs to read (authenticate) the community string embedded in any incoming trap before accepting it - so the read community string is always about receiving from an SNMP Agent, not about sending or forwarding anywhere.

No community discussion yet for this question.