|
|
Post by ratagupt on Apr 5, 2021 4:10:14 GMT
We have a requirement where we want to configure the SNMP trap details, I understand that we can configure the SNMP trap details through the EventDestination schema where we can mention the protocol as SNMP., Here is te example below.
==================================================================
curl -k -H "X-Auth-Token: $token" -X POST
https://${bmc}/redfish/v1/EventService/Subscriptions
-d '{"Destination": "snmp://192.168.31.89:162",
"SubscriptionType": "SNMPTrap",
"DeliveryRetryPolicy": "TerminateAfterRetries",
"Protocol": "SNMPv2c"}'
{
"@message.ExtendedInfo": [
{
"@odata.type": "#Message.v1_0_0.Message",
"Message": "The resource has been created successfully",
"MessageArgs": [],
"MessageId": "Base.1.8.1.Created",
"MessageSeverity": "OK",
"Resolution": "None"
}
]
} ==================================================================
For the SNMP trap details we have defined our own MIB , Does Redfsh mandates the MIB? , that a particular MIB to be implemented by the redfish implementation.?
Or it is up to the implementation that they can define and implement their own MIB and use the redfish to configure the trap configuration(eg: where to send the trap, retry policy etc).
Thanks
Ratan
|
|
|
|
Post by jautor on Apr 5, 2021 18:05:13 GMT
No, this support is only to provide a Redfish method to configure (existing) SNMP support in a product. This was done to allow administrators to fully configure their gear using the Redfish interface, without having to resort to vendor-specific tools or other interfaces. And we would expect a Web GUI to utilize this method as well (since you should be able to build the GUI using only Redfish calls to the service). But that's as far as we go. More "custom" setup of SNMP services, if necessary, could be added as OEM sections...
Jeff
|
|
|
|
Post by ratagupt on Apr 16, 2021 7:19:26 GMT
No, this support is only to provide a Redfish method to configure (existing) SNMP support in a product. This was done to allow administrators to fully configure their gear using the Redfish interface, without having to resort to vendor-specific tools or other interfaces. And we would expect a Web GUI to utilize this method as well (since you should be able to build the GUI using only Redfish calls to the service). But that's as far as we go. More "custom" setup of SNMP services, if necessary, could be added as OEM sections... Jeff Sorry Jeff, I think I was not clear that
There are two parts of SNMP
1) Configure the SNMP trap listener (which definitely we can use the EventDestination schema) which can be used by the GUI
2) How the trap looks like? - Does the SNMP trap to follow some redfish defined mib or Implementation can define on its own MIB?
|
|
|
|
Post by jautor on Apr 16, 2021 16:59:16 GMT
No, this support is only to provide a Redfish method to configure (existing) SNMP support in a product. This was done to allow administrators to fully configure their gear using the Redfish interface, without having to resort to vendor-specific tools or other interfaces. And we would expect a Web GUI to utilize this method as well (since you should be able to build the GUI using only Redfish calls to the service). But that's as far as we go. More "custom" setup of SNMP services, if necessary, could be added as OEM sections... Jeff Sorry Jeff, I think I was not clear that
There are two parts of SNMP
1) Configure the SNMP trap listener (which definitely we can use the EventDestination schema) which can be used by the GUI
2) How the trap looks like? - Does the SNMP trap to follow some redfish defined mib or Implementation can define on its own MIB?
No, there is no Redfish-defined MIB. We're just providing the means to configure the SNMP support on a product, not define the SNMP support itself. So yes, the implementation uses (and, well, has to) whatever MIB definition it chooses. Jeff |
|
